Generated: 2025.02.13 03:04:35 +0000

• -llvm-toolchain-15 (1:15.0.7-15 to -)
  • Migration status for -llvm-toolchain-15 (1:15.0.7-15 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Package not in unstable, will try to remove
• -ntpsec (1.2.3+dfsg1-3 to -)
  • Migration status for -ntpsec (1.2.3+dfsg1-3 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -openstack-meta-packages (0.35 to -)
  • Migration status for -openstack-meta-packages (0.35 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -uw-imap (8:2007f~dfsg-7.1 to -)
  • Migration status for -uw-imap (8:2007f~dfsg-7.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• 389-ds-base_pu (- to 2.3.1+dfsg1-1+deb12u1)
  • Migration status for 389-ds-base_pu (- to 2.3.1+dfsg1-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 389-ds-base/armel has unsatisfiable dependency
    • 389-ds-base-libs/armel has unsatisfiable dependency
    • 389-ds-base/armhf has unsatisfiable dependency
    • 389-ds-base-libs/armhf has unsatisfiable dependency
    • Impossible Depends: 389-ds-base_pu -> libldap-2.5-0/2.5.19+dfsg-1/amd64
    • Impossible Depends: 389-ds-base_pu -> libldap-2.5-0/2.5.19+dfsg-1/arm64
    • Impossible Depends: 389-ds-base_pu -> libldap-2.5-0/2.5.19+dfsg-1/i386
    • Impossible Depends: 389-ds-base_pu -> libldap-2.5-0/2.5.19+dfsg-1/mips64el
    • Impossible Depends: 389-ds-base_pu -> libldap-2.5-0/2.5.19+dfsg-1/ppc64el
    • Impossible Depends: 389-ds-base_pu -> libldap-2.5-0/2.5.19+dfsg-1/s390x
    • NEEDS APPROVAL BY RM
• aclock.app/amd64 (0.4.0+20210312-1 to 0.4.0+20210312-1)
  • Migration status for aclock.app/amd64 (0.4.0+20210312-1 to 0.4.0+20210312-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: aclock.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• aclock.app/arm64 (0.4.0+20210312-1 to 0.4.0+20210312-1)
  • Migration status for aclock.app/arm64 (0.4.0+20210312-1 to 0.4.0+20210312-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: aclock.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• aclock.app/armel (0.4.0+20210312-1 to 0.4.0+20210312-1)
  • Migration status for aclock.app/armel (0.4.0+20210312-1 to 0.4.0+20210312-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: aclock.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• aclock.app/armhf (0.4.0+20210312-1 to 0.4.0+20210312-1)
  • Migration status for aclock.app/armhf (0.4.0+20210312-1 to 0.4.0+20210312-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: aclock.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• aclock.app/i386 (0.4.0+20210312-1 to 0.4.0+20210312-1)
  • Migration status for aclock.app/i386 (0.4.0+20210312-1 to 0.4.0+20210312-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: aclock.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• aclock.app/mips64el (0.4.0+20210312-1 to 0.4.0+20210312-1)
  • Migration status for aclock.app/mips64el (0.4.0+20210312-1 to 0.4.0+20210312-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: aclock.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• aclock.app/ppc64el (0.4.0+20210312-1 to 0.4.0+20210312-1)
  • Migration status for aclock.app/ppc64el (0.4.0+20210312-1 to 0.4.0+20210312-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: aclock.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• aclock.app/riscv64 (0.4.0+20210312-1 to 0.4.0+20210312-1)
  • Migration status for aclock.app/riscv64 (0.4.0+20210312-1 to 0.4.0+20210312-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: aclock.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• aclock.app/s390x (0.4.0+20210312-1 to 0.4.0+20210312-1)
  • Migration status for aclock.app/s390x (0.4.0+20210312-1 to 0.4.0+20210312-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: aclock.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• acmetool/amd64 (0.2.2-2 to 0.2.2-2)
  • Migration status for acmetool/amd64 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: acmetool/amd64 golang-1.23
    • Built-Using: acmetool/amd64 golang-github-mattn-go-runewidth
• acmetool/arm64 (0.2.2-2 to 0.2.2-2)
  • Migration status for acmetool/arm64 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: acmetool/arm64 golang-1.23
    • Built-Using: acmetool/arm64 golang-github-mattn-go-runewidth
• acmetool/armel (0.2.2-2 to 0.2.2-2)
  • Migration status for acmetool/armel (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: acmetool/armel golang-1.23
    • Built-Using: acmetool/armel golang-github-mattn-go-runewidth
• acmetool/armhf (0.2.2-2 to 0.2.2-2)
  • Migration status for acmetool/armhf (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: acmetool/armhf golang-1.23
    • Built-Using: acmetool/armhf golang-github-mattn-go-runewidth
• acmetool/i386 (0.2.2-2 to 0.2.2-2)
  • Migration status for acmetool/i386 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: acmetool/i386 golang-1.23
    • Built-Using: acmetool/i386 golang-github-mattn-go-runewidth
• acmetool/mips64el (0.2.2-2 to 0.2.2-2)
  • Migration status for acmetool/mips64el (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: acmetool/mips64el golang-1.23
    • Built-Using: acmetool/mips64el golang-github-mattn-go-runewidth
• acmetool/ppc64el (0.2.2-2 to 0.2.2-2)
  • Migration status for acmetool/ppc64el (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: acmetool/ppc64el golang-1.23
    • Built-Using: acmetool/ppc64el golang-github-mattn-go-runewidth
• acmetool/riscv64 (0.2.2-2 to 0.2.2-2)
  • Migration status for acmetool/riscv64 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: acmetool/riscv64 golang-1.23
    • Built-Using: acmetool/riscv64 golang-github-mattn-go-runewidth
• acmetool/s390x (0.2.2-2 to 0.2.2-2)
  • Migration status for acmetool/s390x (0.2.2-2 to 0.2.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: acmetool/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: acmetool/s390x golang-1.23
    • Built-Using: acmetool/s390x golang-github-mattn-go-runewidth
• adequate/amd64 (0.17.5 to 0.17.5)
  • Migration status for adequate/amd64 (0.17.5 to 0.17.5): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/amd64 golang-1.23
• adequate/arm64 (0.17.5 to 0.17.5)
  • Migration status for adequate/arm64 (0.17.5 to 0.17.5): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/arm64 golang-1.23
• adequate/armel (0.17.5 to 0.17.5)
  • Migration status for adequate/armel (0.17.5 to 0.17.5): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/armel golang-1.23
• adequate/armhf (0.17.5 to 0.17.5)
  • Migration status for adequate/armhf (0.17.5 to 0.17.5): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/armhf golang-1.23
• adequate/i386 (0.17.5 to 0.17.5)
  • Migration status for adequate/i386 (0.17.5 to 0.17.5): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/i386 golang-1.23
• adequate/mips64el (0.17.5 to 0.17.5)
  • Migration status for adequate/mips64el (0.17.5 to 0.17.5): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/mips64el golang-1.23
• adequate/ppc64el (0.17.5 to 0.17.5)
  • Migration status for adequate/ppc64el (0.17.5 to 0.17.5): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/ppc64el golang-1.23
• adequate/riscv64 (0.17.5 to 0.17.5)
  • Migration status for adequate/riscv64 (0.17.5 to 0.17.5): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/riscv64 golang-1.23
• adequate/s390x (0.17.5 to 0.17.5)
  • Migration status for adequate/s390x (0.17.5 to 0.17.5): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/s390x golang-1.23
• aerc/amd64 (0.20.0-1 to 0.20.0-1)
  • Migration status for aerc/amd64 (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/amd64 golang-1.23
    • Built-Using: aerc/amd64 golang-github-mattn-go-runewidth
• aerc/arm64 (0.20.0-1 to 0.20.0-1)
  • Migration status for aerc/arm64 (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/arm64 golang-1.23
    • Built-Using: aerc/arm64 golang-github-mattn-go-runewidth
• aerc/armel (0.20.0-1 to 0.20.0-1)
  • Migration status for aerc/armel (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/armel golang-1.23
    • Built-Using: aerc/armel golang-github-mattn-go-runewidth
• aerc/armhf (0.20.0-1 to 0.20.0-1)
  • Migration status for aerc/armhf (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/armhf golang-1.23
    • Built-Using: aerc/armhf golang-github-mattn-go-runewidth
• aerc/i386 (0.20.0-1 to 0.20.0-1)
  • Migration status for aerc/i386 (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/i386 golang-1.23
    • Built-Using: aerc/i386 golang-github-mattn-go-runewidth
• aerc/ppc64el (0.20.0-1 to 0.20.0-1)
  • Migration status for aerc/ppc64el (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/ppc64el golang-1.23
    • Built-Using: aerc/ppc64el golang-github-mattn-go-runewidth
• aerc/riscv64 (0.20.0-1 to 0.20.0-1)
  • Migration status for aerc/riscv64 (0.20.0-1 to 0.20.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: aerc/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: aerc/riscv64 golang-1.23
    • Built-Using: aerc/riscv64 golang-github-mattn-go-runewidth
• aerc/s390x (0.20.0-1 to 0.20.0-1)
  • Migration status for aerc/s390x (0.20.0-1 to 0.20.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: aerc/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: aerc/s390x golang-1.23
    • Built-Using: aerc/s390x golang-github-mattn-go-runewidth
• affiche/amd64 (0.6.0-12 to 0.6.0-12)
  • Migration status for affiche/amd64 (0.6.0-12 to 0.6.0-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: affiche/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• affiche/arm64 (0.6.0-12 to 0.6.0-12)
  • Migration status for affiche/arm64 (0.6.0-12 to 0.6.0-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: affiche/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• affiche/armel (0.6.0-12 to 0.6.0-12)
  • Migration status for affiche/armel (0.6.0-12 to 0.6.0-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: affiche/armel gnustep-make (not considered)
    • Invalidated by dependency
• affiche/armhf (0.6.0-12 to 0.6.0-12)
  • Migration status for affiche/armhf (0.6.0-12 to 0.6.0-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: affiche/armhf gnustep-make (not considered)
    • Invalidated by dependency
• affiche/i386 (0.6.0-12 to 0.6.0-12)
  • Migration status for affiche/i386 (0.6.0-12 to 0.6.0-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: affiche/i386 gnustep-make (not considered)
    • Invalidated by dependency
• affiche/mips64el (0.6.0-12 to 0.6.0-12)
  • Migration status for affiche/mips64el (0.6.0-12 to 0.6.0-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: affiche/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• affiche/ppc64el (0.6.0-12 to 0.6.0-12)
  • Migration status for affiche/ppc64el (0.6.0-12 to 0.6.0-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: affiche/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• affiche/riscv64 (0.6.0-12 to 0.6.0-12)
  • Migration status for affiche/riscv64 (0.6.0-12 to 0.6.0-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: affiche/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• affiche/s390x (0.6.0-12 to 0.6.0-12)
  • Migration status for affiche/s390x (0.6.0-12 to 0.6.0-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: affiche/s390x gnustep-make (not considered)
    • Invalidated by dependency
• age/amd64 (1.2.1-1 to 1.2.1-1)
  • Migration status for age/amd64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/amd64 golang-1.23
• age/arm64 (1.2.1-1 to 1.2.1-1)
  • Migration status for age/arm64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/arm64 golang-1.23
• age/armel (1.2.1-1 to 1.2.1-1)
  • Migration status for age/armel (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/armel golang-1.23
• age/armhf (1.2.1-1 to 1.2.1-1)
  • Migration status for age/armhf (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/armhf golang-1.23
• age/i386 (1.2.1-1 to 1.2.1-1)
  • Migration status for age/i386 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/i386 golang-1.23
• age/ppc64el (1.2.1-1 to 1.2.1-1)
  • Migration status for age/ppc64el (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/ppc64el golang-1.23
• age/riscv64 (1.2.1-1 to 1.2.1-1)
  • Migration status for age/riscv64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/riscv64 golang-1.23
• age/s390x (1.2.1-1 to 1.2.1-1)
  • Migration status for age/s390x (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/s390x golang-1.23
• alertmanager-irc-relay/amd64 (0.4.2-1 to 0.4.2-1)
  • Migration status for alertmanager-irc-relay/amd64 (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: alertmanager-irc-relay/amd64 golang-1.23
• alertmanager-irc-relay/arm64 (0.4.2-1 to 0.4.2-1)
  • Migration status for alertmanager-irc-relay/arm64 (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: alertmanager-irc-relay/arm64 golang-1.23
• alertmanager-irc-relay/armel (0.4.2-1 to 0.4.2-1)
  • Migration status for alertmanager-irc-relay/armel (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: alertmanager-irc-relay/armel golang-1.23
• alertmanager-irc-relay/armhf (0.4.2-1 to 0.4.2-1)
  • Migration status for alertmanager-irc-relay/armhf (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: alertmanager-irc-relay/armhf golang-1.23
• alertmanager-irc-relay/i386 (0.4.2-1 to 0.4.2-1)
  • Migration status for alertmanager-irc-relay/i386 (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: alertmanager-irc-relay/i386 golang-1.23
• alertmanager-irc-relay/mips64el (0.4.2-1 to 0.4.2-1)
  • Migration status for alertmanager-irc-relay/mips64el (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: alertmanager-irc-relay/mips64el golang-1.23
• alertmanager-irc-relay/ppc64el (0.4.2-1 to 0.4.2-1)
  • Migration status for alertmanager-irc-relay/ppc64el (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: alertmanager-irc-relay/ppc64el golang-1.23
• alertmanager-irc-relay/riscv64 (0.4.2-1 to 0.4.2-1)
  • Migration status for alertmanager-irc-relay/riscv64 (0.4.2-1 to 0.4.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: alertmanager-irc-relay/riscv64 prometheus-alertmanager (not considered)
    • Invalidated by built-using
    • Built-Using: alertmanager-irc-relay/riscv64 golang-1.23
    • Built-Using: alertmanager-irc-relay/riscv64 golang-golang-x-text
• alertmanager-irc-relay/s390x (0.4.2-1 to 0.4.2-1)
  • Migration status for alertmanager-irc-relay/s390x (0.4.2-1 to 0.4.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: alertmanager-irc-relay/s390x prometheus-alertmanager (not considered)
    • Invalidated by built-using
    • Built-Using: alertmanager-irc-relay/s390x golang-1.23
    • Built-Using: alertmanager-irc-relay/s390x golang-golang-x-text
• amazon-ecr-credential-helper/amd64 (0.7.1-2.1 to 0.7.1-2.1)
  • Migration status for amazon-ecr-credential-helper/amd64 (0.7.1-2.1 to 0.7.1-2.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amazon-ecr-credential-helper/amd64 golang-1.23
• amazon-ecr-credential-helper/arm64 (0.7.1-2.1 to 0.7.1-2.1)
  • Migration status for amazon-ecr-credential-helper/arm64 (0.7.1-2.1 to 0.7.1-2.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amazon-ecr-credential-helper/arm64 golang-1.23
• amazon-ecr-credential-helper/armel (0.7.1-2.1 to 0.7.1-2.1)
  • Migration status for amazon-ecr-credential-helper/armel (0.7.1-2.1 to 0.7.1-2.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amazon-ecr-credential-helper/armel golang-1.23
• amazon-ecr-credential-helper/armhf (0.7.1-2.1 to 0.7.1-2.1)
  • Migration status for amazon-ecr-credential-helper/armhf (0.7.1-2.1 to 0.7.1-2.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amazon-ecr-credential-helper/armhf golang-1.23
• amazon-ecr-credential-helper/i386 (0.7.1-2.1 to 0.7.1-2.1)
  • Migration status for amazon-ecr-credential-helper/i386 (0.7.1-2.1 to 0.7.1-2.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amazon-ecr-credential-helper/i386 golang-1.23
• amazon-ecr-credential-helper/mips64el (0.7.1-2.1 to 0.7.1-2.1)
  • Migration status for amazon-ecr-credential-helper/mips64el (0.7.1-2.1 to 0.7.1-2.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amazon-ecr-credential-helper/mips64el golang-1.23
• amazon-ecr-credential-helper/ppc64el (0.7.1-2.1 to 0.7.1-2.1)
  • Migration status for amazon-ecr-credential-helper/ppc64el (0.7.1-2.1 to 0.7.1-2.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amazon-ecr-credential-helper/ppc64el golang-1.23
• amazon-ecr-credential-helper/riscv64 (0.7.1-2.1 to 0.7.1-2.1)
  • Migration status for amazon-ecr-credential-helper/riscv64 (0.7.1-2.1 to 0.7.1-2.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amazon-ecr-credential-helper/riscv64 golang-1.23
• amazon-ecr-credential-helper/s390x (0.7.1-2.1 to 0.7.1-2.1)
  • Migration status for amazon-ecr-credential-helper/s390x (0.7.1-2.1 to 0.7.1-2.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amazon-ecr-credential-helper/s390x golang-1.23
• amfora/amd64 (1.10.0-1 to 1.10.0-1)
  • Migration status for amfora/amd64 (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amfora/amd64 golang-1.23
    • Built-Using: amfora/amd64 golang-github-mattn-go-runewidth
• amfora/arm64 (1.10.0-1 to 1.10.0-1)
  • Migration status for amfora/arm64 (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amfora/arm64 golang-1.23
    • Built-Using: amfora/arm64 golang-github-mattn-go-runewidth
• amfora/armel (1.10.0-1 to 1.10.0-1)
  • Migration status for amfora/armel (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amfora/armel golang-1.23
    • Built-Using: amfora/armel golang-github-mattn-go-runewidth
• amfora/armhf (1.10.0-1 to 1.10.0-1)
  • Migration status for amfora/armhf (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amfora/armhf golang-1.23
    • Built-Using: amfora/armhf golang-github-mattn-go-runewidth
• amfora/i386 (1.10.0-1 to 1.10.0-1)
  • Migration status for amfora/i386 (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amfora/i386 golang-1.23
    • Built-Using: amfora/i386 golang-github-mattn-go-runewidth
• amfora/mips64el (1.10.0-1 to 1.10.0-1)
  • Migration status for amfora/mips64el (1.10.0-1 to 1.10.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: amfora/mips64el golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: amfora/mips64el golang-1.23
    • Built-Using: amfora/mips64el golang-github-gdamore-encoding
    • Built-Using: amfora/mips64el golang-github-mattn-go-runewidth
• amfora/ppc64el (1.10.0-1 to 1.10.0-1)
  • Migration status for amfora/ppc64el (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amfora/ppc64el golang-1.23
    • Built-Using: amfora/ppc64el golang-github-mattn-go-runewidth
• amfora/riscv64 (1.10.0-1 to 1.10.0-1)
  • Migration status for amfora/riscv64 (1.10.0-1 to 1.10.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: amfora/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: amfora/riscv64 golang-1.23
    • Built-Using: amfora/riscv64 golang-github-gdamore-encoding
    • Built-Using: amfora/riscv64 golang-github-mattn-go-runewidth
• amfora/s390x (1.10.0-1 to 1.10.0-1)
  • Migration status for amfora/s390x (1.10.0-1 to 1.10.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: amfora/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: amfora/s390x golang-1.23
    • Built-Using: amfora/s390x golang-github-gdamore-encoding
    • Built-Using: amfora/s390x golang-github-mattn-go-runewidth
• android-platform-build-kati/amd64 (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1)
  • Migration status for android-platform-build-kati/amd64 (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: android-platform-build-kati/amd64 golang-1.23
    • Built-Using: android-platform-build-kati/amd64 golang-glog
• android-platform-build-kati/arm64 (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1)
  • Migration status for android-platform-build-kati/arm64 (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: android-platform-build-kati/arm64 golang-1.23
    • Built-Using: android-platform-build-kati/arm64 golang-glog
• android-platform-build-kati/armel (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1)
  • Migration status for android-platform-build-kati/armel (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: android-platform-build-kati/armel golang-1.23
    • Built-Using: android-platform-build-kati/armel golang-glog
• android-platform-build-kati/armhf (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1)
  • Migration status for android-platform-build-kati/armhf (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: android-platform-build-kati/armhf golang-1.23
    • Built-Using: android-platform-build-kati/armhf golang-glog
• android-platform-build-kati/i386 (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1)
  • Migration status for android-platform-build-kati/i386 (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: android-platform-build-kati/i386 golang-1.23
    • Built-Using: android-platform-build-kati/i386 golang-glog
• android-platform-build-kati/mips64el (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1)
  • Migration status for android-platform-build-kati/mips64el (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: android-platform-build-kati/mips64el golang-1.23
    • Built-Using: android-platform-build-kati/mips64el golang-glog
• android-platform-build-kati/ppc64el (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1)
  • Migration status for android-platform-build-kati/ppc64el (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: android-platform-build-kati/ppc64el golang-1.23
    • Built-Using: android-platform-build-kati/ppc64el golang-glog
• android-platform-build-kati/riscv64 (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1)
  • Migration status for android-platform-build-kati/riscv64 (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: android-platform-build-kati/riscv64 golang-1.23
    • Built-Using: android-platform-build-kati/riscv64 golang-glog
• android-platform-build-kati/s390x (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1)
  • Migration status for android-platform-build-kati/s390x (10.0.0+r32+git20220314.09dfa26c4e59-7.1 to 10.0.0+r32+git20220314.09dfa26c4e59-7.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: android-platform-build-kati/s390x golang-1.23
    • Built-Using: android-platform-build-kati/s390x golang-glog
• aptly/amd64 (1.6.0+ds1-3 to 1.6.0+ds1-3)
  • Migration status for aptly/amd64 (1.6.0+ds1-3 to 1.6.0+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/amd64 golang-1.23
    • Built-Using: aptly/amd64 golang-github-mattn-go-runewidth
• aptly/arm64 (1.6.0+ds1-3 to 1.6.0+ds1-3)
  • Migration status for aptly/arm64 (1.6.0+ds1-3 to 1.6.0+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/arm64 golang-1.23
    • Built-Using: aptly/arm64 golang-github-mattn-go-runewidth
• aptly/armel (1.6.0+ds1-3 to 1.6.0+ds1-3)
  • Migration status for aptly/armel (1.6.0+ds1-3 to 1.6.0+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/armel golang-1.23
    • Built-Using: aptly/armel golang-github-mattn-go-runewidth
• aptly/armhf (1.6.0+ds1-3 to 1.6.0+ds1-3)
  • Migration status for aptly/armhf (1.6.0+ds1-3 to 1.6.0+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/armhf golang-1.23
    • Built-Using: aptly/armhf golang-github-mattn-go-runewidth
• aptly/i386 (1.6.0+ds1-3 to 1.6.0+ds1-3)
  • Migration status for aptly/i386 (1.6.0+ds1-3 to 1.6.0+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/i386 golang-1.23
    • Built-Using: aptly/i386 golang-github-mattn-go-runewidth
• aptly/ppc64el (1.6.0+ds1-3 to 1.6.0+ds1-3)
  • Migration status for aptly/ppc64el (1.6.0+ds1-3 to 1.6.0+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/ppc64el golang-1.23
    • Built-Using: aptly/ppc64el golang-github-mattn-go-runewidth
• aptly/riscv64 (1.6.0+ds1-3 to 1.6.0+ds1-3)
  • Migration status for aptly/riscv64 (1.6.0+ds1-3 to 1.6.0+ds1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: aptly/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: aptly/riscv64 golang-1.23
    • Built-Using: aptly/riscv64 golang-github-mattn-go-runewidth
• aptly/s390x (1.6.0+ds1-3 to 1.6.0+ds1-3)
  • Migration status for aptly/s390x (1.6.0+ds1-3 to 1.6.0+ds1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: aptly/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: aptly/s390x golang-1.23
    • Built-Using: aptly/s390x golang-github-mattn-go-runewidth
• apvlv/amd64 (0.7.0-alpha-2 to 0.7.0-alpha-2)
  • Migration status for apvlv/amd64 (0.7.0-alpha-2 to 0.7.0-alpha-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: apvlv/amd64 mupdf (not considered)
    • Invalidated by dependency
• apvlv/arm64 (0.7.0-alpha-2 to 0.7.0-alpha-2)
  • Migration status for apvlv/arm64 (0.7.0-alpha-2 to 0.7.0-alpha-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: apvlv/arm64 mupdf (not considered)
    • Invalidated by dependency
• apvlv/armhf (0.7.0-alpha-2 to 0.7.0-alpha-2)
  • Migration status for apvlv/armhf (0.7.0-alpha-2 to 0.7.0-alpha-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: apvlv/armhf mupdf (not considered)
    • Invalidated by dependency
• apvlv/i386 (0.7.0-alpha-2 to 0.7.0-alpha-2)
  • Migration status for apvlv/i386 (0.7.0-alpha-2 to 0.7.0-alpha-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: apvlv/i386 mupdf (not considered)
    • Invalidated by dependency
• assetfinder/amd64 (0.1.1-1 to 0.1.1-1)
  • Migration status for assetfinder/amd64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: assetfinder/amd64 golang-1.23
• assetfinder/arm64 (0.1.1-1 to 0.1.1-1)
  • Migration status for assetfinder/arm64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: assetfinder/arm64 golang-1.23
• assetfinder/armel (0.1.1-1 to 0.1.1-1)
  • Migration status for assetfinder/armel (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: assetfinder/armel golang-1.23
• assetfinder/armhf (0.1.1-1 to 0.1.1-1)
  • Migration status for assetfinder/armhf (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: assetfinder/armhf golang-1.23
• assetfinder/i386 (0.1.1-1 to 0.1.1-1)
  • Migration status for assetfinder/i386 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: assetfinder/i386 golang-1.23
• assetfinder/mips64el (0.1.1-1 to 0.1.1-1)
  • Migration status for assetfinder/mips64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: assetfinder/mips64el golang-1.23
• assetfinder/ppc64el (0.1.1-1 to 0.1.1-1)
  • Migration status for assetfinder/ppc64el (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: assetfinder/ppc64el golang-1.23
• assetfinder/riscv64 (0.1.1-1 to 0.1.1-1)
  • Migration status for assetfinder/riscv64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: assetfinder/riscv64 golang-1.23
• assetfinder/s390x (0.1.1-1 to 0.1.1-1)
  • Migration status for assetfinder/s390x (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: assetfinder/s390x golang-1.23
• aws-nuke/amd64 (2.16.0-1 to 2.16.0-1)
  • Migration status for aws-nuke/amd64 (2.16.0-1 to 2.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aws-nuke/amd64 golang-1.23
• aws-nuke/arm64 (2.16.0-1 to 2.16.0-1)
  • Migration status for aws-nuke/arm64 (2.16.0-1 to 2.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aws-nuke/arm64 golang-1.23
• aws-nuke/armel (2.16.0-1 to 2.16.0-1)
  • Migration status for aws-nuke/armel (2.16.0-1 to 2.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aws-nuke/armel golang-1.23
• aws-nuke/armhf (2.16.0-1 to 2.16.0-1)
  • Migration status for aws-nuke/armhf (2.16.0-1 to 2.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aws-nuke/armhf golang-1.23
• aws-nuke/i386 (2.16.0-1 to 2.16.0-1)
  • Migration status for aws-nuke/i386 (2.16.0-1 to 2.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aws-nuke/i386 golang-1.23
• aws-nuke/ppc64el (2.16.0-1 to 2.16.0-1)
  • Migration status for aws-nuke/ppc64el (2.16.0-1 to 2.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aws-nuke/ppc64el golang-1.23
• aws-nuke/s390x (2.16.0-1 to 2.16.0-1)
  • Migration status for aws-nuke/s390x (2.16.0-1 to 2.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aws-nuke/s390x golang-1.23
• badger/amd64 (2.2007.2-4 to 2.2007.2-4)
  • Migration status for badger/amd64 (2.2007.2-4 to 2.2007.2-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: badger/amd64 golang-1.23
• badger/arm64 (2.2007.2-4 to 2.2007.2-4)
  • Migration status for badger/arm64 (2.2007.2-4 to 2.2007.2-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: badger/arm64 golang-1.23
• badger/armel (2.2007.2-4 to 2.2007.2-4)
  • Migration status for badger/armel (2.2007.2-4 to 2.2007.2-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: badger/armel golang-1.23
• badger/armhf (2.2007.2-4 to 2.2007.2-4)
  • Migration status for badger/armhf (2.2007.2-4 to 2.2007.2-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: badger/armhf golang-1.23
• badger/i386 (2.2007.2-4 to 2.2007.2-4)
  • Migration status for badger/i386 (2.2007.2-4 to 2.2007.2-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: badger/i386 golang-1.23
• badger/riscv64 (2.2007.2-4 to 2.2007.2-4)
  • Migration status for badger/riscv64 (2.2007.2-4 to 2.2007.2-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: badger/riscv64 golang-1.23
• badger/s390x (2.2007.2-4 to 2.2007.2-4)
  • Migration status for badger/s390x (2.2007.2-4 to 2.2007.2-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: badger/s390x golang-1.23
• balboa/amd64 (2.0.0+ds-6 to 2.0.0+ds-6)
  • Migration status for balboa/amd64 (2.0.0+ds-6 to 2.0.0+ds-6): 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
    • Built-Using: balboa/amd64 golang-1.23
• balboa/arm64 (2.0.0+ds-6 to 2.0.0+ds-6)
  • Migration status for balboa/arm64 (2.0.0+ds-6 to 2.0.0+ds-6): 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
    • Built-Using: balboa/arm64 golang-1.23
• balboa/armel (2.0.0+ds-6 to 2.0.0+ds-6)
  • Migration status for balboa/armel (2.0.0+ds-6 to 2.0.0+ds-6): 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
    • Built-Using: balboa/armel golang-1.23
• balboa/armhf (2.0.0+ds-6 to 2.0.0+ds-6)
  • Migration status for balboa/armhf (2.0.0+ds-6 to 2.0.0+ds-6): 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
    • Built-Using: balboa/armhf golang-1.23
• balboa/i386 (2.0.0+ds-6 to 2.0.0+ds-6)
  • Migration status for balboa/i386 (2.0.0+ds-6 to 2.0.0+ds-6): 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
    • Built-Using: balboa/i386 golang-1.23
• balboa/mips64el (2.0.0+ds-6 to 2.0.0+ds-6)
  • Migration status for balboa/mips64el (2.0.0+ds-6 to 2.0.0+ds-6): 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
    • Built-Using: balboa/mips64el golang-1.23
• balboa/ppc64el (2.0.0+ds-6 to 2.0.0+ds-6)
  • Migration status for balboa/ppc64el (2.0.0+ds-6 to 2.0.0+ds-6): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: balboa/ppc64el rocksdb (not considered)
    • Invalidated by dependency
    • Built-Using: balboa/ppc64el golang-1.23
• balboa/riscv64 (2.0.0+ds-6 to 2.0.0+ds-6)
  • Migration status for balboa/riscv64 (2.0.0+ds-6 to 2.0.0+ds-6): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: balboa/riscv64 rocksdb (not considered)
    • Invalidated by dependency
    • Built-Using: balboa/riscv64 golang-1.23
• balboa/s390x (2.0.0+ds-6 to 2.0.0+ds-6)
  • Migration status for balboa/s390x (2.0.0+ds-6 to 2.0.0+ds-6): 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
    • Built-Using: balboa/s390x golang-1.23
• balloon/amd64 (1.1.1-2 to 1.1.1-2)
  • Migration status for balloon/amd64 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: balloon/amd64 golang-1.23
• balloon/arm64 (1.1.1-2 to 1.1.1-2)
  • Migration status for balloon/arm64 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: balloon/arm64 golang-1.23
• balloon/armel (1.1.1-2 to 1.1.1-2)
  • Migration status for balloon/armel (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: balloon/armel golang-1.23
• balloon/armhf (1.1.1-2 to 1.1.1-2)
  • Migration status for balloon/armhf (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: balloon/armhf golang-1.23
• balloon/i386 (1.1.1-2 to 1.1.1-2)
  • Migration status for balloon/i386 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: balloon/i386 golang-1.23
• balloon/mips64el (1.1.1-2 to 1.1.1-2)
  • Migration status for balloon/mips64el (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: balloon/mips64el golang-1.23
• balloon/ppc64el (1.1.1-2 to 1.1.1-2)
  • Migration status for balloon/ppc64el (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: balloon/ppc64el golang-1.23
• balloon/riscv64 (1.1.1-2 to 1.1.1-2)
  • Migration status for balloon/riscv64 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: balloon/riscv64 golang-1.23
• balloon/s390x (1.1.1-2 to 1.1.1-2)
  • Migration status for balloon/s390x (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: balloon/s390x golang-1.23
• batmon.app/amd64 (0.9-4 to 0.9-4)
  • Migration status for batmon.app/amd64 (0.9-4 to 0.9-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: batmon.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• batmon.app/arm64 (0.9-4 to 0.9-4)
  • Migration status for batmon.app/arm64 (0.9-4 to 0.9-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: batmon.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• batmon.app/armel (0.9-4 to 0.9-4)
  • Migration status for batmon.app/armel (0.9-4 to 0.9-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: batmon.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• batmon.app/armhf (0.9-4 to 0.9-4)
  • Migration status for batmon.app/armhf (0.9-4 to 0.9-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: batmon.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• batmon.app/i386 (0.9-4 to 0.9-4)
  • Migration status for batmon.app/i386 (0.9-4 to 0.9-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: batmon.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• batmon.app/mips64el (0.9-4 to 0.9-4)
  • Migration status for batmon.app/mips64el (0.9-4 to 0.9-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: batmon.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• batmon.app/ppc64el (0.9-4 to 0.9-4)
  • Migration status for batmon.app/ppc64el (0.9-4 to 0.9-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: batmon.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• batmon.app/riscv64 (0.9-4 to 0.9-4)
  • Migration status for batmon.app/riscv64 (0.9-4 to 0.9-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: batmon.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• batmon.app/s390x (0.9-4 to 0.9-4)
  • Migration status for batmon.app/s390x (0.9-4 to 0.9-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: batmon.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• bettercap/amd64 (2.33.0-1 to 2.33.0-1)
  • Migration status for bettercap/amd64 (2.33.0-1 to 2.33.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bettercap/amd64 golang-1.23
• bettercap/arm64 (2.33.0-1 to 2.33.0-1)
  • Migration status for bettercap/arm64 (2.33.0-1 to 2.33.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bettercap/arm64 golang-1.23
• bettercap/armel (2.33.0-1 to 2.33.0-1)
  • Migration status for bettercap/armel (2.33.0-1 to 2.33.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bettercap/armel golang-1.23
• bettercap/armhf (2.33.0-1 to 2.33.0-1)
  • Migration status for bettercap/armhf (2.33.0-1 to 2.33.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bettercap/armhf golang-1.23
• bettercap/i386 (2.33.0-1 to 2.33.0-1)
  • Migration status for bettercap/i386 (2.33.0-1 to 2.33.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bettercap/i386 golang-1.23
• bettercap/ppc64el (2.33.0-1 to 2.33.0-1)
  • Migration status for bettercap/ppc64el (2.33.0-1 to 2.33.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bettercap/ppc64el golang-1.23
• bettercap/riscv64 (2.33.0-1 to 2.33.0-1)
  • Migration status for bettercap/riscv64 (2.33.0-1 to 2.33.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: bettercap/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: bettercap/riscv64 golang-1.23
• bettercap/s390x (2.33.0-1 to 2.33.0-1)
  • Migration status for bettercap/s390x (2.33.0-1 to 2.33.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: bettercap/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: bettercap/s390x golang-1.23
• bind9_pu (1:9.20.4-4 to 1:9.18.33-1~deb12u2)
  • Migration status for bind9_pu (1:9.20.4-4 to 1:9.18.33-1~deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: bind9 is newer in the target suite (1:9.20.4-4 1:9.18.33-1~deb12u2)
• bombadillo/amd64 (2.4.0-1 to 2.4.0-1)
  • Migration status for bombadillo/amd64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bombadillo/amd64 golang-1.23
• bombadillo/arm64 (2.4.0-1 to 2.4.0-1)
  • Migration status for bombadillo/arm64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bombadillo/arm64 golang-1.23
• bombadillo/armel (2.4.0-1 to 2.4.0-1)
  • Migration status for bombadillo/armel (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bombadillo/armel golang-1.23
• bombadillo/armhf (2.4.0-1 to 2.4.0-1)
  • Migration status for bombadillo/armhf (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bombadillo/armhf golang-1.23
• bombadillo/i386 (2.4.0-1 to 2.4.0-1)
  • Migration status for bombadillo/i386 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bombadillo/i386 golang-1.23
• bombadillo/mips64el (2.4.0-1 to 2.4.0-1)
  • Migration status for bombadillo/mips64el (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bombadillo/mips64el golang-1.23
• bombadillo/ppc64el (2.4.0-1 to 2.4.0-1)
  • Migration status for bombadillo/ppc64el (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bombadillo/ppc64el golang-1.23
• bombadillo/riscv64 (2.4.0-1 to 2.4.0-1)
  • Migration status for bombadillo/riscv64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bombadillo/riscv64 golang-1.23
• bombadillo/s390x (2.4.0-1 to 2.4.0-1)
  • Migration status for bombadillo/s390x (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bombadillo/s390x golang-1.23
• bpftop/riscv64 (0.5.2.20.gc23a822-1 to 0.5.2.20.gc23a822-1)
  • Migration status for bpftop/riscv64 (0.5.2.20.gc23a822-1 to 0.5.2.20.gc23a822-1): Will attempt migration (Any information below is purely informational)
• bpftop/s390x (0.5.2.20.gc23a822-1 to 0.5.2.20.gc23a822-1)
  • Migration status for bpftop/s390x (0.5.2.20.gc23a822-1 to 0.5.2.20.gc23a822-1): Will attempt migration (Any information below is purely informational)
• browserpass/amd64 (3.7.2-1 to 3.7.2-1)
  • Migration status for browserpass/amd64 (3.7.2-1 to 3.7.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: browserpass/amd64 golang-1.23
• browserpass/arm64 (3.7.2-1 to 3.7.2-1)
  • Migration status for browserpass/arm64 (3.7.2-1 to 3.7.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: browserpass/arm64 golang-1.23
• browserpass/armel (3.7.2-1 to 3.7.2-1)
  • Migration status for browserpass/armel (3.7.2-1 to 3.7.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: browserpass/armel golang-1.23
• browserpass/armhf (3.7.2-1 to 3.7.2-1)
  • Migration status for browserpass/armhf (3.7.2-1 to 3.7.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: browserpass/armhf golang-1.23
• browserpass/i386 (3.7.2-1 to 3.7.2-1)
  • Migration status for browserpass/i386 (3.7.2-1 to 3.7.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: browserpass/i386 golang-1.23
• browserpass/mips64el (3.7.2-1 to 3.7.2-1)
  • Migration status for browserpass/mips64el (3.7.2-1 to 3.7.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: browserpass/mips64el golang-1.23
• browserpass/ppc64el (3.7.2-1 to 3.7.2-1)
  • Migration status for browserpass/ppc64el (3.7.2-1 to 3.7.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: browserpass/ppc64el golang-1.23
• browserpass/riscv64 (3.7.2-1 to 3.7.2-1)
  • Migration status for browserpass/riscv64 (3.7.2-1 to 3.7.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: browserpass/riscv64 golang-1.23
• browserpass/s390x (3.7.2-1 to 3.7.2-1)
  • Migration status for browserpass/s390x (3.7.2-1 to 3.7.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: browserpass/s390x golang-1.23
• bup_pu (0.33.7-1 to 0.33.7-1~deb12u1)
  • Migration status for bup_pu (0.33.7-1 to 0.33.7-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: bup is newer in the target suite (0.33.7-1 0.33.7-1~deb12u1)
• burrow/amd64 (1.2.1-4 to 1.2.1-4)
  • Migration status for burrow/amd64 (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/amd64 golang-1.23
• burrow/arm64 (1.2.1-4 to 1.2.1-4)
  • Migration status for burrow/arm64 (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/arm64 golang-1.23
• burrow/armel (1.2.1-4 to 1.2.1-4)
  • Migration status for burrow/armel (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/armel golang-1.23
• burrow/armhf (1.2.1-4 to 1.2.1-4)
  • Migration status for burrow/armhf (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/armhf golang-1.23
• burrow/i386 (1.2.1-4 to 1.2.1-4)
  • Migration status for burrow/i386 (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/i386 golang-1.23
• burrow/mips64el (1.2.1-4 to 1.2.1-4)
  • Migration status for burrow/mips64el (1.2.1-4 to 1.2.1-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: burrow/mips64el golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: burrow/mips64el golang-1.23
• burrow/ppc64el (1.2.1-4 to 1.2.1-4)
  • Migration status for burrow/ppc64el (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/ppc64el golang-1.23
• burrow/riscv64 (1.2.1-4 to 1.2.1-4)
  • Migration status for burrow/riscv64 (1.2.1-4 to 1.2.1-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: burrow/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: burrow/riscv64 golang-1.23
• c2go/amd64 (0.26.11-1 to 0.26.11-1)
  • Migration status for c2go/amd64 (0.26.11-1 to 0.26.11-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/amd64 golang-1.23
• c2go/arm64 (0.26.11-1 to 0.26.11-1)
  • Migration status for c2go/arm64 (0.26.11-1 to 0.26.11-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/arm64 golang-1.23
• c2go/armel (0.26.11-1 to 0.26.11-1)
  • Migration status for c2go/armel (0.26.11-1 to 0.26.11-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/armel golang-1.23
• c2go/armhf (0.26.11-1 to 0.26.11-1)
  • Migration status for c2go/armhf (0.26.11-1 to 0.26.11-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/armhf golang-1.23
• c2go/i386 (0.26.11-1 to 0.26.11-1)
  • Migration status for c2go/i386 (0.26.11-1 to 0.26.11-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/i386 golang-1.23
• c2go/mips64el (0.26.11-1 to 0.26.11-1)
  • Migration status for c2go/mips64el (0.26.11-1 to 0.26.11-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/mips64el golang-1.23
• c2go/ppc64el (0.26.11-1 to 0.26.11-1)
  • Migration status for c2go/ppc64el (0.26.11-1 to 0.26.11-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/ppc64el golang-1.23
• c2go/riscv64 (0.26.11-1 to 0.26.11-1)
  • Migration status for c2go/riscv64 (0.26.11-1 to 0.26.11-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/riscv64 golang-1.23
• c2go/s390x (0.26.11-1 to 0.26.11-1)
  • Migration status for c2go/s390x (0.26.11-1 to 0.26.11-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/s390x golang-1.23
• caddy/amd64 (2.6.2-8 to 2.6.2-8)
  • Migration status for caddy/amd64 (2.6.2-8 to 2.6.2-8): Will attempt migration (Any information below is purely informational)
    • Built-Using: caddy/amd64 golang-1.23
• caddy/arm64 (2.6.2-8 to 2.6.2-8)
  • Migration status for caddy/arm64 (2.6.2-8 to 2.6.2-8): Will attempt migration (Any information below is purely informational)
    • Built-Using: caddy/arm64 golang-1.23
• caddy/armel (2.6.2-8 to 2.6.2-8)
  • Migration status for caddy/armel (2.6.2-8 to 2.6.2-8): Will attempt migration (Any information below is purely informational)
    • Built-Using: caddy/armel golang-1.23
• caddy/armhf (2.6.2-8 to 2.6.2-8)
  • Migration status for caddy/armhf (2.6.2-8 to 2.6.2-8): Will attempt migration (Any information below is purely informational)
    • Built-Using: caddy/armhf golang-1.23
• caddy/i386 (2.6.2-8 to 2.6.2-8)
  • Migration status for caddy/i386 (2.6.2-8 to 2.6.2-8): Will attempt migration (Any information below is purely informational)
    • Built-Using: caddy/i386 golang-1.23
• caddy/ppc64el (2.6.2-8 to 2.6.2-8)
  • Migration status for caddy/ppc64el (2.6.2-8 to 2.6.2-8): Will attempt migration (Any information below is purely informational)
    • Built-Using: caddy/ppc64el golang-1.23
• caddy/riscv64 (2.6.2-8 to 2.6.2-8)
  • Migration status for caddy/riscv64 (2.6.2-8 to 2.6.2-8): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: caddy/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: caddy/riscv64 golang-1.23
• caddy/s390x (2.6.2-8 to 2.6.2-8)
  • Migration status for caddy/s390x (2.6.2-8 to 2.6.2-8): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: caddy/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: caddy/s390x golang-1.23
• cam2ip/amd64 (1.6-4 to 1.6-4)
  • Migration status for cam2ip/amd64 (1.6-4 to 1.6-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: cam2ip/amd64 golang-1.23
• cam2ip/arm64 (1.6-4 to 1.6-4)
  • Migration status for cam2ip/arm64 (1.6-4 to 1.6-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: cam2ip/arm64 golang-1.23
• cam2ip/armel (1.6-4 to 1.6-4)
  • Migration status for cam2ip/armel (1.6-4 to 1.6-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: cam2ip/armel golang-1.23
• cam2ip/armhf (1.6-4 to 1.6-4)
  • Migration status for cam2ip/armhf (1.6-4 to 1.6-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: cam2ip/armhf golang-1.23
• cam2ip/i386 (1.6-4 to 1.6-4)
  • Migration status for cam2ip/i386 (1.6-4 to 1.6-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: cam2ip/i386 golang-1.23
• cam2ip/mips64el (1.6-4 to 1.6-4)
  • Migration status for cam2ip/mips64el (1.6-4 to 1.6-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: cam2ip/mips64el golang-1.23
• cam2ip/ppc64el (1.6-4 to 1.6-4)
  • Migration status for cam2ip/ppc64el (1.6-4 to 1.6-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: cam2ip/ppc64el golang-1.23
• cam2ip/riscv64 (1.6-4 to 1.6-4)
  • Migration status for cam2ip/riscv64 (1.6-4 to 1.6-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: cam2ip/riscv64 golang-1.23
• cam2ip/s390x (1.6-4 to 1.6-4)
  • Migration status for cam2ip/s390x (1.6-4 to 1.6-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: cam2ip/s390x golang-1.23
• canid/amd64 (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2)
  • Migration status for canid/amd64 (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: canid/amd64 golang-1.23
• canid/arm64 (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2)
  • Migration status for canid/arm64 (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: canid/arm64 golang-1.23
• canid/armel (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2)
  • Migration status for canid/armel (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: canid/armel golang-1.23
• canid/armhf (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2)
  • Migration status for canid/armhf (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: canid/armhf golang-1.23
• canid/i386 (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2)
  • Migration status for canid/i386 (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: canid/i386 golang-1.23
• canid/mips64el (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2)
  • Migration status for canid/mips64el (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: canid/mips64el golang-1.23
• canid/ppc64el (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2)
  • Migration status for canid/ppc64el (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: canid/ppc64el golang-1.23
• canid/riscv64 (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2)
  • Migration status for canid/riscv64 (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: canid/riscv64 golang-1.23
• canid/s390x (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2)
  • Migration status for canid/s390x (0.0~git20180613.007c9af-2 to 0.0~git20180613.007c9af-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: canid/s390x golang-1.23
• cdebootstrap/mips64el (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/mips64el (0.7.8 to 0.7.8): Will attempt migration (Any information below is purely informational)
• cdebootstrap/riscv64 (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/riscv64 (0.7.8 to 0.7.8): Will attempt migration (Any information below is purely informational)
• cdebootstrap/s390x (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/s390x (0.7.8 to 0.7.8): Will attempt migration (Any information below is purely informational)
• cdogs-sdl/mips64el (2.1.0+dfsg-2 to 2.1.0+dfsg-2)
  • Migration status for cdogs-sdl/mips64el (2.1.0+dfsg-2 to 2.1.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• cdogs-sdl/riscv64 (2.1.0+dfsg-2 to 2.1.0+dfsg-2)
  • Migration status for cdogs-sdl/riscv64 (2.1.0+dfsg-2 to 2.1.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• cdogs-sdl/s390x (2.1.0+dfsg-2 to 2.1.0+dfsg-2)
  • Migration status for cdogs-sdl/s390x (2.1.0+dfsg-2 to 2.1.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• certinfo/amd64 (1.0.6+ds1-2 to 1.0.6+ds1-2)
  • Migration status for certinfo/amd64 (1.0.6+ds1-2 to 1.0.6+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certinfo/amd64 golang-1.23
• certinfo/arm64 (1.0.6+ds1-2 to 1.0.6+ds1-2)
  • Migration status for certinfo/arm64 (1.0.6+ds1-2 to 1.0.6+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certinfo/arm64 golang-1.23
• certinfo/armel (1.0.6+ds1-2 to 1.0.6+ds1-2)
  • Migration status for certinfo/armel (1.0.6+ds1-2 to 1.0.6+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certinfo/armel golang-1.23
• certinfo/armhf (1.0.6+ds1-2 to 1.0.6+ds1-2)
  • Migration status for certinfo/armhf (1.0.6+ds1-2 to 1.0.6+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certinfo/armhf golang-1.23
• certinfo/i386 (1.0.6+ds1-2 to 1.0.6+ds1-2)
  • Migration status for certinfo/i386 (1.0.6+ds1-2 to 1.0.6+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certinfo/i386 golang-1.23
• certinfo/mips64el (1.0.6+ds1-2 to 1.0.6+ds1-2)
  • Migration status for certinfo/mips64el (1.0.6+ds1-2 to 1.0.6+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certinfo/mips64el golang-1.23
• certinfo/ppc64el (1.0.6+ds1-2 to 1.0.6+ds1-2)
  • Migration status for certinfo/ppc64el (1.0.6+ds1-2 to 1.0.6+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certinfo/ppc64el golang-1.23
• certinfo/riscv64 (1.0.6+ds1-2 to 1.0.6+ds1-2)
  • Migration status for certinfo/riscv64 (1.0.6+ds1-2 to 1.0.6+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certinfo/riscv64 golang-1.23
• certinfo/s390x (1.0.6+ds1-2 to 1.0.6+ds1-2)
  • Migration status for certinfo/s390x (1.0.6+ds1-2 to 1.0.6+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certinfo/s390x golang-1.23
• certstream-server-go/amd64 (1.7.0-2 to 1.7.0-2)
  • Migration status for certstream-server-go/amd64 (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certstream-server-go/amd64 golang-1.23
• certstream-server-go/arm64 (1.7.0-2 to 1.7.0-2)
  • Migration status for certstream-server-go/arm64 (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certstream-server-go/arm64 golang-1.23
• certstream-server-go/armel (1.7.0-2 to 1.7.0-2)
  • Migration status for certstream-server-go/armel (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certstream-server-go/armel golang-1.23
• certstream-server-go/armhf (1.7.0-2 to 1.7.0-2)
  • Migration status for certstream-server-go/armhf (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certstream-server-go/armhf golang-1.23
• certstream-server-go/i386 (1.7.0-2 to 1.7.0-2)
  • Migration status for certstream-server-go/i386 (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certstream-server-go/i386 golang-1.23
• certstream-server-go/mips64el (1.7.0-2 to 1.7.0-2)
  • Migration status for certstream-server-go/mips64el (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certstream-server-go/mips64el golang-1.23
• certstream-server-go/ppc64el (1.7.0-2 to 1.7.0-2)
  • Migration status for certstream-server-go/ppc64el (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certstream-server-go/ppc64el golang-1.23
• certstream-server-go/riscv64 (1.7.0-2 to 1.7.0-2)
  • Migration status for certstream-server-go/riscv64 (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certstream-server-go/riscv64 golang-1.23
• certstream-server-go/s390x (1.7.0-2 to 1.7.0-2)
  • Migration status for certstream-server-go/s390x (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: certstream-server-go/s390x golang-1.23
• chasquid/amd64 (1.14.0-2 to 1.14.0-2)
  • Migration status for chasquid/amd64 (1.14.0-2 to 1.14.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: chasquid/amd64 golang-1.23
• chasquid/arm64 (1.14.0-2 to 1.14.0-2)
  • Migration status for chasquid/arm64 (1.14.0-2 to 1.14.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: chasquid/arm64 golang-1.23
• chasquid/armel (1.14.0-2 to 1.14.0-2)
  • Migration status for chasquid/armel (1.14.0-2 to 1.14.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: chasquid/armel golang-1.23
• chasquid/armhf (1.14.0-2 to 1.14.0-2)
  • Migration status for chasquid/armhf (1.14.0-2 to 1.14.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: chasquid/armhf golang-1.23
• chasquid/i386 (1.14.0-2 to 1.14.0-2)
  • Migration status for chasquid/i386 (1.14.0-2 to 1.14.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: chasquid/i386 golang-1.23
• chasquid/ppc64el (1.14.0-2 to 1.14.0-2)
  • Migration status for chasquid/ppc64el (1.14.0-2 to 1.14.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: chasquid/ppc64el golang-1.23
• chasquid/riscv64 (1.14.0-2 to 1.14.0-2)
  • Migration status for chasquid/riscv64 (1.14.0-2 to 1.14.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: chasquid/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: chasquid/riscv64 golang-1.23
• chess.app/amd64 (2.8-6 to 2.8-6)
  • Migration status for chess.app/amd64 (2.8-6 to 2.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: chess.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• chess.app/arm64 (2.8-6 to 2.8-6)
  • Migration status for chess.app/arm64 (2.8-6 to 2.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: chess.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• chess.app/armel (2.8-6 to 2.8-6)
  • Migration status for chess.app/armel (2.8-6 to 2.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: chess.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• chess.app/armhf (2.8-6 to 2.8-6)
  • Migration status for chess.app/armhf (2.8-6 to 2.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: chess.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• chess.app/i386 (2.8-6 to 2.8-6)
  • Migration status for chess.app/i386 (2.8-6 to 2.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: chess.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• chess.app/mips64el (2.8-6 to 2.8-6)
  • Migration status for chess.app/mips64el (2.8-6 to 2.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: chess.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• chess.app/ppc64el (2.8-6 to 2.8-6)
  • Migration status for chess.app/ppc64el (2.8-6 to 2.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: chess.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• chess.app/riscv64 (2.8-6 to 2.8-6)
  • Migration status for chess.app/riscv64 (2.8-6 to 2.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: chess.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• chess.app/s390x (2.8-6 to 2.8-6)
  • Migration status for chess.app/s390x (2.8-6 to 2.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: chess.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• chkrootkit/mips64el (0.58b-3 to 0.58b-3)
  • Migration status for chkrootkit/mips64el (0.58b-3 to 0.58b-3): Will attempt migration (Any information below is purely informational)
• chkrootkit/riscv64 (0.58b-3 to 0.58b-3)
  • Migration status for chkrootkit/riscv64 (0.58b-3 to 0.58b-3): Will attempt migration (Any information below is purely informational)
• chkrootkit/s390x (0.58b-3 to 0.58b-3)
  • Migration status for chkrootkit/s390x (0.58b-3 to 0.58b-3): Will attempt migration (Any information below is purely informational)
• chromium_pu (132.0.6834.159-1 to 132.0.6834.159-1~deb12u1)
  • Migration status for chromium_pu (132.0.6834.159-1 to 132.0.6834.159-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: chromium is newer in the target suite (132.0.6834.159-1 132.0.6834.159-1~deb12u1)
• cidr/amd64 (2.2.0-2 to 2.2.0-2)
  • Migration status for cidr/amd64 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cidr/amd64 golang-1.23
• cidr/arm64 (2.2.0-2 to 2.2.0-2)
  • Migration status for cidr/arm64 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cidr/arm64 golang-1.23
• cidr/armel (2.2.0-2 to 2.2.0-2)
  • Migration status for cidr/armel (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cidr/armel golang-1.23
• cidr/armhf (2.2.0-2 to 2.2.0-2)
  • Migration status for cidr/armhf (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cidr/armhf golang-1.23
• cidr/i386 (2.2.0-2 to 2.2.0-2)
  • Migration status for cidr/i386 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cidr/i386 golang-1.23
• cidr/mips64el (2.2.0-2 to 2.2.0-2)
  • Migration status for cidr/mips64el (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cidr/mips64el golang-1.23
• cidr/ppc64el (2.2.0-2 to 2.2.0-2)
  • Migration status for cidr/ppc64el (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cidr/ppc64el golang-1.23
• cidr/riscv64 (2.2.0-2 to 2.2.0-2)
  • Migration status for cidr/riscv64 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cidr/riscv64 golang-1.23
• cidr/s390x (2.2.0-2 to 2.2.0-2)
  • Migration status for cidr/s390x (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cidr/s390x golang-1.23
• claws-mail/amd64 (4.3.0-2 to 4.3.0-2)
  • Migration status for claws-mail/amd64 (4.3.0-2 to 4.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: claws-mail/amd64 gumbo-parser (not considered)
    • Invalidated by dependency
• claws-mail/arm64 (4.3.0-2 to 4.3.0-2)
  • Migration status for claws-mail/arm64 (4.3.0-2 to 4.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: claws-mail/arm64 gumbo-parser (not considered)
    • Invalidated by dependency
• claws-mail/armel (4.3.0-2 to 4.3.0-2)
  • Migration status for claws-mail/armel (4.3.0-2 to 4.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: claws-mail/armel gumbo-parser (not considered)
    • Invalidated by dependency
• claws-mail/armhf (4.3.0-2 to 4.3.0-2)
  • Migration status for claws-mail/armhf (4.3.0-2 to 4.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: claws-mail/armhf gumbo-parser (not considered)
    • Invalidated by dependency
• claws-mail/i386 (4.3.0-2 to 4.3.0-2)
  • Migration status for claws-mail/i386 (4.3.0-2 to 4.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: claws-mail/i386 gumbo-parser (not considered)
    • Invalidated by dependency
• claws-mail/mips64el (4.3.0-2 to 4.3.0-2)
  • Migration status for claws-mail/mips64el (4.3.0-2 to 4.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: claws-mail/mips64el gumbo-parser (not considered)
    • Invalidated by dependency
• claws-mail/ppc64el (4.3.0-2 to 4.3.0-2)
  • Migration status for claws-mail/ppc64el (4.3.0-2 to 4.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: claws-mail/ppc64el gumbo-parser (not considered)
    • Invalidated by dependency
• claws-mail/riscv64 (4.3.0-2 to 4.3.0-2)
  • Migration status for claws-mail/riscv64 (4.3.0-2 to 4.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: claws-mail/riscv64 gumbo-parser (not considered)
    • Invalidated by dependency
• claws-mail/s390x (4.3.0-2 to 4.3.0-2)
  • Migration status for claws-mail/s390x (4.3.0-2 to 4.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: claws-mail/s390x gumbo-parser (not considered)
    • Invalidated by dependency
• cliphist/amd64 (0.5.0-1 to 0.5.0-1)
  • Migration status for cliphist/amd64 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cliphist/amd64 golang-1.23
• cliphist/arm64 (0.5.0-1 to 0.5.0-1)
  • Migration status for cliphist/arm64 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cliphist/arm64 golang-1.23
• cliphist/armel (0.5.0-1 to 0.5.0-1)
  • Migration status for cliphist/armel (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cliphist/armel golang-1.23
• cliphist/armhf (0.5.0-1 to 0.5.0-1)
  • Migration status for cliphist/armhf (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cliphist/armhf golang-1.23
• cliphist/i386 (0.5.0-1 to 0.5.0-1)
  • Migration status for cliphist/i386 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cliphist/i386 golang-1.23
• cliphist/mips64el (0.5.0-1 to 0.5.0-1)
  • Migration status for cliphist/mips64el (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cliphist/mips64el golang-1.23
• cliphist/ppc64el (0.5.0-1 to 0.5.0-1)
  • Migration status for cliphist/ppc64el (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cliphist/ppc64el golang-1.23
• cliphist/riscv64 (0.5.0-1 to 0.5.0-1)
  • Migration status for cliphist/riscv64 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cliphist/riscv64 golang-1.23
• cliphist/s390x (0.5.0-1 to 0.5.0-1)
  • Migration status for cliphist/s390x (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cliphist/s390x golang-1.23
• clipman/amd64 (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2)
  • Migration status for clipman/amd64 (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: clipman/amd64 golang-1.23
• clipman/arm64 (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2)
  • Migration status for clipman/arm64 (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: clipman/arm64 golang-1.23
• clipman/armel (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2)
  • Migration status for clipman/armel (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: clipman/armel golang-1.23
• clipman/armhf (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2)
  • Migration status for clipman/armhf (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: clipman/armhf golang-1.23
• clipman/i386 (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2)
  • Migration status for clipman/i386 (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: clipman/i386 golang-1.23
• clipman/mips64el (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2)
  • Migration status for clipman/mips64el (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: clipman/mips64el golang-1.23
• clipman/ppc64el (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2)
  • Migration status for clipman/ppc64el (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: clipman/ppc64el golang-1.23
• clipman/riscv64 (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2)
  • Migration status for clipman/riscv64 (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: clipman/riscv64 golang-1.23
• clipman/s390x (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2)
  • Migration status for clipman/s390x (1.2.0+git20200218.39fd4fe-2 to 1.2.0+git20200218.39fd4fe-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: clipman/s390x golang-1.23
• cloudsql-proxy/amd64 (1.33.14-1 to 1.33.14-1)
  • Migration status for cloudsql-proxy/amd64 (1.33.14-1 to 1.33.14-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cloudsql-proxy/amd64 golang-1.23
• cloudsql-proxy/arm64 (1.33.14-1 to 1.33.14-1)
  • Migration status for cloudsql-proxy/arm64 (1.33.14-1 to 1.33.14-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cloudsql-proxy/arm64 golang-1.23
• cloudsql-proxy/armel (1.33.14-1 to 1.33.14-1)
  • Migration status for cloudsql-proxy/armel (1.33.14-1 to 1.33.14-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cloudsql-proxy/armel golang-1.23
• cloudsql-proxy/armhf (1.33.14-1 to 1.33.14-1)
  • Migration status for cloudsql-proxy/armhf (1.33.14-1 to 1.33.14-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cloudsql-proxy/armhf golang-1.23
• cloudsql-proxy/i386 (1.33.14-1 to 1.33.14-1)
  • Migration status for cloudsql-proxy/i386 (1.33.14-1 to 1.33.14-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cloudsql-proxy/i386 golang-1.23
• cloudsql-proxy/mips64el (1.33.14-1 to 1.33.14-1)
  • Migration status for cloudsql-proxy/mips64el (1.33.14-1 to 1.33.14-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: cloudsql-proxy/mips64el golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: cloudsql-proxy/mips64el golang-1.23
• cloudsql-proxy/ppc64el (1.33.14-1 to 1.33.14-1)
  • Migration status for cloudsql-proxy/ppc64el (1.33.14-1 to 1.33.14-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: cloudsql-proxy/ppc64el golang-1.23
• cloudsql-proxy/riscv64 (1.33.14-1 to 1.33.14-1)
  • Migration status for cloudsql-proxy/riscv64 (1.33.14-1 to 1.33.14-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: cloudsql-proxy/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: cloudsql-proxy/riscv64 golang-1.23
• cloudsql-proxy/s390x (1.33.14-1 to 1.33.14-1)
  • Migration status for cloudsql-proxy/s390x (1.33.14-1 to 1.33.14-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: cloudsql-proxy/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: cloudsql-proxy/s390x golang-1.23
• cobra-cli/amd64 (1.3.0-3 to 1.3.0-3)
  • Migration status for cobra-cli/amd64 (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: cobra-cli/amd64 golang-1.23
• cobra-cli/arm64 (1.3.0-3 to 1.3.0-3)
  • Migration status for cobra-cli/arm64 (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: cobra-cli/arm64 golang-1.23
• cobra-cli/armel (1.3.0-3 to 1.3.0-3)
  • Migration status for cobra-cli/armel (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: cobra-cli/armel golang-1.23
• cobra-cli/armhf (1.3.0-3 to 1.3.0-3)
  • Migration status for cobra-cli/armhf (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: cobra-cli/armhf golang-1.23
• cobra-cli/i386 (1.3.0-3 to 1.3.0-3)
  • Migration status for cobra-cli/i386 (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: cobra-cli/i386 golang-1.23
• cobra-cli/mips64el (1.3.0-3 to 1.3.0-3)
  • Migration status for cobra-cli/mips64el (1.3.0-3 to 1.3.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: cobra-cli/mips64el golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: cobra-cli/mips64el golang-1.23
• cobra-cli/ppc64el (1.3.0-3 to 1.3.0-3)
  • Migration status for cobra-cli/ppc64el (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: cobra-cli/ppc64el golang-1.23
• cobra-cli/riscv64 (1.3.0-3 to 1.3.0-3)
  • Migration status for cobra-cli/riscv64 (1.3.0-3 to 1.3.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: cobra-cli/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: cobra-cli/riscv64 golang-1.23
• cobra-cli/s390x (1.3.0-3 to 1.3.0-3)
  • Migration status for cobra-cli/s390x (1.3.0-3 to 1.3.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: cobra-cli/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: cobra-cli/s390x golang-1.23
• codesearch/amd64 (1.2.0-1 to 1.2.0-1)
  • Migration status for codesearch/amd64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: codesearch/amd64 golang-1.23
• codesearch/arm64 (1.2.0-1 to 1.2.0-1)
  • Migration status for codesearch/arm64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: codesearch/arm64 golang-1.23
• codesearch/armel (1.2.0-1 to 1.2.0-1)
  • Migration status for codesearch/armel (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: codesearch/armel golang-1.23
• codesearch/armhf (1.2.0-1 to 1.2.0-1)
  • Migration status for codesearch/armhf (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: codesearch/armhf golang-1.23
• codesearch/i386 (1.2.0-1 to 1.2.0-1)
  • Migration status for codesearch/i386 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: codesearch/i386 golang-1.23
• codesearch/mips64el (1.2.0-1 to 1.2.0-1)
  • Migration status for codesearch/mips64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: codesearch/mips64el golang-1.23
• codesearch/ppc64el (1.2.0-1 to 1.2.0-1)
  • Migration status for codesearch/ppc64el (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: codesearch/ppc64el golang-1.23
• codesearch/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for codesearch/riscv64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: codesearch/riscv64 golang-1.23
• codesearch/s390x (1.2.0-1 to 1.2.0-1)
  • Migration status for codesearch/s390x (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: codesearch/s390x golang-1.23
• containerd/amd64 (1.7.24~ds1-4 to 1.7.24~ds1-4)
  • Migration status for containerd/amd64 (1.7.24~ds1-4 to 1.7.24~ds1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/amd64 golang-1.23
• containerd/arm64 (1.7.24~ds1-4 to 1.7.24~ds1-4)
  • Migration status for containerd/arm64 (1.7.24~ds1-4 to 1.7.24~ds1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/arm64 golang-1.23
• containerd/armel (1.7.24~ds1-4 to 1.7.24~ds1-4)
  • Migration status for containerd/armel (1.7.24~ds1-4 to 1.7.24~ds1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/armel golang-1.23
• containerd/armhf (1.7.24~ds1-4 to 1.7.24~ds1-4)
  • Migration status for containerd/armhf (1.7.24~ds1-4 to 1.7.24~ds1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/armhf golang-1.23
• containerd/i386 (1.7.24~ds1-4 to 1.7.24~ds1-4)
  • Migration status for containerd/i386 (1.7.24~ds1-4 to 1.7.24~ds1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/i386 golang-1.23
• containerd/ppc64el (1.7.24~ds1-4 to 1.7.24~ds1-4)
  • Migration status for containerd/ppc64el (1.7.24~ds1-4 to 1.7.24~ds1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/ppc64el golang-1.23
• containerd/riscv64 (1.7.24~ds1-4 to 1.7.24~ds1-4)
  • Migration status for containerd/riscv64 (1.7.24~ds1-4 to 1.7.24~ds1-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: containerd/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: containerd/riscv64 golang-1.23
• containerd/s390x (1.7.24~ds1-4 to 1.7.24~ds1-4)
  • Migration status for containerd/s390x (1.7.24~ds1-4 to 1.7.24~ds1-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: containerd/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: containerd/s390x golang-1.23
• containerd_pu (1.7.24~ds1-4 to 1.6.20~ds1-1+deb12u1)
  • Migration status for containerd_pu (1.7.24~ds1-4 to 1.6.20~ds1-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: containerd is newer in the target suite (1.7.24~ds1-4 1.6.20~ds1-1+deb12u1)
• cosign/amd64 (2.4.1-2 to 2.4.1-2)
  • Migration status for cosign/amd64 (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cosign/amd64 golang-1.23
• cosign/arm64 (2.4.1-2 to 2.4.1-2)
  • Migration status for cosign/arm64 (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cosign/arm64 golang-1.23
• cosign/armel (2.4.1-2 to 2.4.1-2)
  • Migration status for cosign/armel (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cosign/armel golang-1.23
• cosign/armhf (2.4.1-2 to 2.4.1-2)
  • Migration status for cosign/armhf (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cosign/armhf golang-1.23
• cosign/i386 (2.4.1-2 to 2.4.1-2)
  • Migration status for cosign/i386 (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cosign/i386 golang-1.23
• cosign/ppc64el (2.4.1-2 to 2.4.1-2)
  • Migration status for cosign/ppc64el (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: cosign/ppc64el golang-1.23
• cosign/riscv64 (2.4.1-2 to 2.4.1-2)
  • Migration status for cosign/riscv64 (2.4.1-2 to 2.4.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: cosign/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: cosign/riscv64 golang-1.23
• cosign/s390x (2.4.1-2 to 2.4.1-2)
  • Migration status for cosign/s390x (2.4.1-2 to 2.4.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: cosign/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: cosign/s390x golang-1.23
• curl_pu (8.12.0+git20250209.89ed161+ds-1 to 7.88.1-10+deb12u9)
  • Migration status for curl_pu (8.12.0+git20250209.89ed161+ds-1 to 7.88.1-10+deb12u9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: curl is newer in the target suite (8.12.0+git20250209.89ed161+ds-1 7.88.1-10+deb12u9)
• cynthiune.app/amd64 (1.0.0-3 to 1.0.0-3)
  • Migration status for cynthiune.app/amd64 (1.0.0-3 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: cynthiune.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• cynthiune.app/arm64 (1.0.0-3 to 1.0.0-3)
  • Migration status for cynthiune.app/arm64 (1.0.0-3 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: cynthiune.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• cynthiune.app/armel (1.0.0-3 to 1.0.0-3)
  • Migration status for cynthiune.app/armel (1.0.0-3 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: cynthiune.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• cynthiune.app/armhf (1.0.0-3 to 1.0.0-3)
  • Migration status for cynthiune.app/armhf (1.0.0-3 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: cynthiune.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• cynthiune.app/i386 (1.0.0-3 to 1.0.0-3)
  • Migration status for cynthiune.app/i386 (1.0.0-3 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: cynthiune.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• cynthiune.app/mips64el (1.0.0-3 to 1.0.0-3)
  • Migration status for cynthiune.app/mips64el (1.0.0-3 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: cynthiune.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• cynthiune.app/ppc64el (1.0.0-3 to 1.0.0-3)
  • Migration status for cynthiune.app/ppc64el (1.0.0-3 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: cynthiune.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• cynthiune.app/riscv64 (1.0.0-3 to 1.0.0-3)
  • Migration status for cynthiune.app/riscv64 (1.0.0-3 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: cynthiune.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• cynthiune.app/s390x (1.0.0-3 to 1.0.0-3)
  • Migration status for cynthiune.app/s390x (1.0.0-3 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: cynthiune.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• dar/s390x (2.7.15-2 to 2.7.15-2)
  • Migration status for dar/s390x (2.7.15-2 to 2.7.15-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: dar/s390x openssl (not considered)
    • Invalidated by built-using
• debos/amd64 (1.1.4-1.1 to 1.1.4-1.1)
  • Migration status for debos/amd64 (1.1.4-1.1 to 1.1.4-1.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: debos/amd64 golang-1.23
• debos/arm64 (1.1.4-1.1 to 1.1.4-1.1)
  • Migration status for debos/arm64 (1.1.4-1.1 to 1.1.4-1.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: debos/arm64 golang-1.23
• debsig-verify/mips64el (0.31 to 0.31)
  • Migration status for debsig-verify/mips64el (0.31 to 0.31): Will attempt migration (Any information below is purely informational)
• debsig-verify/riscv64 (0.31 to 0.31)
  • Migration status for debsig-verify/riscv64 (0.31 to 0.31): Will attempt migration (Any information below is purely informational)
• debsig-verify/s390x (0.31 to 0.31)
  • Migration status for debsig-verify/s390x (0.31 to 0.31): Will attempt migration (Any information below is purely informational)
• deck/amd64 (1.4.0-1 to 1.4.0-1)
  • Migration status for deck/amd64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: deck/amd64 golang-1.23
• deck/arm64 (1.4.0-1 to 1.4.0-1)
  • Migration status for deck/arm64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: deck/arm64 golang-1.23
• deck/armel (1.4.0-1 to 1.4.0-1)
  • Migration status for deck/armel (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: deck/armel golang-1.23
• deck/armhf (1.4.0-1 to 1.4.0-1)
  • Migration status for deck/armhf (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: deck/armhf golang-1.23
• deck/i386 (1.4.0-1 to 1.4.0-1)
  • Migration status for deck/i386 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: deck/i386 golang-1.23
• deck/ppc64el (1.4.0-1 to 1.4.0-1)
  • Migration status for deck/ppc64el (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: deck/ppc64el golang-1.23
• deck/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for deck/riscv64 (1.4.0-1 to 1.4.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: deck/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: deck/riscv64 golang-1.23
• deck/s390x (1.4.0-1 to 1.4.0-1)
  • Migration status for deck/s390x (1.4.0-1 to 1.4.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: deck/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: deck/s390x golang-1.23
• deets/mips64el (0.3.2-1 to 0.3.2-1)
  • Migration status for deets/mips64el (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• deets/riscv64 (0.3.2-1 to 0.3.2-1)
  • Migration status for deets/riscv64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• deets/s390x (0.3.2-1 to 0.3.2-1)
  • Migration status for deets/s390x (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• delve/amd64 (1.24.0-2 to 1.24.0-2)
  • Migration status for delve/amd64 (1.24.0-2 to 1.24.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: delve/amd64 golang-1.23
    • Built-Using: delve/amd64 golang-github-mattn-go-runewidth
• delve/arm64 (1.24.0-2 to 1.24.0-2)
  • Migration status for delve/arm64 (1.24.0-2 to 1.24.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: delve/arm64 golang-1.23
    • Built-Using: delve/arm64 golang-github-mattn-go-runewidth
• delve/i386 (1.24.0-2 to 1.24.0-2)
  • Migration status for delve/i386 (1.24.0-2 to 1.24.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: delve/i386 golang-1.23
    • Built-Using: delve/i386 golang-github-mattn-go-runewidth
• direnv/amd64 (2.32.1-2 to 2.32.1-2)
  • Migration status for direnv/amd64 (2.32.1-2 to 2.32.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: direnv/amd64 golang-1.23
• direnv/arm64 (2.32.1-2 to 2.32.1-2)
  • Migration status for direnv/arm64 (2.32.1-2 to 2.32.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: direnv/arm64 golang-1.23
• direnv/armel (2.32.1-2 to 2.32.1-2)
  • Migration status for direnv/armel (2.32.1-2 to 2.32.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: direnv/armel golang-1.23
• direnv/armhf (2.32.1-2 to 2.32.1-2)
  • Migration status for direnv/armhf (2.32.1-2 to 2.32.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: direnv/armhf golang-1.23
• direnv/i386 (2.32.1-2 to 2.32.1-2)
  • Migration status for direnv/i386 (2.32.1-2 to 2.32.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: direnv/i386 golang-1.23
• direnv/mips64el (2.32.1-2 to 2.32.1-2)
  • Migration status for direnv/mips64el (2.32.1-2 to 2.32.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: direnv/mips64el golang-1.23
• direnv/ppc64el (2.32.1-2 to 2.32.1-2)
  • Migration status for direnv/ppc64el (2.32.1-2 to 2.32.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: direnv/ppc64el golang-1.23
• direnv/riscv64 (2.32.1-2 to 2.32.1-2)
  • Migration status for direnv/riscv64 (2.32.1-2 to 2.32.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: direnv/riscv64 golang-1.23
• direnv/s390x (2.32.1-2 to 2.32.1-2)
  • Migration status for direnv/s390x (2.32.1-2 to 2.32.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: direnv/s390x golang-1.23
• distrobuilder/amd64 (3.1-1 to 3.1-1)
  • Migration status for distrobuilder/amd64 (3.1-1 to 3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: distrobuilder/amd64 runc (not considered)
    • Invalidated by built-using
    • Built-Using: distrobuilder/amd64 golang-1.23
• distrobuilder/arm64 (3.1-1 to 3.1-1)
  • Migration status for distrobuilder/arm64 (3.1-1 to 3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: distrobuilder/arm64 runc (not considered)
    • Invalidated by built-using
    • Built-Using: distrobuilder/arm64 golang-1.23
• distrobuilder/armel (3.1-1 to 3.1-1)
  • Migration status for distrobuilder/armel (3.1-1 to 3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: distrobuilder/armel runc (not considered)
    • Invalidated by built-using
    • Built-Using: distrobuilder/armel golang-1.23
• distrobuilder/armhf (3.1-1 to 3.1-1)
  • Migration status for distrobuilder/armhf (3.1-1 to 3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: distrobuilder/armhf runc (not considered)
    • Invalidated by built-using
    • Built-Using: distrobuilder/armhf golang-1.23
• distrobuilder/i386 (3.1-1 to 3.1-1)
  • Migration status for distrobuilder/i386 (3.1-1 to 3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: distrobuilder/i386 runc (not considered)
    • Invalidated by built-using
    • Built-Using: distrobuilder/i386 golang-1.23
• distrobuilder/ppc64el (3.1-1 to 3.1-1)
  • Migration status for distrobuilder/ppc64el (3.1-1 to 3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: distrobuilder/ppc64el runc (not considered)
    • Invalidated by built-using
    • Built-Using: distrobuilder/ppc64el golang-1.23
• distrobuilder/riscv64 (3.1-1 to 3.1-1)
  • Migration status for distrobuilder/riscv64 (3.1-1 to 3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: distrobuilder/riscv64 runc (not considered)
    • Invalidated by built-using
    • Built-Using: distrobuilder/riscv64 golang-1.23
    • Built-Using: distrobuilder/riscv64 golang-golang-x-text
• distrobuilder/s390x (3.1-1 to 3.1-1)
  • Migration status for distrobuilder/s390x (3.1-1 to 3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: distrobuilder/s390x runc (not considered)
    • Invalidated by built-using
    • Built-Using: distrobuilder/s390x golang-1.23
    • Built-Using: distrobuilder/s390x golang-golang-x-text
• dmarc-cat/amd64 (0.15.0-1 to 0.15.0-1)
  • Migration status for dmarc-cat/amd64 (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dmarc-cat/amd64 golang-1.23
• dmarc-cat/arm64 (0.15.0-1 to 0.15.0-1)
  • Migration status for dmarc-cat/arm64 (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dmarc-cat/arm64 golang-1.23
• dmarc-cat/armel (0.15.0-1 to 0.15.0-1)
  • Migration status for dmarc-cat/armel (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dmarc-cat/armel golang-1.23
• dmarc-cat/armhf (0.15.0-1 to 0.15.0-1)
  • Migration status for dmarc-cat/armhf (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dmarc-cat/armhf golang-1.23
• dmarc-cat/i386 (0.15.0-1 to 0.15.0-1)
  • Migration status for dmarc-cat/i386 (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dmarc-cat/i386 golang-1.23
• dmarc-cat/mips64el (0.15.0-1 to 0.15.0-1)
  • Migration status for dmarc-cat/mips64el (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dmarc-cat/mips64el golang-1.23
• dmarc-cat/ppc64el (0.15.0-1 to 0.15.0-1)
  • Migration status for dmarc-cat/ppc64el (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dmarc-cat/ppc64el golang-1.23
• dmarc-cat/riscv64 (0.15.0-1 to 0.15.0-1)
  • Migration status for dmarc-cat/riscv64 (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dmarc-cat/riscv64 golang-1.23
• dmarc-cat/s390x (0.15.0-1 to 0.15.0-1)
  • Migration status for dmarc-cat/s390x (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dmarc-cat/s390x golang-1.23
• dns-root-data_pu (2024071801 to 2024071801~deb12u1)
  • Migration status for dns-root-data_pu (2024071801 to 2024071801~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: dns-root-data is newer in the target suite (2024071801 2024071801~deb12u1)
• dnscrypt-proxy/amd64 (2.1.5+ds1-2 to 2.1.5+ds1-2)
  • Migration status for dnscrypt-proxy/amd64 (2.1.5+ds1-2 to 2.1.5+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/amd64 golang-1.23
• dnscrypt-proxy/arm64 (2.1.5+ds1-2 to 2.1.5+ds1-2)
  • Migration status for dnscrypt-proxy/arm64 (2.1.5+ds1-2 to 2.1.5+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/arm64 golang-1.23
• dnscrypt-proxy/armel (2.1.5+ds1-2 to 2.1.5+ds1-2)
  • Migration status for dnscrypt-proxy/armel (2.1.5+ds1-2 to 2.1.5+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/armel golang-1.23
• dnscrypt-proxy/armhf (2.1.5+ds1-2 to 2.1.5+ds1-2)
  • Migration status for dnscrypt-proxy/armhf (2.1.5+ds1-2 to 2.1.5+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/armhf golang-1.23
• dnscrypt-proxy/i386 (2.1.5+ds1-2 to 2.1.5+ds1-2)
  • Migration status for dnscrypt-proxy/i386 (2.1.5+ds1-2 to 2.1.5+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/i386 golang-1.23
• dnscrypt-proxy/mips64el (2.1.5+ds1-2 to 2.1.5+ds1-2)
  • Migration status for dnscrypt-proxy/mips64el (2.1.5+ds1-2 to 2.1.5+ds1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: dnscrypt-proxy/mips64el golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: dnscrypt-proxy/mips64el golang-1.23
• dnscrypt-proxy/ppc64el (2.1.5+ds1-2 to 2.1.5+ds1-2)
  • Migration status for dnscrypt-proxy/ppc64el (2.1.5+ds1-2 to 2.1.5+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/ppc64el golang-1.23
• dnscrypt-proxy/riscv64 (2.1.5+ds1-2 to 2.1.5+ds1-2)
  • Migration status for dnscrypt-proxy/riscv64 (2.1.5+ds1-2 to 2.1.5+ds1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: dnscrypt-proxy/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: dnscrypt-proxy/riscv64 golang-1.23
• dnscrypt-proxy/s390x (2.1.5+ds1-2 to 2.1.5+ds1-2)
  • Migration status for dnscrypt-proxy/s390x (2.1.5+ds1-2 to 2.1.5+ds1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: dnscrypt-proxy/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: dnscrypt-proxy/s390x golang-1.23
• dnss/amd64 (0.1.0-1 to 0.1.0-1)
  • Migration status for dnss/amd64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnss/amd64 golang-1.23
• dnss/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for dnss/arm64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnss/arm64 golang-1.23
• dnss/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for dnss/armel (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnss/armel golang-1.23
• dnss/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for dnss/armhf (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnss/armhf golang-1.23
• dnss/i386 (0.1.0-1 to 0.1.0-1)
  • Migration status for dnss/i386 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnss/i386 golang-1.23
• dnss/mips64el (0.1.0-1 to 0.1.0-1)
  • Migration status for dnss/mips64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnss/mips64el golang-1.23
• dnss/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for dnss/ppc64el (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnss/ppc64el golang-1.23
• dnss/riscv64 (0.1.0-1 to 0.1.0-1)
  • Migration status for dnss/riscv64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnss/riscv64 golang-1.23
• dnss/s390x (0.1.0-1 to 0.1.0-1)
  • Migration status for dnss/s390x (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnss/s390x golang-1.23
• docker-registry/amd64 (2.8.3+ds1-2 to 2.8.3+ds1-2)
  • Migration status for docker-registry/amd64 (2.8.3+ds1-2 to 2.8.3+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker-registry/amd64 golang-1.23
• docker-registry/arm64 (2.8.3+ds1-2 to 2.8.3+ds1-2)
  • Migration status for docker-registry/arm64 (2.8.3+ds1-2 to 2.8.3+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker-registry/arm64 golang-1.23
• docker-registry/armel (2.8.3+ds1-2 to 2.8.3+ds1-2)
  • Migration status for docker-registry/armel (2.8.3+ds1-2 to 2.8.3+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker-registry/armel golang-1.23
• docker-registry/armhf (2.8.3+ds1-2 to 2.8.3+ds1-2)
  • Migration status for docker-registry/armhf (2.8.3+ds1-2 to 2.8.3+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker-registry/armhf golang-1.23
• docker-registry/i386 (2.8.3+ds1-2 to 2.8.3+ds1-2)
  • Migration status for docker-registry/i386 (2.8.3+ds1-2 to 2.8.3+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker-registry/i386 golang-1.23
• docker-registry/ppc64el (2.8.3+ds1-2 to 2.8.3+ds1-2)
  • Migration status for docker-registry/ppc64el (2.8.3+ds1-2 to 2.8.3+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker-registry/ppc64el golang-1.23
• docker-registry/s390x (2.8.3+ds1-2 to 2.8.3+ds1-2)
  • Migration status for docker-registry/s390x (2.8.3+ds1-2 to 2.8.3+ds1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: docker-registry/s390x golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: docker-registry/s390x golang-1.23
• docker.io/amd64 (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4)
  • Migration status for docker.io/amd64 (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: docker.io/amd64 runc (not considered)
    • Invalidated by built-using
    • Built-Using: docker.io/amd64 golang-1.23
    • Built-Using: docker.io/amd64 golang-github-mattn-go-runewidth
• docker.io/arm64 (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4)
  • Migration status for docker.io/arm64 (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: docker.io/arm64 runc (not considered)
    • Invalidated by built-using
    • Built-Using: docker.io/arm64 golang-1.23
    • Built-Using: docker.io/arm64 golang-github-mattn-go-runewidth
• docker.io/armel (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4)
  • Migration status for docker.io/armel (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: docker.io/armel runc (not considered)
    • Invalidated by built-using
    • Built-Using: docker.io/armel golang-1.23
    • Built-Using: docker.io/armel golang-github-mattn-go-runewidth
• docker.io/armhf (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4)
  • Migration status for docker.io/armhf (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: docker.io/armhf runc (not considered)
    • Invalidated by built-using
    • Built-Using: docker.io/armhf golang-1.23
    • Built-Using: docker.io/armhf golang-github-mattn-go-runewidth
• docker.io/i386 (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4)
  • Migration status for docker.io/i386 (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: docker.io/i386 runc (not considered)
    • Invalidated by built-using
    • Built-Using: docker.io/i386 golang-1.23
    • Built-Using: docker.io/i386 golang-github-mattn-go-runewidth
• docker.io/ppc64el (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4)
  • Migration status for docker.io/ppc64el (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: docker.io/ppc64el runc (not considered)
    • Invalidated by built-using
    • Built-Using: docker.io/ppc64el golang-1.23
    • Built-Using: docker.io/ppc64el golang-github-mattn-go-runewidth
• docker.io/s390x (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4)
  • Migration status for docker.io/s390x (26.1.5+dfsg1-4 to 26.1.5+dfsg1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: docker.io/s390x runc (not considered)
    • Invalidated by built-using
    • Built-Using: docker.io/s390x golang-1.23
    • Built-Using: docker.io/s390x golang-github-mattn-go-runewidth
    • Built-Using: docker.io/s390x golang-golang-x-text
• duf/amd64 (0.8.1-2 to 0.8.1-2)
  • Migration status for duf/amd64 (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: duf/amd64 golang-1.23
    • Built-Using: duf/amd64 golang-github-mattn-go-runewidth
• duf/arm64 (0.8.1-2 to 0.8.1-2)
  • Migration status for duf/arm64 (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: duf/arm64 golang-1.23
    • Built-Using: duf/arm64 golang-github-mattn-go-runewidth
• duf/armel (0.8.1-2 to 0.8.1-2)
  • Migration status for duf/armel (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: duf/armel golang-1.23
    • Built-Using: duf/armel golang-github-mattn-go-runewidth
• duf/armhf (0.8.1-2 to 0.8.1-2)
  • Migration status for duf/armhf (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: duf/armhf golang-1.23
    • Built-Using: duf/armhf golang-github-mattn-go-runewidth
• duf/i386 (0.8.1-2 to 0.8.1-2)
  • Migration status for duf/i386 (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: duf/i386 golang-1.23
    • Built-Using: duf/i386 golang-github-mattn-go-runewidth
• duf/mips64el (0.8.1-2 to 0.8.1-2)
  • Migration status for duf/mips64el (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: duf/mips64el golang-1.23
    • Built-Using: duf/mips64el golang-github-mattn-go-runewidth
• duf/ppc64el (0.8.1-2 to 0.8.1-2)
  • Migration status for duf/ppc64el (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: duf/ppc64el golang-1.23
    • Built-Using: duf/ppc64el golang-github-mattn-go-runewidth
• duf/riscv64 (0.8.1-2 to 0.8.1-2)
  • Migration status for duf/riscv64 (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: duf/riscv64 golang-1.23
    • Built-Using: duf/riscv64 golang-github-mattn-go-runewidth
• duf/s390x (0.8.1-2 to 0.8.1-2)
  • Migration status for duf/s390x (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: duf/s390x golang-1.23
    • Built-Using: duf/s390x golang-github-mattn-go-runewidth
• edenmath.app/amd64 (1.1.1a-9 to 1.1.1a-9)
  • Migration status for edenmath.app/amd64 (1.1.1a-9 to 1.1.1a-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: edenmath.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• edenmath.app/arm64 (1.1.1a-9 to 1.1.1a-9)
  • Migration status for edenmath.app/arm64 (1.1.1a-9 to 1.1.1a-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: edenmath.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• edenmath.app/armel (1.1.1a-9 to 1.1.1a-9)
  • Migration status for edenmath.app/armel (1.1.1a-9 to 1.1.1a-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: edenmath.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• edenmath.app/armhf (1.1.1a-9 to 1.1.1a-9)
  • Migration status for edenmath.app/armhf (1.1.1a-9 to 1.1.1a-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: edenmath.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• edenmath.app/i386 (1.1.1a-9 to 1.1.1a-9)
  • Migration status for edenmath.app/i386 (1.1.1a-9 to 1.1.1a-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: edenmath.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• edenmath.app/mips64el (1.1.1a-9 to 1.1.1a-9)
  • Migration status for edenmath.app/mips64el (1.1.1a-9 to 1.1.1a-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: edenmath.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• edenmath.app/ppc64el (1.1.1a-9 to 1.1.1a-9)
  • Migration status for edenmath.app/ppc64el (1.1.1a-9 to 1.1.1a-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: edenmath.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• edenmath.app/riscv64 (1.1.1a-9 to 1.1.1a-9)
  • Migration status for edenmath.app/riscv64 (1.1.1a-9 to 1.1.1a-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: edenmath.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• edenmath.app/s390x (1.1.1a-9 to 1.1.1a-9)
  • Migration status for edenmath.app/s390x (1.1.1a-9 to 1.1.1a-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: edenmath.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• elpa_pu (2022.11.001-3 to 2022.11.001-2+deb12u1)
  • Migration status for elpa_pu (2022.11.001-3 to 2022.11.001-2+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: elpa is newer in the target suite (2022.11.001-3 2022.11.001-2+deb12u1)
• eos-sdk/armel (0~git20230107+ds-5.1 to 0~git20230107+ds-5.1)
  • Migration status for eos-sdk/armel (0~git20230107+ds-5.1 to 0~git20230107+ds-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libendless-bin/armel has unsatisfiable dependency
• etoile/amd64 (0+20080616+dfsg-3 to 0+20080616+dfsg-3)
  • Migration status for etoile/amd64 (0+20080616+dfsg-3 to 0+20080616+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: etoile/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• etoile/arm64 (0+20080616+dfsg-3 to 0+20080616+dfsg-3)
  • Migration status for etoile/arm64 (0+20080616+dfsg-3 to 0+20080616+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: etoile/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• etoile/armel (0+20080616+dfsg-3 to 0+20080616+dfsg-3)
  • Migration status for etoile/armel (0+20080616+dfsg-3 to 0+20080616+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: etoile/armel gnustep-make (not considered)
    • Invalidated by dependency
• etoile/armhf (0+20080616+dfsg-3 to 0+20080616+dfsg-3)
  • Migration status for etoile/armhf (0+20080616+dfsg-3 to 0+20080616+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: etoile/armhf gnustep-make (not considered)
    • Invalidated by dependency
• etoile/i386 (0+20080616+dfsg-3 to 0+20080616+dfsg-3)
  • Migration status for etoile/i386 (0+20080616+dfsg-3 to 0+20080616+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: etoile/i386 gnustep-make (not considered)
    • Invalidated by dependency
• etoile/mips64el (0+20080616+dfsg-3 to 0+20080616+dfsg-3)
  • Migration status for etoile/mips64el (0+20080616+dfsg-3 to 0+20080616+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: etoile/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• etoile/ppc64el (0+20080616+dfsg-3 to 0+20080616+dfsg-3)
  • Migration status for etoile/ppc64el (0+20080616+dfsg-3 to 0+20080616+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: etoile/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• etoile/riscv64 (0+20080616+dfsg-3 to 0+20080616+dfsg-3)
  • Migration status for etoile/riscv64 (0+20080616+dfsg-3 to 0+20080616+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: etoile/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• etoile/s390x (0+20080616+dfsg-3 to 0+20080616+dfsg-3)
  • Migration status for etoile/s390x (0+20080616+dfsg-3 to 0+20080616+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: etoile/s390x gnustep-make (not considered)
    • Invalidated by dependency
• firefox-esr_pu (128.7.0esr-1 to 128.7.0esr-1~deb12u1)
  • Migration status for firefox-esr_pu (128.7.0esr-1 to 128.7.0esr-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: firefox-esr is newer in the target suite (128.7.0esr-1 128.7.0esr-1~deb12u1)
• flightgear_pu (1:2020.3.19+dfsg-1 to 1:2020.3.16+dfsg-1+deb12u1)
  • Migration status for flightgear_pu (1:2020.3.19+dfsg-1 to 1:2020.3.16+dfsg-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: flightgear is newer in the target suite (1:2020.3.19+dfsg-1 1:2020.3.16+dfsg-1+deb12u1)
• fontmanager.app/amd64 (0.1-4 to 0.1-4)
  • Migration status for fontmanager.app/amd64 (0.1-4 to 0.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fontmanager.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• fontmanager.app/arm64 (0.1-4 to 0.1-4)
  • Migration status for fontmanager.app/arm64 (0.1-4 to 0.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fontmanager.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• fontmanager.app/armel (0.1-4 to 0.1-4)
  • Migration status for fontmanager.app/armel (0.1-4 to 0.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fontmanager.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• fontmanager.app/armhf (0.1-4 to 0.1-4)
  • Migration status for fontmanager.app/armhf (0.1-4 to 0.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fontmanager.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• fontmanager.app/i386 (0.1-4 to 0.1-4)
  • Migration status for fontmanager.app/i386 (0.1-4 to 0.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fontmanager.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• fontmanager.app/mips64el (0.1-4 to 0.1-4)
  • Migration status for fontmanager.app/mips64el (0.1-4 to 0.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fontmanager.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• fontmanager.app/ppc64el (0.1-4 to 0.1-4)
  • Migration status for fontmanager.app/ppc64el (0.1-4 to 0.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fontmanager.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• fontmanager.app/riscv64 (0.1-4 to 0.1-4)
  • Migration status for fontmanager.app/riscv64 (0.1-4 to 0.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fontmanager.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• fontmanager.app/s390x (0.1-4 to 0.1-4)
  • Migration status for fontmanager.app/s390x (0.1-4 to 0.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fontmanager.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• fortunate.app/amd64 (3.1-5 to 3.1-5)
  • Migration status for fortunate.app/amd64 (3.1-5 to 3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fortunate.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• fortunate.app/arm64 (3.1-5 to 3.1-5)
  • Migration status for fortunate.app/arm64 (3.1-5 to 3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fortunate.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• fortunate.app/armel (3.1-5 to 3.1-5)
  • Migration status for fortunate.app/armel (3.1-5 to 3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fortunate.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• fortunate.app/armhf (3.1-5 to 3.1-5)
  • Migration status for fortunate.app/armhf (3.1-5 to 3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fortunate.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• fortunate.app/i386 (3.1-5 to 3.1-5)
  • Migration status for fortunate.app/i386 (3.1-5 to 3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fortunate.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• fortunate.app/mips64el (3.1-5 to 3.1-5)
  • Migration status for fortunate.app/mips64el (3.1-5 to 3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fortunate.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• fortunate.app/ppc64el (3.1-5 to 3.1-5)
  • Migration status for fortunate.app/ppc64el (3.1-5 to 3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fortunate.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• fortunate.app/riscv64 (3.1-5 to 3.1-5)
  • Migration status for fortunate.app/riscv64 (3.1-5 to 3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fortunate.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• fortunate.app/s390x (3.1-5 to 3.1-5)
  • Migration status for fortunate.app/s390x (3.1-5 to 3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fortunate.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• ftp.app/amd64 (0.6-3 to 0.6-3)
  • Migration status for ftp.app/amd64 (0.6-3 to 0.6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ftp.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• ftp.app/arm64 (0.6-3 to 0.6-3)
  • Migration status for ftp.app/arm64 (0.6-3 to 0.6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ftp.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• ftp.app/armel (0.6-3 to 0.6-3)
  • Migration status for ftp.app/armel (0.6-3 to 0.6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ftp.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• ftp.app/armhf (0.6-3 to 0.6-3)
  • Migration status for ftp.app/armhf (0.6-3 to 0.6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ftp.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• ftp.app/i386 (0.6-3 to 0.6-3)
  • Migration status for ftp.app/i386 (0.6-3 to 0.6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ftp.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• ftp.app/mips64el (0.6-3 to 0.6-3)
  • Migration status for ftp.app/mips64el (0.6-3 to 0.6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ftp.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• ftp.app/ppc64el (0.6-3 to 0.6-3)
  • Migration status for ftp.app/ppc64el (0.6-3 to 0.6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ftp.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• ftp.app/riscv64 (0.6-3 to 0.6-3)
  • Migration status for ftp.app/riscv64 (0.6-3 to 0.6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ftp.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• ftp.app/s390x (0.6-3 to 0.6-3)
  • Migration status for ftp.app/s390x (0.6-3 to 0.6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ftp.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• gensim_pu (- to 4.2.0+dfsg-1+deb12u1)
  • Migration status for gensim_pu (- to 4.2.0+dfsg-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-gensim/amd64 has unsatisfiable dependency
    • python3-gensim/arm64 has unsatisfiable dependency
    • python3-gensim/armel has unsatisfiable dependency
    • python3-gensim/armhf has unsatisfiable dependency
    • python3-gensim/i386 has unsatisfiable dependency
    • python3-gensim/mips64el has unsatisfiable dependency
    • python3-gensim/ppc64el has unsatisfiable dependency
    • python3-gensim/s390x has unsatisfiable dependency
    • gensim unsatisfiable Build-Depends(-Arch) on amd64: python3-pyemd
    • gensim unsatisfiable Build-Depends(-Arch) on arm64: python3-pyemd
    • gensim unsatisfiable Build-Depends(-Arch) on armel: python3-pyemd
    • gensim unsatisfiable Build-Depends(-Arch) on armhf: python3-pyemd
    • gensim unsatisfiable Build-Depends(-Arch) on i386: python3-pyemd
    • gensim unsatisfiable Build-Depends(-Arch) on mips64el: python3-pyemd
    • gensim unsatisfiable Build-Depends(-Arch) on ppc64el: python3-pyemd
    • gensim unsatisfiable Build-Depends(-Arch) on s390x: python3-pyemd
    • NEEDS APPROVAL BY RM
• git-delta/amd64 (0.18.2-3 to 0.18.2-3)
  • Migration status for git-delta/amd64 (0.18.2-3 to 0.18.2-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-delta/amd64 rust-futures-timer
• git-delta/arm64 (0.18.2-3 to 0.18.2-3)
  • Migration status for git-delta/arm64 (0.18.2-3 to 0.18.2-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-delta/arm64 rust-futures-timer
• git-delta/armel (0.18.2-3 to 0.18.2-3)
  • Migration status for git-delta/armel (0.18.2-3 to 0.18.2-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-delta/armel rust-futures-timer
• git-delta/armhf (0.18.2-3 to 0.18.2-3)
  • Migration status for git-delta/armhf (0.18.2-3 to 0.18.2-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-delta/armhf rust-futures-timer
• git-delta/i386 (0.18.2-3 to 0.18.2-3)
  • Migration status for git-delta/i386 (0.18.2-3 to 0.18.2-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-delta/i386 rust-futures-timer
• git-delta/ppc64el (0.18.2-3 to 0.18.2-3)
  • Migration status for git-delta/ppc64el (0.18.2-3 to 0.18.2-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-delta/ppc64el rust-futures-timer
• git-delta/riscv64 (0.18.2-3 to 0.18.2-3)
  • Migration status for git-delta/riscv64 (0.18.2-3 to 0.18.2-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-delta/riscv64 rust-futures-timer
• git-lfs_pu (3.6.1-1 to 3.3.0-1+deb12u1)
  • Migration status for git-lfs_pu (3.6.1-1 to 3.3.0-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: git-lfs is newer in the target suite (3.6.1-1 3.3.0-1+deb12u1)
• git_pu (1:2.47.2-0.1 to 1:2.39.5-0+deb12u2)
  • Migration status for git_pu (1:2.47.2-0.1 to 1:2.39.5-0+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: git is newer in the target suite (1:2.47.2-0.1 1:2.39.5-0+deb12u2)
• glabels/amd64 (3.4.1-5 to 3.4.1-5)
  • Migration status for glabels/amd64 (3.4.1-5 to 3.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: glabels/amd64 iec16022 (not considered)
    • Invalidated by dependency
• glabels/arm64 (3.4.1-5 to 3.4.1-5)
  • Migration status for glabels/arm64 (3.4.1-5 to 3.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: glabels/arm64 iec16022 (not considered)
    • Invalidated by dependency
• glabels/armel (3.4.1-5 to 3.4.1-5)
  • Migration status for glabels/armel (3.4.1-5 to 3.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: glabels/armel iec16022 (not considered)
    • Invalidated by dependency
• glabels/armhf (3.4.1-5 to 3.4.1-5)
  • Migration status for glabels/armhf (3.4.1-5 to 3.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: glabels/armhf iec16022 (not considered)
    • Invalidated by dependency
• glabels/i386 (3.4.1-5 to 3.4.1-5)
  • Migration status for glabels/i386 (3.4.1-5 to 3.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: glabels/i386 iec16022 (not considered)
    • Invalidated by dependency
• glabels/mips64el (3.4.1-5 to 3.4.1-5)
  • Migration status for glabels/mips64el (3.4.1-5 to 3.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: glabels/mips64el iec16022 (not considered)
    • Invalidated by dependency
• glabels/ppc64el (3.4.1-5 to 3.4.1-5)
  • Migration status for glabels/ppc64el (3.4.1-5 to 3.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: glabels/ppc64el iec16022 (not considered)
    • Invalidated by dependency
• glabels/riscv64 (3.4.1-5 to 3.4.1-5)
  • Migration status for glabels/riscv64 (3.4.1-5 to 3.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: glabels/riscv64 iec16022 (not considered)
    • Invalidated by dependency
• glabels/s390x (3.4.1-5 to 3.4.1-5)
  • Migration status for glabels/s390x (3.4.1-5 to 3.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: glabels/s390x iec16022 (not considered)
    • Invalidated by dependency
• gmastermind.app/amd64 (0.6-2 to 0.6-2)
  • Migration status for gmastermind.app/amd64 (0.6-2 to 0.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gmastermind.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• gmastermind.app/arm64 (0.6-2 to 0.6-2)
  • Migration status for gmastermind.app/arm64 (0.6-2 to 0.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gmastermind.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• gmastermind.app/armel (0.6-2 to 0.6-2)
  • Migration status for gmastermind.app/armel (0.6-2 to 0.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gmastermind.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• gmastermind.app/armhf (0.6-2 to 0.6-2)
  • Migration status for gmastermind.app/armhf (0.6-2 to 0.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gmastermind.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• gmastermind.app/i386 (0.6-2 to 0.6-2)
  • Migration status for gmastermind.app/i386 (0.6-2 to 0.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gmastermind.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• gmastermind.app/mips64el (0.6-2 to 0.6-2)
  • Migration status for gmastermind.app/mips64el (0.6-2 to 0.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gmastermind.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• gmastermind.app/ppc64el (0.6-2 to 0.6-2)
  • Migration status for gmastermind.app/ppc64el (0.6-2 to 0.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gmastermind.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• gmastermind.app/riscv64 (0.6-2 to 0.6-2)
  • Migration status for gmastermind.app/riscv64 (0.6-2 to 0.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gmastermind.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• gmastermind.app/s390x (0.6-2 to 0.6-2)
  • Migration status for gmastermind.app/s390x (0.6-2 to 0.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gmastermind.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• gnustep-examples/amd64 (1:1.4.0-4 to 1:1.4.0-4)
  • Migration status for gnustep-examples/amd64 (1:1.4.0-4 to 1:1.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-examples/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• gnustep-examples/arm64 (1:1.4.0-4 to 1:1.4.0-4)
  • Migration status for gnustep-examples/arm64 (1:1.4.0-4 to 1:1.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-examples/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• gnustep-examples/armel (1:1.4.0-4 to 1:1.4.0-4)
  • Migration status for gnustep-examples/armel (1:1.4.0-4 to 1:1.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-examples/armel gnustep-make (not considered)
    • Invalidated by dependency
• gnustep-examples/armhf (1:1.4.0-4 to 1:1.4.0-4)
  • Migration status for gnustep-examples/armhf (1:1.4.0-4 to 1:1.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-examples/armhf gnustep-make (not considered)
    • Invalidated by dependency
• gnustep-examples/i386 (1:1.4.0-4 to 1:1.4.0-4)
  • Migration status for gnustep-examples/i386 (1:1.4.0-4 to 1:1.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-examples/i386 gnustep-make (not considered)
    • Invalidated by dependency
• gnustep-examples/mips64el (1:1.4.0-4 to 1:1.4.0-4)
  • Migration status for gnustep-examples/mips64el (1:1.4.0-4 to 1:1.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-examples/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• gnustep-examples/ppc64el (1:1.4.0-4 to 1:1.4.0-4)
  • Migration status for gnustep-examples/ppc64el (1:1.4.0-4 to 1:1.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-examples/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• gnustep-examples/riscv64 (1:1.4.0-4 to 1:1.4.0-4)
  • Migration status for gnustep-examples/riscv64 (1:1.4.0-4 to 1:1.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-examples/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• gnustep-examples/s390x (1:1.4.0-4 to 1:1.4.0-4)
  • Migration status for gnustep-examples/s390x (1:1.4.0-4 to 1:1.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-examples/s390x gnustep-make (not considered)
    • Invalidated by dependency
• golang-github-containers-buildah_pu (1.38.1+ds1-1 to 1.28.2+ds1-3+deb12u1)
  • Migration status for golang-github-containers-buildah_pu (1.38.1+ds1-1 to 1.28.2+ds1-3+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: golang-github-containers-buildah is newer in the target suite (1.38.1+ds1-1 1.28.2+ds1-3+deb12u1)
• gridlock.app/amd64 (1.10-6 to 1.10-6)
  • Migration status for gridlock.app/amd64 (1.10-6 to 1.10-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gridlock.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• gridlock.app/arm64 (1.10-6 to 1.10-6)
  • Migration status for gridlock.app/arm64 (1.10-6 to 1.10-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gridlock.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• gridlock.app/armel (1.10-6 to 1.10-6)
  • Migration status for gridlock.app/armel (1.10-6 to 1.10-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gridlock.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• gridlock.app/armhf (1.10-6 to 1.10-6)
  • Migration status for gridlock.app/armhf (1.10-6 to 1.10-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gridlock.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• gridlock.app/i386 (1.10-6 to 1.10-6)
  • Migration status for gridlock.app/i386 (1.10-6 to 1.10-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gridlock.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• gridlock.app/mips64el (1.10-6 to 1.10-6)
  • Migration status for gridlock.app/mips64el (1.10-6 to 1.10-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gridlock.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• gridlock.app/ppc64el (1.10-6 to 1.10-6)
  • Migration status for gridlock.app/ppc64el (1.10-6 to 1.10-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gridlock.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• gridlock.app/riscv64 (1.10-6 to 1.10-6)
  • Migration status for gridlock.app/riscv64 (1.10-6 to 1.10-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gridlock.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• gridlock.app/s390x (1.10-6 to 1.10-6)
  • Migration status for gridlock.app/s390x (1.10-6 to 1.10-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gridlock.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• grpc/amd64 (1.51.1-5 to 1.51.1-5)
  • Migration status for grpc/amd64 (1.51.1-5 to 1.51.1-5): Will attempt migration (Any information below is purely informational)
• grpc/i386 (1.51.1-5 to 1.51.1-5)
  • Migration status for grpc/i386 (1.51.1-5 to 1.51.1-5): Will attempt migration (Any information below is purely informational)
• grpc/ppc64el (1.51.1-5 to 1.51.1-5)
  • Migration status for grpc/ppc64el (1.51.1-5 to 1.51.1-5): Will attempt migration (Any information below is purely informational)
• gss_pu (1.0.4-4 to 1.0.4-1+deb12u1)
  • Migration status for gss_pu (1.0.4-4 to 1.0.4-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: gss is newer in the target suite (1.0.4-4 1.0.4-1+deb12u1)
• gtamsanalyzer.app/amd64 (0.42-9 to 0.42-9)
  • Migration status for gtamsanalyzer.app/amd64 (0.42-9 to 0.42-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gtamsanalyzer.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• gtamsanalyzer.app/arm64 (0.42-9 to 0.42-9)
  • Migration status for gtamsanalyzer.app/arm64 (0.42-9 to 0.42-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gtamsanalyzer.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• gtamsanalyzer.app/armel (0.42-9 to 0.42-9)
  • Migration status for gtamsanalyzer.app/armel (0.42-9 to 0.42-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gtamsanalyzer.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• gtamsanalyzer.app/armhf (0.42-9 to 0.42-9)
  • Migration status for gtamsanalyzer.app/armhf (0.42-9 to 0.42-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gtamsanalyzer.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• gtamsanalyzer.app/i386 (0.42-9 to 0.42-9)
  • Migration status for gtamsanalyzer.app/i386 (0.42-9 to 0.42-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gtamsanalyzer.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• gtamsanalyzer.app/mips64el (0.42-9 to 0.42-9)
  • Migration status for gtamsanalyzer.app/mips64el (0.42-9 to 0.42-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gtamsanalyzer.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• gtamsanalyzer.app/ppc64el (0.42-9 to 0.42-9)
  • Migration status for gtamsanalyzer.app/ppc64el (0.42-9 to 0.42-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gtamsanalyzer.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• gtamsanalyzer.app/riscv64 (0.42-9 to 0.42-9)
  • Migration status for gtamsanalyzer.app/riscv64 (0.42-9 to 0.42-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gtamsanalyzer.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• gtamsanalyzer.app/s390x (0.42-9 to 0.42-9)
  • Migration status for gtamsanalyzer.app/s390x (0.42-9 to 0.42-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gtamsanalyzer.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• haskell-active/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for haskell-active/amd64 (0.2.1-1 to 0.2.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: haskell-active/amd64 haskell-diagrams-lib/amd64 (not considered)
    • Invalidated by implicit-dependency
    • Depends: haskell-active/amd64 haskell-linear/amd64
• haskell-binary-instances/amd64 (1.0.4-2 to 1.0.4-2)
  • Migration status for haskell-binary-instances/amd64 (1.0.4-2 to 1.0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: haskell-binary-instances/amd64 haskell-binary-orphans/amd64 (not considered)
    • Invalidated by dependency
• haskell-binary-orphans/amd64 (1.0.5-1 to 1.0.5-1)
  • Migration status for haskell-binary-orphans/amd64 (1.0.5-1 to 1.0.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: haskell-binary-orphans/amd64 haskell-bytes/amd64 (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: haskell-binary-orphans/amd64 haskell-binary-instances/amd64
    • Implicit dependency: haskell-binary-orphans/amd64 haskell-criterion/amd64
• haskell-bytes/amd64 (0.17.3-2 to 0.17.3-2)
  • Migration status for haskell-bytes/amd64 (0.17.3-2 to 0.17.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: haskell-bytes/amd64 haskell-linear/amd64 (not considered)
    • Invalidated by implicit-dependency
    • Depends: haskell-bytes/amd64 haskell-binary-orphans/amd64
    • Implicit dependency: haskell-bytes/amd64 haskell-log-domain/amd64
• haskell-criterion/amd64 (1.6.3.0-1 to 1.6.3.0-1)
  • Migration status for haskell-criterion/amd64 (1.6.3.0-1 to 1.6.3.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: haskell-criterion/amd64 haskell-binary-orphans/amd64 (not considered)
    • Invalidated by dependency
    • Depends: haskell-criterion/amd64 haskell-statistics/amd64
• haskell-dense-linear-algebra/amd64 (0.1.0.0-6 to 0.1.0.0-6)
  • Migration status for haskell-dense-linear-algebra/amd64 (0.1.0.0-6 to 0.1.0.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: haskell-dense-linear-algebra/amd64 haskell-statistics/amd64 (not considered)
    • Invalidated by implicit-dependency
    • Depends: haskell-dense-linear-algebra/amd64 haskell-vector-th-unbox/amd64
• haskell-diagrams-cairo/amd64 (1.4.2.1-2 to 1.4.2.1-2)
  • Migration status for haskell-diagrams-cairo/amd64 (1.4.2.1-2 to 1.4.2.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: haskell-diagrams-cairo/amd64 haskell-pango/amd64 (not considered)
    • Invalidated by dependency
    • Depends: haskell-diagrams-cairo/amd64 haskell-diagrams-core/amd64
    • Depends: haskell-diagrams-cairo/amd64 haskell-diagrams-lib/amd64
• haskell-diagrams-core/amd64 (1.5.1.1-1 to 1.5.1.1-1)
  • Migration status for haskell-diagrams-core/amd64 (1.5.1.1-1 to 1.5.1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: haskell-diagrams-core/amd64 haskell-diagrams-cairo/amd64 (not considered)
    • Invalidated by implicit-dependency
    • Depends: haskell-diagrams-core/amd64 haskell-linear/amd64
    • Implicit dependency: haskell-diagrams-core/amd64 haskell-diagrams-lib/amd64
    • Implicit dependency: haskell-diagrams-core/amd64 haskell-diagrams-svg/amd64
• haskell-diagrams-lib/amd64 (1.4.6.2-1 to 1.4.6.2-1)
  • Migration status for haskell-diagrams-lib/amd64 (1.4.6.2-1 to 1.4.6.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: haskell-diagrams-lib/amd64 haskell-diagrams-cairo/amd64 (not considered)
    • Invalidated by implicit-dependency
    • Depends: haskell-diagrams-lib/amd64 haskell-active/amd64
    • Depends: haskell-diagrams-lib/amd64 haskell-diagrams-core/amd64
    • Depends: haskell-diagrams-lib/amd64 haskell-linear/amd64
    • Implicit dependency: haskell-diagrams-lib/amd64 haskell-diagrams-svg/amd64
• haskell-diagrams-svg/amd64 (1.4.3.2-1 to 1.4.3.2-1)
  • Migration status for haskell-diagrams-svg/amd64 (1.4.3.2-1 to 1.4.3.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: haskell-diagrams-svg/amd64 haskell-diagrams-lib/amd64 (not considered)
    • Invalidated by dependency
    • Depends: haskell-diagrams-svg/amd64 haskell-diagrams-core/amd64
• haskell-lambdahack/amd64 (0.11.0.1-1 to 0.11.0.1-1)
  • Migration status for haskell-lambdahack/amd64 (0.11.0.1-1 to 0.11.0.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: haskell-lambdahack/amd64 haskell-sdl2/amd64 (not considered)
    • Invalidated by dependency
    • Depends: haskell-lambdahack/amd64 haskell-sdl2-ttf/amd64
• haskell-linear/amd64 (1.22-2 to 1.22-2)
  • Migration status for haskell-linear/amd64 (1.22-2 to 1.22-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: haskell-linear/amd64 haskell-diagrams-lib/amd64 (not considered)
    • Invalidated by implicit-dependency
    • Depends: haskell-linear/amd64 haskell-bytes/amd64
    • Implicit dependency: haskell-linear/amd64 haskell-active/amd64
    • Implicit dependency: haskell-linear/amd64 haskell-diagrams-core/amd64
    • Implicit dependency: haskell-linear/amd64 haskell-sdl2/amd64
• haskell-log-domain/amd64 (0.13.2-3 to 0.13.2-3)
  • Migration status for haskell-log-domain/amd64 (0.13.2-3 to 0.13.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: haskell-log-domain/amd64 haskell-bytes/amd64 (not considered)
    • Invalidated by dependency
• haskell-pango/amd64 (0.13.11.0-1 to 0.13.11.0-1)
  • Migration status for haskell-pango/amd64 (0.13.11.0-1 to 0.13.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libghc-pango-dev/0.13.11.0-1+b1/amd64 to testing makes libghc-gtk-dev/0.15.9-1+b1/amd64 uninstallable
    • migrating libghc-pango-dev/0.13.11.0-1+b1/amd64 to testing makes libghc-gtk3-dev/0.15.9-1+b1/amd64 uninstallable
    • migrating libghc-pango-prof/0.13.11.0-1+b1/amd64 to testing makes libghc-gtk-prof/0.15.9-1+b1/amd64 uninstallable
    • migrating libghc-pango-prof/0.13.11.0-1+b1/amd64 to testing makes libghc-gtk3-prof/0.15.9-1+b1/amd64 uninstallable
    • Implicit dependency: haskell-pango/amd64 haskell-diagrams-cairo/amd64
• haskell-sdl2-image/amd64 (2.1.0.0-4 to 2.1.0.0-4)
  • Migration status for haskell-sdl2-image/amd64 (2.1.0.0-4 to 2.1.0.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: haskell-sdl2-image/amd64 haskell-sdl2/amd64 (not considered)
    • Invalidated by dependency
• haskell-sdl2-mixer/amd64 (1.2.0.0-4 to 1.2.0.0-4)
  • Migration status for haskell-sdl2-mixer/amd64 (1.2.0.0-4 to 1.2.0.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: haskell-sdl2-mixer/amd64 haskell-sdl2/amd64 (not considered)
    • Invalidated by dependency
• haskell-sdl2-ttf/amd64 (2.1.3-3 to 2.1.3-3)
  • Migration status for haskell-sdl2-ttf/amd64 (2.1.3-3 to 2.1.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: haskell-sdl2-ttf/amd64 haskell-sdl2/amd64 (not considered)
    • Invalidated by dependency
    • Implicit dependency: haskell-sdl2-ttf/amd64 haskell-lambdahack/amd64
• haskell-sdl2/amd64 (2.5.5.0-2 to 2.5.5.0-2)
  • Migration status for haskell-sdl2/amd64 (2.5.5.0-2 to 2.5.5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: haskell-sdl2/amd64 haskell-linear/amd64 (not considered)
    • Invalidated by dependency
    • Implicit dependency: haskell-sdl2/amd64 haskell-lambdahack/amd64
    • Implicit dependency: haskell-sdl2/amd64 haskell-sdl2-image/amd64
    • Implicit dependency: haskell-sdl2/amd64 haskell-sdl2-mixer/amd64
    • Implicit dependency: haskell-sdl2/amd64 haskell-sdl2-ttf/amd64
• haskell-statistics/amd64 (0.16.2.1-2 to 0.16.2.1-2)
  • Migration status for haskell-statistics/amd64 (0.16.2.1-2 to 0.16.2.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: haskell-statistics/amd64 haskell-criterion/amd64 (not considered)
    • Invalidated by implicit-dependency
    • Depends: haskell-statistics/amd64 haskell-dense-linear-algebra/amd64
    • Depends: haskell-statistics/amd64 haskell-vector-th-unbox/amd64
• haskell-vector-th-unbox/amd64 (0.2.2-3 to 0.2.2-3)
  • Migration status for haskell-vector-th-unbox/amd64 (0.2.2-3 to 0.2.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: haskell-vector-th-unbox/amd64 haskell-statistics/amd64 (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: haskell-vector-th-unbox/amd64 haskell-dense-linear-algebra/amd64
• helpviewer.app/amd64 (0.4-2 to 0.4-2)
  • Migration status for helpviewer.app/amd64 (0.4-2 to 0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: helpviewer.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• helpviewer.app/arm64 (0.4-2 to 0.4-2)
  • Migration status for helpviewer.app/arm64 (0.4-2 to 0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: helpviewer.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• helpviewer.app/armel (0.4-2 to 0.4-2)
  • Migration status for helpviewer.app/armel (0.4-2 to 0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: helpviewer.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• helpviewer.app/armhf (0.4-2 to 0.4-2)
  • Migration status for helpviewer.app/armhf (0.4-2 to 0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: helpviewer.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• helpviewer.app/i386 (0.4-2 to 0.4-2)
  • Migration status for helpviewer.app/i386 (0.4-2 to 0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: helpviewer.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• helpviewer.app/mips64el (0.4-2 to 0.4-2)
  • Migration status for helpviewer.app/mips64el (0.4-2 to 0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: helpviewer.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• helpviewer.app/ppc64el (0.4-2 to 0.4-2)
  • Migration status for helpviewer.app/ppc64el (0.4-2 to 0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: helpviewer.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• helpviewer.app/riscv64 (0.4-2 to 0.4-2)
  • Migration status for helpviewer.app/riscv64 (0.4-2 to 0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: helpviewer.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• helpviewer.app/s390x (0.4-2 to 0.4-2)
  • Migration status for helpviewer.app/s390x (0.4-2 to 0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: helpviewer.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• hivex/amd64 (1.3.24-1 to 1.3.24-1)
  • Migration status for hivex/amd64 (1.3.24-1 to 1.3.24-1): Will attempt migration (Any information below is purely informational)
• hivex/arm64 (1.3.24-1 to 1.3.24-1)
  • Migration status for hivex/arm64 (1.3.24-1 to 1.3.24-1): Will attempt migration (Any information below is purely informational)
• hivex/armel (1.3.24-1 to 1.3.24-1)
  • Migration status for hivex/armel (1.3.24-1 to 1.3.24-1): Will attempt migration (Any information below is purely informational)
• hivex/armhf (1.3.24-1 to 1.3.24-1)
  • Migration status for hivex/armhf (1.3.24-1 to 1.3.24-1): Will attempt migration (Any information below is purely informational)
• hivex/i386 (1.3.24-1 to 1.3.24-1)
  • Migration status for hivex/i386 (1.3.24-1 to 1.3.24-1): Will attempt migration (Any information below is purely informational)
• hivex/mips64el (1.3.24-1 to 1.3.24-1)
  • Migration status for hivex/mips64el (1.3.24-1 to 1.3.24-1): Will attempt migration (Any information below is purely informational)
• hivex/ppc64el (1.3.24-1 to 1.3.24-1)
  • Migration status for hivex/ppc64el (1.3.24-1 to 1.3.24-1): Will attempt migration (Any information below is purely informational)
• hivex/riscv64 (1.3.24-1 to 1.3.24-1)
  • Migration status for hivex/riscv64 (1.3.24-1 to 1.3.24-1): Will attempt migration (Any information below is purely informational)
• hivex/s390x (1.3.24-1 to 1.3.24-1)
  • Migration status for hivex/s390x (1.3.24-1 to 1.3.24-1): Will attempt migration (Any information below is purely informational)
• httpdirfs-fuse/amd64 (1.2.5-1 to 1.2.5-1)
  • Migration status for httpdirfs-fuse/amd64 (1.2.5-1 to 1.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: httpdirfs-fuse/amd64 gumbo-parser (not considered)
    • Invalidated by dependency
• httpdirfs-fuse/arm64 (1.2.5-1 to 1.2.5-1)
  • Migration status for httpdirfs-fuse/arm64 (1.2.5-1 to 1.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: httpdirfs-fuse/arm64 gumbo-parser (not considered)
    • Invalidated by dependency
• httpdirfs-fuse/armel (1.2.5-1 to 1.2.5-1)
  • Migration status for httpdirfs-fuse/armel (1.2.5-1 to 1.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: httpdirfs-fuse/armel gumbo-parser (not considered)
    • Invalidated by dependency
• httpdirfs-fuse/armhf (1.2.5-1 to 1.2.5-1)
  • Migration status for httpdirfs-fuse/armhf (1.2.5-1 to 1.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: httpdirfs-fuse/armhf gumbo-parser (not considered)
    • Invalidated by dependency
• httpdirfs-fuse/i386 (1.2.5-1 to 1.2.5-1)
  • Migration status for httpdirfs-fuse/i386 (1.2.5-1 to 1.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: httpdirfs-fuse/i386 gumbo-parser (not considered)
    • Invalidated by dependency
• httpdirfs-fuse/mips64el (1.2.5-1 to 1.2.5-1)
  • Migration status for httpdirfs-fuse/mips64el (1.2.5-1 to 1.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: httpdirfs-fuse/mips64el gumbo-parser (not considered)
    • Invalidated by dependency
• httpdirfs-fuse/ppc64el (1.2.5-1 to 1.2.5-1)
  • Migration status for httpdirfs-fuse/ppc64el (1.2.5-1 to 1.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: httpdirfs-fuse/ppc64el gumbo-parser (not considered)
    • Invalidated by dependency
• httpdirfs-fuse/riscv64 (1.2.5-1 to 1.2.5-1)
  • Migration status for httpdirfs-fuse/riscv64 (1.2.5-1 to 1.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: httpdirfs-fuse/riscv64 gumbo-parser (not considered)
    • Invalidated by dependency
• httpdirfs-fuse/s390x (1.2.5-1 to 1.2.5-1)
  • Migration status for httpdirfs-fuse/s390x (1.2.5-1 to 1.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: httpdirfs-fuse/s390x gumbo-parser (not considered)
    • Invalidated by dependency
• joblib_pu (1.3.2-6 to 1.2.0-4+deb12u1)
  • Migration status for joblib_pu (1.3.2-6 to 1.2.0-4+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: joblib is newer in the target suite (1.3.2-6 1.2.0-4+deb12u1)
• js-of-ocaml/amd64 (5.9.1-1 to 5.9.1-1)
  • Migration status for js-of-ocaml/amd64 (5.9.1-1 to 5.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libjs-of-ocaml/5.9.1-1+b4/amd64 to testing makes libcohttp-lwt-jsoo-ocaml/5.3.0-1+b17/amd64 uninstallable
    • migrating libjs-of-ocaml/5.9.1-1+b4/amd64 to testing makes liblogs-ocaml/0.7.0-3+b17/amd64 uninstallable
    • migrating libjs-of-ocaml/5.9.1-1+b4/amd64 to testing makes nurpawiki/1.2.4-4+b18/amd64 uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b4/amd64 to testing makes libcohttp-lwt-jsoo-ocaml-dev/5.3.0-1+b17/amd64 uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b4/amd64 to testing makes libeliom-ocaml-dev/11.1.1-2/amd64 uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b4/amd64 to testing makes liblogs-ocaml-dev/0.7.0-3+b17/amd64 uninstallable
    • Depends: js-of-ocaml/amd64 findlib (not considered)
• js-of-ocaml/arm64 (5.9.1-1 to 5.9.1-1)
  • Migration status for js-of-ocaml/arm64 (5.9.1-1 to 5.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libjs-of-ocaml/5.9.1-1+b3/arm64 to testing makes libcohttp-lwt-jsoo-ocaml/5.3.0-1+b17/arm64 uninstallable
    • migrating libjs-of-ocaml/5.9.1-1+b3/arm64 to testing makes liblogs-ocaml/0.7.0-3+b17/arm64 uninstallable
    • migrating libjs-of-ocaml/5.9.1-1+b3/arm64 to testing makes nurpawiki/1.2.4-4+b18/arm64 uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b3/arm64 to testing makes libcohttp-lwt-jsoo-ocaml-dev/5.3.0-1+b17/arm64 uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b3/arm64 to testing makes libeliom-ocaml-dev/11.1.1-2/arm64 uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b3/arm64 to testing makes liblogs-ocaml-dev/0.7.0-3+b17/arm64 uninstallable
    • Depends: js-of-ocaml/arm64 findlib (not considered)
• js-of-ocaml/armel (5.9.1-1 to 5.9.1-1)
  • Migration status for js-of-ocaml/armel (5.9.1-1 to 5.9.1-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 findlib (not considered)
    • Invalidated by dependency
• js-of-ocaml/armhf (5.9.1-1 to 5.9.1-1)
  • Migration status for js-of-ocaml/armhf (5.9.1-1 to 5.9.1-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 findlib (not considered)
    • Invalidated by dependency
• js-of-ocaml/i386 (5.9.1-1 to 5.9.1-1)
  • Migration status for js-of-ocaml/i386 (5.9.1-1 to 5.9.1-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 findlib (not considered)
    • Invalidated by dependency
• js-of-ocaml/mips64el (5.9.1-1 to 5.9.1-1)
  • Migration status for js-of-ocaml/mips64el (5.9.1-1 to 5.9.1-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 findlib (not considered)
    • Invalidated by dependency
• js-of-ocaml/ppc64el (5.9.1-1 to 5.9.1-1)
  • Migration status for js-of-ocaml/ppc64el (5.9.1-1 to 5.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libjs-of-ocaml/5.9.1-1+b3/ppc64el to testing makes libcohttp-lwt-jsoo-ocaml/5.3.0-1+b17/ppc64el uninstallable
    • migrating libjs-of-ocaml/5.9.1-1+b3/ppc64el to testing makes liblogs-ocaml/0.7.0-3+b17/ppc64el uninstallable
    • migrating libjs-of-ocaml/5.9.1-1+b3/ppc64el to testing makes nurpawiki/1.2.4-4+b18/ppc64el uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b3/ppc64el to testing makes libcohttp-lwt-jsoo-ocaml-dev/5.3.0-1+b17/ppc64el uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b3/ppc64el to testing makes libeliom-ocaml-dev/11.1.1-2/ppc64el uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b3/ppc64el to testing makes liblogs-ocaml-dev/0.7.0-3+b17/ppc64el uninstallable
    • Depends: js-of-ocaml/ppc64el findlib (not considered)
• js-of-ocaml/riscv64 (5.9.1-1 to 5.9.1-1)
  • Migration status for js-of-ocaml/riscv64 (5.9.1-1 to 5.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libjs-of-ocaml/5.9.1-1+b3/riscv64 to testing makes libcohttp-lwt-jsoo-ocaml/5.3.0-1+b17/riscv64 uninstallable
    • migrating libjs-of-ocaml/5.9.1-1+b3/riscv64 to testing makes liblogs-ocaml/0.7.0-3+b17/riscv64 uninstallable
    • migrating libjs-of-ocaml/5.9.1-1+b3/riscv64 to testing makes nurpawiki/1.2.4-4+b19/riscv64 uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b3/riscv64 to testing makes libcohttp-lwt-jsoo-ocaml-dev/5.3.0-1+b17/riscv64 uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b3/riscv64 to testing makes libeliom-ocaml-dev/11.1.1-2/riscv64 uninstallable
    • migrating libjs-of-ocaml-dev/5.9.1-1+b3/riscv64 to testing makes liblogs-ocaml-dev/0.7.0-3+b17/riscv64 uninstallable
    • Depends: js-of-ocaml/riscv64 findlib (not considered)
• k2pdfopt/amd64 (2.55+ds-3.1 to 2.55+ds-3.1)
  • Migration status for k2pdfopt/amd64 (2.55+ds-3.1 to 2.55+ds-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: k2pdfopt/amd64 mupdf (not considered)
    • Invalidated by dependency
• k2pdfopt/arm64 (2.55+ds-3.1 to 2.55+ds-3.1)
  • Migration status for k2pdfopt/arm64 (2.55+ds-3.1 to 2.55+ds-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: k2pdfopt/arm64 mupdf (not considered)
    • Invalidated by dependency
• k2pdfopt/armel (2.55+ds-3.1 to 2.55+ds-3.1)
  • Migration status for k2pdfopt/armel (2.55+ds-3.1 to 2.55+ds-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: k2pdfopt/armel mupdf (not considered)
    • Invalidated by dependency
• k2pdfopt/armhf (2.55+ds-3.1 to 2.55+ds-3.1)
  • Migration status for k2pdfopt/armhf (2.55+ds-3.1 to 2.55+ds-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: k2pdfopt/armhf mupdf (not considered)
    • Invalidated by dependency
• k2pdfopt/i386 (2.55+ds-3.1 to 2.55+ds-3.1)
  • Migration status for k2pdfopt/i386 (2.55+ds-3.1 to 2.55+ds-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: k2pdfopt/i386 mupdf (not considered)
    • Invalidated by dependency
• k2pdfopt/ppc64el (2.55+ds-3.1 to 2.55+ds-3.1)
  • Migration status for k2pdfopt/ppc64el (2.55+ds-3.1 to 2.55+ds-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: k2pdfopt/ppc64el mupdf (not considered)
    • Invalidated by dependency
• k2pdfopt/riscv64 (2.55+ds-3.1 to 2.55+ds-3.1)
  • Migration status for k2pdfopt/riscv64 (2.55+ds-3.1 to 2.55+ds-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: k2pdfopt/riscv64 mupdf (not considered)
    • Invalidated by dependency
• k2pdfopt/s390x (2.55+ds-3.1 to 2.55+ds-3.1)
  • Migration status for k2pdfopt/s390x (2.55+ds-3.1 to 2.55+ds-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: k2pdfopt/s390x mupdf (not considered)
    • Invalidated by dependency
• kcov/riscv64 (43+dfsg-1 to 43+dfsg-1)
  • Migration status for kcov/riscv64 (43+dfsg-1 to 43+dfsg-1): Will attempt migration (Any information below is purely informational)
• kexec-tools_pu (1:2.0.29-2 to 1:2.0.25-3+deb12u2)
  • Migration status for kexec-tools_pu (1:2.0.29-2 to 1:2.0.25-3+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: kexec-tools is newer in the target suite (1:2.0.29-2 1:2.0.25-3+deb12u2)
• kristall/amd64 (0.4+dfsg-4 to 0.4+dfsg-4)
  • Migration status for kristall/amd64 (0.4+dfsg-4 to 0.4+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kristall/amd64 gumbo-parser (not considered)
    • Invalidated by dependency
• kristall/arm64 (0.4+dfsg-4 to 0.4+dfsg-4)
  • Migration status for kristall/arm64 (0.4+dfsg-4 to 0.4+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kristall/arm64 gumbo-parser (not considered)
    • Invalidated by dependency
• kristall/armel (0.4+dfsg-4 to 0.4+dfsg-4)
  • Migration status for kristall/armel (0.4+dfsg-4 to 0.4+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kristall/armel gumbo-parser (not considered)
    • Invalidated by dependency
• kristall/armhf (0.4+dfsg-4 to 0.4+dfsg-4)
  • Migration status for kristall/armhf (0.4+dfsg-4 to 0.4+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kristall/armhf gumbo-parser (not considered)
    • Invalidated by dependency
• kristall/i386 (0.4+dfsg-4 to 0.4+dfsg-4)
  • Migration status for kristall/i386 (0.4+dfsg-4 to 0.4+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kristall/i386 gumbo-parser (not considered)
    • Invalidated by dependency
• kristall/mips64el (0.4+dfsg-4 to 0.4+dfsg-4)
  • Migration status for kristall/mips64el (0.4+dfsg-4 to 0.4+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kristall/mips64el gumbo-parser (not considered)
    • Invalidated by dependency
• kristall/ppc64el (0.4+dfsg-4 to 0.4+dfsg-4)
  • Migration status for kristall/ppc64el (0.4+dfsg-4 to 0.4+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kristall/ppc64el gumbo-parser (not considered)
    • Invalidated by dependency
• kristall/riscv64 (0.4+dfsg-4 to 0.4+dfsg-4)
  • Migration status for kristall/riscv64 (0.4+dfsg-4 to 0.4+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kristall/riscv64 gumbo-parser (not considered)
    • Invalidated by dependency
• kristall/s390x (0.4+dfsg-4 to 0.4+dfsg-4)
  • Migration status for kristall/s390x (0.4+dfsg-4 to 0.4+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kristall/s390x gumbo-parser (not considered)
    • Invalidated by dependency
• lablgl/amd64 (1:1.07-2 to 1:1.07-2)
  • Migration status for lablgl/amd64 (1:1.07-2 to 1:1.07-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lablgl/amd64 labltk (not considered)
    • Invalidated by dependency
• lablgl/arm64 (1:1.07-2 to 1:1.07-2)
  • Migration status for lablgl/arm64 (1:1.07-2 to 1:1.07-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lablgl/arm64 labltk (not considered)
    • Invalidated by dependency
• lablgl/armel (1:1.07-2 to 1:1.07-2)
  • Migration status for lablgl/armel (1:1.07-2 to 1:1.07-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lablgl/armel labltk (not considered)
    • Invalidated by dependency
• lablgl/armhf (1:1.07-2 to 1:1.07-2)
  • Migration status for lablgl/armhf (1:1.07-2 to 1:1.07-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lablgl/armhf labltk (not considered)
    • Invalidated by dependency
• lablgl/i386 (1:1.07-2 to 1:1.07-2)
  • Migration status for lablgl/i386 (1:1.07-2 to 1:1.07-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lablgl/i386 labltk (not considered)
    • Invalidated by dependency
• lablgl/mips64el (1:1.07-2 to 1:1.07-2)
  • Migration status for lablgl/mips64el (1:1.07-2 to 1:1.07-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lablgl/mips64el labltk (not considered)
    • Invalidated by dependency
• lablgl/ppc64el (1:1.07-2 to 1:1.07-2)
  • Migration status for lablgl/ppc64el (1:1.07-2 to 1:1.07-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lablgl/ppc64el labltk (not considered)
    • Invalidated by dependency
• lablgl/riscv64 (1:1.07-2 to 1:1.07-2)
  • Migration status for lablgl/riscv64 (1:1.07-2 to 1:1.07-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lablgl/riscv64 labltk (not considered)
    • Invalidated by dependency
• lemonldap-ng_pu (2.20.2+ds-1 to 2.16.1+ds-deb12u5)
  • Migration status for lemonldap-ng_pu (2.20.2+ds-1 to 2.16.1+ds-deb12u5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: lemonldap-ng is newer in the target suite (2.20.2+ds-1 2.16.1+ds-deb12u5)
• lfortran/s390x (0.45.0-1 to 0.45.0-1)
  • Migration status for lfortran/s390x (0.45.0-1 to 0.45.0-1): Will attempt migration (Any information below is purely informational)
• libguestfs/amd64 (1:1.52.2-7 to 1:1.52.2-7)
  • Migration status for libguestfs/amd64 (1:1.52.2-7 to 1:1.52.2-7): Will attempt migration (Any information below is purely informational)
• libguestfs/arm64 (1:1.52.2-7 to 1:1.52.2-7)
  • Migration status for libguestfs/arm64 (1:1.52.2-7 to 1:1.52.2-7): Will attempt migration (Any information below is purely informational)
• libguestfs/i386 (1:1.52.2-7 to 1:1.52.2-7)
  • Migration status for libguestfs/i386 (1:1.52.2-7 to 1:1.52.2-7): Will attempt migration (Any information below is purely informational)
• libguestfs/mips64el (1:1.52.2-7 to 1:1.52.2-7)
  • Migration status for libguestfs/mips64el (1:1.52.2-7 to 1:1.52.2-7): Will attempt migration (Any information below is purely informational)
• libguestfs/ppc64el (1:1.52.2-7 to 1:1.52.2-7)
  • Migration status for libguestfs/ppc64el (1:1.52.2-7 to 1:1.52.2-7): Will attempt migration (Any information below is purely informational)
• libpaper/mips64el (2.2.5-0.3 to 2.2.5-0.3)
  • Migration status for libpaper/mips64el (2.2.5-0.3 to 2.2.5-0.3): Will attempt migration (Any information below is purely informational)
• libpaper/riscv64 (2.2.5-0.3 to 2.2.5-0.3)
  • Migration status for libpaper/riscv64 (2.2.5-0.3 to 2.2.5-0.3): Will attempt migration (Any information below is purely informational)
• libpaper/s390x (2.2.5-0.3 to 2.2.5-0.3)
  • Migration status for libpaper/s390x (2.2.5-0.3 to 2.2.5-0.3): Will attempt migration (Any information below is purely informational)
• librabbitmq_pu (0.15.0-1 to 0.11.0-1+deb12u1)
  • Migration status for librabbitmq_pu (0.15.0-1 to 0.11.0-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: librabbitmq is newer in the target suite (0.15.0-1 0.11.0-1+deb12u1)
• libreoffice_pu (4:24.8.4-2 to 4:7.4.7-1+deb12u6)
  • Migration status for libreoffice_pu (4:24.8.4-2 to 4:7.4.7-1+deb12u6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libreoffice is newer in the target suite (4:24.8.4-2 4:7.4.7-1+deb12u6)
• libsemanage/amd64 (3.7-2.1 to 3.7-2.1)
  • Migration status for libsemanage/amd64 (3.7-2.1 to 3.7-2.1): Will attempt migration (Any information below is purely informational)
• libsemanage/arm64 (3.7-2.1 to 3.7-2.1)
  • Migration status for libsemanage/arm64 (3.7-2.1 to 3.7-2.1): Will attempt migration (Any information below is purely informational)
• libsemanage/armel (3.7-2.1 to 3.7-2.1)
  • Migration status for libsemanage/armel (3.7-2.1 to 3.7-2.1): Will attempt migration (Any information below is purely informational)
• libsemanage/armhf (3.7-2.1 to 3.7-2.1)
  • Migration status for libsemanage/armhf (3.7-2.1 to 3.7-2.1): Will attempt migration (Any information below is purely informational)
• libsemanage/i386 (3.7-2.1 to 3.7-2.1)
  • Migration status for libsemanage/i386 (3.7-2.1 to 3.7-2.1): Will attempt migration (Any information below is purely informational)
• libsemanage/mips64el (3.7-2.1 to 3.7-2.1)
  • Migration status for libsemanage/mips64el (3.7-2.1 to 3.7-2.1): Will attempt migration (Any information below is purely informational)
• libsemanage/ppc64el (3.7-2.1 to 3.7-2.1)
  • Migration status for libsemanage/ppc64el (3.7-2.1 to 3.7-2.1): Will attempt migration (Any information below is purely informational)
• libsemanage/riscv64 (3.7-2.1 to 3.7-2.1)
  • Migration status for libsemanage/riscv64 (3.7-2.1 to 3.7-2.1): Will attempt migration (Any information below is purely informational)
• libtar_pu (- to 1.2.20-8+deb12u1)
  • Migration status for libtar_pu (- to 1.2.20-8+deb12u1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • NEEDS APPROVAL BY RM
• links2/riscv64 (2.29-2 to 2.29-2)
  • Migration status for links2/riscv64 (2.29-2 to 2.29-2): Will attempt migration (Any information below is purely informational)
• links2/s390x (2.29-2 to 2.29-2)
  • Migration status for links2/s390x (2.29-2 to 2.29-2): Will attempt migration (Any information below is purely informational)
• linux-signed-amd64_pu (6.12.12+1 to 6.1.128+1)
  • Migration status for linux-signed-amd64_pu (6.12.12+1 to 6.1.128+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linux-signed-amd64 is newer in the target suite (6.12.12+1 6.1.128+1)
• linux-signed-arm64_pu (6.12.12+1 to 6.1.128+1)
  • Migration status for linux-signed-arm64_pu (6.12.12+1 to 6.1.128+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linux-signed-arm64 is newer in the target suite (6.12.12+1 6.1.128+1)
• linux-signed-i386_pu (- to 6.1.128+1)
  • Migration status for linux-signed-i386_pu (- to 6.1.128+1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Build-Depends(-Arch): linux-signed-i386_pu -> linux-image-6.1.0-31-686-pae-unsigned/6.1.128-1/i386
    • Impossible Build-Depends(-Arch): linux-signed-i386_pu -> linux-image-6.1.0-31-686-unsigned/6.1.128-1/i386
    • Impossible Build-Depends(-Arch): linux-signed-i386_pu -> linux-image-6.1.0-31-rt-686-pae-unsigned/6.1.128-1/i386
    • Impossible Build-Depends(-Arch): linux-signed-i386_pu -> linux-support-6.1.0-31/6.1.128-1/i386
    • Impossible Depends: linux-signed-i386_pu -> linux-headers-6.1.0-31-686-pae/6.1.128-1/i386
    • Impossible Depends: linux-signed-i386_pu -> linux-headers-6.1.0-31-686/6.1.128-1/i386
    • Impossible Depends: linux-signed-i386_pu -> linux-headers-6.1.0-31-rt-686-pae/6.1.128-1/i386
    • NEEDS APPROVAL BY RM
• linux_pu (6.12.12-1 to 6.1.128-1)
  • Migration status for linux_pu (6.12.12-1 to 6.1.128-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linux is newer in the target suite (6.12.12-1 6.1.128-1)
• linuxcnc_pu (2.9.3-2 to 2.9.0~pre1+git20230208.f1270d6ed7-1+deb12u1)
  • Migration status for linuxcnc_pu (2.9.3-2 to 2.9.0~pre1+git20230208.f1270d6ed7-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: linuxcnc is newer in the target suite (2.9.3-2 2.9.0~pre1+git20230208.f1270d6ed7-1+deb12u1)
• litehtml/amd64 (0.6-1.2 to 0.6-1.2)
  • Migration status for litehtml/amd64 (0.6-1.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:
    • Depends: litehtml/amd64 gumbo-parser (not considered)
    • Invalidated by dependency
• litehtml/arm64 (0.6-1.2 to 0.6-1.2)
  • Migration status for litehtml/arm64 (0.6-1.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:
    • Depends: litehtml/arm64 gumbo-parser (not considered)
    • Invalidated by dependency
• litehtml/armel (0.6-1.2 to 0.6-1.2)
  • Migration status for litehtml/armel (0.6-1.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:
    • Depends: litehtml/armel gumbo-parser (not considered)
    • Invalidated by dependency
• litehtml/armhf (0.6-1.2 to 0.6-1.2)
  • Migration status for litehtml/armhf (0.6-1.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:
    • Depends: litehtml/armhf gumbo-parser (not considered)
    • Invalidated by dependency
• litehtml/i386 (0.6-1.2 to 0.6-1.2)
  • Migration status for litehtml/i386 (0.6-1.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:
    • Depends: litehtml/i386 gumbo-parser (not considered)
    • Invalidated by dependency
• litehtml/mips64el (0.6-1.2 to 0.6-1.2)
  • Migration status for litehtml/mips64el (0.6-1.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:
    • Depends: litehtml/mips64el gumbo-parser (not considered)
    • Invalidated by dependency
• litehtml/ppc64el (0.6-1.2 to 0.6-1.2)
  • Migration status for litehtml/ppc64el (0.6-1.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:
    • Depends: litehtml/ppc64el gumbo-parser (not considered)
    • Invalidated by dependency
• litehtml/riscv64 (0.6-1.2 to 0.6-1.2)
  • Migration status for litehtml/riscv64 (0.6-1.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:
    • Depends: litehtml/riscv64 gumbo-parser (not considered)
    • Invalidated by dependency
• litehtml/s390x (0.6-1.2 to 0.6-1.2)
  • Migration status for litehtml/s390x (0.6-1.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:
    • Depends: litehtml/s390x gumbo-parser (not considered)
    • Invalidated by dependency
• luametatex/amd64 (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1)
  • Migration status for luametatex/amd64 (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: luametatex/amd64 mimalloc (not considered)
    • Invalidated by dependency
• luametatex/arm64 (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1)
  • Migration status for luametatex/arm64 (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: luametatex/arm64 mimalloc (not considered)
    • Invalidated by dependency
• luametatex/armel (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1)
  • Migration status for luametatex/armel (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: luametatex/armel mimalloc (not considered)
    • Invalidated by dependency
• luametatex/armhf (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1)
  • Migration status for luametatex/armhf (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: luametatex/armhf mimalloc (not considered)
    • Invalidated by dependency
• luametatex/i386 (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1)
  • Migration status for luametatex/i386 (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: luametatex/i386 mimalloc (not considered)
    • Invalidated by dependency
• luametatex/mips64el (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1)
  • Migration status for luametatex/mips64el (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: luametatex/mips64el mimalloc (not considered)
    • Invalidated by dependency
• luametatex/ppc64el (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1)
  • Migration status for luametatex/ppc64el (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: luametatex/ppc64el mimalloc (not considered)
    • Invalidated by dependency
• luametatex/riscv64 (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1)
  • Migration status for luametatex/riscv64 (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: luametatex/riscv64 mimalloc (not considered)
    • Invalidated by dependency
• luametatex/s390x (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1)
  • Migration status for luametatex/s390x (2.11.02+really2.11.01+ds-1 to 2.11.02+really2.11.01+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: luametatex/s390x mimalloc (not considered)
    • Invalidated by dependency
• lusernet.app/amd64 (0.4.3-2 to 0.4.3-2)
  • Migration status for lusernet.app/amd64 (0.4.3-2 to 0.4.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lusernet.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• lusernet.app/arm64 (0.4.3-2 to 0.4.3-2)
  • Migration status for lusernet.app/arm64 (0.4.3-2 to 0.4.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lusernet.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• lusernet.app/armel (0.4.3-2 to 0.4.3-2)
  • Migration status for lusernet.app/armel (0.4.3-2 to 0.4.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lusernet.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• lusernet.app/armhf (0.4.3-2 to 0.4.3-2)
  • Migration status for lusernet.app/armhf (0.4.3-2 to 0.4.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lusernet.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• lusernet.app/i386 (0.4.3-2 to 0.4.3-2)
  • Migration status for lusernet.app/i386 (0.4.3-2 to 0.4.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lusernet.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• lusernet.app/mips64el (0.4.3-2 to 0.4.3-2)
  • Migration status for lusernet.app/mips64el (0.4.3-2 to 0.4.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lusernet.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• lusernet.app/ppc64el (0.4.3-2 to 0.4.3-2)
  • Migration status for lusernet.app/ppc64el (0.4.3-2 to 0.4.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lusernet.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• lusernet.app/riscv64 (0.4.3-2 to 0.4.3-2)
  • Migration status for lusernet.app/riscv64 (0.4.3-2 to 0.4.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lusernet.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• lusernet.app/s390x (0.4.3-2 to 0.4.3-2)
  • Migration status for lusernet.app/s390x (0.4.3-2 to 0.4.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lusernet.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• mariadb_pu (1:11.4.4-3 to 1:10.11.9-0+deb12u1)
  • Migration status for mariadb_pu (1:11.4.4-3 to 1:10.11.9-0+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: mariadb is newer in the target suite (1:11.4.4-3 1:10.11.9-0+deb12u1)
• maxima-sage/amd64 (5.45.1-2 to 5.45.1-2)
  • Migration status for maxima-sage/amd64 (5.45.1-2 to 5.45.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: maxima-sage/amd64 ecl (not considered)
    • Invalidated by dependency
• maxima-sage/arm64 (5.45.1-2 to 5.45.1-2)
  • Migration status for maxima-sage/arm64 (5.45.1-2 to 5.45.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: maxima-sage/arm64 ecl (not considered)
    • Invalidated by dependency
• maxima-sage/armel (5.45.1-2 to 5.45.1-2)
  • Migration status for maxima-sage/armel (5.45.1-2 to 5.45.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: maxima-sage/armel ecl (not considered)
    • Invalidated by dependency
• maxima-sage/armhf (5.45.1-2 to 5.45.1-2)
  • Migration status for maxima-sage/armhf (5.45.1-2 to 5.45.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: maxima-sage/armhf ecl (not considered)
    • Invalidated by dependency
• maxima-sage/i386 (5.45.1-2 to 5.45.1-2)
  • Migration status for maxima-sage/i386 (5.45.1-2 to 5.45.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: maxima-sage/i386 ecl (not considered)
    • Invalidated by dependency
• maxima-sage/mips64el (5.45.1-2 to 5.45.1-2)
  • Migration status for maxima-sage/mips64el (5.45.1-2 to 5.45.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: maxima-sage/mips64el ecl (not considered)
    • Invalidated by dependency
• maxima-sage/ppc64el (5.45.1-2 to 5.45.1-2)
  • Migration status for maxima-sage/ppc64el (5.45.1-2 to 5.45.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: maxima-sage/ppc64el ecl (not considered)
    • Invalidated by dependency
• maxima-sage/riscv64 (5.45.1-2 to 5.45.1-2)
  • Migration status for maxima-sage/riscv64 (5.45.1-2 to 5.45.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: maxima-sage/riscv64 ecl (not considered)
    • Invalidated by dependency
• maxima-sage/s390x (5.45.1-2 to 5.45.1-2)
  • Migration status for maxima-sage/s390x (5.45.1-2 to 5.45.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: maxima-sage/s390x ecl (not considered)
    • Invalidated by dependency
• mdevctl/riscv64 (1.3.0-3 to 1.3.0-3)
  • Migration status for mdevctl/riscv64 (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
• mdevctl/s390x (1.3.0-3 to 1.3.0-3)
  • Migration status for mdevctl/s390x (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
• mecab/amd64 (0.996-15.1 to 0.996-15.1)
  • Migration status for mecab/amd64 (0.996-15.1 to 0.996-15.1): Will attempt migration (Any information below is purely informational)
• mecab/arm64 (0.996-15.1 to 0.996-15.1)
  • Migration status for mecab/arm64 (0.996-15.1 to 0.996-15.1): Will attempt migration (Any information below is purely informational)
• mecab/armel (0.996-15.1 to 0.996-15.1)
  • Migration status for mecab/armel (0.996-15.1 to 0.996-15.1): Will attempt migration (Any information below is purely informational)
• mecab/armhf (0.996-15.1 to 0.996-15.1)
  • Migration status for mecab/armhf (0.996-15.1 to 0.996-15.1): Will attempt migration (Any information below is purely informational)
• mecab/i386 (0.996-15.1 to 0.996-15.1)
  • Migration status for mecab/i386 (0.996-15.1 to 0.996-15.1): Will attempt migration (Any information below is purely informational)
• mecab/mips64el (0.996-15.1 to 0.996-15.1)
  • Migration status for mecab/mips64el (0.996-15.1 to 0.996-15.1): Will attempt migration (Any information below is purely informational)
• mecab/ppc64el (0.996-15.1 to 0.996-15.1)
  • Migration status for mecab/ppc64el (0.996-15.1 to 0.996-15.1): Will attempt migration (Any information below is purely informational)
• mecab/riscv64 (0.996-15.1 to 0.996-15.1)
  • Migration status for mecab/riscv64 (0.996-15.1 to 0.996-15.1): Will attempt migration (Any information below is purely informational)
• mecab/s390x (0.996-15.1 to 0.996-15.1)
  • Migration status for mecab/s390x (0.996-15.1 to 0.996-15.1): Will attempt migration (Any information below is purely informational)
• meli/arm64 (0.8.10+dfsg-2 to 0.8.10+dfsg-2)
  • Migration status for meli/arm64 (0.8.10+dfsg-2 to 0.8.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• meli/s390x (0.8.10+dfsg-2 to 0.8.10+dfsg-2)
  • Migration status for meli/s390x (0.8.10+dfsg-2 to 0.8.10+dfsg-2): Will attempt migration (Any information below is purely informational)
• mozc_pu (2.29.5160.102+dfsg-1.3 to 2.28.4715.102+dfsg-2.2+deb12u1)
  • Migration status for mozc_pu (2.29.5160.102+dfsg-1.3 to 2.28.4715.102+dfsg-2.2+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: mozc is newer in the target suite (2.29.5160.102+dfsg-1.3 2.28.4715.102+dfsg-2.2+deb12u1)
• mpd/s390x (0.23.16-1 to 0.23.16-1)
  • Migration status for mpd/s390x (0.23.16-1 to 0.23.16-1): Will attempt migration (Any information below is purely informational)
• mpdcon.app/amd64 (1.5.1-0.2 to 1.5.1-0.2)
  • Migration status for mpdcon.app/amd64 (1.5.1-0.2 to 1.5.1-0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mpdcon.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• mpdcon.app/arm64 (1.5.1-0.2 to 1.5.1-0.2)
  • Migration status for mpdcon.app/arm64 (1.5.1-0.2 to 1.5.1-0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mpdcon.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• mpdcon.app/armel (1.5.1-0.2 to 1.5.1-0.2)
  • Migration status for mpdcon.app/armel (1.5.1-0.2 to 1.5.1-0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mpdcon.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• mpdcon.app/armhf (1.5.1-0.2 to 1.5.1-0.2)
  • Migration status for mpdcon.app/armhf (1.5.1-0.2 to 1.5.1-0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mpdcon.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• mpdcon.app/i386 (1.5.1-0.2 to 1.5.1-0.2)
  • Migration status for mpdcon.app/i386 (1.5.1-0.2 to 1.5.1-0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mpdcon.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• mpdcon.app/mips64el (1.5.1-0.2 to 1.5.1-0.2)
  • Migration status for mpdcon.app/mips64el (1.5.1-0.2 to 1.5.1-0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mpdcon.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• mpdcon.app/ppc64el (1.5.1-0.2 to 1.5.1-0.2)
  • Migration status for mpdcon.app/ppc64el (1.5.1-0.2 to 1.5.1-0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mpdcon.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• mpdcon.app/riscv64 (1.5.1-0.2 to 1.5.1-0.2)
  • Migration status for mpdcon.app/riscv64 (1.5.1-0.2 to 1.5.1-0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mpdcon.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• mpdcon.app/s390x (1.5.1-0.2 to 1.5.1-0.2)
  • Migration status for mpdcon.app/s390x (1.5.1-0.2 to 1.5.1-0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mpdcon.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• ndcube_pu (2.3.0-1 to 2.0.3-1+deb12u1)
  • Migration status for ndcube_pu (2.3.0-1 to 2.0.3-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ndcube is newer in the target suite (2.3.0-1 2.0.3-1+deb12u1)
• node-axios_pu (1.7.9+dfsg-1 to 1.2.1+dfsg-1+deb12u1)
  • Migration status for node-axios_pu (1.7.9+dfsg-1 to 1.2.1+dfsg-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-axios is newer in the target suite (1.7.9+dfsg-1 1.2.1+dfsg-1+deb12u1)
• node-postcss_pu (8.4.49+~cs9.2.32-1 to 8.4.20+~cs8.0.23-1+deb12u1)
  • Migration status for node-postcss_pu (8.4.49+~cs9.2.32-1 to 8.4.20+~cs8.0.23-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-postcss is newer in the target suite (8.4.49+~cs9.2.32-1 8.4.20+~cs8.0.23-1+deb12u1)
• ntpsec/amd64 (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3)
  • Migration status for ntpsec/amd64 (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ntpsec/arm64 (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3)
  • Migration status for ntpsec/arm64 (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ntpsec/armel (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3)
  • Migration status for ntpsec/armel (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ntpsec/armhf (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3)
  • Migration status for ntpsec/armhf (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ntpsec/i386 (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3)
  • Migration status for ntpsec/i386 (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ntpsec/mips64el (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3)
  • Migration status for ntpsec/mips64el (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ntpsec/ppc64el (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3)
  • Migration status for ntpsec/ppc64el (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ntpsec/riscv64 (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3)
  • Migration status for ntpsec/riscv64 (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ntpsec/s390x (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3)
  • Migration status for ntpsec/s390x (1.2.3+dfsg1-3 to 1.2.3+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• oasis/amd64 (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/amd64 (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/amd64 findlib (not considered)
    • Invalidated by dependency
• oasis/arm64 (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/arm64 (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/arm64 findlib (not considered)
    • Invalidated by dependency
• oasis/armel (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/armel (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/armel findlib (not considered)
    • Invalidated by dependency
• oasis/armhf (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/armhf (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/armhf findlib (not considered)
    • Invalidated by dependency
• oasis/i386 (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/i386 (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/i386 findlib (not considered)
    • Invalidated by dependency
• oasis/mips64el (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/mips64el (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/mips64el findlib (not considered)
    • Invalidated by dependency
• oasis/ppc64el (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/ppc64el (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/ppc64el findlib (not considered)
    • Invalidated by dependency
• oasis/riscv64 (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/riscv64 (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/riscv64 findlib (not considered)
    • Invalidated by dependency
• ocp-indent/amd64 (1.8.2-5 to 1.8.2-5)
  • Migration status for ocp-indent/amd64 (1.8.2-5 to 1.8.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libocp-indent-ocaml/1.8.2-5+b4/amd64 to testing makes libocamlformat-ocaml/0.27.0-1+b3/amd64 uninstallable
    • migrating libocp-indent-ocaml-dev/1.8.2-5+b4/amd64 to testing makes libocamlformat-ocaml-dev/0.27.0-1+b3/amd64 uninstallable
    • Depends: ocp-indent/amd64 findlib (not considered)
• ocp-indent/arm64 (1.8.2-5 to 1.8.2-5)
  • Migration status for ocp-indent/arm64 (1.8.2-5 to 1.8.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libocp-indent-ocaml/1.8.2-5+b4/arm64 to testing makes libocamlformat-ocaml/0.27.0-1+b3/arm64 uninstallable
    • migrating libocp-indent-ocaml-dev/1.8.2-5+b4/arm64 to testing makes libocamlformat-ocaml-dev/0.27.0-1+b3/arm64 uninstallable
    • Depends: ocp-indent/arm64 findlib (not considered)
• ocp-indent/armel (1.8.2-5 to 1.8.2-5)
  • Migration status for ocp-indent/armel (1.8.2-5 to 1.8.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocp-indent/armel findlib (not considered)
    • Invalidated by dependency
• ocp-indent/armhf (1.8.2-5 to 1.8.2-5)
  • Migration status for ocp-indent/armhf (1.8.2-5 to 1.8.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocp-indent/armhf findlib (not considered)
    • Invalidated by dependency
• ocp-indent/i386 (1.8.2-5 to 1.8.2-5)
  • Migration status for ocp-indent/i386 (1.8.2-5 to 1.8.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocp-indent/i386 findlib (not considered)
    • Invalidated by dependency
• ocp-indent/mips64el (1.8.2-5 to 1.8.2-5)
  • Migration status for ocp-indent/mips64el (1.8.2-5 to 1.8.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocp-indent/mips64el findlib (not considered)
    • Invalidated by dependency
• ocp-indent/ppc64el (1.8.2-5 to 1.8.2-5)
  • Migration status for ocp-indent/ppc64el (1.8.2-5 to 1.8.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libocp-indent-ocaml/1.8.2-5+b4/ppc64el to testing makes libocamlformat-ocaml/0.27.0-1+b3/ppc64el uninstallable
    • migrating libocp-indent-ocaml-dev/1.8.2-5+b4/ppc64el to testing makes libocamlformat-ocaml-dev/0.27.0-1+b3/ppc64el uninstallable
    • Depends: ocp-indent/ppc64el findlib (not considered)
• ocp-indent/riscv64 (1.8.2-5 to 1.8.2-5)
  • Migration status for ocp-indent/riscv64 (1.8.2-5 to 1.8.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libocp-indent-ocaml/1.8.2-5+b5/riscv64 to testing makes libocamlformat-ocaml/0.27.0-1+b3/riscv64 uninstallable
    • migrating libocp-indent-ocaml-dev/1.8.2-5+b5/riscv64 to testing makes libocamlformat-ocaml-dev/0.27.0-1+b3/riscv64 uninstallable
    • Depends: ocp-indent/riscv64 findlib (not considered)
• openafs_pu (- to 1.8.9-1+deb12u1)
  • Migration status for openafs_pu (- to 1.8.9-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libafsauthent2/armel has unsatisfiable dependency
    • libafsrpc2/armel has unsatisfiable dependency
    • openafs-client/armel has unsatisfiable dependency
    • openafs-dbserver/armel has unsatisfiable dependency
    • openafs-fileserver/armel has unsatisfiable dependency
    • openafs-fuse/armel has unsatisfiable dependency
    • openafs-krb5/armel has unsatisfiable dependency
    • libafsauthent2/armhf has unsatisfiable dependency
    • libafsrpc2/armhf has unsatisfiable dependency
    • openafs-client/armhf has unsatisfiable dependency
    • openafs-dbserver/armhf has unsatisfiable dependency
    • openafs-fileserver/armhf has unsatisfiable dependency
    • openafs-fuse/armhf has unsatisfiable dependency
    • openafs-krb5/armhf has unsatisfiable dependency
    • NEEDS APPROVAL BY RM
• openjdk-17_pu (17.0.14+7-1 to 17.0.14+7-1~deb12u1)
  • Migration status for openjdk-17_pu (17.0.14+7-1 to 17.0.14+7-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: openjdk-17 is newer in the target suite (17.0.14+7-1 17.0.14+7-1~deb12u1)
• openjpeg2_pu (2.5.3-1 to 2.5.0-2+deb12u1)
  • Migration status for openjpeg2_pu (2.5.3-1 to 2.5.0-2+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: openjpeg2 is newer in the target suite (2.5.3-1 2.5.0-2+deb12u1)
• openstack-meta-packages/amd64 (0.35 to 0.35)
  • Migration status for openstack-meta-packages/amd64 (0.35 to 0.35): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-meta-packages/arm64 (0.35 to 0.35)
  • Migration status for openstack-meta-packages/arm64 (0.35 to 0.35): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-meta-packages/armel (0.35 to 0.35)
  • Migration status for openstack-meta-packages/armel (0.35 to 0.35): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-meta-packages/armhf (0.35 to 0.35)
  • Migration status for openstack-meta-packages/armhf (0.35 to 0.35): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-meta-packages/i386 (0.35 to 0.35)
  • Migration status for openstack-meta-packages/i386 (0.35 to 0.35): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-meta-packages/mips64el (0.35 to 0.35)
  • Migration status for openstack-meta-packages/mips64el (0.35 to 0.35): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-meta-packages/ppc64el (0.35 to 0.35)
  • Migration status for openstack-meta-packages/ppc64el (0.35 to 0.35): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-meta-packages/riscv64 (0.35 to 0.35)
  • Migration status for openstack-meta-packages/riscv64 (0.35 to 0.35): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openstack-meta-packages/s390x (0.35 to 0.35)
  • Migration status for openstack-meta-packages/s390x (0.35 to 0.35): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pam-u2f_pu (1.3.2-1 to 1.1.0-1.1+deb12u1)
  • Migration status for pam-u2f_pu (1.3.2-1 to 1.1.0-1.1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: pam-u2f is newer in the target suite (1.3.2-1 1.1.0-1.1+deb12u1)
• passenger/amd64 (6.0.24+ds-3 to 6.0.24+ds-3)
  • Migration status for passenger/amd64 (6.0.24+ds-3 to 6.0.24+ds-3): Will attempt migration (Any information below is purely informational)
• passenger/arm64 (6.0.24+ds-3 to 6.0.24+ds-3)
  • Migration status for passenger/arm64 (6.0.24+ds-3 to 6.0.24+ds-3): Will attempt migration (Any information below is purely informational)
• passenger/armel (6.0.24+ds-3 to 6.0.24+ds-3)
  • Migration status for passenger/armel (6.0.24+ds-3 to 6.0.24+ds-3): Will attempt migration (Any information below is purely informational)
• passenger/armhf (6.0.24+ds-3 to 6.0.24+ds-3)
  • Migration status for passenger/armhf (6.0.24+ds-3 to 6.0.24+ds-3): Will attempt migration (Any information below is purely informational)
• passenger/i386 (6.0.24+ds-3 to 6.0.24+ds-3)
  • Migration status for passenger/i386 (6.0.24+ds-3 to 6.0.24+ds-3): Will attempt migration (Any information below is purely informational)
• passenger/mips64el (6.0.24+ds-3 to 6.0.24+ds-3)
  • Migration status for passenger/mips64el (6.0.24+ds-3 to 6.0.24+ds-3): Will attempt migration (Any information below is purely informational)
• passenger/ppc64el (6.0.24+ds-3 to 6.0.24+ds-3)
  • Migration status for passenger/ppc64el (6.0.24+ds-3 to 6.0.24+ds-3): Will attempt migration (Any information below is purely informational)
• passenger/riscv64 (6.0.24+ds-3 to 6.0.24+ds-3)
  • Migration status for passenger/riscv64 (6.0.24+ds-3 to 6.0.24+ds-3): Will attempt migration (Any information below is purely informational)
• passenger/s390x (6.0.24+ds-3 to 6.0.24+ds-3)
  • Migration status for passenger/s390x (6.0.24+ds-3 to 6.0.24+ds-3): Will attempt migration (Any information below is purely informational)
• pdns-recursor_pu (5.1.3-1 to 4.8.8-1+deb12u1)
  • Migration status for pdns-recursor_pu (5.1.3-1 to 4.8.8-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: pdns-recursor is newer in the target suite (5.1.3-1 4.8.8-1+deb12u1)
• pendulum/amd64 (3.0.0-2 to 3.0.0-2)
  • Migration status for pendulum/amd64 (3.0.0-2 to 3.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pendulum/amd64 mimalloc (not considered)
    • Invalidated by dependency
• pendulum/armel (3.0.0-2 to 3.0.0-2)
  • Migration status for pendulum/armel (3.0.0-2 to 3.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pendulum/armel mimalloc (not considered)
    • Invalidated by dependency
• pendulum/armhf (3.0.0-2 to 3.0.0-2)
  • Migration status for pendulum/armhf (3.0.0-2 to 3.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pendulum/armhf mimalloc (not considered)
    • Invalidated by dependency
• pendulum/i386 (3.0.0-2 to 3.0.0-2)
  • Migration status for pendulum/i386 (3.0.0-2 to 3.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pendulum/i386 mimalloc (not considered)
    • Invalidated by dependency
• pendulum/mips64el (3.0.0-2 to 3.0.0-2)
  • Migration status for pendulum/mips64el (3.0.0-2 to 3.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pendulum/mips64el mimalloc (not considered)
    • Invalidated by dependency
• pendulum/ppc64el (3.0.0-2 to 3.0.0-2)
  • Migration status for pendulum/ppc64el (3.0.0-2 to 3.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pendulum/ppc64el mimalloc (not considered)
    • Invalidated by dependency
• pendulum/riscv64 (3.0.0-2 to 3.0.0-2)
  • Migration status for pendulum/riscv64 (3.0.0-2 to 3.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pendulum/riscv64 mimalloc (not considered)
    • Invalidated by dependency
• pendulum/s390x (3.0.0-2 to 3.0.0-2)
  • Migration status for pendulum/s390x (3.0.0-2 to 3.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pendulum/s390x mimalloc (not considered)
    • Invalidated by dependency
• phcpack/arm64 (2.4.90+dfsg-1 to 2.4.90+dfsg-1)
  • Migration status for phcpack/arm64 (2.4.90+dfsg-1 to 2.4.90+dfsg-1): Will attempt migration (Any information below is purely informational)
• phcpack/armel (2.4.90+dfsg-1 to 2.4.90+dfsg-1)
  • Migration status for phcpack/armel (2.4.90+dfsg-1 to 2.4.90+dfsg-1): Will attempt migration (Any information below is purely informational)
• phcpack/armhf (2.4.90+dfsg-1 to 2.4.90+dfsg-1)
  • Migration status for phcpack/armhf (2.4.90+dfsg-1 to 2.4.90+dfsg-1): Will attempt migration (Any information below is purely informational)
• phcpack/s390x (2.4.90+dfsg-1 to 2.4.90+dfsg-1)
  • Migration status for phcpack/s390x (2.4.90+dfsg-1 to 2.4.90+dfsg-1): Will attempt migration (Any information below is purely informational)
• pikopixel.app/amd64 (1.0-b10b-3 to 1.0-b10b-3)
  • Migration status for pikopixel.app/amd64 (1.0-b10b-3 to 1.0-b10b-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pikopixel.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• pikopixel.app/arm64 (1.0-b10b-3 to 1.0-b10b-3)
  • Migration status for pikopixel.app/arm64 (1.0-b10b-3 to 1.0-b10b-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pikopixel.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• pikopixel.app/armel (1.0-b10b-3 to 1.0-b10b-3)
  • Migration status for pikopixel.app/armel (1.0-b10b-3 to 1.0-b10b-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pikopixel.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• pikopixel.app/armhf (1.0-b10b-3 to 1.0-b10b-3)
  • Migration status for pikopixel.app/armhf (1.0-b10b-3 to 1.0-b10b-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pikopixel.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• pikopixel.app/i386 (1.0-b10b-3 to 1.0-b10b-3)
  • Migration status for pikopixel.app/i386 (1.0-b10b-3 to 1.0-b10b-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pikopixel.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• pikopixel.app/mips64el (1.0-b10b-3 to 1.0-b10b-3)
  • Migration status for pikopixel.app/mips64el (1.0-b10b-3 to 1.0-b10b-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pikopixel.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• pikopixel.app/ppc64el (1.0-b10b-3 to 1.0-b10b-3)
  • Migration status for pikopixel.app/ppc64el (1.0-b10b-3 to 1.0-b10b-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pikopixel.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• pikopixel.app/riscv64 (1.0-b10b-3 to 1.0-b10b-3)
  • Migration status for pikopixel.app/riscv64 (1.0-b10b-3 to 1.0-b10b-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pikopixel.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• pikopixel.app/s390x (1.0-b10b-3 to 1.0-b10b-3)
  • Migration status for pikopixel.app/s390x (1.0-b10b-3 to 1.0-b10b-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pikopixel.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• planets/amd64 (0.1.13-23 to 0.1.13-23)
  • Migration status for planets/amd64 (0.1.13-23 to 0.1.13-23): Will attempt migration (Any information below is purely informational)
• planets/arm64 (0.1.13-23 to 0.1.13-23)
  • Migration status for planets/arm64 (0.1.13-23 to 0.1.13-23): Will attempt migration (Any information below is purely informational)
• planets/armel (0.1.13-23 to 0.1.13-23)
  • Migration status for planets/armel (0.1.13-23 to 0.1.13-23): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: planets/armel labltk (not considered)
    • Invalidated by dependency
• planets/armhf (0.1.13-23 to 0.1.13-23)
  • Migration status for planets/armhf (0.1.13-23 to 0.1.13-23): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: planets/armhf labltk (not considered)
    • Invalidated by dependency
• planets/i386 (0.1.13-23 to 0.1.13-23)
  • Migration status for planets/i386 (0.1.13-23 to 0.1.13-23): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: planets/i386 labltk (not considered)
    • Invalidated by dependency
• planets/mips64el (0.1.13-23 to 0.1.13-23)
  • Migration status for planets/mips64el (0.1.13-23 to 0.1.13-23): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: planets/mips64el labltk (not considered)
    • Invalidated by dependency
• planets/ppc64el (0.1.13-23 to 0.1.13-23)
  • Migration status for planets/ppc64el (0.1.13-23 to 0.1.13-23): Will attempt migration (Any information below is purely informational)
• planets/riscv64 (0.1.13-23 to 0.1.13-23)
  • Migration status for planets/riscv64 (0.1.13-23 to 0.1.13-23): Will attempt migration (Any information below is purely informational)
• plastimatch/amd64 (1.9.4+dfsg.1-3 to 1.9.4+dfsg.1-3)
  • Migration status for plastimatch/amd64 (1.9.4+dfsg.1-3 to 1.9.4+dfsg.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: plastimatch/amd64 insighttoolkit5 (not considered)
    • Invalidated by dependency
• plopfolio.app/amd64 (0.1.0-9 to 0.1.0-9)
  • Migration status for plopfolio.app/amd64 (0.1.0-9 to 0.1.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: plopfolio.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• plopfolio.app/arm64 (0.1.0-9 to 0.1.0-9)
  • Migration status for plopfolio.app/arm64 (0.1.0-9 to 0.1.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: plopfolio.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• plopfolio.app/armel (0.1.0-9 to 0.1.0-9)
  • Migration status for plopfolio.app/armel (0.1.0-9 to 0.1.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: plopfolio.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• plopfolio.app/armhf (0.1.0-9 to 0.1.0-9)
  • Migration status for plopfolio.app/armhf (0.1.0-9 to 0.1.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: plopfolio.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• plopfolio.app/i386 (0.1.0-9 to 0.1.0-9)
  • Migration status for plopfolio.app/i386 (0.1.0-9 to 0.1.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: plopfolio.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• plopfolio.app/mips64el (0.1.0-9 to 0.1.0-9)
  • Migration status for plopfolio.app/mips64el (0.1.0-9 to 0.1.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: plopfolio.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• plopfolio.app/ppc64el (0.1.0-9 to 0.1.0-9)
  • Migration status for plopfolio.app/ppc64el (0.1.0-9 to 0.1.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: plopfolio.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• plopfolio.app/riscv64 (0.1.0-9 to 0.1.0-9)
  • Migration status for plopfolio.app/riscv64 (0.1.0-9 to 0.1.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: plopfolio.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• plopfolio.app/s390x (0.1.0-9 to 0.1.0-9)
  • Migration status for plopfolio.app/s390x (0.1.0-9 to 0.1.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: plopfolio.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• poe.app/amd64 (0.5.1-7 to 0.5.1-7)
  • Migration status for poe.app/amd64 (0.5.1-7 to 0.5.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: poe.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• poe.app/arm64 (0.5.1-7 to 0.5.1-7)
  • Migration status for poe.app/arm64 (0.5.1-7 to 0.5.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: poe.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• poe.app/armel (0.5.1-7 to 0.5.1-7)
  • Migration status for poe.app/armel (0.5.1-7 to 0.5.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: poe.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• poe.app/armhf (0.5.1-7 to 0.5.1-7)
  • Migration status for poe.app/armhf (0.5.1-7 to 0.5.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: poe.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• poe.app/i386 (0.5.1-7 to 0.5.1-7)
  • Migration status for poe.app/i386 (0.5.1-7 to 0.5.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: poe.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• poe.app/mips64el (0.5.1-7 to 0.5.1-7)
  • Migration status for poe.app/mips64el (0.5.1-7 to 0.5.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: poe.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• poe.app/ppc64el (0.5.1-7 to 0.5.1-7)
  • Migration status for poe.app/ppc64el (0.5.1-7 to 0.5.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: poe.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• poe.app/riscv64 (0.5.1-7 to 0.5.1-7)
  • Migration status for poe.app/riscv64 (0.5.1-7 to 0.5.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: poe.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• poe.app/s390x (0.5.1-7 to 0.5.1-7)
  • Migration status for poe.app/s390x (0.5.1-7 to 0.5.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: poe.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• popplerkit.framework/amd64 (0.0.20051227svn-13 to 0.0.20051227svn-13)
  • Migration status for popplerkit.framework/amd64 (0.0.20051227svn-13 to 0.0.20051227svn-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: popplerkit.framework/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• popplerkit.framework/arm64 (0.0.20051227svn-13 to 0.0.20051227svn-13)
  • Migration status for popplerkit.framework/arm64 (0.0.20051227svn-13 to 0.0.20051227svn-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: popplerkit.framework/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• popplerkit.framework/armel (0.0.20051227svn-13 to 0.0.20051227svn-13)
  • Migration status for popplerkit.framework/armel (0.0.20051227svn-13 to 0.0.20051227svn-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: popplerkit.framework/armel gnustep-make (not considered)
    • Invalidated by dependency
• popplerkit.framework/armhf (0.0.20051227svn-13 to 0.0.20051227svn-13)
  • Migration status for popplerkit.framework/armhf (0.0.20051227svn-13 to 0.0.20051227svn-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: popplerkit.framework/armhf gnustep-make (not considered)
    • Invalidated by dependency
• popplerkit.framework/i386 (0.0.20051227svn-13 to 0.0.20051227svn-13)
  • Migration status for popplerkit.framework/i386 (0.0.20051227svn-13 to 0.0.20051227svn-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: popplerkit.framework/i386 gnustep-make (not considered)
    • Invalidated by dependency
• popplerkit.framework/mips64el (0.0.20051227svn-13 to 0.0.20051227svn-13)
  • Migration status for popplerkit.framework/mips64el (0.0.20051227svn-13 to 0.0.20051227svn-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: popplerkit.framework/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• popplerkit.framework/ppc64el (0.0.20051227svn-13 to 0.0.20051227svn-13)
  • Migration status for popplerkit.framework/ppc64el (0.0.20051227svn-13 to 0.0.20051227svn-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: popplerkit.framework/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• popplerkit.framework/riscv64 (0.0.20051227svn-13 to 0.0.20051227svn-13)
  • Migration status for popplerkit.framework/riscv64 (0.0.20051227svn-13 to 0.0.20051227svn-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: popplerkit.framework/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• popplerkit.framework/s390x (0.0.20051227svn-13 to 0.0.20051227svn-13)
  • Migration status for popplerkit.framework/s390x (0.0.20051227svn-13 to 0.0.20051227svn-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: popplerkit.framework/s390x gnustep-make (not considered)
    • Invalidated by dependency
• precious/s390x (0.7.3-8 to 0.7.3-8)
  • Migration status for precious/s390x (0.7.3-8 to 0.7.3-8): Will attempt migration (Any information below is purely informational)
• preview.app/amd64 (0.8.5-12 to 0.8.5-12)
  • Migration status for preview.app/amd64 (0.8.5-12 to 0.8.5-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: preview.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• preview.app/arm64 (0.8.5-12 to 0.8.5-12)
  • Migration status for preview.app/arm64 (0.8.5-12 to 0.8.5-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: preview.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• preview.app/armel (0.8.5-12 to 0.8.5-12)
  • Migration status for preview.app/armel (0.8.5-12 to 0.8.5-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: preview.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• preview.app/armhf (0.8.5-12 to 0.8.5-12)
  • Migration status for preview.app/armhf (0.8.5-12 to 0.8.5-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: preview.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• preview.app/i386 (0.8.5-12 to 0.8.5-12)
  • Migration status for preview.app/i386 (0.8.5-12 to 0.8.5-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: preview.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• preview.app/mips64el (0.8.5-12 to 0.8.5-12)
  • Migration status for preview.app/mips64el (0.8.5-12 to 0.8.5-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: preview.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• preview.app/ppc64el (0.8.5-12 to 0.8.5-12)
  • Migration status for preview.app/ppc64el (0.8.5-12 to 0.8.5-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: preview.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• preview.app/riscv64 (0.8.5-12 to 0.8.5-12)
  • Migration status for preview.app/riscv64 (0.8.5-12 to 0.8.5-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: preview.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• preview.app/s390x (0.8.5-12 to 0.8.5-12)
  • Migration status for preview.app/s390x (0.8.5-12 to 0.8.5-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: preview.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• price.app/amd64 (1.3.0-6 to 1.3.0-6)
  • Migration status for price.app/amd64 (1.3.0-6 to 1.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: price.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• price.app/arm64 (1.3.0-6 to 1.3.0-6)
  • Migration status for price.app/arm64 (1.3.0-6 to 1.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: price.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• price.app/armel (1.3.0-6 to 1.3.0-6)
  • Migration status for price.app/armel (1.3.0-6 to 1.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: price.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• price.app/armhf (1.3.0-6 to 1.3.0-6)
  • Migration status for price.app/armhf (1.3.0-6 to 1.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: price.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• price.app/i386 (1.3.0-6 to 1.3.0-6)
  • Migration status for price.app/i386 (1.3.0-6 to 1.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: price.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• price.app/mips64el (1.3.0-6 to 1.3.0-6)
  • Migration status for price.app/mips64el (1.3.0-6 to 1.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: price.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• price.app/ppc64el (1.3.0-6 to 1.3.0-6)
  • Migration status for price.app/ppc64el (1.3.0-6 to 1.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: price.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• price.app/riscv64 (1.3.0-6 to 1.3.0-6)
  • Migration status for price.app/riscv64 (1.3.0-6 to 1.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: price.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• price.app/s390x (1.3.0-6 to 1.3.0-6)
  • Migration status for price.app/s390x (1.3.0-6 to 1.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: price.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• projectcenter.app/amd64 (0.7.0-2 to 0.7.0-2)
  • Migration status for projectcenter.app/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: projectcenter.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• projectcenter.app/arm64 (0.7.0-2 to 0.7.0-2)
  • Migration status for projectcenter.app/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: projectcenter.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• projectcenter.app/armel (0.7.0-2 to 0.7.0-2)
  • Migration status for projectcenter.app/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: projectcenter.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• projectcenter.app/armhf (0.7.0-2 to 0.7.0-2)
  • Migration status for projectcenter.app/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: projectcenter.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• projectcenter.app/i386 (0.7.0-2 to 0.7.0-2)
  • Migration status for projectcenter.app/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: projectcenter.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• projectcenter.app/mips64el (0.7.0-2 to 0.7.0-2)
  • Migration status for projectcenter.app/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: projectcenter.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• projectcenter.app/ppc64el (0.7.0-2 to 0.7.0-2)
  • Migration status for projectcenter.app/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: projectcenter.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• projectcenter.app/riscv64 (0.7.0-2 to 0.7.0-2)
  • Migration status for projectcenter.app/riscv64 (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: projectcenter.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• projectcenter.app/s390x (0.7.0-2 to 0.7.0-2)
  • Migration status for projectcenter.app/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: projectcenter.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• protobuf/amd64 (3.21.12-10 to 3.21.12-10)
  • Migration status for protobuf/amd64 (3.21.12-10 to 3.21.12-10): Will attempt migration (Any information below is purely informational)
• protobuf/arm64 (3.21.12-10 to 3.21.12-10)
  • Migration status for protobuf/arm64 (3.21.12-10 to 3.21.12-10): Will attempt migration (Any information below is purely informational)
• protobuf/armel (3.21.12-10 to 3.21.12-10)
  • Migration status for protobuf/armel (3.21.12-10 to 3.21.12-10): Will attempt migration (Any information below is purely informational)
• protobuf/armhf (3.21.12-10 to 3.21.12-10)
  • Migration status for protobuf/armhf (3.21.12-10 to 3.21.12-10): Will attempt migration (Any information below is purely informational)
• protobuf/i386 (3.21.12-10 to 3.21.12-10)
  • Migration status for protobuf/i386 (3.21.12-10 to 3.21.12-10): Will attempt migration (Any information below is purely informational)
• protobuf/mips64el (3.21.12-10 to 3.21.12-10)
  • Migration status for protobuf/mips64el (3.21.12-10 to 3.21.12-10): Will attempt migration (Any information below is purely informational)
• protobuf/ppc64el (3.21.12-10 to 3.21.12-10)
  • Migration status for protobuf/ppc64el (3.21.12-10 to 3.21.12-10): Will attempt migration (Any information below is purely informational)
• protobuf/riscv64 (3.21.12-10 to 3.21.12-10)
  • Migration status for protobuf/riscv64 (3.21.12-10 to 3.21.12-10): Will attempt migration (Any information below is purely informational)
• protobuf/s390x (3.21.12-10 to 3.21.12-10)
  • Migration status for protobuf/s390x (3.21.12-10 to 3.21.12-10): Will attempt migration (Any information below is purely informational)
• puma/amd64 (6.6.0-2 to 6.6.0-2)
  • Migration status for puma/amd64 (6.6.0-2 to 6.6.0-2): Will attempt migration (Any information below is purely informational)
• puma/arm64 (6.6.0-2 to 6.6.0-2)
  • Migration status for puma/arm64 (6.6.0-2 to 6.6.0-2): Will attempt migration (Any information below is purely informational)
• puma/armel (6.6.0-2 to 6.6.0-2)
  • Migration status for puma/armel (6.6.0-2 to 6.6.0-2): Will attempt migration (Any information below is purely informational)
• puma/i386 (6.6.0-2 to 6.6.0-2)
  • Migration status for puma/i386 (6.6.0-2 to 6.6.0-2): Will attempt migration (Any information below is purely informational)
• puma/mips64el (6.6.0-2 to 6.6.0-2)
  • Migration status for puma/mips64el (6.6.0-2 to 6.6.0-2): Will attempt migration (Any information below is purely informational)
• puma/ppc64el (6.6.0-2 to 6.6.0-2)
  • Migration status for puma/ppc64el (6.6.0-2 to 6.6.0-2): Will attempt migration (Any information below is purely informational)
• puma/riscv64 (6.6.0-2 to 6.6.0-2)
  • Migration status for puma/riscv64 (6.6.0-2 to 6.6.0-2): Will attempt migration (Any information below is purely informational)
• puma_pu (6.6.0-2 to 5.6.5-3+deb12u1)
  • Migration status for puma_pu (6.6.0-2 to 5.6.5-3+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: puma is newer in the target suite (6.6.0-2 5.6.5-3+deb12u1)
• pydantic-core/s390x (2.27.2-1 to 2.27.2-1)
  • Migration status for pydantic-core/s390x (2.27.2-1 to 2.27.2-1): Will attempt migration (Any information below is purely informational)
• pynauty/mips64el (2.8.8.1+ds-1 to 2.8.8.1+ds-1)
  • Migration status for pynauty/mips64el (2.8.8.1+ds-1 to 2.8.8.1+ds-1): Will attempt migration (Any information below is purely informational)
• pynauty/riscv64 (2.8.8.1+ds-1 to 2.8.8.1+ds-1)
  • Migration status for pynauty/riscv64 (2.8.8.1+ds-1 to 2.8.8.1+ds-1): Will attempt migration (Any information below is purely informational)
• pynauty/s390x (2.8.8.1+ds-1 to 2.8.8.1+ds-1)
  • Migration status for pynauty/s390x (2.8.8.1+ds-1 to 2.8.8.1+ds-1): Will attempt migration (Any information below is purely informational)
• python-django_pu (3:4.2.19-1 to 3:3.2.19-1+deb12u2)
  • Migration status for python-django_pu (3:4.2.19-1 to 3:3.2.19-1+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: python-django is newer in the target suite (3:4.2.19-1 3:3.2.19-1+deb12u2)
• python-pycdlib_pu (1.12.0+ds1-7 to 1.12.0+ds1-4+deb12u1)
  • Migration status for python-pycdlib_pu (1.12.0+ds1-7 to 1.12.0+ds1-4+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: python-pycdlib is newer in the target suite (1.12.0+ds1-7 1.12.0+ds1-4+deb12u1)
• qdbm/amd64 (1.8.78-13 to 1.8.78-13)
  • Migration status for qdbm/amd64 (1.8.78-13 to 1.8.78-13): Will attempt migration (Any information below is purely informational)
• qdbm/arm64 (1.8.78-13 to 1.8.78-13)
  • Migration status for qdbm/arm64 (1.8.78-13 to 1.8.78-13): Will attempt migration (Any information below is purely informational)
• qdbm/armel (1.8.78-13 to 1.8.78-13)
  • Migration status for qdbm/armel (1.8.78-13 to 1.8.78-13): Will attempt migration (Any information below is purely informational)
• qdbm/armhf (1.8.78-13 to 1.8.78-13)
  • Migration status for qdbm/armhf (1.8.78-13 to 1.8.78-13): Will attempt migration (Any information below is purely informational)
• qdbm/i386 (1.8.78-13 to 1.8.78-13)
  • Migration status for qdbm/i386 (1.8.78-13 to 1.8.78-13): Will attempt migration (Any information below is purely informational)
• qdbm/mips64el (1.8.78-13 to 1.8.78-13)
  • Migration status for qdbm/mips64el (1.8.78-13 to 1.8.78-13): Will attempt migration (Any information below is purely informational)
• qdbm/ppc64el (1.8.78-13 to 1.8.78-13)
  • Migration status for qdbm/ppc64el (1.8.78-13 to 1.8.78-13): Will attempt migration (Any information below is purely informational)
• qdbm/riscv64 (1.8.78-13 to 1.8.78-13)
  • Migration status for qdbm/riscv64 (1.8.78-13 to 1.8.78-13): Will attempt migration (Any information below is purely informational)
• qdbm/s390x (1.8.78-13 to 1.8.78-13)
  • Migration status for qdbm/s390x (1.8.78-13 to 1.8.78-13): Will attempt migration (Any information below is purely informational)
• qtwebview-opensource-src/amd64 (5.15.15-2 to 5.15.15-2)
  • Migration status for qtwebview-opensource-src/amd64 (5.15.15-2 to 5.15.15-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: qtwebview-opensource-src/amd64 qtwebengine-opensource-src (not considered)
    • Invalidated by dependency
• qtwebview-opensource-src/arm64 (5.15.15-2 to 5.15.15-2)
  • Migration status for qtwebview-opensource-src/arm64 (5.15.15-2 to 5.15.15-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: qtwebview-opensource-src/arm64 qtwebengine-opensource-src (not considered)
    • Invalidated by dependency
• qtwebview-opensource-src/armhf (5.15.15-2 to 5.15.15-2)
  • Migration status for qtwebview-opensource-src/armhf (5.15.15-2 to 5.15.15-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: qtwebview-opensource-src/armhf qtwebengine-opensource-src (not considered)
    • Invalidated by dependency
• qtwebview-opensource-src/i386 (5.15.15-2 to 5.15.15-2)
  • Migration status for qtwebview-opensource-src/i386 (5.15.15-2 to 5.15.15-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: qtwebview-opensource-src/i386 qtwebengine-opensource-src (not considered)
    • Invalidated by dependency
• qtwebview-opensource-src/mips64el (5.15.15-2 to 5.15.15-2)
  • Migration status for qtwebview-opensource-src/mips64el (5.15.15-2 to 5.15.15-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: qtwebview-opensource-src/mips64el qtwebengine-opensource-src (not considered)
    • Invalidated by dependency
• qwertone/riscv64 (0.4.0-2 to 0.4.0-2)
  • Migration status for qwertone/riscv64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• qwertone/s390x (0.4.0-2 to 0.4.0-2)
  • Migration status for qwertone/s390x (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• rapiddisk_pu (9.1.0-5 to 9.0.0-1+deb12u1)
  • Migration status for rapiddisk_pu (9.1.0-5 to 9.0.0-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: rapiddisk is newer in the target suite (9.1.0-5 9.0.0-1+deb12u1)
• redis_pu (5:7.0.15-3 to 5:7.0.15-1~deb12u3)
  • Migration status for redis_pu (5:7.0.15-3 to 5:7.0.15-1~deb12u3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: redis is newer in the target suite (5:7.0.15-3 5:7.0.15-1~deb12u3)
• remctl/amd64 (3.18-2 to 3.18-2)
  • Migration status for remctl/amd64 (3.18-2 to 3.18-2): Will attempt migration (Any information below is purely informational)
• remctl/arm64 (3.18-2 to 3.18-2)
  • Migration status for remctl/arm64 (3.18-2 to 3.18-2): Will attempt migration (Any information below is purely informational)
• remctl/armel (3.18-2 to 3.18-2)
  • Migration status for remctl/armel (3.18-2 to 3.18-2): Will attempt migration (Any information below is purely informational)
• remctl/armhf (3.18-2 to 3.18-2)
  • Migration status for remctl/armhf (3.18-2 to 3.18-2): Will attempt migration (Any information below is purely informational)
• remctl/i386 (3.18-2 to 3.18-2)
  • Migration status for remctl/i386 (3.18-2 to 3.18-2): Will attempt migration (Any information below is purely informational)
• remctl/mips64el (3.18-2 to 3.18-2)
  • Migration status for remctl/mips64el (3.18-2 to 3.18-2): Will attempt migration (Any information below is purely informational)
• remctl/ppc64el (3.18-2 to 3.18-2)
  • Migration status for remctl/ppc64el (3.18-2 to 3.18-2): Will attempt migration (Any information below is purely informational)
• remctl/riscv64 (3.18-2 to 3.18-2)
  • Migration status for remctl/riscv64 (3.18-2 to 3.18-2): Will attempt migration (Any information below is purely informational)
• remctl/s390x (3.18-2 to 3.18-2)
  • Migration status for remctl/s390x (3.18-2 to 3.18-2): Will attempt migration (Any information below is purely informational)
• renaissance/amd64 (0.9.0-4.3 to 0.9.0-4.3)
  • Migration status for renaissance/amd64 (0.9.0-4.3 to 0.9.0-4.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: renaissance/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• renaissance/arm64 (0.9.0-4.3 to 0.9.0-4.3)
  • Migration status for renaissance/arm64 (0.9.0-4.3 to 0.9.0-4.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: renaissance/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• renaissance/armel (0.9.0-4.3 to 0.9.0-4.3)
  • Migration status for renaissance/armel (0.9.0-4.3 to 0.9.0-4.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: renaissance/armel gnustep-make (not considered)
    • Invalidated by dependency
• renaissance/armhf (0.9.0-4.3 to 0.9.0-4.3)
  • Migration status for renaissance/armhf (0.9.0-4.3 to 0.9.0-4.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: renaissance/armhf gnustep-make (not considered)
    • Invalidated by dependency
• renaissance/i386 (0.9.0-4.3 to 0.9.0-4.3)
  • Migration status for renaissance/i386 (0.9.0-4.3 to 0.9.0-4.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: renaissance/i386 gnustep-make (not considered)
    • Invalidated by dependency
• renaissance/mips64el (0.9.0-4.3 to 0.9.0-4.3)
  • Migration status for renaissance/mips64el (0.9.0-4.3 to 0.9.0-4.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: renaissance/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• renaissance/ppc64el (0.9.0-4.3 to 0.9.0-4.3)
  • Migration status for renaissance/ppc64el (0.9.0-4.3 to 0.9.0-4.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: renaissance/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• renaissance/riscv64 (0.9.0-4.3 to 0.9.0-4.3)
  • Migration status for renaissance/riscv64 (0.9.0-4.3 to 0.9.0-4.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: renaissance/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• renaissance/s390x (0.9.0-4.3 to 0.9.0-4.3)
  • Migration status for renaissance/s390x (0.9.0-4.3 to 0.9.0-4.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: renaissance/s390x gnustep-make (not considered)
    • Invalidated by dependency
• rrdtool/amd64 (1.7.2-4.2 to 1.7.2-4.2)
  • Migration status for rrdtool/amd64 (1.7.2-4.2 to 1.7.2-4.2): Will attempt migration (Any information below is purely informational)
• rrdtool/arm64 (1.7.2-4.2 to 1.7.2-4.2)
  • Migration status for rrdtool/arm64 (1.7.2-4.2 to 1.7.2-4.2): Will attempt migration (Any information below is purely informational)
• rrdtool/armel (1.7.2-4.2 to 1.7.2-4.2)
  • Migration status for rrdtool/armel (1.7.2-4.2 to 1.7.2-4.2): Will attempt migration (Any information below is purely informational)
• rrdtool/armhf (1.7.2-4.2 to 1.7.2-4.2)
  • Migration status for rrdtool/armhf (1.7.2-4.2 to 1.7.2-4.2): Will attempt migration (Any information below is purely informational)
• rrdtool/i386 (1.7.2-4.2 to 1.7.2-4.2)
  • Migration status for rrdtool/i386 (1.7.2-4.2 to 1.7.2-4.2): Will attempt migration (Any information below is purely informational)
• rrdtool/mips64el (1.7.2-4.2 to 1.7.2-4.2)
  • Migration status for rrdtool/mips64el (1.7.2-4.2 to 1.7.2-4.2): Will attempt migration (Any information below is purely informational)
• rrdtool/ppc64el (1.7.2-4.2 to 1.7.2-4.2)
  • Migration status for rrdtool/ppc64el (1.7.2-4.2 to 1.7.2-4.2): Will attempt migration (Any information below is purely informational)
• rrdtool/riscv64 (1.7.2-4.2 to 1.7.2-4.2)
  • Migration status for rrdtool/riscv64 (1.7.2-4.2 to 1.7.2-4.2): Will attempt migration (Any information below is purely informational)
• rrdtool/s390x (1.7.2-4.2 to 1.7.2-4.2)
  • Migration status for rrdtool/s390x (1.7.2-4.2 to 1.7.2-4.2): Will attempt migration (Any information below is purely informational)
• rsync_pu (3.3.0+ds1-4 to 3.2.7-1+deb12u2)
  • Migration status for rsync_pu (3.3.0+ds1-4 to 3.2.7-1+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: rsync is newer in the target suite (3.3.0+ds1-4 3.2.7-1+deb12u2)
• rsyslog_pu (8.2412.0-1 to 8.2302.0-1+deb12u1)
  • Migration status for rsyslog_pu (8.2412.0-1 to 8.2302.0-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: rsyslog is newer in the target suite (8.2412.0-1 8.2302.0-1+deb12u1)
• ruby-aliyun-sdk/amd64 (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-aliyun-sdk/amd64 (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-aliyun-sdk/arm64 (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-aliyun-sdk/arm64 (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-aliyun-sdk/armel (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-aliyun-sdk/armel (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-aliyun-sdk/i386 (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-aliyun-sdk/i386 (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-aliyun-sdk/mips64el (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-aliyun-sdk/mips64el (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-aliyun-sdk/ppc64el (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-aliyun-sdk/ppc64el (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-aliyun-sdk/riscv64 (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-aliyun-sdk/riscv64 (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-atomic/amd64 (1.1.101-1 to 1.1.101-1)
  • Migration status for ruby-atomic/amd64 (1.1.101-1 to 1.1.101-1): Will attempt migration (Any information below is purely informational)
• ruby-atomic/arm64 (1.1.101-1 to 1.1.101-1)
  • Migration status for ruby-atomic/arm64 (1.1.101-1 to 1.1.101-1): Will attempt migration (Any information below is purely informational)
• ruby-atomic/armel (1.1.101-1 to 1.1.101-1)
  • Migration status for ruby-atomic/armel (1.1.101-1 to 1.1.101-1): Will attempt migration (Any information below is purely informational)
• ruby-atomic/armhf (1.1.101-1 to 1.1.101-1)
  • Migration status for ruby-atomic/armhf (1.1.101-1 to 1.1.101-1): Will attempt migration (Any information below is purely informational)
• ruby-atomic/i386 (1.1.101-1 to 1.1.101-1)
  • Migration status for ruby-atomic/i386 (1.1.101-1 to 1.1.101-1): Will attempt migration (Any information below is purely informational)
• ruby-atomic/mips64el (1.1.101-1 to 1.1.101-1)
  • Migration status for ruby-atomic/mips64el (1.1.101-1 to 1.1.101-1): Will attempt migration (Any information below is purely informational)
• ruby-atomic/ppc64el (1.1.101-1 to 1.1.101-1)
  • Migration status for ruby-atomic/ppc64el (1.1.101-1 to 1.1.101-1): Will attempt migration (Any information below is purely informational)
• ruby-atomic/riscv64 (1.1.101-1 to 1.1.101-1)
  • Migration status for ruby-atomic/riscv64 (1.1.101-1 to 1.1.101-1): Will attempt migration (Any information below is purely informational)
• ruby-atomic/s390x (1.1.101-1 to 1.1.101-1)
  • Migration status for ruby-atomic/s390x (1.1.101-1 to 1.1.101-1): Will attempt migration (Any information below is purely informational)
• ruby-augeas/amd64 (1:0.5.0+gem-2 to 1:0.5.0+gem-2)
  • Migration status for ruby-augeas/amd64 (1:0.5.0+gem-2 to 1:0.5.0+gem-2): Will attempt migration (Any information below is purely informational)
• ruby-augeas/arm64 (1:0.5.0+gem-2 to 1:0.5.0+gem-2)
  • Migration status for ruby-augeas/arm64 (1:0.5.0+gem-2 to 1:0.5.0+gem-2): Will attempt migration (Any information below is purely informational)
• ruby-augeas/armel (1:0.5.0+gem-2 to 1:0.5.0+gem-2)
  • Migration status for ruby-augeas/armel (1:0.5.0+gem-2 to 1:0.5.0+gem-2): Will attempt migration (Any information below is purely informational)
• ruby-augeas/armhf (1:0.5.0+gem-2 to 1:0.5.0+gem-2)
  • Migration status for ruby-augeas/armhf (1:0.5.0+gem-2 to 1:0.5.0+gem-2): Will attempt migration (Any information below is purely informational)
• ruby-augeas/i386 (1:0.5.0+gem-2 to 1:0.5.0+gem-2)
  • Migration status for ruby-augeas/i386 (1:0.5.0+gem-2 to 1:0.5.0+gem-2): Will attempt migration (Any information below is purely informational)
• ruby-augeas/mips64el (1:0.5.0+gem-2 to 1:0.5.0+gem-2)
  • Migration status for ruby-augeas/mips64el (1:0.5.0+gem-2 to 1:0.5.0+gem-2): Will attempt migration (Any information below is purely informational)
• ruby-augeas/ppc64el (1:0.5.0+gem-2 to 1:0.5.0+gem-2)
  • Migration status for ruby-augeas/ppc64el (1:0.5.0+gem-2 to 1:0.5.0+gem-2): Will attempt migration (Any information below is purely informational)
• ruby-augeas/riscv64 (1:0.5.0+gem-2 to 1:0.5.0+gem-2)
  • Migration status for ruby-augeas/riscv64 (1:0.5.0+gem-2 to 1:0.5.0+gem-2): Will attempt migration (Any information below is purely informational)
• ruby-augeas/s390x (1:0.5.0+gem-2 to 1:0.5.0+gem-2)
  • Migration status for ruby-augeas/s390x (1:0.5.0+gem-2 to 1:0.5.0+gem-2): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt-pbkdf/amd64 (1.1.1-1 to 1.1.1-1)
  • Migration status for ruby-bcrypt-pbkdf/amd64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt-pbkdf/arm64 (1.1.1-1 to 1.1.1-1)
  • Migration status for ruby-bcrypt-pbkdf/arm64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt-pbkdf/armel (1.1.1-1 to 1.1.1-1)
  • Migration status for ruby-bcrypt-pbkdf/armel (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt-pbkdf/armhf (1.1.1-1 to 1.1.1-1)
  • Migration status for ruby-bcrypt-pbkdf/armhf (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt-pbkdf/i386 (1.1.1-1 to 1.1.1-1)
  • Migration status for ruby-bcrypt-pbkdf/i386 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt-pbkdf/mips64el (1.1.1-1 to 1.1.1-1)
  • Migration status for ruby-bcrypt-pbkdf/mips64el (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt-pbkdf/ppc64el (1.1.1-1 to 1.1.1-1)
  • Migration status for ruby-bcrypt-pbkdf/ppc64el (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt-pbkdf/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for ruby-bcrypt-pbkdf/riscv64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt-pbkdf/s390x (1.1.1-1 to 1.1.1-1)
  • Migration status for ruby-bcrypt-pbkdf/s390x (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt/amd64 (3.1.20-1 to 3.1.20-1)
  • Migration status for ruby-bcrypt/amd64 (3.1.20-1 to 3.1.20-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt/arm64 (3.1.20-1 to 3.1.20-1)
  • Migration status for ruby-bcrypt/arm64 (3.1.20-1 to 3.1.20-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt/armel (3.1.20-1 to 3.1.20-1)
  • Migration status for ruby-bcrypt/armel (3.1.20-1 to 3.1.20-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt/armhf (3.1.20-1 to 3.1.20-1)
  • Migration status for ruby-bcrypt/armhf (3.1.20-1 to 3.1.20-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt/i386 (3.1.20-1 to 3.1.20-1)
  • Migration status for ruby-bcrypt/i386 (3.1.20-1 to 3.1.20-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt/mips64el (3.1.20-1 to 3.1.20-1)
  • Migration status for ruby-bcrypt/mips64el (3.1.20-1 to 3.1.20-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt/ppc64el (3.1.20-1 to 3.1.20-1)
  • Migration status for ruby-bcrypt/ppc64el (3.1.20-1 to 3.1.20-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt/riscv64 (3.1.20-1 to 3.1.20-1)
  • Migration status for ruby-bcrypt/riscv64 (3.1.20-1 to 3.1.20-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt/s390x (3.1.20-1 to 3.1.20-1)
  • Migration status for ruby-bcrypt/s390x (3.1.20-1 to 3.1.20-1): Will attempt migration (Any information below is purely informational)
• ruby-bert/amd64 (1.1.6-3 to 1.1.6-3)
  • Migration status for ruby-bert/amd64 (1.1.6-3 to 1.1.6-3): Will attempt migration (Any information below is purely informational)
• ruby-bert/arm64 (1.1.6-3 to 1.1.6-3)
  • Migration status for ruby-bert/arm64 (1.1.6-3 to 1.1.6-3): Will attempt migration (Any information below is purely informational)
• ruby-bert/armel (1.1.6-3 to 1.1.6-3)
  • Migration status for ruby-bert/armel (1.1.6-3 to 1.1.6-3): Will attempt migration (Any information below is purely informational)
• ruby-bert/armhf (1.1.6-3 to 1.1.6-3)
  • Migration status for ruby-bert/armhf (1.1.6-3 to 1.1.6-3): Will attempt migration (Any information below is purely informational)
• ruby-bert/i386 (1.1.6-3 to 1.1.6-3)
  • Migration status for ruby-bert/i386 (1.1.6-3 to 1.1.6-3): Will attempt migration (Any information below is purely informational)
• ruby-bert/mips64el (1.1.6-3 to 1.1.6-3)
  • Migration status for ruby-bert/mips64el (1.1.6-3 to 1.1.6-3): Will attempt migration (Any information below is purely informational)
• ruby-bert/ppc64el (1.1.6-3 to 1.1.6-3)
  • Migration status for ruby-bert/ppc64el (1.1.6-3 to 1.1.6-3): Will attempt migration (Any information below is purely informational)
• ruby-bert/riscv64 (1.1.6-3 to 1.1.6-3)
  • Migration status for ruby-bert/riscv64 (1.1.6-3 to 1.1.6-3): Will attempt migration (Any information below is purely informational)
• ruby-bert/s390x (1.1.6-3 to 1.1.6-3)
  • Migration status for ruby-bert/s390x (1.1.6-3 to 1.1.6-3): Will attempt migration (Any information below is purely informational)
• ruby-bindex/amd64 (0.8.1+ds-2 to 0.8.1+ds-2)
  • Migration status for ruby-bindex/amd64 (0.8.1+ds-2 to 0.8.1+ds-2): Will attempt migration (Any information below is purely informational)
• ruby-bindex/arm64 (0.8.1+ds-2 to 0.8.1+ds-2)
  • Migration status for ruby-bindex/arm64 (0.8.1+ds-2 to 0.8.1+ds-2): Will attempt migration (Any information below is purely informational)
• ruby-bindex/armel (0.8.1+ds-2 to 0.8.1+ds-2)
  • Migration status for ruby-bindex/armel (0.8.1+ds-2 to 0.8.1+ds-2): Will attempt migration (Any information below is purely informational)
• ruby-bindex/armhf (0.8.1+ds-2 to 0.8.1+ds-2)
  • Migration status for ruby-bindex/armhf (0.8.1+ds-2 to 0.8.1+ds-2): Will attempt migration (Any information below is purely informational)
• ruby-bindex/i386 (0.8.1+ds-2 to 0.8.1+ds-2)
  • Migration status for ruby-bindex/i386 (0.8.1+ds-2 to 0.8.1+ds-2): Will attempt migration (Any information below is purely informational)
• ruby-bindex/mips64el (0.8.1+ds-2 to 0.8.1+ds-2)
  • Migration status for ruby-bindex/mips64el (0.8.1+ds-2 to 0.8.1+ds-2): Will attempt migration (Any information below is purely informational)
• ruby-bindex/ppc64el (0.8.1+ds-2 to 0.8.1+ds-2)
  • Migration status for ruby-bindex/ppc64el (0.8.1+ds-2 to 0.8.1+ds-2): Will attempt migration (Any information below is purely informational)
• ruby-bindex/riscv64 (0.8.1+ds-2 to 0.8.1+ds-2)
  • Migration status for ruby-bindex/riscv64 (0.8.1+ds-2 to 0.8.1+ds-2): Will attempt migration (Any information below is purely informational)
• ruby-bindex/s390x (0.8.1+ds-2 to 0.8.1+ds-2)
  • Migration status for ruby-bindex/s390x (0.8.1+ds-2 to 0.8.1+ds-2): Will attempt migration (Any information below is purely informational)
• ruby-binding-ninja/amd64 (0.2.3-2 to 0.2.3-2)
  • Migration status for ruby-binding-ninja/amd64 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-binding-ninja/arm64 (0.2.3-2 to 0.2.3-2)
  • Migration status for ruby-binding-ninja/arm64 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-binding-ninja/armel (0.2.3-2 to 0.2.3-2)
  • Migration status for ruby-binding-ninja/armel (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-binding-ninja/armhf (0.2.3-2 to 0.2.3-2)
  • Migration status for ruby-binding-ninja/armhf (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-binding-ninja/i386 (0.2.3-2 to 0.2.3-2)
  • Migration status for ruby-binding-ninja/i386 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-binding-ninja/mips64el (0.2.3-2 to 0.2.3-2)
  • Migration status for ruby-binding-ninja/mips64el (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-binding-ninja/ppc64el (0.2.3-2 to 0.2.3-2)
  • Migration status for ruby-binding-ninja/ppc64el (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-binding-ninja/riscv64 (0.2.3-2 to 0.2.3-2)
  • Migration status for ruby-binding-ninja/riscv64 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-binding-ninja/s390x (0.2.3-2 to 0.2.3-2)
  • Migration status for ruby-binding-ninja/s390x (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-bootsnap/amd64 (1.18.4-1 to 1.18.4-1)
  • Migration status for ruby-bootsnap/amd64 (1.18.4-1 to 1.18.4-1): Will attempt migration (Any information below is purely informational)
• ruby-bootsnap/arm64 (1.18.4-1 to 1.18.4-1)
  • Migration status for ruby-bootsnap/arm64 (1.18.4-1 to 1.18.4-1): Will attempt migration (Any information below is purely informational)
• ruby-bootsnap/armel (1.18.4-1 to 1.18.4-1)
  • Migration status for ruby-bootsnap/armel (1.18.4-1 to 1.18.4-1): Will attempt migration (Any information below is purely informational)
• ruby-bootsnap/i386 (1.18.4-1 to 1.18.4-1)
  • Migration status for ruby-bootsnap/i386 (1.18.4-1 to 1.18.4-1): Will attempt migration (Any information below is purely informational)
• ruby-bootsnap/mips64el (1.18.4-1 to 1.18.4-1)
  • Migration status for ruby-bootsnap/mips64el (1.18.4-1 to 1.18.4-1): Will attempt migration (Any information below is purely informational)
• ruby-bootsnap/ppc64el (1.18.4-1 to 1.18.4-1)
  • Migration status for ruby-bootsnap/ppc64el (1.18.4-1 to 1.18.4-1): Will attempt migration (Any information below is purely informational)
• ruby-bootsnap/riscv64 (1.18.4-1 to 1.18.4-1)
  • Migration status for ruby-bootsnap/riscv64 (1.18.4-1 to 1.18.4-1): Will attempt migration (Any information below is purely informational)
• ruby-bson/amd64 (4.15.0-1 to 4.15.0-1)
  • Migration status for ruby-bson/amd64 (4.15.0-1 to 4.15.0-1): Will attempt migration (Any information below is purely informational)
• ruby-bson/arm64 (4.15.0-1 to 4.15.0-1)
  • Migration status for ruby-bson/arm64 (4.15.0-1 to 4.15.0-1): Will attempt migration (Any information below is purely informational)
• ruby-bson/armel (4.15.0-1 to 4.15.0-1)
  • Migration status for ruby-bson/armel (4.15.0-1 to 4.15.0-1): Will attempt migration (Any information below is purely informational)
• ruby-bson/i386 (4.15.0-1 to 4.15.0-1)
  • Migration status for ruby-bson/i386 (4.15.0-1 to 4.15.0-1): Will attempt migration (Any information below is purely informational)
• ruby-bson/mips64el (4.15.0-1 to 4.15.0-1)
  • Migration status for ruby-bson/mips64el (4.15.0-1 to 4.15.0-1): Will attempt migration (Any information below is purely informational)
• ruby-bson/ppc64el (4.15.0-1 to 4.15.0-1)
  • Migration status for ruby-bson/ppc64el (4.15.0-1 to 4.15.0-1): Will attempt migration (Any information below is purely informational)
• ruby-bson/riscv64 (4.15.0-1 to 4.15.0-1)
  • Migration status for ruby-bson/riscv64 (4.15.0-1 to 4.15.0-1): Will attempt migration (Any information below is purely informational)
• ruby-byebug/amd64 (11.1.3-5 to 11.1.3-5)
  • Migration status for ruby-byebug/amd64 (11.1.3-5 to 11.1.3-5): Will attempt migration (Any information below is purely informational)
• ruby-byebug/arm64 (11.1.3-5 to 11.1.3-5)
  • Migration status for ruby-byebug/arm64 (11.1.3-5 to 11.1.3-5): Will attempt migration (Any information below is purely informational)
• ruby-byebug/armel (11.1.3-5 to 11.1.3-5)
  • Migration status for ruby-byebug/armel (11.1.3-5 to 11.1.3-5): Will attempt migration (Any information below is purely informational)
• ruby-byebug/armhf (11.1.3-5 to 11.1.3-5)
  • Migration status for ruby-byebug/armhf (11.1.3-5 to 11.1.3-5): Will attempt migration (Any information below is purely informational)
• ruby-byebug/i386 (11.1.3-5 to 11.1.3-5)
  • Migration status for ruby-byebug/i386 (11.1.3-5 to 11.1.3-5): Will attempt migration (Any information below is purely informational)
• ruby-byebug/mips64el (11.1.3-5 to 11.1.3-5)
  • Migration status for ruby-byebug/mips64el (11.1.3-5 to 11.1.3-5): Will attempt migration (Any information below is purely informational)
• ruby-byebug/ppc64el (11.1.3-5 to 11.1.3-5)
  • Migration status for ruby-byebug/ppc64el (11.1.3-5 to 11.1.3-5): Will attempt migration (Any information below is purely informational)
• ruby-byebug/riscv64 (11.1.3-5 to 11.1.3-5)
  • Migration status for ruby-byebug/riscv64 (11.1.3-5 to 11.1.3-5): Will attempt migration (Any information below is purely informational)
• ruby-byebug/s390x (11.1.3-5 to 11.1.3-5)
  • Migration status for ruby-byebug/s390x (11.1.3-5 to 11.1.3-5): Will attempt migration (Any information below is purely informational)
• ruby-cairo/amd64 (1.17.13-1 to 1.17.13-1)
  • Migration status for ruby-cairo/amd64 (1.17.13-1 to 1.17.13-1): Will attempt migration (Any information below is purely informational)
• ruby-cairo/arm64 (1.17.13-1 to 1.17.13-1)
  • Migration status for ruby-cairo/arm64 (1.17.13-1 to 1.17.13-1): Will attempt migration (Any information below is purely informational)
• ruby-cairo/armel (1.17.13-1 to 1.17.13-1)
  • Migration status for ruby-cairo/armel (1.17.13-1 to 1.17.13-1): Will attempt migration (Any information below is purely informational)
• ruby-cairo/armhf (1.17.13-1 to 1.17.13-1)
  • Migration status for ruby-cairo/armhf (1.17.13-1 to 1.17.13-1): Will attempt migration (Any information below is purely informational)
• ruby-cairo/i386 (1.17.13-1 to 1.17.13-1)
  • Migration status for ruby-cairo/i386 (1.17.13-1 to 1.17.13-1): Will attempt migration (Any information below is purely informational)
• ruby-cairo/mips64el (1.17.13-1 to 1.17.13-1)
  • Migration status for ruby-cairo/mips64el (1.17.13-1 to 1.17.13-1): Will attempt migration (Any information below is purely informational)
• ruby-cairo/ppc64el (1.17.13-1 to 1.17.13-1)
  • Migration status for ruby-cairo/ppc64el (1.17.13-1 to 1.17.13-1): Will attempt migration (Any information below is purely informational)
• ruby-cairo/riscv64 (1.17.13-1 to 1.17.13-1)
  • Migration status for ruby-cairo/riscv64 (1.17.13-1 to 1.17.13-1): Will attempt migration (Any information below is purely informational)
• ruby-cairo/s390x (1.17.13-1 to 1.17.13-1)
  • Migration status for ruby-cairo/s390x (1.17.13-1 to 1.17.13-1): Will attempt migration (Any information below is purely informational)
• ruby-cbor/amd64 (0.5.9.8-1 to 0.5.9.8-1)
  • Migration status for ruby-cbor/amd64 (0.5.9.8-1 to 0.5.9.8-1): Will attempt migration (Any information below is purely informational)
• ruby-cbor/arm64 (0.5.9.8-1 to 0.5.9.8-1)
  • Migration status for ruby-cbor/arm64 (0.5.9.8-1 to 0.5.9.8-1): Will attempt migration (Any information below is purely informational)
• ruby-cbor/mips64el (0.5.9.8-1 to 0.5.9.8-1)
  • Migration status for ruby-cbor/mips64el (0.5.9.8-1 to 0.5.9.8-1): Will attempt migration (Any information below is purely informational)
• ruby-cbor/ppc64el (0.5.9.8-1 to 0.5.9.8-1)
  • Migration status for ruby-cbor/ppc64el (0.5.9.8-1 to 0.5.9.8-1): Will attempt migration (Any information below is purely informational)
• ruby-cbor/riscv64 (0.5.9.8-1 to 0.5.9.8-1)
  • Migration status for ruby-cbor/riscv64 (0.5.9.8-1 to 0.5.9.8-1): Will attempt migration (Any information below is purely informational)
• ruby-cbor/s390x (0.5.9.8-1 to 0.5.9.8-1)
  • Migration status for ruby-cbor/s390x (0.5.9.8-1 to 0.5.9.8-1): Will attempt migration (Any information below is purely informational)
• ruby-character-set/amd64 (1.8.0-1 to 1.8.0-1)
  • Migration status for ruby-character-set/amd64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• ruby-character-set/arm64 (1.8.0-1 to 1.8.0-1)
  • Migration status for ruby-character-set/arm64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• ruby-character-set/armel (1.8.0-1 to 1.8.0-1)
  • Migration status for ruby-character-set/armel (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• ruby-character-set/armhf (1.8.0-1 to 1.8.0-1)
  • Migration status for ruby-character-set/armhf (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• ruby-character-set/i386 (1.8.0-1 to 1.8.0-1)
  • Migration status for ruby-character-set/i386 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• ruby-character-set/mips64el (1.8.0-1 to 1.8.0-1)
  • Migration status for ruby-character-set/mips64el (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• ruby-character-set/ppc64el (1.8.0-1 to 1.8.0-1)
  • Migration status for ruby-character-set/ppc64el (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• ruby-character-set/riscv64 (1.8.0-1 to 1.8.0-1)
  • Migration status for ruby-character-set/riscv64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• ruby-character-set/s390x (1.8.0-1 to 1.8.0-1)
  • Migration status for ruby-character-set/s390x (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• ruby-charlock-holmes/amd64 (0.7.9-1 to 0.7.9-1)
  • Migration status for ruby-charlock-holmes/amd64 (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• ruby-charlock-holmes/arm64 (0.7.9-1 to 0.7.9-1)
  • Migration status for ruby-charlock-holmes/arm64 (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• ruby-charlock-holmes/armel (0.7.9-1 to 0.7.9-1)
  • Migration status for ruby-charlock-holmes/armel (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• ruby-charlock-holmes/armhf (0.7.9-1 to 0.7.9-1)
  • Migration status for ruby-charlock-holmes/armhf (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• ruby-charlock-holmes/i386 (0.7.9-1 to 0.7.9-1)
  • Migration status for ruby-charlock-holmes/i386 (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• ruby-charlock-holmes/mips64el (0.7.9-1 to 0.7.9-1)
  • Migration status for ruby-charlock-holmes/mips64el (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• ruby-charlock-holmes/ppc64el (0.7.9-1 to 0.7.9-1)
  • Migration status for ruby-charlock-holmes/ppc64el (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• ruby-charlock-holmes/riscv64 (0.7.9-1 to 0.7.9-1)
  • Migration status for ruby-charlock-holmes/riscv64 (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• ruby-charlock-holmes/s390x (0.7.9-1 to 0.7.9-1)
  • Migration status for ruby-charlock-holmes/s390x (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• ruby-commonmarker/amd64 (0.23.10-1 to 0.23.10-1)
  • Migration status for ruby-commonmarker/amd64 (0.23.10-1 to 0.23.10-1): Will attempt migration (Any information below is purely informational)
• ruby-commonmarker/arm64 (0.23.10-1 to 0.23.10-1)
  • Migration status for ruby-commonmarker/arm64 (0.23.10-1 to 0.23.10-1): Will attempt migration (Any information below is purely informational)
• ruby-commonmarker/armel (0.23.10-1 to 0.23.10-1)
  • Migration status for ruby-commonmarker/armel (0.23.10-1 to 0.23.10-1): Will attempt migration (Any information below is purely informational)
• ruby-commonmarker/i386 (0.23.10-1 to 0.23.10-1)
  • Migration status for ruby-commonmarker/i386 (0.23.10-1 to 0.23.10-1): Will attempt migration (Any information below is purely informational)
• ruby-commonmarker/mips64el (0.23.10-1 to 0.23.10-1)
  • Migration status for ruby-commonmarker/mips64el (0.23.10-1 to 0.23.10-1): Will attempt migration (Any information below is purely informational)
• ruby-commonmarker/ppc64el (0.23.10-1 to 0.23.10-1)
  • Migration status for ruby-commonmarker/ppc64el (0.23.10-1 to 0.23.10-1): Will attempt migration (Any information below is purely informational)
• ruby-commonmarker/riscv64 (0.23.10-1 to 0.23.10-1)
  • Migration status for ruby-commonmarker/riscv64 (0.23.10-1 to 0.23.10-1): Will attempt migration (Any information below is purely informational)
• ruby-concurrent/amd64 (1.3.4-1 to 1.3.4-1)
  • Migration status for ruby-concurrent/amd64 (1.3.4-1 to 1.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-concurrent/arm64 (1.3.4-1 to 1.3.4-1)
  • Migration status for ruby-concurrent/arm64 (1.3.4-1 to 1.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-concurrent/armel (1.3.4-1 to 1.3.4-1)
  • Migration status for ruby-concurrent/armel (1.3.4-1 to 1.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-concurrent/armhf (1.3.4-1 to 1.3.4-1)
  • Migration status for ruby-concurrent/armhf (1.3.4-1 to 1.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-concurrent/i386 (1.3.4-1 to 1.3.4-1)
  • Migration status for ruby-concurrent/i386 (1.3.4-1 to 1.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-concurrent/mips64el (1.3.4-1 to 1.3.4-1)
  • Migration status for ruby-concurrent/mips64el (1.3.4-1 to 1.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-concurrent/ppc64el (1.3.4-1 to 1.3.4-1)
  • Migration status for ruby-concurrent/ppc64el (1.3.4-1 to 1.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-concurrent/riscv64 (1.3.4-1 to 1.3.4-1)
  • Migration status for ruby-concurrent/riscv64 (1.3.4-1 to 1.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-concurrent/s390x (1.3.4-1 to 1.3.4-1)
  • Migration status for ruby-concurrent/s390x (1.3.4-1 to 1.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-cool.io/amd64 (1.8.1-1 to 1.8.1-1)
  • Migration status for ruby-cool.io/amd64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• ruby-cool.io/arm64 (1.8.1-1 to 1.8.1-1)
  • Migration status for ruby-cool.io/arm64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• ruby-cool.io/armel (1.8.1-1 to 1.8.1-1)
  • Migration status for ruby-cool.io/armel (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• ruby-cool.io/armhf (1.8.1-1 to 1.8.1-1)
  • Migration status for ruby-cool.io/armhf (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• ruby-cool.io/i386 (1.8.1-1 to 1.8.1-1)
  • Migration status for ruby-cool.io/i386 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• ruby-cool.io/mips64el (1.8.1-1 to 1.8.1-1)
  • Migration status for ruby-cool.io/mips64el (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• ruby-cool.io/ppc64el (1.8.1-1 to 1.8.1-1)
  • Migration status for ruby-cool.io/ppc64el (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• ruby-cool.io/riscv64 (1.8.1-1 to 1.8.1-1)
  • Migration status for ruby-cool.io/riscv64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• ruby-cool.io/s390x (1.8.1-1 to 1.8.1-1)
  • Migration status for ruby-cool.io/s390x (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• ruby-curb/amd64 (1.0.5-2 to 1.0.5-2)
  • Migration status for ruby-curb/amd64 (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• ruby-curb/arm64 (1.0.5-2 to 1.0.5-2)
  • Migration status for ruby-curb/arm64 (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• ruby-curb/armel (1.0.5-2 to 1.0.5-2)
  • Migration status for ruby-curb/armel (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• ruby-curb/armhf (1.0.5-2 to 1.0.5-2)
  • Migration status for ruby-curb/armhf (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• ruby-curb/i386 (1.0.5-2 to 1.0.5-2)
  • Migration status for ruby-curb/i386 (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• ruby-curb/mips64el (1.0.5-2 to 1.0.5-2)
  • Migration status for ruby-curb/mips64el (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• ruby-curb/ppc64el (1.0.5-2 to 1.0.5-2)
  • Migration status for ruby-curb/ppc64el (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• ruby-curb/riscv64 (1.0.5-2 to 1.0.5-2)
  • Migration status for ruby-curb/riscv64 (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• ruby-curb/s390x (1.0.5-2 to 1.0.5-2)
  • Migration status for ruby-curb/s390x (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• ruby-curses/amd64 (1.4.6-1 to 1.4.6-1)
  • Migration status for ruby-curses/amd64 (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-curses/arm64 (1.4.6-1 to 1.4.6-1)
  • Migration status for ruby-curses/arm64 (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-curses/armel (1.4.6-1 to 1.4.6-1)
  • Migration status for ruby-curses/armel (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-curses/armhf (1.4.6-1 to 1.4.6-1)
  • Migration status for ruby-curses/armhf (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-curses/i386 (1.4.6-1 to 1.4.6-1)
  • Migration status for ruby-curses/i386 (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-curses/mips64el (1.4.6-1 to 1.4.6-1)
  • Migration status for ruby-curses/mips64el (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-curses/ppc64el (1.4.6-1 to 1.4.6-1)
  • Migration status for ruby-curses/ppc64el (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-curses/riscv64 (1.4.6-1 to 1.4.6-1)
  • Migration status for ruby-curses/riscv64 (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-curses/s390x (1.4.6-1 to 1.4.6-1)
  • Migration status for ruby-curses/s390x (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-damerau-levenshtein/amd64 (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for ruby-damerau-levenshtein/amd64 (1.3.3+dfsg-1 to 1.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-damerau-levenshtein/arm64 (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for ruby-damerau-levenshtein/arm64 (1.3.3+dfsg-1 to 1.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-damerau-levenshtein/armel (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for ruby-damerau-levenshtein/armel (1.3.3+dfsg-1 to 1.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-damerau-levenshtein/armhf (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for ruby-damerau-levenshtein/armhf (1.3.3+dfsg-1 to 1.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-damerau-levenshtein/i386 (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for ruby-damerau-levenshtein/i386 (1.3.3+dfsg-1 to 1.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-damerau-levenshtein/mips64el (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for ruby-damerau-levenshtein/mips64el (1.3.3+dfsg-1 to 1.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-damerau-levenshtein/ppc64el (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for ruby-damerau-levenshtein/ppc64el (1.3.3+dfsg-1 to 1.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-damerau-levenshtein/riscv64 (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for ruby-damerau-levenshtein/riscv64 (1.3.3+dfsg-1 to 1.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-damerau-levenshtein/s390x (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for ruby-damerau-levenshtein/s390x (1.3.3+dfsg-1 to 1.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-dbm/amd64 (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-dbm/amd64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-dbm/arm64 (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-dbm/arm64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-dbm/armel (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-dbm/armel (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-dbm/armhf (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-dbm/armhf (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-dbm/i386 (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-dbm/i386 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-dbm/mips64el (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-dbm/mips64el (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-dbm/ppc64el (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-dbm/ppc64el (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-dbm/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-dbm/riscv64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-dbm/s390x (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-dbm/s390x (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-debian/amd64 (0.3.10 to 0.3.10)
  • Migration status for ruby-debian/amd64 (0.3.10 to 0.3.10): Will attempt migration (Any information below is purely informational)
• ruby-debian/arm64 (0.3.10 to 0.3.10)
  • Migration status for ruby-debian/arm64 (0.3.10 to 0.3.10): Will attempt migration (Any information below is purely informational)
• ruby-debian/armel (0.3.10 to 0.3.10)
  • Migration status for ruby-debian/armel (0.3.10 to 0.3.10): Will attempt migration (Any information below is purely informational)
• ruby-debian/armhf (0.3.10 to 0.3.10)
  • Migration status for ruby-debian/armhf (0.3.10 to 0.3.10): Will attempt migration (Any information below is purely informational)
• ruby-debian/i386 (0.3.10 to 0.3.10)
  • Migration status for ruby-debian/i386 (0.3.10 to 0.3.10): Will attempt migration (Any information below is purely informational)
• ruby-debian/mips64el (0.3.10 to 0.3.10)
  • Migration status for ruby-debian/mips64el (0.3.10 to 0.3.10): Will attempt migration (Any information below is purely informational)
• ruby-debian/ppc64el (0.3.10 to 0.3.10)
  • Migration status for ruby-debian/ppc64el (0.3.10 to 0.3.10): Will attempt migration (Any information below is purely informational)
• ruby-debian/riscv64 (0.3.10 to 0.3.10)
  • Migration status for ruby-debian/riscv64 (0.3.10 to 0.3.10): Will attempt migration (Any information below is purely informational)
• ruby-debian/s390x (0.3.10 to 0.3.10)
  • Migration status for ruby-debian/s390x (0.3.10 to 0.3.10): Will attempt migration (Any information below is purely informational)
• ruby-debug-inspector/amd64 (1.1.0+gh-2 to 1.1.0+gh-2)
  • Migration status for ruby-debug-inspector/amd64 (1.1.0+gh-2 to 1.1.0+gh-2): Will attempt migration (Any information below is purely informational)
• ruby-debug-inspector/arm64 (1.1.0+gh-2 to 1.1.0+gh-2)
  • Migration status for ruby-debug-inspector/arm64 (1.1.0+gh-2 to 1.1.0+gh-2): Will attempt migration (Any information below is purely informational)
• ruby-debug-inspector/armel (1.1.0+gh-2 to 1.1.0+gh-2)
  • Migration status for ruby-debug-inspector/armel (1.1.0+gh-2 to 1.1.0+gh-2): Will attempt migration (Any information below is purely informational)
• ruby-debug-inspector/armhf (1.1.0+gh-2 to 1.1.0+gh-2)
  • Migration status for ruby-debug-inspector/armhf (1.1.0+gh-2 to 1.1.0+gh-2): Will attempt migration (Any information below is purely informational)
• ruby-debug-inspector/i386 (1.1.0+gh-2 to 1.1.0+gh-2)
  • Migration status for ruby-debug-inspector/i386 (1.1.0+gh-2 to 1.1.0+gh-2): Will attempt migration (Any information below is purely informational)
• ruby-debug-inspector/mips64el (1.1.0+gh-2 to 1.1.0+gh-2)
  • Migration status for ruby-debug-inspector/mips64el (1.1.0+gh-2 to 1.1.0+gh-2): Will attempt migration (Any information below is purely informational)
• ruby-debug-inspector/ppc64el (1.1.0+gh-2 to 1.1.0+gh-2)
  • Migration status for ruby-debug-inspector/ppc64el (1.1.0+gh-2 to 1.1.0+gh-2): Will attempt migration (Any information below is purely informational)
• ruby-debug-inspector/riscv64 (1.1.0+gh-2 to 1.1.0+gh-2)
  • Migration status for ruby-debug-inspector/riscv64 (1.1.0+gh-2 to 1.1.0+gh-2): Will attempt migration (Any information below is purely informational)
• ruby-debug-inspector/s390x (1.1.0+gh-2 to 1.1.0+gh-2)
  • Migration status for ruby-debug-inspector/s390x (1.1.0+gh-2 to 1.1.0+gh-2): Will attempt migration (Any information below is purely informational)
• ruby-ed25519/amd64 (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for ruby-ed25519/amd64 (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-ed25519/arm64 (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for ruby-ed25519/arm64 (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-ed25519/armel (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for ruby-ed25519/armel (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-ed25519/armhf (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for ruby-ed25519/armhf (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-ed25519/i386 (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for ruby-ed25519/i386 (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-ed25519/mips64el (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for ruby-ed25519/mips64el (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-ed25519/ppc64el (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for ruby-ed25519/ppc64el (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-ed25519/riscv64 (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for ruby-ed25519/riscv64 (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-ed25519/s390x (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for ruby-ed25519/s390x (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-enumerable-statistics/amd64 (2.0.7+dfsg-3 to 2.0.7+dfsg-3)
  • Migration status for ruby-enumerable-statistics/amd64 (2.0.7+dfsg-3 to 2.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• ruby-enumerable-statistics/arm64 (2.0.7+dfsg-3 to 2.0.7+dfsg-3)
  • Migration status for ruby-enumerable-statistics/arm64 (2.0.7+dfsg-3 to 2.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• ruby-enumerable-statistics/armel (2.0.7+dfsg-3 to 2.0.7+dfsg-3)
  • Migration status for ruby-enumerable-statistics/armel (2.0.7+dfsg-3 to 2.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• ruby-enumerable-statistics/armhf (2.0.7+dfsg-3 to 2.0.7+dfsg-3)
  • Migration status for ruby-enumerable-statistics/armhf (2.0.7+dfsg-3 to 2.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• ruby-enumerable-statistics/i386 (2.0.7+dfsg-3 to 2.0.7+dfsg-3)
  • Migration status for ruby-enumerable-statistics/i386 (2.0.7+dfsg-3 to 2.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• ruby-enumerable-statistics/mips64el (2.0.7+dfsg-3 to 2.0.7+dfsg-3)
  • Migration status for ruby-enumerable-statistics/mips64el (2.0.7+dfsg-3 to 2.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• ruby-enumerable-statistics/ppc64el (2.0.7+dfsg-3 to 2.0.7+dfsg-3)
  • Migration status for ruby-enumerable-statistics/ppc64el (2.0.7+dfsg-3 to 2.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• ruby-enumerable-statistics/riscv64 (2.0.7+dfsg-3 to 2.0.7+dfsg-3)
  • Migration status for ruby-enumerable-statistics/riscv64 (2.0.7+dfsg-3 to 2.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• ruby-enumerable-statistics/s390x (2.0.7+dfsg-3 to 2.0.7+dfsg-3)
  • Migration status for ruby-enumerable-statistics/s390x (2.0.7+dfsg-3 to 2.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• ruby-escape-utils/amd64 (1.2.1-4 to 1.2.1-4)
  • Migration status for ruby-escape-utils/amd64 (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
• ruby-escape-utils/arm64 (1.2.1-4 to 1.2.1-4)
  • Migration status for ruby-escape-utils/arm64 (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
• ruby-escape-utils/armel (1.2.1-4 to 1.2.1-4)
  • Migration status for ruby-escape-utils/armel (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
• ruby-escape-utils/i386 (1.2.1-4 to 1.2.1-4)
  • Migration status for ruby-escape-utils/i386 (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
• ruby-escape-utils/mips64el (1.2.1-4 to 1.2.1-4)
  • Migration status for ruby-escape-utils/mips64el (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
• ruby-escape-utils/ppc64el (1.2.1-4 to 1.2.1-4)
  • Migration status for ruby-escape-utils/ppc64el (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
• ruby-escape-utils/riscv64 (1.2.1-4 to 1.2.1-4)
  • Migration status for ruby-escape-utils/riscv64 (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
• ruby-eventmachine/amd64 (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5)
  • Migration status for ruby-eventmachine/amd64 (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5): Will attempt migration (Any information below is purely informational)
• ruby-eventmachine/arm64 (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5)
  • Migration status for ruby-eventmachine/arm64 (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5): Will attempt migration (Any information below is purely informational)
• ruby-eventmachine/armel (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5)
  • Migration status for ruby-eventmachine/armel (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5): Will attempt migration (Any information below is purely informational)
• ruby-eventmachine/armhf (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5)
  • Migration status for ruby-eventmachine/armhf (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5): Will attempt migration (Any information below is purely informational)
• ruby-eventmachine/i386 (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5)
  • Migration status for ruby-eventmachine/i386 (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5): Will attempt migration (Any information below is purely informational)
• ruby-eventmachine/mips64el (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5)
  • Migration status for ruby-eventmachine/mips64el (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5): Will attempt migration (Any information below is purely informational)
• ruby-eventmachine/ppc64el (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5)
  • Migration status for ruby-eventmachine/ppc64el (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5): Will attempt migration (Any information below is purely informational)
• ruby-eventmachine/riscv64 (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5)
  • Migration status for ruby-eventmachine/riscv64 (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5): Will attempt migration (Any information below is purely informational)
• ruby-eventmachine/s390x (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5)
  • Migration status for ruby-eventmachine/s390x (1.3~pre20220315-df4ab006-5 to 1.3~pre20220315-df4ab006-5): Will attempt migration (Any information below is purely informational)
• ruby-exif/amd64 (0.1.2-22 to 0.1.2-22)
  • Migration status for ruby-exif/amd64 (0.1.2-22 to 0.1.2-22): Will attempt migration (Any information below is purely informational)
• ruby-exif/arm64 (0.1.2-22 to 0.1.2-22)
  • Migration status for ruby-exif/arm64 (0.1.2-22 to 0.1.2-22): Will attempt migration (Any information below is purely informational)
• ruby-exif/armel (0.1.2-22 to 0.1.2-22)
  • Migration status for ruby-exif/armel (0.1.2-22 to 0.1.2-22): Will attempt migration (Any information below is purely informational)
• ruby-exif/armhf (0.1.2-22 to 0.1.2-22)
  • Migration status for ruby-exif/armhf (0.1.2-22 to 0.1.2-22): Will attempt migration (Any information below is purely informational)
• ruby-exif/i386 (0.1.2-22 to 0.1.2-22)
  • Migration status for ruby-exif/i386 (0.1.2-22 to 0.1.2-22): Will attempt migration (Any information below is purely informational)
• ruby-exif/mips64el (0.1.2-22 to 0.1.2-22)
  • Migration status for ruby-exif/mips64el (0.1.2-22 to 0.1.2-22): Will attempt migration (Any information below is purely informational)
• ruby-exif/ppc64el (0.1.2-22 to 0.1.2-22)
  • Migration status for ruby-exif/ppc64el (0.1.2-22 to 0.1.2-22): Will attempt migration (Any information below is purely informational)
• ruby-exif/riscv64 (0.1.2-22 to 0.1.2-22)
  • Migration status for ruby-exif/riscv64 (0.1.2-22 to 0.1.2-22): Will attempt migration (Any information below is purely informational)
• ruby-exif/s390x (0.1.2-22 to 0.1.2-22)
  • Migration status for ruby-exif/s390x (0.1.2-22 to 0.1.2-22): Will attempt migration (Any information below is purely informational)
• ruby-fast-blank/amd64 (1.0.1-1 to 1.0.1-1)
  • Migration status for ruby-fast-blank/amd64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ruby-fast-blank/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for ruby-fast-blank/arm64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ruby-fast-blank/armel (1.0.1-1 to 1.0.1-1)
  • Migration status for ruby-fast-blank/armel (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ruby-fast-blank/armhf (1.0.1-1 to 1.0.1-1)
  • Migration status for ruby-fast-blank/armhf (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ruby-fast-blank/i386 (1.0.1-1 to 1.0.1-1)
  • Migration status for ruby-fast-blank/i386 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ruby-fast-blank/mips64el (1.0.1-1 to 1.0.1-1)
  • Migration status for ruby-fast-blank/mips64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ruby-fast-blank/ppc64el (1.0.1-1 to 1.0.1-1)
  • Migration status for ruby-fast-blank/ppc64el (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ruby-fast-blank/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for ruby-fast-blank/riscv64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ruby-fast-blank/s390x (1.0.1-1 to 1.0.1-1)
  • Migration status for ruby-fast-blank/s390x (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ruby-fast-stemmer/amd64 (1.0.2-4 to 1.0.2-4)
  • Migration status for ruby-fast-stemmer/amd64 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• ruby-fast-stemmer/arm64 (1.0.2-4 to 1.0.2-4)
  • Migration status for ruby-fast-stemmer/arm64 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• ruby-fast-stemmer/armel (1.0.2-4 to 1.0.2-4)
  • Migration status for ruby-fast-stemmer/armel (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• ruby-fast-stemmer/armhf (1.0.2-4 to 1.0.2-4)
  • Migration status for ruby-fast-stemmer/armhf (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• ruby-fast-stemmer/i386 (1.0.2-4 to 1.0.2-4)
  • Migration status for ruby-fast-stemmer/i386 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• ruby-fast-stemmer/mips64el (1.0.2-4 to 1.0.2-4)
  • Migration status for ruby-fast-stemmer/mips64el (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• ruby-fast-stemmer/ppc64el (1.0.2-4 to 1.0.2-4)
  • Migration status for ruby-fast-stemmer/ppc64el (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• ruby-fast-stemmer/riscv64 (1.0.2-4 to 1.0.2-4)
  • Migration status for ruby-fast-stemmer/riscv64 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• ruby-fast-stemmer/s390x (1.0.2-4 to 1.0.2-4)
  • Migration status for ruby-fast-stemmer/s390x (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• ruby-fast-xs/amd64 (0.8.0-3.1 to 0.8.0-3.1)
  • Migration status for ruby-fast-xs/amd64 (0.8.0-3.1 to 0.8.0-3.1): Will attempt migration (Any information below is purely informational)
• ruby-fast-xs/arm64 (0.8.0-3.1 to 0.8.0-3.1)
  • Migration status for ruby-fast-xs/arm64 (0.8.0-3.1 to 0.8.0-3.1): Will attempt migration (Any information below is purely informational)
• ruby-fast-xs/armel (0.8.0-3.1 to 0.8.0-3.1)
  • Migration status for ruby-fast-xs/armel (0.8.0-3.1 to 0.8.0-3.1): Will attempt migration (Any information below is purely informational)
• ruby-fast-xs/armhf (0.8.0-3.1 to 0.8.0-3.1)
  • Migration status for ruby-fast-xs/armhf (0.8.0-3.1 to 0.8.0-3.1): Will attempt migration (Any information below is purely informational)
• ruby-fast-xs/i386 (0.8.0-3.1 to 0.8.0-3.1)
  • Migration status for ruby-fast-xs/i386 (0.8.0-3.1 to 0.8.0-3.1): Will attempt migration (Any information below is purely informational)
• ruby-fast-xs/mips64el (0.8.0-3.1 to 0.8.0-3.1)
  • Migration status for ruby-fast-xs/mips64el (0.8.0-3.1 to 0.8.0-3.1): Will attempt migration (Any information below is purely informational)
• ruby-fast-xs/ppc64el (0.8.0-3.1 to 0.8.0-3.1)
  • Migration status for ruby-fast-xs/ppc64el (0.8.0-3.1 to 0.8.0-3.1): Will attempt migration (Any information below is purely informational)
• ruby-fast-xs/riscv64 (0.8.0-3.1 to 0.8.0-3.1)
  • Migration status for ruby-fast-xs/riscv64 (0.8.0-3.1 to 0.8.0-3.1): Will attempt migration (Any information below is purely informational)
• ruby-fast-xs/s390x (0.8.0-3.1 to 0.8.0-3.1)
  • Migration status for ruby-fast-xs/s390x (0.8.0-3.1 to 0.8.0-3.1): Will attempt migration (Any information below is purely informational)
• ruby-fcgi/amd64 (0.9.2.2-1 to 0.9.2.2-1)
  • Migration status for ruby-fcgi/amd64 (0.9.2.2-1 to 0.9.2.2-1): Will attempt migration (Any information below is purely informational)
• ruby-fcgi/arm64 (0.9.2.2-1 to 0.9.2.2-1)
  • Migration status for ruby-fcgi/arm64 (0.9.2.2-1 to 0.9.2.2-1): Will attempt migration (Any information below is purely informational)
• ruby-fcgi/armel (0.9.2.2-1 to 0.9.2.2-1)
  • Migration status for ruby-fcgi/armel (0.9.2.2-1 to 0.9.2.2-1): Will attempt migration (Any information below is purely informational)
• ruby-fcgi/armhf (0.9.2.2-1 to 0.9.2.2-1)
  • Migration status for ruby-fcgi/armhf (0.9.2.2-1 to 0.9.2.2-1): Will attempt migration (Any information below is purely informational)
• ruby-fcgi/i386 (0.9.2.2-1 to 0.9.2.2-1)
  • Migration status for ruby-fcgi/i386 (0.9.2.2-1 to 0.9.2.2-1): Will attempt migration (Any information below is purely informational)
• ruby-fcgi/mips64el (0.9.2.2-1 to 0.9.2.2-1)
  • Migration status for ruby-fcgi/mips64el (0.9.2.2-1 to 0.9.2.2-1): Will attempt migration (Any information below is purely informational)
• ruby-fcgi/ppc64el (0.9.2.2-1 to 0.9.2.2-1)
  • Migration status for ruby-fcgi/ppc64el (0.9.2.2-1 to 0.9.2.2-1): Will attempt migration (Any information below is purely informational)
• ruby-fcgi/riscv64 (0.9.2.2-1 to 0.9.2.2-1)
  • Migration status for ruby-fcgi/riscv64 (0.9.2.2-1 to 0.9.2.2-1): Will attempt migration (Any information below is purely informational)
• ruby-fcgi/s390x (0.9.2.2-1 to 0.9.2.2-1)
  • Migration status for ruby-fcgi/s390x (0.9.2.2-1 to 0.9.2.2-1): Will attempt migration (Any information below is purely informational)
• ruby-ffi-yajl/amd64 (2.3.1-3 to 2.3.1-3)
  • Migration status for ruby-ffi-yajl/amd64 (2.3.1-3 to 2.3.1-3): Will attempt migration (Any information below is purely informational)
• ruby-ffi-yajl/arm64 (2.3.1-3 to 2.3.1-3)
  • Migration status for ruby-ffi-yajl/arm64 (2.3.1-3 to 2.3.1-3): Will attempt migration (Any information below is purely informational)
• ruby-ffi-yajl/armel (2.3.1-3 to 2.3.1-3)
  • Migration status for ruby-ffi-yajl/armel (2.3.1-3 to 2.3.1-3): Will attempt migration (Any information below is purely informational)
• ruby-ffi-yajl/armhf (2.3.1-3 to 2.3.1-3)
  • Migration status for ruby-ffi-yajl/armhf (2.3.1-3 to 2.3.1-3): Will attempt migration (Any information below is purely informational)
• ruby-ffi-yajl/i386 (2.3.1-3 to 2.3.1-3)
  • Migration status for ruby-ffi-yajl/i386 (2.3.1-3 to 2.3.1-3): Will attempt migration (Any information below is purely informational)
• ruby-ffi-yajl/mips64el (2.3.1-3 to 2.3.1-3)
  • Migration status for ruby-ffi-yajl/mips64el (2.3.1-3 to 2.3.1-3): Will attempt migration (Any information below is purely informational)
• ruby-ffi-yajl/ppc64el (2.3.1-3 to 2.3.1-3)
  • Migration status for ruby-ffi-yajl/ppc64el (2.3.1-3 to 2.3.1-3): Will attempt migration (Any information below is purely informational)
• ruby-ffi-yajl/riscv64 (2.3.1-3 to 2.3.1-3)
  • Migration status for ruby-ffi-yajl/riscv64 (2.3.1-3 to 2.3.1-3): Will attempt migration (Any information below is purely informational)
• ruby-ffi-yajl/s390x (2.3.1-3 to 2.3.1-3)
  • Migration status for ruby-ffi-yajl/s390x (2.3.1-3 to 2.3.1-3): Will attempt migration (Any information below is purely informational)
• ruby-ffi/amd64 (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
  • Migration status for ruby-ffi/amd64 (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-ffi/arm64 (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
  • Migration status for ruby-ffi/arm64 (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-ffi/armel (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
  • Migration status for ruby-ffi/armel (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-ffi/armhf (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
  • Migration status for ruby-ffi/armhf (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-ffi/i386 (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
  • Migration status for ruby-ffi/i386 (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-ffi/mips64el (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
  • Migration status for ruby-ffi/mips64el (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-ffi/ppc64el (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
  • Migration status for ruby-ffi/ppc64el (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-ffi/riscv64 (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
  • Migration status for ruby-ffi/riscv64 (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-ffi/s390x (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
  • Migration status for ruby-ffi/s390x (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-fftw3/amd64 (1.0.2-3 to 1.0.2-3)
  • Migration status for ruby-fftw3/amd64 (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-fftw3/arm64 (1.0.2-3 to 1.0.2-3)
  • Migration status for ruby-fftw3/arm64 (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-fftw3/armel (1.0.2-3 to 1.0.2-3)
  • Migration status for ruby-fftw3/armel (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-fftw3/i386 (1.0.2-3 to 1.0.2-3)
  • Migration status for ruby-fftw3/i386 (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-fftw3/mips64el (1.0.2-3 to 1.0.2-3)
  • Migration status for ruby-fftw3/mips64el (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-fftw3/ppc64el (1.0.2-3 to 1.0.2-3)
  • Migration status for ruby-fftw3/ppc64el (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-fftw3/riscv64 (1.0.2-3 to 1.0.2-3)
  • Migration status for ruby-fftw3/riscv64 (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-fusefs/amd64 (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/amd64 (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• ruby-fusefs/arm64 (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/arm64 (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• ruby-fusefs/armel (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/armel (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• ruby-fusefs/armhf (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/armhf (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• ruby-fusefs/i386 (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/i386 (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• ruby-fusefs/mips64el (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/mips64el (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• ruby-fusefs/ppc64el (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/ppc64el (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• ruby-fusefs/riscv64 (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/riscv64 (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• ruby-fusefs/s390x (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/s390x (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• ruby-github-linguist/amd64 (7.27.0-1 to 7.27.0-1)
  • Migration status for ruby-github-linguist/amd64 (7.27.0-1 to 7.27.0-1): Will attempt migration (Any information below is purely informational)
• ruby-github-linguist/arm64 (7.27.0-1 to 7.27.0-1)
  • Migration status for ruby-github-linguist/arm64 (7.27.0-1 to 7.27.0-1): Will attempt migration (Any information below is purely informational)
• ruby-github-linguist/armel (7.27.0-1 to 7.27.0-1)
  • Migration status for ruby-github-linguist/armel (7.27.0-1 to 7.27.0-1): Will attempt migration (Any information below is purely informational)
• ruby-github-linguist/i386 (7.27.0-1 to 7.27.0-1)
  • Migration status for ruby-github-linguist/i386 (7.27.0-1 to 7.27.0-1): Will attempt migration (Any information below is purely informational)
• ruby-github-linguist/mips64el (7.27.0-1 to 7.27.0-1)
  • Migration status for ruby-github-linguist/mips64el (7.27.0-1 to 7.27.0-1): Will attempt migration (Any information below is purely informational)
• ruby-github-linguist/ppc64el (7.27.0-1 to 7.27.0-1)
  • Migration status for ruby-github-linguist/ppc64el (7.27.0-1 to 7.27.0-1): Will attempt migration (Any information below is purely informational)
• ruby-github-linguist/riscv64 (7.27.0-1 to 7.27.0-1)
  • Migration status for ruby-github-linguist/riscv64 (7.27.0-1 to 7.27.0-1): Will attempt migration (Any information below is purely informational)
• ruby-github-markdown/amd64 (0.6.9-5 to 0.6.9-5)
  • Migration status for ruby-github-markdown/amd64 (0.6.9-5 to 0.6.9-5): Will attempt migration (Any information below is purely informational)
• ruby-github-markdown/arm64 (0.6.9-5 to 0.6.9-5)
  • Migration status for ruby-github-markdown/arm64 (0.6.9-5 to 0.6.9-5): Will attempt migration (Any information below is purely informational)
• ruby-github-markdown/armel (0.6.9-5 to 0.6.9-5)
  • Migration status for ruby-github-markdown/armel (0.6.9-5 to 0.6.9-5): Will attempt migration (Any information below is purely informational)
• ruby-github-markdown/i386 (0.6.9-5 to 0.6.9-5)
  • Migration status for ruby-github-markdown/i386 (0.6.9-5 to 0.6.9-5): Will attempt migration (Any information below is purely informational)
• ruby-github-markdown/mips64el (0.6.9-5 to 0.6.9-5)
  • Migration status for ruby-github-markdown/mips64el (0.6.9-5 to 0.6.9-5): Will attempt migration (Any information below is purely informational)
• ruby-github-markdown/ppc64el (0.6.9-5 to 0.6.9-5)
  • Migration status for ruby-github-markdown/ppc64el (0.6.9-5 to 0.6.9-5): Will attempt migration (Any information below is purely informational)
• ruby-github-markdown/riscv64 (0.6.9-5 to 0.6.9-5)
  • Migration status for ruby-github-markdown/riscv64 (0.6.9-5 to 0.6.9-5): Will attempt migration (Any information below is purely informational)
• ruby-gnome/amd64 (4.2.2-2 to 4.2.2-2)
  • Migration status for ruby-gnome/amd64 (4.2.2-2 to 4.2.2-2): Will attempt migration (Any information below is purely informational)
• ruby-gnome/arm64 (4.2.2-2 to 4.2.2-2)
  • Migration status for ruby-gnome/arm64 (4.2.2-2 to 4.2.2-2): Will attempt migration (Any information below is purely informational)
• ruby-gnome/armel (4.2.2-2 to 4.2.2-2)
  • Migration status for ruby-gnome/armel (4.2.2-2 to 4.2.2-2): Will attempt migration (Any information below is purely informational)
• ruby-gnome/i386 (4.2.2-2 to 4.2.2-2)
  • Migration status for ruby-gnome/i386 (4.2.2-2 to 4.2.2-2): Will attempt migration (Any information below is purely informational)
• ruby-gnome/mips64el (4.2.2-2 to 4.2.2-2)
  • Migration status for ruby-gnome/mips64el (4.2.2-2 to 4.2.2-2): Will attempt migration (Any information below is purely informational)
• ruby-gnome/ppc64el (4.2.2-2 to 4.2.2-2)
  • Migration status for ruby-gnome/ppc64el (4.2.2-2 to 4.2.2-2): Will attempt migration (Any information below is purely informational)
• ruby-gnome/riscv64 (4.2.2-2 to 4.2.2-2)
  • Migration status for ruby-gnome/riscv64 (4.2.2-2 to 4.2.2-2): Will attempt migration (Any information below is purely informational)
• ruby-gpgme/amd64 (2.0.23-1 to 2.0.23-1)
  • Migration status for ruby-gpgme/amd64 (2.0.23-1 to 2.0.23-1): Will attempt migration (Any information below is purely informational)
• ruby-gpgme/arm64 (2.0.23-1 to 2.0.23-1)
  • Migration status for ruby-gpgme/arm64 (2.0.23-1 to 2.0.23-1): Will attempt migration (Any information below is purely informational)
• ruby-gpgme/armel (2.0.23-1 to 2.0.23-1)
  • Migration status for ruby-gpgme/armel (2.0.23-1 to 2.0.23-1): Will attempt migration (Any information below is purely informational)
• ruby-gpgme/armhf (2.0.23-1 to 2.0.23-1)
  • Migration status for ruby-gpgme/armhf (2.0.23-1 to 2.0.23-1): Will attempt migration (Any information below is purely informational)
• ruby-gpgme/i386 (2.0.23-1 to 2.0.23-1)
  • Migration status for ruby-gpgme/i386 (2.0.23-1 to 2.0.23-1): Will attempt migration (Any information below is purely informational)
• ruby-gpgme/mips64el (2.0.23-1 to 2.0.23-1)
  • Migration status for ruby-gpgme/mips64el (2.0.23-1 to 2.0.23-1): Will attempt migration (Any information below is purely informational)
• ruby-gpgme/ppc64el (2.0.23-1 to 2.0.23-1)
  • Migration status for ruby-gpgme/ppc64el (2.0.23-1 to 2.0.23-1): Will attempt migration (Any information below is purely informational)
• ruby-gpgme/riscv64 (2.0.23-1 to 2.0.23-1)
  • Migration status for ruby-gpgme/riscv64 (2.0.23-1 to 2.0.23-1): Will attempt migration (Any information below is purely informational)
• ruby-gpgme/s390x (2.0.23-1 to 2.0.23-1)
  • Migration status for ruby-gpgme/s390x (2.0.23-1 to 2.0.23-1): Will attempt migration (Any information below is purely informational)
• ruby-grib/amd64 (0.4.0-7 to 0.4.0-7)
  • Migration status for ruby-grib/amd64 (0.4.0-7 to 0.4.0-7): Will attempt migration (Any information below is purely informational)
• ruby-grib/arm64 (0.4.0-7 to 0.4.0-7)
  • Migration status for ruby-grib/arm64 (0.4.0-7 to 0.4.0-7): Will attempt migration (Any information below is purely informational)
• ruby-grib/mips64el (0.4.0-7 to 0.4.0-7)
  • Migration status for ruby-grib/mips64el (0.4.0-7 to 0.4.0-7): Will attempt migration (Any information below is purely informational)
• ruby-grib/ppc64el (0.4.0-7 to 0.4.0-7)
  • Migration status for ruby-grib/ppc64el (0.4.0-7 to 0.4.0-7): Will attempt migration (Any information below is purely informational)
• ruby-grib/riscv64 (0.4.0-7 to 0.4.0-7)
  • Migration status for ruby-grib/riscv64 (0.4.0-7 to 0.4.0-7): Will attempt migration (Any information below is purely informational)
• ruby-haml/amd64 (6.1.2-1 to 6.1.2-1)
  • Migration status for ruby-haml/amd64 (6.1.2-1 to 6.1.2-1): Will attempt migration (Any information below is purely informational)
• ruby-haml/arm64 (6.1.2-1 to 6.1.2-1)
  • Migration status for ruby-haml/arm64 (6.1.2-1 to 6.1.2-1): Will attempt migration (Any information below is purely informational)
• ruby-haml/armel (6.1.2-1 to 6.1.2-1)
  • Migration status for ruby-haml/armel (6.1.2-1 to 6.1.2-1): Will attempt migration (Any information below is purely informational)
• ruby-haml/i386 (6.1.2-1 to 6.1.2-1)
  • Migration status for ruby-haml/i386 (6.1.2-1 to 6.1.2-1): Will attempt migration (Any information below is purely informational)
• ruby-haml/mips64el (6.1.2-1 to 6.1.2-1)
  • Migration status for ruby-haml/mips64el (6.1.2-1 to 6.1.2-1): Will attempt migration (Any information below is purely informational)
• ruby-haml/ppc64el (6.1.2-1 to 6.1.2-1)
  • Migration status for ruby-haml/ppc64el (6.1.2-1 to 6.1.2-1): Will attempt migration (Any information below is purely informational)
• ruby-haml/riscv64 (6.1.2-1 to 6.1.2-1)
  • Migration status for ruby-haml/riscv64 (6.1.2-1 to 6.1.2-1): Will attempt migration (Any information below is purely informational)
• ruby-hamlit/amd64 (2.15.1-3 to 2.15.1-3)
  • Migration status for ruby-hamlit/amd64 (2.15.1-3 to 2.15.1-3): Will attempt migration (Any information below is purely informational)
• ruby-hamlit/arm64 (2.15.1-3 to 2.15.1-3)
  • Migration status for ruby-hamlit/arm64 (2.15.1-3 to 2.15.1-3): Will attempt migration (Any information below is purely informational)
• ruby-hamlit/armel (2.15.1-3 to 2.15.1-3)
  • Migration status for ruby-hamlit/armel (2.15.1-3 to 2.15.1-3): Will attempt migration (Any information below is purely informational)
• ruby-hamlit/i386 (2.15.1-3 to 2.15.1-3)
  • Migration status for ruby-hamlit/i386 (2.15.1-3 to 2.15.1-3): Will attempt migration (Any information below is purely informational)
• ruby-hamlit/mips64el (2.15.1-3 to 2.15.1-3)
  • Migration status for ruby-hamlit/mips64el (2.15.1-3 to 2.15.1-3): Will attempt migration (Any information below is purely informational)
• ruby-hamlit/ppc64el (2.15.1-3 to 2.15.1-3)
  • Migration status for ruby-hamlit/ppc64el (2.15.1-3 to 2.15.1-3): Will attempt migration (Any information below is purely informational)
• ruby-hamlit/riscv64 (2.15.1-3 to 2.15.1-3)
  • Migration status for ruby-hamlit/riscv64 (2.15.1-3 to 2.15.1-3): Will attempt migration (Any information below is purely informational)
• ruby-hdfeos5/amd64 (1.2-14 to 1.2-14)
  • Migration status for ruby-hdfeos5/amd64 (1.2-14 to 1.2-14): Will attempt migration (Any information below is purely informational)
• ruby-hdfeos5/arm64 (1.2-14 to 1.2-14)
  • Migration status for ruby-hdfeos5/arm64 (1.2-14 to 1.2-14): Will attempt migration (Any information below is purely informational)
• ruby-hdfeos5/armel (1.2-14 to 1.2-14)
  • Migration status for ruby-hdfeos5/armel (1.2-14 to 1.2-14): Will attempt migration (Any information below is purely informational)
• ruby-hdfeos5/i386 (1.2-14 to 1.2-14)
  • Migration status for ruby-hdfeos5/i386 (1.2-14 to 1.2-14): Will attempt migration (Any information below is purely informational)
• ruby-hdfeos5/mips64el (1.2-14 to 1.2-14)
  • Migration status for ruby-hdfeos5/mips64el (1.2-14 to 1.2-14): Will attempt migration (Any information below is purely informational)
• ruby-hdfeos5/ppc64el (1.2-14 to 1.2-14)
  • Migration status for ruby-hdfeos5/ppc64el (1.2-14 to 1.2-14): Will attempt migration (Any information below is purely informational)
• ruby-hdfeos5/riscv64 (1.2-14 to 1.2-14)
  • Migration status for ruby-hdfeos5/riscv64 (1.2-14 to 1.2-14): Will attempt migration (Any information below is purely informational)
• ruby-hiredis/amd64 (0.6.3-5 to 0.6.3-5)
  • Migration status for ruby-hiredis/amd64 (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
• ruby-hiredis/arm64 (0.6.3-5 to 0.6.3-5)
  • Migration status for ruby-hiredis/arm64 (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
• ruby-hiredis/armel (0.6.3-5 to 0.6.3-5)
  • Migration status for ruby-hiredis/armel (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
• ruby-hiredis/armhf (0.6.3-5 to 0.6.3-5)
  • Migration status for ruby-hiredis/armhf (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
• ruby-hiredis/i386 (0.6.3-5 to 0.6.3-5)
  • Migration status for ruby-hiredis/i386 (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
• ruby-hiredis/mips64el (0.6.3-5 to 0.6.3-5)
  • Migration status for ruby-hiredis/mips64el (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
• ruby-hiredis/ppc64el (0.6.3-5 to 0.6.3-5)
  • Migration status for ruby-hiredis/ppc64el (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
• ruby-hiredis/riscv64 (0.6.3-5 to 0.6.3-5)
  • Migration status for ruby-hiredis/riscv64 (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
• ruby-hiredis/s390x (0.6.3-5 to 0.6.3-5)
  • Migration status for ruby-hiredis/s390x (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
• ruby-hitimes/amd64 (1.3.1-1 to 1.3.1-1)
  • Migration status for ruby-hitimes/amd64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-hitimes/arm64 (1.3.1-1 to 1.3.1-1)
  • Migration status for ruby-hitimes/arm64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-hitimes/armel (1.3.1-1 to 1.3.1-1)
  • Migration status for ruby-hitimes/armel (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-hitimes/armhf (1.3.1-1 to 1.3.1-1)
  • Migration status for ruby-hitimes/armhf (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-hitimes/i386 (1.3.1-1 to 1.3.1-1)
  • Migration status for ruby-hitimes/i386 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-hitimes/mips64el (1.3.1-1 to 1.3.1-1)
  • Migration status for ruby-hitimes/mips64el (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-hitimes/ppc64el (1.3.1-1 to 1.3.1-1)
  • Migration status for ruby-hitimes/ppc64el (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-hitimes/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for ruby-hitimes/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-hitimes/s390x (1.3.1-1 to 1.3.1-1)
  • Migration status for ruby-hitimes/s390x (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-http-parser.rb/amd64 (0.6.0-6 to 0.6.0-6)
  • Migration status for ruby-http-parser.rb/amd64 (0.6.0-6 to 0.6.0-6): Will attempt migration (Any information below is purely informational)
• ruby-http-parser.rb/arm64 (0.6.0-6 to 0.6.0-6)
  • Migration status for ruby-http-parser.rb/arm64 (0.6.0-6 to 0.6.0-6): Will attempt migration (Any information below is purely informational)
• ruby-http-parser.rb/armel (0.6.0-6 to 0.6.0-6)
  • Migration status for ruby-http-parser.rb/armel (0.6.0-6 to 0.6.0-6): Will attempt migration (Any information below is purely informational)
• ruby-http-parser.rb/i386 (0.6.0-6 to 0.6.0-6)
  • Migration status for ruby-http-parser.rb/i386 (0.6.0-6 to 0.6.0-6): Will attempt migration (Any information below is purely informational)
• ruby-http-parser.rb/mips64el (0.6.0-6 to 0.6.0-6)
  • Migration status for ruby-http-parser.rb/mips64el (0.6.0-6 to 0.6.0-6): Will attempt migration (Any information below is purely informational)
• ruby-http-parser.rb/ppc64el (0.6.0-6 to 0.6.0-6)
  • Migration status for ruby-http-parser.rb/ppc64el (0.6.0-6 to 0.6.0-6): Will attempt migration (Any information below is purely informational)
• ruby-http-parser.rb/riscv64 (0.6.0-6 to 0.6.0-6)
  • Migration status for ruby-http-parser.rb/riscv64 (0.6.0-6 to 0.6.0-6): Will attempt migration (Any information below is purely informational)
• ruby-jaro-winkler/amd64 (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-jaro-winkler/amd64 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-jaro-winkler/arm64 (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-jaro-winkler/arm64 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-jaro-winkler/armel (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-jaro-winkler/armel (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-jaro-winkler/armhf (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-jaro-winkler/armhf (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-jaro-winkler/i386 (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-jaro-winkler/i386 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-jaro-winkler/mips64el (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-jaro-winkler/mips64el (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-jaro-winkler/ppc64el (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-jaro-winkler/ppc64el (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-jaro-winkler/riscv64 (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-jaro-winkler/riscv64 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-jaro-winkler/s390x (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-jaro-winkler/s390x (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-json/amd64 (2.9.1+dfsg-1 to 2.9.1+dfsg-1)
  • Migration status for ruby-json/amd64 (2.9.1+dfsg-1 to 2.9.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-json/arm64 (2.9.1+dfsg-1 to 2.9.1+dfsg-1)
  • Migration status for ruby-json/arm64 (2.9.1+dfsg-1 to 2.9.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-json/armel (2.9.1+dfsg-1 to 2.9.1+dfsg-1)
  • Migration status for ruby-json/armel (2.9.1+dfsg-1 to 2.9.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-json/armhf (2.9.1+dfsg-1 to 2.9.1+dfsg-1)
  • Migration status for ruby-json/armhf (2.9.1+dfsg-1 to 2.9.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-json/i386 (2.9.1+dfsg-1 to 2.9.1+dfsg-1)
  • Migration status for ruby-json/i386 (2.9.1+dfsg-1 to 2.9.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-json/mips64el (2.9.1+dfsg-1 to 2.9.1+dfsg-1)
  • Migration status for ruby-json/mips64el (2.9.1+dfsg-1 to 2.9.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-json/ppc64el (2.9.1+dfsg-1 to 2.9.1+dfsg-1)
  • Migration status for ruby-json/ppc64el (2.9.1+dfsg-1 to 2.9.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-json/riscv64 (2.9.1+dfsg-1 to 2.9.1+dfsg-1)
  • Migration status for ruby-json/riscv64 (2.9.1+dfsg-1 to 2.9.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-json/s390x (2.9.1+dfsg-1 to 2.9.1+dfsg-1)
  • Migration status for ruby-json/s390x (2.9.1+dfsg-1 to 2.9.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-kgio/amd64 (2.11.2-2 to 2.11.2-2)
  • Migration status for ruby-kgio/amd64 (2.11.2-2 to 2.11.2-2): Will attempt migration (Any information below is purely informational)
• ruby-kgio/arm64 (2.11.2-2 to 2.11.2-2)
  • Migration status for ruby-kgio/arm64 (2.11.2-2 to 2.11.2-2): Will attempt migration (Any information below is purely informational)
• ruby-kgio/armel (2.11.2-2 to 2.11.2-2)
  • Migration status for ruby-kgio/armel (2.11.2-2 to 2.11.2-2): Will attempt migration (Any information below is purely informational)
• ruby-kgio/armhf (2.11.2-2 to 2.11.2-2)
  • Migration status for ruby-kgio/armhf (2.11.2-2 to 2.11.2-2): Will attempt migration (Any information below is purely informational)
• ruby-kgio/i386 (2.11.2-2 to 2.11.2-2)
  • Migration status for ruby-kgio/i386 (2.11.2-2 to 2.11.2-2): Will attempt migration (Any information below is purely informational)
• ruby-kgio/mips64el (2.11.2-2 to 2.11.2-2)
  • Migration status for ruby-kgio/mips64el (2.11.2-2 to 2.11.2-2): Will attempt migration (Any information below is purely informational)
• ruby-kgio/ppc64el (2.11.2-2 to 2.11.2-2)
  • Migration status for ruby-kgio/ppc64el (2.11.2-2 to 2.11.2-2): Will attempt migration (Any information below is purely informational)
• ruby-kgio/riscv64 (2.11.2-2 to 2.11.2-2)
  • Migration status for ruby-kgio/riscv64 (2.11.2-2 to 2.11.2-2): Will attempt migration (Any information below is purely informational)
• ruby-kgio/s390x (2.11.2-2 to 2.11.2-2)
  • Migration status for ruby-kgio/s390x (2.11.2-2 to 2.11.2-2): Will attempt migration (Any information below is purely informational)
• ruby-kyotocabinet/amd64 (1.34-2 to 1.34-2)
  • Migration status for ruby-kyotocabinet/amd64 (1.34-2 to 1.34-2): Will attempt migration (Any information below is purely informational)
• ruby-kyotocabinet/arm64 (1.34-2 to 1.34-2)
  • Migration status for ruby-kyotocabinet/arm64 (1.34-2 to 1.34-2): Will attempt migration (Any information below is purely informational)
• ruby-kyotocabinet/armel (1.34-2 to 1.34-2)
  • Migration status for ruby-kyotocabinet/armel (1.34-2 to 1.34-2): Will attempt migration (Any information below is purely informational)
• ruby-kyotocabinet/armhf (1.34-2 to 1.34-2)
  • Migration status for ruby-kyotocabinet/armhf (1.34-2 to 1.34-2): Will attempt migration (Any information below is purely informational)
• ruby-kyotocabinet/i386 (1.34-2 to 1.34-2)
  • Migration status for ruby-kyotocabinet/i386 (1.34-2 to 1.34-2): Will attempt migration (Any information below is purely informational)
• ruby-kyotocabinet/mips64el (1.34-2 to 1.34-2)
  • Migration status for ruby-kyotocabinet/mips64el (1.34-2 to 1.34-2): Will attempt migration (Any information below is purely informational)
• ruby-kyotocabinet/ppc64el (1.34-2 to 1.34-2)
  • Migration status for ruby-kyotocabinet/ppc64el (1.34-2 to 1.34-2): Will attempt migration (Any information below is purely informational)
• ruby-kyotocabinet/riscv64 (1.34-2 to 1.34-2)
  • Migration status for ruby-kyotocabinet/riscv64 (1.34-2 to 1.34-2): Will attempt migration (Any information below is purely informational)
• ruby-kyotocabinet/s390x (1.34-2 to 1.34-2)
  • Migration status for ruby-kyotocabinet/s390x (1.34-2 to 1.34-2): Will attempt migration (Any information below is purely informational)
• ruby-lapack/amd64 (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/amd64 (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
• ruby-lapack/arm64 (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/arm64 (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
• ruby-lapack/i386 (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/i386 (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
• ruby-lapack/mips64el (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/mips64el (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
• ruby-lapack/ppc64el (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/ppc64el (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
• ruby-levenshtein/amd64 (0.2.2-3 to 0.2.2-3)
  • Migration status for ruby-levenshtein/amd64 (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• ruby-levenshtein/arm64 (0.2.2-3 to 0.2.2-3)
  • Migration status for ruby-levenshtein/arm64 (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• ruby-levenshtein/armel (0.2.2-3 to 0.2.2-3)
  • Migration status for ruby-levenshtein/armel (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• ruby-levenshtein/armhf (0.2.2-3 to 0.2.2-3)
  • Migration status for ruby-levenshtein/armhf (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• ruby-levenshtein/i386 (0.2.2-3 to 0.2.2-3)
  • Migration status for ruby-levenshtein/i386 (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• ruby-levenshtein/mips64el (0.2.2-3 to 0.2.2-3)
  • Migration status for ruby-levenshtein/mips64el (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• ruby-levenshtein/ppc64el (0.2.2-3 to 0.2.2-3)
  • Migration status for ruby-levenshtein/ppc64el (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• ruby-levenshtein/riscv64 (0.2.2-3 to 0.2.2-3)
  • Migration status for ruby-levenshtein/riscv64 (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• ruby-levenshtein/s390x (0.2.2-3 to 0.2.2-3)
  • Migration status for ruby-levenshtein/s390x (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• ruby-libvirt/amd64 (0.8.4-1 to 0.8.4-1)
  • Migration status for ruby-libvirt/amd64 (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• ruby-libvirt/arm64 (0.8.4-1 to 0.8.4-1)
  • Migration status for ruby-libvirt/arm64 (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• ruby-libvirt/armel (0.8.4-1 to 0.8.4-1)
  • Migration status for ruby-libvirt/armel (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• ruby-libvirt/armhf (0.8.4-1 to 0.8.4-1)
  • Migration status for ruby-libvirt/armhf (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• ruby-libvirt/i386 (0.8.4-1 to 0.8.4-1)
  • Migration status for ruby-libvirt/i386 (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• ruby-libvirt/mips64el (0.8.4-1 to 0.8.4-1)
  • Migration status for ruby-libvirt/mips64el (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• ruby-libvirt/ppc64el (0.8.4-1 to 0.8.4-1)
  • Migration status for ruby-libvirt/ppc64el (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• ruby-libvirt/riscv64 (0.8.4-1 to 0.8.4-1)
  • Migration status for ruby-libvirt/riscv64 (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• ruby-libvirt/s390x (0.8.4-1 to 0.8.4-1)
  • Migration status for ruby-libvirt/s390x (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• ruby-libxml/amd64 (5.0.3-1 to 5.0.3-1)
  • Migration status for ruby-libxml/amd64 (5.0.3-1 to 5.0.3-1): Will attempt migration (Any information below is purely informational)
• ruby-libxml/arm64 (5.0.3-1 to 5.0.3-1)
  • Migration status for ruby-libxml/arm64 (5.0.3-1 to 5.0.3-1): Will attempt migration (Any information below is purely informational)
• ruby-libxml/armel (5.0.3-1 to 5.0.3-1)
  • Migration status for ruby-libxml/armel (5.0.3-1 to 5.0.3-1): Will attempt migration (Any information below is purely informational)
• ruby-libxml/armhf (5.0.3-1 to 5.0.3-1)
  • Migration status for ruby-libxml/armhf (5.0.3-1 to 5.0.3-1): Will attempt migration (Any information below is purely informational)
• ruby-libxml/i386 (5.0.3-1 to 5.0.3-1)
  • Migration status for ruby-libxml/i386 (5.0.3-1 to 5.0.3-1): Will attempt migration (Any information below is purely informational)
• ruby-libxml/mips64el (5.0.3-1 to 5.0.3-1)
  • Migration status for ruby-libxml/mips64el (5.0.3-1 to 5.0.3-1): Will attempt migration (Any information below is purely informational)
• ruby-libxml/ppc64el (5.0.3-1 to 5.0.3-1)
  • Migration status for ruby-libxml/ppc64el (5.0.3-1 to 5.0.3-1): Will attempt migration (Any information below is purely informational)
• ruby-libxml/riscv64 (5.0.3-1 to 5.0.3-1)
  • Migration status for ruby-libxml/riscv64 (5.0.3-1 to 5.0.3-1): Will attempt migration (Any information below is purely informational)
• ruby-libxml/s390x (5.0.3-1 to 5.0.3-1)
  • Migration status for ruby-libxml/s390x (5.0.3-1 to 5.0.3-1): Will attempt migration (Any information below is purely informational)
• ruby-liquid-c/amd64 (4.2.0-3 to 4.2.0-3)
  • Migration status for ruby-liquid-c/amd64 (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• ruby-liquid-c/arm64 (4.2.0-3 to 4.2.0-3)
  • Migration status for ruby-liquid-c/arm64 (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• ruby-liquid-c/armel (4.2.0-3 to 4.2.0-3)
  • Migration status for ruby-liquid-c/armel (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• ruby-liquid-c/armhf (4.2.0-3 to 4.2.0-3)
  • Migration status for ruby-liquid-c/armhf (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• ruby-liquid-c/i386 (4.2.0-3 to 4.2.0-3)
  • Migration status for ruby-liquid-c/i386 (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• ruby-liquid-c/mips64el (4.2.0-3 to 4.2.0-3)
  • Migration status for ruby-liquid-c/mips64el (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• ruby-liquid-c/ppc64el (4.2.0-3 to 4.2.0-3)
  • Migration status for ruby-liquid-c/ppc64el (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• ruby-liquid-c/riscv64 (4.2.0-3 to 4.2.0-3)
  • Migration status for ruby-liquid-c/riscv64 (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• ruby-mpi/amd64 (0.4.0-3 to 0.4.0-3)
  • Migration status for ruby-mpi/amd64 (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• ruby-mpi/arm64 (0.4.0-3 to 0.4.0-3)
  • Migration status for ruby-mpi/arm64 (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• ruby-mpi/armel (0.4.0-3 to 0.4.0-3)
  • Migration status for ruby-mpi/armel (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• ruby-mpi/i386 (0.4.0-3 to 0.4.0-3)
  • Migration status for ruby-mpi/i386 (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• ruby-mpi/mips64el (0.4.0-3 to 0.4.0-3)
  • Migration status for ruby-mpi/mips64el (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• ruby-mpi/ppc64el (0.4.0-3 to 0.4.0-3)
  • Migration status for ruby-mpi/ppc64el (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• ruby-mpi/riscv64 (0.4.0-3 to 0.4.0-3)
  • Migration status for ruby-mpi/riscv64 (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• ruby-msgpack/amd64 (1.7.2-1.1 to 1.7.2-1.1)
  • Migration status for ruby-msgpack/amd64 (1.7.2-1.1 to 1.7.2-1.1): Will attempt migration (Any information below is purely informational)
• ruby-msgpack/arm64 (1.7.2-1.1 to 1.7.2-1.1)
  • Migration status for ruby-msgpack/arm64 (1.7.2-1.1 to 1.7.2-1.1): Will attempt migration (Any information below is purely informational)
• ruby-msgpack/armel (1.7.2-1.1 to 1.7.2-1.1)
  • Migration status for ruby-msgpack/armel (1.7.2-1.1 to 1.7.2-1.1): Will attempt migration (Any information below is purely informational)
• ruby-msgpack/i386 (1.7.2-1.1 to 1.7.2-1.1)
  • Migration status for ruby-msgpack/i386 (1.7.2-1.1 to 1.7.2-1.1): Will attempt migration (Any information below is purely informational)
• ruby-msgpack/mips64el (1.7.2-1.1 to 1.7.2-1.1)
  • Migration status for ruby-msgpack/mips64el (1.7.2-1.1 to 1.7.2-1.1): Will attempt migration (Any information below is purely informational)
• ruby-msgpack/ppc64el (1.7.2-1.1 to 1.7.2-1.1)
  • Migration status for ruby-msgpack/ppc64el (1.7.2-1.1 to 1.7.2-1.1): Will attempt migration (Any information below is purely informational)
• ruby-msgpack/riscv64 (1.7.2-1.1 to 1.7.2-1.1)
  • Migration status for ruby-msgpack/riscv64 (1.7.2-1.1 to 1.7.2-1.1): Will attempt migration (Any information below is purely informational)
• ruby-multibitnums/amd64 (0.1.4-4 to 0.1.4-4)
  • Migration status for ruby-multibitnums/amd64 (0.1.4-4 to 0.1.4-4): Will attempt migration (Any information below is purely informational)
• ruby-multibitnums/arm64 (0.1.4-4 to 0.1.4-4)
  • Migration status for ruby-multibitnums/arm64 (0.1.4-4 to 0.1.4-4): Will attempt migration (Any information below is purely informational)
• ruby-multibitnums/armel (0.1.4-4 to 0.1.4-4)
  • Migration status for ruby-multibitnums/armel (0.1.4-4 to 0.1.4-4): Will attempt migration (Any information below is purely informational)
• ruby-multibitnums/i386 (0.1.4-4 to 0.1.4-4)
  • Migration status for ruby-multibitnums/i386 (0.1.4-4 to 0.1.4-4): Will attempt migration (Any information below is purely informational)
• ruby-multibitnums/mips64el (0.1.4-4 to 0.1.4-4)
  • Migration status for ruby-multibitnums/mips64el (0.1.4-4 to 0.1.4-4): Will attempt migration (Any information below is purely informational)
• ruby-multibitnums/ppc64el (0.1.4-4 to 0.1.4-4)
  • Migration status for ruby-multibitnums/ppc64el (0.1.4-4 to 0.1.4-4): Will attempt migration (Any information below is purely informational)
• ruby-multibitnums/riscv64 (0.1.4-4 to 0.1.4-4)
  • Migration status for ruby-multibitnums/riscv64 (0.1.4-4 to 0.1.4-4): Will attempt migration (Any information below is purely informational)
• ruby-murmurhash3/amd64 (0.1.6-2 to 0.1.6-2)
  • Migration status for ruby-murmurhash3/amd64 (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• ruby-murmurhash3/arm64 (0.1.6-2 to 0.1.6-2)
  • Migration status for ruby-murmurhash3/arm64 (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• ruby-murmurhash3/armel (0.1.6-2 to 0.1.6-2)
  • Migration status for ruby-murmurhash3/armel (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• ruby-murmurhash3/armhf (0.1.6-2 to 0.1.6-2)
  • Migration status for ruby-murmurhash3/armhf (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• ruby-murmurhash3/i386 (0.1.6-2 to 0.1.6-2)
  • Migration status for ruby-murmurhash3/i386 (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• ruby-murmurhash3/mips64el (0.1.6-2 to 0.1.6-2)
  • Migration status for ruby-murmurhash3/mips64el (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• ruby-murmurhash3/ppc64el (0.1.6-2 to 0.1.6-2)
  • Migration status for ruby-murmurhash3/ppc64el (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• ruby-murmurhash3/riscv64 (0.1.6-2 to 0.1.6-2)
  • Migration status for ruby-murmurhash3/riscv64 (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• ruby-murmurhash3/s390x (0.1.6-2 to 0.1.6-2)
  • Migration status for ruby-murmurhash3/s390x (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• ruby-mysql2/amd64 (0.5.5-3 to 0.5.5-3)
  • Migration status for ruby-mysql2/amd64 (0.5.5-3 to 0.5.5-3): Will attempt migration (Any information below is purely informational)
• ruby-mysql2/arm64 (0.5.5-3 to 0.5.5-3)
  • Migration status for ruby-mysql2/arm64 (0.5.5-3 to 0.5.5-3): Will attempt migration (Any information below is purely informational)
• ruby-mysql2/armel (0.5.5-3 to 0.5.5-3)
  • Migration status for ruby-mysql2/armel (0.5.5-3 to 0.5.5-3): Will attempt migration (Any information below is purely informational)
• ruby-mysql2/armhf (0.5.5-3 to 0.5.5-3)
  • Migration status for ruby-mysql2/armhf (0.5.5-3 to 0.5.5-3): Will attempt migration (Any information below is purely informational)
• ruby-mysql2/i386 (0.5.5-3 to 0.5.5-3)
  • Migration status for ruby-mysql2/i386 (0.5.5-3 to 0.5.5-3): Will attempt migration (Any information below is purely informational)
• ruby-mysql2/mips64el (0.5.5-3 to 0.5.5-3)
  • Migration status for ruby-mysql2/mips64el (0.5.5-3 to 0.5.5-3): Will attempt migration (Any information below is purely informational)
• ruby-mysql2/ppc64el (0.5.5-3 to 0.5.5-3)
  • Migration status for ruby-mysql2/ppc64el (0.5.5-3 to 0.5.5-3): Will attempt migration (Any information below is purely informational)
• ruby-mysql2/riscv64 (0.5.5-3 to 0.5.5-3)
  • Migration status for ruby-mysql2/riscv64 (0.5.5-3 to 0.5.5-3): Will attempt migration (Any information below is purely informational)
• ruby-mysql2/s390x (0.5.5-3 to 0.5.5-3)
  • Migration status for ruby-mysql2/s390x (0.5.5-3 to 0.5.5-3): Will attempt migration (Any information below is purely informational)
• ruby-narray/amd64 (0.6.1.2-6 to 0.6.1.2-6)
  • Migration status for ruby-narray/amd64 (0.6.1.2-6 to 0.6.1.2-6): Will attempt migration (Any information below is purely informational)
• ruby-narray/arm64 (0.6.1.2-6 to 0.6.1.2-6)
  • Migration status for ruby-narray/arm64 (0.6.1.2-6 to 0.6.1.2-6): Will attempt migration (Any information below is purely informational)
• ruby-narray/armel (0.6.1.2-6 to 0.6.1.2-6)
  • Migration status for ruby-narray/armel (0.6.1.2-6 to 0.6.1.2-6): Will attempt migration (Any information below is purely informational)
• ruby-narray/armhf (0.6.1.2-6 to 0.6.1.2-6)
  • Migration status for ruby-narray/armhf (0.6.1.2-6 to 0.6.1.2-6): Will attempt migration (Any information below is purely informational)
• ruby-narray/i386 (0.6.1.2-6 to 0.6.1.2-6)
  • Migration status for ruby-narray/i386 (0.6.1.2-6 to 0.6.1.2-6): Will attempt migration (Any information below is purely informational)
• ruby-narray/mips64el (0.6.1.2-6 to 0.6.1.2-6)
  • Migration status for ruby-narray/mips64el (0.6.1.2-6 to 0.6.1.2-6): Will attempt migration (Any information below is purely informational)
• ruby-narray/ppc64el (0.6.1.2-6 to 0.6.1.2-6)
  • Migration status for ruby-narray/ppc64el (0.6.1.2-6 to 0.6.1.2-6): Will attempt migration (Any information below is purely informational)
• ruby-narray/riscv64 (0.6.1.2-6 to 0.6.1.2-6)
  • Migration status for ruby-narray/riscv64 (0.6.1.2-6 to 0.6.1.2-6): Will attempt migration (Any information below is purely informational)
• ruby-narray/s390x (0.6.1.2-6 to 0.6.1.2-6)
  • Migration status for ruby-narray/s390x (0.6.1.2-6 to 0.6.1.2-6): Will attempt migration (Any information below is purely informational)
• ruby-ncurses/amd64 (1.4.11-1 to 1.4.11-1)
  • Migration status for ruby-ncurses/amd64 (1.4.11-1 to 1.4.11-1): Will attempt migration (Any information below is purely informational)
• ruby-ncurses/arm64 (1.4.11-1 to 1.4.11-1)
  • Migration status for ruby-ncurses/arm64 (1.4.11-1 to 1.4.11-1): Will attempt migration (Any information below is purely informational)
• ruby-ncurses/armel (1.4.11-1 to 1.4.11-1)
  • Migration status for ruby-ncurses/armel (1.4.11-1 to 1.4.11-1): Will attempt migration (Any information below is purely informational)
• ruby-ncurses/armhf (1.4.11-1 to 1.4.11-1)
  • Migration status for ruby-ncurses/armhf (1.4.11-1 to 1.4.11-1): Will attempt migration (Any information below is purely informational)
• ruby-ncurses/i386 (1.4.11-1 to 1.4.11-1)
  • Migration status for ruby-ncurses/i386 (1.4.11-1 to 1.4.11-1): Will attempt migration (Any information below is purely informational)
• ruby-ncurses/mips64el (1.4.11-1 to 1.4.11-1)
  • Migration status for ruby-ncurses/mips64el (1.4.11-1 to 1.4.11-1): Will attempt migration (Any information below is purely informational)
• ruby-ncurses/ppc64el (1.4.11-1 to 1.4.11-1)
  • Migration status for ruby-ncurses/ppc64el (1.4.11-1 to 1.4.11-1): Will attempt migration (Any information below is purely informational)
• ruby-ncurses/riscv64 (1.4.11-1 to 1.4.11-1)
  • Migration status for ruby-ncurses/riscv64 (1.4.11-1 to 1.4.11-1): Will attempt migration (Any information below is purely informational)
• ruby-ncurses/s390x (1.4.11-1 to 1.4.11-1)
  • Migration status for ruby-ncurses/s390x (1.4.11-1 to 1.4.11-1): Will attempt migration (Any information below is purely informational)
• ruby-netcdf/amd64 (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-netcdf/amd64 (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-netcdf/arm64 (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-netcdf/arm64 (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-netcdf/armel (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-netcdf/armel (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-netcdf/i386 (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-netcdf/i386 (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-netcdf/mips64el (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-netcdf/mips64el (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-netcdf/ppc64el (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-netcdf/ppc64el (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-netcdf/riscv64 (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-netcdf/riscv64 (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-nfc/amd64 (3.1.2-3 to 3.1.2-3)
  • Migration status for ruby-nfc/amd64 (3.1.2-3 to 3.1.2-3): Will attempt migration (Any information below is purely informational)
• ruby-nfc/arm64 (3.1.2-3 to 3.1.2-3)
  • Migration status for ruby-nfc/arm64 (3.1.2-3 to 3.1.2-3): Will attempt migration (Any information below is purely informational)
• ruby-nfc/armel (3.1.2-3 to 3.1.2-3)
  • Migration status for ruby-nfc/armel (3.1.2-3 to 3.1.2-3): Will attempt migration (Any information below is purely informational)
• ruby-nfc/armhf (3.1.2-3 to 3.1.2-3)
  • Migration status for ruby-nfc/armhf (3.1.2-3 to 3.1.2-3): Will attempt migration (Any information below is purely informational)
• ruby-nfc/i386 (3.1.2-3 to 3.1.2-3)
  • Migration status for ruby-nfc/i386 (3.1.2-3 to 3.1.2-3): Will attempt migration (Any information below is purely informational)
• ruby-nfc/mips64el (3.1.2-3 to 3.1.2-3)
  • Migration status for ruby-nfc/mips64el (3.1.2-3 to 3.1.2-3): Will attempt migration (Any information below is purely informational)
• ruby-nfc/ppc64el (3.1.2-3 to 3.1.2-3)
  • Migration status for ruby-nfc/ppc64el (3.1.2-3 to 3.1.2-3): Will attempt migration (Any information below is purely informational)
• ruby-nfc/riscv64 (3.1.2-3 to 3.1.2-3)
  • Migration status for ruby-nfc/riscv64 (3.1.2-3 to 3.1.2-3): Will attempt migration (Any information below is purely informational)
• ruby-nfc/s390x (3.1.2-3 to 3.1.2-3)
  • Migration status for ruby-nfc/s390x (3.1.2-3 to 3.1.2-3): Will attempt migration (Any information below is purely informational)
• ruby-nio4r/amd64 (2.7.3-1 to 2.7.3-1)
  • Migration status for ruby-nio4r/amd64 (2.7.3-1 to 2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-nio4r/arm64 (2.7.3-1 to 2.7.3-1)
  • Migration status for ruby-nio4r/arm64 (2.7.3-1 to 2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-nio4r/armel (2.7.3-1 to 2.7.3-1)
  • Migration status for ruby-nio4r/armel (2.7.3-1 to 2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-nio4r/armhf (2.7.3-1 to 2.7.3-1)
  • Migration status for ruby-nio4r/armhf (2.7.3-1 to 2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-nio4r/i386 (2.7.3-1 to 2.7.3-1)
  • Migration status for ruby-nio4r/i386 (2.7.3-1 to 2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-nio4r/mips64el (2.7.3-1 to 2.7.3-1)
  • Migration status for ruby-nio4r/mips64el (2.7.3-1 to 2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-nio4r/ppc64el (2.7.3-1 to 2.7.3-1)
  • Migration status for ruby-nio4r/ppc64el (2.7.3-1 to 2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-nio4r/riscv64 (2.7.3-1 to 2.7.3-1)
  • Migration status for ruby-nio4r/riscv64 (2.7.3-1 to 2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-nio4r/s390x (2.7.3-1 to 2.7.3-1)
  • Migration status for ruby-nio4r/s390x (2.7.3-1 to 2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-nokogiri/amd64 (1.18.2+dfsg-1 to 1.18.2+dfsg-1)
  • Migration status for ruby-nokogiri/amd64 (1.18.2+dfsg-1 to 1.18.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-nokogiri/arm64 (1.18.2+dfsg-1 to 1.18.2+dfsg-1)
  • Migration status for ruby-nokogiri/arm64 (1.18.2+dfsg-1 to 1.18.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-nokogiri/armel (1.18.2+dfsg-1 to 1.18.2+dfsg-1)
  • Migration status for ruby-nokogiri/armel (1.18.2+dfsg-1 to 1.18.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-nokogiri/armhf (1.18.2+dfsg-1 to 1.18.2+dfsg-1)
  • Migration status for ruby-nokogiri/armhf (1.18.2+dfsg-1 to 1.18.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-nokogiri/i386 (1.18.2+dfsg-1 to 1.18.2+dfsg-1)
  • Migration status for ruby-nokogiri/i386 (1.18.2+dfsg-1 to 1.18.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-nokogiri/mips64el (1.18.2+dfsg-1 to 1.18.2+dfsg-1)
  • Migration status for ruby-nokogiri/mips64el (1.18.2+dfsg-1 to 1.18.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-nokogiri/ppc64el (1.18.2+dfsg-1 to 1.18.2+dfsg-1)
  • Migration status for ruby-nokogiri/ppc64el (1.18.2+dfsg-1 to 1.18.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-nokogiri/riscv64 (1.18.2+dfsg-1 to 1.18.2+dfsg-1)
  • Migration status for ruby-nokogiri/riscv64 (1.18.2+dfsg-1 to 1.18.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-nokogiri/s390x (1.18.2+dfsg-1 to 1.18.2+dfsg-1)
  • Migration status for ruby-nokogiri/s390x (1.18.2+dfsg-1 to 1.18.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-odbc/amd64 (0.999992-1 to 0.999992-1)
  • Migration status for ruby-odbc/amd64 (0.999992-1 to 0.999992-1): Will attempt migration (Any information below is purely informational)
• ruby-odbc/arm64 (0.999992-1 to 0.999992-1)
  • Migration status for ruby-odbc/arm64 (0.999992-1 to 0.999992-1): Will attempt migration (Any information below is purely informational)
• ruby-odbc/armel (0.999992-1 to 0.999992-1)
  • Migration status for ruby-odbc/armel (0.999992-1 to 0.999992-1): Will attempt migration (Any information below is purely informational)
• ruby-odbc/armhf (0.999992-1 to 0.999992-1)
  • Migration status for ruby-odbc/armhf (0.999992-1 to 0.999992-1): Will attempt migration (Any information below is purely informational)
• ruby-odbc/i386 (0.999992-1 to 0.999992-1)
  • Migration status for ruby-odbc/i386 (0.999992-1 to 0.999992-1): Will attempt migration (Any information below is purely informational)
• ruby-odbc/mips64el (0.999992-1 to 0.999992-1)
  • Migration status for ruby-odbc/mips64el (0.999992-1 to 0.999992-1): Will attempt migration (Any information below is purely informational)
• ruby-odbc/ppc64el (0.999992-1 to 0.999992-1)
  • Migration status for ruby-odbc/ppc64el (0.999992-1 to 0.999992-1): Will attempt migration (Any information below is purely informational)
• ruby-odbc/riscv64 (0.999992-1 to 0.999992-1)
  • Migration status for ruby-odbc/riscv64 (0.999992-1 to 0.999992-1): Will attempt migration (Any information below is purely informational)
• ruby-odbc/s390x (0.999992-1 to 0.999992-1)
  • Migration status for ruby-odbc/s390x (0.999992-1 to 0.999992-1): Will attempt migration (Any information below is purely informational)
• ruby-oily-png/amd64 (1.2.1~dfsg-4 to 1.2.1~dfsg-4)
  • Migration status for ruby-oily-png/amd64 (1.2.1~dfsg-4 to 1.2.1~dfsg-4): Will attempt migration (Any information below is purely informational)
• ruby-oily-png/arm64 (1.2.1~dfsg-4 to 1.2.1~dfsg-4)
  • Migration status for ruby-oily-png/arm64 (1.2.1~dfsg-4 to 1.2.1~dfsg-4): Will attempt migration (Any information below is purely informational)
• ruby-oily-png/armel (1.2.1~dfsg-4 to 1.2.1~dfsg-4)
  • Migration status for ruby-oily-png/armel (1.2.1~dfsg-4 to 1.2.1~dfsg-4): Will attempt migration (Any information below is purely informational)
• ruby-oily-png/armhf (1.2.1~dfsg-4 to 1.2.1~dfsg-4)
  • Migration status for ruby-oily-png/armhf (1.2.1~dfsg-4 to 1.2.1~dfsg-4): Will attempt migration (Any information below is purely informational)
• ruby-oily-png/i386 (1.2.1~dfsg-4 to 1.2.1~dfsg-4)
  • Migration status for ruby-oily-png/i386 (1.2.1~dfsg-4 to 1.2.1~dfsg-4): Will attempt migration (Any information below is purely informational)
• ruby-oily-png/mips64el (1.2.1~dfsg-4 to 1.2.1~dfsg-4)
  • Migration status for ruby-oily-png/mips64el (1.2.1~dfsg-4 to 1.2.1~dfsg-4): Will attempt migration (Any information below is purely informational)
• ruby-oily-png/ppc64el (1.2.1~dfsg-4 to 1.2.1~dfsg-4)
  • Migration status for ruby-oily-png/ppc64el (1.2.1~dfsg-4 to 1.2.1~dfsg-4): Will attempt migration (Any information below is purely informational)
• ruby-oily-png/riscv64 (1.2.1~dfsg-4 to 1.2.1~dfsg-4)
  • Migration status for ruby-oily-png/riscv64 (1.2.1~dfsg-4 to 1.2.1~dfsg-4): Will attempt migration (Any information below is purely informational)
• ruby-oily-png/s390x (1.2.1~dfsg-4 to 1.2.1~dfsg-4)
  • Migration status for ruby-oily-png/s390x (1.2.1~dfsg-4 to 1.2.1~dfsg-4): Will attempt migration (Any information below is purely informational)
• ruby-oj-introspect/amd64 (0.7.1-3 to 0.7.1-3)
  • Migration status for ruby-oj-introspect/amd64 (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• ruby-oj-introspect/arm64 (0.7.1-3 to 0.7.1-3)
  • Migration status for ruby-oj-introspect/arm64 (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• ruby-oj-introspect/armel (0.7.1-3 to 0.7.1-3)
  • Migration status for ruby-oj-introspect/armel (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• ruby-oj-introspect/i386 (0.7.1-3 to 0.7.1-3)
  • Migration status for ruby-oj-introspect/i386 (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• ruby-oj-introspect/mips64el (0.7.1-3 to 0.7.1-3)
  • Migration status for ruby-oj-introspect/mips64el (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• ruby-oj-introspect/ppc64el (0.7.1-3 to 0.7.1-3)
  • Migration status for ruby-oj-introspect/ppc64el (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• ruby-oj-introspect/riscv64 (0.7.1-3 to 0.7.1-3)
  • Migration status for ruby-oj-introspect/riscv64 (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• ruby-oj/amd64 (3.16.3-1 to 3.16.3-1)
  • Migration status for ruby-oj/amd64 (3.16.3-1 to 3.16.3-1): Will attempt migration (Any information below is purely informational)
• ruby-oj/arm64 (3.16.3-1 to 3.16.3-1)
  • Migration status for ruby-oj/arm64 (3.16.3-1 to 3.16.3-1): Will attempt migration (Any information below is purely informational)
• ruby-oj/armel (3.16.3-1 to 3.16.3-1)
  • Migration status for ruby-oj/armel (3.16.3-1 to 3.16.3-1): Will attempt migration (Any information below is purely informational)
• ruby-oj/armhf (3.16.3-1 to 3.16.3-1)
  • Migration status for ruby-oj/armhf (3.16.3-1 to 3.16.3-1): Will attempt migration (Any information below is purely informational)
• ruby-oj/i386 (3.16.3-1 to 3.16.3-1)
  • Migration status for ruby-oj/i386 (3.16.3-1 to 3.16.3-1): Will attempt migration (Any information below is purely informational)
• ruby-oj/mips64el (3.16.3-1 to 3.16.3-1)
  • Migration status for ruby-oj/mips64el (3.16.3-1 to 3.16.3-1): Will attempt migration (Any information below is purely informational)
• ruby-oj/ppc64el (3.16.3-1 to 3.16.3-1)
  • Migration status for ruby-oj/ppc64el (3.16.3-1 to 3.16.3-1): Will attempt migration (Any information below is purely informational)
• ruby-oj/riscv64 (3.16.3-1 to 3.16.3-1)
  • Migration status for ruby-oj/riscv64 (3.16.3-1 to 3.16.3-1): Will attempt migration (Any information below is purely informational)
• ruby-oj/s390x (3.16.3-1 to 3.16.3-1)
  • Migration status for ruby-oj/s390x (3.16.3-1 to 3.16.3-1): Will attempt migration (Any information below is purely informational)
• ruby-ox/amd64 (2.14.17-1 to 2.14.17-1)
  • Migration status for ruby-ox/amd64 (2.14.17-1 to 2.14.17-1): Will attempt migration (Any information below is purely informational)
• ruby-ox/arm64 (2.14.17-1 to 2.14.17-1)
  • Migration status for ruby-ox/arm64 (2.14.17-1 to 2.14.17-1): Will attempt migration (Any information below is purely informational)
• ruby-ox/armel (2.14.17-1 to 2.14.17-1)
  • Migration status for ruby-ox/armel (2.14.17-1 to 2.14.17-1): Will attempt migration (Any information below is purely informational)
• ruby-ox/armhf (2.14.17-1 to 2.14.17-1)
  • Migration status for ruby-ox/armhf (2.14.17-1 to 2.14.17-1): Will attempt migration (Any information below is purely informational)
• ruby-ox/i386 (2.14.17-1 to 2.14.17-1)
  • Migration status for ruby-ox/i386 (2.14.17-1 to 2.14.17-1): Will attempt migration (Any information below is purely informational)
• ruby-ox/mips64el (2.14.17-1 to 2.14.17-1)
  • Migration status for ruby-ox/mips64el (2.14.17-1 to 2.14.17-1): Will attempt migration (Any information below is purely informational)
• ruby-ox/ppc64el (2.14.17-1 to 2.14.17-1)
  • Migration status for ruby-ox/ppc64el (2.14.17-1 to 2.14.17-1): Will attempt migration (Any information below is purely informational)
• ruby-ox/riscv64 (2.14.17-1 to 2.14.17-1)
  • Migration status for ruby-ox/riscv64 (2.14.17-1 to 2.14.17-1): Will attempt migration (Any information below is purely informational)
• ruby-ox/s390x (2.14.17-1 to 2.14.17-1)
  • Migration status for ruby-ox/s390x (2.14.17-1 to 2.14.17-1): Will attempt migration (Any information below is purely informational)
• ruby-password/amd64 (0.5.3-5 to 0.5.3-5)
  • Migration status for ruby-password/amd64 (0.5.3-5 to 0.5.3-5): Will attempt migration (Any information below is purely informational)
• ruby-password/arm64 (0.5.3-5 to 0.5.3-5)
  • Migration status for ruby-password/arm64 (0.5.3-5 to 0.5.3-5): Will attempt migration (Any information below is purely informational)
• ruby-password/armel (0.5.3-5 to 0.5.3-5)
  • Migration status for ruby-password/armel (0.5.3-5 to 0.5.3-5): Will attempt migration (Any information below is purely informational)
• ruby-password/i386 (0.5.3-5 to 0.5.3-5)
  • Migration status for ruby-password/i386 (0.5.3-5 to 0.5.3-5): Will attempt migration (Any information below is purely informational)
• ruby-password/mips64el (0.5.3-5 to 0.5.3-5)
  • Migration status for ruby-password/mips64el (0.5.3-5 to 0.5.3-5): Will attempt migration (Any information below is purely informational)
• ruby-password/ppc64el (0.5.3-5 to 0.5.3-5)
  • Migration status for ruby-password/ppc64el (0.5.3-5 to 0.5.3-5): Will attempt migration (Any information below is purely informational)
• ruby-password/riscv64 (0.5.3-5 to 0.5.3-5)
  • Migration status for ruby-password/riscv64 (0.5.3-5 to 0.5.3-5): Will attempt migration (Any information below is purely informational)
• ruby-pcaprub/amd64 (0.13.3-1 to 0.13.3-1)
  • Migration status for ruby-pcaprub/amd64 (0.13.3-1 to 0.13.3-1): Will attempt migration (Any information below is purely informational)
• ruby-pcaprub/arm64 (0.13.3-1 to 0.13.3-1)
  • Migration status for ruby-pcaprub/arm64 (0.13.3-1 to 0.13.3-1): Will attempt migration (Any information below is purely informational)
• ruby-pcaprub/armel (0.13.3-1 to 0.13.3-1)
  • Migration status for ruby-pcaprub/armel (0.13.3-1 to 0.13.3-1): Will attempt migration (Any information below is purely informational)
• ruby-pcaprub/armhf (0.13.3-1 to 0.13.3-1)
  • Migration status for ruby-pcaprub/armhf (0.13.3-1 to 0.13.3-1): Will attempt migration (Any information below is purely informational)
• ruby-pcaprub/i386 (0.13.3-1 to 0.13.3-1)
  • Migration status for ruby-pcaprub/i386 (0.13.3-1 to 0.13.3-1): Will attempt migration (Any information below is purely informational)
• ruby-pcaprub/mips64el (0.13.3-1 to 0.13.3-1)
  • Migration status for ruby-pcaprub/mips64el (0.13.3-1 to 0.13.3-1): Will attempt migration (Any information below is purely informational)
• ruby-pcaprub/ppc64el (0.13.3-1 to 0.13.3-1)
  • Migration status for ruby-pcaprub/ppc64el (0.13.3-1 to 0.13.3-1): Will attempt migration (Any information below is purely informational)
• ruby-pcaprub/riscv64 (0.13.3-1 to 0.13.3-1)
  • Migration status for ruby-pcaprub/riscv64 (0.13.3-1 to 0.13.3-1): Will attempt migration (Any information below is purely informational)
• ruby-pcaprub/s390x (0.13.3-1 to 0.13.3-1)
  • Migration status for ruby-pcaprub/s390x (0.13.3-1 to 0.13.3-1): Will attempt migration (Any information below is purely informational)
• ruby-pg-query/amd64 (4.2.3-2 to 4.2.3-2)
  • Migration status for ruby-pg-query/amd64 (4.2.3-2 to 4.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-pg-query/arm64 (4.2.3-2 to 4.2.3-2)
  • Migration status for ruby-pg-query/arm64 (4.2.3-2 to 4.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-pg-query/armel (4.2.3-2 to 4.2.3-2)
  • Migration status for ruby-pg-query/armel (4.2.3-2 to 4.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-pg-query/i386 (4.2.3-2 to 4.2.3-2)
  • Migration status for ruby-pg-query/i386 (4.2.3-2 to 4.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-pg-query/mips64el (4.2.3-2 to 4.2.3-2)
  • Migration status for ruby-pg-query/mips64el (4.2.3-2 to 4.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-pg-query/ppc64el (4.2.3-2 to 4.2.3-2)
  • Migration status for ruby-pg-query/ppc64el (4.2.3-2 to 4.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-pg-query/riscv64 (4.2.3-2 to 4.2.3-2)
  • Migration status for ruby-pg-query/riscv64 (4.2.3-2 to 4.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-pg/amd64 (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-pg/amd64 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-pg/arm64 (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-pg/arm64 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-pg/armel (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-pg/armel (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-pg/armhf (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-pg/armhf (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-pg/i386 (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-pg/i386 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-pg/mips64el (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-pg/mips64el (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-pg/ppc64el (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-pg/ppc64el (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-pg/riscv64 (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-pg/riscv64 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-pg/s390x (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-pg/s390x (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-pgplot/amd64 (0.2.0-4 to 0.2.0-4)
  • Migration status for ruby-pgplot/amd64 (0.2.0-4 to 0.2.0-4): Will attempt migration (Any information below is purely informational)
• ruby-pgplot/arm64 (0.2.0-4 to 0.2.0-4)
  • Migration status for ruby-pgplot/arm64 (0.2.0-4 to 0.2.0-4): Will attempt migration (Any information below is purely informational)
• ruby-pgplot/armel (0.2.0-4 to 0.2.0-4)
  • Migration status for ruby-pgplot/armel (0.2.0-4 to 0.2.0-4): Will attempt migration (Any information below is purely informational)
• ruby-pgplot/i386 (0.2.0-4 to 0.2.0-4)
  • Migration status for ruby-pgplot/i386 (0.2.0-4 to 0.2.0-4): Will attempt migration (Any information below is purely informational)
• ruby-pgplot/mips64el (0.2.0-4 to 0.2.0-4)
  • Migration status for ruby-pgplot/mips64el (0.2.0-4 to 0.2.0-4): Will attempt migration (Any information below is purely informational)
• ruby-pgplot/ppc64el (0.2.0-4 to 0.2.0-4)
  • Migration status for ruby-pgplot/ppc64el (0.2.0-4 to 0.2.0-4): Will attempt migration (Any information below is purely informational)
• ruby-pgplot/riscv64 (0.2.0-4 to 0.2.0-4)
  • Migration status for ruby-pgplot/riscv64 (0.2.0-4 to 0.2.0-4): Will attempt migration (Any information below is purely informational)
• ruby-posix-spawn/amd64 (0.3.15-3 to 0.3.15-3)
  • Migration status for ruby-posix-spawn/amd64 (0.3.15-3 to 0.3.15-3): Will attempt migration (Any information below is purely informational)
• ruby-posix-spawn/arm64 (0.3.15-3 to 0.3.15-3)
  • Migration status for ruby-posix-spawn/arm64 (0.3.15-3 to 0.3.15-3): Will attempt migration (Any information below is purely informational)
• ruby-posix-spawn/armel (0.3.15-3 to 0.3.15-3)
  • Migration status for ruby-posix-spawn/armel (0.3.15-3 to 0.3.15-3): Will attempt migration (Any information below is purely informational)
• ruby-posix-spawn/armhf (0.3.15-3 to 0.3.15-3)
  • Migration status for ruby-posix-spawn/armhf (0.3.15-3 to 0.3.15-3): Will attempt migration (Any information below is purely informational)
• ruby-posix-spawn/i386 (0.3.15-3 to 0.3.15-3)
  • Migration status for ruby-posix-spawn/i386 (0.3.15-3 to 0.3.15-3): Will attempt migration (Any information below is purely informational)
• ruby-posix-spawn/mips64el (0.3.15-3 to 0.3.15-3)
  • Migration status for ruby-posix-spawn/mips64el (0.3.15-3 to 0.3.15-3): Will attempt migration (Any information below is purely informational)
• ruby-posix-spawn/ppc64el (0.3.15-3 to 0.3.15-3)
  • Migration status for ruby-posix-spawn/ppc64el (0.3.15-3 to 0.3.15-3): Will attempt migration (Any information below is purely informational)
• ruby-posix-spawn/riscv64 (0.3.15-3 to 0.3.15-3)
  • Migration status for ruby-posix-spawn/riscv64 (0.3.15-3 to 0.3.15-3): Will attempt migration (Any information below is purely informational)
• ruby-posix-spawn/s390x (0.3.15-3 to 0.3.15-3)
  • Migration status for ruby-posix-spawn/s390x (0.3.15-3 to 0.3.15-3): Will attempt migration (Any information below is purely informational)
• ruby-prof/amd64 (1.7.0-1 to 1.7.0-1)
  • Migration status for ruby-prof/amd64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ruby-prof/arm64 (1.7.0-1 to 1.7.0-1)
  • Migration status for ruby-prof/arm64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ruby-prof/armel (1.7.0-1 to 1.7.0-1)
  • Migration status for ruby-prof/armel (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ruby-prof/armhf (1.7.0-1 to 1.7.0-1)
  • Migration status for ruby-prof/armhf (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ruby-prof/i386 (1.7.0-1 to 1.7.0-1)
  • Migration status for ruby-prof/i386 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ruby-prof/mips64el (1.7.0-1 to 1.7.0-1)
  • Migration status for ruby-prof/mips64el (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ruby-prof/ppc64el (1.7.0-1 to 1.7.0-1)
  • Migration status for ruby-prof/ppc64el (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ruby-prof/riscv64 (1.7.0-1 to 1.7.0-1)
  • Migration status for ruby-prof/riscv64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ruby-prof/s390x (1.7.0-1 to 1.7.0-1)
  • Migration status for ruby-prof/s390x (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• ruby-psych/amd64 (5.0.2-3 to 5.0.2-3)
  • Migration status for ruby-psych/amd64 (5.0.2-3 to 5.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-psych/arm64 (5.0.2-3 to 5.0.2-3)
  • Migration status for ruby-psych/arm64 (5.0.2-3 to 5.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-psych/armel (5.0.2-3 to 5.0.2-3)
  • Migration status for ruby-psych/armel (5.0.2-3 to 5.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-psych/armhf (5.0.2-3 to 5.0.2-3)
  • Migration status for ruby-psych/armhf (5.0.2-3 to 5.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-psych/i386 (5.0.2-3 to 5.0.2-3)
  • Migration status for ruby-psych/i386 (5.0.2-3 to 5.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-psych/mips64el (5.0.2-3 to 5.0.2-3)
  • Migration status for ruby-psych/mips64el (5.0.2-3 to 5.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-psych/ppc64el (5.0.2-3 to 5.0.2-3)
  • Migration status for ruby-psych/ppc64el (5.0.2-3 to 5.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-psych/riscv64 (5.0.2-3 to 5.0.2-3)
  • Migration status for ruby-psych/riscv64 (5.0.2-3 to 5.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-psych/s390x (5.0.2-3 to 5.0.2-3)
  • Migration status for ruby-psych/s390x (5.0.2-3 to 5.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-raindrops/amd64 (0.20.0-2 to 0.20.0-2)
  • Migration status for ruby-raindrops/amd64 (0.20.0-2 to 0.20.0-2): Will attempt migration (Any information below is purely informational)
• ruby-raindrops/arm64 (0.20.0-2 to 0.20.0-2)
  • Migration status for ruby-raindrops/arm64 (0.20.0-2 to 0.20.0-2): Will attempt migration (Any information below is purely informational)
• ruby-raindrops/armel (0.20.0-2 to 0.20.0-2)
  • Migration status for ruby-raindrops/armel (0.20.0-2 to 0.20.0-2): Will attempt migration (Any information below is purely informational)
• ruby-raindrops/armhf (0.20.0-2 to 0.20.0-2)
  • Migration status for ruby-raindrops/armhf (0.20.0-2 to 0.20.0-2): Will attempt migration (Any information below is purely informational)
• ruby-raindrops/i386 (0.20.0-2 to 0.20.0-2)
  • Migration status for ruby-raindrops/i386 (0.20.0-2 to 0.20.0-2): Will attempt migration (Any information below is purely informational)
• ruby-raindrops/mips64el (0.20.0-2 to 0.20.0-2)
  • Migration status for ruby-raindrops/mips64el (0.20.0-2 to 0.20.0-2): Will attempt migration (Any information below is purely informational)
• ruby-raindrops/ppc64el (0.20.0-2 to 0.20.0-2)
  • Migration status for ruby-raindrops/ppc64el (0.20.0-2 to 0.20.0-2): Will attempt migration (Any information below is purely informational)
• ruby-raindrops/riscv64 (0.20.0-2 to 0.20.0-2)
  • Migration status for ruby-raindrops/riscv64 (0.20.0-2 to 0.20.0-2): Will attempt migration (Any information below is purely informational)
• ruby-raindrops/s390x (0.20.0-2 to 0.20.0-2)
  • Migration status for ruby-raindrops/s390x (0.20.0-2 to 0.20.0-2): Will attempt migration (Any information below is purely informational)
• ruby-rblineprof/amd64 (0.3.7-3 to 0.3.7-3)
  • Migration status for ruby-rblineprof/amd64 (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• ruby-rblineprof/arm64 (0.3.7-3 to 0.3.7-3)
  • Migration status for ruby-rblineprof/arm64 (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• ruby-rblineprof/armel (0.3.7-3 to 0.3.7-3)
  • Migration status for ruby-rblineprof/armel (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• ruby-rblineprof/armhf (0.3.7-3 to 0.3.7-3)
  • Migration status for ruby-rblineprof/armhf (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• ruby-rblineprof/i386 (0.3.7-3 to 0.3.7-3)
  • Migration status for ruby-rblineprof/i386 (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• ruby-rblineprof/mips64el (0.3.7-3 to 0.3.7-3)
  • Migration status for ruby-rblineprof/mips64el (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• ruby-rblineprof/ppc64el (0.3.7-3 to 0.3.7-3)
  • Migration status for ruby-rblineprof/ppc64el (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• ruby-rblineprof/riscv64 (0.3.7-3 to 0.3.7-3)
  • Migration status for ruby-rblineprof/riscv64 (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• ruby-rblineprof/s390x (0.3.7-3 to 0.3.7-3)
  • Migration status for ruby-rblineprof/s390x (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• ruby-rbtrace/amd64 (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/amd64 (0.5.1-1.1 to 0.5.1-1.1): Will attempt migration (Any information below is purely informational)
• ruby-rbtrace/arm64 (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/arm64 (0.5.1-1.1 to 0.5.1-1.1): Will attempt migration (Any information below is purely informational)
• ruby-rbtrace/armel (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/armel (0.5.1-1.1 to 0.5.1-1.1): Will attempt migration (Any information below is purely informational)
• ruby-rbtrace/i386 (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/i386 (0.5.1-1.1 to 0.5.1-1.1): Will attempt migration (Any information below is purely informational)
• ruby-rbtrace/mips64el (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/mips64el (0.5.1-1.1 to 0.5.1-1.1): Will attempt migration (Any information below is purely informational)
• ruby-rbtrace/ppc64el (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/ppc64el (0.5.1-1.1 to 0.5.1-1.1): Will attempt migration (Any information below is purely informational)
• ruby-rbtrace/riscv64 (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/riscv64 (0.5.1-1.1 to 0.5.1-1.1): Will attempt migration (Any information below is purely informational)
• ruby-rbtree/amd64 (0.4.6-1 to 0.4.6-1)
  • Migration status for ruby-rbtree/amd64 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-rbtree/arm64 (0.4.6-1 to 0.4.6-1)
  • Migration status for ruby-rbtree/arm64 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-rbtree/armel (0.4.6-1 to 0.4.6-1)
  • Migration status for ruby-rbtree/armel (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-rbtree/armhf (0.4.6-1 to 0.4.6-1)
  • Migration status for ruby-rbtree/armhf (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-rbtree/i386 (0.4.6-1 to 0.4.6-1)
  • Migration status for ruby-rbtree/i386 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-rbtree/mips64el (0.4.6-1 to 0.4.6-1)
  • Migration status for ruby-rbtree/mips64el (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-rbtree/ppc64el (0.4.6-1 to 0.4.6-1)
  • Migration status for ruby-rbtree/ppc64el (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-rbtree/riscv64 (0.4.6-1 to 0.4.6-1)
  • Migration status for ruby-rbtree/riscv64 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-rbtree/s390x (0.4.6-1 to 0.4.6-1)
  • Migration status for ruby-rbtree/s390x (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-rdiscount/amd64 (2.2.7.3-1 to 2.2.7.3-1)
  • Migration status for ruby-rdiscount/amd64 (2.2.7.3-1 to 2.2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-rdiscount/arm64 (2.2.7.3-1 to 2.2.7.3-1)
  • Migration status for ruby-rdiscount/arm64 (2.2.7.3-1 to 2.2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-rdiscount/armel (2.2.7.3-1 to 2.2.7.3-1)
  • Migration status for ruby-rdiscount/armel (2.2.7.3-1 to 2.2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-rdiscount/armhf (2.2.7.3-1 to 2.2.7.3-1)
  • Migration status for ruby-rdiscount/armhf (2.2.7.3-1 to 2.2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-rdiscount/i386 (2.2.7.3-1 to 2.2.7.3-1)
  • Migration status for ruby-rdiscount/i386 (2.2.7.3-1 to 2.2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-rdiscount/mips64el (2.2.7.3-1 to 2.2.7.3-1)
  • Migration status for ruby-rdiscount/mips64el (2.2.7.3-1 to 2.2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-rdiscount/ppc64el (2.2.7.3-1 to 2.2.7.3-1)
  • Migration status for ruby-rdiscount/ppc64el (2.2.7.3-1 to 2.2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-rdiscount/riscv64 (2.2.7.3-1 to 2.2.7.3-1)
  • Migration status for ruby-rdiscount/riscv64 (2.2.7.3-1 to 2.2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-rdiscount/s390x (2.2.7.3-1 to 2.2.7.3-1)
  • Migration status for ruby-rdiscount/s390x (2.2.7.3-1 to 2.2.7.3-1): Will attempt migration (Any information below is purely informational)
• ruby-re2/amd64 (2.7.0-2 to 2.7.0-2)
  • Migration status for ruby-re2/amd64 (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• ruby-re2/arm64 (2.7.0-2 to 2.7.0-2)
  • Migration status for ruby-re2/arm64 (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• ruby-re2/armel (2.7.0-2 to 2.7.0-2)
  • Migration status for ruby-re2/armel (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• ruby-re2/armhf (2.7.0-2 to 2.7.0-2)
  • Migration status for ruby-re2/armhf (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• ruby-re2/i386 (2.7.0-2 to 2.7.0-2)
  • Migration status for ruby-re2/i386 (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• ruby-re2/mips64el (2.7.0-2 to 2.7.0-2)
  • Migration status for ruby-re2/mips64el (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• ruby-re2/ppc64el (2.7.0-2 to 2.7.0-2)
  • Migration status for ruby-re2/ppc64el (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• ruby-re2/riscv64 (2.7.0-2 to 2.7.0-2)
  • Migration status for ruby-re2/riscv64 (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• ruby-re2/s390x (2.7.0-2 to 2.7.0-2)
  • Migration status for ruby-re2/s390x (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• ruby-redcarpet/amd64 (3.6.0-1 to 3.6.0-1)
  • Migration status for ruby-redcarpet/amd64 (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
• ruby-redcarpet/arm64 (3.6.0-1 to 3.6.0-1)
  • Migration status for ruby-redcarpet/arm64 (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
• ruby-redcarpet/armel (3.6.0-1 to 3.6.0-1)
  • Migration status for ruby-redcarpet/armel (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
• ruby-redcarpet/armhf (3.6.0-1 to 3.6.0-1)
  • Migration status for ruby-redcarpet/armhf (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
• ruby-redcarpet/i386 (3.6.0-1 to 3.6.0-1)
  • Migration status for ruby-redcarpet/i386 (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
• ruby-redcarpet/mips64el (3.6.0-1 to 3.6.0-1)
  • Migration status for ruby-redcarpet/mips64el (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
• ruby-redcarpet/ppc64el (3.6.0-1 to 3.6.0-1)
  • Migration status for ruby-redcarpet/ppc64el (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
• ruby-redcarpet/riscv64 (3.6.0-1 to 3.6.0-1)
  • Migration status for ruby-redcarpet/riscv64 (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
• ruby-redcarpet/s390x (3.6.0-1 to 3.6.0-1)
  • Migration status for ruby-redcarpet/s390x (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
• ruby-redcloth/amd64 (4.3.4-1 to 4.3.4-1)
  • Migration status for ruby-redcloth/amd64 (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-redcloth/arm64 (4.3.4-1 to 4.3.4-1)
  • Migration status for ruby-redcloth/arm64 (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-redcloth/armel (4.3.4-1 to 4.3.4-1)
  • Migration status for ruby-redcloth/armel (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-redcloth/armhf (4.3.4-1 to 4.3.4-1)
  • Migration status for ruby-redcloth/armhf (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-redcloth/i386 (4.3.4-1 to 4.3.4-1)
  • Migration status for ruby-redcloth/i386 (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-redcloth/mips64el (4.3.4-1 to 4.3.4-1)
  • Migration status for ruby-redcloth/mips64el (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-redcloth/ppc64el (4.3.4-1 to 4.3.4-1)
  • Migration status for ruby-redcloth/ppc64el (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-redcloth/riscv64 (4.3.4-1 to 4.3.4-1)
  • Migration status for ruby-redcloth/riscv64 (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-redcloth/s390x (4.3.4-1 to 4.3.4-1)
  • Migration status for ruby-redcloth/s390x (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
• ruby-regexp-property-values/amd64 (1.0.0-2 to 1.0.0-2)
  • Migration status for ruby-regexp-property-values/amd64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• ruby-regexp-property-values/arm64 (1.0.0-2 to 1.0.0-2)
  • Migration status for ruby-regexp-property-values/arm64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• ruby-regexp-property-values/armel (1.0.0-2 to 1.0.0-2)
  • Migration status for ruby-regexp-property-values/armel (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• ruby-regexp-property-values/armhf (1.0.0-2 to 1.0.0-2)
  • Migration status for ruby-regexp-property-values/armhf (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• ruby-regexp-property-values/i386 (1.0.0-2 to 1.0.0-2)
  • Migration status for ruby-regexp-property-values/i386 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• ruby-regexp-property-values/mips64el (1.0.0-2 to 1.0.0-2)
  • Migration status for ruby-regexp-property-values/mips64el (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• ruby-regexp-property-values/ppc64el (1.0.0-2 to 1.0.0-2)
  • Migration status for ruby-regexp-property-values/ppc64el (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• ruby-regexp-property-values/riscv64 (1.0.0-2 to 1.0.0-2)
  • Migration status for ruby-regexp-property-values/riscv64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• ruby-regexp-property-values/s390x (1.0.0-2 to 1.0.0-2)
  • Migration status for ruby-regexp-property-values/s390x (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• ruby-rinku/amd64 (1.7.3-2.1 to 1.7.3-2.1)
  • Migration status for ruby-rinku/amd64 (1.7.3-2.1 to 1.7.3-2.1): Will attempt migration (Any information below is purely informational)
• ruby-rinku/arm64 (1.7.3-2.1 to 1.7.3-2.1)
  • Migration status for ruby-rinku/arm64 (1.7.3-2.1 to 1.7.3-2.1): Will attempt migration (Any information below is purely informational)
• ruby-rinku/armel (1.7.3-2.1 to 1.7.3-2.1)
  • Migration status for ruby-rinku/armel (1.7.3-2.1 to 1.7.3-2.1): Will attempt migration (Any information below is purely informational)
• ruby-rinku/armhf (1.7.3-2.1 to 1.7.3-2.1)
  • Migration status for ruby-rinku/armhf (1.7.3-2.1 to 1.7.3-2.1): Will attempt migration (Any information below is purely informational)
• ruby-rinku/i386 (1.7.3-2.1 to 1.7.3-2.1)
  • Migration status for ruby-rinku/i386 (1.7.3-2.1 to 1.7.3-2.1): Will attempt migration (Any information below is purely informational)
• ruby-rinku/mips64el (1.7.3-2.1 to 1.7.3-2.1)
  • Migration status for ruby-rinku/mips64el (1.7.3-2.1 to 1.7.3-2.1): Will attempt migration (Any information below is purely informational)
• ruby-rinku/ppc64el (1.7.3-2.1 to 1.7.3-2.1)
  • Migration status for ruby-rinku/ppc64el (1.7.3-2.1 to 1.7.3-2.1): Will attempt migration (Any information below is purely informational)
• ruby-rinku/riscv64 (1.7.3-2.1 to 1.7.3-2.1)
  • Migration status for ruby-rinku/riscv64 (1.7.3-2.1 to 1.7.3-2.1): Will attempt migration (Any information below is purely informational)
• ruby-rinku/s390x (1.7.3-2.1 to 1.7.3-2.1)
  • Migration status for ruby-rinku/s390x (1.7.3-2.1 to 1.7.3-2.1): Will attempt migration (Any information below is purely informational)
• ruby-rmagick/amd64 (6.0.1-2 to 6.0.1-2)
  • Migration status for ruby-rmagick/amd64 (6.0.1-2 to 6.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rmagick/arm64 (6.0.1-2 to 6.0.1-2)
  • Migration status for ruby-rmagick/arm64 (6.0.1-2 to 6.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rmagick/armel (6.0.1-2 to 6.0.1-2)
  • Migration status for ruby-rmagick/armel (6.0.1-2 to 6.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rmagick/armhf (6.0.1-2 to 6.0.1-2)
  • Migration status for ruby-rmagick/armhf (6.0.1-2 to 6.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rmagick/i386 (6.0.1-2 to 6.0.1-2)
  • Migration status for ruby-rmagick/i386 (6.0.1-2 to 6.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rmagick/mips64el (6.0.1-2 to 6.0.1-2)
  • Migration status for ruby-rmagick/mips64el (6.0.1-2 to 6.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rmagick/ppc64el (6.0.1-2 to 6.0.1-2)
  • Migration status for ruby-rmagick/ppc64el (6.0.1-2 to 6.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rmagick/riscv64 (6.0.1-2 to 6.0.1-2)
  • Migration status for ruby-rmagick/riscv64 (6.0.1-2 to 6.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rmagick/s390x (6.0.1-2 to 6.0.1-2)
  • Migration status for ruby-rmagick/s390x (6.0.1-2 to 6.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rpam-ruby19/amd64 (1.2.1-1 to 1.2.1-1)
  • Migration status for ruby-rpam-ruby19/amd64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ruby-rpam-ruby19/arm64 (1.2.1-1 to 1.2.1-1)
  • Migration status for ruby-rpam-ruby19/arm64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ruby-rpam-ruby19/armel (1.2.1-1 to 1.2.1-1)
  • Migration status for ruby-rpam-ruby19/armel (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ruby-rpam-ruby19/i386 (1.2.1-1 to 1.2.1-1)
  • Migration status for ruby-rpam-ruby19/i386 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ruby-rpam-ruby19/mips64el (1.2.1-1 to 1.2.1-1)
  • Migration status for ruby-rpam-ruby19/mips64el (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ruby-rpam-ruby19/ppc64el (1.2.1-1 to 1.2.1-1)
  • Migration status for ruby-rpam-ruby19/ppc64el (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ruby-rpam-ruby19/riscv64 (1.2.1-1 to 1.2.1-1)
  • Migration status for ruby-rpam-ruby19/riscv64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ruby-rpatricia/amd64 (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/amd64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rpatricia/arm64 (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/arm64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rpatricia/armel (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/armel (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rpatricia/armhf (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/armhf (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rpatricia/i386 (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/i386 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rpatricia/mips64el (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/mips64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rpatricia/ppc64el (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/ppc64el (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rpatricia/riscv64 (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/riscv64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rpatricia/s390x (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/s390x (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-ruby-magic-static/amd64 (0.6.0-3 to 0.6.0-3)
  • Migration status for ruby-ruby-magic-static/amd64 (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
• ruby-ruby-magic-static/arm64 (0.6.0-3 to 0.6.0-3)
  • Migration status for ruby-ruby-magic-static/arm64 (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
• ruby-ruby-magic-static/armel (0.6.0-3 to 0.6.0-3)
  • Migration status for ruby-ruby-magic-static/armel (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
• ruby-ruby-magic-static/armhf (0.6.0-3 to 0.6.0-3)
  • Migration status for ruby-ruby-magic-static/armhf (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
• ruby-ruby-magic-static/i386 (0.6.0-3 to 0.6.0-3)
  • Migration status for ruby-ruby-magic-static/i386 (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
• ruby-ruby-magic-static/mips64el (0.6.0-3 to 0.6.0-3)
  • Migration status for ruby-ruby-magic-static/mips64el (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
• ruby-ruby-magic-static/ppc64el (0.6.0-3 to 0.6.0-3)
  • Migration status for ruby-ruby-magic-static/ppc64el (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
• ruby-ruby-magic-static/riscv64 (0.6.0-3 to 0.6.0-3)
  • Migration status for ruby-ruby-magic-static/riscv64 (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
• ruby-ruby-magic-static/s390x (0.6.0-3 to 0.6.0-3)
  • Migration status for ruby-ruby-magic-static/s390x (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
• ruby-rugged/amd64 (1.7.2+ds-3 to 1.7.2+ds-3)
  • Migration status for ruby-rugged/amd64 (1.7.2+ds-3 to 1.7.2+ds-3): Will attempt migration (Any information below is purely informational)
• ruby-rugged/arm64 (1.7.2+ds-3 to 1.7.2+ds-3)
  • Migration status for ruby-rugged/arm64 (1.7.2+ds-3 to 1.7.2+ds-3): Will attempt migration (Any information below is purely informational)
• ruby-rugged/armel (1.7.2+ds-3 to 1.7.2+ds-3)
  • Migration status for ruby-rugged/armel (1.7.2+ds-3 to 1.7.2+ds-3): Will attempt migration (Any information below is purely informational)
• ruby-rugged/armhf (1.7.2+ds-3 to 1.7.2+ds-3)
  • Migration status for ruby-rugged/armhf (1.7.2+ds-3 to 1.7.2+ds-3): Will attempt migration (Any information below is purely informational)
• ruby-rugged/i386 (1.7.2+ds-3 to 1.7.2+ds-3)
  • Migration status for ruby-rugged/i386 (1.7.2+ds-3 to 1.7.2+ds-3): Will attempt migration (Any information below is purely informational)
• ruby-rugged/mips64el (1.7.2+ds-3 to 1.7.2+ds-3)
  • Migration status for ruby-rugged/mips64el (1.7.2+ds-3 to 1.7.2+ds-3): Will attempt migration (Any information below is purely informational)
• ruby-rugged/ppc64el (1.7.2+ds-3 to 1.7.2+ds-3)
  • Migration status for ruby-rugged/ppc64el (1.7.2+ds-3 to 1.7.2+ds-3): Will attempt migration (Any information below is purely informational)
• ruby-rugged/riscv64 (1.7.2+ds-3 to 1.7.2+ds-3)
  • Migration status for ruby-rugged/riscv64 (1.7.2+ds-3 to 1.7.2+ds-3): Will attempt migration (Any information below is purely informational)
• ruby-rugged/s390x (1.7.2+ds-3 to 1.7.2+ds-3)
  • Migration status for ruby-rugged/s390x (1.7.2+ds-3 to 1.7.2+ds-3): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/amd64 (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/amd64 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/arm64 (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/arm64 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/armel (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/armel (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/armhf (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/armhf (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/i386 (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/i386 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/mips64el (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/mips64el (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/ppc64el (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/ppc64el (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/riscv64 (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/riscv64 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/s390x (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/s390x (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-sdl/amd64 (2.2.0-2 to 2.2.0-2)
  • Migration status for ruby-sdl/amd64 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• ruby-sdl/arm64 (2.2.0-2 to 2.2.0-2)
  • Migration status for ruby-sdl/arm64 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• ruby-sdl/armel (2.2.0-2 to 2.2.0-2)
  • Migration status for ruby-sdl/armel (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• ruby-sdl/armhf (2.2.0-2 to 2.2.0-2)
  • Migration status for ruby-sdl/armhf (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• ruby-sdl/i386 (2.2.0-2 to 2.2.0-2)
  • Migration status for ruby-sdl/i386 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• ruby-sdl/mips64el (2.2.0-2 to 2.2.0-2)
  • Migration status for ruby-sdl/mips64el (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• ruby-sdl/ppc64el (2.2.0-2 to 2.2.0-2)
  • Migration status for ruby-sdl/ppc64el (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• ruby-sdl/riscv64 (2.2.0-2 to 2.2.0-2)
  • Migration status for ruby-sdl/riscv64 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• ruby-sdl/s390x (2.2.0-2 to 2.2.0-2)
  • Migration status for ruby-sdl/s390x (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• ruby-sequel-pg/amd64 (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/amd64 (1.14.0-1 to 1.14.0-1): Will attempt migration (Any information below is purely informational)
• ruby-sequel-pg/arm64 (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/arm64 (1.14.0-1 to 1.14.0-1): Will attempt migration (Any information below is purely informational)
• ruby-sequel-pg/armel (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/armel (1.14.0-1 to 1.14.0-1): Will attempt migration (Any information below is purely informational)
• ruby-sequel-pg/armhf (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/armhf (1.14.0-1 to 1.14.0-1): Will attempt migration (Any information below is purely informational)
• ruby-sequel-pg/i386 (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/i386 (1.14.0-1 to 1.14.0-1): Will attempt migration (Any information below is purely informational)
• ruby-sequel-pg/mips64el (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/mips64el (1.14.0-1 to 1.14.0-1): Will attempt migration (Any information below is purely informational)
• ruby-sequel-pg/ppc64el (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/ppc64el (1.14.0-1 to 1.14.0-1): Will attempt migration (Any information below is purely informational)
• ruby-sequel-pg/riscv64 (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/riscv64 (1.14.0-1 to 1.14.0-1): Will attempt migration (Any information below is purely informational)
• ruby-sequel-pg/s390x (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/s390x (1.14.0-1 to 1.14.0-1): Will attempt migration (Any information below is purely informational)
• ruby-shadow/amd64 (2.5.1-2 to 2.5.1-2)
  • Migration status for ruby-shadow/amd64 (2.5.1-2 to 2.5.1-2): Will attempt migration (Any information below is purely informational)
• ruby-shadow/arm64 (2.5.1-2 to 2.5.1-2)
  • Migration status for ruby-shadow/arm64 (2.5.1-2 to 2.5.1-2): Will attempt migration (Any information below is purely informational)
• ruby-shadow/armel (2.5.1-2 to 2.5.1-2)
  • Migration status for ruby-shadow/armel (2.5.1-2 to 2.5.1-2): Will attempt migration (Any information below is purely informational)
• ruby-shadow/armhf (2.5.1-2 to 2.5.1-2)
  • Migration status for ruby-shadow/armhf (2.5.1-2 to 2.5.1-2): Will attempt migration (Any information below is purely informational)
• ruby-shadow/i386 (2.5.1-2 to 2.5.1-2)
  • Migration status for ruby-shadow/i386 (2.5.1-2 to 2.5.1-2): Will attempt migration (Any information below is purely informational)
• ruby-shadow/mips64el (2.5.1-2 to 2.5.1-2)
  • Migration status for ruby-shadow/mips64el (2.5.1-2 to 2.5.1-2): Will attempt migration (Any information below is purely informational)
• ruby-shadow/ppc64el (2.5.1-2 to 2.5.1-2)
  • Migration status for ruby-shadow/ppc64el (2.5.1-2 to 2.5.1-2): Will attempt migration (Any information below is purely informational)
• ruby-shadow/riscv64 (2.5.1-2 to 2.5.1-2)
  • Migration status for ruby-shadow/riscv64 (2.5.1-2 to 2.5.1-2): Will attempt migration (Any information below is purely informational)
• ruby-shadow/s390x (2.5.1-2 to 2.5.1-2)
  • Migration status for ruby-shadow/s390x (2.5.1-2 to 2.5.1-2): Will attempt migration (Any information below is purely informational)
• ruby-sqlite3/amd64 (1.6.9-2 to 1.6.9-2)
  • Migration status for ruby-sqlite3/amd64 (1.6.9-2 to 1.6.9-2): Will attempt migration (Any information below is purely informational)
• ruby-sqlite3/arm64 (1.6.9-2 to 1.6.9-2)
  • Migration status for ruby-sqlite3/arm64 (1.6.9-2 to 1.6.9-2): Will attempt migration (Any information below is purely informational)
• ruby-sqlite3/armel (1.6.9-2 to 1.6.9-2)
  • Migration status for ruby-sqlite3/armel (1.6.9-2 to 1.6.9-2): Will attempt migration (Any information below is purely informational)
• ruby-sqlite3/armhf (1.6.9-2 to 1.6.9-2)
  • Migration status for ruby-sqlite3/armhf (1.6.9-2 to 1.6.9-2): Will attempt migration (Any information below is purely informational)
• ruby-sqlite3/i386 (1.6.9-2 to 1.6.9-2)
  • Migration status for ruby-sqlite3/i386 (1.6.9-2 to 1.6.9-2): Will attempt migration (Any information below is purely informational)
• ruby-sqlite3/mips64el (1.6.9-2 to 1.6.9-2)
  • Migration status for ruby-sqlite3/mips64el (1.6.9-2 to 1.6.9-2): Will attempt migration (Any information below is purely informational)
• ruby-sqlite3/ppc64el (1.6.9-2 to 1.6.9-2)
  • Migration status for ruby-sqlite3/ppc64el (1.6.9-2 to 1.6.9-2): Will attempt migration (Any information below is purely informational)
• ruby-sqlite3/riscv64 (1.6.9-2 to 1.6.9-2)
  • Migration status for ruby-sqlite3/riscv64 (1.6.9-2 to 1.6.9-2): Will attempt migration (Any information below is purely informational)
• ruby-sqlite3/s390x (1.6.9-2 to 1.6.9-2)
  • Migration status for ruby-sqlite3/s390x (1.6.9-2 to 1.6.9-2): Will attempt migration (Any information below is purely informational)
• ruby-stackprof/amd64 (0.2.26-3 to 0.2.26-3)
  • Migration status for ruby-stackprof/amd64 (0.2.26-3 to 0.2.26-3): Will attempt migration (Any information below is purely informational)
• ruby-stackprof/arm64 (0.2.26-3 to 0.2.26-3)
  • Migration status for ruby-stackprof/arm64 (0.2.26-3 to 0.2.26-3): Will attempt migration (Any information below is purely informational)
• ruby-stackprof/armel (0.2.26-3 to 0.2.26-3)
  • Migration status for ruby-stackprof/armel (0.2.26-3 to 0.2.26-3): Will attempt migration (Any information below is purely informational)
• ruby-stackprof/i386 (0.2.26-3 to 0.2.26-3)
  • Migration status for ruby-stackprof/i386 (0.2.26-3 to 0.2.26-3): Will attempt migration (Any information below is purely informational)
• ruby-stackprof/mips64el (0.2.26-3 to 0.2.26-3)
  • Migration status for ruby-stackprof/mips64el (0.2.26-3 to 0.2.26-3): Will attempt migration (Any information below is purely informational)
• ruby-stackprof/ppc64el (0.2.26-3 to 0.2.26-3)
  • Migration status for ruby-stackprof/ppc64el (0.2.26-3 to 0.2.26-3): Will attempt migration (Any information below is purely informational)
• ruby-stackprof/riscv64 (0.2.26-3 to 0.2.26-3)
  • Migration status for ruby-stackprof/riscv64 (0.2.26-3 to 0.2.26-3): Will attempt migration (Any information below is purely informational)
• ruby-strptime/amd64 (0.2.5-1 to 0.2.5-1)
  • Migration status for ruby-strptime/amd64 (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• ruby-strptime/arm64 (0.2.5-1 to 0.2.5-1)
  • Migration status for ruby-strptime/arm64 (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• ruby-strptime/armel (0.2.5-1 to 0.2.5-1)
  • Migration status for ruby-strptime/armel (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• ruby-strptime/armhf (0.2.5-1 to 0.2.5-1)
  • Migration status for ruby-strptime/armhf (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• ruby-strptime/i386 (0.2.5-1 to 0.2.5-1)
  • Migration status for ruby-strptime/i386 (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• ruby-strptime/mips64el (0.2.5-1 to 0.2.5-1)
  • Migration status for ruby-strptime/mips64el (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• ruby-strptime/ppc64el (0.2.5-1 to 0.2.5-1)
  • Migration status for ruby-strptime/ppc64el (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• ruby-strptime/riscv64 (0.2.5-1 to 0.2.5-1)
  • Migration status for ruby-strptime/riscv64 (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• ruby-strptime/s390x (0.2.5-1 to 0.2.5-1)
  • Migration status for ruby-strptime/s390x (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• ruby-termios/amd64 (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-termios/amd64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-termios/arm64 (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-termios/arm64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-termios/armel (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-termios/armel (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-termios/armhf (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-termios/armhf (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-termios/i386 (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-termios/i386 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-termios/mips64el (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-termios/mips64el (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-termios/ppc64el (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-termios/ppc64el (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-termios/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-termios/riscv64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-termios/s390x (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-termios/s390x (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-thrift/amd64 (0.16.0-2 to 0.16.0-2)
  • Migration status for ruby-thrift/amd64 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
• ruby-thrift/arm64 (0.16.0-2 to 0.16.0-2)
  • Migration status for ruby-thrift/arm64 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
• ruby-thrift/armel (0.16.0-2 to 0.16.0-2)
  • Migration status for ruby-thrift/armel (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
• ruby-thrift/armhf (0.16.0-2 to 0.16.0-2)
  • Migration status for ruby-thrift/armhf (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
• ruby-thrift/i386 (0.16.0-2 to 0.16.0-2)
  • Migration status for ruby-thrift/i386 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
• ruby-thrift/mips64el (0.16.0-2 to 0.16.0-2)
  • Migration status for ruby-thrift/mips64el (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
• ruby-thrift/ppc64el (0.16.0-2 to 0.16.0-2)
  • Migration status for ruby-thrift/ppc64el (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
• ruby-thrift/riscv64 (0.16.0-2 to 0.16.0-2)
  • Migration status for ruby-thrift/riscv64 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
• ruby-thrift/s390x (0.16.0-2 to 0.16.0-2)
  • Migration status for ruby-thrift/s390x (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
• ruby-timfel-krb5-auth/amd64 (0.8.3-3 to 0.8.3-3)
  • Migration status for ruby-timfel-krb5-auth/amd64 (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
• ruby-timfel-krb5-auth/arm64 (0.8.3-3 to 0.8.3-3)
  • Migration status for ruby-timfel-krb5-auth/arm64 (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
• ruby-timfel-krb5-auth/armel (0.8.3-3 to 0.8.3-3)
  • Migration status for ruby-timfel-krb5-auth/armel (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
• ruby-timfel-krb5-auth/armhf (0.8.3-3 to 0.8.3-3)
  • Migration status for ruby-timfel-krb5-auth/armhf (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
• ruby-timfel-krb5-auth/i386 (0.8.3-3 to 0.8.3-3)
  • Migration status for ruby-timfel-krb5-auth/i386 (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
• ruby-timfel-krb5-auth/mips64el (0.8.3-3 to 0.8.3-3)
  • Migration status for ruby-timfel-krb5-auth/mips64el (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
• ruby-timfel-krb5-auth/ppc64el (0.8.3-3 to 0.8.3-3)
  • Migration status for ruby-timfel-krb5-auth/ppc64el (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
• ruby-timfel-krb5-auth/riscv64 (0.8.3-3 to 0.8.3-3)
  • Migration status for ruby-timfel-krb5-auth/riscv64 (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
• ruby-timfel-krb5-auth/s390x (0.8.3-3 to 0.8.3-3)
  • Migration status for ruby-timfel-krb5-auth/s390x (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
• ruby-tioga/amd64 (1.19.1-6 to 1.19.1-6)
  • Migration status for ruby-tioga/amd64 (1.19.1-6 to 1.19.1-6): Will attempt migration (Any information below is purely informational)
• ruby-tioga/arm64 (1.19.1-6 to 1.19.1-6)
  • Migration status for ruby-tioga/arm64 (1.19.1-6 to 1.19.1-6): Will attempt migration (Any information below is purely informational)
• ruby-tioga/armel (1.19.1-6 to 1.19.1-6)
  • Migration status for ruby-tioga/armel (1.19.1-6 to 1.19.1-6): Will attempt migration (Any information below is purely informational)
• ruby-tioga/armhf (1.19.1-6 to 1.19.1-6)
  • Migration status for ruby-tioga/armhf (1.19.1-6 to 1.19.1-6): Will attempt migration (Any information below is purely informational)
• ruby-tioga/i386 (1.19.1-6 to 1.19.1-6)
  • Migration status for ruby-tioga/i386 (1.19.1-6 to 1.19.1-6): Will attempt migration (Any information below is purely informational)
• ruby-tioga/mips64el (1.19.1-6 to 1.19.1-6)
  • Migration status for ruby-tioga/mips64el (1.19.1-6 to 1.19.1-6): Will attempt migration (Any information below is purely informational)
• ruby-tioga/ppc64el (1.19.1-6 to 1.19.1-6)
  • Migration status for ruby-tioga/ppc64el (1.19.1-6 to 1.19.1-6): Will attempt migration (Any information below is purely informational)
• ruby-tioga/riscv64 (1.19.1-6 to 1.19.1-6)
  • Migration status for ruby-tioga/riscv64 (1.19.1-6 to 1.19.1-6): Will attempt migration (Any information below is purely informational)
• ruby-tioga/s390x (1.19.1-6 to 1.19.1-6)
  • Migration status for ruby-tioga/s390x (1.19.1-6 to 1.19.1-6): Will attempt migration (Any information below is purely informational)
• ruby-tokyocabinet/amd64 (1.31-7 to 1.31-7)
  • Migration status for ruby-tokyocabinet/amd64 (1.31-7 to 1.31-7): Will attempt migration (Any information below is purely informational)
• ruby-tokyocabinet/arm64 (1.31-7 to 1.31-7)
  • Migration status for ruby-tokyocabinet/arm64 (1.31-7 to 1.31-7): Will attempt migration (Any information below is purely informational)
• ruby-tokyocabinet/armel (1.31-7 to 1.31-7)
  • Migration status for ruby-tokyocabinet/armel (1.31-7 to 1.31-7): Will attempt migration (Any information below is purely informational)
• ruby-tokyocabinet/armhf (1.31-7 to 1.31-7)
  • Migration status for ruby-tokyocabinet/armhf (1.31-7 to 1.31-7): Will attempt migration (Any information below is purely informational)
• ruby-tokyocabinet/i386 (1.31-7 to 1.31-7)
  • Migration status for ruby-tokyocabinet/i386 (1.31-7 to 1.31-7): Will attempt migration (Any information below is purely informational)
• ruby-tokyocabinet/mips64el (1.31-7 to 1.31-7)
  • Migration status for ruby-tokyocabinet/mips64el (1.31-7 to 1.31-7): Will attempt migration (Any information below is purely informational)
• ruby-tokyocabinet/ppc64el (1.31-7 to 1.31-7)
  • Migration status for ruby-tokyocabinet/ppc64el (1.31-7 to 1.31-7): Will attempt migration (Any information below is purely informational)
• ruby-tokyocabinet/riscv64 (1.31-7 to 1.31-7)
  • Migration status for ruby-tokyocabinet/riscv64 (1.31-7 to 1.31-7): Will attempt migration (Any information below is purely informational)
• ruby-tokyocabinet/s390x (1.31-7 to 1.31-7)
  • Migration status for ruby-tokyocabinet/s390x (1.31-7 to 1.31-7): Will attempt migration (Any information below is purely informational)
• ruby-uconv/amd64 (0.6.1-4 to 0.6.1-4)
  • Migration status for ruby-uconv/amd64 (0.6.1-4 to 0.6.1-4): Will attempt migration (Any information below is purely informational)
• ruby-uconv/arm64 (0.6.1-4 to 0.6.1-4)
  • Migration status for ruby-uconv/arm64 (0.6.1-4 to 0.6.1-4): Will attempt migration (Any information below is purely informational)
• ruby-uconv/armel (0.6.1-4 to 0.6.1-4)
  • Migration status for ruby-uconv/armel (0.6.1-4 to 0.6.1-4): Will attempt migration (Any information below is purely informational)
• ruby-uconv/armhf (0.6.1-4 to 0.6.1-4)
  • Migration status for ruby-uconv/armhf (0.6.1-4 to 0.6.1-4): Will attempt migration (Any information below is purely informational)
• ruby-uconv/i386 (0.6.1-4 to 0.6.1-4)
  • Migration status for ruby-uconv/i386 (0.6.1-4 to 0.6.1-4): Will attempt migration (Any information below is purely informational)
• ruby-uconv/mips64el (0.6.1-4 to 0.6.1-4)
  • Migration status for ruby-uconv/mips64el (0.6.1-4 to 0.6.1-4): Will attempt migration (Any information below is purely informational)
• ruby-uconv/ppc64el (0.6.1-4 to 0.6.1-4)
  • Migration status for ruby-uconv/ppc64el (0.6.1-4 to 0.6.1-4): Will attempt migration (Any information below is purely informational)
• ruby-uconv/riscv64 (0.6.1-4 to 0.6.1-4)
  • Migration status for ruby-uconv/riscv64 (0.6.1-4 to 0.6.1-4): Will attempt migration (Any information below is purely informational)
• ruby-uconv/s390x (0.6.1-4 to 0.6.1-4)
  • Migration status for ruby-uconv/s390x (0.6.1-4 to 0.6.1-4): Will attempt migration (Any information below is purely informational)
• ruby-unf-ext/amd64 (0.0.7.7-1 to 0.0.7.7-1)
  • Migration status for ruby-unf-ext/amd64 (0.0.7.7-1 to 0.0.7.7-1): Will attempt migration (Any information below is purely informational)
• ruby-unf-ext/arm64 (0.0.7.7-1 to 0.0.7.7-1)
  • Migration status for ruby-unf-ext/arm64 (0.0.7.7-1 to 0.0.7.7-1): Will attempt migration (Any information below is purely informational)
• ruby-unf-ext/armel (0.0.7.7-1 to 0.0.7.7-1)
  • Migration status for ruby-unf-ext/armel (0.0.7.7-1 to 0.0.7.7-1): Will attempt migration (Any information below is purely informational)
• ruby-unf-ext/armhf (0.0.7.7-1 to 0.0.7.7-1)
  • Migration status for ruby-unf-ext/armhf (0.0.7.7-1 to 0.0.7.7-1): Will attempt migration (Any information below is purely informational)
• ruby-unf-ext/i386 (0.0.7.7-1 to 0.0.7.7-1)
  • Migration status for ruby-unf-ext/i386 (0.0.7.7-1 to 0.0.7.7-1): Will attempt migration (Any information below is purely informational)
• ruby-unf-ext/mips64el (0.0.7.7-1 to 0.0.7.7-1)
  • Migration status for ruby-unf-ext/mips64el (0.0.7.7-1 to 0.0.7.7-1): Will attempt migration (Any information below is purely informational)
• ruby-unf-ext/ppc64el (0.0.7.7-1 to 0.0.7.7-1)
  • Migration status for ruby-unf-ext/ppc64el (0.0.7.7-1 to 0.0.7.7-1): Will attempt migration (Any information below is purely informational)
• ruby-unf-ext/riscv64 (0.0.7.7-1 to 0.0.7.7-1)
  • Migration status for ruby-unf-ext/riscv64 (0.0.7.7-1 to 0.0.7.7-1): Will attempt migration (Any information below is purely informational)
• ruby-unf-ext/s390x (0.0.7.7-1 to 0.0.7.7-1)
  • Migration status for ruby-unf-ext/s390x (0.0.7.7-1 to 0.0.7.7-1): Will attempt migration (Any information below is purely informational)
• ruby-unicode/amd64 (0.4.4.5-1 to 0.4.4.5-1)
  • Migration status for ruby-unicode/amd64 (0.4.4.5-1 to 0.4.4.5-1): Will attempt migration (Any information below is purely informational)
• ruby-unicode/arm64 (0.4.4.5-1 to 0.4.4.5-1)
  • Migration status for ruby-unicode/arm64 (0.4.4.5-1 to 0.4.4.5-1): Will attempt migration (Any information below is purely informational)
• ruby-unicode/armel (0.4.4.5-1 to 0.4.4.5-1)
  • Migration status for ruby-unicode/armel (0.4.4.5-1 to 0.4.4.5-1): Will attempt migration (Any information below is purely informational)
• ruby-unicode/armhf (0.4.4.5-1 to 0.4.4.5-1)
  • Migration status for ruby-unicode/armhf (0.4.4.5-1 to 0.4.4.5-1): Will attempt migration (Any information below is purely informational)
• ruby-unicode/i386 (0.4.4.5-1 to 0.4.4.5-1)
  • Migration status for ruby-unicode/i386 (0.4.4.5-1 to 0.4.4.5-1): Will attempt migration (Any information below is purely informational)
• ruby-unicode/mips64el (0.4.4.5-1 to 0.4.4.5-1)
  • Migration status for ruby-unicode/mips64el (0.4.4.5-1 to 0.4.4.5-1): Will attempt migration (Any information below is purely informational)
• ruby-unicode/ppc64el (0.4.4.5-1 to 0.4.4.5-1)
  • Migration status for ruby-unicode/ppc64el (0.4.4.5-1 to 0.4.4.5-1): Will attempt migration (Any information below is purely informational)
• ruby-unicode/riscv64 (0.4.4.5-1 to 0.4.4.5-1)
  • Migration status for ruby-unicode/riscv64 (0.4.4.5-1 to 0.4.4.5-1): Will attempt migration (Any information below is purely informational)
• ruby-unicode/s390x (0.4.4.5-1 to 0.4.4.5-1)
  • Migration status for ruby-unicode/s390x (0.4.4.5-1 to 0.4.4.5-1): Will attempt migration (Any information below is purely informational)
• ruby-version-sorter/amd64 (2.3.0-1 to 2.3.0-1)
  • Migration status for ruby-version-sorter/amd64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• ruby-version-sorter/arm64 (2.3.0-1 to 2.3.0-1)
  • Migration status for ruby-version-sorter/arm64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• ruby-version-sorter/armel (2.3.0-1 to 2.3.0-1)
  • Migration status for ruby-version-sorter/armel (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• ruby-version-sorter/armhf (2.3.0-1 to 2.3.0-1)
  • Migration status for ruby-version-sorter/armhf (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• ruby-version-sorter/i386 (2.3.0-1 to 2.3.0-1)
  • Migration status for ruby-version-sorter/i386 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• ruby-version-sorter/mips64el (2.3.0-1 to 2.3.0-1)
  • Migration status for ruby-version-sorter/mips64el (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• ruby-version-sorter/ppc64el (2.3.0-1 to 2.3.0-1)
  • Migration status for ruby-version-sorter/ppc64el (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• ruby-version-sorter/riscv64 (2.3.0-1 to 2.3.0-1)
  • Migration status for ruby-version-sorter/riscv64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• ruby-version-sorter/s390x (2.3.0-1 to 2.3.0-1)
  • Migration status for ruby-version-sorter/s390x (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• ruby-vmstat/amd64 (2.3.1-1 to 2.3.1-1)
  • Migration status for ruby-vmstat/amd64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-vmstat/arm64 (2.3.1-1 to 2.3.1-1)
  • Migration status for ruby-vmstat/arm64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-vmstat/armel (2.3.1-1 to 2.3.1-1)
  • Migration status for ruby-vmstat/armel (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-vmstat/armhf (2.3.1-1 to 2.3.1-1)
  • Migration status for ruby-vmstat/armhf (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-vmstat/i386 (2.3.1-1 to 2.3.1-1)
  • Migration status for ruby-vmstat/i386 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-vmstat/mips64el (2.3.1-1 to 2.3.1-1)
  • Migration status for ruby-vmstat/mips64el (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-vmstat/ppc64el (2.3.1-1 to 2.3.1-1)
  • Migration status for ruby-vmstat/ppc64el (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-vmstat/riscv64 (2.3.1-1 to 2.3.1-1)
  • Migration status for ruby-vmstat/riscv64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-vmstat/s390x (2.3.1-1 to 2.3.1-1)
  • Migration status for ruby-vmstat/s390x (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-websocket-driver/amd64 (0.6.3-3 to 0.6.3-3)
  • Migration status for ruby-websocket-driver/amd64 (0.6.3-3 to 0.6.3-3): Will attempt migration (Any information below is purely informational)
• ruby-websocket-driver/arm64 (0.6.3-3 to 0.6.3-3)
  • Migration status for ruby-websocket-driver/arm64 (0.6.3-3 to 0.6.3-3): Will attempt migration (Any information below is purely informational)
• ruby-websocket-driver/armel (0.6.3-3 to 0.6.3-3)
  • Migration status for ruby-websocket-driver/armel (0.6.3-3 to 0.6.3-3): Will attempt migration (Any information below is purely informational)
• ruby-websocket-driver/armhf (0.6.3-3 to 0.6.3-3)
  • Migration status for ruby-websocket-driver/armhf (0.6.3-3 to 0.6.3-3): Will attempt migration (Any information below is purely informational)
• ruby-websocket-driver/i386 (0.6.3-3 to 0.6.3-3)
  • Migration status for ruby-websocket-driver/i386 (0.6.3-3 to 0.6.3-3): Will attempt migration (Any information below is purely informational)
• ruby-websocket-driver/mips64el (0.6.3-3 to 0.6.3-3)
  • Migration status for ruby-websocket-driver/mips64el (0.6.3-3 to 0.6.3-3): Will attempt migration (Any information below is purely informational)
• ruby-websocket-driver/ppc64el (0.6.3-3 to 0.6.3-3)
  • Migration status for ruby-websocket-driver/ppc64el (0.6.3-3 to 0.6.3-3): Will attempt migration (Any information below is purely informational)
• ruby-websocket-driver/riscv64 (0.6.3-3 to 0.6.3-3)
  • Migration status for ruby-websocket-driver/riscv64 (0.6.3-3 to 0.6.3-3): Will attempt migration (Any information below is purely informational)
• ruby-websocket-driver/s390x (0.6.3-3 to 0.6.3-3)
  • Migration status for ruby-websocket-driver/s390x (0.6.3-3 to 0.6.3-3): Will attempt migration (Any information below is purely informational)
• ruby-xmlhash/amd64 (1.3.6-3.1 to 1.3.6-3.1)
  • Migration status for ruby-xmlhash/amd64 (1.3.6-3.1 to 1.3.6-3.1): Will attempt migration (Any information below is purely informational)
• ruby-xmlhash/arm64 (1.3.6-3.1 to 1.3.6-3.1)
  • Migration status for ruby-xmlhash/arm64 (1.3.6-3.1 to 1.3.6-3.1): Will attempt migration (Any information below is purely informational)
• ruby-xmlhash/armel (1.3.6-3.1 to 1.3.6-3.1)
  • Migration status for ruby-xmlhash/armel (1.3.6-3.1 to 1.3.6-3.1): Will attempt migration (Any information below is purely informational)
• ruby-xmlhash/armhf (1.3.6-3.1 to 1.3.6-3.1)
  • Migration status for ruby-xmlhash/armhf (1.3.6-3.1 to 1.3.6-3.1): Will attempt migration (Any information below is purely informational)
• ruby-xmlhash/i386 (1.3.6-3.1 to 1.3.6-3.1)
  • Migration status for ruby-xmlhash/i386 (1.3.6-3.1 to 1.3.6-3.1): Will attempt migration (Any information below is purely informational)
• ruby-xmlhash/mips64el (1.3.6-3.1 to 1.3.6-3.1)
  • Migration status for ruby-xmlhash/mips64el (1.3.6-3.1 to 1.3.6-3.1): Will attempt migration (Any information below is purely informational)
• ruby-xmlhash/ppc64el (1.3.6-3.1 to 1.3.6-3.1)
  • Migration status for ruby-xmlhash/ppc64el (1.3.6-3.1 to 1.3.6-3.1): Will attempt migration (Any information below is purely informational)
• ruby-xmlhash/riscv64 (1.3.6-3.1 to 1.3.6-3.1)
  • Migration status for ruby-xmlhash/riscv64 (1.3.6-3.1 to 1.3.6-3.1): Will attempt migration (Any information below is purely informational)
• ruby-xmlhash/s390x (1.3.6-3.1 to 1.3.6-3.1)
  • Migration status for ruby-xmlhash/s390x (1.3.6-3.1 to 1.3.6-3.1): Will attempt migration (Any information below is purely informational)
• ruby-xmlparser/amd64 (0.7.3-6 to 0.7.3-6)
  • Migration status for ruby-xmlparser/amd64 (0.7.3-6 to 0.7.3-6): Will attempt migration (Any information below is purely informational)
• ruby-xmlparser/arm64 (0.7.3-6 to 0.7.3-6)
  • Migration status for ruby-xmlparser/arm64 (0.7.3-6 to 0.7.3-6): Will attempt migration (Any information below is purely informational)
• ruby-xmlparser/armel (0.7.3-6 to 0.7.3-6)
  • Migration status for ruby-xmlparser/armel (0.7.3-6 to 0.7.3-6): Will attempt migration (Any information below is purely informational)
• ruby-xmlparser/armhf (0.7.3-6 to 0.7.3-6)
  • Migration status for ruby-xmlparser/armhf (0.7.3-6 to 0.7.3-6): Will attempt migration (Any information below is purely informational)
• ruby-xmlparser/i386 (0.7.3-6 to 0.7.3-6)
  • Migration status for ruby-xmlparser/i386 (0.7.3-6 to 0.7.3-6): Will attempt migration (Any information below is purely informational)
• ruby-xmlparser/mips64el (0.7.3-6 to 0.7.3-6)
  • Migration status for ruby-xmlparser/mips64el (0.7.3-6 to 0.7.3-6): Will attempt migration (Any information below is purely informational)
• ruby-xmlparser/ppc64el (0.7.3-6 to 0.7.3-6)
  • Migration status for ruby-xmlparser/ppc64el (0.7.3-6 to 0.7.3-6): Will attempt migration (Any information below is purely informational)
• ruby-xmlparser/riscv64 (0.7.3-6 to 0.7.3-6)
  • Migration status for ruby-xmlparser/riscv64 (0.7.3-6 to 0.7.3-6): Will attempt migration (Any information below is purely informational)
• ruby-xmlparser/s390x (0.7.3-6 to 0.7.3-6)
  • Migration status for ruby-xmlparser/s390x (0.7.3-6 to 0.7.3-6): Will attempt migration (Any information below is purely informational)
• ruby-yajl/amd64 (1.4.3-1 to 1.4.3-1)
  • Migration status for ruby-yajl/amd64 (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• ruby-yajl/arm64 (1.4.3-1 to 1.4.3-1)
  • Migration status for ruby-yajl/arm64 (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• ruby-yajl/armel (1.4.3-1 to 1.4.3-1)
  • Migration status for ruby-yajl/armel (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• ruby-yajl/armhf (1.4.3-1 to 1.4.3-1)
  • Migration status for ruby-yajl/armhf (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• ruby-yajl/i386 (1.4.3-1 to 1.4.3-1)
  • Migration status for ruby-yajl/i386 (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• ruby-yajl/mips64el (1.4.3-1 to 1.4.3-1)
  • Migration status for ruby-yajl/mips64el (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• ruby-yajl/ppc64el (1.4.3-1 to 1.4.3-1)
  • Migration status for ruby-yajl/ppc64el (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• ruby-yajl/riscv64 (1.4.3-1 to 1.4.3-1)
  • Migration status for ruby-yajl/riscv64 (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• ruby-yajl/s390x (1.4.3-1 to 1.4.3-1)
  • Migration status for ruby-yajl/s390x (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• ruby-zoom/amd64 (0.5.0-2 to 0.5.0-2)
  • Migration status for ruby-zoom/amd64 (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• ruby-zoom/arm64 (0.5.0-2 to 0.5.0-2)
  • Migration status for ruby-zoom/arm64 (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• ruby-zoom/armel (0.5.0-2 to 0.5.0-2)
  • Migration status for ruby-zoom/armel (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• ruby-zoom/armhf (0.5.0-2 to 0.5.0-2)
  • Migration status for ruby-zoom/armhf (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• ruby-zoom/i386 (0.5.0-2 to 0.5.0-2)
  • Migration status for ruby-zoom/i386 (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• ruby-zoom/mips64el (0.5.0-2 to 0.5.0-2)
  • Migration status for ruby-zoom/mips64el (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• ruby-zoom/ppc64el (0.5.0-2 to 0.5.0-2)
  • Migration status for ruby-zoom/ppc64el (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• ruby-zoom/riscv64 (0.5.0-2 to 0.5.0-2)
  • Migration status for ruby-zoom/riscv64 (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• ruby-zoom/s390x (0.5.0-2 to 0.5.0-2)
  • Migration status for ruby-zoom/s390x (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• runit-services_pu (- to 0.5.5~deb12u2)
  • Migration status for runit-services_pu (- to 0.5.5~deb12u2): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • NEEDS APPROVAL BY RM
• rust-asahi-nvram/mips64el (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-asahi-nvram/mips64el (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• rust-asahi-nvram/riscv64 (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-asahi-nvram/riscv64 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• rust-asahi-wifisync/mips64el (0.2.2-2 to 0.2.2-2)
  • Migration status for rust-asahi-wifisync/mips64el (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
• rust-asahi-wifisync/riscv64 (0.2.2-2 to 0.2.2-2)
  • Migration status for rust-asahi-wifisync/riscv64 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
• rust-asahi-wifisync/s390x (0.2.2-2 to 0.2.2-2)
  • Migration status for rust-asahi-wifisync/s390x (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
• rust-b3sum/riscv64 (1.5.4-1 to 1.5.4-1)
  • Migration status for rust-b3sum/riscv64 (1.5.4-1 to 1.5.4-1): Will attempt migration (Any information below is purely informational)
• rust-backdown/riscv64 (1.1.2-3 to 1.1.2-3)
  • Migration status for rust-backdown/riscv64 (1.1.2-3 to 1.1.2-3): Will attempt migration (Any information below is purely informational)
• rust-backdown/s390x (1.1.2-3 to 1.1.2-3)
  • Migration status for rust-backdown/s390x (1.1.2-3 to 1.1.2-3): Will attempt migration (Any information below is purely informational)
• rust-bkt/riscv64 (0.6.1-2 to 0.6.1-2)
  • Migration status for rust-bkt/riscv64 (0.6.1-2 to 0.6.1-2): Will attempt migration (Any information below is purely informational)
• rust-bkt/s390x (0.6.1-2 to 0.6.1-2)
  • Migration status for rust-bkt/s390x (0.6.1-2 to 0.6.1-2): Will attempt migration (Any information below is purely informational)
• rust-buildlog-consultant/riscv64 (0.1.1-2 to 0.1.1-2)
  • Migration status for rust-buildlog-consultant/riscv64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• rust-cargo-auditable/riscv64 (0.6.1-3 to 0.6.1-3)
  • Migration status for rust-cargo-auditable/riscv64 (0.6.1-3 to 0.6.1-3): Will attempt migration (Any information below is purely informational)
• rust-cargo-auditable/s390x (0.6.1-3 to 0.6.1-3)
  • Migration status for rust-cargo-auditable/s390x (0.6.1-3 to 0.6.1-3): Will attempt migration (Any information below is purely informational)
• rust-cargo-c/s390x (0.10.7-1 to 0.10.7-1)
  • Migration status for rust-cargo-c/s390x (0.10.7-1 to 0.10.7-1): Will attempt migration (Any information below is purely informational)
• rust-cargo-debstatus/riscv64 (0.6.3-1 to 0.6.3-1)
  • Migration status for rust-cargo-debstatus/riscv64 (0.6.3-1 to 0.6.3-1): Will attempt migration (Any information below is purely informational)
• rust-cargo-debstatus/s390x (0.6.3-1 to 0.6.3-1)
  • Migration status for rust-cargo-debstatus/s390x (0.6.3-1 to 0.6.3-1): Will attempt migration (Any information below is purely informational)
• rust-cargo-lichking/riscv64 (0.9.0-4 to 0.9.0-4)
  • Migration status for rust-cargo-lichking/riscv64 (0.9.0-4 to 0.9.0-4): Will attempt migration (Any information below is purely informational)
• rust-cargo-lichking/s390x (0.9.0-4 to 0.9.0-4)
  • Migration status for rust-cargo-lichking/s390x (0.9.0-4 to 0.9.0-4): Will attempt migration (Any information below is purely informational)
• rust-cargo-mutants/riscv64 (23.10.0-1 to 23.10.0-1)
  • Migration status for rust-cargo-mutants/riscv64 (23.10.0-1 to 23.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-cargo-mutants/s390x (23.10.0-1 to 23.10.0-1)
  • Migration status for rust-cargo-mutants/s390x (23.10.0-1 to 23.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-cargo-outdated/armel (0.15.0-6 to 0.15.0-6)
  • Migration status for rust-cargo-outdated/armel (0.15.0-6 to 0.15.0-6): Will attempt migration (Any information below is purely informational)
• rust-cargo-outdated/s390x (0.15.0-6 to 0.15.0-6)
  • Migration status for rust-cargo-outdated/s390x (0.15.0-6 to 0.15.0-6): Will attempt migration (Any information below is purely informational)
• rust-cddl/riscv64 (0.9.4-2 to 0.9.4-2)
  • Migration status for rust-cddl/riscv64 (0.9.4-2 to 0.9.4-2): Will attempt migration (Any information below is purely informational)
• rust-cddl/s390x (0.9.4-2 to 0.9.4-2)
  • Migration status for rust-cddl/s390x (0.9.4-2 to 0.9.4-2): Will attempt migration (Any information below is purely informational)
• rust-cid-npm/riscv64 (0.0~git20200813.59cf068-2 to 0.0~git20200813.59cf068-2)
  • Migration status for rust-cid-npm/riscv64 (0.0~git20200813.59cf068-2 to 0.0~git20200813.59cf068-2): Will attempt migration (Any information below is purely informational)
• rust-cid-npm/s390x (0.0~git20200813.59cf068-2 to 0.0~git20200813.59cf068-2)
  • Migration status for rust-cid-npm/s390x (0.0~git20200813.59cf068-2 to 0.0~git20200813.59cf068-2): Will attempt migration (Any information below is purely informational)
• rust-cntr/riscv64 (1.6.0-2 to 1.6.0-2)
  • Migration status for rust-cntr/riscv64 (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
• rust-cntr/s390x (1.6.0-2 to 1.6.0-2)
  • Migration status for rust-cntr/s390x (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
• rust-cotp/riscv64 (1.9.2-1 to 1.9.2-1)
  • Migration status for rust-cotp/riscv64 (1.9.2-1 to 1.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-cotp/s390x (1.9.2-1 to 1.9.2-1)
  • Migration status for rust-cotp/s390x (1.9.2-1 to 1.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-csv2svg/riscv64 (0.2.2-2 to 0.2.2-2)
  • Migration status for rust-csv2svg/riscv64 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
• rust-debian-repro-status/amd64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-debian-repro-status/amd64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-debian-repro-status/amd64 rust-hyper-rustls
• rust-debian-repro-status/arm64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-debian-repro-status/arm64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-debian-repro-status/arm64 rust-hyper-rustls
• rust-debian-repro-status/armel (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-debian-repro-status/armel (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-debian-repro-status/armel rust-hyper-rustls
• rust-debian-repro-status/armhf (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-debian-repro-status/armhf (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-debian-repro-status/armhf rust-hyper-rustls
• rust-debian-repro-status/i386 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-debian-repro-status/i386 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-debian-repro-status/i386 rust-hyper-rustls
• rust-debian-repro-status/ppc64el (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-debian-repro-status/ppc64el (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-debian-repro-status/ppc64el rust-hyper-rustls
• rust-debian-repro-status/riscv64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-debian-repro-status/riscv64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-debian-repro-status/riscv64 rust-hyper-rustls
• rust-dfrs/riscv64 (0.0.7-11 to 0.0.7-11)
  • Migration status for rust-dfrs/riscv64 (0.0.7-11 to 0.0.7-11): Will attempt migration (Any information below is purely informational)
• rust-diffr/mips64el (0.1.5-2 to 0.1.5-2)
  • Migration status for rust-diffr/mips64el (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• rust-diffr/riscv64 (0.1.5-2 to 0.1.5-2)
  • Migration status for rust-diffr/riscv64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• rust-diffutils/riscv64 (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-diffutils/riscv64 (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-drt-tools/riscv64 (0.2.26-1 to 0.2.26-1)
  • Migration status for rust-drt-tools/riscv64 (0.2.26-1 to 0.2.26-1): Will attempt migration (Any information below is purely informational)
• rust-dysk/riscv64 (2.10.0-2 to 2.10.0-2)
  • Migration status for rust-dysk/riscv64 (2.10.0-2 to 2.10.0-2): Will attempt migration (Any information below is purely informational)
• rust-erbium/riscv64 (1.0.5-2 to 1.0.5-2)
  • Migration status for rust-erbium/riscv64 (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• rust-eza/armel (0.20.14-1 to 0.20.14-1)
  • Migration status for rust-eza/armel (0.20.14-1 to 0.20.14-1): Will attempt migration (Any information below is purely informational)
• rust-eza/riscv64 (0.20.14-1 to 0.20.14-1)
  • Migration status for rust-eza/riscv64 (0.20.14-1 to 0.20.14-1): Will attempt migration (Any information below is purely informational)
• rust-fd-find/riscv64 (10.2.0-1 to 10.2.0-1)
  • Migration status for rust-fd-find/riscv64 (10.2.0-1 to 10.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-gping/armel (1.19.0-1 to 1.19.0-1)
  • Migration status for rust-gping/armel (1.19.0-1 to 1.19.0-1): Will attempt migration (Any information below is purely informational)
• rust-gping/riscv64 (1.19.0-1 to 1.19.0-1)
  • Migration status for rust-gping/riscv64 (1.19.0-1 to 1.19.0-1): Will attempt migration (Any information below is purely informational)
• rust-grcov/armhf (0.8.20-1 to 0.8.20-1)
  • Migration status for rust-grcov/armhf (0.8.20-1 to 0.8.20-1): Will attempt migration (Any information below is purely informational)
• rust-grcov/riscv64 (0.8.20-1 to 0.8.20-1)
  • Migration status for rust-grcov/riscv64 (0.8.20-1 to 0.8.20-1): Will attempt migration (Any information below is purely informational)
• rust-hyperfine/armhf (1.19.0-1 to 1.19.0-1)
  • Migration status for rust-hyperfine/armhf (1.19.0-1 to 1.19.0-1): Will attempt migration (Any information below is purely informational)
• rust-hyperfine/riscv64 (1.19.0-1 to 1.19.0-1)
  • Migration status for rust-hyperfine/riscv64 (1.19.0-1 to 1.19.0-1): Will attempt migration (Any information below is purely informational)
• rust-just/armel (1.39.0-1 to 1.39.0-1)
  • Migration status for rust-just/armel (1.39.0-1 to 1.39.0-1): Will attempt migration (Any information below is purely informational)
• rust-just/armhf (1.39.0-1 to 1.39.0-1)
  • Migration status for rust-just/armhf (1.39.0-1 to 1.39.0-1): Will attempt migration (Any information below is purely informational)
• rust-just/riscv64 (1.39.0-1 to 1.39.0-1)
  • Migration status for rust-just/riscv64 (1.39.0-1 to 1.39.0-1): Will attempt migration (Any information below is purely informational)
• rust-kmon/armel (1.6.5-1 to 1.6.5-1)
  • Migration status for rust-kmon/armel (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
• rust-kmon/armhf (1.6.5-1 to 1.6.5-1)
  • Migration status for rust-kmon/armhf (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
• rust-kmon/riscv64 (1.6.5-1 to 1.6.5-1)
  • Migration status for rust-kmon/riscv64 (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
• rust-libbpf-cargo/armel (0.25.0~beta.1-1 to 0.25.0~beta.1-1)
  • Migration status for rust-libbpf-cargo/armel (0.25.0~beta.1-1 to 0.25.0~beta.1-1): Will attempt migration (Any information below is purely informational)
• rust-libbpf-cargo/armhf (0.25.0~beta.1-1 to 0.25.0~beta.1-1)
  • Migration status for rust-libbpf-cargo/armhf (0.25.0~beta.1-1 to 0.25.0~beta.1-1): Will attempt migration (Any information below is purely informational)
• rust-libbpf-cargo/riscv64 (0.25.0~beta.1-1 to 0.25.0~beta.1-1)
  • Migration status for rust-libbpf-cargo/riscv64 (0.25.0~beta.1-1 to 0.25.0~beta.1-1): Will attempt migration (Any information below is purely informational)
• rust-libslirp/armel (4.3.2-1 to 4.3.2-1)
  • Migration status for rust-libslirp/armel (4.3.2-1 to 4.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-libslirp/armhf (4.3.2-1 to 4.3.2-1)
  • Migration status for rust-libslirp/armhf (4.3.2-1 to 4.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-libslirp/riscv64 (4.3.2-1 to 4.3.2-1)
  • Migration status for rust-libslirp/riscv64 (4.3.2-1 to 4.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-linescroll/armel (0.2.0-2 to 0.2.0-2)
  • Migration status for rust-linescroll/armel (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-linescroll/armhf (0.2.0-2 to 0.2.0-2)
  • Migration status for rust-linescroll/armhf (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-linescroll/mips64el (0.2.0-2 to 0.2.0-2)
  • Migration status for rust-linescroll/mips64el (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-linescroll/riscv64 (0.2.0-2 to 0.2.0-2)
  • Migration status for rust-linescroll/riscv64 (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-lsd/armel (1.1.5-3 to 1.1.5-3)
  • Migration status for rust-lsd/armel (1.1.5-3 to 1.1.5-3): Will attempt migration (Any information below is purely informational)
• rust-lsd/armhf (1.1.5-3 to 1.1.5-3)
  • Migration status for rust-lsd/armhf (1.1.5-3 to 1.1.5-3): Will attempt migration (Any information below is purely informational)
• rust-lsd/riscv64 (1.1.5-3 to 1.1.5-3)
  • Migration status for rust-lsd/riscv64 (1.1.5-3 to 1.1.5-3): Will attempt migration (Any information below is purely informational)
• rust-magic-wormhole-cli/armel (0.7.5-1 to 0.7.5-1)
  • Migration status for rust-magic-wormhole-cli/armel (0.7.5-1 to 0.7.5-1): Will attempt migration (Any information below is purely informational)
• rust-magic-wormhole-cli/armhf (0.7.5-1 to 0.7.5-1)
  • Migration status for rust-magic-wormhole-cli/armhf (0.7.5-1 to 0.7.5-1): Will attempt migration (Any information below is purely informational)
• rust-meow-cli/armel (2.1.4-1 to 2.1.4-1)
  • Migration status for rust-meow-cli/armel (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-meow-cli/armhf (2.1.4-1 to 2.1.4-1)
  • Migration status for rust-meow-cli/armhf (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-meow-cli/riscv64 (2.1.4-1 to 2.1.4-1)
  • Migration status for rust-meow-cli/riscv64 (2.1.4-1 to 2.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-netr/armel (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-netr/armel (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-netr/armhf (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-netr/armhf (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-netr/mips64el (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-netr/mips64el (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-netr/riscv64 (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-netr/riscv64 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-nitrocli/armel (0.2.4-2 to 0.2.4-2)
  • Migration status for rust-nitrocli/armel (0.2.4-2 to 0.2.4-2): Will attempt migration (Any information below is purely informational)
• rust-nitrocli/armhf (0.2.4-2 to 0.2.4-2)
  • Migration status for rust-nitrocli/armhf (0.2.4-2 to 0.2.4-2): Will attempt migration (Any information below is purely informational)
• rust-nitrocli/mips64el (0.2.4-2 to 0.2.4-2)
  • Migration status for rust-nitrocli/mips64el (0.2.4-2 to 0.2.4-2): Will attempt migration (Any information below is purely informational)
• rust-nitrocli/riscv64 (0.2.4-2 to 0.2.4-2)
  • Migration status for rust-nitrocli/riscv64 (0.2.4-2 to 0.2.4-2): Will attempt migration (Any information below is purely informational)
• rust-numbat-cli/armel (1.11.0-2 to 1.11.0-2)
  • Migration status for rust-numbat-cli/armel (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• rust-numbat-cli/armhf (1.11.0-2 to 1.11.0-2)
  • Migration status for rust-numbat-cli/armhf (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• rust-numbat-cli/riscv64 (1.11.0-2 to 1.11.0-2)
  • Migration status for rust-numbat-cli/riscv64 (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• rust-ognibuild/armel (0.0.32-2 to 0.0.32-2)
  • Migration status for rust-ognibuild/armel (0.0.32-2 to 0.0.32-2): Will attempt migration (Any information below is purely informational)
• rust-ognibuild/armhf (0.0.32-2 to 0.0.32-2)
  • Migration status for rust-ognibuild/armhf (0.0.32-2 to 0.0.32-2): Will attempt migration (Any information below is purely informational)
• rust-parsec-tool/armel (0.7.0-6 to 0.7.0-6)
  • Migration status for rust-parsec-tool/armel (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• rust-parsec-tool/armhf (0.7.0-6 to 0.7.0-6)
  • Migration status for rust-parsec-tool/armhf (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• rust-pleaser/armel (0.5.6-1 to 0.5.6-1)
  • Migration status for rust-pleaser/armel (0.5.6-1 to 0.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-pleaser/armhf (0.5.6-1 to 0.5.6-1)
  • Migration status for rust-pleaser/armhf (0.5.6-1 to 0.5.6-1): Will attempt migration (Any information below is purely informational)
• rust-process-viewer/armel (0.5.9-6 to 0.5.9-6)
  • Migration status for rust-process-viewer/armel (0.5.9-6 to 0.5.9-6): Will attempt migration (Any information below is purely informational)
• rust-process-viewer/armhf (0.5.9-6 to 0.5.9-6)
  • Migration status for rust-process-viewer/armhf (0.5.9-6 to 0.5.9-6): Will attempt migration (Any information below is purely informational)
• rust-procs/armel (0.14.9-1 to 0.14.9-1)
  • Migration status for rust-procs/armel (0.14.9-1 to 0.14.9-1): Will attempt migration (Any information below is purely informational)
• rust-procs/armhf (0.14.9-1 to 0.14.9-1)
  • Migration status for rust-procs/armhf (0.14.9-1 to 0.14.9-1): Will attempt migration (Any information below is purely informational)
• rust-prr/amd64 (0.18.0-3 to 0.18.0-3)
  • Migration status for rust-prr/amd64 (0.18.0-3 to 0.18.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-prr/amd64 rust-hyper-rustls
• rust-prr/arm64 (0.18.0-3 to 0.18.0-3)
  • Migration status for rust-prr/arm64 (0.18.0-3 to 0.18.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-prr/arm64 rust-hyper-rustls
• rust-prr/armel (0.18.0-3 to 0.18.0-3)
  • Migration status for rust-prr/armel (0.18.0-3 to 0.18.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-prr/armel rust-hyper-rustls
• rust-prr/armhf (0.18.0-3 to 0.18.0-3)
  • Migration status for rust-prr/armhf (0.18.0-3 to 0.18.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-prr/armhf rust-hyper-rustls
• rust-prr/i386 (0.18.0-3 to 0.18.0-3)
  • Migration status for rust-prr/i386 (0.18.0-3 to 0.18.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-prr/i386 rust-hyper-rustls
• rust-prr/ppc64el (0.18.0-3 to 0.18.0-3)
  • Migration status for rust-prr/ppc64el (0.18.0-3 to 0.18.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-prr/ppc64el rust-hyper-rustls
• rust-pulldown-cmark/armel (0.10.3-1 to 0.10.3-1)
  • Migration status for rust-pulldown-cmark/armel (0.10.3-1 to 0.10.3-1): Will attempt migration (Any information below is purely informational)
• rust-pulldown-cmark/armhf (0.10.3-1 to 0.10.3-1)
  • Migration status for rust-pulldown-cmark/armhf (0.10.3-1 to 0.10.3-1): Will attempt migration (Any information below is purely informational)
• rust-pulldown-cmark/mips64el (0.10.3-1 to 0.10.3-1)
  • Migration status for rust-pulldown-cmark/mips64el (0.10.3-1 to 0.10.3-1): Will attempt migration (Any information below is purely informational)
• rust-rav1e/armel (0.7.1-9 to 0.7.1-9)
  • Migration status for rust-rav1e/armel (0.7.1-9 to 0.7.1-9): Will attempt migration (Any information below is purely informational)
• rust-rav1e/armhf (0.7.1-9 to 0.7.1-9)
  • Migration status for rust-rav1e/armhf (0.7.1-9 to 0.7.1-9): Will attempt migration (Any information below is purely informational)
• rust-rebuildctl/armel (0.21.0-2 to 0.21.0-2)
  • Migration status for rust-rebuildctl/armel (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
• rust-rebuildctl/armhf (0.21.0-2 to 0.21.0-2)
  • Migration status for rust-rebuildctl/armhf (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
• rust-rebuilderd-worker/armel (0.21.0-2 to 0.21.0-2)
  • Migration status for rust-rebuilderd-worker/armel (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
• rust-rebuilderd-worker/armhf (0.21.0-2 to 0.21.0-2)
  • Migration status for rust-rebuilderd-worker/armhf (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
• rust-regolith-powerd/armel (0.3.9-1 to 0.3.9-1)
  • Migration status for rust-regolith-powerd/armel (0.3.9-1 to 0.3.9-1): Will attempt migration (Any information below is purely informational)
• rust-regolith-powerd/armhf (0.3.9-1 to 0.3.9-1)
  • Migration status for rust-regolith-powerd/armhf (0.3.9-1 to 0.3.9-1): Will attempt migration (Any information below is purely informational)
• rust-repro-env/amd64 (0.4.1-2 to 0.4.1-2)
  • Migration status for rust-repro-env/amd64 (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-repro-env/amd64 rust-hyper-rustls
• rust-repro-env/arm64 (0.4.1-2 to 0.4.1-2)
  • Migration status for rust-repro-env/arm64 (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-repro-env/arm64 rust-hyper-rustls
• rust-repro-env/ppc64el (0.4.1-2 to 0.4.1-2)
  • Migration status for rust-repro-env/ppc64el (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-repro-env/ppc64el rust-hyper-rustls
• rust-ripgrep/armel (14.1.1-1 to 14.1.1-1)
  • Migration status for rust-ripgrep/armel (14.1.1-1 to 14.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-ripgrep/armhf (14.1.1-1 to 14.1.1-1)
  • Migration status for rust-ripgrep/armhf (14.1.1-1 to 14.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-rockusb/armel (0.2.0-2 to 0.2.0-2)
  • Migration status for rust-rockusb/armel (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-rockusb/armhf (0.2.0-2 to 0.2.0-2)
  • Migration status for rust-rockusb/armhf (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-rpacket/armel (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-rpacket/armel (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-rpacket/armhf (0.1.4-1 to 0.1.4-1)
  • Migration status for rust-rpacket/armhf (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• rust-rustfilt/armel (0.2.1-2 to 0.2.1-2)
  • Migration status for rust-rustfilt/armel (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-rustfilt/armhf (0.2.1-2 to 0.2.1-2)
  • Migration status for rust-rustfilt/armhf (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-rusty-tags/armel (3.10.0-1 to 3.10.0-1)
  • Migration status for rust-rusty-tags/armel (3.10.0-1 to 3.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-rusty-tags/armhf (3.10.0-1 to 3.10.0-1)
  • Migration status for rust-rusty-tags/armhf (3.10.0-1 to 3.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-scriptisto/armel (2.2.0-2 to 2.2.0-2)
  • Migration status for rust-scriptisto/armel (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-scriptisto/armhf (2.2.0-2 to 2.2.0-2)
  • Migration status for rust-scriptisto/armhf (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-sd/armel (1.0.0-3 to 1.0.0-3)
  • Migration status for rust-sd/armel (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
• rust-sd/armhf (1.0.0-3 to 1.0.0-3)
  • Migration status for rust-sd/armhf (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
• rust-sequoia-keyring-linter/armel (1.0.1-4 to 1.0.1-4)
  • Migration status for rust-sequoia-keyring-linter/armel (1.0.1-4 to 1.0.1-4): Will attempt migration (Any information below is purely informational)
• rust-sequoia-keyring-linter/armhf (1.0.1-4 to 1.0.1-4)
  • Migration status for rust-sequoia-keyring-linter/armhf (1.0.1-4 to 1.0.1-4): Will attempt migration (Any information below is purely informational)
• rust-sequoia-keystore-server/amd64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-sequoia-keystore-server/amd64 (0.1.0-1 to 0.1.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-keystore-server/amd64 rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-keystore-server/arm64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-sequoia-keystore-server/arm64 (0.1.0-1 to 0.1.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-keystore-server/arm64 rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-keystore-server/armel (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-sequoia-keystore-server/armel (0.1.0-1 to 0.1.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-keystore-server/armel rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-keystore-server/armhf (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-sequoia-keystore-server/armhf (0.1.0-1 to 0.1.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-keystore-server/armhf rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-keystore-server/i386 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-sequoia-keystore-server/i386 (0.1.0-1 to 0.1.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-keystore-server/i386 rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-keystore-server/ppc64el (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-sequoia-keystore-server/ppc64el (0.1.0-1 to 0.1.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-keystore-server/ppc64el rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-sop/armel (0.36.1-1 to 0.36.1-1)
  • Migration status for rust-sequoia-sop/armel (0.36.1-1 to 0.36.1-1): Will attempt migration (Any information below is purely informational)
• rust-sequoia-sop/armhf (0.36.1-1 to 0.36.1-1)
  • Migration status for rust-sequoia-sop/armhf (0.36.1-1 to 0.36.1-1): Will attempt migration (Any information below is purely informational)
• rust-sequoia-sq/amd64 (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-sequoia-sq/amd64 (1.2.0-1 to 1.2.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-sq/amd64 rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-sq/arm64 (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-sequoia-sq/arm64 (1.2.0-1 to 1.2.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-sq/arm64 rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-sq/armel (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-sequoia-sq/armel (1.2.0-1 to 1.2.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-sq/armel rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-sq/armhf (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-sequoia-sq/armhf (1.2.0-1 to 1.2.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-sq/armhf rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-sq/i386 (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-sequoia-sq/i386 (1.2.0-1 to 1.2.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-sq/i386 rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-sq/ppc64el (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-sequoia-sq/ppc64el (1.2.0-1 to 1.2.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: rust-sequoia-sq/ppc64el rust-sequoia-keystore (not considered)
    • Invalidated by built-using
• rust-sequoia-sqv/armel (1.2.1-6 to 1.2.1-6)
  • Migration status for rust-sequoia-sqv/armel (1.2.1-6 to 1.2.1-6): Will attempt migration (Any information below is purely informational)
• rust-sequoia-sqv/armhf (1.2.1-6 to 1.2.1-6)
  • Migration status for rust-sequoia-sqv/armhf (1.2.1-6 to 1.2.1-6): Will attempt migration (Any information below is purely informational)
• rust-spytrap-adb/amd64 (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-spytrap-adb/amd64 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-spytrap-adb/amd64 rust-hyper-rustls
• rust-spytrap-adb/arm64 (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-spytrap-adb/arm64 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-spytrap-adb/arm64 rust-hyper-rustls
• rust-spytrap-adb/armel (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-spytrap-adb/armel (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-spytrap-adb/armel rust-hyper-rustls
• rust-spytrap-adb/armhf (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-spytrap-adb/armhf (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-spytrap-adb/armhf rust-hyper-rustls
• rust-spytrap-adb/i386 (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-spytrap-adb/i386 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-spytrap-adb/i386 rust-hyper-rustls
• rust-spytrap-adb/ppc64el (0.3.3-2 to 0.3.3-2)
  • Migration status for rust-spytrap-adb/ppc64el (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-spytrap-adb/ppc64el rust-hyper-rustls
• rust-swaysome/armel (2.1.2-1 to 2.1.2-1)
  • Migration status for rust-swaysome/armel (2.1.2-1 to 2.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-swaysome/armhf (2.1.2-1 to 2.1.2-1)
  • Migration status for rust-swaysome/armhf (2.1.2-1 to 2.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-swtchr/armel (0.1.2-6 to 0.1.2-6)
  • Migration status for rust-swtchr/armel (0.1.2-6 to 0.1.2-6): Will attempt migration (Any information below is purely informational)
• rust-swtchr/armhf (0.1.2-6 to 0.1.2-6)
  • Migration status for rust-swtchr/armhf (0.1.2-6 to 0.1.2-6): Will attempt migration (Any information below is purely informational)
• rust-tealdeer/armel (1.7.0-2 to 1.7.0-2)
  • Migration status for rust-tealdeer/armel (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
• rust-tealdeer/armhf (1.7.0-2 to 1.7.0-2)
  • Migration status for rust-tealdeer/armhf (1.7.0-2 to 1.7.0-2): Will attempt migration (Any information below is purely informational)
• rust-tokei/arm64 (12.1.2-5 to 12.1.2-5)
  • Migration status for rust-tokei/arm64 (12.1.2-5 to 12.1.2-5): Will attempt migration (Any information below is purely informational)
• rust-tokei/armel (12.1.2-5 to 12.1.2-5)
  • Migration status for rust-tokei/armel (12.1.2-5 to 12.1.2-5): Will attempt migration (Any information below is purely informational)
• rust-tokei/armhf (12.1.2-5 to 12.1.2-5)
  • Migration status for rust-tokei/armhf (12.1.2-5 to 12.1.2-5): Will attempt migration (Any information below is purely informational)
• rust-toml2json/arm64 (1.3.1-1 to 1.3.1-1)
  • Migration status for rust-toml2json/arm64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-toml2json/armel (1.3.1-1 to 1.3.1-1)
  • Migration status for rust-toml2json/armel (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-toml2json/armhf (1.3.1-1 to 1.3.1-1)
  • Migration status for rust-toml2json/armhf (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-trawld/arm64 (0.2.8-1 to 0.2.8-1)
  • Migration status for rust-trawld/arm64 (0.2.8-1 to 0.2.8-1): Will attempt migration (Any information below is purely informational)
• rust-trawld/armel (0.2.8-1 to 0.2.8-1)
  • Migration status for rust-trawld/armel (0.2.8-1 to 0.2.8-1): Will attempt migration (Any information below is purely informational)
• rust-trawld/armhf (0.2.8-1 to 0.2.8-1)
  • Migration status for rust-trawld/armhf (0.2.8-1 to 0.2.8-1): Will attempt migration (Any information below is purely informational)
• rust-trawldb/arm64 (0.2.9-1 to 0.2.9-1)
  • Migration status for rust-trawldb/arm64 (0.2.9-1 to 0.2.9-1): Will attempt migration (Any information below is purely informational)
• rust-trawldb/armel (0.2.9-1 to 0.2.9-1)
  • Migration status for rust-trawldb/armel (0.2.9-1 to 0.2.9-1): Will attempt migration (Any information below is purely informational)
• rust-trawldb/armhf (0.2.9-1 to 0.2.9-1)
  • Migration status for rust-trawldb/armhf (0.2.9-1 to 0.2.9-1): Will attempt migration (Any information below is purely informational)
• rust-tre-command/arm64 (0.4.0-6 to 0.4.0-6)
  • Migration status for rust-tre-command/arm64 (0.4.0-6 to 0.4.0-6): Will attempt migration (Any information below is purely informational)
• rust-tre-command/armel (0.4.0-6 to 0.4.0-6)
  • Migration status for rust-tre-command/armel (0.4.0-6 to 0.4.0-6): Will attempt migration (Any information below is purely informational)
• rust-tre-command/armhf (0.4.0-6 to 0.4.0-6)
  • Migration status for rust-tre-command/armhf (0.4.0-6 to 0.4.0-6): Will attempt migration (Any information below is purely informational)
• rust-ucd-generate/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-ucd-generate/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-generate/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-ucd-generate/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-ucd-generate/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-ucd-generate/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-vivid/arm64 (0.9.0-2 to 0.9.0-2)
  • Migration status for rust-vivid/arm64 (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• rust-vivid/armel (0.9.0-2 to 0.9.0-2)
  • Migration status for rust-vivid/armel (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• rust-vivid/armhf (0.9.0-2 to 0.9.0-2)
  • Migration status for rust-vivid/armhf (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• rust-xh/amd64 (0.23.1-3 to 0.23.1-3)
  • Migration status for rust-xh/amd64 (0.23.1-3 to 0.23.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-xh/amd64 rust-hyper-rustls
• rust-xh/arm64 (0.23.1-3 to 0.23.1-3)
  • Migration status for rust-xh/arm64 (0.23.1-3 to 0.23.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-xh/arm64 rust-hyper-rustls
• rust-xh/armel (0.23.1-3 to 0.23.1-3)
  • Migration status for rust-xh/armel (0.23.1-3 to 0.23.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-xh/armel rust-hyper-rustls
• rust-xh/armhf (0.23.1-3 to 0.23.1-3)
  • Migration status for rust-xh/armhf (0.23.1-3 to 0.23.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-xh/armhf rust-hyper-rustls
• rust-xh/i386 (0.23.1-3 to 0.23.1-3)
  • Migration status for rust-xh/i386 (0.23.1-3 to 0.23.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-xh/i386 rust-hyper-rustls
• rust-xh/ppc64el (0.23.1-3 to 0.23.1-3)
  • Migration status for rust-xh/ppc64el (0.23.1-3 to 0.23.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: rust-xh/ppc64el rust-hyper-rustls
• rust-zoxide/arm64 (0.9.6-1 to 0.9.6-1)
  • Migration status for rust-zoxide/arm64 (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• rust-zoxide/armel (0.9.6-1 to 0.9.6-1)
  • Migration status for rust-zoxide/armel (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• rust-zoxide/armhf (0.9.6-1 to 0.9.6-1)
  • Migration status for rust-zoxide/armhf (0.9.6-1 to 0.9.6-1): Will attempt migration (Any information below is purely informational)
• rust-zram-generator/arm64 (1.2.1-1 to 1.2.1-1)
  • Migration status for rust-zram-generator/arm64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-zram-generator/armel (1.2.1-1 to 1.2.1-1)
  • Migration status for rust-zram-generator/armel (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-zram-generator/armhf (1.2.1-1 to 1.2.1-1)
  • Migration status for rust-zram-generator/armhf (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• rustup/arm64 (1.27.1-2 to 1.27.1-2)
  • Migration status for rustup/arm64 (1.27.1-2 to 1.27.1-2): Will attempt migration (Any information below is purely informational)
• rustup/armhf (1.27.1-2 to 1.27.1-2)
  • Migration status for rustup/armhf (1.27.1-2 to 1.27.1-2): Will attempt migration (Any information below is purely informational)
• seqan3_pu (3.3.0+ds-3 to 3.2.0+ds-6+deb12u1)
  • Migration status for seqan3_pu (3.3.0+ds-3 to 3.2.0+ds-6+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: seqan3 is newer in the target suite (3.3.0+ds-3 3.2.0+ds-6+deb12u1)
• simgear_pu (1:2020.3.19+dfsg-1 to 1:2020.3.16+dfsg-1+deb12u1)
  • Migration status for simgear_pu (1:2020.3.19+dfsg-1 to 1:2020.3.16+dfsg-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: simgear is newer in the target suite (1:2020.3.19+dfsg-1 1:2020.3.16+dfsg-1+deb12u1)
• snapcast_pu (0.30.0-1 to 0.26.0+dfsg1-1+deb12u1)
  • Migration status for snapcast_pu (0.30.0-1 to 0.26.0+dfsg1-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: snapcast is newer in the target suite (0.30.0-1 0.26.0+dfsg1-1+deb12u1)
• sortmerna/amd64 (4.3.7-2 to 4.3.7-2)
  • Migration status for sortmerna/amd64 (4.3.7-2 to 4.3.7-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: sortmerna/amd64 rocksdb (not considered)
    • Invalidated by dependency
• sortmerna/i386 (4.3.7-2 to 4.3.7-2)
  • Migration status for sortmerna/i386 (4.3.7-2 to 4.3.7-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: sortmerna/i386 rocksdb (not considered)
    • Invalidated by dependency
• stfl/amd64 (0.22-5 to 0.22-5)
  • Migration status for stfl/amd64 (0.22-5 to 0.22-5): Will attempt migration (Any information below is purely informational)
• stfl/arm64 (0.22-5 to 0.22-5)
  • Migration status for stfl/arm64 (0.22-5 to 0.22-5): Will attempt migration (Any information below is purely informational)
• stfl/armel (0.22-5 to 0.22-5)
  • Migration status for stfl/armel (0.22-5 to 0.22-5): Will attempt migration (Any information below is purely informational)
• stfl/armhf (0.22-5 to 0.22-5)
  • Migration status for stfl/armhf (0.22-5 to 0.22-5): Will attempt migration (Any information below is purely informational)
• stfl/i386 (0.22-5 to 0.22-5)
  • Migration status for stfl/i386 (0.22-5 to 0.22-5): Will attempt migration (Any information below is purely informational)
• stfl/mips64el (0.22-5 to 0.22-5)
  • Migration status for stfl/mips64el (0.22-5 to 0.22-5): Will attempt migration (Any information below is purely informational)
• stfl/ppc64el (0.22-5 to 0.22-5)
  • Migration status for stfl/ppc64el (0.22-5 to 0.22-5): Will attempt migration (Any information below is purely informational)
• stfl/riscv64 (0.22-5 to 0.22-5)
  • Migration status for stfl/riscv64 (0.22-5 to 0.22-5): Will attempt migration (Any information below is purely informational)
• stfl/s390x (0.22-5 to 0.22-5)
  • Migration status for stfl/s390x (0.22-5 to 0.22-5): Will attempt migration (Any information below is purely informational)
• subversion_pu (1.14.5-2 to 1.14.2-4+deb12u1)
  • Migration status for subversion_pu (1.14.5-2 to 1.14.2-4+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: subversion is newer in the target suite (1.14.5-2 1.14.2-4+deb12u1)
• sunpy_pu (6.0.4-1 to 4.1.2-1+deb12u1)
  • Migration status for sunpy_pu (6.0.4-1 to 4.1.2-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: sunpy is newer in the target suite (6.0.4-1 4.1.2-1+deb12u1)
• talksoup.app/amd64 (1.1-1 to 1.1-1)
  • Migration status for talksoup.app/amd64 (1.1-1 to 1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: talksoup.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• talksoup.app/arm64 (1.1-1 to 1.1-1)
  • Migration status for talksoup.app/arm64 (1.1-1 to 1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: talksoup.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• talksoup.app/armel (1.1-1 to 1.1-1)
  • Migration status for talksoup.app/armel (1.1-1 to 1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: talksoup.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• talksoup.app/armhf (1.1-1 to 1.1-1)
  • Migration status for talksoup.app/armhf (1.1-1 to 1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: talksoup.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• talksoup.app/i386 (1.1-1 to 1.1-1)
  • Migration status for talksoup.app/i386 (1.1-1 to 1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: talksoup.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• talksoup.app/mips64el (1.1-1 to 1.1-1)
  • Migration status for talksoup.app/mips64el (1.1-1 to 1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: talksoup.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• talksoup.app/ppc64el (1.1-1 to 1.1-1)
  • Migration status for talksoup.app/ppc64el (1.1-1 to 1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: talksoup.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• talksoup.app/riscv64 (1.1-1 to 1.1-1)
  • Migration status for talksoup.app/riscv64 (1.1-1 to 1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: talksoup.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• talksoup.app/s390x (1.1-1 to 1.1-1)
  • Migration status for talksoup.app/s390x (1.1-1 to 1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: talksoup.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• tdom/amd64 (0.9.5-1.1 to 0.9.5-1.1)
  • Migration status for tdom/amd64 (0.9.5-1.1 to 0.9.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tdom/amd64 gumbo-parser (not considered)
    • Invalidated by dependency
• tdom/arm64 (0.9.5-1.1 to 0.9.5-1.1)
  • Migration status for tdom/arm64 (0.9.5-1.1 to 0.9.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tdom/arm64 gumbo-parser (not considered)
    • Invalidated by dependency
• tdom/armel (0.9.5-1.1 to 0.9.5-1.1)
  • Migration status for tdom/armel (0.9.5-1.1 to 0.9.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tdom/armel gumbo-parser (not considered)
    • Invalidated by dependency
• tdom/armhf (0.9.5-1.1 to 0.9.5-1.1)
  • Migration status for tdom/armhf (0.9.5-1.1 to 0.9.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tdom/armhf gumbo-parser (not considered)
    • Invalidated by dependency
• tdom/i386 (0.9.5-1.1 to 0.9.5-1.1)
  • Migration status for tdom/i386 (0.9.5-1.1 to 0.9.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tdom/i386 gumbo-parser (not considered)
    • Invalidated by dependency
• tdom/mips64el (0.9.5-1.1 to 0.9.5-1.1)
  • Migration status for tdom/mips64el (0.9.5-1.1 to 0.9.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tdom/mips64el gumbo-parser (not considered)
    • Invalidated by dependency
• tdom/ppc64el (0.9.5-1.1 to 0.9.5-1.1)
  • Migration status for tdom/ppc64el (0.9.5-1.1 to 0.9.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tdom/ppc64el gumbo-parser (not considered)
    • Invalidated by dependency
• tdom/riscv64 (0.9.5-1.1 to 0.9.5-1.1)
  • Migration status for tdom/riscv64 (0.9.5-1.1 to 0.9.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tdom/riscv64 gumbo-parser (not considered)
    • Invalidated by dependency
• tdom/s390x (0.9.5-1.1 to 0.9.5-1.1)
  • Migration status for tdom/s390x (0.9.5-1.1 to 0.9.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tdom/s390x gumbo-parser (not considered)
    • Invalidated by dependency
• tea-cli/amd64 (0.9.2-1 to 0.9.2-1)
  • Migration status for tea-cli/amd64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tea-cli/amd64 golang-1.23
• tea-cli/arm64 (0.9.2-1 to 0.9.2-1)
  • Migration status for tea-cli/arm64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tea-cli/arm64 golang-1.23
• tea-cli/armel (0.9.2-1 to 0.9.2-1)
  • Migration status for tea-cli/armel (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tea-cli/armel golang-1.23
• tea-cli/armhf (0.9.2-1 to 0.9.2-1)
  • Migration status for tea-cli/armhf (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tea-cli/armhf golang-1.23
• tea-cli/i386 (0.9.2-1 to 0.9.2-1)
  • Migration status for tea-cli/i386 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tea-cli/i386 golang-1.23
• tea-cli/mips64el (0.9.2-1 to 0.9.2-1)
  • Migration status for tea-cli/mips64el (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tea-cli/mips64el golang-1.23
• tea-cli/ppc64el (0.9.2-1 to 0.9.2-1)
  • Migration status for tea-cli/ppc64el (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tea-cli/ppc64el golang-1.23
• tea-cli/riscv64 (0.9.2-1 to 0.9.2-1)
  • Migration status for tea-cli/riscv64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tea-cli/riscv64 golang-1.23
• tea-cli/s390x (0.9.2-1 to 0.9.2-1)
  • Migration status for tea-cli/s390x (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tea-cli/s390x golang-1.23
• terminal.app/amd64 (0.9.9-5 to 0.9.9-5)
  • Migration status for terminal.app/amd64 (0.9.9-5 to 0.9.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: terminal.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• terminal.app/arm64 (0.9.9-5 to 0.9.9-5)
  • Migration status for terminal.app/arm64 (0.9.9-5 to 0.9.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: terminal.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• terminal.app/armel (0.9.9-5 to 0.9.9-5)
  • Migration status for terminal.app/armel (0.9.9-5 to 0.9.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: terminal.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• terminal.app/armhf (0.9.9-5 to 0.9.9-5)
  • Migration status for terminal.app/armhf (0.9.9-5 to 0.9.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: terminal.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• terminal.app/i386 (0.9.9-5 to 0.9.9-5)
  • Migration status for terminal.app/i386 (0.9.9-5 to 0.9.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: terminal.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• terminal.app/mips64el (0.9.9-5 to 0.9.9-5)
  • Migration status for terminal.app/mips64el (0.9.9-5 to 0.9.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: terminal.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• terminal.app/ppc64el (0.9.9-5 to 0.9.9-5)
  • Migration status for terminal.app/ppc64el (0.9.9-5 to 0.9.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: terminal.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• terminal.app/riscv64 (0.9.9-5 to 0.9.9-5)
  • Migration status for terminal.app/riscv64 (0.9.9-5 to 0.9.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: terminal.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• terminal.app/s390x (0.9.9-5 to 0.9.9-5)
  • Migration status for terminal.app/s390x (0.9.9-5 to 0.9.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: terminal.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• terminews/amd64 (1.2.2-1 to 1.2.2-1)
  • Migration status for terminews/amd64 (1.2.2-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terminews/amd64 golang-1.23
• terminews/arm64 (1.2.2-1 to 1.2.2-1)
  • Migration status for terminews/arm64 (1.2.2-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terminews/arm64 golang-1.23
• terminews/armel (1.2.2-1 to 1.2.2-1)
  • Migration status for terminews/armel (1.2.2-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terminews/armel golang-1.23
• terminews/armhf (1.2.2-1 to 1.2.2-1)
  • Migration status for terminews/armhf (1.2.2-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terminews/armhf golang-1.23
• terminews/i386 (1.2.2-1 to 1.2.2-1)
  • Migration status for terminews/i386 (1.2.2-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terminews/i386 golang-1.23
• terminews/mips64el (1.2.2-1 to 1.2.2-1)
  • Migration status for terminews/mips64el (1.2.2-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terminews/mips64el golang-1.23
• terminews/ppc64el (1.2.2-1 to 1.2.2-1)
  • Migration status for terminews/ppc64el (1.2.2-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terminews/ppc64el golang-1.23
• terminews/riscv64 (1.2.2-1 to 1.2.2-1)
  • Migration status for terminews/riscv64 (1.2.2-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terminews/riscv64 golang-1.23
• terminews/s390x (1.2.2-1 to 1.2.2-1)
  • Migration status for terminews/s390x (1.2.2-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terminews/s390x golang-1.23
• termshark/amd64 (2.4.0-2 to 2.4.0-2)
  • Migration status for termshark/amd64 (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: termshark/amd64 golang-1.23
• termshark/arm64 (2.4.0-2 to 2.4.0-2)
  • Migration status for termshark/arm64 (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: termshark/arm64 golang-1.23
• termshark/armel (2.4.0-2 to 2.4.0-2)
  • Migration status for termshark/armel (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: termshark/armel golang-1.23
• termshark/armhf (2.4.0-2 to 2.4.0-2)
  • Migration status for termshark/armhf (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: termshark/armhf golang-1.23
• termshark/i386 (2.4.0-2 to 2.4.0-2)
  • Migration status for termshark/i386 (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: termshark/i386 golang-1.23
• termshark/mips64el (2.4.0-2 to 2.4.0-2)
  • Migration status for termshark/mips64el (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: termshark/mips64el golang-1.23
• termshark/ppc64el (2.4.0-2 to 2.4.0-2)
  • Migration status for termshark/ppc64el (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: termshark/ppc64el golang-1.23
• termshark/riscv64 (2.4.0-2 to 2.4.0-2)
  • Migration status for termshark/riscv64 (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: termshark/riscv64 golang-1.23
    • Built-Using: termshark/riscv64 golang-github-mattn-go-runewidth
• termshark/s390x (2.4.0-2 to 2.4.0-2)
  • Migration status for termshark/s390x (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: termshark/s390x golang-1.23
• terraform-switcher/amd64 (0.13.1308+ds-1 to 0.13.1308+ds-1)
  • Migration status for terraform-switcher/amd64 (0.13.1308+ds-1 to 0.13.1308+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terraform-switcher/amd64 golang-1.23
• terraform-switcher/arm64 (0.13.1308+ds-1 to 0.13.1308+ds-1)
  • Migration status for terraform-switcher/arm64 (0.13.1308+ds-1 to 0.13.1308+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terraform-switcher/arm64 golang-1.23
• terraform-switcher/armel (0.13.1308+ds-1 to 0.13.1308+ds-1)
  • Migration status for terraform-switcher/armel (0.13.1308+ds-1 to 0.13.1308+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terraform-switcher/armel golang-1.23
• terraform-switcher/armhf (0.13.1308+ds-1 to 0.13.1308+ds-1)
  • Migration status for terraform-switcher/armhf (0.13.1308+ds-1 to 0.13.1308+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terraform-switcher/armhf golang-1.23
• terraform-switcher/i386 (0.13.1308+ds-1 to 0.13.1308+ds-1)
  • Migration status for terraform-switcher/i386 (0.13.1308+ds-1 to 0.13.1308+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terraform-switcher/i386 golang-1.23
• terraform-switcher/mips64el (0.13.1308+ds-1 to 0.13.1308+ds-1)
  • Migration status for terraform-switcher/mips64el (0.13.1308+ds-1 to 0.13.1308+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terraform-switcher/mips64el golang-1.23
• terraform-switcher/ppc64el (0.13.1308+ds-1 to 0.13.1308+ds-1)
  • Migration status for terraform-switcher/ppc64el (0.13.1308+ds-1 to 0.13.1308+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terraform-switcher/ppc64el golang-1.23
• terraform-switcher/riscv64 (0.13.1308+ds-1 to 0.13.1308+ds-1)
  • Migration status for terraform-switcher/riscv64 (0.13.1308+ds-1 to 0.13.1308+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terraform-switcher/riscv64 golang-1.23
• terraform-switcher/s390x (0.13.1308+ds-1 to 0.13.1308+ds-1)
  • Migration status for terraform-switcher/s390x (0.13.1308+ds-1 to 0.13.1308+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: terraform-switcher/s390x golang-1.23
• textql/amd64 (2.0.3-5 to 2.0.3-5)
  • Migration status for textql/amd64 (2.0.3-5 to 2.0.3-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: textql/amd64 golang-1.23
• textql/arm64 (2.0.3-5 to 2.0.3-5)
  • Migration status for textql/arm64 (2.0.3-5 to 2.0.3-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: textql/arm64 golang-1.23
• textql/armel (2.0.3-5 to 2.0.3-5)
  • Migration status for textql/armel (2.0.3-5 to 2.0.3-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: textql/armel golang-1.23
• textql/armhf (2.0.3-5 to 2.0.3-5)
  • Migration status for textql/armhf (2.0.3-5 to 2.0.3-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: textql/armhf golang-1.23
• textql/i386 (2.0.3-5 to 2.0.3-5)
  • Migration status for textql/i386 (2.0.3-5 to 2.0.3-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: textql/i386 golang-1.23
• textql/mips64el (2.0.3-5 to 2.0.3-5)
  • Migration status for textql/mips64el (2.0.3-5 to 2.0.3-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: textql/mips64el golang-1.23
• textql/ppc64el (2.0.3-5 to 2.0.3-5)
  • Migration status for textql/ppc64el (2.0.3-5 to 2.0.3-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: textql/ppc64el golang-1.23
• textql/riscv64 (2.0.3-5 to 2.0.3-5)
  • Migration status for textql/riscv64 (2.0.3-5 to 2.0.3-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: textql/riscv64 golang-1.23
• textql/s390x (2.0.3-5 to 2.0.3-5)
  • Migration status for textql/s390x (2.0.3-5 to 2.0.3-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: textql/s390x golang-1.23
• tfk8s/amd64 (0.1.10-2 to 0.1.10-2)
  • Migration status for tfk8s/amd64 (0.1.10-2 to 0.1.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tfk8s/amd64 golang-1.23
• tfk8s/arm64 (0.1.10-2 to 0.1.10-2)
  • Migration status for tfk8s/arm64 (0.1.10-2 to 0.1.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tfk8s/arm64 golang-1.23
• tfk8s/armel (0.1.10-2 to 0.1.10-2)
  • Migration status for tfk8s/armel (0.1.10-2 to 0.1.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tfk8s/armel golang-1.23
• tfk8s/armhf (0.1.10-2 to 0.1.10-2)
  • Migration status for tfk8s/armhf (0.1.10-2 to 0.1.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tfk8s/armhf golang-1.23
• tfk8s/i386 (0.1.10-2 to 0.1.10-2)
  • Migration status for tfk8s/i386 (0.1.10-2 to 0.1.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tfk8s/i386 golang-1.23
• tfk8s/mips64el (0.1.10-2 to 0.1.10-2)
  • Migration status for tfk8s/mips64el (0.1.10-2 to 0.1.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tfk8s/mips64el golang-1.23
• tfk8s/ppc64el (0.1.10-2 to 0.1.10-2)
  • Migration status for tfk8s/ppc64el (0.1.10-2 to 0.1.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tfk8s/ppc64el golang-1.23
• tfk8s/riscv64 (0.1.10-2 to 0.1.10-2)
  • Migration status for tfk8s/riscv64 (0.1.10-2 to 0.1.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tfk8s/riscv64 golang-1.23
• tfk8s/s390x (0.1.10-2 to 0.1.10-2)
  • Migration status for tfk8s/s390x (0.1.10-2 to 0.1.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tfk8s/s390x golang-1.23
• tftp-proxy/amd64 (1.0.0-1 to 1.0.0-1)
  • Migration status for tftp-proxy/amd64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tftp-proxy/amd64 golang-1.23
• tftp-proxy/arm64 (1.0.0-1 to 1.0.0-1)
  • Migration status for tftp-proxy/arm64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tftp-proxy/arm64 golang-1.23
• tftp-proxy/armel (1.0.0-1 to 1.0.0-1)
  • Migration status for tftp-proxy/armel (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tftp-proxy/armel golang-1.23
• tftp-proxy/armhf (1.0.0-1 to 1.0.0-1)
  • Migration status for tftp-proxy/armhf (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tftp-proxy/armhf golang-1.23
• tftp-proxy/i386 (1.0.0-1 to 1.0.0-1)
  • Migration status for tftp-proxy/i386 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tftp-proxy/i386 golang-1.23
• tftp-proxy/mips64el (1.0.0-1 to 1.0.0-1)
  • Migration status for tftp-proxy/mips64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tftp-proxy/mips64el golang-1.23
• tftp-proxy/ppc64el (1.0.0-1 to 1.0.0-1)
  • Migration status for tftp-proxy/ppc64el (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tftp-proxy/ppc64el golang-1.23
• tftp-proxy/riscv64 (1.0.0-1 to 1.0.0-1)
  • Migration status for tftp-proxy/riscv64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tftp-proxy/riscv64 golang-1.23
• tftp-proxy/s390x (1.0.0-1 to 1.0.0-1)
  • Migration status for tftp-proxy/s390x (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tftp-proxy/s390x golang-1.23
• thin/amd64 (1.8.2-3 to 1.8.2-3)
  • Migration status for thin/amd64 (1.8.2-3 to 1.8.2-3): Will attempt migration (Any information below is purely informational)
• thin/arm64 (1.8.2-3 to 1.8.2-3)
  • Migration status for thin/arm64 (1.8.2-3 to 1.8.2-3): Will attempt migration (Any information below is purely informational)
• thin/armel (1.8.2-3 to 1.8.2-3)
  • Migration status for thin/armel (1.8.2-3 to 1.8.2-3): Will attempt migration (Any information below is purely informational)
• thin/i386 (1.8.2-3 to 1.8.2-3)
  • Migration status for thin/i386 (1.8.2-3 to 1.8.2-3): Will attempt migration (Any information below is purely informational)
• thin/mips64el (1.8.2-3 to 1.8.2-3)
  • Migration status for thin/mips64el (1.8.2-3 to 1.8.2-3): Will attempt migration (Any information below is purely informational)
• thin/ppc64el (1.8.2-3 to 1.8.2-3)
  • Migration status for thin/ppc64el (1.8.2-3 to 1.8.2-3): Will attempt migration (Any information below is purely informational)
• thin/riscv64 (1.8.2-3 to 1.8.2-3)
  • Migration status for thin/riscv64 (1.8.2-3 to 1.8.2-3): Will attempt migration (Any information below is purely informational)
• thunderbird_pu (1:128.6.0esr-1 to 1:128.6.0esr-1~deb12u1)
  • Migration status for thunderbird_pu (1:128.6.0esr-1 to 1:128.6.0esr-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: thunderbird is newer in the target suite (1:128.6.0esr-1 1:128.6.0esr-1~deb12u1)
• timemon.app/amd64 (4.2-3 to 4.2-3)
  • Migration status for timemon.app/amd64 (4.2-3 to 4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: timemon.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• timemon.app/arm64 (4.2-3 to 4.2-3)
  • Migration status for timemon.app/arm64 (4.2-3 to 4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: timemon.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• timemon.app/armel (4.2-3 to 4.2-3)
  • Migration status for timemon.app/armel (4.2-3 to 4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: timemon.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• timemon.app/armhf (4.2-3 to 4.2-3)
  • Migration status for timemon.app/armhf (4.2-3 to 4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: timemon.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• timemon.app/i386 (4.2-3 to 4.2-3)
  • Migration status for timemon.app/i386 (4.2-3 to 4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: timemon.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• timemon.app/mips64el (4.2-3 to 4.2-3)
  • Migration status for timemon.app/mips64el (4.2-3 to 4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: timemon.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• timemon.app/ppc64el (4.2-3 to 4.2-3)
  • Migration status for timemon.app/ppc64el (4.2-3 to 4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: timemon.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• timemon.app/riscv64 (4.2-3 to 4.2-3)
  • Migration status for timemon.app/riscv64 (4.2-3 to 4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: timemon.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• timemon.app/s390x (4.2-3 to 4.2-3)
  • Migration status for timemon.app/s390x (4.2-3 to 4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: timemon.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• tkey-ssh-agent/amd64 (1.0.0+ds-3 to 1.0.0+ds-3)
  • Migration status for tkey-ssh-agent/amd64 (1.0.0+ds-3 to 1.0.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: tkey-ssh-agent/amd64 golang-1.23
• tkey-ssh-agent/arm64 (1.0.0+ds-3 to 1.0.0+ds-3)
  • Migration status for tkey-ssh-agent/arm64 (1.0.0+ds-3 to 1.0.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: tkey-ssh-agent/arm64 golang-1.23
• tkey-ssh-agent/armel (1.0.0+ds-3 to 1.0.0+ds-3)
  • Migration status for tkey-ssh-agent/armel (1.0.0+ds-3 to 1.0.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: tkey-ssh-agent/armel golang-1.23
• tkey-ssh-agent/armhf (1.0.0+ds-3 to 1.0.0+ds-3)
  • Migration status for tkey-ssh-agent/armhf (1.0.0+ds-3 to 1.0.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: tkey-ssh-agent/armhf golang-1.23
• tkey-ssh-agent/i386 (1.0.0+ds-3 to 1.0.0+ds-3)
  • Migration status for tkey-ssh-agent/i386 (1.0.0+ds-3 to 1.0.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: tkey-ssh-agent/i386 golang-1.23
• tkey-ssh-agent/mips64el (1.0.0+ds-3 to 1.0.0+ds-3)
  • Migration status for tkey-ssh-agent/mips64el (1.0.0+ds-3 to 1.0.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: tkey-ssh-agent/mips64el golang-1.23
• tkey-ssh-agent/ppc64el (1.0.0+ds-3 to 1.0.0+ds-3)
  • Migration status for tkey-ssh-agent/ppc64el (1.0.0+ds-3 to 1.0.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: tkey-ssh-agent/ppc64el golang-1.23
• tkey-ssh-agent/riscv64 (1.0.0+ds-3 to 1.0.0+ds-3)
  • Migration status for tkey-ssh-agent/riscv64 (1.0.0+ds-3 to 1.0.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: tkey-ssh-agent/riscv64 golang-1.23
• tkey-ssh-agent/s390x (1.0.0+ds-3 to 1.0.0+ds-3)
  • Migration status for tkey-ssh-agent/s390x (1.0.0+ds-3 to 1.0.0+ds-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: tkey-ssh-agent/s390x golang-1.23
• tomcat10_pu (10.1.34-1 to 10.1.34-0+deb12u1)
  • Migration status for tomcat10_pu (10.1.34-1 to 10.1.34-0+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: tomcat10 is newer in the target suite (10.1.34-1 10.1.34-0+deb12u1)
• tty-record/amd64 (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1)
  • Migration status for tty-record/amd64 (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-record/amd64 golang-1.23
• tty-record/arm64 (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1)
  • Migration status for tty-record/arm64 (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-record/arm64 golang-1.23
• tty-record/armel (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1)
  • Migration status for tty-record/armel (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-record/armel golang-1.23
• tty-record/armhf (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1)
  • Migration status for tty-record/armhf (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-record/armhf golang-1.23
• tty-record/i386 (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1)
  • Migration status for tty-record/i386 (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-record/i386 golang-1.23
• tty-record/mips64el (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1)
  • Migration status for tty-record/mips64el (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-record/mips64el golang-1.23
• tty-record/ppc64el (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1)
  • Migration status for tty-record/ppc64el (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-record/ppc64el golang-1.23
• tty-record/riscv64 (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1)
  • Migration status for tty-record/riscv64 (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-record/riscv64 golang-1.23
• tty-record/s390x (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1)
  • Migration status for tty-record/s390x (0.1.0+git20240821.2a020f5+ds-1 to 0.1.0+git20240821.2a020f5+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-record/s390x golang-1.23
• tty-share/amd64 (2.4.0+ds-2 to 2.4.0+ds-2)
  • Migration status for tty-share/amd64 (2.4.0+ds-2 to 2.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-share/amd64 golang-1.23
• tty-share/arm64 (2.4.0+ds-2 to 2.4.0+ds-2)
  • Migration status for tty-share/arm64 (2.4.0+ds-2 to 2.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-share/arm64 golang-1.23
• tty-share/armel (2.4.0+ds-2 to 2.4.0+ds-2)
  • Migration status for tty-share/armel (2.4.0+ds-2 to 2.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-share/armel golang-1.23
• tty-share/armhf (2.4.0+ds-2 to 2.4.0+ds-2)
  • Migration status for tty-share/armhf (2.4.0+ds-2 to 2.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-share/armhf golang-1.23
• tty-share/i386 (2.4.0+ds-2 to 2.4.0+ds-2)
  • Migration status for tty-share/i386 (2.4.0+ds-2 to 2.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-share/i386 golang-1.23
• tty-share/mips64el (2.4.0+ds-2 to 2.4.0+ds-2)
  • Migration status for tty-share/mips64el (2.4.0+ds-2 to 2.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-share/mips64el golang-1.23
• tty-share/ppc64el (2.4.0+ds-2 to 2.4.0+ds-2)
  • Migration status for tty-share/ppc64el (2.4.0+ds-2 to 2.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-share/ppc64el golang-1.23
• tty-share/riscv64 (2.4.0+ds-2 to 2.4.0+ds-2)
  • Migration status for tty-share/riscv64 (2.4.0+ds-2 to 2.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-share/riscv64 golang-1.23
• tty-share/s390x (2.4.0+ds-2 to 2.4.0+ds-2)
  • Migration status for tty-share/s390x (2.4.0+ds-2 to 2.4.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: tty-share/s390x golang-1.23
• umoci/amd64 (0.4.7+ds-4 to 0.4.7+ds-4)
  • Migration status for umoci/amd64 (0.4.7+ds-4 to 0.4.7+ds-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: umoci/amd64 runc (not considered)
    • Invalidated by built-using
    • Built-Using: umoci/amd64 golang-1.23
• umoci/arm64 (0.4.7+ds-4 to 0.4.7+ds-4)
  • Migration status for umoci/arm64 (0.4.7+ds-4 to 0.4.7+ds-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: umoci/arm64 runc (not considered)
    • Invalidated by built-using
    • Built-Using: umoci/arm64 golang-1.23
• umoci/armel (0.4.7+ds-4 to 0.4.7+ds-4)
  • Migration status for umoci/armel (0.4.7+ds-4 to 0.4.7+ds-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: umoci/armel runc (not considered)
    • Invalidated by built-using
    • Built-Using: umoci/armel golang-1.23
• umoci/armhf (0.4.7+ds-4 to 0.4.7+ds-4)
  • Migration status for umoci/armhf (0.4.7+ds-4 to 0.4.7+ds-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: umoci/armhf runc (not considered)
    • Invalidated by built-using
    • Built-Using: umoci/armhf golang-1.23
• umoci/i386 (0.4.7+ds-4 to 0.4.7+ds-4)
  • Migration status for umoci/i386 (0.4.7+ds-4 to 0.4.7+ds-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: umoci/i386 runc (not considered)
    • Invalidated by built-using
    • Built-Using: umoci/i386 golang-1.23
• umoci/mips64el (0.4.7+ds-4 to 0.4.7+ds-4)
  • Migration status for umoci/mips64el (0.4.7+ds-4 to 0.4.7+ds-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: umoci/mips64el runc (not considered)
    • Invalidated by built-using
    • Built-Using: umoci/mips64el golang-1.23
• umoci/ppc64el (0.4.7+ds-4 to 0.4.7+ds-4)
  • Migration status for umoci/ppc64el (0.4.7+ds-4 to 0.4.7+ds-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: umoci/ppc64el runc (not considered)
    • Invalidated by built-using
    • Built-Using: umoci/ppc64el golang-1.23
• umoci/riscv64 (0.4.7+ds-4 to 0.4.7+ds-4)
  • Migration status for umoci/riscv64 (0.4.7+ds-4 to 0.4.7+ds-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: umoci/riscv64 runc (not considered)
    • Invalidated by built-using
    • Built-Using: umoci/riscv64 golang-1.23
• umoci/s390x (0.4.7+ds-4 to 0.4.7+ds-4)
  • Migration status for umoci/s390x (0.4.7+ds-4 to 0.4.7+ds-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: umoci/s390x runc (not considered)
    • Invalidated by built-using
    • Built-Using: umoci/s390x golang-1.23
• unicorn-engine/amd64 (2.1.1-2 to 2.1.1-2)
  • Migration status for unicorn-engine/amd64 (2.1.1-2 to 2.1.1-2): Will attempt migration (Any information below is purely informational)
• unicorn-engine/arm64 (2.1.1-2 to 2.1.1-2)
  • Migration status for unicorn-engine/arm64 (2.1.1-2 to 2.1.1-2): Will attempt migration (Any information below is purely informational)
• unicorn-engine/armel (2.1.1-2 to 2.1.1-2)
  • Migration status for unicorn-engine/armel (2.1.1-2 to 2.1.1-2): Will attempt migration (Any information below is purely informational)
• unicorn-engine/armhf (2.1.1-2 to 2.1.1-2)
  • Migration status for unicorn-engine/armhf (2.1.1-2 to 2.1.1-2): Will attempt migration (Any information below is purely informational)
• unicorn-engine/i386 (2.1.1-2 to 2.1.1-2)
  • Migration status for unicorn-engine/i386 (2.1.1-2 to 2.1.1-2): Will attempt migration (Any information below is purely informational)
• unicorn-engine/mips64el (2.1.1-2 to 2.1.1-2)
  • Migration status for unicorn-engine/mips64el (2.1.1-2 to 2.1.1-2): Will attempt migration (Any information below is purely informational)
• unicorn-engine/ppc64el (2.1.1-2 to 2.1.1-2)
  • Migration status for unicorn-engine/ppc64el (2.1.1-2 to 2.1.1-2): Will attempt migration (Any information below is purely informational)
• unicorn-engine/riscv64 (2.1.1-2 to 2.1.1-2)
  • Migration status for unicorn-engine/riscv64 (2.1.1-2 to 2.1.1-2): Will attempt migration (Any information below is purely informational)
• unicorn/amd64 (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1)
  • Migration status for unicorn/amd64 (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1): Will attempt migration (Any information below is purely informational)
• unicorn/arm64 (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1)
  • Migration status for unicorn/arm64 (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1): Will attempt migration (Any information below is purely informational)
• unicorn/armel (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1)
  • Migration status for unicorn/armel (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1): Will attempt migration (Any information below is purely informational)
• unicorn/i386 (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1)
  • Migration status for unicorn/i386 (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1): Will attempt migration (Any information below is purely informational)
• unicorn/mips64el (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1)
  • Migration status for unicorn/mips64el (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1): Will attempt migration (Any information below is purely informational)
• unicorn/ppc64el (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1)
  • Migration status for unicorn/ppc64el (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1): Will attempt migration (Any information below is purely informational)
• unicorn/riscv64 (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1)
  • Migration status for unicorn/riscv64 (6.1.0+git.20250131.1370f52-1 to 6.1.0+git.20250131.1370f52-1): Will attempt migration (Any information below is purely informational)
• unikmer/amd64 (0.20.0-1 to 0.20.0-1)
  • Migration status for unikmer/amd64 (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: unikmer/amd64 golang-1.23
• unikmer/arm64 (0.20.0-1 to 0.20.0-1)
  • Migration status for unikmer/arm64 (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: unikmer/arm64 golang-1.23
• unikmer/armel (0.20.0-1 to 0.20.0-1)
  • Migration status for unikmer/armel (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: unikmer/armel golang-1.23
• unikmer/armhf (0.20.0-1 to 0.20.0-1)
  • Migration status for unikmer/armhf (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: unikmer/armhf golang-1.23
• unikmer/i386 (0.20.0-1 to 0.20.0-1)
  • Migration status for unikmer/i386 (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: unikmer/i386 golang-1.23
• unikmer/mips64el (0.20.0-1 to 0.20.0-1)
  • Migration status for unikmer/mips64el (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: unikmer/mips64el golang-1.23
    • Built-Using: unikmer/mips64el golang-github-mattn-go-runewidth
• unikmer/ppc64el (0.20.0-1 to 0.20.0-1)
  • Migration status for unikmer/ppc64el (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: unikmer/ppc64el golang-1.23
• unikmer/riscv64 (0.20.0-1 to 0.20.0-1)
  • Migration status for unikmer/riscv64 (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: unikmer/riscv64 golang-1.23
    • Built-Using: unikmer/riscv64 golang-github-mattn-go-runewidth
• unikmer/s390x (0.20.0-1 to 0.20.0-1)
  • Migration status for unikmer/s390x (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: unikmer/s390x golang-1.23
• user-mode-linux/amd64 (6.12um1 to 6.12um1)
  • Migration status for user-mode-linux/amd64 (6.12um1 to 6.12um1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: user-mode-linux/amd64 linux (not considered)
    • Invalidated by built-using
• user-mode-linux/i386 (6.12um1 to 6.12um1)
  • Migration status for user-mode-linux/i386 (6.12um1 to 6.12um1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: user-mode-linux/i386 linux (not considered)
    • Invalidated by built-using
• uw-imap/amd64 (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1)
  • Migration status for uw-imap/amd64 (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• uw-imap/arm64 (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1)
  • Migration status for uw-imap/arm64 (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• uw-imap/armel (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1)
  • Migration status for uw-imap/armel (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• uw-imap/armhf (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1)
  • Migration status for uw-imap/armhf (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• uw-imap/i386 (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1)
  • Migration status for uw-imap/i386 (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• uw-imap/mips64el (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1)
  • Migration status for uw-imap/mips64el (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• uw-imap/ppc64el (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1)
  • Migration status for uw-imap/ppc64el (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• uw-imap/riscv64 (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1)
  • Migration status for uw-imap/riscv64 (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• uw-imap/s390x (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1)
  • Migration status for uw-imap/s390x (8:2007f~dfsg-7.1 to 8:2007f~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vagrant/amd64 (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3)
  • Migration status for vagrant/amd64 (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3): Will attempt migration (Any information below is purely informational)
• vagrant/arm64 (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3)
  • Migration status for vagrant/arm64 (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3): Will attempt migration (Any information below is purely informational)
• vagrant/armel (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3)
  • Migration status for vagrant/armel (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3): Will attempt migration (Any information below is purely informational)
• vagrant/i386 (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3)
  • Migration status for vagrant/i386 (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3): Will attempt migration (Any information below is purely informational)
• vagrant/mips64el (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3)
  • Migration status for vagrant/mips64el (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3): Will attempt migration (Any information below is purely informational)
• vagrant/ppc64el (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3)
  • Migration status for vagrant/ppc64el (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.7+git20230731.5fc64cde+dfsg-3): Will attempt migration (Any information below is purely informational)
• vagrant_pu (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.4+dfsg-1+deb12u1)
  • Migration status for vagrant_pu (2.3.7+git20230731.5fc64cde+dfsg-3 to 2.3.4+dfsg-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: vagrant is newer in the target suite (2.3.7+git20230731.5fc64cde+dfsg-3 2.3.4+dfsg-1+deb12u1)
• vcfanno/amd64 (0.3.5+ds-2 to 0.3.5+ds-2)
  • Migration status for vcfanno/amd64 (0.3.5+ds-2 to 0.3.5+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vcfanno/amd64 golang-1.23
• vcfanno/arm64 (0.3.5+ds-2 to 0.3.5+ds-2)
  • Migration status for vcfanno/arm64 (0.3.5+ds-2 to 0.3.5+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vcfanno/arm64 golang-1.23
• vcfanno/armel (0.3.5+ds-2 to 0.3.5+ds-2)
  • Migration status for vcfanno/armel (0.3.5+ds-2 to 0.3.5+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vcfanno/armel golang-1.23
• vcfanno/armhf (0.3.5+ds-2 to 0.3.5+ds-2)
  • Migration status for vcfanno/armhf (0.3.5+ds-2 to 0.3.5+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vcfanno/armhf golang-1.23
• vcfanno/i386 (0.3.5+ds-2 to 0.3.5+ds-2)
  • Migration status for vcfanno/i386 (0.3.5+ds-2 to 0.3.5+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vcfanno/i386 golang-1.23
• vcfanno/mips64el (0.3.5+ds-2 to 0.3.5+ds-2)
  • Migration status for vcfanno/mips64el (0.3.5+ds-2 to 0.3.5+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vcfanno/mips64el golang-1.23
• vcfanno/ppc64el (0.3.5+ds-2 to 0.3.5+ds-2)
  • Migration status for vcfanno/ppc64el (0.3.5+ds-2 to 0.3.5+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vcfanno/ppc64el golang-1.23
• vcfanno/riscv64 (0.3.5+ds-2 to 0.3.5+ds-2)
  • Migration status for vcfanno/riscv64 (0.3.5+ds-2 to 0.3.5+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vcfanno/riscv64 golang-1.23
• vcfanno/s390x (0.3.5+ds-2 to 0.3.5+ds-2)
  • Migration status for vcfanno/s390x (0.3.5+ds-2 to 0.3.5+ds-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vcfanno/s390x golang-1.23
• victoriametrics/amd64 (1.79.14+ds1-2 to 1.79.14+ds1-2)
  • Migration status for victoriametrics/amd64 (1.79.14+ds1-2 to 1.79.14+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: victoriametrics/amd64 golang-1.23
• victoriametrics/arm64 (1.79.14+ds1-2 to 1.79.14+ds1-2)
  • Migration status for victoriametrics/arm64 (1.79.14+ds1-2 to 1.79.14+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: victoriametrics/arm64 golang-1.23
• victoriametrics/armel (1.79.14+ds1-2 to 1.79.14+ds1-2)
  • Migration status for victoriametrics/armel (1.79.14+ds1-2 to 1.79.14+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: victoriametrics/armel golang-1.23
• victoriametrics/armhf (1.79.14+ds1-2 to 1.79.14+ds1-2)
  • Migration status for victoriametrics/armhf (1.79.14+ds1-2 to 1.79.14+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: victoriametrics/armhf golang-1.23
• victoriametrics/i386 (1.79.14+ds1-2 to 1.79.14+ds1-2)
  • Migration status for victoriametrics/i386 (1.79.14+ds1-2 to 1.79.14+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: victoriametrics/i386 golang-1.23
• victoriametrics/mips64el (1.79.14+ds1-2 to 1.79.14+ds1-2)
  • Migration status for victoriametrics/mips64el (1.79.14+ds1-2 to 1.79.14+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: victoriametrics/mips64el golang-1.23
    • Built-Using: victoriametrics/mips64el golang-github-mattn-go-runewidth
• victoriametrics/ppc64el (1.79.14+ds1-2 to 1.79.14+ds1-2)
  • Migration status for victoriametrics/ppc64el (1.79.14+ds1-2 to 1.79.14+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: victoriametrics/ppc64el golang-1.23
• victoriametrics/riscv64 (1.79.14+ds1-2 to 1.79.14+ds1-2)
  • Migration status for victoriametrics/riscv64 (1.79.14+ds1-2 to 1.79.14+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: victoriametrics/riscv64 golang-1.23
    • Built-Using: victoriametrics/riscv64 golang-github-mattn-go-runewidth
• victoriametrics/s390x (1.79.14+ds1-2 to 1.79.14+ds1-2)
  • Migration status for victoriametrics/s390x (1.79.14+ds1-2 to 1.79.14+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: victoriametrics/s390x golang-1.23
• viewpdf.app/amd64 (1:0.2dfsg1-8 to 1:0.2dfsg1-8)
  • Migration status for viewpdf.app/amd64 (1:0.2dfsg1-8 to 1:0.2dfsg1-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: viewpdf.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• viewpdf.app/arm64 (1:0.2dfsg1-8 to 1:0.2dfsg1-8)
  • Migration status for viewpdf.app/arm64 (1:0.2dfsg1-8 to 1:0.2dfsg1-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: viewpdf.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• viewpdf.app/armel (1:0.2dfsg1-8 to 1:0.2dfsg1-8)
  • Migration status for viewpdf.app/armel (1:0.2dfsg1-8 to 1:0.2dfsg1-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: viewpdf.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• viewpdf.app/armhf (1:0.2dfsg1-8 to 1:0.2dfsg1-8)
  • Migration status for viewpdf.app/armhf (1:0.2dfsg1-8 to 1:0.2dfsg1-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: viewpdf.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• viewpdf.app/i386 (1:0.2dfsg1-8 to 1:0.2dfsg1-8)
  • Migration status for viewpdf.app/i386 (1:0.2dfsg1-8 to 1:0.2dfsg1-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: viewpdf.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• viewpdf.app/mips64el (1:0.2dfsg1-8 to 1:0.2dfsg1-8)
  • Migration status for viewpdf.app/mips64el (1:0.2dfsg1-8 to 1:0.2dfsg1-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: viewpdf.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• viewpdf.app/ppc64el (1:0.2dfsg1-8 to 1:0.2dfsg1-8)
  • Migration status for viewpdf.app/ppc64el (1:0.2dfsg1-8 to 1:0.2dfsg1-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: viewpdf.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• viewpdf.app/riscv64 (1:0.2dfsg1-8 to 1:0.2dfsg1-8)
  • Migration status for viewpdf.app/riscv64 (1:0.2dfsg1-8 to 1:0.2dfsg1-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: viewpdf.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• viewpdf.app/s390x (1:0.2dfsg1-8 to 1:0.2dfsg1-8)
  • Migration status for viewpdf.app/s390x (1:0.2dfsg1-8 to 1:0.2dfsg1-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: viewpdf.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• vim_pu (2:9.1.0967-2 to 2:9.0.1378-2+deb12u1)
  • Migration status for vim_pu (2:9.1.0967-2 to 2:9.0.1378-2+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: vim is newer in the target suite (2:9.1.0967-2 2:9.0.1378-2+deb12u1)
• vip-manager/amd64 (1.0.2-9 to 1.0.2-9)
  • Migration status for vip-manager/amd64 (1.0.2-9 to 1.0.2-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager/amd64 golang-1.23
• vip-manager/arm64 (1.0.2-9 to 1.0.2-9)
  • Migration status for vip-manager/arm64 (1.0.2-9 to 1.0.2-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager/arm64 golang-1.23
• vip-manager/armel (1.0.2-9 to 1.0.2-9)
  • Migration status for vip-manager/armel (1.0.2-9 to 1.0.2-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager/armel golang-1.23
• vip-manager/armhf (1.0.2-9 to 1.0.2-9)
  • Migration status for vip-manager/armhf (1.0.2-9 to 1.0.2-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager/armhf golang-1.23
• vip-manager/i386 (1.0.2-9 to 1.0.2-9)
  • Migration status for vip-manager/i386 (1.0.2-9 to 1.0.2-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager/i386 golang-1.23
• vip-manager/mips64el (1.0.2-9 to 1.0.2-9)
  • Migration status for vip-manager/mips64el (1.0.2-9 to 1.0.2-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager/mips64el golang-1.23
• vip-manager/ppc64el (1.0.2-9 to 1.0.2-9)
  • Migration status for vip-manager/ppc64el (1.0.2-9 to 1.0.2-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager/ppc64el golang-1.23
• vip-manager/riscv64 (1.0.2-9 to 1.0.2-9)
  • Migration status for vip-manager/riscv64 (1.0.2-9 to 1.0.2-9): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: vip-manager/riscv64 golang-golang-x-text (not considered)
    • Invalidated by built-using
    • Built-Using: vip-manager/riscv64 golang-1.23
• vip-manager/s390x (1.0.2-9 to 1.0.2-9)
  • Migration status for vip-manager/s390x (1.0.2-9 to 1.0.2-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager/s390x golang-1.23
• vip-manager2/amd64 (3.0.0-2 to 3.0.0-2)
  • Migration status for vip-manager2/amd64 (3.0.0-2 to 3.0.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager2/amd64 golang-1.23
• vip-manager2/arm64 (3.0.0-2 to 3.0.0-2)
  • Migration status for vip-manager2/arm64 (3.0.0-2 to 3.0.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager2/arm64 golang-1.23
• vip-manager2/armel (3.0.0-2 to 3.0.0-2)
  • Migration status for vip-manager2/armel (3.0.0-2 to 3.0.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager2/armel golang-1.23
• vip-manager2/armhf (3.0.0-2 to 3.0.0-2)
  • Migration status for vip-manager2/armhf (3.0.0-2 to 3.0.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager2/armhf golang-1.23
• vip-manager2/i386 (3.0.0-2 to 3.0.0-2)
  • Migration status for vip-manager2/i386 (3.0.0-2 to 3.0.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager2/i386 golang-1.23
• vip-manager2/mips64el (3.0.0-2 to 3.0.0-2)
  • Migration status for vip-manager2/mips64el (3.0.0-2 to 3.0.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager2/mips64el golang-1.23
• vip-manager2/ppc64el (3.0.0-2 to 3.0.0-2)
  • Migration status for vip-manager2/ppc64el (3.0.0-2 to 3.0.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager2/ppc64el golang-1.23
• vip-manager2/riscv64 (3.0.0-2 to 3.0.0-2)
  • Migration status for vip-manager2/riscv64 (3.0.0-2 to 3.0.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager2/riscv64 golang-1.23
• vip-manager2/s390x (3.0.0-2 to 3.0.0-2)
  • Migration status for vip-manager2/s390x (3.0.0-2 to 3.0.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: vip-manager2/s390x golang-1.23
• volumecontrol.app/amd64 (0.8-2 to 0.8-2)
  • Migration status for volumecontrol.app/amd64 (0.8-2 to 0.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: volumecontrol.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• volumecontrol.app/arm64 (0.8-2 to 0.8-2)
  • Migration status for volumecontrol.app/arm64 (0.8-2 to 0.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: volumecontrol.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• volumecontrol.app/armel (0.8-2 to 0.8-2)
  • Migration status for volumecontrol.app/armel (0.8-2 to 0.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: volumecontrol.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• volumecontrol.app/armhf (0.8-2 to 0.8-2)
  • Migration status for volumecontrol.app/armhf (0.8-2 to 0.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: volumecontrol.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• volumecontrol.app/i386 (0.8-2 to 0.8-2)
  • Migration status for volumecontrol.app/i386 (0.8-2 to 0.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: volumecontrol.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• volumecontrol.app/mips64el (0.8-2 to 0.8-2)
  • Migration status for volumecontrol.app/mips64el (0.8-2 to 0.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: volumecontrol.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• volumecontrol.app/ppc64el (0.8-2 to 0.8-2)
  • Migration status for volumecontrol.app/ppc64el (0.8-2 to 0.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: volumecontrol.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• volumecontrol.app/riscv64 (0.8-2 to 0.8-2)
  • Migration status for volumecontrol.app/riscv64 (0.8-2 to 0.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: volumecontrol.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• volumecontrol.app/s390x (0.8-2 to 0.8-2)
  • Migration status for volumecontrol.app/s390x (0.8-2 to 0.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: volumecontrol.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• webhook/amd64 (2.8.0-4 to 2.8.0-4)
  • Migration status for webhook/amd64 (2.8.0-4 to 2.8.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: webhook/amd64 golang-1.23
• webhook/arm64 (2.8.0-4 to 2.8.0-4)
  • Migration status for webhook/arm64 (2.8.0-4 to 2.8.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: webhook/arm64 golang-1.23
• webhook/armel (2.8.0-4 to 2.8.0-4)
  • Migration status for webhook/armel (2.8.0-4 to 2.8.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: webhook/armel golang-1.23
• webhook/armhf (2.8.0-4 to 2.8.0-4)
  • Migration status for webhook/armhf (2.8.0-4 to 2.8.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: webhook/armhf golang-1.23
• webhook/i386 (2.8.0-4 to 2.8.0-4)
  • Migration status for webhook/i386 (2.8.0-4 to 2.8.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: webhook/i386 golang-1.23
• webhook/mips64el (2.8.0-4 to 2.8.0-4)
  • Migration status for webhook/mips64el (2.8.0-4 to 2.8.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: webhook/mips64el golang-1.23
• webhook/ppc64el (2.8.0-4 to 2.8.0-4)
  • Migration status for webhook/ppc64el (2.8.0-4 to 2.8.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: webhook/ppc64el golang-1.23
• webhook/riscv64 (2.8.0-4 to 2.8.0-4)
  • Migration status for webhook/riscv64 (2.8.0-4 to 2.8.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: webhook/riscv64 golang-1.23
• webhook/s390x (2.8.0-4 to 2.8.0-4)
  • Migration status for webhook/s390x (2.8.0-4 to 2.8.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: webhook/s390x golang-1.23
• websocketd/amd64 (0.4.1-1 to 0.4.1-1)
  • Migration status for websocketd/amd64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: websocketd/amd64 golang-1.23
• websocketd/arm64 (0.4.1-1 to 0.4.1-1)
  • Migration status for websocketd/arm64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: websocketd/arm64 golang-1.23
• websocketd/armel (0.4.1-1 to 0.4.1-1)
  • Migration status for websocketd/armel (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: websocketd/armel golang-1.23
• websocketd/armhf (0.4.1-1 to 0.4.1-1)
  • Migration status for websocketd/armhf (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: websocketd/armhf golang-1.23
• websocketd/i386 (0.4.1-1 to 0.4.1-1)
  • Migration status for websocketd/i386 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: websocketd/i386 golang-1.23
• websocketd/mips64el (0.4.1-1 to 0.4.1-1)
  • Migration status for websocketd/mips64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: websocketd/mips64el golang-1.23
• websocketd/ppc64el (0.4.1-1 to 0.4.1-1)
  • Migration status for websocketd/ppc64el (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: websocketd/ppc64el golang-1.23
• websocketd/riscv64 (0.4.1-1 to 0.4.1-1)
  • Migration status for websocketd/riscv64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: websocketd/riscv64 golang-1.23
• websocketd/s390x (0.4.1-1 to 0.4.1-1)
  • Migration status for websocketd/s390x (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: websocketd/s390x golang-1.23
• wego/amd64 (2.3-2 to 2.3-2)
  • Migration status for wego/amd64 (2.3-2 to 2.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wego/amd64 golang-1.23
• wego/arm64 (2.3-2 to 2.3-2)
  • Migration status for wego/arm64 (2.3-2 to 2.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wego/arm64 golang-1.23
• wego/armel (2.3-2 to 2.3-2)
  • Migration status for wego/armel (2.3-2 to 2.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wego/armel golang-1.23
• wego/armhf (2.3-2 to 2.3-2)
  • Migration status for wego/armhf (2.3-2 to 2.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wego/armhf golang-1.23
• wego/i386 (2.3-2 to 2.3-2)
  • Migration status for wego/i386 (2.3-2 to 2.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wego/i386 golang-1.23
• wego/mips64el (2.3-2 to 2.3-2)
  • Migration status for wego/mips64el (2.3-2 to 2.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wego/mips64el golang-1.23
    • Built-Using: wego/mips64el golang-github-mattn-go-runewidth
• wego/ppc64el (2.3-2 to 2.3-2)
  • Migration status for wego/ppc64el (2.3-2 to 2.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wego/ppc64el golang-1.23
• wego/riscv64 (2.3-2 to 2.3-2)
  • Migration status for wego/riscv64 (2.3-2 to 2.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wego/riscv64 golang-1.23
    • Built-Using: wego/riscv64 golang-github-mattn-go-runewidth
• wego/s390x (2.3-2 to 2.3-2)
  • Migration status for wego/s390x (2.3-2 to 2.3-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wego/s390x golang-1.23
• winrmcp/amd64 (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2)
  • Migration status for winrmcp/amd64 (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: winrmcp/amd64 golang-1.23
• winrmcp/arm64 (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2)
  • Migration status for winrmcp/arm64 (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: winrmcp/arm64 golang-1.23
• winrmcp/armel (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2)
  • Migration status for winrmcp/armel (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: winrmcp/armel golang-1.23
• winrmcp/armhf (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2)
  • Migration status for winrmcp/armhf (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: winrmcp/armhf golang-1.23
• winrmcp/i386 (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2)
  • Migration status for winrmcp/i386 (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: winrmcp/i386 golang-1.23
• winrmcp/mips64el (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2)
  • Migration status for winrmcp/mips64el (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: winrmcp/mips64el golang-1.23
• winrmcp/ppc64el (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2)
  • Migration status for winrmcp/ppc64el (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: winrmcp/ppc64el golang-1.23
• winrmcp/riscv64 (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2)
  • Migration status for winrmcp/riscv64 (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: winrmcp/riscv64 golang-1.23
• winrmcp/s390x (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2)
  • Migration status for winrmcp/s390x (0.0~git20180921.c76d91c-2 to 0.0~git20180921.c76d91c-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: winrmcp/s390x golang-1.23
• wireguard-go/amd64 (0.0.20231211-1 to 0.0.20231211-1)
  • Migration status for wireguard-go/amd64 (0.0.20231211-1 to 0.0.20231211-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wireguard-go/amd64 golang-1.23
• wireguard-go/arm64 (0.0.20231211-1 to 0.0.20231211-1)
  • Migration status for wireguard-go/arm64 (0.0.20231211-1 to 0.0.20231211-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wireguard-go/arm64 golang-1.23
• wireguard-go/armel (0.0.20231211-1 to 0.0.20231211-1)
  • Migration status for wireguard-go/armel (0.0.20231211-1 to 0.0.20231211-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wireguard-go/armel golang-1.23
• wireguard-go/armhf (0.0.20231211-1 to 0.0.20231211-1)
  • Migration status for wireguard-go/armhf (0.0.20231211-1 to 0.0.20231211-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wireguard-go/armhf golang-1.23
• wireguard-go/i386 (0.0.20231211-1 to 0.0.20231211-1)
  • Migration status for wireguard-go/i386 (0.0.20231211-1 to 0.0.20231211-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wireguard-go/i386 golang-1.23
• wireguard-go/mips64el (0.0.20231211-1 to 0.0.20231211-1)
  • Migration status for wireguard-go/mips64el (0.0.20231211-1 to 0.0.20231211-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wireguard-go/mips64el golang-1.23
• wireguard-go/ppc64el (0.0.20231211-1 to 0.0.20231211-1)
  • Migration status for wireguard-go/ppc64el (0.0.20231211-1 to 0.0.20231211-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wireguard-go/ppc64el golang-1.23
• wireguard-go/riscv64 (0.0.20231211-1 to 0.0.20231211-1)
  • Migration status for wireguard-go/riscv64 (0.0.20231211-1 to 0.0.20231211-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wireguard-go/riscv64 golang-1.23
• wireguard-go/s390x (0.0.20231211-1 to 0.0.20231211-1)
  • Migration status for wireguard-go/s390x (0.0.20231211-1 to 0.0.20231211-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wireguard-go/s390x golang-1.23
• wormhole-william/amd64 (1.0.7-1 to 1.0.7-1)
  • Migration status for wormhole-william/amd64 (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wormhole-william/amd64 golang-1.23
• wormhole-william/arm64 (1.0.7-1 to 1.0.7-1)
  • Migration status for wormhole-william/arm64 (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wormhole-william/arm64 golang-1.23
• wormhole-william/armel (1.0.7-1 to 1.0.7-1)
  • Migration status for wormhole-william/armel (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wormhole-william/armel golang-1.23
• wormhole-william/armhf (1.0.7-1 to 1.0.7-1)
  • Migration status for wormhole-william/armhf (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wormhole-william/armhf golang-1.23
• wormhole-william/i386 (1.0.7-1 to 1.0.7-1)
  • Migration status for wormhole-william/i386 (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wormhole-william/i386 golang-1.23
• wormhole-william/mips64el (1.0.7-1 to 1.0.7-1)
  • Migration status for wormhole-william/mips64el (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wormhole-william/mips64el golang-1.23
    • Built-Using: wormhole-william/mips64el golang-github-mattn-go-runewidth
• wormhole-william/riscv64 (1.0.7-1 to 1.0.7-1)
  • Migration status for wormhole-william/riscv64 (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wormhole-william/riscv64 golang-1.23
    • Built-Using: wormhole-william/riscv64 golang-github-mattn-go-runewidth
• wormhole-william/s390x (1.0.7-1 to 1.0.7-1)
  • Migration status for wormhole-william/s390x (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: wormhole-william/s390x golang-1.23
• wrapperfactory.app/amd64 (0.1.0-6 to 0.1.0-6)
  • Migration status for wrapperfactory.app/amd64 (0.1.0-6 to 0.1.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wrapperfactory.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• wrapperfactory.app/arm64 (0.1.0-6 to 0.1.0-6)
  • Migration status for wrapperfactory.app/arm64 (0.1.0-6 to 0.1.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wrapperfactory.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• wrapperfactory.app/armel (0.1.0-6 to 0.1.0-6)
  • Migration status for wrapperfactory.app/armel (0.1.0-6 to 0.1.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wrapperfactory.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• wrapperfactory.app/armhf (0.1.0-6 to 0.1.0-6)
  • Migration status for wrapperfactory.app/armhf (0.1.0-6 to 0.1.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wrapperfactory.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• wrapperfactory.app/i386 (0.1.0-6 to 0.1.0-6)
  • Migration status for wrapperfactory.app/i386 (0.1.0-6 to 0.1.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wrapperfactory.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• wrapperfactory.app/mips64el (0.1.0-6 to 0.1.0-6)
  • Migration status for wrapperfactory.app/mips64el (0.1.0-6 to 0.1.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wrapperfactory.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• wrapperfactory.app/ppc64el (0.1.0-6 to 0.1.0-6)
  • Migration status for wrapperfactory.app/ppc64el (0.1.0-6 to 0.1.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wrapperfactory.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• wrapperfactory.app/riscv64 (0.1.0-6 to 0.1.0-6)
  • Migration status for wrapperfactory.app/riscv64 (0.1.0-6 to 0.1.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wrapperfactory.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• wrapperfactory.app/s390x (0.1.0-6 to 0.1.0-6)
  • Migration status for wrapperfactory.app/s390x (0.1.0-6 to 0.1.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wrapperfactory.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• wuzz/amd64 (0.4.0-2 to 0.4.0-2)
  • Migration status for wuzz/amd64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wuzz/amd64 golang-1.23
• wuzz/arm64 (0.4.0-2 to 0.4.0-2)
  • Migration status for wuzz/arm64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wuzz/arm64 golang-1.23
• wuzz/armel (0.4.0-2 to 0.4.0-2)
  • Migration status for wuzz/armel (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wuzz/armel golang-1.23
• wuzz/armhf (0.4.0-2 to 0.4.0-2)
  • Migration status for wuzz/armhf (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wuzz/armhf golang-1.23
• wuzz/i386 (0.4.0-2 to 0.4.0-2)
  • Migration status for wuzz/i386 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wuzz/i386 golang-1.23
• wuzz/mips64el (0.4.0-2 to 0.4.0-2)
  • Migration status for wuzz/mips64el (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wuzz/mips64el golang-1.23
    • Built-Using: wuzz/mips64el golang-github-mattn-go-runewidth
• wuzz/ppc64el (0.4.0-2 to 0.4.0-2)
  • Migration status for wuzz/ppc64el (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wuzz/ppc64el golang-1.23
• wuzz/riscv64 (0.4.0-2 to 0.4.0-2)
  • Migration status for wuzz/riscv64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wuzz/riscv64 golang-1.23
    • Built-Using: wuzz/riscv64 golang-github-mattn-go-runewidth
• wuzz/s390x (0.4.0-2 to 0.4.0-2)
  • Migration status for wuzz/s390x (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: wuzz/s390x golang-1.23
• xapian-bindings/amd64 (1.4.25-1 to 1.4.25-1)
  • Migration status for xapian-bindings/amd64 (1.4.25-1 to 1.4.25-1): Will attempt migration (Any information below is purely informational)
• xapian-bindings/arm64 (1.4.25-1 to 1.4.25-1)
  • Migration status for xapian-bindings/arm64 (1.4.25-1 to 1.4.25-1): Will attempt migration (Any information below is purely informational)
• xapian-bindings/armel (1.4.25-1 to 1.4.25-1)
  • Migration status for xapian-bindings/armel (1.4.25-1 to 1.4.25-1): Will attempt migration (Any information below is purely informational)
• xapian-bindings/i386 (1.4.25-1 to 1.4.25-1)
  • Migration status for xapian-bindings/i386 (1.4.25-1 to 1.4.25-1): Will attempt migration (Any information below is purely informational)
• xapian-bindings/mips64el (1.4.25-1 to 1.4.25-1)
  • Migration status for xapian-bindings/mips64el (1.4.25-1 to 1.4.25-1): Will attempt migration (Any information below is purely informational)
• xapian-bindings/ppc64el (1.4.25-1 to 1.4.25-1)
  • Migration status for xapian-bindings/ppc64el (1.4.25-1 to 1.4.25-1): Will attempt migration (Any information below is purely informational)
• xen_pu (4.19.1-1 to 4.17.5+23-ga4e5191dc0-1)
  • Migration status for xen_pu (4.19.1-1 to 4.17.5+23-ga4e5191dc0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: xen is newer in the target suite (4.19.1-1 4.17.5+23-ga4e5191dc0-1)
• xmpp-dns/amd64 (0.4.5-1 to 0.4.5-1)
  • Migration status for xmpp-dns/amd64 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xmpp-dns/amd64 golang-1.23
• xmpp-dns/arm64 (0.4.5-1 to 0.4.5-1)
  • Migration status for xmpp-dns/arm64 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xmpp-dns/arm64 golang-1.23
• xmpp-dns/armel (0.4.5-1 to 0.4.5-1)
  • Migration status for xmpp-dns/armel (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xmpp-dns/armel golang-1.23
• xmpp-dns/armhf (0.4.5-1 to 0.4.5-1)
  • Migration status for xmpp-dns/armhf (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xmpp-dns/armhf golang-1.23
• xmpp-dns/i386 (0.4.5-1 to 0.4.5-1)
  • Migration status for xmpp-dns/i386 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xmpp-dns/i386 golang-1.23
• xmpp-dns/mips64el (0.4.5-1 to 0.4.5-1)
  • Migration status for xmpp-dns/mips64el (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xmpp-dns/mips64el golang-1.23
• xmpp-dns/ppc64el (0.4.5-1 to 0.4.5-1)
  • Migration status for xmpp-dns/ppc64el (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xmpp-dns/ppc64el golang-1.23
• xmpp-dns/riscv64 (0.4.5-1 to 0.4.5-1)
  • Migration status for xmpp-dns/riscv64 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xmpp-dns/riscv64 golang-1.23
• xmpp-dns/s390x (0.4.5-1 to 0.4.5-1)
  • Migration status for xmpp-dns/s390x (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xmpp-dns/s390x golang-1.23
• xq/amd64 (1.3.0-1 to 1.3.0-1)
  • Migration status for xq/amd64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xq/amd64 golang-1.23
• xq/arm64 (1.3.0-1 to 1.3.0-1)
  • Migration status for xq/arm64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xq/arm64 golang-1.23
• xq/armel (1.3.0-1 to 1.3.0-1)
  • Migration status for xq/armel (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xq/armel golang-1.23
• xq/armhf (1.3.0-1 to 1.3.0-1)
  • Migration status for xq/armhf (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xq/armhf golang-1.23
• xq/i386 (1.3.0-1 to 1.3.0-1)
  • Migration status for xq/i386 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xq/i386 golang-1.23
• xq/mips64el (1.3.0-1 to 1.3.0-1)
  • Migration status for xq/mips64el (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xq/mips64el golang-1.23
• xq/ppc64el (1.3.0-1 to 1.3.0-1)
  • Migration status for xq/ppc64el (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xq/ppc64el golang-1.23
• xq/riscv64 (1.3.0-1 to 1.3.0-1)
  • Migration status for xq/riscv64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xq/riscv64 golang-1.23
• xq/s390x (1.3.0-1 to 1.3.0-1)
  • Migration status for xq/s390x (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: xq/s390x golang-1.23
• yggdrasil/amd64 (0.5.12-1 to 0.5.12-1)
  • Migration status for yggdrasil/amd64 (0.5.12-1 to 0.5.12-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yggdrasil/amd64 golang-1.23
• yggdrasil/arm64 (0.5.12-1 to 0.5.12-1)
  • Migration status for yggdrasil/arm64 (0.5.12-1 to 0.5.12-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yggdrasil/arm64 golang-1.23
• yggdrasil/armel (0.5.12-1 to 0.5.12-1)
  • Migration status for yggdrasil/armel (0.5.12-1 to 0.5.12-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yggdrasil/armel golang-1.23
• yggdrasil/armhf (0.5.12-1 to 0.5.12-1)
  • Migration status for yggdrasil/armhf (0.5.12-1 to 0.5.12-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yggdrasil/armhf golang-1.23
• yggdrasil/i386 (0.5.12-1 to 0.5.12-1)
  • Migration status for yggdrasil/i386 (0.5.12-1 to 0.5.12-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yggdrasil/i386 golang-1.23
• yggdrasil/mips64el (0.5.12-1 to 0.5.12-1)
  • Migration status for yggdrasil/mips64el (0.5.12-1 to 0.5.12-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yggdrasil/mips64el golang-1.23
    • Built-Using: yggdrasil/mips64el golang-github-mattn-go-runewidth
• yggdrasil/ppc64el (0.5.12-1 to 0.5.12-1)
  • Migration status for yggdrasil/ppc64el (0.5.12-1 to 0.5.12-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yggdrasil/ppc64el golang-1.23
• yggdrasil/riscv64 (0.5.12-1 to 0.5.12-1)
  • Migration status for yggdrasil/riscv64 (0.5.12-1 to 0.5.12-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yggdrasil/riscv64 golang-1.23
    • Built-Using: yggdrasil/riscv64 golang-github-mattn-go-runewidth
• yggdrasil/s390x (0.5.12-1 to 0.5.12-1)
  • Migration status for yggdrasil/s390x (0.5.12-1 to 0.5.12-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yggdrasil/s390x golang-1.23
• ymuse/amd64 (0.22-1 to 0.22-1)
  • Migration status for ymuse/amd64 (0.22-1 to 0.22-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ymuse/amd64 golang-1.23
• ymuse/arm64 (0.22-1 to 0.22-1)
  • Migration status for ymuse/arm64 (0.22-1 to 0.22-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ymuse/arm64 golang-1.23
• ymuse/armel (0.22-1 to 0.22-1)
  • Migration status for ymuse/armel (0.22-1 to 0.22-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ymuse/armel golang-1.23
• ymuse/armhf (0.22-1 to 0.22-1)
  • Migration status for ymuse/armhf (0.22-1 to 0.22-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ymuse/armhf golang-1.23
• ymuse/i386 (0.22-1 to 0.22-1)
  • Migration status for ymuse/i386 (0.22-1 to 0.22-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ymuse/i386 golang-1.23
• ymuse/ppc64el (0.22-1 to 0.22-1)
  • Migration status for ymuse/ppc64el (0.22-1 to 0.22-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ymuse/ppc64el golang-1.23
• ymuse/riscv64 (0.22-1 to 0.22-1)
  • Migration status for ymuse/riscv64 (0.22-1 to 0.22-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ymuse/riscv64 golang-1.23
• ymuse/s390x (0.22-1 to 0.22-1)
  • Migration status for ymuse/s390x (0.22-1 to 0.22-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ymuse/s390x golang-1.23
• yubikey-agent/amd64 (0.1.4-2 to 0.1.4-2)
  • Migration status for yubikey-agent/amd64 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-agent/amd64 golang-1.23
• yubikey-agent/arm64 (0.1.4-2 to 0.1.4-2)
  • Migration status for yubikey-agent/arm64 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-agent/arm64 golang-1.23
• yubikey-agent/armel (0.1.4-2 to 0.1.4-2)
  • Migration status for yubikey-agent/armel (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-agent/armel golang-1.23
• yubikey-agent/armhf (0.1.4-2 to 0.1.4-2)
  • Migration status for yubikey-agent/armhf (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-agent/armhf golang-1.23
• yubikey-agent/i386 (0.1.4-2 to 0.1.4-2)
  • Migration status for yubikey-agent/i386 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-agent/i386 golang-1.23
• yubikey-agent/mips64el (0.1.4-2 to 0.1.4-2)
  • Migration status for yubikey-agent/mips64el (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-agent/mips64el golang-1.23
• yubikey-agent/ppc64el (0.1.4-2 to 0.1.4-2)
  • Migration status for yubikey-agent/ppc64el (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-agent/ppc64el golang-1.23
• yubikey-agent/riscv64 (0.1.4-2 to 0.1.4-2)
  • Migration status for yubikey-agent/riscv64 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-agent/riscv64 golang-1.23
• yubikey-agent/s390x (0.1.4-2 to 0.1.4-2)
  • Migration status for yubikey-agent/s390x (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-agent/s390x golang-1.23
• yubikey-touch-detector/amd64 (1.12.5-1 to 1.12.5-1)
  • Migration status for yubikey-touch-detector/amd64 (1.12.5-1 to 1.12.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-touch-detector/amd64 golang-1.23
• yubikey-touch-detector/arm64 (1.12.5-1 to 1.12.5-1)
  • Migration status for yubikey-touch-detector/arm64 (1.12.5-1 to 1.12.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-touch-detector/arm64 golang-1.23
• yubikey-touch-detector/armel (1.12.5-1 to 1.12.5-1)
  • Migration status for yubikey-touch-detector/armel (1.12.5-1 to 1.12.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-touch-detector/armel golang-1.23
• yubikey-touch-detector/armhf (1.12.5-1 to 1.12.5-1)
  • Migration status for yubikey-touch-detector/armhf (1.12.5-1 to 1.12.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-touch-detector/armhf golang-1.23
• yubikey-touch-detector/i386 (1.12.5-1 to 1.12.5-1)
  • Migration status for yubikey-touch-detector/i386 (1.12.5-1 to 1.12.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-touch-detector/i386 golang-1.23
• yubikey-touch-detector/mips64el (1.12.5-1 to 1.12.5-1)
  • Migration status for yubikey-touch-detector/mips64el (1.12.5-1 to 1.12.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-touch-detector/mips64el golang-1.23
• yubikey-touch-detector/ppc64el (1.12.5-1 to 1.12.5-1)
  • Migration status for yubikey-touch-detector/ppc64el (1.12.5-1 to 1.12.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-touch-detector/ppc64el golang-1.23
• yubikey-touch-detector/riscv64 (1.12.5-1 to 1.12.5-1)
  • Migration status for yubikey-touch-detector/riscv64 (1.12.5-1 to 1.12.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-touch-detector/riscv64 golang-1.23
• yubikey-touch-detector/s390x (1.12.5-1 to 1.12.5-1)
  • Migration status for yubikey-touch-detector/s390x (1.12.5-1 to 1.12.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: yubikey-touch-detector/s390x golang-1.23
• zim-tools/amd64 (3.5.0-1.2 to 3.5.0-1.2)
  • Migration status for zim-tools/amd64 (3.5.0-1.2 to 3.5.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zim-tools/amd64 gumbo-parser (not considered)
    • Invalidated by dependency
• zim-tools/arm64 (3.5.0-1.2 to 3.5.0-1.2)
  • Migration status for zim-tools/arm64 (3.5.0-1.2 to 3.5.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zim-tools/arm64 gumbo-parser (not considered)
    • Invalidated by dependency
• zim-tools/armel (3.5.0-1.2 to 3.5.0-1.2)
  • Migration status for zim-tools/armel (3.5.0-1.2 to 3.5.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zim-tools/armel gumbo-parser (not considered)
    • Invalidated by dependency
• zim-tools/armhf (3.5.0-1.2 to 3.5.0-1.2)
  • Migration status for zim-tools/armhf (3.5.0-1.2 to 3.5.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zim-tools/armhf gumbo-parser (not considered)
    • Invalidated by dependency
• zim-tools/i386 (3.5.0-1.2 to 3.5.0-1.2)
  • Migration status for zim-tools/i386 (3.5.0-1.2 to 3.5.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zim-tools/i386 gumbo-parser (not considered)
    • Invalidated by dependency
• zim-tools/mips64el (3.5.0-1.2 to 3.5.0-1.2)
  • Migration status for zim-tools/mips64el (3.5.0-1.2 to 3.5.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zim-tools/mips64el gumbo-parser (not considered)
    • Invalidated by dependency
• zim-tools/ppc64el (3.5.0-1.2 to 3.5.0-1.2)
  • Migration status for zim-tools/ppc64el (3.5.0-1.2 to 3.5.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zim-tools/ppc64el gumbo-parser (not considered)
    • Invalidated by dependency
• zim-tools/riscv64 (3.5.0-1.2 to 3.5.0-1.2)
  • Migration status for zim-tools/riscv64 (3.5.0-1.2 to 3.5.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zim-tools/riscv64 gumbo-parser (not considered)
    • Invalidated by dependency
• zim-tools/s390x (3.5.0-1.2 to 3.5.0-1.2)
  • Migration status for zim-tools/s390x (3.5.0-1.2 to 3.5.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zim-tools/s390x gumbo-parser (not considered)
    • Invalidated by dependency
• zipper.app/amd64 (1.5-4 to 1.5-4)
  • Migration status for zipper.app/amd64 (1.5-4 to 1.5-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zipper.app/amd64 gnustep-make (not considered)
    • Invalidated by dependency
• zipper.app/arm64 (1.5-4 to 1.5-4)
  • Migration status for zipper.app/arm64 (1.5-4 to 1.5-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zipper.app/arm64 gnustep-make (not considered)
    • Invalidated by dependency
• zipper.app/armel (1.5-4 to 1.5-4)
  • Migration status for zipper.app/armel (1.5-4 to 1.5-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zipper.app/armel gnustep-make (not considered)
    • Invalidated by dependency
• zipper.app/armhf (1.5-4 to 1.5-4)
  • Migration status for zipper.app/armhf (1.5-4 to 1.5-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zipper.app/armhf gnustep-make (not considered)
    • Invalidated by dependency
• zipper.app/i386 (1.5-4 to 1.5-4)
  • Migration status for zipper.app/i386 (1.5-4 to 1.5-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zipper.app/i386 gnustep-make (not considered)
    • Invalidated by dependency
• zipper.app/mips64el (1.5-4 to 1.5-4)
  • Migration status for zipper.app/mips64el (1.5-4 to 1.5-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zipper.app/mips64el gnustep-make (not considered)
    • Invalidated by dependency
• zipper.app/ppc64el (1.5-4 to 1.5-4)
  • Migration status for zipper.app/ppc64el (1.5-4 to 1.5-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zipper.app/ppc64el gnustep-make (not considered)
    • Invalidated by dependency
• zipper.app/riscv64 (1.5-4 to 1.5-4)
  • Migration status for zipper.app/riscv64 (1.5-4 to 1.5-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zipper.app/riscv64 gnustep-make (not considered)
    • Invalidated by dependency
• zipper.app/s390x (1.5-4 to 1.5-4)
  • Migration status for zipper.app/s390x (1.5-4 to 1.5-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zipper.app/s390x gnustep-make (not considered)
    • Invalidated by dependency
• zsh/amd64 (5.9-8 to 5.9-8)
  • Migration status for zsh/amd64 (5.9-8 to 5.9-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: zsh/amd64 pcre2 (not considered)
    • Invalidated by built-using
• zsh/arm64 (5.9-8 to 5.9-8)
  • Migration status for zsh/arm64 (5.9-8 to 5.9-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: zsh/arm64 pcre2 (not considered)
    • Invalidated by built-using
• zsh/armel (5.9-8 to 5.9-8)
  • Migration status for zsh/armel (5.9-8 to 5.9-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: zsh/armel pcre2 (not considered)
    • Invalidated by built-using
• zsh/armhf (5.9-8 to 5.9-8)
  • Migration status for zsh/armhf (5.9-8 to 5.9-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: zsh/armhf pcre2 (not considered)
    • Invalidated by built-using
• zsh/i386 (5.9-8 to 5.9-8)
  • Migration status for zsh/i386 (5.9-8 to 5.9-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: zsh/i386 pcre2 (not considered)
    • Invalidated by built-using
• zsh/mips64el (5.9-8 to 5.9-8)
  • Migration status for zsh/mips64el (5.9-8 to 5.9-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: zsh/mips64el pcre2 (not considered)
    • Invalidated by built-using
• zsh/ppc64el (5.9-8 to 5.9-8)
  • Migration status for zsh/ppc64el (5.9-8 to 5.9-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: zsh/ppc64el pcre2 (not considered)
    • Invalidated by built-using
• zsh/riscv64 (5.9-8 to 5.9-8)
  • Migration status for zsh/riscv64 (5.9-8 to 5.9-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: zsh/riscv64 pcre2 (not considered)
    • Invalidated by built-using
• zsh/s390x (5.9-8 to 5.9-8)
  • Migration status for zsh/s390x (5.9-8 to 5.9-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: zsh/s390x pcre2 (not considered)
    • Invalidated by built-using
• adwaita-icon-theme (47.0-2 to 48~beta-3)
  • Migration status for adwaita-icon-theme (47.0-2 to 48~beta-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mutter/47.4-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adwaita-icon-theme.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• autopkgtest (5.43 to 5.44)
  • Migration status for autopkgtest (5.43 to 5.44): 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 0 of 5 days old
  • Additional info:
    • Updating autopkgtest will fix bugs in testing: #1093275
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autopkgtest.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• boulder-game (- to 1.02+ds-1)
  • Migration status for boulder-game (- to 1.02+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/boulder-game.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• camel-snake-kebab-clojure (- to 0.4.3-1)
  • Migration status for camel-snake-kebab-clojure (- to 0.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by lavamind, a new source-only upload is needed to allow migration
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camel-snake-kebab-clojure.html
    • autopkgtest for camel-snake-kebab-clojure/0.4.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• ciborium (1.0.1-1 to 1.0.1-2)
  • Migration status for ciborium (1.0.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 0 of 5 days old
    • Built-Using: ciborium golang-1.23
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ciborium.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cpuinfo (0.0~git20250110.8a1772a-1 to 0.0~git20250203.aaac07e-1)
  • Migration status for cpuinfo (0.0~git20250110.8a1772a-1 to 0.0~git20250203.aaac07e-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 cpuinfo/0.0~git20250203.aaac07e-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpuinfo.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cpupower-gui (1.0.0-3 to 1.0.0-4)
  • Migration status for cpupower-gui (1.0.0-3 to 1.0.0-4): 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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpupower-gui.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• django-assets (2.0-5 to 2.0-6)
  • Migration status for django-assets (2.0-5 to 2.0-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-assets.html
    • autopkgtest for django-assets/2.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• django-sass (1.0.0-3 to 1.1.0-1)
  • Migration status for django-sass (1.0.0-3 to 1.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-sass.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dnf-plugins-core (4.9.0-1 to 4.10.0-1)
  • Migration status for dnf-plugins-core (4.9.0-1 to 4.10.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnf-plugins-core.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ecbuild (3.9.0-2 to 3.9.1-1)
  • Migration status for ecbuild (3.9.0-2 to 3.9.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecbuild.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• emacs-jsonrpc (- to 1.0.25-1)
  • Migration status for emacs-jsonrpc (- to 1.0.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by soren@stoutner.com, a new source-only upload is needed to allow migration
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-jsonrpc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• emacs-llama (- to 0.6.0-1)
  • Migration status for emacs-llama (- 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 jas, a new source-only upload is needed to allow migration
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-llama.html
    • autopkgtest for emacs-llama/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• faiss (1.9.0-5 to 1.10.0-1)
  • Migration status for faiss (1.9.0-5 to 1.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for faiss/1.10.0-1: arm64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • missing build on amd64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/faiss.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• felix-framework (4.6.1-2.1 to 4.6.1-3)
  • Migration status for felix-framework (4.6.1-2.1 to 4.6.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/felix-framework.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• felix-gogo-shell (0.12.0-1.1 to 0.12.0-2)
  • Migration status for felix-gogo-shell (0.12.0-1.1 to 0.12.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/felix-gogo-shell.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• felix-main (5.0.0-5 to 5.0.0-7)
  • Migration status for felix-main (5.0.0-5 to 5.0.0-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/felix-main.html
    • Reproducibility regression on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• felix-shell-tui (1.4.1-4 to 1.4.1-5)
  • Migration status for felix-shell-tui (1.4.1-4 to 1.4.1-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/felix-shell-tui.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• felix-utils (1.8.6-1.1 to 1.8.6-2)
  • Migration status for felix-utils (1.8.6-1.1 to 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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/felix-utils.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• frugen (2.0+git20240917.25293b1-1 to 2.1-1)
  • Migration status for frugen (2.0+git20240917.25293b1-1 to 2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frugen.html
    • autopkgtest for frugen/2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• game-data-packager (82 to 84)
  • Migration status for game-data-packager (82 to 84): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for game-data-packager/84: i386: Pass
    • Required age reduced by 3 days because of autopkgtest
• gcc-14 (14.2.0-16 to 14.2.0-17)
  • Migration status for gcc-14 (14.2.0-16 to 14.2.0-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for apt/2.9.27: armel: Regression or new test ♻ (reference ♻)
    • autopkgtest for fastdds/3.1.0+ds-2: armel: Regression or new test ♻ (reference ♻)
    • autopkgtest for fenics-dolfinx: armel: Test in progress
    • autopkgtest for gcc-14/14.2.0-17: armel: Pass
    • autopkgtest for ghc/9.6.6-3: armel: Reference test in progress, but real test failed already ♻
    • autopkgtest for gyoto: armel: Test in progress
    • autopkgtest for posterazor: armel: Test in progress
    • autopkgtest for python3.13: armel: Test in progress
    • autopkgtest for pythran: armel: Test in progress
    • autopkgtest for pyvkfft: armel: Test in progress
    • autopkgtest for r-cran-prophet: armel: Test in progress
    • autopkgtest for r-cran-sf: armel: Test in progress
    • autopkgtest for r-cran-survey: armel: Test in progress
    • autopkgtest for r-cran-tidygraph: armel: Test in progress
    • autopkgtest for r-cran-tidyr: armel: Test in progress
    • autopkgtest for r-cran-timechange: armel: Test in progress
    • autopkgtest for r-cran-tm: armel: Test in progress
    • autopkgtest for r-cran-tokenizers: armel: Test in progress
    • autopkgtest for r-cran-transformr: armel: Test in progress
    • autopkgtest for r-cran-treespace: armel: Test in progress
    • autopkgtest for r-cran-triebeard: armel: Test in progress
    • autopkgtest for r-cran-tweenr: armel: Test in progress
    • autopkgtest for r-cran-units: armel: Test in progress
    • autopkgtest for r-cran-urltools: armel: Test in progress
    • autopkgtest for r-cran-uwot: armel: Test in progress
    • autopkgtest for r-cran-v8: armel: Test in progress
    • autopkgtest for r-cran-vdiffr: armel: Test in progress
    • autopkgtest for r-cran-vegan: armel: Test in progress
    • autopkgtest for r-cran-vim: armel: Test in progress
    • autopkgtest for r-cran-webgestaltr: armel: Test in progress
    • autopkgtest for r-cran-wk: armel: Test in progress
    • autopkgtest for r-cran-wkutils: armel: Test in progress
    • autopkgtest for r-cran-wordcloud: armel: Test in progress
    • autopkgtest for r-cran-xml2: armel: Test in progress
    • autopkgtest for r-cran-xslt: armel: Test in progress
    • autopkgtest for r-other-amsmercury: armel: Test in progress
    • autopkgtest for r-other-x4r: armel: Test in progress
    • autopkgtest for racon: armel: Test in progress
    • autopkgtest for ragout: armel: Test in progress
    • autopkgtest for rampler: armel: Test in progress
    • autopkgtest for rapidfuzz: armel: Test in progress
    • autopkgtest for raster3d: armel: Test in progress
    • autopkgtest for rasterio: armel: Test in progress
    • autopkgtest for rate4site: armel: Test in progress
    • autopkgtest for ray: armel: Test in progress
    • autopkgtest for re2: armel: Test in progress
    • autopkgtest for re2c: armel: Test in progress
    • autopkgtest for reapr: armel: Test in progress
    • autopkgtest for recoverjpeg: armel: Test in progress
    • autopkgtest for redict: armel: Test in progress
    • autopkgtest for redis: armel: Test in progress
    • autopkgtest for reflect-cpp: armel: Test in progress
    • autopkgtest for refnx: armel: Test in progress
    • autopkgtest for reform-firedecor: armel: Test in progress
    • autopkgtest for regexxer: armel: Test in progress
    • autopkgtest for relion: armel: Test in progress
    • autopkgtest for remctl: armel: Test in progress
    • autopkgtest for rig: armel: Test in progress
    • autopkgtest for ripser: armel: Test in progress
    • autopkgtest for riseup-vpn: armel: Test in progress
    • autopkgtest for rnp: armel: Test in progress
    • autopkgtest for roc-toolkit: armel: Test in progress
    • autopkgtest for rocm-smi-lib: armel: Test in progress
    • autopkgtest for ros-actionlib: armel: Test in progress
    • autopkgtest for ros-diagnostics: armel: Test in progress
    • autopkgtest for ros-geometry: armel: Test in progress
    • autopkgtest for ros-geometry2: armel: Test in progress
    • autopkgtest for ros-image-pipeline: armel: Test in progress
    • autopkgtest for ros-kdl-parser: armel: Test in progress
    • autopkgtest for ros-perception-pcl: armel: Test in progress
    • autopkgtest for ros-robot-state-publisher: armel: Test in progress
    • autopkgtest for ros-ros-comm: armel: Test in progress
    • autopkgtest for ros-urdf: armel: Test in progress
    • autopkgtest for ros-vision-opencv: armel: Test in progress
    • autopkgtest for rpds-py: armel: Test in progress
    • autopkgtest for rpm: armel: Test in progress
    • autopkgtest for rsakeyfind: armel: Test in progress
    • autopkgtest for rsass: armel: Test in progress
    • autopkgtest for rspamd: armel: Test in progress
    • autopkgtest for rtags: armel: Test in progress
    • autopkgtest for rtpengine: armel: Test in progress
    • autopkgtest for rubberband: armel: Test in progress
    • autopkgtest for ruby-aliyun-sdk: armel: Test in progress
    • autopkgtest for ruby-atomic: armel: Test in progress
    • autopkgtest for ruby-augeas: armel: Test in progress
    • autopkgtest for ruby-bcrypt: armel: Test in progress
    • autopkgtest for ruby-bcrypt-pbkdf: armel: Test in progress
    • autopkgtest for ruby-bert: armel: Test in progress
    • autopkgtest for ruby-bindex: armel: Test in progress
    • autopkgtest for ruby-binding-ninja: armel: Test in progress
    • autopkgtest for ruby-bootsnap: armel: Test in progress
    • autopkgtest for ruby-bson: armel: Test in progress
    • autopkgtest for ruby-byebug: armel: Test in progress
    • autopkgtest for ruby-cairo: armel: Test in progress
    • autopkgtest for ruby-character-set: armel: Test in progress
    • autopkgtest for ruby-charlock-holmes: armel: Test in progress
    • autopkgtest for ruby-commonmarker: armel: Test in progress
    • autopkgtest for ruby-concurrent: armel: Test in progress
    • autopkgtest for ruby-cool.io: armel: Test in progress
    • autopkgtest for ruby-curb: armel: Test in progress
    • autopkgtest for ruby-curses: armel: Test in progress
    • autopkgtest for ruby-damerau-levenshtein: armel: Test in progress
    • autopkgtest for ruby-dbm: armel: Test in progress
    • autopkgtest for ruby-debian: armel: Test in progress
    • autopkgtest for ruby-debug-inspector: armel: Test in progress
    • autopkgtest for ruby-ed25519: armel: Test in progress
    • autopkgtest for ruby-enumerable-statistics: armel: Test in progress
    • autopkgtest for ruby-escape-utils: armel: Test in progress
    • autopkgtest for ruby-eventmachine: armel: Test in progress
    • autopkgtest for ruby-fast-blank: armel: Test in progress
    • autopkgtest for ruby-fast-stemmer: armel: Test in progress
    • autopkgtest for ruby-fcgi: armel: Test in progress
    • autopkgtest for ruby-ffi: armel: Test in progress
    • autopkgtest for ruby-ffi-yajl: armel: Test in progress
    • autopkgtest for ruby-fftw3: armel: Test in progress
    • autopkgtest for ruby-github-linguist: armel: Test in progress
    • autopkgtest for ruby-github-markdown: armel: Test in progress
    • autopkgtest for ruby-gnome: armel: Test in progress
    • autopkgtest for ruby-gpgme: armel: Test in progress
    • autopkgtest for ruby-haml: armel: Test in progress
    • autopkgtest for ruby-hamlit: armel: Test in progress
    • autopkgtest for ruby-hdfeos5: armel: Test in progress
    • autopkgtest for ruby-hiredis: armel: Test in progress
    • autopkgtest for ruby-hitimes: armel: Test in progress
    • autopkgtest for ruby-http-parser: armel: Test in progress
    • autopkgtest for ruby-http-parser.rb: armel: Test in progress
    • autopkgtest for ruby-jaro-winkler: armel: Test in progress
    • autopkgtest for ruby-json: armel: Test in progress
    • autopkgtest for ruby-kgio: armel: Test in progress
    • autopkgtest for ruby-kyotocabinet: armel: Test in progress
    • autopkgtest for ruby-lapack: armel: Test in progress
    • autopkgtest for ruby-libvirt: armel: Test in progress
    • autopkgtest for ruby-libxml: armel: Test in progress
    • autopkgtest for ruby-liquid-c: armel: Test in progress
    • autopkgtest for ruby-msgpack: armel: Test in progress
    • autopkgtest for ruby-multibitnums: armel: Test in progress
    • autopkgtest for ruby-murmurhash3: armel: Test in progress
    • autopkgtest for ruby-mysql2: armel: Test in progress
    • autopkgtest for ruby-ncurses: armel: Test in progress
    • autopkgtest for ruby-netcdf: armel: Test in progress
    • autopkgtest for ruby-nio4r: armel: Test in progress
    • autopkgtest for ruby-nokogiri: armel: Test in progress
    • autopkgtest for ruby-oily-png: armel: Test in progress
    • autopkgtest for ruby-oj: armel: Test in progress
    • autopkgtest for ruby-oj-introspect: armel: Test in progress
    • autopkgtest for ruby-ox: armel: Test in progress
    • autopkgtest for ruby-password: armel: Test in progress
    • autopkgtest for ruby-pcaprub: armel: Test in progress
    • autopkgtest for ruby-pg: armel: Test in progress
    • autopkgtest for ruby-pg-query: armel: Test in progress
    • autopkgtest for ruby-posix-spawn: armel: Test in progress
    • autopkgtest for ruby-prof: armel: Test in progress
    • autopkgtest for ruby-psych: armel: Test in progress
    • autopkgtest for ruby-raindrops: armel: Test in progress
    • autopkgtest for ruby-rblineprof: armel: Test in progress
    • autopkgtest for ruby-rbtrace: armel: Test in progress
    • autopkgtest for ruby-rbtree: armel: Test in progress
    • autopkgtest for ruby-re2: armel: Test in progress
    • autopkgtest for ruby-redcarpet: armel: Test in progress
    • autopkgtest for ruby-redcloth: armel: Test in progress
    • autopkgtest for ruby-regexp-property-values: armel: Test in progress
    • autopkgtest for ruby-rmagick: armel: Test in progress
    • autopkgtest for ruby-rugged: armel: Test in progress
    • autopkgtest for ruby-sdbm: armel: Test in progress
    • autopkgtest for ruby-sequel-pg: armel: Test in progress
    • autopkgtest for ruby-shadow: armel: Test in progress
    • autopkgtest for ruby-sqlite3: armel: Test in progress
    • autopkgtest for ruby-stackprof: armel: Test in progress
    • autopkgtest for ruby-strptime: armel: Test in progress
    • autopkgtest for ruby-termios: armel: Test in progress
    • autopkgtest for ruby-thrift: armel: Test in progress
    • autopkgtest for ruby-timfel-krb5-auth: armel: Test in progress
    • autopkgtest for ruby-tokyocabinet: armel: Test in progress
    • autopkgtest for ruby-uconv: armel: Test in progress
    • autopkgtest for ruby-unf-ext: armel: Test in progress
    • autopkgtest for ruby-unicode: armel: Test in progress
    • autopkgtest for ruby-version-sorter: armel: Test in progress
    • autopkgtest for ruby-vmstat: armel: Test in progress
    • autopkgtest for ruby-websocket-driver: armel: Test in progress
    • autopkgtest for ruby-xmlparser: armel: Test in progress
    • autopkgtest for ruby-yajl: armel: Test in progress
    • autopkgtest for ruby-zoom: armel: Test in progress
    • autopkgtest for rumur: armel: Test in progress
    • autopkgtest for rust-apt-swarm: armel: Test in progress
    • autopkgtest for rust-asahi-bless: armel: Test in progress
    • autopkgtest for rust-backdown: armel: Test in progress
    • autopkgtest for rust-bat: armel: Test in progress
    • autopkgtest for rust-bkt: armel: Test in progress
    • autopkgtest for rust-blight: armel: Test in progress
    • autopkgtest for rust-broot: armel: Test in progress
    • autopkgtest for rust-brotli: armel: Test in progress
    • autopkgtest for rust-buildlog-consultant: armel: Test in progress
    • autopkgtest for rust-cargo-binutils: armel: Test in progress
    • autopkgtest for rust-cargo-c: armel: Test in progress
    • autopkgtest for rust-cargo-lock: armel: Test in progress
    • autopkgtest for rust-cbindgen: armel: Test in progress
    • autopkgtest for rust-cddl: armel: Test in progress
    • autopkgtest for rust-cntr: armel: Test in progress
    • autopkgtest for rust-condure: armel: Test in progress
    • autopkgtest for rust-csv2svg: armel: Test in progress
    • autopkgtest for rust-debcargo: armel: Test in progress
    • autopkgtest for rust-diffutils: armel: Test in progress
    • autopkgtest for rust-dolby-vision: armel: Test in progress
    • autopkgtest for rust-eza: armel: Test in progress
    • autopkgtest for rust-filespooler: armel: Test in progress
    • autopkgtest for rust-findutils: armel: Test in progress
    • autopkgtest for rust-git-absorb: armel: Test in progress
    • autopkgtest for rust-grcov: armel: Test in progress
    • autopkgtest for rust-gst-plugin-gtk4: armel: Test in progress
    • autopkgtest for rust-hexyl: armel: Test in progress
    • autopkgtest for rust-hypothesis: armel: Test in progress
    • autopkgtest for rust-just: armel: Test in progress
    • autopkgtest for rust-kmon: armel: Test in progress
    • autopkgtest for rust-lalrpop: armel: Test in progress
    • autopkgtest for rust-laurel: armel: Test in progress
    • autopkgtest for rust-leb128: armel: Test in progress
    • autopkgtest for rust-libbpf-cargo: armel: Test in progress
    • autopkgtest for rust-libslirp: armel: Test in progress
    • autopkgtest for rust-linescroll: armel: Test in progress
    • autopkgtest for rust-lscolors: armel: Test in progress
    • autopkgtest for rust-merge3: armel: Test in progress
    • autopkgtest for rust-names: armel: Test in progress
    • autopkgtest for rust-ognibuild: armel: Test in progress
    • autopkgtest for rust-parsec-service: armel: Test in progress
    • autopkgtest for rust-parsec-tool: armel: Test in progress
    • autopkgtest for rust-pikchr: armel: Test in progress
    • autopkgtest for rust-pleaser: armel: Test in progress
    • autopkgtest for rust-protobuf-codegen: armel: Test in progress
    • autopkgtest for rust-proton-call: armel: Test in progress
    • autopkgtest for rust-pulldown-cmark: armel: Test in progress
    • autopkgtest for rust-rav1e: armel: Test in progress
    • autopkgtest for rust-regalloc2: armel: Test in progress
    • autopkgtest for rust-resource-proof: armel: Test in progress
    • autopkgtest for rust-ripcalc: armel: Test in progress
    • autopkgtest for rust-rockusb: armel: Test in progress
    • autopkgtest for rust-rpm-sequoia: armel: Test in progress
    • autopkgtest for rust-rustdoc-stripper: armel: Test in progress
    • autopkgtest for rust-sequoia-git: armel: Test in progress
    • autopkgtest for rust-sequoia-octopus-librnp: armel: Test in progress
    • autopkgtest for rust-sequoia-sop: armel: Test in progress
    • autopkgtest for rust-sniffglue: armel: Test in progress
    • autopkgtest for rust-spytrap-adb: armel: Test in progress
    • autopkgtest for rust-sudo-rs: armel: Test in progress
    • autopkgtest for rust-swaysome: armel: Test in progress
    • autopkgtest for rust-swtchr: armel: Test in progress
    • autopkgtest for rust-tokei: armel: Test in progress
    • autopkgtest for rust-trawld: armel: Test in progress
    • autopkgtest for rust-trawldb: armel: Test in progress
    • autopkgtest for rust-tree-sitter-cli: armel: Test in progress
    • autopkgtest for rust-xml-rs: armel: Test in progress
    • autopkgtest for rust-zram-generator: armel: Test in progress
    • autopkgtest for rustc: armel: Test in progress
    • autopkgtest for sabctools: armel: Test in progress
    • autopkgtest for safetensors: armel: Test in progress
    • autopkgtest for samba: armel: Test in progress
    • autopkgtest for samblaster: armel: Test in progress
    • autopkgtest for samplv1: armel: Test in progress
    • autopkgtest for saods9: armel: Test in progress
    • autopkgtest for sbuild: armel: Test in progress
    • autopkgtest for scalene: armel: Test in progress
    • autopkgtest for scikit-fmm: armel: Test in progress
    • autopkgtest for scikit-learn: armel: Test in progress
    • autopkgtest for scipy: armel: Test in progress
    • autopkgtest for scrm: armel: Test in progress
    • autopkgtest for scscp-imcce: armel: Test in progress
    • autopkgtest for sdcv: armel: Test in progress
    • autopkgtest for seaview: armel: Test in progress
    • autopkgtest for seer: armel: Test in progress
    • autopkgtest for sentencepiece: armel: Test in progress
    • autopkgtest for seqan2: armel: Test in progress
    • autopkgtest for seqtools: armel: Test in progress
    • autopkgtest for sfarklib: armel: Test in progress
    • autopkgtest for sfarkxtc: armel: Test in progress
    • autopkgtest for sfst: armel: Test in progress
    • autopkgtest for shaderc: armel: Test in progress
    • autopkgtest for shapeit4: armel: Test in progress
    • autopkgtest for shelltestrunner: armel: Test in progress
    • autopkgtest for shibboleth-sp: armel: Test in progress
    • autopkgtest for sibelia: armel: Test in progress
    • autopkgtest for sigscheme: armel: Test in progress
    • autopkgtest for silver-platter: armel: Test in progress
    • autopkgtest for simbody: armel: Test in progress
    • autopkgtest for simdjson: armel: Test in progress
    • autopkgtest for simrisc: armel: Test in progress
    • autopkgtest for sirikali: armel: Test in progress
    • autopkgtest for ska: armel: Test in progress
    • autopkgtest for skewer: armel: Test in progress
    • autopkgtest for skimage: armel: Test in progress
    • autopkgtest for slepc: armel: Test in progress
    • autopkgtest for smartdns: armel: Test in progress
    • autopkgtest for snap7: armel: Test in progress
    • autopkgtest for snapd-glib: armel: Test in progress
    • autopkgtest for snpomatic: armel: Test in progress
    • autopkgtest for soapysdr: armel: Test in progress
    • autopkgtest for soci: armel: Test in progress
    • autopkgtest for solid: armel: Test in progress
    • autopkgtest for solvespace: armel: Test in progress
    • autopkgtest for sonnet: armel: Test in progress
    • autopkgtest for soqt: armel: Test in progress
    • autopkgtest for soundtouch: armel: Test in progress
    • autopkgtest for sox: armel: Test in progress
    • autopkgtest for sp800-90b-entropy-assessment: armel: Test in progress
    • autopkgtest for spaced: armel: Test in progress
    • autopkgtest for spdlog: armel: Test in progress
    • autopkgtest for speech-tools: armel: Test in progress
    • autopkgtest for spherepack: armel: Test in progress
    • autopkgtest for spigot: armel: Test in progress
    • autopkgtest for spirv-llvm-translator-17: armel: Test in progress
    • autopkgtest for spirv-llvm-translator-18: armel: Test in progress
    • autopkgtest for spirv-llvm-translator-19: armel: Test in progress
    • autopkgtest for spoa: armel: Test in progress
    • autopkgtest for sqlsmith: armel: Test in progress
    • autopkgtest for squashfuse: armel: Test in progress
    • autopkgtest for squid: armel: Test in progress
    • autopkgtest for srpc: armel: Test in progress
    • autopkgtest for srt: armel: Test in progress
    • autopkgtest for ssdeep: armel: Test in progress
    • autopkgtest for ssh-agent-filter: armel: Test in progress
    • autopkgtest for sslsniff: armel: Test in progress
    • autopkgtest for stacks: armel: Test in progress
    • autopkgtest for starpu: armel: Test in progress
    • autopkgtest for starship: armel: Test in progress
    • autopkgtest for steghide: armel: Test in progress
    • autopkgtest for stegseek: armel: Test in progress
    • autopkgtest for stenographer: armel: Test in progress
    • autopkgtest for steptalk: armel: Test in progress
    • autopkgtest for stopt: armel: Test in progress
    • autopkgtest for stress-ng: armel: Test in progress
    • autopkgtest for stressapptest: armel: Test in progress
    • autopkgtest for stringtie: armel: Test in progress
    • autopkgtest for subnetcalc: armel: Test in progress
    • autopkgtest for subversion: armel: Test in progress
    • autopkgtest for sudoku-solver: armel: Test in progress
    • autopkgtest for suitesparse: armel: Test in progress
    • autopkgtest for sumo: armel: Test in progress
    • autopkgtest for sundials: armel: Test in progress
    • autopkgtest for superlu-dist: armel: Test in progress
    • autopkgtest for surf-alggeo: armel: Test in progress
    • autopkgtest for suricata: armel: Test in progress
    • autopkgtest for survex: armel: Test in progress
    • autopkgtest for survivor: armel: Test in progress
    • autopkgtest for svn-all-fast-export: armel: Test in progress
    • autopkgtest for swath: armel: Test in progress
    • autopkgtest for swi-prolog: armel: Test in progress
    • autopkgtest for swig: armel: Test in progress
    • autopkgtest for syndication-domination: armel: Test in progress
    • autopkgtest for synthv1: armel: Test in progress
    • autopkgtest for syslog-ng: armel: Test in progress
    • autopkgtest for sysprof: armel: Test in progress
    • autopkgtest for systemd: armel: Test in progress
    • autopkgtest for systemd-cron: armel: Test in progress
    • autopkgtest for t-coffee: armel: Test in progress
    • autopkgtest for tagpy: armel: Test in progress
    • autopkgtest for tango: armel: Test in progress
    • autopkgtest for tantan: armel: Test in progress
    • autopkgtest for taptempo: armel: Test in progress
    • autopkgtest for task: armel: Test in progress
    • autopkgtest for taskflow: armel: Test in progress
    • autopkgtest for teckit: armel: Test in progress
    • autopkgtest for termpaint: armel: Test in progress
    • autopkgtest for terraphast: armel: Test in progress
    • autopkgtest for tetgen: armel: Test in progress
    • autopkgtest for texmacs: armel: Test in progress
    • autopkgtest for texworks: armel: Test in progress
    • autopkgtest for therion: armel: Test in progress
    • autopkgtest for thin: armel: Test in progress
    • autopkgtest for threadweaver: armel: Test in progress
    • autopkgtest for tigr-glimmer: armel: Test in progress
    • autopkgtest for tiktoken: armel: Test in progress
    • autopkgtest for timew: armel: Test in progress
    • autopkgtest for tinyexr: armel: Test in progress
    • autopkgtest for tinygltf: armel: Test in progress
    • autopkgtest for tinyobjloader: armel: Test in progress
    • autopkgtest for tkagif: armel: Test in progress
    • autopkgtest for tkmpeg: armel: Test in progress
    • autopkgtest for tkrzw-python: armel: Test in progress
    • autopkgtest for tlsh: armel: Test in progress
    • autopkgtest for tm-align: armel: Test in progress
    • autopkgtest for tntdb: armel: Test in progress
    • autopkgtest for tombo: armel: Test in progress
    • autopkgtest for tomlplusplus: armel: Test in progress
    • autopkgtest for tomopy: armel: Test in progress
    • autopkgtest for topcom: armel: Test in progress
    • autopkgtest for tor: armel: Test in progress
    • autopkgtest for traceshark: armel: Test in progress
    • autopkgtest for transrate-tools: armel: Test in progress
    • autopkgtest for transtermhp: armel: Test in progress
    • autopkgtest for trend: armel: Test in progress
    • autopkgtest for trinculo: armel: Test in progress
    • autopkgtest for trojan: armel: Test in progress
    • autopkgtest for tvc: armel: Test in progress
    • autopkgtest for uc-echo: armel: Test in progress
    • autopkgtest for uchardet: armel: Test in progress
    • autopkgtest for ugrep: armel: Test in progress
    • autopkgtest for uim: armel: Test in progress
    • autopkgtest for ujson: armel: Test in progress
    • autopkgtest for ums2net: armel: Test in progress
    • autopkgtest for unar: armel: Test in progress
    • autopkgtest for uncalled: armel: Test in progress
    • autopkgtest for unicorn: armel: Test in progress
    • autopkgtest for unifrac-tools: armel: Test in progress
    • autopkgtest for unrar-nonfree: armel: Test in progress
    • autopkgtest for upx-ucl: armel: Test in progress
    • autopkgtest for urdfdom: armel: Test in progress
    • autopkgtest for uwsgi: armel: Test in progress
    • autopkgtest for vagrant: armel: Test in progress
    • autopkgtest for valkey: armel: Test in progress
    • autopkgtest for vamp-plugin-sdk: armel: Test in progress
    • autopkgtest for vcftools: armel: Test in progress
    • autopkgtest for velvet: armel: Test in progress
    • autopkgtest for veryfasttree: armel: Test in progress
    • autopkgtest for veusz: armel: Test in progress
    • autopkgtest for vibes: armel: Test in progress
    • autopkgtest for visp: armel: Test in progress
    • autopkgtest for vlc: armel: Test in progress
    • autopkgtest for vnlog: armel: Test in progress
    • autopkgtest for voacapl: armel: Test in progress
    • autopkgtest for voronota: armel: Test in progress
    • autopkgtest for vt: armel: Test in progress
    • autopkgtest for vtable-dumper: armel: Test in progress
    • autopkgtest for vte2.91: armel: Test in progress
    • autopkgtest for vtk9: armel: Test in progress
    • autopkgtest for wcslib: armel: Test in progress
    • autopkgtest for wesnoth-1.18: armel: Test in progress
    • autopkgtest for wham-align: armel: Test in progress
    • autopkgtest for wikidiff2: armel: Test in progress
    • autopkgtest for wireshark: armel: Test in progress
    • autopkgtest for wmanager: armel: Test in progress
    • autopkgtest for workflow: armel: Test in progress
    • autopkgtest for wp2latex: armel: Test in progress
    • autopkgtest for wpa: armel: Test in progress
    • autopkgtest for wsclean: armel: Test in progress
    • autopkgtest for wvdial: armel: Test in progress
    • autopkgtest for wxwidgets3.2: armel: Test in progress
    • autopkgtest for x265: armel: Test in progress
    • autopkgtest for x42-plugins: armel: Test in progress
    • autopkgtest for xapian-bindings: armel: Test in progress
    • autopkgtest for xapian-core: armel: Test in progress
    • autopkgtest for xapian-omega: armel: Test in progress
    • autopkgtest for xbrzscale: armel: Test in progress
    • autopkgtest for xdg-desktop-portal-phosh: armel: Test in progress
    • autopkgtest for xerces-c: armel: Test in progress
    • autopkgtest for xeus-python: armel: Test in progress
    • autopkgtest for xgboost: armel: Test in progress
    • autopkgtest for xmake: armel: Test in progress
    • autopkgtest for xml-security-c: armel: Test in progress
    • autopkgtest for xmltooling: armel: Test in progress
    • autopkgtest for xmobar: armel: Test in progress
    • autopkgtest for xmoto: armel: Test in progress
    • autopkgtest for xplanet: armel: Test in progress
    • autopkgtest for xsnow: armel: Test in progress
    • autopkgtest for yaha: armel: Test in progress
    • autopkgtest for yapet: armel: Test in progress
    • autopkgtest for ycmd: armel: Test in progress
    • autopkgtest for yoshimi: armel: Test in progress
    • autopkgtest for z3: armel: Test in progress
    • autopkgtest for zarchive: armel: Test in progress
    • autopkgtest for zbar: armel: Test in progress
    • autopkgtest for zfp: armel: Test in progress
    • autopkgtest for zfs-linux: armel: Test in progress
    • autopkgtest for zim-tools: armel: Test in progress
    • autopkgtest for zpspell: armel: Test in progress
    • autopkgtest for zulucrypt: armel: Test in progress
    • autopkgtest for zypper: armel: Test in progress
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • 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:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): gcc-14 amdgcn-tools-19
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-14.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gcl27 (2.7.0-32 to 2.7.0-33)
  • Migration status for gcl27 (2.7.0-32 to 2.7.0-33): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcl27.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• geronimo-interceptor-3.0-spec (1.0.1-4 to 1.0.1-5)
  • Migration status for geronimo-interceptor-3.0-spec (1.0.1-4 to 1.0.1-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
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geronimo-interceptor-3.0-spec.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• geronimo-j2ee-management-1.1-spec (1.0.1-1.1 to 1.0.1-2)
  • Migration status for geronimo-j2ee-management-1.1-spec (1.0.1-1.1 to 1.0.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
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geronimo-j2ee-management-1.1-spec.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-connections (47.0-2 to 48~beta-1)
  • Migration status for gnome-connections (47.0-2 to 48~beta-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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-connections.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-shell-extensions-extra (20240916-1 to 20250212-1)
  • Migration status for gnome-shell-extensions-extra (20240916-1 to 20250212-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating gnome-shell-extensions-extra will fix bugs in testing: #1095826
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extensions-extra.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-github-containers-buildah (1.38.1+ds1-1 to 1.39.0+ds1-1)
  • Migration status for golang-github-containers-buildah (1.38.1+ds1-1 to 1.39.0+ds1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for autopkgtest/5.43: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for golang-github-containers-buildah/1.39.0+ds1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-podman/5.3.0-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): golang-github-containers-buildah golang-github-containers-common
    • Build-Depends(-Arch): golang-github-containers-buildah golang-github-containers-image
    • Build-Depends(-Arch): golang-github-containers-buildah golang-github-containers-storage
    • Built-Using: golang-github-containers-buildah golang-1.23
    • Built-Using: golang-github-containers-buildah golang-github-containers-common
    • Built-Using: golang-github-containers-buildah golang-github-containers-image
    • Built-Using: golang-github-containers-buildah golang-github-containers-storage
    • Built-Using: golang-github-containers-buildah golang-github-mattn-go-runewidth
    • Built-Using: golang-github-containers-buildah golang-golang-x-text
    • Built-Using: golang-github-containers-buildah runc (not considered)
    • Depends: golang-github-containers-buildah golang-github-containers-common
    • Depends: golang-github-containers-buildah golang-github-containers-image
    • Depends: golang-github-containers-buildah golang-github-containers-storage
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-containers-buildah.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-github-prometheus-common (0.61.0-1 to 0.62.0-1)
  • Migration status for golang-github-prometheus-common (0.61.0-1 to 0.62.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-armon-go-metrics/0.4.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for golang-github-minio-madmin-go/3.0.88-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for golang-github-prometheus-client-golang/1.20.5-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Test in progress, armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for golang-github-prometheus-common/0.62.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for golang-github-prometheus-exporter-toolkit/0.14.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for golang-github-prometheus-prom2json/1.3.0+ds1-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for golang-k8s-component-base/0.31.4-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for prometheus/2.45.6+ds-9: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Test in progress, armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for prometheus-alertmanager/0.27.0+ds-3: amd64: Failed (not a regression), arm64: Regression or new test ♻ (reference ♻), armel: Test in progress, armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-prometheus-common.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-github-skeema-mybase (1.0.18-1 to 1.1.0-1)
  • Migration status for golang-github-skeema-mybase (1.0.18-1 to 1.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for golang-github-skeema-mybase/1.1.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-skeema-mybase.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gpicview (0.2.6-1 to 0.2.6-2)
  • Migration status for gpicview (0.2.6-1 to 0.2.6-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpicview.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gtk-vnc (1.4.0-1 to 1.5.0-1)
  • Migration status for gtk-vnc (1.4.0-1 to 1.5.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
    • autopkgtest for gtk-vnc/1.5.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for virt-manager/1:5.0.0-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk-vnc.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gtk4 (4.16.12+ds-3 to 4.17.4+ds-3)
  • Migration status for gtk4 (4.16.12+ds-3 to 4.17.4+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for alsa-scarlett-gui/0.4.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for amberol/2024.2-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for chatty/0.8.6~rc.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for clapper/0.6.1-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for confy/0.8.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for cozy/1.3.0-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for evolution-data-server/3.55.2-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for flatpak/1.16.0-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻
    • autopkgtest for flatpak-builder/1.4.4-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for game-data-packager/82: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for gcr4/4.3.90.3-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gnome-bluetooth3/47.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gnome-calls/47.0-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gnome-console/47.1-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gnome-desktop/44.1-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gnome-metronome/1.3.0-7: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gnome-online-accounts/3.53.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gnome-text-editor/47.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gsequencer/7.5.5-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for gtk+2.0/2.24.33-7: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for gtk+3.0/3.24.48-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for gtk4/4.17.4+ds-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻)
    • autopkgtest for gtkmm4.0/4.16.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gtksourceview5/5.15.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for hydrapaper/3.3.1-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for ibus/1.5.32~beta1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for libadwaita-1/1.7~beta-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for libpanel/1.9.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for libportal/0.9.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for libspelling/0.4.6-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for livi/0.3.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • autopkgtest for mutter/47.4-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for nfoview/2.0.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for nicotine/3.3.7-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for papers/47.3-1: arm64: No tests, superficial or marked flaky ♻, armel: Test in progress
    • autopkgtest for parlatype/4.2-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for phosh/0.44.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for phosh-antispam/3.5-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for phosh-mobile-settings/0.44.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for phosh-tour/0.45~rc1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for picplanner/0.5.0-0.1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for ruby-gnome/4.2.2-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for rust-gdk4/0.9.5-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for rust-gdk4-sys/0.9.5-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for rust-gdk4-wayland-sys/0.9.5-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for rust-gdk4-x11/0.9.5-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for rust-gdk4-x11-sys/0.9.5-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for rust-gsk4-sys/0.9.5-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for rust-gst-plugin-gtk4/0.13.3-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for rust-gtk4/0.9.5-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for rust-gtk4-sys/0.9.5-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for rust-swtchr/0.1.2-6: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for sysprof/47.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for vte2.91/0.78.3-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for vvmplayer/2.6-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for xdg-desktop-portal-phosh/0.44.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • missing build on riscv64
    • missing build on s390x
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk4.html
    • No reference result, but not reproducibility on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• idzebra (2.2.7-2 to 2.2.8-1)
  • Migration status for idzebra (2.2.7-2 to 2.2.8-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 idzebra/2.2.8-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/idzebra.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ikvswitch (1.0.1 to 1.0.2)
  • Migration status for ikvswitch (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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ikvswitch.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• jna-inchi (1.2.1+dfsg-3 to 1.3+dfsg-1)
  • Migration status for jna-inchi (1.2.1+dfsg-3 to 1.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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jna-inchi.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• jnacl (- to 1.0-2)
  • Migration status for jnacl (- 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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jnacl.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• joserfc (1.0.2-1 to 1.0.3-1)
  • Migration status for joserfc (1.0.2-1 to 1.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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/joserfc.html
    • autopkgtest for joserfc/1.0.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• jsonlint (1.11.0-1 to 1.11.0-2)
  • Migration status for jsonlint (1.11.0-1 to 1.11.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsonlint.html
    • autopkgtest for jsonlint/1.11.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• kamailio (5.8.5-1 to 6.0.0-1)
  • Migration status for kamailio (5.8.5-1 to 6.0.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
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kamailio.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• labwc (0.8.2-2 to 0.8.2-3)
  • Migration status for labwc (0.8.2-2 to 0.8.2-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 s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): labwc libsfdo
    • Depends: labwc libsfdo
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/labwc.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lgrind (3.67-8 to 3.67-9)
  • Migration status for lgrind (3.67-8 to 3.67-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 armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• libffi (3.4.6-1 to 3.4.7-1)
  • Migration status for libffi (3.4.6-1 to 3.4.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cjs/6.4.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for diaspora-installer/0.9.0.0+debian2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for flask-jwt-simple/0.0.3-14: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for gauche-c-wrapper/0.6.1-17: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for ghc/9.6.6-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for git-annex/10.20241202-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for glib2.0/2.83.3-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for gnustep-base/1.30.0-9: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for gobject-introspection/1.82.0-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for haskell-hopenpgp-tools/0.23.10-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for hkl/5.1.3-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for libffi-platypus-perl/2.10-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for libglib-object-introspection-perl/0.051-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for libjna-java/5.15.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for llvm-toolchain-17/1:17.0.6-20: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Test in progress, armhf: Pass, i386: Failed (not a regression), ppc64el: Test in progress (will not be considered a regression), riscv64: Failed (not a regression)
    • autopkgtest for llvm-toolchain-18/1:18.1.8-16: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Test in progress, armhf: Pass, i386: Failed (not a regression), ppc64el: Test in progress (will not be considered a regression), riscv64: Pass
    • autopkgtest for llvm-toolchain-19/1:19.1.7-1: amd64: Pass, arm64: Failed (not a regression), armel: Test in progress, armhf: Pass, i386: Failed (not a regression), ppc64el: Test in progress (will not be considered a regression), riscv64: Pass
    • autopkgtest for lua-lgi/0.9.2-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for macaulay2/1.24.11+ds-3: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Pass, riscv64: Test in progress (will not be considered a regression)
    • autopkgtest for pandoc-citeproc-preamble/1.7-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for php8.4/8.4.3-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for phybin/0.3-6: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for pygobject/3.50.0-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻
    • autopkgtest for pypy3/7.3.18+dfsg-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-cffi/1.17.1-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python3.12/3.12.9-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression)
    • autopkgtest for python3.13/3.13.2-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression)
    • autopkgtest for ruby-ffi/1.17.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for ruby3.3/3.3.7-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for shelltestrunner/1.10-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for xmobar/0.48.1-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for yabasic/1:2.90.5-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libffi.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• liboggz (1.1.2-2 to 1.1.2-4)
  • Migration status for liboggz (1.1.2-2 to 1.1.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for liboggz/1.1.2-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • 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 ppc64el binaries not found
    • Not built on buildd: upload info for arch riscv64 binaries not found
    • Not built on buildd: upload info for arch s390x binaries not found
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/liboggz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libportal (0.9.0-1 to 0.9.1-1)
  • Migration status for libportal (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
    • autopkgtest for libportal/0.9.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating libportal will fix bugs in testing: #1082570
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libportal.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• librelaxng-datatype-java (1.0+ds1-3.1 to 1.0+ds1-4)
  • Migration status for librelaxng-datatype-java (1.0+ds1-3.1 to 1.0+ds1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/librelaxng-datatype-java.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libselinux (3.7-3.1 to 3.8-3)
  • Migration status for libselinux (3.7-3.1 to 3.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for at/3.2.5-2.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for libselinux/3.8-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for refpolicy/2:2.20250115-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for sudo/1.9.16p2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for util-linux/2.40.4-3: amd64: Failed (not a regression), arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): libselinux libsepol (not considered)
    • Built-Using: libselinux libsepol (not considered)
    • Depends: libselinux libsepol (not considered)
    • Depends: libselinux pcre2 (not considered)
  • Additional info:
    • Updating libselinux will fix bugs in testing: #1094990
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libselinux.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libss7 (- to 2.0.1-2)
  • Migration status for libss7 (- to 2.0.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libss7.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libsys-virt-perl (10.9.0-1 to 11.0.0-1)
  • Migration status for libsys-virt-perl (10.9.0-1 to 11.0.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
    • autopkgtest for libsys-virt-perl/11.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsys-virt-perl.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libxlsxwriter (1.1.9-1 to 1.2.0-2)
  • Migration status for libxlsxwriter (1.1.9-1 to 1.2.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxlsxwriter.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libzip (1.11.3-1 to 1.11.3-2)
  • Migration status for libzip (1.11.3-1 to 1.11.3-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for ebook-tools/0.2.2-6: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for fuse-zip/0.5.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for libzip/1.11.3-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for php8.4/8.4.3-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libz/libzip.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lodepng (0.0~git20240415.ed3c5f1-1 to 0.0~git20241228.0b1d9cc-1)
  • Migration status for lodepng (0.0~git20240415.ed3c5f1-1 to 0.0~git20241228.0b1d9cc-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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lodepng.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lxml (5.3.0-1 to 5.3.1-1)
  • Migration status for lxml (5.3.0-1 to 5.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for afdko/4.0.1+dfsg1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for androguard/3.4.0~a1-16: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for aodh/19.0.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for beautifulsoup4/4.13.3-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for cairosvg/2.7.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for calibre/7.25.0+ds-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for ceilometer/1:23.0.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for changeme/1.2.3-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for cinder/2:25.0.0-6: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for citeproc-py/0.6.0-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for crmsh/4.6.0-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for ctdconverter/2.1-8: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for debusine/0.8.1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for django-cas-server/2.1.0-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for django-tables/2.7.5-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for dnsrecon/1.2.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for endesive/2.18.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for exhale/0.3.7-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for fonttools/4.55.3-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for freeipa/4.12.2-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • autopkgtest for gla11y/0.4-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for glymur/0.13.8-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for gnome-feeds/2.2.0-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gnumed-client/1.8.19+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gtg/0.6-10: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for heat/1:23.0.0-5: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Pass
    • autopkgtest for hovercraft/2.7-8: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for html5lib/1.2-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for kalamine/0.38-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for keyman/17.0.335-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for keystone/2:26.0.0-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for ledger-autosync/1.2.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for libervia-backend/0.9.0~hg4332-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for libvirt/11.0.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for manila/1:19.0.0-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Pass
    • autopkgtest for mantis-xray/3.2.2-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for masakari-monitors/18.0.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for matrix-synapse/1.121.0-5: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for mintpy/1.6.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Pass
    • autopkgtest for mypy/1.15.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for nova/2:30.0.0-6: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻
    • autopkgtest for octave-geometry/4.1.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for openlp/3.1.6+ds-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for openpyxl/3.1.5+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for openstack-trove/1:22.0.0-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for osinfo-db/0.20250124-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for owslib/0.32.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for oz/0.17.0-5.5: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for pandas/2.2.3+dfsg-8: amd64: Pass, arm64: Test in progress, armel: Test in progress (will not be considered a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for pandoc-include/1.4.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for pcs/0.11.7-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for pikepdf/9.5.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for plip/2.4.0+dfsg-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for pontos/24.9.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for pygments/2.18.0+dfsg-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for pygml/0.2.2-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for pyhamtools/0.10.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for pykeepass/4.1.0.post1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for pykml/0.2.0+dfsg-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for pypeg2/2.15.2-2.2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻
    • autopkgtest for pystemd/0.13.2-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-agate/1.9.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-caldav/1.3.9-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-csb43/0.10.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-cursive/0.2.3-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-docx/1.1.2+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-docx-template/0.19.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-docxcompose/1.4.0-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-ebooklib/0.18-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-exchangelib/5.5.0-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-fabio/2024.4.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-freenom/0.0.2-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-keystoneauth1/5.8.0-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-keystoneclient/1:5.5.0-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-lti/0.9.5-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-mechanicalsoup/1.3.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-meshio/7.0.0-really-5.3.5-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-ncclient/0.6.16-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-ofxclient/2.0.4-7: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-oslo.vmware/4.5.0-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-parsel/1.10.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-prov/2.0.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-pskc/1.3-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-pynlpl/1.2.9-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-scrapy/2.12.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻
    • autopkgtest for python-signxml/4.0.3+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • autopkgtest for python-stetl/2.1-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-svglib/1.5.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-ulmo/0.8.8+dfsg1-8: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-xmlrunner/3.2.0-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-xmlsec/1.3.14-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for python-zeep/4.3.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for pytrainer/2.2.1-5: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for pyxnat/1.6.2-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for rdflib/7.1.1-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for readability/0.8.1+dfsg1-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for recon-ng/5.1.2-1.2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for relatorio/0.11.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for ros-catkin-lint/1.6.25-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for sacad/2.8.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for sasdata/0.9.0-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for slm/1.31-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Failed (not a regression)
    • autopkgtest for soupsieve/2.6-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for spyne/2.14.0-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for stactools/0.5.3-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for streamlink/7.1.2-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for supysonic/0.7.8+ds-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for swift/2.34.0-5: amd64: Failed (not a regression), arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Pass
    • autopkgtest for termtosvg/1.1.0+dfsg-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for tifffile/20250110-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for translate-toolkit/3.14.7-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for tryton-modules-account-payment-sepa/7.0.0+dfsg1-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for tryton-modules-account-payment-sepa-cfonb/7.0.0-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for tryton-modules-account-statement-sepa/7.0.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for tryton-modules-currency-ro/7.0.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for tryton-modules-currency-rs/7.0.0-2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for tryton-modules-dashboard/7.0.1-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for tryton-modules-edocument-uncefact/7.0.1-3: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for tryton-modules-stock-package-shipping-dpd/7.0.1-4: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for tryton-server/7.0.24-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for urlwatch/2.29-1: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for xarray-safe-rcm/2024.11.0-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for xarray-safe-s1/2024.11.28-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for xmds2/3.1.0+dfsg2-10: amd64: Test in progress (will not be considered a regression), arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Test in progress (will not be considered a regression), riscv64: Pass
    • autopkgtest for xml2rfc/3.23.0-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for xmldiff/2.6.3-0.2: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for xsar/2024.12.03-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxml.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mastodon-el (1.1.8-1 to 1.1.9-1)
  • Migration status for mastodon-el (1.1.8-1 to 1.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mastodon-el/1.1.9-1: amd64: Regression or new test ♻, arm64: Test in progress, armel: Test in progress, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mastodon-el.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ng (1.5~beta1-12 to 1.5~beta1-13)
  • Migration status for ng (1.5~beta1-12 to 1.5~beta1-13): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • missing build on s390x
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ng.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nitroxcalc (- to 1.0-2)
  • Migration status for nitroxcalc (- to 1.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nitroxcalc.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ocaml-atd (2.15.0-2 to 2.16.0-1)
  • Migration status for ocaml-atd (2.15.0-2 to 2.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ocaml-atd/2.16.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-atd.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ocaml-benchmark (1.6-4 to 1.7-1)
  • Migration status for ocaml-benchmark (1.6-4 to 1.7-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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-benchmark.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ocaml-mem-usage (0.1.1-2 to 0.1.2-1)
  • Migration status for ocaml-mem-usage (0.1.1-2 to 0.1.2-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 ocaml-mem-usage/0.1.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-mem-usage.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ocaml-spdx-licenses (1.2.0-1 to 1.3.0-1)
  • Migration status for ocaml-spdx-licenses (1.2.0-1 to 1.3.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
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-spdx-licenses.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ocaml-sqlite3 (5.2.0-1 to 5.3.0-1)
  • Migration status for ocaml-sqlite3 (5.2.0-1 to 5.3.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
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-sqlite3.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• openjfx (11.0.11+1-4 to 11.0.11+1-6)
  • Migration status for openjfx (11.0.11+1-4 to 11.0.11+1-6): 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 s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for beast2-mcmc/2.7.6+dfsg-1: amd64: Pass, arm64: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for davmail/6.2.2.3546-1: amd64: Pass, arm64: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • autopkgtest for openchemlib/2023.1.1+dfsg-1: amd64: Pass, arm64: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass
    • autopkgtest for starjava-topcat/4.10.2-1: amd64: Pass, arm64: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating openjfx will fix bugs in testing: #1087423
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjfx.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• patroni (- to 4.0.4-7)
  • Migration status for patroni (- to 4.0.4-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for patroni/4.0.4-7: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/patroni.html
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• php-composer-class-map-generator (1.6.0-1 to 1.6.0-2)
  • Migration status for php-composer-class-map-generator (1.6.0-1 to 1.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for composer/2.8.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for php-composer-class-map-generator/1.6.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-composer-class-map-generator.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• php-composer-pcre (3.3.2-1 to 3.3.2-2)
  • Migration status for php-composer-pcre (3.3.2-1 to 3.3.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for composer/2.8.5-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for php-composer-class-map-generator/1.6.0-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for php-composer-pcre/3.3.2-2: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for php-composer-xdebug-handler/3.0.5-2: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-composer-pcre.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• php-composer-spdx-licenses (1.5.8-2 to 1.5.8-3)
  • Migration status for php-composer-spdx-licenses (1.5.8-2 to 1.5.8-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-composer-spdx-licenses.html
    • autopkgtest for php-composer-spdx-licenses/1.5.8-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-composer-xdebug-handler (3.0.5-2 to 3.0.5-3)
  • Migration status for php-composer-xdebug-handler (3.0.5-2 to 3.0.5-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for composer/2.8.5-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for php-composer-xdebug-handler/3.0.5-3: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-composer-xdebug-handler.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• php-constant-time (3.0.0-2 to 3.0.0-3)
  • Migration status for php-constant-time (3.0.0-2 to 3.0.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-constant-time.html
    • autopkgtest for php-constant-time/3.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-deepcopy (1.12.1-3 to 1.13.0-1)
  • Migration status for php-deepcopy (1.12.1-3 to 1.13.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for php-deepcopy/1.13.0-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for phpunit/11.5.7-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-deepcopy.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ppxlib (0.34.0-1 to 0.35.0-1)
  • Migration status for ppxlib (0.34.0-1 to 0.35.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for elpi/2.0.5-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for ocaml-sedlex/3.3-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for ocaml-visitors/20210608-6: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for ppx-deriving/6.0.3-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for ppx-deriving-yojson/3.9.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ppxlib.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• puppet-module-cloudkitty (14.0.0-2 to 14.0.0-3)
  • Migration status for puppet-module-cloudkitty (14.0.0-2 to 14.0.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-module-cloudkitty.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• putty (0.82-2 to 0.83-1)
  • Migration status for putty (0.82-2 to 0.83-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/putty.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pydbus (0.6.0-5 to 0.6.0-6)
  • Migration status for pydbus (0.6.0-5 to 0.6.0-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydbus.html
    • autopkgtest for pydbus/0.6.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pyferret (- to 7.6.5-9)
  • Migration status for pyferret (- to 7.6.5-9): 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 pyferret/7.6.5-9: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyferret.html
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pytest-check (2.4.1-1 to 2.4.2-1)
  • Migration status for pytest-check (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:
    • autopkgtest for pytest-check/2.4.2-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-sphobjinv/2.3.1.2-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-check.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-asyncclick (8.1.7.2-1 to 8.1.8.0+async-1)
  • Migration status for python-asyncclick (8.1.7.2-1 to 8.1.8.0+async-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Updating python-asyncclick will fix bugs in testing: #1095367
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-asyncclick.html
    • autopkgtest for python-asyncclick/8.1.8.0+async-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-django-libsass (0.9-1 to 0.9-2)
  • Migration status for python-django-libsass (0.9-1 to 0.9-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-libsass.html
    • autopkgtest for python-django-libsass/0.9-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-evdev (1.8.0-1 to 1.9.0-1)
  • Migration status for python-evdev (1.8.0-1 to 1.9.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • missing build on s390x
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for pynput/1.7.7-1: amd64: No tests, superficial or marked flaky ♻, arm64: Test in progress, armel: Test in progress, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-evdev/1.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: Test in progress, armel: Test in progress, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-evdev.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-gsd (3.3.0-1 to 3.4.2-1)
  • Migration status for python-gsd (3.3.0-1 to 3.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mdtraj/1.10.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-gsd/3.4.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Test in progress, armel: Test in progress, armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gsd.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-msrest (0.6.21-4 to 0.6.21-5)
  • Migration status for python-msrest (0.6.21-4 to 0.6.21-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-msrest.html
    • autopkgtest for python-msrest/0.6.21-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-msrestazure (0.6.4-3 to 0.6.4-4)
  • Migration status for python-msrestazure (0.6.4-3 to 0.6.4-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-msrestazure.html
    • autopkgtest for python-msrestazure/0.6.4-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-path-and-address (2.0.1-3 to 2.0.1-4)
  • Migration status for python-path-and-address (2.0.1-3 to 2.0.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-path-and-address.html
    • autopkgtest for python-path-and-address/2.0.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-plugwise (1.7.0-1 to 1.7.1-1)
  • Migration status for python-plugwise (1.7.0-1 to 1.7.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-plugwise.html
    • autopkgtest for python-plugwise/1.7.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• qalculate-qt (- to 5.5.0-1)
  • Migration status for qalculate-qt (- to 5.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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qalculate-qt.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• qtorganizer-mkcal (0.1.0~git20241001.1676e8b-2 to 0.1.0~git20250211.88829da-1)
  • Migration status for qtorganizer-mkcal (0.1.0~git20241001.1676e8b-2 to 0.1.0~git20250211.88829da-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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtorganizer-mkcal.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• r-cran-cards (- to 0.4.0-1)
  • Migration status for r-cran-cards (- 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 michael.crusoe@gmail.com, a new source-only upload is needed to allow migration
    • autopkgtest for r-cran-cards/0.4.0-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-cards.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• r-cran-googledrive (2.1.1-2 to 2.1.1-3)
  • Migration status for r-cran-googledrive (2.1.1-2 to 2.1.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-googledrive.html
    • autopkgtest for r-cran-googledrive/2.1.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• r-cran-shiny (1.10.0+dfsg-1 to 1.10.0+dfsg-2)
  • Migration status for r-cran-shiny (1.10.0+dfsg-1 to 1.10.0+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shiny.html
    • autopkgtest for r-cran-shiny/1.10.0+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• r-cran-waldo (0.6.1-1 to 0.6.1-2)
  • Migration status for r-cran-waldo (0.6.1-1 to 0.6.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-waldo.html
    • autopkgtest for r-cran-waldo/0.6.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• reform-tools (- to 1.67-1)
  • Migration status for reform-tools (- to 1.67-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/reform-tools.html
    • autopkgtest for reform-tools/1.67-1: amd64: No tests, superficial or marked flaky ♻, arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Too young, only 0 of 5 days old
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ros2-colcon-defaults (0.2.8-1 to 0.2.9-1)
  • Migration status for ros2-colcon-defaults (0.2.8-1 to 0.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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros2-colcon-defaults.html
    • autopkgtest for ros2-colcon-defaults/0.2.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• ros2-colcon-python-setup-py (0.2.8-1 to 0.2.9-1)
  • Migration status for ros2-colcon-python-setup-py (0.2.8-1 to 0.2.9-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for ros2-colcon-python-setup-py/0.2.9-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for ros2-colcon-ros/0.5.0-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros2-colcon-python-setup-py.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-dry-logger (- to 1.0.4-1)
  • Migration status for ruby-dry-logger (- 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 abhijith@openmailbox.org, a new source-only upload is needed to allow migration
    • autopkgtest for ruby-dry-logger/1.0.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dry-logger.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-invisible-captcha (2.1.0-1 to 2.3.0-1)
  • Migration status for ruby-invisible-captcha (2.1.0-1 to 2.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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-invisible-captcha.html
    • autopkgtest for ruby-invisible-captcha/2.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-actix-web-codegen (- to 4.3.0-1)
  • Migration status for rust-actix-web-codegen (- to 4.3.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 s390x binaries not found
    • autopkgtest for rust-actix-web-codegen/4.3.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-actix-web-codegen.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• seqan3 (3.3.0+ds-3 to 3.4.0~rc.3+ds-3)
  • Migration status for seqan3 (3.3.0+ds-3 to 3.4.0~rc.3+ds-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating seqan3 will fix bugs in testing: #1093357
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/seqan3.html
    • autopkgtest for seqan3/3.4.0~rc.3+ds-3: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• simdjson (3.10.1-1 to 3.12.0-2)
  • Migration status for simdjson (3.10.1-1 to 3.12.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for simdjson/3.12.0-2: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simdjson.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sinntp (1.6-5 to 1.6-6)
  • Migration status for sinntp (1.6-5 to 1.6-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sinntp.html
    • autopkgtest for sinntp/1.6-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• smartypants (2.0.0-3 to 2.0.0-4)
  • Migration status for smartypants (2.0.0-3 to 2.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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smartypants.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• spdlog (1:1.15.0+ds-2 to 1:1.15.1+ds-1)
  • Migration status for spdlog (1:1.15.0+ds-2 to 1:1.15.1+ds-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 bear/3.1.5-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression)
    • autopkgtest for cryfs/0.11.4-3: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for dolfinx-mpc/0.9.0-2: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for fenics-dolfinx/1:0.9.0-6: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Test in progress (will not be considered a regression), riscv64: Test in progress (will not be considered a regression)
    • autopkgtest for fenicsx-performance-tests/0.9.0-2: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for gr-dab/0.5-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gr-limesdr/3.0.1.10.69-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for j4-dmenu-desktop/3.2-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for kodi/2:21.2+dfsg-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for spdlog/1:1.15.1+ds-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for wasmedge/0.14.1+dfsg-3.1: amd64: Pass, arm64: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spdlog.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• terminaltables (3.1.10-6 to 3.1.10-7)
  • Migration status for terminaltables (3.1.10-6 to 3.1.10-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for terminaltables/3.1.10-7: amd64: No tests, superficial or marked flaky ♻, arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for usbrip/2.2.2+git20221003.5093c84-2: amd64: No tests, superficial or marked flaky ♻, arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/terminaltables.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• typogrify (1:2.0.7-3 to 1:2.0.7-4)
  • Migration status for typogrify (1:2.0.7-3 to 1:2.0.7-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/typogrify.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• wayvnc (- to 0.9.1-1)
  • Migration status for wayvnc (- 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
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wayvnc.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xmake (2.9.7+ds-1 to 2.9.8+ds-1)
  • Migration status for xmake (2.9.7+ds-1 to 2.9.8+ds-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 xmake/2.9.8+ds-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, riscv64: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmake.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• zope.testrunner (6.7-1 to 7.0-1)
  • Migration status for zope.testrunner (6.7-1 to 7.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for lazr.uri/1.0.6-5: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-flexmock/0.12.2-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for zope.testing/5.0.1-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for zope.testrunner/7.0-1: amd64: Pass, arm64: Test in progress, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zope.testrunner.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• alsa-ucm-conf (1.2.13-1 to 1.2.13-2)
  • Migration status for alsa-ucm-conf (1.2.13-1 to 1.2.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 5 days old
  • Additional info:
    • Updating alsa-ucm-conf will fix bugs in testing: #1092257
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/alsa-ucm-conf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ants (2.4.3+dfsg-1 to 2.5.4+dfsg-1)
  • Migration status for ants (2.4.3+dfsg-1 to 2.5.4+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Depends: ants insighttoolkit5
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ants.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• aom (3.11.0-1 to 3.12.0-1)
  • Migration status for aom (3.11.0-1 to 3.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/a/aom.html
    • autopkgtest for aom/3.12.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• asterisk (- to 1:22.2.0~dfsg+~cs6.15.60671435-1)
  • Migration status for asterisk (- to 1:22.2.0~dfsg+~cs6.15.60671435-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asterisk would introduce bugs in testing: #1031046
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): asterisk libss7 (not considered)
    • Depends: asterisk libss7 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk.html
    • autopkgtest for asterisk/1:22.2.0~dfsg+~cs6.15.60671435-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • Remove hint for (transitive) dependency: uw-imap
• beangrow (1.0.0+git20250126-1 to 1.0.0+git20250207-1)
  • Migration status for beangrow (1.0.0+git20250126-1 to 1.0.0+git20250207-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/beangrow.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bluedevil (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for bluedevil (4:6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bluedevil unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): bluedevil libplasma (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bluedevil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• breeze (4:6.2.5-2 to 4:6.3.0-1)
  • Migration status for breeze (4:6.2.5-2 to 4:6.3.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
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): breeze kdecoration
    • Depends: breeze kdecoration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breeze.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• breeze-grub (6.2.5-1 to 6.3.0-1)
  • Migration status for breeze-grub (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breeze-grub.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• breeze-gtk (6.2.5-1 to 6.3.0-1)
  • Migration status for breeze-gtk (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • breeze-gtk unsatisfiable Build-Depends(-Arch) on s390x: breeze-dev (>= 4:6.2.90~)
    • breeze-gtk unsatisfiable Build-Depends(-Arch) on s390x: kde-style-breeze (>= 4:6.2.90~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): breeze-gtk breeze (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breeze-gtk.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• breeze-plymouth (6.2.5-1 to 6.3.0-1)
  • Migration status for breeze-plymouth (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breeze-plymouth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cinder (2:25.0.0-6 to 2:25.0.0-7)
  • Migration status for cinder (2:25.0.0-6 to 2:25.0.0-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/c/cinder.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • autopkgtest for cinder/2:25.0.0-7: amd64: Pass, arm64: Pass, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dde-calendar (5.9.1-4 to 5.14.13-1)
  • Migration status for dde-calendar (5.9.1-4 to 5.14.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dde-calendar unsatisfiable Build-Depends(-Arch) on s390x: libdtkgui-dev (>= 5.7.6)
    • dde-calendar unsatisfiable Build-Depends(-Arch) on s390x: libdtkwidget-dev (>= 5.7.6)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): dde-calendar dde-qt-dbus-factory
    • Build-Depends(-Arch): dde-calendar dtkgui (not considered)
    • Build-Depends(-Arch): dde-calendar dtkwidget (not considered)
    • Depends: dde-calendar dtkcore
    • Depends: dde-calendar dtkgui (not considered)
    • Depends: dde-calendar dtkwidget (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dde-calendar.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dde-qt-dbus-factory (5.5.22-2 to 6.0.1-1)
  • Migration status for dde-qt-dbus-factory (5.5.22-2 to 6.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): dde-qt-dbus-factory dtkcore
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dde-qt-dbus-factory.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dde-qt5integration (5.6.11-1 to 5.7.9-1)
  • Migration status for dde-qt5integration (5.6.11-1 to 5.7.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dde-qt5integration unsatisfiable Build-Depends(-Arch) on s390x: libdtkgui-dev (>= 5.7.8)
    • dde-qt5integration unsatisfiable Build-Depends(-Arch) on s390x: libdtkwidget-dev (>= 5.7.8)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): dde-qt5integration dtkgui (not considered)
    • Build-Depends(-Arch): dde-qt5integration dtkwidget (not considered)
    • Build-Depends(-Arch): dde-qt5integration libqt5xdg
    • Depends: dde-qt5integration dtkcore
    • Depends: dde-qt5integration dtkgui (not considered)
    • Depends: dde-qt5integration dtkwidget (not considered)
    • Depends: dde-qt5integration libqt5xdg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dde-qt5integration.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• deepin-boot-maker (5.7.8+dfsg-4 to 5.10.0+dfsg2-1)
  • Migration status for deepin-boot-maker (5.7.8+dfsg-4 to 5.10.0+dfsg2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): deepin-boot-maker dtkgui (not considered)
    • Build-Depends(-Arch): deepin-boot-maker dtkwidget (not considered)
    • Depends: deepin-boot-maker dtkcore
    • Depends: deepin-boot-maker dtkgui (not considered)
    • Depends: deepin-boot-maker dtkwidget (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepin-boot-maker.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• deepin-calculator (6.5.2-1 to 6.5.4-1)
  • Migration status for deepin-calculator (6.5.2-1 to 6.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • deepin-calculator unsatisfiable Build-Depends(-Arch) on s390x: libdtkgui-dev (>= 5.7.8)
    • deepin-calculator unsatisfiable Build-Depends(-Arch) on s390x: libdtkwidget-dev (>= 5.7.8)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): deepin-calculator dde-qt-dbus-factory
    • Build-Depends(-Arch): deepin-calculator dtkgui (not considered)
    • Build-Depends(-Arch): deepin-calculator dtkwidget (not considered)
    • Depends: deepin-calculator dtkcore
    • Depends: deepin-calculator dtkgui (not considered)
    • Depends: deepin-calculator dtkwidget (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepin-calculator.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• deepin-deb-installer (5.12.4-3 to 6.5.5-1)
  • Migration status for deepin-deb-installer (5.12.4-3 to 6.5.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • deepin-deb-installer unsatisfiable Build-Depends(-Arch) on s390x: libdtkwidget-dev (>= 5.7.6)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): deepin-deb-installer dtkcore
    • Build-Depends(-Arch): deepin-deb-installer dtkwidget (not considered)
    • Depends: deepin-deb-installer dtkcore
    • Depends: deepin-deb-installer dtkgui (not considered)
    • Depends: deepin-deb-installer dtkwidget (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepin-deb-installer.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• deepin-log-viewer (6.5.4+ds1-1 to 6.5.7+ds1-1)
  • Migration status for deepin-log-viewer (6.5.4+ds1-1 to 6.5.7+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • deepin-log-viewer unsatisfiable Build-Depends(-Arch) on s390x: libdtkgui-dev (>= 5.7.6)
    • deepin-log-viewer unsatisfiable Build-Depends(-Arch) on s390x: libdtkwidget-dev (>= 5.7.6)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): deepin-log-viewer dde-qt-dbus-factory
    • Build-Depends(-Arch): deepin-log-viewer dtkgui (not considered)
    • Build-Depends(-Arch): deepin-log-viewer dtkwidget (not considered)
    • Depends: deepin-log-viewer dtkcore
    • Depends: deepin-log-viewer dtkgui (not considered)
    • Depends: deepin-log-viewer dtkwidget (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepin-log-viewer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• deepin-qt5dxcb-plugin (5.6.5-1 to 5.7.9-1)
  • Migration status for deepin-qt5dxcb-plugin (5.6.5-1 to 5.7.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
    • Build-Depends(-Arch): deepin-qt5dxcb-plugin dtkcommon
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepin-qt5dxcb-plugin.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• di (4.54.0.1-1 to 5.0.6-1)
  • Migration status for di (4.54.0.1-1 to 5.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/di.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dislocker (0.7.3+git20240607-2 to 0.7.3+git20240607-3)
  • Migration status for dislocker (0.7.3+git20240607-2 to 0.7.3+git20240607-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/d/dislocker.html
    • autopkgtest for dislocker/0.7.3+git20240607-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• django-celery-email (3.0.0-2 to 3.0.0-3)
  • Migration status for django-celery-email (3.0.0-2 to 3.0.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-celery-email.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• doxygen (1.9.8+ds-2 to 1.9.8+ds-2.1)
  • Migration status for doxygen (1.9.8+ds-2 to 1.9.8+ds-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/doxygen.html
    • autopkgtest for doxygen/1.9.8+ds-2.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• drkonqi (6.2.5-1 to 6.3.0-1)
  • Migration status for drkonqi (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drkonqi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• drumkv1 (1.2.0-1 to 1.3.0-1)
  • Migration status for drumkv1 (1.2.0-1 to 1.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drumkv1.html
    • autopkgtest for drumkv1/1.3.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dtkcore (5.6.2.2-1 to 5.7.9-1)
  • Migration status for dtkcore (5.6.2.2-1 to 5.7.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
    • Build-Depends(-Arch): dtkcore dtkcommon
    • Depends: dtkcore dtkcommon
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dtkcore.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dtkgui (5.6.2.2-2 to 5.7.9-1)
  • Migration status for dtkgui (5.6.2.2-2 to 5.7.9-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
    • Build-Depends(-Arch): dtkgui dtkcommon
    • Build-Depends(-Arch): dtkgui dtkcore
    • Build-Depends(-Arch): dtkgui libqt5xdg
    • Depends: dtkgui dtkcore
    • Depends: dtkgui libqt5xdg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dtkgui.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dtkwidget (5.6.2.2-1 to 5.7.9-1)
  • Migration status for dtkwidget (5.6.2.2-1 to 5.7.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dtkwidget unsatisfiable Build-Depends(-Arch) on s390x: libdtkgui-dev (>= 5.7.9~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): dtkwidget dde-qt-dbus-factory
    • Build-Depends(-Arch): dtkwidget dtkcore
    • Build-Depends(-Arch): dtkwidget dtkgui (not considered)
    • Depends: dtkwidget dtkcore
    • Depends: dtkwidget dtkgui (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dtkwidget.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ejabberd (- to 24.12-2)
  • Migration status for ejabberd (- to 24.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-acme (>= 1.0.25)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-cache-tab (>= 1.0.31-2~)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-mysql (>= 1.0.25)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-pam (>= 1.0.14-3~)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-pgsql (>= 1.1.29)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-pkix (>= 1.0.10-2~)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-sip (>= 1.0.56)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-stringprep (>= 1.0.30-2~)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-xml (>= 1.1.55)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-xmpp (>= 1.9.4)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-yaml (>= 1.0.37-2~)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-yconf (>= 1.0.17)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-zlib (>= 1.0.13-2~)
    • ejabberd unsatisfiable Build-Depends(-Arch) on mips64el: erlang-redis-client (>= 1.2.0-8~)
    • ejabberd unsatisfiable Build-Depends(-Arch) on s390x: erlang-p1-xmpp (>= 1.9.4)
    • missing build on mips64el
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for ejabberd/24.12-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): ejabberd erlang-p1-acme (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-cache-tab (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-eimp
    • Build-Depends(-Arch): ejabberd erlang-p1-mqtree
    • Build-Depends(-Arch): ejabberd erlang-p1-mysql (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-pam (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-pgsql (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-pkix (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-sip (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-sqlite3
    • Build-Depends(-Arch): ejabberd erlang-p1-stringprep (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-stun
    • Build-Depends(-Arch): ejabberd erlang-p1-tls
    • Build-Depends(-Arch): ejabberd erlang-p1-xml (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-xmpp (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-yaml (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-yconf (not considered)
    • Build-Depends(-Arch): ejabberd erlang-p1-zlib (not considered)
    • Build-Depends(-Arch): ejabberd erlang-redis-client (not considered)
    • Depends: ejabberd erlang (not considered)
    • Depends: ejabberd erlang-p1-acme (not considered)
    • Depends: ejabberd erlang-p1-cache-tab (not considered)
    • Depends: ejabberd erlang-p1-eimp
    • Depends: ejabberd erlang-p1-mqtree
    • Depends: ejabberd erlang-p1-pkix (not considered)
    • Depends: ejabberd erlang-p1-stringprep (not considered)
    • Depends: ejabberd erlang-p1-stun
    • Depends: ejabberd erlang-p1-tls
    • Depends: ejabberd erlang-p1-xml (not considered)
    • Depends: ejabberd erlang-p1-xmpp (not considered)
    • Depends: ejabberd erlang-p1-yaml (not considered)
    • Depends: ejabberd erlang-p1-yconf (not considered)
    • Depends: ejabberd erlang-p1-zlib (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ejabberd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• elastix (5.1.0-1 to 5.2.0-2)
  • Migration status for elastix (5.1.0-1 to 5.2.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): elastix insighttoolkit5
    • Depends: elastix insighttoolkit5
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elastix.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• emacs (1:29.4+1-5 to 1:29.4+1-6)
  • Migration status for emacs (1:29.4+1-5 to 1:29.4+1-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• erlang-p1-xmpp (1.8.3-1 to 1.9.4-1)
  • Migration status for erlang-p1-xmpp (1.8.3-1 to 1.9.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • erlang-p1-xmpp unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-xml (>= 1.1.55)
    • erlang-p1-xmpp unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-stringprep (>= 1.0.30-2~)
    • erlang-p1-xmpp unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-zlib (>= 1.0.13-2~)
    • missing build on mips64el
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): erlang-p1-xmpp erlang-p1-stringprep (not considered)
    • Build-Depends(-Arch): erlang-p1-xmpp erlang-p1-tls
    • Build-Depends(-Arch): erlang-p1-xmpp erlang-p1-xml (not considered)
    • Build-Depends(-Arch): erlang-p1-xmpp erlang-p1-zlib (not considered)
    • Depends: erlang-p1-xmpp erlang (not considered)
    • Depends: erlang-p1-xmpp erlang-p1-stringprep (not considered)
    • Depends: erlang-p1-xmpp erlang-p1-tls
    • Depends: erlang-p1-xmpp erlang-p1-xml (not considered)
    • Depends: erlang-p1-xmpp erlang-p1-zlib (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-xmpp.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• eumdac (- to 3.0.0-1.1)
  • Migration status for eumdac (- to 3.0.0-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eumdac.html
    • autopkgtest for eumdac/3.0.0-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• findlib (1.9.6-3 to 1.9.8-1)
  • Migration status for findlib (1.9.6-3 to 1.9.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libfindlib-ocaml/1.9.8-1/amd64 to testing makes coq/8.20.0+dfsg-1+b1/amd64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/amd64 to testing makes libcoq-core-ocaml/8.20.0+dfsg-1+b1/amd64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/amd64 to testing makes libmdx-ocaml/2.5.0-2+b3/amd64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/amd64 to testing makes libocsigenserver-ocaml/6.0.0-1+b3/amd64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/amd64 to testing makes libutop-ocaml/2.15.0-1+b3/amd64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/amd64 to testing makes ocsigenserver/6.0.0-1+b3/amd64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/amd64 to testing makes utop/2.15.0-1+b3/amd64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/amd64 to testing makes libcoq-core-ocaml-dev/8.20.0+dfsg-1+b1/amd64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/amd64 to testing makes libmdx-ocaml-dev/2.5.0-2+b3/amd64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/amd64 to testing makes libocsigenserver-ocaml-dev/6.0.0-1+b3/amd64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/amd64 to testing makes libutop-ocaml-dev/2.15.0-1+b3/amd64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/arm64 to testing makes coq/8.20.0+dfsg-1+b1/arm64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/arm64 to testing makes libcoq-core-ocaml/8.20.0+dfsg-1+b1/arm64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/arm64 to testing makes libmdx-ocaml/2.5.0-2+b3/arm64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/arm64 to testing makes libocsigenserver-ocaml/6.0.0-1+b3/arm64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/arm64 to testing makes libutop-ocaml/2.15.0-1+b2/arm64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/arm64 to testing makes ocsigenserver/6.0.0-1+b3/arm64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/arm64 to testing makes utop/2.15.0-1+b2/arm64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/arm64 to testing makes libcoq-core-ocaml-dev/8.20.0+dfsg-1+b1/arm64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/arm64 to testing makes libmdx-ocaml-dev/2.5.0-2+b3/arm64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/arm64 to testing makes libocsigenserver-ocaml-dev/6.0.0-1+b3/arm64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/arm64 to testing makes libutop-ocaml-dev/2.15.0-1+b2/arm64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/armel to testing makes libmdx-ocaml/2.5.0-2+b3/armel uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/armel to testing makes libocsigenserver-ocaml/6.0.0-1+b3/armel uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/armel to testing makes libutop-ocaml/2.15.0-1+b2/armel uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/armel to testing makes ocsigenserver/6.0.0-1+b3/armel uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/armel to testing makes utop/2.15.0-1+b2/armel uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/armel to testing makes libmdx-ocaml-dev/2.5.0-2+b3/armel uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/armel to testing makes libocsigenserver-ocaml-dev/6.0.0-1+b3/armel uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/armel to testing makes libutop-ocaml-dev/2.15.0-1+b2/armel uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/armhf to testing makes libmdx-ocaml/2.5.0-2+b3/armhf uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/armhf to testing makes libocsigenserver-ocaml/6.0.0-1+b3/armhf uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/armhf to testing makes libutop-ocaml/2.15.0-1+b2/armhf uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/armhf to testing makes ocsigenserver/6.0.0-1+b3/armhf uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/armhf to testing makes utop/2.15.0-1+b2/armhf uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/armhf to testing makes libmdx-ocaml-dev/2.5.0-2+b3/armhf uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/armhf to testing makes libocsigenserver-ocaml-dev/6.0.0-1+b3/armhf uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/armhf to testing makes libutop-ocaml-dev/2.15.0-1+b2/armhf uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/i386 to testing makes libmdx-ocaml/2.5.0-2+b3/i386 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/i386 to testing makes libocsigenserver-ocaml/6.0.0-1+b3/i386 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/i386 to testing makes libutop-ocaml/2.15.0-1+b3/i386 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/i386 to testing makes ocsigenserver/6.0.0-1+b3/i386 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/i386 to testing makes utop/2.15.0-1+b3/i386 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/i386 to testing makes libmdx-ocaml-dev/2.5.0-2+b3/i386 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/i386 to testing makes libocsigenserver-ocaml-dev/6.0.0-1+b3/i386 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/i386 to testing makes libutop-ocaml-dev/2.15.0-1+b3/i386 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/mips64el to testing makes libmdx-ocaml/2.5.0-2+b3/mips64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/mips64el to testing makes libocsigenserver-ocaml/6.0.0-1+b3/mips64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/mips64el to testing makes libutop-ocaml/2.15.0-1+b2/mips64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/mips64el to testing makes ocsigenserver/6.0.0-1+b3/mips64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/mips64el to testing makes utop/2.15.0-1+b2/mips64el uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/mips64el to testing makes libmdx-ocaml-dev/2.5.0-2+b3/mips64el uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/mips64el to testing makes libocsigenserver-ocaml-dev/6.0.0-1+b3/mips64el uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/mips64el to testing makes libutop-ocaml-dev/2.15.0-1+b2/mips64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/ppc64el to testing makes coq/8.20.0+dfsg-1+b1/ppc64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/ppc64el to testing makes libcoq-core-ocaml/8.20.0+dfsg-1+b1/ppc64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/ppc64el to testing makes libmdx-ocaml/2.5.0-2+b3/ppc64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/ppc64el to testing makes libocsigenserver-ocaml/6.0.0-1+b3/ppc64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/ppc64el to testing makes libutop-ocaml/2.15.0-1+b3/ppc64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/ppc64el to testing makes ocsigenserver/6.0.0-1+b3/ppc64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/ppc64el to testing makes utop/2.15.0-1+b3/ppc64el uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/ppc64el to testing makes libcoq-core-ocaml-dev/8.20.0+dfsg-1+b1/ppc64el uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/ppc64el to testing makes libmdx-ocaml-dev/2.5.0-2+b3/ppc64el uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/ppc64el to testing makes libocsigenserver-ocaml-dev/6.0.0-1+b3/ppc64el uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/ppc64el to testing makes libutop-ocaml-dev/2.15.0-1+b3/ppc64el uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/riscv64 to testing makes coq/8.20.0+dfsg-1+b1/riscv64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/riscv64 to testing makes libcoq-core-ocaml/8.20.0+dfsg-1+b1/riscv64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/riscv64 to testing makes libmdx-ocaml/2.5.0-2+b3/riscv64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/riscv64 to testing makes libocsigenserver-ocaml/6.0.0-1+b3/riscv64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/riscv64 to testing makes libutop-ocaml/2.15.0-1+b2/riscv64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/riscv64 to testing makes ocsigenserver/6.0.0-1+b3/riscv64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/riscv64 to testing makes utop/2.15.0-1+b2/riscv64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/riscv64 to testing makes libcoq-core-ocaml-dev/8.20.0+dfsg-1+b1/riscv64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/riscv64 to testing makes libmdx-ocaml-dev/2.5.0-2+b3/riscv64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/riscv64 to testing makes libocsigenserver-ocaml-dev/6.0.0-1+b3/riscv64 uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/riscv64 to testing makes libutop-ocaml-dev/2.15.0-1+b2/riscv64 uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/s390x to testing makes coq/8.20.0+dfsg-1+b1/s390x uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/s390x to testing makes libcoq-core-ocaml/8.20.0+dfsg-1+b1/s390x uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/s390x to testing makes libjs-of-ocaml/5.9.1-1+b3/s390x uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/s390x to testing makes libmdx-ocaml/2.5.0-2+b3/s390x uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/s390x to testing makes liboasis-ocaml/0.4.11-5+b3/s390x uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/s390x to testing makes libocp-indent-ocaml/1.8.2-5+b3/s390x uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/s390x to testing makes libocsigenserver-ocaml/6.0.0-1+b3/s390x uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/s390x to testing makes libutop-ocaml/2.15.0-1+b3/s390x uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/s390x to testing makes ocsigenserver/6.0.0-1+b3/s390x uninstallable
    • migrating libfindlib-ocaml/1.9.8-1/s390x to testing makes utop/2.15.0-1+b3/s390x uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/s390x to testing makes libcoq-core-ocaml-dev/8.20.0+dfsg-1+b1/s390x uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/s390x to testing makes libjs-of-ocaml-dev/5.9.1-1+b3/s390x uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/s390x to testing makes libmdx-ocaml-dev/2.5.0-2+b3/s390x uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/s390x to testing makes liboasis-ocaml-dev/0.4.11-5+b3/s390x uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/s390x to testing makes libocp-indent-ocaml-dev/1.8.2-5+b3/s390x uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/s390x to testing makes libocsigenserver-ocaml-dev/6.0.0-1+b3/s390x uninstallable
    • migrating libfindlib-ocaml-dev/1.9.8-1/s390x to testing makes libutop-ocaml-dev/2.15.0-1+b3/s390x uninstallable
    • autopkgtest for coq/8.20.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for js-of-ocaml-ocamlbuild/5.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ocaml-iter/1.8-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ocaml-mdx/2.5.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ocp-indent/1.8.2-5: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Implicit dependency: findlib js-of-ocaml/amd64 (not considered)
    • Implicit dependency: findlib js-of-ocaml/arm64 (not considered)
    • Implicit dependency: findlib js-of-ocaml/armel
    • Implicit dependency: findlib js-of-ocaml/armhf
    • Implicit dependency: findlib js-of-ocaml/i386
    • Implicit dependency: findlib js-of-ocaml/mips64el
    • Implicit dependency: findlib js-of-ocaml/ppc64el (not considered)
    • Implicit dependency: findlib js-of-ocaml/riscv64 (not considered)
    • Implicit dependency: findlib oasis/amd64
    • Implicit dependency: findlib oasis/arm64
    • Implicit dependency: findlib oasis/armel
    • Implicit dependency: findlib oasis/armhf
    • Implicit dependency: findlib oasis/i386
    • Implicit dependency: findlib oasis/mips64el
    • Implicit dependency: findlib oasis/ppc64el
    • Implicit dependency: findlib oasis/riscv64
    • Implicit dependency: findlib ocp-indent/amd64 (not considered)
    • Implicit dependency: findlib ocp-indent/arm64 (not considered)
    • Implicit dependency: findlib ocp-indent/armel
    • Implicit dependency: findlib ocp-indent/armhf
    • Implicit dependency: findlib ocp-indent/i386
    • Implicit dependency: findlib ocp-indent/mips64el
    • Implicit dependency: findlib ocp-indent/ppc64el (not considered)
    • Implicit dependency: findlib ocp-indent/riscv64 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/findlib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• flask-openapi3 (4.0.3-2 to 4.1.0-1)
  • Migration status for flask-openapi3 (4.0.3-2 to 4.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-openapi3.html
    • autopkgtest for flask-openapi3/4.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• flatpak-kcm (6.2.5-1 to 6.3.0-1)
  • Migration status for flatpak-kcm (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flatpak-kcm.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fte (0.50.2b6-20110708-6 to 0.50.2b6-20110708-7)
  • Migration status for fte (0.50.2b6-20110708-6 to 0.50.2b6-20110708-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/f/fte.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gdbuspp (- to 3-1)
  • Migration status for gdbuspp (- to 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/g/gdbuspp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gecode (6.2.0-6 to 6.2.0-7)
  • Migration status for gecode (6.2.0-6 to 6.2.0-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:
    • Updating gecode will fix bugs in testing: #1092413
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gecode.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gita (0.16.7.2-1 to 0.16.7.2-2)
  • Migration status for gita (0.16.7.2-1 to 0.16.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gita.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnunet-fuse (0.20.0-4 to 0.20.0-5)
  • Migration status for gnunet-fuse (0.20.0-4 to 0.20.0-5): 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 gnunet-fuse/0.20.0-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnunet-fuse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnunet-gtk (0.20.0-4 to 0.20.0-5)
  • Migration status for gnunet-gtk (0.20.0-4 to 0.20.0-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/g/gnunet-gtk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-1.24 (1.24~rc2-1 to 1.24.0-1)
  • Migration status for golang-1.24 (1.24~rc2-1 to 1.24.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-1.24.html
    • autopkgtest for golang-1.24/1.24.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-c2sp-cctv (- to 0.0~git20250126.ac53b9f+ds-1)
  • Migration status for golang-github-c2sp-cctv (- to 0.0~git20250126.ac53b9f+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-c2sp-cctv.html
    • autopkgtest for golang-github-c2sp-cctv/0.0~git20250126.ac53b9f+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-coder-quartz (- to 0.1.3-2)
  • Migration status for golang-github-coder-quartz (- to 0.1.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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-coder-quartz.html
    • autopkgtest for golang-github-coder-quartz/0.1.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-containers-common (0.61.1+ds1-1 to 0.62.0+ds1-1)
  • Migration status for golang-github-containers-common (0.61.1+ds1-1 to 0.62.0+ds1-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): golang-github-containers-common golang-github-containers-image
    • Build-Depends(-Arch): golang-github-containers-common golang-github-containers-storage
    • Depends: golang-github-containers-common golang-github-containers-image
    • Depends: golang-github-containers-common golang-github-containers-storage
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-containers-common.html
    • autopkgtest for golang-github-containers-common/0.62.0+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-containers-image (5.33.1-1 to 5.34.0-1)
  • Migration status for golang-github-containers-image (5.33.1-1 to 5.34.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): golang-github-containers-image golang-github-containers-storage
    • Depends: golang-github-containers-image golang-github-containers-storage
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-containers-image.html
    • autopkgtest for golang-github-containers-image/5.34.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-gdamore-encoding (1.0.0-3 to 1.0.1-1)
  • Migration status for golang-github-gdamore-encoding (1.0.0-3 to 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gdamore-encoding.html
    • autopkgtest for golang-github-gdamore-encoding/1.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-xyproto-randomstring (- to 1.2.0-1)
  • Migration status for golang-github-xyproto-randomstring (- 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 guillem, a new source-only upload is needed to allow migration
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-xyproto-randomstring.html
    • autopkgtest for golang-github-xyproto-randomstring/1.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-go4-unsafe-assume-no-moving-gc (- to 0.0~git20231121.b99613f-2)
  • Migration status for golang-go4-unsafe-assume-no-moving-gc (- to 0.0~git20231121.b99613f-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-go4-unsafe-assume-no-moving-gc.html
    • autopkgtest for golang-go4-unsafe-assume-no-moving-gc/0.0~git20231121.b99613f-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-golang-x-text (0.16.0-1 to 0.22.0-1)
  • Migration status for golang-golang-x-text (0.16.0-1 to 0.22.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/g/golang-golang-x-text.html
    • autopkgtest for golang-golang-x-text/0.22.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• grml-keyring (- to 2025.01.27)
  • Migration status for grml-keyring (- to 2025.01.27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by christian@hofstaedtler.name, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grml-keyring.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• guetzli (1.0.1-1 to 1.0.1-2)
  • Migration status for guetzli (1.0.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/g/guetzli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• hare (- to 0.24.2-1)
  • Migration status for hare (- to 0.24.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): hare harec
    • Depends: hare harec
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hare.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• html-text (0.6.2-1 to 0.7.0-1)
  • Migration status for html-text (0.6.2-1 to 0.7.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/html-text.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• insighttoolkit5 (5.3.0-7 to 5.4.0-2)
  • Migration status for insighttoolkit5 (5.3.0-7 to 5.4.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/insighttoolkit5.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• jakarta-cdi-api (- to 4.0.1-1)
  • Migration status for jakarta-cdi-api (- to 4.0.1-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
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): jakarta-cdi-api jakarta-inject-api (not considered)
    • Depends: jakarta-cdi-api jakarta-inject-api (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jakarta-cdi-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• jakarta-inject-api (- to 2.0.1-1)
  • Migration status for jakarta-inject-api (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jakarta-inject-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• jpylyzer (2.1.0-3 to 2.1.0-4)
  • Migration status for jpylyzer (2.1.0-3 to 2.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/j/jpylyzer.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kactivitymanagerd (6.2.5-1 to 6.3.0-1)
  • Migration status for kactivitymanagerd (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kactivitymanagerd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kbibtex (0.10.0-3 to 0.10.0-4)
  • Migration status for kbibtex (0.10.0-3 to 0.10.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/k/kbibtex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kde-cli-tools (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for kde-cli-tools (4:6.2.5-1 to 4:6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kde-cli-tools.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kde-gtk-config (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for kde-gtk-config (4:6.2.5-1 to 4:6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): kde-gtk-config kdecoration
    • Depends: kde-gtk-config kdecoration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kde-gtk-config.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kde-spectacle (24.12.1-1 to 4:6.3.0-1)
  • Migration status for kde-spectacle (24.12.1-1 to 4:6.3.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
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kde-spectacle.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kdecoration (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for kdecoration (4:6.2.5-1 to 4:6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdecoration.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kdeplasma-addons (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for kdeplasma-addons (4:6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kdeplasma-addons unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • kdeplasma-addons unsatisfiable Build-Depends(-Arch) on s390x: libplasma5support-dev (>= 4:6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): kdeplasma-addons libplasma (not considered)
    • Build-Depends(-Arch): kdeplasma-addons plasma5support (not considered)
    • Depends: kdeplasma-addons kwin (not considered)
    • Depends: kdeplasma-addons libplasma (not considered)
    • Depends: kdeplasma-addons plasma-workspace (not considered)
    • Depends: kdeplasma-addons plasma5support (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdeplasma-addons.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• keyd (- to 2.5.0-1.1)
  • Migration status for keyd (- to 2.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keyd.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kgamma (6.2.5-1 to 6.3.0-1)
  • Migration status for kgamma (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kgamma.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kglobalacceld (6.2.5-1 to 6.3.0-1)
  • Migration status for kglobalacceld (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kglobalacceld.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kinfocenter (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for kinfocenter (4:6.2.5-1 to 4:6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kinfocenter.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kmenuedit (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for kmenuedit (4:6.2.5-1 to 4:6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmenuedit.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kpipewire (6.2.5-1 to 6.3.0-1)
  • Migration status for kpipewire (6.2.5-1 to 6.3.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
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kpipewire.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• krdp (6.2.5-2 to 6.3.0-1)
  • Migration status for krdp (6.2.5-2 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • krdp unsatisfiable Build-Depends(-Arch) on s390x: libkpipewire-dev (>= 6.2.90~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): krdp kpipewire (not considered)
    • Depends: krdp kpipewire (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/krdp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kscreen (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for kscreen (4:6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kscreen unsatisfiable Build-Depends(-Arch) on s390x: libkscreen-dev (>= 4:6.3.0~)
    • kscreen unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): kscreen layer-shell-qt
    • Build-Depends(-Arch): kscreen libkscreen (not considered)
    • Build-Depends(-Arch): kscreen libplasma (not considered)
    • Depends: kscreen kde-cli-tools
    • Depends: kscreen layer-shell-qt
    • Depends: kscreen libkscreen (not considered)
    • Depends: kscreen libplasma (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kscreen.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kscreenlocker (6.2.5-1 to 6.3.0-1)
  • Migration status for kscreenlocker (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kscreenlocker unsatisfiable Build-Depends(-Arch) on s390x: libkscreen-dev (>= 4:6.2.90~)
    • kscreenlocker unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): kscreenlocker layer-shell-qt
    • Build-Depends(-Arch): kscreenlocker libkscreen (not considered)
    • Build-Depends(-Arch): kscreenlocker libplasma (not considered)
    • Depends: kscreenlocker layer-shell-qt
    • Depends: kscreenlocker libkscreen (not considered)
    • Depends: kscreenlocker libplasma (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kscreenlocker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ksshaskpass (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for ksshaskpass (4:6.2.5-1 to 4:6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ksshaskpass.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ksystemstats (6.2.5-1 to 6.3.0-1)
  • Migration status for ksystemstats (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ksystemstats unsatisfiable Build-Depends(-Arch) on s390x: libksysguard-dev (>= 4:6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): ksystemstats libksysguard (not considered)
    • Depends: ksystemstats libksysguard (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ksystemstats.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kustomize (- to 5.5.0+ds-1)
  • Migration status for kustomize (- to 5.5.0+ds-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
    • Not built on buildd: arch amd64 binaries uploaded by samueloph
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): kustomize golang-k8s-sigs-kustomize-api (not considered)
    • Built-Using: kustomize golang-1.23
    • Built-Using: kustomize golang-golang-x-text
    • Built-Using: kustomize golang-k8s-sigs-kustomize-api (not considered)
    • Depends: kustomize golang-k8s-sigs-kustomize-api (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kustomize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kwallet-pam (6.2.5-1 to 6.3.0-1)
  • Migration status for kwallet-pam (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwallet-pam.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kwayland (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for kwayland (4:6.2.5-1 to 4:6.3.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
    • autopkgtest for kwayland/4:6.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwayland.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kwayland-integration (6.2.5-1 to 6.3.0-1)
  • Migration status for kwayland-integration (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwayland-integration.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kwin (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for kwin (4:6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kwin unsatisfiable Build-Depends(-Arch) on s390x: breeze-dev (>= 4:6.2.90~)
    • kwin unsatisfiable Build-Depends(-Arch) on s390x: kscreenlocker-dev (>= 6.2.90~)
    • kwin unsatisfiable Build-Depends(-Arch) on s390x: kwayland-dev (>= 4:6.3.0~)
    • kwin unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • kwin unsatisfiable Build-Depends(-Arch) on s390x: libplasmaactivities-dev (>= 6.3.0~)
    • missing build on s390x
    • 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 ppc64el binaries not found
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): kwin breeze (not considered)
    • Build-Depends(-Arch): kwin kdecoration
    • Build-Depends(-Arch): kwin kglobalacceld
    • Build-Depends(-Arch): kwin kscreenlocker (not considered)
    • Build-Depends(-Arch): kwin kwayland (not considered)
    • Build-Depends(-Arch): kwin libplasma (not considered)
    • Build-Depends(-Arch): kwin plasma-activities (not considered)
    • Depends: kwin kdecoration
    • Depends: kwin kglobalacceld
    • Depends: kwin kscreenlocker (not considered)
    • Depends: kwin kwayland (not considered)
    • Depends: kwin plasma-activities (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwin.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• kwrited (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for kwrited (4:6.2.5-1 to 4:6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kwrited.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• labltk (8.06.14-1 to 8.06.15-1)
  • Migration status for labltk (8.06.14-1 to 8.06.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating liblabltk-ocaml/8.06.15-1/s390x to testing makes liblablgl-ocaml/1:1.07-2+b2/s390x uninstallable
    • migrating liblabltk-ocaml-dev/8.06.15-1/s390x to testing makes liblablgl-ocaml-dev/1:1.07-2+b2/s390x uninstallable
    • Too young, only 1 of 5 days old
    • Implicit dependency: labltk lablgl/amd64
    • Implicit dependency: labltk lablgl/arm64
    • Implicit dependency: labltk lablgl/armel
    • Implicit dependency: labltk lablgl/armhf
    • Implicit dependency: labltk lablgl/i386
    • Implicit dependency: labltk lablgl/mips64el
    • Implicit dependency: labltk lablgl/ppc64el
    • Implicit dependency: labltk lablgl/riscv64
    • Implicit dependency: labltk planets/armel
    • Implicit dependency: labltk planets/armhf
    • Implicit dependency: labltk planets/i386
    • Implicit dependency: labltk planets/mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/labltk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• layer-shell-qt (6.2.5-1 to 6.3.0-1)
  • Migration status for layer-shell-qt (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/layer-shell-qt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lazarus (3.8+dfsg1-5 to 3.8+dfsg1-9)
  • Migration status for lazarus (3.8+dfsg1-5 to 3.8+dfsg1-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 2 days old
    • Build-Depends(-Arch): lazarus fpc (not considered)
    • Depends: lazarus fpc (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lazarus.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for lazarus/3.8+dfsg1-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• legacycrypt (- to 0.3-2)
  • Migration status for legacycrypt (- to 0.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/legacycrypt.html
    • autopkgtest for legacycrypt/0.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libfishsound (1.0.0-10 to 1.0.0-11)
  • Migration status for libfishsound (1.0.0-10 to 1.0.0-11): 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/libf/libfishsound.html
    • autopkgtest for libfishsound/1.0.0-11: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libgraph-nauty-perl (0.5.2-1 to 0.5.3-1)
  • Migration status for libgraph-nauty-perl (0.5.2-1 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/libg/libgraph-nauty-perl.html
    • autopkgtest for libgraph-nauty-perl/0.5.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libkode (- to 0.0~git20241211.68f9908-1)
  • Migration status for libkode (- to 0.0~git20241211.68f9908-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/libk/libkode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libkscreen (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for libkscreen (4:6.2.5-1 to 4:6.3.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
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkscreen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libksysguard (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for libksysguard (4:6.2.5-1 to 4:6.3.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
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libksysguard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libnss-mysql (- to 1.6.1-2)
  • Migration status for libnss-mysql (- to 1.6.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnss-mysql.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libplasma (6.2.5-1 to 6.3.0-1)
  • Migration status for libplasma (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libplasma unsatisfiable Build-Depends(-Arch) on s390x: libplasmaactivities-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for libplasma/6.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): libplasma plasma-activities (not considered)
    • Depends: libplasma plasma-activities (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libplasma.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libregexp-java (1.5-4 to 1.5+dfsg-1)
  • Migration status for libregexp-java (1.5-4 to 1.5+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libregexp-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• librsvg (2.59.1+dfsg-1 to 2.59.90+dfsg-2)
  • Migration status for librsvg (2.59.1+dfsg-1 to 2.59.90+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating librsvg will fix bugs in testing: #1091629
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/librsvg.html
    • autopkgtest for librsvg/2.59.90+dfsg-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libslf4j2-java (- to 2.0.16-1)
  • Migration status for libslf4j2-java (- to 2.0.16-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
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libslf4j2-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libxmlenc-java (0.52+dfsg-5 to 0.52+dfsg2-1)
  • Migration status for libxmlenc-java (0.52+dfsg-5 to 0.52+dfsg2-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/libx/libxmlenc-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libxpp2-java (2.1.10-8 to 2.1.10-9)
  • Migration status for libxpp2-java (2.1.10-8 to 2.1.10-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxpp2-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libxpp3-java (1.1.4c-3 to 1.1.4c-4)
  • Migration status for libxpp3-java (1.1.4c-3 to 1.1.4c-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/libx/libxpp3-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• litestar-htmx (- to 0.4.1-1)
  • Migration status for litestar-htmx (- to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for litestar-htmx/0.4.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/litestar-htmx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• livetribe-jsr223 (2.0.6-2 to 2.0.7-1)
  • Migration status for livetribe-jsr223 (2.0.6-2 to 2.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/l/livetribe-jsr223.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• luanti (- to 5.10.0+dfsg-1)
  • Migration status for luanti (- to 5.10.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • luanti-server/amd64 has unsatisfiable dependency
    • luanti-server/arm64 has unsatisfiable dependency
    • luanti-server/i386 has unsatisfiable dependency
    • luanti-server/s390x has unsatisfiable dependency
    • Not built on buildd: arch amd64 binaries uploaded by tobi
    • Not built on buildd: arch all binaries uploaded by tobi, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/luanti.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lxqt-qt5plugin (- to 1.4.1-1)
  • Migration status for lxqt-qt5plugin (- to 1.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): lxqt-qt5plugin libfm-qt5 (not considered)
    • Build-Depends(-Arch): lxqt-qt5plugin libqt5xdg
    • Build-Depends(-Arch): lxqt-qt5plugin lxqt-build-tools-qt5
    • Depends: lxqt-qt5plugin libfm-qt5 (not considered)
    • Depends: lxqt-qt5plugin libqt5xdg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-qt5plugin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lxqt-wayland-session (- to 0.1.1-1)
  • Migration status for lxqt-wayland-session (- 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 czchen, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-wayland-session.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mathpiper (0.81f+svn4469+dfsg3-3.1 to 0.81f+svn4469+dfsg3-4)
  • Migration status for mathpiper (0.81f+svn4469+dfsg3-3.1 to 0.81f+svn4469+dfsg3-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/m/mathpiper.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mdbook (0.4.43+ds-3 to 0.4.44+ds-1)
  • Migration status for mdbook (0.4.43+ds-3 to 0.4.44+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdbook.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mdtraj (1.10.1-2 to 1.10.3-2)
  • Migration status for mdtraj (1.10.1-2 to 1.10.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating mdtraj will fix bugs in testing: #1094713
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdtraj.html
    • autopkgtest for mdtraj/1.10.3-2: amd64: Pass, arm64: Pass, i386: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• milou (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for milou (4:6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • milou unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): milou libplasma (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/milou.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mkosi (25.3-1 to 25.3-3)
  • Migration status for mkosi (25.3-1 to 25.3-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkosi.html
    • autopkgtest for mkosi/25.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• mkvtoolnix (89.0-1 to 90.0-1)
  • Migration status for mkvtoolnix (89.0-1 to 90.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/m/mkvtoolnix.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mplayer (2:1.5+svn38638-3 to 2:1.5+svn38674-1)
  • Migration status for mplayer (2:1.5+svn38638-3 to 2:1.5+svn38674-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/mplayer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mussort (0.4-3.1 to 0.4-4)
  • Migration status for mussort (0.4-3.1 to 0.4-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/m/mussort.html
    • autopkgtest for mussort/0.4-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• mypy (1.15.0-1 to 1.15.0-2)
  • Migration status for mypy (1.15.0-1 to 1.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mypy/1.15.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for sqlalchemy/2.0.32+ds1-1: amd64: Failed (not a regression), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • missing build on mips64el
    • missing build on riscv64
    • arch:riscv64 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/m/mypy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nanovna-saver (0.6.8-2 to 0.7.1-1)
  • Migration status for nanovna-saver (0.6.8-2 to 0.7.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/n/nanovna-saver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• notification-position-reloaded (- to 0.0~git20241003.720f7e2-2)
  • Migration status for notification-position-reloaded (- to 0.0~git20241003.720f7e2-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/n/notification-position-reloaded.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ocaml-dune (3.17.1-2 to 3.17.2-1)
  • Migration status for ocaml-dune (3.17.1-2 to 3.17.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/o/ocaml-dune.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ocean-sound-theme (6.2.5-1 to 6.3.0-1)
  • Migration status for ocean-sound-theme (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocean-sound-theme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• openjdk-8 (- to 8u442-ga-2)
  • Migration status for openjdk-8 (- to 8u442-ga-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-8 would introduce bugs in testing: #989736
    • autopkgtest for fdroidserver/2.3.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for openjdk-8: amd64: Test in progress (will not be considered a regression), arm64: Test in progress (will not be considered a regression), armel: Test in progress (will not be considered a regression), armhf: Test in progress (will not be considered a regression), i386: Test in progress (will not be considered a regression), ppc64el: Test in progress (will not be considered a regression), s390x: Test in progress (will not be considered a regression)
    • autopkgtest for swi-prolog/9.2.9+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • missing build on mips64el
    • Too young, only 1 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-8.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• openssl (3.4.0-2 to 3.4.1-1)
  • Migration status for openssl (3.4.0-2 to 3.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for aiocoap/0.4.12-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for aioquic/1.2.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for dkms/3.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for golang-github-mendersoftware-openssl/1.1.0-4: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Pass, s390x: Pass
    • autopkgtest for libnet-ssleay-perl/1.94-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for nodejs/20.18.2+dfsg-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for openssl/3.4.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for puppetlabs-http-client-clojure/2.1.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • autopkgtest for python3.12/3.12.9-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for resource-agents/1:4.16.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for systemd/257.2-3: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for testssl.sh/3.2~rc4+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for tlswrapper/0~20250201-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating openssl will fix bugs in testing: #1095765
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openssl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• opm-common (2024.10+ds-3 to 2024.10+ds-4)
  • Migration status for opm-common (2024.10+ds-3 to 2024.10+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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opm-common.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for opm-common/2024.10+ds-4: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• oxygen (4:6.2.5-2 to 4:6.3.0-1)
  • Migration status for oxygen (4:6.2.5-2 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • oxygen unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): oxygen kdecoration
    • Build-Depends(-Arch): oxygen libplasma (not considered)
    • Depends: oxygen kdecoration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oxygen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• oxygen-sounds (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for oxygen-sounds (4:6.2.5-1 to 4:6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oxygen-sounds.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• padthv1 (1.2.0-1 to 1.3.0-1)
  • Migration status for padthv1 (1.2.0-1 to 1.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/padthv1.html
    • autopkgtest for padthv1/1.3.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pglast (7.2-1 to 7.3-1)
  • Migration status for pglast (7.2-1 to 7.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/p/pglast.html
    • autopkgtest for pglast/7.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pkcs11-provider (0.6-1 to 1.0-1)
  • Migration status for pkcs11-provider (0.6-1 to 1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pkcs11-provider.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-activities (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-activities (6.2.5-1 to 6.3.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
    • autopkgtest for plasma-activities/6.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-activities.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-activities-stats (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-activities-stats (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-activities-stats unsatisfiable Build-Depends(-Arch) on s390x: libplasmaactivities-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for plasma-activities-stats/6.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-activities-stats plasma-activities (not considered)
    • Depends: plasma-activities-stats plasma-activities (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-activities-stats.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-browser-integration (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-browser-integration (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-browser-integration unsatisfiable Build-Depends(-Arch) on s390x: libplasmaactivities-dev (>= 6.3.0~)
    • plasma-browser-integration unsatisfiable Build-Depends(-Arch) on s390x: plasma-workspace-dev (>= 4:6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-browser-integration plasma-activities (not considered)
    • Build-Depends(-Arch): plasma-browser-integration plasma-workspace (not considered)
    • Depends: plasma-browser-integration plasma-activities (not considered)
    • Depends: plasma-browser-integration plasma-workspace (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-browser-integration.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-desktop (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for plasma-desktop (4:6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-desktop unsatisfiable Build-Depends(-Arch) on s390x: kscreenlocker-dev (>= 6.2.90~)
    • plasma-desktop unsatisfiable Build-Depends(-Arch) on s390x: kwin-dev (>= 4:6.2.90~)
    • plasma-desktop unsatisfiable Build-Depends(-Arch) on s390x: libksysguard-dev (>= 4:6.2.90~)
    • plasma-desktop unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • plasma-desktop unsatisfiable Build-Depends(-Arch) on s390x: libplasma5support-dev (>= 4:6.3.0~)
    • plasma-desktop unsatisfiable Build-Depends(-Arch) on s390x: libplasmaactivities-dev (>= 6.3.0~)
    • plasma-desktop unsatisfiable Build-Depends(-Arch) on s390x: libplasmaactivitiesstats-dev (>= 6.3.0~)
    • plasma-desktop unsatisfiable Build-Depends(-Arch) on s390x: plasma-workspace-dev (>= 4:6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-desktop kscreenlocker (not considered)
    • Build-Depends(-Arch): plasma-desktop kwin (not considered)
    • Build-Depends(-Arch): plasma-desktop libksysguard (not considered)
    • Build-Depends(-Arch): plasma-desktop libplasma (not considered)
    • Build-Depends(-Arch): plasma-desktop plasma-activities (not considered)
    • Build-Depends(-Arch): plasma-desktop plasma-activities-stats (not considered)
    • Build-Depends(-Arch): plasma-desktop plasma-workspace (not considered)
    • Build-Depends(-Arch): plasma-desktop plasma5support (not considered)
    • Depends: plasma-desktop breeze (not considered)
    • Depends: plasma-desktop kactivitymanagerd
    • Depends: plasma-desktop kde-cli-tools
    • Depends: plasma-desktop layer-shell-qt
    • Depends: plasma-desktop libksysguard (not considered)
    • Depends: plasma-desktop libplasma (not considered)
    • Depends: plasma-desktop ocean-sound-theme
    • Depends: plasma-desktop oxygen-sounds
    • Depends: plasma-desktop plasma-activities (not considered)
    • Depends: plasma-desktop plasma-activities-stats (not considered)
    • Depends: plasma-desktop plasma-integration (not considered)
    • Depends: plasma-desktop plasma-workspace (not considered)
    • Depends: plasma-desktop polkit-kde-agent-1
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-desktop.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-discover (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-discover (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-discover.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-disks (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-disks (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-disks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-firewall (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-firewall (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-firewall.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-integration (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-integration (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-integration unsatisfiable Build-Depends(-Arch) on s390x: breeze-dev (>= 4:6.2.90~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-integration breeze (not considered)
    • Depends: plasma-integration breeze (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-integration.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-nano (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-nano (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-nano unsatisfiable Build-Depends(-Arch) on s390x: kwayland-dev (>= 4:6.3.0~)
    • plasma-nano unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-nano kwayland (not considered)
    • Build-Depends(-Arch): plasma-nano libplasma (not considered)
    • Depends: plasma-nano kwayland (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-nano.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-nm (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for plasma-nm (4:6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-nm unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-nm libplasma (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-nm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-pa (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for plasma-pa (4:6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-pa unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-pa libplasma (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-pa.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-sdk (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-sdk (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-sdk unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • plasma-sdk unsatisfiable Build-Depends(-Arch) on s390x: libplasma5support-dev (>= 4:6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-sdk libplasma (not considered)
    • Build-Depends(-Arch): plasma-sdk plasma5support (not considered)
    • Depends: plasma-sdk libplasma (not considered)
    • Depends: plasma-sdk plasma5support (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-sdk.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-systemmonitor (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-systemmonitor (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-systemmonitor unsatisfiable Build-Depends(-Arch) on s390x: libksysguard-dev (>= 4:6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-systemmonitor libksysguard (not considered)
    • Depends: plasma-systemmonitor ksystemstats (not considered)
    • Depends: plasma-systemmonitor libksysguard (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-systemmonitor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-thunderbolt (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-thunderbolt (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-thunderbolt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-vault (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-vault (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-vault unsatisfiable Build-Depends(-Arch) on s390x: libksysguard-dev (>= 4:6.2.90~)
    • plasma-vault unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • plasma-vault unsatisfiable Build-Depends(-Arch) on s390x: libplasmaactivities-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-vault libksysguard (not considered)
    • Build-Depends(-Arch): plasma-vault libplasma (not considered)
    • Build-Depends(-Arch): plasma-vault plasma-activities (not considered)
    • Depends: plasma-vault libksysguard (not considered)
    • Depends: plasma-vault libplasma (not considered)
    • Depends: plasma-vault plasma-activities (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-vault.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-welcome (6.2.5-1 to 6.3.0-1)
  • Migration status for plasma-welcome (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-welcome unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-welcome libplasma (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-welcome.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-workspace (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for plasma-workspace (4:6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma-workspace unsatisfiable Build-Depends(-Arch) on s390x: breeze-dev (>= 4:6.3.0~)
    • plasma-workspace unsatisfiable Build-Depends(-Arch) on s390x: kscreenlocker-dev (>= 6.3.0~)
    • plasma-workspace unsatisfiable Build-Depends(-Arch) on s390x: kwayland-dev (>= 4:6.3.0~)
    • plasma-workspace unsatisfiable Build-Depends(-Arch) on s390x: kwin-dev (>= 4:6.2.90~)
    • plasma-workspace unsatisfiable Build-Depends(-Arch) on s390x: libkpipewire-dev (>= 6.2.90~)
    • plasma-workspace unsatisfiable Build-Depends(-Arch) on s390x: libkscreen-dev (>= 4:6.3.0~)
    • plasma-workspace unsatisfiable Build-Depends(-Arch) on s390x: libksysguard-dev (>= 4:6.3.0~)
    • plasma-workspace unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • plasma-workspace unsatisfiable Build-Depends(-Arch) on s390x: libplasma5support-dev (>= 4:6.3.0~)
    • plasma-workspace unsatisfiable Build-Depends(-Arch) on s390x: libplasmaactivities-dev (>= 6.3.0~)
    • plasma-workspace unsatisfiable Build-Depends(-Arch) on s390x: libplasmaactivitiesstats-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma-workspace breeze (not considered)
    • Build-Depends(-Arch): plasma-workspace kpipewire (not considered)
    • Build-Depends(-Arch): plasma-workspace kscreenlocker (not considered)
    • Build-Depends(-Arch): plasma-workspace kwayland (not considered)
    • Build-Depends(-Arch): plasma-workspace kwin (not considered)
    • Build-Depends(-Arch): plasma-workspace layer-shell-qt
    • Build-Depends(-Arch): plasma-workspace libkscreen (not considered)
    • Build-Depends(-Arch): plasma-workspace libksysguard (not considered)
    • Build-Depends(-Arch): plasma-workspace libplasma (not considered)
    • Build-Depends(-Arch): plasma-workspace plasma-activities (not considered)
    • Build-Depends(-Arch): plasma-workspace plasma-activities-stats (not considered)
    • Build-Depends(-Arch): plasma-workspace plasma5support (not considered)
    • Depends: plasma-workspace drkonqi
    • Depends: plasma-workspace kactivitymanagerd
    • Depends: plasma-workspace kglobalacceld
    • Depends: plasma-workspace kscreenlocker (not considered)
    • Depends: plasma-workspace kwayland (not considered)
    • Depends: plasma-workspace kwin (not considered)
    • Depends: plasma-workspace layer-shell-qt
    • Depends: plasma-workspace libksysguard (not considered)
    • Depends: plasma-workspace libplasma (not considered)
    • Depends: plasma-workspace milou (not considered)
    • Depends: plasma-workspace plasma-activities (not considered)
    • Depends: plasma-workspace plasma-activities-stats (not considered)
    • Depends: plasma-workspace plasma-integration (not considered)
    • Depends: plasma-workspace plasma5support (not considered)
  • Additional info:
    • Updating plasma-workspace will fix bugs in testing: #1095120
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-workspace.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma-workspace-wallpapers (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for plasma-workspace-wallpapers (4:6.2.5-1 to 4:6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-workspace-wallpapers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plasma5support (6.2.5-1 to 4:6.3.0-1)
  • Migration status for plasma5support (6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • plasma5support unsatisfiable Build-Depends(-Arch) on s390x: libksysguard-dev (>= 4:6.2.90~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): plasma5support libksysguard (not considered)
    • Depends: plasma5support libksysguard (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma5support.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• plymouth-kcm (6.2.5-1 to 6.3.0-1)
  • Migration status for plymouth-kcm (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plymouth-kcm.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• polkit-kde-agent-1 (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for polkit-kde-agent-1 (4:6.2.5-1 to 4:6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polkit-kde-agent-1.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pomegranate-clojure (1.2.24-1 to 1.2.24-3)
  • Migration status for pomegranate-clojure (1.2.24-1 to 1.2.24-3): 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 5 days old
    • Build-Depends(-Arch): pomegranate-clojure cognitect-test-runner-clojure (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pomegranate-clojure.html
    • autopkgtest for pomegranate-clojure/1.2.24-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• powerdevil (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for powerdevil (4:6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • powerdevil unsatisfiable Build-Depends(-Arch) on s390x: libkscreen-dev (>= 4:6.2.90~)
    • powerdevil unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • powerdevil unsatisfiable Build-Depends(-Arch) on s390x: libplasmaactivities-dev (>= 6.3.0~)
    • powerdevil unsatisfiable Build-Depends(-Arch) on s390x: plasma-workspace-dev (>= 4:6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): powerdevil layer-shell-qt
    • Build-Depends(-Arch): powerdevil libkscreen (not considered)
    • Build-Depends(-Arch): powerdevil libplasma (not considered)
    • Build-Depends(-Arch): powerdevil plasma-activities (not considered)
    • Build-Depends(-Arch): powerdevil plasma-workspace (not considered)
    • Depends: powerdevil libkscreen (not considered)
    • Depends: powerdevil plasma-activities (not considered)
    • Depends: powerdevil plasma-workspace (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/powerdevil.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pqconnect (- to 1.2.1-2)
  • Migration status for pqconnect (- to 1.2.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pqconnect.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• print-manager (6:6.2.5-1 to 6:6.3.0-1)
  • Migration status for print-manager (6:6.2.5-1 to 6:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • print-manager unsatisfiable Build-Depends(-Arch) on s390x: libplasma-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): print-manager libplasma (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/print-manager.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• prometheus-alertmanager (0.27.0+ds-3 to 0.28.0+ds-1)
  • Migration status for prometheus-alertmanager (0.27.0+ds-3 to 0.28.0+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): prometheus-alertmanager golang-github-coder-quartz
    • Built-Using: prometheus-alertmanager golang-1.23
    • Built-Using: prometheus-alertmanager golang-github-coder-quartz
    • Built-Using: prometheus-alertmanager golang-golang-x-text
    • Depends: prometheus-alertmanager golang-github-coder-quartz
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-alertmanager.html
    • autopkgtest for prometheus-alertmanager/0.28.0+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Failed (not a regression), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• prosody-modules (0.0~hg20250119.82a10e21b7f9+dfsg-1 to 0.0~hg20250211.fe8222112cf4+dfsg-1)
  • Migration status for prosody-modules (0.0~hg20250119.82a10e21b7f9+dfsg-1 to 0.0~hg20250211.fe8222112cf4+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prosody-modules.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pwru (- to 1.0.5+ds1-1)
  • Migration status for pwru (- to 1.0.5+ds1-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
    • Built-Using: pwru golang-1.23
    • Built-Using: pwru golang-github-mattn-go-runewidth
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pwru.html
    • autopkgtest for pwru/1.0.5+ds1-1: amd64: Pass, arm64: Pass, i386: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pycollada (- to 0.8-1)
  • Migration status for pycollada (- to 0.8-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/pycollada.html
    • autopkgtest for pycollada/0.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pyinstaller (- to 6.12.0+ds-1)
  • Migration status for pyinstaller (- to 6.12.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pyinstaller/6.12.0+ds-1: amd64: Pass, arm64: Pass, armhf: Regression or new test ♻, i386: Regression or new test ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyinstaller.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pylint-celery (0.3-7 to 0.3-8)
  • Migration status for pylint-celery (0.3-7 to 0.3-8): 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/pylint-celery.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-apptools (5.3.0-2 to 5.3.0-3)
  • Migration status for python-apptools (5.3.0-2 to 5.3.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-apptools.html
    • autopkgtest for python-apptools/5.3.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-django-waffle (4.1.0-2 to 4.2.0-1)
  • Migration status for python-django-waffle (4.1.0-2 to 4.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-waffle.html
    • autopkgtest for python-django-waffle/4.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-pathtools (0.1.2-6 to 0.1.2-7)
  • Migration status for python-pathtools (0.1.2-6 to 0.1.2-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/p/python-pathtools.html
    • autopkgtest for python-pathtools/0.1.2-7: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-srsly (- to 2.5.1-1)
  • Migration status for python-srsly (- to 2.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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-srsly.html
    • autopkgtest for python-srsly/2.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-tktooltip (3.0.0-3 to 3.0.0-4)
  • Migration status for python-tktooltip (3.0.0-3 to 3.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/p/python-tktooltip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-truststore (0.10.0-3 to 0.10.1-1)
  • Migration status for python-truststore (0.10.0-3 to 0.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-truststore.html
    • autopkgtest for python-truststore/0.10.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-user-agents (2.2.0-3 to 2.2.0-4)
  • Migration status for python-user-agents (2.2.0-3 to 2.2.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-user-agents.html
    • autopkgtest for python-user-agents/2.2.0-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pyvicare (2.41.0-2 to 2.42.0-1)
  • Migration status for pyvicare (2.41.0-2 to 2.42.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/pyvicare.html
    • autopkgtest for pyvicare/2.42.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• qbootctl (0.2.0-1 to 0.2.0-2)
  • Migration status for qbootctl (0.2.0-1 to 0.2.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qbootctl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• qqc2-breeze-style (6.2.5-1 to 6.3.0-1)
  • Migration status for qqc2-breeze-style (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qqc2-breeze-style.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• qtractor (- to 1.5.3-1)
  • Migration status for qtractor (- to 1.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtractor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• qtrvsim (- to 0.9.8-1)
  • Migration status for qtrvsim (- to 0.9.8-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/q/qtrvsim.html
    • autopkgtest for qtrvsim/0.9.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• r-cran-spacefillr (- to 0.3.3-2)
  • Migration status for r-cran-spacefillr (- to 0.3.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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spacefillr.html
    • autopkgtest for r-cran-spacefillr/0.3.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• railcontrol (- to 23+dfsg1-1)
  • Migration status for railcontrol (- to 23+dfsg1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/railcontrol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• resource-agents (1:4.16.0-1 to 1:4.16.0-2)
  • Migration status for resource-agents (1:4.16.0-1 to 1:4.16.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for resource-agents/1:4.16.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resource-agents.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• resvg (- to 0.44.0-3)
  • Migration status for resvg (- to 0.44.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for resvg/0.44.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resvg.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rkward (0.8.0-2 to 0.8.0-3)
  • Migration status for rkward (0.8.0-2 to 0.8.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/r/rkward.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rosegarden (1:24.12-1 to 1:24.12.1-1)
  • Migration status for rosegarden (1:24.12-1 to 1:24.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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rosegarden.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-defaults (1:3.3~3.2 to 1:3.3)
  • Migration status for ruby-defaults (1:3.3~3.2 to 1:3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-defaults/1:3.3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for ruby-httpclient/2.8.3+git20211122.4658227-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-maxitest/5.8.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-defaults.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ruby-soap4r (2.0.5-8 to 2.0.5-9)
  • Migration status for ruby-soap4r (2.0.5-8 to 2.0.5-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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-soap4r.html
    • autopkgtest for ruby-soap4r/2.0.5-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-gio-0.18 (0.18.4-2 to 0.18.4-3)
  • Migration status for rust-gio-0.18 (0.18.4-2 to 0.18.4-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Depends: rust-gio-0.18 rust-glib-0.18
  • Additional info:
    • Updating rust-gio-0.18 will fix bugs in testing: #1095189
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gio-0.18.html
    • autopkgtest for rust-gio-0.18/0.18.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-wasmtime (21.0.2+dfsg-1.1 to 26.0.1+dfsg-2)
  • Migration status for rust-wasmtime (21.0.2+dfsg-1.1 to 26.0.1+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-wasmtime rust-regalloc2
    • Depends: rust-wasmtime rust-regalloc2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-wasmtime.html
    • autopkgtest for rust-wasmtime/26.0.1+dfsg-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• samplv1 (1.2.0-1 to 1.3.0-1)
  • Migration status for samplv1 (1.2.0-1 to 1.3.0-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 samplv1/1.3.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/samplv1.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• scaphandre (1.0.0-7 to 1.0.2-1)
  • Migration status for scaphandre (1.0.0-7 to 1.0.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • 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/s/scaphandre.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sddm-kcm (- to 4:6.3.0-1)
  • Migration status for sddm-kcm (- to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sddm-kcm would introduce bugs in testing: #1090041
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sddm-kcm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sdl2-pango (- to 2.1.5-2)
  • Migration status for sdl2-pango (- to 2.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdl2-pango.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• seqan-raptor (3.0.1+ds-5 to 3.0.1+ds-9)
  • Migration status for seqan-raptor (3.0.1+ds-5 to 3.0.1+ds-9): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): seqan-raptor seqan3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/seqan-raptor.html
    • autopkgtest for seqan-raptor/3.0.1+ds-9: amd64: Pass, arm64: Pass, ppc64el: Failed (not a regression), riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sogo (5.11.2-1 to 5.11.2-3)
  • Migration status for sogo (5.11.2-1 to 5.11.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
    • Build-Depends(-Arch): sogo sbjson
    • Build-Depends(-Arch): sogo sope
    • Depends: sogo gnustep-make (not considered)
  • Additional info:
    • Updating sogo will fix bugs in testing: #1094304
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sogo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sourmash (4.8.14-2 to 4.8.14-3)
  • Migration status for sourmash (4.8.14-2 to 4.8.14-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
    • Depends: sourmash rocksdb
  • Additional info:
    • Updating sourmash will fix bugs in testing: #1095393
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sourmash.html
    • autopkgtest for sourmash/4.8.14-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• sphinx-toolbox (- to 3.8.2-1)
  • Migration status for sphinx-toolbox (- to 3.8.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-toolbox.html
    • autopkgtest for sphinx-toolbox/3.8.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• synthv1 (1.2.0-1 to 1.3.0-1)
  • Migration status for synthv1 (1.2.0-1 to 1.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/synthv1.html
    • autopkgtest for synthv1/1.3.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• systemsettings (4:6.2.5-1 to 4:6.3.0-1)
  • Migration status for systemsettings (4:6.2.5-1 to 4:6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • systemsettings unsatisfiable Build-Depends(-Arch) on s390x: libplasmaactivities-dev (>= 6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): systemsettings plasma-activities (not considered)
    • Depends: systemsettings plasma-activities (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/systemsettings.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• tasmanian (- to 8.1-3)
  • Migration status for tasmanian (- to 8.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for tasmanian/8.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tasmanian.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• tellico (4.1-1 to 4.1.1-1)
  • Migration status for tellico (4.1-1 to 4.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/t/tellico.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• thermald (2.5.8-2 to 2.5.9-1)
  • Migration status for thermald (2.5.8-2 to 2.5.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/t/thermald.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• tinycbor (- to 0.6.0-2)
  • Migration status for tinycbor (- 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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tinycbor.html
    • autopkgtest for tinycbor/0.6.0-2: amd64: Pass, i386: Pass
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• tools-build-clojure (0.10.6+ds-3 to 0.10.6+ds-4)
  • Migration status for tools-build-clojure (0.10.6+ds-3 to 0.10.6+ds-4): 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/t/tools-build-clojure.html
    • autopkgtest for tools-build-clojure/0.10.6+ds-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• tsctp (- to 0.8.1-1)
  • Migration status for tsctp (- to 0.8.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tsctp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• uwsgi-plugin-java (- to 0.0.5)
  • Migration status for uwsgi-plugin-java (- to 0.0.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/u/uwsgi-plugin-java.html
    • autopkgtest for uwsgi-plugin-java/0.0.5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• vcmi (- to 1.6.5+dfsg-1)
  • Migration status for vcmi (- to 1.6.5+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• vmtouch (1.3.1-2 to 1.3.1-3)
  • Migration status for vmtouch (1.3.1-2 to 1.3.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vmtouch.html
    • autopkgtest for vmtouch/1.3.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• wacomtablet (6.2.5-1 to 6.3.0-1)
  • Migration status for wacomtablet (6.2.5-1 to 6.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): wacomtablet libplasma (not considered)
    • Build-Depends(-Arch): wacomtablet plasma5support (not considered)
    • Depends: wacomtablet plasma5support (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wacomtablet.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• wchartype (0.1-3 to 0.1-4)
  • Migration status for wchartype (0.1-3 to 0.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wchartype.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• weii (- to 0.1.2-5)
  • Migration status for weii (- to 0.1.2-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/w/weii.html
    • autopkgtest for weii/0.1.2-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• wireviz (- to 0.4.1-1)
  • Migration status for wireviz (- to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by obbardc@gmail.com, a new source-only upload is needed to allow migration
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wireviz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xdg-desktop-portal-kde (6.2.5-1 to 6.3.0-1)
  • Migration status for xdg-desktop-portal-kde (6.2.5-1 to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xdg-desktop-portal-kde unsatisfiable Build-Depends(-Arch) on s390x: kwayland-dev (>= 4:6.3.0~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): xdg-desktop-portal-kde kwayland (not considered)
    • Depends: xdg-desktop-portal-kde kwayland (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdg-desktop-portal-kde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xrayutilities (- to 1.7.8-2)
  • Migration status for xrayutilities (- to 1.7.8-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xrayutilities.html
    • autopkgtest for xrayutilities/1.7.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• yamale (5.2.1-2 to 6.0.0-1)
  • Migration status for yamale (5.2.1-2 to 6.0.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yamale.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• yuzu (- to 0-1734+ds-3)
  • Migration status for yuzu (- to 0-1734+ds-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
    • autopkgtest for yuzu/0-1734+ds-3: amd64: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): yuzu oaknut
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yuzu.html
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• zypper (1.14.81-1 to 1.14.83-1)
  • Migration status for zypper (1.14.81-1 to 1.14.83-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • zypper unsatisfiable Build-Depends(-Arch) on s390x: libzypp-dev (>= 17.36~)
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for zypper/1.14.83-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): zypper libzypp (not considered)
    • Depends: zypper libzypp (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zypper.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• zzuf (0.15-4 to 0.15-5)
  • Migration status for zzuf (0.15-4 to 0.15-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/z/zzuf.html
    • autopkgtest for zzuf/0.15-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• 7zip (24.09+dfsg-3 to 24.09+dfsg-4)
  • Migration status for 7zip (24.09+dfsg-3 to 24.09+dfsg-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): 7zip asmc-linux (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/7/7zip.html
    • autopkgtest for 7zip/24.09+dfsg-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ablog (- to 0.11.12-4)
  • Migration status for ablog (- to 0.11.12-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/a/ablog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• alicevision (- to 3.2.0+repack-1)
  • Migration status for alicevision (- to 3.2.0+repack-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): alicevision geogram
    • Depends: alicevision geogram
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• asmc-linux (- to 0.0~git20250115.1606b4a+ds-1)
  • Migration status for asmc-linux (- to 0.0~git20250115.1606b4a+ds-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/a/asmc-linux.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• azure-cli (2.68.0-1 to 2.69.0-1)
  • Migration status for azure-cli (2.68.0-1 to 2.69.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): azure-cli python-azure (not considered)
    • Depends: azure-cli python-azure (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/azure-cli.html
    • autopkgtest for azure-cli/2.69.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• basemap (- to 1.4.1-1)
  • Migration status for basemap (- to 1.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): basemap numpy (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/basemap.html
    • autopkgtest for basemap/1.4.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• beagle (- to 241217-3)
  • Migration status for beagle (- to 241217-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/b/beagle.html
    • autopkgtest for beagle/241217-3: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• budgie-extras (1.8.0-1 to 1.9.0-1)
  • Migration status for budgie-extras (1.8.0-1 to 1.9.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/budgie-extras.html
    • autopkgtest for budgie-extras/1.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• buteo-syncfw (0.11.6-3 to 0.11.8-1)
  • Migration status for buteo-syncfw (0.11.6-3 to 0.11.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/buteo-syncfw.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• castle-game-engine (7.0~alpha.3+dfsg1-11 to 7.0~alpha.3+dfsg2-2)
  • Migration status for castle-game-engine (7.0~alpha.3+dfsg1-11 to 7.0~alpha.3+dfsg2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for castle-game-engine/7.0~alpha.3+dfsg2-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Failed (not a regression)
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): castle-game-engine fpc (not considered)
    • Depends: castle-game-engine fpc (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/castle-game-engine.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• checksecurity (- to 2.0.18)
  • Migration status for checksecurity (- to 2.0.18): 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/checksecurity.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• chromhmm (- to 1.26+dfsg-2)
  • Migration status for chromhmm (- to 1.26+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for chromhmm/1.26+dfsg-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chromhmm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• clonezilla (5.8.9-1 to 5.8.14-1)
  • Migration status for clonezilla (5.8.9-1 to 5.8.14-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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• code-minimap (- to 0.6.8+dfsg-1)
  • Migration status for code-minimap (- to 0.6.8+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/code-minimap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cognitect-test-runner-clojure (- to 0.5.1-1)
  • Migration status for cognitect-test-runner-clojure (- to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by rlb, 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/c/cognitect-test-runner-clojure.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• courier (- to 1.3.13-6)
  • Migration status for courier (- to 1.3.13-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/courier.html
    • autopkgtest for courier/1.3.13-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): courier courier-authlib (not considered)
    • Depends: courier courier-authlib (not considered)
    • Depends: courier maildrop
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ddcci-driver-linux (0.4.4-3 to 0.4.5-1)
  • Migration status for ddcci-driver-linux (0.4.4-3 to 0.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/ddcci-driver-linux.html
    • autopkgtest for ddcci-driver-linux/0.4.5-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dde-account-faces (1.0.16-1 to 1.0.17-1)
  • Migration status for dde-account-faces (1.0.16-1 to 1.0.17-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/dde-account-faces.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• django-choices-field (- to 2.3.0-1)
  • Migration status for django-choices-field (- 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 c.schoenert@t-online.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-choices-field.html
    • autopkgtest for django-choices-field/2.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• django-iconify (0.4-2 to 0.4.1-1)
  • Migration status for django-iconify (0.4-2 to 0.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-iconify.html
    • autopkgtest for django-iconify/0.4.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• django-yarnpkg (6.1.2-1 to 6.1.2-2)
  • Migration status for django-yarnpkg (6.1.2-1 to 6.1.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/d/django-yarnpkg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• drbl (5.4.3-1 to 5.4.5-1)
  • Migration status for drbl (5.4.3-1 to 5.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drbl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• dtkcommon (5.7.4-1 to 5.7.9-3)
  • Migration status for dtkcommon (5.7.4-1 to 5.7.9-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/d/dtkcommon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• eprosima-idl-parser (4.0.2+dfsg-1 to 4.0.3+dfsg-1)
  • Migration status for eprosima-idl-parser (4.0.2+dfsg-1 to 4.0.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eprosima-idl-parser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• exiv2 (0.28.3+dfsg-2 to 0.28.4+dfsg-1)
  • Migration status for exiv2 (0.28.3+dfsg-2 to 0.28.4+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/exiv2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• fastddsgen (4.0.2+dfsg-1 to 4.0.3+dfsg-1)
  • Migration status for fastddsgen (4.0.2+dfsg-1 to 4.0.3+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fastddsgen.html
    • autopkgtest for fastddsgen/4.0.3+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• fisicalab.app (- to 0.4.0-2)
  • Migration status for fisicalab.app (- to 0.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 2 of 5 days old
    • Build-Depends(-Arch): fisicalab.app gnustep-gui (not considered)
    • Depends: fisicalab.app gnustep-make (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fisicalab.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• flatseal (- to 2.3.0-1.1)
  • Migration status for flatseal (- to 2.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flatseal.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• fldigi (4.2.05-1 to 4.2.06-1)
  • Migration status for fldigi (4.2.05-1 to 4.2.06-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/f/fldigi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• flickcurl (1.26-8 to 1.26-9)
  • Migration status for flickcurl (1.26-8 to 1.26-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flickcurl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• flufl.bounce (4.0-5 to 4.0-6)
  • Migration status for flufl.bounce (4.0-5 to 4.0-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flufl.bounce.html
    • autopkgtest for flufl.bounce/4.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• flufl.i18n (5.0.2-2 to 5.1.0-1)
  • Migration status for flufl.i18n (5.0.2-2 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flufl.i18n.html
    • autopkgtest for flufl.i18n/5.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• forgejo-api (- to 0.6.0-1)
  • Migration status for forgejo-api (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for forgejo-api/0.6.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forgejo-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• forgejo-cli (- to 0.2.0-2)
  • Migration status for forgejo-cli (- to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on arm64: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on armel: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on armhf: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on i386: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on mips64el: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on ppc64el: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on riscv64: librust-forgejo-api-0.5+default-dev
    • forgejo-cli unsatisfiable Build-Depends(-Arch) on s390x: librust-forgejo-api-0.5+default-dev
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 2 of 10 days old
    • Build-Depends(-Arch): forgejo-cli rust-sha256 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forgejo-cli.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• freedombox (25.2 to 25.3)
  • Migration status for freedombox (25.2 to 25.3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating freedombox will fix bugs in testing: #1094944
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freedombox.html
    • autopkgtest for freedombox/25.3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• futuresql (0.1.1-1 to 0.1.1-2)
  • Migration status for futuresql (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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/futuresql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gdm3 (47.0-4 to 48~beta-1)
  • Migration status for gdm3 (47.0-4 to 48~beta-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/g/gdm3.html
    • autopkgtest for gdm3/48~beta-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-decoder (- to 0.6.1-1)
  • Migration status for gnome-decoder (- to 0.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/g/gnome-decoder.html
    • autopkgtest for gnome-decoder/0.6.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on armhf - info ♻
• gnome-nibbles (1:4.2~rc4-1 to 1:4.2~rc5-1)
  • Migration status for gnome-nibbles (1:4.2~rc4-1 to 1:4.2~rc5-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/g/gnome-nibbles.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• gnunet (0.20.0-6 to 0.20.0-7)
  • Migration status for gnunet (0.20.0-6 to 0.20.0-7): 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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnunet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnustep-back (0.31.0-4 to 0.31.0-8)
  • Migration status for gnustep-back (0.31.0-4 to 0.31.0-8): 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 gnustep-back/0.31.0-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): gnustep-back gnustep-gui (not considered)
    • Depends: gnustep-back gnustep-gui (not considered)
    • Depends: gnustep-back gnustep-make (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnustep-back.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnustep-base (1.30.0-9 to 1.30.0-14)
  • Migration status for gnustep-base (1.30.0-9 to 1.30.0-14): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gnustep-base gnustep-make (not considered)
    • Depends: gnustep-base gnustep-make (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Implicit dependency: gnustep-base gnustep-corebase
    • Implicit dependency: gnustep-base gnustep-gui (not considered)
    • Implicit dependency: gnustep-base gnustep-netclasses
    • Implicit dependency: gnustep-base unar
    • Implicit dependency: gnustep-base universal-detector
  • Additional info:
    • Updating gnustep-base will fix bugs in testing: #1093948
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnustep-base.html
    • autopkgtest for gnustep-base/1.30.0-14: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for gnustep-dl2/0.12.0+git20171224-4: s390x: Pass
    • autopkgtest for gnustep-gui/0.31.1-9: s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• gnustep-dl2 (0.12.0+git20171224-3 to 0.12.0+git20171224-5)
  • Migration status for gnustep-dl2 (0.12.0+git20171224-3 to 0.12.0+git20171224-5): 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 gnustep-dl2/0.12.0+git20171224-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): gnustep-dl2 gorm.app (not considered)
    • Depends: gnustep-dl2 gnustep-make (not considered)
  • Additional info:
    • Updating gnustep-dl2 will fix bugs in testing: #1094001
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnustep-dl2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnustep-gui (0.31.1-6 to 0.31.1-10)
  • Migration status for gnustep-gui (0.31.1-6 to 0.31.1-10): 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 gnustep-gui/0.31.1-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): gnustep-gui gnustep-base
    • Depends: gnustep-gui gnustep-base
    • Depends: gnustep-gui gnustep-make (not considered)
  • Additional info:
    • Updating gnustep-gui will fix bugs in testing: #1093950
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnustep-gui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-1.22 (1.22.11-1 to 1.22.12-3)
  • Migration status for golang-1.22 (1.22.11-1 to 1.22.12-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-1.22.html
    • autopkgtest for golang-1.22/1.22.12-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-1.23 (1.23.5-1 to 1.23.6-3)
  • Migration status for golang-1.23 (1.23.5-1 to 1.23.6-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-1.23.html
    • autopkgtest for golang-1.23/1.23.6-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-containers-storage (1.56.1+ds1-1 to 1.57.1+ds1-1)
  • Migration status for golang-github-containers-storage (1.56.1+ds1-1 to 1.57.1+ds1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containers-storage golang-1.23
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-containers-storage.html
    • autopkgtest for golang-github-containers-storage/1.57.1+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-d4l3k-go-bfloat16 (- to 0.0~git20211005.690c3bd-2)
  • Migration status for golang-github-d4l3k-go-bfloat16 (- to 0.0~git20211005.690c3bd-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-d4l3k-go-bfloat16.html
    • autopkgtest for golang-github-d4l3k-go-bfloat16/0.0~git20211005.690c3bd-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-google-go-sev-guest (- to 0.12.1-2)
  • Migration status for golang-github-google-go-sev-guest (- to 0.12.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-google-go-sev-guest.html
    • autopkgtest for golang-github-google-go-sev-guest/0.12.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-mattn-go-runewidth (0.0.15-2 to 0.0.16-1)
  • Migration status for golang-github-mattn-go-runewidth (0.0.15-2 to 0.0.16-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-mattn-go-runewidth.html
    • autopkgtest for golang-github-mattn-go-runewidth/0.0.16-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-nlpodyssey-gopickle (- to 0.3.0-2)
  • Migration status for golang-github-nlpodyssey-gopickle (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-nlpodyssey-gopickle/0.3.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-nlpodyssey-gopickle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• golang-github-saracen-fastzip (- to 0.1.11-2)
  • Migration status for golang-github-saracen-fastzip (- to 0.1.11-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-saracen-fastzip.html
    • autopkgtest for golang-github-saracen-fastzip/0.1.11-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-github-xtgo-set (- to 1.0.0-2)
  • Migration status for golang-github-xtgo-set (- to 1.0.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-xtgo-set.html
    • autopkgtest for golang-github-xtgo-set/1.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• golang-glog (1.2.2-1 to 1.2.4-1)
  • Migration status for golang-glog (1.2.2-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-glog.html
    • autopkgtest for golang-glog/1.2.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• gorm.app (1.4.0-5 to 1.4.0-7)
  • Migration status for gorm.app (1.4.0-5 to 1.4.0-7): 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 2 of 5 days old
    • Build-Depends(-Arch): gorm.app gnustep-gui (not considered)
    • Depends: gorm.app gnustep-make (not considered)
  • Additional info:
    • Updating gorm.app will fix bugs in testing: #1093990
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gorm.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• govee-ble (0.42.0-1 to 0.43.0-1)
  • Migration status for govee-ble (0.42.0-1 to 0.43.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/govee-ble.html
    • autopkgtest for govee-ble/0.43.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• grml-hwinfo (- to 0.18.5)
  • Migration status for grml-hwinfo (- to 0.18.5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grml-hwinfo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• grml-paste (- to 0.9.4)
  • Migration status for grml-paste (- to 0.9.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/g/grml-paste.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gtk-session-lock (- to 0.2.0-2)
  • Migration status for gtk-session-lock (- to 0.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk-session-lock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• haruna (1.3.2-1 to 1.3.2-3)
  • Migration status for haruna (1.3.2-1 to 1.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haruna.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• haskell-futhark (- to 0.25.27-1)
  • Migration status for haskell-futhark (- to 0.25.27-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:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for haskell-futhark/0.25.27-1: amd64: No tests, superficial or marked flaky ♻, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): haskell-futhark haskell-cmark-gfm (not considered)
    • Build-Depends-Indep: haskell-futhark haskell-cmark-gfm (not considered)
    • Depends: haskell-futhark haskell-cmark-gfm (not considered)
    • Depends: haskell-futhark haskell-statistics/amd64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-futhark.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• hplip (- to 3.22.10+dfsg0-7)
  • Migration status for hplip (- to 3.22.10+dfsg0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hplip would introduce bugs in testing: #1085142
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hplip.html
    • autopkgtest for hplip/3.22.10+dfsg0-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ibus-typing-booster (2.27.13-1 to 2.27.23-1)
  • Migration status for ibus-typing-booster (2.27.13-1 to 2.27.23-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/ibus-typing-booster.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• ikiwiki-hosting (0.20220717-1 to 0.20220717-2)
  • Migration status for ikiwiki-hosting (0.20220717-1 to 0.20220717-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating ikiwiki-hosting will fix bugs in testing: #1094946
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ikiwiki-hosting.html
    • autopkgtest for ikiwiki-hosting/0.20220717-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• intel-graphics-compiler2 (- to 2.5.12-1)
  • Migration status for intel-graphics-compiler2 (- to 2.5.12-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): intel-graphics-compiler2 intel-vc-intrinsics (not considered)
    • Build-Depends(-Arch): intel-graphics-compiler2 llvm-toolchain-14 (not considered)
    • Build-Depends(-Arch): intel-graphics-compiler2 opencl-clang-14
    • Build-Depends(-Arch): intel-graphics-compiler2 spirv-llvm-translator-14
    • Depends: intel-graphics-compiler2 llvm-toolchain-14 (not considered)
    • Depends: intel-graphics-compiler2 opencl-clang-14
    • Depends: intel-graphics-compiler2 spirv-llvm-translator-14
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-graphics-compiler2.html
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• leds-alix (0.0.1-3 to 0.0.1-5)
  • Migration status for leds-alix (0.0.1-3 to 0.0.1-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/leds-alix.html
    • autopkgtest for leds-alix/0.0.1-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libavtp (0.2.0-1 to 0.2.0-2)
  • Migration status for libavtp (0.2.0-1 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libavtp.html
    • autopkgtest for libavtp/0.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libexif (0.6.24-2 to 0.6.25-1)
  • Migration status for libexif (0.6.24-2 to 0.6.25-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/libe/libexif.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libjsr311-api-java (1.1.1-1.1 to 1.1.1-2)
  • Migration status for libjsr311-api-java (1.1.1-1.1 to 1.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjsr311-api-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libjxp-java (1.6.1-6.1 to 1.6.1-7)
  • Migration status for libjxp-java (1.6.1-6.1 to 1.6.1-7): 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/libj/libjxp-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libmicroba-java (1:0.4.4.3-5.1 to 1:0.4.4.3-6)
  • Migration status for libmicroba-java (1:0.4.4.3-5.1 to 1:0.4.4.3-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/libm/libmicroba-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libmime-util-java (2.1.3-3 to 2.1.3-4)
  • Migration status for libmime-util-java (2.1.3-3 to 2.1.3-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/libm/libmime-util-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libmnemonicsetter-java (0.5-1.1 to 0.6-1)
  • Migration status for libmnemonicsetter-java (0.5-1.1 to 0.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmnemonicsetter-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libnginx-mod-http-auth-spnego (- to 1.1.2-2)
  • Migration status for libnginx-mod-http-auth-spnego (- to 1.1.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnginx-mod-http-auth-spnego.html
    • autopkgtest for libnginx-mod-http-auth-spnego/1.1.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libnginx-mod-http-headers-more-filter (1:0.37-2 to 1:0.38-1)
  • Migration status for libnginx-mod-http-headers-more-filter (1:0.37-2 to 1:0.38-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnginx-mod-http-headers-more-filter.html
    • autopkgtest for libnginx-mod-http-headers-more-filter/1:0.38-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libnginx-mod-http-lua (1:0.10.27-3 to 1:0.10.28-1)
  • Migration status for libnginx-mod-http-lua (1:0.10.27-3 to 1:0.10.28-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: libnginx-mod-http-lua lua-resty-core (not considered)
    • Implicit dependency: libnginx-mod-http-lua lua-resty-core (not considered)
    • Invalidated by dependency
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnginx-mod-http-lua.html
    • autopkgtest for libnginx-mod-http-lua/1:0.10.28-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libnginx-mod-http-push-stream (- to 0.6.0+dfsg-2)
  • Migration status for libnginx-mod-http-push-stream (- to 0.6.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libnginx-mod-http-push-stream/0.6.0+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnginx-mod-http-push-stream.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libparsington-java (1.0.1-1.1 to 3.1.0-1)
  • Migration status for libparsington-java (1.0.1-1.1 to 3.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libparsington-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libreoffice (4:24.8.4-2 to 4:24.8.4-3)
  • Migration status for libreoffice (4:24.8.4-2 to 4:24.8.4-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libreoffice.html
    • autopkgtest for libreoffice/4:24.8.4-3: amd64: Test in progress (will not be considered a regression), arm64: Test in progress (will not be considered a regression), armel: Test in progress (will not be considered a regression), armhf: Test in progress (will not be considered a regression), i386: Test in progress (will not be considered a regression), ppc64el: Test in progress (will not be considered a regression), riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libsdl2 (2.30.12+dfsg-2 to 2.32.0+dfsg-1)
  • Migration status for libsdl2 (2.30.12+dfsg-2 to 2.32.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsdl2.html
    • autopkgtest for libsdl2/2.32.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libsdl3 (3.2.4+ds-1 to 3.2.4+ds-2)
  • Migration status for libsdl3 (3.2.4+ds-1 to 3.2.4+ds-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsdl3.html
    • autopkgtest for libsdl3/3.2.4+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• libtablelayout-java (20090826-4 to 20090826-5)
  • Migration status for libtablelayout-java (20090826-4 to 20090826-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtablelayout-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• libva (2.22.0-1 to 2.22.0-2)
  • Migration status for libva (2.22.0-1 to 2.22.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/libv/libva.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libzypp (17.35.19-1 to 17.36.0-1)
  • Migration status for libzypp (17.35.19-1 to 17.36.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
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libz/libzypp.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lmfit-py (1.2.2-4 to 1.3.2-2)
  • Migration status for lmfit-py (1.2.2-4 to 1.3.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): lmfit-py python-asteval
    • Depends: lmfit-py python-asteval
  • Additional info:
    • Updating lmfit-py will fix bugs in testing: #1095023
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lmfit-py.html
    • autopkgtest for lmfit-py/1.3.2-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• lomiri-addressbook-app (0.9.0-3 to 0.9.0-4)
  • Migration status for lomiri-addressbook-app (0.9.0-3 to 0.9.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-addressbook-app.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lomiri-calculator-app (4.0.2-2 to 4.0.2-3)
  • Migration status for lomiri-calculator-app (4.0.2-2 to 4.0.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-calculator-app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lomiri-calendar-app (1.1.2-3 to 1.1.2-4)
  • Migration status for lomiri-calendar-app (1.1.2-3 to 1.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-calendar-app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lomiri-schemas (0.1.7-1 to 0.1.7-3)
  • Migration status for lomiri-schemas (0.1.7-1 to 0.1.7-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/l/lomiri-schemas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lomiri-session (- to 0.3-9)
  • Migration status for lomiri-session (- to 0.3-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
    • Depends: lomiri-session lomiri
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-session.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• lomiri-tfamanager-app (1.7.3+dfsg-2 to 1.7.3+dfsg-4)
  • Migration status for lomiri-tfamanager-app (1.7.3+dfsg-2 to 1.7.3+dfsg-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/l/lomiri-tfamanager-app.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lua-resty-core (0.1.30-2 to 0.1.31-1)
  • Migration status for lua-resty-core (0.1.30-2 to 0.1.31-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: lua-resty-core libnginx-mod-http-lua
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-resty-core.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • autopkgtest for lua-resty-core/0.1.31-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxqt-build-tools-qt5 (- to 0.13.0-2)
  • Migration status for lxqt-build-tools-qt5 (- to 0.13.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/l/lxqt-build-tools-qt5.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• lynis (3.1.2-1 to 3.1.4-1)
  • Migration status for lynis (3.1.2-1 to 3.1.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating lynis will fix bugs in testing: #1094951
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lynis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• maildrop (- to 3.1.8-2)
  • Migration status for maildrop (- to 3.1.8-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
    • Build-Depends(-Arch): maildrop courier-authlib (not considered)
    • Depends: maildrop courier-authlib (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/maildrop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• mangohud (0.7.2-1 to 0.7.2-2)
  • Migration status for mangohud (0.7.2-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/m/mangohud.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• mdanalysis (2.7.0-5 to 2.8.0-1)
  • Migration status for mdanalysis (2.7.0-5 to 2.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mdanalysis would introduce bugs in testing: #1095739
    • missing build on armel
    • missing build on i386
    • missing build on riscv64
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for mdanalysis/2.8.0-1: amd64: Pass, arm64: Pass, armhf: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating mdanalysis will fix bugs in testing: #1094808
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdanalysis.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• meta-gnustep (9 to 10)
  • Migration status for meta-gnustep (9 to 10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
    • Too young, only 2 of 5 days old
    • Depends: meta-gnustep fisicalab.app
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meta-gnustep.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• nanoflann (1.6.3+ds-1 to 1.7.0+ds-1)
  • Migration status for nanoflann (1.6.3+ds-1 to 1.7.0+ds-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nanoflann.html
    • autopkgtest for nanoflann/1.7.0+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• node-mqtt (4.3.7-4 to 4.3.7-5)
  • Migration status for node-mqtt (4.3.7-4 to 4.3.7-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mqtt.html
    • autopkgtest for node-mqtt/4.3.7-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• node-sumchecker (- to 3.0.1-1)
  • Migration status for node-sumchecker (- 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 talau@users.sourceforge.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-sumchecker.html
    • autopkgtest for node-sumchecker/3.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• node-svgdotjs-svg.draggable.js (- to 3.0.4-2)
  • Migration status for node-svgdotjs-svg.draggable.js (- to 3.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-svgdotjs-svg.draggable.js/3.0.4-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-svgdotjs-svg.draggable.js.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• nodejs (20.18.2+dfsg-4 to 20.18.3+dfsg-1)
  • Migration status for nodejs (20.18.2+dfsg-4 to 20.18.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-ava/5.3.1+dfsg+~cs46.3.10-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for node-babel7/7.20.15+ds1+~cs214.269.168-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for node-chokidar/3.6.0-2: amd64: Pass, arm64: Failed (not a regression), armel: Pass, armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for node-clean-css/5.3.3+~5.6.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for node-jsdoc2/2.4.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for node-mqtt/4.3.7-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • autopkgtest for nodejs/20.18.3+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nodejs.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• oaknut (- to 1.2.2+git20240301.94c726c-1)
  • Migration status for oaknut (- to 1.2.2+git20240301.94c726c-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oaknut.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• octave (9.3.0-1 to 9.4.0-1)
  • Migration status for octave (9.3.0-1 to 9.4.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave.html
    • autopkgtest for octave/9.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility reference results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• openvpn (2.6.12-1 to 2.6.13-1)
  • Migration status for openvpn (2.6.12-1 to 2.6.13-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvpn.html
    • autopkgtest for openvpn/2.6.13-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• osmocom-dahdi-linux (0.0~git20241003.b2ea348-1 to 0.0~git20241003.b2ea348-2)
  • Migration status for osmocom-dahdi-linux (0.0~git20241003.b2ea348-1 to 0.0~git20241003.b2ea348-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating osmocom-dahdi-linux will fix bugs in testing: #1095643
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/osmocom-dahdi-linux.html
    • autopkgtest for osmocom-dahdi-linux/0.0~git20241003.b2ea348-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pagure (5.14.1+dfsg-1 to 5.14.1+dfsg-7)
  • Migration status for pagure (5.14.1+dfsg-1 to 5.14.1+dfsg-7): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pagure.html
    • autopkgtest for pagure/5.14.1+dfsg-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pam (1.7.0-2 to 1.7.0-3)
  • Migration status for pam (1.7.0-2 to 1.7.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for glome/0.1-3: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for mariadb/1:11.4.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pam/1.7.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for postgresql-17/17.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for slurm-wlm/24.11.0-2: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for sudo/1.9.16p2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating pam will fix bugs in testing: #1095194
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pam.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2 days old (needed 2 days)
• pam-session-timelimit (0.7-3 to 0.7-4)
  • Migration status for pam-session-timelimit (0.7-3 to 0.7-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/p/pam-session-timelimit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• papilo (- to 2.4.1+ds-1)
  • Migration status for papilo (- to 2.4.1+ds-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/papilo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• patool (2.0.0-2 to 3.1.0-2)
  • Migration status for patool (2.0.0-2 to 3.1.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/patool.html
    • autopkgtest for patool/3.1.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pd-binfile (- to 0.1-1)
  • Migration status for pd-binfile (- 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/pd-binfile.html
    • autopkgtest for pd-binfile/0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pd-midifile (- to 0.4-1)
  • Migration status for pd-midifile (- to 0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pd-midifile/0.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pd-midifile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pdns-recursor (5.1.3-1 to 5.1.3-2)
  • Migration status for pdns-recursor (5.1.3-1 to 5.1.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): pdns-recursor rust-cxx (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdns-recursor.html
    • autopkgtest for pdns-recursor/5.1.3-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pg-wait-sampling (1.1.6-2 to 1.1.7-1)
  • Migration status for pg-wait-sampling (1.1.6-2 to 1.1.7-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-wait-sampling.html
    • autopkgtest for pg-wait-sampling/1.1.7-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pgrouting (3.7.2-2 to 3.7.3-1)
  • Migration status for pgrouting (3.7.2-2 to 3.7.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgrouting.html
    • autopkgtest for pgrouting/3.7.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• php-laravel-framework (- to 10.48.25+dfsg-2)
  • Migration status for php-laravel-framework (- to 10.48.25+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
    • Depends: php-laravel-framework php-laravel-prompts
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-laravel-framework.html
    • autopkgtest for php-laravel-framework/10.48.25+dfsg-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• php-laravel-lumen-framework (- to 10.0.4-1)
  • Migration status for php-laravel-lumen-framework (- to 10.0.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-laravel-lumen-framework php-laravel-framework (not considered)
    • Depends: php-laravel-lumen-framework php-laravel-framework (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-laravel-lumen-framework.html
    • autopkgtest for php-laravel-lumen-framework/10.0.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• phrog (- to 0.44.1-1)
  • Migration status for phrog (- to 0.44.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
    • Build-Depends(-Arch): phrog rust-libphosh
    • Depends: phrog phosh
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phrog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• plasma-gamemode (0.0~git20220224.3adea2bd-2 to 0.0~git20240315.4d60358-1)
  • Migration status for plasma-gamemode (0.0~git20220224.3adea2bd-2 to 0.0~git20240315.4d60358-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/plasma-gamemode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• plpgsql-check (2.7.14-1 to 2.7.15-1)
  • Migration status for plpgsql-check (2.7.14-1 to 2.7.15-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plpgsql-check.html
    • autopkgtest for plpgsql-check/2.7.15-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ply-probe (- to 2.3.0.25.gec815ed-1)
  • Migration status for ply-probe (- to 2.3.0.25.gec815ed-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/ply-probe.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• prometheus (2.45.6+ds-9 to 2.53.1+ds-2)
  • Migration status for prometheus (2.45.6+ds-9 to 2.53.1+ds-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for prometheus/2.53.1+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
    • Built-Using: prometheus golang-1.23
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• prs (- to 0.5.2+dfsg-2)
  • Migration status for prs (- to 0.5.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • prs/armel has unsatisfiable dependency
    • prs/armhf has unsatisfiable dependency
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prs.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pycorrfit (1.1.7+nopack-1 to 1.1.7+nopack-2)
  • Migration status for pycorrfit (1.1.7+nopack-1 to 1.1.7+nopack-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pycorrfit would introduce bugs in testing: #1095798
    • missing build on mips64el
  • Additional info:
    • Updating pycorrfit will fix bugs in testing: #1095281
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycorrfit.html
    • autopkgtest for pycorrfit/1.1.7+nopack-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• pyeconet (0.1.26-1 to 0.1.27-1)
  • Migration status for pyeconet (0.1.26-1 to 0.1.27-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/pyeconet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pyodc (1.4.1-1 to 1.5.0-1)
  • Migration status for pyodc (1.4.1-1 to 1.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyodc.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pyspread (2.3.1-1 to 2.3.1-2)
  • Migration status for pyspread (2.3.1-1 to 2.3.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyspread.html
    • autopkgtest for pyspread/2.3.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-asteval (0.9.31-1 to 1.0.6-2)
  • Migration status for python-asteval (0.9.31-1 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-asteval.html
    • autopkgtest for python-asteval/1.0.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-azure (20250114+git-1 to 20250211+git-1)
  • Migration status for python-azure (20250114+git-1 to 20250211+git-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-azure.html
    • autopkgtest for python-azure/20250211+git-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-datapoint (- to 0.9.9-2)
  • Migration status for python-datapoint (- to 0.9.9-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: python-datapoint appdirs (not considered)
    • Depends: python-datapoint appdirs (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-datapoint.html
    • autopkgtest for python-datapoint/0.9.9-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-dataset (- to 1.6.2-3)
  • Migration status for python-dataset (- to 1.6.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/p/python-dataset.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-django-guid (3.5.0-1 to 3.5.1-1)
  • Migration status for python-django-guid (3.5.0-1 to 3.5.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-guid.html
    • autopkgtest for python-django-guid/3.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-django-timescaledb (- to 0.2.13-3)
  • Migration status for python-django-timescaledb (- to 0.2.13-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-django-timescaledb/0.2.13-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-timescaledb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-fake-useragent (- to 2.0.3-2)
  • Migration status for python-fake-useragent (- to 2.0.3-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fake-useragent.html
    • autopkgtest for python-fake-useragent/2.0.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-odf (1.4.2-3 to 1.4.2-4)
  • Migration status for python-odf (1.4.2-3 to 1.4.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pandas/2.2.3+dfsg-8: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for python-odf/1.4.2-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-odf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• python-reportlab (4.2.5-1 to 4.3.0-1)
  • Migration status for python-reportlab (4.2.5-1 to 4.3.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-reportlab.html
    • autopkgtest for python-reportlab/4.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-semantic-release (9.17.0-1 to 9.19.0-1)
  • Migration status for python-semantic-release (9.17.0-1 to 9.19.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-semantic-release.html
    • autopkgtest for python-semantic-release/9.19.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• qtcontacts-sqlite (0.3.20-1 to 0.3.20-2)
  • Migration status for qtcontacts-sqlite (0.3.20-1 to 0.3.20-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 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/q/qtcontacts-sqlite.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-s7 (- to 0.2.0-1)
  • Migration status for r-cran-s7 (- to 0.2.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-s7.html
    • autopkgtest for r-cran-s7/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rabbitvcs (0.19-3 to 0.19-4)
  • Migration status for rabbitvcs (0.19-3 to 0.19-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/r/rabbitvcs.html
    • autopkgtest for rabbitvcs/0.19-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• recommonmark (0.7.1+ds-7 to 0.7.1+ds-8)
  • Migration status for recommonmark (0.7.1+ds-7 to 0.7.1+ds-8): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/recommonmark.html
    • autopkgtest for recommonmark/0.7.1+ds-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ruby-actionpack-xml-parser (2.0.1-4 to 2.0.1-5)
  • Migration status for ruby-actionpack-xml-parser (2.0.1-4 to 2.0.1-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-actionpack-xml-parser.html
    • autopkgtest for ruby-actionpack-xml-parser/2.0.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ruby-minitest (5.25.4-1 to 5.25.4-2)
  • Migration status for ruby-minitest (5.25.4-1 to 5.25.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-minitest.html
    • autopkgtest for ruby-minitest/5.25.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ruby-roadie-rails (3.0.0-1 to 3.3.0-1)
  • Migration status for ruby-roadie-rails (3.0.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating ruby-roadie-rails will fix bugs in testing: #1093928
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-roadie-rails.html
    • autopkgtest for ruby-roadie-rails/3.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ruby-thor (1.3.2-1 to 1.3.2-2)
  • Migration status for ruby-thor (1.3.2-1 to 1.3.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-thor.html
    • autopkgtest for ruby-thor/1.3.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-anyhow (1.0.86-1 to 1.0.95-1)
  • Migration status for rust-anyhow (1.0.86-1 to 1.0.95-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-anyhow.html
    • autopkgtest for rust-anyhow/1.0.95-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-bitstream-io (2.5.0-1 to 2.6.0-1)
  • Migration status for rust-bitstream-io (2.5.0-1 to 2.6.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bitstream-io.html
    • autopkgtest for rust-bitstream-io/2.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-bitvec-helpers (3.1.5-1 to 3.1.6-1)
  • Migration status for rust-bitvec-helpers (3.1.5-1 to 3.1.6-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): rust-bitvec-helpers rust-anyhow
    • Depends: rust-bitvec-helpers rust-anyhow
    • Depends: rust-bitvec-helpers rust-bitstream-io
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bitvec-helpers.html
    • autopkgtest for rust-bitvec-helpers/3.1.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-libphosh (0.0.5-1 to 0.0.6-1)
  • Migration status for rust-libphosh (0.0.5-1 to 0.0.6-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-libphosh rust-libphosh-sys (not considered)
    • Depends: rust-libphosh rust-libphosh-sys (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libphosh.html
    • autopkgtest for rust-libphosh/0.0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-libphosh-sys (0.0.5-1 to 0.0.6-1)
  • Migration status for rust-libphosh-sys (0.0.5-1 to 0.0.6-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-libphosh-sys phosh (not considered)
    • Depends: rust-libphosh-sys phosh (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Implicit dependency: rust-libphosh-sys rust-libphosh
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libphosh-sys.html
    • autopkgtest for rust-libphosh-sys/0.0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-mdns-sd (0.12.0-1 to 0.13.2-1)
  • Migration status for rust-mdns-sd (0.12.0-1 to 0.13.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/r/rust-mdns-sd.html
    • autopkgtest for rust-mdns-sd/0.13.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-sanitize-filename (0.5.0-1 to 0.6.0-1)
  • Migration status for rust-sanitize-filename (0.5.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sanitize-filename.html
    • autopkgtest for rust-sanitize-filename/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• sdl2-compat (2.30.54+ds-1 to 2.32.50+ds-1)
  • Migration status for sdl2-compat (2.30.54+ds-1 to 2.32.50+ds-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdl2-compat.html
    • autopkgtest for sdl2-compat/2.32.50+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• shadowsocks-libev (- to 3.3.5+ds-12)
  • Migration status for shadowsocks-libev (- to 3.3.5+ds-12): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shadowsocks-libev.html
    • autopkgtest for shadowsocks-libev/3.3.5+ds-12: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• snd (25.0-1 to 25.1-1)
  • Migration status for snd (25.0-1 to 25.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snd.html
    • autopkgtest for snd/25.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• squid (6.12-1 to 6.13-1)
  • Migration status for squid (6.12-1 to 6.13-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squid.html
    • autopkgtest for squid/6.13-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • Required age is not allowed to drop below 2 days
    • 2 days old (needed 2 days)
• stimfit (- to 0.16.6-1)
  • Migration status for stimfit (- to 0.16.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/s/stimfit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• timescaledb (2.18.0+dfsg-1 to 2.18.1+dfsg-1)
  • Migration status for timescaledb (2.18.0+dfsg-1 to 2.18.1+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/timescaledb.html
    • autopkgtest for timescaledb/2.18.1+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• tp-el (0.6-2 to 0.7-1)
  • Migration status for tp-el (0.6-2 to 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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tp-el.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• uvloop (0.21.0+ds1-1 to 0.21.0+ds1-2)
  • Migration status for uvloop (0.21.0+ds1-1 to 0.21.0+ds1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating uvloop will fix bugs in testing: #1093363
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uvloop.html
    • autopkgtest for uvloop/0.21.0+ds1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• vagrant-cachier (1.2.1-3.1 to 1.2.1+git20221205.7e885eb-1)
  • Migration status for vagrant-cachier (1.2.1-3.1 to 1.2.1+git20221205.7e885eb-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vagrant-cachier.html
    • autopkgtest for vagrant-cachier/1.2.1+git20221205.7e885eb-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• vdr-plugin-xineliboutput (2.2.0+git20211212-2.2 to 2.3.0-1)
  • Migration status for vdr-plugin-xineliboutput (2.2.0+git20211212-2.2 to 2.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdr-plugin-xineliboutput.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• video-downloader (0.12.20-1 to 0.12.22-1)
  • Migration status for video-downloader (0.12.20-1 to 0.12.22-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/v/video-downloader.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• vim-minimap (- to 0.0+git20250126-1)
  • Migration status for vim-minimap (- to 0.0+git20250126-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: vim-minimap code-minimap
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-minimap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• vuos (- to 0.9.0-1)
  • Migration status for vuos (- 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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vuos.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• waycheck (- to 1.5.0-1)
  • Migration status for waycheck (- to 1.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/waycheck.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• wxglade (1:1.1.0+repack-1 to 1:1.1.1+repack-1)
  • Migration status for wxglade (1:1.1.0+repack-1 to 1:1.1.1+repack-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/w/wxglade.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• xar (- to 1.8.0.498-2)
  • Migration status for xar (- to 1.8.0.498-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xar.html
    • autopkgtest for xar/1.8.0.498-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• xraylib (- to 4.0.0+dfsg1-8)
  • Migration status for xraylib (- to 4.0.0+dfsg1-8): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xraylib.html
    • autopkgtest for xraylib/4.0.0+dfsg1-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• xserver-xorg-video-nouveau (1:1.0.17-3 to 1:1.0.18-1)
  • Migration status for xserver-xorg-video-nouveau (1:1.0.17-3 to 1:1.0.18-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-nouveau.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• xterm (396-1 to 397-1)
  • Migration status for xterm (396-1 to 397-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xterm.html
    • autopkgtest for xterm/397-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• yaz (5.34.2-1 to 5.34.3-1)
  • Migration status for yaz (5.34.2-1 to 5.34.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/y/yaz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• yt (- to 4.4.0-2)
  • Migration status for yt (- to 4.4.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yt.html
    • autopkgtest for yt/4.4.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• accerciser (3.44.1-1 to 3.46.2-1)
  • Migration status for accerciser (3.44.1-1 to 3.46.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/a/accerciser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• agenda.app (0.46-4 to 0.47-1)
  • Migration status for agenda.app (0.46-4 to 0.47-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: agenda.app gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): agenda.app addresses-for-gnustep
    • Build-Depends(-Arch): agenda.app gnustep-gui (not considered)
  • Additional info:
    • Updating agenda.app will fix bugs in testing: #1094007
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/agenda.app.html
    • autopkgtest for agenda.app/0.47-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• angelfish (23.04.3-2 to 24.12.2-1)
  • Migration status for angelfish (23.04.3-2 to 24.12.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating angelfish would introduce bugs in testing: #1095584
    • angelfish unsatisfiable Build-Depends(-Arch) on mips64el: qt6-webengine-dev
    • angelfish unsatisfiable Build-Depends(-Arch) on mips64el: qt6-webengine-private-dev
    • missing build on mips64el
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/angelfish.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• bash-unit (- to 2.3.1-1)
  • Migration status for bash-unit (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by soren@stoutner.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bash-unit.html
    • autopkgtest for bash-unit/2.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• bcmatroska2 (5.2.0-5 to 5.3.101-1)
  • Migration status for bcmatroska2 (5.2.0-5 to 5.3.101-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libbcmatroska2-5/5.3.101-1/amd64 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/amd64 uninstallable
    • migrating libbcmatroska2-5/5.3.101-1/arm64 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/arm64 uninstallable
    • migrating libbcmatroska2-5/5.3.101-1/armel to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/armel uninstallable
    • migrating libbcmatroska2-5/5.3.101-1/armhf to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/armhf uninstallable
    • migrating libbcmatroska2-5/5.3.101-1/i386 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/i386 uninstallable
    • migrating libbcmatroska2-5/5.3.101-1/mips64el to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/mips64el uninstallable
    • migrating libbcmatroska2-5/5.3.101-1/ppc64el to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/ppc64el uninstallable
    • migrating libbcmatroska2-5/5.3.101-1/riscv64 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/riscv64 uninstallable
    • migrating libbcmatroska2-5/5.3.101-1/s390x to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/s390x uninstallable
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bcmatroska2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ben (1.8 to 1.9)
  • Migration status for ben (1.8 to 1.9): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/ben.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• bpftune (- to 0.0~git20241205.2a8d043-1)
  • Migration status for bpftune (- to 0.0~git20241205.2a8d043-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bpftune.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• caio (- to 0.9.17-1)
  • Migration status for caio (- to 0.9.17-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 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/caio.html
    • autopkgtest for caio/0.9.17-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• calligra (- to 1:24.12.2+dfsg-2)
  • Migration status for calligra (- to 1:24.12.2+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): calligra okular
    • Depends: calligra okular
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calligra.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• cambalache (- to 0.94.1-1)
  • Migration status for cambalache (- to 0.94.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cambalache would introduce bugs in testing: #1095742
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cambalache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cfgv (3.4.0-2 to 3.4.0-3)
  • Migration status for cfgv (3.4.0-2 to 3.4.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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cfgv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• clc-intercal (- to 1:1.00-3)
  • Migration status for clc-intercal (- to 1:1.00-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 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clc-intercal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• cloc (2.02-1 to 2.04-1)
  • Migration status for cloc (2.02-1 to 2.04-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/cloc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• commons-dbcp2 (2.12.0-1 to 2.13.0-1)
  • Migration status for commons-dbcp2 (2.12.0-1 to 2.13.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/c/commons-dbcp2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• creduce (- to 2.11.0~20240909-2)
  • Migration status for creduce (- to 2.11.0~20240909-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/c/creduce.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cryptacular (1.2.6-1 to 1.2.7-1)
  • Migration status for cryptacular (1.2.6-1 to 1.2.7-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/cryptacular.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cryptopant (- to 1.3.1-2)
  • Migration status for cryptopant (- to 1.3.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/c/cryptopant.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• csound-manual (1:6.18.0+dfsg0-1 to 1:7.00.0+dfsg-1)
  • Migration status for csound-manual (1:6.18.0+dfsg0-1 to 1:7.00.0+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/csound-manual.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• cubeb (0.0~git20250127.2816b5a+ds-1 to 0.0~git20250203.224b7cb+ds-1)
  • Migration status for cubeb (0.0~git20250127.2816b5a+ds-1 to 0.0~git20250203.224b7cb+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 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cubeb.html
    • autopkgtest for cubeb/0.0~git20250203.224b7cb+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• deepdish (0.3.7-3 to 0.3.7-4)
  • Migration status for deepdish (0.3.7-3 to 0.3.7-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:
    • Updating deepdish will fix bugs in testing: #1095339
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepdish.html
    • autopkgtest for deepdish/0.3.7-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• dnsvi (1.4 to 1.5)
  • Migration status for dnsvi (1.4 to 1.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:
    • Updating dnsvi will fix bugs in testing: #1094943
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnsvi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• elixir-nimble-parsec (1.4.0-1 to 1.4.2-1)
  • Migration status for elixir-nimble-parsec (1.4.0-1 to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • elixir-nimble-parsec unsatisfiable Build-Depends(-Arch) on mips64el: elixir (>= 1.18.1.dfsg-1.1~)
    • missing build on mips64el
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): elixir-nimble-parsec elixir-lang (not considered)
  • Additional info:
    • Updating elixir-nimble-parsec will fix bugs in testing: #1092584
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elixir-nimble-parsec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• enum (1.1-1 to 1.1-2)
  • Migration status for enum (1.1-1 to 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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/enum.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• eos-downloader (0.10.3-1 to 0.12.0-1)
  • Migration status for eos-downloader (0.10.3-1 to 0.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 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• erlang (1:25.3.2.12+dfsg-3 to 1:27.2.2+dfsg-1)
  • Migration status for erlang (1:25.3.2.12+dfsg-3 to 1:27.2.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rebar3/3.19.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • missing build on mips64el
    • Too young, only 3 of 5 days old
    • Build-Depends-Indep: erlang elixir-ex-doc (not considered)
  • Additional info:
    • Updating erlang will fix bugs in testing: #1092439
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• erofs-utils (1.8.4-2 to 1.8.5-1)
  • Migration status for erofs-utils (1.8.4-2 to 1.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erofs-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• fdb (5.14.0-1 to 5.15.1-1)
  • Migration status for fdb (5.14.0-1 to 5.15.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fdb.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• file-roller (44.4-1 to 44.5-1)
  • Migration status for file-roller (44.4-1 to 44.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/file-roller.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• flamp (2.2.12-1 to 2.2.14-1)
  • Migration status for flamp (2.2.12-1 to 2.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flamp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• free42-nologo (3.1.12+ds-1 to 3.2.1+ds-1)
  • Migration status for free42-nologo (3.1.12+ds-1 to 3.2.1+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/f/free42-nologo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• fsearch (0.2.3-3 to 0.2.3-4)
  • Migration status for fsearch (0.2.3-3 to 0.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fsearch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• ftnchek (- to 3.3.1-7)
  • Migration status for ftnchek (- to 3.3.1-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/ftnchek.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• g10k (0.9.9-1 to 0.9.9-2)
  • Migration status for g10k (0.9.9-1 to 0.9.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating g10k would introduce bugs in testing: #1095672
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on riscv64
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for g10k/0.9.9-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
    • Built-Using: g10k golang-1.23
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/g10k.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gcr4 (4.3.90.3-1 to 4.3.91-1)
  • Migration status for gcr4 (4.3.90.3-1 to 4.3.91-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/gcr4.html
    • autopkgtest for gcr4/4.3.91-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gegl (1:0.4.52-1 to 1:0.4.54-1)
  • Migration status for gegl (1:0.4.52-1 to 1:0.4.54-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/gegl.html
    • autopkgtest for gegl/1:0.4.54-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ghex (46.1-1 to 46.2-1)
  • Migration status for ghex (46.1-1 to 46.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/ghex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gimp (3.0.0~RC2-1 to 3.0.0~RC3-1)
  • Migration status for gimp (3.0.0~RC2-1 to 3.0.0~RC3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): gimp gegl
    • Depends: gimp gegl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gimp.html
    • autopkgtest for gimp/3.0.0~RC3-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnomad2 (2.9.6-10 to 2.9.6-11)
  • Migration status for gnomad2 (2.9.6-10 to 2.9.6-11): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnomad2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-commander (1.18.1-1 to 1.18.2-1)
  • Migration status for gnome-commander (1.18.1-1 to 1.18.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-commander.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-music (47.1-1 to 48~beta-1)
  • Migration status for gnome-music (47.1-1 to 48~beta-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-music.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnumail (1.4.0-2 to 1.4.0-3)
  • Migration status for gnumail (1.4.0-2 to 1.4.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
    • Build-Depends(-Arch): gnumail addresses-for-gnustep
    • Depends: gnumail gnustep-make (not considered)
  • Additional info:
    • Updating gnumail will fix bugs in testing: #1094008
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnumail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnutls28 (3.8.8-2 to 3.8.9-2)
  • Migration status for gnutls28 (3.8.8-2 to 3.8.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for curl/8.12.0+git20250209.89ed161+ds-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for gnutls28/3.8.9-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnutls28.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• golang-github-jstemmer-go-junit-report (- to 2.1.0-1)
  • Migration status for golang-github-jstemmer-go-junit-report (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by andrewsh
    • Not built on buildd: arch all binaries uploaded by andrewsh, a new source-only upload is needed to allow migration
    • Built-Using: golang-github-jstemmer-go-junit-report golang-1.23
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jstemmer-go-junit-report.html
    • autopkgtest for golang-github-jstemmer-go-junit-report/2.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• golang-github-lifenjoiner-dhcpdns (- to 0.0.6-3)
  • Migration status for golang-github-lifenjoiner-dhcpdns (- to 0.0.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by eric, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-lifenjoiner-dhcpdns.html
    • autopkgtest for golang-github-lifenjoiner-dhcpdns/0.0.6-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• golang-k8s-component-helpers (- to 0.31.4-1)
  • Migration status for golang-k8s-component-helpers (- to 0.31.4-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/g/golang-k8s-component-helpers.html
    • autopkgtest for golang-k8s-component-helpers/0.31.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• golang-k8s-kms (- to 0.31.4-1)
  • Migration status for golang-k8s-kms (- to 0.31.4-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/g/golang-k8s-kms.html
    • autopkgtest for golang-k8s-kms/0.31.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• grml-debootstrap (0.113 to 0.114)
  • Migration status for grml-debootstrap (0.113 to 0.114): 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/grml-debootstrap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• grub (0.97-83 to 0.97-84)
  • Migration status for grub (0.97-83 to 0.97-84): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/grub.html
    • Too young, only 3 of 5 days old
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
• gthumb (3:3.12.6-2 to 3:3.12.7-1)
  • Migration status for gthumb (3:3.12.6-2 to 3:3.12.7-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/gthumb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• harec (- to 0.24.2-1)
  • Migration status for harec (- to 0.24.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/h/harec.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• hexagonrpc (- to 0.3.2-1)
  • Migration status for hexagonrpc (- to 0.3.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hexagonrpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• hsqldb (2.7.2-1 to 2.7.4-1)
  • Migration status for hsqldb (2.7.2-1 to 2.7.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hsqldb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• iec16022 (0.2.7-1 to 0.3.1-1)
  • Migration status for iec16022 (0.2.7-1 to 0.3.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iec16022.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• iredis (1.15.0-3 to 1.15.0-4)
  • Migration status for iredis (1.15.0-3 to 1.15.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iredis.html
    • autopkgtest for iredis/1.15.0-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• jacktrip (2.5.0+ds-1 to 2.5.1+ds-1)
  • Migration status for jacktrip (2.5.0+ds-1 to 2.5.1+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/j/jacktrip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• jakarta-authentication-api (- to 3.0.0-1)
  • Migration status for jakarta-authentication-api (- 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 ebourg@apache.org, a new source-only upload is needed to allow migration
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jakarta-authentication-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• jakarta-transaction-api (- to 2.0.1-1)
  • Migration status for jakarta-transaction-api (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): jakarta-transaction-api jakarta-cdi-api (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jakarta-transaction-api.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• jaraco.stream (- to 3.0.4-1)
  • Migration status for jaraco.stream (- to 3.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for jaraco.stream/3.0.4-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not built on buildd: arch all binaries uploaded by ben@benfinney.id.au, a new source-only upload is needed to allow migration
    • Too young, only 3 of 5 days old
    • Build-Depends-Indep: jaraco.stream ruff (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jaraco.stream.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• jboss-modules (2.1.2-1 to 2.1.6-1)
  • Migration status for jboss-modules (2.1.2-1 to 2.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jboss-modules.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• juce (- to 8.0.6+ds-2)
  • Migration status for juce (- to 8.0.6+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/juce.html
    • autopkgtest for juce/8.0.6+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• julius (- to 1.7.0+dfsg-1)
  • Migration status for julius (- to 1.7.0+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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• kdenlive (24.12.1-1 to 24.12.2-1)
  • Migration status for kdenlive (24.12.1-1 to 24.12.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:
    • Updating kdenlive will fix bugs in testing: #1094217
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdenlive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kile (4:2.9.94-0.1 to 4:2.9.94-1)
  • Migration status for kile (4:2.9.94-0.1 to 4:2.9.94-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): kile okular
    • Depends: kile okular
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kiwi (- to 10.2.10-1)
  • Migration status for kiwi (- to 10.2.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kiwi.html
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libdng (- to 0.2.1-1)
  • Migration status for libdng (- to 0.2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libfm-qt5 (- to 1.4.0-4)
  • Migration status for libfm-qt5 (- to 1.4.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by ajqlee
    • Not built on buildd: arch all binaries uploaded by ajqlee, a new source-only upload is needed to allow migration
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): libfm-qt5 lxqt-build-tools-qt5
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libfm-qt5.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libircclient (1.9-1 to 1.10-1)
  • Migration status for libircclient (1.9-1 to 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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libircclient.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libjsonp2-java (2.1.2-1 to 2.1.3-1)
  • Migration status for libjsonp2-java (2.1.2-1 to 2.1.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjsonp2-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libjsr305-java (0.1~+svn49-11 to 0.1~+svn49-12)
  • Migration status for libjsr305-java (0.1~+svn49-11 to 0.1~+svn49-12): 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/libj/libjsr305-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libjuniversalchardet-java (2.4.0-3 to 2.5.0-1)
  • Migration status for libjuniversalchardet-java (2.4.0-3 to 2.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjuniversalchardet-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libpgjava (42.7.3-2 to 42.7.5-1)
  • Migration status for libpgjava (42.7.3-2 to 42.7.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Built-Using: libpgjava libscram-java (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpgjava.html
    • autopkgtest for libpgjava/42.7.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• libscram-java (2.1-1 to 3.1-1)
  • Migration status for libscram-java (2.1-1 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 3 of 5 days old
    • Build-Depends-Indep: libscram-java libstringprep-java
    • Depends: libscram-java libstringprep-java
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libscram-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libsfdo (- to 0.1.3-1)
  • Migration status for libsfdo (- to 0.1.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsfdo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libstringprep-java (1.1-3 to 2.1-1)
  • Migration status for libstringprep-java (1.1-3 to 2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libstringprep-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libthumbor (2.0.2-2 to 2.0.2-3)
  • Migration status for libthumbor (2.0.2-2 to 2.0.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libthumbor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• lilv (0.24.24-2 to 0.24.26-1)
  • Migration status for lilv (0.24.24-2 to 0.24.26-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: lilv zix
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lilv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• linux-signed-amd64 (6.12.12+1 to 6.12.13+1)
  • Migration status for linux-signed-amd64 (6.12.12+1 to 6.12.13+1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): linux-signed-amd64 linux (not considered)
    • Built-Using: linux-signed-amd64 linux (not considered)
    • Depends: linux-signed-amd64 linux (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-signed-amd64.html
    • Reproducible on amd64 - info ♻
• linux-signed-arm64 (6.12.12+1 to 6.12.13+1)
  • Migration status for linux-signed-arm64 (6.12.12+1 to 6.12.13+1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): linux-signed-arm64 linux (not considered)
    • Built-Using: linux-signed-arm64 linux (not considered)
    • Depends: linux-signed-arm64 linux (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• litecli (1.14.4-1 to 1.14.4-2)
  • Migration status for litecli (1.14.4-1 to 1.14.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/litecli.html
    • autopkgtest for litecli/1.14.4-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• log2ram (- to 1.7.2+ds-1)
  • Migration status for log2ram (- to 1.7.2+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 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/log2ram.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lua-augeas (0.1.1-3 to 0.1.1-4)
  • Migration status for lua-augeas (0.1.1-3 to 0.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/l/lua-augeas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• macaulay2 (1.24.11+ds-3 to 1.24.11+ds-5)
  • Migration status for macaulay2 (1.24.11+ds-3 to 1.24.11+ds-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:
    • Updating macaulay2 will fix bugs in testing: #1095290
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/macaulay2.html
    • autopkgtest for macaulay2/1.24.11+ds-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Failed (not a regression), ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• mame (0.270+dfsg.1-1 to 0.274+dfsg.1-2)
  • Migration status for mame (0.270+dfsg.1-1 to 0.274+dfsg.1-2): 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
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating mame will fix bugs in testing: #1092719
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mame.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• metkit (1.12.0-1 to 1.12.1-1)
  • Migration status for metkit (1.12.0-1 to 1.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 3 of 5 days old
    • Depends: metkit odc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/metkit.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• mimic (- to 0.6.3+ds-1)
  • Migration status for mimic (- to 0.6.3+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mimic would introduce bugs in testing: #1095728
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/m/mimic.html
    • Too young, only 3 of 5 days old
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• msktutil (1.2.1-2 to 1.2.2-1)
  • Migration status for msktutil (1.2.1-2 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/m/msktutil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mycli (1.29.2-2 to 1.29.2-4)
  • Migration status for mycli (1.29.2-2 to 1.29.2-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/mycli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• node-gyp (10.3.0+~5.0.0-1 to 11.1.0+~5.0.0-1)
  • Migration status for node-gyp (10.3.0+~5.0.0-1 to 11.1.0+~5.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-gyp/11.1.0+~5.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for npm/9.2.0~ds1-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-gyp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• nvidia-graphics-drivers-tesla (525.147.05-12 to 525.147.05-13)
  • Migration status for nvidia-graphics-drivers-tesla (525.147.05-12 to 525.147.05-13): 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 nvidia-graphics-drivers-tesla will fix bugs in testing: #1090254
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-tesla/525.147.05-13: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
• objenesis (3.3-3 to 3.4-1)
  • Migration status for objenesis (3.3-3 to 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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/objenesis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ocaml-websocket (- to 2.17-1)
  • Migration status for ocaml-websocket (- to 2.17-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/o/ocaml-websocket.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ocaml-zarith-stubs-js (- to 0.17.0-1)
  • Migration status for ocaml-zarith-stubs-js (- to 0.17.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-zarith-stubs-js.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• openjdk-25 (25~8ea-1 to 25~9ea-1)
  • Migration status for openjdk-25 (25~8ea-1 to 25~9ea-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by doko
    • Not built on buildd: arch all binaries uploaded by doko, a new source-only upload is needed to allow migration
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for openjdk-25/25~9ea-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-25.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• packetq (- to 1.7.3+dfsg-2)
  • Migration status for packetq (- to 1.7.3+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/packetq.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pdfposter (0.8.1-3 to 0.8.1-4)
  • Migration status for pdfposter (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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdfposter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pgcli (4.1.0-3 to 4.1.0-4)
  • Migration status for pgcli (4.1.0-3 to 4.1.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgcli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• phosh (0.44.1-1 to 0.45~rc1-2)
  • Migration status for phosh (0.44.1-1 to 0.45~rc1-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
    • Implicit dependency: phosh rust-libphosh-sys
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phosh.html
    • autopkgtest for phosh/0.45~rc1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• phosh-mobile-settings (0.44.0-1 to 0.45~rc1-1)
  • Migration status for phosh-mobile-settings (0.44.0-1 to 0.45~rc1-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/phosh-mobile-settings.html
    • autopkgtest for phosh-mobile-settings/0.45~rc1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• php-laravel-prompts (- to 0.1.25-1)
  • Migration status for php-laravel-prompts (- to 0.1.25-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: php-laravel-prompts php-laravel-framework
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-laravel-prompts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• php-ramsey-uuid (4.7.4-2 to 4.7.6-1)
  • Migration status for php-ramsey-uuid (4.7.4-2 to 4.7.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-ramsey-uuid.html
    • autopkgtest for php-ramsey-uuid/4.7.6-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• picard (2.12.3-1 to 2.13.2-1)
  • Migration status for picard (2.12.3-1 to 2.13.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/p/picard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• polybar (3.7.1-1 to 3.7.2-1)
  • Migration status for polybar (3.7.1-1 to 3.7.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polybar.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• pre-commit (4.1.0-1 to 4.1.0-2)
  • Migration status for pre-commit (4.1.0-1 to 4.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/p/pre-commit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• pre-commit-hooks (5.0.0+dfsg-1 to 5.0.0+dfsg-2)
  • Migration status for pre-commit-hooks (5.0.0+dfsg-1 to 5.0.0+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pre-commit-hooks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ptpython (3.0.29-1 to 3.0.29-2)
  • Migration status for ptpython (3.0.29-1 to 3.0.29-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/p/ptpython.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• puppet-module-puppetlabs-java (- to 11.1.0-2)
  • Migration status for puppet-module-puppetlabs-java (- to 11.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
    • Depends: puppet-module-puppetlabs-java puppet-module-voxpupuli-archive (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• puppet-module-puppetlabs-java-ks (- to 5.1.1-2)
  • Migration status for puppet-module-puppetlabs-java-ks (- to 5.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/puppet-module-puppetlabs-java-ks.html
    • Too young, only 3 of 5 days old
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• puppet-module-voxpupuli-archive (- to 7.1.0-2)
  • Migration status for puppet-module-voxpupuli-archive (- to 7.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/puppet-module-voxpupuli-archive.html
    • Too young, only 3 of 5 days old
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• puppet-module-voxpupuli-elastic-stack (- to 9.0.0-2)
  • Migration status for puppet-module-voxpupuli-elastic-stack (- to 9.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/puppet-module-voxpupuli-elastic-stack.html
    • Too young, only 3 of 5 days old
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• puppet-module-voxpupuli-elasticsearch (- to 9.0.0-2)
  • Migration status for puppet-module-voxpupuli-elasticsearch (- to 9.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Depends: puppet-module-voxpupuli-elasticsearch puppet-module-puppetlabs-java
    • Depends: puppet-module-voxpupuli-elasticsearch puppet-module-puppetlabs-java-ks (not considered)
    • Depends: puppet-module-voxpupuli-elasticsearch puppet-module-voxpupuli-elastic-stack (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/puppet-module-voxpupuli-elasticsearch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• py-serializable (- to 2.0.0-1)
  • Migration status for py-serializable (- 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 santiago, a new source-only upload is needed to allow migration
    • Too young, only 3 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/py-serializable.html
    • autopkgtest for py-serializable/2.0.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pynx (- to 2025.1-1)
  • Migration status for pynx (- to 2025.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pynx/2025.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): pynx nabu
    • Build-Depends(-Arch): pynx nxtomo
    • Build-Depends(-Arch): pynx silx (not considered)
    • Build-Depends(-Arch): pynx tomoscan
    • Depends: pynx nxtomo
    • Depends: pynx silx (not considered)
    • Depends: pynx tomoscan
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynx.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
• pyqt6 (6.8.0-1 to 6.8.1-1)
  • Migration status for pyqt6 (6.8.0-1 to 6.8.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for pyqt6/6.8.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyqt6.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• pysilfont (- to 1.8.0-2)
  • Migration status for pysilfont (- 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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysilfont.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pysoundfile (0.12.1-1 to 0.13.1-1)
  • Migration status for pysoundfile (0.12.1-1 to 0.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pysoundfile/0.13.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysoundfile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-aiovodafone (- to 0.9.0-1)
  • Migration status for python-aiovodafone (- 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 zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiovodafone.html
    • autopkgtest for python-aiovodafone/0.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• python-bincopy (20.0.0+dfsg1-1 to 20.1.0+dfsg1-1)
  • Migration status for python-bincopy (20.0.0+dfsg1-1 to 20.1.0+dfsg1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bincopy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-googleapi (2.159.0-1 to 2.160.0-1)
  • Migration status for python-googleapi (2.159.0-1 to 2.160.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-googleapi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-internetarchive (5.1.0-1 to 5.2.0-1)
  • Migration status for python-internetarchive (5.1.0-1 to 5.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-internetarchive.html
    • autopkgtest for python-internetarchive/5.2.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-zopfli (- to 0.2.3.post1-1)
  • Migration status for python-zopfli (- to 0.2.3.post1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-zopfli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-gstat (- to 2.1-3-1)
  • Migration status for r-cran-gstat (- to 2.1-3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-gstat/2.1-3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gstat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-ncmeta (0.3.6-1 to 0.4.0-1)
  • Migration status for r-cran-ncmeta (0.3.6-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • r-cran-ncmeta unsatisfiable Build-Depends(-Arch) on amd64: r-cran-cftime
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ncmeta.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rem (1.0.0-2 to 1.0.0-3)
  • Migration status for rem (1.0.0-2 to 1.0.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• remind (05.02.03-1 to 05.03.02-1)
  • Migration status for remind (05.02.03-1 to 05.03.02-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/remind.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• reproc (- to 14.2.5-1)
  • Migration status for reproc (- to 14.2.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/reproc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• rpki-trust-anchors (20210817-2 to 20250116-1)
  • Migration status for rpki-trust-anchors (20210817-2 to 20250116-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rpki-trust-anchors.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-cxx (1.0.87-1 to 1.0.130-1)
  • Migration status for rust-cxx (1.0.87-1 to 1.0.130-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-cxx rust-cxxbridge-macro (not considered)
    • Depends: rust-cxx rust-cxxbridge-macro (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-cxx rust-cxxbridge-flags
    • Depends: rust-cxx rust-cxxbridge-flags
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cxx.html
    • autopkgtest for rust-cxx/1.0.130-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-cxxbridge-cmd (- to 1.0.137-1)
  • Migration status for rust-cxxbridge-cmd (- to 1.0.137-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cxxbridge-cmd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-cxxbridge-flags (1.0.87-1 to 1.0.130-1)
  • Migration status for rust-cxxbridge-flags (1.0.87-1 to 1.0.130-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Implicit dependency: rust-cxxbridge-flags rust-cxx (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cxxbridge-flags.html
    • autopkgtest for rust-cxxbridge-flags/1.0.130-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-cxxbridge-macro (1.0.87-2 to 1.0.130-1)
  • Migration status for rust-cxxbridge-macro (1.0.87-2 to 1.0.130-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
    • Implicit dependency: rust-cxxbridge-macro rust-cxx
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cxxbridge-macro.html
    • autopkgtest for rust-cxxbridge-macro/1.0.130-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-litemap (- to 0.7.4-1)
  • Migration status for rust-litemap (- to 0.7.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-litemap-dev/amd64 has unsatisfiable dependency
    • librust-litemap-dev/arm64 has unsatisfiable dependency
    • librust-litemap-dev/armel has unsatisfiable dependency
    • librust-litemap-dev/armhf has unsatisfiable dependency
    • librust-litemap-dev/i386 has unsatisfiable dependency
    • librust-litemap-dev/mips64el has unsatisfiable dependency
    • librust-litemap-dev/ppc64el has unsatisfiable dependency
    • librust-litemap-dev/riscv64 has unsatisfiable dependency
    • librust-litemap-dev/s390x has unsatisfiable dependency
    • Updating rust-litemap would introduce bugs in testing: #1095683
    • 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-litemap.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-railway-provider-db-movas (- to 0.1.0-1)
  • Migration status for rust-railway-provider-db-movas (- to 0.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-railway-provider-db-movas.html
    • autopkgtest for rust-railway-provider-db-movas/0.1.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-regalloc2 (0.9.4-1 to 0.10.2-4)
  • Migration status for rust-regalloc2 (0.9.4-1 to 0.10.2-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Implicit dependency: rust-regalloc2 rust-wasmtime (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-regalloc2.html
    • autopkgtest for rust-regalloc2/0.10.2-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-ripasso-cursive (0.6.5-4 to 0.6.5-5)
  • Migration status for rust-ripasso-cursive (0.6.5-4 to 0.6.5-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/r/rust-ripasso-cursive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-ryu-js (- to 1.0.1-1)
  • Migration status for rust-ryu-js (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ryu-js/1.0.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ryu-js.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-scm-record (- to 0.5.0-1)
  • Migration status for rust-scm-record (- 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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-scm-record.html
    • autopkgtest for rust-scm-record/0.5.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-zerovec (- to 0.11.0-1)
  • Migration status for rust-zerovec (- to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-zerovec-dev/amd64 has unsatisfiable dependency
    • librust-zerovec-dev/arm64 has unsatisfiable dependency
    • librust-zerovec-dev/armel has unsatisfiable dependency
    • librust-zerovec-dev/armhf has unsatisfiable dependency
    • librust-zerovec-dev/i386 has unsatisfiable dependency
    • librust-zerovec-dev/mips64el has unsatisfiable dependency
    • librust-zerovec-dev/ppc64el has unsatisfiable dependency
    • librust-zerovec-dev/riscv64 has unsatisfiable dependency
    • librust-zerovec-dev/s390x has unsatisfiable dependency
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): rust-zerovec rust-zerofrom (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-zerovec.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• satellite-gtk (0.4.2-1 to 0.9.0-1)
  • Migration status for satellite-gtk (0.4.2-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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/satellite-gtk.html
    • autopkgtest for satellite-gtk/0.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sayonara (1.10.0-stable1-3 to 1.10.0-stable1-4)
  • Migration status for sayonara (1.10.0-stable1-3 to 1.10.0-stable1-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/s/sayonara.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• scifem (- to 0.3.0-1)
  • Migration status for scifem (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for scifem/0.3.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scifem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• sord (0.16.16-2 to 0.16.18-1)
  • Migration status for sord (0.16.16-2 to 0.16.18-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sord.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sphinxygen (1.0.4-2 to 1.0.10-1)
  • Migration status for sphinxygen (1.0.4-2 to 1.0.10-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinxygen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sqlmap (1.9-1 to 1.9.2-1)
  • Migration status for sqlmap (1.9-1 to 1.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlmap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sratom (0.6.16-1 to 0.6.18-1)
  • Migration status for sratom (0.6.16-1 to 0.6.18-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sratom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• stow (2.4.1-1 to 2.4.1-2)
  • Migration status for stow (2.4.1-1 to 2.4.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:
    • Updating stow will fix bugs in testing: #1095395
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stow.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• strace (6.12+ds-1 to 6.13+ds-1)
  • Migration status for strace (6.12+ds-1 to 6.13+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/s/strace.html
    • Reproducible on arm64 - info ♻
• suil (0.10.20-1 to 0.10.22-1)
  • Migration status for suil (0.10.20-1 to 0.10.22-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/suil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sweethome3d-furniture-editor (1.30-1 to 2.2-1)
  • Migration status for sweethome3d-furniture-editor (1.30-1 to 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/s/sweethome3d-furniture-editor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sweethome3d-textures-editor (1.8-1 to 2.1-1)
  • Migration status for sweethome3d-textures-editor (1.8-1 to 2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sweethome3d-textures-editor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• systemd-netlogd (- to 1.4.2-1)
  • Migration status for systemd-netlogd (- to 1.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/systemd-netlogd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• sysvinit (3.13-1 to 3.14-1)
  • Migration status for sysvinit (3.13-1 to 3.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dracut/106-1: amd64: Regression or new test ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysvinit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• tex-fmt (- to 0.5.2+dfsg-1)
  • Migration status for tex-fmt (- to 0.5.2+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tex-fmt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• tomwer (- to 1.4.0~rc5-1)
  • Migration status for tomwer (- to 1.4.0~rc5-1): 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
    • Too young, only 3 of 10 days old
    • Build-Depends(-Arch): tomwer nabu
    • Build-Depends(-Arch): tomwer nxtomo
    • Build-Depends(-Arch): tomwer python-ewoks (not considered)
    • Build-Depends(-Arch): tomwer python-ewokscore (not considered)
    • Build-Depends(-Arch): tomwer python-ewoksorange (not considered)
    • Build-Depends(-Arch): tomwer python-nxtomomill (not considered)
    • Build-Depends(-Arch): tomwer python-processview (not considered)
    • Build-Depends(-Arch): tomwer python-rsyncmanager (not considered)
    • Build-Depends(-Arch): tomwer silx (not considered)
    • Depends: tomwer nxtomo
    • Depends: tomwer python-ewoks (not considered)
    • Depends: tomwer python-nxtomomill (not considered)
    • Depends: tomwer python-processview (not considered)
    • Depends: tomwer silx (not considered)
    • Depends: tomwer tomoscan
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomwer.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
• tua (- to 4.3-17)
  • Migration status for tua (- to 4.3-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tua would introduce bugs in testing: #1089457
    • Too young, only 3 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tua.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ublock-origin (1.60.0+dfsg-1 to 1.62.0+dfsg-1)
  • Migration status for ublock-origin (1.60.0+dfsg-1 to 1.62.0+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/u/ublock-origin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• uranium (5.0.0-5 to 5.0.0-6)
  • Migration status for uranium (5.0.0-5 to 5.0.0-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating uranium will fix bugs in testing: #1095608
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uranium.html
    • autopkgtest for uranium/5.0.0-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• vulkan-memory-allocator (3.2.0+dfsg-1 to 3.2.1+dfsg-1)
  • Migration status for vulkan-memory-allocator (3.2.0+dfsg-1 to 3.2.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vulkan-memory-allocator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• wasix-libc (- to 2024.07.08.1+ds-1)
  • Migration status for wasix-libc (- to 2024.07.08.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • wasix-libc unsatisfiable Build-Depends(-Arch) on amd64: clang-16
    • wasix-libc unsatisfiable Build-Depends(-Arch) on amd64: llvm-16
    • wasix-libc unsatisfiable Build-Depends(-Arch) on amd64: libclang-rt-16-dev-wasm32
    • Not built on buildd: arch amd64 binaries uploaded by onlyjob@member.fsf.org
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wasix-libc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• wike (3.1.0-1 to 3.1.1-1)
  • Migration status for wike (3.1.0-1 to 3.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wike.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• wlroots-0.17 (- to 0.17.4-2)
  • Migration status for wlroots-0.17 (- to 0.17.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wlroots-0.17 would introduce bugs in testing: #1095751
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wlroots-0.17.html
    • autopkgtest for wlroots-0.17/0.17.4-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• xbubble (0.5.11.2-3.5 to 0.5.11.2-4)
  • Migration status for xbubble (0.5.11.2-3.5 to 0.5.11.2-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/x/xbubble.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• xkeycaps (- to 2.47-9)
  • Migration status for xkeycaps (- to 2.47-9): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xkeycaps.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• zlog (- to 1.2.18-1)
  • Migration status for zlog (- to 1.2.18-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 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zlog.html
    • autopkgtest for zlog/1.2.18-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• abicheck (1.2-8 to 1.2-9)
  • Migration status for abicheck (1.2-8 to 1.2-9): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/abicheck.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• adun.app (0.81-14 to 0.81-15)
  • Migration status for adun.app (0.81-14 to 0.81-15): 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): adun.app gnustep-gui (not considered)
    • Build-Depends(-Arch): adun.app gnustep-sqlclient
    • Build-Depends(-Arch): adun.app steptalk
    • Depends: adun.app gnustep-make (not considered)
  • Additional info:
    • Updating adun.app will fix bugs in testing: #1094355
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adun.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• amdgcn-tools-19 (- to 19.1)
  • Migration status for amdgcn-tools-19 (- to 19.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/a/amdgcn-tools-19.html
    • Reproducible on amd64 - info ♻
• apt-offline (1.8.5-1 to 1.8.6-1)
  • Migration status for apt-offline (1.8.5-1 to 1.8.6-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/a/apt-offline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• astrometry-data-2mass (1.1 to 1.2)
  • Migration status for astrometry-data-2mass (1.1 to 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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• bankstown-lv2 (1.1.0-1 to 1.1.0-2)
  • Migration status for bankstown-lv2 (1.1.0-1 to 1.1.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bankstown-lv2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• bedstead (3.251-1 to 3.251-2)
  • Migration status for bedstead (3.251-1 to 3.251-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for bedstead/3.251-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• bfs (4.0.4-1 to 4.0.5-2)
  • Migration status for bfs (4.0.4-1 to 4.0.5-2): 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/b/bfs.html
    • autopkgtest for bfs/4.0.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• blastem (0.6.3.4-2 to 0.6.3.4-3)
  • Migration status for blastem (0.6.3.4-2 to 0.6.3.4-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/blastem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
• btm (0.10.2+20250107-3 to 0.10.2+20250107-4)
  • Migration status for btm (0.10.2+20250107-3 to 0.10.2+20250107-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• castle-model-viewer (5.2.0-2 to 5.2.0-3)
  • Migration status for castle-model-viewer (5.2.0-2 to 5.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:
    • Updating castle-model-viewer will fix bugs in testing: #1095334
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/castle-model-viewer.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• cinnamon (6.4.5-1 to 6.4.7-1)
  • Migration status for cinnamon (6.4.5-1 to 6.4.7-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/c/cinnamon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• cinnamon-desktop-environment (6.2.0 to 6.4.0)
  • Migration status for cinnamon-desktop-environment (6.2.0 to 6.4.0): 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/cinnamon-desktop-environment.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ck (0.7.2-1 to 0.7.2-2)
  • Migration status for ck (0.7.2-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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ck.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
• cmake (3.31.5-1 to 3.31.5-2)
  • Migration status for cmake (3.31.5-1 to 3.31.5-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cmake.html
    • autopkgtest for cmake/3.31.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Test in progress (will not be considered a regression), riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• cutemaze (1.3.3-1 to 1.3.4-1)
  • Migration status for cutemaze (1.3.3-1 to 1.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cutemaze.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• cyme (2.1.1+dfsg-1 to 2.1.1+dfsg-2)
  • Migration status for cyme (2.1.1+dfsg-1 to 2.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cyme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• dart (- to 6.13.2+ds-2)
  • Migration status for dart (- to 6.13.2+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dart unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • dart unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • dart unsatisfiable Build-Depends(-Arch) on i386: architecture-is-64-bit
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for dart/6.13.2+ds-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dart.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• desmume (- to 0.9.13-3)
  • Migration status for desmume (- to 0.9.13-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on mips64el
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el 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/d/desmume.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• dnscap (2.2.1-1 to 2.2.1-2)
  • Migration status for dnscap (2.2.1-1 to 2.2.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnscap.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• dnsjit (1.4.0-1 to 1.4.0-2)
  • Migration status for dnsjit (1.4.0-1 to 1.4.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnsjit.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• dnsperf (2.14.0-2 to 2.14.0-3)
  • Migration status for dnsperf (2.14.0-2 to 2.14.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/d/dnsperf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• dnswire (0.4.0-5 to 0.4.0-6)
  • Migration status for dnswire (0.4.0-5 to 0.4.0-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/d/dnswire.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• dxchange (0.1.8-3 to 0.1.9-1)
  • Migration status for dxchange (0.1.8-3 to 0.1.9-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dxchange.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• easymock (5.2.0-1 to 5.5.0-1)
  • Migration status for easymock (5.2.0-1 to 5.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/e/easymock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ejabberd-contrib (- to 0.2025.01.11~dfsg0-1)
  • Migration status for ejabberd-contrib (- to 0.2025.01.11~dfsg0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ejabberd-contrib/amd64 has unsatisfiable dependency
    • ejabberd-mod-cron/amd64 has unsatisfiable dependency
    • ejabberd-mod-default-contacts/amd64 has unsatisfiable dependency
    • ejabberd-mod-default-rooms/amd64 has unsatisfiable dependency
    • ejabberd-mod-deny-omemo/amd64 has unsatisfiable dependency
    • ejabberd-mod-filter/amd64 has unsatisfiable dependency
    • ejabberd-mod-grafite/amd64 has unsatisfiable dependency
    • ejabberd-mod-irc/amd64 has unsatisfiable dependency
    • ejabberd-mod-isolation/amd64 has unsatisfiable dependency
    • ejabberd-mod-log-chat/amd64 has unsatisfiable dependency
    • ejabberd-mod-logsession/amd64 has unsatisfiable dependency
    • ejabberd-mod-logxml/amd64 has unsatisfiable dependency
    • ejabberd-mod-message-log/amd64 has unsatisfiable dependency
    • ejabberd-mod-muc-log-http/amd64 has unsatisfiable dependency
    • ejabberd-mod-post-log/amd64 has unsatisfiable dependency
    • ejabberd-mod-pottymouth/amd64 has unsatisfiable dependency
    • ejabberd-mod-rest/amd64 has unsatisfiable dependency
    • ejabberd-mod-s2s-log/amd64 has unsatisfiable dependency
    • ejabberd-mod-shcommands/amd64 has unsatisfiable dependency
    • ejabberd-mod-spam-filter/amd64 has unsatisfiable dependency
    • ejabberd-mod-statsdx/amd64 has unsatisfiable dependency
    • ejabberd-mod-webpresence/amd64 has unsatisfiable dependency
    • ejabberd-contrib/arm64 has unsatisfiable dependency
    • ejabberd-mod-cron/arm64 has unsatisfiable dependency
    • ejabberd-mod-default-contacts/arm64 has unsatisfiable dependency
    • ejabberd-mod-default-rooms/arm64 has unsatisfiable dependency
    • ejabberd-mod-deny-omemo/arm64 has unsatisfiable dependency
    • ejabberd-mod-filter/arm64 has unsatisfiable dependency
    • ejabberd-mod-grafite/arm64 has unsatisfiable dependency
    • ejabberd-mod-irc/arm64 has unsatisfiable dependency
    • ejabberd-mod-isolation/arm64 has unsatisfiable dependency
    • ejabberd-mod-log-chat/arm64 has unsatisfiable dependency
    • ejabberd-mod-logsession/arm64 has unsatisfiable dependency
    • ejabberd-mod-logxml/arm64 has unsatisfiable dependency
    • ejabberd-mod-message-log/arm64 has unsatisfiable dependency
    • ejabberd-mod-muc-log-http/arm64 has unsatisfiable dependency
    • ejabberd-mod-post-log/arm64 has unsatisfiable dependency
    • ejabberd-mod-pottymouth/arm64 has unsatisfiable dependency
    • ejabberd-mod-rest/arm64 has unsatisfiable dependency
    • ejabberd-mod-s2s-log/arm64 has unsatisfiable dependency
    • ejabberd-mod-shcommands/arm64 has unsatisfiable dependency
    • ejabberd-mod-spam-filter/arm64 has unsatisfiable dependency
    • ejabberd-mod-statsdx/arm64 has unsatisfiable dependency
    • ejabberd-mod-webpresence/arm64 has unsatisfiable dependency
    • ejabberd-mod-cron/armel has unsatisfiable dependency
    • ejabberd-mod-default-contacts/armel has unsatisfiable dependency
    • ejabberd-mod-default-rooms/armel has unsatisfiable dependency
    • ejabberd-mod-deny-omemo/armel has unsatisfiable dependency
    • ejabberd-mod-filter/armel has unsatisfiable dependency
    • ejabberd-mod-grafite/armel has unsatisfiable dependency
    • ejabberd-mod-irc/armel has unsatisfiable dependency
    • ejabberd-mod-isolation/armel has unsatisfiable dependency
    • ejabberd-mod-log-chat/armel has unsatisfiable dependency
    • ejabberd-mod-logsession/armel has unsatisfiable dependency
    • ejabberd-mod-logxml/armel has unsatisfiable dependency
    • ejabberd-mod-message-log/armel has unsatisfiable dependency
    • ejabberd-mod-muc-log-http/armel has unsatisfiable dependency
    • ejabberd-mod-post-log/armel has unsatisfiable dependency
    • ejabberd-mod-pottymouth/armel has unsatisfiable dependency
    • ejabberd-mod-rest/armel has unsatisfiable dependency
    • ejabberd-mod-s2s-log/armel has unsatisfiable dependency
    • ejabberd-mod-shcommands/armel has unsatisfiable dependency
    • ejabberd-mod-spam-filter/armel has unsatisfiable dependency
    • ejabberd-mod-statsdx/armel has unsatisfiable dependency
    • ejabberd-mod-webpresence/armel has unsatisfiable dependency
    • ejabberd-mod-cron/armhf has unsatisfiable dependency
    • ejabberd-mod-default-contacts/armhf has unsatisfiable dependency
    • ejabberd-mod-default-rooms/armhf has unsatisfiable dependency
    • ejabberd-mod-deny-omemo/armhf has unsatisfiable dependency
    • ejabberd-mod-filter/armhf has unsatisfiable dependency
    • ejabberd-mod-grafite/armhf has unsatisfiable dependency
    • ejabberd-mod-irc/armhf has unsatisfiable dependency
    • ejabberd-mod-isolation/armhf has unsatisfiable dependency
    • ejabberd-mod-log-chat/armhf has unsatisfiable dependency
    • ejabberd-mod-logsession/armhf has unsatisfiable dependency
    • ejabberd-mod-logxml/armhf has unsatisfiable dependency
    • ejabberd-mod-message-log/armhf has unsatisfiable dependency
    • ejabberd-mod-muc-log-http/armhf has unsatisfiable dependency
    • ejabberd-mod-post-log/armhf has unsatisfiable dependency
    • ejabberd-mod-pottymouth/armhf has unsatisfiable dependency
    • ejabberd-mod-rest/armhf has unsatisfiable dependency
    • ejabberd-mod-s2s-log/armhf has unsatisfiable dependency
    • ejabberd-mod-shcommands/armhf has unsatisfiable dependency
    • ejabberd-mod-spam-filter/armhf has unsatisfiable dependency
    • ejabberd-mod-statsdx/armhf has unsatisfiable dependency
    • ejabberd-mod-webpresence/armhf has unsatisfiable dependency
    • ejabberd-mod-cron/i386 has unsatisfiable dependency
    • ejabberd-mod-default-contacts/i386 has unsatisfiable dependency
    • ejabberd-mod-default-rooms/i386 has unsatisfiable dependency
    • ejabberd-mod-deny-omemo/i386 has unsatisfiable dependency
    • ejabberd-mod-filter/i386 has unsatisfiable dependency
    • ejabberd-mod-grafite/i386 has unsatisfiable dependency
    • ejabberd-mod-irc/i386 has unsatisfiable dependency
    • ejabberd-mod-isolation/i386 has unsatisfiable dependency
    • ejabberd-mod-log-chat/i386 has unsatisfiable dependency
    • ejabberd-mod-logsession/i386 has unsatisfiable dependency
    • ejabberd-mod-logxml/i386 has unsatisfiable dependency
    • ejabberd-mod-message-log/i386 has unsatisfiable dependency
    • ejabberd-mod-muc-log-http/i386 has unsatisfiable dependency
    • ejabberd-mod-post-log/i386 has unsatisfiable dependency
    • ejabberd-mod-pottymouth/i386 has unsatisfiable dependency
    • ejabberd-mod-rest/i386 has unsatisfiable dependency
    • ejabberd-mod-s2s-log/i386 has unsatisfiable dependency
    • ejabberd-mod-shcommands/i386 has unsatisfiable dependency
    • ejabberd-mod-spam-filter/i386 has unsatisfiable dependency
    • ejabberd-mod-statsdx/i386 has unsatisfiable dependency
    • ejabberd-mod-webpresence/i386 has unsatisfiable dependency
    • ejabberd-mod-cron/ppc64el has unsatisfiable dependency
    • ejabberd-mod-default-contacts/ppc64el has unsatisfiable dependency
    • ejabberd-mod-default-rooms/ppc64el has unsatisfiable dependency
    • ejabberd-mod-deny-omemo/ppc64el has unsatisfiable dependency
    • ejabberd-mod-filter/ppc64el has unsatisfiable dependency
    • ejabberd-mod-grafite/ppc64el has unsatisfiable dependency
    • ejabberd-mod-irc/ppc64el has unsatisfiable dependency
    • ejabberd-mod-isolation/ppc64el has unsatisfiable dependency
    • ejabberd-mod-log-chat/ppc64el has unsatisfiable dependency
    • ejabberd-mod-logsession/ppc64el has unsatisfiable dependency
    • ejabberd-mod-logxml/ppc64el has unsatisfiable dependency
    • ejabberd-mod-message-log/ppc64el has unsatisfiable dependency
    • ejabberd-mod-muc-log-http/ppc64el has unsatisfiable dependency
    • ejabberd-mod-post-log/ppc64el has unsatisfiable dependency
    • ejabberd-mod-pottymouth/ppc64el has unsatisfiable dependency
    • ejabberd-mod-rest/ppc64el has unsatisfiable dependency
    • ejabberd-mod-s2s-log/ppc64el has unsatisfiable dependency
    • ejabberd-mod-shcommands/ppc64el has unsatisfiable dependency
    • ejabberd-mod-spam-filter/ppc64el has unsatisfiable dependency
    • ejabberd-mod-statsdx/ppc64el has unsatisfiable dependency
    • ejabberd-mod-webpresence/ppc64el has unsatisfiable dependency
    • ejabberd-mod-cron/riscv64 has unsatisfiable dependency
    • ejabberd-mod-default-contacts/riscv64 has unsatisfiable dependency
    • ejabberd-mod-default-rooms/riscv64 has unsatisfiable dependency
    • ejabberd-mod-deny-omemo/riscv64 has unsatisfiable dependency
    • ejabberd-mod-filter/riscv64 has unsatisfiable dependency
    • ejabberd-mod-grafite/riscv64 has unsatisfiable dependency
    • ejabberd-mod-irc/riscv64 has unsatisfiable dependency
    • ejabberd-mod-isolation/riscv64 has unsatisfiable dependency
    • ejabberd-mod-log-chat/riscv64 has unsatisfiable dependency
    • ejabberd-mod-logsession/riscv64 has unsatisfiable dependency
    • ejabberd-mod-logxml/riscv64 has unsatisfiable dependency
    • ejabberd-mod-message-log/riscv64 has unsatisfiable dependency
    • ejabberd-mod-muc-log-http/riscv64 has unsatisfiable dependency
    • ejabberd-mod-post-log/riscv64 has unsatisfiable dependency
    • ejabberd-mod-pottymouth/riscv64 has unsatisfiable dependency
    • ejabberd-mod-rest/riscv64 has unsatisfiable dependency
    • ejabberd-mod-s2s-log/riscv64 has unsatisfiable dependency
    • ejabberd-mod-shcommands/riscv64 has unsatisfiable dependency
    • ejabberd-mod-spam-filter/riscv64 has unsatisfiable dependency
    • ejabberd-mod-statsdx/riscv64 has unsatisfiable dependency
    • ejabberd-mod-webpresence/riscv64 has unsatisfiable dependency
    • ejabberd-contrib unsatisfiable Build-Depends(-Arch) on mips64el: ejabberd (>= 24.12~)
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): ejabberd-contrib ejabberd (not considered)
    • Depends: ejabberd-contrib ejabberd (not considered)
    • Depends: ejabberd-contrib erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ejabberd-contrib.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• elixir-lang (1.14.0.dfsg-2 to 1.18.1.dfsg-1.1)
  • Migration status for elixir-lang (1.14.0.dfsg-2 to 1.18.1.dfsg-1.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: elixir-lang erlang (not considered)
  • Additional info:
    • Updating elixir-lang will fix bugs in testing: #1092438
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elixir-lang.html
    • autopkgtest for elixir-lang/1.18.1.dfsg-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • No reference result, but not reproducibility on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • No reference result, but not reproducibility on armhf - info ♻
    • No reference result, but not reproducibility on i386 - info ♻
• erlang-meck (0.9.2-2 to 1.0.0-1)
  • Migration status for erlang-meck (0.9.2-2 to 1.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Depends: erlang-meck erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-meck.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-acme (1.0.23-1 to 1.0.25-1)
  • Migration status for erlang-p1-acme (1.0.23-1 to 1.0.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • erlang-p1-acme unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-yconf (>= 1.0.17)
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): erlang-p1-acme erlang-p1-yconf (not considered)
    • Depends: erlang-p1-acme erlang (not considered)
    • Depends: erlang-p1-acme erlang-p1-yconf (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-acme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-cache-tab (1.0.31-1 to 1.0.31-2)
  • Migration status for erlang-p1-cache-tab (1.0.31-1 to 1.0.31-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: erlang-p1-cache-tab erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-cache-tab.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-eimp (- to 1.0.23-4)
  • Migration status for erlang-p1-eimp (- to 1.0.23-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Depends: erlang-p1-eimp erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-eimp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-iconv (1.0.14-1 to 1.0.14-2)
  • Migration status for erlang-p1-iconv (1.0.14-1 to 1.0.14-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: erlang-p1-iconv erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-iconv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-mqtree (1.0.17-1 to 1.0.17-2)
  • Migration status for erlang-p1-mqtree (1.0.17-1 to 1.0.17-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: erlang-p1-mqtree erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-mqtree.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-mysql (1.0.24-1 to 1.0.25-1)
  • Migration status for erlang-p1-mysql (1.0.24-1 to 1.0.25-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: erlang-p1-mysql erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-mysql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-oauth2 (0.6.14-1 to 0.6.14-2)
  • Migration status for erlang-p1-oauth2 (0.6.14-1 to 0.6.14-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: erlang-p1-oauth2 erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-oauth2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-pam (1.0.14-2 to 1.0.14-3)
  • Migration status for erlang-p1-pam (1.0.14-2 to 1.0.14-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: erlang-p1-pam erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-pam.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-pgsql (1.1.27-1 to 1.1.31-1)
  • Migration status for erlang-p1-pgsql (1.1.27-1 to 1.1.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • erlang-p1-pgsql unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-xml (>= 1.1.55)
    • erlang-p1-pgsql unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-xmpp (>= 1.9.2)
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): erlang-p1-pgsql erlang-p1-tls
    • Build-Depends(-Arch): erlang-p1-pgsql erlang-p1-xml (not considered)
    • Build-Depends(-Arch): erlang-p1-pgsql erlang-p1-xmpp (not considered)
    • Depends: erlang-p1-pgsql erlang (not considered)
    • Depends: erlang-p1-pgsql erlang-p1-tls
    • Depends: erlang-p1-pgsql erlang-p1-xml (not considered)
    • Depends: erlang-p1-pgsql erlang-p1-xmpp (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-pgsql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-pkix (1.0.10-1 to 1.0.10-2)
  • Migration status for erlang-p1-pkix (1.0.10-1 to 1.0.10-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: erlang-p1-pkix erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-pkix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-sip (1.0.54-1 to 1.0.56-1)
  • Migration status for erlang-p1-sip (1.0.54-1 to 1.0.56-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): erlang-p1-sip erlang-p1-stun
    • Build-Depends(-Arch): erlang-p1-sip erlang-p1-tls
    • Depends: erlang-p1-sip erlang (not considered)
    • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-sqlite3 (1.1.15-1 to 1.1.15-2)
  • Migration status for erlang-p1-sqlite3 (1.1.15-1 to 1.1.15-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: erlang-p1-sqlite3 erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-sqlite3.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-stringprep (1.0.30-1 to 1.0.30-2)
  • Migration status for erlang-p1-stringprep (1.0.30-1 to 1.0.30-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: erlang-p1-stringprep erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-stringprep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-stun (1.2.14-1 to 1.2.15-1)
  • Migration status for erlang-p1-stun (1.2.14-1 to 1.2.15-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): erlang-p1-stun erlang-p1-tls
    • Depends: erlang-p1-stun erlang (not considered)
    • Depends: erlang-p1-stun erlang-p1-tls
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-stun.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-tls (1.1.21-1 to 1.1.22-1)
  • Migration status for erlang-p1-tls (1.1.21-1 to 1.1.22-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
    • Depends: erlang-p1-tls erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-tls.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-utils (1.0.26-1 to 1.0.26-2)
  • Migration status for erlang-p1-utils (1.0.26-1 to 1.0.26-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: erlang-p1-utils erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-xml (1.1.52-1 to 1.1.55-1)
  • Migration status for erlang-p1-xml (1.1.52-1 to 1.1.55-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: erlang-p1-xml erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-xml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-yaml (1.0.37-1 to 1.0.37-2)
  • Migration status for erlang-p1-yaml (1.0.37-1 to 1.0.37-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: erlang-p1-yaml erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-yaml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-yconf (1.0.16-1 to 1.0.17-1)
  • Migration status for erlang-p1-yconf (1.0.16-1 to 1.0.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • erlang-p1-yconf unsatisfiable Build-Depends(-Arch) on mips64el: erlang-p1-yaml (>= 1.0.37-2~)
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): erlang-p1-yconf erlang-p1-yaml (not considered)
    • Depends: erlang-p1-yconf erlang (not considered)
    • Depends: erlang-p1-yconf erlang-p1-yaml (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-yconf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-p1-zlib (1.0.13-1 to 1.0.13-2)
  • Migration status for erlang-p1-zlib (1.0.13-1 to 1.0.13-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: erlang-p1-zlib erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-p1-zlib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• erlang-redis-client (1.2.0-7 to 1.2.0-8)
  • Migration status for erlang-redis-client (1.2.0-7 to 1.2.0-8): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
    • Depends: erlang-redis-client erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-redis-client.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• espeakup (1:0.90-16.1 to 1:0.90-17)
  • Migration status for espeakup (1:0.90-16.1 to 1:0.90-17): 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/espeakup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• fnott (1.7.0+ds-3 to 1.7.1+ds-1)
  • Migration status for fnott (1.7.0+ds-3 to 1.7.1+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/f/fnott.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• fonts-smiley-sans (2.0.1-1 to 2.0.1-2)
  • Migration status for fonts-smiley-sans (2.0.1-1 to 2.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/fonts-smiley-sans.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• fretsonfire-songs-muldjord (2.dfsg-2.1 to 2.dfsg-3)
  • Migration status for fretsonfire-songs-muldjord (2.dfsg-2.1 to 2.dfsg-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/f/fretsonfire-songs-muldjord.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• fretsonfire-songs-sectoid (1.dfsg-3.1 to 1.dfsg-4)
  • Migration status for fretsonfire-songs-sectoid (1.dfsg-3.1 to 1.dfsg-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fretsonfire-songs-sectoid.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• g-golf (0.8.0~rc9-2 to 0.8.0-1)
  • Migration status for g-golf (0.8.0~rc9-2 to 0.8.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/g-golf.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
• gamescope (3.15.13-2 to 3.16.1-1)
  • Migration status for gamescope (3.15.13-2 to 3.16.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gamescope unsatisfiable Build-Depends(-Arch) on ppc64el: libluajit-5.1-dev
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Too young, only 4 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• garlic-doc (1.6-1.1 to 1.6-2)
  • Migration status for garlic-doc (1.6-1.1 to 1.6-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/garlic-doc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• glyphspkg (0.2.1-1 to 0.2.1-2)
  • Migration status for glyphspkg (0.2.1-1 to 0.2.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glyphspkg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-caffeine (55-1 to 55-2)
  • Migration status for gnome-shell-extension-caffeine (55-1 to 55-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-caffeine.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-desktop-icons-ng (47.0.11-3 to 47.0.13-1)
  • Migration status for gnome-shell-extension-desktop-icons-ng (47.0.11-3 to 47.0.13-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-extension-desktop-icons-ng.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• golang-github-seccomp-libseccomp-golang (0.10.0-3 to 0.10.0-4)
  • Migration status for golang-github-seccomp-libseccomp-golang (0.10.0-3 to 0.10.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-seccomp-libseccomp-golang.html
    • autopkgtest for golang-github-seccomp-libseccomp-golang/0.10.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• htop (3.3.0-4 to 3.3.0-5)
  • Migration status for htop (3.3.0-4 to 3.3.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/htop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ibm-3270 (4.1ga10-1.1 to 4.3ga10-3)
  • Migration status for ibm-3270 (4.1ga10-1.1 to 4.3ga10-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 i386
    • missing build on ppc64el
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch: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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibm-3270.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• iptables-persistent (1.0.22 to 1.0.23)
  • Migration status for iptables-persistent (1.0.22 to 1.0.23): 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/iptables-persistent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• itinerary (24.12.0-2 to 24.12.0-3)
  • Migration status for itinerary (24.12.0-2 to 24.12.0-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating itinerary will fix bugs in testing: #1093784
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/itinerary.html
• jag (0.3.8-2 to 0.3.8-3)
  • Migration status for jag (0.3.8-2 to 0.3.8-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/j/jag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• jctools (2.0.2-2 to 4.0.5+dfsg-1)
  • Migration status for jctools (2.0.2-2 to 4.0.5+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/j/jctools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• jwm (- to 2.4.6-2)
  • Migration status for jwm (- to 2.4.6-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/j/jwm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• kdsoap (2.2.0+dfsg-2 to 2.2.0+dfsg-3)
  • Migration status for kdsoap (2.2.0+dfsg-2 to 2.2.0+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdsoap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• ldc (1:1.40.0-4 to 1:1.40.0-5)
  • Migration status for ldc (1:1.40.0-4 to 1:1.40.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ldc.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Reproducibility regression on armhf - info ♻
    • Reproducible on i386 - info ♻
• libapache-mod-jk (1:1.2.49-1 to 1:1.2.50-1)
  • Migration status for libapache-mod-jk (1:1.2.49-1 to 1:1.2.50-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/libapache-mod-jk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libinfinity (0.7.2-3 to 0.7.2-4)
  • Migration status for libinfinity (0.7.2-3 to 0.7.2-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libinfinity.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libjaudiotagger-java (2.0.3-3 to 3.0.1+dfsg-1)
  • Migration status for libjaudiotagger-java (2.0.3-3 to 3.0.1+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjaudiotagger-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libjgroups-java (2.12.2.Final-5 to 2.12.2.Final-6)
  • Migration status for libjgroups-java (2.12.2.Final-5 to 2.12.2.Final-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/libj/libjgroups-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libjpfcodegen-java (0.4+dfsg1-1.1 to 0.4+dfsg1-2)
  • Migration status for libjpfcodegen-java (0.4+dfsg1-1.1 to 0.4+dfsg1-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/libj/libjpfcodegen-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libmad (0.15.1b-10.2 to 0.15.1b-11)
  • Migration status for libmad (0.15.1b-10.2 to 0.15.1b-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/libm/libmad.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libnxt (0.4.2-2 to 0.5.0-1)
  • Migration status for libnxt (0.4.2-2 to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libnxt/0.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for nxt-firmware/1.29.7-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnxt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libpcap (1.10.5-1 to 1.10.5-2)
  • Migration status for libpcap (1.10.5-1 to 1.10.5-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpcap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libsdl2-image (2.8.4+dfsg-1 to 2.8.5+dfsg-1)
  • Migration status for libsdl2-image (2.8.4+dfsg-1 to 2.8.5+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsdl2-image.html
    • autopkgtest for libsdl2-image/2.8.5+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libsdl2-mixer (2.8.0+dfsg-1 to 2.8.1+dfsg-1)
  • Migration status for libsdl2-mixer (2.8.0+dfsg-1 to 2.8.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsdl2-mixer.html
    • autopkgtest for libsdl2-mixer/2.8.1+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libtasn1-6 (4.19.0-3 to 4.20.0-1)
  • Migration status for libtasn1-6 (4.19.0-3 to 4.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libtasn1-6/4.20.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtasn1-6.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• linux (6.12.12-1 to 6.12.13-1)
  • Migration status for linux (6.12.12-1 to 6.12.13-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux.html
    • autopkgtest for linux/6.12.13-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• lomiri-dekko-app (- to 0.4.1+dfsg-3)
  • Migration status for lomiri-dekko-app (- to 0.4.1+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): lomiri-dekko-app lomiri-indicator-network
    • Depends: lomiri-dekko-app lomiri-indicator-network
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-dekko-app.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• lrcalc (1.2-2.1 to 1.2-2.2)
  • Migration status for lrcalc (1.2-2.1 to 1.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lrcalc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• lugaru (1.2-6 to 1.2-7)
  • Migration status for lugaru (1.2-6 to 1.2-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/l/lugaru.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• lutris (0.5.17-1 to 0.5.17-2)
  • Migration status for lutris (0.5.17-1 to 0.5.17-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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• magma (2.7.2+ds-1 to 2.9.0+ds-1)
  • Migration status for magma (2.7.2+ds-1 to 2.9.0+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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• minigalaxy (1.2.6-2 to 1.2.6-3)
  • Migration status for minigalaxy (1.2.6-2 to 1.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/minigalaxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• mobile-tweaks (7 to 8)
  • Migration status for mobile-tweaks (7 to 8): 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/mobile-tweaks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• mpvqt (1.0.0-1 to 1.0.1-1)
  • Migration status for mpvqt (1.0.0-1 to 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpvqt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• mujs (1.3.5-1 to 1.3.6-1)
  • Migration status for mujs (1.3.5-1 to 1.3.6-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/mujs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ngrep (1.47+ds1-5 to 1.47+ds1-6)
  • Migration status for ngrep (1.47+ds1-5 to 1.47+ds1-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/n/ngrep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• odc (1.5.2-1 to 1.6.0-1)
  • Migration status for odc (1.5.2-1 to 1.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odc.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• okular (4:24.12.0-2 to 4:24.12.2-1)
  • Migration status for okular (4:24.12.0-2 to 4:24.12.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/o/okular.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• open3d (0.18.0+ds-6 to 0.19.0-2)
  • Migration status for open3d (0.18.0+ds-6 to 0.19.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open3d.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for open3d/0.19.0-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• openbgpd (8.7-1 to 8.8-1)
  • Migration status for openbgpd (8.7-1 to 8.8-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/openbgpd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• openjdk-24 (24~33ea-1 to 24~36ea-1)
  • Migration status for openjdk-24 (24~33ea-1 to 24~36ea-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by doko
    • Not built on buildd: arch all binaries uploaded by doko, a new source-only upload is needed to allow migration
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for openjdk-24/24~36ea-1: amd64: Pass, arm64: Pass, armel: Test in progress (will not be considered a regression), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-24.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• openjph (0.18.2-2 to 0.21.0-1)
  • Migration status for openjph (0.18.2-2 to 0.21.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by mathieu.malaterre@gmail.com
    • Not built on buildd: arch all binaries uploaded by mathieu.malaterre@gmail.com, a new source-only upload is needed to allow migration
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjph.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• openmpi (5.0.6-3 to 5.0.6-4)
  • Migration status for openmpi (5.0.6-3 to 5.0.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for deal.ii/9.6.2-1: amd64: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for gromacs/2024.5-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for mpi-defaults/1.18: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for mpi4py/4.0.1-7: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for netgen/6.2.2404+dfsg1-5: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for nwchem/7.2.3-7: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for openmpi/5.0.6-4: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmpi.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• oxigraph (0.4.4-1 to 0.4.7-4)
  • Migration status for oxigraph (0.4.4-1 to 0.4.7-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): oxigraph rust-dashmap
    • Depends: oxigraph rocksdb
    • Depends: oxigraph rust-dashmap
  • Additional info:
    • Updating oxigraph will fix bugs in testing: #1090901, #1094687
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oxigraph.html
    • autopkgtest for oxigraph/0.4.7-4: amd64: Failed (not a regression), arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• paho.mqtt.cpp (1.2.0-2 to 1.5.0-1)
  • Migration status for paho.mqtt.cpp (1.2.0-2 to 1.5.0-1): 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
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paho.mqtt.cpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• pam-pkcs11 (0.6.12-2 to 0.6.13-1)
  • Migration status for pam-pkcs11 (0.6.12-2 to 0.6.13-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 pam-pkcs11 will fix bugs in testing: #1095402
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pam-pkcs11.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• pci.ids (0.0~2025.01.27-1 to 0.0~2025.02.05-1)
  • Migration status for pci.ids (0.0~2025.01.27-1 to 0.0~2025.02.05-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pci.ids/0.0~2025.02.05-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for pciutils/1:3.13.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pci.ids.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• phosh-osk-stub (0.44.0-1 to 0.45~rc1-1)
  • Migration status for phosh-osk-stub (0.44.0-1 to 0.45~rc1-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/phosh-osk-stub.html
    • autopkgtest for phosh-osk-stub/0.45~rc1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• photofilmstrip (4.0.0-2 to 4.1.0-1)
  • Migration status for photofilmstrip (4.0.0-2 to 4.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/photofilmstrip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• pudb (2022.1.3-1 to 2022.1.3-1.1)
  • Migration status for pudb (2022.1.3-1 to 2022.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/p/pudb.html
    • autopkgtest for pudb/2022.1.3-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• pwdsphinx (2.0.0~rc2-1 to 2.0.0~rc6-1)
  • Migration status for pwdsphinx (2.0.0~rc2-1 to 2.0.0~rc6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pwdsphinx.html
    • autopkgtest for pwdsphinx/2.0.0~rc6-1: amd64: No tests, superficial or marked flaky ♻, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• pysrt (1.1.2-1 to 1.1.2-2)
  • Migration status for pysrt (1.1.2-1 to 1.1.2-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/pysrt.html
    • autopkgtest for pysrt/1.1.2-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-aws-requests-auth (0.4.3-4 to 0.4.3-5)
  • Migration status for python-aws-requests-auth (0.4.3-4 to 0.4.3-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aws-requests-auth.html
    • autopkgtest for python-aws-requests-auth/0.4.3-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-drf-spectacular-sidecar-nonfree (2024.12.1-1 to 2025.2.1-1)
  • Migration status for python-drf-spectacular-sidecar-nonfree (2024.12.1-1 to 2025.2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• python-libtmux (0.40.1-1 to 0.42.0-2)
  • Migration status for python-libtmux (0.40.1-1 to 0.42.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-libtmux/0.42.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression)
    • autopkgtest for tmuxp/1.50.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-libtmux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-ly (0.9.7-1 to 0.9.9-3)
  • Migration status for python-ly (0.9.7-1 to 0.9.9-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 python-ly will fix bugs in testing: #1095526
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ly.html
    • autopkgtest for python-ly/0.9.9-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-mrcz (0.5.6-2 to 0.5.7-1)
  • Migration status for python-mrcz (0.5.6-2 to 0.5.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-mrcz/0.5.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating python-mrcz will fix bugs in testing: #1095373
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mrcz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-s3transfer (0.10.4-1 to 0.11.2-1)
  • Migration status for python-s3transfer (0.10.4-1 to 0.11.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/p/python-s3transfer.html
    • autopkgtest for python-s3transfer/0.11.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• qcom-phone-utils (0.3.1 to 0.4.0)
  • Migration status for qcom-phone-utils (0.3.1 to 0.4.0): 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/q/qcom-phone-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• qtbase-opensource-src (5.15.15+dfsg-2 to 5.15.15+dfsg-4)
  • Migration status for qtbase-opensource-src (5.15.15+dfsg-2 to 5.15.15+dfsg-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtbase-opensource-src.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• quadrule (0~20121001-2 to 0~20121001-3)
  • Migration status for quadrule (0~20121001-2 to 0~20121001-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/q/quadrule.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-bioc-biomart (2.62.0+dfsg-2 to 2.62.1+dfsg-1)
  • Migration status for r-bioc-biomart (2.62.0+dfsg-2 to 2.62.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biomart.html
    • autopkgtest for r-bioc-biomart/2.62.1+dfsg-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• racket-mode (20250125~git.a3bcfd2-1 to 20250205~git.d9e66c7-1)
  • Migration status for racket-mode (20250125~git.a3bcfd2-1 to 20250205~git.d9e66c7-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/racket-mode.html
    • autopkgtest for racket-mode/20250205~git.d9e66c7-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• readpe (0.84-1 to 0.84-2)
  • Migration status for readpe (0.84-1 to 0.84-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/r/readpe.html
    • autopkgtest for readpe/0.84-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• reform-branding (2 to 4)
  • Migration status for reform-branding (2 to 4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• retroarch (1.19.1+dfsg-1 to 1.20.0+dfsg-1)
  • Migration status for retroarch (1.19.1+dfsg-1 to 1.20.0+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/retroarch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rmysql (0.10.29-1 to 0.11.0-1)
  • Migration status for rmysql (0.10.29-1 to 0.11.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/r/rmysql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rocksdb (9.8.4-1 to 9.10.0-1)
  • Migration status for rocksdb (9.8.4-1 to 9.10.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating rocksdb will fix bugs in testing: #1088523
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rocksdb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• runc (1.1.15+ds1-1 to 1.1.15+ds1-2)
  • Migration status for runc (1.1.15+ds1-1 to 1.1.15+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for runc/1.1.15+ds1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
    • Built-Using: runc golang-1.23
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/runc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• rust-launchpadlib (- to 0.2.0-3)
  • Migration status for rust-launchpadlib (- to 0.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-launchpadlib/0.2.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
    • Depends: rust-launchpadlib rust-keyring (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-launchpadlib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-sequoia-keystore (0.6.1-3 to 0.6.2-1)
  • Migration status for rust-sequoia-keystore (0.6.1-3 to 0.6.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-keystore.html
    • autopkgtest for rust-sequoia-keystore/0.6.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-sequoia-octopus-librnp (1.10.0-4 to 1.10.0-5)
  • Migration status for rust-sequoia-octopus-librnp (1.10.0-4 to 1.10.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-octopus-librnp.html
    • autopkgtest for rust-sequoia-octopus-librnp/1.10.0-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• s3ql (5.2.3+dfsg-1 to 5.2.3+dfsg-2)
  • Migration status for s3ql (5.2.3+dfsg-1 to 5.2.3+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/s3ql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• safe-vdash (0.19.3-1 to 0.19.3-2)
  • Migration status for safe-vdash (0.19.3-1 to 0.19.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Built-Using: safe-vdash rust-hyper-rustls
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/safe-vdash.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sccache (0.9.1-2 to 0.9.1-3)
  • Migration status for sccache (0.9.1-2 to 0.9.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/sccache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• schism (2:20241226-1 to 2:20250208-1)
  • Migration status for schism (2:20241226-1 to 2:20250208-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/schism.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Reproducibility regression on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
• serd (0.32.2-1 to 0.32.4-1)
  • Migration status for serd (0.32.2-1 to 0.32.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/s/serd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• settle (0.40.1-7 to 0.40.1-8)
  • Migration status for settle (0.40.1-7 to 0.40.1-8): 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/settle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• smb4k (3.2.5-1 to 4.0.0-1)
  • Migration status for smb4k (3.2.5-1 to 4.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smb4k.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sos (- to 4.8.2-4)
  • Migration status for sos (- to 4.8.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sos/4.8.2-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for sosreport/n/a: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sos.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sshuttle (1.1.2-3 to 1.2.0-1)
  • Migration status for sshuttle (1.1.2-3 to 1.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sshuttle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sway-contrib (1.10-contrib.0-1 to 1.10.1-1)
  • Migration status for sway-contrib (1.10-contrib.0-1 to 1.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sway-contrib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• swirc (3.5.2-1 to 3.5.3-1)
  • Migration status for swirc (3.5.2-1 to 3.5.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swirc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sysprof (47.2-1 to 48~beta-2)
  • Migration status for sysprof (47.2-1 to 48~beta-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysprof.html
    • autopkgtest for sysprof/48~beta-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• tailspin (4.0.0+dfsg-3 to 4.0.0+dfsg-4)
  • Migration status for tailspin (4.0.0+dfsg-3 to 4.0.0+dfsg-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tailspin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• thonny (4.0.1-1 to 4.1.7-1)
  • Migration status for thonny (4.0.1-1 to 4.1.7-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/thonny.html
    • autopkgtest for thonny/4.1.7-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• tinyframe (0.1.1-6 to 0.1.1-7)
  • Migration status for tinyframe (0.1.1-6 to 0.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tinyframe.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• tomcat10 (10.1.34-1 to 10.1.35-1)
  • Migration status for tomcat10 (10.1.34-1 to 10.1.35-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/tomcat10.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• tox-current-env (0.0.12-1 to 0.0.14-1)
  • Migration status for tox-current-env (0.0.12-1 to 0.0.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/t/tox-current-env.html
    • autopkgtest for tox-current-env/0.0.14-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• turtlefmt (0.1.1-4 to 0.1.2-3)
  • Migration status for turtlefmt (0.1.1-4 to 0.1.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
    • Built-Using: turtlefmt oxigraph
  • Additional info:
    • Updating turtlefmt will fix bugs in testing: #1094859
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/turtlefmt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• vdr-plugin-skinenigmang (- to 0.1.5-1)
  • Migration status for vdr-plugin-skinenigmang (- to 0.1.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdr-plugin-skinenigmang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• volume-key (0.3.12-8 to 0.3.12-9)
  • Migration status for volume-key (0.3.12-8 to 0.3.12-9): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/volume-key.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• zangband (1:2.7.5pre1-14 to 1:2.7.5pre1-15)
  • Migration status for zangband (1:2.7.5pre1-14 to 1:2.7.5pre1-15): 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 zangband will fix bugs in testing: #1093369
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• zix (0.4.2-2 to 0.6.2-1)
  • Migration status for zix (0.4.2-2 to 0.6.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• anna (1.95 to 1.96)
  • Migration status for anna (1.95 to 1.96): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• apt (2.9.27 to 2.9.28)
  • Migration status for apt (2.9.27 to 2.9.28): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt.html
    • autopkgtest for apt/2.9.28: amd64: Pass, arm64: Failed (not a regression), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• atuin (18.4.0-1 to 18.4.0-2)
  • Migration status for atuin (18.4.0-1 to 18.4.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating atuin will fix bugs in testing: #1095327
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/atuin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• beanprice (1.2.2-1 to 2.0.0-1)
  • Migration status for beanprice (1.2.2-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/beanprice.html
    • 5 days old (needed 5 days)
• casacore (3.6.1-4 to 3.6.1-5)
  • Migration status for casacore (3.6.1-4 to 3.6.1-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating casacore will fix bugs in testing: #1095333
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/casacore.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• cdebconf-entropy (0.55 to 0.56)
  • Migration status for cdebconf-entropy (0.55 to 0.56): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• chewmail (- to 1.3-2)
  • Migration status for chewmail (- to 1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chewmail would introduce bugs in testing: #1095129, #512231
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chewmail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• cram (0.7-5 to 0.7-6)
  • Migration status for cram (0.7-5 to 0.7-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cram.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• culmus-fancy (0.0.20240129+nmu1 to 0.0.20240129.1)
  • Migration status for culmus-fancy (0.0.20240129+nmu1 to 0.0.20240129.1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/culmus-fancy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• debugedit (1:5.1-1 to 1:5.1-2)
  • Migration status for debugedit (1:5.1-1 to 1:5.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debugedit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• dh-rust (0.0.10 to 0.0.11)
  • Migration status for dh-rust (0.0.10 to 0.0.11): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-rust.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• dhcpcd (1:10.1.0-3 to 1:10.1.0-6)
  • Migration status for dhcpcd (1:10.1.0-3 to 1:10.1.0-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dhcpcd.html
    • autopkgtest for dhcpcd/1:10.1.0-6: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• dracut (105-3 to 106-1)
  • Migration status for dracut (105-3 to 106-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dracut/106-1: amd64: Regression or new test ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dracut.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• fontcustom (2.0.0+ds4-5.1 to 2.0.0+ds4-6)
  • Migration status for fontcustom (2.0.0+ds4-5.1 to 2.0.0+ds4-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fontcustom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• getdns (- to 1.6.0-3.2)
  • Migration status for getdns (- to 1.6.0-3.2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/getdns.html
    • autopkgtest for getdns/1.6.0-3.2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• gimagereader (3.4.2-6 to 3.4.2-7)
  • Migration status for gimagereader (3.4.2-6 to 3.4.2-7): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gimagereader.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• gnome-keysign (- to 1.3.0-5)
  • Migration status for gnome-keysign (- to 1.3.0-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-keysign.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• libidw-java (1.6.1-1.1 to 1.6.1-2)
  • Migration status for libidw-java (1.6.1-1.1 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libidw-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• libjgoodies-animation-java (1.4.3-2 to 1.4.3-3)
  • Migration status for libjgoodies-animation-java (1.4.3-2 to 1.4.3-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjgoodies-animation-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• libjgoodies-binding-java (2.13.0-2 to 2.13.0-3)
  • Migration status for libjgoodies-binding-java (2.13.0-2 to 2.13.0-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjgoodies-binding-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• libjgoodies-common-java (1.8.1-2.1 to 1.8.1-3)
  • Migration status for libjgoodies-common-java (1.8.1-2.1 to 1.8.1-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjgoodies-common-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• megatools (1.11.1-1 to 1.11.3-1)
  • Migration status for megatools (1.11.1-1 to 1.11.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/megatools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• metastore (1.1.2-5 to 1.1.2-6)
  • Migration status for metastore (1.1.2-5 to 1.1.2-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/metastore.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• ode (2:0.16.6-1 to 2:0.16.6-2)
  • Migration status for ode (2:0.16.6-1 to 2:0.16.6-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• okasha (0.3.0-1 to 0.3.0-2)
  • Migration status for okasha (0.3.0-1 to 0.3.0-2): 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)
• os-autoinst (4.6.1712854180.1bf07142-4 to 4.6.1731418769.97d9a7fd-2)
  • Migration status for os-autoinst (4.6.1712854180.1bf07142-4 to 4.6.1731418769.97d9a7fd-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
  • Additional info:
    • Updating os-autoinst will fix bugs in testing: #1093790
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/os-autoinst.html
    • 5 days old (needed 5 days)
• partman-auto (173 to 174)
  • Migration status for partman-auto (173 to 174): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• partman-ext3 (115 to 116)
  • Migration status for partman-ext3 (115 to 116): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• partman-target (130 to 131)
  • Migration status for partman-target (130 to 131): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• phoc (0.45~git+beta1-1 to 0.45~rc1-1)
  • Migration status for phoc (0.45~git+beta1-1 to 0.45~rc1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phoc.html
    • autopkgtest for phoc/0.45~rc1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• pikepdf (9.5.1+dfsg-1 to 9.5.2+dfsg-1)
  • Migration status for pikepdf (9.5.1+dfsg-1 to 9.5.2+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for ocrmypdf/16.7.0+dfsg1-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for pikepdf/9.5.2+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pikepdf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
    • 5 days old (needed 5 days)
• plink2 (2.00~a5.8-231123+dfsg-1 to 2.00~a6.9-250129+dfsg-1)
  • Migration status for plink2 (2.00~a5.8-231123+dfsg-1 to 2.00~a6.9-250129+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plink2.html
    • autopkgtest for plink2/2.00~a6.9-250129+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• procserv (2.7.0-2 to 2.8.0-1)
  • Migration status for procserv (2.7.0-2 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/procserv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• prometheus-snmp-exporter (0.27.0-1 to 0.28.0-1)
  • Migration status for prometheus-snmp-exporter (0.27.0-1 to 0.28.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: prometheus-snmp-exporter golang-1.23
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-snmp-exporter.html
    • autopkgtest for prometheus-snmp-exporter/0.28.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• pydyf (0.11.0-1 to 0.11.0-2)
  • Migration status for pydyf (0.11.0-1 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydyf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-aiosqlite (0.20.0-1 to 0.21.0-1)
  • Migration status for python-aiosqlite (0.20.0-1 to 0.21.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for libervia-backend/0.9.0~hg4332-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for postfix-mta-sts-resolver/1.4.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-aiosqlite/0.21.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-pyomop/4.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiosqlite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-hypothesis (6.124.0-1 to 6.125.2-1)
  • Migration status for python-hypothesis (6.124.0-1 to 6.125.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pandas/2.2.3+dfsg-8: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for python-hypothesis/6.125.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for scipy/1.14.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for sqlfluff/3.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-hypothesis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-pykka (4.0.2-1 to 4.1.1-1)
  • Migration status for python-pykka (4.0.2-1 to 4.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by stein.magnus@jodal.no, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pykka.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-simpy (2.3.1+dfsg-5 to 2.3.1+dfsg-6)
  • Migration status for python-simpy (2.3.1+dfsg-5 to 2.3.1+dfsg-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-simpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• qtwebengine-opensource-src (5.15.17+dfsg2-3 to 5.15.18+dfsg-2)
  • Migration status for qtwebengine-opensource-src (5.15.17+dfsg2-3 to 5.15.18+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: qtwebengine-opensource-src angelfish (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: qtwebengine-opensource-src qtwebview-opensource-src/amd64
    • Implicit dependency: qtwebengine-opensource-src qtwebview-opensource-src/arm64
    • Implicit dependency: qtwebengine-opensource-src qtwebview-opensource-src/armhf
    • Implicit dependency: qtwebengine-opensource-src qtwebview-opensource-src/i386
    • Implicit dependency: qtwebengine-opensource-src qtwebview-opensource-src/mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtwebengine-opensource-src.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• rcs (5.10.1-1 to 5.10.1-2)
  • Migration status for rcs (5.10.1-1 to 5.10.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rcs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-glib-0.18 (0.18.5-3 to 0.18.5-4)
  • Migration status for rust-glib-0.18 (0.18.5-3 to 0.18.5-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating rust-glib-0.18 will fix bugs in testing: #1095190
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-glib-0.18.html
    • autopkgtest for rust-glib-0.18/0.18.5-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Failed (not a regression), s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-safe-arch (0.7.2-2 to 0.7.4-2)
  • Migration status for rust-safe-arch (0.7.2-2 to 0.7.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-safe-arch would introduce bugs in testing: #1092391
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Updating rust-safe-arch will fix bugs in testing: #1093789
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-safe-arch.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 5 days old (needed 5 days)
• rust-socks (0.3.4-5 to 0.3.4-6)
  • Migration status for rust-socks (0.3.4-5 to 0.3.4-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-socks.html
    • autopkgtest for rust-socks/0.3.4-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-sop (0.8.1-1 to 0.8.2-1)
  • Migration status for rust-sop (0.8.1-1 to 0.8.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-sequoia-sop/0.36.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rust-sop/0.8.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-tesseract-sys (0.6.1-4 to 0.6.1-6)
  • Migration status for rust-tesseract-sys (0.6.1-4 to 0.6.1-6): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-tesseract-sys rust-bindgen (not considered)
    • Depends: rust-tesseract-sys rust-bindgen (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tesseract-sys.html
    • autopkgtest for rust-tesseract-sys/0.6.1-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• rust-tonic (0.10.2+dfsg-10 to 0.10.2+dfsg-11)
  • Migration status for rust-tonic (0.10.2+dfsg-10 to 0.10.2+dfsg-11): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tonic.html
    • 5 days old (needed 5 days)
• soundcraft-utils (0.4.0-3 to 0.4.0-4)
  • Migration status for soundcraft-utils (0.4.0-3 to 0.4.0-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/soundcraft-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• suitesparse (1:7.8.3+dfsg-2 to 1:7.8.3+dfsg-3)
  • Migration status for suitesparse (1:7.8.3+dfsg-2 to 1:7.8.3+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for apbs/3.4.1-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for augustus/3.5.0+dfsg-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for ceres-solver/2.2.0+dfsg-4.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for cvxopt/1.3.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-18: amd64: Test in progress, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for dune-istl/2.10.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for dynare/6.2-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for fclib/3.1.0+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for fenics-dolfinx/1:0.9.0-6: amd64: Test in progress, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Test in progress (will not be considered a regression), riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for freefem++/4.14+dfsg-1: amd64: Failed (not a regression), arm64: Pass, armel: Pass, armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for gegl/1:0.4.52-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for glpk/5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for mccs/1:1.1-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for mrcal/2.4.1-4: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for octave/9.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for opm-simulators/2024.10+ds-4: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for opm-upscaling/2024.10+ds-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress
    • autopkgtest for scilab/2024.1.0+dfsg-6: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for suitesparse/1:7.8.3+dfsg-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for sundials/7.1.1+dfsg1-8: amd64: Failed (not a regression), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Updating suitesparse will fix bugs in testing: #1095099
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/suitesparse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• validns (0.8+git20230810.a7e6b4f-1 to 0.8+git20230810.a7e6b4f-2)
  • Migration status for validns (0.8+git20230810.a7e6b4f-1 to 0.8+git20230810.a7e6b4f-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/validns.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• vdr-plugin-live (3.3.7-1 to 3.4.1-1)
  • Migration status for vdr-plugin-live (3.3.7-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdr-plugin-live.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• vdr-plugin-mp3 (0.10.4-2 to 0.10.5-1)
  • Migration status for vdr-plugin-mp3 (0.10.4-2 to 0.10.5-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdr-plugin-mp3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• virtnbdbackup (2.18-1 to 2.20-1)
  • Migration status for virtnbdbackup (2.18-1 to 2.20-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virtnbdbackup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• wireplumber (0.5.7-1 to 0.5.8-1)
  • Migration status for wireplumber (0.5.7-1 to 0.5.8-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wireplumber.html
    • autopkgtest for wireplumber/0.5.8-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• yotta (0.20.5-7 to 0.20.5-8)
  • Migration status for yotta (0.20.5-7 to 0.20.5-8): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yotta.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• zxing-cpp (2.3.0-2 to 2.3.0-3)
  • Migration status for zxing-cpp (2.3.0-2 to 2.3.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for libreoffice/4:24.8.4-2: amd64: Failed (not a regression), arm64: Pass, armel: Test in progress (will not be considered a regression), armhf: Test in progress (will not be considered a regression), i386: Test in progress (will not be considered a regression), ppc64el: Test in progress (will not be considered a regression), riscv64: Pass, s390x: Test in progress
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zxing-cpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• addresses-for-gnustep (0.4.8-6 to 0.4.8-7)
  • Migration status for addresses-for-gnustep (0.4.8-6 to 0.4.8-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: addresses-for-gnustep gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): addresses-for-gnustep gworkspace
  • Additional info:
    • Updating addresses-for-gnustep will fix bugs in testing: #1094005
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/addresses-for-gnustep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• avogadro (- to 1.100.0-2)
  • Migration status for avogadro (- to 1.100.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): avogadro spglib (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): avogadro avogadrolibs
    • Depends: avogadro avogadrolibs
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/avogadro.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• bdebstrap (- to 0.7.0-2)
  • Migration status for bdebstrap (- to 0.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for bdebstrap/0.7.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bdebstrap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• bzrtp (5.2.0-2 to 5.3.104-1)
  • Migration status for bzrtp (5.2.0-2 to 5.3.104-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libbzrtp1/5.3.104-1/amd64 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/amd64 uninstallable
    • migrating libbzrtp1/5.3.104-1/arm64 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/arm64 uninstallable
    • migrating libbzrtp1/5.3.104-1/armel to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/armel uninstallable
    • migrating libbzrtp1/5.3.104-1/armhf to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/armhf uninstallable
    • migrating libbzrtp1/5.3.104-1/i386 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/i386 uninstallable
    • migrating libbzrtp1/5.3.104-1/mips64el to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/mips64el uninstallable
    • migrating libbzrtp1/5.3.104-1/ppc64el to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/ppc64el uninstallable
    • migrating libbzrtp1/5.3.104-1/riscv64 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/riscv64 uninstallable
    • migrating libbzrtp1/5.3.104-1/s390x to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/s390x uninstallable
  • Additional info:
    • Updating bzrtp will fix bugs in testing: #1094083
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bzrtp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• check-all-the-things (- to 2025.02.06)
  • Migration status for check-all-the-things (- to 2025.02.06): 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• cnvkit (0.9.10-2 to 0.9.12-1)
  • Migration status for cnvkit (0.9.10-2 to 0.9.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): cnvkit python-pomegranate (not considered)
    • Depends: cnvkit python-pomegranate (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cnvkit.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for cnvkit/0.9.12-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• fpc (3.2.2+dfsg-40 to 3.2.2+dfsg-45)
  • Migration status for fpc (3.2.2+dfsg-40 to 3.2.2+dfsg-45): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for castle-game-engine/7.0~alpha.3+dfsg1-11: armel: Regression or new test ♻ (reference ♻)
    • autopkgtest for fpc/3.2.2+dfsg-45: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fpc.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Reproducibility regression on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
    • 6 days old (needed 5 days)
• gcc-snapshot (- to 1:20250207-1)
  • Migration status for gcc-snapshot (- to 1:20250207-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-snapshot would introduce bugs in testing: #321449, #651291
    • autopkgtest for gcc-snapshot/1:20250207-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on armel
    • missing build on armhf
    • missing build on riscv64
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-snapshot.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• libjpeg9 (- to 1:9f-2)
  • Migration status for libjpeg9 (- to 1:9f-2): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• libstdc++-riscv64-unknown-elf (- to 4)
  • Migration status for libstdc++-riscv64-unknown-elf (- to 4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/libs/libstdc++-riscv64-unknown-elf.html
    • autopkgtest for libstdc++-riscv64-unknown-elf/4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• lilypond (- to 2.24.4-3)
  • Migration status for lilypond (- to 2.24.4-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lilypond extractpdfmark (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lilypond.html
    • autopkgtest for lilypond/2.24.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• llvm-toolchain-17 (1:17.0.6-20 to 1:17.0.6-21)
  • Migration status for llvm-toolchain-17 (1:17.0.6-20 to 1:17.0.6-21): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-18: amd64: Test in progress, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for fenics-dolfinx/1:0.9.0-6: amd64: Test in progress, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Test in progress (will not be considered a regression), riscv64: Test in progress (will not be considered a regression), s390x: Pass
    • autopkgtest for llvm-toolchain-17/1:17.0.6-21: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Test in progress (will not be considered a regression), riscv64: Failed (not a regression), s390x: Pass
  • Additional info:
    • Updating llvm-toolchain-17 will fix bugs in testing: #1095354
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvm-toolchain-17.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• mediawiki2latex (8.25-3 to 8.26-1)
  • Migration status for mediawiki2latex (8.25-3 to 8.26-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:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mediawiki2latex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• ortp (1:5.2.0-2 to 1:5.3.104-2)
  • Migration status for ortp (1:5.2.0-2 to 1:5.3.104-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libortp16/1:5.3.104-2/amd64 to testing makes libmediastreamer-tools/1:5.2.0+dfsg-4+b4/amd64 uninstallable
    • migrating libortp16/1:5.3.104-2/amd64 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/amd64 uninstallable
    • migrating libortp16/1:5.3.104-2/amd64 to testing makes libosmotrau10/1.6.0-4/amd64 uninstallable
    • migrating libortp16/1:5.3.104-2/amd64 to testing makes mediastreamer2-plugin-msqogl/1:5.2.0+dfsg-4+b4/amd64 uninstallable
    • migrating libortp16/1:5.3.104-2/amd64 to testing makes mediastreamer2-plugin-openh264/5.2.0-2+b4/amd64 uninstallable
    • migrating libortp16/1:5.3.104-2/arm64 to testing makes libmediastreamer-tools/1:5.2.0+dfsg-4+b4/arm64 uninstallable
    • migrating libortp16/1:5.3.104-2/arm64 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/arm64 uninstallable
    • migrating libortp16/1:5.3.104-2/arm64 to testing makes libosmotrau10/1.6.0-4/arm64 uninstallable
    • migrating libortp16/1:5.3.104-2/arm64 to testing makes mediastreamer2-plugin-msqogl/1:5.2.0+dfsg-4+b4/arm64 uninstallable
    • migrating libortp16/1:5.3.104-2/arm64 to testing makes mediastreamer2-plugin-openh264/5.2.0-2+b4/arm64 uninstallable
    • migrating libortp16/1:5.3.104-2/armel to testing makes libmediastreamer-tools/1:5.2.0+dfsg-4+b4/armel uninstallable
    • migrating libortp16/1:5.3.104-2/armel to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/armel uninstallable
    • migrating libortp16/1:5.3.104-2/armel to testing makes libosmotrau10/1.6.0-4/armel uninstallable
    • migrating libortp16/1:5.3.104-2/armel to testing makes mediastreamer2-plugin-msqogl/1:5.2.0+dfsg-4+b4/armel uninstallable
    • migrating libortp16/1:5.3.104-2/armel to testing makes mediastreamer2-plugin-openh264/5.2.0-2+b4/armel uninstallable
    • migrating libortp16/1:5.3.104-2/armhf to testing makes libmediastreamer-tools/1:5.2.0+dfsg-4+b4/armhf uninstallable
    • migrating libortp16/1:5.3.104-2/armhf to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/armhf uninstallable
    • migrating libortp16/1:5.3.104-2/armhf to testing makes libosmotrau10/1.6.0-4/armhf uninstallable
    • migrating libortp16/1:5.3.104-2/armhf to testing makes mediastreamer2-plugin-msqogl/1:5.2.0+dfsg-4+b4/armhf uninstallable
    • migrating libortp16/1:5.3.104-2/armhf to testing makes mediastreamer2-plugin-openh264/5.2.0-2+b4/armhf uninstallable
    • migrating libortp16/1:5.3.104-2/i386 to testing makes libmediastreamer-tools/1:5.2.0+dfsg-4+b4/i386 uninstallable
    • migrating libortp16/1:5.3.104-2/i386 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/i386 uninstallable
    • migrating libortp16/1:5.3.104-2/i386 to testing makes libosmotrau10/1.6.0-4/i386 uninstallable
    • migrating libortp16/1:5.3.104-2/i386 to testing makes mediastreamer2-plugin-msqogl/1:5.2.0+dfsg-4+b4/i386 uninstallable
    • migrating libortp16/1:5.3.104-2/i386 to testing makes mediastreamer2-plugin-openh264/5.2.0-2+b4/i386 uninstallable
    • migrating libortp16/1:5.3.104-2/mips64el to testing makes libmediastreamer-tools/1:5.2.0+dfsg-4+b4/mips64el uninstallable
    • migrating libortp16/1:5.3.104-2/mips64el to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/mips64el uninstallable
    • migrating libortp16/1:5.3.104-2/mips64el to testing makes libosmotrau10/1.6.0-4/mips64el uninstallable
    • migrating libortp16/1:5.3.104-2/mips64el to testing makes mediastreamer2-plugin-msqogl/1:5.2.0+dfsg-4+b4/mips64el uninstallable
    • migrating libortp16/1:5.3.104-2/mips64el to testing makes mediastreamer2-plugin-openh264/5.2.0-2+b4/mips64el uninstallable
    • migrating libortp16/1:5.3.104-2/ppc64el to testing makes libmediastreamer-tools/1:5.2.0+dfsg-4+b4/ppc64el uninstallable
    • migrating libortp16/1:5.3.104-2/ppc64el to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/ppc64el uninstallable
    • migrating libortp16/1:5.3.104-2/ppc64el to testing makes libosmotrau10/1.6.0-4/ppc64el uninstallable
    • migrating libortp16/1:5.3.104-2/ppc64el to testing makes mediastreamer2-plugin-msqogl/1:5.2.0+dfsg-4+b4/ppc64el uninstallable
    • migrating libortp16/1:5.3.104-2/ppc64el to testing makes mediastreamer2-plugin-openh264/5.2.0-2+b4/ppc64el uninstallable
    • migrating libortp16/1:5.3.104-2/riscv64 to testing makes libmediastreamer-tools/1:5.2.0+dfsg-4+b4/riscv64 uninstallable
    • migrating libortp16/1:5.3.104-2/riscv64 to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/riscv64 uninstallable
    • migrating libortp16/1:5.3.104-2/riscv64 to testing makes libosmotrau10/1.6.0-4/riscv64 uninstallable
    • migrating libortp16/1:5.3.104-2/riscv64 to testing makes mediastreamer2-plugin-msqogl/1:5.2.0+dfsg-4+b4/riscv64 uninstallable
    • migrating libortp16/1:5.3.104-2/riscv64 to testing makes mediastreamer2-plugin-openh264/5.2.0-2+b4/riscv64 uninstallable
    • migrating libortp16/1:5.3.104-2/s390x to testing makes libmediastreamer-tools/1:5.2.0+dfsg-4+b4/s390x uninstallable
    • migrating libortp16/1:5.3.104-2/s390x to testing makes libmediastreamer13t64/1:5.2.0+dfsg-4+b4/s390x uninstallable
    • migrating libortp16/1:5.3.104-2/s390x to testing makes mediastreamer2-plugin-msqogl/1:5.2.0+dfsg-4+b4/s390x uninstallable
    • migrating libortp16/1:5.3.104-2/s390x to testing makes mediastreamer2-plugin-openh264/5.2.0-2+b4/s390x uninstallable
  • Additional info:
    • Updating ortp will fix bugs in testing: #1052747
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ortp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• papers (47.3-1 to 48~beta-1)
  • Migration status for papers (47.3-1 to 48~beta-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • papers unsatisfiable Build-Depends(-Arch) on riscv64: libgtk-4-dev (>= 4.17.1)
    • papers unsatisfiable Build-Depends(-Arch) on s390x: libgtk-4-dev (>= 4.17.1)
    • missing build on mips64el
    • missing build on riscv64
    • missing build on s390x
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for papers/48~beta-1: amd64: No tests, superficial or marked flaky ♻, arm64: Test in progress, armel: Test in progress, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): papers gtk4 (not considered)
    • Depends: papers gtk4 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/papers.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• pyfftw (- to 0.15.0-1)
  • Migration status for pyfftw (- to 0.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pyfftw/0.15.0-1: amd64: Pass, arm64: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): pyfftw numpy (not considered)
    • Depends: pyfftw numpy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfftw.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• python-pomegranate (0.14.8-7 to 0.15.0-1)
  • Migration status for python-pomegranate (0.14.8-7 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): python-pomegranate numpy (not considered)
    • Depends: python-pomegranate numpy (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Updating python-pomegranate will fix bugs in testing: #1094703
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pomegranate.html
    • autopkgtest for python-pomegranate/0.15.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• rdma-core (55.0-1 to 56.0-1)
  • Migration status for rdma-core (55.0-1 to 56.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ibsim/0.10-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rdma-core.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 6 days old (needed 5 days)
• rust-futures-timer (3.0.3-3 to 3.0.3-4)
  • Migration status for rust-futures-timer (3.0.3-3 to 3.0.3-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-futures-timer.html
    • autopkgtest for rust-futures-timer/3.0.3-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• rust-hstr (- to 0+20250106-2)
  • Migration status for rust-hstr (- to 0+20250106-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-hstr/0+20250106-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hstr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• rust-hyper-rustls (0.24.2-4 to 0.24.2-5)
  • Migration status for rust-hyper-rustls (0.24.2-4 to 0.24.2-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hyper-rustls.html
    • autopkgtest for rust-hyper-rustls/0.24.2-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• rust-leptonica-sys (0.4.9-2 to 0.4.9-4)
  • Migration status for rust-leptonica-sys (0.4.9-2 to 0.4.9-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-leptonica-sys rust-bindgen (not considered)
    • Depends: rust-leptonica-sys rust-bindgen (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-leptonica-sys.html
    • autopkgtest for rust-leptonica-sys/0.4.9-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• sep (1.2.1-8 to 1.4.0-1)
  • Migration status for sep (1.2.1-8 to 1.4.0-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 sep/1.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• sosreport (4.8.2-2 to 4.8.2-3)
  • Migration status for sosreport (4.8.2-2 to 4.8.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sosreport has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• steptalk (0.10.0+git20200629-2 to 0.10.0+git20200629-3)
  • Migration status for steptalk (0.10.0+git20200629-2 to 0.10.0+git20200629-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: steptalk gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): steptalk gnustep-dl2 (not considered)
    • Build-Depends(-Arch): steptalk gnustep-gui (not considered)
    • Build-Depends(-Arch): steptalk gnustep-sqlclient
  • Additional info:
    • Updating steptalk will fix bugs in testing: #1094006
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/steptalk.html
    • autopkgtest for steptalk/0.10.0+git20200629-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• textedit.app (5.0-4 to 5.0-5)
  • Migration status for textedit.app (5.0-4 to 5.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: textedit.app gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): textedit.app gnustep-gui (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/textedit.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• tml (0.6.0-1 to 0.7.0-1)
  • Migration status for tml (0.6.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: tml golang-1.23
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tml.html
    • autopkgtest for tml/0.7.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
• avogadrolibs (- to 1.100.0-1)
  • Migration status for avogadrolibs (- to 1.100.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): avogadrolibs spglib (not considered)
    • Depends: avogadrolibs spglib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/avogadrolibs.html
    • autopkgtest for avogadrolibs/1.100.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• bbswitch (0.8-15 to 0.8-16)
  • Migration status for bbswitch (0.8-15 to 0.8-16): 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 bbswitch/0.8-16: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bbswitch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 7 days old (needed 5 days)
• checkpolicy (3.7-1 to 3.8-1)
  • Migration status for checkpolicy (3.7-1 to 3.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• chromium (132.0.6834.159-1 to 133.0.6943.53-1)
  • Migration status for chromium (132.0.6834.159-1 to 133.0.6943.53-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chromium.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 7 days old (needed 2 days)
• libsepol (3.7-1 to 3.8-1)
  • Migration status for libsepol (3.7-1 to 3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for refpolicy/2:2.20250115-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsepol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• mcstrans (3.7-2 to 3.8-1)
  • Migration status for mcstrans (3.7-2 to 3.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mcstrans libsepol (not considered)
    • Built-Using: mcstrans libsepol (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Build-Depends(-Arch): mcstrans libselinux (not considered)
    • Depends: mcstrans libselinux (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mcstrans.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• media-types (10.1.0 to 11.0.0)
  • Migration status for media-types (10.1.0 to 11.0.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lighttpd/1.4.77-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/media-types.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• r-cran-hardhat (1.4.0+dfsg-1 to 1.4.1+dfsg-1)
  • Migration status for r-cran-hardhat (1.4.0+dfsg-1 to 1.4.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • r-cran-hardhat unsatisfiable Build-Depends(-Arch) on amd64: r-cran-sparsevctrs
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-hardhat.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 7 days old (needed 5 days)
• restorecond (3.7-1 to 3.8-1)
  • Migration status for restorecond (3.7-1 to 3.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• rust-clio (0.3.5-4 to 0.3.5-5)
  • Migration status for rust-clio (0.3.5-4 to 0.3.5-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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-clio.html
    • 7 days old (needed 5 days)
• secilc (3.7-1 to 3.8-1)
  • Migration status for secilc (3.7-1 to 3.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 7 days old (needed 5 days)
• semodule-utils (3.7-1 to 3.8-1)
  • Migration status for semodule-utils (3.7-1 to 3.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• smlsharp (- to 4.1.0-1)
  • Migration status for smlsharp (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smlsharp would introduce bugs in testing: #1071781
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smlsharp.html
    • Reproducible on amd64 - info ♻
    • 7 days old (needed 5 days)
• unicycler (- to 0.5.1+dfsg-3)
  • Migration status for unicycler (- to 0.5.1+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): unicycler pilon (not considered)
    • Depends: unicycler pilon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unicycler.html
    • autopkgtest for unicycler/0.5.1+dfsg-3: amd64: Pass
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• vpb-driver (4.2.61-1.6 to 4.2.61-1.7)
  • Migration status for vpb-driver (4.2.61-1.6 to 4.2.61-1.7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for vpb-driver/4.2.61-1.7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vpb-driver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• cura (- to 5.0.0-6)
  • Migration status for cura (- to 5.0.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: cura trimesh (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cura.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• firefox (- to 135.0-1)
  • Migration status for firefox (- to 135.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating firefox would introduce bugs in testing: #1017919, #817954, #992263, #993659
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firefox.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• linuxtv-dvb-apps (- to 1.1.1+rev1500-2)
  • Migration status for linuxtv-dvb-apps (- to 1.1.1+rev1500-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/l/linuxtv-dvb-apps.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• lomiri-online-accounts-plugins (- to 0.19-1)
  • Migration status for lomiri-online-accounts-plugins (- to 0.19-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lomiri-online-accounts-plugins lomiri-system-settings-online-accounts (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lomiri-online-accounts-plugins.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• paje.app (1.98-1.2 to 1.98-2)
  • Migration status for paje.app (1.98-1.2 to 1.98-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: paje.app gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): paje.app gnustep-gui (not considered)
  • Additional info:
    • Updating paje.app will fix bugs in testing: #1094312
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paje.app.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 8 days old (needed 5 days)
• pcre2 (10.44-5 to 10.45-1)
  • Migration status for pcre2 (10.44-5 to 10.45-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mariadb/1:11.4.4-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcre2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• python-aioraven (- to 0.7.0-1)
  • Migration status for python-aioraven (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-aioraven/amd64 has unsatisfiable dependency
    • python3-aioraven/arm64 has unsatisfiable dependency
    • python-aioraven unsatisfiable Build-Depends-Indep on amd64: python3-iso4217
    • Not built on buildd: arch all binaries uploaded by zigo, 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-aioraven.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• python-aioswitcher (- to 4.0.2-1)
  • Migration status for python-aioswitcher (- to 4.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
    • Build-Depends-Indep: python-aioswitcher python-assertpy (not considered)
    • Build-Depends-Indep: python-aioswitcher python-pytest-resource-path (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioswitcher.html
    • autopkgtest for python-aioswitcher/4.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• python-assertpy (- to 1.1-1)
  • Migration status for python-assertpy (- to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-assertpy.html
    • autopkgtest for python-assertpy/1.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• python-buienradar (- to 1.0.6-1)
  • Migration status for python-buienradar (- to 1.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-buienradar.html
    • autopkgtest for python-buienradar/1.0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• python-pytest-resource-path (- to 1.3.0-1)
  • Migration status for python-pytest-resource-path (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pytest-resource-path.html
    • autopkgtest for python-pytest-resource-path/1.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• r-cran-sparr (2.3-10-1 to 2.3-15-1)
  • Migration status for r-cran-sparr (2.3-10-1 to 2.3-15-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/r/r-cran-sparr.html
    • 8 days old (needed 5 days)
• ruby-puppetlabs-spec-helper (- to 8.0.0-1)
  • Migration status for ruby-puppetlabs-spec-helper (- to 8.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-puppetlabs-spec-helper would introduce bugs in testing: #1092699
    • Build-Depends(-Arch): ruby-puppetlabs-spec-helper ruby-puppet-syntax (not considered)
    • Depends: ruby-puppetlabs-spec-helper ruby-puppet-syntax (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-puppetlabs-spec-helper.html
    • autopkgtest for ruby-puppetlabs-spec-helper/8.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• rust-aya-obj (- to 0.2.1-1)
  • Migration status for rust-aya-obj (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-aya-obj/0.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-aya-obj.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 8 days old (needed 5 days)
• rust-ntp-proto (1.1.3-1 to 1.4.0-2)
  • Migration status for rust-ntp-proto (1.1.3-1 to 1.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-ntp-proto-dev/amd64 has unsatisfiable dependency
    • librust-ntp-proto-dev/arm64 has unsatisfiable dependency
    • librust-ntp-proto-dev/armel has unsatisfiable dependency
    • librust-ntp-proto-dev/armhf has unsatisfiable dependency
    • librust-ntp-proto-dev/i386 has unsatisfiable dependency
    • librust-ntp-proto-dev/mips64el has unsatisfiable dependency
    • librust-ntp-proto-dev/ppc64el has unsatisfiable dependency
    • librust-ntp-proto-dev/riscv64 has unsatisfiable dependency
    • librust-ntp-proto-dev/s390x has unsatisfiable dependency
    • migrating librust-ntp-proto-dev/1.4.0-2/amd64 to testing makes librust-ntp-os-clock-dev/1.1.3-2/amd64 uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/amd64 to testing makes librust-ntp-udp-dev/1.1.3-2/amd64 uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/arm64 to testing makes librust-ntp-os-clock-dev/1.1.3-2/arm64 uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/arm64 to testing makes librust-ntp-udp-dev/1.1.3-2/arm64 uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/armel to testing makes librust-ntp-os-clock-dev/1.1.3-2/armel uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/armel to testing makes librust-ntp-udp-dev/1.1.3-2/armel uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/armhf to testing makes librust-ntp-os-clock-dev/1.1.3-2/armhf uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/armhf to testing makes librust-ntp-udp-dev/1.1.3-2/armhf uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/i386 to testing makes librust-ntp-os-clock-dev/1.1.3-2/i386 uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/i386 to testing makes librust-ntp-udp-dev/1.1.3-2/i386 uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/mips64el to testing makes librust-ntp-os-clock-dev/1.1.3-2/mips64el uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/mips64el to testing makes librust-ntp-udp-dev/1.1.3-2/mips64el uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/ppc64el to testing makes librust-ntp-os-clock-dev/1.1.3-2/ppc64el uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/ppc64el to testing makes librust-ntp-udp-dev/1.1.3-2/ppc64el uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/riscv64 to testing makes librust-ntp-os-clock-dev/1.1.3-2/riscv64 uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/riscv64 to testing makes librust-ntp-udp-dev/1.1.3-2/riscv64 uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/s390x to testing makes librust-ntp-os-clock-dev/1.1.3-2/s390x uninstallable
    • migrating librust-ntp-proto-dev/1.4.0-2/s390x to testing makes librust-ntp-udp-dev/1.1.3-2/s390x uninstallable
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-ntp-proto.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• rust-sha256 (- to 1.5.0-3)
  • Migration status for rust-sha256 (- to 1.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-sha256/1.5.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sha256.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• scrcpy (- to 1.25-1.1)
  • Migration status for scrcpy (- to 1.25-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for scrcpy/1.25-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends-Indep: scrcpy android-framework-23 (not considered)
    • Build-Depends-Indep: scrcpy android-platform-dalvik
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scrcpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• trimesh (- to 4.5.1-2)
  • Migration status for trimesh (- to 4.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): trimesh python-beartype (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): trimesh pycollada
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trimesh.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 8 days old (needed 5 days)
• tzdata (2024b-6 to 2025a-2)
  • Migration status for tzdata (2024b-6 to 2025a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for postgresql-17/17.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for tzdata/2025a-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tzdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• vedo (- to 2025.5.3-1)
  • Migration status for vedo (- to 2025.5.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vedo.html
    • autopkgtest for vedo/2025.5.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• yard (0.9.36-1 to 0.9.37-1)
  • Migration status for yard (0.9.36-1 to 0.9.37-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating yard/0.9.37-1/amd64 to testing makes puppet-strings/4.1.3-1/amd64 uninstallable
    • migrating yard/0.9.37-1/arm64 to testing makes puppet-strings/4.1.3-1/arm64 uninstallable
  • Additional info:
    • Updating yard will fix bugs in testing: #1094556
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yard.html
    • autopkgtest for yard/0.9.37-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• cod-tools (- to 3.10.0+dfsg-3)
  • Migration status for cod-tools (- to 3.10.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): cod-tools spglib (not considered)
    • Depends: cod-tools spglib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cod-tools.html
    • autopkgtest for cod-tools/3.10.0+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• elixir-earmark-parser (- to 1.4.43-1)
  • Migration status for elixir-earmark-parser (- to 1.4.43-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • elixir-earmark-parser unsatisfiable Build-Depends(-Arch) on mips64el: elixir (>= 1.18)
    • missing build on mips64el
    • Build-Depends(-Arch): elixir-earmark-parser elixir-lang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elixir-earmark-parser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• elixir-makeup-erlang (- to 1.0.2-1)
  • Migration status for elixir-makeup-erlang (- to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • elixir-makeup-erlang unsatisfiable Build-Depends(-Arch) on mips64el: elixir (>= 1.18)
    • missing build on mips64el
    • Build-Depends(-Arch): elixir-makeup-erlang elixir-lang (not considered)
    • Build-Depends(-Arch): elixir-makeup-erlang elixir-makeup (not considered)
    • Depends: elixir-makeup-erlang elixir-makeup (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elixir-makeup-erlang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• gworkspace (1.0.0-4 to 1.0.0-5)
  • Migration status for gworkspace (1.0.0-4 to 1.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gworkspace gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): gworkspace gnustep-gui (not considered)
    • Build-Depends(-Arch): gworkspace systempreferences.app
  • Additional info:
    • Updating gworkspace will fix bugs in testing: #1094003
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gworkspace.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• hurd (- to 1:0.9.git20241227-4)
  • Migration status for hurd (- to 1:0.9.git20241227-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hurd would introduce bugs in testing: #838244
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libc0.3-dev (>= 2.33-2~1)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-disk-dev (>= 0~20211031-2)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-usb-dev
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libacpica-dev
    • Not 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
    • 9 days old (needed 5 days)
• libsdl3-ttf (- to 3.1.0+ds-1)
  • Migration status for libsdl3-ttf (- to 3.1.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libsdl3-ttf would introduce bugs in testing: #1095059
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsdl3-ttf.html
    • autopkgtest for libsdl3-ttf/3.1.0+ds-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• moarvm (2024.09+dfsg-3 to 2024.09+dfsg-4)
  • Migration status for moarvm (2024.09+dfsg-3 to 2024.09+dfsg-4): 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
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/moarvm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-460 (- to 460.106.00-19)
  • Migration status for nvidia-graphics-drivers-tesla-460 (- to 460.106.00-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-tesla-460 would introduce bugs in testing: #1027704
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-tesla-460/460.106.00-19: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • 9 days old (needed 5 days)
• oakleaf (0.0.1-3 to 1.0.0-1)
  • Migration status for oakleaf (0.0.1-3 to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oakleaf would introduce bugs in testing: #1095650
    • Not built on buildd: arch amd64 binaries uploaded by debian@liska.ath.cx
    • Not built on buildd: arch all binaries uploaded by debian@liska.ath.cx, a new source-only upload is needed to allow migration
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for oakleaf/1.0.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 9 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oakleaf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• reform-handbook (- to 2024-08-19+dfsg-2)
  • Migration status for reform-handbook (- to 2024-08-19+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by josch, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/reform-handbook.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• rsass (0.28.10-6 to 0.29.0-1)
  • Migration status for rsass (0.28.10-6 to 0.29.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rsass/0.29.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • missing build on i386
    • missing build on mips64el
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsass.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 9 days old (needed 5 days)
• tmuxp (1.50.1-1 to 1.52.2-1)
  • Migration status for tmuxp (1.50.1-1 to 1.52.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tmuxp python-libtmux (not considered)
    • Depends: tmuxp python-libtmux (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tmuxp.html
    • autopkgtest for tmuxp/1.52.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• wings3d (- to 2.4.1-1)
  • Migration status for wings3d (- to 2.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • wings3d unsatisfiable Build-Depends(-Arch) on mips64el: erlang-dev (>= 1:27)
    • missing build on mips64el
    • Build-Depends(-Arch): wings3d erlang (not considered)
    • Depends: wings3d erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wings3d.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• bluez-alsa (4.2.0-1 to 4.3.1-2)
  • Migration status for bluez-alsa (4.2.0-1 to 4.3.1-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bluez-alsa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• cenon.app (4.0.6+ds1-4 to 4.0.6+ds1-5)
  • Migration status for cenon.app (4.0.6+ds1-4 to 4.0.6+ds1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: cenon.app gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): cenon.app gnustep-gui (not considered)
  • Additional info:
    • Updating cenon.app will fix bugs in testing: #1093983
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cenon.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• charmap.app (0.3~rc1-5 to 0.3~rc1-6)
  • Migration status for charmap.app (0.3~rc1-5 to 0.3~rc1-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: charmap.app gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): charmap.app gnustep-gui (not considered)
  • Additional info:
    • Updating charmap.app will fix bugs in testing: #1093985
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/charmap.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• draai (20201215-2 to 20250202-1)
  • Migration status for draai (20201215-2 to 20250202-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/draai.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 10 days)
• fai (6.2.5 to 6.2.6)
  • Migration status for fai (6.2.5 to 6.2.6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fai.html
    • autopkgtest for fai/6.2.6: amd64: Failed (not a regression), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 10 days)
• gnustep-sqlclient (1.9.0-3 to 1.9.0-4)
  • Migration status for gnustep-sqlclient (1.9.0-3 to 1.9.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-sqlclient gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): gnustep-sqlclient gnustep-base
    • Build-Depends(-Arch): gnustep-sqlclient gnustep-performance
  • Additional info:
    • Updating gnustep-sqlclient will fix bugs in testing: #1093988
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnustep-sqlclient.html
    • autopkgtest for gnustep-sqlclient/1.9.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• gomoku.app (1.2.9-6 to 1.2.9-7)
  • Migration status for gomoku.app (1.2.9-6 to 1.2.9-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gomoku.app gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): gomoku.app gnustep-gui (not considered)
  • Additional info:
    • Updating gomoku.app will fix bugs in testing: #1093989
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gomoku.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• graph-tool (- to 2.88+ds-1)
  • Migration status for graph-tool (- to 2.88+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on riscv64
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graph-tool.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 10 days old (needed 5 days)
• grr.app (1.0-2 to 1.0-3)
  • Migration status for grr.app (1.0-2 to 1.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: grr.app gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): grr.app gnustep-gui (not considered)
    • Build-Depends(-Arch): grr.app rsskit
  • Additional info:
    • Updating grr.app will fix bugs in testing: #1093991
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grr.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• kxml2 (2.3.0+ds1-2.1 to 2.3.0+ds1-3)
  • Migration status for kxml2 (2.3.0+ds1-2.1 to 2.3.0+ds1-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kxml2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 10 days)
• libpulp (- to 0.2.8-1)
  • Migration status for libpulp (- to 0.2.8-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpulp.html
    • 10 days old (needed 10 days)
• libqt5xdg (- to 3.12.0-2)
  • Migration status for libqt5xdg (- to 3.12.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): libqt5xdg lxqt-build-tools-qt5 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libq/libqt5xdg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• logwatch (7.7-1 to 7.12-2)
  • Migration status for logwatch (7.7-1 to 7.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for logwatch/7.12-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Updating logwatch will fix bugs in testing: #1095242
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/logwatch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• lynkeos.app (3.7+dfsg-5 to 3.7+dfsg-6)
  • Migration status for lynkeos.app (3.7+dfsg-5 to 3.7+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lynkeos.app gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): lynkeos.app gnustep-corebase
    • Build-Depends(-Arch): lynkeos.app gnustep-gui (not considered)
  • Additional info:
    • Updating lynkeos.app will fix bugs in testing: #1093992
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lynkeos.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-450 (- to 450.248.02-9)
  • Migration status for nvidia-graphics-drivers-tesla-450 (- to 450.248.02-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-tesla-450 would introduce bugs in testing: #1014304
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-tesla-450/450.248.02-9: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • 10 days old (needed 5 days)
• phonopy (- to 2.35.0-1)
  • Migration status for phonopy (- to 2.35.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): phonopy spglib (not considered)
    • Depends: phonopy spglib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phonopy.html
    • autopkgtest for phonopy/2.35.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• r-cran-testthat (3.2.1.1-1 to 3.2.3-1)
  • Migration status for r-cran-testthat (3.2.1.1-1 to 3.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-googledrive/2.1.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-hdf5r/1.3.12+dfsg-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression)
    • autopkgtest for r-cran-plotly/4.10.4+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for r-cran-rcmdcheck/1.4.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-s2/1.1.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • autopkgtest for r-cran-sessioninfo/1.2.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-shiny/1.10.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-testthat/3.2.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for r-cran-waldo/0.6.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-testthat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• r-cran-vegan (2.6-8+dfsg-1 to 2.6-10+dfsg-1)
  • Migration status for r-cran-vegan (2.6-8+dfsg-1 to 2.6-10+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-vegan/2.6-10+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-vegan.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• sympy (1.13.3-1 to 1.13.3-2)
  • Migration status for sympy (1.13.3-1 to 1.13.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sympy would introduce bugs in testing: #1095778
    • autopkgtest for sympy/1.13.3-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sympy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• systempreferences.app (1.2.1-1 to 1.2.1-2)
  • Migration status for systempreferences.app (1.2.1-1 to 1.2.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: systempreferences.app gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): systempreferences.app gnustep-gui (not considered)
  • Additional info:
    • Updating systempreferences.app will fix bugs in testing: #1093995
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/systempreferences.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• td1.8.11 (- to 1.8.11~git20230202.3179d35+dfsg-3)
  • Migration status for td1.8.11 (- to 1.8.11~git20230202.3179d35+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: td1.8.11 td (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/td1.8.11.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• unar (1.10.8+ds1-6 to 1.10.8+ds1-7)
  • Migration status for unar (1.10.8+ds1-6 to 1.10.8+ds1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): unar gnustep-base (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): unar universal-detector
  • Additional info:
    • Updating unar will fix bugs in testing: #1093997
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unar.html
    • autopkgtest for unar/1.10.8+ds1-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• at-spi2-core (2.55.0.1-1 to 2.55.2-1)
  • Migration status for at-spi2-core (2.55.0.1-1 to 2.55.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/at-spi2-core.html
    • autopkgtest for at-spi2-core/2.55.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 11 days old (needed 2 days)
• erlang-bbmustache (- to 1.12.2-1)
  • Migration status for erlang-bbmustache (- to 1.12.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating erlang-bbmustache would introduce bugs in testing: #1090216
    • Depends: erlang-bbmustache erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-bbmustache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 11 days old (needed 5 days)
• exchange-calendars (4.8-1 to 4.9-1)
  • Migration status for exchange-calendars (4.8-1 to 4.9-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/e/exchange-calendars.html
    • 11 days old (needed 5 days)
• sope (5.11.1-1 to 5.11.1-2)
  • Migration status for sope (5.11.1-1 to 5.11.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sope gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): sope gnustep-base
  • Additional info:
    • Updating sope will fix bugs in testing: #1094178
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sope.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 11 days old (needed 5 days)
• virtualbox (- to 7.0.20-dfsg-1.2)
  • Migration status for virtualbox (- to 7.0.20-dfsg-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtualbox would introduce bugs in testing: #1085440, #1093879, #794466
    • autopkgtest for virtualbox/7.0.20-dfsg-1.2: amd64: No tests, superficial or marked flaky ♻, i386: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 11 days old (needed 5 days)
• bornagain (- to 22~git20250131135257.50eb7b6+ds3-3)
  • Migration status for bornagain (- to 22~git20250131135257.50eb7b6+ds3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bornagain would introduce bugs in testing: #1092071, #1092152
    • bornagain unsatisfiable Build-Depends(-Arch) on s390x: python3-fabio
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • 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/b/bornagain.html
    • 12 days old (needed 5 days)
• dante (- to 1.4.3+dfsg-3)
  • Migration status for dante (- to 1.4.3+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dante would introduce bugs in testing: #1067709
    • autopkgtest for dante/1.4.3+dfsg-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dante.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• gumbo-parser (0.12.0+dfsg-2 to 0.13.0+dfsg-2)
  • Migration status for gumbo-parser (0.12.0+dfsg-2 to 0.13.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libhtml-gumbo-perl/0.18-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating gumbo-parser will fix bugs in testing: #1093481
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gumbo-parser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• lomiri (- to 0.3.0-4)
  • Migration status for lomiri (- to 0.3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lomiri lomiri-indicator-network (not considered)
    • Depends: lomiri lomiri-indicator-network (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): lomiri lomiri-system-settings
    • Depends: lomiri lomiri-system-settings
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• python-ansible-compat (24.10.0-1 to 25.1.1-1)
  • Migration status for python-ansible-compat (24.10.0-1 to 25.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ansible-lint/24.10.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-ansible-compat/25.1.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ansible-compat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• r-cran-seurat (- to 5.2.1-3)
  • Migration status for r-cran-seurat (- to 5.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-seurat would introduce bugs in testing: #1091919
    • autopkgtest for r-cran-seurat/5.2.1-3: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-seurat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-capstone-sys (0.15.0-3 to 0.15.0-4)
  • Migration status for rust-capstone-sys (0.15.0-3 to 0.15.0-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-capstone-sys rust-bindgen (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-capstone-sys.html
    • autopkgtest for rust-capstone-sys/0.15.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• bind9 (1:9.20.4-4 to 1:9.20.5-1)
  • Migration status for bind9 (1:9.20.4-4 to 1:9.20.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for bind9/1:9.20.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for prometheus-dnsmasq-exporter/0.3.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for resource-agents/1:4.16.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating bind9 will fix bugs in testing: #1094735
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bind9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• brickos (- to 0.9.0.dfsg-13)
  • Migration status for brickos (- to 0.9.0.dfsg-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): brickos gcc-h8300-hms (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): brickos binutils-h8300-hms (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/brickos.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• haskell-regex (- to 1.1.0.2-2)
  • Migration status for haskell-regex (- to 1.1.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-regex-dev/amd64 has unsatisfiable dependency
    • libghc-regex-dev/arm64 has unsatisfiable dependency
    • libghc-regex-dev/armel has unsatisfiable dependency
    • libghc-regex-dev/armhf has unsatisfiable dependency
    • libghc-regex-dev/i386 has unsatisfiable dependency
    • libghc-regex-dev/mips64el has unsatisfiable dependency
    • libghc-regex-dev/ppc64el has unsatisfiable dependency
    • libghc-regex-dev/riscv64 has unsatisfiable dependency
    • libghc-regex-dev/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): haskell-regex haskell-regex-pcre (not considered)
    • Build-Depends-Indep: haskell-regex haskell-regex-pcre (not considered)
    • Depends: haskell-regex haskell-regex-pcre (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-regex.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• lomiri-system-settings-cellular (- to 1.1-1)
  • Migration status for lomiri-system-settings-cellular (- 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(-Arch): lomiri-system-settings-cellular lomiri-system-settings (not considered)
    • Depends: lomiri-system-settings-cellular lomiri-system-settings (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-system-settings-cellular.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• lomiri-system-settings-phone (- to 1.1-1)
  • Migration status for lomiri-system-settings-phone (- 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(-Arch): lomiri-system-settings-phone lomiri-system-settings (not considered)
    • Depends: lomiri-system-settings-phone lomiri-system-settings (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-system-settings-phone.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• lomiri-teleports-app (- to 1.20-5)
  • Migration status for lomiri-teleports-app (- to 1.20-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lomiri-teleports-app td1.8.11 (not considered)
    • Depends: lomiri-teleports-app td1.8.11 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: lomiri-teleports-app lomiri-push-qml
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-teleports-app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-535 (- to 535.216.01-1)
  • Migration status for nvidia-graphics-drivers-tesla-535 (- to 535.216.01-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-tesla-535 would introduce bugs in testing: #1093917
    • Depends: nvidia-graphics-drivers-tesla-535 nvidia-settings-tesla-535
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-tesla-535/535.216.01-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • 13 days old (needed 5 days)
• nvidia-settings-tesla-535 (- to 535.216.01-1)
  • Migration status for nvidia-settings-tesla-535 (- to 535.216.01-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-tesla-535 nvidia-graphics-drivers-tesla-535 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 13 days old (needed 5 days)
• openafs (- to 1.8.13.2-1)
  • Migration status for openafs (- to 1.8.13.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for openafs/1.8.13.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: Regression or new test ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openafs.html
    • Reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• r-cran-effectsize (- to 1.0.0+dfsg-1)
  • Migration status for r-cran-effectsize (- to 1.0.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-effectsize/1.0.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): r-cran-effectsize r-cran-bayestestr (not considered)
    • Build-Depends(-Arch): r-cran-effectsize r-cran-parameters
    • Build-Depends(-Arch): r-cran-effectsize r-cran-performance (not considered)
    • Depends: r-cran-effectsize r-cran-bayestestr (not considered)
    • Depends: r-cran-effectsize r-cran-parameters
    • Depends: r-cran-effectsize r-cran-performance (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-effectsize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• r-cran-irace (3.5-2 to 4.1-1)
  • Migration status for r-cran-irace (3.5-2 to 4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • r-cran-irace unsatisfiable Build-Depends(-Arch) on s390x: r-cran-spacefillr
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for r-cran-irace/4.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Build-Depends(-Arch): r-cran-irace r-cran-spacefillr
    • Depends: r-cran-irace r-cran-spacefillr
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-irace.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 13 days old (needed 5 days)
• r-cran-spatstat.explore (3.2-7-1 to 3.3-4-1)
  • Migration status for r-cran-spatstat.explore (3.2-7-1 to 3.3-4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on amd64: r-cran-spatstat.geom (>= 3.3-2)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on amd64: r-cran-spatstat.random (>= 3.3-1)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on amd64: r-cran-spatstat.univar
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on arm64: r-cran-spatstat.geom (>= 3.3-2)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on arm64: r-cran-spatstat.random (>= 3.3-1)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on arm64: r-cran-spatstat.univar
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on armel: r-cran-spatstat.geom (>= 3.3-2)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on armel: r-cran-spatstat.random (>= 3.3-1)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on armel: r-cran-spatstat.univar
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on armhf: r-cran-spatstat.geom (>= 3.3-2)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on armhf: r-cran-spatstat.random (>= 3.3-1)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on armhf: r-cran-spatstat.univar
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on i386: r-cran-spatstat.geom (>= 3.3-2)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on i386: r-cran-spatstat.random (>= 3.3-1)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on i386: r-cran-spatstat.univar
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on mips64el: r-cran-spatstat.geom (>= 3.3-2)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on mips64el: r-cran-spatstat.random (>= 3.3-1)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on mips64el: r-cran-spatstat.univar
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on ppc64el: r-cran-spatstat.geom (>= 3.3-2)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on ppc64el: r-cran-spatstat.random (>= 3.3-1)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on ppc64el: r-cran-spatstat.univar
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on riscv64: r-cran-spatstat.geom (>= 3.3-2)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on riscv64: r-cran-spatstat.random (>= 3.3-1)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on riscv64: r-cran-spatstat.univar
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on s390x: r-cran-spatstat.geom (>= 3.3-2)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on s390x: r-cran-spatstat.random (>= 3.3-1)
    • r-cran-spatstat.explore unsatisfiable Build-Depends(-Arch) on s390x: r-cran-spatstat.univar
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 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/r/r-cran-spatstat.explore.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 13 days old (needed 5 days)
• r-cran-spatstat.geom (3.2-9-2 to 3.3-5-1)
  • Migration status for r-cran-spatstat.geom (3.2-9-2 to 3.3-5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • r-cran-spatstat.geom unsatisfiable Build-Depends(-Arch) on amd64: r-cran-spatstat.univar
    • r-cran-spatstat.geom unsatisfiable Build-Depends(-Arch) on arm64: r-cran-spatstat.univar
    • r-cran-spatstat.geom unsatisfiable Build-Depends(-Arch) on armel: r-cran-spatstat.univar
    • r-cran-spatstat.geom unsatisfiable Build-Depends(-Arch) on armhf: r-cran-spatstat.univar
    • r-cran-spatstat.geom unsatisfiable Build-Depends(-Arch) on i386: r-cran-spatstat.univar
    • r-cran-spatstat.geom unsatisfiable Build-Depends(-Arch) on mips64el: r-cran-spatstat.univar
    • r-cran-spatstat.geom unsatisfiable Build-Depends(-Arch) on ppc64el: r-cran-spatstat.univar
    • r-cran-spatstat.geom unsatisfiable Build-Depends(-Arch) on riscv64: r-cran-spatstat.univar
    • r-cran-spatstat.geom unsatisfiable Build-Depends(-Arch) on s390x: r-cran-spatstat.univar
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 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/r/r-cran-spatstat.geom.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 13 days old (needed 5 days)
• r-cran-spatstat.model (3.2-11-1 to 3.3-4-1)
  • Migration status for r-cran-spatstat.model (3.2-11-1 to 3.3-4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on amd64: r-cran-spatstat.geom (>= 3.3-4)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on amd64: r-cran-spatstat.random (>= 3.3-2)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on amd64: r-cran-spatstat.explore (>= 3.3-0)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on arm64: r-cran-spatstat.geom (>= 3.3-4)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on arm64: r-cran-spatstat.random (>= 3.3-2)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on arm64: r-cran-spatstat.explore (>= 3.3-0)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on armel: r-cran-spatstat.geom (>= 3.3-4)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on armel: r-cran-spatstat.random (>= 3.3-2)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on armel: r-cran-spatstat.explore (>= 3.3-0)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on armhf: r-cran-spatstat.geom (>= 3.3-4)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on armhf: r-cran-spatstat.random (>= 3.3-2)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on armhf: r-cran-spatstat.explore (>= 3.3-0)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on i386: r-cran-spatstat.geom (>= 3.3-4)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on i386: r-cran-spatstat.random (>= 3.3-2)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on i386: r-cran-spatstat.explore (>= 3.3-0)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on mips64el: r-cran-spatstat.geom (>= 3.3-4)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on mips64el: r-cran-spatstat.random (>= 3.3-2)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on mips64el: r-cran-spatstat.explore (>= 3.3-0)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on ppc64el: r-cran-spatstat.geom (>= 3.3-4)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on ppc64el: r-cran-spatstat.random (>= 3.3-2)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on ppc64el: r-cran-spatstat.explore (>= 3.3-0)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on riscv64: r-cran-spatstat.geom (>= 3.3-4)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on riscv64: r-cran-spatstat.random (>= 3.3-2)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on riscv64: r-cran-spatstat.explore (>= 3.3-0)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on s390x: r-cran-spatstat.geom (>= 3.3-4)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on s390x: r-cran-spatstat.random (>= 3.3-2)
    • r-cran-spatstat.model unsatisfiable Build-Depends(-Arch) on s390x: r-cran-spatstat.explore (>= 3.3-0)
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 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/r/r-cran-spatstat.model.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 13 days old (needed 5 days)
• r-cran-spatstat.random (3.2-3-1 to 3.3-2-1)
  • Migration status for r-cran-spatstat.random (3.2-3-1 to 3.3-2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • r-cran-spatstat.random unsatisfiable Build-Depends(-Arch) on amd64: r-cran-spatstat.geom (>= 3.3-0)
    • r-cran-spatstat.random unsatisfiable Build-Depends(-Arch) on arm64: r-cran-spatstat.geom (>= 3.3-0)
    • r-cran-spatstat.random unsatisfiable Build-Depends(-Arch) on armel: r-cran-spatstat.geom (>= 3.3-0)
    • r-cran-spatstat.random unsatisfiable Build-Depends(-Arch) on armhf: r-cran-spatstat.geom (>= 3.3-0)
    • r-cran-spatstat.random unsatisfiable Build-Depends(-Arch) on i386: r-cran-spatstat.geom (>= 3.3-0)
    • r-cran-spatstat.random unsatisfiable Build-Depends(-Arch) on mips64el: r-cran-spatstat.geom (>= 3.3-0)
    • r-cran-spatstat.random unsatisfiable Build-Depends(-Arch) on ppc64el: r-cran-spatstat.geom (>= 3.3-0)
    • r-cran-spatstat.random unsatisfiable Build-Depends(-Arch) on riscv64: r-cran-spatstat.geom (>= 3.3-0)
    • r-cran-spatstat.random unsatisfiable Build-Depends(-Arch) on s390x: r-cran-spatstat.geom (>= 3.3-0)
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 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/r/r-cran-spatstat.random.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 13 days old (needed 5 days)
• rust-aom-sys (0.3.3-4 to 0.3.3-5)
  • Migration status for rust-aom-sys (0.3.3-4 to 0.3.3-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-aom-sys rust-bindgen (not considered)
    • Depends: rust-aom-sys rust-bindgen (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-aom-sys.html
    • autopkgtest for rust-aom-sys/0.3.3-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-bindgen (0.70.1-2 to 0.71.1-2)
  • Migration status for rust-bindgen (0.70.1-2 to 0.71.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Implicit dependency: rust-bindgen oxigraph (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: rust-bindgen rust-aom-sys
    • Implicit dependency: rust-bindgen rust-capstone-sys
    • Implicit dependency: rust-bindgen rust-drm-fourcc
    • Implicit dependency: rust-bindgen rust-drm-sys
    • Implicit dependency: rust-bindgen rust-exacl
    • Implicit dependency: rust-bindgen rust-fts-sys
    • Implicit dependency: rust-bindgen rust-input-sys
    • Implicit dependency: rust-bindgen rust-libbpf-sys
    • Implicit dependency: rust-bindgen rust-libspa-sys
    • Implicit dependency: rust-bindgen rust-lmdb-master-sys
    • Implicit dependency: rust-bindgen rust-loopdev
    • Implicit dependency: rust-bindgen rust-parsec-service
    • Implicit dependency: rust-bindgen rust-pipewire-sys
    • Implicit dependency: rust-bindgen rust-rb-sys-build
    • Implicit dependency: rust-bindgen rust-subversion
    • Implicit dependency: rust-bindgen rust-tss-esapi-sys
    • Implicit dependency: rust-bindgen rust-xkbcommon-sys
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bindgen.html
    • autopkgtest for rust-bindgen/0.71.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-bindgen-cli (0.70.1-3 to 0.71.1-2)
  • Migration status for rust-bindgen-cli (0.70.1-3 to 0.71.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-bindgen-cli rust-bindgen (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bindgen-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• rust-drm-fourcc (2.2.0-2 to 2.2.0-3)
  • Migration status for rust-drm-fourcc (2.2.0-2 to 2.2.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-drm-fourcc rust-bindgen (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-drm-fourcc.html
    • autopkgtest for rust-drm-fourcc/2.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-drm-sys (0.6.1-2 to 0.6.1-3)
  • Migration status for rust-drm-sys (0.6.1-2 to 0.6.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-drm-sys rust-bindgen (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-drm-sys.html
    • autopkgtest for rust-drm-sys/0.6.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-exacl (0.10.0-3 to 0.10.0-4)
  • Migration status for rust-exacl (0.10.0-3 to 0.10.0-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-exacl rust-bindgen (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-exacl.html
    • autopkgtest for rust-exacl/0.10.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-fts-sys (0.2.11-2 to 0.2.11-3)
  • Migration status for rust-fts-sys (0.2.11-2 to 0.2.11-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-fts-sys rust-bindgen (not considered)
    • Depends: rust-fts-sys rust-bindgen (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fts-sys.html
    • autopkgtest for rust-fts-sys/0.2.11-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-gix-merge (- to 0.0.0-1)
  • Migration status for rust-gix-merge (- to 0.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-gix-merge-dev/amd64 has unsatisfiable dependency
    • rust-gix-merge unsatisfiable Build-Depends(-Arch) on amd64: librust-gix-command-0.3+default-dev (>= 0.3.10-~~)
    • rust-gix-merge unsatisfiable Build-Depends(-Arch) on amd64: librust-gix-filter-0.14+default-dev
    • rust-gix-merge unsatisfiable Build-Depends(-Arch) on amd64: librust-gix-fs-0.12+default-dev
    • rust-gix-merge unsatisfiable Build-Depends(-Arch) on amd64: librust-gix-hash-0.15+default-dev
    • rust-gix-merge unsatisfiable Build-Depends(-Arch) on amd64: librust-gix-object-0.45+default-dev
    • rust-gix-merge unsatisfiable Build-Depends(-Arch) on amd64: librust-gix-path-0.10+default-dev (>= 0.10.12-~~)
    • rust-gix-merge unsatisfiable Build-Depends(-Arch) on amd64: librust-gix-quote-0.4+default-dev (>= 0.4.13-~~)
    • rust-gix-merge unsatisfiable Build-Depends(-Arch) on amd64: librust-gix-tempfile-15+default-dev
    • rust-gix-merge unsatisfiable Build-Depends(-Arch) on amd64: librust-gix-trace-0.1+default-dev (>= 0.1.11-~~)
    • rust-gix-merge unsatisfiable Build-Depends(-Arch) on amd64: librust-gix-worktree-0.37+attributes-dev
    • Not built on buildd: arch amd64 binaries uploaded by debian@fabian.gruenbichler.email
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gix-merge.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 13 days old (needed 5 days)
• rust-input-sys (1.18.0-3 to 1.18.0-4)
  • Migration status for rust-input-sys (1.18.0-3 to 1.18.0-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-input-sys rust-bindgen (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-input-sys.html
    • autopkgtest for rust-input-sys/1.18.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-libbpf-sys (1.5.0-1 to 1.5.0-2)
  • Migration status for rust-libbpf-sys (1.5.0-1 to 1.5.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-libbpf-sys rust-bindgen (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libbpf-sys.html
    • autopkgtest for rust-libbpf-sys/1.5.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-libspa-sys (0.8.0-5 to 0.8.0-6)
  • Migration status for rust-libspa-sys (0.8.0-5 to 0.8.0-6): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-libspa-sys rust-bindgen (not considered)
    • Depends: rust-libspa-sys rust-bindgen (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libspa-sys.html
    • autopkgtest for rust-libspa-sys/0.8.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-lmdb-master-sys (0.2.4-2 to 0.2.4-3)
  • Migration status for rust-lmdb-master-sys (0.2.4-2 to 0.2.4-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-lmdb-master-sys rust-bindgen (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-lmdb-master-sys.html
    • autopkgtest for rust-lmdb-master-sys/0.2.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-loopdev (0.4.0-5 to 0.4.0-6)
  • Migration status for rust-loopdev (0.4.0-5 to 0.4.0-6): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-loopdev rust-bindgen (not considered)
    • Depends: rust-loopdev rust-bindgen (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-loopdev.html
    • autopkgtest for rust-loopdev/0.4.0-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• rust-mail-send (0.4.9-4 to 0.5.0-1)
  • Migration status for rust-mail-send (0.4.9-4 to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-mail-send/0.5.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-mail-send.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• rust-parsec-service (1.4.1-2 to 1.4.1-3)
  • Migration status for rust-parsec-service (1.4.1-2 to 1.4.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-parsec-service rust-bindgen (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-parsec-service.html
    • autopkgtest for rust-parsec-service/1.4.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-pipewire-sys (0.8.0-5 to 0.8.0-6)
  • Migration status for rust-pipewire-sys (0.8.0-5 to 0.8.0-6): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-pipewire-sys rust-bindgen (not considered)
    • Depends: rust-pipewire-sys rust-bindgen (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pipewire-sys.html
    • autopkgtest for rust-pipewire-sys/0.8.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-rb-sys-build (0.9.102-2 to 0.9.102-3)
  • Migration status for rust-rb-sys-build (0.9.102-2 to 0.9.102-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-rb-sys-build rust-bindgen (not considered)
    • Depends: rust-rb-sys-build rust-bindgen (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rb-sys-build.html
    • autopkgtest for rust-rb-sys-build/0.9.102-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-subversion (0.0.8-2 to 0.0.8-3)
  • Migration status for rust-subversion (0.0.8-2 to 0.0.8-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-subversion rust-bindgen (not considered)
    • Depends: rust-subversion rust-bindgen (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-subversion.html
    • autopkgtest for rust-subversion/0.0.8-3: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-tss-esapi-sys (0.5.0-2 to 0.5.0-3)
  • Migration status for rust-tss-esapi-sys (0.5.0-2 to 0.5.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-tss-esapi-sys rust-bindgen (not considered)
    • Depends: rust-tss-esapi-sys rust-bindgen (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tss-esapi-sys.html
    • autopkgtest for rust-tss-esapi-sys/0.5.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• rust-xkbcommon-sys (1.4.1-3 to 1.4.1-4)
  • Migration status for rust-xkbcommon-sys (1.4.1-3 to 1.4.1-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-xkbcommon-sys rust-bindgen (not considered)
    • Depends: rust-xkbcommon-sys rust-bindgen (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xkbcommon-sys.html
    • autopkgtest for rust-xkbcommon-sys/1.4.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• supernovas (1.1.1-2 to 1.2.0-1)
  • Migration status for supernovas (1.1.1-2 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by debian@liska.ath.cx
    • Not built on buildd: arch all binaries uploaded by debian@liska.ath.cx, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/supernovas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• camera.app (0.8.0-14 to 0.8.0-15)
  • Migration status for camera.app (0.8.0-14 to 0.8.0-15): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: camera.app gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): camera.app gnustep-gui (not considered)
  • Additional info:
    • Updating camera.app will fix bugs in testing: #1093981
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camera.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• dbuskit (0.1.1-4 to 0.1.1-6)
  • Migration status for dbuskit (0.1.1-4 to 0.1.1-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dbuskit gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): dbuskit gnustep-base
  • Additional info:
    • Updating dbuskit will fix bugs in testing: #1093970
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dbuskit.html
    • autopkgtest for dbuskit/0.1.1-6: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• dxvk (- to 2.5.3-1)
  • Migration status for dxvk (- to 2.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dxvk/2.5.3-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Pass, i386: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dxvk.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• gitlab (- to 17.3.5-2)
  • Migration status for gitlab (- to 17.3.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab would introduce bugs in testing: #1009942, #1077946, #983915
    • gitlab unsatisfiable Build-Depends(-Arch) on amd64: golang-gitlab-gitlab-org-gitaly-dev (>= 16.11~)
    • gitlab unsatisfiable Build-Depends(-Arch) on arm64: golang-gitlab-gitlab-org-gitaly-dev (>= 16.11~)
    • gitlab unsatisfiable Build-Depends(-Arch) on armel: golang-gitlab-gitlab-org-gitaly-dev (>= 16.11~)
    • gitlab unsatisfiable Build-Depends(-Arch) on armhf: golang-gitlab-gitlab-org-gitaly-dev (>= 16.11~)
    • gitlab unsatisfiable Build-Depends(-Arch) on i386: golang-gitlab-gitlab-org-gitaly-dev (>= 16.11~)
    • gitlab unsatisfiable Build-Depends(-Arch) on mips64el: golang-gitlab-gitlab-org-gitaly-dev (>= 16.11~)
    • gitlab unsatisfiable Build-Depends(-Arch) on ppc64el: golang-gitlab-gitlab-org-gitaly-dev (>= 16.11~)
    • gitlab unsatisfiable Build-Depends(-Arch) on riscv64: golang-gitlab-gitlab-org-gitaly-dev (>= 16.11~)
    • gitlab unsatisfiable Build-Depends(-Arch) on s390x: golang-gitlab-gitlab-org-gitaly-dev (>= 16.11~)
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Built-Using: gitlab gitaly (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 14 days old (needed 5 days)
• gnustep-corebase (0.1.1+20230710-4 to 0.1.1+20230710-5)
  • Migration status for gnustep-corebase (0.1.1+20230710-4 to 0.1.1+20230710-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-corebase gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): gnustep-corebase gnustep-base
  • Additional info:
    • Updating gnustep-corebase will fix bugs in testing: #1093973
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnustep-corebase.html
    • autopkgtest for gnustep-corebase/0.1.1+20230710-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• gnustep-netclasses (1.06.dfsg+really1.1.0-2 to 1.06.dfsg+really1.1.0-3)
  • Migration status for gnustep-netclasses (1.06.dfsg+really1.1.0-2 to 1.06.dfsg+really1.1.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-netclasses gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): gnustep-netclasses gnustep-base
  • Additional info:
    • Updating gnustep-netclasses will fix bugs in testing: #1093974
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnustep-netclasses.html
    • autopkgtest for gnustep-netclasses/1.06.dfsg+really1.1.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• gnustep-performance (0.6.0-3 to 0.6.0-4)
  • Migration status for gnustep-performance (0.6.0-3 to 0.6.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnustep-performance gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): gnustep-performance gnustep-base
  • Additional info:
    • Updating gnustep-performance will fix bugs in testing: #1093975
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnustep-performance.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• golang-k8s-sigs-kustomize-api (- to 0.18.0+ds-3)
  • Migration status for golang-k8s-sigs-kustomize-api (- to 0.18.0+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-k8s-sigs-kustomize-api/0.18.0+ds-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Not built on buildd: upload info for arch all binaries not found, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-sigs-kustomize-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• notcurses (- to 3.0.13+dfsg-2)
  • Migration status for notcurses (- to 3.0.13+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating notcurses would introduce bugs in testing: #1001661, #1015747
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/notcurses.html
    • autopkgtest for notcurses/3.0.13+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• pantomime (1.4.0+dfsg-3 to 1.4.0+dfsg-4)
  • Migration status for pantomime (1.4.0+dfsg-3 to 1.4.0+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pantomime gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): pantomime gnustep-base
  • Additional info:
    • Updating pantomime will fix bugs in testing: #1093976
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pantomime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• python-molotov (- to 2.7-2)
  • Migration status for python-molotov (- to 2.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-molotov/2.7-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-molotov.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• rsskit (0.4-2 to 0.4-3)
  • Migration status for rsskit (0.4-2 to 0.4-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rsskit gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): rsskit gnustep-base
  • Additional info:
    • Updating rsskit will fix bugs in testing: #1093977
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsskit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• sbjson (2.3.2-4.1 to 2.3.2-5)
  • Migration status for sbjson (2.3.2-4.1 to 2.3.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sbjson gnustep-make (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): sbjson gnustep-base
  • Additional info:
    • Updating sbjson will fix bugs in testing: #1094171
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbjson.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• slurm-wlm (24.11.0-2 to 24.11.1-1)
  • Migration status for slurm-wlm (24.11.0-2 to 24.11.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: slurm-wlm slurm-wlm-contrib (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slurm-wlm.html
    • autopkgtest for slurm-wlm/24.11.1-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• slurm-wlm-contrib (24.11.0-2 to 24.11.1-1)
  • Migration status for slurm-wlm-contrib (24.11.0-2 to 24.11.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 14 days old (needed 5 days)
• tryton-modules-web-shop-shopify (- to 7.0.3-3)
  • Migration status for tryton-modules-web-shop-shopify (- to 7.0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for tryton-modules-web-shop-shopify/7.0.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tryton-modules-web-shop-shopify.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• universal-detector (1.1-5 to 1.1-6)
  • Migration status for universal-detector (1.1-5 to 1.1-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): universal-detector gnustep-base (not considered)
    • Depends: universal-detector gnustep-base (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Updating universal-detector will fix bugs in testing: #1093978
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/universal-detector.html
    • autopkgtest for universal-detector/1.1-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• gocryptfs (2.4.0-1 to 2.5.1-1)
  • Migration status for gocryptfs (2.4.0-1 to 2.5.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for gocryptfs/2.5.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gocryptfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 15 days old (needed 5 days)
• golang-k8s-cli-runtime (- to 0.31.4-2)
  • Migration status for golang-k8s-cli-runtime (- to 0.31.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-k8s-cli-runtime golang-k8s-sigs-kustomize-api (not considered)
    • Depends: golang-k8s-cli-runtime golang-k8s-sigs-kustomize-api (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-cli-runtime.html
    • autopkgtest for golang-k8s-cli-runtime/0.31.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• kissat (4.0.1-3 to 4.0.2-1)
  • Migration status for kissat (4.0.1-3 to 4.0.2-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 kissat/4.0.2-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kissat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-418 (- to 418.226.00-17)
  • Migration status for nvidia-graphics-drivers-tesla-418 (- to 418.226.00-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xserver-xorg-video-nvidia-tesla-418/amd64 has unsatisfiable dependency
    • xserver-xorg-video-nvidia-tesla-418/ppc64el has unsatisfiable dependency
    • Updating nvidia-graphics-drivers-tesla-418 would introduce bugs in testing: #1005930, #1006718, #1011143, #1016617, #1025282, #1033777, #1039681, #1055139, #1064986, #1072795, #1081648, #1085971, #1093911
    • autopkgtest for nvidia-graphics-drivers-tesla-418/418.226.00-17: i386: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 15 days old (needed 5 days)
• r-cran-bios2cor (- to 2.2.2-1)
  • Migration status for r-cran-bios2cor (- to 2.2.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-bios2cor r-cran-bigmemory (not considered)
    • Depends: r-cran-bios2cor r-cran-bigmemory (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bios2cor.html
    • autopkgtest for r-cran-bios2cor/2.2.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 15 days old (needed 2 days)
• r-cran-dbscan (1.2-0+ds-1 to 1.2.2+ds-1)
  • Migration status for r-cran-dbscan (1.2-0+ds-1 to 1.2.2+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-dbscan/1.2.2+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dbscan.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• r-cran-parameters (- to 0.24.1-1)
  • Migration status for r-cran-parameters (- to 0.24.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-parameters r-cran-bayestestr (not considered)
    • Depends: r-cran-parameters r-cran-bayestestr (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-parameters.html
    • autopkgtest for r-cran-parameters/0.24.1-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• r-cran-paramhelpers (1.14.1-1 to 1.14.2-1)
  • Migration status for r-cran-paramhelpers (1.14.1-1 to 1.14.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-paramhelpers/1.14.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-paramhelpers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• r-cran-patrick (- to 0.3.0-1)
  • Migration status for r-cran-patrick (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-patrick/0.3.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-patrick.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• bazel-bootstrap (- to 4.2.3+ds-10)
  • Migration status for bazel-bootstrap (- to 4.2.3+ds-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for bazel-bootstrap/4.2.3+ds-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • autopkgtest for python-ml-collections/1.0.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bazel-bootstrap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 16 days old (needed 5 days)
• displaycal-py3 (3.9.14-1 to 3.9.14-2)
  • Migration status for displaycal-py3 (3.9.14-1 to 3.9.14-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: displaycal-py3 numpy (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/displaycal-py3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• gnustep-make (2.9.2-4 to 2.9.2-6)
  • Migration status for gnustep-make (2.9.2-4 to 2.9.2-6): 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 pochu (please contact debian-release if update is needed)
    • Implicit dependency: gnustep-make gnustep-base
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnustep-make.html
    • autopkgtest for gnustep-dl2/0.12.0+git20171224-4: s390x: Pass
    • autopkgtest for gnustep-gui/0.31.1-9: s390x: Pass
    • autopkgtest for gnustep-make/2.9.2-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• pcp (- to 6.3.3-1)
  • Migration status for pcp (- to 6.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pcp would introduce bugs in testing: #1071103
    • pcp unsatisfiable Build-Depends(-Arch) on ppc64el: bpftrace (>= 0.9.2) [amd64 arm64 ppc64el]
    • 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/p/pcp.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 16 days old (needed 10 days)
• php-inotify (- to 3.0.0++-2)
  • Migration status for php-inotify (- to 3.0.0++-2): 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
    • Not built on buildd: arch amd64 binaries uploaded by ondrej
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-inotify.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• php-zstd (- to 0.14.0-1)
  • Migration status for php-zstd (- to 0.14.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
    • Not built on buildd: arch amd64 binaries uploaded by ondrej
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-zstd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• python-anyio (4.7.0-1 to 4.8.0-1)
  • Migration status for python-anyio (4.7.0-1 to 4.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-anyio/4.8.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-asyncclick/8.1.7.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-anyio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• r-cran-tmb (1.9.15-1 to 1.9.16-1)
  • Migration status for r-cran-tmb (1.9.15-1 to 1.9.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-glmmtmb/1.1.9+dfsg-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-tmb/1.9.16-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tmb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 16 days old (needed 5 days)
• rainbows (- to 5.2.1-2)
  • Migration status for rainbows (- to 5.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rainbows/amd64 has unsatisfiable dependency
    • rainbows/arm64 has unsatisfiable dependency
    • Updating rainbows would introduce bugs in testing: #1094473
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rainbows.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• redmine (- to 5.1.3+ds-6)
  • Migration status for redmine (- to 5.1.3+ds-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating redmine would introduce bugs in testing: #1095148
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/redmine.html
  • Additional info:
    • autopkgtest for redmine/5.1.3+ds-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 days)
• spglib (- to 2.5.0-2)
  • Migration status for spglib (- to 2.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spglib would introduce bugs in testing: #1094821
    • autopkgtest for spglib/2.5.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spglib.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• golang-github-awslabs-soci-snapshotter (- to 0.4.1-4)
  • Migration status for golang-github-awslabs-soci-snapshotter (- to 0.4.1-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for golang-github-awslabs-soci-snapshotter/0.4.1-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-awslabs-soci-snapshotter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 17 days old (needed 5 days)
• mccode (- to 3.5.19+ds5-1)
  • Migration status for mccode (- to 3.5.19+ds5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mccode/3.5.19+ds5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: mccode xraylib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mccode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• numpy (1:1.26.4+ds-13 to 1:2.2.2+ds-2)
  • Migration status for numpy (1:1.26.4+ds-13 to 1:2.2.2+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating python3-numpy/1:2.2.2+ds-2/amd64 to testing makes python3-gpyfft/0.7.1-2+b8/amd64 uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/amd64 to testing makes python3-pyvkfft-cuda/2024.1.4+ds1-6/amd64 uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/amd64 to testing makes python3-soxr/0.5.0-1/amd64 uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/arm64 to testing makes python3-gpyfft/0.7.1-2+b8/arm64 uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/arm64 to testing makes python3-soxr/0.5.0-1/arm64 uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/armel to testing makes python3-gpyfft/0.7.1-2+b7/armel uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/armel to testing makes python3-soxr/0.5.0-1/armel uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/armhf to testing makes python3-gpyfft/0.7.1-2+b7/armhf uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/armhf to testing makes python3-soxr/0.5.0-1/armhf uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/i386 to testing makes python3-gpyfft/0.7.1-2+b8/i386 uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/i386 to testing makes python3-soxr/0.5.0-1/i386 uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/mips64el to testing makes python3-soxr/0.5.0-1/mips64el uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/ppc64el to testing makes python3-soxr/0.5.0-1/ppc64el uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/riscv64 to testing makes python3-soxr/0.5.0-1/riscv64 uninstallable
    • migrating python3-numpy/1:2.2.2+ds-2/s390x to testing makes python3-soxr/0.5.0-1/s390x uninstallable
    • autopkgtest for bmtk/1.1.1+ds-3: amd64: Regression or new test ♻ (reference ♻)
    • autopkgtest for cython/3.0.11+dfsg-1: arm64: Regression or new test ♻ (reference ♻)
    • autopkgtest for getfem/5.4.4+dfsg1-1: riscv64: Pass
    • autopkgtest for gpyfft/0.7.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻)
    • autopkgtest for joblib/1.3.2-6: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for lmfit-py/1.2.2-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mdanalysis/2.7.0-5: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mdp/3.6-9: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mdtraj/1.10.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻)
    • autopkgtest for meep/1.25.0-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for numpy/1:2.2.2+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Pass, s390x: Pass
    • autopkgtest for pycorrfit/1.1.7+nopack-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pyopencl/2024.1-2: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for pyrr/0.10.3-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-hug/2.6.0-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-meshio/7.0.0-really-5.3.5-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-meshplex/0.17.1-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-pbcore/2.1.2+dfsg-10: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-qmix/1.0.6-10: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-soxr/0.5.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for scikit-learn/1.4.2+dfsg-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for seaborn/0.13.2-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for spectral-cube/0.6.6-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for suitesparse/1:7.8.3+dfsg-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for sympy/1.13.3-2: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for tomopy/1.15.0+ds1-9: amd64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Implicit dependency: numpy displaycal-py3
    • Implicit dependency: numpy python-pomegranate
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/numpy.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
    • 17 days old (needed 5 days)
• orange-spectroscopy (- to 0.8.1-1)
  • Migration status for orange-spectroscopy (- to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating orange-spectroscopy would introduce bugs in testing: #1095364
    • autopkgtest for orange-spectroscopy/0.8.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orange-spectroscopy.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 17 days old (needed 5 days)
• orange-widget-base (4.24.0-2 to 4.25.1-1)
  • Migration status for orange-widget-base (4.24.0-2 to 4.25.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orange-widget-base/4.25.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orange-widget-base.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 17 days old (needed 5 days)
• r-cran-bayestestr (- to 0.15.1-4)
  • Migration status for r-cran-bayestestr (- to 0.15.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-bayestestr/0.15.1-4: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • autopkgtest for r-cran-bayestestr/blocked-on-ci-infra: i386: Ignored failure
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bayestestr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• ruby-mongo (2.5.1-1.1 to 2.5.1-1.2)
  • Migration status for ruby-mongo (2.5.1-1.1 to 2.5.1-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:
    • Updating ruby-mongo will fix bugs in testing: #1033590
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-mongo.html
    • 17 days old (needed 5 days)
• lomiri-system-settings (- to 1.3.0-4)
  • Migration status for lomiri-system-settings (- to 1.3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lomiri-system-settings lomiri-indicator-network (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-system-settings.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-340xx (- to 340.108-24)
  • Migration status for nvidia-graphics-drivers-legacy-340xx (- to 340.108-24): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-legacy-340xx would introduce bugs in testing: #1004848, #1011141, #1016615, #1025280, #1033775, #1039679, #1055137, #1064984, #1072793, #1085969, #1093909, #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-24: amd64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • 18 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-390xx (- to 390.157-11)
  • Migration status for nvidia-graphics-drivers-legacy-390xx (- to 390.157-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-legacy-390xx would introduce bugs in testing: #1006719, #1033776, #1039680, #1055138, #1064985, #1072794, #1085970, #1093910
    • Depends: nvidia-graphics-drivers-legacy-390xx nvidia-graphics-drivers-tesla-418 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-legacy-390xx/390.157-11: amd64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • 18 days old (needed 5 days)
• xperia-flashtool (- to 0.9.34+ds-2)
  • Migration status for xperia-flashtool (- to 0.9.34+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xperia-flashtool jarchivelib (not considered)
    • Depends: xperia-flashtool jarchivelib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xperia-flashtool.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 18 days old (needed 5 days)
• kotlin (- to 1.3.31+ds1-2)
  • Migration status for kotlin (- to 1.3.31+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: kotlin openjdk-11 (not considered)
    • Invalidated by build-dependency (indep)
    • Build-Depends(-Arch): kotlin kotlinx-atomicfu (not considered)
    • Build-Depends(-Arch): kotlin kotlinx-coroutines (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kotlin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• mimalloc (2.1.7+ds-1 to 3.0.1+ds-2)
  • Migration status for mimalloc (2.1.7+ds-1 to 3.0.1+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mimalloc would introduce bugs in testing: #1094235, #1094269, #1094881
    • autopkgtest for pendulum/3.0.0-2: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating mimalloc will fix bugs in testing: #1095272
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mimalloc.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducibility regression on i386 - info ♻
    • 19 days old (needed 5 days)
• mysql-8.0 (- to 8.0.41-2)
  • Migration status for mysql-8.0 (- to 8.0.41-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mysql-8.0/8.0.41-2: amd64: Regression or new test ♻, arm64: Pass, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not touching package due to block request by pochu (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-8.0.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • 19 days old (needed 5 days)
• rust-serde-json (1.0.133-1 to 1.0.134-1)
  • Migration status for rust-serde-json (1.0.133-1 to 1.0.134-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-serde-json/1.0.134-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-serde-json.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• uwsgi-plugin-pypy (- to 0.0.2)
  • Migration status for uwsgi-plugin-pypy (- to 0.0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for uwsgi-plugin-pypy/0.0.2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uwsgi-plugin-pypy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 19 days old (needed 5 days)
• plaso (- to 20241006-3)
  • Migration status for plaso (- to 20241006-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating plaso would introduce bugs in testing: #1093745
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plaso.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 20 days old (needed 5 days)
• r-cran-dendextend (1.18.1+dfsg-1 to 1.19.0+dfsg-1)
  • Migration status for r-cran-dendextend (1.18.1+dfsg-1 to 1.19.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-dendextend/1.19.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dendextend.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 20 days old (needed 5 days)
• r-cran-performance (- to 0.13.0-1)
  • Migration status for r-cran-performance (- to 0.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-performance would introduce bugs in testing: #1071104
    • autopkgtest for r-cran-performance/0.13.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): r-cran-performance r-cran-bayestestr (not considered)
    • Depends: r-cran-performance r-cran-bayestestr (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-performance.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 20 days old (needed 5 days)
• r-cran-sjplot (- to 2.8.16+dfsg-2)
  • Migration status for r-cran-sjplot (- to 2.8.16+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-sjplot r-cran-performance (not considered)
    • Depends: r-cran-sjplot r-cran-performance (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-sjplot r-cran-bayestestr (not considered)
    • Build-Depends(-Arch): r-cran-sjplot r-cran-parameters
    • Build-Depends(-Arch): r-cran-sjplot r-cran-sjstats
    • Depends: r-cran-sjplot r-cran-bayestestr (not considered)
    • Depends: r-cran-sjplot r-cran-parameters
    • Depends: r-cran-sjplot r-cran-sjstats
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sjplot.html
    • autopkgtest for r-cran-sjplot/2.8.16+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 20 days old (needed 2 days)
• rust-pdb-addr2line (- to 0.11.1-1)
  • Migration status for rust-pdb-addr2line (- to 0.11.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-pdb-addr2line rust-pdb2 (not considered)
    • Depends: rust-pdb-addr2line rust-pdb2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pdb-addr2line.html
    • autopkgtest for rust-pdb-addr2line/0.11.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 20 days old (needed 5 days)
• rust-pdb2 (- to 0.9.1-1)
  • Migration status for rust-pdb2 (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-pdb2/0.9.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pdb2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 20 days old (needed 5 days)
• rust-proc-macro2-diagnostics (- to 0.10.1-1)
  • Migration status for rust-proc-macro2-diagnostics (- to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-proc-macro2-diagnostics/0.10.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proc-macro2-diagnostics.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 20 days old (needed 5 days)
• xserver-xorg-video-vesa (1:2.6.0-1 to 1:2.6.0-2)
  • Migration status for xserver-xorg-video-vesa (1:2.6.0-1 to 1:2.6.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-vesa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 20 days old (needed 5 days)
• gittuf (- to 0.8.0-1)
  • Migration status for gittuf (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gittuf/0.8.0-1: amd64: Regression or new test ♻, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not built on buildd: arch amd64 binaries uploaded by jas
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gittuf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • 21 days old (needed 5 days)
• mathgl (- to 8.0.2-4)
  • Migration status for mathgl (- to 8.0.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mathgl would introduce bugs in testing: #1094884
    • autopkgtest for mathgl/8.0.2-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathgl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• openstructure (- to 2.9.1-1)
  • Migration status for openstructure (- to 2.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openstructure would introduce bugs in testing: #1092077
    • missing build on amd64
    • missing build on mips64el
    • arch:amd64 not built yet, autopkgtest delayed there
    • autopkgtest for openstructure/2.9.1-1: i386: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openstructure.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• r-cran-spdata (2.3.1-1 to 2.3.4-1)
  • Migration status for r-cran-spdata (2.3.1-1 to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-spatialreg/1.3-1+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-spdata/2.3.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• td (1.8.0+git20240817.9b6ff58+dfsg2-1 to 1.8.38~git20241021.d321984+dfsg-3)
  • Migration status for td (1.8.0+git20240817.9b6ff58+dfsg2-1 to 1.8.38~git20241021.d321984+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating td would introduce bugs in testing: #1093746
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/td.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• coot (- to 1.1.09+dfsg-4)
  • Migration status for coot (- to 1.1.09+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): coot rdkit (not considered)
    • Depends: coot rdkit (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coot.html
    • autopkgtest for coot/1.1.09+dfsg-4: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 22 days old (needed 2 days)
• dub (- to 1.38.1-2)
  • Migration status for dub (- to 1.38.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dub would introduce bugs in testing: #1095342
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dub.html
    • autopkgtest for dub/1.38.1-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 22 days old (needed 2 days)
• libgovirt (- to 0.3.9-4)
  • Migration status for libgovirt (- to 0.3.9-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgovirt would introduce bugs in testing: #1030904
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgovirt.html
    • 22 days old (needed 5 days)
• openjdk-11 (- to 11.0.26+4-1)
  • Migration status for openjdk-11 (- to 11.0.26+4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-11 would introduce bugs in testing: #1023237, #1071118
    • missing build on armel
    • missing build on armhf
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for openjdk-11/11.0.26+4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 22 days old (needed 5 days)
• openmolcas (- to 24.10-4)
  • Migration status for openmolcas (- to 24.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for openmolcas/24.10-4: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmolcas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 22 days old (needed 5 days)
• rust-dashmap (5.5.3-2 to 6.1.0-1)
  • Migration status for rust-dashmap (5.5.3-2 to 6.1.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Implicit dependency: rust-dashmap oxigraph (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-dashmap.html
    • autopkgtest for rust-dashmap/6.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 22 days old (needed 2 days)
• rust-glycin-utils (2.0.2-2 to 3.0.0~alpha.1-1)
  • Migration status for rust-glycin-utils (2.0.2-2 to 3.0.0~alpha.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-glycin-utils would introduce bugs in testing: #1094111
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on amd64: librust-gufo-common-0.2+default-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on amd64: librust-gufo-common-0.2+serde-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on amd64: librust-zbus-5+async-io-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on amd64: librust-zbus-5+p2p-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on arm64: librust-gufo-common-0.2+default-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on arm64: librust-gufo-common-0.2+serde-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on arm64: librust-zbus-5+async-io-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on arm64: librust-zbus-5+p2p-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on armel: librust-gufo-common-0.2+default-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on armel: librust-gufo-common-0.2+serde-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on armel: librust-zbus-5+async-io-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on armel: librust-zbus-5+p2p-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on armhf: librust-gufo-common-0.2+default-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on armhf: librust-gufo-common-0.2+serde-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on armhf: librust-zbus-5+async-io-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on armhf: librust-zbus-5+p2p-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on i386: librust-gufo-common-0.2+default-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on i386: librust-gufo-common-0.2+serde-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on i386: librust-zbus-5+async-io-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on i386: librust-zbus-5+p2p-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on mips64el: librust-gufo-common-0.2+default-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on mips64el: librust-gufo-common-0.2+serde-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on mips64el: librust-zbus-5+async-io-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on mips64el: librust-zbus-5+p2p-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gufo-common-0.2+default-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gufo-common-0.2+serde-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on ppc64el: librust-zbus-5+async-io-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on ppc64el: librust-zbus-5+p2p-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on riscv64: librust-gufo-common-0.2+default-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on riscv64: librust-gufo-common-0.2+serde-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on riscv64: librust-zbus-5+async-io-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on riscv64: librust-zbus-5+p2p-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on s390x: librust-gufo-common-0.2+default-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on s390x: librust-gufo-common-0.2+serde-dev
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on s390x: librust-zbus-5+async-io-dev (>= 5.2.0-~~)
    • rust-glycin-utils unsatisfiable Build-Depends(-Arch) on s390x: librust-zbus-5+p2p-dev (>= 5.2.0-~~)
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 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/r/rust-glycin-utils.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 22 days old (needed 5 days)
• avfs (- to 1.1.5-1.3)
  • Migration status for avfs (- to 1.1.5-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating avfs would introduce bugs in testing: #1061322
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/avfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 days old (needed 5 days)
• danmaq (- to 0.2.3.2-3)
  • Migration status for danmaq (- to 0.2.3.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating danmaq would introduce bugs in testing: #1091543
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/danmaq.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 days old (needed 5 days)
• libisal (2.31.0-0.3 to 2.31.1-1)
  • Migration status for libisal (2.31.0-0.3 to 2.31.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for libisal/2.31.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libisal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 23 days old (needed 5 days)
• python-einops (- to 0.8.0-2)
  • Migration status for python-einops (- to 0.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-einops would introduce bugs in testing: #1093687
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-einops.html
    • autopkgtest for python-einops/0.8.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• rabbitmq-server (3.10.8-4 to 4.0.5-2)
  • Migration status for rabbitmq-server (3.10.8-4 to 4.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): rabbitmq-server erlang (not considered)
    • Depends: rabbitmq-server erlang (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Updating rabbitmq-server will fix bugs in testing: #1090027, #1090259, #1090295, #1093408
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rabbitmq-server.html
    • autopkgtest for rabbitmq-server/4.0.5-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 23 days old (needed 5 days)
• docker-compose (- to 1.29.2-6.4)
  • Migration status for docker-compose (- to 1.29.2-6.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating docker-compose would introduce bugs in testing: #1040417
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/docker-compose.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 days)
• libpsml (- to 2.0.1-2)
  • Migration status for libpsml (- to 2.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpsml would introduce bugs in testing: #1071043
    • libpsml unsatisfiable Build-Depends(-Arch) on amd64: libxmlf90-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/libp/libpsml.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 24 days old (needed 5 days)
• luminance-hdr (- to 2.6.1.1+dfsg-4)
  • Migration status for luminance-hdr (- to 2.6.1.1+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: luminance-hdr hugin (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/luminance-hdr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 days)
• mu-editor (- to 1.2.0+dfsg-2)
  • Migration status for mu-editor (- to 1.2.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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.2.0+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 24 days old (needed 2 days)
• mumble (- to 1.5.735-2)
  • Migration status for mumble (- to 1.5.735-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mumble would introduce bugs in testing: #1093661
    • autopkgtest for mumble/1.5.735-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): mumble zeroc-ice (not considered)
    • Depends: mumble zeroc-ice (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mumble.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 days)
• watchman (- to 4.9.0-8)
  • Migration status for watchman (- to 4.9.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • watchman/amd64 has unsatisfiable dependency
    • watchman/arm64 has unsatisfiable dependency
    • watchman/armel has unsatisfiable dependency
    • watchman/armhf has unsatisfiable dependency
    • watchman/i386 has unsatisfiable dependency
    • watchman/mips64el has unsatisfiable dependency
    • watchman/ppc64el has unsatisfiable dependency
    • watchman/riscv64 has unsatisfiable dependency
    • Updating watchman would introduce bugs in testing: #999930
    • watchman unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/watchman.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 days)
• cp2k (- to 2024.1-1)
  • Migration status for cp2k (- to 2024.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cp2k would introduce bugs in testing: #1087987
    • autopkgtest for cp2k/2024.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • cp2k unsatisfiable Build-Depends(-Arch) on armel: libelpa-dev (>= 2022.11.001-1)
    • cp2k unsatisfiable Build-Depends(-Arch) on armhf: libelpa-dev (>= 2022.11.001-1)
    • cp2k unsatisfiable Build-Depends(-Arch) on i386: libelpa-dev (>= 2022.11.001-1)
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): cp2k spglib (not considered)
    • Depends: cp2k spglib (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cp2k.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 25 days old (needed 5 days)
• elixir-ex-doc (- to 0.35.1+dfsg-4)
  • Migration status for elixir-ex-doc (- to 0.35.1+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • elixir-ex-doc unsatisfiable Build-Depends(-Arch) on mips64el: elixir (>= 1.18)
    • missing build on mips64el
    • Build-Depends(-Arch): elixir-ex-doc elixir-earmark-parser (not considered)
    • Build-Depends(-Arch): elixir-ex-doc elixir-lang (not considered)
    • Build-Depends(-Arch): elixir-ex-doc elixir-makeup-c (not considered)
    • Build-Depends(-Arch): elixir-ex-doc elixir-makeup-elixir (not considered)
    • Build-Depends(-Arch): elixir-ex-doc elixir-makeup-erlang (not considered)
    • Depends: elixir-ex-doc elixir-earmark-parser (not considered)
    • Depends: elixir-ex-doc elixir-makeup-elixir (not considered)
    • Depends: elixir-ex-doc elixir-makeup-erlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elixir-ex-doc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• kf6-kimageformats (6.8.0-1 to 6.10.0-2)
  • Migration status for kf6-kimageformats (6.8.0-1 to 6.10.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 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/k/kf6-kimageformats.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• rust-symphonia-format-riff (- to 0.5.4-1)
  • Migration status for rust-symphonia-format-riff (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-symphonia-format-riff-dev/amd64 has unsatisfiable dependency
    • rust-symphonia-format-riff unsatisfiable Build-Depends(-Arch) on amd64: librust-symphonia-core-0.5+default-dev (>= 0.5.4-~~)
    • rust-symphonia-format-riff unsatisfiable Build-Depends(-Arch) on amd64: librust-symphonia-metadata-0.5+default-dev (>= 0.5.4-~~)
    • Not built on buildd: arch amd64 binaries uploaded by alexander.kjall@gmail.com
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-symphonia-format-riff.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 25 days old (needed 5 days)
• shaderc (2024.3-1 to 2024.4-1)
  • Migration status for shaderc (2024.3-1 to 2024.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: shaderc glslang (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shaderc.html
    • autopkgtest for shaderc/2024.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 25 days old (needed 2 days)
• devicexlib (- to 0.8.5-1)
  • Migration status for devicexlib (- to 0.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating devicexlib would introduce bugs in testing: #1077607, #1077608
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/devicexlib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 26 days old (needed 5 days)
• openshot-qt (- to 3.1.1+dfsg1-2)
  • Migration status for openshot-qt (- to 3.1.1+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openshot-qt would introduce bugs in testing: #1083075
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openshot-qt.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for openshot-qt/3.1.1+dfsg1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 26 days old (needed 5 days)
• glslang (14.3.0-1 to 15.1.0-1)
  • Migration status for glslang (14.3.0-1 to 15.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glslang would introduce bugs in testing: #1093845
    • autopkgtest for glslang/15.1.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating glslang will fix bugs in testing: #1088554
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glslang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 days old (needed 5 days)
• intel-compute-runtime (- to 24.35.30872.32-1)
  • Migration status for intel-compute-runtime (- to 24.35.30872.32-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-compute-runtime would introduce bugs in testing: #1081100
    • Build-Depends(-Arch): intel-compute-runtime intel-graphics-compiler (not considered)
    • Depends: intel-compute-runtime intel-graphics-compiler (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-compute-runtime.html
    • autopkgtest for intel-compute-runtime/24.35.30872.32-1: amd64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • 27 days old (needed 5 days)
• plakativ (- to 0.5.2-3.1)
  • Migration status for plakativ (- to 0.5.2-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for plakativ/0.5.2-3.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): plakativ pymupdf (not considered)
    • Depends: plakativ pymupdf (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plakativ.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 days old (needed 5 days)
• vulkan-validationlayers (- to 1.4.304.0-1)
  • Migration status for vulkan-validationlayers (- to 1.4.304.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vulkan-validationlayers glslang (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vulkan-validationlayers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 days old (needed 5 days)
• bfh-metapackages (- to 20211009-32)
  • Migration status for bfh-metapackages (- to 20211009-32): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bfh-container-server/amd64 has unsatisfiable dependency
    • bfh-container-server/arm64 has unsatisfiable dependency
    • bfh-base-system/armel has unsatisfiable dependency
    • bfh-base-system/armhf has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bfh-metapackages.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• last-align (1542-1 to 1608-1)
  • Migration status for last-align (1542-1 to 1608-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for last-align/1608-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for nanook/1.33+dfsg-6: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/last-align.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• osmo-tetra (- to 0.0~git20230902.c0956b9-2)
  • Migration status for osmo-tetra (- to 0.0~git20230902.c0956b9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating osmo-tetra would introduce bugs in testing: #1091398
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/osmo-tetra.html
    • autopkgtest for osmo-tetra/0.0~git20230902.c0956b9-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• progress-linux-metapackages (- to 20221002-21)
  • Migration status for progress-linux-metapackages (- to 20221002-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • progress-linux-container-server/amd64 has unsatisfiable dependency
    • progress-linux-container-server/arm64 has unsatisfiable dependency
    • progress-linux-base-system/armel has unsatisfiable dependency
    • progress-linux-base-system/armhf has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/progress-linux-metapackages.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• rally-openstack (- to 3.0.0-3)
  • Migration status for rally-openstack (- to 3.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-rally-openstack/amd64 has unsatisfiable dependency
    • python3-rally-openstack/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rally-openstack.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• rdkit (- to 202409.4-1)
  • Migration status for rdkit (- to 202409.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rdkit would introduce bugs in testing: #1083076, #1093086
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for rdkit/202409.4-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rdkit.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 28 days old (needed 5 days)
• geophar (- to 18.10+dfsg1-6)
  • Migration status for geophar (- to 18.10+dfsg1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating geophar would introduce bugs in testing: #1078365
    • autopkgtest for geophar/18.10+dfsg1-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geophar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• pymupdf (- to 1.25.0+ds1-2)
  • Migration status for pymupdf (- to 1.25.0+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pymupdf/1.25.0+ds1-2: amd64: Pass, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): pymupdf mupdf
    • Depends: pymupdf mupdf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymupdf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• python-redfish (- to 3.2.7-3)
  • Migration status for python-redfish (- to 3.2.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-redfish would introduce bugs in testing: #1093034
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-redfish.html
    • autopkgtest for python-redfish/3.2.7-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 29 days old (needed 2 days)
• rst2pdf (0.102-2 to 0.102-3)
  • Migration status for rst2pdf (0.102-2 to 0.102-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rst2pdf would introduce bugs in testing: #1095375
    • Build-Depends-Indep: rst2pdf pymupdf (not considered)
  • Additional info:
    • Updating rst2pdf will fix bugs in testing: #1088257, #1089526
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rst2pdf.html
    • autopkgtest for rst2pdf/0.102-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• texlive-base (2024.20241115-1 to 2024.20250114-1)
  • Migration status for texlive-base (2024.20241115-1 to 2024.20250114-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating texlive-base would introduce bugs in testing: #1093732
    • autopkgtest for recommonmark/0.7.1+ds-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/texlive-base.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• texlive-extra (2024.20241115-1 to 2024.20250114-1)
  • Migration status for texlive-extra (2024.20241115-1 to 2024.20250114-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating texlive-extra would introduce bugs in testing: #1093247
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/texlive-extra.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• texlive-lang (2024.20241115-1 to 2024.20250114-1)
  • Migration status for texlive-lang (2024.20241115-1 to 2024.20250114-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating texlive-lang would introduce bugs in testing: #1093251
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/texlive-lang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• amgcl (- to 1.4.4-1)
  • Migration status for amgcl (- to 1.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • amgcl unsatisfiable Build-Depends(-Arch) on i386: libopenmpi-dev
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): amgcl parmetis (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 30 days old (needed 5 days)
• fasttrack-archive-keyring (- to 2025.01.13)
  • Migration status for fasttrack-archive-keyring (- to 2025.01.13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fasttrack-archive-keyring would introduce bugs in testing: #1093330
    • Not built on buildd: arch all binaries uploaded by vivekkj@disroot.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fasttrack-archive-keyring.html
    • 30 days old (needed 5 days)
• geogram (- to 1.9.2-1)
  • Migration status for geogram (- to 1.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): geogram amgcl (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 30 days old (needed 5 days)
• r-bioc-cummerbund (- to 2.48.0-2)
  • Migration status for r-bioc-cummerbund (- to 2.48.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-cummerbund r-cran-fastcluster (not considered)
    • Depends: r-bioc-cummerbund r-cran-fastcluster (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-cummerbund.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for r-bioc-cummerbund/2.48.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 30 days old (needed 2 days)
• r-bioc-netsam (- to 1.46.0-3)
  • Migration status for r-bioc-netsam (- to 1.46.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-netsam r-cran-wgcna (not considered)
    • Depends: r-bioc-netsam r-cran-wgcna (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-netsam.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for r-bioc-netsam/1.46.0-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 30 days old (needed 2 days)
• tlv8-python (- to 0.10.0-1)
  • Migration status for tlv8-python (- to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for tlv8-python/0.10.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by eighthave, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tlv8-python.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• lomiri-online-accounts-plugins-caldav (- to 0.5.1-1)
  • Migration status for lomiri-online-accounts-plugins-caldav (- to 0.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lomiri-online-accounts-plugins-caldav lomiri-online-accounts-plugins (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-online-accounts-plugins-caldav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• sioyek (2.0.0+dfsg-4 to 2.0.0+dfsg-5.1)
  • Migration status for sioyek (2.0.0+dfsg-4 to 2.0.0+dfsg-5.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sioyek mupdf (not considered)
    • Invalidated by dependency
  • Additional info:
    • Updating sioyek will fix bugs in testing: #1092888
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sioyek.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• antpm (1.21-2 to 1.21-3)
  • Migration status for antpm (1.21-2 to 1.21-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • antpm unsatisfiable Build-Depends(-Arch) on armel: valgrind
    • antpm unsatisfiable Build-Depends(-Arch) on riscv64: valgrind
    • missing build on armel
    • missing build on riscv64
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:riscv64 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/antpm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• django-pipeline (- to 4.0.0-3)
  • Migration status for django-pipeline (- to 4.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for django-pipeline/4.0.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-pipeline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• mupdf (1.24.10+ds1-1 to 1.25.1+ds1-5)
  • Migration status for mupdf (1.24.10+ds1-1 to 1.25.1+ds1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: mupdf texlive-extra (not considered)
    • Invalidated by built-using
    • Depends: mupdf gumbo-parser (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mupdf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• eartag (- to 0.6.4-1)
  • Migration status for eartag (- to 0.6.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): eartag pyacoustid (not considered)
    • Depends: eartag pyacoustid (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eartag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 days old (needed 5 days)
• elixir-makeup (- to 1.2.1-2)
  • Migration status for elixir-makeup (- to 1.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • elixir-makeup unsatisfiable Build-Depends(-Arch) on mips64el: elixir (>= 1.17)
    • elixir-makeup unsatisfiable Build-Depends(-Arch) on mips64el: elixir-nimble-parsec (>= 1.4.0-2~)
    • missing build on mips64el
    • Build-Depends(-Arch): elixir-makeup elixir-lang (not considered)
    • Build-Depends(-Arch): elixir-makeup elixir-nimble-parsec (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elixir-makeup.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 33 days old (needed 5 days)
• elixir-makeup-c (- to 0.1.1-4)
  • Migration status for elixir-makeup-c (- to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • elixir-makeup-c unsatisfiable Build-Depends(-Arch) on mips64el: elixir (>= 1.17)
    • missing build on mips64el
    • Build-Depends(-Arch): elixir-makeup-c elixir-lang (not considered)
    • Build-Depends(-Arch): elixir-makeup-c elixir-makeup (not considered)
    • Depends: elixir-makeup-c elixir-makeup (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elixir-makeup-c.html
    • Reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 days old (needed 5 days)
• elixir-makeup-elixir (- to 1.0.1-1)
  • Migration status for elixir-makeup-elixir (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • elixir-makeup-elixir unsatisfiable Build-Depends(-Arch) on mips64el: elixir (>= 1.17)
    • missing build on mips64el
    • Build-Depends(-Arch): elixir-makeup-elixir elixir-lang (not considered)
    • Build-Depends(-Arch): elixir-makeup-elixir elixir-makeup (not considered)
    • Depends: elixir-makeup-elixir elixir-makeup (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elixir-makeup-elixir.html
    • Reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 days old (needed 5 days)
• rust-opendal (- to 0.51.0-1)
  • Migration status for rust-opendal (- to 0.51.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-opendal-dev/amd64 has unsatisfiable dependency
    • librust-opendal-dev/arm64 has unsatisfiable dependency
    • librust-opendal-dev/armhf has unsatisfiable dependency
    • librust-opendal-dev/i386 has unsatisfiable dependency
    • librust-opendal-dev/mips64el has unsatisfiable dependency
    • librust-opendal-dev/ppc64el has unsatisfiable dependency
    • librust-opendal-dev/s390x has unsatisfiable dependency
    • Updating rust-opendal would introduce bugs in testing: #1069715
    • missing build on armel
    • missing build on riscv64
    • arch:armel not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-opendal.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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 days old (needed 5 days)
• simplesamlphp (- to 1.19.7-1+deb12u1)
  • Migration status for simplesamlphp (- to 1.19.7-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simplesamlphp would introduce bugs in testing: #1088816
    • Not built on buildd: arch all binaries uploaded by thijs, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simplesamlphp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 days old (needed 5 days)
• lomiri-settings-components (1.1.1-1 to 1.1.2-1)
  • Migration status for lomiri-settings-components (1.1.1-1 to 1.1.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Updating lomiri-settings-components will fix bugs in testing: #1095695
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-settings-components.html
    • autopkgtest for lomiri-settings-components/1.1.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 34 days old (needed 2 days)
• pytorch-cuda (- to 2.5.1+dfsg-4)
  • Migration status for pytorch-cuda (- to 2.5.1+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytorch-cuda would introduce bugs in testing: #1094326
    • Impossible Depends: pytorch-cuda -> libbenchmark1.8.3/1.8.3-3+b1/amd64
    • Impossible Depends: pytorch-cuda -> libbenchmark1.8.3/1.8.3-3+b1/arm64
    • Impossible Depends: pytorch-cuda -> libbenchmark1.8.3/1.8.3-3+b1/ppc64el
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for pytorch-cuda/2.5.1+dfsg-4: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 34 days old (needed 2 days)
• routine-update (- to 0.2.3)
  • Migration status for routine-update (- to 0.2.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: routine-update lintian-brush (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/routine-update.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 35 days old (needed 5 days)
• rust-utmp-classic (- to 0.1.6-1)
  • Migration status for rust-utmp-classic (- to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-utmp-classic/0.1.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-utmp-classic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 35 days old (needed 5 days)
• slic3r-prusa (- to 2.9.0+dfsg-1)
  • Migration status for slic3r-prusa (- to 2.9.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for slic3r-prusa/2.9.0+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r-prusa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 35 days old (needed 5 days)
• yadifa (2.6.7-1 to 3.0.0-1)
  • Migration status for yadifa (2.6.7-1 to 3.0.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating yadifa will fix bugs in testing: #1095527
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yadifa.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • 35 days old (needed 5 days)
• 389-ds-base (- to 3.1.1+dfsg1-3)
  • Migration status for 389-ds-base (- to 3.1.1+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating 389-ds-base would introduce bugs in testing: #1095537
    • Build-Depends(-Arch): 389-ds-base rust-ahash-0.7 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/3/389-ds-base.html
    • autopkgtest for 389-ds-base/3.1.1+dfsg1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 36 days old (needed 2 days)
• lomiri-indicator-network (- to 1.1.0-1)
  • Migration status for lomiri-indicator-network (- to 1.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lomiri-indicator-network ofono (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-indicator-network.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 36 days old (needed 5 days)
• python-mashumaro (3.13.1-4 to 3.15-1)
  • Migration status for python-mashumaro (3.13.1-4 to 3.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-mashumaro/3.15-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating python-mashumaro will fix bugs in testing: #1095694
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mashumaro.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 36 days old (needed 5 days)
• rust-append-only-vec (- to 0.1.7-1)
  • Migration status for rust-append-only-vec (- to 0.1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-append-only-vec/0.1.7-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-append-only-vec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 36 days old (needed 5 days)
• rust-clap-complete-nushell (- to 4.5.4-1)
  • Migration status for rust-clap-complete-nushell (- to 4.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-clap-complete-nushell-dev/amd64 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/arm64 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/armel has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/armhf has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/i386 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/mips64el has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/ppc64el has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/riscv64 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/s390x has unsatisfiable dependency
    • Updating rust-clap-complete-nushell would introduce bugs in testing: #1092486
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-clap-complete-nushell.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 36 days old (needed 5 days)
• chuck (1.5.4.3-1 to 1.5.4.4-1)
  • Migration status for chuck (1.5.4.3-1 to 1.5.4.4-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on ppc64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Updating chuck will fix bugs in testing: #1095273
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chuck.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• lomiri-push-qml (- to 0.3-2)
  • Migration status for lomiri-push-qml (- to 0.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lomiri-push-qml lomiri-indicator-network (not considered)
    • Depends: lomiri-push-qml lomiri-indicator-network (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-push-qml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• mlterm (- to 3.9.3-3)
  • Migration status for mlterm (- to 3.9.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mlterm freewnn (not considered)
    • Depends: mlterm freewnn (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• rust-concurrent-arena (- to 0.1.10-2)
  • Migration status for rust-concurrent-arena (- to 0.1.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-concurrent-arena/0.1.10-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-concurrent-arena.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• yosys (- to 0.33-6)
  • Migration status for yosys (- to 0.33-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yosys would introduce bugs in testing: #1093368
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yosys.html
    • 37 days old (needed 5 days)
• cl-usocket (0.8.3-3 to 0.8.8-2)
  • Migration status for cl-usocket (0.8.3-3 to 0.8.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-usocket would introduce bugs in testing: #1093589
    • autopkgtest for cl-usocket/0.8.8-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Regression or new test ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
  • Additional info:
    • Updating cl-usocket will fix bugs in testing: #1094860
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-usocket.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 38 days old (needed 5 days)
• ofono (- to 2.14-1)
  • Migration status for ofono (- to 2.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ofono would introduce bugs in testing: #1078555
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ofono.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 38 days old (needed 5 days)
• spirv-llvm-translator-14 (- to 14.0.8-1)
  • Migration status for spirv-llvm-translator-14 (- to 14.0.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): spirv-llvm-translator-14 llvm-toolchain-14 (not considered)
    • Depends: spirv-llvm-translator-14 llvm-toolchain-14 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spirv-llvm-translator-14.html
    • autopkgtest for spirv-llvm-translator-14/14.0.8-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 38 days old (needed 5 days)
• crun (1.18.2-1 to 1.19.1-1)
  • Migration status for crun (1.18.2-1 to 1.19.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for crun/1.19.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • crun unsatisfiable Build-Depends(-Arch) on armel: libcriu-dev
    • crun unsatisfiable Build-Depends(-Arch) on armhf: libcriu-dev
    • crun unsatisfiable Build-Depends(-Arch) on i386: libcriu-dev
    • crun unsatisfiable Build-Depends(-Arch) on mips64el: libcriu-dev
    • crun unsatisfiable Build-Depends(-Arch) on riscv64: libcriu-dev
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on riscv64
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating crun will fix bugs in testing: #1095245
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crun.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 39 days old (needed 5 days)
• golang-fsnotify (1.8.0-1 to 1.8.0-2)
  • Migration status for golang-fsnotify (1.8.0-1 to 1.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-fsnotify would introduce bugs in testing: #1092191
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Updating golang-fsnotify will fix bugs in testing: #1091498, #1095243
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-fsnotify.html
    • 39 days old (needed 5 days)
• libhtml-gumbo-perl (0.18-3 to 0.18-4)
  • Migration status for libhtml-gumbo-perl (0.18-3 to 0.18-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libhtml-gumbo-perl gumbo-parser (not considered)
    • Depends: libhtml-gumbo-perl gumbo-parser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhtml-gumbo-perl.html
    • autopkgtest for libhtml-gumbo-perl/0.18-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 39 days old (needed 2 days)
• cppgir (2.0-2.2 to 2.0+git20240928.c8bb1c6-1)
  • Migration status for cppgir (2.0-2.2 to 2.0+git20240928.c8bb1c6-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating cppgir will fix bugs in testing: #1095240
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cppgir.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 40 days old (needed 5 days)
• golang-github-cronokirby-saferith (- to 0.33.0-4)
  • Migration status for golang-github-cronokirby-saferith (- to 0.33.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-cronokirby-saferith/0.33.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-cronokirby-saferith.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 40 days old (needed 5 days)
• napari (- to 0.5.5-1)
  • Migration status for napari (- to 0.5.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating napari would introduce bugs in testing: #1095359
    • autopkgtest for napari/0.5.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): napari napari-console (not considered)
    • Build-Depends(-Arch): napari napari-plugin-manager (not considered)
    • Build-Depends(-Arch): napari napari-svg (not considered)
    • Depends: napari napari-console (not considered)
    • Depends: napari napari-svg (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari.html
    • 40 days old (needed 5 days)
• napari-plugin-manager (- to 0.1.1-5)
  • Migration status for napari-plugin-manager (- to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for napari-plugin-manager/0.1.1-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): napari-plugin-manager napari (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari-plugin-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 40 days old (needed 5 days)
• deepboof (- to 0.5.1+ds-2)
  • Migration status for deepboof (- to 0.5.1+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): deepboof jarchivelib (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepboof.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 41 days old (needed 5 days)
• gcc-11 (- to 11.5.0-2)
  • Migration status for gcc-11 (- to 11.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-11 would introduce bugs in testing: #1023690
    • Depends: gcc-11 hsail-tools
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11.html
    • autopkgtest for gcc-11/11.5.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 41 days old (needed 2 days)
• gcc-11-cross (- to 22)
  • Migration status for gcc-11-cross (- to 22): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-11-cross gcc-11 (not considered)
    • Built-Using: gcc-11-cross gcc-11 (not considered)
    • Depends: gcc-11-cross gcc-11 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
    • Depends: gcc-11-cross hsail-tools
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11-cross.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 41 days old (needed 5 days)
• gcc-11-cross-ports (- to 19)
  • Migration status for gcc-11-cross-ports (- to 19): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-11-cross-ports gcc-11 (not considered)
    • Built-Using: gcc-11-cross-ports gcc-11 (not considered)
    • Depends: gcc-11-cross-ports gcc-11 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
    • Depends: gcc-11-cross-ports hsail-tools
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11-cross-ports.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 41 days old (needed 5 days)
• python-discord (- to 2.4.0+dfsg-1)
  • Migration status for python-discord (- to 2.4.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-discord would introduce bugs in testing: #1057608
    • autopkgtest for python-discord/2.4.0+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-discord.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 41 days old (needed 5 days)
• djbdns (- to 1:1.05-18)
  • Migration status for djbdns (- to 1:1.05-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for djbdns/1:1.05-18: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/djbdns.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 42 days old (needed 5 days)
• ecl (21.2.1+ds-4.1 to 24.5.10+ds-1)
  • Migration status for ecl (21.2.1+ds-4.1 to 24.5.10+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cl-usocket/0.8.8-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Regression or new test ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
  • Additional info:
    • Updating ecl will fix bugs in testing: #1094914
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecl.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 42 days old (needed 5 days)
• golang-github-henrybear327-go-proton-api (- to 1.0.0-4)
  • Migration status for golang-github-henrybear327-go-proton-api (- to 1.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-henrybear327-go-proton-api/1.0.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-henrybear327-go-proton-api golang-github-protonmail-gluon (not considered)
    • Build-Depends(-Arch): golang-github-henrybear327-go-proton-api golang-github-protonmail-go-srp (not considered)
    • Depends: golang-github-henrybear327-go-proton-api golang-github-protonmail-gluon (not considered)
    • Depends: golang-github-henrybear327-go-proton-api golang-github-protonmail-go-srp (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-henrybear327-go-proton-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 42 days old (needed 5 days)
• pmbootstrap (2.3.1-1 to 3.1.0-1)
  • Migration status for pmbootstrap (2.3.1-1 to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pmbootstrap/3.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating pmbootstrap will fix bugs in testing: #1094980
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pmbootstrap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 42 days old (needed 5 days)
• pytorch-vision (- to 0.20.1-1)
  • Migration status for pytorch-vision (- to 0.20.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pytorch-vision/0.20.1-1: amd64: Pass, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-vision.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 42 days old (needed 5 days)
• tt-rss (- to 21~git20210204.b4cbc79+dfsg-2)
  • Migration status for tt-rss (- to 21~git20210204.b4cbc79+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tt-rss would introduce bugs in testing: #1021656, #1054608
    • Depends: tt-rss php-gettext (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tt-rss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 42 days old (needed 5 days)
• napari-console (- to 0.1.3-1)
  • Migration status for napari-console (- to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for napari-console/0.1.3-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): napari-console napari (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari-console.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 43 days old (needed 5 days)
• python-homeassistant-analytics (- to 0.8.1-1)
  • Migration status for python-homeassistant-analytics (- to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-homeassistant-analytics would introduce bugs in testing: #1084336
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-homeassistant-analytics.html
    • autopkgtest for python-homeassistant-analytics/0.8.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 43 days old (needed 2 days)
• rust-netlink-packet-wireguard (- to 0.2.3-2)
  • Migration status for rust-netlink-packet-wireguard (- to 0.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-netlink-packet-wireguard/0.2.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-netlink-packet-wireguard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 43 days old (needed 5 days)
• wine (9.0~repack-7 to 10.0~rc2~repack-2)
  • Migration status for wine (9.0~repack-7 to 10.0~rc2~repack-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wine would introduce bugs in testing: #1093197
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Updating wine will fix bugs in testing: #1094858
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wine.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 44 days old (needed 5 days)
• aspell-sk (2.04+ds.3 to 2.04+ds.7)
  • Migration status for aspell-sk (2.04+ds.3 to 2.04+ds.7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for aspell-sk/2.04+ds.7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating aspell-sk will fix bugs in testing: #1094685
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aspell-sk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 45 days old (needed 5 days)
• genomicsdb (- to 1.5.4-4)
  • Migration status for genomicsdb (- to 1.5.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for genomicsdb/1.5.4-4: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/genomicsdb.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 45 days old (needed 5 days)
• lenovolegionlinux (- to 0.0.18+ds-5)
  • Migration status for lenovolegionlinux (- to 0.0.18+ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lenovolegionlinux would introduce bugs in testing: #1070824, #1083011
    • Not built on buildd: arch amd64 binaries uploaded by zigo
    • Not built on buildd: arch all binaries uploaded by zigo, 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/lenovolegionlinux.html
    • autopkgtest for lenovolegionlinux/0.0.18+ds-5: amd64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • 45 days old (needed 5 days)
• adios4dolfinx (- to 0.9.1.post0-1)
  • Migration status for adios4dolfinx (- to 0.9.1.post0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for adios4dolfinx/0.9.1.post0-1: amd64: Pass, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adios4dolfinx.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 46 days old (needed 5 days)
• genwqe-user (- to 4.0.20-1)
  • Migration status for genwqe-user (- to 4.0.20-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:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/genwqe-user.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 46 days old (needed 5 days)
• ruby-build (20241105-1 to 20241225.2-1)
  • Migration status for ruby-build (20241105-1 to 20241225.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-build would introduce bugs in testing: #1095653
    • autopkgtest for ruby-build/20241225.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating ruby-build will fix bugs in testing: #1093196
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-build.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 46 days old (needed 5 days)
• dioptas (- to 0.6.0-3)
  • Migration status for dioptas (- to 0.6.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): dioptas pyfai (not considered)
    • Depends: dioptas pyfai (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dioptas.html
    • autopkgtest for dioptas/0.6.0-3: amd64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 47 days old (needed 5 days)
• solfege (- to 3.23.4-13)
  • Migration status for solfege (- to 3.23.4-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): solfege lilypond (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/solfege.html
    • autopkgtest for solfege/3.23.4-13: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 47 days old (needed 2 days)
• vitrage (- to 13.0.0-5)
  • Migration status for vitrage (- to 13.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for vitrage/13.0.0-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vitrage.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 47 days old (needed 5 days)
• balsa (- to 2.6.4-3)
  • Migration status for balsa (- to 2.6.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating balsa would introduce bugs in testing: #1094887
    • autopkgtest for balsa/2.6.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/balsa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• lammps (- to 20240207+dfsg-3)
  • Migration status for lammps (- to 20240207+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lammps spglib (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lammps.html
    • autopkgtest for lammps/20240207+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 48 days old (needed 2 days)
• linux-show-player (- to 0.5.3-2)
  • Migration status for linux-show-player (- to 0.5.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for linux-show-player/0.5.3-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-show-player.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• python-rsyncmanager (- to 0.1.3-2)
  • Migration status for python-rsyncmanager (- to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-rsyncmanager would introduce bugs in testing: #1092044
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): python-rsyncmanager silx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-rsyncmanager.html
    • 48 days old (needed 5 days)
• bioxtasraw (- to 2.3.0-2)
  • Migration status for bioxtasraw (- to 2.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-bioxtasraw/riscv64 has unsatisfiable dependency
    • autopkgtest for bioxtasraw/2.3.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/b/bioxtasraw.html
    • Build-Depends(-Arch): bioxtasraw pyfai (not considered)
    • Build-Depends(-Arch): bioxtasraw silx (not considered)
    • Depends: bioxtasraw pyfai (not considered)
    • Depends: bioxtasraw silx (not considered)
  • Additional info:
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 49 days old (needed 5 days)
• libphp-swiftmailer (- to 6.3.0-7)
  • Migration status for libphp-swiftmailer (- to 6.3.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libphp-swiftmailer would introduce bugs in testing: #1039752, #1085113
    • autopkgtest for libphp-swiftmailer/6.3.0-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libphp-swiftmailer.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 50 days old (needed 5 days)
• rust-ruma-state-res (- to 0.8.0-5)
  • Migration status for rust-ruma-state-res (- to 0.8.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-ruma-state-res/0.8.0-5: amd64: Pass, arm64: Pass, armel: Test in progress, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ruma-state-res.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 50 days old (needed 5 days)
• bidentd (- to 1.1.4-1.4)
  • Migration status for bidentd (- to 1.1.4-1.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bidentd would introduce bugs in testing: #763430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bidentd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 51 days old (needed 5 days)
• php-codesniffer (- to 3.11.2-2)
  • Migration status for php-codesniffer (- to 3.11.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-codesniffer would introduce bugs in testing: #1092009
    • autopkgtest for php-codesniffer/3.11.2-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-codesniffer.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 51 days old (needed 5 days)
• php8.2 (- to 8.2.27-1)
  • Migration status for php8.2 (- to 8.2.27-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for adminer/4.8.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for baconqrcode/3.0.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for geshi/1.0.9.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for hoteldruid/3.0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for jsonlint/1.11.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for libsoup2.4/2.74.3-8.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-console-commandline/1.2.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-font-lib/1.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-horde-kolab-format/2.0.9-8: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for php-horde-ldap/2.4.2-6: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for php-horde-service-weather/2.5.6-1: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for php-horde-util/2.5.12-2: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Test in progress, s390x: Failed (not a regression)
    • autopkgtest for php-httpful/1.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-kissifrot-php-ixr/1.8.4-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-league-html-to-markdown/5.1.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-lorenzo-pinky/1.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-luasandbox/4.1.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-mail-mime/1.10.12-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-masterminds-html5/2.9.0+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-ml-json-ld/1.2.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-pda-pheanstalk/4.0.5-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-phar-io-manifest/2.0.4-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-pubsubhubbub-publisher/0~~20181009-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-ramsey-uuid/4.7.4-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for php-slim/3.12.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-wmerrors/2.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php-zumba-json-serializer/3.2.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for php8.2/8.2.27-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
    • autopkgtest for phpsysinfo/3.4.4-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for roundcube/1.6.10+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for rss-bridge/2022-01-20+dfsg1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for smarty3/3.1.48-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for wikidiff2/1.14.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php8.2.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 51 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• xsok (- to 1.02-22)
  • Migration status for xsok (- to 1.02-22): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xsok would introduce bugs in testing: #1091286
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xsok.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 51 days old (needed 5 days)
• apt-clone (- to 0.4.3+nmu3)
  • Migration status for apt-clone (- to 0.4.3+nmu3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apt-clone would introduce bugs in testing: #1074515
    • autopkgtest for apt-clone/0.4.3+nmu3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Pass, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt-clone.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 52 days old (needed 5 days)
• ukui-panel (- to 4.0.0.5-1)
  • Migration status for ukui-panel (- to 4.0.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ukui-panel/amd64 has unsatisfiable dependency
    • ukui-panel/arm64 has unsatisfiable dependency
    • ukui-panel/armel has unsatisfiable dependency
    • ukui-panel/armhf has unsatisfiable dependency
    • ukui-panel/i386 has unsatisfiable dependency
    • ukui-panel/mips64el has unsatisfiable dependency
    • ukui-panel/ppc64el has unsatisfiable dependency
    • ukui-panel/riscv64 has unsatisfiable dependency
    • ukui-panel/s390x has unsatisfiable dependency
    • Updating ukui-panel would introduce bugs in testing: #1079813
    • ukui-panel unsatisfiable Build-Depends(-Arch) on amd64: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on arm64: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on armel: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on armhf: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on i386: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on mips64el: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on riscv64: libkf5screen-dev
    • ukui-panel unsatisfiable Build-Depends(-Arch) on s390x: libkf5screen-dev
    • Build-Depends(-Arch): ukui-panel ukui-control-center (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-panel.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 52 days old (needed 5 days)
• zeal (- to 1:0.7.2-1)
  • Migration status for zeal (- to 1:0.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zeal would introduce bugs in testing: #1081227
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zeal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 52 days old (needed 5 days)
• pairtools (- to 1.1.2-1)
  • Migration status for pairtools (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pairtools would introduce bugs in testing: #1094701
    • autopkgtest for pairtools/1.1.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pairtools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 53 days old (needed 5 days)
• puppet-hiera-enc (- to 1.0.0-1)
  • Migration status for puppet-hiera-enc (- 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 lavamind, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-hiera-enc.html
    • autopkgtest for puppet-hiera-enc/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 53 days old (needed 2 days)
• ruby-chef-config (- to 16.12.3-3)
  • Migration status for ruby-chef-config (- to 16.12.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Updating ruby-chef-config would introduce bugs in testing: #1091657
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-chef-config.html
    • autopkgtest for ruby-chef-config/16.12.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 53 days old (needed 2 days)
    • Remove hint for (transitive) dependency: ruby-chef-config
• lomiri-online-accounts-plugins-carddav (- to 0.5.0-2)
  • Migration status for lomiri-online-accounts-plugins-carddav (- to 0.5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lomiri-online-accounts-plugins-carddav lomiri-online-accounts-plugins (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-online-accounts-plugins-carddav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 54 days old (needed 5 days)
• tryton-meta (55 to 56)
  • Migration status for tryton-meta (55 to 56): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tryton-meta tryton-modules-web-shop-shopify (not considered)
    • Invalidated by dependency
  • Additional info:
    • Updating tryton-meta will fix bugs in testing: #1093785
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tryton-meta.html
    • autopkgtest for tryton-meta/56: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 54 days old (needed 5 days)
• tycho (- to 2.7.5-1.1)
  • Migration status for tycho (- to 2.7.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tycho would introduce bugs in testing: #1086322
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tycho.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 54 days old (needed 5 days)
• lintian-brush (- to 0.160)
  • Migration status for lintian-brush (- to 0.160): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lintian-brush/0.160: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on armel
    • missing build on mips64el
    • arch:armel not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lintian-brush.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 55 days old (needed 5 days)
• python-dtcwt (- to 0.14.0-1)
  • Migration status for python-dtcwt (- to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-dtcwt would introduce bugs in testing: #1095371
    • autopkgtest for python-dtcwt/0.14.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dtcwt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 55 days old (needed 5 days)
• ruby-vips (2.1.4-1.1 to 2.2.2-1)
  • Migration status for ruby-vips (2.1.4-1.1 to 2.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-vips would introduce bugs in testing: #1088648
    • autopkgtest for ruby-image-processing/1.13.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-vips/2.2.2-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
  • Additional info:
    • Updating ruby-vips will fix bugs in testing: #1093786
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-vips.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 55 days old (needed 5 days)
• runit-services (- to 0.8.1)
  • Migration status for runit-services (- to 0.8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for runit-services/0.8.1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/runit-services.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 55 days old (needed 5 days)
• rust-symphonia-format-caf (- to 0.5.4-1)
  • Migration status for rust-symphonia-format-caf (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-symphonia-format-caf-dev/amd64 has unsatisfiable dependency
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/rust-symphonia-format-caf.html
    • rust-symphonia-format-caf unsatisfiable Build-Depends(-Arch) on amd64: librust-symphonia-core-0.5+default-dev (>= 0.5.4-~~)
    • rust-symphonia-format-caf unsatisfiable Build-Depends(-Arch) on amd64: librust-symphonia-metadata-0.5+default-dev (>= 0.5.4-~~)
    • Not built on buildd: arch amd64 binaries uploaded by alexander.kjall@gmail.com
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 55 days old (needed 5 days)
• libjpeg6b (- to 1:6b2-4)
  • Migration status for libjpeg6b (- to 1:6b2-4): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg6b.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 56 days old (needed 5 days)
• nabu (- to 2024.2.1-1)
  • Migration status for nabu (- to 2024.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): nabu silx (not considered)
    • Depends: nabu silx (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): nabu nxtomo
    • Build-Depends(-Arch): nabu tomoscan
    • Depends: nabu tomoscan
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nabu.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for nabu/2024.2.1-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 56 days old (needed 5 days)
• ruby-dalli (3.0.6-2 to 3.2.8-1)
  • Migration status for ruby-dalli (3.0.6-2 to 3.2.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-dalli would introduce bugs in testing: #1095247
  • Additional info:
    • Updating ruby-dalli will fix bugs in testing: #1093482
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dalli.html
    • autopkgtest for ruby-dalli/3.2.8-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 56 days old (needed 5 days)
• python-ewoks (- to 0.6.0-3)
  • Migration status for python-ewoks (- to 0.6.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-ewoks/0.6.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): python-ewoks python-ewokscore (not considered)
    • Build-Depends(-Arch): python-ewoks python-ewoksdask (not considered)
    • Build-Depends(-Arch): python-ewoks python-ewoksdata
    • Build-Depends(-Arch): python-ewoks python-ewoksorange (not considered)
    • Build-Depends(-Arch): python-ewoks python-ewoksppf (not considered)
    • Depends: python-ewoks python-ewokscore (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ewoks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 57 days old (needed 5 days)
• python-ewoksdask (- to 0.2.0-3)
  • Migration status for python-ewoksdask (- to 0.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-ewoksdask/0.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): python-ewoksdask python-ewokscore (not considered)
    • Depends: python-ewoksdask python-ewokscore (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ewoksdask.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 57 days old (needed 5 days)
• python-ewoksdata (- to 0.6.0~rc0-3)
  • Migration status for python-ewoksdata (- to 0.6.0~rc0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-ewoksdata silx (not considered)
    • Depends: python-ewoksdata silx (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ewoksdata.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for python-ewoksdata/0.6.0~rc0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 57 days old (needed 2 days)
• python-ewoksorange (- to 0.9.0-2)
  • Migration status for python-ewoksorange (- to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ewoksorange would introduce bugs in testing: #1092042
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): python-ewoksorange python-ewokscore (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ewoksorange.html
    • 57 days old (needed 5 days)
• python-ewoksppf (- to 0.4.0-3)
  • Migration status for python-ewoksppf (- to 0.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-ewoksppf/0.4.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): python-ewoksppf python-ewokscore (not considered)
    • Build-Depends(-Arch): python-ewoksppf python-pypushflow (not considered)
    • Depends: python-ewoksppf python-ewokscore (not considered)
    • Depends: python-ewoksppf python-pypushflow (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ewoksppf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 57 days old (needed 5 days)
• python-processview (- to 1.4.1-2)
  • Migration status for python-processview (- to 1.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-processview would introduce bugs in testing: #1092043
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): python-processview silx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-processview.html
    • 57 days old (needed 5 days)
• python-pypushflow (- to 0.7.0-3)
  • Migration status for python-pypushflow (- to 0.7.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-pypushflow/0.7.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): python-pypushflow silx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pypushflow.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 57 days old (needed 5 days)
• tomoscan (- to 2.2.0~dev0-2)
  • Migration status for tomoscan (- to 2.2.0~dev0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tomoscan silx (not considered)
    • Depends: tomoscan silx (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): tomoscan nxtomo
    • Depends: tomoscan nxtomo
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomoscan.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for tomoscan/2.2.0~dev0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 57 days old (needed 2 days)
• camping (- to 2.3-2)
  • Migration status for camping (- to 2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating camping would introduce bugs in testing: #1094532
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camping.html
    • autopkgtest for camping/2.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 58 days old (needed 2 days)
• knxd (- to 0.14.70-1)
  • Migration status for knxd (- to 0.14.70-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating knxd would introduce bugs in testing: #1091852
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 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/k/knxd.html
    • 58 days old (needed 5 days)
• liggghts (- to 3.8.0+repack1-12)
  • Migration status for liggghts (- to 3.8.0+repack1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liggghts would introduce bugs in testing: #1091874
    • autopkgtest for liggghts/3.8.0+repack1-12: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/liggghts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 58 days old (needed 5 days)
• opencl-clang-14 (- to 14.0.1-1)
  • Migration status for opencl-clang-14 (- to 14.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): opencl-clang-14 llvm-toolchain-14 (not considered)
    • Depends: opencl-clang-14 llvm-toolchain-14 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): opencl-clang-14 spirv-llvm-translator-14
    • Depends: opencl-clang-14 spirv-llvm-translator-14
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencl-clang-14.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 58 days old (needed 5 days)
• promod3 (- to 3.4.1+ds-1)
  • Migration status for promod3 (- to 3.4.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-promod3/amd64 has unsatisfiable dependency
    • promod3/arm64 has unsatisfiable dependency
    • Build-Depends(-Arch): promod3 openstructure (not considered)
    • Depends: promod3 openstructure (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/promod3.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 58 days old (needed 5 days)
• python-ewokscore (- to 0.15.0-2)
  • Migration status for python-ewokscore (- to 0.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-ewokscore/0.15.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): python-ewokscore silx (not considered)
    • Depends: python-ewokscore silx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ewokscore.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 58 days old (needed 5 days)
• python-nxtomomill (- to 1.1.0-2)
  • Migration status for python-nxtomomill (- to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-nxtomomill/1.1.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): python-nxtomomill nxtomo
    • Build-Depends(-Arch): python-nxtomomill tomoscan
    • Depends: python-nxtomomill nxtomo
    • Depends: python-nxtomomill silx (not considered)
    • Depends: python-nxtomomill tomoscan
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nxtomomill.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 58 days old (needed 5 days)
• python-pycudwt (- to 1.0.2-3)
  • Migration status for python-pycudwt (- to 1.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-pycudwt/1.0.2-3: amd64: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 58 days old (needed 5 days)
• python-scikit-cuda (- to 0.5.1-3)
  • Migration status for python-scikit-cuda (- to 0.5.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-scikit-cuda/0.5.1-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 58 days old (needed 5 days)
• ruby-clockwork (- to 3.0.1-2)
  • Migration status for ruby-clockwork (- to 3.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-clockwork would introduce bugs in testing: #1066730
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-clockwork.html
    • autopkgtest for ruby-clockwork/3.0.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 58 days old (needed 2 days)
• git-ubuntu (- to 1.1-2)
  • Migration status for git-ubuntu (- to 1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for git-ubuntu/1.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-ubuntu.html
    • 59 days old (needed 5 days)
• python-preshed (- to 4.0.0-3)
  • Migration status for python-preshed (- to 4.0.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-preshed python-cymem (not considered)
    • Depends: python-preshed python-cymem (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-preshed.html
    • autopkgtest for python-preshed/4.0.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 59 days old (needed 5 days)
• smiles-scripts (- to 0.2.0+svn754+branch+system+deps-1)
  • Migration status for smiles-scripts (- to 0.2.0+svn754+branch+system+deps-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smiles-scripts would introduce bugs in testing: #1093359
    • autopkgtest for smiles-scripts/0.2.0+svn754+branch+system+deps-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smiles-scripts.html
    • 59 days old (needed 5 days)
• deblur (- to 1.1.1-3)
  • Migration status for deblur (- to 1.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating deblur would introduce bugs in testing: #1091151
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deblur.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for deblur/1.1.1-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 60 days old (needed 5 days)
• iitii (- to 0.0+git20191030.85209e0-3)
  • Migration status for iitii (- to 0.0+git20191030.85209e0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): iitii libmmap-allocator (not considered)
    • Depends: iitii libmmap-allocator (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iitii.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 60 days old (needed 5 days)
• rust-termwiz (- to 0.22.0-2)
  • Migration status for rust-termwiz (- to 0.22.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-termwiz unsatisfiable Build-Depends(-Arch) on amd64: librust-finl-unicode-1+default-dev (>= 1.2-~~)
    • rust-termwiz unsatisfiable Build-Depends(-Arch) on amd64: librust-siphasher-0.3+default-dev
    • rust-termwiz unsatisfiable Build-Depends(-Arch) on amd64: librust-terminfo-0.8+default-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-termwiz.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 60 days old (needed 5 days)
• hugin (- to 2024.0.1+dfsg-1)
  • Migration status for hugin (- to 2024.0.1+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): hugin libvigraimpex (not considered)
    • Depends: hugin libvigraimpex (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: hugin enblend-enfuse
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hugin.html
    • autopkgtest for hugin/2024.0.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 61 days old (needed 2 days)
• mosdepth (- to 0.3.10+ds-1)
  • Migration status for mosdepth (- to 0.3.10+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mosdepth nim (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): mosdepth nim-docopt (not considered)
    • Build-Depends(-Arch): mosdepth nim-hts
    • Build-Depends(-Arch): mosdepth nim-regex
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mosdepth.html
    • autopkgtest for mosdepth/0.3.10+ds-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 61 days old (needed 5 days)
• kaidan (- to 0.9.2-1)
  • Migration status for kaidan (- to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kaidan/amd64 has unsatisfiable dependency
    • kaidan/arm64 has unsatisfiable dependency
    • kaidan/armel has unsatisfiable dependency
    • kaidan/armhf has unsatisfiable dependency
    • kaidan/i386 has unsatisfiable dependency
    • kaidan/mips64el has unsatisfiable dependency
    • kaidan/ppc64el has unsatisfiable dependency
    • kaidan/riscv64 has unsatisfiable dependency
    • kaidan/s390x has unsatisfiable dependency
    • Updating kaidan would introduce bugs in testing: #1089817, #1090237
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kaidan.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 62 days old (needed 5 days)
• rust-pollster (- to 0.4.0-1)
  • Migration status for rust-pollster (- to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-pollster-dev/amd64 has unsatisfiable dependency
    • librust-pollster-dev/arm64 has unsatisfiable dependency
    • librust-pollster-dev/armel has unsatisfiable dependency
    • librust-pollster-dev/armhf has unsatisfiable dependency
    • librust-pollster-dev/i386 has unsatisfiable dependency
    • librust-pollster-dev/mips64el has unsatisfiable dependency
    • librust-pollster-dev/ppc64el has unsatisfiable dependency
    • librust-pollster-dev/riscv64 has unsatisfiable dependency
    • librust-pollster-dev/s390x has unsatisfiable dependency
    • Updating rust-pollster would introduce bugs in testing: #1091355
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-pollster.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• sumaclust (- to 1.0.36+ds-3)
  • Migration status for sumaclust (- to 1.0.36+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sumaclust/1.0.36+ds-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sumaclust.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 62 days old (needed 5 days)
• gpa (- to 0.11.0-1)
  • Migration status for gpa (- to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpa would introduce bugs in testing: #1089914
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 63 days old (needed 5 days)
• lomiri-sync-monitor (- to 0.6.0-4)
  • Migration status for lomiri-sync-monitor (- to 0.6.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lomiri-sync-monitor lomiri-indicator-network (not considered)
    • Depends: lomiri-sync-monitor lomiri-indicator-network (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: lomiri-sync-monitor syncevolution
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-sync-monitor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 63 days old (needed 5 days)
• sia (- to 1.3.0-4)
  • Migration status for sia (- to 1.3.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sia would introduce bugs in testing: #1089970
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sia.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 63 days old (needed 5 days)
• umis (- to 1.0.9-2)
  • Migration status for umis (- to 1.0.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umis would introduce bugs in testing: #1089115
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umis.html
    • autopkgtest for umis/1.0.9-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 63 days old (needed 2 days)
• readucks (- to 0.0.3-6)
  • Migration status for readucks (- to 0.0.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for readucks/0.0.3-6: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/readucks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 64 days old (needed 5 days)
• snippy (- to 4.6.0+dfsg-5)
  • Migration status for snippy (- to 4.6.0+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): snippy snpeff (not considered)
    • Depends: snippy snpeff (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): snippy freebayes (not considered)
    • Depends: snippy freebayes (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snippy.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for snippy/4.6.0+dfsg-5: amd64: Pass, arm64: Pass, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 64 days old (needed 5 days)
• jnettop (- to 0.13.0-2)
  • Migration status for jnettop (- to 0.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jnettop would introduce bugs in testing: #1075103
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jnettop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 65 days old (needed 5 days)
• pbsuite (- to 15.8.24+dfsg-8)
  • Migration status for pbsuite (- to 15.8.24+dfsg-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pbsuite would introduce bugs in testing: #1091721
    • autopkgtest for pbsuite/15.8.24+dfsg-8: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pbsuite.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 65 days old (needed 5 days)
• wapiti (- to 3.2.2+dfsg-1)
  • Migration status for wapiti (- to 3.2.2+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wapiti mitmproxy (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wapiti.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 65 days old (needed 5 days)
• resteasy (- to 3.6.2-3)
  • Migration status for resteasy (- to 3.6.2-3): 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 66 days old (needed 5 days)
• python-aiobotocore (- to 2.13.1-1.1)
  • Migration status for python-aiobotocore (- to 2.13.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiobotocore would introduce bugs in testing: #1091485
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiobotocore.html
    • 67 days old (needed 5 days)
• nxtomo (- to 1.3.0.dev9-1)
  • Migration status for nxtomo (- to 1.3.0.dev9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nxtomo silx (not considered)
    • Depends: nxtomo silx (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nxtomo.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 68 days old (needed 5 days)
• open-adventure (- to 1.20-1)
  • Migration status for open-adventure (- to 1.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating open-adventure would introduce bugs in testing: #1091064
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open-adventure.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 68 days old (needed 5 days)
• rust-libyml (- to 0.0.5-2)
  • Migration status for rust-libyml (- to 0.0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-libyml would introduce bugs in testing: #1094422
    • autopkgtest for rust-libyml/0.0.5-2: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libyml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 68 days old (needed 5 days)
• rust-serde-yml (- to 0.0.12-2)
  • Migration status for rust-serde-yml (- to 0.0.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-serde-yml would introduce bugs in testing: #1094419
    • Build-Depends(-Arch): rust-serde-yml rust-libyml (not considered)
    • Depends: rust-serde-yml rust-libyml (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-serde-yml.html
    • autopkgtest for rust-serde-yml/0.0.12-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 68 days old (needed 2 days)
• circlator (- to 1.5.6-12)
  • Migration status for circlator (- to 1.5.6-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for circlator/1.5.6-12: amd64: Pass, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): circlator canu (not considered)
    • Depends: circlator canu (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/circlator.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 69 days old (needed 5 days)
• gutenprint (- to 5.3.4.20220624T01008808d602-4)
  • Migration status for gutenprint (- to 5.3.4.20220624T01008808d602-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gutenprint/5.3.4.20220624T01008808d602-4: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gutenprint.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 69 days old (needed 5 days)
• rebar3 (3.19.0-1 to 3.23.0-3)
  • Migration status for rebar3 (3.19.0-1 to 3.23.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rebar3 erlang (not considered)
    • Depends: rebar3 erlang (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Updating rebar3 will fix bugs in testing: #1092716
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rebar3.html
    • autopkgtest for rebar3/3.23.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 69 days old (needed 2 days)
• tgl (- to 2.0.1+git20160323.ffb04cac-4)
  • Migration status for tgl (- to 2.0.1+git20160323.ffb04cac-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tgl would introduce bugs in testing: #1087142
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tgl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 69 days old (needed 5 days)
• ensmallen (2.21.1-1 to 2.22.1-1)
  • Migration status for ensmallen (2.21.1-1 to 2.22.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ensmallen/2.22.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating ensmallen will fix bugs in testing: #1092437
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ensmallen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 70 days old (needed 5 days)
• rust-cargo-test-support (- to 0.3.0-1)
  • Migration status for rust-cargo-test-support (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-cargo-test-support-dev/amd64 has unsatisfiable dependency
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-pasetors-0.6+default-dev (>= 0.6.8-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-pasetors-0.6+paserk-dev (>= 0.6.8-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-pasetors-0.6+serde-dev (>= 0.6.8-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-pasetors-0.6+std-dev (>= 0.6.8-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-pasetors-0.6+v3-dev (>= 0.6.8-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+default-dev (>= 0.6.9-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+diff-dev (>= 0.6.9-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+dir-dev (>= 0.6.9-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+json-dev (>= 0.6.9-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+regex-dev (>= 0.6.9-~~)
    • rust-cargo-test-support unsatisfiable Build-Depends(-Arch) on amd64: librust-snapbox-0.6+term-svg-dev (>= 0.6.9-~~)
    • Not built on buildd: arch amd64 binaries uploaded by debian@fabian.gruenbichler.email
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cargo-test-support.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 70 days old (needed 5 days)
• rust-state (- to 0.6.0-1)
  • Migration status for rust-state (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-state/0.6.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-state.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 70 days old (needed 5 days)
• zeroc-ice (- to 3.7.10-3)
  • Migration status for zeroc-ice (- to 3.7.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-zeroc-ice/amd64 has unsatisfiable dependency
    • python3-zeroc-ice/arm64 has unsatisfiable dependency
    • python3-zeroc-ice/armel has unsatisfiable dependency
    • python3-zeroc-ice/armhf has unsatisfiable dependency
    • python3-zeroc-ice/i386 has unsatisfiable dependency
    • python3-zeroc-ice/mips64el has unsatisfiable dependency
    • python3-zeroc-ice/ppc64el has unsatisfiable dependency
    • python3-zeroc-ice/riscv64 has unsatisfiable dependency
    • python3-zeroc-ice/s390x has unsatisfiable dependency
    • Updating zeroc-ice would introduce bugs in testing: #1092441
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zeroc-ice.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 70 days old (needed 5 days)
• pushpin (- to 1.39.1-3)
  • Migration status for pushpin (- to 1.39.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pushpin would introduce bugs in testing: #1084517
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pushpin.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 71 days old (needed 5 days)
• python-rosettasciio (- to 0.6-1)
  • Migration status for python-rosettasciio (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-rosettasciio/amd64 has unsatisfiable dependency
    • python3-rosettasciio/armel has unsatisfiable dependency
    • python3-rosettasciio/i386 has unsatisfiable dependency
    • python3-rosettasciio/mips64el has unsatisfiable dependency
    • python3-rosettasciio/ppc64el has unsatisfiable dependency
    • Updating python-rosettasciio would introduce bugs in testing: #1087285, #1089634
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): python-rosettasciio python-sparse (not considered)
    • Build-Depends(-Arch): python-rosettasciio pyusid (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-rosettasciio.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 71 days old (needed 5 days)
• rebar (2.6.4-4 to 2.6.4-5)
  • Migration status for rebar (2.6.4-4 to 2.6.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rebar unsatisfiable Build-Depends(-Arch) on mips64el: erlang-dev (>= 1:27)
    • missing build on mips64el
    • Build-Depends(-Arch): rebar erlang (not considered)
    • Depends: rebar erlang (not considered)
  • Additional info:
    • Updating rebar will fix bugs in testing: #1092717
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rebar.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 71 days old (needed 5 days)
• intel-graphics-compiler (- to 1.0.17791.18-1)
  • Migration status for intel-graphics-compiler (- to 1.0.17791.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-graphics-compiler would introduce bugs in testing: #1061213
    • Build-Depends(-Arch): intel-graphics-compiler intel-vc-intrinsics (not considered)
    • Build-Depends(-Arch): intel-graphics-compiler llvm-toolchain-14 (not considered)
    • Build-Depends(-Arch): intel-graphics-compiler opencl-clang-14
    • Build-Depends(-Arch): intel-graphics-compiler spirv-llvm-translator-14
    • Depends: intel-graphics-compiler llvm-toolchain-14 (not considered)
    • Depends: intel-graphics-compiler opencl-clang-14
    • Depends: intel-graphics-compiler spirv-llvm-translator-14
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-graphics-compiler.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 72 days old (needed 5 days)
• nim-hts (- to 0.3.25+ds-2)
  • Migration status for nim-hts (- to 0.3.25+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nim-hts nim (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-hts.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for nim-hts/0.3.25+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 72 days old (needed 2 days)
• php-imap (- to 3:1.0.3-1)
  • Migration status for php-imap (- to 3:1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-imap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 72 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• python-easyenergy (- to 2.1.2-1)
  • Migration status for python-easyenergy (- to 2.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-easyenergy would introduce bugs in testing: #1088925
    • 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/python-easyenergy.html
    • autopkgtest for python-easyenergy/2.1.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 72 days old (needed 2 days)
• dnspython (2.6.1-1 to 2.7.0-1)
  • Migration status for dnspython (2.6.1-1 to 2.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dnspython/2.7.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating dnspython will fix bugs in testing: #1091973
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnspython.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 73 days old (needed 5 days)
• gfpoken (- to 1-5)
  • Migration status for gfpoken (- to 1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gfpoken would introduce bugs in testing: #1090226
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfpoken.html
    • New but not reproducible on i386 - info ♻
    • 73 days old (needed 5 days)
• hts-nim-tools (- to 0.2.1-2)
  • Migration status for hts-nim-tools (- to 0.2.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): hts-nim-tools nim (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): hts-nim-tools nim-docopt (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-hts
    • Build-Depends(-Arch): hts-nim-tools nim-kexpr (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-lapper (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-regex
    • Build-Depends(-Arch): hts-nim-tools nim-unicodedb
    • Build-Depends(-Arch): hts-nim-tools nim-unicodeplus
    • Depends: hts-nim-tools nim-hts
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hts-nim-tools.html
    • autopkgtest for hts-nim-tools/0.2.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 73 days old (needed 2 days)
• hiera-eyaml (- to 4.2.0-1.1)
  • Migration status for hiera-eyaml (- to 4.2.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hiera-eyaml would introduce bugs in testing: #1094446
    • autopkgtest for hiera-eyaml/4.2.0-1.1: amd64: Regression or new test ♻, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hiera-eyaml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 74 days old (needed 5 days)
• asymptote (2.91+ds-1 to 2.95+ds-1)
  • Migration status for asymptote (2.91+ds-1 to 2.95+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asymptote would introduce bugs in testing: #1091292
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for asymptote/2.95+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating asymptote will fix bugs in testing: #1088550
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asymptote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Reproducible on i386 - info ♻
    • 75 days old (needed 5 days)
• eye (- to 1:10.30.11~ds-1)
  • Migration status for eye (- to 1:10.30.11~ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eye would introduce bugs in testing: #1088839
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eye.html
    • autopkgtest for eye/1:10.30.11~ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 75 days old (needed 2 days)
• partman-hfs (- to 14)
  • Migration status for partman-hfs (- to 14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • partman-hfs/amd64 has unsatisfiable dependency
    • partman-hfs/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 75 days old (needed 5 days)
• gvm (- to 24.11.1)
  • Migration status for gvm (- to 24.11.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gvm openvas-scanner (not considered)
    • Invalidated by dependency
    • Depends: gvm gsad
    • Depends: gvm gvmd
    • Depends: gvm ospd-openvas
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 76 days old (needed 5 days)
• openvas-scanner (- to 23.13.1-1)
  • Migration status for openvas-scanner (- to 23.13.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): openvas-scanner gvm-libs (not considered)
    • Depends: openvas-scanner gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvas-scanner.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 77 days old (needed 5 days)
• python-pyvista (- to 0.44.1-10)
  • Migration status for python-pyvista (- to 0.44.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyvista would introduce bugs in testing: #1093608
    • autopkgtest for python-pyvista/0.44.1-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyvista.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 77 days old (needed 5 days)
• sctk (- to 2.4.12+dfsg-1)
  • Migration status for sctk (- to 2.4.12+dfsg-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/s/sctk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 77 days old (needed 5 days)
• tinydyndns (- to 0.4.2.debian1-4)
  • Migration status for tinydyndns (- to 0.4.2.debian1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tinydyndns would introduce bugs in testing: #1090038
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 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/tinydyndns.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 77 days old (needed 5 days)
• linphone (- to 5.2.0-5)
  • Migration status for linphone (- to 5.2.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Depends: linphone -> libldap-2.5-0/2.5.19+dfsg-1/amd64
    • Impossible Depends: linphone -> libldap-2.5-0/2.5.19+dfsg-1/arm64
    • Impossible Depends: linphone -> libldap-2.5-0/2.5.19+dfsg-1/armel
    • Impossible Depends: linphone -> libldap-2.5-0/2.5.19+dfsg-1/armhf
    • Impossible Depends: linphone -> libldap-2.5-0/2.5.19+dfsg-1/i386
    • Impossible Depends: linphone -> libldap-2.5-0/2.5.19+dfsg-1/mips64el
    • Impossible Depends: linphone -> libldap-2.5-0/2.5.19+dfsg-1/ppc64el
    • Impossible Depends: linphone -> libldap-2.5-0/2.5.19+dfsg-1/riscv64
    • Impossible Depends: linphone -> libldap-2.5-0/2.5.19+dfsg-1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linphone.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 78 days old (needed 5 days)
• votca (- to 2024.2-1)
  • Migration status for votca (- to 2024.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): votca rdkit (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/votca.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 78 days old (needed 5 days)
• gsad (- to 24.0.0-1)
  • Migration status for gsad (- to 24.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): gsad gvm-libs (not considered)
    • Depends: gsad gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: gsad gvmd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsad.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 79 days old (needed 5 days)
• gvmd (- to 24.0.0-1)
  • Migration status for gvmd (- to 24.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): gvmd gvm-libs (not considered)
    • Depends: gvmd gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: gvmd ospd-openvas
    • Depends: gvmd pg-gvm
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvmd.html
    • autopkgtest for gvmd/24.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 79 days old (needed 2 days)
• mariadb-connector-python (- to 1.1.11-2)
  • Migration status for mariadb-connector-python (- to 1.1.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mariadb-connector-python/1.1.11-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mariadb-connector-python.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 79 days old (needed 5 days)
• pybdsf (- to 1.12.0-1)
  • Migration status for pybdsf (- to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pybdsf would introduce bugs in testing: #1094757, #1095216
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pybdsf.html
    • autopkgtest for pybdsf/1.12.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 79 days old (needed 2 days)
• pytorch-geometric (- to 2.6.1-1)
  • Migration status for pytorch-geometric (- to 2.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytorch-geometric would introduce bugs in testing: #1093354
    • autopkgtest for pytorch-geometric/2.6.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): pytorch-geometric python-ase (not considered)
    • Build-Depends(-Arch): pytorch-geometric rdkit (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-geometric.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 79 days old (needed 5 days)
• parmed (- to 4.3.0+dfsg-2)
  • Migration status for parmed (- to 4.3.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): parmed rdkit (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/parmed.html
    • autopkgtest for parmed/4.3.0+dfsg-2: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 80 days old (needed 2 days)
• pymatgen (- to 2024.10.29+dfsg1-4)
  • Migration status for pymatgen (- to 2024.10.29+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pymatgen would introduce bugs in testing: #1091556, #1092981, #1092982
    • autopkgtest for pymatgen/2024.10.29+dfsg1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): pymatgen phonopy
    • Build-Depends(-Arch): pymatgen python-ase (not considered)
    • Build-Depends(-Arch): pymatgen python-emmet-core
    • Build-Depends(-Arch): pymatgen spglib (not considered)
    • Depends: pymatgen spglib (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymatgen.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 80 days old (needed 5 days)
• tardy (- to 1.28-1)
  • Migration status for tardy (- to 1.28-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/t/tardy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 80 days old (needed 5 days)
• dadadodo (- to 1.04-10)
  • Migration status for dadadodo (- to 1.04-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dadadodo/1.04-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dadadodo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 81 days old (needed 5 days)
• python-mypermobil (- to 0.1.8-1.1)
  • Migration status for python-mypermobil (- to 0.1.8-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-mypermobil would introduce bugs in testing: #1090280
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mypermobil.html
    • 81 days old (needed 5 days)
• ruby-puppet-syntax (- to 4.1.1-1)
  • Migration status for ruby-puppet-syntax (- to 4.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-puppet-syntax would introduce bugs in testing: #1092698
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-puppet-syntax.html
    • autopkgtest for ruby-puppet-syntax/4.1.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 81 days old (needed 2 days)
• vg (- to 1.59.0+ds-0.1)
  • Migration status for vg (- to 1.59.0+ds-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vg would introduce bugs in testing: #1089275
    • autopkgtest for vg/1.59.0+ds-0.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vg.html
    • 81 days old (needed 5 days)
• gosa-plugins-rolemanagement (- to 2.8~git20211022.90f50d1-1.1)
  • Migration status for gosa-plugins-rolemanagement (- to 2.8~git20211022.90f50d1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: gosa-plugins-rolemanagement gosa (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-rolemanagement.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 82 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• python-androidtv (- to 0.0.73-1.1)
  • Migration status for python-androidtv (- to 0.0.73-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: python-androidtv python-adb-shell (not considered)
    • Depends: python-androidtv python-adb-shell (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-androidtv.html
    • autopkgtest for python-androidtv/0.0.73-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 82 days old (needed 2 days)
• afnix (- to 3.8.0-1.1)
  • Migration status for afnix (- to 3.8.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • afnix unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • afnix unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • afnix unsatisfiable Build-Depends(-Arch) on i386: architecture-is-64-bit
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/afnix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 83 days old (needed 5 days)
• gosa (- to 2.8~git20230203.10abe45+dfsg-18)
  • Migration status for gosa (- to 2.8~git20230203.10abe45+dfsg-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: gosa php-imap (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 83 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• lastpass-cli (- to 1.6.1-1)
  • Migration status for lastpass-cli (- to 1.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lastpass-cli would introduce bugs in testing: #1092429
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lastpass-cli.html
    • autopkgtest for lastpass-cli/1.6.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 83 days old (needed 2 days)
• trocla (- to 0.5.1-4)
  • Migration status for trocla (- to 0.5.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • trocla-puppetserver/amd64 has unsatisfiable dependency
    • trocla-puppetserver/arm64 has unsatisfiable dependency
    • trocla-puppetserver/armel has unsatisfiable dependency
    • trocla-puppetserver/armhf has unsatisfiable dependency
    • trocla-puppetserver/i386 has unsatisfiable dependency
    • trocla-puppetserver/mips64el has unsatisfiable dependency
    • trocla-puppetserver/ppc64el has unsatisfiable dependency
    • trocla-puppetserver/riscv64 has unsatisfiable dependency
    • trocla-puppetserver/s390x has unsatisfiable dependency
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/t/trocla.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 83 days old (needed 5 days)
• gourmand (- to 1.1.0+really1.1.0~rc3-6)
  • Migration status for gourmand (- to 1.1.0+really1.1.0~rc3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gourmand/amd64 has unsatisfiable dependency
    • gourmand/arm64 has unsatisfiable dependency
    • Updating gourmand would introduce bugs in testing: #1074472
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gourmand.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 84 days old (needed 5 days)
• slic3r (- to 1.3.0+dfsg1-5.1)
  • Migration status for slic3r (- to 1.3.0+dfsg1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating slic3r would introduce bugs in testing: #1034848
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 84 days old (needed 5 days)
• shotcut (- to 24.11.27+ds-1)
  • Migration status for shotcut (- to 24.11.27+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shotcut.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 85 days old (needed 5 days)
• invesalius (- to 3.1.99998-6)
  • Migration status for invesalius (- to 3.1.99998-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating invesalius would introduce bugs in testing: #1092908
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/invesalius.html
    • autopkgtest for invesalius/3.1.99998-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 86 days old (needed 5 days)
• libgetdata (- to 0.11.0-14)
  • Migration status for libgetdata (- to 0.11.0-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgetdata would introduce bugs in testing: #1094712
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgetdata.html
    • autopkgtest for libgetdata/0.11.0-14: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 86 days old (needed 2 days)
• mayavi2 (- to 4.8.2-4)
  • Migration status for mayavi2 (- to 4.8.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mayavi2/amd64 has unsatisfiable dependency
    • mayavi2/arm64 has unsatisfiable dependency
    • mayavi2/mips64el has unsatisfiable dependency
    • mayavi2/ppc64el has unsatisfiable dependency
    • mayavi2/riscv64 has unsatisfiable dependency
    • mayavi2/s390x has unsatisfiable dependency
    • Updating mayavi2 would introduce bugs in testing: #1092083
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mayavi2.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 riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 86 days old (needed 5 days)
• qt5-ukui-platformtheme (- to 1.0.8-5)
  • Migration status for qt5-ukui-platformtheme (- to 1.0.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qt5-ukui-platformtheme would introduce bugs in testing: #1091097
    • Build-Depends(-Arch): qt5-ukui-platformtheme libqt5xdg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qt5-ukui-platformtheme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 86 days old (needed 5 days)
• jdeb (- to 1.11-1)
  • Migration status for jdeb (- to 1.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jdeb would introduce bugs in testing: #1086278
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jdeb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 87 days old (needed 5 days)
• mystic (- to 0.4.3-2)
  • Migration status for mystic (- to 0.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mystic would introduce bugs in testing: #1090106
    • autopkgtest for mystic/0.4.3-2: amd64: Regression or new test ♻, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mystic.html
    • Reproducible on armhf - info ♻
    • 87 days old (needed 5 days)
• ruby-proc-to-ast (- to 0.2.0-1)
  • Migration status for ruby-proc-to-ast (- to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-proc-to-ast ruby-unparser (not considered)
    • Depends: ruby-proc-to-ast ruby-unparser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-proc-to-ast.html
    • autopkgtest for ruby-proc-to-ast/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 87 days old (needed 2 days)
• pct-scanner-scripts (- to 0.0.4-5)
  • Migration status for pct-scanner-scripts (- to 0.0.4-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pct-scanner-scripts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 88 days old (needed 5 days)
• prewikka (- to 5.2.0-2.3)
  • Migration status for prewikka (- to 5.2.0-2.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: prewikka libpreludedb (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prewikka.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 88 days old (needed 5 days)
• protontricks (- to 1.12.0-1)
  • Migration status for protontricks (- to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for protontricks/1.12.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 88 days old (needed 5 days)
• ruby-fuubar (2.5.0-1 to 2.5.1-1)
  • Migration status for ruby-fuubar (2.5.0-1 to 2.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-fuubar/2.5.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating ruby-fuubar will fix bugs in testing: #1090382
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-fuubar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 88 days old (needed 5 days)
• ruby-unparser (- to 0.6.13-1)
  • Migration status for ruby-unparser (- to 0.6.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-unparser/0.6.13-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-unparser.html
    • 88 days old (needed 5 days)
• gvm-libs (- to 22.14.0-2)
  • Migration status for gvm-libs (- to 22.14.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gvm-libs would introduce bugs in testing: #986529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm-libs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 90 days old (needed 5 days)
• lava (- to 2024.09-1)
  • Migration status for lava (- to 2024.09-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lava would introduce bugs in testing: #1093079
    • autopkgtest for lava/2024.09-1: amd64: Pass, arm64: Pass, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: lava djangorestframework-filters (not considered)
    • Depends: lava lavacli (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lava.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 90 days old (needed 5 days)
• nwall (- to 1.32+debian-10)
  • Migration status for nwall (- to 1.32+debian-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nwall would introduce bugs in testing: #1089824
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nwall.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 90 days old (needed 5 days)
• ruby-redis-clustering (- to 5.3.0-1)
  • Migration status for ruby-redis-clustering (- to 5.3.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
    • autopkgtest for ruby-redis-clustering/5.3.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: Test in progress, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: Test in progress
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-clustering.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 90 days old (needed 5 days)
• dials (- to 3.22.1+dfsg3-1)
  • Migration status for dials (- to 3.22.1+dfsg3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dials would introduce bugs in testing: #1089231
    • autopkgtest for dials/3.22.1+dfsg3-1: amd64: Regression or new test ♻
    • Build-Depends(-Arch): dials pyfai (not considered)
    • Depends: dials pyfai (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dials.html
    • Reproducible on amd64 - info ♻
    • 92 days old (needed 5 days)
• rust-dbus-secret-service (- to 4.0.3-2)
  • Migration status for rust-dbus-secret-service (- to 4.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-dbus-secret-service would introduce bugs in testing: #1081520
    • autopkgtest for rust-dbus-secret-service/4.0.3-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-dbus-secret-service.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 92 days old (needed 5 days)
• rust-secret-service (- to 4.0.0-2)
  • Migration status for rust-secret-service (- to 4.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-secret-service would introduce bugs in testing: #1083230
    • autopkgtest for rust-secret-service/4.0.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-secret-service.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 92 days old (needed 5 days)
• python-cymem (- to 2.0.10-1)
  • Migration status for python-cymem (- to 2.0.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-cymem would introduce bugs in testing: #1093017
    • autopkgtest for python-cymem/2.0.10-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cymem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 93 days old (needed 5 days)
• sardana (- to 3.5.0-2)
  • Migration status for sardana (- to 3.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sardana would introduce bugs in testing: #1091057
    • Build-Depends-Indep: sardana taurus (not considered)
    • Depends: sardana taurus (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sardana.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 93 days old (needed 5 days)
• gensim (- to 4.3.3+dfsg-2)
  • Migration status for gensim (- to 4.3.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gensim/4.3.3+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): gensim pyemd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gensim.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 94 days old (needed 5 days)
• silx (- to 2.1.2+dfsg-1)
  • Migration status for silx (- to 2.1.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating silx would introduce bugs in testing: #1095215
    • autopkgtest for silx/2.1.2+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/silx.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 94 days old (needed 5 days)
• ompl (- to 1.6.0+ds1-1)
  • Migration status for ompl (- to 1.6.0+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ompl would introduce bugs in testing: #1091159
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ompl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 95 days old (needed 5 days)
• valentina (- to 0.7.53~dfsg-2)
  • Migration status for valentina (- to 0.7.53~dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating valentina would introduce bugs in testing: #1087710
    • autopkgtest for valentina/0.7.53~dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/valentina.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 95 days old (needed 5 days)
• netdata (- to 1.47.5-1)
  • Migration status for netdata (- to 1.47.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netdata would introduce bugs in testing: #1042533, #1045145
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 96 days old (needed 5 days)
• golang-github-vulcand-oxy (- to 2.0.0-3)
  • Migration status for golang-github-vulcand-oxy (- to 2.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-vulcand-oxy/2.0.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-vulcand-oxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 97 days old (needed 5 days)
• postgresql-filedump (- to 17.1-1)
  • Migration status for postgresql-filedump (- to 17.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 postgresql-filedump/17.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postgresql-filedump.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 97 days old (needed 5 days)
• python-mp-api (- to 0.43.0rc0-1)
  • Migration status for python-mp-api (- to 0.43.0rc0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-mp-api/0.43.0rc0-1: amd64: Pass, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): python-mp-api pymatgen (not considered)
    • Build-Depends(-Arch): python-mp-api python-emmet-core
    • Depends: python-mp-api pymatgen (not considered)
    • Depends: python-mp-api python-emmet-core
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mp-api.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 98 days old (needed 5 days)
• python-sparse (- to 0.16.0a9-1)
  • Migration status for python-sparse (- to 0.16.0a9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-sparse would introduce bugs in testing: #1055847
    • autopkgtest for python-sparse/0.16.0a9-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/p/python-sparse.html
    • Build-Depends(-Arch): python-sparse numba (not considered)
  • Additional info:
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 98 days old (needed 5 days)
• r-cran-wgcna (- to 1.73-1)
  • Migration status for r-cran-wgcna (- to 1.73-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-wgcna r-cran-fastcluster (not considered)
    • Depends: r-cran-wgcna r-cran-fastcluster (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-wgcna.html
    • autopkgtest for r-cran-wgcna/1.73-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 98 days old (needed 2 days)
• priv-wrapper (- to 1.0.1-4)
  • Migration status for priv-wrapper (- to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for priv-wrapper/1.0.1-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/priv-wrapper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 99 days old (needed 5 days)
• sdml (- to 0.3.1+20241024-1)
  • Migration status for sdml (- to 0.3.1+20241024-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sdml would introduce bugs in testing: #1086384
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on arm64: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on armel: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on armhf: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on i386: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on mips64el: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on riscv64: librust-tree-sitter-sdml-0.3+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-i18n-embed-0.14+default-dev
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-i18n-embed-0.14+desktop-requester-dev
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-i18n-embed-0.14+fluent-system-dev
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-i18n-embed-fl-dev (<< 0.9)
    • sdml unsatisfiable Build-Depends(-Arch) on s390x: librust-tree-sitter-sdml-0.3+default-dev
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 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/sdml.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 99 days old (needed 5 days)
• socket-wrapper (- to 1.4.3-2)
  • Migration status for socket-wrapper (- to 1.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for socket-wrapper/1.4.3-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socket-wrapper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 99 days old (needed 5 days)
• rust-num-prime (- to 0.4.4-2)
  • Migration status for rust-num-prime (- to 0.4.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-num-prime/0.4.4-2: amd64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-num-prime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 102 days old (needed 5 days)
• libgeo-libproj-ffi-perl (- to 1.00-2)
  • Migration status for libgeo-libproj-ffi-perl (- to 1.00-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgeo-libproj-ffi-perl would introduce bugs in testing: #1086655
    • autopkgtest for libgeo-libproj-ffi-perl/1.00-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgeo-libproj-ffi-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 104 days old (needed 5 days)
• ruby-rspec-parameterized-table-syntax (- to 1.0.1-1.1)
  • Migration status for ruby-rspec-parameterized-table-syntax (- 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(-Arch): ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core (not considered)
    • Depends: ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized-table-syntax.html
    • autopkgtest for ruby-rspec-parameterized-table-syntax/1.0.1-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 104 days old (needed 5 days)
• gudhi (- to 3.10.1+dfsg-2)
  • Migration status for gudhi (- to 3.10.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gudhi/3.10.1+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gudhi.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 106 days old (needed 5 days)
• micropython (- to 1.24.0+ds-1)
  • Migration status for micropython (- to 1.24.0+ds-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/m/micropython.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 107 days old (needed 5 days)
• mysql-connector-python (- to 9.1.0-1)
  • Migration status for mysql-connector-python (- to 9.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-connector-python would introduce bugs in testing: #1093881, #923347
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-connector-python.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 108 days old (needed 5 days)
• r-cran-git2r (- to 0.35.0-1)
  • Migration status for r-cran-git2r (- to 0.35.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-git2r would introduce bugs in testing: #1084352
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-git2r.html
    • autopkgtest for r-cran-git2r/0.35.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 108 days old (needed 2 days)
• tortoize (- to 2.0.13-1)
  • Migration status for tortoize (- to 2.0.13-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for tortoize/2.0.13-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tortoize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 108 days old (needed 5 days)
• gssproxy (- to 0.9.2-3)
  • Migration status for gssproxy (- to 0.9.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gssproxy socket-wrapper (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gssproxy.html
    • autopkgtest for gssproxy/0.9.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 109 days old (needed 2 days)
• simple-whip-server (- to 0.0~git20240308-1)
  • Migration status for simple-whip-server (- to 0.0~git20240308-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: simple-whip-server node-websocket (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simple-whip-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 109 days old (needed 5 days)
• cecilia (- to 5.4.1-3)
  • Migration status for cecilia (- to 5.4.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cecilia would introduce bugs in testing: #1089034
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cecilia.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 112 days old (needed 5 days)
• napari-svg (- to 0.2.0-3)
  • Migration status for napari-svg (- to 0.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating napari-svg would introduce bugs in testing: #1095358
    • Build-Depends(-Arch): napari-svg napari (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari-svg.html
    • autopkgtest for napari-svg/0.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 114 days old (needed 2 days)
• eiskaltdcpp (- to 2.4.2-1.2)
  • Migration status for eiskaltdcpp (- to 2.4.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eiskaltdcpp would introduce bugs in testing: #1086098
    • eiskaltdcpp unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • eiskaltdcpp unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • eiskaltdcpp unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • eiskaltdcpp unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • eiskaltdcpp unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • eiskaltdcpp unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • eiskaltdcpp unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • eiskaltdcpp unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • eiskaltdcpp unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eiskaltdcpp.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 115 days old (needed 5 days)
• hyperkitty (- to 1.3.12-1)
  • Migration status for hyperkitty (- to 1.3.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyperkitty would introduce bugs in testing: #1088312
    • autopkgtest for hyperkitty/1.3.12-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyperkitty.html
    • Reproducible on armhf - info ♻
    • 115 days old (needed 5 days)
• kel-agent (- to 0.4.6-2.1)
  • Migration status for kel-agent (- to 0.4.6-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kel-agent would introduce bugs in testing: #1033710
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kel-agent.html
    • autopkgtest for kel-agent/0.4.6-2.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 115 days old (needed 2 days)
• xraylarch (- to 0.9.81+ds1-2)
  • Migration status for xraylarch (- to 0.9.81+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xraylarch silx (not considered)
    • Depends: xraylarch silx (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): xraylarch pyfai (not considered)
    • Build-Depends(-Arch): xraylarch pymatgen (not considered)
    • Build-Depends(-Arch): xraylarch python-mp-api (not considered)
    • Depends: xraylarch pyfai (not considered)
    • Depends: xraylarch pymatgen (not considered)
    • Depends: xraylarch python-mp-api (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xraylarch.html
    • autopkgtest for xraylarch/0.9.81+ds1-2: amd64: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 115 days old (needed 2 days)
• haskell-lambdabot-novelty-plugins (- to 5.3.1.2-1)
  • Migration status for haskell-lambdabot-novelty-plugins (- to 5.3.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): haskell-lambdabot-novelty-plugins haskell-misfortune (not considered)
    • Build-Depends-Indep: haskell-lambdabot-novelty-plugins haskell-misfortune (not considered)
    • Depends: haskell-lambdabot-novelty-plugins haskell-misfortune (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-novelty-plugins.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 116 days old (needed 5 days)
• haskell-misfortune (- to 0.1.2.1-4)
  • Migration status for haskell-misfortune (- to 0.1.2.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • haskell-misfortune/amd64 has unsatisfiable dependency
    • haskell-misfortune/arm64 has unsatisfiable dependency
    • haskell-misfortune/armel has unsatisfiable dependency
    • haskell-misfortune/armhf has unsatisfiable dependency
    • haskell-misfortune/i386 has unsatisfiable dependency
    • haskell-misfortune/mips64el has unsatisfiable dependency
    • haskell-misfortune/ppc64el has unsatisfiable dependency
    • haskell-misfortune/riscv64 has unsatisfiable dependency
    • haskell-misfortune/s390x has unsatisfiable dependency
    • Updating haskell-misfortune would introduce bugs in testing: #1061618
    • Build-Depends(-Arch): haskell-misfortune haskell-regex-pcre (not considered)
    • Build-Depends-Indep: haskell-misfortune haskell-regex-pcre (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-misfortune.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 116 days old (needed 5 days)
• haskell-regex-pcre (- to 0.95.0.0-5)
  • Migration status for haskell-regex-pcre (- to 0.95.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-regex-pcre-dev/amd64 has unsatisfiable dependency
    • libghc-regex-pcre-dev/arm64 has unsatisfiable dependency
    • libghc-regex-pcre-dev/armel has unsatisfiable dependency
    • libghc-regex-pcre-dev/armhf has unsatisfiable dependency
    • libghc-regex-pcre-dev/i386 has unsatisfiable dependency
    • libghc-regex-pcre-dev/mips64el has unsatisfiable dependency
    • libghc-regex-pcre-dev/ppc64el has unsatisfiable dependency
    • libghc-regex-pcre-dev/riscv64 has unsatisfiable dependency
    • libghc-regex-pcre-dev/s390x has unsatisfiable dependency
    • Updating haskell-regex-pcre would introduce bugs in testing: #1000067
    • haskell-regex-pcre unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • haskell-regex-pcre unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • haskell-regex-pcre unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • haskell-regex-pcre unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • haskell-regex-pcre unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • haskell-regex-pcre unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • haskell-regex-pcre unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • haskell-regex-pcre unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • haskell-regex-pcre unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-regex-pcre.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 116 days old (needed 5 days)
• lambdabot (- to 5.3.1.2-1)
  • Migration status for lambdabot (- to 5.3.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): lambdabot haskell-lambdabot-novelty-plugins (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lambdabot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 116 days old (needed 5 days)
• python-aiodhcpwatcher (- to 1.0.2-1)
  • Migration status for python-aiodhcpwatcher (- to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiodhcpwatcher.html
    • autopkgtest for python-aiodhcpwatcher/1.0.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 117 days old (needed 2 days)
• rust-fips203-ffi (- to 0.4.1-2)
  • Migration status for rust-fips203-ffi (- to 0.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-fips203-ffi would introduce bugs in testing: #1085021
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fips203-ffi.html
    • autopkgtest for rust-fips203-ffi/0.4.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 117 days old (needed 2 days)
• openstreetmap-carto (- to 5.9.0-1)
  • Migration status for openstreetmap-carto (- to 5.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openstreetmap-carto would introduce bugs in testing: #1088195
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openstreetmap-carto.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 118 days old (needed 5 days)
• sysdig (- to 0.38.1+repack-3)
  • Migration status for sysdig (- to 0.38.1+repack-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sysdig would introduce bugs in testing: #1066959
    • missing build on ppc64el
    • missing build on riscv64
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysdig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 119 days old (needed 5 days)
• gitit (- to 0.15.1.2+dfsg-1)
  • Migration status for gitit (- to 0.15.1.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): gitit haskell-hoauth2 (not considered)
    • Build-Depends-Indep: gitit haskell-hoauth2 (not considered)
    • Depends: gitit haskell-hoauth2 (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/g/gitit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 120 days old (needed 5 days)
• pointpats (- to 2.5.1-1)
  • Migration status for pointpats (- to 2.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pointpats/2.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pointpats.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 120 days old (needed 5 days)
• efitools (- to 1.9.2-3.1)
  • Migration status for efitools (- to 1.9.2-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating efitools would introduce bugs in testing: #1069410
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • missing build on riscv64
    • 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:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/efitools.html
    • 123 days old (needed 5 days)
• glvis (- to 4.3-1)
  • Migration status for glvis (- to 4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • glvis/arm64 has unsatisfiable dependency
    • Updating glvis would introduce bugs in testing: #1085056
    • Not built on buildd: arch arm64 binaries uploaded by tar
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch arm64, not running autopkgtest there
    • 123 days old (needed 5 days)
• haskell-hledger-web (- to 1.32.3-1)
  • Migration status for haskell-hledger-web (- to 1.32.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-hledger-web haskell-base64 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hledger-web.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 123 days old (needed 5 days)
• haskell-hoauth2 (- to 2.10.0-1)
  • Migration status for haskell-hoauth2 (- to 2.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): haskell-hoauth2 haskell-base64 (not considered)
    • Build-Depends-Indep: haskell-hoauth2 haskell-base64 (not considered)
    • Depends: haskell-hoauth2 haskell-base64 (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-hoauth2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 124 days old (needed 5 days)
• python-synologydsm-api (- to 2.5.3-1)
  • Migration status for python-synologydsm-api (- to 2.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-synologydsm-api would introduce bugs in testing: #1084348
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-synologydsm-api.html
    • autopkgtest for python-synologydsm-api/2.5.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 124 days old (needed 2 days)
• phploc (- to 7.0.2-4)
  • Migration status for phploc (- to 7.0.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • phploc/amd64 has unsatisfiable dependency
    • phploc/arm64 has unsatisfiable dependency
    • Updating phploc would introduce bugs in testing: #1092879
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phploc.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 125 days old (needed 5 days)
• sonic-visualiser (- to 5.0.1-1)
  • Migration status for sonic-visualiser (- to 5.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sonic-visualiser unsatisfiable Build-Depends(-Arch) on armel: qt6-pdf-dev
    • sonic-visualiser unsatisfiable Build-Depends(-Arch) on mips64el: qt6-pdf-dev
    • sonic-visualiser unsatisfiable Build-Depends(-Arch) on ppc64el: qt6-pdf-dev
    • sonic-visualiser unsatisfiable Build-Depends(-Arch) on riscv64: qt6-pdf-dev
    • sonic-visualiser unsatisfiable Build-Depends(-Arch) on s390x: qt6-pdf-dev
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 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/sonic-visualiser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 125 days old (needed 5 days)
• gvm-tools (- to 24.8.0-1)
  • Migration status for gvm-tools (- to 24.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): 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/24.8.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 126 days old (needed 5 days)
• python-gvm (- to 24.8.0-1)
  • Migration status for python-gvm (- to 24.8.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/24.8.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 126 days old (needed 2 days)
• binoculars (- to 0.0.19-1)
  • Migration status for binoculars (- to 0.0.19-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): binoculars xrayutilities (not considered)
    • Depends: binoculars xrayutilities (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): binoculars pyfai (not considered)
    • Depends: binoculars pyfai (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binoculars.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for binoculars/0.0.19-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 127 days old (needed 2 days)
• haskell-github (- to 0.29-1)
  • Migration status for haskell-github (- to 0.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-github would introduce bugs in testing: #1085141
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Depends: haskell-github haskell-binary-instances/amd64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-github.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 127 days old (needed 5 days)
• eclipse-wtp (- to 3.35-1)
  • Migration status for eclipse-wtp (- to 3.35-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for eclipse-wtp/3.35-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-wtp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 128 days old (needed 5 days)
• geotranz (- to 3.7-4)
  • Migration status for geotranz (- to 3.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating geotranz would introduce bugs in testing: #1092415
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geotranz.html
    • Reproducible on armhf - info ♻
    • 128 days old (needed 5 days)
• python-homematicip (- to 1.1.2-1)
  • Migration status for python-homematicip (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-homematicip would introduce bugs in testing: #1084768
    • autopkgtest for python-homematicip/1.1.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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/python-homematicip.html
    • 128 days old (needed 5 days)
• eclipse-collections (- to 11.1.0-1)
  • Migration status for eclipse-collections (- to 11.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): eclipse-collections tycho (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-collections.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 129 days old (needed 5 days)
• pcbasic (- to 2.0.7-4)
  • Migration status for pcbasic (- to 2.0.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pcbasic would introduce bugs in testing: #1084701
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcbasic.html
    • autopkgtest for pcbasic/2.0.7-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 129 days old (needed 2 days)
• snpsift (- to 5.2.e+dfsg-1)
  • Migration status for snpsift (- to 5.2.e+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for snpsift/5.2.e+dfsg-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): snpsift snpeff (not considered)
    • Depends: snpsift snpeff (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snpsift.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 129 days old (needed 5 days)
• jalview (- to 2.11.4.0+dfsg-3)
  • Migration status for jalview (- to 2.11.4.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for jalview/2.11.4.0+dfsg-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jalview.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 130 days old (needed 5 days)
• projectreactor (- to 2.0.8-2)
  • Migration status for projectreactor (- to 2.0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating projectreactor would introduce bugs in testing: #1091946
    • Build-Depends(-Arch): projectreactor eclipse-collections
    • Depends: projectreactor eclipse-collections
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/projectreactor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 130 days old (needed 5 days)
• python-xknx (- to 3.2.0-2)
  • Migration status for python-xknx (- to 3.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-xknx would introduce bugs in testing: #1084765
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xknx.html
    • autopkgtest for python-xknx/3.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 130 days old (needed 2 days)
• snpeff (- to 5.2.e+dfsg-1)
  • Migration status for snpeff (- to 5.2.e+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for snpeff/5.2.e+dfsg-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snpeff.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 130 days old (needed 5 days)
• telepathy-ofono (- to 0.3.1-4)
  • Migration status for telepathy-ofono (- to 0.3.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: telepathy-ofono ofono (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telepathy-ofono.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 130 days old (needed 5 days)
• glowing-bear (- to 0.9.0+ds-5)
  • Migration status for glowing-bear (- to 0.9.0+ds-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: glowing-bear ruby-rails-assets-emojione (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glowing-bear.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 131 days old (needed 5 days)
• vala-panel-appmenu (- to 0.7.6+dfsg1-7)
  • Migration status for vala-panel-appmenu (- to 0.7.6+dfsg1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vala-panel-appmenu would introduce bugs in testing: #1091049, #1095102
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vala-panel-appmenu.html
    • Reproducible on armhf - info ♻
    • 131 days old (needed 5 days)
• xfce4-sntray-plugin (- to 0.4.13.1-5)
  • Migration status for xfce4-sntray-plugin (- to 0.4.13.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfce4-sntray-plugin would introduce bugs in testing: #1086771, #1091960
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfce4-sntray-plugin.html
    • Reproducible on armhf - info ♻
    • 131 days old (needed 5 days)
• haskell-base64 (- to 0.4.2.4-4)
  • Migration status for haskell-base64 (- to 0.4.2.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-base64 would introduce bugs in testing: #1057652
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-base64.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 132 days old (needed 5 days)
• r-cran-gbm (- to 2.2.2-1)
  • Migration status for r-cran-gbm (- to 2.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-gbm would introduce bugs in testing: #1064922
    • autopkgtest for r-cran-gbm/2.2.2-1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gbm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 132 days old (needed 5 days)
• jsurf-alggeo (- to 0.4.1+ds-5)
  • Migration status for jsurf-alggeo (- to 0.4.1+ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for jsurf-alggeo/0.4.1+ds-5: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsurf-alggeo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 133 days old (needed 5 days)
• r-cran-rpact (- to 4.1.0-1)
  • Migration status for r-cran-rpact (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-rpact/4.1.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rpact.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 133 days old (needed 5 days)
• kraft (- to 1.2.2-1)
  • Migration status for kraft (- to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kraft/amd64 has unsatisfiable dependency
    • kraft/arm64 has unsatisfiable dependency
    • kraft/armel has unsatisfiable dependency
    • kraft/armhf has unsatisfiable dependency
    • kraft/i386 has unsatisfiable dependency
    • kraft/mips64el has unsatisfiable dependency
    • kraft/ppc64el has unsatisfiable dependency
    • kraft/riscv64 has unsatisfiable dependency
    • kraft/s390x has unsatisfiable dependency
    • Updating kraft would introduce bugs in testing: #1029734, #1088983
    • kraft unsatisfiable Build-Depends(-Arch) on amd64: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on amd64: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on arm64: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on arm64: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on armel: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on armel: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on armhf: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on armhf: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on i386: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on i386: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on mips64el: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on mips64el: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on riscv64: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on riscv64: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on s390x: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on s390x: libkf5akonadicontact-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kraft.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 134 days old (needed 5 days)
• mediawiki (- to 1:1.39.10-1)
  • Migration status for mediawiki (- to 1:1.39.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mediawiki would introduce bugs in testing: #1085453, #1089725
    • autopkgtest for mediawiki/1:1.39.10-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mediawiki.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 134 days old (needed 5 days)
• onionshare (- to 2.6.2-4)
  • Migration status for onionshare (- to 2.6.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating onionshare would introduce bugs in testing: #1091943
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onionshare.html
    • autopkgtest for onionshare/2.6.2-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 134 days old (needed 2 days)
• ruby-rspec-parameterized-core (- to 1.0.0-1.1)
  • Migration status for ruby-rspec-parameterized-core (- to 1.0.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-rspec-parameterized-core ruby-unparser (not considered)
    • Depends: ruby-rspec-parameterized-core ruby-unparser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ruby-rspec-parameterized-core ruby-proc-to-ast
    • Depends: ruby-rspec-parameterized-core ruby-proc-to-ast
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized-core.html
    • autopkgtest for ruby-rspec-parameterized-core/1.0.0-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 134 days old (needed 5 days)
• sepp (- to 4.5.5+dfsg-1)
  • Migration status for sepp (- to 4.5.5+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for sepp/4.5.5+dfsg-1: amd64: Pass, arm64: Test in progress
    • Build-Depends(-Arch): sepp pplacer (not considered)
    • Depends: sepp pplacer (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sepp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 135 days old (needed 5 days)
• xtrx-dkms (- to 0.0.1+git20190320.5ae3a3e-3.6)
  • Migration status for xtrx-dkms (- to 0.0.1+git20190320.5ae3a3e-3.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for xtrx-dkms/0.0.1+git20190320.5ae3a3e-3.6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Regression or new test ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xtrx-dkms.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 136 days old (needed 5 days)
• gitlab-shell (- to 14.35.0+ds1-2)
  • Migration status for gitlab-shell (- to 14.35.0+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab-shell would introduce bugs in testing: #1078811
    • Build-Depends(-Arch): gitlab-shell gitaly (not considered)
    • Built-Using: gitlab-shell gitaly (not considered)
    • Depends: gitlab-shell gitaly (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-shell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 137 days old (needed 5 days)
• python-beartype (- to 0.19.0-1)
  • Migration status for python-beartype (- to 0.19.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-beartype would introduce bugs in testing: #1089017
    • autopkgtest for python-beartype/0.19.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-beartype.html
    • Reproducible on armhf - info ♻
    • 137 days old (needed 5 days)
• ukui-settings-daemon (- to 4.0.0.1-1)
  • Migration status for ukui-settings-daemon (- to 4.0.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ukui-settings-daemon/amd64 has unsatisfiable dependency
    • ukui-settings-daemon/arm64 has unsatisfiable dependency
    • ukui-settings-daemon/armel has unsatisfiable dependency
    • ukui-settings-daemon/armhf has unsatisfiable dependency
    • ukui-settings-daemon/i386 has unsatisfiable dependency
    • ukui-settings-daemon/mips64el has unsatisfiable dependency
    • ukui-settings-daemon/ppc64el has unsatisfiable dependency
    • ukui-settings-daemon/riscv64 has unsatisfiable dependency
    • ukui-settings-daemon/s390x has unsatisfiable dependency
    • Updating ukui-settings-daemon would introduce bugs in testing: #1079812
    • ukui-settings-daemon unsatisfiable Build-Depends(-Arch) on amd64: libkf5screen-dev
    • ukui-settings-daemon unsatisfiable Build-Depends(-Arch) on arm64: libkf5screen-dev
    • ukui-settings-daemon unsatisfiable Build-Depends(-Arch) on armel: libkf5screen-dev
    • ukui-settings-daemon unsatisfiable Build-Depends(-Arch) on armhf: libkf5screen-dev
    • ukui-settings-daemon unsatisfiable Build-Depends(-Arch) on i386: libkf5screen-dev
    • ukui-settings-daemon unsatisfiable Build-Depends(-Arch) on mips64el: libkf5screen-dev
    • ukui-settings-daemon unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5screen-dev
    • ukui-settings-daemon unsatisfiable Build-Depends(-Arch) on riscv64: libkf5screen-dev
    • ukui-settings-daemon unsatisfiable Build-Depends(-Arch) on s390x: libkf5screen-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-settings-daemon.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 138 days old (needed 5 days)
• mnemosyne (- to 2.11+ds1-1)
  • Migration status for mnemosyne (- to 2.11+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mnemosyne would introduce bugs in testing: #1084719
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mnemosyne.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 139 days old (needed 5 days)
• apt-transport-in-toto (- to 0.1.1-5)
  • Migration status for apt-transport-in-toto (- to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apt-transport-in-toto would introduce bugs in testing: #1090090
    • Build-Depends(-Arch): apt-transport-in-toto in-toto (not considered)
    • Depends: apt-transport-in-toto in-toto (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt-transport-in-toto.html
    • Reproducible on armhf - info ♻
    • 140 days old (needed 5 days)
• ruby-premailer (- to 1.27.0-1)
  • Migration status for ruby-premailer (- to 1.27.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-premailer would introduce bugs in testing: #1073370
    • autopkgtest for ruby-premailer/1.27.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-premailer.html
    • 140 days old (needed 5 days)
• smifb2 (- to 2.4.0-2)
  • Migration status for smifb2 (- to 2.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smifb2 would introduce bugs in testing: #1089505
    • autopkgtest for smifb2/2.4.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: No tests, superficial or marked flaky ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smifb2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 140 days old (needed 5 days)
• php-horde-db (- to 2.4.1-8.1)
  • Migration status for php-horde-db (- to 2.4.1-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-db would introduce bugs in testing: #1089726
    • autopkgtest for php-horde-db/2.4.1-8.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-db.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 141 days old (needed 5 days)
• python-calendra (- to 7.9.1-1)
  • Migration status for python-calendra (- to 7.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-calendra would introduce bugs in testing: #1078636, #1092399
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-calendra.html
    • Reproducible on armhf - info ♻
    • 141 days old (needed 5 days)
• haskell-cryptohash-cryptoapi (- to 0.1.4-9)
  • Migration status for haskell-cryptohash-cryptoapi (- to 0.1.4-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-cryptohash-cryptoapi would introduce bugs in testing: #1082561
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cryptohash-cryptoapi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 143 days old (needed 5 days)
• nvchecker (- to 2.15.1-0.1)
  • Migration status for nvchecker (- to 2.15.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvchecker would introduce bugs in testing: #1082628
    • autopkgtest for nvchecker/2.15.1-0.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nvchecker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 143 days old (needed 5 days)
• opensm (- to 3.3.23-3)
  • Migration status for opensm (- to 3.3.23-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensm would introduce bugs in testing: #1090984
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 143 days old (needed 5 days)
• plover (- to 4.0.0~rc2-0.4)
  • Migration status for plover (- to 4.0.0~rc2-0.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating plover would introduce bugs in testing: #1084319
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plover.html
    • 143 days old (needed 5 days)
• python-cobra (- to 0.29.1-1)
  • Migration status for python-cobra (- to 0.29.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-cobra would introduce bugs in testing: #1092791
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cobra.html
    • autopkgtest for python-cobra/0.29.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 143 days old (needed 2 days)
• haskell-options (- to 1.2.1.2-1)
  • Migration status for haskell-options (- to 1.2.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-options would introduce bugs in testing: #1082184
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • 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/h/haskell-options.html
    • 145 days old (needed 5 days)
• haskell-set-extra (- to 1.4.2-1)
  • Migration status for haskell-set-extra (- to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-set-extra would introduce bugs in testing: #1081387
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-set-extra.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• lapackpp (- to 2024.05.31-1)
  • Migration status for lapackpp (- to 2024.05.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lapackpp would introduce bugs in testing: #1074641
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lapackpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• unknown-horizons (- to 2019.1-8)
  • Migration status for unknown-horizons (- to 2019.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unknown-horizons would introduce bugs in testing: #1089495
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unknown-horizons.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• pg-gvm (- to 22.6.5-2)
  • Migration status for pg-gvm (- to 22.6.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pg-gvm gvm-libs (not considered)
    • Depends: pg-gvm gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-gvm.html
    • autopkgtest for pg-gvm/22.6.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 146 days old (needed 2 days)
• rust-openpgp-card-state (- to 0.3.1-1)
  • Migration status for rust-openpgp-card-state (- to 0.3.1-1): 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
    • Build-Depends(-Arch): rust-openpgp-card-state rust-keyring (not considered)
    • Depends: rust-openpgp-card-state rust-keyring (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-openpgp-card-state.html
    • autopkgtest for rust-openpgp-card-state/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 146 days old (needed 2 days)
• coremltools (- to 8.0-1)
  • Migration status for coremltools (- to 8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating coremltools would introduce bugs in testing: #1077292
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coremltools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 147 days old (needed 5 days)
• freesas (- to 2024.9.0-1)
  • Migration status for freesas (- to 2024.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-freesas/amd64 has unsatisfiable dependency
    • python3-freesas/arm64 has unsatisfiable dependency
    • python3-freesas/armel has unsatisfiable dependency
    • python3-freesas/armhf has unsatisfiable dependency
    • python3-freesas/i386 has unsatisfiable dependency
    • python3-freesas/mips64el has unsatisfiable dependency
    • python3-freesas/ppc64el has unsatisfiable dependency
    • python3-freesas/riscv64 has unsatisfiable dependency
    • Updating freesas would introduce bugs in testing: #1088040, #1092054
    • Build-Depends(-Arch): freesas pyfai (not considered)
    • Build-Depends(-Arch): freesas silx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freesas.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • 147 days old (needed 5 days)
• haskell-presburger (- to 1.3.1-11)
  • Migration status for haskell-presburger (- to 1.3.1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-presburger would introduce bugs in testing: #1085437
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-presburger.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 147 days old (needed 5 days)
• haskell-cmark-gfm (- to 0.2.5+ds1-3)
  • Migration status for haskell-cmark-gfm (- to 0.2.5+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-cmark-gfm would introduce bugs in testing: #1092404
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm-extensions0.29.0.gfm.6/0.29.0.gfm.6-6+b2/riscv64
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm-extensions0.29.0.gfm.6/0.29.0.gfm.6-6+b3/amd64
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm-extensions0.29.0.gfm.6/0.29.0.gfm.6-6+b3/arm64
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm-extensions0.29.0.gfm.6/0.29.0.gfm.6-6+b3/armel
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm-extensions0.29.0.gfm.6/0.29.0.gfm.6-6+b3/armhf
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm-extensions0.29.0.gfm.6/0.29.0.gfm.6-6+b3/i386
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm-extensions0.29.0.gfm.6/0.29.0.gfm.6-6+b3/mips64el
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm-extensions0.29.0.gfm.6/0.29.0.gfm.6-6+b3/ppc64el
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm-extensions0.29.0.gfm.6/0.29.0.gfm.6-6+b3/s390x
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm0.29.0.gfm.6/0.29.0.gfm.6-6+b2/riscv64
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm0.29.0.gfm.6/0.29.0.gfm.6-6+b3/amd64
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm0.29.0.gfm.6/0.29.0.gfm.6-6+b3/arm64
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm0.29.0.gfm.6/0.29.0.gfm.6-6+b3/armel
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm0.29.0.gfm.6/0.29.0.gfm.6-6+b3/armhf
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm0.29.0.gfm.6/0.29.0.gfm.6-6+b3/i386
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm0.29.0.gfm.6/0.29.0.gfm.6-6+b3/mips64el
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm0.29.0.gfm.6/0.29.0.gfm.6-6+b3/ppc64el
    • Impossible Depends: haskell-cmark-gfm -> libcmark-gfm0.29.0.gfm.6/0.29.0.gfm.6-6+b3/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cmark-gfm.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 148 days old (needed 5 days)
• gxr-openvr (- to 0.15.1-2.2)
  • Migration status for gxr-openvr (- to 0.15.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): gxr-openvr openvr (not considered)
    • Depends: gxr-openvr openvr (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): gxr-openvr gulkan (not considered)
    • Build-Depends(-Arch): gxr-openvr gxr (not considered)
    • Depends: gxr-openvr gulkan (not considered)
    • Depends: gxr-openvr gxr (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 150 days old (needed 5 days)
• emscripten (3.1.6~dfsg-9 to 3.1.66~dfsg-2)
  • Migration status for emscripten (3.1.6~dfsg-9 to 3.1.66~dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emscripten would introduce bugs in testing: #1081967, #1091015
    • autopkgtest for emscripten/3.1.66~dfsg-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for node-inwasm/0.0.13~git20230419+dfsg-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating emscripten will fix bugs in testing: #1061212, #1085468
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emscripten.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 151 days old (needed 5 days)
• haskell-hcwiid (- to 0.0.6.1-7)
  • Migration status for haskell-hcwiid (- to 0.0.6.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-hcwiid would introduce bugs in testing: #1093530
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hcwiid.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 151 days old (needed 5 days)
• memkind (- to 1.14.0-3.1)
  • Migration status for memkind (- to 1.14.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating memkind would introduce bugs in testing: #1089267
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/memkind.html
    • autopkgtest for memkind/1.14.0-3.1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 152 days old (needed 2 days)
• nrpe-ng (- to 0.2.0-1.3)
  • Migration status for nrpe-ng (- to 0.2.0-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nrpe-ng would introduce bugs in testing: #1087622
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nrpe-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 152 days old (needed 5 days)
• pass-audit (- to 1.2-1.2)
  • Migration status for pass-audit (- to 1.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pass-audit/1.2-1.2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pass-audit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 152 days old (needed 5 days)
• resampy (- to 0.4.3+ds-4)
  • Migration status for resampy (- to 0.4.3+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for resampy/0.4.3+ds-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): resampy numba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resampy.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • 152 days old (needed 5 days)
• purify (- to 4.1.0-1)
  • Migration status for purify (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating purify would introduce bugs in testing: #1092262
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/purify.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 153 days old (needed 5 days)
• meep-mpi-default (- to 1.25.0-6)
  • Migration status for meep-mpi-default (- to 1.25.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for meep-mpi-default/1.25.0-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meep-mpi-default.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 154 days old (needed 5 days)
• rust-keyring (- to 3.2.1-1)
  • Migration status for rust-keyring (- to 3.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-keyring/3.2.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: rust-keyring rust-dbus-secret-service (not considered)
    • Depends: rust-keyring rust-secret-service (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-keyring.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 154 days old (needed 5 days)
• epoptes (- to 23.08-2)
  • Migration status for epoptes (- to 23.08-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating epoptes would introduce bugs in testing: #1084716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epoptes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 156 days old (needed 5 days)
• node-microsoft-fast (- to 0~20240320+ds1-1)
  • Migration status for node-microsoft-fast (- to 0~20240320+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-microsoft-fast would introduce bugs in testing: #1081223
    • 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-microsoft-fast.html
    • autopkgtest for node-microsoft-fast/0~20240320+ds1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 157 days old (needed 5 days)
• oscs (- to 0.0.1)
  • Migration status for oscs (- to 0.0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oscs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 157 days old (needed 5 days)
• python-bellows (- to 0.40.5-1)
  • Migration status for python-bellows (- to 0.40.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-bellows/0.40.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • 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/python-bellows.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 157 days old (needed 5 days)
• python-foobot-async (- to 1.0.1-2)
  • Migration status for python-foobot-async (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-foobot-async would introduce bugs in testing: #1090274
    • autopkgtest for python-foobot-async/1.0.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-foobot-async.html
    • Reproducible on armhf - info ♻
    • 157 days old (needed 5 days)
• pocketsphinx-python (- to 1:0.1.15-7)
  • Migration status for pocketsphinx-python (- to 1:0.1.15-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pocketsphinx-python would introduce bugs in testing: #1088764
    • autopkgtest for pocketsphinx-python/1:0.1.15-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pocketsphinx-python.html
    • Reproducible on armhf - info ♻
    • 158 days old (needed 5 days)
• python-aiowebostv (- to 0.4.2-2)
  • Migration status for python-aiowebostv (- to 0.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-aiowebostv/amd64 has unsatisfiable dependency
    • python3-aiowebostv/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-aiowebostv.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 158 days old (needed 5 days)
• python-aiowithings (- to 3.0.3-2)
  • Migration status for python-aiowithings (- to 3.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiowithings would introduce bugs in testing: #1084327
    • autopkgtest for python-aiowithings/3.0.3-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiowithings.html
    • 158 days old (needed 5 days)
• rust-openssh-sftp-client (- to 0.15.0-1)
  • Migration status for rust-openssh-sftp-client (- 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-openssh-sftp-client rust-openssh-sftp-client-lowlevel (not considered)
    • Depends: rust-openssh-sftp-client rust-openssh-sftp-client-lowlevel (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-openssh-sftp-client.html
    • autopkgtest for rust-openssh-sftp-client/0.15.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 158 days old (needed 5 days)
• rust-openssh-sftp-client-lowlevel (- to 0.7.0-1)
  • Migration status for rust-openssh-sftp-client-lowlevel (- to 0.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): rust-openssh-sftp-client-lowlevel rust-concurrent-arena (not considered)
    • Depends: rust-openssh-sftp-client-lowlevel rust-concurrent-arena (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-openssh-sftp-client-lowlevel.html
    • autopkgtest for rust-openssh-sftp-client-lowlevel/0.7.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 158 days old (needed 5 days)
• gnome-authenticator (- to 4.5.0-1)
  • Migration status for gnome-authenticator (- to 4.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-authenticator would introduce bugs in testing: #1081185, #1091937
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-authenticator.html
    • autopkgtest for gnome-authenticator/4.5.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • New but not reproducible on i386 - info ♻
    • 159 days old (needed 5 days)
• mindthegap (- to 2.3.0-4)
  • Migration status for mindthegap (- to 2.3.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mindthegap/2.3.0-4: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mindthegap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 159 days old (needed 5 days)
• r-cran-filehash (- to 2.4-6-1)
  • Migration status for r-cran-filehash (- to 2.4-6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-filehash/2.4-6-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-filehash.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 160 days old (needed 5 days)
• libvigraimpex (- to 1.12.1+dfsg-1)
  • Migration status for libvigraimpex (- to 1.12.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libvigraimpex would introduce bugs in testing: #1094371
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvigraimpex.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 161 days old (needed 5 days)
• python-auto-pytabs (- to 0.4.0-2)
  • Migration status for python-auto-pytabs (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-auto-pytabs/0.4.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends-Indep: python-auto-pytabs ruff (not considered)
    • Depends: python-auto-pytabs ruff (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-auto-pytabs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 162 days old (needed 5 days)
• weakforced (- to 2.10.2-1)
  • Migration status for weakforced (- to 2.10.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating weakforced would introduce bugs in testing: #1088172
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/w/weakforced.html
    • Build-Depends(-Arch): weakforced getdns
    • Depends: weakforced getdns
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 163 days old (needed 5 days)
• golang-github-traefik-paerser (- to 0.2.0-1)
  • Migration status for golang-github-traefik-paerser (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-traefik-paerser/0.2.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • 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-traefik-paerser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 167 days old (needed 5 days)
• qtox (- to 1.17.6-1)
  • Migration status for qtox (- to 1.17.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for qtox/1.17.6-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 168 days old (needed 5 days)
• gpaw (- to 24.6.0-1)
  • Migration status for gpaw (- to 24.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gpaw/amd64 has unsatisfiable dependency
    • gpaw/arm64 has unsatisfiable dependency
    • gpaw/mips64el has unsatisfiable dependency
    • gpaw/ppc64el has unsatisfiable dependency
    • gpaw/riscv64 has unsatisfiable dependency
    • gpaw/s390x has unsatisfiable dependency
    • Updating gpaw would introduce bugs in testing: #1088823
    • Build-Depends(-Arch): gpaw python-ase (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpaw.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 riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 171 days old (needed 5 days)
• telegram-desktop (- to 4.14.9+ds-1.1)
  • Migration status for telegram-desktop (- to 4.14.9+ds-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telegram-desktop would introduce bugs in testing: #1091237, #1092377
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telegram-desktop.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 171 days old (needed 5 days)
• astra-toolbox (- to 2.1.0-5)
  • Migration status for astra-toolbox (- to 2.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating astra-toolbox would introduce bugs in testing: #1092777
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): astra-toolbox cython-legacy (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 172 days old (needed 5 days)
• ruby-active-model-serializers (- to 0.10.14-1)
  • Migration status for ruby-active-model-serializers (- to 0.10.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-active-model-serializers would introduce bugs in testing: #1095377
    • Build-Depends(-Arch): ruby-active-model-serializers ruby-grape (not considered)
  • 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.14-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 173 days old (needed 2 days)
• trafficserver (- to 9.2.5+ds-1)
  • Migration status for trafficserver (- to 9.2.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • trafficserver/amd64 has unsatisfiable dependency
    • trafficserver/arm64 has unsatisfiable dependency
    • Updating trafficserver would introduce bugs in testing: #1087531, #999938
    • trafficserver unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • trafficserver unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trafficserver.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 173 days old (needed 5 days)
• ukui-media (- to 3.1.1.2-2)
  • Migration status for ukui-media (- to 3.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): ukui-media ukui-control-center (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-media.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 173 days old (needed 5 days)
• golang-github-jesseduffield-asciigraph (- to 0.4.1+git20190605.6d88e39-4)
  • Migration status for golang-github-jesseduffield-asciigraph (- to 0.4.1+git20190605.6d88e39-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-asciigraph would introduce bugs in testing: #1032108
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-asciigraph.html
    • autopkgtest for golang-github-jesseduffield-asciigraph/0.4.1+git20190605.6d88e39-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 174 days old (needed 2 days)
• golang-github-jesseduffield-pty (- to 1.1.3+git20191112.07ed706-3)
  • Migration status for golang-github-jesseduffield-pty (- to 1.1.3+git20191112.07ed706-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-pty would introduce bugs in testing: #1032111
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-pty.html
    • autopkgtest for golang-github-jesseduffield-pty/1.1.3+git20191112.07ed706-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 174 days old (needed 2 days)
• py-libzfs (- to 0.0+git20240510.5ae7d5e-1)
  • Migration status for py-libzfs (- to 0.0+git20240510.5ae7d5e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-libzfs/amd64 has unsatisfiable dependency
    • python3-libzfs/arm64 has unsatisfiable dependency
    • python3-libzfs/armel has unsatisfiable dependency
    • python3-libzfs/armhf has unsatisfiable dependency
    • python3-libzfs/i386 has unsatisfiable dependency
    • python3-libzfs/mips64el has unsatisfiable dependency
    • python3-libzfs/ppc64el has unsatisfiable dependency
    • python3-libzfs/riscv64 has unsatisfiable dependency
    • python3-libzfs/s390x has unsatisfiable dependency
    • Updating py-libzfs would introduce bugs in testing: #1082340, #1093171
    • Build-Depends(-Arch): py-libzfs cython-legacy (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, 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 riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 174 days old (needed 5 days)
• clblas (- to 2.12-6)
  • Migration status for clblas (- to 2.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clblas would introduce bugs in testing: #949767
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clblas.html
    • autopkgtest for clblas/2.12-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 175 days old (needed 2 days)
• pympler (- to 1.1+dfsg1-1)
  • Migration status for pympler (- to 1.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pympler would introduce bugs in testing: #1082154
    • autopkgtest for pympler/1.1+dfsg1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pympler.html
    • Reproducible on armhf - info ♻
    • 175 days old (needed 5 days)
• python-sidpy (- to 0.12.3-3)
  • Migration status for python-sidpy (- to 0.12.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-sidpy python-ase (not considered)
    • Depends: python-sidpy python-ase (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sidpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 175 days old (needed 5 days)
• lomiri-system-settings-online-accounts (- to 0.12-2)
  • Migration status for lomiri-system-settings-online-accounts (- to 0.12-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lomiri-system-settings-online-accounts lomiri-system-settings (not considered)
    • Depends: lomiri-system-settings-online-accounts lomiri-system-settings (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-system-settings-online-accounts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 176 days old (needed 5 days)
• trickle (- to 1.08+ds-1)
  • Migration status for trickle (- to 1.08+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating trickle would introduce bugs in testing: #1081646
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trickle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 176 days old (needed 5 days)
• singularity-container (- to 4.1.5+ds3-1)
  • Migration status for singularity-container (- to 4.1.5+ds3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating singularity-container would introduce bugs in testing: #1029669, #1087556
    • singularity-container/mips64el has unsatisfiable Built-Using on golang-1.21 1.21.6-1
    • singularity-container/mips64el has unsatisfiable Built-Using on golang-github-container-orchestrated-devices-container-device-interface 0.6.1-2
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/singularity-container.html
    • Reproducible on armhf - info ♻
    • 177 days old (needed 5 days)
• ocserv (- to 1.3.0-1)
  • Migration status for ocserv (- 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): ocserv socket-wrapper (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocserv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 178 days old (needed 5 days)
• bluez-firmware (1.2-11.1 to 1.2-12)
  • Migration status for bluez-firmware (1.2-11.1 to 1.2-12): 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)
    • 179 days old (needed 5 days)
• sreview (- to 0.10.0-1)
  • Migration status for sreview (- to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sreview would introduce bugs in testing: #1089440
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sreview.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 181 days old (needed 5 days)
• christianriesen-otp (- to 1.4.3-5)
  • Migration status for christianriesen-otp (- to 1.4.3-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): christianriesen-otp christianriesen-base32 (not considered)
    • Depends: christianriesen-otp christianriesen-base32 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/christianriesen-otp.html
    • autopkgtest for christianriesen-otp/1.4.3-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 182 days old (needed 2 days)
• gosa-plugins-ldapmanager (- to 2.8~git20240614.c540e17-1)
  • Migration status for gosa-plugins-ldapmanager (- to 2.8~git20240614.c540e17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: gosa-plugins-ldapmanager gosa (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-ldapmanager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 182 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• matthiasmullie-minify (- to 1.3.73-1)
  • Migration status for matthiasmullie-minify (- to 1.3.73-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): matthiasmullie-minify matthiasmullie-path-converter (not considered)
    • Depends: matthiasmullie-minify matthiasmullie-path-converter (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matthiasmullie-minify.html
    • autopkgtest for matthiasmullie-minify/1.3.73-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 182 days old (needed 2 days)
• python-aiomodernforms (- to 0.1.8-2)
  • Migration status for python-aiomodernforms (- to 0.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiomodernforms would introduce bugs in testing: #1084326
    • autopkgtest for python-aiomodernforms/0.1.8-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiomodernforms.html
    • Reproducible on armhf - info ♻
    • 182 days old (needed 5 days)
• christianriesen-base32 (- to 1.6.0-4)
  • Migration status for christianriesen-base32 (- to 1.6.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating christianriesen-base32 would introduce bugs in testing: #1092005
    • autopkgtest for christianriesen-base32/1.6.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/christianriesen-base32.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 183 days old (needed 5 days)
• matthiasmullie-path-converter (- to 1.1.3-3)
  • Migration status for matthiasmullie-path-converter (- to 1.1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating matthiasmullie-path-converter would introduce bugs in testing: #1092008
    • autopkgtest for matthiasmullie-path-converter/1.1.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matthiasmullie-path-converter.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 183 days old (needed 5 days)
• photoqt (- to 4.6+ds-1)
  • Migration status for photoqt (- to 4.6+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • photoqt/amd64 has unsatisfiable dependency
    • photoqt/arm64 has unsatisfiable dependency
    • photoqt/armel has unsatisfiable dependency
    • photoqt/armhf has unsatisfiable dependency
    • photoqt/mips64el has unsatisfiable dependency
    • photoqt/ppc64el has unsatisfiable dependency
    • photoqt/riscv64 has unsatisfiable dependency
    • photoqt/s390x has unsatisfiable dependency
    • Updating photoqt would introduce bugs in testing: #1070134, #1086940
    • photoqt unsatisfiable Build-Depends(-Arch) on amd64: libmagick++-6.q16-dev [!kfreebsd-amd64 !kfreebsd-i386]
    • photoqt unsatisfiable Build-Depends(-Arch) on arm64: libmagick++-6.q16-dev [!kfreebsd-amd64 !kfreebsd-i386]
    • photoqt unsatisfiable Build-Depends(-Arch) on armel: libmagick++-6.q16-dev [!kfreebsd-amd64 !kfreebsd-i386]
    • photoqt unsatisfiable Build-Depends(-Arch) on armhf: libmagick++-6.q16-dev [!kfreebsd-amd64 !kfreebsd-i386]
    • photoqt unsatisfiable Build-Depends(-Arch) on mips64el: libmagick++-6.q16-dev [!kfreebsd-amd64 !kfreebsd-i386]
    • photoqt unsatisfiable Build-Depends(-Arch) on ppc64el: libmagick++-6.q16-dev [!kfreebsd-amd64 !kfreebsd-i386]
    • photoqt unsatisfiable Build-Depends(-Arch) on riscv64: libmagick++-6.q16-dev [!kfreebsd-amd64 !kfreebsd-i386]
    • photoqt unsatisfiable Build-Depends(-Arch) on s390x: libmagick++-6.q16-dev [!kfreebsd-amd64 !kfreebsd-i386]
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/photoqt.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 184 days old (needed 5 days)
• python-wyoming (- to 1.6.0-1)
  • Migration status for python-wyoming (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-wyoming/1.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-wyoming.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 184 days old (needed 5 days)
• alpine (- to 2.26+dfsg-2)
  • Migration status for alpine (- to 2.26+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating alpine would introduce bugs in testing: #1089250
    • Impossible Depends: alpine -> libldap-2.5-0/2.5.19+dfsg-1/amd64
    • Impossible Depends: alpine -> libldap-2.5-0/2.5.19+dfsg-1/arm64
    • Impossible Depends: alpine -> libldap-2.5-0/2.5.19+dfsg-1/armel
    • Impossible Depends: alpine -> libldap-2.5-0/2.5.19+dfsg-1/armhf
    • Impossible Depends: alpine -> libldap-2.5-0/2.5.19+dfsg-1/i386
    • Impossible Depends: alpine -> libldap-2.5-0/2.5.19+dfsg-1/mips64el
    • Impossible Depends: alpine -> libldap-2.5-0/2.5.19+dfsg-1/ppc64el
    • Impossible Depends: alpine -> libldap-2.5-0/2.5.19+dfsg-1/riscv64
    • Impossible Depends: alpine -> libldap-2.5-0/2.5.19+dfsg-1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/alpine.html
    • 185 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• looking-glass (- to 0+b6+ds1-1)
  • Migration status for looking-glass (- to 0+b6+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating looking-glass would introduce bugs in testing: #1094308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/looking-glass.html
    • Reproducible on amd64 - info ♻
    • 185 days old (needed 5 days)
• node-http-server (- to 14.1.1+~cs3.14.34-4)
  • Migration status for node-http-server (- to 14.1.1+~cs3.14.34-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-http-server would introduce bugs in testing: #1082992
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-http-server.html
    • autopkgtest for node-http-server/14.1.1+~cs3.14.34-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 185 days old (needed 5 days)
• python-getdns (- to 1.0.0~b1-6)
  • Migration status for python-getdns (- to 1.0.0~b1-6): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): python-getdns getdns
    • Depends: python-getdns getdns
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-getdns.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 185 days old (needed 5 days)
• tracy (- to 0.11.0+ds-1)
  • Migration status for tracy (- to 0.11.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tracy would introduce bugs in testing: #1078703
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tracy.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 185 days old (needed 5 days)
• aioelectricitymaps (- to 1.0.0-2)
  • Migration status for aioelectricitymaps (- to 1.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aioelectricitymaps would introduce bugs in testing: #1092539
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aioelectricitymaps.html
    • autopkgtest for aioelectricitymaps/1.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 186 days old (needed 2 days)
• botch (- to 0.24-5)
  • Migration status for botch (- to 0.24-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • botch/armel has unsatisfiable dependency
    • botch/armhf has unsatisfiable dependency
    • botch/i386 has unsatisfiable dependency
    • botch/mips64el has unsatisfiable dependency
    • Updating botch would introduce bugs in testing: #1092479
    • autopkgtest for botch/0.24-5: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/botch.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • 186 days old (needed 5 days)
• python-emmet-core (- to 0.76.2-1)
  • Migration status for python-emmet-core (- to 0.76.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-emmet-core spglib (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): python-emmet-core pymatgen (not considered)
    • Depends: python-emmet-core pymatgen (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-emmet-core.html
    • autopkgtest for python-emmet-core/0.76.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 186 days old (needed 2 days)
• spectrum2 (- to 2.2.1+dfsg-2)
  • Migration status for spectrum2 (- to 2.2.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): spectrum2 swift-im (not considered)
    • Depends: spectrum2 swift-im (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spectrum2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 186 days old (needed 5 days)
• packagesearch (- to 2.8.3)
  • Migration status for packagesearch (- to 2.8.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating packagesearch would introduce bugs in testing: #1093203
    • Depends: packagesearch debtags (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/packagesearch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 187 days old (needed 5 days)
• gimp-plugin-registry (- to 9.20240808)
  • Migration status for gimp-plugin-registry (- to 9.20240808): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gimp-plugin-registry/amd64 has unsatisfiable dependency
    • gimp-plugin-registry/arm64 has unsatisfiable dependency
    • gimp-plugin-registry/armel has unsatisfiable dependency
    • gimp-plugin-registry/armhf has unsatisfiable dependency
    • gimp-plugin-registry/i386 has unsatisfiable dependency
    • gimp-plugin-registry/mips64el has unsatisfiable dependency
    • gimp-plugin-registry/ppc64el has unsatisfiable dependency
    • gimp-plugin-registry/riscv64 has unsatisfiable dependency
    • Updating gimp-plugin-registry would introduce bugs in testing: #1043232
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on amd64: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on arm64: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on armel: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on armhf: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on i386: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on mips64el: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on ppc64el: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on riscv64: libgimp2.0-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gimp-plugin-registry.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 188 days old (needed 5 days)
• google-guest-agent (- to 20211116.00-6.2)
  • Migration status for google-guest-agent (- to 20211116.00-6.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating google-guest-agent would introduce bugs in testing: #1070319
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/google-guest-agent.html
    • autopkgtest for google-guest-agent/20211116.00-6.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 188 days old (needed 2 days)
• libprelude (- to 5.2.0-5.6)
  • Migration status for libprelude (- to 5.2.0-5.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-prelude/amd64 has unsatisfiable dependency
    • ruby-libprelude/amd64 has unsatisfiable dependency
    • python3-prelude/arm64 has unsatisfiable dependency
    • ruby-libprelude/arm64 has unsatisfiable dependency
    • python3-prelude/armel has unsatisfiable dependency
    • ruby-libprelude/armel has unsatisfiable dependency
    • python3-prelude/armhf has unsatisfiable dependency
    • ruby-libprelude/armhf has unsatisfiable dependency
    • python3-prelude/i386 has unsatisfiable dependency
    • ruby-libprelude/i386 has unsatisfiable dependency
    • python3-prelude/mips64el has unsatisfiable dependency
    • ruby-libprelude/mips64el has unsatisfiable dependency
    • python3-prelude/ppc64el has unsatisfiable dependency
    • ruby-libprelude/ppc64el has unsatisfiable dependency
    • python3-prelude/riscv64 has unsatisfiable dependency
    • ruby-libprelude/riscv64 has unsatisfiable dependency
    • python3-prelude/s390x has unsatisfiable dependency
    • ruby-libprelude/s390x has unsatisfiable dependency
    • Updating libprelude would introduce bugs in testing: #1081473
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libprelude.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 188 days old (needed 5 days)
• ukwm (- to 1.2.3-1)
  • Migration status for ukwm (- to 1.2.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukwm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 188 days old (needed 5 days)
• r-cran-psychtools (- to 2.4.3-1)
  • Migration status for r-cran-psychtools (- to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-psychtools would introduce bugs in testing: #1078401
    • r-cran-psychtools unsatisfiable Build-Depends(-Arch) on amd64: r-cran-rtf
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-psychtools.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 189 days old (needed 5 days)
• python-adb-shell (- to 0.4.4-2)
  • Migration status for python-adb-shell (- to 0.4.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-adb-shell would introduce bugs in testing: #1082192, #1086887
    • python-adb-shell unsatisfiable Build-Depends-Indep on amd64: python3-libusb1
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-adb-shell.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 190 days old (needed 5 days)
• safeeyes (- to 2.1.9-1.1)
  • Migration status for safeeyes (- to 2.1.9-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating safeeyes would introduce bugs in testing: #1077629
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/safeeyes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 190 days old (needed 5 days)
• custodian (- to 2024.6.24-1)
  • Migration status for custodian (- to 2024.6.24-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): custodian pymatgen (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/custodian.html
    • autopkgtest for custodian/2024.6.24-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 191 days old (needed 2 days)
• intel-vc-intrinsics (- to 0.19.0-1)
  • Migration status for intel-vc-intrinsics (- to 0.19.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-vc-intrinsics would introduce bugs in testing: #1070422
    • Build-Depends(-Arch): intel-vc-intrinsics llvm-toolchain-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-vc-intrinsics.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 191 days old (needed 5 days)
• prospector (- to 1.10.3-1)
  • Migration status for prospector (- to 1.10.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): prospector pyroma (not considered)
    • Depends: prospector pyroma (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prospector.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 191 days old (needed 5 days)
• pyfai (- to 2024.05-3)
  • Migration status for pyfai (- to 2024.05-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyfai would introduce bugs in testing: #1095217
    • autopkgtest for pyfai/2024.05-3: amd64: Pass, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): pyfai silx (not considered)
    • Depends: pyfai silx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfai.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 191 days old (needed 5 days)
• wordpress (- to 6.6.1+dfsg1-1)
  • Migration status for wordpress (- to 6.6.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wordpress would introduce bugs in testing: #1089468
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wordpress.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 191 days old (needed 5 days)
• haskell-libxml-sax (- to 0.7.5-15)
  • Migration status for haskell-libxml-sax (- to 0.7.5-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-libxml-sax-doc/amd64 has unsatisfiable dependency
    • libghc-libxml-sax-doc/arm64 has unsatisfiable dependency
    • Updating haskell-libxml-sax would introduce bugs in testing: #1081369
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-libxml-sax.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 193 days old (needed 5 days)
• pychess (- to 1.0.5-0.1)
  • Migration status for pychess (- to 1.0.5-0.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pychess gaviotatb (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pychess.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 194 days old (needed 5 days)
• python-open-meteo (- to 0.3.1-2)
  • Migration status for python-open-meteo (- to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-open-meteo would introduce bugs in testing: #1084343
    • Build-Depends-Indep: python-open-meteo ruff (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-open-meteo.html
    • Reproducible on armhf - info ♻
    • 194 days old (needed 5 days)
• swift-im (- to 5.0~alpha2.145.g12d031cf8+dfsg-4)
  • Migration status for swift-im (- to 5.0~alpha2.145.g12d031cf8+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating swift-im would introduce bugs in testing: #1088140, #1093866
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swift-im.html
    • Reproducible on armhf - info ♻
    • 194 days old (needed 5 days)
• python-directv (- to 0.4.0-2)
  • Migration status for python-directv (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-directv would introduce bugs in testing: #1084331
    • autopkgtest for python-directv/0.4.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-directv.html
    • Reproducible on armhf - info ♻
    • 195 days old (needed 5 days)
• python-thinc (- to 9.0.0-2)
  • Migration status for python-thinc (- to 9.0.0-2): 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/armhf has unsatisfiable dependency
    • python3-thinc/i386 has unsatisfiable dependency
    • python3-thinc/mips64el has unsatisfiable dependency
    • python3-thinc/riscv64 has unsatisfiable dependency
    • python3-thinc/s390x has unsatisfiable dependency
    • Updating python-thinc would introduce bugs in testing: #1082128, #1089717
    • Build-Depends(-Arch): python-thinc cython-legacy (not considered)
    • Build-Depends(-Arch): python-thinc python-cymem (not considered)
    • Build-Depends(-Arch): python-thinc python-preshed
    • Build-Depends(-Arch): python-thinc python-srsly
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-thinc.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 riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 195 days old (needed 5 days)
• python-ase (- to 3.23.0-1)
  • Migration status for python-ase (- to 3.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ase would introduce bugs in testing: #1094768
    • Build-Depends(-Arch): python-ase cod-tools
    • Depends: python-ase spglib (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ase.html
    • autopkgtest for python-ase/3.23.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 196 days old (needed 2 days)
• python-confection (- to 0.1.5-1)
  • Migration status for python-confection (- to 0.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-confection/0.1.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): python-confection python-srsly
    • Depends: python-confection python-srsly
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-confection.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 196 days old (needed 5 days)
• crowdsec (- to 1.4.6-9)
  • Migration status for crowdsec (- to 1.4.6-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crowdsec would introduce bugs in testing: #1081196
    • autopkgtest for crowdsec/1.4.6-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Not built on buildd: upload info for arch mips64el binaries not found
    • Built-Using: crowdsec golang-1.23
    • Built-Using: crowdsec golang-github-mattn-go-runewidth
    • Built-Using: crowdsec golang-golang-x-text
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crowdsec.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 197 days old (needed 5 days)
• pychopper (- to 2.7.10-1)
  • Migration status for pychopper (- to 2.7.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pychopper would introduce bugs in testing: #1082368
    • autopkgtest for pychopper/2.7.10-1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pychopper.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 197 days old (needed 5 days)
• pyroma (- to 4.2-2)
  • Migration status for pyroma (- to 4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyroma would introduce bugs in testing: #1077701
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyroma.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 199 days old (needed 5 days)
• cadabra2 (- to 2.4.3.2-2)
  • Migration status for cadabra2 (- to 2.4.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cadabra2 would introduce bugs in testing: #1061319
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cadabra2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 200 days old (needed 5 days)
• pageedit (- to 2.2.0+dfsg-1)
  • Migration status for pageedit (- to 2.2.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pageedit unsatisfiable Build-Depends(-Arch) on mips64el: qt6-webengine-dev
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pageedit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 200 days old (needed 5 days)
• backuppc (- to 4.4.0-10)
  • Migration status for backuppc (- to 4.4.0-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating backuppc would introduce bugs in testing: #1085289
    • autopkgtest for backuppc/4.4.0-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/backuppc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 201 days old (needed 5 days)
• cider (- to 0.19.0+dfsg-4)
  • Migration status for cider (- to 0.19.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cider would introduce bugs in testing: #1017834, #1071793
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cider.html
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 202 days old (needed 5 days)
• markdown-toc-el (- to 0.1.5-4)
  • Migration status for markdown-toc-el (- to 0.1.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating markdown-toc-el would introduce bugs in testing: #1036359
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/markdown-toc-el.html
    • autopkgtest for markdown-toc-el/0.1.5-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 202 days old (needed 2 days)
• php-enum (- to 4.7.0-1)
  • Migration status for php-enum (- to 4.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-enum would introduce bugs in testing: #1089767
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-enum.html
    • autopkgtest for php-enum/4.7.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 202 days old (needed 2 days)
• cycle-quotes (- to 0.1-6)
  • Migration status for cycle-quotes (- to 0.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cycle-quotes would introduce bugs in testing: #1020192
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cycle-quotes.html
    • 203 days old (needed 5 days)
• emacs-helm-ag (- to 0.59-3)
  • Migration status for emacs-helm-ag (- to 0.59-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-helm-ag would introduce bugs in testing: #1057557
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-helm-ag.html
    • autopkgtest for emacs-helm-ag/0.59-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 203 days old (needed 2 days)
• synfig (- to 1.5.1+dfsg-4)
  • Migration status for synfig (- to 1.5.1+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsynfig0t64/amd64 has unsatisfiable dependency
    • libsynfig0t64/arm64 has unsatisfiable dependency
    • libsynfig0t64/armel has unsatisfiable dependency
    • libsynfig0t64/armhf has unsatisfiable dependency
    • libsynfig0t64/i386 has unsatisfiable dependency
    • libsynfig0t64/mips64el has unsatisfiable dependency
    • libsynfig0t64/ppc64el has unsatisfiable dependency
    • libsynfig0t64/riscv64 has unsatisfiable dependency
    • libsynfig0t64/s390x has unsatisfiable dependency
    • Updating synfig would introduce bugs in testing: #1079335, #1086935
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/synfig.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 203 days old (needed 5 days)
• numba (- to 0.59.1+dfsg-3)
  • Migration status for numba (- to 0.59.1+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-numba/amd64 has unsatisfiable dependency
    • python3-numba/ppc64el has unsatisfiable dependency
    • Updating numba would introduce bugs in testing: #1033907, #1077047, #1086090, #1090292
    • numba unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • numba unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • numba unsatisfiable Build-Depends(-Arch) on i386: architecture-is-64-bit
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): numba llvmlite (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/numba.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 204 days old (needed 5 days)
• python-pymzml (- to 2.5.10+repack1-1)
  • Migration status for python-pymzml (- to 2.5.10+repack1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pymzml would introduce bugs in testing: #1092544
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pymzml.html
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 204 days old (needed 5 days)
• zziplib (0.13.72+dfsg.1-1.2 to 0.13.72+dfsg.1-1.3)
  • Migration status for zziplib (0.13.72+dfsg.1-1.2 to 0.13.72+dfsg.1-1.3): 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 zziplib will fix bugs in testing: #1079553
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zziplib.html
    • 204 days old (needed 5 days)
• vimix (- to 0.7.2+git20221123+ds-3)
  • Migration status for vimix (- to 0.7.2+git20221123+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vimix would introduce bugs in testing: #1075621
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vimix.html
    • 205 days old (needed 5 days)
• pynpoint (- to 0.11.0-3)
  • Migration status for pynpoint (- to 0.11.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pynpoint/amd64 has unsatisfiable dependency
    • python3-pynpoint/arm64 has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynpoint.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 206 days old (needed 5 days)
• hyprpaper (- to 0.7.0-1)
  • Migration status for hyprpaper (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyprpaper would introduce bugs in testing: #1092436
    • Build-Depends(-Arch): hyprpaper wlroots-0.17 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyprpaper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 208 days old (needed 5 days)
• pydrive2 (- to 1.20.0-1)
  • Migration status for pydrive2 (- to 1.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pydrive2 would introduce bugs in testing: #1083031
    • Build-Depends(-Arch): pydrive2 python-oauth2client (not considered)
    • Depends: pydrive2 python-oauth2client (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydrive2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 209 days old (needed 5 days)
• tulip (- to 5.4.0+dfsg-3.1)
  • Migration status for tulip (- to 5.4.0+dfsg-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tulip would introduce bugs in testing: #1092993
    • Build-Depends(-Arch): tulip sip4 (not considered)
    • Depends: tulip sip4 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tulip.html
    • Reproducible on i386 - info ♻
    • 210 days old (needed 5 days)
• ffcv (- to 1.0.0+git20240202+ds-2)
  • Migration status for ffcv (- to 1.0.0+git20240202+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-ffcv/riscv64 has unsatisfiable dependency
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/f/ffcv.html
  • Additional info:
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 211 days old (needed 5 days)
• komposter (- to 0+git20201216+ds-4)
  • Migration status for komposter (- to 0+git20201216+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating komposter would introduce bugs in testing: #1075121
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/komposter.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 212 days old (needed 5 days)
• virtualbox-ext-pack (- to 7.0.20-1)
  • Migration status for virtualbox-ext-pack (- to 7.0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • virtualbox-ext-pack/arm64 has unsatisfiable dependency
    • Depends: virtualbox-ext-pack virtualbox (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 212 days old (needed 5 days)
• ifupdown2 (- to 3.0.0-1.2)
  • Migration status for ifupdown2 (- to 3.0.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ifupdown2 would introduce bugs in testing: #1074250
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ifupdown2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 213 days old (needed 5 days)
• sks (- to 1.1.6+git20210302.c3ba6d5a-4.1)
  • Migration status for sks (- to 1.1.6+git20210302.c3ba6d5a-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sks/armel has unsatisfiable dependency
    • sks/mips64el has unsatisfiable dependency
    • Updating sks would introduce bugs in testing: #1073911, #1093110
    • autopkgtest for sks/1.1.6+git20210302.c3ba6d5a-4.1: amd64: Regression or new test ♻, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sks.html
    • uninstallable on arch armel, not running autopkgtest there
    • 213 days old (needed 5 days)
• crowdsec-custom-bouncer (- to 0.0.15-4)
  • Migration status for crowdsec-custom-bouncer (- to 0.0.15-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
    • Build-Depends(-Arch): crowdsec-custom-bouncer crowdsec (not considered)
    • Build-Depends(-Arch): crowdsec-custom-bouncer golang-github-crowdsecurity-go-cs-bouncer
    • Built-Using: crowdsec-custom-bouncer crowdsec (not considered)
    • Built-Using: crowdsec-custom-bouncer golang-1.23
    • Built-Using: crowdsec-custom-bouncer golang-github-crowdsecurity-go-cs-bouncer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crowdsec-custom-bouncer.html
    • autopkgtest for crowdsec-custom-bouncer/0.0.15-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 214 days old (needed 2 days)
• crowdsec-firewall-bouncer (- to 0.0.25-5)
  • Migration status for crowdsec-firewall-bouncer (- to 0.0.25-5): 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
    • Build-Depends(-Arch): crowdsec-firewall-bouncer crowdsec (not considered)
    • Build-Depends(-Arch): crowdsec-firewall-bouncer golang-github-crowdsecurity-go-cs-bouncer
    • Built-Using: crowdsec-firewall-bouncer crowdsec (not considered)
    • Built-Using: crowdsec-firewall-bouncer golang-1.23
    • Built-Using: crowdsec-firewall-bouncer golang-github-crowdsecurity-go-cs-bouncer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crowdsec-firewall-bouncer.html
    • autopkgtest for crowdsec-firewall-bouncer/0.0.25-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 214 days old (needed 2 days)
• mes (- to 0.27-1)
  • Migration status for mes (- to 0.27-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mes would introduce bugs in testing: #1067952
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mes.html
    • 215 days old (needed 5 days)
• quickemu (- to 4.9.2-1)
  • Migration status for quickemu (- to 4.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • quickemu/armel has unsatisfiable dependency
    • quickemu/armhf has unsatisfiable dependency
    • Updating quickemu would introduce bugs in testing: #1076281
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quickemu.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 215 days old (needed 5 days)
• bibcursed (- to 2.0.1-0.1)
  • Migration status for bibcursed (- to 2.0.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bibcursed would introduce bugs in testing: #1077349
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bibcursed.html
    • 216 days old (needed 5 days)
• mailfront (- to 2.12-3)
  • Migration status for mailfront (- to 2.12-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mailfront cvm (not considered)
    • Depends: mailfront cvm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailfront.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 219 days old (needed 5 days)
• purple-lurch (- to 0.7.0-2.1)
  • Migration status for purple-lurch (- to 0.7.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • purple-lurch/armel has unsatisfiable dependency
    • purple-lurch/armhf has unsatisfiable dependency
    • autopkgtest for purple-lurch/0.7.0-2.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/purple-lurch.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 219 days old (needed 5 days)
• spopt (- to 0.6.1-2)
  • Migration status for spopt (- to 0.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for spopt/0.6.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): spopt pointpats (not considered)
    • Depends: spopt pointpats (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spopt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 219 days old (needed 5 days)
• socklog (- to 2.1.0+repack-5.1)
  • Migration status for socklog (- to 2.1.0+repack-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating socklog would introduce bugs in testing: #1075523
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socklog.html
    • 220 days old (needed 5 days)
• python-cogent (- to 2024.5.7a1+dfsg-3)
  • Migration status for python-cogent (- to 2024.5.7a1+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-cogent would introduce bugs in testing: #1090269
    • python-cogent unsatisfiable Build-Depends(-Arch) on s390x: architecture-is-little-endian
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for python-cogent/2024.5.7a1+dfsg-3: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Build-Depends(-Arch): python-cogent numba (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-cogent.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 222 days old (needed 5 days)
• klystrack (- to 0.20171212-7)
  • Migration status for klystrack (- to 0.20171212-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating klystrack would introduce bugs in testing: #1075115
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/klystrack.html
    • 223 days old (needed 5 days)
• yaramod (- to 3.21.0-1.1)
  • Migration status for yaramod (- to 3.21.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-yaramod/ppc64el has unsatisfiable dependency
    • autopkgtest for yaramod/3.21.0-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Pass, i386: Pass, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yaramod.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 224 days old (needed 5 days)
• miniupnpd (- to 2.3.7-1)
  • Migration status for miniupnpd (- to 2.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating miniupnpd would introduce bugs in testing: #1090753
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/miniupnpd.html
    • autopkgtest for miniupnpd/2.3.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 226 days old (needed 2 days)
• krop (- to 0.6.0-3)
  • Migration status for krop (- to 0.6.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating krop would introduce bugs in testing: #1029735
    • Build-Depends(-Arch): krop pypdf2 (not considered)
    • Depends: krop pypdf2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/krop.html
    • autopkgtest for krop/0.6.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 227 days old (needed 2 days)
• mwrap (- to 1.1.1-3)
  • Migration status for mwrap (- to 1.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mwrap would introduce bugs in testing: #1092433
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mwrap.html
    • autopkgtest for mwrap/1.1.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 227 days old (needed 2 days)
• nohang (- to 0.2.0-2)
  • Migration status for nohang (- to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nohang would introduce bugs in testing: #1088276
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nohang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 227 days old (needed 5 days)
• symfit (- to 0.5.6-3)
  • Migration status for symfit (- to 0.5.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating symfit would introduce bugs in testing: #1078417, #1079756
    • autopkgtest for symfit/0.5.6-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/symfit.html
    • 227 days old (needed 5 days)
• git-remote-hg (- to 1.0.4~ds-2)
  • Migration status for git-remote-hg (- to 1.0.4~ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): git-remote-hg hg-git (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-remote-hg.html
    • autopkgtest for git-remote-hg/1.0.4~ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 228 days old (needed 2 days)
• golang-github-protonmail-gluon (- to 0.17.0-3)
  • Migration status for golang-github-protonmail-gluon (- to 0.17.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-protonmail-gluon/0.17.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-protonmail-gluon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 228 days old (needed 5 days)
• nat-rtsp (- to 0.7+5.3-0.3)
  • Migration status for nat-rtsp (- to 0.7+5.3-0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nat-rtsp would introduce bugs in testing: #1088903
    • autopkgtest for nat-rtsp/0.7+5.3-0.3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: Regression or new test ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nat-rtsp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 228 days old (needed 5 days)
• q2-diversity-lib (- to 2024.5.0-1)
  • Migration status for q2-diversity-lib (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-diversity-lib/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Ignored failure
    • Build-Depends(-Arch): q2-diversity-lib qiime (not considered)
    • Depends: q2-diversity-lib q2-emperor
    • Depends: q2-diversity-lib q2-feature-table (not considered)
    • Depends: q2-diversity-lib qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-diversity-lib.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 228 days old (needed 5 days)
• q2-emperor (- to 2024.5.0-2)
  • Migration status for q2-emperor (- to 2024.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): q2-emperor qiime (not considered)
    • Depends: q2-emperor qiime (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): q2-emperor q2-types (not considered)
    • Depends: q2-emperor q2-types (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-emperor.html
    • autopkgtest for q2-emperor/2024.5.0-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 228 days old (needed 5 days)
• q2-sample-classifier (- to 2024.5.0-2)
  • Migration status for q2-sample-classifier (- to 2024.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-sample-classifier/2024.5.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: Ignored failure, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): q2-sample-classifier qiime (not considered)
    • Depends: q2-sample-classifier q2-feature-table (not considered)
    • Depends: q2-sample-classifier q2-types (not considered)
    • Depends: q2-sample-classifier qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-sample-classifier.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 228 days old (needed 5 days)
• sagenb-export (- to 3.4-1)
  • Migration status for sagenb-export (- to 3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sagenb-export would introduce bugs in testing: #1091611
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sagenb-export.html
    • autopkgtest for sagenb-export/3.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 228 days old (needed 5 days)
• x2goclient (- to 4.1.2.3-3)
  • Migration status for x2goclient (- to 4.1.2.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating x2goclient would introduce bugs in testing: #1089277
    • Impossible Depends: x2goclient -> libldap-2.5-0/2.5.19+dfsg-1/amd64
    • Impossible Depends: x2goclient -> libldap-2.5-0/2.5.19+dfsg-1/arm64
    • Impossible Depends: x2goclient -> libldap-2.5-0/2.5.19+dfsg-1/armel
    • Impossible Depends: x2goclient -> libldap-2.5-0/2.5.19+dfsg-1/armhf
    • Impossible Depends: x2goclient -> libldap-2.5-0/2.5.19+dfsg-1/i386
    • Impossible Depends: x2goclient -> libldap-2.5-0/2.5.19+dfsg-1/mips64el
    • Impossible Depends: x2goclient -> libldap-2.5-0/2.5.19+dfsg-1/ppc64el
    • Impossible Depends: x2goclient -> libldap-2.5-0/2.5.19+dfsg-1/riscv64
    • Impossible Depends: x2goclient -> libldap-2.5-0/2.5.19+dfsg-1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2goclient.html
    • 228 days old (needed 5 days)
• rust-ntpd (- to 1.1.3-1)
  • Migration status for rust-ntpd (- to 1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ntpd/1.1.3-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • autopkgtest for rust-ntpd/blocked-on-ci-infra: riscv64: Ignored failure
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ntpd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 229 days old (needed 5 days)
• gpscorrelate (- to 2.1-2)
  • Migration status for gpscorrelate (- to 2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpscorrelate would introduce bugs in testing: #1076775
    • autopkgtest for gpscorrelate/2.1-2: amd64: Regression or new test ♻, arm64: Test in progress, armel: Regression or new test ♻, armhf: Test in progress, i386: Test in progress, ppc64el: Test in progress, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpscorrelate.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 230 days old (needed 5 days)
• caml-crush (- to 1.0.12-1.2)
  • Migration status for caml-crush (- to 1.0.12-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating caml-crush would introduce bugs in testing: #1074545, #1076869
    • caml-crush unsatisfiable Build-Depends(-Arch) on armhf: ocaml-native-compilers
    • caml-crush unsatisfiable Build-Depends(-Arch) on i386: ocaml-native-compilers
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/caml-crush.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 231 days old (needed 5 days)
• q2-dada2 (- to 2024.5.0-1)
  • Migration status for q2-dada2 (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-dada2/2024.5.0-1: amd64: Regression or new test ♻
    • Build-Depends(-Arch): q2-dada2 qiime (not considered)
    • Depends: q2-dada2 q2-types (not considered)
    • Depends: q2-dada2 qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-dada2.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 231 days old (needed 5 days)
• q2cli (- to 2024.5.0-2)
  • Migration status for q2cli (- to 2024.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • q2cli/amd64 has unsatisfiable dependency
    • q2cli/arm64 has unsatisfiable dependency
    • Updating q2cli would introduce bugs in testing: #1076080
    • Build-Depends(-Arch): q2cli qiime (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/q/q2cli.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 231 days old (needed 5 days)
• slapi-nis (- to 0.60.0-1.1)
  • Migration status for slapi-nis (- to 0.60.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): slapi-nis 389-ds-base (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slapi-nis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 231 days old (needed 5 days)
• cluster3 (- to 1.59+ds-6)
  • Migration status for cluster3 (- to 1.59+ds-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cluster3/amd64 has unsatisfiable dependency
    • Updating cluster3 would introduce bugs in testing: #1092364
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • 232 days old (needed 5 days)
• openttd (- to 14.1-1)
  • Migration status for openttd (- to 14.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): openttd openttd-opengfx (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openttd.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 232 days old (needed 5 days)
• q2-alignment (- to 2024.5.0-1)
  • Migration status for q2-alignment (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-alignment would introduce bugs in testing: #1076318
    • autopkgtest for q2-alignment/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Ignored failure
    • Build-Depends(-Arch): q2-alignment q2-types (not considered)
    • Build-Depends(-Arch): q2-alignment qiime (not considered)
    • Depends: q2-alignment q2-types (not considered)
    • Depends: q2-alignment qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-alignment.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 232 days old (needed 5 days)
• q2-demux (- to 2024.5.0+dfsg-1)
  • Migration status for q2-demux (- to 2024.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-demux would introduce bugs in testing: #1076315
    • autopkgtest for q2-demux/2024.5.0+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-demux q2-types (not considered)
    • Build-Depends(-Arch): q2-demux qiime (not considered)
    • Depends: q2-demux q2-types (not considered)
    • Depends: q2-demux qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-demux.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 232 days old (needed 5 days)
• q2-metadata (- to 2024.5.0+dfsg-1)
  • Migration status for q2-metadata (- to 2024.5.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): q2-metadata qiime (not considered)
    • Depends: q2-metadata qiime (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): q2-metadata q2-quality-filter (not considered)
    • Build-Depends(-Arch): q2-metadata q2-types (not considered)
    • Depends: q2-metadata q2-quality-filter (not considered)
    • Depends: q2-metadata q2-types (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-metadata.html
    • autopkgtest for q2-metadata/2024.5.0+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 232 days old (needed 2 days)
• q2-phylogeny (- to 2024.5.0-1)
  • Migration status for q2-phylogeny (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-phylogeny would introduce bugs in testing: #1076317
    • autopkgtest for q2-phylogeny/2024.5.0-1: amd64: Regression or new test ♻
    • Depends: q2-phylogeny q2-alignment (not considered)
    • Depends: q2-phylogeny q2-types (not considered)
    • Depends: q2-phylogeny qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-phylogeny.html
    • Reproducible on amd64 - info ♻
    • 232 days old (needed 5 days)
• q2-quality-control (- to 2024.5.0-1)
  • Migration status for q2-quality-control (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-quality-control would introduce bugs in testing: #1076914
    • autopkgtest for q2-quality-control/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Ignored failure
    • Build-Depends(-Arch): q2-quality-control q2-feature-table (not considered)
    • Build-Depends(-Arch): q2-quality-control q2-taxa
    • Build-Depends(-Arch): q2-quality-control qiime (not considered)
    • Depends: q2-quality-control q2-taxa
    • Depends: q2-quality-control qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-quality-control.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 232 days old (needed 5 days)
• q2-taxa (- to 2024.5.0+dfsg-1)
  • Migration status for q2-taxa (- to 2024.5.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): q2-taxa qiime (not considered)
    • Depends: q2-taxa qiime (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): q2-taxa q2-types (not considered)
    • Depends: q2-taxa q2-types (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-taxa.html
    • autopkgtest for q2-taxa/2024.5.0+dfsg-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 232 days old (needed 5 days)
• puddletag (- to 2.4.0-1)
  • Migration status for puddletag (- to 2.4.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: puddletag pyacoustid (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puddletag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 233 days old (needed 5 days)
• q2-cutadapt (- to 2024.5.0-1)
  • Migration status for q2-cutadapt (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-cutadapt/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-cutadapt q2-types (not considered)
    • Build-Depends(-Arch): q2-cutadapt qiime (not considered)
    • Depends: q2-cutadapt q2-types (not considered)
    • Depends: q2-cutadapt qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-cutadapt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 233 days old (needed 5 days)
• q2-feature-table (- to 2024.5.0+dfsg-1)
  • Migration status for q2-feature-table (- to 2024.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-feature-table/2024.5.0+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-feature-table q2-types (not considered)
    • Build-Depends(-Arch): q2-feature-table qiime (not considered)
    • Depends: q2-feature-table q2-types (not considered)
    • Depends: q2-feature-table qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-feature-table.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 233 days old (needed 5 days)
• q2-fragment-insertion (- to 2024.5.0-1)
  • Migration status for q2-fragment-insertion (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-fragment-insertion/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-fragment-insertion qiime (not considered)
    • Depends: q2-fragment-insertion q2-types (not considered)
    • Depends: q2-fragment-insertion qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-fragment-insertion.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 233 days old (needed 5 days)
• q2-quality-filter (- to 2024.5.0-1)
  • Migration status for q2-quality-filter (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-quality-filter/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: Ignored failure, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): q2-quality-filter q2-types (not considered)
    • Build-Depends(-Arch): q2-quality-filter qiime (not considered)
    • Depends: q2-quality-filter q2-types (not considered)
    • Depends: q2-quality-filter qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-quality-filter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 233 days old (needed 5 days)
• q2-types (- to 2024.5.0-1)
  • Migration status for q2-types (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-types would introduce bugs in testing: #1076316
    • autopkgtest for q2-types/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-types qiime (not considered)
    • Depends: q2-types qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-types.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 233 days old (needed 5 days)
• qiime (- to 2024.5.0-1)
  • Migration status for qiime (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qiime would introduce bugs in testing: #1076314, #1084668
    • autopkgtest for qiime/2024.5.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qiime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 233 days old (needed 5 days)
• sdpa (- to 7.3.18-1)
  • Migration status for sdpa (- to 7.3.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sdpa/amd64 has unsatisfiable dependency
    • sdpa/arm64 has unsatisfiable dependency
    • sdpa/armhf has unsatisfiable dependency
    • sdpa/i386 has unsatisfiable dependency
    • sdpa/mips64el has unsatisfiable dependency
    • sdpa/ppc64el has unsatisfiable dependency
    • sdpa/riscv64 has unsatisfiable dependency
    • sdpa/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sdpa.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 riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 233 days old (needed 5 days)
• fonts-arapey (- to 0+git20200408-3)
  • Migration status for fonts-arapey (- to 0+git20200408-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-arapey would introduce bugs in testing: #1087299
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-arapey.html
    • 235 days old (needed 5 days)
• libhdr-histogram (- to 0.11.8-4)
  • Migration status for libhdr-histogram (- to 0.11.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libhdr-histogram/0.11.8-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhdr-histogram.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 235 days old (needed 5 days)
• camitk (- to 5.2.0-2)
  • Migration status for camitk (- to 5.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating camitk would introduce bugs in testing: #1091145, #1094895
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camitk.html
    • autopkgtest for camitk/5.2.0-2: amd64: Pass
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 236 days old (needed 2 days)
• ospd-openvas (- to 22.7.1-2)
  • Migration status for ospd-openvas (- to 22.7.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ospd-openvas openvas-scanner (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ospd-openvas.html
    • autopkgtest for ospd-openvas/22.7.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 236 days old (needed 2 days)
• libcypher-parser (- to 0.6.2-0.2)
  • Migration status for libcypher-parser (- to 0.6.2-0.2): 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/libc/libcypher-parser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 237 days old (needed 5 days)
• ubertooth (- to 2018.12.R1-5.2)
  • Migration status for ubertooth (- to 2018.12.R1-5.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ubertooth would introduce bugs in testing: #1076930
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ubertooth.html
    • autopkgtest for ubertooth/2018.12.R1-5.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 237 days old (needed 2 days)
• phnxdeco (- to 0.33-3.2)
  • Migration status for phnxdeco (- to 0.33-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phnxdeco would introduce bugs in testing: #1075385
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phnxdeco.html
    • 238 days old (needed 5 days)
• r-cran-sjstats (- to 0.19.0-1)
  • Migration status for r-cran-sjstats (- to 0.19.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-sjstats r-cran-performance (not considered)
    • Depends: r-cran-sjstats r-cran-performance (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-sjstats r-cran-effectsize (not considered)
    • Build-Depends(-Arch): r-cran-sjstats r-cran-parameters
    • Depends: r-cran-sjstats r-cran-effectsize (not considered)
    • Depends: r-cran-sjstats r-cran-parameters
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sjstats.html
    • autopkgtest for r-cran-sjstats/0.19.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 240 days old (needed 2 days)
• node-websocket (- to 1.0.35+~cs11.0.28-1)
  • Migration status for node-websocket (- to 1.0.35+~cs11.0.28-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for node-websocket/1.0.35+~cs11.0.28-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-websocket.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 241 days old (needed 5 days)
• ntopng (- to 5.2.1+dfsg1-2)
  • Migration status for ntopng (- to 5.2.1+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ntopng would introduce bugs in testing: #1038842, #1090110
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ntopng.html
    • New but not reproducible on armhf - info ♻
    • 241 days old (needed 5 days)
• ruff (- to 0.0.291+dfsg1-4)
  • Migration status for ruff (- to 0.0.291+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruff would introduce bugs in testing: #1074734
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruff.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • 241 days old (needed 5 days)
• gtklock-playerctl-module (- to 2.0.1-1)
  • Migration status for gtklock-playerctl-module (- to 2.0.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gtklock-playerctl-module gtklock (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtklock-playerctl-module.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 242 days old (needed 5 days)
• gtklock-userinfo-module (- to 2.1.0-1)
  • Migration status for gtklock-userinfo-module (- to 2.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gtklock-userinfo-module gtklock (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtklock-userinfo-module.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 242 days old (needed 5 days)
• mailman3 (- to 3.3.8-3.2)
  • Migration status for mailman3 (- to 3.3.8-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mailman3 would introduce bugs in testing: #1084674
    • autopkgtest for mailman3/3.3.8-3.2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: mailman3 mailman-hyperkitty (not considered)
    • Depends: mailman3 mailman-suite
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailman3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 243 days old (needed 5 days)
• pam-krb5-migrate (- to 0.0.11-5.1)
  • Migration status for pam-krb5-migrate (- to 0.0.11-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pam-krb5-migrate would introduce bugs in testing: #1075357
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pam-krb5-migrate.html
    • 243 days old (needed 5 days)
• hilive (- to 2.0a-4)
  • Migration status for hilive (- to 2.0a-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hilive would introduce bugs in testing: #1053499
    • autopkgtest for hilive/2.0a-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hilive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 244 days old (needed 5 days)
• softether-vpn (- to 5.01.9674+git20200806+8181039+dfsg3-1)
  • Migration status for softether-vpn (- to 5.01.9674+git20200806+8181039+dfsg3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating softether-vpn would introduce bugs in testing: #1075525
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/softether-vpn.html
    • 244 days old (needed 5 days)
• streamtuner2 (- to 2.2.2+dfsg-2.1)
  • Migration status for streamtuner2 (- to 2.2.2+dfsg-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating streamtuner2 would introduce bugs in testing: #1084715
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/streamtuner2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 244 days old (needed 5 days)
• archmbox (- to 4.10.0-7)
  • Migration status for archmbox (- to 4.10.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/archmbox.html
    • autopkgtest for archmbox/4.10.0-7: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 245 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• lua-vips (- to 1.1.11-3)
  • Migration status for lua-vips (- to 1.1.11-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lua-vips would introduce bugs in testing: #1073143
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-vips.html
    • autopkgtest for lua-vips/1.1.11-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 245 days old (needed 2 days)
• r-cran-estimatr (- to 1.0.4-1)
  • Migration status for r-cran-estimatr (- to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-estimatr would introduce bugs in testing: #1064921
    • autopkgtest for r-cran-estimatr/1.0.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-estimatr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 246 days old (needed 5 days)
• simh (- to 3.8.1-6.2)
  • Migration status for simh (- to 3.8.1-6.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simh would introduce bugs in testing: #1075511
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simh.html
    • 247 days old (needed 5 days)
• src2tex (- to 2.12h-9.1)
  • Migration status for src2tex (- to 2.12h-9.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating src2tex would introduce bugs in testing: #1075535
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/src2tex.html
    • 247 days old (needed 5 days)
• netdiag (- to 1.2-1.3)
  • Migration status for netdiag (- to 1.2-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netdiag would introduce bugs in testing: #1075311
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netdiag.html
    • 248 days old (needed 5 days)
• gridengine (- to 8.1.9+dfsg-11.1)
  • Migration status for gridengine (- to 8.1.9+dfsg-11.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gridengine would introduce bugs in testing: #1075042
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gridengine.html
    • Reproducible on arm64 - info ♻
    • 249 days old (needed 5 days)
• x2gothinclient (- to 1.5.0.1-10.1)
  • Migration status for x2gothinclient (- to 1.5.0.1-10.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: x2gothinclient x2goclient (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2gothinclient.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 249 days old (needed 5 days)
• python-awkward (- to 2.6.5-1)
  • Migration status for python-awkward (- to 2.6.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-awkward/2.6.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-awkward.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 251 days old (needed 5 days)
• satdump (- to 1.2.0-2)
  • Migration status for satdump (- to 1.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Build-Depends(-Arch): satdump -> libomp-dev/1:16.0-58.1/i386
    • Build-Depends(-Arch): satdump intel-compute-runtime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/satdump.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 253 days old (needed 5 days)
• kokkos (- to 4.3.01-1)
  • Migration status for kokkos (- to 4.3.01-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kokkos unsatisfiable Build-Depends(-Arch) on s390x: libmemkind-dev
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): kokkos memkind (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kokkos.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 254 days old (needed 5 days)
• harden-doc (- to 3.19+nmu3)
  • Migration status for harden-doc (- to 3.19+nmu3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating harden-doc would introduce bugs in testing: #1053602
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/harden-doc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 256 days old (needed 5 days)
• netctl (- to 1.29-1)
  • Migration status for netctl (- to 1.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/n/netctl.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 256 days old (needed 5 days)
• ecryptfs-utils (- to 111-7)
  • Migration status for ecryptfs-utils (- to 111-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ecryptfs-utils would introduce bugs in testing: #1074931
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecryptfs-utils.html
    • 257 days old (needed 5 days)
• eterm (- to 0.9.6-7.2)
  • Migration status for eterm (- to 0.9.6-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eterm would introduce bugs in testing: #1074940
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eterm.html
    • 257 days old (needed 5 days)
• gfxreconstruct (- to 1.0.4+dfsg-1)
  • Migration status for gfxreconstruct (- to 1.0.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gfxreconstruct would introduce bugs in testing: #1081863
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfxreconstruct.html
    • 257 days old (needed 5 days)
• python-pynndescent (- to 0.5.11-1)
  • Migration status for python-pynndescent (- to 0.5.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pynndescent would introduce bugs in testing: #1090284
    • autopkgtest for python-pynndescent/0.5.11-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻
    • Build-Depends(-Arch): python-pynndescent llvmlite (not considered)
    • Build-Depends(-Arch): python-pynndescent numba (not considered)
    • Depends: python-pynndescent llvmlite (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pynndescent.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 257 days old (needed 5 days)
• python-pytray (- to 0.3.5-4)
  • Migration status for python-pytray (- to 0.3.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pytray would introduce bugs in testing: #1092793
    • autopkgtest for python-pytray/0.3.5-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pytray.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 258 days old (needed 5 days)
• gcc-12-cross-mipsen (- to 5+c1)
  • Migration status for gcc-12-cross-mipsen (- to 5+c1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-12-cross-mipsen would introduce bugs in testing: #1089258, #1089889
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-12-cross-mipsen.html
    • New but not reproducible on i386 - info ♻
    • 259 days old (needed 5 days)
• prelude-correlator (- to 5.2.0-1.2)
  • Migration status for prelude-correlator (- to 5.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): prelude-correlator libprelude (not considered)
    • Depends: prelude-correlator libprelude (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prelude-correlator.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 262 days old (needed 5 days)
• libmmap-allocator (- to 0.4.0+git20200122.adbfbe1-2)
  • Migration status for libmmap-allocator (- to 0.4.0+git20200122.adbfbe1-2): 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/libm/libmmap-allocator.html
    • autopkgtest for libmmap-allocator/0.4.0+git20200122.adbfbe1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 263 days old (needed 2 days)
• plm (- to 2.9.2-1.1)
  • Migration status for plm (- to 2.9.2-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: plm scala (not considered)
    • Depends: plm scala (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 263 days old (needed 5 days)
• ripe-atlas-tools (- to 2.3.0-3)
  • Migration status for ripe-atlas-tools (- to 2.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ripe-atlas-tools would introduce bugs in testing: #1018615, #1090166
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ripe-atlas-tools.html
    • 263 days old (needed 5 days)
• ledgersmb (- to 1.6.33+ds-2.2)
  • Migration status for ledgersmb (- to 1.6.33+ds-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ledgersmb would introduce bugs in testing: #1027472
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ledgersmb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 264 days old (needed 5 days)
• tomoyo-tools (- to 2.6.1-20210910-1.1)
  • Migration status for tomoyo-tools (- to 2.6.1-20210910-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomoyo-tools would introduce bugs in testing: #1088729
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomoyo-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 264 days old (needed 5 days)
• unicrypto (- to 0.0.10-2)
  • Migration status for unicrypto (- to 0.0.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unicrypto would introduce bugs in testing: #1090176
    • autopkgtest for unicrypto/0.0.10-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): unicrypto python-mbedtls (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unicrypto.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 264 days old (needed 5 days)
• vanguards (- to 0.3.1-2.4)
  • Migration status for vanguards (- to 0.3.1-2.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vanguards would introduce bugs in testing: #1074750
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vanguards.html
    • 264 days old (needed 5 days)
• x2gobroker (- to 0.0.4.3-4.1)
  • Migration status for x2gobroker (- to 0.0.4.3-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • x2gobroker/amd64 has unsatisfiable dependency
    • x2gobroker/arm64 has unsatisfiable dependency
    • Updating x2gobroker would introduce bugs in testing: #1018666, #1082881, #1082883, #1082884, #1087443
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/x/x2gobroker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 264 days old (needed 5 days)
• pplacer (- to 1.1~alpha19-8)
  • Migration status for pplacer (- to 1.1~alpha19-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pplacer would introduce bugs in testing: #1074546, #1093109
    • autopkgtest for pplacer/1.1~alpha19-8: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pplacer.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 265 days old (needed 5 days)
• ukui-screensaver (- to 3.0.3.3-2)
  • Migration status for ukui-screensaver (- to 3.0.3.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ukui-screensaver ukui-session-manager (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-screensaver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 265 days old (needed 5 days)
• mercurial-evolve (- to 11.1.3-1)
  • Migration status for mercurial-evolve (- to 11.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mercurial-evolve would introduce bugs in testing: #1076081, #1076895
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mercurial-evolve.html
    • 266 days old (needed 5 days)
• tla (- to 1.3.5+dfsg2-1)
  • Migration status for tla (- to 1.3.5+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tla would introduce bugs in testing: #1075579
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tla.html
    • 266 days old (needed 5 days)
• quickml (- to 0.8-2)
  • Migration status for quickml (- to 0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quickml would introduce bugs in testing: #1073471
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quickml.html
    • 267 days old (needed 5 days)
• iptables-netflow (- to 2.6-7)
  • Migration status for iptables-netflow (- to 2.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iptables-netflow would introduce bugs in testing: #1081377, #1089498
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/i/iptables-netflow.html
    • autopkgtest for iptables-netflow/2.6-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 268 days old (needed 5 days)
• ukui-power-manager (- to 4.0.0.1-2)
  • Migration status for ukui-power-manager (- to 4.0.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): ukui-power-manager ukui-control-center (not considered)
    • Depends: ukui-power-manager ukui-control-center (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-power-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 268 days old (needed 5 days)
• photopc (- to 3.07-4)
  • Migration status for photopc (- to 3.07-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating photopc would introduce bugs in testing: #1091307
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/photopc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 270 days old (needed 5 days)
• olive-editor (- to 20230614+ds-2)
  • Migration status for olive-editor (- to 20230614+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • olive-editor/amd64 has unsatisfiable dependency
    • olive-editor/arm64 has unsatisfiable dependency
    • olive-editor/mips64el has unsatisfiable dependency
    • olive-editor/ppc64el has unsatisfiable dependency
    • olive-editor/riscv64 has unsatisfiable dependency
    • olive-editor/s390x has unsatisfiable dependency
    • Updating olive-editor would introduce bugs in testing: #1072441
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/olive-editor.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 riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 272 days old (needed 5 days)
• rust-ahash-0.7 (- to 0.7.8-2)
  • Migration status for rust-ahash-0.7 (- to 0.7.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-ahash-0.7 would introduce bugs in testing: #1077617
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ahash-0.7.html
    • autopkgtest for rust-ahash-0.7/0.7.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 272 days old (needed 2 days)
• cpptraj (- to 5.1.0+dfsg-4)
  • Migration status for cpptraj (- to 5.1.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpptraj would introduce bugs in testing: #1091156
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpptraj.html
    • autopkgtest for cpptraj/5.1.0+dfsg-4: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 275 days old (needed 2 days)
• python-fastparquet (- to 2024.2.0-2)
  • Migration status for python-fastparquet (- to 2024.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-fastparquet/2024.2.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻
    • Build-Depends(-Arch): python-fastparquet python-cramjam (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fastparquet.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 275 days old (needed 5 days)
• liblopsub (- to 1.0.5-1)
  • Migration status for liblopsub (- to 1.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liblopsub would introduce bugs in testing: #1086623, #1089365
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libl/liblopsub.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 277 days old (needed 5 days)
• pyusid (- to 0.0.12-2)
  • Migration status for pyusid (- to 0.0.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyusid would introduce bugs in testing: #1095092
    • Build-Depends(-Arch): pyusid python-sidpy
    • Depends: pyusid python-sidpy
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyusid.html
    • autopkgtest for pyusid/0.0.12-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 277 days old (needed 2 days)
• software-properties (- to 0.99.30-4.1)
  • Migration status for software-properties (- to 0.99.30-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating software-properties would introduce bugs in testing: #1038747, #1088285, #1089720
    • autopkgtest for software-properties/0.99.30-4.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/software-properties.html
    • 277 days old (needed 5 days)
• tfortune (- to 1.0.2-1)
  • Migration status for tfortune (- to 1.0.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tfortune liblopsub (not considered)
    • Depends: tfortune liblopsub (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tfortune.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 277 days old (needed 5 days)
• python-mbedtls (- to 2.10.1-1)
  • Migration status for python-mbedtls (- to 2.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-mbedtls/amd64 has unsatisfiable dependency
    • python3-mbedtls/arm64 has unsatisfiable dependency
    • python3-mbedtls/armel has unsatisfiable dependency
    • python3-mbedtls/armhf has unsatisfiable dependency
    • python3-mbedtls/i386 has unsatisfiable dependency
    • python3-mbedtls/mips64el has unsatisfiable dependency
    • python3-mbedtls/ppc64el has unsatisfiable dependency
    • python3-mbedtls/riscv64 has unsatisfiable dependency
    • python3-mbedtls/s390x has unsatisfiable dependency
    • Updating python-mbedtls would introduce bugs in testing: #1075872
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mbedtls.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 278 days old (needed 5 days)
• coz-profiler (- to 0.2.2-3)
  • Migration status for coz-profiler (- to 0.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating coz-profiler would introduce bugs in testing: #1066941
    • 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 riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for coz-profiler/0.2.2-3: ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coz-profiler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 280 days old (needed 5 days)
• gngb (- to 20060309-6)
  • Migration status for gngb (- to 20060309-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gngb would introduce bugs in testing: #1075020
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gngb.html
    • 280 days old (needed 5 days)
• linux-ftpd-ssl (- to 0.17.36+really0.17-3)
  • Migration status for linux-ftpd-ssl (- to 0.17.36+really0.17-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating linux-ftpd-ssl would introduce bugs in testing: #1075225
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-ftpd-ssl.html
    • 281 days old (needed 5 days)
• rust-yaxpeax-x86 (- to 1.2.2-1)
  • Migration status for rust-yaxpeax-x86 (- to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-yaxpeax-x86-dev/amd64 has unsatisfiable dependency
    • librust-yaxpeax-x86-dev/arm64 has unsatisfiable dependency
    • librust-yaxpeax-x86-dev/armel has unsatisfiable dependency
    • librust-yaxpeax-x86-dev/armhf has unsatisfiable dependency
    • librust-yaxpeax-x86-dev/i386 has unsatisfiable dependency
    • librust-yaxpeax-x86-dev/mips64el has unsatisfiable dependency
    • librust-yaxpeax-x86-dev/ppc64el has unsatisfiable dependency
    • librust-yaxpeax-x86-dev/riscv64 has unsatisfiable dependency
    • librust-yaxpeax-x86-dev/s390x has unsatisfiable dependency
    • Updating rust-yaxpeax-x86 would introduce bugs in testing: #1089100
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on amd64: librust-yaxpeax-arch-0.2+colors-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on amd64: librust-yaxpeax-arch-0.2+std-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on amd64: librust-yaxpeax-arch-0.2+use-serde-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on amd64: librust-yaxpeax-arch-0.2-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on arm64: librust-yaxpeax-arch-0.2+colors-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on arm64: librust-yaxpeax-arch-0.2+std-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on arm64: librust-yaxpeax-arch-0.2+use-serde-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on arm64: librust-yaxpeax-arch-0.2-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on armel: librust-yaxpeax-arch-0.2+colors-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on armel: librust-yaxpeax-arch-0.2+std-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on armel: librust-yaxpeax-arch-0.2+use-serde-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on armel: librust-yaxpeax-arch-0.2-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on armhf: librust-yaxpeax-arch-0.2+colors-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on armhf: librust-yaxpeax-arch-0.2+std-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on armhf: librust-yaxpeax-arch-0.2+use-serde-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on armhf: librust-yaxpeax-arch-0.2-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on i386: librust-yaxpeax-arch-0.2+colors-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on i386: librust-yaxpeax-arch-0.2+std-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on i386: librust-yaxpeax-arch-0.2+use-serde-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on i386: librust-yaxpeax-arch-0.2-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on mips64el: librust-yaxpeax-arch-0.2+colors-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on mips64el: librust-yaxpeax-arch-0.2+std-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on mips64el: librust-yaxpeax-arch-0.2+use-serde-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on mips64el: librust-yaxpeax-arch-0.2-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-yaxpeax-arch-0.2+colors-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-yaxpeax-arch-0.2+std-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-yaxpeax-arch-0.2+use-serde-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on ppc64el: librust-yaxpeax-arch-0.2-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on riscv64: librust-yaxpeax-arch-0.2+colors-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on riscv64: librust-yaxpeax-arch-0.2+std-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on riscv64: librust-yaxpeax-arch-0.2+use-serde-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on riscv64: librust-yaxpeax-arch-0.2-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on s390x: librust-yaxpeax-arch-0.2+colors-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on s390x: librust-yaxpeax-arch-0.2+std-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on s390x: librust-yaxpeax-arch-0.2+use-serde-dev (>= 0.2.7-~~)
    • rust-yaxpeax-x86 unsatisfiable Build-Depends(-Arch) on s390x: librust-yaxpeax-arch-0.2-dev (>= 0.2.7-~~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-yaxpeax-x86.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 281 days old (needed 5 days)
• xfireworks (- to 1.3-14)
  • Migration status for xfireworks (- to 1.3-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfireworks would introduce bugs in testing: #1075661
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfireworks.html
    • 281 days old (needed 5 days)
• oxygen-icons5 (- to 5:5.115.0-2)
  • Migration status for oxygen-icons5 (- to 5:5.115.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • oxygen-icons5 has no binaries on any arch
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 284 days old (needed 5 days)
• hugs98 (- to 98.200609.21-7)
  • Migration status for hugs98 (- to 98.200609.21-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hugs98 would introduce bugs in testing: #1075073
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hugs98.html
    • 285 days old (needed 5 days)
• llvm-toolchain-14 (- to 1:14.0.6-20)
  • Migration status for llvm-toolchain-14 (- to 1:14.0.6-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liblldb-14t64/amd64 has unsatisfiable dependency
    • liblldb-14t64/arm64 has unsatisfiable dependency
    • liblldb-14t64/armel has unsatisfiable dependency
    • liblldb-14t64/armhf has unsatisfiable dependency
    • liblldb-14t64/i386 has unsatisfiable dependency
    • liblldb-14t64/ppc64el has unsatisfiable dependency
    • liblldb-14t64/s390x has unsatisfiable dependency
    • Updating llvm-toolchain-14 would introduce bugs in testing: #1036596, #1058822, #1068840, #1076412, #1084564
    • autopkgtest for llvm-toolchain-14/1:14.0.6-20: riscv64: Regression or new test ♻
    • missing build on mips64el
    • Not touching package due to block request by sramacher (please contact debian-release if update is needed)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/llvm-toolchain-14.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 285 days old (needed 5 days)
• kst (- to 2.0.8-6)
  • Migration status for kst (- to 2.0.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kst libgetdata (not considered)
    • Depends: kst libgetdata (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kst.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 289 days old (needed 5 days)
• toil (- to 6.1.0-4)
  • Migration status for toil (- to 6.1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating toil would introduce bugs in testing: #1073358
    • autopkgtest for toil/6.1.0-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/toil.html
    • 289 days old (needed 5 days)
• cgroupfs-mount (- to 1.4+nmu1)
  • Migration status for cgroupfs-mount (- to 1.4+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cgroupfs-mount would introduce bugs in testing: #1070295
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cgroupfs-mount.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 290 days old (needed 5 days)
• rust-yoke (- to 0.7.3-1)
  • Migration status for rust-yoke (- to 0.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-yoke-dev/amd64 has unsatisfiable dependency
    • librust-yoke-dev/arm64 has unsatisfiable dependency
    • librust-yoke-dev/armel has unsatisfiable dependency
    • librust-yoke-dev/armhf has unsatisfiable dependency
    • librust-yoke-dev/i386 has unsatisfiable dependency
    • librust-yoke-dev/mips64el has unsatisfiable dependency
    • librust-yoke-dev/ppc64el has unsatisfiable dependency
    • librust-yoke-dev/riscv64 has unsatisfiable dependency
    • librust-yoke-dev/s390x has unsatisfiable dependency
    • Updating rust-yoke would introduce bugs in testing: #1073151
    • Build-Depends(-Arch): rust-yoke rust-zerofrom (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-yoke.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 292 days old (needed 5 days)
• rust-zerofrom (- to 0.1.3-1)
  • Migration status for rust-zerofrom (- to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-zerofrom would introduce bugs in testing: #1073146
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zerofrom.html
    • autopkgtest for rust-zerofrom/0.1.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 292 days old (needed 2 days)
• nim (- to 1.6.14-3)
  • Migration status for nim (- to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • nim/amd64 has unsatisfiable dependency
    • nim/arm64 has unsatisfiable dependency
    • nim/armel has unsatisfiable dependency
    • nim/armhf has unsatisfiable dependency
    • nim/i386 has unsatisfiable dependency
    • nim/mips64el has unsatisfiable dependency
    • nim/ppc64el has unsatisfiable dependency
    • nim/riscv64 has unsatisfiable dependency
    • Updating nim would introduce bugs in testing: #1071691
    • nim unsatisfiable Build-Depends(-Arch) on amd64: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on arm64: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on armel: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on armhf: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on i386: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3
    • nim unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 293 days old (needed 5 days)
• ganglia (- to 3.7.2-7)
  • Migration status for ganglia (- to 3.7.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ganglia would introduce bugs in testing: #1074977
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganglia.html
    • autopkgtest for ganglia/3.7.2-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 294 days old (needed 2 days)
• libtranscript (- to 0.3.3-1.1)
  • Migration status for libtranscript (- to 0.3.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libtranscript would introduce bugs in testing: #1075215
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtranscript.html
    • 294 days old (needed 5 days)
• mailman-suite (- to 0+20240312-1)
  • Migration status for mailman-suite (- to 0+20240312-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mailman-suite hyperkitty (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailman-suite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 294 days old (needed 5 days)
• python-measurement (- to 3.2.2-2)
  • Migration status for python-measurement (- to 3.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-measurement would introduce bugs in testing: #1078362
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-measurement.html
    • autopkgtest for python-measurement/3.2.2-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 294 days old (needed 5 days)
• sniffit (- to 0.6-1)
  • Migration status for sniffit (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sniffit would introduce bugs in testing: #1075521
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sniffit.html
    • autopkgtest for sniffit/0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 295 days old (needed 2 days)
• libt3window (- to 0.4.0-1.1)
  • Migration status for libt3window (- to 0.4.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libt3window libtranscript (not considered)
    • Depends: libt3window libtranscript (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libt3window.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 296 days old (needed 5 days)
• loqui (- to 0.7.0-2.1)
  • Migration status for loqui (- to 0.7.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating loqui would introduce bugs in testing: #1075233
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/loqui.html
    • 296 days old (needed 5 days)
• nml (- to 0.7.5-1)
  • Migration status for nml (- to 0.7.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nml would introduce bugs in testing: #1092509
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nml.html
    • Reproducible on i386 - info ♻
    • 296 days old (needed 5 days)
• francine (- to 0.99.8+orig-2.2)
  • Migration status for francine (- to 0.99.8+orig-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating francine would introduce bugs in testing: #1074964
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/francine.html
    • Reproducible on arm64 - info ♻
    • 297 days old (needed 5 days)
• ukui-control-center (- to 3.22.1.28-1)
  • Migration status for ukui-control-center (- to 3.22.1.28-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ukui-control-center/amd64 has unsatisfiable dependency
    • ukui-control-center/arm64 has unsatisfiable dependency
    • ukui-control-center/armel has unsatisfiable dependency
    • ukui-control-center/armhf has unsatisfiable dependency
    • ukui-control-center/i386 has unsatisfiable dependency
    • ukui-control-center/mips64el has unsatisfiable dependency
    • ukui-control-center/ppc64el has unsatisfiable dependency
    • ukui-control-center/riscv64 has unsatisfiable dependency
    • ukui-control-center/s390x has unsatisfiable dependency
    • Updating ukui-control-center would introduce bugs in testing: #1079811
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on amd64: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on amd64: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on arm64: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on arm64: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on armel: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on armel: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on armhf: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on armhf: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on i386: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on i386: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on mips64el: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on mips64el: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on riscv64: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on riscv64: libkf5screen-dev
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on s390x: libkf5screen-bin
    • ukui-control-center unsatisfiable Build-Depends(-Arch) on s390x: libkf5screen-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-control-center.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 297 days old (needed 5 days)
• network-manager-fortisslvpn (- to 1.4.0-1.1)
  • Migration status for network-manager-fortisslvpn (- to 1.4.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating network-manager-fortisslvpn would introduce bugs in testing: #1069693
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/network-manager-fortisslvpn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 298 days old (needed 5 days)
• tss2 (- to 1045-3)
  • Migration status for tss2 (- to 1045-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tss2 would introduce bugs in testing: #971758
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tss2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 298 days old (needed 5 days)
• cegui-mk2 (- to 0.8.7+git20220615-6)
  • Migration status for cegui-mk2 (- to 0.8.7+git20220615-6): 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/ppc64el has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/riscv64 has unsatisfiable dependency
    • python3-libcegui-mk2-0.8.7/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - 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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 299 days old (needed 5 days)
• pplatex (- to 1.0~beta2023.12.01.repack-1)
  • Migration status for pplatex (- to 1.0~beta2023.12.01.repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pplatex/amd64 has unsatisfiable dependency
    • pplatex/arm64 has unsatisfiable dependency
    • pplatex/armel has unsatisfiable dependency
    • pplatex/armhf has unsatisfiable dependency
    • pplatex/i386 has unsatisfiable dependency
    • pplatex/mips64el has unsatisfiable dependency
    • pplatex/ppc64el has unsatisfiable dependency
    • pplatex/riscv64 has unsatisfiable dependency
    • pplatex/s390x has unsatisfiable dependency
    • Updating pplatex would introduce bugs in testing: #1070288
    • pplatex unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • pplatex unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pplatex.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 299 days old (needed 5 days)
• syncevolution (- to 2.0.0-3.1)
  • Migration status for syncevolution (- to 2.0.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): syncevolution libsynthesis (not considered)
    • Depends: syncevolution libsynthesis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syncevolution.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 299 days old (needed 5 days)
• pyzbar (- to 0.1.9-2)
  • Migration status for pyzbar (- to 0.1.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyzbar would introduce bugs in testing: #1080136
    • autopkgtest for pyzbar/0.1.9-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyzbar.html
    • 300 days old (needed 5 days)
• lektor (- to 3.3.7-2.1)
  • Migration status for lektor (- to 3.3.7-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lektor would introduce bugs in testing: #1084286
    • autopkgtest for lektor/3.3.7-2.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lektor.html
    • 301 days old (needed 5 days)
• gnome-paint (- to 0.4.0-10)
  • Migration status for gnome-paint (- to 0.4.0-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-paint would introduce bugs in testing: #1075026
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-paint.html
    • 302 days old (needed 5 days)
• librem5-flash-image (- to 0.0.4-2)
  • Migration status for librem5-flash-image (- to 0.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating librem5-flash-image would introduce bugs in testing: #1085089
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 302 days old (needed 5 days)
• sambamba (- to 1.0.1+dfsg-2)
  • Migration status for sambamba (- to 1.0.1+dfsg-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: sambamba ldc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sambamba.html
    • autopkgtest for sambamba/1.0.1+dfsg-2: amd64: Pass, arm64: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 302 days old (needed 2 days)
• tcpxtract (- to 1.0.1-18)
  • Migration status for tcpxtract (- to 1.0.1-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tcpxtract would introduce bugs in testing: #1075557
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tcpxtract.html
    • autopkgtest for tcpxtract/1.0.1-18: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 302 days old (needed 2 days)
• hfsutils (- to 3.2.6-16)
  • Migration status for hfsutils (- to 3.2.6-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hfsutils would introduce bugs in testing: #1075067
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hfsutils.html
    • 305 days old (needed 5 days)
• kcemu (- to 0.5.2+dfsg-2)
  • Migration status for kcemu (- to 0.5.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kcemu would introduce bugs in testing: #1078231
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 306 days old (needed 5 days)
• r-cran-rstanarm (- to 2.32.1-2)
  • Migration status for r-cran-rstanarm (- to 2.32.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-rstanarm would introduce bugs in testing: #1091239
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rstanarm.html
    • autopkgtest for r-cran-rstanarm/2.32.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 308 days old (needed 2 days)
• eclib (- to 20240408-1)
  • Migration status for eclib (- to 20240408-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libec10t64/amd64 has unsatisfiable dependency
    • libec10t64/arm64 has unsatisfiable dependency
    • libec10t64/i386 has unsatisfiable dependency
    • libec10t64/mips64el has unsatisfiable dependency
    • libec10t64/ppc64el has unsatisfiable dependency
    • libec10t64/riscv64 has unsatisfiable dependency
    • libec10t64/s390x has unsatisfiable dependency
    • Updating eclib would introduce bugs in testing: #1069515
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclib.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 309 days old (needed 5 days)
• foxeye (- to 0.12.1-5)
  • Migration status for foxeye (- to 0.12.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating foxeye would introduce bugs in testing: #1086099
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foxeye.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 309 days old (needed 5 days)
• peony (- to 4.0.0.1-1)
  • Migration status for peony (- to 4.0.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • peony/amd64 has unsatisfiable dependency
    • peony/arm64 has unsatisfiable dependency
    • peony/armel has unsatisfiable dependency
    • peony/armhf has unsatisfiable dependency
    • peony/i386 has unsatisfiable dependency
    • peony/mips64el has unsatisfiable dependency
    • peony/ppc64el has unsatisfiable dependency
    • peony/riscv64 has unsatisfiable dependency
    • peony/s390x has unsatisfiable dependency
    • Updating peony would introduce bugs in testing: #1079810
    • peony unsatisfiable Build-Depends(-Arch) on amd64: libkf5screen-dev
    • peony unsatisfiable Build-Depends(-Arch) on arm64: libkf5screen-dev
    • peony unsatisfiable Build-Depends(-Arch) on armel: libkf5screen-dev
    • peony unsatisfiable Build-Depends(-Arch) on armhf: libkf5screen-dev
    • peony unsatisfiable Build-Depends(-Arch) on i386: libkf5screen-dev
    • peony unsatisfiable Build-Depends(-Arch) on mips64el: libkf5screen-dev
    • peony unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5screen-dev
    • peony unsatisfiable Build-Depends(-Arch) on riscv64: libkf5screen-dev
    • peony unsatisfiable Build-Depends(-Arch) on s390x: libkf5screen-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/peony.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 309 days old (needed 5 days)
• form (- to 4.3.1+git20240409+ds-2)
  • Migration status for form (- to 4.3.1+git20240409+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating form would introduce bugs in testing: #1091275
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/form.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 310 days old (needed 5 days)
• cython-legacy (- to 0.29.37-2)
  • Migration status for cython-legacy (- to 0.29.37-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cython3-legacy/amd64 has unsatisfiable dependency
    • cython3-legacy/arm64 has unsatisfiable dependency
    • cython3-legacy/armel has unsatisfiable dependency
    • cython3-legacy/armhf has unsatisfiable dependency
    • cython3-legacy/i386 has unsatisfiable dependency
    • cython3-legacy/mips64el has unsatisfiable dependency
    • cython3-legacy/ppc64el has unsatisfiable dependency
    • cython3-legacy/riscv64 has unsatisfiable dependency
    • cython3-legacy/s390x has unsatisfiable dependency
    • Updating cython-legacy would introduce bugs in testing: #1078460
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cython-legacy.html
    • Not touching package due to block request by ginggs (please contact debian-release if update is needed)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 311 days old (needed 5 days)
• ttyd (- to 1.7.7-2)
  • Migration status for ttyd (- to 1.7.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ttyd would introduce bugs in testing: #996042
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/ttyd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 311 days old (needed 5 days)
• bitlbee (- to 3.6-1.4)
  • Migration status for bitlbee (- to 3.6-1.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bitlbee would introduce bugs in testing: #1070904
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bitlbee.html
    • 316 days old (needed 5 days)
• bitlbee-facebook (- to 1.2.2-3)
  • Migration status for bitlbee-facebook (- to 1.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): bitlbee-facebook bitlbee (not considered)
    • Depends: bitlbee-facebook bitlbee (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bitlbee-facebook.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 316 days old (needed 5 days)
• nstreams (- to 1.0.4-1.1)
  • Migration status for nstreams (- to 1.0.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nstreams would introduce bugs in testing: #1075323
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nstreams.html
    • 316 days old (needed 5 days)
• psgml (- to 1.4.0-12.1)
  • Migration status for psgml (- to 1.4.0-12.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating psgml would introduce bugs in testing: #1092426
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psgml.html
    • Reproducible on armhf - info ♻
    • 316 days old (needed 5 days)
• python-xsdata (- to 24.1-1)
  • Migration status for python-xsdata (- to 24.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-xsdata/24.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): python-xsdata ruff (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xsdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 316 days old (needed 5 days)
• python-anndata (- to 0.10.6-1)
  • Migration status for python-anndata (- to 0.10.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-anndata/0.10.6-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): python-anndata python-array-api-compat (not considered)
    • Depends: python-anndata python-array-api-compat (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-anndata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 321 days old (needed 5 days)
• aplus-fsf (- to 4.22.1-13)
  • Migration status for aplus-fsf (- to 4.22.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aplus-fsf would introduce bugs in testing: #1067921, #1088380
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aplus-fsf.html
    • 322 days old (needed 5 days)
• python-ppmd (- to 0.5.0-1)
  • Migration status for python-ppmd (- to 0.5.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for python-ppmd/0.5.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ppmd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 322 days old (needed 5 days)
• xtb (- to 6.7.0-1)
  • Migration status for xtb (- to 6.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xtb would introduce bugs in testing: #1091310
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xtb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 324 days old (needed 5 days)
• oclgrind (- to 21.10-4)
  • Migration status for oclgrind (- to 21.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oclgrind would introduce bugs in testing: #1061215
    • Build-Depends(-Arch): oclgrind llvm-toolchain-14 (not considered)
    • Depends: oclgrind llvm-toolchain-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oclgrind.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 327 days old (needed 5 days)
• dh-make-golang (- to 0.7.0-1)
  • Migration status for dh-make-golang (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dh-make-golang would introduce bugs in testing: #1091273
    • autopkgtest for dh-make-golang/0.7.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-make-golang.html
    • 328 days old (needed 5 days)
• python-uflash (- to 1.2.4+dfsg-11)
  • Migration status for python-uflash (- to 1.2.4+dfsg-11): 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-11: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 328 days old (needed 2 days)
• ruby-premailer-rails (- to 1.12.0-1)
  • Migration status for ruby-premailer-rails (- to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-premailer-rails would introduce bugs in testing: #1093925
    • Build-Depends(-Arch): ruby-premailer-rails ruby-premailer (not considered)
    • Depends: ruby-premailer-rails ruby-premailer (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-premailer-rails.html
    • autopkgtest for ruby-premailer-rails/1.12.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 328 days old (needed 2 days)
• glib-d (- to 2.4.3-2)
  • Migration status for glib-d (- to 2.4.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: glib-d ldc (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): glib-d gir-to-d
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glib-d.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 330 days old (needed 5 days)
• gtk-d (- to 3.10.0-3)
  • Migration status for gtk-d (- to 3.10.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gtk-d ldc (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): gtk-d gir-to-d
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk-d.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 330 days old (needed 5 days)
• tilix (- to 1.9.6-2)
  • Migration status for tilix (- to 1.9.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tilix would introduce bugs in testing: #1068051
    • Build-Depends(-Arch): tilix gtk-d
    • Depends: tilix gtk-d
    • Depends: tilix ldc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tilix.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 330 days old (needed 5 days)
• nanovg (- to 0.0~git20230826.f93799c+dfsg-2)
  • Migration status for nanovg (- to 0.0~git20230826.f93799c+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nanovg ruby-entypo-rails (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nanovg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 331 days old (needed 5 days)
• python-ptrace (- to 0.9.9-0.1)
  • Migration status for python-ptrace (- to 0.9.9-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ptrace would introduce bugs in testing: #1087588
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ptrace.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 332 days old (needed 5 days)
• pachi (- to 1:1.0-11)
  • Migration status for pachi (- to 1:1.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pachi would introduce bugs in testing: #1075354
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pachi.html
    • 333 days old (needed 5 days)
• calculix-ccx (- to 2.21-1)
  • Migration status for calculix-ccx (- to 2.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for calculix-ccx/2.21-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): calculix-ccx spooles (not considered)
    • Depends: calculix-ccx spooles (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calculix-ccx.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 334 days old (needed 5 days)
• sane-frontends (- to 1.0.14-18)
  • Migration status for sane-frontends (- to 1.0.14-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sane/amd64 has unsatisfiable dependency
    • sane/arm64 has unsatisfiable dependency
    • sane/armel has unsatisfiable dependency
    • sane/armhf has unsatisfiable dependency
    • sane/i386 has unsatisfiable dependency
    • sane/mips64el has unsatisfiable dependency
    • sane/ppc64el has unsatisfiable dependency
    • sane/riscv64 has unsatisfiable dependency
    • sane/s390x has unsatisfiable dependency
    • Updating sane-frontends would introduce bugs in testing: #1088081
    • sane-frontends unsatisfiable Build-Depends(-Arch) on amd64: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on arm64: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on armel: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on armhf: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on i386: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on mips64el: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on ppc64el: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on riscv64: libgimp2.0-dev
    • sane-frontends unsatisfiable Build-Depends(-Arch) on s390x: libgimp2.0-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sane-frontends.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 335 days old (needed 5 days)
• oss4 (- to 4.2-build2020-3)
  • Migration status for oss4 (- to 4.2-build2020-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oss4 would introduce bugs in testing: #1064301, #796636
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oss4.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 336 days old (needed 5 days)
• freewnn (- to 1.1.1~a021+cvs20130302-8)
  • Migration status for freewnn (- to 1.1.1~a021+cvs20130302-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freewnn would introduce bugs in testing: #1074968
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freewnn.html
    • 340 days old (needed 5 days)
• clippoly (- to 0.11-11)
  • Migration status for clippoly (- to 0.11-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clippoly would introduce bugs in testing: #976540
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clippoly.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 341 days old (needed 5 days)
• libapache2-mod-python (- to 3.5.0.1-3)
  • Migration status for libapache2-mod-python (- to 3.5.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libapache2-mod-python/amd64 has unsatisfiable dependency
    • libapache2-mod-python/arm64 has unsatisfiable dependency
    • libapache2-mod-python/armel has unsatisfiable dependency
    • libapache2-mod-python/armhf has unsatisfiable dependency
    • libapache2-mod-python/i386 has unsatisfiable dependency
    • libapache2-mod-python/mips64el has unsatisfiable dependency
    • libapache2-mod-python/ppc64el has unsatisfiable dependency
    • libapache2-mod-python/riscv64 has unsatisfiable dependency
    • libapache2-mod-python/s390x has unsatisfiable dependency
    • Updating libapache2-mod-python would introduce bugs in testing: #1091289, #1092440
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/liba/libapache2-mod-python.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 342 days old (needed 5 days)
• ohai (- to 18.1.3-2.1)
  • Migration status for ohai (- to 18.1.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Build-Depends(-Arch): ohai ruby-chef-config (not considered)
    • Depends: ohai ruby-chef-config (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ohai.html
    • autopkgtest for ohai/18.1.3-2.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 342 days old (needed 5 days)
    • Remove hint for (transitive) dependency: ohai, ruby-chef-config
• pyacoustid (- to 1.3.0-1)
  • Migration status for pyacoustid (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyacoustid would introduce bugs in testing: #1093700
    • autopkgtest for pyacoustid/1.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyacoustid.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 342 days old (needed 5 days)
• pdepend (- to 2.16.2-2)
  • Migration status for pdepend (- to 2.16.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pdepend would introduce bugs in testing: #1039755
    • autopkgtest for pdepend/2.16.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdepend.html
    • Reproducible on armhf - info ♻
    • 343 days old (needed 5 days)
• phpcpd (- to 6.0.3-3)
  • Migration status for phpcpd (- to 6.0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • phpcpd/amd64 has unsatisfiable dependency
    • phpcpd/arm64 has unsatisfiable dependency
    • Updating phpcpd would introduce bugs in testing: #1070618
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpcpd.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 343 days old (needed 5 days)
• phpmd (- to 2.15.0-2)
  • Migration status for phpmd (- to 2.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phpmd would introduce bugs in testing: #1039795
    • autopkgtest for phpmd/2.15.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): phpmd pdepend (not considered)
    • Depends: phpmd pdepend (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpmd.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 343 days old (needed 5 days)
• tvnamer (- to 3.0.4-2)
  • Migration status for tvnamer (- to 3.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tvnamer would introduce bugs in testing: #1084947
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tvnamer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 348 days old (needed 5 days)
• jss (- to 5.5.0-1)
  • Migration status for jss (- to 5.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jss would introduce bugs in testing: #1091274
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 349 days old (needed 5 days)
• ldapjdk (- to 5.5.0+dfsg1-1)
  • Migration status for ldapjdk (- to 5.5.0+dfsg1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: ldapjdk jss (not considered)
    • Depends: ldapjdk jss (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ldapjdk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 349 days old (needed 5 days)
• openvr (- to 1.23.7~ds1-2.1)
  • Migration status for openvr (- to 1.23.7~ds1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openvr would introduce bugs in testing: #1067724
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 349 days old (needed 5 days)
• palabos (- to 1.5~r1+repack1-5.1)
  • Migration status for palabos (- to 1.5~r1+repack1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for palabos/1.5~r1+repack1-5.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/palabos.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 349 days old (needed 5 days)
• s2geometry (- to 0.10.0-6.1)
  • Migration status for s2geometry (- to 0.10.0-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libs2-0t64/amd64 has unsatisfiable dependency
    • python3-pywraps2/amd64 has unsatisfiable dependency
    • libs2-0t64/arm64 has unsatisfiable dependency
    • python3-pywraps2/arm64 has unsatisfiable dependency
    • libs2-0t64/armel has unsatisfiable dependency
    • python3-pywraps2/armel has unsatisfiable dependency
    • libs2-0t64/armhf has unsatisfiable dependency
    • python3-pywraps2/armhf has unsatisfiable dependency
    • libs2-0t64/i386 has unsatisfiable dependency
    • python3-pywraps2/i386 has unsatisfiable dependency
    • libs2-0t64/mips64el has unsatisfiable dependency
    • python3-pywraps2/mips64el has unsatisfiable dependency
    • libs2-0t64/ppc64el has unsatisfiable dependency
    • python3-pywraps2/ppc64el has unsatisfiable dependency
    • libs2-0t64/riscv64 has unsatisfiable dependency
    • python3-pywraps2/riscv64 has unsatisfiable dependency
    • libs2-0t64/s390x has unsatisfiable dependency
    • python3-pywraps2/s390x has unsatisfiable dependency
    • Updating s2geometry would introduce bugs in testing: #1059228
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/s2geometry.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 349 days old (needed 5 days)
• shapetools (- to 1.4pl6-16.1)
  • Migration status for shapetools (- to 1.4pl6-16.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shapetools would introduce bugs in testing: #1075506
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shapetools.html
    • 349 days old (needed 5 days)
• sphde (- to 1.4.0-5.1)
  • Migration status for sphde (- to 1.4.0-5.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/s/sphde.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 349 days old (needed 5 days)
• spooles (- to 2.2-14.1)
  • Migration status for spooles (- to 2.2-14.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libspooles2.2t64/amd64 has unsatisfiable dependency
    • libspooles2.2t64/arm64 has unsatisfiable dependency
    • libspooles2.2t64/mips64el has unsatisfiable dependency
    • libspooles2.2t64/ppc64el has unsatisfiable dependency
    • libspooles2.2t64/riscv64 has unsatisfiable dependency
    • libspooles2.2t64/s390x has unsatisfiable dependency
    • Updating spooles would introduce bugs in testing: #1075534
    • autopkgtest for spooles/2.2-14.1: armel: Pass, armhf: Pass, i386: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spooles.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 riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 349 days old (needed 5 days)
• termrec (- to 0.19-2.1)
  • Migration status for termrec (- to 0.19-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating termrec would introduce bugs in testing: #1065906
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/termrec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 349 days old (needed 5 days)
• android-platform-frameworks-native (- to 1:10.0.0+r36-1.2)
  • Migration status for android-platform-frameworks-native (- to 1:10.0.0+r36-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-frameworks-native would introduce bugs in testing: #1062267
    • autopkgtest for android-platform-frameworks-native/1:10.0.0+r36-1.2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-frameworks-native.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 350 days old (needed 5 days)
• bernhard (- to 0.2.6-4)
  • Migration status for bernhard (- to 0.2.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for bernhard/0.2.6-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bernhard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 350 days old (needed 5 days)
• chemps2 (- to 1.8.12-3.1)
  • Migration status for chemps2 (- to 1.8.12-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-chemps2/amd64 has unsatisfiable dependency
    • python3-chemps2/arm64 has unsatisfiable dependency
    • python3-chemps2/armel has unsatisfiable dependency
    • python3-chemps2/armhf has unsatisfiable dependency
    • python3-chemps2/i386 has unsatisfiable dependency
    • python3-chemps2/mips64el has unsatisfiable dependency
    • python3-chemps2/ppc64el has unsatisfiable dependency
    • python3-chemps2/riscv64 has unsatisfiable dependency
    • python3-chemps2/s390x has unsatisfiable dependency
    • Updating chemps2 would introduce bugs in testing: #1092786
    • Build-Depends(-Arch): chemps2 cython-legacy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chemps2.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 350 days old (needed 5 days)
• grok (- to 1.20110708.1-7.1)
  • Migration status for grok (- to 1.20110708.1-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • grok/amd64 has unsatisfiable dependency
    • libgrok1t64/amd64 has unsatisfiable dependency
    • grok/arm64 has unsatisfiable dependency
    • libgrok1t64/arm64 has unsatisfiable dependency
    • grok/i386 has unsatisfiable dependency
    • libgrok1t64/i386 has unsatisfiable dependency
    • grok/mips64el has unsatisfiable dependency
    • libgrok1t64/mips64el has unsatisfiable dependency
    • grok/ppc64el has unsatisfiable dependency
    • libgrok1t64/ppc64el has unsatisfiable dependency
    • grok/riscv64 has unsatisfiable dependency
    • libgrok1t64/riscv64 has unsatisfiable dependency
    • grok/s390x has unsatisfiable dependency
    • libgrok1t64/s390x has unsatisfiable dependency
    • Updating grok would introduce bugs in testing: #1000065, #1065556
    • grok unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grok.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • 350 days old (needed 5 days)
• libapr-memcache (- to 0.7.0-3.1)
  • Migration status for libapr-memcache (- to 0.7.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapr-memcache would introduce bugs in testing: #1075144
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapr-memcache.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 350 days old (needed 5 days)
• libkqueue (- to 2.3.1-1.1)
  • Migration status for libkqueue (- to 2.3.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libkqueue would introduce bugs in testing: #955260
    • autopkgtest for libkqueue/2.3.1-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkqueue.html
    • Reproducible on arm64 - info ♻
    • 350 days old (needed 5 days)
• libonvif (- to 1.4.4-1.1)
  • Migration status for libonvif (- to 1.4.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libonvif1t64/amd64 has unsatisfiable dependency
    • libonvif1t64/arm64 has unsatisfiable dependency
    • libonvif1t64/armel has unsatisfiable dependency
    • libonvif1t64/armhf has unsatisfiable dependency
    • libonvif1t64/i386 has unsatisfiable dependency
    • libonvif1t64/mips64el has unsatisfiable dependency
    • libonvif1t64/ppc64el has unsatisfiable dependency
    • libonvif1t64/riscv64 has unsatisfiable dependency
    • libonvif1t64/s390x has unsatisfiable dependency
    • Updating libonvif would introduce bugs in testing: #1072430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libonvif.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 350 days old (needed 5 days)
• libpreludedb (- to 5.2.0-2.2)
  • Migration status for libpreludedb (- to 5.2.0-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/libp/libpreludedb.html
    • Build-Depends(-Arch): libpreludedb libprelude (not considered)
    • Depends: libpreludedb libprelude (not considered)
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 350 days old (needed 5 days)
• libpwiz (- to 3.0.18342-4.1)
  • Migration status for libpwiz (- to 3.0.18342-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpwiz would introduce bugs in testing: #1075199
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpwiz.html
    • 350 days old (needed 5 days)
• libsnl (- to 0.2.1.svn.18-1.2)
  • Migration status for libsnl (- to 0.2.1.svn.18-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libsnl would introduce bugs in testing: #1074861
    • autopkgtest for libsnl/0.2.1.svn.18-1.2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsnl.html
    • 350 days old (needed 5 days)
• libsynthesis (- to 3.4.0.47.5+syncevolution-1.5.3-1.2)
  • Migration status for libsynthesis (- to 3.4.0.47.5+syncevolution-1.5.3-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsynthesis0t64/amd64 has unsatisfiable dependency
    • libsynthesis0t64/arm64 has unsatisfiable dependency
    • libsynthesis0t64/armel has unsatisfiable dependency
    • libsynthesis0t64/armhf has unsatisfiable dependency
    • libsynthesis0t64/i386 has unsatisfiable dependency
    • libsynthesis0t64/mips64el has unsatisfiable dependency
    • libsynthesis0t64/ppc64el has unsatisfiable dependency
    • libsynthesis0t64/riscv64 has unsatisfiable dependency
    • libsynthesis0t64/s390x has unsatisfiable dependency
    • Updating libsynthesis would introduce bugs in testing: #1000047
    • libsynthesis unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • libsynthesis unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsynthesis.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 350 days old (needed 5 days)
• libt3widget (- to 1.2.0-1.1)
  • Migration status for libt3widget (- to 1.2.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): libt3widget libtranscript (not considered)
    • Depends: libt3widget libtranscript (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): libt3widget libt3window
    • Depends: libt3widget libt3window
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libt3widget.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 350 days old (needed 5 days)
• llvmlite (- to 0.42.0-1)
  • Migration status for llvmlite (- to 0.42.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating llvmlite would introduce bugs in testing: #1061214
    • Build-Depends(-Arch): llvmlite llvm-toolchain-14 (not considered)
    • Depends: llvmlite llvm-toolchain-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvmlite.html
    • autopkgtest for llvmlite/0.42.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 350 days old (needed 2 days)
• mongo-cxx-driver-legacy (- to 1.1.3-3.3)
  • Migration status for mongo-cxx-driver-legacy (- to 1.1.3-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mongo-cxx-driver-legacy would introduce bugs in testing: #1065905
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on amd64: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on arm64: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on armel: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on armhf: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on i386: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on mips64el: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on ppc64el: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on riscv64: python3-distutils
    • mongo-cxx-driver-legacy unsatisfiable Build-Depends(-Arch) on s390x: python3-distutils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mongo-cxx-driver-legacy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 350 days old (needed 5 days)
• mrtdreader (- to 0.1.6-3.1)
  • Migration status for mrtdreader (- to 0.1.6-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mrtdreader would introduce bugs in testing: #1066260
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for mrtdreader/0.1.6-3.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrtdreader.html
    • 350 days old (needed 5 days)
• ogre-1.9 (- to 1.9.0+dfsg1-14.1)
  • Migration status for ogre-1.9 (- to 1.9.0+dfsg1-14.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ogre-1.9 would introduce bugs in testing: #1024182
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ogre-1.9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 350 days old (needed 5 days)
• opendht (- to 3.0.1-1.1)
  • Migration status for opendht (- to 3.0.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opendht would introduce bugs in testing: #1087610
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opendht.html
    • autopkgtest for opendht/3.0.1-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 350 days old (needed 2 days)
• xbase64 (- to 3.1.2-14.1)
  • Migration status for xbase64 (- to 3.1.2-14.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libxbase64-bin/armel has unsatisfiable dependency
    • libxbase64-bin/armhf has unsatisfiable dependency
    • Updating xbase64 would introduce bugs in testing: #1069340
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xbase64.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 350 days old (needed 5 days)
• ygl (- to 4.2e-6.1)
  • Migration status for ygl (- to 4.2e-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ygl would introduce bugs in testing: #1075698
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ygl.html
    • autopkgtest for ygl/4.2e-6.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 350 days old (needed 2 days)
• armnn (- to 23.08-4.1)
  • Migration status for armnn (- to 23.08-4.1): 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/armhf has unsatisfiable dependency
    • python3-pyarmnn/i386 has unsatisfiable dependency
    • python3-pyarmnn/mips64el has unsatisfiable dependency
    • python3-pyarmnn/ppc64el has unsatisfiable dependency
    • Updating armnn would introduce bugs in testing: #1074820
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/a/armnn.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
    • 351 days old (needed 5 days)
• brial (- to 1.2.12-1.1)
  • Migration status for brial (- to 1.2.12-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-brial/riscv64 has unsatisfiable dependency
    • Updating brial would introduce bugs in testing: #1093321
    • autopkgtest for brial/1.2.12-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Test in progress, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/brial.html
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 351 days old (needed 5 days)
• cvm (- to 0.97-3.1)
  • Migration status for cvm (- to 0.97-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cvm would introduce bugs in testing: #1074896
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cvm.html
    • 351 days old (needed 5 days)
• daq (- to 2.0.7-5.1)
  • Migration status for daq (- to 2.0.7-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating daq would introduce bugs in testing: #1074902
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/daq.html
    • 351 days old (needed 5 days)
• dyssol (- to 1.1.1+ds1-2.1)
  • Migration status for dyssol (- to 1.1.1+ds1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dyssol/amd64 has unsatisfiable dependency
    • dyssol-gui/amd64 has unsatisfiable dependency
    • libdyssol1.0t64/amd64 has unsatisfiable dependency
    • dyssol/arm64 has unsatisfiable dependency
    • dyssol-gui/arm64 has unsatisfiable dependency
    • libdyssol1.0t64/arm64 has unsatisfiable dependency
    • dyssol/armel has unsatisfiable dependency
    • dyssol-gui/armel has unsatisfiable dependency
    • libdyssol1.0t64/armel has unsatisfiable dependency
    • dyssol/armhf has unsatisfiable dependency
    • dyssol-gui/armhf has unsatisfiable dependency
    • libdyssol1.0t64/armhf has unsatisfiable dependency
    • dyssol/i386 has unsatisfiable dependency
    • dyssol-gui/i386 has unsatisfiable dependency
    • libdyssol1.0t64/i386 has unsatisfiable dependency
    • dyssol/mips64el has unsatisfiable dependency
    • dyssol-gui/mips64el has unsatisfiable dependency
    • libdyssol1.0t64/mips64el has unsatisfiable dependency
    • dyssol/ppc64el has unsatisfiable dependency
    • dyssol-gui/ppc64el has unsatisfiable dependency
    • libdyssol1.0t64/ppc64el has unsatisfiable dependency
    • dyssol/riscv64 has unsatisfiable dependency
    • dyssol-gui/riscv64 has unsatisfiable dependency
    • libdyssol1.0t64/riscv64 has unsatisfiable dependency
    • dyssol/s390x has unsatisfiable dependency
    • dyssol-gui/s390x has unsatisfiable dependency
    • libdyssol1.0t64/s390x has unsatisfiable dependency
    • Updating dyssol would introduce bugs in testing: #1082562
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dyssol.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 351 days old (needed 5 days)
• forge (- to 1.0.1-3.1)
  • Migration status for forge (- to 1.0.1-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libforge1t64/amd64 has unsatisfiable dependency
    • libforge1t64/arm64 has unsatisfiable dependency
    • libforge1t64/armel has unsatisfiable dependency
    • libforge1t64/armhf has unsatisfiable dependency
    • libforge1t64/i386 has unsatisfiable dependency
    • libforge1t64/mips64el has unsatisfiable dependency
    • libforge1t64/ppc64el has unsatisfiable dependency
    • libforge1t64/riscv64 has unsatisfiable dependency
    • libforge1t64/s390x has unsatisfiable dependency
    • Updating forge would introduce bugs in testing: #1090222
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forge.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 351 days old (needed 5 days)
• gulkan (- to 0.15.1-2.2)
  • Migration status for gulkan (- to 0.15.1-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gulkan would introduce bugs in testing: #1086208
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gulkan.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 351 days old (needed 5 days)
• gxr (- to 0.15.1-4.1)
  • Migration status for gxr (- to 0.15.1-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gxr would introduce bugs in testing: #1075057
    • Build-Depends(-Arch): gxr gulkan (not considered)
    • Depends: gxr gulkan (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gxr.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 351 days old (needed 5 days)
• hepmc3 (- to 3.1.2-2.1)
  • Migration status for hepmc3 (- to 3.1.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hepmc3 would introduce bugs in testing: #1064556
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hepmc3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 351 days old (needed 5 days)
• libghemical (- to 3.0.0-4.4)
  • Migration status for libghemical (- to 3.0.0-4.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghemical5t64/amd64 has unsatisfiable dependency
    • libghemical5t64/arm64 has unsatisfiable dependency
    • libghemical5t64/i386 has unsatisfiable dependency
    • libghemical5t64/mips64el has unsatisfiable dependency
    • libghemical5t64/ppc64el has unsatisfiable dependency
    • libghemical5t64/riscv64 has unsatisfiable dependency
    • libghemical5t64/s390x has unsatisfiable dependency
    • Updating libghemical would introduce bugs in testing: #1086282
    • Build-Depends(-Arch): libghemical mpqc (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libghemical.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 351 days old (needed 5 days)
• tlog (- to 14-1)
  • Migration status for tlog (- to 14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tlog would introduce bugs in testing: #1067828
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tlog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 351 days old (needed 5 days)
• taurus (- to 5.1.8-1)
  • Migration status for taurus (- to 5.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating taurus would introduce bugs in testing: #1091075
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/taurus.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 352 days old (needed 5 days)
• taurus-pyqtgraph (- to 0.8.0-1)
  • Migration status for taurus-pyqtgraph (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating taurus-pyqtgraph would introduce bugs in testing: #1091042
    • Build-Depends(-Arch): taurus-pyqtgraph taurus (not considered)
    • Depends: taurus-pyqtgraph taurus (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/taurus-pyqtgraph.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 352 days old (needed 5 days)
• ukui-session-manager (- to 4.0.0.1-1)
  • Migration status for ukui-session-manager (- to 4.0.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ukui-session-manager would introduce bugs in testing: #1089800
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on amd64: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on arm64: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on armel: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on armhf: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on i386: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on mips64el: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on riscv64: libkf5screen-dev
    • ukui-session-manager unsatisfiable Build-Depends(-Arch) on s390x: libkf5screen-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ukui-session-manager.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 352 days old (needed 5 days)
• adjtimex (- to 1.29-11.1)
  • Migration status for adjtimex (- to 1.29-11.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating adjtimex would introduce bugs in testing: #1091256
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adjtimex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 353 days old (needed 5 days)
• ruby-riddle (- to 2.4.3-1)
  • Migration status for ruby-riddle (- to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-riddle would introduce bugs in testing: #1033369
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-riddle.html
    • autopkgtest for ruby-riddle/2.4.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for ruby-riddle/blocked-on-ci-infra: armel: Ignored failure, armhf: Ignored failure, i386: Ignored failure
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 356 days old (needed 2 days)
• ruby-grape (- to 2.0.0-3)
  • Migration status for ruby-grape (- to 2.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-grape would introduce bugs in testing: #1091659
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-grape.html
    • autopkgtest for ruby-grape/2.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 357 days old (needed 2 days)
• mir-core (- to 1.7.0-1)
  • Migration status for mir-core (- to 1.7.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: mir-core ldc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mir-core.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 358 days old (needed 5 days)
• siconos (- to 4.4.0+dfsg-4)
  • Migration status for siconos (- to 4.4.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsiconos-numerics7/amd64 has unsatisfiable dependency
    • python3-siconos/amd64 has unsatisfiable dependency
    • libsiconos-numerics7/arm64 has unsatisfiable dependency
    • python3-siconos/arm64 has unsatisfiable dependency
    • libsiconos-numerics7/ppc64el has unsatisfiable dependency
    • python3-siconos/ppc64el has unsatisfiable dependency
    • libsiconos-numerics7/riscv64 has unsatisfiable dependency
    • python3-siconos/riscv64 has unsatisfiable dependency
    • Updating siconos would introduce bugs in testing: #1066316
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/siconos.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 358 days old (needed 5 days)
• gir-to-d (- to 0.23.2-1)
  • Migration status for gir-to-d (- to 0.23.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gir-to-d ldc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gir-to-d.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 360 days old (needed 5 days)
• gitaly (- to 16.8.2+ds3-2)
  • Migration status for gitaly (- to 16.8.2+ds3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitaly would introduce bugs in testing: #1088134
    • Build-Depends(-Arch): gitaly gitlab-shell (not considered)
    • Depends: gitaly gitlab-shell (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitaly.html
    • 360 days old (needed 5 days)
• q2-feature-classifier (- to 2024.2.0-1)
  • Migration status for q2-feature-classifier (- to 2024.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-feature-classifier would introduce bugs in testing: #1071882
    • autopkgtest for q2-feature-classifier/2024.2.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): q2-feature-classifier q2-feature-table (not considered)
    • Build-Depends(-Arch): q2-feature-classifier q2-quality-control (not considered)
    • Build-Depends(-Arch): q2-feature-classifier q2-taxa
    • Build-Depends(-Arch): q2-feature-classifier q2-types (not considered)
    • Build-Depends(-Arch): q2-feature-classifier qiime (not considered)
    • Depends: q2-feature-classifier q2-feature-table (not considered)
    • Depends: q2-feature-classifier q2-quality-control (not considered)
    • Depends: q2-feature-classifier q2-taxa
    • Depends: q2-feature-classifier q2-types (not considered)
    • Depends: q2-feature-classifier qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-feature-classifier.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 360 days old (needed 5 days)
• ruby-grape-path-helpers (- to 2.0.1-2)
  • Migration status for ruby-grape-path-helpers (- 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): 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/2.0.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 360 days old (needed 2 days)
• sklearn-pandas (- to 2.2.0-3)
  • Migration status for sklearn-pandas (- to 2.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sklearn-pandas would introduce bugs in testing: #1084379
    • autopkgtest for sklearn-pandas/2.2.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sklearn-pandas.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 360 days old (needed 5 days)
• triton (- to 2.0.0.post1-4)
  • Migration status for triton (- to 2.0.0.post1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating triton would introduce bugs in testing: #1061219, #1067839
    • Build-Depends(-Arch): triton llvm-toolchain-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/triton.html
    • autopkgtest for triton/2.0.0.post1-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 361 days old (needed 2 days)
• python-certbot-dns-dnsimple (- to 2.9.0-1)
  • Migration status for python-certbot-dns-dnsimple (- to 2.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-dnsimple lexicon (not considered)
    • Depends: python-certbot-dns-dnsimple lexicon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-dnsimple.html
    • autopkgtest for python-certbot-dns-dnsimple/2.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 362 days old (needed 5 days)
• python-certbot-dns-gehirn (- to 2.9.0-1)
  • Migration status for python-certbot-dns-gehirn (- to 2.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-gehirn lexicon (not considered)
    • Depends: python-certbot-dns-gehirn lexicon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-gehirn.html
    • autopkgtest for python-certbot-dns-gehirn/2.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 362 days old (needed 5 days)
• python-certbot-dns-linode (- to 2.9.0-1)
  • Migration status for python-certbot-dns-linode (- to 2.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-linode lexicon (not considered)
    • Depends: python-certbot-dns-linode lexicon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-linode.html
    • autopkgtest for python-certbot-dns-linode/2.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 362 days old (needed 5 days)
• python-certbot-dns-ovh (- to 2.9.0-1)
  • Migration status for python-certbot-dns-ovh (- to 2.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-ovh lexicon (not considered)
    • Depends: python-certbot-dns-ovh lexicon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-ovh.html
    • autopkgtest for python-certbot-dns-ovh/2.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 362 days old (needed 5 days)
• python-certbot-dns-sakuracloud (- to 2.9.0-1)
  • Migration status for python-certbot-dns-sakuracloud (- to 2.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-sakuracloud lexicon (not considered)
    • Depends: python-certbot-dns-sakuracloud lexicon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-sakuracloud.html
    • autopkgtest for python-certbot-dns-sakuracloud/2.9.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 362 days old (needed 5 days)
• gtklock (- to 2.1.0-1)
  • Migration status for gtklock (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtklock would introduce bugs in testing: #1085992
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtklock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 363 days old (needed 5 days)
• lexicon (- to 3.17.0-1)
  • Migration status for lexicon (- to 3.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lexicon would introduce bugs in testing: #1076826
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lexicon.html
    • autopkgtest for lexicon/3.17.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 364 days old (needed 5 days)
• octave-arduino (- to 0.12.1-2)
  • Migration status for octave-arduino (- to 0.12.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: octave-arduino arduino (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-arduino.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for octave-arduino/0.12.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 365 days old (needed 5 days)
• r-cran-mertools (- to 0.6.2-1)
  • Migration status for r-cran-mertools (- to 0.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-mertools would introduce bugs in testing: #1071171
    • autopkgtest for r-cran-mertools/0.6.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mertools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 365 days old (needed 5 days)
• octave-vrml (- to 1.0.13-9)
  • Migration status for octave-vrml (- to 1.0.13-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for octave-vrml/1.0.13-9: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Depends: octave-vrml whitedune (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-vrml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 366 days old (needed 5 days)
• prody (- to 2.4.1+dfsg-2)
  • Migration status for prody (- to 2.4.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-prody/amd64 has unsatisfiable dependency
    • python3-prody/arm64 has unsatisfiable dependency
    • python3-prody/armel has unsatisfiable dependency
    • python3-prody/armhf has unsatisfiable dependency
    • python3-prody/mips64el has unsatisfiable dependency
    • python3-prody/ppc64el has unsatisfiable dependency
    • python3-prody/riscv64 has unsatisfiable dependency
    • Updating prody would introduce bugs in testing: #1058454, #1071807
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/prody.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 366 days old (needed 5 days)
• psychopy (- to 2023.2.4+dfsg-3)
  • Migration status for psychopy (- to 2023.2.4+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating psychopy would introduce bugs in testing: #1084568, #1086772
    • autopkgtest for psychopy/2023.2.4+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): psychopy python-pyo (not considered)
    • Depends: psychopy astunparse (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psychopy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 368 days old (needed 5 days)
• ruby-rails-assets-markdown-it-diaspora-mention (- to 1.2.0-3)
  • Migration status for ruby-rails-assets-markdown-it-diaspora-mention (- to 1.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-markdown-it-diaspora-mention would introduce bugs in testing: #1092700
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-markdown-it-diaspora-mention.html
    • autopkgtest for ruby-rails-assets-markdown-it-diaspora-mention/1.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 369 days old (needed 2 days)
• ruby-rails-assets-underscore (- to 1.8.3+dfsg-5)
  • Migration status for ruby-rails-assets-underscore (- to 1.8.3+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-underscore would introduce bugs in testing: #1091737, #1092701
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-underscore.html
    • autopkgtest for ruby-rails-assets-underscore/1.8.3+dfsg-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 369 days old (needed 2 days)
• python-feather-format (- to 0.3.1+dfsg1-8)
  • Migration status for python-feather-format (- to 0.3.1+dfsg1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-feather-format/amd64 has unsatisfiable dependency
    • python3-feather-format/arm64 has unsatisfiable dependency
    • python3-feather-format/armel has unsatisfiable dependency
    • python3-feather-format/armhf has unsatisfiable dependency
    • python3-feather-format/i386 has unsatisfiable dependency
    • python3-feather-format/mips64el has unsatisfiable dependency
    • python3-feather-format/ppc64el has unsatisfiable dependency
    • python3-feather-format/riscv64 has unsatisfiable dependency
    • python3-feather-format/s390x has unsatisfiable dependency
    • Updating python-feather-format would introduce bugs in testing: #1090271, #1092784
    • Build-Depends(-Arch): python-feather-format cython-legacy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-feather-format.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 370 days old (needed 5 days)
• ruby-mmap2 (- to 2.2.9-1)
  • Migration status for ruby-mmap2 (- to 2.2.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-mmap2 would introduce bugs in testing: #1075466
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-mmap2.html
    • autopkgtest for ruby-mmap2/2.2.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 372 days old (needed 2 days)
• ruby-redis-actionpack (- to 5.4.0-1)
  • Migration status for ruby-redis-actionpack (- to 5.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-redis-actionpack would introduce bugs in testing: #1095384
    • Build-Depends(-Arch): ruby-redis-actionpack ruby-redis-rack (not considered)
    • Depends: ruby-redis-actionpack ruby-redis-rack (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-actionpack.html
    • autopkgtest for ruby-redis-actionpack/5.4.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 372 days old (needed 5 days)
• django-simple-redis-admin (- to 1.4.0-4)
  • Migration status for django-simple-redis-admin (- to 1.4.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-simple-redis-admin would introduce bugs in testing: #1072858
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-simple-redis-admin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 373 days old (needed 5 days)
• abinit (- to 9.10.4-3)
  • Migration status for abinit (- to 9.10.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating abinit would introduce bugs in testing: #1076027, #1089281
    • autopkgtest for abinit/9.10.4-3: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/abinit.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 374 days old (needed 5 days)
• giada (- to 0.22.0-4)
  • Migration status for giada (- to 0.22.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • giada/amd64 has unsatisfiable dependency
    • giada/arm64 has unsatisfiable dependency
    • giada/armhf has unsatisfiable dependency
    • giada/i386 has unsatisfiable dependency
    • giada/mips64el has unsatisfiable dependency
    • giada/ppc64el has unsatisfiable dependency
    • giada/riscv64 has unsatisfiable dependency
    • giada/s390x has unsatisfiable dependency
    • Updating giada would introduce bugs in testing: #1073997
    • Build-Depends(-Arch): giada juce
    • Built-Using: giada juce
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/giada.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 riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 374 days old (needed 5 days)
• rss-glx (- to 0.9.1-6.5)
  • Migration status for rss-glx (- to 0.9.1-6.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rss-glx/amd64 has unsatisfiable dependency
    • rss-glx/arm64 has unsatisfiable dependency
    • rss-glx/armel has unsatisfiable dependency
    • rss-glx/armhf has unsatisfiable dependency
    • rss-glx/i386 has unsatisfiable dependency
    • rss-glx/mips64el has unsatisfiable dependency
    • rss-glx/ppc64el has unsatisfiable dependency
    • rss-glx/riscv64 has unsatisfiable dependency
    • rss-glx/s390x has unsatisfiable dependency
    • Updating rss-glx would introduce bugs in testing: #1079338
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rss-glx.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 375 days old (needed 5 days)
• python-lsp-ruff (- to 1.5.3-2)
  • Migration status for python-lsp-ruff (- to 1.5.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-lsp-ruff/1.5.3-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): python-lsp-ruff ruff (not considered)
    • Depends: python-lsp-ruff ruff (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lsp-ruff.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 376 days old (needed 5 days)
• c2x (- to 2.41.b+ds-2)
  • Migration status for c2x (- to 2.41.b+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): c2x spglib (not considered)
    • Depends: c2x spglib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/c2x.html
    • autopkgtest for c2x/2.41.b+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 377 days old (needed 2 days)
• dt-schema (- to 2023.11-3)
  • Migration status for dt-schema (- to 2023.11-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dt-schema would introduce bugs in testing: #1063562
    • autopkgtest for dt-schema/2023.11-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dt-schema.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 381 days old (needed 5 days)
• asterisk-espeak (- to 5.0~1-4)
  • Migration status for asterisk-espeak (- to 5.0~1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for asterisk-espeak/5.0~1-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): asterisk-espeak asterisk (not considered)
    • Depends: asterisk-espeak asterisk (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-espeak.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 383 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• wine-development (- to 8.21~repack-1)
  • Migration status for wine-development (- to 8.21~repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wine-development would introduce bugs in testing: #1069318, #988246
    • wine-development unsatisfiable Build-Depends(-Arch) on amd64: unicode-idna (<< 16)
    • wine-development unsatisfiable Build-Depends(-Arch) on arm64: unicode-idna (<< 16)
    • wine-development unsatisfiable Build-Depends(-Arch) on armel: unicode-idna (<< 16)
    • wine-development unsatisfiable Build-Depends(-Arch) on armhf: unicode-idna (<< 16)
    • wine-development unsatisfiable Build-Depends(-Arch) on i386: unicode-idna (<< 16)
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wine-development.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 383 days old (needed 5 days)
• pmacct (- to 1.7.8-2)
  • Migration status for pmacct (- to 1.7.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pmacct avro-c (not considered)
    • Depends: pmacct avro-c (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pmacct.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 384 days old (needed 5 days)
• redmine-plugin-redhopper (- to 2.0.0-3)
  • Migration status for redmine-plugin-redhopper (- to 2.0.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-redhopper redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redmine-plugin-redhopper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 385 days old (needed 5 days)
• calculix-cgx (- to 2.21+dfsg-1)
  • Migration status for calculix-cgx (- to 2.21+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating calculix-cgx would introduce bugs in testing: #1077425
    • Build-Depends(-Arch): calculix-cgx libsnl (not considered)
    • Depends: calculix-cgx libsnl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calculix-cgx.html
    • autopkgtest for calculix-cgx/2.21+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 388 days old (needed 2 days)
• mlpy (- to 3.5.0+ds-3)
  • Migration status for mlpy (- to 3.5.0+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-mlpy-lib/amd64 has unsatisfiable dependency
    • python3-mlpy-lib/arm64 has unsatisfiable dependency
    • python3-mlpy-lib/armel has unsatisfiable dependency
    • python3-mlpy-lib/armhf has unsatisfiable dependency
    • python3-mlpy-lib/i386 has unsatisfiable dependency
    • python3-mlpy-lib/mips64el has unsatisfiable dependency
    • python3-mlpy-lib/ppc64el has unsatisfiable dependency
    • python3-mlpy-lib/riscv64 has unsatisfiable dependency
    • python3-mlpy-lib/s390x has unsatisfiable dependency
    • Updating mlpy would introduce bugs in testing: #1075279, #1092779
    • Build-Depends(-Arch): mlpy cython-legacy (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mlpy.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • 388 days old (needed 5 days)
• pybj (- to 0.2.6-2)
  • Migration status for pybj (- to 0.2.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pybj would introduce bugs in testing: #1076204, #1076206
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pybj.html
    • autopkgtest for pybj/0.2.6-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 388 days old (needed 5 days)
• python-refurb (- to 1.27.0-1)
  • Migration status for python-refurb (- to 1.27.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-refurb would introduce bugs in testing: #1077460
    • autopkgtest for python-refurb/1.27.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-refurb.html
    • 388 days old (needed 5 days)
• elvis-tiny (- to 1.4-24.2)
  • Migration status for elvis-tiny (- to 1.4-24.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating elvis-tiny would introduce bugs in testing: #1074934
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elvis-tiny.html
    • 390 days old (needed 5 days)
• endless-sky (- to 0.10.4-1)
  • Migration status for endless-sky (- to 0.10.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating endless-sky would introduce bugs in testing: #1061241
    • 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/e/endless-sky.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 390 days old (needed 5 days)
• pypdf2 (- to 2.12.1-4)
  • Migration status for pypdf2 (- to 2.12.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pypdf2 would introduce bugs in testing: #1061162, #1066762
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pypdf2.html
    • 390 days old (needed 5 days)
• cypari2 (- to 2.1.4-1)
  • Migration status for cypari2 (- to 2.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-cypari2/amd64 has unsatisfiable dependency
    • python3-cypari2/arm64 has unsatisfiable dependency
    • python3-cypari2/armel has unsatisfiable dependency
    • python3-cypari2/armhf has unsatisfiable dependency
    • python3-cypari2/i386 has unsatisfiable dependency
    • python3-cypari2/mips64el has unsatisfiable dependency
    • python3-cypari2/ppc64el has unsatisfiable dependency
    • python3-cypari2/riscv64 has unsatisfiable dependency
    • python3-cypari2/s390x has unsatisfiable dependency
    • Updating cypari2 would introduce bugs in testing: #1081687
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cypari2.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 391 days old (needed 5 days)
• r-cran-fastcluster (- to 1.2.6-1)
  • Migration status for r-cran-fastcluster (- to 1.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-fastcluster would introduce bugs in testing: #1094704
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fastcluster.html
    • autopkgtest for r-cran-fastcluster/1.2.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 392 days old (needed 2 days)
• r-cran-bigmemory (- to 4.6.4-1)
  • Migration status for r-cran-bigmemory (- to 4.6.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-bigmemory would introduce bugs in testing: #1064135
    • autopkgtest for r-cran-bigmemory/4.6.4-1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-bigmemory.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 393 days old (needed 5 days)
• ezquake (- to 3.6.4-3)
  • Migration status for ezquake (- to 3.6.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ezquake would introduce bugs in testing: #1088891
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ezquake.html
    • 395 days old (needed 5 days)
• libdbd-oracle-perl (- to 1.83-3)
  • Migration status for libdbd-oracle-perl (- to 1.83-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libdbd-oracle-perl/amd64 has unsatisfiable dependency
    • libdbd-oracle-perl/i386 has unsatisfiable dependency
    • Updating libdbd-oracle-perl would introduce bugs in testing: #1069101
    • libdbd-oracle-perl unsatisfiable Build-Depends(-Arch) on amd64: oracle-instantclient-basic
    • libdbd-oracle-perl unsatisfiable Build-Depends(-Arch) on amd64: oracle-instantclient-devel
    • libdbd-oracle-perl unsatisfiable Build-Depends(-Arch) on i386: oracle-instantclient-basic
    • libdbd-oracle-perl unsatisfiable Build-Depends(-Arch) on i386: oracle-instantclient-devel
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • 396 days old (needed 5 days)
• ostree-push (- to 1.1.0-1)
  • Migration status for ostree-push (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ostree-push would introduce bugs in testing: #1066774
    • autopkgtest for ostree-push/1.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ostree-push.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 396 days old (needed 5 days)
• awesfx (- to 0.5.2-1.1)
  • Migration status for awesfx (- to 0.5.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating awesfx would introduce bugs in testing: #1074831
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/awesfx.html
    • 397 days old (needed 5 days)
• fweb (- to 1.62-14.1)
  • Migration status for fweb (- to 1.62-14.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fweb would introduce bugs in testing: #1074976
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fweb.html
    • 397 days old (needed 5 days)
• python-aiortc (- to 1.6.0-1)
  • Migration status for python-aiortc (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiortc would introduce bugs in testing: #1081093
    • autopkgtest for python-aiortc/1.6.0-1: arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • autopkgtest for python-aiortc/blocked-on-ci-infra: amd64: Ignored failure, riscv64: Ignored failure
    • python-aiortc unsatisfiable Build-Depends(-Arch) on amd64: python3-av (<< 12)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on arm64: python3-av (<< 12)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on armel: python3-av (<< 12)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on armhf: python3-av (<< 12)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on i386: python3-av (<< 12)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on mips64el: python3-av (<< 12)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on ppc64el: python3-av (<< 12)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on riscv64: python3-av (<< 12)
    • python-aiortc unsatisfiable Build-Depends(-Arch) on s390x: python3-av (<< 12)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiortc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 397 days old (needed 5 days)
• sfwbar (- to 1.0~beta13-1)
  • Migration status for sfwbar (- to 1.0~beta13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sfwbar would introduce bugs in testing: #1091451
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sfwbar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 397 days old (needed 5 days)
• pybik (- to 3.0-6)
  • Migration status for pybik (- to 3.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pybik-bin/amd64 has unsatisfiable dependency
    • pybik-bin/arm64 has unsatisfiable dependency
    • pybik-bin/armel has unsatisfiable dependency
    • pybik-bin/armhf has unsatisfiable dependency
    • pybik-bin/i386 has unsatisfiable dependency
    • pybik-bin/mips64el has unsatisfiable dependency
    • pybik-bin/ppc64el has unsatisfiable dependency
    • pybik-bin/riscv64 has unsatisfiable dependency
    • pybik-bin/s390x has unsatisfiable dependency
    • Updating pybik would introduce bugs in testing: #1087643, #1092780
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pybik.html
    • Build-Depends(-Arch): pybik cython-legacy (not considered)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 399 days old (needed 5 days)
• python-cramjam (- to 2.7.0.1+ds1-2)
  • Migration status for python-cramjam (- to 2.7.0.1+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-cramjam/amd64 has unsatisfiable dependency
    • python3-cramjam/arm64 has unsatisfiable dependency
    • Updating python-cramjam would introduce bugs in testing: #1061310
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cramjam.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 400 days old (needed 5 days)
• unittest2 (- to 1.1.0-11)
  • Migration status for unittest2 (- to 1.1.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unittest2 would introduce bugs in testing: #1077434
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unittest2.html
    • autopkgtest for unittest2/1.1.0-11: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 400 days old (needed 2 days)
• mailman-hyperkitty (- to 1.2.1-2)
  • Migration status for mailman-hyperkitty (- to 1.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mailman-hyperkitty would introduce bugs in testing: #1093342
    • autopkgtest for mailman-hyperkitty/1.2.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): mailman-hyperkitty mailman3 (not considered)
    • Depends: mailman-hyperkitty mailman3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailman-hyperkitty.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 401 days old (needed 5 days)
• r-cran-tikzdevice (- to 0.12.6-1)
  • Migration status for r-cran-tikzdevice (- to 0.12.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-tikzdevice r-cran-filehash (not considered)
    • Depends: r-cran-tikzdevice r-cran-filehash (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tikzdevice.html
    • autopkgtest for r-cran-tikzdevice/0.12.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 401 days old (needed 2 days)
• pysph (- to 1.0~b1-8)
  • Migration status for pysph (- to 1.0~b1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pysph/amd64 has unsatisfiable dependency
    • python3-pysph/arm64 has unsatisfiable dependency
    • Updating pysph would introduce bugs in testing: #1084148
    • Build-Depends(-Arch): pysph mayavi2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysph.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 402 days old (needed 5 days)
• python-loompy (- to 3.0.7+dfsg-3)
  • Migration status for python-loompy (- to 3.0.7+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-loompy would introduce bugs in testing: #1090279
    • autopkgtest for python-loompy/3.0.7+dfsg-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): python-loompy numba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-loompy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 403 days old (needed 5 days)
• apt-verify (- to 2.0-1)
  • Migration status for apt-verify (- to 2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apt-verify would introduce bugs in testing: #1061185
    • Not built on buildd: arch all binaries uploaded by jas, 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/apt-verify.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 404 days old (needed 5 days)
• civicrm (- to 5.68.1+dfsg1-1)
  • Migration status for civicrm (- to 5.68.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • civicrm-common/amd64 has unsatisfiable dependency
    • civicrm-common/arm64 has unsatisfiable dependency
    • Updating civicrm would introduce bugs in testing: #1078951
    • Depends: civicrm wordpress (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/civicrm.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 405 days old (needed 5 days)
• codraft (- to 2.2.1-3)
  • Migration status for codraft (- to 2.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating codraft would introduce bugs in testing: #1064714
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/codraft.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for codraft/2.2.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass
    • Waiting for reproducibility test results on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 405 days old (needed 2 days)
• intake (- to 0.6.6-3)
  • Migration status for intake (- to 0.6.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intake would introduce bugs in testing: #1063953, #1064752
    • autopkgtest for intake/0.6.6-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
    • Build-Depends(-Arch): intake appdirs (not considered)
    • Depends: intake appdirs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intake.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 405 days old (needed 5 days)
• ruby-devise (- to 4.9.3-1)
  • Migration status for ruby-devise (- to 4.9.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-devise ruby-warden (not considered)
    • Depends: ruby-devise ruby-warden (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ruby-devise ruby-responders (not considered)
    • Depends: ruby-devise ruby-responders (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-devise.html
    • autopkgtest for ruby-devise/4.9.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 407 days old (needed 2 days)
• einsteinpy (- to 0.4.0-3)
  • Migration status for einsteinpy (- to 0.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating einsteinpy would introduce bugs in testing: #1063527
    • autopkgtest for einsteinpy/0.4.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/einsteinpy.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 408 days old (needed 5 days)
• concurrent-log-handler (- to 0.9.25-1)
  • Migration status for concurrent-log-handler (- to 0.9.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating concurrent-log-handler would introduce bugs in testing: #1071301
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/concurrent-log-handler.html
    • 410 days old (needed 5 days)
• erlang-bitcask (- to 2.1.0-2)
  • Migration status for erlang-bitcask (- to 2.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating erlang-bitcask would introduce bugs in testing: #1091312
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-bitcask.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 411 days old (needed 5 days)
• yash (- to 2.55-2)
  • Migration status for yash (- to 2.55-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yash would introduce bugs in testing: #1086620
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yash.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 412 days old (needed 5 days)
• casparcg-server (- to 2.3.3+dfsg-3.2)
  • Migration status for casparcg-server (- to 2.3.3+dfsg-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • casparcg-server/amd64 has unsatisfiable dependency
    • casparcg-server/arm64 has unsatisfiable dependency
    • Updating casparcg-server would introduce bugs in testing: #1077504
  • 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
    • 415 days old (needed 5 days)
• mate-hud (- to 22.10.3-2)
  • Migration status for mate-hud (- to 22.10.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mate-hud vala-panel-appmenu (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-hud.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 415 days old (needed 5 days)
• golang-github-henrybear327-proton-api-bridge (- to 1.0.0-2)
  • Migration status for golang-github-henrybear327-proton-api-bridge (- to 1.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-henrybear327-proton-api-bridge golang-github-protonmail-gluon (not considered)
    • Depends: golang-github-henrybear327-proton-api-bridge golang-github-protonmail-gluon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): golang-github-henrybear327-proton-api-bridge golang-github-henrybear327-go-proton-api (not considered)
    • Depends: golang-github-henrybear327-proton-api-bridge golang-github-henrybear327-go-proton-api (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-henrybear327-proton-api-bridge.html
    • autopkgtest for golang-github-henrybear327-proton-api-bridge/1.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 418 days old (needed 2 days)
• golang-github-protonmail-go-srp (- to 0.0.7+ds-2)
  • Migration status for golang-github-protonmail-go-srp (- to 0.0.7+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-protonmail-go-srp/0.0.7+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-protonmail-go-srp golang-github-cronokirby-saferith (not considered)
    • Depends: golang-github-protonmail-go-srp golang-github-cronokirby-saferith (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-protonmail-go-srp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 418 days old (needed 5 days)
• aseba (- to 1.6.99+dfsg-9)
  • Migration status for aseba (- to 1.6.99+dfsg-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aseba would introduce bugs in testing: #1074821
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aseba.html
    • 419 days old (needed 5 days)
• burp (- to 3.1.4-3.1)
  • Migration status for burp (- to 3.1.4-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating burp would introduce bugs in testing: #1091240
    • autopkgtest for burp/3.1.4-3.1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/burp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 420 days old (needed 5 days)
• greenbone-security-assistant (- to 22.9.1-1)
  • Migration status for greenbone-security-assistant (- to 22.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating greenbone-security-assistant would introduce bugs in testing: #1029780, #1061106
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 422 days old (needed 5 days)
• squeak-vm (- to 1:4.10.2.2614+20120917~dfsg-2)
  • Migration status for squeak-vm (- to 1:4.10.2.2614+20120917~dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating squeak-vm would introduce bugs in testing: #1066698
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squeak-vm.html
    • 422 days old (needed 5 days)
• apper (- to 1.0.0-5)
  • Migration status for apper (- to 1.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • apper/amd64 has unsatisfiable dependency
    • apper/arm64 has unsatisfiable dependency
    • apper/armel has unsatisfiable dependency
    • apper/armhf has unsatisfiable dependency
    • apper/i386 has unsatisfiable dependency
    • apper/mips64el has unsatisfiable dependency
    • apper/ppc64el has unsatisfiable dependency
    • apper/riscv64 has unsatisfiable dependency
    • apper/s390x has unsatisfiable dependency
    • Updating apper would introduce bugs in testing: #1090089
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apper.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 423 days old (needed 5 days)
• appstream-generator (- to 0.9.1-1)
  • Migration status for appstream-generator (- to 0.9.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: appstream-generator ldc (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): appstream-generator gir-to-d
    • 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
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 424 days old (needed 5 days)
• pysurfer (- to 0.11.2-1)
  • Migration status for pysurfer (- to 0.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pysurfer/0.11.2-1: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): pysurfer mayavi2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysurfer.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 425 days old (needed 5 days)
• pynn (- to 0.10.1-3)
  • Migration status for pynn (- to 0.10.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pynn would introduce bugs in testing: #1018448, #1071337
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynn.html
    • autopkgtest for pynn/0.10.1-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 426 days old (needed 5 days)
• hg-git (- to 1.0.3-1)
  • Migration status for hg-git (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hg-git would introduce bugs in testing: #1058538, #1092199
    • autopkgtest for hg-git/1.0.3-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hg-git.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 429 days old (needed 5 days)
• pandoc-sidenote (- to 0.23.0-1)
  • Migration status for pandoc-sidenote (- to 0.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-pandoc-sidenote-doc/amd64 has unsatisfiable dependency
    • pandoc-sidenote/amd64 has unsatisfiable dependency
    • libghc-pandoc-sidenote-doc/arm64 has unsatisfiable dependency
    • pandoc-sidenote/arm64 has unsatisfiable dependency
    • pandoc-sidenote/ppc64el has unsatisfiable dependency
    • pandoc-sidenote/s390x has unsatisfiable dependency
    • Updating pandoc-sidenote would introduce bugs in testing: #1055980
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pandoc-sidenote.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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 430 days old (needed 5 days)
• rear (- to 2.7+dfsg-1.1)
  • Migration status for rear (- to 2.7+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Updating rear would introduce bugs in testing: #1060747
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rear.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 431 days old (needed 5 days)
    • Remove hint for (transitive) dependency: rear
• node-har-validator (- to 5.1.5-4)
  • Migration status for node-har-validator (- to 5.1.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-har-validator would introduce bugs in testing: #1024575
    • autopkgtest for node-har-validator/5.1.5-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-har-validator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 434 days old (needed 5 days)
• kmscon (- to 9.0.0-5)
  • Migration status for kmscon (- to 9.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kmscon would introduce bugs in testing: #1061686
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kmscon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 436 days old (needed 5 days)
• python-array-api-compat (- to 1.4-1)
  • Migration status for python-array-api-compat (- to 1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-array-api-compat would introduce bugs in testing: #1071777
    • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-array-api-compat.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 436 days old (needed 5 days)
• slashtime (- to 0.5.13-3)
  • Migration status for slashtime (- to 0.5.13-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): slashtime java-gnome (not considered)
    • Depends: slashtime java-gnome (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slashtime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 437 days old (needed 5 days)
• comskip (- to 0.82.009+git20230112.d0cc422+ds.1-2.1)
  • Migration status for comskip (- to 0.82.009+git20230112.d0cc422+ds.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • comskip/amd64 has unsatisfiable dependency
    • comskip-gui/amd64 has unsatisfiable dependency
    • comskip/arm64 has unsatisfiable dependency
    • comskip-gui/arm64 has unsatisfiable dependency
    • comskip/armel has unsatisfiable dependency
    • comskip-gui/armel has unsatisfiable dependency
    • comskip/armhf has unsatisfiable dependency
    • comskip-gui/armhf has unsatisfiable dependency
    • comskip/i386 has unsatisfiable dependency
    • comskip-gui/i386 has unsatisfiable dependency
    • comskip/mips64el has unsatisfiable dependency
    • comskip-gui/mips64el has unsatisfiable dependency
    • comskip/ppc64el has unsatisfiable dependency
    • comskip-gui/ppc64el has unsatisfiable dependency
    • comskip/riscv64 has unsatisfiable dependency
    • comskip-gui/riscv64 has unsatisfiable dependency
    • comskip/s390x has unsatisfiable dependency
    • comskip-gui/s390x has unsatisfiable dependency
    • Updating comskip would introduce bugs in testing: #1072406
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/comskip.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 438 days old (needed 5 days)
• gau2grid (- to 2.0.7-2)
  • Migration status for gau2grid (- to 2.0.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gau2grid would introduce bugs in testing: #1074649
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gau2grid.html
    • autopkgtest for gau2grid/2.0.7-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 438 days old (needed 5 days)
• pilon (- to 1.24-3)
  • Migration status for pilon (- to 1.24-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pilon/1.24-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): pilon scala (not considered)
    • Depends: pilon scala (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pilon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 438 days old (needed 5 days)
• rockhopper (- to 2.0.3+dfsg2-4)
  • Migration status for rockhopper (- to 2.0.3+dfsg2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rockhopper/2.0.3+dfsg2-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rockhopper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 438 days old (needed 5 days)
• node-webfont (- to 11.4.0+dfsg2+~cs35.7.26-10)
  • Migration status for node-webfont (- to 11.4.0+dfsg2+~cs35.7.26-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-webfont would introduce bugs in testing: #1084309
    • autopkgtest for node-webfont/11.4.0+dfsg2+~cs35.7.26-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-webfont.html
    • 441 days old (needed 5 days)
• imexam (- to 0.9.1-6)
  • Migration status for imexam (- to 0.9.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating imexam would introduce bugs in testing: #1084277
    • autopkgtest for imexam/0.9.1-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/imexam.html
    • 443 days old (needed 5 days)
• open-build-service (- to 2.9.4-10)
  • Migration status for open-build-service (- to 2.9.4-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating open-build-service would introduce bugs in testing: #1088953
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open-build-service.html
    • autopkgtest for open-build-service/2.9.4-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 445 days old (needed 2 days)
• pygccjit (- to 0.4-13)
  • Migration status for pygccjit (- to 0.4-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-gccjit/amd64 has unsatisfiable dependency
    • python3-gccjit/arm64 has unsatisfiable dependency
    • python3-gccjit/armel has unsatisfiable dependency
    • python3-gccjit/armhf has unsatisfiable dependency
    • python3-gccjit/i386 has unsatisfiable dependency
    • python3-gccjit/mips64el has unsatisfiable dependency
    • python3-gccjit/ppc64el has unsatisfiable dependency
    • python3-gccjit/riscv64 has unsatisfiable dependency
    • python3-gccjit/s390x has unsatisfiable dependency
    • Updating pygccjit would introduce bugs in testing: #1082097, #1092782
    • Build-Depends(-Arch): pygccjit cython-legacy (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pygccjit.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 445 days old (needed 5 days)
• recutils (- to 1.9-3)
  • Migration status for recutils (- to 1.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • recutils/armel has unsatisfiable dependency
    • recutils/armhf has unsatisfiable dependency
    • Updating recutils would introduce bugs in testing: #1066370
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/recutils.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 445 days old (needed 5 days)
• acedb (- to 4.9.39+dfsg.02-9)
  • Migration status for acedb (- to 4.9.39+dfsg.02-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating acedb would introduce bugs in testing: #1066334
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/acedb.html
    • 446 days old (needed 5 days)
• mysql-workbench (- to 8.0.32+dfsg-2)
  • Migration status for mysql-workbench (- to 8.0.32+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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/ppc64el has unsatisfiable dependency
    • mysql-workbench/riscv64 has unsatisfiable dependency
    • mysql-workbench/s390x has unsatisfiable dependency
    • Updating mysql-workbench would introduce bugs in testing: #1000093, #1074563, #1084634, #1085320
    • mysql-workbench unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • mysql-workbench unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • mysql-workbench unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • mysql-workbench unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • mysql-workbench unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • mysql-workbench unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • mysql-workbench unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • mysql-workbench unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • mysql-workbench unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • 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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 447 days old (needed 5 days)
• xemacs21-packages (- to 2009.02.17.dfsg.3-3)
  • Migration status for xemacs21-packages (- to 2009.02.17.dfsg.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: xemacs21-packages xemacs21 (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xemacs21-packages.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 447 days old (needed 5 days)
• node-wikibase-cli (- to 15.15.4-5)
  • Migration status for node-wikibase-cli (- to 15.15.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-wikibase-cli would introduce bugs in testing: #1056699, #1056708
    • autopkgtest for node-wikibase-cli/15.15.4-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-wikibase-cli.html
    • 448 days old (needed 5 days)
• gnome-split (- to 1.2-5)
  • Migration status for gnome-split (- 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): gnome-split java-gnome (not considered)
    • Depends: gnome-split java-gnome (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-split.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 450 days old (needed 5 days)
• yersinia (- to 0.8.2-2.2)
  • Migration status for yersinia (- to 0.8.2-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yersinia would introduce bugs in testing: #1075697
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yersinia.html
    • 450 days old (needed 5 days)
• pixelmed (- to 20220618+dfsg-2)
  • Migration status for pixelmed (- to 20220618+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pixelmed would introduce bugs in testing: #1084318
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pixelmed.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 452 days old (needed 5 days)
• cryptojs (- to 3.1.2+dfsg-4)
  • Migration status for cryptojs (- to 3.1.2+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cryptojs would introduce bugs in testing: #1056014
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cryptojs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 454 days old (needed 5 days)
• ruby-voight-kampff (- to 2.0.0-1)
  • Migration status for ruby-voight-kampff (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-voight-kampff/amd64 has unsatisfiable dependency
    • ruby-voight-kampff/arm64 has unsatisfiable dependency
    • Updating ruby-voight-kampff would introduce bugs in testing: #1094529
    • ruby-voight-kampff unsatisfiable Build-Depends(-Arch) on amd64: ruby-rack (<< 3.0)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-voight-kampff.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 454 days old (needed 5 days)
• jupyter-ydoc (- to 1.0.2-2)
  • Migration status for jupyter-ydoc (- to 1.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-jupyter-ydoc/arm64 has unsatisfiable dependency
    • Updating jupyter-ydoc would introduce bugs in testing: #1071771
    • autopkgtest for jupyter-ydoc/1.0.2-2: amd64: Regression or new test ♻
    • Build-Depends(-Arch): jupyter-ydoc ypy (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/j/jupyter-ydoc.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 455 days old (needed 5 days)
• ypy (- to 0.7.0~a1-2)
  • Migration status for ypy (- to 0.7.0~a1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ypy would introduce bugs in testing: #1071899
    • ypy unsatisfiable Build-Depends(-Arch) on amd64: librust-lib0-dev
    • ypy unsatisfiable Build-Depends(-Arch) on amd64: librust-yrs-dev
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/y/ypy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 455 days old (needed 5 days)
• in-toto (- to 2.0.0-1)
  • Migration status for in-toto (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating in-toto would introduce bugs in testing: #1090235
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/in-toto.html
    • 456 days old (needed 5 days)
• python-diagrams (- to 0.23.4-1)
  • Migration status for python-diagrams (- to 0.23.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-diagrams/amd64 has unsatisfiable dependency
    • python3-diagrams/arm64 has unsatisfiable dependency
    • Updating python-diagrams would introduce bugs in testing: #1057174
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-diagrams.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 457 days old (needed 5 days)
• kiwi-boxed-plugin (- to 0.2.31-1)
  • Migration status for kiwi-boxed-plugin (- to 0.2.31-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kiwi-boxed-plugin kiwi (not considered)
    • Depends: kiwi-boxed-plugin kiwi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kiwi-boxed-plugin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 459 days old (needed 5 days)
• calcurse (- to 4.8.1-1.1)
  • Migration status for calcurse (- to 4.8.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating calcurse would introduce bugs in testing: #1086259
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calcurse.html
    • 460 days old (needed 5 days)
• umap-learn (- to 0.5.4+dfsg-1)
  • Migration status for umap-learn (- to 0.5.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umap-learn would introduce bugs in testing: #1071816
    • autopkgtest for umap-learn/0.5.4+dfsg-1: amd64: Regression or new test ♻, arm64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): umap-learn numba (not considered)
    • Build-Depends(-Arch): umap-learn python-pynndescent (not considered)
    • Depends: umap-learn python-pynndescent (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umap-learn.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 462 days old (needed 5 days)
• ruby-timeliness (- to 0.4.5-1)
  • Migration status for ruby-timeliness (- to 0.4.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-timeliness would introduce bugs in testing: #1086314
    • autopkgtest for ruby-timeliness/0.4.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-timeliness.html
    • 465 days old (needed 5 days)
• ycm-cmake-modules (- to 0.13.0-3)
  • Migration status for ycm-cmake-modules (- to 0.13.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ycm-cmake-modules would introduce bugs in testing: #1057941
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ycm-cmake-modules.html
    • 466 days old (needed 5 days)
• robot-testing-framework (- to 2.0.1+ds1-3)
  • Migration status for robot-testing-framework (- to 2.0.1+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating robot-testing-framework would introduce bugs in testing: #1075449
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/robot-testing-framework.html
    • 467 days old (needed 5 days)
• tint2 (- to 17.0.1-1.1)
  • Migration status for tint2 (- to 17.0.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tint2 would introduce bugs in testing: #1082699
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tint2.html
    • 468 days old (needed 5 days)
• ruby-distribution (- to 0.8.0+dfsg-1)
  • Migration status for ruby-distribution (- to 0.8.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-distribution/0.8.0+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-distribution ruby-gsl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-distribution.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 469 days old (needed 5 days)
• kasumi (- to 2.5+debian1-1)
  • Migration status for kasumi (- to 2.5+debian1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kasumi would introduce bugs in testing: #1075108
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kasumi.html
    • 474 days old (needed 5 days)
• parcellite (- to 1.2.1-8)
  • Migration status for parcellite (- to 1.2.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating parcellite would introduce bugs in testing: #1075362
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/parcellite.html
    • autopkgtest for parcellite/1.2.1-8: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 476 days old (needed 5 days)
• python-certbot-dns-gandi (- to 1.4.3-2)
  • Migration status for python-certbot-dns-gandi (- to 1.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-certbot-dns-gandi would introduce bugs in testing: #1038920
    • autopkgtest for python-certbot-dns-gandi/1.4.3-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-gandi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 476 days old (needed 5 days)
• haskell-soap-tls (- to 0.1.1.4-6)
  • Migration status for haskell-soap-tls (- to 0.1.1.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-soap-tls-dev/amd64 has unsatisfiable dependency
    • libghc-soap-tls-doc/amd64 has unsatisfiable dependency
    • libghc-soap-tls-prof/amd64 has unsatisfiable dependency
    • libghc-soap-tls-dev/arm64 has unsatisfiable dependency
    • libghc-soap-tls-doc/arm64 has unsatisfiable dependency
    • libghc-soap-tls-prof/arm64 has unsatisfiable dependency
    • libghc-soap-tls-dev/armel has unsatisfiable dependency
    • libghc-soap-tls-prof/armel has unsatisfiable dependency
    • libghc-soap-tls-dev/armhf has unsatisfiable dependency
    • libghc-soap-tls-prof/armhf has unsatisfiable dependency
    • libghc-soap-tls-dev/i386 has unsatisfiable dependency
    • libghc-soap-tls-prof/i386 has unsatisfiable dependency
    • libghc-soap-tls-dev/mips64el has unsatisfiable dependency
    • libghc-soap-tls-prof/mips64el has unsatisfiable dependency
    • libghc-soap-tls-dev/ppc64el has unsatisfiable dependency
    • libghc-soap-tls-prof/ppc64el has unsatisfiable dependency
    • libghc-soap-tls-dev/riscv64 has unsatisfiable dependency
    • libghc-soap-tls-prof/riscv64 has unsatisfiable dependency
    • libghc-soap-tls-dev/s390x has unsatisfiable dependency
    • libghc-soap-tls-prof/s390x has unsatisfiable dependency
    • Updating haskell-soap-tls would introduce bugs in testing: #1082423
    • Build-Depends(-Arch): haskell-soap-tls haskell-connection (not considered)
    • Build-Depends-Indep: haskell-soap-tls haskell-connection (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-soap-tls.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 477 days old (needed 5 days)
• empire-hub (- to 1.0.2.2+nmu1)
  • Migration status for empire-hub (- to 1.0.2.2+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating empire-hub would introduce bugs in testing: #1074937
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/empire-hub.html
    • 478 days old (needed 5 days)
• haskell-cryptol (- to 3.0.0-1)
  • Migration status for haskell-cryptol (- to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-cryptol-dev/amd64 has unsatisfiable dependency
    • libghc-cryptol-doc/amd64 has unsatisfiable dependency
    • libghc-cryptol-prof/amd64 has unsatisfiable dependency
    • libghc-cryptol-dev/arm64 has unsatisfiable dependency
    • libghc-cryptol-doc/arm64 has unsatisfiable dependency
    • libghc-cryptol-prof/arm64 has unsatisfiable dependency
    • libghc-cryptol-dev/mips64el has unsatisfiable dependency
    • libghc-cryptol-prof/mips64el has unsatisfiable dependency
    • libghc-cryptol-dev/ppc64el has unsatisfiable dependency
    • libghc-cryptol-prof/ppc64el has unsatisfiable dependency
    • libghc-cryptol-dev/riscv64 has unsatisfiable dependency
    • libghc-cryptol-prof/riscv64 has unsatisfiable dependency
    • Updating haskell-cryptol would introduce bugs in testing: #1081937
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on amd64: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on arm64: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on mips64el: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on riscv64: libghc-base-compat-dev (<< 0.13)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-base-compat-dev (<< 0.13)
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-cryptol.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 riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 478 days old (needed 5 days)
• haskell-smtp-mail (- to 0.3.0.0-3)
  • Migration status for haskell-smtp-mail (- to 0.3.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-smtp-mail-dev/amd64 has unsatisfiable dependency
    • libghc-smtp-mail-doc/amd64 has unsatisfiable dependency
    • libghc-smtp-mail-prof/amd64 has unsatisfiable dependency
    • libghc-smtp-mail-dev/arm64 has unsatisfiable dependency
    • libghc-smtp-mail-doc/arm64 has unsatisfiable dependency
    • libghc-smtp-mail-prof/arm64 has unsatisfiable dependency
    • libghc-smtp-mail-dev/armel has unsatisfiable dependency
    • libghc-smtp-mail-prof/armel has unsatisfiable dependency
    • libghc-smtp-mail-dev/armhf has unsatisfiable dependency
    • libghc-smtp-mail-prof/armhf has unsatisfiable dependency
    • libghc-smtp-mail-dev/i386 has unsatisfiable dependency
    • libghc-smtp-mail-prof/i386 has unsatisfiable dependency
    • libghc-smtp-mail-dev/mips64el has unsatisfiable dependency
    • libghc-smtp-mail-prof/mips64el has unsatisfiable dependency
    • libghc-smtp-mail-dev/ppc64el has unsatisfiable dependency
    • libghc-smtp-mail-prof/ppc64el has unsatisfiable dependency
    • libghc-smtp-mail-dev/riscv64 has unsatisfiable dependency
    • libghc-smtp-mail-prof/riscv64 has unsatisfiable dependency
    • libghc-smtp-mail-dev/s390x has unsatisfiable dependency
    • libghc-smtp-mail-prof/s390x has unsatisfiable dependency
    • Updating haskell-smtp-mail would introduce bugs in testing: #1082420
    • Build-Depends(-Arch): haskell-smtp-mail haskell-connection (not considered)
    • Build-Depends-Indep: haskell-smtp-mail haskell-connection (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-smtp-mail.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 478 days old (needed 5 days)
• haskell-connection (- to 0.3.1-4)
  • Migration status for haskell-connection (- to 0.3.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-connection-dev/amd64 has unsatisfiable dependency
    • libghc-connection-doc/amd64 has unsatisfiable dependency
    • libghc-connection-prof/amd64 has unsatisfiable dependency
    • libghc-connection-dev/arm64 has unsatisfiable dependency
    • libghc-connection-doc/arm64 has unsatisfiable dependency
    • libghc-connection-prof/arm64 has unsatisfiable dependency
    • libghc-connection-dev/armel has unsatisfiable dependency
    • libghc-connection-prof/armel has unsatisfiable dependency
    • libghc-connection-dev/armhf has unsatisfiable dependency
    • libghc-connection-prof/armhf has unsatisfiable dependency
    • libghc-connection-dev/i386 has unsatisfiable dependency
    • libghc-connection-prof/i386 has unsatisfiable dependency
    • libghc-connection-dev/mips64el has unsatisfiable dependency
    • libghc-connection-prof/mips64el has unsatisfiable dependency
    • libghc-connection-dev/ppc64el has unsatisfiable dependency
    • libghc-connection-prof/ppc64el has unsatisfiable dependency
    • libghc-connection-dev/riscv64 has unsatisfiable dependency
    • libghc-connection-prof/riscv64 has unsatisfiable dependency
    • libghc-connection-dev/s390x has unsatisfiable dependency
    • libghc-connection-prof/s390x has unsatisfiable dependency
    • Updating haskell-connection would introduce bugs in testing: #1084124, #1085013
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-connection.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 479 days old (needed 5 days)
• opensearch (- to 2.4.1+dfsg-2)
  • Migration status for opensearch (- to 2.4.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensearch would introduce bugs in testing: #1066450
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensearch.html
    • 479 days old (needed 5 days)
• rust-xflags-macros (- to 0.3.1-1)
  • Migration status for rust-xflags-macros (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-xflags-macros/0.3.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xflags-macros.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 479 days old (needed 5 days)
• haskell-cryptohash-conduit (- to 0.1.1-13)
  • Migration status for haskell-cryptohash-conduit (- to 0.1.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-cryptohash-conduit-doc/amd64 has unsatisfiable dependency
    • libghc-cryptohash-conduit-doc/arm64 has unsatisfiable dependency
    • Updating haskell-cryptohash-conduit would introduce bugs in testing: #1082560
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-cryptohash-conduit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 480 days old (needed 5 days)
• canu (- to 2.2+dfsg-5)
  • Migration status for canu (- to 2.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for canu/2.2+dfsg-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • autopkgtest for canu/blocked-on-ci-infra: riscv64: Ignored failure
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/canu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 481 days old (needed 5 days)
• gnome-chemistry-utils (- to 0.14.17-6.2)
  • Migration status for gnome-chemistry-utils (- to 0.14.17-6.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-chemistry-utils would introduce bugs in testing: #1078386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-chemistry-utils.html
    • autopkgtest for gnome-chemistry-utils/0.14.17-6.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 481 days old (needed 2 days)
• haskell-crypto-random (- to 0.0.9-11)
  • Migration status for haskell-crypto-random (- to 0.0.9-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-crypto-random-dev/amd64 has unsatisfiable dependency
    • libghc-crypto-random-doc/amd64 has unsatisfiable dependency
    • libghc-crypto-random-prof/amd64 has unsatisfiable dependency
    • libghc-crypto-random-dev/arm64 has unsatisfiable dependency
    • libghc-crypto-random-doc/arm64 has unsatisfiable dependency
    • libghc-crypto-random-prof/arm64 has unsatisfiable dependency
    • libghc-crypto-random-dev/armel has unsatisfiable dependency
    • libghc-crypto-random-prof/armel has unsatisfiable dependency
    • libghc-crypto-random-dev/armhf has unsatisfiable dependency
    • libghc-crypto-random-prof/armhf has unsatisfiable dependency
    • libghc-crypto-random-dev/i386 has unsatisfiable dependency
    • libghc-crypto-random-prof/i386 has unsatisfiable dependency
    • libghc-crypto-random-dev/mips64el has unsatisfiable dependency
    • libghc-crypto-random-prof/mips64el has unsatisfiable dependency
    • libghc-crypto-random-dev/ppc64el has unsatisfiable dependency
    • libghc-crypto-random-prof/ppc64el has unsatisfiable dependency
    • libghc-crypto-random-dev/riscv64 has unsatisfiable dependency
    • libghc-crypto-random-prof/riscv64 has unsatisfiable dependency
    • libghc-crypto-random-dev/s390x has unsatisfiable dependency
    • libghc-crypto-random-prof/s390x has unsatisfiable dependency
    • Updating haskell-crypto-random would introduce bugs in testing: #1082405
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-crypto-random.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 481 days old (needed 5 days)
• rust-xflags (- to 0.3.1-1)
  • Migration status for rust-xflags (- to 0.3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-xflags rust-xflags-macros (not considered)
    • Depends: rust-xflags rust-xflags-macros (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xflags.html
    • autopkgtest for rust-xflags/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 485 days old (needed 2 days)
• procdump (- to 2.2-1)
  • Migration status for procdump (- to 2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating procdump would introduce bugs in testing: #1064137
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for procdump/2.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/procdump.html
    • 486 days old (needed 5 days)
• r-cran-propclust (- to 1.4-7-1)
  • Migration status for r-cran-propclust (- to 1.4-7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-propclust r-cran-fastcluster (not considered)
    • Depends: r-cran-propclust r-cran-fastcluster (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-propclust.html
    • autopkgtest for r-cran-propclust/1.4-7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 486 days old (needed 2 days)
• cdde (- to 0.3.1-1.1)
  • Migration status for cdde (- to 0.3.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cdde would introduce bugs in testing: #1066301
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cdde.html
    • 488 days old (needed 5 days)
• gnome-packagekit (- to 43.0-2)
  • Migration status for gnome-packagekit (- to 43.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-packagekit would introduce bugs in testing: #1074666
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-packagekit.html
    • 492 days old (needed 5 days)
• mrb (- to 0.3+nmu3)
  • Migration status for mrb (- to 0.3+nmu3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mrb would introduce bugs in testing: #1092435
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrb.html
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 492 days old (needed 5 days)
• haskell-web-routes-boomerang (- to 0.28.4.4-1)
  • Migration status for haskell-web-routes-boomerang (- to 0.28.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-web-routes-boomerang-dev/amd64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-doc/amd64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/amd64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/arm64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-doc/arm64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/arm64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/armel has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/armel has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/armhf has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/armhf has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/i386 has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/i386 has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/mips64el has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/mips64el has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/ppc64el has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/ppc64el has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/riscv64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/riscv64 has unsatisfiable dependency
    • libghc-web-routes-boomerang-dev/s390x has unsatisfiable dependency
    • libghc-web-routes-boomerang-prof/s390x has unsatisfiable dependency
    • Updating haskell-web-routes-boomerang would introduce bugs in testing: #1084755
    • Build-Depends(-Arch): haskell-web-routes-boomerang haskell-web-routes (not considered)
    • Build-Depends-Indep: haskell-web-routes-boomerang haskell-web-routes (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-web-routes-boomerang.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 493 days old (needed 5 days)
• haskell-web-routes-happstack (- to 0.23.12.3-1)
  • Migration status for haskell-web-routes-happstack (- to 0.23.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-web-routes-happstack-dev/amd64 has unsatisfiable dependency
    • libghc-web-routes-happstack-doc/amd64 has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/amd64 has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/arm64 has unsatisfiable dependency
    • libghc-web-routes-happstack-doc/arm64 has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/arm64 has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/armel has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/armel has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/armhf has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/armhf has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/i386 has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/i386 has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/mips64el has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/mips64el has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/ppc64el has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/ppc64el has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/riscv64 has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/riscv64 has unsatisfiable dependency
    • libghc-web-routes-happstack-dev/s390x has unsatisfiable dependency
    • libghc-web-routes-happstack-prof/s390x has unsatisfiable dependency
    • Updating haskell-web-routes-happstack would introduce bugs in testing: #1084756
    • Build-Depends(-Arch): haskell-web-routes-happstack haskell-web-routes (not considered)
    • Build-Depends-Indep: haskell-web-routes-happstack haskell-web-routes (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-web-routes-happstack.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 493 days old (needed 5 days)
• haskell-web-routes-th (- to 0.22.8.1-1)
  • Migration status for haskell-web-routes-th (- to 0.22.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-web-routes-th-dev/amd64 has unsatisfiable dependency
    • libghc-web-routes-th-doc/amd64 has unsatisfiable dependency
    • libghc-web-routes-th-prof/amd64 has unsatisfiable dependency
    • libghc-web-routes-th-dev/arm64 has unsatisfiable dependency
    • libghc-web-routes-th-doc/arm64 has unsatisfiable dependency
    • libghc-web-routes-th-prof/arm64 has unsatisfiable dependency
    • libghc-web-routes-th-dev/armel has unsatisfiable dependency
    • libghc-web-routes-th-prof/armel has unsatisfiable dependency
    • libghc-web-routes-th-dev/armhf has unsatisfiable dependency
    • libghc-web-routes-th-prof/armhf has unsatisfiable dependency
    • libghc-web-routes-th-dev/i386 has unsatisfiable dependency
    • libghc-web-routes-th-prof/i386 has unsatisfiable dependency
    • libghc-web-routes-th-dev/mips64el has unsatisfiable dependency
    • libghc-web-routes-th-prof/mips64el has unsatisfiable dependency
    • libghc-web-routes-th-dev/ppc64el has unsatisfiable dependency
    • libghc-web-routes-th-prof/ppc64el has unsatisfiable dependency
    • libghc-web-routes-th-dev/riscv64 has unsatisfiable dependency
    • libghc-web-routes-th-prof/riscv64 has unsatisfiable dependency
    • libghc-web-routes-th-dev/s390x has unsatisfiable dependency
    • libghc-web-routes-th-prof/s390x has unsatisfiable dependency
    • Updating haskell-web-routes-th would introduce bugs in testing: #1084757
    • Build-Depends(-Arch): haskell-web-routes-th haskell-web-routes (not considered)
    • Build-Depends-Indep: haskell-web-routes-th haskell-web-routes (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-web-routes-th.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 493 days old (needed 5 days)
• rust-extprim (- to 1.7.1-2)
  • Migration status for rust-extprim (- to 1.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-extprim would introduce bugs in testing: #1053625
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-extprim.html
    • autopkgtest for rust-extprim/1.7.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 494 days old (needed 2 days)
• haskell-csv-conduit (- to 0.7.3.0-2)
  • Migration status for haskell-csv-conduit (- to 0.7.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-csv-conduit-dev/amd64 has unsatisfiable dependency
    • libghc-csv-conduit-doc/amd64 has unsatisfiable dependency
    • libghc-csv-conduit-prof/amd64 has unsatisfiable dependency
    • libghc-csv-conduit-dev/arm64 has unsatisfiable dependency
    • libghc-csv-conduit-doc/arm64 has unsatisfiable dependency
    • libghc-csv-conduit-prof/arm64 has unsatisfiable dependency
    • libghc-csv-conduit-dev/armel has unsatisfiable dependency
    • libghc-csv-conduit-prof/armel has unsatisfiable dependency
    • libghc-csv-conduit-dev/armhf has unsatisfiable dependency
    • libghc-csv-conduit-prof/armhf has unsatisfiable dependency
    • libghc-csv-conduit-dev/i386 has unsatisfiable dependency
    • libghc-csv-conduit-prof/i386 has unsatisfiable dependency
    • libghc-csv-conduit-dev/mips64el has unsatisfiable dependency
    • libghc-csv-conduit-prof/mips64el has unsatisfiable dependency
    • libghc-csv-conduit-dev/ppc64el has unsatisfiable dependency
    • libghc-csv-conduit-prof/ppc64el has unsatisfiable dependency
    • libghc-csv-conduit-dev/riscv64 has unsatisfiable dependency
    • libghc-csv-conduit-prof/riscv64 has unsatisfiable dependency
    • libghc-csv-conduit-dev/s390x has unsatisfiable dependency
    • libghc-csv-conduit-prof/s390x has unsatisfiable dependency
    • Updating haskell-csv-conduit would introduce bugs in testing: #1082408
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-csv-conduit.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 495 days old (needed 5 days)
• haskell-hsx-jmacro (- to 7.3.8.2-2)
  • Migration status for haskell-hsx-jmacro (- to 7.3.8.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hsx-jmacro-dev/amd64 has unsatisfiable dependency
    • libghc-hsx-jmacro-doc/amd64 has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/amd64 has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/arm64 has unsatisfiable dependency
    • libghc-hsx-jmacro-doc/arm64 has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/arm64 has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/armel has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/armel has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/armhf has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/armhf has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/i386 has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/i386 has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/mips64el has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/mips64el has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/ppc64el has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/ppc64el has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/riscv64 has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/riscv64 has unsatisfiable dependency
    • libghc-hsx-jmacro-dev/s390x has unsatisfiable dependency
    • libghc-hsx-jmacro-prof/s390x has unsatisfiable dependency
    • Updating haskell-hsx-jmacro would introduce bugs in testing: #1082355
    • Build-Depends(-Arch): haskell-hsx-jmacro haskell-hsp (not considered)
    • Build-Depends-Indep: haskell-hsx-jmacro haskell-hsp (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hsx-jmacro.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 495 days old (needed 5 days)
• haskell-publicsuffixlist (- to 0.1-15)
  • Migration status for haskell-publicsuffixlist (- to 0.1-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-publicsuffixlist-dev/amd64 has unsatisfiable dependency
    • libghc-publicsuffixlist-doc/amd64 has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/amd64 has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/arm64 has unsatisfiable dependency
    • libghc-publicsuffixlist-doc/arm64 has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/arm64 has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/armel has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/armel has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/armhf has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/armhf has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/i386 has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/i386 has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/mips64el has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/mips64el has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/ppc64el has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/ppc64el has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/riscv64 has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/riscv64 has unsatisfiable dependency
    • libghc-publicsuffixlist-dev/s390x has unsatisfiable dependency
    • libghc-publicsuffixlist-prof/s390x has unsatisfiable dependency
    • Updating haskell-publicsuffixlist would introduce bugs in testing: #1082006
    • Build-Depends(-Arch): haskell-publicsuffixlist haskell-idna (not considered)
    • Build-Depends-Indep: haskell-publicsuffixlist haskell-idna (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-publicsuffixlist.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 495 days old (needed 5 days)
• haskell-web-routes-hsp (- to 0.24.6.2-2)
  • Migration status for haskell-web-routes-hsp (- to 0.24.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-web-routes-hsp-dev/amd64 has unsatisfiable dependency
    • libghc-web-routes-hsp-doc/amd64 has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/amd64 has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/arm64 has unsatisfiable dependency
    • libghc-web-routes-hsp-doc/arm64 has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/arm64 has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/armel has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/armel has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/armhf has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/armhf has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/i386 has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/i386 has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/mips64el has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/mips64el has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/ppc64el has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/ppc64el has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/riscv64 has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/riscv64 has unsatisfiable dependency
    • libghc-web-routes-hsp-dev/s390x has unsatisfiable dependency
    • libghc-web-routes-hsp-prof/s390x has unsatisfiable dependency
    • Updating haskell-web-routes-hsp would introduce bugs in testing: #1082356
    • Build-Depends(-Arch): haskell-web-routes-hsp haskell-hsp (not considered)
    • Build-Depends(-Arch): haskell-web-routes-hsp haskell-web-routes (not considered)
    • Build-Depends-Indep: haskell-web-routes-hsp haskell-hsp (not considered)
    • Build-Depends-Indep: haskell-web-routes-hsp haskell-web-routes (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-web-routes-hsp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 495 days old (needed 5 days)
• apertium-en-gl (- to 0.5.4-2)
  • Migration status for apertium-en-gl (- to 0.5.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-en-gl would introduce bugs in testing: #1061038
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-en-gl.html
    • 496 days old (needed 5 days)
• haskell-web-routes (- to 0.27.15-1)
  • Migration status for haskell-web-routes (- to 0.27.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-web-routes-dev/amd64 has unsatisfiable dependency
    • libghc-web-routes-doc/amd64 has unsatisfiable dependency
    • libghc-web-routes-prof/amd64 has unsatisfiable dependency
    • libghc-web-routes-dev/arm64 has unsatisfiable dependency
    • libghc-web-routes-doc/arm64 has unsatisfiable dependency
    • libghc-web-routes-prof/arm64 has unsatisfiable dependency
    • libghc-web-routes-dev/armel has unsatisfiable dependency
    • libghc-web-routes-prof/armel has unsatisfiable dependency
    • libghc-web-routes-dev/armhf has unsatisfiable dependency
    • libghc-web-routes-prof/armhf has unsatisfiable dependency
    • libghc-web-routes-dev/i386 has unsatisfiable dependency
    • libghc-web-routes-prof/i386 has unsatisfiable dependency
    • libghc-web-routes-dev/mips64el has unsatisfiable dependency
    • libghc-web-routes-prof/mips64el has unsatisfiable dependency
    • libghc-web-routes-dev/ppc64el has unsatisfiable dependency
    • libghc-web-routes-prof/ppc64el has unsatisfiable dependency
    • libghc-web-routes-dev/riscv64 has unsatisfiable dependency
    • libghc-web-routes-prof/riscv64 has unsatisfiable dependency
    • libghc-web-routes-dev/s390x has unsatisfiable dependency
    • libghc-web-routes-prof/s390x has unsatisfiable dependency
    • Updating haskell-web-routes would introduce bugs in testing: #1084129, #1084758
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-web-routes.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 496 days old (needed 5 days)
• yosys-plugin-ghdl (- to 0.0~git20230419.5b64ccf-1)
  • Migration status for yosys-plugin-ghdl (- to 0.0~git20230419.5b64ccf-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • yosys-plugin-ghdl/amd64 has unsatisfiable dependency
    • yosys-plugin-ghdl/i386 has unsatisfiable dependency
    • Updating yosys-plugin-ghdl would introduce bugs in testing: #1067465
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on arm64: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on armel: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on i386: libghdl-dev (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on i386: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on mips64el: libghdl-dev (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on mips64el: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on ppc64el: ghdl-mcode (>= 3.0.0)
    • missing build on arm64
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): yosys-plugin-ghdl yosys (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/y/yosys-plugin-ghdl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 502 days old (needed 5 days)
• bonnie++ (- to 2.00a+nmu2)
  • Migration status for bonnie++ (- to 2.00a+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for bonnie++/2.00a+nmu2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bonnie++.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 503 days old (needed 5 days)
• jh7100-bootloader-recovery (- to 0~2021.07.14~git2b268a1c-3)
  • Migration status for jh7100-bootloader-recovery (- to 0~2021.07.14~git2b268a1c-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jh7100-bootloader-recovery would introduce bugs in testing: #1066679
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jh7100-bootloader-recovery.html
    • 504 days old (needed 5 days)
• fbb (- to 7.011-3)
  • Migration status for fbb (- to 7.011-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fbb would introduce bugs in testing: #1091298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fbb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 505 days old (needed 5 days)
• lxdm (- to 0.5.3-5)
  • Migration status for lxdm (- to 0.5.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lxdm would introduce bugs in testing: #1053089
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxdm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 509 days old (needed 5 days)
• rust-test-strategy (- to 0.3.1-1)
  • Migration status for rust-test-strategy (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-test-strategy/0.3.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-test-strategy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 509 days old (needed 5 days)
• gimp-texturize (- to 2.2-4)
  • Migration status for gimp-texturize (- to 2.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gimp-texturize/amd64 has unsatisfiable dependency
    • gimp-texturize/arm64 has unsatisfiable dependency
    • gimp-texturize/armel has unsatisfiable dependency
    • gimp-texturize/armhf has unsatisfiable dependency
    • gimp-texturize/i386 has unsatisfiable dependency
    • gimp-texturize/mips64el has unsatisfiable dependency
    • gimp-texturize/ppc64el has unsatisfiable dependency
    • gimp-texturize/riscv64 has unsatisfiable dependency
    • Updating gimp-texturize would introduce bugs in testing: #1088063
    • gimp-texturize unsatisfiable Build-Depends(-Arch) on amd64: libgimp2.0-dev
    • gimp-texturize unsatisfiable Build-Depends(-Arch) on arm64: libgimp2.0-dev
    • gimp-texturize unsatisfiable Build-Depends(-Arch) on armel: libgimp2.0-dev
    • gimp-texturize unsatisfiable Build-Depends(-Arch) on armhf: libgimp2.0-dev
    • gimp-texturize unsatisfiable Build-Depends(-Arch) on i386: libgimp2.0-dev
    • gimp-texturize unsatisfiable Build-Depends(-Arch) on mips64el: libgimp2.0-dev
    • gimp-texturize unsatisfiable Build-Depends(-Arch) on ppc64el: libgimp2.0-dev
    • gimp-texturize unsatisfiable Build-Depends(-Arch) on riscv64: libgimp2.0-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gimp-texturize.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 511 days old (needed 5 days)
• python-pyo (- to 1.0.5-5)
  • Migration status for python-pyo (- to 1.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pyo/amd64 has unsatisfiable dependency
    • python3-pyo/arm64 has unsatisfiable dependency
    • python3-pyo/armel has unsatisfiable dependency
    • python3-pyo/armhf has unsatisfiable dependency
    • python3-pyo/i386 has unsatisfiable dependency
    • python3-pyo/mips64el has unsatisfiable dependency
    • python3-pyo/ppc64el has unsatisfiable dependency
    • python3-pyo/riscv64 has unsatisfiable dependency
    • python3-pyo/s390x has unsatisfiable dependency
    • Updating python-pyo would introduce bugs in testing: #1075420, #1084560
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/python-pyo.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 511 days old (needed 5 days)
• ghostess (- to 20210101-1)
  • Migration status for ghostess (- to 20210101-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ghostess would introduce bugs in testing: #1074995
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghostess.html
    • 512 days old (needed 5 days)
• gosa-plugins-systems (- to 2.8~git20211027.5741b8f-9)
  • Migration status for gosa-plugins-systems (- to 2.8~git20211027.5741b8f-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: gosa-plugins-systems gosa (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-systems.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 513 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• jack-capture (- to 0.9.73-4)
  • Migration status for jack-capture (- to 0.9.73-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jack-capture would introduce bugs in testing: #1071318
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jack-capture.html
    • 513 days old (needed 5 days)
• jack-tools (- to 20131226-2)
  • Migration status for jack-tools (- to 20131226-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jack-tools would introduce bugs in testing: #1075097
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jack-tools.html
    • 513 days old (needed 5 days)
• materia-kde (- to 20220823-2)
  • Migration status for materia-kde (- to 20220823-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating materia-kde would introduce bugs in testing: #1091373
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/materia-kde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 514 days old (needed 5 days)
• haskell-reform-happstack (- to 0.2.5.6-1)
  • Migration status for haskell-reform-happstack (- to 0.2.5.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-reform-happstack-dev/amd64 has unsatisfiable dependency
    • libghc-reform-happstack-doc/amd64 has unsatisfiable dependency
    • libghc-reform-happstack-prof/amd64 has unsatisfiable dependency
    • libghc-reform-happstack-dev/arm64 has unsatisfiable dependency
    • libghc-reform-happstack-doc/arm64 has unsatisfiable dependency
    • libghc-reform-happstack-prof/arm64 has unsatisfiable dependency
    • libghc-reform-happstack-dev/armel has unsatisfiable dependency
    • libghc-reform-happstack-prof/armel has unsatisfiable dependency
    • libghc-reform-happstack-dev/armhf has unsatisfiable dependency
    • libghc-reform-happstack-prof/armhf has unsatisfiable dependency
    • libghc-reform-happstack-dev/i386 has unsatisfiable dependency
    • libghc-reform-happstack-prof/i386 has unsatisfiable dependency
    • libghc-reform-happstack-dev/mips64el has unsatisfiable dependency
    • libghc-reform-happstack-prof/mips64el has unsatisfiable dependency
    • libghc-reform-happstack-dev/ppc64el has unsatisfiable dependency
    • libghc-reform-happstack-prof/ppc64el has unsatisfiable dependency
    • libghc-reform-happstack-dev/riscv64 has unsatisfiable dependency
    • libghc-reform-happstack-prof/riscv64 has unsatisfiable dependency
    • libghc-reform-happstack-dev/s390x has unsatisfiable dependency
    • libghc-reform-happstack-prof/s390x has unsatisfiable dependency
    • Updating haskell-reform-happstack would introduce bugs in testing: #1082414
    • Build-Depends(-Arch): haskell-reform-happstack haskell-reform (not considered)
    • Build-Depends-Indep: haskell-reform-happstack haskell-reform (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-reform-happstack.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 515 days old (needed 5 days)
• haskell-happstack-hsp (- to 7.3.7.7-1)
  • Migration status for haskell-happstack-hsp (- to 7.3.7.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-happstack-hsp-dev/amd64 has unsatisfiable dependency
    • libghc-happstack-hsp-doc/amd64 has unsatisfiable dependency
    • libghc-happstack-hsp-prof/amd64 has unsatisfiable dependency
    • libghc-happstack-hsp-dev/arm64 has unsatisfiable dependency
    • libghc-happstack-hsp-doc/arm64 has unsatisfiable dependency
    • libghc-happstack-hsp-prof/arm64 has unsatisfiable dependency
    • libghc-happstack-hsp-dev/armel has unsatisfiable dependency
    • libghc-happstack-hsp-prof/armel has unsatisfiable dependency
    • libghc-happstack-hsp-dev/armhf has unsatisfiable dependency
    • libghc-happstack-hsp-prof/armhf has unsatisfiable dependency
    • libghc-happstack-hsp-dev/i386 has unsatisfiable dependency
    • libghc-happstack-hsp-prof/i386 has unsatisfiable dependency
    • libghc-happstack-hsp-dev/mips64el has unsatisfiable dependency
    • libghc-happstack-hsp-prof/mips64el has unsatisfiable dependency
    • libghc-happstack-hsp-dev/ppc64el has unsatisfiable dependency
    • libghc-happstack-hsp-prof/ppc64el has unsatisfiable dependency
    • libghc-happstack-hsp-dev/riscv64 has unsatisfiable dependency
    • libghc-happstack-hsp-prof/riscv64 has unsatisfiable dependency
    • libghc-happstack-hsp-dev/s390x has unsatisfiable dependency
    • libghc-happstack-hsp-prof/s390x has unsatisfiable dependency
    • Updating haskell-happstack-hsp would introduce bugs in testing: #1082351
    • Build-Depends(-Arch): haskell-happstack-hsp haskell-harp (not considered)
    • Build-Depends(-Arch): haskell-happstack-hsp haskell-hsp (not considered)
    • Build-Depends(-Arch): haskell-happstack-hsp haskell-hsx2hs (not considered)
    • Build-Depends-Indep: haskell-happstack-hsp haskell-harp (not considered)
    • Build-Depends-Indep: haskell-happstack-hsp haskell-hsp (not considered)
    • Build-Depends-Indep: haskell-happstack-hsp haskell-hsx2hs (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-happstack-hsp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 516 days old (needed 5 days)
• xpra (- to 3.1.5+dfsg1-0.2)
  • Migration status for xpra (- to 3.1.5+dfsg1-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xpra/amd64 has unsatisfiable dependency
    • xpra/arm64 has unsatisfiable dependency
    • xpra/armel has unsatisfiable dependency
    • xpra/armhf has unsatisfiable dependency
    • xpra/i386 has unsatisfiable dependency
    • xpra/mips64el has unsatisfiable dependency
    • xpra/ppc64el has unsatisfiable dependency
    • xpra/riscv64 has unsatisfiable dependency
    • xpra/s390x has unsatisfiable dependency
    • Updating xpra would introduce bugs in testing: #1067627, #1072463, #1086122
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/x/xpra.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 517 days old (needed 5 days)
• rust-xxhash-c-sys (- to 0.8.4-1)
  • Migration status for rust-xxhash-c-sys (- to 0.8.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-xxhash-c-sys would introduce bugs in testing: #1092411
    • autopkgtest for rust-xxhash-c-sys/0.8.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xxhash-c-sys.html
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 518 days old (needed 5 days)
• haskell-reform (- to 0.2.7.5-2)
  • Migration status for haskell-reform (- to 0.2.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-reform-dev/amd64 has unsatisfiable dependency
    • libghc-reform-doc/amd64 has unsatisfiable dependency
    • libghc-reform-prof/amd64 has unsatisfiable dependency
    • libghc-reform-dev/arm64 has unsatisfiable dependency
    • libghc-reform-doc/arm64 has unsatisfiable dependency
    • libghc-reform-prof/arm64 has unsatisfiable dependency
    • libghc-reform-dev/armel has unsatisfiable dependency
    • libghc-reform-prof/armel has unsatisfiable dependency
    • libghc-reform-dev/armhf has unsatisfiable dependency
    • libghc-reform-prof/armhf has unsatisfiable dependency
    • libghc-reform-dev/i386 has unsatisfiable dependency
    • libghc-reform-prof/i386 has unsatisfiable dependency
    • libghc-reform-dev/mips64el has unsatisfiable dependency
    • libghc-reform-prof/mips64el has unsatisfiable dependency
    • libghc-reform-dev/ppc64el has unsatisfiable dependency
    • libghc-reform-prof/ppc64el has unsatisfiable dependency
    • libghc-reform-dev/riscv64 has unsatisfiable dependency
    • libghc-reform-prof/riscv64 has unsatisfiable dependency
    • libghc-reform-dev/s390x has unsatisfiable dependency
    • libghc-reform-prof/s390x has unsatisfiable dependency
    • Updating haskell-reform would introduce bugs in testing: #1082413
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-reform.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 519 days old (needed 5 days)
• soundgrain (- to 6.0.1-5)
  • Migration status for soundgrain (- to 6.0.1-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/soundgrain.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 519 days old (needed 5 days)
• frama-c (- to 20220511-manganese-5)
  • Migration status for frama-c (- to 20220511-manganese-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • frama-c-base/amd64 has unsatisfiable dependency
    • frama-c-base/arm64 has unsatisfiable dependency
    • frama-c-base/armel has unsatisfiable dependency
    • frama-c-base/armhf has unsatisfiable dependency
    • frama-c-base/i386 has unsatisfiable dependency
    • frama-c-base/mips64el has unsatisfiable dependency
    • frama-c-base/ppc64el has unsatisfiable dependency
    • frama-c-base/riscv64 has unsatisfiable dependency
    • frama-c-base/s390x has unsatisfiable dependency
    • Updating frama-c would introduce bugs in testing: #1093102
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frama-c.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 523 days old (needed 5 days)
• haskell-idna (- to 0.3.0-13)
  • Migration status for haskell-idna (- to 0.3.0-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-idna-dev/amd64 has unsatisfiable dependency
    • libghc-idna-doc/amd64 has unsatisfiable dependency
    • libghc-idna-prof/amd64 has unsatisfiable dependency
    • libghc-idna-dev/arm64 has unsatisfiable dependency
    • libghc-idna-doc/arm64 has unsatisfiable dependency
    • libghc-idna-prof/arm64 has unsatisfiable dependency
    • libghc-idna-dev/armel has unsatisfiable dependency
    • libghc-idna-prof/armel has unsatisfiable dependency
    • libghc-idna-dev/armhf has unsatisfiable dependency
    • libghc-idna-prof/armhf has unsatisfiable dependency
    • libghc-idna-dev/i386 has unsatisfiable dependency
    • libghc-idna-prof/i386 has unsatisfiable dependency
    • libghc-idna-dev/mips64el has unsatisfiable dependency
    • libghc-idna-prof/mips64el has unsatisfiable dependency
    • libghc-idna-dev/ppc64el has unsatisfiable dependency
    • libghc-idna-prof/ppc64el has unsatisfiable dependency
    • libghc-idna-dev/riscv64 has unsatisfiable dependency
    • libghc-idna-prof/riscv64 has unsatisfiable dependency
    • libghc-idna-dev/s390x has unsatisfiable dependency
    • libghc-idna-prof/s390x has unsatisfiable dependency
    • Updating haskell-idna would introduce bugs in testing: #1082007
    • Build-Depends(-Arch): haskell-idna haskell-punycode (not considered)
    • Build-Depends-Indep: haskell-idna haskell-punycode (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-idna.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 523 days old (needed 5 days)
• haskell-regex-applicative-text (- to 0.1.0.1-10)
  • Migration status for haskell-regex-applicative-text (- to 0.1.0.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-regex-applicative-text-doc/amd64 has unsatisfiable dependency
    • libghc-regex-applicative-text-doc/arm64 has unsatisfiable dependency
    • Updating haskell-regex-applicative-text would introduce bugs in testing: #1082416
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-regex-applicative-text.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 523 days old (needed 5 days)
• haskell-file-location (- to 0.4.9.1-5)
  • Migration status for haskell-file-location (- to 0.4.9.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-file-location-dev/amd64 has unsatisfiable dependency
    • libghc-file-location-doc/amd64 has unsatisfiable dependency
    • libghc-file-location-prof/amd64 has unsatisfiable dependency
    • libghc-file-location-dev/arm64 has unsatisfiable dependency
    • libghc-file-location-doc/arm64 has unsatisfiable dependency
    • libghc-file-location-prof/arm64 has unsatisfiable dependency
    • libghc-file-location-dev/armel has unsatisfiable dependency
    • libghc-file-location-prof/armel has unsatisfiable dependency
    • libghc-file-location-dev/armhf has unsatisfiable dependency
    • libghc-file-location-prof/armhf has unsatisfiable dependency
    • libghc-file-location-dev/i386 has unsatisfiable dependency
    • libghc-file-location-prof/i386 has unsatisfiable dependency
    • libghc-file-location-dev/mips64el has unsatisfiable dependency
    • libghc-file-location-prof/mips64el has unsatisfiable dependency
    • libghc-file-location-dev/ppc64el has unsatisfiable dependency
    • libghc-file-location-prof/ppc64el has unsatisfiable dependency
    • libghc-file-location-dev/riscv64 has unsatisfiable dependency
    • libghc-file-location-prof/riscv64 has unsatisfiable dependency
    • libghc-file-location-dev/s390x has unsatisfiable dependency
    • libghc-file-location-prof/s390x has unsatisfiable dependency
    • Updating haskell-file-location would introduce bugs in testing: #1082409
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-file-location.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 524 days old (needed 5 days)
• vuls (- to 0.6.1-5)
  • Migration status for vuls (- to 0.6.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vuls would introduce bugs in testing: #1085477
    • Build-Depends(-Arch): vuls go-cve-dictionary (not considered)
    • Build-Depends(-Arch): vuls go-exploitdb (not considered)
    • Build-Depends(-Arch): vuls gost (not considered)
    • Build-Depends(-Arch): vuls goval-dictionary (not considered)
    • Built-Using: vuls go-cve-dictionary (not considered)
    • Built-Using: vuls go-exploitdb (not considered)
    • Built-Using: vuls golang-1.23
    • Built-Using: vuls golang-github-go-redis-redis (not considered)
    • Built-Using: vuls golang-github-mattn-go-runewidth
    • Built-Using: vuls gost (not considered)
    • Built-Using: vuls goval-dictionary (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vuls.html
    • autopkgtest for vuls/0.6.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 525 days old (needed 2 days)
• haskell-argon2 (- to 1.3.0.1-10)
  • Migration status for haskell-argon2 (- to 1.3.0.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-argon2-dev/amd64 has unsatisfiable dependency
    • libghc-argon2-doc/amd64 has unsatisfiable dependency
    • libghc-argon2-prof/amd64 has unsatisfiable dependency
    • libghc-argon2-dev/arm64 has unsatisfiable dependency
    • libghc-argon2-doc/arm64 has unsatisfiable dependency
    • libghc-argon2-prof/arm64 has unsatisfiable dependency
    • libghc-argon2-dev/armel has unsatisfiable dependency
    • libghc-argon2-prof/armel has unsatisfiable dependency
    • libghc-argon2-dev/armhf has unsatisfiable dependency
    • libghc-argon2-prof/armhf has unsatisfiable dependency
    • libghc-argon2-dev/i386 has unsatisfiable dependency
    • libghc-argon2-prof/i386 has unsatisfiable dependency
    • libghc-argon2-dev/mips64el has unsatisfiable dependency
    • libghc-argon2-prof/mips64el has unsatisfiable dependency
    • libghc-argon2-dev/ppc64el has unsatisfiable dependency
    • libghc-argon2-prof/ppc64el has unsatisfiable dependency
    • libghc-argon2-dev/riscv64 has unsatisfiable dependency
    • libghc-argon2-prof/riscv64 has unsatisfiable dependency
    • libghc-argon2-dev/s390x has unsatisfiable dependency
    • libghc-argon2-prof/s390x has unsatisfiable dependency
    • Updating haskell-argon2 would introduce bugs in testing: #1081373
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-argon2.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 526 days old (needed 5 days)
• haskell-hsx2hs (- to 0.14.1.11-1)
  • Migration status for haskell-hsx2hs (- to 0.14.1.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hsx2hs-dev/amd64 has unsatisfiable dependency
    • libghc-hsx2hs-doc/amd64 has unsatisfiable dependency
    • libghc-hsx2hs-prof/amd64 has unsatisfiable dependency
    • libghc-hsx2hs-dev/arm64 has unsatisfiable dependency
    • libghc-hsx2hs-doc/arm64 has unsatisfiable dependency
    • libghc-hsx2hs-prof/arm64 has unsatisfiable dependency
    • libghc-hsx2hs-dev/armel has unsatisfiable dependency
    • libghc-hsx2hs-prof/armel has unsatisfiable dependency
    • libghc-hsx2hs-dev/armhf has unsatisfiable dependency
    • libghc-hsx2hs-prof/armhf has unsatisfiable dependency
    • libghc-hsx2hs-dev/i386 has unsatisfiable dependency
    • libghc-hsx2hs-prof/i386 has unsatisfiable dependency
    • libghc-hsx2hs-dev/mips64el has unsatisfiable dependency
    • libghc-hsx2hs-prof/mips64el has unsatisfiable dependency
    • libghc-hsx2hs-dev/ppc64el has unsatisfiable dependency
    • libghc-hsx2hs-prof/ppc64el has unsatisfiable dependency
    • libghc-hsx2hs-dev/riscv64 has unsatisfiable dependency
    • libghc-hsx2hs-prof/riscv64 has unsatisfiable dependency
    • libghc-hsx2hs-dev/s390x has unsatisfiable dependency
    • libghc-hsx2hs-prof/s390x has unsatisfiable dependency
    • Updating haskell-hsx2hs would introduce bugs in testing: #1082352
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hsx2hs.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 526 days old (needed 5 days)
• gcc-11-cross-mipsen (- to 6+c1+nmu1)
  • Migration status for gcc-11-cross-mipsen (- to 6+c1+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-11-cross-mipsen would introduce bugs in testing: #1032167, #1089256, #1089881
    • Build-Depends(-Arch): gcc-11-cross-mipsen gcc-11 (not considered)
    • Built-Using: gcc-11-cross-mipsen gcc-11 (not considered)
    • Depends: gcc-11-cross-mipsen gcc-11 (not considered)
    • Depends: gcc-11-cross-mipsen gcc-12-cross-mipsen (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11-cross-mipsen.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 528 days old (needed 5 days)
• haskell-configfile (- to 1.1.4-11)
  • Migration status for haskell-configfile (- to 1.1.4-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-configfile-dev/amd64 has unsatisfiable dependency
    • libghc-configfile-doc/amd64 has unsatisfiable dependency
    • libghc-configfile-prof/amd64 has unsatisfiable dependency
    • libghc-configfile-dev/arm64 has unsatisfiable dependency
    • libghc-configfile-doc/arm64 has unsatisfiable dependency
    • libghc-configfile-prof/arm64 has unsatisfiable dependency
    • libghc-configfile-dev/armel has unsatisfiable dependency
    • libghc-configfile-prof/armel has unsatisfiable dependency
    • libghc-configfile-dev/armhf has unsatisfiable dependency
    • libghc-configfile-prof/armhf has unsatisfiable dependency
    • libghc-configfile-dev/i386 has unsatisfiable dependency
    • libghc-configfile-prof/i386 has unsatisfiable dependency
    • libghc-configfile-dev/mips64el has unsatisfiable dependency
    • libghc-configfile-prof/mips64el has unsatisfiable dependency
    • libghc-configfile-dev/ppc64el has unsatisfiable dependency
    • libghc-configfile-prof/ppc64el has unsatisfiable dependency
    • libghc-configfile-dev/riscv64 has unsatisfiable dependency
    • libghc-configfile-prof/riscv64 has unsatisfiable dependency
    • libghc-configfile-dev/s390x has unsatisfiable dependency
    • libghc-configfile-prof/s390x has unsatisfiable dependency
    • Updating haskell-configfile would introduce bugs in testing: #1081936
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-configfile.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 528 days old (needed 5 days)
• haskell-prettyprinter-convert-ansi-wl-pprint (- to 1.1.2-2)
  • Migration status for haskell-prettyprinter-convert-ansi-wl-pprint (- to 1.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/amd64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-doc/amd64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/amd64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/arm64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-doc/arm64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/arm64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/armel has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/armel has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/armhf has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/armhf has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/i386 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/i386 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/mips64el has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/mips64el has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/ppc64el has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/ppc64el has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/riscv64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/riscv64 has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-dev/s390x has unsatisfiable dependency
    • libghc-prettyprinter-convert-ansi-wl-pprint-prof/s390x has unsatisfiable dependency
    • Updating haskell-prettyprinter-convert-ansi-wl-pprint would introduce bugs in testing: #1083255
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-prettyprinter-convert-ansi-wl-pprint.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 528 days old (needed 5 days)
• w3cam (- to 0.7.2-6.4)
  • Migration status for w3cam (- to 0.7.2-6.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating w3cam would introduce bugs in testing: #1091279
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/w3cam.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 528 days old (needed 5 days)
• haskell-lucid-svg (- to 0.7.1.1-1)
  • Migration status for haskell-lucid-svg (- to 0.7.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-lucid-svg-dev/amd64 has unsatisfiable dependency
    • libghc-lucid-svg-doc/amd64 has unsatisfiable dependency
    • libghc-lucid-svg-prof/amd64 has unsatisfiable dependency
    • libghc-lucid-svg-dev/arm64 has unsatisfiable dependency
    • libghc-lucid-svg-doc/arm64 has unsatisfiable dependency
    • libghc-lucid-svg-prof/arm64 has unsatisfiable dependency
    • libghc-lucid-svg-dev/armel has unsatisfiable dependency
    • libghc-lucid-svg-prof/armel has unsatisfiable dependency
    • libghc-lucid-svg-dev/armhf has unsatisfiable dependency
    • libghc-lucid-svg-prof/armhf has unsatisfiable dependency
    • libghc-lucid-svg-dev/i386 has unsatisfiable dependency
    • libghc-lucid-svg-prof/i386 has unsatisfiable dependency
    • libghc-lucid-svg-dev/mips64el has unsatisfiable dependency
    • libghc-lucid-svg-prof/mips64el has unsatisfiable dependency
    • libghc-lucid-svg-dev/ppc64el has unsatisfiable dependency
    • libghc-lucid-svg-prof/ppc64el has unsatisfiable dependency
    • libghc-lucid-svg-dev/riscv64 has unsatisfiable dependency
    • libghc-lucid-svg-prof/riscv64 has unsatisfiable dependency
    • libghc-lucid-svg-dev/s390x has unsatisfiable dependency
    • libghc-lucid-svg-prof/s390x has unsatisfiable dependency
    • Updating haskell-lucid-svg would introduce bugs in testing: #1082410
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-lucid-svg.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 529 days old (needed 5 days)
• haskell-monad-journal (- to 0.8.1-6)
  • Migration status for haskell-monad-journal (- to 0.8.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-monad-journal-dev/amd64 has unsatisfiable dependency
    • libghc-monad-journal-doc/amd64 has unsatisfiable dependency
    • libghc-monad-journal-prof/amd64 has unsatisfiable dependency
    • libghc-monad-journal-dev/arm64 has unsatisfiable dependency
    • libghc-monad-journal-doc/arm64 has unsatisfiable dependency
    • libghc-monad-journal-prof/arm64 has unsatisfiable dependency
    • libghc-monad-journal-dev/armel has unsatisfiable dependency
    • libghc-monad-journal-prof/armel has unsatisfiable dependency
    • libghc-monad-journal-dev/armhf has unsatisfiable dependency
    • libghc-monad-journal-prof/armhf has unsatisfiable dependency
    • libghc-monad-journal-dev/i386 has unsatisfiable dependency
    • libghc-monad-journal-prof/i386 has unsatisfiable dependency
    • libghc-monad-journal-dev/mips64el has unsatisfiable dependency
    • libghc-monad-journal-prof/mips64el has unsatisfiable dependency
    • libghc-monad-journal-dev/ppc64el has unsatisfiable dependency
    • libghc-monad-journal-prof/ppc64el has unsatisfiable dependency
    • libghc-monad-journal-dev/riscv64 has unsatisfiable dependency
    • libghc-monad-journal-prof/riscv64 has unsatisfiable dependency
    • libghc-monad-journal-dev/s390x has unsatisfiable dependency
    • libghc-monad-journal-prof/s390x has unsatisfiable dependency
    • Updating haskell-monad-journal would introduce bugs in testing: #1082411
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-monad-journal.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 529 days old (needed 5 days)
• haskell-hosc (- to 0.20-1)
  • Migration status for haskell-hosc (- to 0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hosc-doc/amd64 has unsatisfiable dependency
    • libghc-hosc-doc/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hosc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 530 days old (needed 5 days)
• haskell-gsasl (- to 0.3.7-3)
  • Migration status for haskell-gsasl (- to 0.3.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gsasl-doc/amd64 has unsatisfiable dependency
    • libghc-gsasl-doc/arm64 has unsatisfiable dependency
    • Updating haskell-gsasl would introduce bugs in testing: #1081386
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-gsasl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 531 days old (needed 5 days)
• haskell-regexpr (- to 0.5.4-17)
  • Migration status for haskell-regexpr (- to 0.5.4-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-regexpr-dev/amd64 has unsatisfiable dependency
    • libghc-regexpr-doc/amd64 has unsatisfiable dependency
    • libghc-regexpr-prof/amd64 has unsatisfiable dependency
    • libghc-regexpr-dev/arm64 has unsatisfiable dependency
    • libghc-regexpr-doc/arm64 has unsatisfiable dependency
    • libghc-regexpr-prof/arm64 has unsatisfiable dependency
    • libghc-regexpr-dev/armel has unsatisfiable dependency
    • libghc-regexpr-prof/armel has unsatisfiable dependency
    • libghc-regexpr-dev/armhf has unsatisfiable dependency
    • libghc-regexpr-prof/armhf has unsatisfiable dependency
    • libghc-regexpr-dev/i386 has unsatisfiable dependency
    • libghc-regexpr-prof/i386 has unsatisfiable dependency
    • libghc-regexpr-dev/mips64el has unsatisfiable dependency
    • libghc-regexpr-prof/mips64el has unsatisfiable dependency
    • libghc-regexpr-dev/ppc64el has unsatisfiable dependency
    • libghc-regexpr-prof/ppc64el has unsatisfiable dependency
    • libghc-regexpr-dev/riscv64 has unsatisfiable dependency
    • libghc-regexpr-prof/riscv64 has unsatisfiable dependency
    • libghc-regexpr-dev/s390x has unsatisfiable dependency
    • libghc-regexpr-prof/s390x has unsatisfiable dependency
    • Updating haskell-regexpr would introduce bugs in testing: #1082536
    • Build-Depends(-Arch): haskell-regexpr haskell-mtlparse (not considered)
    • Build-Depends-Indep: haskell-regexpr haskell-mtlparse (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-regexpr.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 531 days old (needed 5 days)
• ldap-haskell (- to 0.6.11-7)
  • Migration status for ldap-haskell (- to 0.6.11-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-ldap-doc/amd64 has unsatisfiable dependency
    • libghc-ldap-doc/arm64 has unsatisfiable dependency
    • Updating ldap-haskell would introduce bugs in testing: #1082566
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/ldap-haskell.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 531 days old (needed 5 days)
• mmh (- to 0.4-6)
  • Migration status for mmh (- to 0.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mmh would introduce bugs in testing: #1075280, #1076958
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mmh.html
    • 531 days old (needed 5 days)
• ormar (- to 0.12.2-1)
  • Migration status for ormar (- to 0.12.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ormar would introduce bugs in testing: #1066769
    • autopkgtest for ormar/0.12.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ormar aiomysql (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ormar.html
    • 531 days old (needed 5 days)
• gnome-shell-extension-vertical-overview (- to 10-2)
  • Migration status for gnome-shell-extension-vertical-overview (- to 10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnome-shell-extension-vertical-overview/amd64 has unsatisfiable dependency
    • gnome-shell-extension-vertical-overview/arm64 has unsatisfiable dependency
    • Updating gnome-shell-extension-vertical-overview would introduce bugs in testing: #1052110
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-vertical-overview.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 534 days old (needed 5 days)
• haskell-crypto-random-api (- to 0.2.0-13)
  • Migration status for haskell-crypto-random-api (- to 0.2.0-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-crypto-random-api-doc/amd64 has unsatisfiable dependency
    • libghc-crypto-random-api-doc/arm64 has unsatisfiable dependency
    • Updating haskell-crypto-random-api would introduce bugs in testing: #1082407
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-crypto-random-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 534 days old (needed 5 days)
• haskell-djinn-lib (- to 0.0.1.4-2)
  • Migration status for haskell-djinn-lib (- to 0.0.1.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-djinn-lib-doc/amd64 has unsatisfiable dependency
    • libghc-djinn-lib-doc/arm64 has unsatisfiable dependency
    • Updating haskell-djinn-lib would introduce bugs in testing: #1082344
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-djinn-lib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 534 days old (needed 5 days)
• haskell-punycode (- to 2.0-14)
  • Migration status for haskell-punycode (- to 2.0-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-punycode-dev/amd64 has unsatisfiable dependency
    • libghc-punycode-doc/amd64 has unsatisfiable dependency
    • libghc-punycode-prof/amd64 has unsatisfiable dependency
    • libghc-punycode-dev/arm64 has unsatisfiable dependency
    • libghc-punycode-doc/arm64 has unsatisfiable dependency
    • libghc-punycode-prof/arm64 has unsatisfiable dependency
    • libghc-punycode-dev/armel has unsatisfiable dependency
    • libghc-punycode-prof/armel has unsatisfiable dependency
    • libghc-punycode-dev/armhf has unsatisfiable dependency
    • libghc-punycode-prof/armhf has unsatisfiable dependency
    • libghc-punycode-dev/i386 has unsatisfiable dependency
    • libghc-punycode-prof/i386 has unsatisfiable dependency
    • libghc-punycode-dev/mips64el has unsatisfiable dependency
    • libghc-punycode-prof/mips64el has unsatisfiable dependency
    • libghc-punycode-dev/ppc64el has unsatisfiable dependency
    • libghc-punycode-prof/ppc64el has unsatisfiable dependency
    • libghc-punycode-dev/riscv64 has unsatisfiable dependency
    • libghc-punycode-prof/riscv64 has unsatisfiable dependency
    • libghc-punycode-dev/s390x has unsatisfiable dependency
    • libghc-punycode-prof/s390x has unsatisfiable dependency
    • Updating haskell-punycode would introduce bugs in testing: #1082009
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-punycode.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 534 days old (needed 5 days)
• mia (- to 2.4.7-13)
  • Migration status for mia (- to 2.4.7-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libmia-2.4-4/amd64 has unsatisfiable dependency
    • mia-tools/amd64 has unsatisfiable dependency
    • libmia-2.4-4/arm64 has unsatisfiable dependency
    • mia-tools/arm64 has unsatisfiable dependency
    • libmia-2.4-4/armel has unsatisfiable dependency
    • mia-tools/armel has unsatisfiable dependency
    • libmia-2.4-4/armhf has unsatisfiable dependency
    • mia-tools/armhf has unsatisfiable dependency
    • libmia-2.4-4/i386 has unsatisfiable dependency
    • mia-tools/i386 has unsatisfiable dependency
    • libmia-2.4-4/mips64el has unsatisfiable dependency
    • mia-tools/mips64el has unsatisfiable dependency
    • libmia-2.4-4/ppc64el has unsatisfiable dependency
    • mia-tools/ppc64el has unsatisfiable dependency
    • libmia-2.4-4/riscv64 has unsatisfiable dependency
    • mia-tools/riscv64 has unsatisfiable dependency
    • libmia-2.4-4/s390x has unsatisfiable dependency
    • mia-tools/s390x has unsatisfiable dependency
    • Updating mia would introduce bugs in testing: #1075270
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mia.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 534 days old (needed 5 days)
• haskell-generic-trie (- to 0.3.2-1)
  • Migration status for haskell-generic-trie (- to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-generic-trie-dev/amd64 has unsatisfiable dependency
    • libghc-generic-trie-doc/amd64 has unsatisfiable dependency
    • libghc-generic-trie-prof/amd64 has unsatisfiable dependency
    • libghc-generic-trie-dev/arm64 has unsatisfiable dependency
    • libghc-generic-trie-doc/arm64 has unsatisfiable dependency
    • libghc-generic-trie-prof/arm64 has unsatisfiable dependency
    • libghc-generic-trie-dev/armel has unsatisfiable dependency
    • libghc-generic-trie-prof/armel has unsatisfiable dependency
    • libghc-generic-trie-dev/armhf has unsatisfiable dependency
    • libghc-generic-trie-prof/armhf has unsatisfiable dependency
    • libghc-generic-trie-dev/i386 has unsatisfiable dependency
    • libghc-generic-trie-prof/i386 has unsatisfiable dependency
    • libghc-generic-trie-dev/mips64el has unsatisfiable dependency
    • libghc-generic-trie-prof/mips64el has unsatisfiable dependency
    • libghc-generic-trie-dev/ppc64el has unsatisfiable dependency
    • libghc-generic-trie-prof/ppc64el has unsatisfiable dependency
    • libghc-generic-trie-dev/riscv64 has unsatisfiable dependency
    • libghc-generic-trie-prof/riscv64 has unsatisfiable dependency
    • libghc-generic-trie-dev/s390x has unsatisfiable dependency
    • libghc-generic-trie-prof/s390x has unsatisfiable dependency
    • Updating haskell-generic-trie would introduce bugs in testing: #1082348
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-generic-trie.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 535 days old (needed 5 days)
• haskell-geniplate-mirror (- to 0.7.9-1)
  • Migration status for haskell-geniplate-mirror (- to 0.7.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-geniplate-mirror-dev/amd64 has unsatisfiable dependency
    • libghc-geniplate-mirror-doc/amd64 has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/amd64 has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/arm64 has unsatisfiable dependency
    • libghc-geniplate-mirror-doc/arm64 has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/arm64 has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/armel has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/armel has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/armhf has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/armhf has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/i386 has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/i386 has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/mips64el has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/mips64el has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/ppc64el has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/ppc64el has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/riscv64 has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/riscv64 has unsatisfiable dependency
    • libghc-geniplate-mirror-dev/s390x has unsatisfiable dependency
    • libghc-geniplate-mirror-prof/s390x has unsatisfiable dependency
    • Updating haskell-geniplate-mirror would introduce bugs in testing: #1082349
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-geniplate-mirror.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 535 days old (needed 5 days)
• haskell-harp (- to 0.4.3.6-1)
  • Migration status for haskell-harp (- to 0.4.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-harp-dev/amd64 has unsatisfiable dependency
    • libghc-harp-doc/amd64 has unsatisfiable dependency
    • libghc-harp-prof/amd64 has unsatisfiable dependency
    • libghc-harp-dev/arm64 has unsatisfiable dependency
    • libghc-harp-doc/arm64 has unsatisfiable dependency
    • libghc-harp-prof/arm64 has unsatisfiable dependency
    • libghc-harp-dev/armel has unsatisfiable dependency
    • libghc-harp-prof/armel has unsatisfiable dependency
    • libghc-harp-dev/armhf has unsatisfiable dependency
    • libghc-harp-prof/armhf has unsatisfiable dependency
    • libghc-harp-dev/i386 has unsatisfiable dependency
    • libghc-harp-prof/i386 has unsatisfiable dependency
    • libghc-harp-dev/mips64el has unsatisfiable dependency
    • libghc-harp-prof/mips64el has unsatisfiable dependency
    • libghc-harp-dev/ppc64el has unsatisfiable dependency
    • libghc-harp-prof/ppc64el has unsatisfiable dependency
    • libghc-harp-dev/riscv64 has unsatisfiable dependency
    • libghc-harp-prof/riscv64 has unsatisfiable dependency
    • libghc-harp-dev/s390x has unsatisfiable dependency
    • libghc-harp-prof/s390x has unsatisfiable dependency
    • Updating haskell-harp would introduce bugs in testing: #1082350
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-harp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 535 days old (needed 5 days)
• worker (- to 4.12.1-1)
  • Migration status for worker (- to 4.12.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): worker avfs (not considered)
    • Depends: worker avfs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/worker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 535 days old (needed 5 days)
• haskell-bool-extras (- to 0.4.0-11)
  • Migration status for haskell-bool-extras (- to 0.4.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-bool-extras-doc/amd64 has unsatisfiable dependency
    • libghc-bool-extras-doc/arm64 has unsatisfiable dependency
    • Updating haskell-bool-extras would introduce bugs in testing: #1082343
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-bool-extras.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 536 days old (needed 5 days)
• haskell-failure (- to 0.2.0.3-12)
  • Migration status for haskell-failure (- to 0.2.0.3-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-failure-dev/amd64 has unsatisfiable dependency
    • libghc-failure-doc/amd64 has unsatisfiable dependency
    • libghc-failure-prof/amd64 has unsatisfiable dependency
    • libghc-failure-dev/arm64 has unsatisfiable dependency
    • libghc-failure-doc/arm64 has unsatisfiable dependency
    • libghc-failure-prof/arm64 has unsatisfiable dependency
    • libghc-failure-dev/armel has unsatisfiable dependency
    • libghc-failure-prof/armel has unsatisfiable dependency
    • libghc-failure-dev/armhf has unsatisfiable dependency
    • libghc-failure-prof/armhf has unsatisfiable dependency
    • libghc-failure-dev/i386 has unsatisfiable dependency
    • libghc-failure-prof/i386 has unsatisfiable dependency
    • libghc-failure-dev/mips64el has unsatisfiable dependency
    • libghc-failure-prof/mips64el has unsatisfiable dependency
    • libghc-failure-dev/ppc64el has unsatisfiable dependency
    • libghc-failure-prof/ppc64el has unsatisfiable dependency
    • libghc-failure-dev/riscv64 has unsatisfiable dependency
    • libghc-failure-prof/riscv64 has unsatisfiable dependency
    • libghc-failure-dev/s390x has unsatisfiable dependency
    • libghc-failure-prof/s390x has unsatisfiable dependency
    • Updating haskell-failure would introduce bugs in testing: #1082347
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-failure.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 536 days old (needed 5 days)
• haskell-hsp (- to 0.10.0-11)
  • Migration status for haskell-hsp (- to 0.10.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hsp-dev/amd64 has unsatisfiable dependency
    • libghc-hsp-doc/amd64 has unsatisfiable dependency
    • libghc-hsp-prof/amd64 has unsatisfiable dependency
    • libghc-hsp-dev/arm64 has unsatisfiable dependency
    • libghc-hsp-doc/arm64 has unsatisfiable dependency
    • libghc-hsp-prof/arm64 has unsatisfiable dependency
    • libghc-hsp-dev/armel has unsatisfiable dependency
    • libghc-hsp-prof/armel has unsatisfiable dependency
    • libghc-hsp-dev/armhf has unsatisfiable dependency
    • libghc-hsp-prof/armhf has unsatisfiable dependency
    • libghc-hsp-dev/i386 has unsatisfiable dependency
    • libghc-hsp-prof/i386 has unsatisfiable dependency
    • libghc-hsp-dev/mips64el has unsatisfiable dependency
    • libghc-hsp-prof/mips64el has unsatisfiable dependency
    • libghc-hsp-dev/ppc64el has unsatisfiable dependency
    • libghc-hsp-prof/ppc64el has unsatisfiable dependency
    • libghc-hsp-dev/riscv64 has unsatisfiable dependency
    • libghc-hsp-prof/riscv64 has unsatisfiable dependency
    • libghc-hsp-dev/s390x has unsatisfiable dependency
    • libghc-hsp-prof/s390x has unsatisfiable dependency
    • Updating haskell-hsp would introduce bugs in testing: #1082353
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hsp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 536 days old (needed 5 days)
• haskell-mime (- to 0.4.0.2-10)
  • Migration status for haskell-mime (- to 0.4.0.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-mime-doc/amd64 has unsatisfiable dependency
    • libghc-mime-doc/arm64 has unsatisfiable dependency
    • Updating haskell-mime would introduce bugs in testing: #1082534
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-mime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 536 days old (needed 5 days)
• haskell-mtlparse (- to 0.1.4.0-12)
  • Migration status for haskell-mtlparse (- to 0.1.4.0-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-mtlparse-doc/amd64 has unsatisfiable dependency
    • libghc-mtlparse-doc/arm64 has unsatisfiable dependency
    • Updating haskell-mtlparse would introduce bugs in testing: #1082535
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-mtlparse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 536 days old (needed 5 days)
• haskell-qrencode (- to 1.0.4-13)
  • Migration status for haskell-qrencode (- to 1.0.4-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-qrencode-doc/amd64 has unsatisfiable dependency
    • libghc-qrencode-doc/arm64 has unsatisfiable dependency
    • Updating haskell-qrencode would introduce bugs in testing: #1082563
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-qrencode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 536 days old (needed 5 days)
• haskell-readline (- to 1.0.3.0-13)
  • Migration status for haskell-readline (- to 1.0.3.0-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-readline-doc/amd64 has unsatisfiable dependency
    • libghc-readline-doc/arm64 has unsatisfiable dependency
    • Updating haskell-readline would introduce bugs in testing: #1082564
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-readline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 536 days old (needed 5 days)
• haskell-tagshare (- to 0.0-7)
  • Migration status for haskell-tagshare (- to 0.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-tagshare-dev/amd64 has unsatisfiable dependency
    • libghc-tagshare-doc/amd64 has unsatisfiable dependency
    • libghc-tagshare-prof/amd64 has unsatisfiable dependency
    • libghc-tagshare-dev/arm64 has unsatisfiable dependency
    • libghc-tagshare-doc/arm64 has unsatisfiable dependency
    • libghc-tagshare-prof/arm64 has unsatisfiable dependency
    • libghc-tagshare-dev/armel has unsatisfiable dependency
    • libghc-tagshare-prof/armel has unsatisfiable dependency
    • libghc-tagshare-dev/armhf has unsatisfiable dependency
    • libghc-tagshare-prof/armhf has unsatisfiable dependency
    • libghc-tagshare-dev/i386 has unsatisfiable dependency
    • libghc-tagshare-prof/i386 has unsatisfiable dependency
    • libghc-tagshare-dev/mips64el has unsatisfiable dependency
    • libghc-tagshare-prof/mips64el has unsatisfiable dependency
    • libghc-tagshare-dev/ppc64el has unsatisfiable dependency
    • libghc-tagshare-prof/ppc64el has unsatisfiable dependency
    • libghc-tagshare-dev/riscv64 has unsatisfiable dependency
    • libghc-tagshare-prof/riscv64 has unsatisfiable dependency
    • libghc-tagshare-dev/s390x has unsatisfiable dependency
    • libghc-tagshare-prof/s390x has unsatisfiable dependency
    • Updating haskell-tagshare would introduce bugs in testing: #1082565
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-tagshare.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 536 days old (needed 5 days)
• bind-dyndb-ldap (- to 11.10-6)
  • Migration status for bind-dyndb-ldap (- to 11.10-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bind9-dyndb-ldap/amd64 has unsatisfiable dependency
    • bind9-dyndb-ldap/arm64 has unsatisfiable dependency
    • bind9-dyndb-ldap/armel has unsatisfiable dependency
    • bind9-dyndb-ldap/armhf has unsatisfiable dependency
    • bind9-dyndb-ldap/i386 has unsatisfiable dependency
    • bind9-dyndb-ldap/mips64el has unsatisfiable dependency
    • bind9-dyndb-ldap/ppc64el has unsatisfiable dependency
    • bind9-dyndb-ldap/riscv64 has unsatisfiable dependency
    • bind9-dyndb-ldap/s390x has unsatisfiable dependency
    • Updating bind-dyndb-ldap would introduce bugs in testing: #1064294
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bind-dyndb-ldap.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 539 days old (needed 5 days)
• gosa-plugins-sudo (- to 2.8~git20211022.7ff3ed2-3)
  • Migration status for gosa-plugins-sudo (- to 2.8~git20211022.7ff3ed2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: gosa-plugins-sudo gosa (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-sudo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 539 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• shapetools-tutorial (- to 1.3-6)
  • Migration status for shapetools-tutorial (- to 1.3-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: shapetools-tutorial shapetools (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 539 days old (needed 5 days)
• freebayes (- to 1.3.7-1)
  • Migration status for freebayes (- to 1.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freebayes would introduce bugs in testing: #1067271
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freebayes.html
    • autopkgtest for freebayes/1.3.7-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 542 days old (needed 2 days)
• modem-manager-gui (- to 0.0.20-6)
  • Migration status for modem-manager-gui (- to 0.0.20-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): modem-manager-gui ofono (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/modem-manager-gui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 544 days old (needed 5 days)
• totalopenstation (- to 0.5.2-4)
  • Migration status for totalopenstation (- to 0.5.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating totalopenstation would introduce bugs in testing: #1069074
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/totalopenstation.html
    • 544 days old (needed 5 days)
• python-oauth2client (- to 4.1.3-5)
  • Migration status for python-oauth2client (- to 4.1.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-oauth2client would introduce bugs in testing: #1058392, #1066132
    • autopkgtest for python-oauth2client/4.1.3-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends-Indep: python-oauth2client unittest2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-oauth2client.html
    • 545 days old (needed 5 days)
• go-cve-dictionary (- to 0.3.1-5)
  • Migration status for go-cve-dictionary (- to 0.3.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating go-cve-dictionary would introduce bugs in testing: #1085476
    • 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)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-cve-dictionary.html
    • autopkgtest for go-cve-dictionary/0.3.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 546 days old (needed 2 days)
• gost (- to 0.1.2-2)
  • Migration status for gost (- to 0.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gost would introduce bugs in testing: #1085479
    • 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)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gost.html
    • autopkgtest for gost/0.1.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 546 days old (needed 2 days)
• goval-dictionary (- to 0.2.0-6)
  • Migration status for goval-dictionary (- to 0.2.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating goval-dictionary would introduce bugs in testing: #1085471
    • 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)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goval-dictionary.html
    • autopkgtest for goval-dictionary/0.2.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 546 days old (needed 2 days)
• go-exploitdb (- to 0.0~git20181130.7c961e7-3)
  • Migration status for go-exploitdb (- to 0.0~git20181130.7c961e7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating go-exploitdb would introduce bugs in testing: #1085478
    • 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)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-exploitdb.html
    • autopkgtest for go-exploitdb/0.0~git20181130.7c961e7-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 547 days old (needed 2 days)
• redmine-plugin-local-avatars (- to 1.0.6-1)
  • Migration status for redmine-plugin-local-avatars (- to 1.0.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-local-avatars redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redmine-plugin-local-avatars.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 547 days old (needed 5 days)
• redmine-plugin-pretend (- to 1.0-2)
  • Migration status for redmine-plugin-pretend (- to 1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-pretend redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redmine-plugin-pretend.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 547 days old (needed 5 days)
• libengine-gost-openssl (- to 3.0.2-1)
  • Migration status for libengine-gost-openssl (- to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gostsum/armel has unsatisfiable dependency
    • libengine-gost-openssl/armel has unsatisfiable dependency
    • gostsum/armhf has unsatisfiable dependency
    • libengine-gost-openssl/armhf has unsatisfiable dependency
    • Updating libengine-gost-openssl would introduce bugs in testing: #1054922
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libengine-gost-openssl.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 548 days old (needed 5 days)
• xemacs21 (- to 21.4.24-12)
  • Migration status for xemacs21 (- to 21.4.24-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xemacs21 would introduce bugs in testing: #1075659, #1095538
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/amd64
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/arm64
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/armel
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/armhf
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/i386
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/mips64el
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/ppc64el
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/riscv64
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/s390x
    • Build-Depends(-Arch): xemacs21 autoconf2.13 (not considered)
    • Depends: xemacs21 xemacs21-packages
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xemacs21.html
    • 548 days old (needed 5 days)
• pseudo (- to 1.9.0+git20230301+ec6151a2b057-1)
  • Migration status for pseudo (- to 1.9.0+git20230301+ec6151a2b057-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pseudo would introduce bugs in testing: #1069487
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pseudo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 549 days old (needed 5 days)
• searx (- to 1.1.0+dfsg1-2)
  • Migration status for searx (- to 1.1.0+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating searx would introduce bugs in testing: #1051510
    • autopkgtest for searx/1.1.0+dfsg1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/searx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 549 days old (needed 5 days)
• arduino (- to 2:1.8.19+dfsg1-2)
  • Migration status for arduino (- to 2:1.8.19+dfsg1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: arduino arduino-core-avr (not considered)
    • Invalidated by dependency
    • Depends: arduino arduino-builder (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arduino.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 551 days old (needed 5 days)
• tomcatjss (- to 8.4.0-2)
  • Migration status for tomcatjss (- to 8.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomcatjss would introduce bugs in testing: #1031816
    • Build-Depends(-Arch): tomcatjss jss (not considered)
    • Depends: tomcatjss jss (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomcatjss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 552 days old (needed 5 days)
• rheolef (- to 7.2-3)
  • Migration status for rheolef (- to 7.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librheolef1/i386 has unsatisfiable dependency
    • rheolef/i386 has unsatisfiable dependency
    • Updating rheolef would introduce bugs in testing: #1084831
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rheolef.html
    • uninstallable on arch i386, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 554 days old (needed 5 days)
• rmlint (- to 2.9.0-2.5)
  • Migration status for rmlint (- to 2.9.0-2.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rmlint/armel has unsatisfiable dependency
    • rmlint/armhf has unsatisfiable dependency
    • Updating rmlint would introduce bugs in testing: #1018616, #1065947
    • autopkgtest for rmlint/2.9.0-2.5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rmlint.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 555 days old (needed 5 days)
• ddnet (- to 16.4-1.2)
  • Migration status for ddnet (- to 16.4-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ddnet/amd64 has unsatisfiable dependency
    • ddnet/arm64 has unsatisfiable dependency
    • ddnet/armel has unsatisfiable dependency
    • ddnet/armhf has unsatisfiable dependency
    • ddnet/i386 has unsatisfiable dependency
    • ddnet/mips64el has unsatisfiable dependency
    • ddnet/ppc64el has unsatisfiable dependency
    • ddnet/riscv64 has unsatisfiable dependency
    • Updating ddnet would introduce bugs in testing: #1072409
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/ddnet.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • 557 days old (needed 5 days)
• chkservice (- to 0.3-1.1)
  • Migration status for chkservice (- to 0.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chkservice would introduce bugs in testing: #988094
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chkservice.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 558 days old (needed 5 days)
• linphone-desktop (- to 5.0.2-4)
  • Migration status for linphone-desktop (- to 5.0.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating linphone-desktop would introduce bugs in testing: #1094089
    • Build-Depends(-Arch): linphone-desktop linphone (not considered)
    • Depends: linphone-desktop linphone (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linphone-desktop.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 564 days old (needed 5 days)
• sptag (- to 0.0~git20230612.2ffaec6+ds-4)
  • Migration status for sptag (- to 0.0~git20230612.2ffaec6+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sptag would introduce bugs in testing: #1091119
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sptag.html
    • autopkgtest for sptag/0.0~git20230612.2ffaec6+ds-4: amd64: No tests, superficial or marked flaky ♻
    • 567 days old (needed 5 days)
• openmw (- to 0.48.0-1)
  • Migration status for openmw (- to 0.48.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openmw/amd64 has unsatisfiable dependency
    • openmw/arm64 has unsatisfiable dependency
    • openmw/armel has unsatisfiable dependency
    • openmw/armhf has unsatisfiable dependency
    • openmw/i386 has unsatisfiable dependency
    • openmw/mips64el has unsatisfiable dependency
    • openmw/s390x has unsatisfiable dependency
    • Updating openmw would introduce bugs in testing: #1072443, #1075344
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmw.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 572 days old (needed 5 days)
• openjdk-20 (- to 20.0.2+9-1)
  • Migration status for openjdk-20 (- to 20.0.2+9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openjdk-20-jre/armel has unsatisfiable dependency
    • openjdk-20-jre-headless/armel has unsatisfiable dependency
    • openjdk-20-jre/armhf has unsatisfiable dependency
    • openjdk-20-jre-headless/armhf has unsatisfiable dependency
    • Updating openjdk-20 would introduce bugs in testing: #1031889, #1069315
    • openjdk-20 unsatisfiable Build-Depends(-Arch) on armel: libgtk2.0-0 | libgtk-3-0
    • openjdk-20 unsatisfiable Build-Depends(-Arch) on armhf: libgtk2.0-0 | libgtk-3-0
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
    • autopkgtest for openjdk-20/20.0.2+9-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-20.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 573 days old (needed 5 days)
• python-tinyrpc (- to 0.6-5)
  • Migration status for python-tinyrpc (- to 0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-tinyrpc would introduce bugs in testing: #1084578, #1090165
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-tinyrpc.html
    • autopkgtest for python-tinyrpc/0.6-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on i386 - info ♻
    • 573 days old (needed 5 days)
• debian-parl (- to 1.9.31+nmu1)
  • Migration status for debian-parl (- to 1.9.31+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debian-parl would introduce bugs in testing: #1081075
    • debian-parl unsatisfiable Build-Depends(-Arch) on amd64: boxer-data (<< 10.10)
    • Depends: debian-parl parcimonie (not considered)
    • Depends: debian-parl syncevolution
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-parl.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 575 days old (needed 5 days)
• iem-plugin-suite (- to 1.14.1-1)
  • Migration status for iem-plugin-suite (- to 1.14.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iem-plugin-suite would introduce bugs in testing: #1078519
    • iem-plugin-suite unsatisfiable Build-Depends(-Arch) on mips64el: juce-modules-source (>= 7.0.2~)
    • Build-Depends(-Arch): iem-plugin-suite juce
    • Built-Using: iem-plugin-suite juce
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iem-plugin-suite.html
    • 576 days old (needed 5 days)
• renderdoc (- to 1.27+dfsg-1)
  • Migration status for renderdoc (- to 1.27+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • qrenderdoc/amd64 has unsatisfiable dependency
    • Updating renderdoc would introduce bugs in testing: #1067012, #999924
    • renderdoc unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • 579 days old (needed 5 days)
• rust-packed-simd (- to 0.3.8-1)
  • Migration status for rust-packed-simd (- to 0.3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-packed-simd would introduce bugs in testing: #1077952
    • autopkgtest for rust-packed-simd/0.3.8-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-packed-simd.html
    • 579 days old (needed 5 days)
• barrier (- to 2.4.0+dfsg-4)
  • Migration status for barrier (- to 2.4.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating barrier would introduce bugs in testing: #1057544
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/barrier.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 580 days old (needed 5 days)
• ruby-appraiser-rubocop (- to 1.0.1-2)
  • Migration status for ruby-appraiser-rubocop (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-appraiser-rubocop/amd64 has unsatisfiable dependency
    • ruby-appraiser-rubocop/arm64 has unsatisfiable dependency
    • Updating ruby-appraiser-rubocop would introduce bugs in testing: #1054166
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-appraiser-rubocop.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 580 days old (needed 5 days)
• vspline (- to 1.1.7-1)
  • Migration status for vspline (- to 1.1.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: vspline libvigraimpex (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vspline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 580 days old (needed 5 days)
• appdirs (- to 1.4.4-4)
  • Migration status for appdirs (- to 1.4.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating appdirs would introduce bugs in testing: #1060427
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appdirs.html
    • autopkgtest for appdirs/1.4.4-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 581 days old (needed 2 days)
• ruby-prometheus-client-mmap (- to 0.23.1-3)
  • Migration status for ruby-prometheus-client-mmap (- to 0.23.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-prometheus-client-mmap would introduce bugs in testing: #1075473
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-prometheus-client-mmap.html
    • autopkgtest for ruby-prometheus-client-mmap/0.23.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 581 days old (needed 2 days)
• kanboard (- to 1.2.31+ds2-1)
  • Migration status for kanboard (- to 1.2.31+ds2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kanboard would introduce bugs in testing: #1051989, #1052638, #1072791, #1079245, #1088798
    • autopkgtest for kanboard/1.2.31+ds2-1: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
    • Build-Depends(-Arch): kanboard christianriesen-otp
    • Build-Depends(-Arch): kanboard libphp-swiftmailer (not considered)
    • Build-Depends(-Arch): kanboard matthiasmullie-minify
    • Depends: kanboard christianriesen-otp
    • Depends: kanboard libphp-swiftmailer (not considered)
    • Depends: kanboard matthiasmullie-minify
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kanboard.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 585 days old (needed 5 days)
• ruby-rails-assets-jquery (- to 3.5.1+dfsg-2)
  • Migration status for ruby-rails-assets-jquery (- to 3.5.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-jquery would introduce bugs in testing: #1094741
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-jquery.html
    • autopkgtest for ruby-rails-assets-jquery/3.5.1+dfsg-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 586 days old (needed 5 days)
• php-gettext (- to 1.0.12-6)
  • Migration status for php-gettext (- to 1.0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-gettext would introduce bugs in testing: #1092095
    • autopkgtest for php-gettext/1.0.12-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-gettext.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 590 days old (needed 5 days)
• printrun (- to 2.0.1-1)
  • Migration status for printrun (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating printrun would introduce bugs in testing: #1050157, #1067982
    • Depends: printrun appdirs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/printrun.html
    • autopkgtest for printrun/2.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 591 days old (needed 2 days)
• fdm (- to 1.9+git20181219-1.1)
  • Migration status for fdm (- to 1.9+git20181219-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fdm would introduce bugs in testing: #1074950
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fdm.html
    • 592 days old (needed 5 days)
• x2gokdriveclient (- to 0.0.0.1-1)
  • Migration status for x2gokdriveclient (- to 0.0.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating x2gokdriveclient would introduce bugs in testing: #1089278
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/x2gokdriveclient.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 597 days old (needed 5 days)
• r-cran-maotai (- to 0.2.5-1)
  • Migration status for r-cran-maotai (- to 0.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): r-cran-maotai r-cran-fastcluster (not considered)
    • Depends: r-cran-maotai r-cran-fastcluster (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-maotai.html
    • autopkgtest for r-cran-maotai/0.2.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 599 days old (needed 2 days)
• foxtrotgps (- to 1.2.2+bzr332-1)
  • Migration status for foxtrotgps (- to 1.2.2+bzr332-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating foxtrotgps would introduce bugs in testing: #967861
    • Build-Depends(-Arch): foxtrotgps libglade2 (not considered)
    • Depends: foxtrotgps libglade2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foxtrotgps.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 600 days old (needed 5 days)
• gost-crypto (- to 0.3.5-1)
  • Migration status for gost-crypto (- to 0.3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gost-crypto would introduce bugs in testing: #1089497
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gost-crypto.html
    • autopkgtest for gost-crypto/0.3.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 600 days old (needed 5 days)
• golang-github-form3tech-oss-jwt-go (- to 3.2.3-2)
  • Migration status for golang-github-form3tech-oss-jwt-go (- to 3.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-form3tech-oss-jwt-go would introduce bugs in testing: #1038793, #1042736
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-form3tech-oss-jwt-go.html
    • autopkgtest for golang-github-form3tech-oss-jwt-go/3.2.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 603 days old (needed 2 days)
• xserver-xorg-video-qxl (- to 0.1.6-1)
  • Migration status for xserver-xorg-video-qxl (- to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-qxl would introduce bugs in testing: #1089484
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-qxl.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 603 days old (needed 5 days)
• gosa-plugins-netgroups (- to 2.8~git20211022.3b6449d-5)
  • Migration status for gosa-plugins-netgroups (- to 2.8~git20211022.3b6449d-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: gosa-plugins-netgroups gosa (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-netgroups.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 604 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• python-django-ical (- to 1.9.2-1)
  • Migration status for python-django-ical (- to 1.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-ical would introduce bugs in testing: #1052796
    • autopkgtest for python-django-ical/1.9.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-ical.html
    • 604 days old (needed 5 days)
• libapache2-mod-qos (- to 11.74-1)
  • Migration status for libapache2-mod-qos (- to 11.74-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-qos would introduce bugs in testing: #1075142
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-qos.html
    • 605 days old (needed 5 days)
• liboqs (- to 0.8.0-1)
  • Migration status for liboqs (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liboqs3/armel has unsatisfiable dependency
    • liboqs3/armhf has unsatisfiable dependency
    • Updating liboqs would introduce bugs in testing: #1000303, #1065802, #1073250, #1089185
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/liboqs.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 608 days old (needed 5 days)
• ipmctl (- to 03.00.00.0485-1)
  • Migration status for ipmctl (- to 03.00.00.0485-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ipmctl would introduce bugs in testing: #1084577
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ipmctl.html
    • Reproducible on amd64 - info ♻
    • 611 days old (needed 5 days)
• wmdate (- to 0.7-4.2)
  • Migration status for wmdate (- to 0.7-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wmdate would introduce bugs in testing: #1075642
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wmdate.html
    • 637 days old (needed 5 days)
• mac-fdisk (- to 0.1-18.1)
  • Migration status for mac-fdisk (- to 0.1-18.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mac-fdisk would introduce bugs in testing: #1091564
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 638 days old (needed 5 days)
• php-horde-mime-viewer (- to 2.2.4+debian0-2)
  • Migration status for php-horde-mime-viewer (- to 2.2.4+debian0-2): 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-mime (not considered)
    • Invalidated by dependency
    • Depends: php-horde-mime-viewer php-horde-compress (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mime-viewer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 638 days old (needed 5 days)
• wmmatrix (- to 0.2-12.2)
  • Migration status for wmmatrix (- to 0.2-12.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wmmatrix would introduce bugs in testing: #1066282
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wmmatrix.html
    • 639 days old (needed 5 days)
• ogmrip (- to 1.0.1-4)
  • Migration status for ogmrip (- to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ogmrip/amd64 has unsatisfiable dependency
    • ogmrip/arm64 has unsatisfiable dependency
    • ogmrip/armel has unsatisfiable dependency
    • ogmrip/armhf has unsatisfiable dependency
    • ogmrip/i386 has unsatisfiable dependency
    • ogmrip/mips64el has unsatisfiable dependency
    • ogmrip/ppc64el has unsatisfiable dependency
    • ogmrip/riscv64 has unsatisfiable dependency
    • ogmrip/s390x has unsatisfiable dependency
    • Updating ogmrip would introduce bugs in testing: #1074275
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/ogmrip.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 640 days old (needed 5 days)
• tuxmath (- to 2.0.3-9)
  • Migration status for tuxmath (- to 2.0.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tuxmath would introduce bugs in testing: #1075591
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tuxmath.html
    • 642 days old (needed 5 days)
• mate-equake-applet (- to 1.3.8.2-1.1)
  • Migration status for mate-equake-applet (- to 1.3.8.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mate-equake-applet/armel has unsatisfiable dependency
    • mate-equake-applet/armhf has unsatisfiable dependency
    • Updating mate-equake-applet would introduce bugs in testing: #1066183
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-equake-applet.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 646 days old (needed 5 days)
• regina-normal (- to 7.3-2)
  • Migration status for regina-normal (- to 7.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • regina-normal/amd64 has unsatisfiable dependency
    • regina-normal/arm64 has unsatisfiable dependency
    • regina-normal/armel has unsatisfiable dependency
    • regina-normal/armhf has unsatisfiable dependency
    • regina-normal/i386 has unsatisfiable dependency
    • regina-normal/mips64el has unsatisfiable dependency
    • regina-normal/ppc64el has unsatisfiable dependency
    • regina-normal/s390x has unsatisfiable dependency
    • Updating regina-normal would introduce bugs in testing: #1037840
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/regina-normal.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 650 days old (needed 5 days)
• terminus (- to 2.3.1-1)
  • Migration status for terminus (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating terminus would introduce bugs in testing: #1075562
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/terminus.html
    • 656 days old (needed 5 days)
• zstd-jni-java (- to 1.5.2-5+ds-3)
  • Migration status for zstd-jni-java (- to 1.5.2-5+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zstd-jni-java would introduce bugs in testing: #1086252
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zstd-jni-java.html
    • autopkgtest for zstd-jni-java/1.5.2-5+ds-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 676 days old (needed 2 days)
• ponyorm (- to 0.7.16+ds-3)
  • Migration status for ponyorm (- to 0.7.16+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ponyorm would introduce bugs in testing: #1056435
    • autopkgtest for ponyorm/0.7.16+ds-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ponyorm.html
    • 677 days old (needed 5 days)
• ocrfeeder (- to 0.8.5-1)
  • Migration status for ocrfeeder (- to 0.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ocrfeeder would introduce bugs in testing: #1074646, #1084529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocrfeeder.html
    • 690 days old (needed 5 days)
• gitlab-ci-multi-runner (- to 14.10.1-1)
  • Migration status for gitlab-ci-multi-runner (- to 14.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab-ci-multi-runner would introduce bugs in testing: #1080062, #1086672
    • gitlab-runner/amd64 has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/arm64 has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/mips64el has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/ppc64el has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/s390x has unsatisfiable Built-Using on golang-1.19 1.19.6-2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-ci-multi-runner.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 693 days old (needed 5 days)
• lsh-utils (- to 2.1-14)
  • Migration status for lsh-utils (- to 2.1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lsh-client/armel has unsatisfiable dependency
    • lsh-server/armel has unsatisfiable dependency
    • lsh-utils/armel has unsatisfiable dependency
    • lsh-client/armhf has unsatisfiable dependency
    • lsh-server/armhf has unsatisfiable dependency
    • lsh-utils/armhf has unsatisfiable dependency
    • Updating lsh-utils would introduce bugs in testing: #1067313
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsh-utils.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 703 days old (needed 5 days)
• php-horde-kolab-storage (- to 2.2.4-5)
  • Migration status for php-horde-kolab-storage (- to 2.2.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-kolab-storage/2.2.4-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-kolab-storage php-horde-mime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-storage.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 703 days old (needed 5 days)
• searx-admin (- to 0.0~git20170823.95fe63b+ds-3)
  • Migration status for searx-admin (- to 0.0~git20170823.95fe63b+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for searx-admin/0.0~git20170823.95fe63b+ds-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: searx-admin searx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/searx-admin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 705 days old (needed 5 days)
• aiomysql (- to 0.1.1-2)
  • Migration status for aiomysql (- to 0.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aiomysql would introduce bugs in testing: #1087781
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiomysql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 708 days old (needed 5 days)
• ganeti (- to 3.0.2-3)
  • Migration status for ganeti (- to 3.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ganeti-haskell-3.0/amd64 has unsatisfiable dependency
    • ganeti-htools-3.0/amd64 has unsatisfiable dependency
    • ganeti-haskell-3.0/arm64 has unsatisfiable dependency
    • ganeti-htools-3.0/arm64 has unsatisfiable dependency
    • ganeti-haskell-3.0/armel has unsatisfiable dependency
    • ganeti-htools-3.0/armel has unsatisfiable dependency
    • ganeti-haskell-3.0/armhf has unsatisfiable dependency
    • ganeti-htools-3.0/armhf has unsatisfiable dependency
    • ganeti-haskell-3.0/i386 has unsatisfiable dependency
    • ganeti-htools-3.0/i386 has unsatisfiable dependency
    • ganeti-haskell-3.0/mips64el has unsatisfiable dependency
    • ganeti-htools-3.0/mips64el has unsatisfiable dependency
    • ganeti-haskell-3.0/ppc64el has unsatisfiable dependency
    • ganeti-htools-3.0/ppc64el has unsatisfiable dependency
    • ganeti-haskell-3.0/s390x has unsatisfiable dependency
    • ganeti-htools-3.0/s390x has unsatisfiable dependency
    • Updating ganeti would introduce bugs in testing: #1042264
    • Build-Depends(-Arch): ganeti haskell-regex-pcre (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganeti.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on arm64 - info ♻
    • 709 days old (needed 5 days)
• debian-pan (- to 0.4)
  • Migration status for debian-pan (- to 0.4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: debian-pan mathgl (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-pan.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 710 days old (needed 5 days)
• mitmproxy (- to 8.1.1-2)
  • Migration status for mitmproxy (- to 8.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mitmproxy would introduce bugs in testing: #1071640
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mitmproxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 713 days old (needed 5 days)
• debian-timeline (- to 46)
  • Migration status for debian-timeline (- to 46): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debian-timeline would introduce bugs in testing: #655664
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-timeline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 715 days old (needed 5 days)
• denemo (- to 2.6.18-1)
  • Migration status for denemo (- to 2.6.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating denemo would introduce bugs in testing: #1074906
    • autopkgtest for denemo/2.6.18-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): denemo lilypond
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/denemo.html
    • 716 days old (needed 5 days)
• vart (- to 2.5-4)
  • Migration status for vart (- to 2.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vart would introduce bugs in testing: #1037882
    • Build-Depends(-Arch): vart xir (not considered)
    • Depends: vart xir (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vart.html
    • 716 days old (needed 5 days)
• firmware-microbit-micropython (- to 1.0.1-4)
  • Migration status for firmware-microbit-micropython (- to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating firmware-microbit-micropython would introduce bugs in testing: #1073304
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firmware-microbit-micropython.html
    • 720 days old (needed 5 days)
• gdb-doc (- to 13.1-1)
  • Migration status for gdb-doc (- to 13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gdb-doc would introduce bugs in testing: #1057563
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 720 days old (needed 5 days)
• vertx-docgen (- to 0.9.4-2)
  • Migration status for vertx-docgen (- to 0.9.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vertx-docgen would introduce bugs in testing: #1081475
    • Build-Depends(-Arch): vertx-docgen openjdk-11 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vertx-docgen.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 720 days old (needed 5 days)
• zoneminder (- to 1.36.33+dfsg1-1)
  • Migration status for zoneminder (- to 1.36.33+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • zoneminder/amd64 has unsatisfiable dependency
    • zoneminder/arm64 has unsatisfiable dependency
    • zoneminder/armel has unsatisfiable dependency
    • zoneminder/armhf has unsatisfiable dependency
    • zoneminder/i386 has unsatisfiable dependency
    • zoneminder/mips64el has unsatisfiable dependency
    • zoneminder/ppc64el has unsatisfiable dependency
    • zoneminder/riscv64 has unsatisfiable dependency
    • zoneminder/s390x has unsatisfiable dependency
    • Updating zoneminder would introduce bugs in testing: #1072464, #999919
    • zoneminder unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • zoneminder unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • zoneminder unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • zoneminder unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • zoneminder unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • zoneminder unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • zoneminder unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • zoneminder unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • zoneminder unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zoneminder.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 720 days old (needed 5 days)
• fava (- to 1.23.1+dfsg-1)
  • Migration status for fava (- to 1.23.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-fava/amd64 has unsatisfiable dependency
    • python3-fava/arm64 has unsatisfiable dependency
    • Updating fava would introduce bugs in testing: #1031724, #1071795
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/fava.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 722 days old (needed 5 days)
• python-lua (- to 0.6-1)
  • Migration status for python-lua (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-lua/0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lua.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 723 days old (needed 5 days)
• oregano (- to 0.84.41+dfsg.1-1.1)
  • Migration status for oregano (- to 0.84.41+dfsg.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oregano would introduce bugs in testing: #1051281, #1081089
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oregano.html
    • 725 days old (needed 5 days)
• xserver-xorg-video-trident (- to 1:1.4.0-1)
  • Migration status for xserver-xorg-video-trident (- to 1:1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-trident would introduce bugs in testing: #1087037
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-trident.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 725 days old (needed 5 days)
• golang-github-crowdsecurity-go-cs-bouncer (- to 0.0.2-2)
  • Migration status for golang-github-crowdsecurity-go-cs-bouncer (- 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): golang-github-crowdsecurity-go-cs-bouncer crowdsec (not considered)
    • Depends: golang-github-crowdsecurity-go-cs-bouncer crowdsec (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-crowdsecurity-go-cs-bouncer.html
    • autopkgtest for golang-github-crowdsecurity-go-cs-bouncer/0.0.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 726 days old (needed 2 days)
• alien-arena (- to 7.71.3+dfsg-3)
  • Migration status for alien-arena (- to 7.71.3+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating alien-arena would introduce bugs in testing: #1067108
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 728 days old (needed 5 days)
• php-horde-kolab-session (- to 2.0.3-10)
  • Migration status for php-horde-kolab-session (- to 2.0.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-kolab-session would introduce bugs in testing: #1089775
    • autopkgtest for php-horde-kolab-session/2.0.3-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-session.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 728 days old (needed 5 days)
• wcc (- to 0.0.2+dfsg-4.4)
  • Migration status for wcc (- to 0.0.2+dfsg-4.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wcc would introduce bugs in testing: #1075634, #1081015
    • Impossible Depends: wcc -> libcapstone4/4.0.2-5.1+b1/amd64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wcc.html
    • autopkgtest for wcc/0.0.2+dfsg-4.4: amd64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 730 days old (needed 2 days)
• dogtag-pki (- to 11.2.1-2)
  • Migration status for dogtag-pki (- to 11.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pki-server/amd64 has unsatisfiable dependency
    • pki-server/arm64 has unsatisfiable dependency
    • pki-server/armel has unsatisfiable dependency
    • pki-server/armhf has unsatisfiable dependency
    • pki-server/i386 has unsatisfiable dependency
    • pki-server/mips64el has unsatisfiable dependency
    • pki-server/ppc64el has unsatisfiable dependency
    • pki-server/riscv64 has unsatisfiable dependency
    • pki-server/s390x has unsatisfiable dependency
    • Updating dogtag-pki would introduce bugs in testing: #1031815, #1054480, #1065850, #1082868
    • dogtag-pki unsatisfiable Build-Depends(-Arch) on amd64: python3-distutils
    • dogtag-pki unsatisfiable Build-Depends(-Arch) on arm64: python3-distutils
    • dogtag-pki unsatisfiable Build-Depends(-Arch) on armel: python3-distutils
    • dogtag-pki unsatisfiable Build-Depends(-Arch) on armhf: python3-distutils
    • dogtag-pki unsatisfiable Build-Depends(-Arch) on i386: python3-distutils
    • dogtag-pki unsatisfiable Build-Depends(-Arch) on mips64el: python3-distutils
    • dogtag-pki unsatisfiable Build-Depends(-Arch) on ppc64el: python3-distutils
    • dogtag-pki unsatisfiable Build-Depends(-Arch) on riscv64: python3-distutils
    • dogtag-pki unsatisfiable Build-Depends(-Arch) on s390x: python3-distutils
    • Impossible Depends: dogtag-pki -> libldap-2.5-0/2.5.19+dfsg-1/amd64
    • Impossible Depends: dogtag-pki -> libldap-2.5-0/2.5.19+dfsg-1/arm64
    • Impossible Depends: dogtag-pki -> libldap-2.5-0/2.5.19+dfsg-1/armel
    • Impossible Depends: dogtag-pki -> libldap-2.5-0/2.5.19+dfsg-1/armhf
    • Impossible Depends: dogtag-pki -> libldap-2.5-0/2.5.19+dfsg-1/i386
    • Impossible Depends: dogtag-pki -> libldap-2.5-0/2.5.19+dfsg-1/mips64el
    • Impossible Depends: dogtag-pki -> libldap-2.5-0/2.5.19+dfsg-1/ppc64el
    • Impossible Depends: dogtag-pki -> libldap-2.5-0/2.5.19+dfsg-1/riscv64
    • Impossible Depends: dogtag-pki -> libldap-2.5-0/2.5.19+dfsg-1/s390x
    • Build-Depends(-Arch): dogtag-pki idm-console-framework
    • Build-Depends(-Arch): dogtag-pki jss (not considered)
    • Build-Depends(-Arch): dogtag-pki ldapjdk
    • Build-Depends(-Arch): dogtag-pki tomcatjss (not considered)
    • Depends: dogtag-pki idm-console-framework
    • Depends: dogtag-pki jss (not considered)
    • Depends: dogtag-pki ldapjdk
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/dogtag-pki.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 734 days old (needed 5 days)
• libgrokj2k (- to 10.0.5-1)
  • Migration status for libgrokj2k (- to 10.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libgrokj2k1/armhf has unsatisfiable dependency
    • Updating libgrokj2k would introduce bugs in testing: #1085165
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgrokj2k.html
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 734 days old (needed 5 days)
• php-horde-wicked (- to 2.0.8-9)
  • Migration status for php-horde-wicked (- to 2.0.8-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-wicked/2.0.8-9: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Pass
    • Depends: php-horde-wicked php-horde
    • Depends: php-horde-wicked php-horde-auth (not considered)
    • Depends: php-horde-wicked php-horde-core (not considered)
    • Depends: php-horde-wicked php-horde-db (not considered)
    • Depends: php-horde-wicked php-horde-form
    • Depends: php-horde-wicked php-horde-mime (not considered)
    • Depends: php-horde-wicked php-horde-mime-viewer
    • Depends: php-horde-wicked php-horde-perms (not considered)
    • Depends: php-horde-wicked php-horde-prefs (not considered)
    • Depends: php-horde-wicked php-horde-rpc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-wicked.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 734 days old (needed 5 days)
• pytorch-audio (- to 0.13.1-1)
  • Migration status for pytorch-audio (- to 0.13.1-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: #1071137
  • 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
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 734 days old (needed 5 days)
• samizdat (- to 0.7.1-3)
  • Migration status for samizdat (- to 0.7.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating samizdat would introduce bugs in testing: #1038848, #1093940
    • Build-Depends(-Arch): samizdat ruby-whitewash (not considered)
    • Depends: samizdat ruby-whitewash (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/samizdat.html
    • 734 days old (needed 5 days)
• adv-17v35x (- to 5.0.7.0-1)
  • Migration status for adv-17v35x (- to 5.0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating adv-17v35x would introduce bugs in testing: #1077217
    • autopkgtest for adv-17v35x/5.0.7.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adv-17v35x.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 735 days old (needed 5 days)
• ruby-rails-assets-jquery.slimscroll (- to 1.3.6+dfsg-4)
  • Migration status for ruby-rails-assets-jquery.slimscroll (- to 1.3.6+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-jquery.slimscroll would introduce bugs in testing: #1094450
    • Depends: ruby-rails-assets-jquery.slimscroll ruby-rails-assets-jquery (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-jquery.slimscroll.html
    • autopkgtest for ruby-rails-assets-jquery.slimscroll/1.3.6+dfsg-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 735 days old (needed 2 days)
• haskell-raaz (- to 0.2.1-2.1)
  • Migration status for haskell-raaz (- to 0.2.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-raaz-dev/amd64 has unsatisfiable dependency
    • libghc-raaz-doc/amd64 has unsatisfiable dependency
    • libghc-raaz-prof/amd64 has unsatisfiable dependency
    • libghc-raaz-dev/arm64 has unsatisfiable dependency
    • libghc-raaz-doc/arm64 has unsatisfiable dependency
    • libghc-raaz-prof/arm64 has unsatisfiable dependency
    • libghc-raaz-dev/armel has unsatisfiable dependency
    • libghc-raaz-prof/armel has unsatisfiable dependency
    • libghc-raaz-dev/armhf has unsatisfiable dependency
    • libghc-raaz-prof/armhf has unsatisfiable dependency
    • libghc-raaz-dev/i386 has unsatisfiable dependency
    • libghc-raaz-prof/i386 has unsatisfiable dependency
    • libghc-raaz-dev/mips64el has unsatisfiable dependency
    • libghc-raaz-prof/mips64el has unsatisfiable dependency
    • libghc-raaz-dev/ppc64el has unsatisfiable dependency
    • libghc-raaz-prof/ppc64el has unsatisfiable dependency
    • libghc-raaz-dev/riscv64 has unsatisfiable dependency
    • libghc-raaz-prof/riscv64 has unsatisfiable dependency
    • libghc-raaz-dev/s390x has unsatisfiable dependency
    • libghc-raaz-prof/s390x has unsatisfiable dependency
    • Updating haskell-raaz would introduce bugs in testing: #1053980, #1054978
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on riscv64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-raaz.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 736 days old (needed 5 days)
• ruby-arbre (- to 1.5.0-1)
  • Migration status for ruby-arbre (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-arbre would introduce bugs in testing: #1095379
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-arbre.html
    • autopkgtest for ruby-arbre/1.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 736 days old (needed 2 days)
• sagemath (- to 9.5-6)
  • Migration status for sagemath (- to 9.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-sage/amd64 has unsatisfiable dependency
    • sagemath-jupyter/amd64 has unsatisfiable dependency
    • python3-sage/arm64 has unsatisfiable dependency
    • sagemath-jupyter/arm64 has unsatisfiable dependency
    • python3-sage/i386 has unsatisfiable dependency
    • Updating sagemath would introduce bugs in testing: #1042683, #1042935, #1050182, #1052051, #1056885, #1065953, #1076651
    • sagemath unsatisfiable Build-Depends(-Arch) on amd64: python3-distutils
    • sagemath unsatisfiable Build-Depends(-Arch) on amd64: libflint-arb-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on amd64: libsymmetrica2-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on amd64: jupyter-nbextension-jupyter-js-widgets
    • sagemath unsatisfiable Build-Depends(-Arch) on arm64: python3-distutils
    • sagemath unsatisfiable Build-Depends(-Arch) on arm64: libflint-arb-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on arm64: libsymmetrica2-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on arm64: jupyter-nbextension-jupyter-js-widgets
    • sagemath unsatisfiable Build-Depends(-Arch) on i386: python3-distutils
    • sagemath unsatisfiable Build-Depends(-Arch) on i386: libflint-arb-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on i386: libsymmetrica2-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on i386: jupyter-nbextension-jupyter-js-widgets
    • Build-Depends(-Arch): sagemath brial (not considered)
    • Build-Depends(-Arch): sagemath cypari2 (not considered)
    • Build-Depends(-Arch): sagemath eclib (not considered)
    • Build-Depends(-Arch): sagemath sagenb-export (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sagemath.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 736 days old (needed 5 days)
• segyio (- to 1.8.3-1.2)
  • Migration status for segyio (- to 1.8.3-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-segyio/amd64 has unsatisfiable dependency
    • python3-segyio/arm64 has unsatisfiable dependency
    • python3-segyio/armel has unsatisfiable dependency
    • python3-segyio/armhf has unsatisfiable dependency
    • python3-segyio/i386 has unsatisfiable dependency
    • python3-segyio/mips64el has unsatisfiable dependency
    • python3-segyio/ppc64el has unsatisfiable dependency
    • python3-segyio/riscv64 has unsatisfiable dependency
    • python3-segyio/s390x has unsatisfiable dependency
    • Updating segyio would introduce bugs in testing: #1055728
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/segyio.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 736 days old (needed 5 days)
• hyperspy (- to 1.7.3-1)
  • Migration status for hyperspy (- to 1.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyperspy would introduce bugs in testing: #1040332, #1041803
    • hyperspy unsatisfiable Build-Depends(-Arch) on amd64: python3-ptable
    • hyperspy unsatisfiable Build-Depends(-Arch) on ppc64el: python3-ptable
    • Build-Depends(-Arch): hyperspy numba (not considered)
    • Build-Depends(-Arch): hyperspy python-sparse (not considered)
    • Depends: hyperspy python-sparse (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyperspy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 737 days old (needed 5 days)
• ruby-gruff (- to 0.6.0-2)
  • Migration status for ruby-gruff (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gruff would introduce bugs in testing: #1054733
    • autopkgtest for ruby-gruff/0.6.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gruff.html
    • 737 days old (needed 5 days)
• drmaa (- to 0.7.9-3)
  • Migration status for drmaa (- to 0.7.9-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: drmaa gridengine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drmaa.html
    • autopkgtest for drmaa/0.7.9-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 738 days old (needed 5 days)
• phing (- to 2.17.4-1)
  • Migration status for phing (- to 2.17.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phing would introduce bugs in testing: #1091520
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phing.html
    • autopkgtest for phing/2.17.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 738 days old (needed 5 days)
• pyemd (- to 0.5.1.54.g802fa86-2)
  • Migration status for pyemd (- to 0.5.1.54.g802fa86-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pyemd/amd64 has unsatisfiable dependency
    • python3-pyemd/arm64 has unsatisfiable dependency
    • python3-pyemd/armel has unsatisfiable dependency
    • python3-pyemd/armhf has unsatisfiable dependency
    • python3-pyemd/i386 has unsatisfiable dependency
    • python3-pyemd/mips64el has unsatisfiable dependency
    • python3-pyemd/ppc64el has unsatisfiable dependency
    • python3-pyemd/riscv64 has unsatisfiable dependency
    • python3-pyemd/s390x has unsatisfiable dependency
    • Updating pyemd would introduce bugs in testing: #1080277
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pyemd.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • 738 days old (needed 5 days)
• python-aioxmpp (- to 0.13.3-1)
  • Migration status for python-aioxmpp (- to 0.13.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aioxmpp would introduce bugs in testing: #1042239
    • Build-Depends(-Arch): python-aioxmpp python-aioopenssl (not considered)
    • Depends: python-aioxmpp python-aioopenssl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioxmpp.html
    • 738 days old (needed 5 days)
• r-cran-mockr (- to 0.2.1-1)
  • Migration status for r-cran-mockr (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-mockr would introduce bugs in testing: #1072631
    • autopkgtest for r-cran-mockr/0.2.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-mockr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 738 days old (needed 5 days)
• xen-tools (- to 4.9.2-1)
  • Migration status for xen-tools (- to 4.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xen-tools would introduce bugs in testing: #1092454
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xen-tools.html
    • autopkgtest for xen-tools/4.9.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 738 days old (needed 2 days)
• webalizer (- to 2.23.08-3.3)
  • Migration status for webalizer (- to 2.23.08-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating webalizer would introduce bugs in testing: #1075635
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webalizer.html
    • 739 days old (needed 5 days)
• xrdesktop (- to 0.15.1-5.1)
  • Migration status for xrdesktop (- to 0.15.1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xrdesktop would introduce bugs in testing: #1075679
    • Build-Depends(-Arch): xrdesktop gxr (not considered)
    • Depends: xrdesktop gulkan (not considered)
    • Depends: xrdesktop gxr (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xrdesktop.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 739 days old (needed 5 days)
• malai (- to 2.0+ds1-3)
  • Migration status for malai (- to 2.0+ds1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): malai jinput (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/malai.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 740 days old (needed 5 days)
• php-horde-imp (- to 6.2.27-3)
  • Migration status for php-horde-imp (- to 6.2.27-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-imp would introduce bugs in testing: #1038441, #1064391
    • autopkgtest for php-horde-imp/6.2.27-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Pass
    • Depends: php-horde-imp php-horde
    • Depends: php-horde-imp php-horde-auth (not considered)
    • Depends: php-horde-imp php-horde-compress (not considered)
    • Depends: php-horde-imp php-horde-core (not considered)
    • Depends: php-horde-imp php-horde-crypt (not considered)
    • Depends: php-horde-imp php-horde-editor (not considered)
    • Depends: php-horde-imp php-horde-imap-client (not considered)
    • Depends: php-horde-imp php-horde-itip (not considered)
    • Depends: php-horde-imp php-horde-mail-autoconfig (not considered)
    • Depends: php-horde-imp php-horde-mime (not considered)
    • Depends: php-horde-imp php-horde-mime-viewer
    • Depends: php-horde-imp php-horde-perms (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-imp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 740 days old (needed 5 days)
• kotlinx-atomicfu (- to 0.11.12-2)
  • Migration status for kotlinx-atomicfu (- to 0.11.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kotlinx-atomicfu would introduce bugs in testing: #1078395
    • Build-Depends(-Arch): kotlinx-atomicfu kotlin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kotlinx-atomicfu.html
    • Reproducible on amd64 - info ♻
    • 741 days old (needed 5 days)
• kotlinx-coroutines (- to 1.0.1-2)
  • Migration status for kotlinx-coroutines (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kotlinx-coroutines would introduce bugs in testing: #1078414
    • Build-Depends(-Arch): kotlinx-coroutines kotlin
    • Build-Depends(-Arch): kotlinx-coroutines kotlinx-atomicfu (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kotlinx-coroutines.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • 741 days old (needed 5 days)
• polyml (- to 5.7.1-5)
  • Migration status for polyml (- to 5.7.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating polyml would introduce bugs in testing: #1033835
    • autopkgtest for polyml/5.7.1-5: amd64: Regression or new test ♻, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Test in progress, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polyml.html
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 741 days old (needed 5 days)
• stumpwm (- to 2:22.11-3)
  • Migration status for stumpwm (- to 2:22.11-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating stumpwm would introduce bugs in testing: #1090308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stumpwm.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 742 days old (needed 5 days)
• gradle-kotlin-dsl (- to 0.13.2-5)
  • Migration status for gradle-kotlin-dsl (- to 0.13.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gradle-kotlin-dsl would introduce bugs in testing: #1078380
    • Build-Depends(-Arch): gradle-kotlin-dsl kotlin
    • Depends: gradle-kotlin-dsl kotlin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gradle-kotlin-dsl.html
    • New but not reproducible on amd64 - info ♻
    • 743 days old (needed 5 days)
• pyhst2 (- to 2020c-7)
  • Migration status for pyhst2 (- to 2020c-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pyhst2-cuda/amd64 has unsatisfiable dependency
    • Updating pyhst2 would introduce bugs in testing: #1036680, #1056840
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • 743 days old (needed 5 days)
• gosa-plugins-pwreset (- to 2.8~git20211021.d93b138-4)
  • Migration status for gosa-plugins-pwreset (- to 2.8~git20211021.d93b138-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: gosa-plugins-pwreset gosa (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-pwreset.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 744 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• psi4 (- to 1:1.3.2+dfsg-5)
  • Migration status for psi4 (- to 1:1.3.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating psi4 would introduce bugs in testing: #1093352
    • autopkgtest for psi4/1:1.3.2+dfsg-5: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): psi4 chemps2 (not considered)
    • Build-Depends(-Arch): psi4 gau2grid (not considered)
    • Depends: psi4 chemps2 (not considered)
    • Depends: psi4 gau2grid (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psi4.html
    • 745 days old (needed 5 days)
• mvdsv (- to 0.35-6)
  • Migration status for mvdsv (- to 0.35-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mvdsv/amd64 has unsatisfiable dependency
    • mvdsv/arm64 has unsatisfiable dependency
    • mvdsv/armel has unsatisfiable dependency
    • mvdsv/armhf has unsatisfiable dependency
    • mvdsv/i386 has unsatisfiable dependency
    • mvdsv/mips64el has unsatisfiable dependency
    • mvdsv/ppc64el has unsatisfiable dependency
    • mvdsv/riscv64 has unsatisfiable dependency
    • mvdsv/s390x has unsatisfiable dependency
    • Updating mvdsv would introduce bugs in testing: #1050187
    • mvdsv unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • mvdsv unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mvdsv.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 746 days old (needed 5 days)
• ruby-whitewash (- to 2.1-2)
  • Migration status for ruby-whitewash (- to 2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-whitewash would introduce bugs in testing: #1091663
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-whitewash.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 746 days old (needed 5 days)
• php-horde (- to 5.2.23+debian0-6)
  • Migration status for php-horde (- to 5.2.23+debian0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde php-horde-rpc (not considered)
    • Invalidated by dependency
    • Depends: php-horde php-horde-auth (not considered)
    • Depends: php-horde php-horde-core (not considered)
    • Depends: php-horde php-horde-form
    • Depends: php-horde php-horde-mime (not considered)
    • Depends: php-horde php-horde-perms (not considered)
    • Depends: php-horde php-horde-prefs (not considered)
    • Depends: php-horde php-horde-token (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 747 days old (needed 5 days)
• php-horde-kolab-server (- to 2.0.5-10)
  • Migration status for php-horde-kolab-server (- to 2.0.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-kolab-server would introduce bugs in testing: #1089774
    • autopkgtest for php-horde-kolab-server/2.0.5-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-kolab-server php-horde-auth (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 747 days old (needed 5 days)
• gosa-plugins-mailaddress (- to 2.8~git20211027.08b10a2-2)
  • Migration status for gosa-plugins-mailaddress (- to 2.8~git20211027.08b10a2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: gosa-plugins-mailaddress gosa (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-mailaddress.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 748 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• ktx (- to 1.42+dfsg-3)
  • Migration status for ktx (- to 1.42+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ktx would introduce bugs in testing: #1071772
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktx.html
    • 748 days old (needed 5 days)
• php-horde-core (- to 2.31.18+debian0-2)
  • Migration status for php-horde-core (- to 2.31.18+debian0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-core would introduce bugs in testing: #1089769
    • autopkgtest for php-horde-core/2.31.18+debian0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-core php-horde-auth (not considered)
    • Depends: php-horde-core php-horde-compress (not considered)
    • Depends: php-horde-core php-horde-controller (not considered)
    • Depends: php-horde-core php-horde-cssminify
    • Depends: php-horde-core php-horde-data (not considered)
    • Depends: php-horde-core php-horde-history (not considered)
    • Depends: php-horde-core php-horde-injector (not considered)
    • Depends: php-horde-core php-horde-javascriptminify (not considered)
    • Depends: php-horde-core php-horde-log (not considered)
    • Depends: php-horde-core php-horde-mime (not considered)
    • Depends: php-horde-core php-horde-mime-viewer
    • Depends: php-horde-core php-horde-perms (not considered)
    • Depends: php-horde-core php-horde-prefs (not considered)
    • Depends: php-horde-core php-horde-share (not considered)
    • Depends: php-horde-core php-horde-token (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-core.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 748 days old (needed 5 days)
• php-horde-crypt (- to 2.7.12-9)
  • Migration status for php-horde-crypt (- to 2.7.12-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-crypt would introduce bugs in testing: #1089770
    • autopkgtest for php-horde-crypt/2.7.12-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-crypt php-horde-mime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-crypt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 748 days old (needed 5 days)
• php-horde-rdo (- to 2.1.0-10)
  • Migration status for php-horde-rdo (- to 2.1.0-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-rdo/2.1.0-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-rdo php-horde-db (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-rdo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 748 days old (needed 5 days)
• ruby-dataobjects-mysql (- to 0.10.17-4)
  • Migration status for ruby-dataobjects-mysql (- to 0.10.17-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-dataobjects-mysql ruby-dataobjects (not considered)
    • Depends: ruby-dataobjects-mysql ruby-dataobjects (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dataobjects-mysql.html
    • autopkgtest for ruby-dataobjects-mysql/0.10.17-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 748 days old (needed 2 days)
• firetools (- to 0.9.72-1)
  • Migration status for firetools (- to 0.9.72-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: firetools firejail (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firetools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 749 days old (needed 5 days)
• php-horde-injector (- to 2.0.5-12)
  • Migration status for php-horde-injector (- to 2.0.5-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-injector would introduce bugs in testing: #1089773
    • autopkgtest for php-horde-injector/2.0.5-12: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-injector.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 749 days old (needed 5 days)
• php-horde-itip (- to 2.1.2-9)
  • Migration status for php-horde-itip (- to 2.1.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-itip/2.1.2-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-itip php-horde-mime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-itip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 749 days old (needed 5 days)
• php-horde-log (- to 2.3.0-9)
  • Migration status for php-horde-log (- to 2.3.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-log would introduce bugs in testing: #1089776
    • autopkgtest for php-horde-log/2.3.0-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-log.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 749 days old (needed 5 days)
• php-horde-mapi (- to 1.0.10-5)
  • Migration status for php-horde-mapi (- to 1.0.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-mapi would introduce bugs in testing: #1089727
    • autopkgtest for php-horde-mapi/1.0.10-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mapi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 749 days old (needed 5 days)
• php-horde-mime (- to 2.11.2-2)
  • Migration status for php-horde-mime (- to 2.11.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-mime would introduce bugs in testing: #1089777
    • autopkgtest for php-horde-mime/2.11.2-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 749 days old (needed 5 days)
• php-horde-passwd (- to 5.0.7-9)
  • Migration status for php-horde-passwd (- to 5.0.7-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-passwd/5.0.7-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
    • Depends: php-horde-passwd php-horde
    • Depends: php-horde-passwd php-horde-auth (not considered)
    • Depends: php-horde-passwd php-horde-core (not considered)
    • Depends: php-horde-passwd php-horde-injector (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-passwd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 749 days old (needed 5 days)
• php-horde-token (- to 2.0.9-9)
  • Migration status for php-horde-token (- to 2.0.9-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-token would introduce bugs in testing: #1089779
    • autopkgtest for php-horde-token/2.0.9-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-token.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 749 days old (needed 5 days)
• freedroidrpg (- to 1.0-1)
  • Migration status for freedroidrpg (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freedroidrpg would introduce bugs in testing: #1074966
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freedroidrpg.html
    • 750 days old (needed 5 days)
• php-horde-auth (- to 2.2.2-10)
  • Migration status for php-horde-auth (- to 2.2.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-auth would introduce bugs in testing: #1089768
    • autopkgtest for php-horde-auth/2.2.2-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-auth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 750 days old (needed 5 days)
• php-horde-compress (- to 2.2.4-3)
  • Migration status for php-horde-compress (- to 2.2.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-compress/2.2.4-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-compress php-horde-mime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-compress.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 750 days old (needed 5 days)
• aribas (- to 1.65-1)
  • Migration status for aribas (- to 1.65-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aribas would introduce bugs in testing: #1074818
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aribas.html
    • autopkgtest for aribas/1.65-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 751 days old (needed 2 days)
• eviacam (- to 2.1.4-2.1)
  • Migration status for eviacam (- to 2.1.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eviacam would introduce bugs in testing: #1033052
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eviacam.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 751 days old (needed 5 days)
• vtk-dicom (- to 0.8.14-3.1)
  • Migration status for vtk-dicom (- to 0.8.14-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-vtk-dicom/amd64 has unsatisfiable dependency
    • python3-vtk-dicom/arm64 has unsatisfiable dependency
    • python3-vtk-dicom/armel has unsatisfiable dependency
    • python3-vtk-dicom/armhf has unsatisfiable dependency
    • python3-vtk-dicom/i386 has unsatisfiable dependency
    • python3-vtk-dicom/mips64el has unsatisfiable dependency
    • python3-vtk-dicom/ppc64el has unsatisfiable dependency
    • python3-vtk-dicom/riscv64 has unsatisfiable dependency
    • python3-vtk-dicom/s390x has unsatisfiable dependency
    • Updating vtk-dicom would introduce bugs in testing: #1063195, #1091516
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vtk-dicom.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 751 days old (needed 5 days)
• libembperl-perl (- to 2.5.0-17)
  • Migration status for libembperl-perl (- to 2.5.0-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libembperl-perl/amd64 has unsatisfiable dependency
    • libembperl-perl/arm64 has unsatisfiable dependency
    • libembperl-perl/armel has unsatisfiable dependency
    • libembperl-perl/armhf has unsatisfiable dependency
    • libembperl-perl/i386 has unsatisfiable dependency
    • libembperl-perl/mips64el has unsatisfiable dependency
    • libembperl-perl/ppc64el has unsatisfiable dependency
    • libembperl-perl/s390x has unsatisfiable dependency
    • Updating libembperl-perl would introduce bugs in testing: #1042845
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libe/libembperl-perl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 752 days old (needed 5 days)
• sfepy (- to 2021.4-4)
  • Migration status for sfepy (- to 2021.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-sfepy/amd64 has unsatisfiable dependency
    • python3-sfepy/arm64 has unsatisfiable dependency
    • python3-sfepy/mips64el has unsatisfiable dependency
    • python3-sfepy/ppc64el has unsatisfiable dependency
    • python3-sfepy/s390x has unsatisfiable dependency
    • Updating sfepy would introduce bugs in testing: #1056887, #1086578
    • Build-Depends(-Arch): sfepy mayavi2 (not considered)
    • Build-Depends(-Arch): sfepy python-sparse (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sfepy.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 752 days old (needed 5 days)
• bustle (- to 0.8.0-2)
  • Migration status for bustle (- to 0.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bustle would introduce bugs in testing: #1084243, #1084512
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bustle.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • 753 days old (needed 5 days)
• php-horde-imap-client (- to 2.30.6-3)
  • Migration status for php-horde-imap-client (- to 2.30.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-imap-client/2.30.6-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-imap-client php-horde-mime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-imap-client.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 754 days old (needed 5 days)
• janus (- to 1.1.2-1)
  • Migration status for janus (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • janus-tools/amd64 has unsatisfiable dependency
    • janus-tools/arm64 has unsatisfiable dependency
    • janus-tools/armel has unsatisfiable dependency
    • janus-tools/armhf has unsatisfiable dependency
    • janus-tools/i386 has unsatisfiable dependency
    • janus-tools/mips64el has unsatisfiable dependency
    • janus-tools/ppc64el has unsatisfiable dependency
    • janus-tools/riscv64 has unsatisfiable dependency
    • janus-tools/s390x has unsatisfiable dependency
    • Updating janus would introduce bugs in testing: #1072424
    • Impossible Depends: janus -> libconfig9/1.5-0.4+b2/amd64
    • Impossible Depends: janus -> libconfig9/1.5-0.4+b2/arm64
    • Impossible Depends: janus -> libconfig9/1.5-0.4+b2/armel
    • Impossible Depends: janus -> libconfig9/1.5-0.4+b2/armhf
    • Impossible Depends: janus -> libconfig9/1.5-0.4+b2/i386
    • Impossible Depends: janus -> libconfig9/1.5-0.4+b2/mips64el
    • Impossible Depends: janus -> libconfig9/1.5-0.4+b2/ppc64el
    • Impossible Depends: janus -> libconfig9/1.5-0.4+b2/riscv64
    • Impossible Depends: janus -> libconfig9/1.5-0.4+b2/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/janus.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 755 days old (needed 5 days)
• relion-cuda (- to 3.1.3-2)
  • Migration status for relion-cuda (- to 3.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • relion-cuda/amd64 has unsatisfiable dependency
    • relion-gui-cuda/amd64 has unsatisfiable dependency
    • Updating relion-cuda would introduce bugs in testing: #1036681, #1040128
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • 756 days old (needed 5 days)
• latexdraw (- to 3.3.8+ds1-2)
  • Migration status for latexdraw (- to 3.3.8+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: latexdraw scala (not considered)
    • Depends: latexdraw scala (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends-Indep: latexdraw malai
    • Depends: latexdraw malai
    • Depends: latexdraw scala-parser-combinators
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/latexdraw.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 757 days old (needed 5 days)
• firejail (- to 0.9.72-2)
  • Migration status for firejail (- to 0.9.72-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating firejail would introduce bugs in testing: #1069449
    • autopkgtest for firejail/0.9.72-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firejail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 758 days old (needed 5 days)
• vim-ultisnips (- to 3.2-2)
  • Migration status for vim-ultisnips (- to 3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vim-ultisnips would introduce bugs in testing: #1033510
    • autopkgtest for vim-ultisnips/3.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-ultisnips.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 758 days old (needed 5 days)
• odpic (- to 4.6.0-1)
  • Migration status for odpic (- to 4.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating odpic would introduce bugs in testing: #1057936
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 765 days old (needed 5 days)
• organize (- to 2.4.0-1)
  • Migration status for organize (- to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating organize would introduce bugs in testing: #1080883, #1082579
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/organize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 765 days old (needed 5 days)
• openzwave-controlpanel (- to 1.6~git20200306.4b8a39d-1)
  • Migration status for openzwave-controlpanel (- to 1.6~git20200306.4b8a39d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openzwave-controlpanel would introduce bugs in testing: #1091812
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 767 days old (needed 5 days)
• astunparse (- to 1.6.3-2)
  • Migration status for astunparse (- to 1.6.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating astunparse would introduce bugs in testing: #1082046
    • Not touching package due to block request by ginggs (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astunparse.html
    • autopkgtest for astunparse/1.6.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 768 days old (needed 2 days)
• jollyday (- to 0.5.10-2)
  • Migration status for jollyday (- to 0.5.10-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): jollyday jax-maven-plugin (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jollyday.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 768 days old (needed 5 days)
• nvidia-settings-legacy-390xx (- to 390.157-1)
  • Migration status for nvidia-settings-legacy-390xx (- to 390.157-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-legacy-390xx nvidia-graphics-drivers-legacy-390xx (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 769 days old (needed 5 days)
• nvidia-settings-tesla-418 (- to 418.113-9)
  • Migration status for nvidia-settings-tesla-418 (- to 418.113-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-tesla-418 nvidia-graphics-drivers-tesla-418 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 769 days old (needed 5 days)
• nvidia-settings-tesla-450 (- to 450.119.03-4)
  • Migration status for nvidia-settings-tesla-450 (- to 450.119.03-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-tesla-450 nvidia-graphics-drivers-tesla-450 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 769 days old (needed 5 days)
• nvidia-settings-tesla-460 (- to 460.91.03-4)
  • Migration status for nvidia-settings-tesla-460 (- to 460.91.03-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-tesla-460 nvidia-graphics-drivers-tesla-460 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 769 days old (needed 5 days)
• php-horde-activesync (- to 2.41.9-1)
  • Migration status for php-horde-activesync (- to 2.41.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-activesync/2.41.9-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-activesync php-horde-compress (not considered)
    • Depends: php-horde-activesync php-horde-log (not considered)
    • Depends: php-horde-activesync php-horde-mapi (not considered)
    • Depends: php-horde-activesync php-horde-mime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-activesync.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 769 days old (needed 5 days)
• php-horde-sesha (- to 1.0.0~rc3-9)
  • Migration status for php-horde-sesha (- to 1.0.0~rc3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-sesha/1.0.0~rc3-9: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Pass
    • Depends: php-horde-sesha php-horde
    • Depends: php-horde-sesha php-horde-auth (not considered)
    • Depends: php-horde-sesha php-horde-core (not considered)
    • Depends: php-horde-sesha php-horde-db (not considered)
    • Depends: php-horde-sesha php-horde-form
    • Depends: php-horde-sesha php-horde-perms (not considered)
    • Depends: php-horde-sesha php-horde-prefs (not considered)
    • Depends: php-horde-sesha php-horde-rdo (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-sesha.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 769 days old (needed 5 days)
• nvidia-settings-legacy-340xx (- to 340.108-7)
  • Migration status for nvidia-settings-legacy-340xx (- to 340.108-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-legacy-340xx nvidia-graphics-drivers-legacy-340xx (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 770 days old (needed 5 days)
• php-horde-turba (- to 4.2.29-2)
  • Migration status for php-horde-turba (- to 4.2.29-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-turba would introduce bugs in testing: #1064392
    • autopkgtest for php-horde-turba/4.2.29-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Pass
    • Depends: php-horde-turba php-horde
    • Depends: php-horde-turba php-horde-auth (not considered)
    • Depends: php-horde-turba php-horde-content (not considered)
    • Depends: php-horde-turba php-horde-core (not considered)
    • Depends: php-horde-turba php-horde-data (not considered)
    • Depends: php-horde-turba php-horde-dav
    • Depends: php-horde-turba php-horde-form
    • Depends: php-horde-turba php-horde-history (not considered)
    • Depends: php-horde-turba php-horde-mime (not considered)
    • Depends: php-horde-turba php-horde-perms (not considered)
    • Depends: php-horde-turba php-horde-prefs (not considered)
    • Depends: php-horde-turba php-horde-share (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-turba.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 770 days old (needed 5 days)
• php-horde-ingo (- to 3.2.16-9)
  • Migration status for php-horde-ingo (- to 3.2.16-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-ingo/3.2.16-9: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Pass
    • Depends: php-horde-ingo php-horde
    • Depends: php-horde-ingo php-horde-auth (not considered)
    • Depends: php-horde-ingo php-horde-core (not considered)
    • Depends: php-horde-ingo php-horde-form
    • Depends: php-horde-ingo php-horde-imap-client (not considered)
    • Depends: php-horde-ingo php-horde-mime (not considered)
    • Depends: php-horde-ingo php-horde-perms (not considered)
    • Depends: php-horde-ingo php-horde-share (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ingo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 771 days old (needed 5 days)
• ruby-influxdb (- to 0.8.1-2)
  • Migration status for ruby-influxdb (- to 0.8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-influxdb would introduce bugs in testing: #1076919
    • autopkgtest for ruby-influxdb/0.8.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-influxdb.html
    • 771 days old (needed 5 days)
• php-horde-kronolith (- to 4.2.29-3)
  • Migration status for php-horde-kronolith (- to 4.2.29-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-kronolith would introduce bugs in testing: #1054531
    • autopkgtest for php-horde-kronolith/4.2.29-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Pass
    • Depends: php-horde-kronolith php-horde
    • Depends: php-horde-kronolith php-horde-auth (not considered)
    • Depends: php-horde-kronolith php-horde-content (not considered)
    • Depends: php-horde-kronolith php-horde-core (not considered)
    • Depends: php-horde-kronolith php-horde-data (not considered)
    • Depends: php-horde-kronolith php-horde-dav
    • Depends: php-horde-kronolith php-horde-form
    • Depends: php-horde-kronolith php-horde-history (not considered)
    • Depends: php-horde-kronolith php-horde-mime (not considered)
    • Depends: php-horde-kronolith php-horde-perms (not considered)
    • Depends: php-horde-kronolith php-horde-share (not considered)
    • Depends: php-horde-kronolith php-horde-timezone (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kronolith.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 772 days old (needed 5 days)
• whitakers-words (- to 0.2020.10.27-1.3)
  • Migration status for whitakers-words (- to 0.2020.10.27-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating whitakers-words would introduce bugs in testing: #1067285
    • autopkgtest for whitakers-words/0.2020.10.27-1.3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whitakers-words.html
    • 773 days old (needed 5 days)
• calligraplan (- to 1:3.3.0-2)
  • Migration status for calligraplan (- to 1:3.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • calligraplan/amd64 has unsatisfiable dependency
    • calligraplan/arm64 has unsatisfiable dependency
    • calligraplan/armel has unsatisfiable dependency
    • calligraplan/armhf has unsatisfiable dependency
    • calligraplan/i386 has unsatisfiable dependency
    • calligraplan/mips64el has unsatisfiable dependency
    • calligraplan/ppc64el has unsatisfiable dependency
    • calligraplan/riscv64 has unsatisfiable dependency
    • calligraplan/s390x has unsatisfiable dependency
    • Updating calligraplan would introduce bugs in testing: #1086481, #1091122
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calligraplan.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 774 days old (needed 5 days)
• php-horde-perms (- to 2.1.8-5)
  • Migration status for php-horde-perms (- to 2.1.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-perms/2.1.8-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-perms php-horde-db (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-perms.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 774 days old (needed 5 days)
• php-horde-share (- to 2.2.0-9)
  • Migration status for php-horde-share (- to 2.2.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-share/2.2.0-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-share php-horde-db (not considered)
    • Depends: php-horde-share php-horde-perms (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-share.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 774 days old (needed 5 days)
• 3depict (- to 0.0.23-2)
  • Migration status for 3depict (- to 0.0.23-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 3depict mathgl (not considered)
    • Depends: 3depict mathgl (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): 3depict libvigraimpex (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/3/3depict.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 775 days old (needed 5 days)
• arduino-builder (- to 1.3.25-4)
  • Migration status for arduino-builder (- to 1.3.25-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating arduino-builder would introduce bugs in testing: #1085522
    • autopkgtest for arduino-builder/1.3.25-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arduino-builder.html
    • 775 days old (needed 5 days)
• php-sabre-vobject (- to 2.1.7-6.1)
  • Migration status for php-sabre-vobject (- to 2.1.7-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-vobject would introduce bugs in testing: #1052792
    • autopkgtest for php-sabre-vobject/2.1.7-6.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-vobject.html
    • 776 days old (needed 5 days)
• enblend-enfuse (- to 4.2-10)
  • Migration status for enblend-enfuse (- to 4.2-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): enblend-enfuse libvigraimpex (not considered)
    • Depends: enblend-enfuse libvigraimpex (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/enblend-enfuse.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 778 days old (needed 5 days)
• kbtin (- to 2.1-2)
  • Migration status for kbtin (- to 2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kbtin/armhf has unsatisfiable dependency
    • Updating kbtin would introduce bugs in testing: #1061076
    • autopkgtest for kbtin/2.1-2: amd64: Pass, arm64: Pass, armel: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kbtin.html
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 778 days old (needed 5 days)
• gmrender-resurrect (- to 0.1-1)
  • Migration status for gmrender-resurrect (- to 0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gmrender-resurrect would introduce bugs in testing: #1075021
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gmrender-resurrect.html
    • 779 days old (needed 5 days)
• python-bitcoinlib (- to 0.11.2-1)
  • Migration status for python-bitcoinlib (- to 0.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-bitcoinlib would introduce bugs in testing: #1080127
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bitcoinlib.html
    • autopkgtest for python-bitcoinlib/0.11.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 779 days old (needed 2 days)
• php-horde-ansel (- to 3.0.10+debian1-3)
  • Migration status for php-horde-ansel (- to 3.0.10+debian1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-ansel/3.0.10+debian1-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
    • Depends: php-horde-ansel php-horde
    • Depends: php-horde-ansel php-horde-auth (not considered)
    • Depends: php-horde-ansel php-horde-content (not considered)
    • Depends: php-horde-ansel php-horde-core (not considered)
    • Depends: php-horde-ansel php-horde-db (not considered)
    • Depends: php-horde-ansel php-horde-form
    • Depends: php-horde-ansel php-horde-mime (not considered)
    • Depends: php-horde-ansel php-horde-perms (not considered)
    • Depends: php-horde-ansel php-horde-prefs (not considered)
    • Depends: php-horde-ansel php-horde-share (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ansel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 780 days old (needed 5 days)
• php-horde-prefs (- to 2.9.0-9)
  • Migration status for php-horde-prefs (- to 2.9.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-prefs/2.9.0-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-prefs php-horde-mime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-prefs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 780 days old (needed 5 days)
• speedcrunch (- to 0.12.0-6)
  • Migration status for speedcrunch (- to 0.12.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): speedcrunch quark-sphinx-theme (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/speedcrunch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 782 days old (needed 5 days)
• php-horde-history (- to 2.3.6-11)
  • Migration status for php-horde-history (- to 2.3.6-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-history/2.3.6-11: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-history php-horde-db (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-history.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 783 days old (needed 5 days)
• avro-c (- to 1.11.1-1)
  • Migration status for avro-c (- to 1.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating avro-c would introduce bugs in testing: #1074832
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/avro-c.html
    • 784 days old (needed 5 days)
• ball (- to 1.5.0+git20180813.37fc53c-11)
  • Migration status for ball (- to 1.5.0+git20180813.37fc53c-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ball sip4 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/ball.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 784 days old (needed 5 days)
• alsa-oss (- to 1.1.8-2)
  • Migration status for alsa-oss (- to 1.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • alsa-oss/armel has unsatisfiable dependency
    • alsa-oss/armhf has unsatisfiable dependency
    • Updating alsa-oss would introduce bugs in testing: #1066825
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/alsa-oss.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 785 days old (needed 5 days)
• jamin (- to 0.98.9~git20170111~199091~repack1-2)
  • Migration status for jamin (- to 0.98.9~git20170111~199091~repack1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jamin would introduce bugs in testing: #1075099
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jamin.html
    • 786 days old (needed 5 days)
• jax-maven-plugin (- to 0.1.8+dfsg-2)
  • Migration status for jax-maven-plugin (- to 0.1.8+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jax-maven-plugin would introduce bugs in testing: #1091120
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jax-maven-plugin.html
    • Reproducible on armhf - info ♻
    • 786 days old (needed 5 days)
• massxpert (- to 7.0.0-2)
  • Migration status for massxpert (- to 7.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating massxpert would introduce bugs in testing: #1084296
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/massxpert.html
    • 786 days old (needed 5 days)
• mujoco (- to 2.2.2-3)
  • Migration status for mujoco (- to 2.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libmujoco-samples/amd64 has unsatisfiable dependency
    • libmujoco2.2.2/amd64 has unsatisfiable dependency
    • libmujoco-samples/arm64 has unsatisfiable dependency
    • libmujoco2.2.2/arm64 has unsatisfiable dependency
    • libmujoco-samples/armel has unsatisfiable dependency
    • libmujoco2.2.2/armel has unsatisfiable dependency
    • libmujoco-samples/armhf has unsatisfiable dependency
    • libmujoco2.2.2/armhf has unsatisfiable dependency
    • libmujoco-samples/i386 has unsatisfiable dependency
    • libmujoco2.2.2/i386 has unsatisfiable dependency
    • libmujoco-samples/mips64el has unsatisfiable dependency
    • libmujoco2.2.2/mips64el has unsatisfiable dependency
    • libmujoco-samples/ppc64el has unsatisfiable dependency
    • libmujoco2.2.2/ppc64el has unsatisfiable dependency
    • libmujoco-samples/riscv64 has unsatisfiable dependency
    • libmujoco2.2.2/riscv64 has unsatisfiable dependency
    • libmujoco-samples/s390x has unsatisfiable dependency
    • libmujoco2.2.2/s390x has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mujoco.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 791 days old (needed 5 days)
• node-fstream-ignore (- to 1.0.5-4)
  • Migration status for node-fstream-ignore (- to 1.0.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-fstream-ignore would introduce bugs in testing: #1078886
    • autopkgtest for node-fstream-ignore/1.0.5-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-fstream-ignore.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 791 days old (needed 5 days)
• btas (- to 0.0+git20221014.147bf4d4-1)
  • Migration status for btas (- to 0.0+git20221014.147bf4d4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating btas would introduce bugs in testing: #1028634
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 795 days old (needed 5 days)
• atitvout (- to 0.4-13.2)
  • Migration status for atitvout (- to 0.4-13.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating atitvout would introduce bugs in testing: #1063644
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 796 days old (needed 5 days)
• jhbuild (- to 3.38.0-3.1)
  • Migration status for jhbuild (- to 3.38.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • jhbuild/amd64 has unsatisfiable dependency
    • jhbuild/arm64 has unsatisfiable dependency
    • Updating jhbuild would introduce bugs in testing: #1054720, #1065882
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/j/jhbuild.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 796 days old (needed 5 days)
• linssid (- to 3.6-8)
  • Migration status for linssid (- to 3.6-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • linssid/armel has unsatisfiable dependency
    • linssid/armhf has unsatisfiable dependency
    • Updating linssid would introduce bugs in testing: #1067913
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linssid.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 798 days old (needed 5 days)
• python-mockupdb (- to 1.8.0-4)
  • Migration status for python-mockupdb (- to 1.8.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-mockupdb would introduce bugs in testing: #1058189
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mockupdb.html
    • autopkgtest for python-mockupdb/1.8.0-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 798 days old (needed 5 days)
• sooperlooper (- to 1.7.8~dfsg0-2)
  • Migration status for sooperlooper (- to 1.7.8~dfsg0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sooperlooper would introduce bugs in testing: #1071364
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sooperlooper.html
    • 799 days old (needed 5 days)
• mediawiki-extension-codemirror (- to 4.0.0~git20221204.b897975-1)
  • Migration status for mediawiki-extension-codemirror (- to 4.0.0~git20221204.b897975-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mediawiki-extension-codemirror would introduce bugs in testing: #1089763
    • autopkgtest for mediawiki-extension-codemirror/4.0.0~git20221204.b897975-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: mediawiki-extension-codemirror mediawiki (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mediawiki-extension-codemirror.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 days old (needed 5 days)
• mediawiki-extension-youtube (- to 1.9.3~git20221020.e005c0b-1)
  • Migration status for mediawiki-extension-youtube (- to 1.9.3~git20221020.e005c0b-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mediawiki-extension-youtube would introduce bugs in testing: #1089764
    • autopkgtest for mediawiki-extension-youtube/1.9.3~git20221020.e005c0b-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: mediawiki-extension-youtube mediawiki (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mediawiki-extension-youtube.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 days old (needed 5 days)
• mediawiki-skin-greystuff (- to 1.2.5~git20220922.60bda8c-2)
  • Migration status for mediawiki-skin-greystuff (- to 1.2.5~git20220922.60bda8c-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mediawiki-skin-greystuff would introduce bugs in testing: #1089765
    • autopkgtest for mediawiki-skin-greystuff/1.2.5~git20220922.60bda8c-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: mediawiki-skin-greystuff mediawiki (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mediawiki-skin-greystuff.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 days old (needed 5 days)
• dump1090-mutability (- to 1.15~20180310.4a16df3+dfsg-8.1)
  • Migration status for dump1090-mutability (- to 1.15~20180310.4a16df3+dfsg-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dump1090-mutability would introduce bugs in testing: #1074924
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dump1090-mutability.html
    • 802 days old (needed 5 days)
• mpqc (- to 2.3.1-22)
  • Migration status for mpqc (- to 2.3.1-22): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsc-dev/amd64 has unsatisfiable dependency
    • libsc7v5/amd64 has unsatisfiable dependency
    • mpqc/amd64 has unsatisfiable dependency
    • libsc-dev/arm64 has unsatisfiable dependency
    • libsc7v5/arm64 has unsatisfiable dependency
    • mpqc/arm64 has unsatisfiable dependency
    • libsc-dev/mips64el has unsatisfiable dependency
    • libsc7v5/mips64el has unsatisfiable dependency
    • mpqc/mips64el has unsatisfiable dependency
    • libsc-dev/ppc64el has unsatisfiable dependency
    • libsc7v5/ppc64el has unsatisfiable dependency
    • mpqc/ppc64el has unsatisfiable dependency
    • libsc-dev/riscv64 has unsatisfiable dependency
    • libsc7v5/riscv64 has unsatisfiable dependency
    • mpqc/riscv64 has unsatisfiable dependency
    • libsc-dev/s390x has unsatisfiable dependency
    • libsc7v5/s390x has unsatisfiable dependency
    • mpqc/s390x has unsatisfiable dependency
    • Updating mpqc would introduce bugs in testing: #1075293, #1077120
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpqc.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 riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 803 days old (needed 5 days)
• telepathy-haze (- to 0.8.1-0.1)
  • Migration status for telepathy-haze (- to 0.8.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telepathy-haze would introduce bugs in testing: #1075560
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telepathy-haze.html
    • 805 days old (needed 5 days)
• libapache-db-perl (- to 0.18-2)
  • Migration status for libapache-db-perl (- to 0.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libapache-db-perl/amd64 has unsatisfiable dependency
    • libapache-db-perl/arm64 has unsatisfiable dependency
    • libapache-db-perl/armel has unsatisfiable dependency
    • libapache-db-perl/armhf has unsatisfiable dependency
    • libapache-db-perl/i386 has unsatisfiable dependency
    • libapache-db-perl/mips64el has unsatisfiable dependency
    • libapache-db-perl/ppc64el has unsatisfiable dependency
    • libapache-db-perl/riscv64 has unsatisfiable dependency
    • libapache-db-perl/s390x has unsatisfiable dependency
    • Updating libapache-db-perl would introduce bugs in testing: #1040396
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/liba/libapache-db-perl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 806 days old (needed 5 days)
• djangorestframework-filters (- to 1.0.0.dev2-2)
  • Migration status for djangorestframework-filters (- to 1.0.0.dev2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating djangorestframework-filters would introduce bugs in testing: #1052818
    • autopkgtest for djangorestframework-filters/1.0.0.dev2-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/djangorestframework-filters.html
    • 808 days old (needed 5 days)
• octocatalog-diff (- to 2.1.0-1)
  • Migration status for octocatalog-diff (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octocatalog-diff would introduce bugs in testing: #1025300
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octocatalog-diff.html
    • autopkgtest for octocatalog-diff/2.1.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 808 days old (needed 5 days)
• pykwalify (- to 1.8.0-2)
  • Migration status for pykwalify (- to 1.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pykwalify would introduce bugs in testing: #1069386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pykwalify.html
    • 808 days old (needed 5 days)
• funguloids (- to 1.06-15)
  • Migration status for funguloids (- to 1.06-15): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): funguloids ogre-1.9 (not considered)
    • Depends: funguloids ogre-1.9 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/funguloids.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 809 days old (needed 5 days)
• shovill (- to 1.1.0-9)
  • Migration status for shovill (- to 1.1.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: shovill pilon (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shovill.html
    • autopkgtest for shovill/1.1.0-9: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 809 days old (needed 2 days)
• django-measurement (- to 3.2.4-1)
  • Migration status for django-measurement (- to 3.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): django-measurement python-measurement (not considered)
    • Depends: django-measurement python-measurement (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-measurement.html
    • autopkgtest for django-measurement/3.2.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 810 days old (needed 2 days)
• python-aioinflux (- to 0.9.0-5)
  • Migration status for python-aioinflux (- to 0.9.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aioinflux would introduce bugs in testing: #1084325
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioinflux.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 810 days old (needed 5 days)
• ocsinventory-server (- to 2.8.1+dfsg1+~2.11.1-1)
  • Migration status for ocsinventory-server (- to 2.8.1+dfsg1+~2.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: ocsinventory-server php-imap (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocsinventory-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 811 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• asmix (- to 1.5-4.3)
  • Migration status for asmix (- to 1.5-4.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asmix would introduce bugs in testing: #1066206, #1095123
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asmix.html
    • 812 days old (needed 5 days)
• python-certbot-dns-digitalocean (- to 2.0.0-1)
  • Migration status for python-certbot-dns-digitalocean (- 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): python-certbot-dns-digitalocean python-digitalocean (not considered)
    • Depends: python-certbot-dns-digitalocean python-digitalocean (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-digitalocean.html
    • autopkgtest for python-certbot-dns-digitalocean/2.0.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 812 days old (needed 5 days)
• binutils-djgpp (- to 2.35.1+dfsg-2)
  • Migration status for binutils-djgpp (- to 2.35.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils-djgpp would introduce bugs in testing: #1091301
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-djgpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 814 days old (needed 5 days)
• golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2)
  • Migration status for golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-leanovate-gopter/0.2.9+git20210201.bbbf00e-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-leanovate-gopter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 814 days old (needed 5 days)
• node-node-rsa (- to 1.1.1-4)
  • Migration status for node-node-rsa (- to 1.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-node-rsa would introduce bugs in testing: #1064696
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-node-rsa.html
    • autopkgtest for node-node-rsa/1.1.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 814 days old (needed 2 days)
• shush (- to 1.2.3-5.1)
  • Migration status for shush (- to 1.2.3-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • shush/amd64 has unsatisfiable dependency
    • shush/arm64 has unsatisfiable dependency
    • shush/armel has unsatisfiable dependency
    • shush/armhf has unsatisfiable dependency
    • shush/i386 has unsatisfiable dependency
    • shush/mips64el has unsatisfiable dependency
    • shush/ppc64el has unsatisfiable dependency
    • shush/riscv64 has unsatisfiable dependency
    • shush/s390x has unsatisfiable dependency
    • Updating shush would introduce bugs in testing: #999964
    • shush unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • shush unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shush.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 815 days old (needed 5 days)
• osdsh (- to 0.7.0-11)
  • Migration status for osdsh (- to 0.7.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating osdsh would introduce bugs in testing: #1091062
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/osdsh.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 817 days old (needed 5 days)
• bart-cuda (- to 0.8.00-2)
  • Migration status for bart-cuda (- to 0.8.00-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bart-cuda would introduce bugs in testing: #1078156
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for bart-cuda/0.8.00-2: amd64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 818 days old (needed 2 days)
• tipp (- to 1.0+dfsg-3)
  • Migration status for tipp (- to 1.0+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): tipp sepp (not considered)
    • Depends: tipp sepp (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tipp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 819 days old (needed 5 days)
• v-sim (- to 3.7.2-9)
  • Migration status for v-sim (- to 3.7.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating v-sim would introduce bugs in testing: #1075614
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/v-sim.html
    • 821 days old (needed 5 days)
• sip4 (- to 4.19.25+dfsg-5)
  • Migration status for sip4 (- to 4.19.25+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sip4 would introduce bugs in testing: #1059648
    • autopkgtest for sip4/4.19.25+dfsg-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Not touching package due to block request by ginggs (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sip4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 822 days old (needed 5 days)
• between (- to 6+dfsg1-4)
  • Migration status for between (- to 6+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating between would introduce bugs in testing: #1072834
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/between.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 827 days old (needed 5 days)
• ruby-omniauth-rails-csrf-protection (- to 1.0.1-2)
  • Migration status for ruby-omniauth-rails-csrf-protection (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-rails-csrf-protection would introduce bugs in testing: #1095380
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-rails-csrf-protection.html
    • autopkgtest for ruby-omniauth-rails-csrf-protection/1.0.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 827 days old (needed 2 days)
• extractpdfmark (- to 1.1.1-1)
  • Migration status for extractpdfmark (- to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating extractpdfmark would introduce bugs in testing: #1091268
    • Impossible Depends: extractpdfmark -> libpoppler-cpp1/24.08.0-4/armel
    • Impossible Depends: extractpdfmark -> libpoppler-cpp1/24.08.0-4/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/extractpdfmark.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 829 days old (needed 5 days)
• arduino-core-avr (- to 1.8.6+dfsg-1)
  • Migration status for arduino-core-avr (- to 1.8.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating arduino-core-avr would introduce bugs in testing: #1086256
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arduino-core-avr.html
    • 830 days old (needed 5 days)
• py-rnp (- to 0.1.0+git20221014.01b7129-4)
  • Migration status for py-rnp (- to 0.1.0+git20221014.01b7129-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating py-rnp would introduce bugs in testing: #1058436
    • autopkgtest for py-rnp/0.1.0+git20221014.01b7129-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/py-rnp.html
    • 830 days old (needed 5 days)
• gamgi (- to 0.17.5-1)
  • Migration status for gamgi (- to 0.17.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gamgi gtkglext (not considered)
    • Depends: gamgi gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gamgi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 831 days old (needed 5 days)
• grpn (- to 1.4.1-1.1)
  • Migration status for grpn (- to 1.4.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating grpn would introduce bugs in testing: #1075046
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grpn.html
    • 831 days old (needed 5 days)
• catimg (- to 2.7.0-2)
  • Migration status for catimg (- to 2.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating catimg would introduce bugs in testing: #1066339
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/catimg.html
    • 836 days old (needed 5 days)
• xautolock (- to 1:2.2-8)
  • Migration status for xautolock (- to 1:2.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xautolock would introduce bugs in testing: #1070663
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xautolock.html
    • autopkgtest for xautolock/1:2.2-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 837 days old (needed 2 days)
• python-opentimestamps (- to 0.4.2-1)
  • Migration status for python-opentimestamps (- to 0.4.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: python-opentimestamps python-bitcoinlib (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-opentimestamps.html
    • autopkgtest for python-opentimestamps/0.4.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 838 days old (needed 2 days)
• courier-filter-perl (- to 0.200+ds-6)
  • Migration status for courier-filter-perl (- to 0.200+ds-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: courier-filter-perl courier (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier-filter-perl.html
    • autopkgtest for courier-filter-perl/0.200+ds-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 845 days old (needed 5 days)
• openboard (- to 1.6.4+dfsg-1)
  • Migration status for openboard (- to 1.6.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openboard/amd64 has unsatisfiable dependency
    • openboard/arm64 has unsatisfiable dependency
    • openboard/armel has unsatisfiable dependency
    • openboard/armhf has unsatisfiable dependency
    • openboard/i386 has unsatisfiable dependency
    • openboard/mips64el has unsatisfiable dependency
    • openboard/ppc64el has unsatisfiable dependency
    • openboard/riscv64 has unsatisfiable dependency
    • openboard/s390x has unsatisfiable dependency
    • Updating openboard would introduce bugs in testing: #1072442, #1074332
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openboard.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 845 days old (needed 5 days)
• flask-mongoengine (- to 1.0.0-1)
  • Migration status for flask-mongoengine (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flask-mongoengine would introduce bugs in testing: #1061042
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-mongoengine.html
    • 849 days old (needed 5 days)
• dradio (- to 3.8-2.1)
  • Migration status for dradio (- to 3.8-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dradio would introduce bugs in testing: #1057554
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dradio.html
    • 850 days old (needed 5 days)
• subdownloader (- to 2.1.0-5)
  • Migration status for subdownloader (- to 2.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating subdownloader would introduce bugs in testing: #1042355
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/subdownloader.html
    • autopkgtest for subdownloader/2.1.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 850 days old (needed 2 days)
• hashcash (- to 1.22-1)
  • Migration status for hashcash (- to 1.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hashcash would introduce bugs in testing: #1066603
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hashcash.html
    • 851 days old (needed 5 days)
• libextutils-cbuilder-perl (- to 0.280236-2)
  • Migration status for libextutils-cbuilder-perl (- to 0.280236-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libextutils-cbuilder-perl would introduce bugs in testing: #1060712
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/libe/libextutils-cbuilder-perl.html
    • autopkgtest for libextutils-cbuilder-perl/0.280236-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 851 days old (needed 5 days)
• libbio-tools-run-alignment-tcoffee-perl (- to 1.7.4-3)
  • Migration status for libbio-tools-run-alignment-tcoffee-perl (- to 1.7.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libbio-tools-run-alignment-tcoffee-perl/1.7.4-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbio-tools-run-alignment-tcoffee-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 852 days old (needed 5 days)
• python-digitalocean (- to 1.16.0-3)
  • Migration status for python-digitalocean (- to 1.16.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-digitalocean would introduce bugs in testing: #1073401
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-digitalocean.html
    • 853 days old (needed 5 days)
• bcbio (- to 1.2.9-2)
  • Migration status for bcbio (- to 1.2.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bcbio would introduce bugs in testing: #1018312
    • autopkgtest for bcbio/1.2.9-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test in progress
    • Build-Depends(-Arch): bcbio freebayes (not considered)
    • Build-Depends(-Arch): bcbio hts-nim-tools
    • Build-Depends(-Arch): bcbio mosdepth
    • Build-Depends(-Arch): bcbio snpeff (not considered)
    • Build-Depends(-Arch): bcbio umis (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 854 days old (needed 5 days)
• xzoom (- to 0.3-27)
  • Migration status for xzoom (- to 0.3-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xzoom would introduce bugs in testing: #1075693
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xzoom.html
    • 854 days old (needed 5 days)
• bmf (- to 0.9.4-13)
  • Migration status for bmf (- to 0.9.4-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bmf would introduce bugs in testing: #1074850
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bmf.html
    • autopkgtest for bmf/0.9.4-13: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 855 days old (needed 5 days)
• phabricator (- to 0~git20220903-2)
  • Migration status for phabricator (- to 0~git20220903-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phabricator would introduce bugs in testing: #1038843
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phabricator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 857 days old (needed 5 days)
• ruby-elasticsearch-model (- to 7.2.1-1)
  • Migration status for ruby-elasticsearch-model (- to 7.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-elasticsearch-model would introduce bugs in testing: #1064751
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-elasticsearch-model.html
    • autopkgtest for ruby-elasticsearch-model/7.2.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 860 days old (needed 5 days)
• jverein (- to 2.8.19+dfsg-1)
  • Migration status for jverein (- to 2.8.19+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): jverein jollyday (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jverein.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 863 days old (needed 5 days)
• smlnj (- to 110.79-8)
  • Migration status for smlnj (- to 110.79-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smlnj would introduce bugs in testing: #1075518
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smlnj.html
    • 863 days old (needed 5 days)
• dvi2ps (- to 5.1j-1.5)
  • Migration status for dvi2ps (- to 5.1j-1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dvi2ps would introduce bugs in testing: #1066362
    • Build-Depends(-Arch): dvi2ps vflib3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvi2ps.html
    • 864 days old (needed 5 days)
• nautilus-image-converter (- to 0.4.0-2)
  • Migration status for nautilus-image-converter (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nautilus-image-converter would introduce bugs in testing: #1074743
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus-image-converter.html
    • 864 days old (needed 5 days)
• vflib3 (- to 3.7.2+dfsg-0.1)
  • Migration status for vflib3 (- to 3.7.2+dfsg-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vflib3 would introduce bugs in testing: #1075620
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vflib3.html
    • 866 days old (needed 5 days)
• jzmq (- to 3.1.0-16)
  • Migration status for jzmq (- to 3.1.0-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jzmq would introduce bugs in testing: #1053044
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jzmq.html
    • 869 days old (needed 5 days)
• netris (- to 0.52-11)
  • Migration status for netris (- to 0.52-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netris would introduce bugs in testing: #1075313
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netris.html
    • 871 days old (needed 5 days)
• php-fdomdocument (- to 1.6.7-2)
  • Migration status for php-fdomdocument (- to 1.6.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-fdomdocument would introduce bugs in testing: #1082448, #813866
    • autopkgtest for php-fdomdocument/1.6.7-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-fdomdocument pdepend (not considered)
    • Build-Depends(-Arch): php-fdomdocument php-codesniffer (not considered)
    • Build-Depends(-Arch): php-fdomdocument phpcpd (not considered)
    • Build-Depends(-Arch): php-fdomdocument phploc (not considered)
    • Build-Depends(-Arch): php-fdomdocument phpmd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fdomdocument.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 877 days old (needed 5 days)
• phpdox (- to 0.12.0-6)
  • Migration status for phpdox (- to 0.12.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • phpdox/amd64 has unsatisfiable dependency
    • phpdox/arm64 has unsatisfiable dependency
    • Updating phpdox would introduce bugs in testing: #1082485, #813861
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/phpdox.html
    • Build-Depends(-Arch): phpdox php-codesniffer (not considered)
    • Build-Depends(-Arch): phpdox php-fdomdocument (not considered)
    • Build-Depends(-Arch): phpdox php-fxsl (not considered)
    • Build-Depends(-Arch): phpdox phpcpd (not considered)
    • Build-Depends(-Arch): phpdox phploc (not considered)
    • Build-Depends(-Arch): phpdox phpmd (not considered)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 877 days old (needed 5 days)
• eclipse-titan (- to 8.2.0-1)
  • Migration status for eclipse-titan (- to 8.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • eclipse-titan/amd64 has unsatisfiable dependency
    • eclipse-titan/arm64 has unsatisfiable dependency
    • eclipse-titan/armel has unsatisfiable dependency
    • eclipse-titan/armhf has unsatisfiable dependency
    • eclipse-titan/i386 has unsatisfiable dependency
    • eclipse-titan/mips64el has unsatisfiable dependency
    • eclipse-titan/ppc64el has unsatisfiable dependency
    • eclipse-titan/riscv64 has unsatisfiable dependency
    • eclipse-titan/s390x has unsatisfiable dependency
    • Updating eclipse-titan would introduce bugs in testing: #1071679, #1089251
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-titan.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 881 days old (needed 5 days)
• qreator (- to 16.06.1-7.1)
  • Migration status for qreator (- to 16.06.1-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qreator would introduce bugs in testing: #1058246
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qreator.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 881 days old (needed 5 days)
• xserver-xorg-video-tdfx (- to 1:1.5.0-5)
  • Migration status for xserver-xorg-video-tdfx (- to 1:1.5.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-tdfx would introduce bugs in testing: #1087036
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-tdfx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 881 days old (needed 5 days)
• bing (- to 1.3.5-5)
  • Migration status for bing (- to 1.3.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bing would introduce bugs in testing: #1054398, #1071791
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bing.html
    • 882 days old (needed 5 days)
• xserver-xorg-input-aiptek (- to 1:1.4.1-4)
  • Migration status for xserver-xorg-input-aiptek (- to 1:1.4.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-input-aiptek would introduce bugs in testing: #1075678
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-input-aiptek.html
    • 882 days old (needed 5 days)
• xserver-xorg-input-mutouch (- to 1:1.3.0-3)
  • Migration status for xserver-xorg-input-mutouch (- to 1:1.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-input-mutouch would introduce bugs in testing: #1075681
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-input-mutouch.html
    • 882 days old (needed 5 days)
• sagetex (- to 3.6.1+ds-1)
  • Migration status for sagetex (- to 3.6.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sagetex/3.6.1+ds-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): sagetex sagemath (not considered)
    • Depends: sagetex sagemath (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sagetex.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 886 days old (needed 5 days)
• nextepc (- to 0.3.10+nods-4.2)
  • Migration status for nextepc (- to 0.3.10+nods-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nextepc would introduce bugs in testing: #1086105
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nextepc.html
    • autopkgtest for nextepc/0.3.10+nods-4.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 888 days old (needed 2 days)
• php-easyrdf (- to 1.0.0-3)
  • Migration status for php-easyrdf (- to 1.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-easyrdf would introduce bugs in testing: #1082446
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-easyrdf.html
    • autopkgtest for php-easyrdf/1.0.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 892 days old (needed 5 days)
• node-leveldown (- to 5.6.0+dfsg-4)
  • Migration status for node-leveldown (- to 5.6.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-leveldown would introduce bugs in testing: #1064558
    • autopkgtest for node-leveldown/5.6.0+dfsg-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-leveldown.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 897 days old (needed 5 days)
• gnome-subtitles (- to 1.8-1)
  • Migration status for gnome-subtitles (- to 1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-subtitles would introduce bugs in testing: #1053529, #1067191, #1069308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-subtitles.html
    • 903 days old (needed 5 days)
• xstow (- to 1.1.0-1)
  • Migration status for xstow (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xstow would introduce bugs in testing: #1075685
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xstow.html
    • 909 days old (needed 5 days)
• ruby-grape-logging (- to 1.8.4-1)
  • Migration status for ruby-grape-logging (- to 1.8.4-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.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 913 days old (needed 2 days)
• tilem (- to 2.0-5)
  • Migration status for tilem (- to 2.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tilem would introduce bugs in testing: #1075572
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tilem.html
    • 913 days old (needed 5 days)
• node-mock-fs (- to 5.1.4-1)
  • Migration status for node-mock-fs (- to 5.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-mock-fs would introduce bugs in testing: #1072601
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mock-fs.html
    • autopkgtest for node-mock-fs/5.1.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 914 days old (needed 5 days)
• diet-ng (- to 1.8.1-3)
  • Migration status for diet-ng (- to 1.8.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: diet-ng ldc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/diet-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 915 days old (needed 5 days)
• debian-design (- to 3.0.27)
  • Migration status for debian-design (- to 3.0.27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • design-desktop-graphics/amd64 has unsatisfiable dependency
    • design-desktop-graphics/arm64 has unsatisfiable dependency
    • Updating debian-design would introduce bugs in testing: #1081074, #1088060
    • debian-design unsatisfiable Build-Depends(-Arch) on amd64: boxer-data (<< 10.10)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-design.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 916 days old (needed 5 days)
• medialibrary (- to 0.12.3-1)
  • Migration status for medialibrary (- to 0.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating medialibrary would introduce bugs in testing: #1042710, #949532
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/medialibrary.html
    • 918 days old (needed 5 days)
• isochron (- to 0.9~rc4-1)
  • Migration status for isochron (- to 0.9~rc4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating isochron would introduce bugs in testing: #1069513
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/isochron.html
    • 924 days old (needed 5 days)
• xir (- to 2.5-1)
  • Migration status for xir (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libxir-utils/armel has unsatisfiable dependency
    • libxir2/armel has unsatisfiable dependency
    • libxir-utils/armhf has unsatisfiable dependency
    • libxir2/armhf has unsatisfiable dependency
    • Updating xir would introduce bugs in testing: #1037901
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xir.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 924 days old (needed 5 days)
• haskell-hindent (- to 5.3.4-1)
  • Migration status for haskell-hindent (- to 5.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hindent-dev/amd64 has unsatisfiable dependency
    • libghc-hindent-doc/amd64 has unsatisfiable dependency
    • libghc-hindent-prof/amd64 has unsatisfiable dependency
    • libghc-hindent-dev/arm64 has unsatisfiable dependency
    • libghc-hindent-doc/arm64 has unsatisfiable dependency
    • libghc-hindent-prof/arm64 has unsatisfiable dependency
    • libghc-hindent-dev/armel has unsatisfiable dependency
    • libghc-hindent-prof/armel has unsatisfiable dependency
    • libghc-hindent-dev/armhf has unsatisfiable dependency
    • libghc-hindent-prof/armhf has unsatisfiable dependency
    • libghc-hindent-dev/i386 has unsatisfiable dependency
    • libghc-hindent-prof/i386 has unsatisfiable dependency
    • libghc-hindent-dev/mips64el has unsatisfiable dependency
    • libghc-hindent-prof/mips64el has unsatisfiable dependency
    • libghc-hindent-dev/ppc64el has unsatisfiable dependency
    • libghc-hindent-prof/ppc64el has unsatisfiable dependency
    • libghc-hindent-dev/riscv64 has unsatisfiable dependency
    • libghc-hindent-prof/riscv64 has unsatisfiable dependency
    • libghc-hindent-dev/s390x has unsatisfiable dependency
    • libghc-hindent-prof/s390x has unsatisfiable dependency
    • Updating haskell-hindent would introduce bugs in testing: #1053982
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hindent.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 928 days old (needed 5 days)
• haskell-x509-util (- to 1.6.6-1)
  • Migration status for haskell-x509-util (- to 1.6.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-x509-util would introduce bugs in testing: #1082922
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-x509-util.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 932 days old (needed 5 days)
• diceware (- to 0.10-2)
  • Migration status for diceware (- to 0.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating diceware would introduce bugs in testing: #1090096
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/diceware.html
    • autopkgtest for diceware/0.10-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 939 days old (needed 2 days)
• gcc-11-doc (- to 11.3.0-1)
  • Migration status for gcc-11-doc (- to 11.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-11-doc would introduce bugs in testing: #1057560
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 940 days old (needed 5 days)
• ncftp (- to 2:3.2.6-1)
  • Migration status for ncftp (- to 2:3.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ncftp would introduce bugs in testing: #1066410
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ncftp.html
    • 941 days old (needed 5 days)
• node-multiparty (- to 4.2.3-2)
  • Migration status for node-multiparty (- to 4.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-multiparty would introduce bugs in testing: #1072764
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-multiparty.html
    • autopkgtest for node-multiparty/blocked-on-ci-infra: amd64: Ignored failure, arm64: Ignored failure, armel: Ignored failure, armhf: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, riscv64: Ignored failure, s390x: Ignored failure
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 941 days old (needed 5 days)
• parmetis (- to 4.0.3-7)
  • Migration status for parmetis (- to 4.0.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating parmetis would introduce bugs in testing: #1080199
    • autopkgtest for parmetis/4.0.3-7: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 941 days old (needed 5 days)
• php-horde-data (- to 2.1.5-3)
  • Migration status for php-horde-data (- to 2.1.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-data would introduce bugs in testing: #1089772
    • autopkgtest for php-horde-data/2.1.5-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-data php-horde-mime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-data.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 947 days old (needed 5 days)
• php-horde-rpc (- to 2.1.9-2)
  • Migration status for php-horde-rpc (- to 2.1.9-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-rpc php-horde-dav (not considered)
    • Invalidated by dependency
    • Depends: php-horde-rpc php-horde-core (not considered)
    • Depends: php-horde-rpc php-horde-perms (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-rpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 951 days old (needed 5 days)
• tboot (- to 1.10.5-4)
  • Migration status for tboot (- to 1.10.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tboot would introduce bugs in testing: #1075551
    • autopkgtest for tboot/1.10.5-4: amd64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tboot.html
    • 957 days old (needed 5 days)
• ruby-eb (- to 2.6-4)
  • Migration status for ruby-eb (- to 2.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-eb would introduce bugs in testing: #1075457
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-eb.html
    • 958 days old (needed 5 days)
• dvbcut (- to 0.7.4-1)
  • Migration status for dvbcut (- to 0.7.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dvbcut/amd64 has unsatisfiable dependency
    • dvbcut/arm64 has unsatisfiable dependency
    • dvbcut/armel has unsatisfiable dependency
    • dvbcut/armhf has unsatisfiable dependency
    • dvbcut/i386 has unsatisfiable dependency
    • dvbcut/mips64el has unsatisfiable dependency
    • dvbcut/ppc64el has unsatisfiable dependency
    • dvbcut/riscv64 has unsatisfiable dependency
    • dvbcut/s390x has unsatisfiable dependency
    • Updating dvbcut would introduce bugs in testing: #1072411
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvbcut.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 962 days old (needed 5 days)
• ippsample (- to 0.0~git20220607.72f89b3-1)
  • Migration status for ippsample (- to 0.0~git20220607.72f89b3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ippsample/armel has unsatisfiable dependency
    • ippsample/armhf has unsatisfiable dependency
    • Updating ippsample would introduce bugs in testing: #1042570, #1069333
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ippsample.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 968 days old (needed 5 days)
• quark-sphinx-theme (- to 0.5.1-3)
  • Migration status for quark-sphinx-theme (- to 0.5.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quark-sphinx-theme would introduce bugs in testing: #1042679
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quark-sphinx-theme.html
    • 968 days old (needed 5 days)
• php-sql-formatter (- to 1.2.17+dct1.1.3-1)
  • Migration status for php-sql-formatter (- to 1.2.17+dct1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sql-formatter would introduce bugs in testing: #1064641, #1073571
    • autopkgtest for php-sql-formatter/1.2.17+dct1.1.3-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sql-formatter.html
    • 969 days old (needed 5 days)
• gamehub (- to 0.16.3-2-master+ds-1)
  • Migration status for gamehub (- to 0.16.3-2-master+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gamehub/amd64 has unsatisfiable dependency
    • gamehub/arm64 has unsatisfiable dependency
    • gamehub/armel has unsatisfiable dependency
    • gamehub/armhf has unsatisfiable dependency
    • gamehub/i386 has unsatisfiable dependency
    • gamehub/mips64el has unsatisfiable dependency
    • gamehub/ppc64el has unsatisfiable dependency
    • gamehub/riscv64 has unsatisfiable dependency
    • gamehub/s390x has unsatisfiable dependency
    • Updating gamehub would introduce bugs in testing: #1063232
    • gamehub unsatisfiable Build-Depends(-Arch) on amd64: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on arm64: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on armel: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on armhf: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on i386: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on mips64el: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on ppc64el: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on riscv64: libwebkit2gtk-4.0-dev
    • gamehub unsatisfiable Build-Depends(-Arch) on s390x: libwebkit2gtk-4.0-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gamehub.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 973 days old (needed 5 days)
• classified-ads (- to 0.15-1)
  • Migration status for classified-ads (- to 0.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • classified-ads/amd64 has unsatisfiable dependency
    • classified-ads/arm64 has unsatisfiable dependency
    • classified-ads/armel has unsatisfiable dependency
    • classified-ads/armhf has unsatisfiable dependency
    • classified-ads/i386 has unsatisfiable dependency
    • classified-ads/mips64el has unsatisfiable dependency
    • classified-ads/ppc64el has unsatisfiable dependency
    • classified-ads/s390x has unsatisfiable dependency
    • Updating classified-ads would introduce bugs in testing: #1076686, #1077359, #1091838
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/classified-ads.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 975 days old (needed 5 days)
• howdoi (- to 1.1.9-1.1)
  • Migration status for howdoi (- to 1.1.9-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating howdoi would introduce bugs in testing: #1051370
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/howdoi.html
    • autopkgtest for howdoi/1.1.9-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 975 days old (needed 2 days)
• lice5 (- to 1:5.3.0-1.1)
  • Migration status for lice5 (- to 1:5.3.0-1.1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lice5.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 975 days old (needed 5 days)
• php-http-webdav-server (- to 1.0.0RC8-1.1)
  • Migration status for php-http-webdav-server (- to 1.0.0RC8-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-http-webdav-server would introduce bugs in testing: #1065717
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-http-webdav-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 975 days old (needed 5 days)
• php-letodms-core (- to 3.4.2-1.1)
  • Migration status for php-letodms-core (- to 3.4.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-letodms-core would introduce bugs in testing: #1065716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-letodms-core.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 975 days old (needed 5 days)
• php-mdb2 (- to 2.5.0b5-2.1)
  • Migration status for php-mdb2 (- to 2.5.0b5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-mdb2 would introduce bugs in testing: #1065705
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mdb2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 975 days old (needed 5 days)
• php-mdb2-driver-mysql (- to 1.5.0b4-2.1)
  • Migration status for php-mdb2-driver-mysql (- to 1.5.0b4-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-mdb2-driver-mysql php-mdb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mdb2-driver-mysql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 975 days old (needed 5 days)
• php-mdb2-driver-pgsql (- to 1.5.0b4-2.1)
  • Migration status for php-mdb2-driver-pgsql (- to 1.5.0b4-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-mdb2-driver-pgsql php-mdb2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-mdb2-driver-pgsql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 975 days old (needed 5 days)
• php-net-dime (- to 1.0.2-3.1)
  • Migration status for php-net-dime (- to 1.0.2-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-dime would introduce bugs in testing: #1065719
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-dime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 975 days old (needed 5 days)
• php-net-publicsuffix (- to 0.2-1.1)
  • Migration status for php-net-publicsuffix (- to 0.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-publicsuffix would introduce bugs in testing: #1090260
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-publicsuffix.html
    • 975 days old (needed 5 days)
• ruby-devise-token-authenticatable (- to 0.5.2-1.1)
  • Migration status for ruby-devise-token-authenticatable (- to 0.5.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-devise-token-authenticatable ruby-devise (not considered)
    • Depends: ruby-devise-token-authenticatable ruby-devise (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-devise-token-authenticatable.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 975 days old (needed 5 days)
• python-pyepsg (- to 0.4.0-1)
  • Migration status for python-pyepsg (- to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyepsg would introduce bugs in testing: #1033851
    • autopkgtest for python-pyepsg/0.4.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyepsg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 978 days old (needed 5 days)
• ruby-backbone-on-rails (- to 1.4.1+dfsg-1)
  • Migration status for ruby-backbone-on-rails (- to 1.4.1+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-backbone-on-rails ruby-rails-assets-underscore (not considered)
    • Depends: ruby-backbone-on-rails ruby-rails-assets-underscore (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-backbone-on-rails.html
    • autopkgtest for ruby-backbone-on-rails/1.4.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 986 days old (needed 2 days)
• ruby-entypo-rails (- to 3.0.0-4)
  • Migration status for ruby-entypo-rails (- to 3.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-entypo-rails would introduce bugs in testing: #1094819
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-entypo-rails.html
    • autopkgtest for ruby-entypo-rails/3.0.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 986 days old (needed 2 days)
• ruby-rails-assets-markdown-it (- to 8.4.2-6)
  • Migration status for ruby-rails-assets-markdown-it (- to 8.4.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-markdown-it would introduce bugs in testing: #1095463
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-markdown-it.html
    • autopkgtest for ruby-rails-assets-markdown-it/8.4.2-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 986 days old (needed 2 days)
• rust-ioctl-sys (- to 0.8.0-1)
  • Migration status for rust-ioctl-sys (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ioctl-sys/0.8.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ioctl-sys.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 987 days old (needed 5 days)
• sbt-ivy (- to 2.4.0~rc1+dfsg-3)
  • Migration status for sbt-ivy (- to 2.4.0~rc1+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sbt-ivy sbt-serialization (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbt-ivy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 987 days old (needed 5 days)
• pfqueue (- to 0.5.6-9.2)
  • Migration status for pfqueue (- to 0.5.6-9.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pfqueue would introduce bugs in testing: #1066631
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pfqueue.html
    • 994 days old (needed 5 days)
• lwjgl (- to 2.9.3+dfsg-6)
  • Migration status for lwjgl (- to 2.9.3+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lwjgl jinput (not considered)
    • Depends: lwjgl jinput (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lwjgl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 997 days old (needed 5 days)
• python-cx-oracle (- to 8.3.0-3)
  • Migration status for python-cx-oracle (- to 8.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): python-cx-oracle odpic (not considered)
    • Depends: python-cx-oracle odpic (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for python-cx-oracle/8.3.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 999 days old (needed 5 days)
• provean (- to 1.1.5+ds-2)
  • Migration status for provean (- to 1.1.5+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating provean would introduce bugs in testing: #1042769
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/provean.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1002 days old (needed 5 days)
• pinfo (- to 0.6.13-1.3)
  • Migration status for pinfo (- to 0.6.13-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pinfo would introduce bugs in testing: #1077605, #1093745
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pinfo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1005 days old (needed 5 days)
• apertium-es-ro (- to 0.7.5-1)
  • Migration status for apertium-es-ro (- to 0.7.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-es-ro would introduce bugs in testing: #1060980
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-es-ro.html
    • 1008 days old (needed 5 days)
• apertium-isl-eng (- to 0.1.2-1)
  • Migration status for apertium-isl-eng (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-isl-eng would introduce bugs in testing: #1061014
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-isl-eng.html
    • 1008 days old (needed 5 days)
• apertium-oc-es (- to 1.0.8-1)
  • Migration status for apertium-oc-es (- to 1.0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-oc-es would introduce bugs in testing: #1060956
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-oc-es.html
    • 1008 days old (needed 5 days)
• cmtk (- to 3.3.1p2+dfsg-2)
  • Migration status for cmtk (- to 3.3.1p2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cmtk would introduce bugs in testing: #1077441
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cmtk.html
    • 1008 days old (needed 5 days)
• apertium-eo-en (- to 1.0.2-1)
  • Migration status for apertium-eo-en (- to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-eo-en would introduce bugs in testing: #1060984
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-eo-en.html
    • 1010 days old (needed 5 days)
• apertium-eu-en (- to 0.3.3-1)
  • Migration status for apertium-eu-en (- to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-eu-en would introduce bugs in testing: #1061040
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-eu-en.html
    • 1010 days old (needed 5 days)
• openjdk-11-jre-dcevm (- to 11.0.15+1-1)
  • Migration status for openjdk-11-jre-dcevm (- to 11.0.15+1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for openjdk-11-jre-dcevm/11.0.15+1-1: amd64: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): openjdk-11-jre-dcevm openjdk-11 (not considered)
    • Depends: openjdk-11-jre-dcevm openjdk-11 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11-jre-dcevm.html
    • New but not reproducible on amd64 - info ♻
    • 1016 days old (needed 5 days)
• r-cran-zelig (- to 5.1.7-3)
  • Migration status for r-cran-zelig (- to 5.1.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-zelig/5.1.7-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-zelig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1019 days old (needed 5 days)
• unburden-home-dir (- to 0.4.2)
  • Migration status for unburden-home-dir (- to 0.4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unburden-home-dir would introduce bugs in testing: #1073114
    • unburden-home-dir unsatisfiable Build-Depends(-Arch) on amd64: pcregrep
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unburden-home-dir.html
    • autopkgtest for unburden-home-dir/0.4.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1023 days old (needed 2 days)
• coyote (- to 2022.04.12-1)
  • Migration status for coyote (- to 2022.04.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating coyote would introduce bugs in testing: #1073520, #1090204
    • autopkgtest for coyote/2022.04.12-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, riscv64: Regression or new test ♻
    • autopkgtest for coyote/blocked-on-ci-infra: ppc64el: Ignored failure
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coyote.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1036 days old (needed 5 days)
• courier-authlib (- to 0.71.4-1)
  • Migration status for courier-authlib (- to 0.71.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating courier-authlib would introduce bugs in testing: #1086097, #987009
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier-authlib.html
    • autopkgtest for courier-authlib/0.71.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1037 days old (needed 2 days)
• redmine-plugin-custom-css (- to 0.1.7+dfsg-1.1)
  • Migration status for redmine-plugin-custom-css (- to 0.1.7+dfsg-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-custom-css redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redmine-plugin-custom-css.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1038 days old (needed 5 days)
• synfigstudio (- to 1.5.1-1)
  • Migration status for synfigstudio (- to 1.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): synfigstudio synfig (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/synfigstudio.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1039 days old (needed 5 days)
• kubernetes (- to 1.20.5+really1.20.2-1.1)
  • Migration status for kubernetes (- to 1.20.5+really1.20.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kubernetes would introduce bugs in testing: #1055411
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kubernetes.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1040 days old (needed 5 days)
• android-platform-dalvik (- to 10.0.0+r36-4)
  • Migration status for android-platform-dalvik (- to 10.0.0+r36-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: android-platform-dalvik android-framework-23 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-dalvik.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1042 days old (needed 5 days)
• cvsdelta (- to 1.7.0-8)
  • Migration status for cvsdelta (- to 1.7.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cvsdelta would introduce bugs in testing: #1094443
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cvsdelta.html
    • autopkgtest for cvsdelta/1.7.0-8: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1044 days old (needed 5 days)
• ruby-fakeredis (- to 0.8.0-7)
  • Migration status for ruby-fakeredis (- to 0.8.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-fakeredis would introduce bugs in testing: #1084361
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-fakeredis.html
    • autopkgtest for ruby-fakeredis/0.8.0-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1045 days old (needed 2 days)
• gtk-vector-screenshot (- to 0.3.3-2)
  • Migration status for gtk-vector-screenshot (- to 0.3.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtk-vector-screenshot would introduce bugs in testing: #1075051
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk-vector-screenshot.html
    • 1047 days old (needed 5 days)
• ruby-devise-two-factor (- to 4.0.2-1)
  • Migration status for ruby-devise-two-factor (- to 4.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-devise-two-factor would introduce bugs in testing: #1082382, #1084360
    • autopkgtest for ruby-devise-two-factor/4.0.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-devise-two-factor ruby-devise
    • Depends: ruby-devise-two-factor ruby-devise
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-devise-two-factor.html
    • 1048 days old (needed 5 days)
• hackage-tracker (- to 0.1.1)
  • Migration status for hackage-tracker (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hackage-tracker would introduce bugs in testing: #1091077
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hackage-tracker.html
    • 1050 days old (needed 5 days)
• automake-1.16 (- to 1:1.16.5-1.3)
  • Migration status for automake-1.16 (- to 1:1.16.5-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • automake-1.16 has no binaries on any arch
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1062 days old (needed 5 days)
• prelude-lml (- to 5.2.0-3)
  • Migration status for prelude-lml (- to 5.2.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): prelude-lml libprelude (not considered)
    • Depends: prelude-lml libprelude (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prelude-lml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1067 days old (needed 5 days)
• qiskit-terra (- to 0.12.0-4)
  • Migration status for qiskit-terra (- to 0.12.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-qiskit-terra/amd64 has unsatisfiable dependency
    • python3-qiskit-terra/arm64 has unsatisfiable dependency
    • python3-qiskit-terra/armel has unsatisfiable dependency
    • python3-qiskit-terra/armhf has unsatisfiable dependency
    • python3-qiskit-terra/i386 has unsatisfiable dependency
    • python3-qiskit-terra/mips64el has unsatisfiable dependency
    • python3-qiskit-terra/ppc64el has unsatisfiable dependency
    • python3-qiskit-terra/s390x has unsatisfiable dependency
    • Updating qiskit-terra would introduce bugs in testing: #1027203, #1056878
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/q/qiskit-terra.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 1068 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:
    • librust-weedle-dev/amd64 has unsatisfiable dependency
    • librust-weedle-dev/arm64 has unsatisfiable dependency
    • librust-weedle-dev/armel has unsatisfiable dependency
    • librust-weedle-dev/armhf has unsatisfiable dependency
    • librust-weedle-dev/i386 has unsatisfiable dependency
    • librust-weedle-dev/mips64el has unsatisfiable dependency
    • librust-weedle-dev/ppc64el has unsatisfiable dependency
    • librust-weedle-dev/riscv64 has unsatisfiable dependency
    • librust-weedle-dev/s390x has unsatisfiable dependency
    • Updating rust-weedle would introduce bugs in testing: #1007026
    • rust-weedle unsatisfiable Build-Depends(-Arch) on amd64: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on arm64: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on armel: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on armhf: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on i386: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on mips64el: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on ppc64el: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on riscv64: librust-nom-4+default-dev
    • rust-weedle unsatisfiable Build-Depends(-Arch) on s390x: librust-nom-4+default-dev
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-weedle.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1073 days old (needed 5 days)
• kickoff (- to 0.1.1)
  • Migration status for kickoff (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kickoff would introduce bugs in testing: #1091059
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kickoff.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1081 days old (needed 5 days)
• emacs-lintian (- to 0.1.1)
  • Migration status for emacs-lintian (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-lintian would introduce bugs in testing: #1077105
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-lintian.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1086 days old (needed 5 days)
• peony-extensions (- to 3.2.4-1)
  • Migration status for peony-extensions (- to 3.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): peony-extensions peony (not considered)
    • Depends: peony-extensions peony (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/peony-extensions.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1086 days old (needed 5 days)
• wordpress-plugin-http-authentication (- to 4.6-2)
  • Migration status for wordpress-plugin-http-authentication (- to 4.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wordpress-plugin-http-authentication wordpress (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wordpress-plugin-http-authentication.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1090 days old (needed 5 days)
• freeart (- to 3.3.0+ds1-3)
  • Migration status for freeart (- to 3.3.0+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-freeart/amd64 has unsatisfiable dependency
    • python3-freeart/arm64 has unsatisfiable dependency
    • python3-freeart/armel has unsatisfiable dependency
    • python3-freeart/armhf has unsatisfiable dependency
    • python3-freeart/i386 has unsatisfiable dependency
    • python3-freeart/mips64el has unsatisfiable dependency
    • python3-freeart/ppc64el has unsatisfiable dependency
    • Updating freeart would introduce bugs in testing: #1013606, #1056801
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/freeart.html
    • Build-Depends(-Arch): freeart silx (not considered)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 1092 days old (needed 5 days)
• node-functional.js (- to 0.8.0-1)
  • Migration status for node-functional.js (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-functional.js would introduce bugs in testing: #1014605
    • Not built on buildd: arch all binaries uploaded by stephanlachnit@protonmail.com, a new source-only upload is needed to allow migration
    • autopkgtest for node-functional.js/0.8.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test in progress, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-functional.js.html
    • 1096 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
    • autopkgtest for node-grunt-timer/0.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Build-Depends(-Arch): node-grunt-timer node-functional.js (not considered)
    • Depends: node-grunt-timer node-functional.js (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-grunt-timer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1096 days old (needed 5 days)
• xserver-xorg-video-openchrome (- to 1:0.6.0-5)
  • Migration status for xserver-xorg-video-openchrome (- to 1:0.6.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-openchrome would introduce bugs in testing: #1066545
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-openchrome.html
    • 1100 days old (needed 5 days)
• asterisk-flite (- to 3.0-4)
  • Migration status for asterisk-flite (- to 3.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): asterisk-flite asterisk (not considered)
    • Depends: asterisk-flite asterisk (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-flite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1103 days old (needed 5 days)
    • Remove hint for (transitive) dependency: uw-imap
• gcc-h8300-hms (- to 1:3.4.6+dfsg2-4.2)
  • Migration status for gcc-h8300-hms (- to 1:3.4.6+dfsg2-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-h8300-hms would introduce bugs in testing: #1081077
    • Build-Depends(-Arch): gcc-h8300-hms binutils-h8300-hms (not considered)
    • Depends: gcc-h8300-hms binutils-h8300-hms (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-h8300-hms.html
    • 1105 days old (needed 5 days)
• tomogui (- to 0.3.1-2)
  • Migration status for tomogui (- to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomogui would introduce bugs in testing: #1069226
    • Not touching package due to block request by sramacher (please contact debian-release if update is needed)
    • Build-Depends(-Arch): tomogui silx (not considered)
    • Depends: tomogui silx (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/tomogui.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 1107 days old (needed 5 days)
• dumpasn1 (- to 20210212-3)
  • Migration status for dumpasn1 (- to 20210212-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dumpasn1 would introduce bugs in testing: #1060766
    • autopkgtest for dumpasn1/20210212-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dumpasn1.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1112 days old (needed 5 days)
• rust-proc-quote (- to 0.4.0-1)
  • Migration status for rust-proc-quote (- to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-proc-quote/0.4.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proc-quote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1112 days old (needed 5 days)
• mysqmail (- to 0.4.9-10.3)
  • Migration status for mysqmail (- to 0.4.9-10.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mysqmail courier (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysqmail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1113 days old (needed 5 days)
• ruby-nokogumbo (- to 2.0.5-1)
  • Migration status for ruby-nokogumbo (- to 2.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-nokogumbo/arm64 has unsatisfiable dependency
    • Updating ruby-nokogumbo would introduce bugs in testing: #1092697
    • autopkgtest for ruby-nokogumbo/2.0.5-1: amd64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-nokogumbo.html
    • uninstallable on arch arm64, not running autopkgtest there
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 1113 days old (needed 5 days)
• ruby-redis-activesupport (- to 5.3.0-1)
  • Migration status for ruby-redis-activesupport (- to 5.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-redis-activesupport would introduce bugs in testing: #1084364
  • 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1118 days old (needed 2 days)
• xcb (- to 2.4-8)
  • Migration status for xcb (- to 2.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xcb would introduce bugs in testing: #1081108
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcb.html
    • 1121 days old (needed 5 days)
• nim-lapper (- to 0.1.7-5)
  • Migration status for nim-lapper (- to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nim-lapper/0.1.7-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): nim-lapper nim (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-lapper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1122 days old (needed 5 days)
• idseq-bench (- to 0.0~git20210602.27fb6dc-1)
  • Migration status for idseq-bench (- to 0.0~git20210602.27fb6dc-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for idseq-bench/0.0~git20210602.27fb6dc-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/idseq-bench.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1123 days old (needed 5 days)
• growlight (- to 1.2.38-5)
  • Migration status for growlight (- to 1.2.38-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): growlight notcurses (not considered)
    • Depends: growlight notcurses (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/growlight.html
    • autopkgtest for growlight/1.2.38-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1128 days old (needed 2 days)
• bitlbee-mastodon (- to 1.4.5-1)
  • Migration status for bitlbee-mastodon (- to 1.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): bitlbee-mastodon bitlbee (not considered)
    • Depends: bitlbee-mastodon bitlbee (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bitlbee-mastodon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1129 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: #1085472, #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/blocked-on-ci-infra: amd64: Ignored failure, arm64: Ignored failure, armel: Ignored failure, armhf: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, riscv64: Ignored failure, s390x: Ignored failure
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1132 days old (needed 5 days)
• mlton (- to 20210117+dfsg-3)
  • Migration status for mlton (- to 20210117+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mlton would introduce bugs in testing: #917644, #998156
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch arm64 binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch armel binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch armhf binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch i386 binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch mips64el binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch s390x binaries uploaded by ryanakca@kubuntu.org
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlton.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1134 days old (needed 5 days)
• ruby-gon (- to 6.4.0-2)
  • Migration status for ruby-gon (- to 6.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gon would introduce bugs in testing: #1077431
    • autopkgtest for ruby-gon/6.4.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gon.html
    • 1135 days old (needed 5 days)
• tf (- to 1:4.0s1-21.1)
  • Migration status for tf (- to 1:4.0s1-21.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tf would introduce bugs in testing: #1066561
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tf.html
    • 1135 days old (needed 5 days)
• mhddfs (- to 0.1.39+nmu2)
  • Migration status for mhddfs (- to 0.1.39+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mhddfs would introduce bugs in testing: #953919
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mhddfs.html
    • 1137 days old (needed 5 days)
• python-duckpy (- to 3.2.0-3)
  • Migration status for python-duckpy (- to 3.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-duckpy would introduce bugs in testing: #1059642
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-duckpy.html
    • autopkgtest for python-duckpy/3.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1137 days old (needed 2 days)
• tiledarray (- to 1.0.0-1)
  • Migration status for tiledarray (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tiledarray would introduce bugs in testing: #1087560
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): tiledarray btas (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiledarray.html
    • 1137 days old (needed 5 days)
• php-fxsl (- to 1.1.1-6)
  • Migration status for php-fxsl (- to 1.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-fxsl would introduce bugs in testing: #813865
    • autopkgtest for php-fxsl/1.1.1-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-fxsl pdepend (not considered)
    • Build-Depends(-Arch): php-fxsl php-codesniffer (not considered)
    • Build-Depends(-Arch): php-fxsl phpcpd (not considered)
    • Build-Depends(-Arch): php-fxsl phploc (not considered)
    • Build-Depends(-Arch): php-fxsl phpmd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fxsl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1139 days old (needed 5 days)
• openttd-opengfx (- to 7.1-1)
  • Migration status for openttd-opengfx (- to 7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openttd-opengfx would introduce bugs in testing: #1090256
    • Build-Depends(-Arch): openttd-opengfx nml (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openttd-opengfx.html
    • 1143 days old (needed 5 days)
• ssed (- to 3.62-8)
  • Migration status for ssed (- to 3.62-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ssed would introduce bugs in testing: #1066373
    • autopkgtest for ssed/3.62-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/ssed.html
    • 1143 days old (needed 5 days)
• ippl (- to 1.4.14-13)
  • Migration status for ippl (- to 1.4.14-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ippl would introduce bugs in testing: #1066218
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ippl.html
    • 1147 days old (needed 5 days)
• magic (- to 8.3.105+ds.1-1.1)
  • Migration status for magic (- to 8.3.105+ds.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating magic would introduce bugs in testing: #1075249
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magic.html
    • 1150 days old (needed 5 days)
• kore (- to 4.1.0-6)
  • Migration status for kore (- to 4.1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kore would introduce bugs in testing: #1033711, #1081081
    • autopkgtest for kore/4.1.0-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kore.html
    • 1152 days old (needed 5 days)
• lavacli (- to 1.2-1)
  • Migration status for lavacli (- to 1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lavacli would introduce bugs in testing: #1088041
    • autopkgtest for lavacli/1.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lavacli.html
    • 1153 days old (needed 5 days)
• morla (- to 0.16.1-2)
  • Migration status for morla (- to 0.16.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating morla would introduce bugs in testing: #1075286
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/morla.html
    • 1153 days old (needed 5 days)
• pixmap (- to 2.6.6-1)
  • Migration status for pixmap (- to 2.6.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pixmap/armel has unsatisfiable dependency
    • pixmap/armhf has unsatisfiable dependency
    • Updating pixmap would introduce bugs in testing: #1054698
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pixmap.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1154 days old (needed 5 days)
• ruby-gsl (- to 2.1.0.3+dfsg1-5)
  • Migration status for ruby-gsl (- to 2.1.0.3+dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-gsl/amd64 has unsatisfiable dependency
    • ruby-gsl/arm64 has unsatisfiable dependency
    • ruby-gsl/armel has unsatisfiable dependency
    • ruby-gsl/armhf has unsatisfiable dependency
    • ruby-gsl/i386 has unsatisfiable dependency
    • ruby-gsl/mips64el has unsatisfiable dependency
    • ruby-gsl/ppc64el has unsatisfiable dependency
    • ruby-gsl/riscv64 has unsatisfiable dependency
    • ruby-gsl/s390x has unsatisfiable dependency
    • Updating ruby-gsl would introduce bugs in testing: #1075462, #1076659
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-gsl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1167 days old (needed 5 days)
• ruby-puma-worker-killer (- to 0.3.1-3)
  • Migration status for ruby-puma-worker-killer (- to 0.3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-puma-worker-killer would introduce bugs in testing: #1093924
    • autopkgtest for ruby-puma-worker-killer/0.3.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-puma-worker-killer.html
    • 1170 days old (needed 5 days)
• ruby-rails-assets-emojione (- to 2.2.6-7)
  • Migration status for ruby-rails-assets-emojione (- to 2.2.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-emojione would introduce bugs in testing: #1095499
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-emojione.html
    • autopkgtest for ruby-rails-assets-emojione/2.2.6-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1171 days old (needed 2 days)
• ruby-rails-controller-testing (- to 1.0.5-2)
  • Migration status for ruby-rails-controller-testing (- to 1.0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-controller-testing would introduce bugs in testing: #1094552
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-controller-testing.html
    • autopkgtest for ruby-rails-controller-testing/1.0.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1171 days old (needed 2 days)
• ruby-inherited-resources (- to 1.13.0-1)
  • Migration status for ruby-inherited-resources (- to 1.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-inherited-resources would introduce bugs in testing: #1094550
    • Build-Depends(-Arch): ruby-inherited-resources ruby-rails-controller-testing (not considered)
    • Build-Depends(-Arch): ruby-inherited-resources ruby-responders (not considered)
    • Depends: ruby-inherited-resources ruby-responders (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-inherited-resources.html
    • autopkgtest for ruby-inherited-resources/1.13.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1172 days old (needed 2 days)
• php-sabredav (- to 1.8.12-10)
  • Migration status for php-sabredav (- to 1.8.12-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabredav would introduce bugs in testing: #1070597
    • autopkgtest for php-sabredav/1.8.12-10: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): php-sabredav php-sabre-vobject (not considered)
    • Depends: php-sabredav php-sabre-vobject (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabredav.html
    • Reproducible on armhf - info ♻
    • 1175 days old (needed 5 days)
• node-mongodb (- to 3.6.4+~cs11.13.19-2)
  • Migration status for node-mongodb (- to 3.6.4+~cs11.13.19-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-mongodb would introduce bugs in testing: #1033817
    • autopkgtest for node-mongodb/3.6.4+~cs11.13.19-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mongodb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1180 days old (needed 5 days)
• python-rocksdb (- to 0.8.0~rc3-2)
  • Migration status for python-rocksdb (- to 0.8.0~rc3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-rocksdb/amd64 has unsatisfiable dependency
    • python3-rocksdb/arm64 has unsatisfiable dependency
    • python3-rocksdb/i386 has unsatisfiable dependency
    • python3-rocksdb/mips64el has unsatisfiable dependency
    • python3-rocksdb/ppc64el has unsatisfiable dependency
    • python3-rocksdb/s390x has unsatisfiable dependency
    • Updating python-rocksdb would introduce bugs in testing: #1012074, #1056870
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-rocksdb.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1180 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-api-pagination would introduce bugs in testing: #1092690
    • Build-Depends(-Arch): ruby-api-pagination ruby-grape (not considered)
  • 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1180 days old (needed 2 days)
• materialize (- to 1.1.0~alpha+ds-1)
  • Migration status for materialize (- to 1.1.0~alpha+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating materialize would introduce bugs in testing: #1012320
    • materialize unsatisfiable Build-Depends(-Arch) on amd64: libjs-anime
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/materialize.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1181 days old (needed 5 days)
• ruby-responders (- to 3.0.1-2)
  • Migration status for ruby-responders (- to 3.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-responders would introduce bugs in testing: #1095385, #1095456
    • Build-Depends(-Arch): ruby-responders ruby-rails-controller-testing (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-responders.html
    • autopkgtest for ruby-responders/3.0.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1181 days old (needed 2 days)
• node-solid-keychain (- to 0.1.3-3.1)
  • Migration status for node-solid-keychain (- to 0.1.3-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-solid-keychain would introduce bugs in testing: #1071803
    • autopkgtest for node-solid-keychain/0.1.3-3.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
    • Build-Depends(-Arch): node-solid-keychain node-trust-webcrypto (not considered)
    • Depends: node-solid-keychain node-trust-webcrypto (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-solid-keychain.html
    • 1185 days old (needed 5 days)
• ruby-roxml (- to 4.2.0-1)
  • Migration status for ruby-roxml (- to 4.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-roxml would introduce bugs in testing: #1050580
    • autopkgtest for ruby-roxml/4.2.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-roxml.html
    • 1189 days old (needed 5 days)
• jarchivelib (- to 1.2.0-2)
  • Migration status for jarchivelib (- to 1.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jarchivelib would introduce bugs in testing: #1086277
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jarchivelib.html
    • Reproducible on armhf - info ♻
    • 1192 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 or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-intel-go-cpuid.html
    • Reproducible on amd64 - info ♻
    • 1195 days old (needed 5 days)
• reqwest (- to 2.0.5+dfsg-1)
  • Migration status for reqwest (- to 2.0.5+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating reqwest would introduce bugs in testing: #1089900
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/reqwest.html
    • 1197 days old (needed 5 days)
• sbt-launcher-interface (- to 1.0.1-2)
  • Migration status for sbt-launcher-interface (- to 1.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): sbt-launcher-interface scala (not considered)
    • Depends: sbt-launcher-interface scala (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: sbt-launcher-interface scala-xml
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbt-launcher-interface.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1197 days old (needed 5 days)
• ruby-gd (- to 0.8.0-8)
  • Migration status for ruby-gd (- to 0.8.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gd would introduce bugs in testing: #1075461
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gd.html
    • 1200 days old (needed 5 days)
• ruby-serialport (- to 1.3.2-1)
  • Migration status for ruby-serialport (- to 1.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-serialport would introduce bugs in testing: #1075476
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-serialport.html
    • 1204 days old (needed 5 days)
• ruby-github-pages-health-check (- to 1.16.1-3)
  • Migration status for ruby-github-pages-health-check (- to 1.16.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-github-pages-health-check/amd64 has unsatisfiable dependency
    • ruby-github-pages-health-check/arm64 has unsatisfiable dependency
    • Updating ruby-github-pages-health-check would introduce bugs in testing: #1059697
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-github-pages-health-check.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1206 days old (needed 5 days)
• python-librtmp (- to 0.3.0-1.2)
  • Migration status for python-librtmp (- to 0.3.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-librtmp would introduce bugs in testing: #1075416
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-librtmp.html
    • 1209 days old (needed 5 days)
• nim-kexpr (- to 0.0.2-3)
  • Migration status for nim-kexpr (- to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nim-kexpr/0.0.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): nim-kexpr nim (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-kexpr.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1210 days old (needed 5 days)
• libdfp (- to 1.0.16-1)
  • Migration status for libdfp (- to 1.0.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libdfp would introduce bugs in testing: #1077413
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdfp.html
    • Reproducible on i386 - info ♻
    • 1212 days old (needed 5 days)
• idm-console-framework (- to 2.0.0-1)
  • Migration status for idm-console-framework (- 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): idm-console-framework jss (not considered)
    • Depends: idm-console-framework jss (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): idm-console-framework ldapjdk
    • Depends: idm-console-framework ldapjdk
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/idm-console-framework.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1213 days old (needed 5 days)
• utalk (- to 1.0.2-2)
  • Migration status for utalk (- to 1.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating utalk would introduce bugs in testing: #1075611
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/utalk.html
    • 1216 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:
    • prads/amd64 has unsatisfiable dependency
    • prads/arm64 has unsatisfiable dependency
    • prads/armel has unsatisfiable dependency
    • prads/armhf has unsatisfiable dependency
    • prads/i386 has unsatisfiable dependency
    • prads/mips64el has unsatisfiable dependency
    • prads/ppc64el has unsatisfiable dependency
    • prads/s390x has unsatisfiable dependency
    • Updating prads would introduce bugs in testing: #1069335, #1081091, #999984
    • prads unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prads.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 1217 days old (needed 5 days)
• gabedit (- to 2.5.1+ds-1)
  • Migration status for gabedit (- to 2.5.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gabedit/armel has unsatisfiable dependency
    • gabedit/armhf has unsatisfiable dependency
    • Updating gabedit would introduce bugs in testing: #1066984
    • Build-Depends(-Arch): gabedit gtkglext (not considered)
    • Build-Depends(-Arch): gabedit spglib (not considered)
    • Depends: gabedit gtkglext (not considered)
    • Depends: gabedit spglib (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gabedit.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1218 days old (needed 5 days)
• epic5 (- to 2.1.6-1)
  • Migration status for epic5 (- to 2.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • epic5/amd64 has unsatisfiable dependency
    • epic5/arm64 has unsatisfiable dependency
    • epic5/armel has unsatisfiable dependency
    • epic5/armhf has unsatisfiable dependency
    • epic5/i386 has unsatisfiable dependency
    • epic5/mips64el has unsatisfiable dependency
    • epic5/ppc64el has unsatisfiable dependency
    • epic5/riscv64 has unsatisfiable dependency
    • epic5/s390x has unsatisfiable dependency
    • Updating epic5 would introduce bugs in testing: #1066505
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epic5.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1223 days old (needed 5 days)
• anfo (- to 0.98-9)
  • Migration status for anfo (- to 0.98-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • anfo/amd64 has unsatisfiable dependency
    • libanfo0/amd64 has unsatisfiable dependency
    • anfo/arm64 has unsatisfiable dependency
    • libanfo0/arm64 has unsatisfiable dependency
    • anfo/armel has unsatisfiable dependency
    • libanfo0/armel has unsatisfiable dependency
    • anfo/armhf has unsatisfiable dependency
    • libanfo0/armhf has unsatisfiable dependency
    • anfo/i386 has unsatisfiable dependency
    • libanfo0/i386 has unsatisfiable dependency
    • anfo/mips64el has unsatisfiable dependency
    • libanfo0/mips64el has unsatisfiable dependency
    • anfo/ppc64el has unsatisfiable dependency
    • libanfo0/ppc64el has unsatisfiable dependency
    • anfo/s390x has unsatisfiable dependency
    • libanfo0/s390x has unsatisfiable dependency
    • Updating anfo would introduce bugs in testing: #1012893, #1061888
    • anfo unsatisfiable Build-Depends(-Arch) on armel: libelk0
    • anfo unsatisfiable Build-Depends(-Arch) on armhf: libelk0
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/anfo.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 1226 days old (needed 5 days)
• gwc (- to 0.22.05-1)
  • Migration status for gwc (- to 0.22.05-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gwc/armel has unsatisfiable dependency
    • gwc/armhf has unsatisfiable dependency
    • Updating gwc would introduce bugs in testing: #1066364
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gwc.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1228 days old (needed 5 days)
• vim-scripts (- to 20210124.2)
  • Migration status for vim-scripts (- to 20210124.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vim-scripts would introduce bugs in testing: #1051063
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-scripts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1236 days old (needed 5 days)
• node-eslint-plugin-requirejs (- to 4.0.1-1)
  • Migration status for node-eslint-plugin-requirejs (- to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-eslint-plugin-requirejs would introduce bugs in testing: #1060930
    • autopkgtest for node-eslint-plugin-requirejs/4.0.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-eslint-plugin-requirejs.html
    • 1238 days old (needed 5 days)
• async-http-client (- to 2.12.3-1)
  • Migration status for async-http-client (- to 2.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating async-http-client would introduce bugs in testing: #1089228
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/async-http-client.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1244 days old (needed 5 days)
• materia-gtk-theme (- to 20210322-1)
  • Migration status for materia-gtk-theme (- to 20210322-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating materia-gtk-theme would introduce bugs in testing: #970986
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/materia-gtk-theme.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1248 days old (needed 5 days)
• pvpgn (- to 1.8.5-3)
  • Migration status for pvpgn (- to 1.8.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pvpgn would introduce bugs in testing: #1066953
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1248 days old (needed 5 days)
• clues-emacs (- to 1.0.1-3.1)
  • Migration status for clues-emacs (- to 1.0.1-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clues-emacs would introduce bugs in testing: #1077097
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clues-emacs.html
    • autopkgtest for clues-emacs/1.0.1-3.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1250 days old (needed 2 days)
• dwarfutils (- to 20210528-1)
  • Migration status for dwarfutils (- to 20210528-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dwarfutils would introduce bugs in testing: #1065511
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dwarfutils.html
    • autopkgtest for dwarfutils/20210528-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1250 days old (needed 5 days)
• printing-metas (- to 0.20210903)
  • Migration status for printing-metas (- to 0.20210903): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: printing-metas hplip (not considered)
    • Invalidated by dependency
    • Depends: printing-metas gutenprint (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/printing-metas.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1258 days old (needed 5 days)
• libglade2 (- to 1:2.6.4-2.4)
  • Migration status for libglade2 (- to 1:2.6.4-2.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libglade2 would introduce bugs in testing: #895517
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libglade2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1269 days old (needed 5 days)
• libjs-jsxc (- to 3.4.4+dfsg-2)
  • Migration status for libjs-jsxc (- to 3.4.4+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: libjs-jsxc ruby-rails-assets-jquery.slimscroll (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjs-jsxc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1270 days old (needed 5 days)
• ganglia-modules-linux (- to 1.3.6-5)
  • Migration status for ganglia-modules-linux (- to 1.3.6-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ganglia-modules-linux ganglia (not considered)
    • Depends: ganglia-modules-linux ganglia (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganglia-modules-linux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1306 days old (needed 5 days)
• redisearch (- to 1:1.2.2-4)
  • Migration status for redisearch (- to 1:1.2.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating redisearch would introduce bugs in testing: #1091247
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redisearch.html
    • autopkgtest for redisearch/1:1.2.2-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1351 days old (needed 2 days)
• mialmpick (- to 0.2.15-2)
  • Migration status for mialmpick (- to 0.2.15-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mialmpick would introduce bugs in testing: #967880
    • Build-Depends(-Arch): mialmpick gtkglext (not considered)
    • Build-Depends(-Arch): mialmpick libglade2 (not considered)
    • Depends: mialmpick gtkglext (not considered)
    • Depends: mialmpick libglade2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mialmpick.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1352 days old (needed 5 days)
• whizzytex (- to 1.3.7-1)
  • Migration status for whizzytex (- to 1.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating whizzytex would introduce bugs in testing: #1059088
    • autopkgtest for whizzytex/1.3.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whizzytex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1355 days old (needed 5 days)
• scrollz (- to 2.2.3-2)
  • Migration status for scrollz (- to 2.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • scrollz/armel has unsatisfiable dependency
    • scrollz/armhf has unsatisfiable dependency
    • Updating scrollz would introduce bugs in testing: #1066483
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scrollz.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1359 days old (needed 5 days)
• scala (- to 2.11.12-5)
  • Migration status for scala (- to 2.11.12-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scala would introduce bugs in testing: #1091067
    • Build-Depends(-Arch): scala scala-parser-combinators
    • Build-Depends(-Arch): scala scala-xml
    • Depends: scala scala-parser-combinators
    • Depends: scala scala-xml
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scala.html
    • New but not reproducible on i386 - info ♻
    • 1397 days old (needed 5 days)
• dstat (- to 0.7.4-6.1)
  • Migration status for dstat (- to 0.7.4-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dstat would introduce bugs in testing: #1034856
    • autopkgtest for dstat/0.7.4-6.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dstat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1407 days old (needed 5 days)
• gtkglext (- to 1.2.0-11)
  • Migration status for gtkglext (- to 1.2.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtkglext would introduce bugs in testing: #1054392
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtkglext.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1425 days old (needed 5 days)
• gkrellshoot (- to 0.4.4-3)
  • Migration status for gkrellshoot (- to 0.4.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gkrellshoot would introduce bugs in testing: #1075008
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gkrellshoot.html
    • 1444 days old (needed 5 days)
• hotspot (- to 1.3.0-2)
  • Migration status for hotspot (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • hotspot/amd64 has unsatisfiable dependency
    • hotspot/arm64 has unsatisfiable dependency
    • hotspot/armel has unsatisfiable dependency
    • hotspot/armhf has unsatisfiable dependency
    • hotspot/i386 has unsatisfiable dependency
    • hotspot/mips64el has unsatisfiable dependency
    • hotspot/ppc64el has unsatisfiable dependency
    • hotspot/riscv64 has unsatisfiable dependency
    • Updating hotspot would introduce bugs in testing: #1025573, #1033848
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/hotspot.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1453 days old (needed 5 days)
• utox (- to 0.18.1-1)
  • Migration status for utox (- to 0.18.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for utox/0.18.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/utox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1455 days old (needed 5 days)
• qrouter (- to 1.4.71-2)
  • Migration status for qrouter (- to 1.4.71-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qrouter would introduce bugs in testing: #1066488
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qrouter.html
    • autopkgtest for qrouter/1.4.71-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1458 days old (needed 5 days)
• mydumper (- to 0.10.1-1)
  • Migration status for mydumper (- to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mydumper/amd64 has unsatisfiable dependency
    • mydumper/arm64 has unsatisfiable dependency
    • mydumper/armel has unsatisfiable dependency
    • mydumper/armhf has unsatisfiable dependency
    • mydumper/i386 has unsatisfiable dependency
    • mydumper/mips64el has unsatisfiable dependency
    • mydumper/ppc64el has unsatisfiable dependency
    • mydumper/riscv64 has unsatisfiable dependency
    • mydumper/s390x has unsatisfiable dependency
    • Updating mydumper would introduce bugs in testing: #1000014
    • mydumper unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • mydumper unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mydumper.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1464 days old (needed 5 days)
• nattable (- to 2.0.0+dfsg-1)
  • Migration status for nattable (- to 2.0.0+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nattable eclipse-collections (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nattable.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1465 days old (needed 5 days)
• arduino-mk (- to 1.5.2-2.1)
  • Migration status for arduino-mk (- to 1.5.2-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: arduino-mk arduino (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arduino-mk.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1466 days old (needed 5 days)
• btrfs-compsize (- to 1.5-1)
  • Migration status for btrfs-compsize (- to 1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating btrfs-compsize would introduce bugs in testing: #1091561
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btrfs-compsize.html
    • Reproducible on armhf - info ♻
    • 1466 days old (needed 5 days)
• gringotts (- to 1.2.10-4)
  • Migration status for gringotts (- to 1.2.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gringotts would introduce bugs in testing: #1075043
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gringotts.html
    • 1466 days old (needed 5 days)
• java-gnome (- to 4.1.3-10)
  • Migration status for java-gnome (- to 4.1.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating java-gnome would introduce bugs in testing: #1075098
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/java-gnome.html
    • 1466 days old (needed 5 days)
• libreadline-java (- to 0.8.0.1+dfsg-10)
  • Migration status for libreadline-java (- to 0.8.0.1+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libreadline-java would introduce bugs in testing: #1075200
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libreadline-java.html
    • 1466 days old (needed 5 days)
• performous-composer (- to 2.0+20181009-gitbeeea23-2.1)
  • Migration status for performous-composer (- to 2.0+20181009-gitbeeea23-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • performous-composer/amd64 has unsatisfiable dependency
    • performous-composer/arm64 has unsatisfiable dependency
    • performous-composer/armel has unsatisfiable dependency
    • performous-composer/armhf has unsatisfiable dependency
    • performous-composer/i386 has unsatisfiable dependency
    • performous-composer/mips64el has unsatisfiable dependency
    • performous-composer/ppc64el has unsatisfiable dependency
    • performous-composer/s390x has unsatisfiable dependency
    • Updating performous-composer would introduce bugs in testing: #1004816
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/performous-composer.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1467 days old (needed 5 days)
• plotsauce (- to 0~0.1-1)
  • Migration status for plotsauce (- to 0~0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating plotsauce would introduce bugs in testing: #1072135
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plotsauce.html
    • 1471 days old (needed 5 days)
• sugar-etoys-activity (- to 116-10)
  • Migration status for sugar-etoys-activity (- to 116-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sugar-etoys-activity etoys (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1471 days old (needed 5 days)
• arduino-mighty-1284p (- to 1-5)
  • Migration status for arduino-mighty-1284p (- to 1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: arduino-mighty-1284p arduino (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arduino-mighty-1284p.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1472 days old (needed 5 days)
• pantomime-clojure (- to 2.1.0+dfsg-2)
  • Migration status for pantomime-clojure (- to 2.1.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pantomime-clojure tika (not considered)
    • Depends: pantomime-clojure tika (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pantomime-clojure.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1472 days old (needed 5 days)
• tika (- to 1.22-2)
  • Migration status for tika (- to 1.22-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tika would introduce bugs in testing: #1011492
    • Build-Depends(-Arch): tika vorbis-java
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tika.html
    • 1472 days old (needed 5 days)
• libscout (- to 2.3.2-3)
  • Migration status for libscout (- to 2.3.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libscout android-framework-23 (not considered)
    • Depends: libscout android-framework-23 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libscout.html
    • autopkgtest for libscout/2.3.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1477 days old (needed 2 days)
• keynav (- to 0.20180421~git6505bd0d-3)
  • Migration status for keynav (- to 0.20180421~git6505bd0d-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating keynav would introduce bugs in testing: #1065949
    • Impossible Depends: keynav -> libglib2.0-0/2.78.4-1/armel
    • Impossible Depends: keynav -> libglib2.0-0/2.78.4-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keynav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1487 days old (needed 5 days)
• python-aioopenssl (- to 0.6.0-1)
  • Migration status for python-aioopenssl (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aioopenssl would introduce bugs in testing: #1090130
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioopenssl.html
    • Reproducible on armhf - info ♻
    • 1487 days old (needed 5 days)
• sptk (- to 3.9-3)
  • Migration status for sptk (- to 3.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sptk would introduce bugs in testing: #1091296
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sptk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1487 days old (needed 5 days)
• qstopmotion (- to 2.5.2-1)
  • Migration status for qstopmotion (- to 2.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • qstopmotion/armel has unsatisfiable dependency
    • qstopmotion/armhf has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qstopmotion.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1490 days old (needed 5 days)
• apt-src (- to 0.25.3)
  • Migration status for apt-src (- to 0.25.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apt-src would introduce bugs in testing: #1073483
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt-src.html
    • 1494 days old (needed 5 days)
• ruby-rack-google-analytics (- to 1.2.0-2.1)
  • Migration status for ruby-rack-google-analytics (- to 1.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rack-google-analytics would introduce bugs in testing: #1094516, #1094846
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rack-google-analytics.html
    • autopkgtest for ruby-rack-google-analytics/1.2.0-2.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1495 days old (needed 2 days)
• android-platform-external-doclava (- to 6.0.1+r55-1.1)
  • Migration status for android-platform-external-doclava (- to 6.0.1+r55-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-external-doclava would introduce bugs in testing: #1012103
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-external-doclava.html
    • 1496 days old (needed 5 days)
• dlang-libevent (- to 2.0.16.1~really2.0.2-0.2)
  • Migration status for dlang-libevent (- to 2.0.16.1~really2.0.2-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dlang-libevent would introduce bugs in testing: #1091010
    • Depends: dlang-libevent dlang-openssl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dlang-libevent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1496 days old (needed 5 days)
• lisaac (- to 1:0.39~rc1-3.1)
  • Migration status for lisaac (- to 1:0.39~rc1-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lisaac would introduce bugs in testing: #1075228
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lisaac.html
    • 1496 days old (needed 5 days)
• micropolis-activity (- to 0.0.20071228-10)
  • Migration status for micropolis-activity (- to 0.0.20071228-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating micropolis-activity would introduce bugs in testing: #1066598
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/micropolis-activity.html
    • 1496 days old (needed 5 days)
• ruby-cleanroom (- to 1.0.0-1.1)
  • Migration status for ruby-cleanroom (- to 1.0.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-cleanroom would introduce bugs in testing: #1092691
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-cleanroom.html
    • autopkgtest for ruby-cleanroom/1.0.0-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1496 days old (needed 2 days)
• ruby-integration (- to 0.1.0-1.1)
  • Migration status for ruby-integration (- to 0.1.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-integration ruby-gsl (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-integration.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1496 days old (needed 5 days)
• ruby-rails-assets-bootstrap-markdown (- to 2.10.0-1.1)
  • Migration status for ruby-rails-assets-bootstrap-markdown (- to 2.10.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-rails-assets-bootstrap-markdown ruby-rails-assets-bootstrap (not considered)
    • Depends: ruby-rails-assets-bootstrap-markdown ruby-rails-assets-bootstrap (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-bootstrap-markdown.html
    • autopkgtest for ruby-rails-assets-bootstrap-markdown/2.10.0-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1496 days old (needed 5 days)
• ruby-rails-assets-jakobmattsson-jquery-elastic (- to 1.6.11~dfsg-1.1)
  • Migration status for ruby-rails-assets-jakobmattsson-jquery-elastic (- to 1.6.11~dfsg-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-rails-assets-jakobmattsson-jquery-elastic ruby-rails-assets-jquery (not considered)
    • Depends: ruby-rails-assets-jakobmattsson-jquery-elastic ruby-rails-assets-jquery (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-jakobmattsson-jquery-elastic.html
    • autopkgtest for ruby-rails-assets-jakobmattsson-jquery-elastic/1.6.11~dfsg-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1496 days old (needed 5 days)
• ruby-rails-assets-bootstrap (- to 3.3.7-1.1)
  • Migration status for ruby-rails-assets-bootstrap (- to 3.3.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): ruby-rails-assets-bootstrap ruby-rails-assets-jquery (not considered)
    • Depends: ruby-rails-assets-bootstrap ruby-rails-assets-jquery (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-bootstrap.html
    • autopkgtest for ruby-rails-assets-bootstrap/3.3.7-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1497 days old (needed 5 days)
• ruby-rails-assets-jquery-ui (- to 1.11.4-1.1)
  • Migration status for ruby-rails-assets-jquery-ui (- to 1.11.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-rails-assets-jquery-ui ruby-rails-assets-jquery (not considered)
    • Depends: ruby-rails-assets-jquery-ui ruby-rails-assets-jquery (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-jquery-ui.html
    • autopkgtest for ruby-rails-assets-jquery-ui/1.11.4-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1497 days old (needed 5 days)
• dlang-openssl (- to 2.0.0+1.1.0h-0.2)
  • Migration status for dlang-openssl (- to 2.0.0+1.1.0h-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dlang-openssl would introduce bugs in testing: #1091022
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dlang-openssl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1498 days old (needed 5 days)
• graypy (- to 2.1.0-1)
  • Migration status for graypy (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating graypy would introduce bugs in testing: #1082050
    • autopkgtest for graypy/2.1.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • graypy unsatisfiable Build-Depends(-Arch) on amd64: python3-amqplib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graypy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1498 days old (needed 5 days)
• makepp (- to 2.0.98.5-2.1)
  • Migration status for makepp (- to 2.0.98.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating makepp would introduce bugs in testing: #1087904
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/makepp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1498 days old (needed 5 days)
• wordpress-xrds-simple (- to 1.2-1.1)
  • Migration status for wordpress-xrds-simple (- to 1.2-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wordpress-xrds-simple wordpress (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wordpress-xrds-simple.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1499 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: #1091600
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsjac.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 1500 days old (needed 5 days)
• php-validate (- to 0.8.5-4.2)
  • Migration status for php-validate (- to 0.8.5-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-validate would introduce bugs in testing: #1065708
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-validate.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1500 days old (needed 5 days)
• android-framework-23 (- to 6.0.1+r72-6)
  • Migration status for android-framework-23 (- to 6.0.1+r72-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-framework-23 would introduce bugs in testing: #1011567, #1038833
    • Build-Depends(-Arch): android-framework-23 android-platform-external-doclava (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-framework-23.html
    • autopkgtest for android-framework-23/6.0.1+r72-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1502 days old (needed 2 days)
• php-net-ftp (- to 1:1.4.0-2.1)
  • Migration status for php-net-ftp (- to 1:1.4.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-ftp would introduce bugs in testing: #1041477
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-ftp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1502 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pysolfc-cardsets would introduce bugs in testing: #1095777
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pysolfc-cardsets.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1502 days old (needed 5 days)
• gaviotatb (- to 0.4-2.1)
  • Migration status for gaviotatb (- to 0.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gaviotatb would introduce bugs in testing: #1074978
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gaviotatb.html
    • 1503 days old (needed 5 days)
• scala-parser-combinators (- to 1.0.3-3.1)
  • Migration status for scala-parser-combinators (- to 1.0.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): scala-parser-combinators scala (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scala-parser-combinators.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1503 days old (needed 5 days)
• scala-xml (- to 1.0.3-3.1)
  • Migration status for scala-xml (- to 1.0.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): scala-xml scala (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scala-xml.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1503 days old (needed 5 days)
• scratch (- to 1.4.0.6~dfsg1-6.1)
  • Migration status for scratch (- to 1.4.0.6~dfsg1-6.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: scratch squeak-vm (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scratch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1503 days old (needed 5 days)
• libphp-snoopy (- to 2.0.0-3)
  • Migration status for libphp-snoopy (- to 2.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libphp-snoopy would introduce bugs in testing: #1065707
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libphp-snoopy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1509 days old (needed 5 days)
• broker (- to 1.4.0+ds1-1)
  • Migration status for broker (- to 1.4.0+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-broker/amd64 has unsatisfiable dependency
    • python3-broker/arm64 has unsatisfiable dependency
    • libbroker2/armel has unsatisfiable dependency
    • python3-broker/armel has unsatisfiable dependency
    • libbroker2/armhf has unsatisfiable dependency
    • python3-broker/armhf has unsatisfiable dependency
    • python3-broker/i386 has unsatisfiable dependency
    • python3-broker/mips64el has unsatisfiable dependency
    • python3-broker/ppc64el has unsatisfiable dependency
    • python3-broker/s390x has unsatisfiable dependency
    • Updating broker would introduce bugs in testing: #1037597, #1062029
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/b/broker.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1510 days old (needed 5 days)
• ydotool (- to 0.1.8-3)
  • Migration status for ydotool (- to 0.1.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ydotool would introduce bugs in testing: #1069485
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ydotool.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1513 days old (needed 5 days)
• ruby-rspec-parameterized (- to 0.4.2-2)
  • Migration status for ruby-rspec-parameterized (- to 0.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rspec-parameterized would introduce bugs in testing: #1093930
    • Build-Depends(-Arch): ruby-rspec-parameterized ruby-proc-to-ast
    • Build-Depends(-Arch): ruby-rspec-parameterized ruby-unparser (not considered)
    • Depends: ruby-rspec-parameterized ruby-proc-to-ast
    • Depends: ruby-rspec-parameterized ruby-unparser (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized.html
    • autopkgtest for ruby-rspec-parameterized/0.4.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1514 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:
    • adabrowse/amd64 has unsatisfiable dependency
    • adabrowse/arm64 has unsatisfiable dependency
    • adabrowse/armel has unsatisfiable dependency
    • adabrowse/armhf has unsatisfiable dependency
    • adabrowse/i386 has unsatisfiable dependency
    • adabrowse/mips64el has unsatisfiable dependency
    • adabrowse/ppc64el has unsatisfiable dependency
    • adabrowse/s390x has unsatisfiable dependency
    • Updating adabrowse would introduce bugs in testing: #1008980
    • Build-Depends(-Arch): adabrowse asis (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adabrowse.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1516 days old (needed 5 days)
• kcc (- to 2.3+really-0.1)
  • Migration status for kcc (- to 2.3+really-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kcc would introduce bugs in testing: #1066294
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcc.html
    • 1516 days old (needed 5 days)
• asis (- to 2019-5)
  • Migration status for asis (- to 2019-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • asis-programs/amd64 has unsatisfiable dependency
    • libasis2019.1/amd64 has unsatisfiable dependency
    • libasis2019.1-dev/amd64 has unsatisfiable dependency
    • asis-programs/arm64 has unsatisfiable dependency
    • libasis2019.1/arm64 has unsatisfiable dependency
    • libasis2019.1-dev/arm64 has unsatisfiable dependency
    • asis-programs/armel has unsatisfiable dependency
    • libasis2019.1/armel has unsatisfiable dependency
    • libasis2019.1-dev/armel has unsatisfiable dependency
    • asis-programs/armhf has unsatisfiable dependency
    • libasis2019.1/armhf has unsatisfiable dependency
    • libasis2019.1-dev/armhf has unsatisfiable dependency
    • asis-programs/i386 has unsatisfiable dependency
    • libasis2019.1/i386 has unsatisfiable dependency
    • libasis2019.1-dev/i386 has unsatisfiable dependency
    • asis-programs/mips64el has unsatisfiable dependency
    • libasis2019.1/mips64el has unsatisfiable dependency
    • libasis2019.1-dev/mips64el has unsatisfiable dependency
    • asis-programs/ppc64el has unsatisfiable dependency
    • libasis2019.1/ppc64el has unsatisfiable dependency
    • libasis2019.1-dev/ppc64el has unsatisfiable dependency
    • asis-programs/s390x has unsatisfiable dependency
    • libasis2019.1/s390x has unsatisfiable dependency
    • libasis2019.1-dev/s390x has unsatisfiable dependency
    • Updating asis would introduce bugs in testing: #1008979
    • asis unsatisfiable Build-Depends(-Arch) on amd64: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on arm64: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on armel: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on armel: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on armel: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on armhf: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on i386: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on i386: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on i386: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on s390x: gnat-10
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libgnat-util10-dev
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlezout8-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/asis.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1522 days old (needed 5 days)
• autoconf2.13 (- to 2.13-69)
  • Migration status for autoconf2.13 (- to 2.13-69): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating autoconf2.13 would introduce bugs in testing: #1081532
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autoconf2.13.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1522 days old (needed 5 days)
• android-platform-external-libunwind (- to 10.0.0+r36-4)
  • Migration status for android-platform-external-libunwind (- to 10.0.0+r36-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-external-libunwind would introduce bugs in testing: #1060969
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-external-libunwind.html
    • autopkgtest for android-platform-external-libunwind/10.0.0+r36-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1528 days old (needed 2 days)
• siggen (- to 2.3.10-11)
  • Migration status for siggen (- to 2.3.10-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating siggen would introduce bugs in testing: #1075507
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/siggen.html
    • 1533 days old (needed 5 days)
• nanostat (- to 1.4.0-3)
  • Migration status for nanostat (- to 1.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nanostat/1.4.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nanostat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1534 days old (needed 5 days)
• shoogle (- to 0.1.4-10)
  • Migration status for shoogle (- to 0.1.4-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shoogle would introduce bugs in testing: #1083030
    • Depends: shoogle python-oauth2client (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shoogle.html
    • autopkgtest for shoogle/0.1.4-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1535 days old (needed 2 days)
• yagv (- to 0.4~20171211.r234ef16+dfsg-2)
  • Migration status for yagv (- to 0.4~20171211.r234ef16+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yagv would introduce bugs in testing: #1064598
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yagv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1538 days old (needed 5 days)
• prelude-manager (- to 5.2.0-2)
  • Migration status for prelude-manager (- 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): prelude-manager libpreludedb (not considered)
    • Depends: prelude-manager libpreludedb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): prelude-manager libprelude (not considered)
    • Depends: prelude-manager libprelude (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prelude-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1539 days old (needed 5 days)
• php-horde-javascriptminify (- to 1.1.5-7)
  • Migration status for php-horde-javascriptminify (- to 1.1.5-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-javascriptminify/1.1.5-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-javascriptminify php-horde-log (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-javascriptminify.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1542 days old (needed 5 days)
• desproxy (- to 0.1.0~pre3-10.1)
  • Migration status for desproxy (- to 0.1.0~pre3-10.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating desproxy would introduce bugs in testing: #1074907
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/desproxy.html
    • 1546 days old (needed 5 days)
• nim-docopt (- to 0.6.8-3)
  • Migration status for nim-docopt (- to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nim-docopt would introduce bugs in testing: #1081085
    • autopkgtest for nim-docopt/0.6.8-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): nim-docopt nim (not considered)
    • Build-Depends(-Arch): nim-docopt nim-regex
    • Build-Depends(-Arch): nim-docopt nim-unicodedb
    • Build-Depends(-Arch): nim-docopt nim-unicodeplus
    • Depends: nim-docopt nim-regex
    • Depends: nim-docopt nim-unicodedb
    • Depends: nim-docopt nim-unicodeplus
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-docopt.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on i386 - info ♻
    • 1550 days old (needed 5 days)
• ruby-rgfa (- to 1.3.1+dfsg-2)
  • Migration status for ruby-rgfa (- to 1.3.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rgfa would introduce bugs in testing: #1092702
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rgfa.html
    • autopkgtest for ruby-rgfa/1.3.1+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1550 days old (needed 2 days)
• nim-d3 (- to 0.1.3-2)
  • Migration status for nim-d3 (- to 0.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): nim-d3 nim (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-d3.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1552 days old (needed 5 days)
• ibutils (- to 1.5.7+0.2.gbd7e502-3)
  • Migration status for ibutils (- to 1.5.7+0.2.gbd7e502-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ibutils opensm (not considered)
    • Depends: ibutils opensm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1554 days old (needed 5 days)
• tpp (- to 1.3.1-8)
  • Migration status for tpp (- to 1.3.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tpp would introduce bugs in testing: #1077125
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1556 days old (needed 5 days)
• shc (- to 4.0.3-1)
  • Migration status for shc (- to 4.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shc would introduce bugs in testing: #1072469
    • shc unsatisfiable Build-Depends(-Arch) on amd64: ash
    • shc unsatisfiable Build-Depends(-Arch) on arm64: ash
    • shc unsatisfiable Build-Depends(-Arch) on armel: ash
    • shc unsatisfiable Build-Depends(-Arch) on armhf: ash
    • shc unsatisfiable Build-Depends(-Arch) on i386: ash
    • shc unsatisfiable Build-Depends(-Arch) on mips64el: ash
    • shc unsatisfiable Build-Depends(-Arch) on ppc64el: ash
    • shc unsatisfiable Build-Depends(-Arch) on riscv64: ash
    • shc unsatisfiable Build-Depends(-Arch) on s390x: ash
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shc.html
    • autopkgtest for shc/4.0.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1557 days old (needed 2 days)
• holes (- to 0.1-5)
  • Migration status for holes (- to 0.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating holes would introduce bugs in testing: #1069466
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/holes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1564 days old (needed 5 days)
• nim-regex (- to 0.17.0+ds-2)
  • Migration status for nim-regex (- to 0.17.0+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nim-regex nim (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): nim-regex nim-unicodedb
    • Build-Depends(-Arch): nim-regex nim-unicodeplus
    • Depends: nim-regex nim-unicodedb
    • Depends: nim-regex nim-unicodeplus
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-regex.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1565 days old (needed 5 days)
• php-horde-mail-autoconfig (- to 1.0.3-10)
  • Migration status for php-horde-mail-autoconfig (- to 1.0.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-mail-autoconfig/1.0.3-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-mail-autoconfig php-horde-imap-client (not considered)
    • Depends: php-horde-mail-autoconfig php-net-dns2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mail-autoconfig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1575 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-mnemo/4.2.14-10: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Regression or new test ♻
    • Depends: php-horde-mnemo php-horde
    • Depends: php-horde-mnemo php-horde-auth (not considered)
    • Depends: php-horde-mnemo php-horde-content (not considered)
    • Depends: php-horde-mnemo php-horde-core (not considered)
    • Depends: php-horde-mnemo php-horde-data (not considered)
    • Depends: php-horde-mnemo php-horde-form
    • Depends: php-horde-mnemo php-horde-history (not considered)
    • Depends: php-horde-mnemo php-horde-injector (not considered)
    • Depends: php-horde-mnemo php-horde-perms (not considered)
    • Depends: php-horde-mnemo php-horde-prefs (not considered)
    • Depends: php-horde-mnemo php-horde-share (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mnemo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1575 days old (needed 5 days)
• php-net-dns2 (- to 1.5.0-1)
  • Migration status for php-net-dns2 (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-dns2 would introduce bugs in testing: #1042457
    • autopkgtest for php-net-dns2/1.5.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-dns2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1577 days old (needed 5 days)
• pyqwt3d (- to 0.1.8-6)
  • Migration status for pyqwt3d (- to 0.1.8-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyqwt3d sip4 (not considered)
    • Depends: pyqwt3d sip4 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyqwt3d.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1580 days old (needed 5 days)
• gdis (- to 0.90-6)
  • Migration status for gdis (- to 0.90-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gdis/armel has unsatisfiable dependency
    • gdis/armhf has unsatisfiable dependency
    • Updating gdis would introduce bugs in testing: #1066985
    • autopkgtest for gdis/0.90-6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): gdis gtkglext (not considered)
    • Depends: gdis gtkglext (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gdis.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1584 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-nag would introduce bugs in testing: #1064389
    • autopkgtest for php-horde-nag/4.2.19-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-nag php-horde
    • Depends: php-horde-nag php-horde-auth (not considered)
    • Depends: php-horde-nag php-horde-content (not considered)
    • Depends: php-horde-nag php-horde-controller (not considered)
    • Depends: php-horde-nag php-horde-core (not considered)
    • Depends: php-horde-nag php-horde-data (not considered)
    • Depends: php-horde-nag php-horde-dav
    • Depends: php-horde-nag php-horde-form
    • Depends: php-horde-nag php-horde-history (not considered)
    • Depends: php-horde-nag php-horde-mime (not considered)
    • Depends: php-horde-nag php-horde-perms (not considered)
    • Depends: php-horde-nag php-horde-prefs (not considered)
    • Depends: php-horde-nag php-horde-share (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-nag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1593 days old (needed 5 days)
• ruby-rollout (- to 2.5.0-1)
  • Migration status for ruby-rollout (- to 2.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rollout would introduce bugs in testing: #1084366
    • Build-Depends(-Arch): ruby-rollout ruby-fakeredis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rollout.html
    • autopkgtest for ruby-rollout/2.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1594 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-content/2.0.6-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-content php-horde-core (not considered)
    • Depends: php-horde-content php-horde-db (not considered)
    • Depends: php-horde-content php-horde-injector (not considered)
    • Depends: php-horde-content php-horde-rdo (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-content.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1598 days old (needed 5 days)
• salt-pylint (- to 2020.9.28-1)
  • Migration status for salt-pylint (- to 2020.9.28-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating salt-pylint would introduce bugs in testing: #1064678
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/salt-pylint.html
    • autopkgtest for salt-pylint/2020.9.28-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1598 days old (needed 5 days)
• php-horde-javascriptminify-jsmin (- to 1.0.2-9)
  • Migration status for php-horde-javascriptminify-jsmin (- to 1.0.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-javascriptminify-jsmin/1.0.2-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-javascriptminify-jsmin php-horde-javascriptminify (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1607 days old (needed 5 days)
• ruby-rails-assets-fine-uploader (- to 5.13.0-2)
  • Migration status for ruby-rails-assets-fine-uploader (- to 5.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-fine-uploader would introduce bugs in testing: #1034027
    • autopkgtest for ruby-rails-assets-fine-uploader/5.13.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-fine-uploader.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1609 days old (needed 5 days)
• php-horde-timezone (- to 1.1.0-7)
  • Migration status for php-horde-timezone (- to 1.1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-timezone would introduce bugs in testing: #1089778
    • autopkgtest for php-horde-timezone/1.1.0-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-timezone.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1612 days old (needed 5 days)
• eclipse-cdt (- to 9.9.0-5)
  • Migration status for eclipse-cdt (- to 9.9.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eclipse-cdt would introduce bugs in testing: #1022294
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-cdt.html
    • 1622 days old (needed 5 days)
• percona-toolkit (- to 3.2.1-1)
  • Migration status for percona-toolkit (- to 3.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating percona-toolkit would introduce bugs in testing: #1091435
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/percona-toolkit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1627 days old (needed 5 days)
• ruby-rails-assets-blueimp-gallery (- to 2.33.0-2)
  • Migration status for ruby-rails-assets-blueimp-gallery (- to 2.33.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-blueimp-gallery would introduce bugs in testing: #1033914
    • autopkgtest for ruby-rails-assets-blueimp-gallery/2.33.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rails-assets-blueimp-gallery.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1633 days old (needed 5 days)
• freedroid (- to 1.0.2+cvs040112-7)
  • Migration status for freedroid (- to 1.0.2+cvs040112-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freedroid would introduce bugs in testing: #1066474
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freedroid.html
    • 1637 days old (needed 5 days)
• fvwm1 (- to 1.24r-57)
  • Migration status for fvwm1 (- to 1.24r-57): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fvwm1 would introduce bugs in testing: #1066565
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fvwm1.html
    • 1639 days old (needed 5 days)
• mlv-smile (- to 1.47-8)
  • Migration status for mlv-smile (- to 1.47-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mlv-smile would introduce bugs in testing: #1066525
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlv-smile.html
    • autopkgtest for mlv-smile/1.47-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1641 days old (needed 2 days)
• gmanedit (- to 0.4.2-8)
  • Migration status for gmanedit (- to 0.4.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gmanedit would introduce bugs in testing: #1075015
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gmanedit.html
    • 1644 days old (needed 5 days)
• nim-unicodedb (- to 0.9.0-2)
  • Migration status for nim-unicodedb (- to 0.9.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nim-unicodedb nim (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-unicodedb.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1645 days old (needed 5 days)
• nim-unicodeplus (- to 0.5.1-2)
  • Migration status for nim-unicodeplus (- to 0.5.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nim-unicodeplus nim (not considered)
    • Invalidated by build-dependency
    • Depends: nim-unicodeplus nim-unicodedb
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-unicodeplus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1645 days old (needed 5 days)
• restartd (- to 0.2.3-1.1)
  • Migration status for restartd (- to 0.2.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating restartd would introduce bugs in testing: #1089418
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/restartd.html
    • 1645 days old (needed 5 days)
• hexchat-otr (- to 0.2.2-3)
  • Migration status for hexchat-otr (- to 0.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hexchat-otr would introduce bugs in testing: #1076888
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hexchat-otr.html
    • 1646 days old (needed 5 days)
• tree-style-tab (- to 3.5.20-1)
  • Migration status for tree-style-tab (- to 3.5.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tree-style-tab would introduce bugs in testing: #1071896
    • tree-style-tab unsatisfiable Build-Depends(-Arch) on amd64: mozilla-devscripts (>= 0.50~)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tree-style-tab.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1649 days old (needed 5 days)
• d1x-rebirth (- to 0.58.1-1.2)
  • Migration status for d1x-rebirth (- to 0.58.1-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating d1x-rebirth would introduce bugs in testing: #1057551
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1651 days old (needed 5 days)
• d2x-rebirth (- to 0.58.1-1.3)
  • Migration status for d2x-rebirth (- to 0.58.1-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating d2x-rebirth would introduce bugs in testing: #1057552
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1651 days old (needed 5 days)
• pyjdata (- to 0.3.6-1)
  • Migration status for pyjdata (- to 0.3.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pyjdata pybj (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyjdata.html
    • autopkgtest for pyjdata/0.3.6-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1652 days old (needed 5 days)
• nastran (- to 0.1.95-2)
  • Migration status for nastran (- to 0.1.95-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nastran would introduce bugs in testing: #1054241
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1655 days old (needed 5 days)
• gnucap-python (- to 0.0.2-1.2)
  • Migration status for gnucap-python (- to 0.0.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-gnucap/amd64 has unsatisfiable dependency
    • python3-gnucap/arm64 has unsatisfiable dependency
    • python3-gnucap/armel has unsatisfiable dependency
    • python3-gnucap/armhf has unsatisfiable dependency
    • python3-gnucap/i386 has unsatisfiable dependency
    • python3-gnucap/mips64el has unsatisfiable dependency
    • python3-gnucap/ppc64el has unsatisfiable dependency
    • python3-gnucap/riscv64 has unsatisfiable dependency
    • python3-gnucap/s390x has unsatisfiable dependency
    • Updating gnucap-python would introduce bugs in testing: #1067335
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnucap-python.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 1659 days old (needed 5 days)
• cen64 (- to 0.3+git20200723-1)
  • Migration status for cen64 (- to 0.3+git20200723-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cen64 would introduce bugs in testing: #1074875
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cen64.html
    • 1664 days old (needed 5 days)
• mongrel2 (- to 1.12.2-3)
  • Migration status for mongrel2 (- to 1.12.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mongrel2 would introduce bugs in testing: #1075866
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mongrel2.html
    • 1666 days old (needed 5 days)
• php-horde-controller (- to 2.0.5-5)
  • Migration status for php-horde-controller (- to 2.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-controller/2.0.5-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: php-horde-controller php-horde-injector (not considered)
    • Depends: php-horde-controller php-horde-log (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-controller.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1667 days old (needed 5 days)
• yeahconsole (- to 0.3.4-6)
  • Migration status for yeahconsole (- to 0.3.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yeahconsole would introduce bugs in testing: #1075696
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yeahconsole.html
    • 1670 days old (needed 5 days)
• fonts-kacst (- to 2.01+mry-15)
  • Migration status for fonts-kacst (- to 2.01+mry-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-kacst would introduce bugs in testing: #1041017
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-kacst.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1671 days old (needed 5 days)
• eclipse-remote (- to 2.1.0-2)
  • Migration status for eclipse-remote (- to 2.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): eclipse-remote eclipse-cdt (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-remote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1672 days old (needed 5 days)
• php-horde-whups (- to 3.0.12-7)
  • Migration status for php-horde-whups (- to 3.0.12-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-whups php-horde (not considered)
    • Invalidated by dependency
    • Depends: php-horde-whups php-horde-auth (not considered)
    • Depends: php-horde-whups php-horde-compress (not considered)
    • Depends: php-horde-whups php-horde-core (not considered)
    • Depends: php-horde-whups php-horde-db (not considered)
    • Depends: php-horde-whups php-horde-form
    • Depends: php-horde-whups php-horde-mime (not considered)
    • Depends: php-horde-whups php-horde-mime-viewer
    • Depends: php-horde-whups php-horde-perms (not considered)
    • Depends: php-horde-whups php-horde-prefs (not considered)
    • Depends: php-horde-whups php-horde-scheduler
    • Depends: php-horde-whups php-horde-share (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-whups.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1684 days old (needed 5 days)
• php-horde-gollem (- to 3.0.13-5)
  • Migration status for php-horde-gollem (- to 3.0.13-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-gollem php-horde (not considered)
    • Invalidated by dependency
    • Depends: php-horde-gollem php-horde-auth (not considered)
    • Depends: php-horde-gollem php-horde-core (not considered)
    • Depends: php-horde-gollem php-horde-editor (not considered)
    • Depends: php-horde-gollem php-horde-mime (not considered)
    • Depends: php-horde-gollem php-horde-mime-viewer
    • Depends: php-horde-gollem php-horde-perms (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-gollem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1685 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 (not considered)
    • Depends: php-horde-trean php-horde-controller (not considered)
    • Depends: php-horde-trean php-horde-core (not considered)
    • Depends: php-horde-trean php-horde-db (not considered)
    • Depends: php-horde-trean php-horde-form
    • Depends: php-horde-trean php-horde-perms (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-trean.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1685 days old (needed 5 days)
• php-horde-service-twitter (- to 2.1.6-6)
  • Migration status for php-horde-service-twitter (- to 2.1.6-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-service-twitter php-horde-controller (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-service-twitter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1687 days old (needed 5 days)
• php-horde-syncml (- to 2.0.7-7)
  • Migration status for php-horde-syncml (- to 2.0.7-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-syncml php-horde-log (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-syncml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1687 days old (needed 5 days)
• wordpress-shibboleth (- to 1.8-1.1)
  • Migration status for wordpress-shibboleth (- to 1.8-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: wordpress-shibboleth wordpress (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wordpress-shibboleth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1687 days old (needed 5 days)
• php-horde-cssminify (- to 1.0.4-6)
  • Migration status for php-horde-cssminify (- to 1.0.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-cssminify php-horde-log (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-cssminify.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1688 days old (needed 5 days)
• php-horde-dav (- to 1.1.4-6)
  • Migration status for php-horde-dav (- to 1.1.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-dav php-sabredav (not considered)
    • Invalidated by dependency
    • Depends: php-horde-dav php-horde-auth (not considered)
    • Depends: php-horde-dav php-horde-core (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-dav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1688 days old (needed 5 days)
• php-horde-editor (- to 2.0.5+debian0-5)
  • Migration status for php-horde-editor (- to 2.0.5+debian0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-editor would introduce bugs in testing: #1042715
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-editor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1688 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-token (not considered)
    • Invalidated by dependency
    • Depends: php-horde-form php-horde-core (not considered)
    • Depends: php-horde-form php-horde-mime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-form.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1688 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 (not considered)
    • Invalidated by dependency
    • Depends: php-horde-groupware php-horde-content (not considered)
    • Depends: php-horde-groupware php-horde-gollem
    • Depends: php-horde-groupware php-horde-kronolith (not considered)
    • Depends: php-horde-groupware php-horde-mnemo (not considered)
    • Depends: php-horde-groupware php-horde-nag (not considered)
    • Depends: php-horde-groupware php-horde-timeobjects
    • Depends: php-horde-groupware php-horde-trean
    • Depends: php-horde-groupware php-horde-turba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-groupware.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1688 days old (needed 5 days)
• php-horde-openxchange (- to 1.0.1-6)
  • Migration status for php-horde-openxchange (- 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: php-horde-openxchange php-horde-perms (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-openxchange.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1688 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1688 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1688 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 (not considered)
    • Invalidated by dependency
    • Depends: php-horde-webmail php-horde-content (not considered)
    • Depends: php-horde-webmail php-horde-gollem
    • Depends: php-horde-webmail php-horde-imp (not considered)
    • Depends: php-horde-webmail php-horde-ingo (not considered)
    • Depends: php-horde-webmail php-horde-kronolith (not considered)
    • Depends: php-horde-webmail php-horde-mnemo (not considered)
    • Depends: php-horde-webmail php-horde-nag (not considered)
    • Depends: php-horde-webmail php-horde-timeobjects
    • Depends: php-horde-webmail php-horde-trean
    • Depends: php-horde-webmail php-horde-turba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-webmail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1688 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: #1082991
    • Build-Depends(-Arch): dpaste opendht (not considered)
    • Depends: dpaste opendht (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dpaste.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 1694 days old (needed 5 days)
• matchbox (- to 1:7)
  • Migration status for matchbox (- to 1:7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: matchbox matchbox-desktop (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matchbox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1696 days old (needed 5 days)
• matchbox-desktop (- to 2.2+git20200512-1)
  • Migration status for matchbox-desktop (- to 2.2+git20200512-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating matchbox-desktop would introduce bugs in testing: #1075257
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matchbox-desktop.html
    • 1696 days old (needed 5 days)
• lhs2tex (- to 1.24-1)
  • Migration status for lhs2tex (- to 1.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lhs2tex would introduce bugs in testing: #1082301
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lhs2tex.html
    • 1702 days old (needed 5 days)
• fdclone (- to 3.01j-1)
  • Migration status for fdclone (- to 3.01j-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fdclone would introduce bugs in testing: #1074949
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fdclone.html
    • 1706 days old (needed 5 days)
• jinput (- to 20100502+dfsg-11)
  • Migration status for jinput (- to 20100502+dfsg-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jinput would introduce bugs in testing: #1069434
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jinput.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1712 days old (needed 5 days)
• runescape (- to 0.8-2)
  • Migration status for runescape (- to 0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating runescape would introduce bugs in testing: #1061393
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for runescape/0.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1720 days old (needed 2 days)
• opensmtpd-extras (- to 6.7.1-2)
  • Migration status for opensmtpd-extras (- to 6.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensmtpd-extras would introduce bugs in testing: #1066467
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensmtpd-extras.html
    • 1724 days old (needed 5 days)
• tilde (- to 1.1.2-1)
  • Migration status for tilde (- to 1.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): tilde libtranscript (not considered)
    • Depends: tilde libtranscript (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): tilde libt3widget
    • Depends: tilde libt3widget
    • Depends: tilde libt3window
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tilde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1724 days old (needed 5 days)
• btyacc (- to 3.0+dfsg-1)
  • Migration status for btyacc (- to 3.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating btyacc would introduce bugs in testing: #1074856
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btyacc.html
    • autopkgtest for btyacc/3.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1725 days old (needed 2 days)
• id-utils (- to 4.6.28-20200521ss15dab)
  • Migration status for id-utils (- to 4.6.28-20200521ss15dab): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating id-utils would introduce bugs in testing: #1089346, #1091243
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/id-utils.html
    • Reproducible on arm64 - info ♻
    • 1725 days old (needed 5 days)
• r-cran-fitcoach (- to 1.0-4)
  • Migration status for r-cran-fitcoach (- to 1.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-fitcoach r-cran-gbm (not considered)
    • Depends: r-cran-fitcoach r-cran-gbm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fitcoach.html
    • autopkgtest for r-cran-fitcoach/1.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1730 days old (needed 2 days)
• parcimonie (- to 0.12.0-2)
  • Migration status for parcimonie (- to 0.12.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating parcimonie would introduce bugs in testing: #1091033
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/parcimonie.html
    • autopkgtest for parcimonie/0.12.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1755 days old (needed 2 days)
• syrthes (- to 4.3.5+20200129-dfsg1-1)
  • Migration status for syrthes (- to 4.3.5+20200129-dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • syrthes-tools/armel has unsatisfiable dependency
    • syrthes-tools/armhf has unsatisfiable dependency
    • Updating syrthes would introduce bugs in testing: #1066258
    • Build-Depends(-Arch): syrthes code-saturne (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syrthes.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1759 days old (needed 5 days)
• code-saturne (- to 6.0.2-2)
  • Migration status for code-saturne (- to 6.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • code-saturne-bin/amd64 has unsatisfiable dependency
    • code-saturne-bin/arm64 has unsatisfiable dependency
    • code-saturne-bin/armel has unsatisfiable dependency
    • code-saturne-bin/armhf has unsatisfiable dependency
    • code-saturne-bin/i386 has unsatisfiable dependency
    • code-saturne-bin/mips64el has unsatisfiable dependency
    • code-saturne-bin/ppc64el has unsatisfiable dependency
    • code-saturne-bin/riscv64 has unsatisfiable dependency
    • code-saturne-bin/s390x has unsatisfiable dependency
    • Updating code-saturne would introduce bugs in testing: #1066231, #1068318
    • code-saturne unsatisfiable Build-Depends(-Arch) on armel: libopenmpi-dev
    • code-saturne unsatisfiable Build-Depends(-Arch) on armhf: libopenmpi-dev
    • code-saturne unsatisfiable Build-Depends(-Arch) on i386: libopenmpi-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/code-saturne.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1760 days old (needed 5 days)
• scala-tools-sbinary (- to 0.4.2-on-scala-2.11.0~M5-1)
  • Migration status for scala-tools-sbinary (- to 0.4.2-on-scala-2.11.0~M5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): scala-tools-sbinary scala (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scala-tools-sbinary.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1761 days old (needed 5 days)
• ruby-feature (- to 1.4.0-2)
  • Migration status for ruby-feature (- to 1.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-feature would introduce bugs in testing: #1084362
    • Build-Depends(-Arch): ruby-feature ruby-fakeredis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-feature.html
    • autopkgtest for ruby-feature/1.4.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1763 days old (needed 2 days)
• cclib-data (- to 1.6.2-2)
  • Migration status for cclib-data (- to 1.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cclib-data would introduce bugs in testing: #1057547
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1768 days old (needed 5 days)
• ruby-thinking-sphinx (- to 4.1.0-3)
  • Migration status for ruby-thinking-sphinx (- to 4.1.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-thinking-sphinx ruby-riddle (not considered)
    • Depends: ruby-thinking-sphinx ruby-riddle (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-thinking-sphinx.html
    • autopkgtest for ruby-thinking-sphinx/4.1.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1768 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:
    • sdaps/amd64 has unsatisfiable dependency
    • sdaps/arm64 has unsatisfiable dependency
    • sdaps/armel has unsatisfiable dependency
    • sdaps/armhf has unsatisfiable dependency
    • sdaps/i386 has unsatisfiable dependency
    • sdaps/mips64el has unsatisfiable dependency
    • sdaps/ppc64el has unsatisfiable dependency
    • sdaps/riscv64 has unsatisfiable dependency
    • sdaps/s390x has unsatisfiable dependency
    • Updating sdaps would introduce bugs in testing: #1001643, #1061159
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sdaps.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1768 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-redis-rack would introduce bugs in testing: #1084365
  • 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1770 days old (needed 2 days)
• ecb (- to 2.50+git20170628-1)
  • Migration status for ecb (- to 2.50+git20170628-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ecb would introduce bugs in testing: #1020168
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecb.html
    • 1771 days old (needed 5 days)
• clips (- to 6.30-4.1)
  • Migration status for clips (- to 6.30-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clips would introduce bugs in testing: #1061729
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clips.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1780 days old (needed 5 days)
• ruby-warden (- to 1.2.8-1)
  • Migration status for ruby-warden (- to 1.2.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-warden would introduce bugs in testing: #1094553
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-warden.html
    • autopkgtest for ruby-warden/1.2.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1781 days old (needed 2 days)
• tmperamental (- to 1.4)
  • Migration status for tmperamental (- to 1.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tmperamental would introduce bugs in testing: #1069505
    • autopkgtest for tmperamental/1.4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tmperamental.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1802 days old (needed 5 days)
• aboot (- to 1.0~pre20200212-1)
  • Migration status for aboot (- to 1.0~pre20200212-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aboot-cross/amd64 has unsatisfiable dependency
    • aboot-cross/arm64 has unsatisfiable dependency
    • aboot-cross/armel has unsatisfiable dependency
    • aboot-cross/armhf has unsatisfiable dependency
    • aboot-cross/i386 has unsatisfiable dependency
    • aboot-cross/mips64el has unsatisfiable dependency
    • aboot-cross/ppc64el has unsatisfiable dependency
    • aboot-cross/riscv64 has unsatisfiable dependency
    • aboot-cross/s390x has unsatisfiable dependency
    • Updating aboot would introduce bugs in testing: #805988
    • 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/a/aboot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1804 days old (needed 5 days)
• libsmbios (- to 2.4.3-1)
  • Migration status for libsmbios (- to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-libsmbios/arm64 has unsatisfiable dependency
    • Updating libsmbios would introduce bugs in testing: #1092525
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsmbios.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 1806 days old (needed 5 days)
• uml-utilities (- to 20070815.4-1)
  • Migration status for uml-utilities (- to 20070815.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating uml-utilities would introduce bugs in testing: #1075599, #1091398
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uml-utilities.html
    • 1808 days old (needed 5 days)
• vtgrab (- to 0.1.8-3.2)
  • Migration status for vtgrab (- to 0.1.8-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vtgrab would introduce bugs in testing: #1075630
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vtgrab.html
    • 1811 days old (needed 5 days)
• ruby-rubydns (- to 1.0.3-3)
  • Migration status for ruby-rubydns (- to 1.0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rubydns would introduce bugs in testing: #1031468
    • autopkgtest for ruby-rubydns/1.0.3-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-rubydns ruby-celluloid-io (not considered)
    • Depends: ruby-rubydns ruby-celluloid-io (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-rubydns.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1812 days old (needed 5 days)
• mustache-d (- to 0.1.4-1)
  • Migration status for mustache-d (- to 0.1.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: mustache-d ldc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mustache-d.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1819 days old (needed 5 days)
• cafeobj (- to 1.6.0-2)
  • Migration status for cafeobj (- to 1.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cafeobj would introduce bugs in testing: #1085008, #1093322
    • cafeobj unsatisfiable Build-Depends(-Arch) on armel: sbcl
    • cafeobj unsatisfiable Build-Depends(-Arch) on armhf: sbcl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cafeobj.html
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1821 days old (needed 5 days)
• ruby-dataobjects (- to 0.10.17-2)
  • Migration status for ruby-dataobjects (- to 0.10.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-dataobjects would introduce bugs in testing: #1092694
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dataobjects.html
    • Reproducible on armhf - info ♻
    • 1835 days old (needed 5 days)
• ruby-dataobjects-postgres (- to 0.10.17-1)
  • Migration status for ruby-dataobjects-postgres (- to 0.10.17-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-dataobjects-postgres ruby-dataobjects (not considered)
    • Depends: ruby-dataobjects-postgres ruby-dataobjects (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dataobjects-postgres.html
    • autopkgtest for ruby-dataobjects-postgres/0.10.17-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1835 days old (needed 5 days)
• ruby-dataobjects-sqlite3 (- to 0.10.17-1)
  • Migration status for ruby-dataobjects-sqlite3 (- to 0.10.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-dataobjects-sqlite3/arm64 has unsatisfiable dependency
    • Updating ruby-dataobjects-sqlite3 would introduce bugs in testing: #1092692
    • Build-Depends(-Arch): ruby-dataobjects-sqlite3 ruby-dataobjects (not considered)
    • Depends: ruby-dataobjects-sqlite3 ruby-dataobjects (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-dataobjects-sqlite3.html
    • uninstallable on arch arm64, not running autopkgtest there
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1835 days old (needed 5 days)
• fonts-rit-sundar (- to 2.0.0+20170909-2)
  • Migration status for fonts-rit-sundar (- to 2.0.0+20170909-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-rit-sundar would introduce bugs in testing: #1033698
    • autopkgtest for fonts-rit-sundar/2.0.0+20170909-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-rit-sundar.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1838 days old (needed 5 days)
• acpi-override (- to 0.1+nmu1)
  • Migration status for acpi-override (- to 0.1+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating acpi-override would introduce bugs in testing: #968604
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/acpi-override.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1844 days old (needed 5 days)
• ghemical (- to 3.0.0-5)
  • Migration status for ghemical (- to 3.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ghemical/armel has unsatisfiable dependency
    • ghemical/armhf has unsatisfiable dependency
    • Updating ghemical would introduce bugs in testing: #1066986, #967865
    • Build-Depends(-Arch): ghemical gtkglext (not considered)
    • Build-Depends(-Arch): ghemical libghemical (not considered)
    • Build-Depends(-Arch): ghemical libglade2 (not considered)
    • Build-Depends(-Arch): ghemical mpqc (not considered)
    • Depends: ghemical gtkglext (not considered)
    • Depends: ghemical libglade2 (not considered)
    • Depends: ghemical mpqc (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghemical.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1848 days old (needed 5 days)
• form-history-control (- to 2.5.1.0-1)
  • Migration status for form-history-control (- to 2.5.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating form-history-control would introduce bugs in testing: #1085455
    • webext-form-history-control/amd64 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/arm64 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/armel has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/armhf has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/i386 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/mips64el has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/ppc64el has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/riscv64 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/s390x has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/form-history-control.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1858 days old (needed 5 days)
• golang-github-hashicorp-go-getter (- to 1.4.1-1)
  • Migration status for golang-github-hashicorp-go-getter (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-hashicorp-go-getter would introduce bugs in testing: #1083184
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hashicorp-go-getter.html
    • autopkgtest for golang-github-hashicorp-go-getter/1.4.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1861 days old (needed 2 days)
• hsail-tools (- to 0~20180830-1)
  • Migration status for hsail-tools (- to 0~20180830-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): hsail-tools dwarfutils (not considered)
    • Depends: hsail-tools dwarfutils (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hsail-tools.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1861 days old (needed 5 days)
• pyhoca-gui (- to 0.6.1.1-1)
  • Migration status for pyhoca-gui (- to 0.6.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyhoca-gui would introduce bugs in testing: #1054832
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyhoca-gui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1869 days old (needed 5 days)
• fortunes-mario (- to 0.21-1.1)
  • Migration status for fortunes-mario (- to 0.21-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fortunes-mario would introduce bugs in testing: #1073475
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fortunes-mario.html
    • 1870 days old (needed 5 days)
• xbattbar (- to 1.4.9-2)
  • Migration status for xbattbar (- to 1.4.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xbattbar would introduce bugs in testing: #1075651
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xbattbar.html
    • 1870 days old (needed 5 days)
• ruby-devise-lastseenable (- to 0.0.6-1.1)
  • Migration status for ruby-devise-lastseenable (- to 0.0.6-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-devise-lastseenable would introduce bugs in testing: #1095651
    • Build-Depends(-Arch): ruby-devise-lastseenable ruby-devise
    • Build-Depends(-Arch): ruby-devise-lastseenable ruby-warden (not considered)
    • Depends: ruby-devise-lastseenable ruby-devise
    • Depends: ruby-devise-lastseenable ruby-warden (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-devise-lastseenable.html
    • autopkgtest for ruby-devise-lastseenable/0.0.6-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1871 days old (needed 5 days)
• golang-github-throttled-throttled (- to 2.2.4-1)
  • Migration status for golang-github-throttled-throttled (- to 2.2.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-throttled-throttled golang-github-go-redis-redis (not considered)
    • Depends: golang-github-throttled-throttled golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-throttled-throttled.html
    • autopkgtest for golang-github-throttled-throttled/2.2.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1882 days old (needed 2 days)
• golang-github-ulule-limiter (- to 3.3.3-1)
  • Migration status for golang-github-ulule-limiter (- to 3.3.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
    • Depends: golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ulule-limiter.html
    • autopkgtest for golang-github-ulule-limiter/3.3.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1900 days old (needed 2 days)
• android-platform-external-nist-sip (- to 9.0.0+r35-1.1)
  • Migration status for android-platform-external-nist-sip (- to 9.0.0+r35-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-external-nist-sip would introduce bugs in testing: #1065522
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-external-nist-sip.html
    • 1935 days old (needed 5 days)
• unoconv (- to 0.7-2)
  • Migration status for unoconv (- to 0.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unoconv would introduce bugs in testing: #1076522
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unoconv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1936 days old (needed 5 days)
• gphoto2-cffi (- to 0.4.3~a1-1.1)
  • Migration status for gphoto2-cffi (- to 0.4.3~a1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gphoto2-cffi would introduce bugs in testing: #1091277
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gphoto2-cffi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1938 days old (needed 5 days)
• pymia (- to 0.1.9-2.1)
  • Migration status for pymia (- to 0.1.9-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-mia/amd64 has unsatisfiable dependency
    • python3-mia/arm64 has unsatisfiable dependency
    • python3-mia/armel has unsatisfiable dependency
    • python3-mia/armhf has unsatisfiable dependency
    • python3-mia/i386 has unsatisfiable dependency
    • python3-mia/mips64el has unsatisfiable dependency
    • python3-mia/ppc64el has unsatisfiable dependency
    • python3-mia/riscv64 has unsatisfiable dependency
    • python3-mia/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): pymia mia (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pymia.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1939 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
    • 1966 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
    • 1984 days old (needed 5 days)
• raspell (- to 1.3-2)
  • Migration status for raspell (- to 1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating raspell would introduce bugs in testing: #1075436
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raspell.html
    • autopkgtest for raspell/1.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1988 days old (needed 2 days)
• svn-load (- to 1.6-1)
  • Migration status for svn-load (- to 1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating svn-load would introduce bugs in testing: #1033526
    • autopkgtest for svn-load/1.6-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/svn-load.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1990 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: #1079963, #993003
    • autopkgtest for hydroffice.bag/0.2.15-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hydroffice.bag.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 1997 days old (needed 5 days)
• gertty (- to 1.6.0-1)
  • Migration status for gertty (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gertty would introduce bugs in testing: #1054007, #1069052
    • autopkgtest for gertty/1.6.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gertty.html
    • 2011 days old (needed 5 days)
• pytest-salt (- to 2019.6.13-1)
  • Migration status for pytest-salt (- to 2019.6.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytest-salt would introduce bugs in testing: #1074682
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-salt.html
    • autopkgtest for pytest-salt/2019.6.13-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 2045 days old (needed 5 days)
• averell (- to 1.2.5-1.1)
  • Migration status for averell (- to 1.2.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating averell would introduce bugs in testing: #1090191
    • Build-Depends(-Arch): averell erlang-cowboy (not considered)
    • Depends: averell erlang-cowboy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/averell.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • New but not reproducible on armhf - info ♻
    • 2093 days old (needed 5 days)
• libretro-beetle-pce-fast (- to 0.9.38.7+git20160609-2)
  • Migration status for libretro-beetle-pce-fast (- to 0.9.38.7+git20160609-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libretro-beetle-pce-fast would introduce bugs in testing: #1070021
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libretro-beetle-pce-fast.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2174 days old (needed 5 days)
• libretro-beetle-psx (- to 0.9.38.6+git20151019-3)
  • Migration status for libretro-beetle-psx (- to 0.9.38.6+git20151019-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libretro-beetle-psx would introduce bugs in testing: #1070022
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libretro-beetle-psx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2174 days old (needed 5 days)
• whitedune (- to 0.30.10-2.2)
  • Migration status for whitedune (- to 0.30.10-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • whitedune/armel has unsatisfiable dependency
    • whitedune/armhf has unsatisfiable dependency
    • Updating whitedune would introduce bugs in testing: #1036881, #1067618
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whitedune.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 2192 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
    • 2194 days old (needed 5 days)
• node-trust-webcrypto (- to 0.9.2-1)
  • Migration status for node-trust-webcrypto (- to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-trust-webcrypto would introduce bugs in testing: #1002262
    • autopkgtest for node-trust-webcrypto/0.9.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): node-trust-webcrypto node-node-rsa (not considered)
    • Depends: node-trust-webcrypto node-node-rsa (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-trust-webcrypto.html
    • 2198 days old (needed 5 days)
• sqwebmail-de (- to 6.0.0-1)
  • Migration status for sqwebmail-de (- to 6.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sqwebmail-de would introduce bugs in testing: #1093360
    • Build-Depends(-Arch): sqwebmail-de courier (not considered)
    • Built-Using: sqwebmail-de courier (not considered)
    • Depends: sqwebmail-de courier (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqwebmail-de.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 2208 days old (needed 5 days)
• pgcharts (- to 1.0+2017-09-16-1)
  • Migration status for pgcharts (- to 1.0+2017-09-16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pgcharts would introduce bugs in testing: #1024642
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2223 days old (needed 5 days)
• vorbis-java (- to 0.8-3)
  • Migration status for vorbis-java (- to 0.8-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vorbis-java tika (not considered)
    • Depends: vorbis-java tika (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vorbis-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2229 days old (needed 5 days)
• gforth (- to 0.7.3+dfsg-9)
  • Migration status for gforth (- to 0.7.3+dfsg-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gforth would introduce bugs in testing: #1067376
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gforth.html
    • autopkgtest for gforth/0.7.3+dfsg-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2232 days old (needed 2 days)
• jawn (- to 0.11.1+really0.6.0-1)
  • Migration status for jawn (- to 0.11.1+really0.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): jawn scala (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): jawn json4s
    • Depends: jawn json4s
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jawn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2282 days old (needed 5 days)
• json4s (- to 3.5.1+really3.2.10-1)
  • Migration status for json4s (- to 3.5.1+really3.2.10-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): json4s scala (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/json4s.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 2282 days old (needed 5 days)
• sbt-serialization (- to 0.1.2+repack-1)
  • Migration status for sbt-serialization (- to 0.1.2+repack-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sbt-serialization scala (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): sbt-serialization jawn
    • Build-Depends(-Arch): sbt-serialization json4s
    • Build-Depends(-Arch): sbt-serialization scala-pickling
    • Depends: sbt-serialization jawn
    • Depends: sbt-serialization json4s
    • Depends: sbt-serialization scala-pickling
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbt-serialization.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 2282 days old (needed 5 days)
• scala-pickling (- to 0.10.1+repack-2)
  • Migration status for scala-pickling (- to 0.10.1+repack-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): scala-pickling scala (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scala-pickling.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 2282 days old (needed 5 days)
• scopt (- to 3.5.0+repack-1)
  • Migration status for scopt (- to 3.5.0+repack-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): scopt scala (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scopt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2283 days old (needed 5 days)
• xcircuit (- to 3.9.73+dfsg.1-1)
  • Migration status for xcircuit (- to 3.9.73+dfsg.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xcircuit would introduce bugs in testing: #1066600
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcircuit.html
    • 2287 days old (needed 5 days)
• amp (- to 0.6.1-1)
  • Migration status for amp (- to 0.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-amp/amd64 has unsatisfiable dependency
    • python3-amp/arm64 has unsatisfiable dependency
    • python3-amp/armel has unsatisfiable dependency
    • python3-amp/armhf has unsatisfiable dependency
    • python3-amp/i386 has unsatisfiable dependency
    • python3-amp/mips64el has unsatisfiable dependency
    • python3-amp/ppc64el has unsatisfiable dependency
    • python3-amp/riscv64 has unsatisfiable dependency
    • python3-amp/s390x has unsatisfiable dependency
    • Updating amp would introduce bugs in testing: #1018305, #1067375, #1086577
    • Build-Depends(-Arch): amp python-ase (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/amp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2299 days old (needed 5 days)
• sn (- to 0.3.8-12)
  • Migration status for sn (- to 0.3.8-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sn would introduce bugs in testing: #1075519
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sn.html
    • 2299 days old (needed 5 days)
• djinn (- to 2014.9.7-9)
  • Migration status for djinn (- to 2014.9.7-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating djinn would introduce bugs in testing: #1083254
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/djinn.html
    • 2323 days old (needed 5 days)
• only (- to 0.0.6.0-2)
  • Migration status for only (- to 0.0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating only would introduce bugs in testing: #1085428
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/only.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2324 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: #1067173, #961834
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clearlooks-phenix-theme.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2343 days old (needed 5 days)
• chessx (- to 1.4.6-2)
  • Migration status for chessx (- to 1.4.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chessx would introduce bugs in testing: #1074880
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chessx.html
    • 2352 days old (needed 5 days)
• globjects (- to 1.1.0-3)
  • Migration status for globjects (- to 1.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libglobjects1/amd64 has unsatisfiable dependency
    • libglobjects1/arm64 has unsatisfiable dependency
    • libglobjects1/armel has unsatisfiable dependency
    • libglobjects1/armhf has unsatisfiable dependency
    • libglobjects1/i386 has unsatisfiable dependency
    • libglobjects1/mips64el has unsatisfiable dependency
    • libglobjects1/ppc64el has unsatisfiable dependency
    • libglobjects1/riscv64 has unsatisfiable dependency
    • libglobjects1/s390x has unsatisfiable dependency
    • Updating globjects would introduce bugs in testing: #1090229
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globjects.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2416 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 (not considered)
    • Depends: erlang-cowboy erlang-ranch (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang-cowboy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2443 days old (needed 5 days)
• ruby-rjb (- to 1.5.5-3)
  • Migration status for ruby-rjb (- to 1.5.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rjb would introduce bugs in testing: #1075477
    • autopkgtest for ruby-rjb/1.5.5-3: amd64: Regression or new test ♻, i386: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rjb.html
    • 2473 days old (needed 5 days)
• dita-ot (- to 1.5.3+dfsg-1)
  • Migration status for dita-ot (- to 1.5.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dita-ot would introduce bugs in testing: #1092375
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dita-ot.html
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 2496 days old (needed 5 days)
• whowatch (- to 1.8.6-1)
  • Migration status for whowatch (- to 1.8.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating whowatch would introduce bugs in testing: #1091295
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whowatch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 2500 days old (needed 5 days)
• ruby-gitlab-flowdock-git-hook (- to 1.0.1-4)
  • Migration status for ruby-gitlab-flowdock-git-hook (- to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gitlab-flowdock-git-hook would introduce bugs in testing: #1092695
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-flowdock-git-hook.html
    • autopkgtest for ruby-gitlab-flowdock-git-hook/1.0.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2521 days old (needed 2 days)
• ruby-redis-rails (- to 5.0.2-3)
  • Migration status for ruby-redis-rails (- to 5.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-redis-rails would introduce bugs in testing: #1095383
    • Build-Depends(-Arch): ruby-redis-rails ruby-redis-actionpack (not considered)
    • Build-Depends(-Arch): ruby-redis-rails ruby-redis-activesupport (not considered)
    • Build-Depends(-Arch): ruby-redis-rails ruby-redis-rack (not considered)
    • Depends: ruby-redis-rails ruby-redis-actionpack (not considered)
    • Depends: ruby-redis-rails ruby-redis-activesupport (not considered)
    • Depends: ruby-redis-rails ruby-redis-rack (not considered)
  • 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2545 days old (needed 2 days)
• metis-edf (- to 4.1-2-4)
  • Migration status for metis-edf (- to 4.1-2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating metis-edf would introduce bugs in testing: #1066955
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2575 days old (needed 5 days)
• similarity-tester (- to 3.0.2-1)
  • Migration status for similarity-tester (- to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating similarity-tester would introduce bugs in testing: #1066293
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/similarity-tester.html
    • 2595 days old (needed 5 days)
• dapl (- to 2.1.10.1.f1e05b7a-3)
  • Migration status for dapl (- to 2.1.10.1.f1e05b7a-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dapl would introduce bugs in testing: #1066540
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dapl.html
    • 2597 days old (needed 5 days)
• debtags (- to 2.1.5)
  • Migration status for debtags (- to 2.1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debtags would introduce bugs in testing: #1058262, #1094655
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debtags.html
    • 2597 days old (needed 5 days)
• tz-converter (- to 1.0.1-1)
  • Migration status for tz-converter (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tz-converter would introduce bugs in testing: #1038851
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tz-converter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2599 days old (needed 5 days)
• virtualjaguar (- to 2.1.3-2)
  • Migration status for virtualjaguar (- to 2.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtualjaguar would introduce bugs in testing: #1066383
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virtualjaguar.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 2617 days old (needed 5 days)
• urweb (- to 20170720+dfsg-2)
  • Migration status for urweb (- to 20170720+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liburweb0/armel has unsatisfiable dependency
    • liburweb0/armhf has unsatisfiable dependency
    • liburweb0/ppc64el has unsatisfiable dependency
    • Updating urweb would introduce bugs in testing: #1060107
    • Build-Depends(-Arch): urweb mlton (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urweb.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 2705 days old (needed 5 days)
• endless-sky-high-dpi (- to 0.9.8-1)
  • Migration status for endless-sky-high-dpi (- to 0.9.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: endless-sky-high-dpi endless-sky (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/endless-sky-high-dpi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2735 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-twitter would introduce bugs in testing: #1094563
  • 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, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2765 days old (needed 2 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
    • Build-Depends(-Arch): verilog-mode xemacs21 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/verilog-mode.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2962 days old (needed 5 days)
• ruby-celluloid-io (- to 0.16.2-5)
  • Migration status for ruby-celluloid-io (- to 0.16.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-celluloid-io would introduce bugs in testing: #1031476
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-celluloid-io.html
    • autopkgtest for ruby-celluloid-io/0.16.2-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • 2972 days old (needed 5 days)
• simpleproxy (- to 3.5-1)
  • Migration status for simpleproxy (- to 3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simpleproxy would introduce bugs in testing: #1075512
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simpleproxy.html
    • 3015 days old (needed 5 days)
• ccd2iso (- to 0.3-7)
  • Migration status for ccd2iso (- to 0.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ccd2iso would introduce bugs in testing: #1066265
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ccd2iso.html
    • 3053 days old (needed 5 days)
• i2util (- to 1.6-1)
  • Migration status for i2util (- to 1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating i2util would introduce bugs in testing: #1075076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i2util.html
    • 3067 days old (needed 5 days)
• spellcast (- to 1.0-22)
  • Migration status for spellcast (- to 1.0-22): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spellcast would introduce bugs in testing: #1077895
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 3089 days old (needed 5 days)
• ecere-sdk (- to 0.44.15-1)
  • Migration status for ecere-sdk (- to 0.44.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libedasqlite0/amd64 has unsatisfiable dependency
    • libedasqlite0/arm64 has unsatisfiable dependency
    • libecere0/armel has unsatisfiable dependency
    • libecereaudio0/armel has unsatisfiable dependency
    • libedasqlite0/armel has unsatisfiable dependency
    • libecere0/armhf has unsatisfiable dependency
    • libecereaudio0/armhf has unsatisfiable dependency
    • libedasqlite0/armhf has unsatisfiable dependency
    • libecere0/i386 has unsatisfiable dependency
    • libedasqlite0/i386 has unsatisfiable dependency
    • libedasqlite0/mips64el has unsatisfiable dependency
    • libedasqlite0/ppc64el has unsatisfiable dependency
    • libedasqlite0/s390x has unsatisfiable dependency
    • Updating ecere-sdk would introduce bugs in testing: #898832, #995050
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on amd64: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on arm64: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on armel: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on armhf: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on i386: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on mips64el: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on ppc64el: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on s390x: libgl1-mesa-glx
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/ecere-sdk.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 3113 days old (needed 5 days)
• flexml (- to 1.9.6-5)
  • Migration status for flexml (- to 1.9.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flexml would introduce bugs in testing: #1092424
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flexml.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3178 days old (needed 5 days)
• netrw (- to 1.3.2-3)
  • Migration status for netrw (- to 1.3.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netrw would introduce bugs in testing: #1066538
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netrw.html
    • 3215 days old (needed 5 days)
• subtle (- to 0.11.3224-xi-2.2)
  • Migration status for subtle (- to 0.11.3224-xi-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating subtle would introduce bugs in testing: #1075542
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/subtle.html
    • 3268 days old (needed 5 days)
• libr3 (- to 1.3.4-1)
  • Migration status for libr3 (- to 1.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libr3-0/amd64 has unsatisfiable dependency
    • libr3-dev/amd64 has unsatisfiable dependency
    • libr3-0/arm64 has unsatisfiable dependency
    • libr3-dev/arm64 has unsatisfiable dependency
    • libr3-0/armel has unsatisfiable dependency
    • libr3-dev/armel has unsatisfiable dependency
    • libr3-0/armhf has unsatisfiable dependency
    • libr3-dev/armhf has unsatisfiable dependency
    • libr3-0/i386 has unsatisfiable dependency
    • libr3-dev/i386 has unsatisfiable dependency
    • libr3-0/mips64el has unsatisfiable dependency
    • libr3-dev/mips64el has unsatisfiable dependency
    • libr3-0/ppc64el has unsatisfiable dependency
    • libr3-dev/ppc64el has unsatisfiable dependency
    • libr3-0/riscv64 has unsatisfiable dependency
    • libr3-dev/riscv64 has unsatisfiable dependency
    • libr3-0/s390x has unsatisfiable dependency
    • libr3-dev/s390x has unsatisfiable dependency
    • Updating libr3 would introduce bugs in testing: #1000058
    • libr3 unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on armel: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on mips64el: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • libr3 unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libr3.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 3293 days old (needed 5 days)
• nvram-wakeup (- to 1.1-4)
  • Migration status for nvram-wakeup (- to 1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvram-wakeup would introduce bugs in testing: #1074757
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nvram-wakeup.html
    • 3403 days old (needed 5 days)
• psicode (- to 3.4.0-6)
  • Migration status for psicode (- to 3.4.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating psicode would introduce bugs in testing: #1075399
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psicode.html
    • 3438 days old (needed 5 days)
• etoys (- to 5.0.2408-1)
  • Migration status for etoys (- to 5.0.2408-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: etoys squeak-vm (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 3520 days old (needed 5 days)
• mysecureshell (- to 2.0-2)
  • Migration status for mysecureshell (- to 2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysecureshell would introduce bugs in testing: #1092430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysecureshell.html
    • Reproducible on i386 - info ♻
    • 3738 days old (needed 5 days)
• ddate (- to 0.2.2-1)
  • Migration status for ddate (- to 0.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ddate would introduce bugs in testing: #1091251
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/ddate.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 3764 days old (needed 5 days)
• tvoe (- to 0.1-1)
  • Migration status for tvoe (- to 0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tvoe would introduce bugs in testing: #1075592
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tvoe.html
    • 3765 days old (needed 5 days)
• xshogi (- to 1.4.2-2)
  • Migration status for xshogi (- to 1.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xshogi/armel has unsatisfiable dependency
    • xshogi/armhf has unsatisfiable dependency
    • Updating xshogi would introduce bugs in testing: #1066582
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xshogi.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 3822 days old (needed 5 days)
• binutils-h8300-hms (- to 2.16.1-10)
  • Migration status for binutils-h8300-hms (- to 2.16.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils-h8300-hms would introduce bugs in testing: #1066236
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-h8300-hms.html
    • 3882 days old (needed 5 days)
• couriergrey (- to 0.3.2-5)
  • Migration status for couriergrey (- to 0.3.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: couriergrey courier (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/couriergrey.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 4044 days old (needed 5 days)
• reminiscence (- to 0.2.1-2)
  • Migration status for reminiscence (- to 0.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating reminiscence would introduce bugs in testing: #985184
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4132 days old (needed 5 days)
• xserver-xorg-video-ivtvdev (- to 1.1.2-2)
  • Migration status for xserver-xorg-video-ivtvdev (- to 1.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-ivtvdev would introduce bugs in testing: #1078229
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4160 days old (needed 5 days)
• wap-wml-tools (- to 0.0.4-7)
  • Migration status for wap-wml-tools (- to 0.0.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wap-wml-tools would introduce bugs in testing: #1067024
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4193 days old (needed 5 days)
• xfishtank (- to 2.5-1)
  • Migration status for xfishtank (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfishtank would introduce bugs in testing: #1075662
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfishtank.html
    • 4194 days old (needed 5 days)
• libapache2-mod-authn-sasl (- to 1.2-2)
  • Migration status for libapache2-mod-authn-sasl (- to 1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-authn-sasl would introduce bugs in testing: #1075139
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-authn-sasl.html
    • 4260 days old (needed 5 days)
• i810switch (- to 0.6.5-7.1)
  • Migration status for i810switch (- to 0.6.5-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating i810switch would introduce bugs in testing: #1075078
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i810switch.html
    • 4296 days old (needed 5 days)
• mumudvb (- to 1.7.1-1)
  • Migration status for mumudvb (- to 1.7.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): mumudvb linuxtv-dvb-apps (not considered)
    • Depends: mumudvb linuxtv-dvb-apps (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mumudvb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 4610 days old (needed 5 days)
• aggregate (- to 1.6-7)
  • Migration status for aggregate (- to 1.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aggregate would introduce bugs in testing: #1074803
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aggregate.html
    • 4671 days old (needed 5 days)