Generated: 2024.09.14 02:05:12 +0000

• -bioperl-run (1.7.3-11 to -)
  • Migration status for -bioperl-run (1.7.3-11 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -getdns (1.6.0-3.1 to -)
  • Migration status for -getdns (1.6.0-3.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -hplip (3.22.10+dfsg0-5.1 to -)
  • Migration status for -hplip (3.22.10+dfsg0-5.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
• -kotlin (1.3.31+ds1-1 to -)
  • Migration status for -kotlin (1.3.31+ds1-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
• -sentry-python (1.40.4-3 to -)
  • Migration status for -sentry-python (1.40.4-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
• 2048-qt/riscv64 (0.1.6-2 to 0.1.6-2)
  • Migration status for 2048-qt/riscv64 (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• 4pane/riscv64 (8.0-1 to 8.0-1)
  • Migration status for 4pane/riscv64 (8.0-1 to 8.0-1): Will attempt migration (Any information below is purely informational)
• abgate/riscv64 (1.2.0-2 to 1.2.0-2)
  • Migration status for abgate/riscv64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• abx/riscv64 (0.0~b1-1 to 0.0~b1-1)
  • Migration status for abx/riscv64 (0.0~b1-1 to 0.0~b1-1): Will attempt migration (Any information below is purely informational)
• acetoneiso/riscv64 (2.4-4 to 2.4-4)
  • Migration status for acetoneiso/riscv64 (2.4-4 to 2.4-4): Will attempt migration (Any information below is purely informational)
• achilles/riscv64 (2-12 to 2-12)
  • Migration status for achilles/riscv64 (2-12 to 2-12): Will attempt migration (Any information below is purely informational)
• aclock.app/riscv64 (0.4.0-2 to 0.4.0-2)
  • Migration status for aclock.app/riscv64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• 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
• 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
• 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
• 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
• 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
• 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
• 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
• 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): Will attempt migration (Any information below is purely informational)
    • Built-Using: acmetool/s390x golang-1.23
• actiona/riscv64 (3.10.1-1 to 3.10.1-1)
  • Migration status for actiona/riscv64 (3.10.1-1 to 3.10.1-1): Will attempt migration (Any information below is purely informational)
• adequate/amd64 (0.16.18 to 0.16.18)
  • Migration status for adequate/amd64 (0.16.18 to 0.16.18): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/amd64 golang-1.23
• adequate/arm64 (0.16.18 to 0.16.18)
  • Migration status for adequate/arm64 (0.16.18 to 0.16.18): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/arm64 golang-1.23
• adequate/armel (0.16.18 to 0.16.18)
  • Migration status for adequate/armel (0.16.18 to 0.16.18): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/armel golang-1.23
• adequate/armhf (0.16.18 to 0.16.18)
  • Migration status for adequate/armhf (0.16.18 to 0.16.18): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/armhf golang-1.23
• adequate/i386 (0.16.18 to 0.16.18)
  • Migration status for adequate/i386 (0.16.18 to 0.16.18): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/i386 golang-1.23
• adequate/mips64el (0.16.18 to 0.16.18)
  • Migration status for adequate/mips64el (0.16.18 to 0.16.18): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/mips64el golang-1.23
• adequate/ppc64el (0.16.18 to 0.16.18)
  • Migration status for adequate/ppc64el (0.16.18 to 0.16.18): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/ppc64el golang-1.23
• adequate/s390x (0.16.18 to 0.16.18)
  • Migration status for adequate/s390x (0.16.18 to 0.16.18): Will attempt migration (Any information below is purely informational)
    • Built-Using: adequate/s390x golang-1.23
• adios2/riscv64 (2.9.2+dfsg1-13 to 2.9.2+dfsg1-13)
  • Migration status for adios2/riscv64 (2.9.2+dfsg1-13 to 2.9.2+dfsg1-13): Will attempt migration (Any information below is purely informational)
• adun.app/riscv64 (0.81-14 to 0.81-14)
  • Migration status for adun.app/riscv64 (0.81-14 to 0.81-14): Will attempt migration (Any information below is purely informational)
• adwaita-qt/riscv64 (1.4.2-3 to 1.4.2-3)
  • Migration status for adwaita-qt/riscv64 (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
• aerc/amd64 (0.18.2-2 to 0.18.2-2)
  • Migration status for aerc/amd64 (0.18.2-2 to 0.18.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/amd64 golang-1.23
• aerc/arm64 (0.18.2-2 to 0.18.2-2)
  • Migration status for aerc/arm64 (0.18.2-2 to 0.18.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/arm64 golang-1.23
• aerc/armel (0.18.2-2 to 0.18.2-2)
  • Migration status for aerc/armel (0.18.2-2 to 0.18.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/armel golang-1.23
• aerc/armhf (0.18.2-2 to 0.18.2-2)
  • Migration status for aerc/armhf (0.18.2-2 to 0.18.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/armhf golang-1.23
• aerc/i386 (0.18.2-2 to 0.18.2-2)
  • Migration status for aerc/i386 (0.18.2-2 to 0.18.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/i386 golang-1.23
• aerc/ppc64el (0.18.2-2 to 0.18.2-2)
  • Migration status for aerc/ppc64el (0.18.2-2 to 0.18.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/ppc64el golang-1.23
• aerc/s390x (0.18.2-2 to 0.18.2-2)
  • Migration status for aerc/s390x (0.18.2-2 to 0.18.2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aerc/s390x golang-1.23
• afterstep/riscv64 (2.2.12-17.1 to 2.2.12-17.1)
  • Migration status for afterstep/riscv64 (2.2.12-17.1 to 2.2.12-17.1): Will attempt migration (Any information below is purely informational)
• age/amd64 (1.1.1-1 to 1.1.1-1)
  • Migration status for age/amd64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/amd64 golang-1.23
• age/arm64 (1.1.1-1 to 1.1.1-1)
  • Migration status for age/arm64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/arm64 golang-1.23
• age/armel (1.1.1-1 to 1.1.1-1)
  • Migration status for age/armel (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/armel golang-1.23
• age/armhf (1.1.1-1 to 1.1.1-1)
  • Migration status for age/armhf (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/armhf golang-1.23
• age/i386 (1.1.1-1 to 1.1.1-1)
  • Migration status for age/i386 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/i386 golang-1.23
• age/mips64el (1.1.1-1 to 1.1.1-1)
  • Migration status for age/mips64el (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/mips64el golang-1.23
• age/ppc64el (1.1.1-1 to 1.1.1-1)
  • Migration status for age/ppc64el (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/ppc64el golang-1.23
• age/s390x (1.1.1-1 to 1.1.1-1)
  • Migration status for age/s390x (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: age/s390x golang-1.23
• agenda.app/riscv64 (0.46-3 to 0.46-3)
  • Migration status for agenda.app/riscv64 (0.46-3 to 0.46-3): Will attempt migration (Any information below is purely informational)
• aghermann/riscv64 (1.1.2-5 to 1.1.2-5)
  • Migration status for aghermann/riscv64 (1.1.2-5 to 1.1.2-5): Will attempt migration (Any information below is purely informational)
• akonadi-calendar-tools/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for akonadi-calendar-tools/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• akonadi-calendar/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for akonadi-calendar/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• akonadi-contacts/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for akonadi-contacts/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• akonadi-mime/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for akonadi-mime/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• akonadi-notes/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for akonadi-notes/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• akonadi-search/riscv64 (4:22.12.3-1.1 to 4:22.12.3-1.1)
  • Migration status for akonadi-search/riscv64 (4:22.12.3-1.1 to 4:22.12.3-1.1): Will attempt migration (Any information below is purely informational)
• akonadi/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for akonadi/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• alarm-clock-applet/riscv64 (0.4.1-5 to 0.4.1-5)
  • Migration status for alarm-clock-applet/riscv64 (0.4.1-5 to 0.4.1-5): Will attempt migration (Any information below is purely informational)
• 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/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): Will attempt migration (Any information below is purely informational)
    • Built-Using: alertmanager-irc-relay/s390x golang-1.23
• alkimia/riscv64 (8.1.2-2 to 8.1.2-2)
  • Migration status for alkimia/riscv64 (8.1.2-2 to 8.1.2-2): Will attempt migration (Any information below is purely informational)
• allegro5/riscv64 (2:5.2.9.1+dfsg-2 to 2:5.2.9.1+dfsg-2)
  • Migration status for allegro5/riscv64 (2:5.2.9.1+dfsg-2 to 2:5.2.9.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• alsa-scarlett-gui/riscv64 (0.4.0-1 to 0.4.0-1)
  • Migration status for alsa-scarlett-gui/riscv64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• amazon-ecr-credential-helper/amd64 (0.7.1-1 to 0.7.1-1)
  • Migration status for amazon-ecr-credential-helper/amd64 (0.7.1-1 to 0.7.1-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-1 to 0.7.1-1)
  • Migration status for amazon-ecr-credential-helper/arm64 (0.7.1-1 to 0.7.1-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-1 to 0.7.1-1)
  • Migration status for amazon-ecr-credential-helper/armel (0.7.1-1 to 0.7.1-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-1 to 0.7.1-1)
  • Migration status for amazon-ecr-credential-helper/armhf (0.7.1-1 to 0.7.1-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-1 to 0.7.1-1)
  • Migration status for amazon-ecr-credential-helper/i386 (0.7.1-1 to 0.7.1-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-1 to 0.7.1-1)
  • Migration status for amazon-ecr-credential-helper/mips64el (0.7.1-1 to 0.7.1-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-1 to 0.7.1-1)
  • Migration status for amazon-ecr-credential-helper/ppc64el (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: amazon-ecr-credential-helper/ppc64el golang-1.23
• amazon-ecr-credential-helper/s390x (0.7.1-1 to 0.7.1-1)
  • Migration status for amazon-ecr-credential-helper/s390x (0.7.1-1 to 0.7.1-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
• 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
• 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
• 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
• 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
• 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): Will attempt migration (Any information below is purely informational)
    • Built-Using: amfora/mips64el golang-1.23
• 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
• 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): Will attempt migration (Any information below is purely informational)
    • Built-Using: amfora/s390x golang-1.23
• amoeba/riscv64 (1.1-31 to 1.1-31)
  • Migration status for amoeba/riscv64 (1.1-31 to 1.1-31): Will attempt migration (Any information below is purely informational)
• ams/riscv64 (2.2.1-1 to 2.2.1-1)
  • Migration status for ams/riscv64 (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
• amule/riscv64 (1:2.3.3-3 to 1:2.3.3-3)
  • Migration status for amule/riscv64 (1:2.3.3-3 to 1:2.3.3-3): Will attempt migration (Any information below is purely informational)
• analitza/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for analitza/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• android-file-transfer/riscv64 (4.3-1 to 4.3-1)
  • Migration status for android-file-transfer/riscv64 (4.3-1 to 4.3-1): Will attempt migration (Any information below is purely informational)
• 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
• 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
• 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
• 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
• 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
• 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
• 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
• 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
• ansifilter/riscv64 (2.20+repack1-1 to 2.20+repack1-1)
  • Migration status for ansifilter/riscv64 (2.20+repack1-1 to 2.20+repack1-1): Will attempt migration (Any information below is purely informational)
• antigrav/riscv64 (0.0.3-10 to 0.0.3-10)
  • Migration status for antigrav/riscv64 (0.0.3-10 to 0.0.3-10): Will attempt migration (Any information below is purely informational)
• antimicro/riscv64 (3.1.4-2 to 3.1.4-2)
  • Migration status for antimicro/riscv64 (3.1.4-2 to 3.1.4-2): Will attempt migration (Any information below is purely informational)
• antimony/riscv64 (0.9.3-2 to 0.9.3-2)
  • Migration status for antimony/riscv64 (0.9.3-2 to 0.9.3-2): Will attempt migration (Any information below is purely informational)
• antpm/riscv64 (1.21-1 to 1.21-1)
  • Migration status for antpm/riscv64 (1.21-1 to 1.21-1): Will attempt migration (Any information below is purely informational)
• aoflagger/riscv64 (3.4.0-2 to 3.4.0-2)
  • Migration status for aoflagger/riscv64 (3.4.0-2 to 3.4.0-2): Will attempt migration (Any information below is purely informational)
• apache-upload-progress-module/riscv64 (0.2-2 to 0.2-2)
  • Migration status for apache-upload-progress-module/riscv64 (0.2-2 to 0.2-2): Will attempt migration (Any information below is purely informational)
• apache2-mod-xforward/riscv64 (0.6-1 to 0.6-1)
  • Migration status for apache2-mod-xforward/riscv64 (0.6-1 to 0.6-1): Will attempt migration (Any information below is purely informational)
• apertium-anaphora/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for apertium-anaphora/riscv64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• apertium-lex-tools/riscv64 (0.4.2-2 to 0.4.2-2)
  • Migration status for apertium-lex-tools/riscv64 (0.4.2-2 to 0.4.2-2): Will attempt migration (Any information below is purely informational)
• apertium-recursive/riscv64 (1.1.2-1 to 1.1.2-1)
  • Migration status for apertium-recursive/riscv64 (1.1.2-1 to 1.1.2-1): Will attempt migration (Any information below is purely informational)
• apertium-separable/riscv64 (0.6.1-1 to 0.6.1-1)
  • Migration status for apertium-separable/riscv64 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• apertium/riscv64 (3.9.4-1 to 3.9.4-1)
  • Migration status for apertium/riscv64 (3.9.4-1 to 3.9.4-1): Will attempt migration (Any information below is purely informational)
• apitrace/riscv64 (11.1+repack-1.2 to 11.1+repack-1.2)
  • Migration status for apitrace/riscv64 (11.1+repack-1.2 to 11.1+repack-1.2): Will attempt migration (Any information below is purely informational)
• apostrophe/riscv64 (2.6.3-4 to 2.6.3-4)
  • Migration status for apostrophe/riscv64 (2.6.3-4 to 2.6.3-4): Will attempt migration (Any information below is purely informational)
• apper/riscv64 (1.0.0-5 to 1.0.0-5)
  • Migration status for apper/riscv64 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• appstream-glib/riscv64 (0.8.2-1.1 to 0.8.2-1.1)
  • Migration status for appstream-glib/riscv64 (0.8.2-1.1 to 0.8.2-1.1): Will attempt migration (Any information below is purely informational)
• appstream/riscv64 (1.0.3-1 to 1.0.3-1)
  • Migration status for appstream/riscv64 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• apt-dater/riscv64 (1.0.4-8 to 1.0.4-8)
  • Migration status for apt-dater/riscv64 (1.0.4-8 to 1.0.4-8): Will attempt migration (Any information below is purely informational)
• aptly/amd64 (1.5.0+ds1-2 to 1.5.0+ds1-2)
  • Migration status for aptly/amd64 (1.5.0+ds1-2 to 1.5.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/amd64 golang-1.23
• aptly/arm64 (1.5.0+ds1-2 to 1.5.0+ds1-2)
  • Migration status for aptly/arm64 (1.5.0+ds1-2 to 1.5.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/arm64 golang-1.23
• aptly/armel (1.5.0+ds1-2 to 1.5.0+ds1-2)
  • Migration status for aptly/armel (1.5.0+ds1-2 to 1.5.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/armel golang-1.23
• aptly/armhf (1.5.0+ds1-2 to 1.5.0+ds1-2)
  • Migration status for aptly/armhf (1.5.0+ds1-2 to 1.5.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/armhf golang-1.23
• aptly/i386 (1.5.0+ds1-2 to 1.5.0+ds1-2)
  • Migration status for aptly/i386 (1.5.0+ds1-2 to 1.5.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/i386 golang-1.23
• aptly/ppc64el (1.5.0+ds1-2 to 1.5.0+ds1-2)
  • Migration status for aptly/ppc64el (1.5.0+ds1-2 to 1.5.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/ppc64el golang-1.23
• aptly/s390x (1.5.0+ds1-2 to 1.5.0+ds1-2)
  • Migration status for aptly/s390x (1.5.0+ds1-2 to 1.5.0+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: aptly/s390x golang-1.23
• apwal/riscv64 (0.4.5-1.2 to 0.4.5-1.2)
  • Migration status for apwal/riscv64 (0.4.5-1.2 to 0.4.5-1.2): Will attempt migration (Any information below is purely informational)
• arc-gui-clients/riscv64 (0.4.6-7 to 0.4.6-7)
  • Migration status for arc-gui-clients/riscv64 (0.4.6-7 to 0.4.6-7): Will attempt migration (Any information below is purely informational)
• arduino-builder/amd64 (1.3.25-4 to 1.3.25-4)
  • Migration status for arduino-builder/amd64 (1.3.25-4 to 1.3.25-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: arduino-builder/amd64 golang-1.23
• arduino-builder/arm64 (1.3.25-4 to 1.3.25-4)
  • Migration status for arduino-builder/arm64 (1.3.25-4 to 1.3.25-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: arduino-builder/arm64 golang-1.23
• arduino-builder/armel (1.3.25-4 to 1.3.25-4)
  • Migration status for arduino-builder/armel (1.3.25-4 to 1.3.25-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: arduino-builder/armel golang-1.23
• arduino-builder/armhf (1.3.25-4 to 1.3.25-4)
  • Migration status for arduino-builder/armhf (1.3.25-4 to 1.3.25-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: arduino-builder/armhf golang-1.23
• arduino-builder/i386 (1.3.25-4 to 1.3.25-4)
  • Migration status for arduino-builder/i386 (1.3.25-4 to 1.3.25-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: arduino-builder/i386 golang-1.23
• arduino-builder/mips64el (1.3.25-4 to 1.3.25-4)
  • Migration status for arduino-builder/mips64el (1.3.25-4 to 1.3.25-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: arduino-builder/mips64el golang-1.23
• arduino-builder/ppc64el (1.3.25-4 to 1.3.25-4)
  • Migration status for arduino-builder/ppc64el (1.3.25-4 to 1.3.25-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: arduino-builder/ppc64el golang-1.23
• arduino-builder/s390x (1.3.25-4 to 1.3.25-4)
  • Migration status for arduino-builder/s390x (1.3.25-4 to 1.3.25-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: arduino-builder/s390x golang-1.23
• ariba/riscv64 (2.14.7+ds-2 to 2.14.7+ds-2)
  • Migration status for ariba/riscv64 (2.14.7+ds-2 to 2.14.7+ds-2): Will attempt migration (Any information below is purely informational)
• ario/riscv64 (1.6-1.2 to 1.6-1.2)
  • Migration status for ario/riscv64 (1.6-1.2 to 1.6-1.2): Will attempt migration (Any information below is purely informational)
• ark/riscv64 (4:23.08.5-1 to 4:23.08.5-1)
  • Migration status for ark/riscv64 (4:23.08.5-1 to 4:23.08.5-1): Will attempt migration (Any information below is purely informational)
• armagetronad/riscv64 (0.2.9.1.1-1 to 0.2.9.1.1-1)
  • Migration status for armagetronad/riscv64 (0.2.9.1.1-1 to 0.2.9.1.1-1): Will attempt migration (Any information below is purely informational)
• arpys/riscv64 (1:1.0.0~git20230217101414.07b63b3-1 to 1:1.0.0~git20230217101414.07b63b3-1)
  • Migration status for arpys/riscv64 (1:1.0.0~git20230217101414.07b63b3-1 to 1:1.0.0~git20230217101414.07b63b3-1): Will attempt migration (Any information below is purely informational)
• arqiver/riscv64 (0.9.0-1 to 0.9.0-1)
  • Migration status for arqiver/riscv64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• artikulate/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for artikulate/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• asc/riscv64 (2.6.1.0-9 to 2.6.1.0-9)
  • Migration status for asc/riscv64 (2.6.1.0-9 to 2.6.1.0-9): Will attempt migration (Any information below is purely informational)
• asl/riscv64 (0.1.7-4.1 to 0.1.7-4.1)
  • Migration status for asl/riscv64 (0.1.7-4.1 to 0.1.7-4.1): Will attempt migration (Any information below is purely informational)
• assaultcube/riscv64 (1.3.0.2+dfsg-5 to 1.3.0.2+dfsg-5)
  • Migration status for assaultcube/riscv64 (1.3.0.2+dfsg-5 to 1.3.0.2+dfsg-5): Will attempt migration (Any information below is purely informational)
• 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/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
• astromenace/riscv64 (1.3.2+repack-7 to 1.3.2+repack-7)
  • Migration status for astromenace/riscv64 (1.3.2+repack-7 to 1.3.2+repack-7): Will attempt migration (Any information below is purely informational)
• asunder/riscv64 (3.0.1+ds-1 to 3.0.1+ds-1)
  • Migration status for asunder/riscv64 (3.0.1+ds-1 to 3.0.1+ds-1): Will attempt migration (Any information below is purely informational)
• asylum/riscv64 (0.3.2-3 to 0.3.2-3)
  • Migration status for asylum/riscv64 (0.3.2-3 to 0.3.2-3): Will attempt migration (Any information below is purely informational)
• asyncfuture/riscv64 (0~0.1-1 to 0~0.1-1)
  • Migration status for asyncfuture/riscv64 (0~0.1-1 to 0~0.1-1): Will attempt migration (Any information below is purely informational)
• atomes/riscv64 (1.1.14-1.1 to 1.1.14-1.1)
  • Migration status for atomes/riscv64 (1.1.14-1.1 to 1.1.14-1.1): Will attempt migration (Any information below is purely informational)
• atomix/riscv64 (44.0-3 to 44.0-3)
  • Migration status for atomix/riscv64 (44.0-3 to 44.0-3): Will attempt migration (Any information below is purely informational)
• attica-kf5/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for attica-kf5/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• audacious-plugins/riscv64 (4.3.1-3 to 4.3.1-3)
  • Migration status for audacious-plugins/riscv64 (4.3.1-3 to 4.3.1-3): Will attempt migration (Any information below is purely informational)
• audacious/riscv64 (4.3.1-2.1 to 4.3.1-2.1)
  • Migration status for audacious/riscv64 (4.3.1-2.1 to 4.3.1-2.1): Will attempt migration (Any information below is purely informational)
• audiocd-kio/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for audiocd-kio/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• audmes/riscv64 (2024.02.18-1 to 2024.02.18-1)
  • Migration status for audmes/riscv64 (2024.02.18-1 to 2024.02.18-1): Will attempt migration (Any information below is purely informational)
• augeas/riscv64 (1.14.1-1 to 1.14.1-1)
  • Migration status for augeas/riscv64 (1.14.1-1 to 1.14.1-1): Will attempt migration (Any information below is purely informational)
• auralquiz/riscv64 (1.0.0-3 to 1.0.0-3)
  • Migration status for auralquiz/riscv64 (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
• auto-multiple-choice/riscv64 (1.6.0-3 to 1.6.0-3)
  • Migration status for auto-multiple-choice/riscv64 (1.6.0-3 to 1.6.0-3): Will attempt migration (Any information below is purely informational)
• autogen/riscv64 (1:5.18.16-5 to 1:5.18.16-5)
  • Migration status for autogen/riscv64 (1:5.18.16-5 to 1:5.18.16-5): Will attempt migration (Any information below is purely informational)
• autossh/riscv64 (1.4g-1 to 1.4g-1)
  • Migration status for autossh/riscv64 (1.4g-1 to 1.4g-1): Will attempt migration (Any information below is purely informational)
• avogadro/riscv64 (1.99.0-1 to 1.99.0-1)
  • Migration status for avogadro/riscv64 (1.99.0-1 to 1.99.0-1): Will attempt migration (Any information below is purely informational)
• avogadrolibs/riscv64 (1.99.0-5 to 1.99.0-5)
  • Migration status for avogadrolibs/riscv64 (1.99.0-5 to 1.99.0-5): Will attempt migration (Any information below is purely informational)
• awesome/riscv64 (4.3-7 to 4.3-7)
  • Migration status for awesome/riscv64 (4.3-7 to 4.3-7): Will attempt migration (Any information below is purely informational)
• awf-gtk/riscv64 (2.8.0-1 to 2.8.0-1)
  • Migration status for awf-gtk/riscv64 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
• 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/mips64el (2.16.0-1 to 2.16.0-1)
  • Migration status for aws-nuke/mips64el (2.16.0-1 to 2.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: aws-nuke/mips64el 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
• ayatana-ido/riscv64 (0.10.2-1 to 0.10.2-1)
  • Migration status for ayatana-ido/riscv64 (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• ayatana-indicator-notifications/riscv64 (23.10.1-1 to 23.10.1-1)
  • Migration status for ayatana-indicator-notifications/riscv64 (23.10.1-1 to 23.10.1-1): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
    • 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): Will attempt migration (Any information below is purely informational)
    • 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): Will attempt migration (Any information below is purely informational)
    • 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): Will attempt migration (Any information below is purely informational)
    • 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): Will attempt migration (Any information below is purely informational)
    • 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): Will attempt migration (Any information below is purely informational)
    • 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): Will attempt migration (Any information below is purely informational)
    • Built-Using: balboa/ppc64el 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): Will attempt migration (Any information below is purely informational)
    • 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/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
• ballz/riscv64 (1.0.4-1.1 to 1.0.4-1.1)
  • Migration status for ballz/riscv64 (1.0.4-1.1 to 1.0.4-1.1): Will attempt migration (Any information below is purely informational)
• baloo-widgets/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for baloo-widgets/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• bamf/riscv64 (0.5.6+repack-1.1 to 0.5.6+repack-1.1)
  • Migration status for bamf/riscv64 (0.5.6+repack-1.1 to 0.5.6+repack-1.1): Will attempt migration (Any information below is purely informational)
• bandage/riscv64 (0.9.0-2 to 0.9.0-2)
  • Migration status for bandage/riscv64 (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• bankstown-lv2/amd64 (1.1.0-1 to 1.1.0-1)
  • Migration status for bankstown-lv2/amd64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• bankstown-lv2/arm64 (1.1.0-1 to 1.1.0-1)
  • Migration status for bankstown-lv2/arm64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• bankstown-lv2/armel (1.1.0-1 to 1.1.0-1)
  • Migration status for bankstown-lv2/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• bankstown-lv2/armhf (1.1.0-1 to 1.1.0-1)
  • Migration status for bankstown-lv2/armhf (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• bankstown-lv2/i386 (1.1.0-1 to 1.1.0-1)
  • Migration status for bankstown-lv2/i386 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• baobab/riscv64 (46.0-1 to 46.0-1)
  • Migration status for baobab/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• barnowl/riscv64 (1.10-2 to 1.10-2)
  • Migration status for barnowl/riscv64 (1.10-2 to 1.10-2): Will attempt migration (Any information below is purely informational)
• bart-view/riscv64 (0.3.00-1 to 0.3.00-1)
  • Migration status for bart-view/riscv64 (0.3.00-1 to 0.3.00-1): Will attempt migration (Any information below is purely informational)
• bash/amd64 (5.2.32-1 to 5.2.32-1)
  • Migration status for bash/amd64 (5.2.32-1 to 5.2.32-1): Will attempt migration (Any information below is purely informational)
• bash/arm64 (5.2.32-1 to 5.2.32-1)
  • Migration status for bash/arm64 (5.2.32-1 to 5.2.32-1): Will attempt migration (Any information below is purely informational)
• bash/armel (5.2.32-1 to 5.2.32-1)
  • Migration status for bash/armel (5.2.32-1 to 5.2.32-1): Will attempt migration (Any information below is purely informational)
• bash/armhf (5.2.32-1 to 5.2.32-1)
  • Migration status for bash/armhf (5.2.32-1 to 5.2.32-1): Will attempt migration (Any information below is purely informational)
• bash/i386 (5.2.32-1 to 5.2.32-1)
  • Migration status for bash/i386 (5.2.32-1 to 5.2.32-1): Will attempt migration (Any information below is purely informational)
• bash/mips64el (5.2.32-1 to 5.2.32-1)
  • Migration status for bash/mips64el (5.2.32-1 to 5.2.32-1): Will attempt migration (Any information below is purely informational)
• bash/ppc64el (5.2.32-1 to 5.2.32-1)
  • Migration status for bash/ppc64el (5.2.32-1 to 5.2.32-1): Will attempt migration (Any information below is purely informational)
• bash/s390x (5.2.32-1 to 5.2.32-1)
  • Migration status for bash/s390x (5.2.32-1 to 5.2.32-1): Will attempt migration (Any information below is purely informational)
• basic256/riscv64 (2.0.99.10-1 to 2.0.99.10-1)
  • Migration status for basic256/riscv64 (2.0.99.10-1 to 2.0.99.10-1): Will attempt migration (Any information below is purely informational)
• basilisk2/riscv64 (0.9.20240402+dfsg-1 to 0.9.20240402+dfsg-1)
  • Migration status for basilisk2/riscv64 (0.9.20240402+dfsg-1 to 0.9.20240402+dfsg-1): Will attempt migration (Any information below is purely informational)
• basket/riscv64 (2.49-1 to 2.49-1)
  • Migration status for basket/riscv64 (2.49-1 to 2.49-1): Will attempt migration (Any information below is purely informational)
• baycomusb/riscv64 (0.10-15 to 0.10-15)
  • Migration status for baycomusb/riscv64 (0.10-15 to 0.10-15): Will attempt migration (Any information below is purely informational)
• bdbvu/riscv64 (0.1-3.1 to 0.1-3.1)
  • Migration status for bdbvu/riscv64 (0.1-3.1 to 0.1-3.1): Will attempt migration (Any information below is purely informational)
• beads/riscv64 (1.1.22-1 to 1.1.22-1)
  • Migration status for beads/riscv64 (1.1.22-1 to 1.1.22-1): Will attempt migration (Any information below is purely informational)
• ben/amd64 (1.7 to 1.7)
  • Migration status for ben/amd64 (1.7 to 1.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ben/amd64 tyxml/amd64 (not considered)
    • Invalidated by dependency
    • Depends: ben/amd64 ocaml-re (not considered)
• ben/arm64 (1.7 to 1.7)
  • Migration status for ben/arm64 (1.7 to 1.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ben/arm64 tyxml/arm64 (not considered)
    • Invalidated by dependency
    • Depends: ben/arm64 ocaml-re (not considered)
• ben/armel (1.7 to 1.7)
  • Migration status for ben/armel (1.7 to 1.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ben/armel ocaml-re (not considered)
    • Invalidated by dependency
• ben/armhf (1.7 to 1.7)
  • Migration status for ben/armhf (1.7 to 1.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ben/armhf ocaml-re (not considered)
    • Invalidated by dependency
• ben/i386 (1.7 to 1.7)
  • Migration status for ben/i386 (1.7 to 1.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ben/i386 ocaml-re (not considered)
    • Invalidated by dependency
• ben/mips64el (1.7 to 1.7)
  • Migration status for ben/mips64el (1.7 to 1.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ben/mips64el ocaml-re (not considered)
    • Invalidated by dependency
• ben/ppc64el (1.7 to 1.7)
  • Migration status for ben/ppc64el (1.7 to 1.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ben/ppc64el tyxml/ppc64el (not considered)
    • Invalidated by dependency
    • Depends: ben/ppc64el ocaml-re (not considered)
• ben/riscv64 (1.7 to 1.7)
  • Migration status for ben/riscv64 (1.7 to 1.7): Will attempt migration (Any information below is purely informational)
• ben/s390x (1.7 to 1.7)
  • Migration status for ben/s390x (1.7 to 1.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ben/s390x tyxml/s390x (not considered)
    • Invalidated by dependency
    • Depends: ben/s390x ocaml-re (not considered)
• berusky/riscv64 (1.7.2-3 to 1.7.2-3)
  • Migration status for berusky/riscv64 (1.7.2-3 to 1.7.2-3): Will attempt migration (Any information below is purely informational)
• berusky2/riscv64 (0.12-4 to 0.12-4)
  • Migration status for berusky2/riscv64 (0.12-4 to 0.12-4): Will attempt migration (Any information below is purely informational)
• betaradio/riscv64 (1.6-1 to 1.6-1)
  • Migration status for betaradio/riscv64 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
• 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/mips64el (2.33.0-1 to 2.33.0-1)
  • Migration status for bettercap/mips64el (2.33.0-1 to 2.33.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bettercap/mips64el 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/s390x (2.33.0-1 to 2.33.0-1)
  • Migration status for bettercap/s390x (2.33.0-1 to 2.33.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: bettercap/s390x golang-1.23
• bfm/riscv64 (0.6.4-6.1 to 0.6.4-6.1)
  • Migration status for bfm/riscv64 (0.6.4-6.1 to 0.6.4-6.1): Will attempt migration (Any information below is purely informational)
• bibletime/riscv64 (3.0.3-3 to 3.0.3-3)
  • Migration status for bibletime/riscv64 (3.0.3-3 to 3.0.3-3): Will attempt migration (Any information below is purely informational)
• bijiben/riscv64 (40.1-6 to 40.1-6)
  • Migration status for bijiben/riscv64 (40.1-6 to 40.1-6): Will attempt migration (Any information below is purely informational)
• billard-gl/riscv64 (1.75-17 to 1.75-17)
  • Migration status for billard-gl/riscv64 (1.75-17 to 1.75-17): Will attempt migration (Any information below is purely informational)
• bino/riscv64 (2.1-1 to 2.1-1)
  • Migration status for bino/riscv64 (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
• bioperl-run/amd64 (1.7.3-11 to 1.7.3-11)
  • Migration status for bioperl-run/amd64 (1.7.3-11 to 1.7.3-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bioperl-run/arm64 (1.7.3-11 to 1.7.3-11)
  • Migration status for bioperl-run/arm64 (1.7.3-11 to 1.7.3-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bioperl-run/armel (1.7.3-11 to 1.7.3-11)
  • Migration status for bioperl-run/armel (1.7.3-11 to 1.7.3-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bioperl-run/armhf (1.7.3-11 to 1.7.3-11)
  • Migration status for bioperl-run/armhf (1.7.3-11 to 1.7.3-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bioperl-run/i386 (1.7.3-11 to 1.7.3-11)
  • Migration status for bioperl-run/i386 (1.7.3-11 to 1.7.3-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bioperl-run/mips64el (1.7.3-11 to 1.7.3-11)
  • Migration status for bioperl-run/mips64el (1.7.3-11 to 1.7.3-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bioperl-run/ppc64el (1.7.3-11 to 1.7.3-11)
  • Migration status for bioperl-run/ppc64el (1.7.3-11 to 1.7.3-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bioperl-run/riscv64 (1.7.3-11 to 1.7.3-11)
  • Migration status for bioperl-run/riscv64 (1.7.3-11 to 1.7.3-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bioperl-run/s390x (1.7.3-11 to 1.7.3-11)
  • Migration status for bioperl-run/s390x (1.7.3-11 to 1.7.3-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• birdfont/riscv64 (2.33.1-3 to 2.33.1-3)
  • Migration status for birdfont/riscv64 (2.33.1-3 to 2.33.1-3): Will attempt migration (Any information below is purely informational)
• birdtray/riscv64 (1.9.0+ds-2 to 1.9.0+ds-2)
  • Migration status for birdtray/riscv64 (1.9.0+ds-2 to 1.9.0+ds-2): Will attempt migration (Any information below is purely informational)
• blinken/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for blinken/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• blobandconquer/riscv64 (1.11-dfsg+20-2 to 1.11-dfsg+20-2)
  • Migration status for blobandconquer/riscv64 (1.11-dfsg+20-2 to 1.11-dfsg+20-2): Will attempt migration (Any information below is purely informational)
• blobby/riscv64 (1.1+ds-1 to 1.1+ds-1)
  • Migration status for blobby/riscv64 (1.1+ds-1 to 1.1+ds-1): Will attempt migration (Any information below is purely informational)
• bloboats/riscv64 (1.0.2+dfsg-4 to 1.0.2+dfsg-4)
  • Migration status for bloboats/riscv64 (1.0.2+dfsg-4 to 1.0.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• blockout2/riscv64 (2.5+dfsg1-1 to 2.5+dfsg1-1)
  • Migration status for blockout2/riscv64 (2.5+dfsg1-1 to 2.5+dfsg1-1): Will attempt migration (Any information below is purely informational)
• blocks-of-the-undead/riscv64 (1.0-7 to 1.0-7)
  • Migration status for blocks-of-the-undead/riscv64 (1.0-7 to 1.0-7): Will attempt migration (Any information below is purely informational)
• bluefish/riscv64 (2.2.15-1 to 2.2.15-1)
  • Migration status for bluefish/riscv64 (2.2.15-1 to 2.2.15-1): Will attempt migration (Any information below is purely informational)
• bluez-qt/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for bluez-qt/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• blur-effect/riscv64 (1.1.3-2 to 1.1.3-2)
  • Migration status for blur-effect/riscv64 (1.1.3-2 to 1.1.3-2): Will attempt migration (Any information below is purely informational)
• boats/riscv64 (202008-1 to 202008-1)
  • Migration status for boats/riscv64 (202008-1 to 202008-1): Will attempt migration (Any information below is purely informational)
• 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/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
• bomber/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for bomber/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• bookworm/riscv64 (1.1.2+git20210715-4 to 1.1.2+git20210715-4)
  • Migration status for bookworm/riscv64 (1.1.2+git20210715-4 to 1.1.2+git20210715-4): Will attempt migration (Any information below is purely informational)
• boomaga/riscv64 (3.0.0+git13-g7f7ad47-1 to 3.0.0+git13-g7f7ad47-1)
  • Migration status for boomaga/riscv64 (3.0.0+git13-g7f7ad47-1 to 3.0.0+git13-g7f7ad47-1): Will attempt migration (Any information below is purely informational)
• bossa/riscv64 (1.9.1-3 to 1.9.1-3)
  • Migration status for bossa/riscv64 (1.9.1-3 to 1.9.1-3): Will attempt migration (Any information below is purely informational)
• boswars/riscv64 (2.8-2 to 2.8-2)
  • Migration status for boswars/riscv64 (2.8-2 to 2.8-2): Will attempt migration (Any information below is purely informational)
• bovo/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for bovo/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• bppphyview/riscv64 (0.6.1-5 to 0.6.1-5)
  • Migration status for bppphyview/riscv64 (0.6.1-5 to 0.6.1-5): Will attempt migration (Any information below is purely informational)
• brainparty/riscv64 (0.61+dfsg-7 to 0.61+dfsg-7)
  • Migration status for brainparty/riscv64 (0.61+dfsg-7 to 0.61+dfsg-7): Will attempt migration (Any information below is purely informational)
• brasero/riscv64 (3.12.3-2 to 3.12.3-2)
  • Migration status for brasero/riscv64 (3.12.3-2 to 3.12.3-2): Will attempt migration (Any information below is purely informational)
• brewtarget/riscv64 (3.0.11-1 to 3.0.11-1)
  • Migration status for brewtarget/riscv64 (3.0.11-1 to 3.0.11-1): Will attempt migration (Any information below is purely informational)
• brig/riscv64 (0.95+dfsg-3 to 0.95+dfsg-3)
  • Migration status for brig/riscv64 (0.95+dfsg-3 to 0.95+dfsg-3): Will attempt migration (Any information below is purely informational)
• briquolo/riscv64 (0.5.7-11 to 0.5.7-11)
  • Migration status for briquolo/riscv64 (0.5.7-11 to 0.5.7-11): Will attempt migration (Any information below is purely informational)
• brisk-menu/riscv64 (0.6.2-2 to 0.6.2-2)
  • Migration status for brisk-menu/riscv64 (0.6.2-2 to 0.6.2-2): 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/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
• brp-pacu/riscv64 (2.1.2+git20210421-1 to 2.1.2+git20210421-1)
  • Migration status for brp-pacu/riscv64 (2.1.2+git20210421-1 to 2.1.2+git20210421-1): Will attempt migration (Any information below is purely informational)
• brutalchess/riscv64 (0.5.2+dfsg-8 to 0.5.2+dfsg-8)
  • Migration status for brutalchess/riscv64 (0.5.2+dfsg-8 to 0.5.2+dfsg-8): Will attempt migration (Any information below is purely informational)
• bspwm/riscv64 (0.9.10-2 to 0.9.10-2)
  • Migration status for bspwm/riscv64 (0.9.10-2 to 0.9.10-2): Will attempt migration (Any information below is purely informational)
• btanks/riscv64 (0.9.8083-9 to 0.9.8083-9)
  • Migration status for btanks/riscv64 (0.9.8083-9 to 0.9.8083-9): Will attempt migration (Any information below is purely informational)
• bti/riscv64 (034-6 to 034-6)
  • Migration status for bti/riscv64 (034-6 to 034-6): Will attempt migration (Any information below is purely informational)
• btscanner/riscv64 (2.1-9 to 2.1-9)
  • Migration status for btscanner/riscv64 (2.1-9 to 2.1-9): Will attempt migration (Any information below is purely informational)
• budgie-desktop-view/riscv64 (1.3-2 to 1.3-2)
  • Migration status for budgie-desktop-view/riscv64 (1.3-2 to 1.3-2): Will attempt migration (Any information below is purely informational)
• bumblebee/riscv64 (3.2.1-30 to 3.2.1-30)
  • Migration status for bumblebee/riscv64 (3.2.1-30 to 3.2.1-30): Will attempt migration (Any information below is purely informational)
• burrow/amd64 (1.2.1-2 to 1.2.1-2)
  • Migration status for burrow/amd64 (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/amd64 golang-1.23
• burrow/arm64 (1.2.1-2 to 1.2.1-2)
  • Migration status for burrow/arm64 (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/arm64 golang-1.23
• burrow/armel (1.2.1-2 to 1.2.1-2)
  • Migration status for burrow/armel (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/armel golang-1.23
• burrow/armhf (1.2.1-2 to 1.2.1-2)
  • Migration status for burrow/armhf (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/armhf golang-1.23
• burrow/i386 (1.2.1-2 to 1.2.1-2)
  • Migration status for burrow/i386 (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/i386 golang-1.23
• burrow/mips64el (1.2.1-2 to 1.2.1-2)
  • Migration status for burrow/mips64el (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/mips64el golang-1.23
• burrow/ppc64el (1.2.1-2 to 1.2.1-2)
  • Migration status for burrow/ppc64el (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/ppc64el golang-1.23
• burrow/s390x (1.2.1-2 to 1.2.1-2)
  • Migration status for burrow/s390x (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: burrow/s390x golang-1.23
• bustle/riscv64 (0.8.0-2 to 0.8.0-2)
  • Migration status for bustle/riscv64 (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• busybox/amd64 (1:1.36.1-9 to 1:1.36.1-9)
  • Migration status for busybox/amd64 (1:1.36.1-9 to 1:1.36.1-9): Will attempt migration (Any information below is purely informational)
• busybox/arm64 (1:1.36.1-9 to 1:1.36.1-9)
  • Migration status for busybox/arm64 (1:1.36.1-9 to 1:1.36.1-9): Will attempt migration (Any information below is purely informational)
• busybox/armhf (1:1.36.1-9 to 1:1.36.1-9)
  • Migration status for busybox/armhf (1:1.36.1-9 to 1:1.36.1-9): Will attempt migration (Any information below is purely informational)
• busybox/i386 (1:1.36.1-9 to 1:1.36.1-9)
  • Migration status for busybox/i386 (1:1.36.1-9 to 1:1.36.1-9): Will attempt migration (Any information below is purely informational)
• busybox/mips64el (1:1.36.1-9 to 1:1.36.1-9)
  • Migration status for busybox/mips64el (1:1.36.1-9 to 1:1.36.1-9): Will attempt migration (Any information below is purely informational)
• busybox/ppc64el (1:1.36.1-9 to 1:1.36.1-9)
  • Migration status for busybox/ppc64el (1:1.36.1-9 to 1:1.36.1-9): Will attempt migration (Any information below is purely informational)
• busybox/s390x (1:1.36.1-9 to 1:1.36.1-9)
  • Migration status for busybox/s390x (1:1.36.1-9 to 1:1.36.1-9): Will attempt migration (Any information below is purely informational)
• buzztrax/riscv64 (0.10.2-9 to 0.10.2-9)
  • Migration status for buzztrax/riscv64 (0.10.2-9 to 0.10.2-9): Will attempt migration (Any information below is purely informational)
• byzanz/riscv64 (0.3.0+git20160312-5 to 0.3.0+git20160312-5)
  • Migration status for byzanz/riscv64 (0.3.0+git20160312-5 to 0.3.0+git20160312-5): Will attempt migration (Any information below is purely informational)
• bzflag/riscv64 (2.4.26-1 to 2.4.26-1)
  • Migration status for bzflag/riscv64 (2.4.26-1 to 2.4.26-1): Will attempt migration (Any information below is purely informational)
• bzrtp/riscv64 (5.2.0-2 to 5.2.0-2)
  • Migration status for bzrtp/riscv64 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• c-icap-modules/riscv64 (1:0.5.5-2 to 1:0.5.5-2)
  • Migration status for c-icap-modules/riscv64 (1:0.5.5-2 to 1:0.5.5-2): Will attempt migration (Any information below is purely informational)
• c-munipack/riscv64 (2.1.37-1 to 2.1.37-1)
  • Migration status for c-munipack/riscv64 (2.1.37-1 to 2.1.37-1): Will attempt migration (Any information below is purely informational)
• c2go/amd64 (0.26.10-1 to 0.26.10-1)
  • Migration status for c2go/amd64 (0.26.10-1 to 0.26.10-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/amd64 golang-1.23
• c2go/arm64 (0.26.10-1 to 0.26.10-1)
  • Migration status for c2go/arm64 (0.26.10-1 to 0.26.10-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/arm64 golang-1.23
• c2go/armel (0.26.10-1 to 0.26.10-1)
  • Migration status for c2go/armel (0.26.10-1 to 0.26.10-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/armel golang-1.23
• c2go/armhf (0.26.10-1 to 0.26.10-1)
  • Migration status for c2go/armhf (0.26.10-1 to 0.26.10-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/armhf golang-1.23
• c2go/i386 (0.26.10-1 to 0.26.10-1)
  • Migration status for c2go/i386 (0.26.10-1 to 0.26.10-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/i386 golang-1.23
• c2go/mips64el (0.26.10-1 to 0.26.10-1)
  • Migration status for c2go/mips64el (0.26.10-1 to 0.26.10-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/mips64el golang-1.23
• c2go/ppc64el (0.26.10-1 to 0.26.10-1)
  • Migration status for c2go/ppc64el (0.26.10-1 to 0.26.10-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: c2go/ppc64el golang-1.23
• c2go/riscv64 (0.26.10-1 to 0.26.10-1)
  • Migration status for c2go/riscv64 (0.26.10-1 to 0.26.10-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch riscv64 binaries not found
• c2go/s390x (0.26.10-1 to 0.26.10-1)
  • Migration status for c2go/s390x (0.26.10-1 to 0.26.10-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/mips64el (2.6.2-8 to 2.6.2-8)
  • Migration status for caddy/mips64el (2.6.2-8 to 2.6.2-8): Will attempt migration (Any information below is purely informational)
    • Built-Using: caddy/mips64el 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/s390x (2.6.2-8 to 2.6.2-8)
  • Migration status for caddy/s390x (2.6.2-8 to 2.6.2-8): Will attempt migration (Any information below is purely informational)
    • Built-Using: caddy/s390x golang-1.23
• cage/riscv64 (0.1.5+20240127-2 to 0.1.5+20240127-2)
  • Migration status for cage/riscv64 (0.1.5+20240127-2 to 0.1.5+20240127-2): Will attempt migration (Any information below is purely informational)
• cairo-5c/riscv64 (1.21 to 1.21)
  • Migration status for cairo-5c/riscv64 (1.21 to 1.21): Will attempt migration (Any information below is purely informational)
• cairo-dock-plug-ins/riscv64 (3.4.1+git20201022.a0d3415c-1.2 to 3.4.1+git20201022.a0d3415c-1.2)
  • Migration status for cairo-dock-plug-ins/riscv64 (3.4.1+git20201022.a0d3415c-1.2 to 3.4.1+git20201022.a0d3415c-1.2): Will attempt migration (Any information below is purely informational)
• cairo-dock/riscv64 (3.4.1+git20201103.0836f5d1-1 to 3.4.1+git20201103.0836f5d1-1)
  • Migration status for cairo-dock/riscv64 (3.4.1+git20201103.0836f5d1-1 to 3.4.1+git20201103.0836f5d1-1): Will attempt migration (Any information below is purely informational)
• caja-actions/riscv64 (1.27.0-1 to 1.27.0-1)
  • Migration status for caja-actions/riscv64 (1.27.0-1 to 1.27.0-1): Will attempt migration (Any information below is purely informational)
• caja-eiciel/riscv64 (1.20.1-3 to 1.20.1-3)
  • Migration status for caja-eiciel/riscv64 (1.20.1-3 to 1.20.1-3): Will attempt migration (Any information below is purely informational)
• caja-extensions/riscv64 (1.26.1-2 to 1.26.1-2)
  • Migration status for caja-extensions/riscv64 (1.26.1-2 to 1.26.1-2): Will attempt migration (Any information below is purely informational)
• caja/riscv64 (1.26.3-1 to 1.26.3-1)
  • Migration status for caja/riscv64 (1.26.3-1 to 1.26.3-1): Will attempt migration (Any information below is purely informational)
• calamares-extensions/riscv64 (3.3.1-1 to 3.3.1-1)
  • Migration status for calamares-extensions/riscv64 (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• calamares-settings-debian_pu (13.0.11-1 to 12.0.9-1+deb12u2)
  • Migration status for calamares-settings-debian_pu (13.0.11-1 to 12.0.9-1+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: calamares-settings-debian is newer in the target suite (13.0.11-1 12.0.9-1+deb12u2)
• calendar/amd64 (3.0.0-4 to 3.0.0-4)
  • Migration status for calendar/amd64 (3.0.0-4 to 3.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcalendar-ocaml/3.0.0-4+b3/amd64 to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/amd64 uninstallable
    • migrating libcalendar-ocaml/3.0.0-4+b3/amd64 to testing makes nurpawiki/1.2.4-4+b14/amd64 uninstallable
    • migrating libcalendar-ocaml-dev/3.0.0-4+b3/amd64 to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/amd64 uninstallable
    • Depends: calendar/amd64 ocaml-re (not considered)
    • Implicit dependency: calendar/amd64 pgocaml/amd64 (not considered)
• calendar/arm64 (3.0.0-4 to 3.0.0-4)
  • Migration status for calendar/arm64 (3.0.0-4 to 3.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcalendar-ocaml/3.0.0-4+b3/arm64 to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/arm64 uninstallable
    • migrating libcalendar-ocaml/3.0.0-4+b3/arm64 to testing makes nurpawiki/1.2.4-4+b14/arm64 uninstallable
    • migrating libcalendar-ocaml-dev/3.0.0-4+b3/arm64 to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/arm64 uninstallable
    • Depends: calendar/arm64 ocaml-re (not considered)
    • Implicit dependency: calendar/arm64 pgocaml/arm64 (not considered)
• calendar/armel (3.0.0-4 to 3.0.0-4)
  • Migration status for calendar/armel (3.0.0-4 to 3.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcalendar-ocaml/3.0.0-4+b3/armel to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b16/armel uninstallable
    • migrating libcalendar-ocaml/3.0.0-4+b3/armel to testing makes nurpawiki/1.2.4-4+b12/armel uninstallable
    • migrating libcalendar-ocaml-dev/3.0.0-4+b3/armel to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b16/armel uninstallable
    • Depends: calendar/armel ocaml-re (not considered)
    • Implicit dependency: calendar/armel pgocaml/armel (not considered)
• calendar/armhf (3.0.0-4 to 3.0.0-4)
  • Migration status for calendar/armhf (3.0.0-4 to 3.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcalendar-ocaml/3.0.0-4+b3/armhf to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/armhf uninstallable
    • migrating libcalendar-ocaml/3.0.0-4+b3/armhf to testing makes nurpawiki/1.2.4-4+b14/armhf uninstallable
    • migrating libcalendar-ocaml-dev/3.0.0-4+b3/armhf to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/armhf uninstallable
    • Depends: calendar/armhf ocaml-re (not considered)
    • Implicit dependency: calendar/armhf pgocaml/armhf (not considered)
• calendar/i386 (3.0.0-4 to 3.0.0-4)
  • Migration status for calendar/i386 (3.0.0-4 to 3.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcalendar-ocaml/3.0.0-4+b3/i386 to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/i386 uninstallable
    • migrating libcalendar-ocaml/3.0.0-4+b3/i386 to testing makes nurpawiki/1.2.4-4+b14/i386 uninstallable
    • migrating libcalendar-ocaml-dev/3.0.0-4+b3/i386 to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/i386 uninstallable
    • Depends: calendar/i386 ocaml-re (not considered)
    • Implicit dependency: calendar/i386 pgocaml/i386 (not considered)
• calendar/mips64el (3.0.0-4 to 3.0.0-4)
  • Migration status for calendar/mips64el (3.0.0-4 to 3.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcalendar-ocaml/3.0.0-4+b3/mips64el to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b16/mips64el uninstallable
    • migrating libcalendar-ocaml/3.0.0-4+b3/mips64el to testing makes nurpawiki/1.2.4-4+b12/mips64el uninstallable
    • migrating libcalendar-ocaml-dev/3.0.0-4+b3/mips64el to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b16/mips64el uninstallable
    • Depends: calendar/mips64el ocaml-re (not considered)
    • Implicit dependency: calendar/mips64el pgocaml/mips64el (not considered)
• calendar/ppc64el (3.0.0-4 to 3.0.0-4)
  • Migration status for calendar/ppc64el (3.0.0-4 to 3.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcalendar-ocaml/3.0.0-4+b3/ppc64el to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/ppc64el uninstallable
    • migrating libcalendar-ocaml/3.0.0-4+b3/ppc64el to testing makes nurpawiki/1.2.4-4+b14/ppc64el uninstallable
    • migrating libcalendar-ocaml-dev/3.0.0-4+b3/ppc64el to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/ppc64el uninstallable
    • Depends: calendar/ppc64el ocaml-re (not considered)
    • Implicit dependency: calendar/ppc64el pgocaml/ppc64el (not considered)
• calendar/riscv64 (3.0.0-4 to 3.0.0-4)
  • Migration status for calendar/riscv64 (3.0.0-4 to 3.0.0-4): Will attempt migration (Any information below is purely informational)
• calendar/s390x (3.0.0-4 to 3.0.0-4)
  • Migration status for calendar/s390x (3.0.0-4 to 3.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcalendar-ocaml/3.0.0-4+b3/s390x to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/s390x uninstallable
    • migrating libcalendar-ocaml/3.0.0-4+b3/s390x to testing makes nurpawiki/1.2.4-4+b14/s390x uninstallable
    • migrating libcalendar-ocaml-dev/3.0.0-4+b3/s390x to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/s390x uninstallable
    • Depends: calendar/s390x ocaml-re (not considered)
    • Implicit dependency: calendar/s390x pgocaml/s390x (not considered)
• calf/riscv64 (0.90.3-4 to 0.90.3-4)
  • Migration status for calf/riscv64 (0.90.3-4 to 0.90.3-4): Will attempt migration (Any information below is purely informational)
• calindori/riscv64 (24.02.1-1 to 24.02.1-1)
  • Migration status for calindori/riscv64 (24.02.1-1 to 24.02.1-1): Will attempt migration (Any information below is purely informational)
• calligraplan/riscv64 (1:3.3.0-2 to 1:3.3.0-2)
  • Migration status for calligraplan/riscv64 (1:3.3.0-2 to 1:3.3.0-2): Will attempt migration (Any information below is purely informational)
• camlp5/amd64 (8.03.00-1 to 8.03.00-1)
  • Migration status for camlp5/amd64 (8.03.00-1 to 8.03.00-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: camlp5/amd64 ocaml-re (not considered)
    • Invalidated by dependency
• camlp5/arm64 (8.03.00-1 to 8.03.00-1)
  • Migration status for camlp5/arm64 (8.03.00-1 to 8.03.00-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: camlp5/arm64 ocaml-re (not considered)
    • Invalidated by dependency
• camlp5/armel (8.03.00-1 to 8.03.00-1)
  • Migration status for camlp5/armel (8.03.00-1 to 8.03.00-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: camlp5/armel ocaml-re (not considered)
    • Invalidated by dependency
• camlp5/armhf (8.03.00-1 to 8.03.00-1)
  • Migration status for camlp5/armhf (8.03.00-1 to 8.03.00-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: camlp5/armhf ocaml-re (not considered)
    • Invalidated by dependency
• camlp5/i386 (8.03.00-1 to 8.03.00-1)
  • Migration status for camlp5/i386 (8.03.00-1 to 8.03.00-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: camlp5/i386 ocaml-re (not considered)
    • Invalidated by dependency
• camlp5/mips64el (8.03.00-1 to 8.03.00-1)
  • Migration status for camlp5/mips64el (8.03.00-1 to 8.03.00-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: camlp5/mips64el ocaml-re (not considered)
    • Invalidated by dependency
• camlp5/ppc64el (8.03.00-1 to 8.03.00-1)
  • Migration status for camlp5/ppc64el (8.03.00-1 to 8.03.00-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: camlp5/ppc64el ocaml-re (not considered)
    • Invalidated by dependency
• camlp5/riscv64 (8.03.00-1 to 8.03.00-1)
  • Migration status for camlp5/riscv64 (8.03.00-1 to 8.03.00-1): Will attempt migration (Any information below is purely informational)
• camlp5/s390x (8.03.00-1 to 8.03.00-1)
  • Migration status for camlp5/s390x (8.03.00-1 to 8.03.00-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: camlp5/s390x ocaml-re (not considered)
    • Invalidated by dependency
• caneda/riscv64 (0.3.1+gitg08e22168-1 to 0.3.1+gitg08e22168-1)
  • Migration status for caneda/riscv64 (0.3.1+gitg08e22168-1 to 0.3.1+gitg08e22168-1): Will attempt migration (Any information below is purely informational)
• 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/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
• cardpeek/riscv64 (0.8.4-1.3 to 0.8.4-1.3)
  • Migration status for cardpeek/riscv64 (0.8.4-1.3 to 0.8.4-1.3): Will attempt migration (Any information below is purely informational)
• caribou/riscv64 (0.4.21-9 to 0.4.21-9)
  • Migration status for caribou/riscv64 (0.4.21-9 to 0.4.21-9): Will attempt migration (Any information below is purely informational)
• cassbeam/riscv64 (1.1-4 to 1.1-4)
  • Migration status for cassbeam/riscv64 (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• cb2bib/riscv64 (2.0.1-2 to 2.0.1-2)
  • Migration status for cb2bib/riscv64 (2.0.1-2 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
• cba/riscv64 (0.3.6-6 to 0.3.6-6)
  • Migration status for cba/riscv64 (0.3.6-6 to 0.3.6-6): Will attempt migration (Any information below is purely informational)
• cbatticon/riscv64 (1.6.9-1 to 1.6.9-1)
  • Migration status for cbatticon/riscv64 (1.6.9-1 to 1.6.9-1): Will attempt migration (Any information below is purely informational)
• cbmplugs/riscv64 (1.2.2-1.2 to 1.2.2-1.2)
  • Migration status for cbmplugs/riscv64 (1.2.2-1.2 to 1.2.2-1.2): Will attempt migration (Any information below is purely informational)
• ccls/riscv64 (0.20240202-1 to 0.20240202-1)
  • Migration status for ccls/riscv64 (0.20240202-1 to 0.20240202-1): Will attempt migration (Any information below is purely informational)
• cctools/riscv64 (9.9-4.1 to 9.9-4.1)
  • Migration status for cctools/riscv64 (9.9-4.1 to 9.9-4.1): Will attempt migration (Any information below is purely informational)
• cdebconf-terminal/riscv64 (0.44 to 0.44)
  • Migration status for cdebconf-terminal/riscv64 (0.44 to 0.44): Will attempt migration (Any information below is purely informational)
• cdebootstrap/amd64 (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/amd64 (0.7.8 to 0.7.8): Will attempt migration (Any information below is purely informational)
• cdebootstrap/arm64 (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/arm64 (0.7.8 to 0.7.8): Will attempt migration (Any information below is purely informational)
• cdebootstrap/armel (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/armel (0.7.8 to 0.7.8): Will attempt migration (Any information below is purely informational)
• cdebootstrap/armhf (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/armhf (0.7.8 to 0.7.8): Will attempt migration (Any information below is purely informational)
• cdebootstrap/i386 (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/i386 (0.7.8 to 0.7.8): Will attempt migration (Any information below is purely informational)
• 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/ppc64el (0.7.8 to 0.7.8)
  • Migration status for cdebootstrap/ppc64el (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)
• cdftools/riscv64 (4.0.0-3 to 4.0.0-3)
  • Migration status for cdftools/riscv64 (4.0.0-3 to 4.0.0-3): 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/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
• cervisia/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for cervisia/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• cgal/riscv64 (5.6.1-1 to 5.6.1-1)
  • Migration status for cgal/riscv64 (5.6.1-1 to 5.6.1-1): Will attempt migration (Any information below is purely informational)
• cgreen/riscv64 (1.6.3-1 to 1.6.3-1)
  • Migration status for cgreen/riscv64 (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
• charmap.app/riscv64 (0.3~rc1-4 to 0.3~rc1-4)
  • Migration status for charmap.app/riscv64 (0.3~rc1-4 to 0.3~rc1-4): Will attempt migration (Any information below is purely informational)
• charmtimetracker/riscv64 (1.12.0-3 to 1.12.0-3)
  • Migration status for charmtimetracker/riscv64 (1.12.0-3 to 1.12.0-3): Will attempt migration (Any information below is purely informational)
• 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/mips64el (1.14.0-2 to 1.14.0-2)
  • Migration status for chasquid/mips64el (1.14.0-2 to 1.14.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: chasquid/mips64el 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/s390x (1.14.0-2 to 1.14.0-2)
  • Migration status for chasquid/s390x (1.14.0-2 to 1.14.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: chasquid/s390x golang-1.23
• chemtool/riscv64 (1.6.14-6 to 1.6.14-6)
  • Migration status for chemtool/riscv64 (1.6.14-6 to 1.6.14-6): Will attempt migration (Any information below is purely informational)
• cherrytree/riscv64 (1.1.2+dfsg-1 to 1.1.2+dfsg-1)
  • Migration status for cherrytree/riscv64 (1.1.2+dfsg-1 to 1.1.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• chiaki/riscv64 (2.2.0-1 to 2.2.0-1)
  • Migration status for chiaki/riscv64 (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
• chkrootkit/amd64 (0.58b-1 to 0.58b-1)
  • Migration status for chkrootkit/amd64 (0.58b-1 to 0.58b-1): Will attempt migration (Any information below is purely informational)
• chkrootkit/arm64 (0.58b-1 to 0.58b-1)
  • Migration status for chkrootkit/arm64 (0.58b-1 to 0.58b-1): Will attempt migration (Any information below is purely informational)
• chkrootkit/armel (0.58b-1 to 0.58b-1)
  • Migration status for chkrootkit/armel (0.58b-1 to 0.58b-1): Will attempt migration (Any information below is purely informational)
• chkrootkit/armhf (0.58b-1 to 0.58b-1)
  • Migration status for chkrootkit/armhf (0.58b-1 to 0.58b-1): Will attempt migration (Any information below is purely informational)
• chkrootkit/i386 (0.58b-1 to 0.58b-1)
  • Migration status for chkrootkit/i386 (0.58b-1 to 0.58b-1): Will attempt migration (Any information below is purely informational)
• chkrootkit/mips64el (0.58b-1 to 0.58b-1)
  • Migration status for chkrootkit/mips64el (0.58b-1 to 0.58b-1): Will attempt migration (Any information below is purely informational)
• chkrootkit/ppc64el (0.58b-1 to 0.58b-1)
  • Migration status for chkrootkit/ppc64el (0.58b-1 to 0.58b-1): Will attempt migration (Any information below is purely informational)
• chkrootkit/s390x (0.58b-1 to 0.58b-1)
  • Migration status for chkrootkit/s390x (0.58b-1 to 0.58b-1): Will attempt migration (Any information below is purely informational)
• choosewm/riscv64 (0.1.6-3.1 to 0.1.6-3.1)
  • Migration status for choosewm/riscv64 (0.1.6-3.1 to 0.1.6-3.1): Will attempt migration (Any information below is purely informational)
• choqok/riscv64 (1.7.0-3 to 1.7.0-3)
  • Migration status for choqok/riscv64 (1.7.0-3 to 1.7.0-3): Will attempt migration (Any information below is purely informational)
• chromium-bsu/riscv64 (0.9.16.1-3 to 0.9.16.1-3)
  • Migration status for chromium-bsu/riscv64 (0.9.16.1-3 to 0.9.16.1-3): Will attempt migration (Any information below is purely informational)
• chromium_pu (128.0.6613.113-1~deb13u1 to 128.0.6613.119-1~deb12u1)
  • Migration status for chromium_pu (128.0.6613.113-1~deb13u1 to 128.0.6613.119-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • chromium/amd64 has unsatisfiable dependency
    • chromium-shell/amd64 has unsatisfiable dependency
    • chromium/arm64 has unsatisfiable dependency
    • chromium-shell/arm64 has unsatisfiable dependency
    • chromium/armhf has unsatisfiable dependency
    • chromium-common/armhf has unsatisfiable dependency
    • chromium-driver/armhf has unsatisfiable dependency
    • chromium-shell/armhf has unsatisfiable dependency
    • chromium/i386 has unsatisfiable dependency
    • chromium-shell/i386 has unsatisfiable dependency
    • chromium/ppc64el has unsatisfiable dependency
    • chromium-shell/ppc64el has unsatisfiable dependency
    • chromium unsatisfiable Build-Depends(-Arch) on amd64: rustc-web (>= 1.74)
    • chromium unsatisfiable Build-Depends(-Arch) on arm64: rustc-web (>= 1.74)
    • chromium unsatisfiable Build-Depends(-Arch) on armhf: rustc-web (>= 1.74)
    • chromium unsatisfiable Build-Depends(-Arch) on i386: rustc-web (>= 1.74)
    • chromium unsatisfiable Build-Depends(-Arch) on ppc64el: rustc-web (>= 1.74)
    • NEEDS APPROVAL BY RM
• chromono/riscv64 (1.1.1-1.1 to 1.1.1-1.1)
  • Migration status for chromono/riscv64 (1.1.1-1.1 to 1.1.1-1.1): Will attempt migration (Any information below is purely informational)
• 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/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
• ciftilib/riscv64 (1.6.0-2.1 to 1.6.0-2.1)
  • Migration status for ciftilib/riscv64 (1.6.0-2.1 to 1.6.0-2.1): Will attempt migration (Any information below is purely informational)
• cinnamon-desktop/riscv64 (6.0.0-2 to 6.0.0-2)
  • Migration status for cinnamon-desktop/riscv64 (6.0.0-2 to 6.0.0-2): Will attempt migration (Any information below is purely informational)
• cinnamon-session/riscv64 (6.0.4-2 to 6.0.4-2)
  • Migration status for cinnamon-session/riscv64 (6.0.4-2 to 6.0.4-2): Will attempt migration (Any information below is purely informational)
• cinnamon/riscv64 (6.0.4-4 to 6.0.4-4)
  • Migration status for cinnamon/riscv64 (6.0.4-4 to 6.0.4-4): Will attempt migration (Any information below is purely informational)
• citadel-client/riscv64 (916-5 to 916-5)
  • Migration status for citadel-client/riscv64 (916-5 to 916-5): Will attempt migration (Any information below is purely informational)
• ckb-next/riscv64 (0.6.0+dfsg-0.2 to 0.6.0+dfsg-0.2)
  • Migration status for ckb-next/riscv64 (0.6.0+dfsg-0.2 to 0.6.0+dfsg-0.2): Will attempt migration (Any information below is purely informational)
• clanlib/riscv64 (1.0~svn3827-11.2 to 1.0~svn3827-11.2)
  • Migration status for clanlib/riscv64 (1.0~svn3827-11.2 to 1.0~svn3827-11.2): Will attempt migration (Any information below is purely informational)
• clementine/riscv64 (1.4.0~rc1+git867-g9ef681b0e+dfsg-1 to 1.4.0~rc1+git867-g9ef681b0e+dfsg-1)
  • Migration status for clementine/riscv64 (1.4.0~rc1+git867-g9ef681b0e+dfsg-1 to 1.4.0~rc1+git867-g9ef681b0e+dfsg-1): Will attempt migration (Any information below is purely informational)
• clevis/riscv64 (20-1 to 20-1)
  • Migration status for clevis/riscv64 (20-1 to 20-1): Will attempt migration (Any information below is purely informational)
• 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/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/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
• cloud-initramfs-tools_pu (0.18.debian14 to 0.18.debian13+deb12u1)
  • Migration status for cloud-initramfs-tools_pu (0.18.debian14 to 0.18.debian13+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: cloud-initramfs-tools is newer in the target suite (0.18.debian14 0.18.debian13+deb12u1)
• 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): Will attempt migration (Any information below is purely informational)
    • 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/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): Will attempt migration (Any information below is purely informational)
    • Built-Using: cloudsql-proxy/s390x golang-1.23
• clustalx/riscv64 (2.1+lgpl-9 to 2.1+lgpl-9)
  • Migration status for clustalx/riscv64 (2.1+lgpl-9 to 2.1+lgpl-9): Will attempt migration (Any information below is purely informational)
• clutter-1.0/riscv64 (1.26.4+git2779b932+dfsg-7 to 1.26.4+git2779b932+dfsg-7)
  • Migration status for clutter-1.0/riscv64 (1.26.4+git2779b932+dfsg-7 to 1.26.4+git2779b932+dfsg-7): Will attempt migration (Any information below is purely informational)
• clutter-gst-3.0/riscv64 (3.0.27-4 to 3.0.27-4)
  • Migration status for clutter-gst-3.0/riscv64 (3.0.27-4 to 3.0.27-4): Will attempt migration (Any information below is purely informational)
• clutter-gtk/riscv64 (1.8.4-4 to 1.8.4-4)
  • Migration status for clutter-gtk/riscv64 (1.8.4-4 to 1.8.4-4): Will attempt migration (Any information below is purely informational)
• clutter-imcontext/riscv64 (0.1.4-3.1 to 0.1.4-3.1)
  • Migration status for clutter-imcontext/riscv64 (0.1.4-3.1 to 0.1.4-3.1): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
    • 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/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): Will attempt migration (Any information below is purely informational)
    • Built-Using: cobra-cli/s390x golang-1.23
• codeblocks/riscv64 (20.03+svn13046-0.3 to 20.03+svn13046-0.3)
  • Migration status for codeblocks/riscv64 (20.03+svn13046-0.3 to 20.03+svn13046-0.3): Will attempt migration (Any information below is purely informational)
• codequery/riscv64 (0.27.0+dfsg-1 to 0.27.0+dfsg-1)
  • Migration status for codequery/riscv64 (0.27.0+dfsg-1 to 0.27.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• 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/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
• cogl/riscv64 (1.22.8-4 to 1.22.8-4)
  • Migration status for cogl/riscv64 (1.22.8-4 to 1.22.8-4): Will attempt migration (Any information below is purely informational)
• coinor-bonmin/riscv64 (1.8.9-1.1 to 1.8.9-1.1)
  • Migration status for coinor-bonmin/riscv64 (1.8.9-1.1 to 1.8.9-1.1): Will attempt migration (Any information below is purely informational)
• coinor-ipopt/riscv64 (3.11.9-2.3 to 3.11.9-2.3)
  • Migration status for coinor-ipopt/riscv64 (3.11.9-2.3 to 3.11.9-2.3): Will attempt migration (Any information below is purely informational)
• collada-dom/riscv64 (2.5.0+ds1-3 to 2.5.0+ds1-3)
  • Migration status for collada-dom/riscv64 (2.5.0+ds1-3 to 2.5.0+ds1-3): Will attempt migration (Any information below is purely informational)
• collatinus/riscv64 (12.2-2 to 12.2-2)
  • Migration status for collatinus/riscv64 (12.2-2 to 12.2-2): Will attempt migration (Any information below is purely informational)
• colobot/riscv64 (0.2.1-2 to 0.2.1-2)
  • Migration status for colobot/riscv64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• colorcode/riscv64 (0.8.7-1 to 0.8.7-1)
  • Migration status for colorcode/riscv64 (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
• colord-gtk/riscv64 (0.3.1-1 to 0.3.1-1)
  • Migration status for colord-gtk/riscv64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• colord-kde/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for colord-kde/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• colord/riscv64 (1.4.7-1 to 1.4.7-1)
  • Migration status for colord/riscv64 (1.4.7-1 to 1.4.7-1): Will attempt migration (Any information below is purely informational)
• colorhug-client/riscv64 (0.2.8-3 to 0.2.8-3)
  • Migration status for colorhug-client/riscv64 (0.2.8-3 to 0.2.8-3): Will attempt migration (Any information below is purely informational)
• combblas/riscv64 (2.0.0-3.1 to 2.0.0-3.1)
  • Migration status for combblas/riscv64 (2.0.0-3.1 to 2.0.0-3.1): Will attempt migration (Any information below is purely informational)
• compiz-boxmenu/riscv64 (1.1.12-7 to 1.1.12-7)
  • Migration status for compiz-boxmenu/riscv64 (1.1.12-7 to 1.1.12-7): Will attempt migration (Any information below is purely informational)
• compizconfig-python/riscv64 (2:0.8.18-2 to 2:0.8.18-2)
  • Migration status for compizconfig-python/riscv64 (2:0.8.18-2 to 2:0.8.18-2): Will attempt migration (Any information below is purely informational)
• complexity/riscv64 (1.13-1 to 1.13-1)
  • Migration status for complexity/riscv64 (1.13-1 to 1.13-1): Will attempt migration (Any information below is purely informational)
• compreffor/riscv64 (0.5.5-1 to 0.5.5-1)
  • Migration status for compreffor/riscv64 (0.5.5-1 to 0.5.5-1): Will attempt migration (Any information below is purely informational)
• compton/riscv64 (1-3 to 1-3)
  • Migration status for compton/riscv64 (1-3 to 1-3): Will attempt migration (Any information below is purely informational)
• confclerk/riscv64 (0.7.2-1 to 0.7.2-1)
  • Migration status for confclerk/riscv64 (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• connectagram/riscv64 (1.3.5-2 to 1.3.5-2)
  • Migration status for connectagram/riscv64 (1.3.5-2 to 1.3.5-2): Will attempt migration (Any information below is purely informational)
• containerd/amd64 (1.7.20~ds2-2 to 1.7.20~ds2-2)
  • Migration status for containerd/amd64 (1.7.20~ds2-2 to 1.7.20~ds2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/amd64 golang-1.23
• containerd/arm64 (1.7.20~ds2-2 to 1.7.20~ds2-2)
  • Migration status for containerd/arm64 (1.7.20~ds2-2 to 1.7.20~ds2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/arm64 golang-1.23
• containerd/armel (1.7.20~ds2-2 to 1.7.20~ds2-2)
  • Migration status for containerd/armel (1.7.20~ds2-2 to 1.7.20~ds2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/armel golang-1.23
• containerd/armhf (1.7.20~ds2-2 to 1.7.20~ds2-2)
  • Migration status for containerd/armhf (1.7.20~ds2-2 to 1.7.20~ds2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/armhf golang-1.23
• containerd/i386 (1.7.20~ds2-2 to 1.7.20~ds2-2)
  • Migration status for containerd/i386 (1.7.20~ds2-2 to 1.7.20~ds2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/i386 golang-1.23
• containerd/mips64el (1.7.20~ds2-2 to 1.7.20~ds2-2)
  • Migration status for containerd/mips64el (1.7.20~ds2-2 to 1.7.20~ds2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/mips64el golang-1.23
• containerd/ppc64el (1.7.20~ds2-2 to 1.7.20~ds2-2)
  • Migration status for containerd/ppc64el (1.7.20~ds2-2 to 1.7.20~ds2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/ppc64el golang-1.23
• containerd/s390x (1.7.20~ds2-2 to 1.7.20~ds2-2)
  • Migration status for containerd/s390x (1.7.20~ds2-2 to 1.7.20~ds2-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: containerd/s390x golang-1.23
• converseen/riscv64 (0.12.2.3-1 to 0.12.2.3-1)
  • Migration status for converseen/riscv64 (0.12.2.3-1 to 0.12.2.3-1): Will attempt migration (Any information below is purely informational)
• coq-elpi/amd64 (2.1.0-1 to 2.1.0-1)
  • Migration status for coq-elpi/amd64 (2.1.0-1 to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-elpi/2.1.0-1+b7/amd64 to testing makes libcoq-mathcomp-algebra-tactics/1.2.3-4+b3/amd64 uninstallable
    • migrating libcoq-elpi/2.1.0-1+b7/amd64 to testing makes libcoq-mathcomp-analysis/1.2.0-2+b3/amd64 uninstallable
    • migrating libcoq-elpi/2.1.0-1+b7/amd64 to testing makes libcoq-mathcomp-classical/1.2.0-2+b3/amd64 uninstallable
    • Depends: coq-elpi/amd64 elpi/amd64
    • Implicit dependency: coq-elpi/amd64 coq-hierarchy-builder/amd64 (not considered)
• coq-elpi/arm64 (2.1.0-1 to 2.1.0-1)
  • Migration status for coq-elpi/arm64 (2.1.0-1 to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-elpi/2.1.0-1+b7/arm64 to testing makes libcoq-mathcomp-algebra-tactics/1.2.3-4+b3/arm64 uninstallable
    • migrating libcoq-elpi/2.1.0-1+b7/arm64 to testing makes libcoq-mathcomp-analysis/1.2.0-2+b3/arm64 uninstallable
    • migrating libcoq-elpi/2.1.0-1+b7/arm64 to testing makes libcoq-mathcomp-classical/1.2.0-2+b3/arm64 uninstallable
    • Depends: coq-elpi/arm64 elpi/arm64
    • Implicit dependency: coq-elpi/arm64 coq-hierarchy-builder/arm64 (not considered)
• coq-elpi/ppc64el (2.1.0-1 to 2.1.0-1)
  • Migration status for coq-elpi/ppc64el (2.1.0-1 to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-elpi/2.1.0-1+b7/ppc64el to testing makes libcoq-mathcomp-algebra-tactics/1.2.3-4+b3/ppc64el uninstallable
    • migrating libcoq-elpi/2.1.0-1+b7/ppc64el to testing makes libcoq-mathcomp-analysis/1.2.0-2+b3/ppc64el uninstallable
    • migrating libcoq-elpi/2.1.0-1+b7/ppc64el to testing makes libcoq-mathcomp-classical/1.2.0-2+b3/ppc64el uninstallable
    • Depends: coq-elpi/ppc64el elpi/ppc64el
    • Implicit dependency: coq-elpi/ppc64el coq-hierarchy-builder/ppc64el (not considered)
• coq-elpi/riscv64 (2.1.0-1 to 2.1.0-1)
  • Migration status for coq-elpi/riscv64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• coq-elpi/s390x (2.1.0-1 to 2.1.0-1)
  • Migration status for coq-elpi/s390x (2.1.0-1 to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-elpi/2.1.0-1+b6/s390x to testing makes libcoq-mathcomp-algebra-tactics/1.2.3-4+b4/s390x uninstallable
    • migrating libcoq-elpi/2.1.0-1+b6/s390x to testing makes libcoq-mathcomp-analysis/1.2.0-2+b4/s390x uninstallable
    • migrating libcoq-elpi/2.1.0-1+b6/s390x to testing makes libcoq-mathcomp-classical/1.2.0-2+b4/s390x uninstallable
    • Depends: coq-elpi/s390x elpi/s390x
    • Implicit dependency: coq-elpi/s390x coq-hierarchy-builder/s390x (not considered)
• coq-hierarchy-builder/amd64 (1.7.0-2 to 1.7.0-2)
  • Migration status for coq-hierarchy-builder/amd64 (1.7.0-2 to 1.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/amd64 to testing makes libcoq-mathcomp-algebra/2.2.0-2+b4/amd64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/amd64 to testing makes libcoq-mathcomp-analysis/1.2.0-2+b3/amd64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/amd64 to testing makes libcoq-mathcomp-character/2.2.0-2+b4/amd64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/amd64 to testing makes libcoq-mathcomp-classical/1.2.0-2+b3/amd64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/amd64 to testing makes libcoq-mathcomp-field/2.2.0-2+b4/amd64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/amd64 to testing makes libcoq-mathcomp-fingroup/2.2.0-2+b4/amd64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/amd64 to testing makes libcoq-mathcomp-solvable/2.2.0-2+b4/amd64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/amd64 to testing makes libcoq-mathcomp-ssreflect/2.2.0-2+b4/amd64 uninstallable
    • Depends: coq-hierarchy-builder/amd64 coq-elpi/amd64 (not considered)
• coq-hierarchy-builder/arm64 (1.7.0-2 to 1.7.0-2)
  • Migration status for coq-hierarchy-builder/arm64 (1.7.0-2 to 1.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/arm64 to testing makes libcoq-mathcomp-algebra/2.2.0-2+b4/arm64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/arm64 to testing makes libcoq-mathcomp-analysis/1.2.0-2+b3/arm64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/arm64 to testing makes libcoq-mathcomp-character/2.2.0-2+b4/arm64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/arm64 to testing makes libcoq-mathcomp-classical/1.2.0-2+b3/arm64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/arm64 to testing makes libcoq-mathcomp-field/2.2.0-2+b4/arm64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/arm64 to testing makes libcoq-mathcomp-fingroup/2.2.0-2+b4/arm64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/arm64 to testing makes libcoq-mathcomp-solvable/2.2.0-2+b4/arm64 uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/arm64 to testing makes libcoq-mathcomp-ssreflect/2.2.0-2+b4/arm64 uninstallable
    • Depends: coq-hierarchy-builder/arm64 coq-elpi/arm64 (not considered)
• coq-hierarchy-builder/ppc64el (1.7.0-2 to 1.7.0-2)
  • Migration status for coq-hierarchy-builder/ppc64el (1.7.0-2 to 1.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/ppc64el to testing makes libcoq-mathcomp-algebra/2.2.0-2+b4/ppc64el uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/ppc64el to testing makes libcoq-mathcomp-analysis/1.2.0-2+b3/ppc64el uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/ppc64el to testing makes libcoq-mathcomp-character/2.2.0-2+b4/ppc64el uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/ppc64el to testing makes libcoq-mathcomp-classical/1.2.0-2+b3/ppc64el uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/ppc64el to testing makes libcoq-mathcomp-field/2.2.0-2+b4/ppc64el uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/ppc64el to testing makes libcoq-mathcomp-fingroup/2.2.0-2+b4/ppc64el uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/ppc64el to testing makes libcoq-mathcomp-solvable/2.2.0-2+b4/ppc64el uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/ppc64el to testing makes libcoq-mathcomp-ssreflect/2.2.0-2+b4/ppc64el uninstallable
    • Depends: coq-hierarchy-builder/ppc64el coq-elpi/ppc64el (not considered)
• coq-hierarchy-builder/s390x (1.7.0-2 to 1.7.0-2)
  • Migration status for coq-hierarchy-builder/s390x (1.7.0-2 to 1.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/s390x to testing makes libcoq-mathcomp-algebra/2.2.0-2+b4/s390x uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/s390x to testing makes libcoq-mathcomp-analysis/1.2.0-2+b4/s390x uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/s390x to testing makes libcoq-mathcomp-character/2.2.0-2+b4/s390x uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/s390x to testing makes libcoq-mathcomp-classical/1.2.0-2+b4/s390x uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/s390x to testing makes libcoq-mathcomp-field/2.2.0-2+b4/s390x uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/s390x to testing makes libcoq-mathcomp-fingroup/2.2.0-2+b4/s390x uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/s390x to testing makes libcoq-mathcomp-solvable/2.2.0-2+b4/s390x uninstallable
    • migrating libcoq-hierarchy-builder/1.7.0-2+b5/s390x to testing makes libcoq-mathcomp-ssreflect/2.2.0-2+b4/s390x uninstallable
    • Depends: coq-hierarchy-builder/s390x coq-elpi/s390x (not considered)
• corsix-th/riscv64 (0.67-1 to 0.67-1)
  • Migration status for corsix-th/riscv64 (0.67-1 to 0.67-1): Will attempt migration (Any information below is purely informational)
• cpphs/riscv64 (1.20.9.1-3 to 1.20.9.1-3)
  • Migration status for cpphs/riscv64 (1.20.9.1-3 to 1.20.9.1-3): Will attempt migration (Any information below is purely informational)
• cppzmq/riscv64 (4.10.0-1 to 4.10.0-1)
  • Migration status for cppzmq/riscv64 (4.10.0-1 to 4.10.0-1): Will attempt migration (Any information below is purely informational)
• crack-attack/riscv64 (1.1.14-9.2 to 1.1.14-9.2)
  • Migration status for crack-attack/riscv64 (1.1.14-9.2 to 1.1.14-9.2): Will attempt migration (Any information below is purely informational)
• crawl/riscv64 (2:0.28.0-1.1 to 2:0.28.0-1.1)
  • Migration status for crawl/riscv64 (2:0.28.0-1.1 to 2:0.28.0-1.1): Will attempt migration (Any information below is purely informational)
• cricket/riscv64 (1.0.5-23 to 1.0.5-23)
  • Migration status for cricket/riscv64 (1.0.5-23 to 1.0.5-23): Will attempt migration (Any information below is purely informational)
• crimson/riscv64 (0.5.2-1.1 to 0.5.2-1.1)
  • Migration status for crimson/riscv64 (0.5.2-1.1 to 0.5.2-1.1): Will attempt migration (Any information below is purely informational)
• criticalmass/riscv64 (1:1.0.2-4 to 1:1.0.2-4)
  • Migration status for criticalmass/riscv64 (1:1.0.2-4 to 1:1.0.2-4): Will attempt migration (Any information below is purely informational)
• crossfire-client/riscv64 (1.75.3-1 to 1.75.3-1)
  • Migration status for crossfire-client/riscv64 (1.75.3-1 to 1.75.3-1): Will attempt migration (Any information below is purely informational)
• crowdsec-custom-bouncer/amd64 (0.0.15-4 to 0.0.15-4)
  • Migration status for crowdsec-custom-bouncer/amd64 (0.0.15-4 to 0.0.15-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-custom-bouncer/amd64 golang-1.23
• crowdsec-custom-bouncer/arm64 (0.0.15-4 to 0.0.15-4)
  • Migration status for crowdsec-custom-bouncer/arm64 (0.0.15-4 to 0.0.15-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-custom-bouncer/arm64 golang-1.23
• crowdsec-custom-bouncer/armel (0.0.15-4 to 0.0.15-4)
  • Migration status for crowdsec-custom-bouncer/armel (0.0.15-4 to 0.0.15-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-custom-bouncer/armel golang-1.23
• crowdsec-custom-bouncer/armhf (0.0.15-4 to 0.0.15-4)
  • Migration status for crowdsec-custom-bouncer/armhf (0.0.15-4 to 0.0.15-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-custom-bouncer/armhf golang-1.23
• crowdsec-custom-bouncer/i386 (0.0.15-4 to 0.0.15-4)
  • Migration status for crowdsec-custom-bouncer/i386 (0.0.15-4 to 0.0.15-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-custom-bouncer/i386 golang-1.23
• crowdsec-custom-bouncer/mips64el (0.0.15-4 to 0.0.15-4)
  • Migration status for crowdsec-custom-bouncer/mips64el (0.0.15-4 to 0.0.15-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-custom-bouncer/mips64el golang-1.23
• crowdsec-custom-bouncer/ppc64el (0.0.15-4 to 0.0.15-4)
  • Migration status for crowdsec-custom-bouncer/ppc64el (0.0.15-4 to 0.0.15-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-custom-bouncer/ppc64el golang-1.23
• crowdsec-custom-bouncer/s390x (0.0.15-4 to 0.0.15-4)
  • Migration status for crowdsec-custom-bouncer/s390x (0.0.15-4 to 0.0.15-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-custom-bouncer/s390x golang-1.23
• crowdsec-firewall-bouncer/amd64 (0.0.25-5 to 0.0.25-5)
  • Migration status for crowdsec-firewall-bouncer/amd64 (0.0.25-5 to 0.0.25-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-firewall-bouncer/amd64 golang-1.23
• crowdsec-firewall-bouncer/arm64 (0.0.25-5 to 0.0.25-5)
  • Migration status for crowdsec-firewall-bouncer/arm64 (0.0.25-5 to 0.0.25-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-firewall-bouncer/arm64 golang-1.23
• crowdsec-firewall-bouncer/armel (0.0.25-5 to 0.0.25-5)
  • Migration status for crowdsec-firewall-bouncer/armel (0.0.25-5 to 0.0.25-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-firewall-bouncer/armel golang-1.23
• crowdsec-firewall-bouncer/armhf (0.0.25-5 to 0.0.25-5)
  • Migration status for crowdsec-firewall-bouncer/armhf (0.0.25-5 to 0.0.25-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-firewall-bouncer/armhf golang-1.23
• crowdsec-firewall-bouncer/i386 (0.0.25-5 to 0.0.25-5)
  • Migration status for crowdsec-firewall-bouncer/i386 (0.0.25-5 to 0.0.25-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-firewall-bouncer/i386 golang-1.23
• crowdsec-firewall-bouncer/mips64el (0.0.25-5 to 0.0.25-5)
  • Migration status for crowdsec-firewall-bouncer/mips64el (0.0.25-5 to 0.0.25-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-firewall-bouncer/mips64el golang-1.23
• crowdsec-firewall-bouncer/ppc64el (0.0.25-5 to 0.0.25-5)
  • Migration status for crowdsec-firewall-bouncer/ppc64el (0.0.25-5 to 0.0.25-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-firewall-bouncer/ppc64el golang-1.23
• crowdsec-firewall-bouncer/s390x (0.0.25-5 to 0.0.25-5)
  • Migration status for crowdsec-firewall-bouncer/s390x (0.0.25-5 to 0.0.25-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec-firewall-bouncer/s390x golang-1.23
• crowdsec/amd64 (1.4.6-9 to 1.4.6-9)
  • Migration status for crowdsec/amd64 (1.4.6-9 to 1.4.6-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec/amd64 golang-1.23
    • Built-Using: crowdsec/amd64 golang-github-golang-jwt-jwt
• crowdsec/arm64 (1.4.6-9 to 1.4.6-9)
  • Migration status for crowdsec/arm64 (1.4.6-9 to 1.4.6-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec/arm64 golang-1.23
    • Built-Using: crowdsec/arm64 golang-github-golang-jwt-jwt
• crowdsec/armel (1.4.6-9 to 1.4.6-9)
  • Migration status for crowdsec/armel (1.4.6-9 to 1.4.6-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec/armel golang-1.23
    • Built-Using: crowdsec/armel golang-github-golang-jwt-jwt
• crowdsec/armhf (1.4.6-9 to 1.4.6-9)
  • Migration status for crowdsec/armhf (1.4.6-9 to 1.4.6-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec/armhf golang-1.23
    • Built-Using: crowdsec/armhf golang-github-golang-jwt-jwt
• crowdsec/i386 (1.4.6-9 to 1.4.6-9)
  • Migration status for crowdsec/i386 (1.4.6-9 to 1.4.6-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec/i386 golang-1.23
    • Built-Using: crowdsec/i386 golang-github-golang-jwt-jwt
• crowdsec/mips64el (1.4.6-9 to 1.4.6-9)
  • Migration status for crowdsec/mips64el (1.4.6-9 to 1.4.6-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec/mips64el golang-1.23
    • Built-Using: crowdsec/mips64el golang-github-golang-jwt-jwt
• crowdsec/ppc64el (1.4.6-9 to 1.4.6-9)
  • Migration status for crowdsec/ppc64el (1.4.6-9 to 1.4.6-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec/ppc64el golang-1.23
    • Built-Using: crowdsec/ppc64el golang-github-golang-jwt-jwt
• crowdsec/s390x (1.4.6-9 to 1.4.6-9)
  • Migration status for crowdsec/s390x (1.4.6-9 to 1.4.6-9): Will attempt migration (Any information below is purely informational)
    • Built-Using: crowdsec/s390x golang-1.23
    • Built-Using: crowdsec/s390x golang-github-golang-jwt-jwt
• crrcsim/riscv64 (0.9.13-3.2 to 0.9.13-3.2)
  • Migration status for crrcsim/riscv64 (0.9.13-3.2 to 0.9.13-3.2): Will attempt migration (Any information below is purely informational)
• csound-plugins/riscv64 (1.0.2~dfsg1-3 to 1.0.2~dfsg1-3)
  • Migration status for csound-plugins/riscv64 (1.0.2~dfsg1-3 to 1.0.2~dfsg1-3): Will attempt migration (Any information below is purely informational)
• ctsim/riscv64 (6.0.2-6 to 6.0.2-6)
  • Migration status for ctsim/riscv64 (6.0.2-6 to 6.0.2-6): Will attempt migration (Any information below is purely informational)
• cube2/riscv64 (0.0.20201227+dfsg-2 to 0.0.20201227+dfsg-2)
  • Migration status for cube2/riscv64 (0.0.20201227+dfsg-2 to 0.0.20201227+dfsg-2): Will attempt migration (Any information below is purely informational)
• curtain/riscv64 (0.3-1.1 to 0.3-1.1)
  • Migration status for curtain/riscv64 (0.3-1.1 to 0.3-1.1): Will attempt migration (Any information below is purely informational)
• cutecom/riscv64 (0.51.0-1 to 0.51.0-1)
  • Migration status for cutecom/riscv64 (0.51.0-1 to 0.51.0-1): Will attempt migration (Any information below is purely informational)
• cutemaze/riscv64 (1.3.2-1 to 1.3.2-1)
  • Migration status for cutemaze/riscv64 (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
• cutesdr/riscv64 (1.20-4 to 1.20-4)
  • Migration status for cutesdr/riscv64 (1.20-4 to 1.20-4): Will attempt migration (Any information below is purely informational)
• cutycapt/riscv64 (0.0~svn10-0.1 to 0.0~svn10-0.1)
  • Migration status for cutycapt/riscv64 (0.0~svn10-0.1 to 0.0~svn10-0.1): Will attempt migration (Any information below is purely informational)
• cynthiune.app/riscv64 (1.0.0-2 to 1.0.0-2)
  • Migration status for cynthiune.app/riscv64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• cytadela/riscv64 (1.1.0-4 to 1.1.0-4)
  • Migration status for cytadela/riscv64 (1.1.0-4 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
• daisy-player/riscv64 (13.0-4 to 13.0-4)
  • Migration status for daisy-player/riscv64 (13.0-4 to 13.0-4): Will attempt migration (Any information below is purely informational)
• danmaq/riscv64 (0.2.3.2-2 to 0.2.3.2-2)
  • Migration status for danmaq/riscv64 (0.2.3.2-2 to 0.2.3.2-2): Will attempt migration (Any information below is purely informational)
• dar/amd64 (2.7.15-2 to 2.7.15-2)
  • Migration status for dar/amd64 (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/amd64 curl (not considered)
    • Invalidated by built-using
• dar/arm64 (2.7.15-2 to 2.7.15-2)
  • Migration status for dar/arm64 (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/arm64 curl (not considered)
    • Invalidated by built-using
• dar/armhf (2.7.15-2 to 2.7.15-2)
  • Migration status for dar/armhf (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/armhf curl (not considered)
    • Invalidated by built-using
• dar/i386 (2.7.15-2 to 2.7.15-2)
  • Migration status for dar/i386 (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/i386 curl (not considered)
    • Invalidated by built-using
• dar/ppc64el (2.7.15-2 to 2.7.15-2)
  • Migration status for dar/ppc64el (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/ppc64el curl (not considered)
    • Invalidated by built-using
• 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 curl (not considered)
    • Invalidated by built-using
• darknet/riscv64 (0.0.0+git20180914.61c9d02e-2 to 0.0.0+git20180914.61c9d02e-2)
  • Migration status for darknet/riscv64 (0.0.0+git20180914.61c9d02e-2 to 0.0.0+git20180914.61c9d02e-2): Will attempt migration (Any information below is purely informational)
• darkplaces/riscv64 (0~20180908~beta1-5 to 0~20180908~beta1-5)
  • Migration status for darkplaces/riscv64 (0~20180908~beta1-5 to 0~20180908~beta1-5): Will attempt migration (Any information below is purely informational)
• darktable/amd64 (4.8.1-2 to 4.8.1-2)
  • Migration status for darktable/amd64 (4.8.1-2 to 4.8.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: darktable/amd64 exiv2
• darktable/arm64 (4.8.1-2 to 4.8.1-2)
  • Migration status for darktable/arm64 (4.8.1-2 to 4.8.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: darktable/arm64 exiv2
• das-watchdog/riscv64 (0.9.0-5 to 0.9.0-5)
  • Migration status for das-watchdog/riscv64 (0.9.0-5 to 0.9.0-5): Will attempt migration (Any information below is purely informational)
• dasher/riscv64 (5.0.0~beta~repack2-4 to 5.0.0~beta~repack2-4)
  • Migration status for dasher/riscv64 (5.0.0~beta~repack2-4 to 5.0.0~beta~repack2-4): Will attempt migration (Any information below is purely informational)
• dataquay/riscv64 (0.9.1-2 to 0.9.1-2)
  • Migration status for dataquay/riscv64 (0.9.1-2 to 0.9.1-2): Will attempt migration (Any information below is purely informational)
• davfs2/riscv64 (1.7.0-1 to 1.7.0-1)
  • Migration status for davfs2/riscv64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• dcl/riscv64 (7.5.1-2 to 7.5.1-2)
  • Migration status for dcl/riscv64 (7.5.1-2 to 7.5.1-2): Will attempt migration (Any information below is purely informational)
• dconf-editor/riscv64 (45.0.1-1 to 45.0.1-1)
  • Migration status for dconf-editor/riscv64 (45.0.1-1 to 45.0.1-1): Will attempt migration (Any information below is purely informational)
• dde-calendar/riscv64 (5.9.1-4 to 5.9.1-4)
  • Migration status for dde-calendar/riscv64 (5.9.1-4 to 5.9.1-4): Will attempt migration (Any information below is purely informational)
• dde-qt5integration/riscv64 (5.5.23-1 to 5.5.23-1)
  • Migration status for dde-qt5integration/riscv64 (5.5.23-1 to 5.5.23-1): Will attempt migration (Any information below is purely informational)
• dde-store/riscv64 (1.2.5-1 to 1.2.5-1)
  • Migration status for dde-store/riscv64 (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
• deb-gview/riscv64 (0.3.7 to 0.3.7)
  • Migration status for deb-gview/riscv64 (0.3.7 to 0.3.7): Will attempt migration (Any information below is purely informational)
• debconf-kde/riscv64 (1.1.0-1 to 1.1.0-1)
  • Migration status for debconf-kde/riscv64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• 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
• 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/mips64el (1.4.0-1 to 1.4.0-1)
  • Migration status for deck/mips64el (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: deck/mips64el 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/s390x (1.4.0-1 to 1.4.0-1)
  • Migration status for deck/s390x (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: deck/s390x golang-1.23
• deepin-boot-maker/riscv64 (5.7.8+dfsg-3 to 5.7.8+dfsg-3)
  • Migration status for deepin-boot-maker/riscv64 (5.7.8+dfsg-3 to 5.7.8+dfsg-3): Will attempt migration (Any information below is purely informational)
• deepin-calculator/riscv64 (5.7.21-2 to 5.7.21-2)
  • Migration status for deepin-calculator/riscv64 (5.7.21-2 to 5.7.21-2): Will attempt migration (Any information below is purely informational)
• deepin-deb-installer/riscv64 (5.12.4-2 to 5.12.4-2)
  • Migration status for deepin-deb-installer/riscv64 (5.12.4-2 to 5.12.4-2): Will attempt migration (Any information below is purely informational)
• deepin-log-viewer/riscv64 (5.9.7+ds1-3 to 5.9.7+ds1-3)
  • Migration status for deepin-log-viewer/riscv64 (5.9.7+ds1-3 to 5.9.7+ds1-3): Will attempt migration (Any information below is purely informational)
• deepin-menu/riscv64 (5.0.1-2 to 5.0.1-2)
  • Migration status for deepin-menu/riscv64 (5.0.1-2 to 5.0.1-2): Will attempt migration (Any information below is purely informational)
• deepin-notifications/riscv64 (3.3.4-2 to 3.3.4-2)
  • Migration status for deepin-notifications/riscv64 (3.3.4-2 to 3.3.4-2): Will attempt migration (Any information below is purely informational)
• deepin-qt5dxcb-plugin/riscv64 (5.0.65-1 to 5.0.65-1)
  • Migration status for deepin-qt5dxcb-plugin/riscv64 (5.0.65-1 to 5.0.65-1): Will attempt migration (Any information below is purely informational)
• deepin-screen-recorder/riscv64 (5.8.0.46-3 to 5.8.0.46-3)
  • Migration status for deepin-screen-recorder/riscv64 (5.8.0.46-3 to 5.8.0.46-3): Will attempt migration (Any information below is purely informational)
• deepin-shortcut-viewer/riscv64 (5.0.6-1 to 5.0.6-1)
  • Migration status for deepin-shortcut-viewer/riscv64 (5.0.6-1 to 5.0.6-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)
• deja-dup/riscv64 (45.2-1 to 45.2-1)
  • Migration status for deja-dup/riscv64 (45.2-1 to 45.2-1): Will attempt migration (Any information below is purely informational)
• desmume/riscv64 (0.9.11-7 to 0.9.11-7)
  • Migration status for desmume/riscv64 (0.9.11-7 to 0.9.11-7): Will attempt migration (Any information below is purely informational)
• devhelp/riscv64 (43.0-4 to 43.0-4)
  • Migration status for devhelp/riscv64 (43.0-4 to 43.0-4): Will attempt migration (Any information below is purely informational)
• devil/riscv64 (1.7.8-11 to 1.7.8-11)
  • Migration status for devil/riscv64 (1.7.8-11 to 1.7.8-11): Will attempt migration (Any information below is purely informational)
• devilspie/riscv64 (0.23-3 to 0.23-3)
  • Migration status for devilspie/riscv64 (0.23-3 to 0.23-3): Will attempt migration (Any information below is purely informational)
• devilspie2/riscv64 (0.43-5 to 0.43-5)
  • Migration status for devilspie2/riscv64 (0.43-5 to 0.43-5): Will attempt migration (Any information below is purely informational)
• dewalls/riscv64 (1.0.0+ds1-9 to 1.0.0+ds1-9)
  • Migration status for dewalls/riscv64 (1.0.0+ds1-9 to 1.0.0+ds1-9): Will attempt migration (Any information below is purely informational)
• dfcgen-gtk/riscv64 (0.6-2 to 0.6-2)
  • Migration status for dfcgen-gtk/riscv64 (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
• dgedit/riscv64 (0.10.0-2 to 0.10.0-2)
  • Migration status for dgedit/riscv64 (0.10.0-2 to 0.10.0-2): Will attempt migration (Any information below is purely informational)
• dh-dlang/riscv64 (0.6.6 to 0.6.6)
  • Migration status for dh-dlang/riscv64 (0.6.6 to 0.6.6): Will attempt migration (Any information below is purely informational)
• dh-make-golang/riscv64 (0.7.0-1 to 0.7.0-1)
  • Migration status for dh-make-golang/riscv64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• dhcpcd-ui/riscv64 (0.7.9-5 to 0.7.9-5)
  • Migration status for dhcpcd-ui/riscv64 (0.7.9-5 to 0.7.9-5): Will attempt migration (Any information below is purely informational)
• dianara/riscv64 (1.4.4-1 to 1.4.4-1)
  • Migration status for dianara/riscv64 (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
• dicomscope/riscv64 (3.6.0-27 to 3.6.0-27)
  • Migration status for dicomscope/riscv64 (3.6.0-27 to 3.6.0-27): Will attempt migration (Any information below is purely informational)
• dictconv/riscv64 (0.2-7.2 to 0.2-7.2)
  • Migration status for dictconv/riscv64 (0.2-7.2 to 0.2-7.2): Will attempt migration (Any information below is purely informational)
• diff-pdf-wx/riscv64 (0.5.1-2 to 0.5.1-2)
  • Migration status for diff-pdf-wx/riscv64 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• diffoscope_pu (277 to 240+deb12u1)
  • Migration status for diffoscope_pu (277 to 240+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: diffoscope is newer in the target suite (277 240+deb12u1)
• diffpdf/riscv64 (2.1.3.1-2 to 2.1.3.1-2)
  • Migration status for diffpdf/riscv64 (2.1.3.1-2 to 2.1.3.1-2): Will attempt migration (Any information below is purely informational)
• digikam/amd64 (4:8.4.0-3 to 4:8.4.0-3)
  • Migration status for digikam/amd64 (4:8.4.0-3 to 4:8.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: digikam/amd64 exiv2
• digikam/arm64 (4:8.4.0-3 to 4:8.4.0-3)
  • Migration status for digikam/arm64 (4:8.4.0-3 to 4:8.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: digikam/arm64 exiv2
• digikam/armhf (4:8.4.0-3 to 4:8.4.0-3)
  • Migration status for digikam/armhf (4:8.4.0-3 to 4:8.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: digikam/armhf exiv2
• digikam/i386 (4:8.4.0-3 to 4:8.4.0-3)
  • Migration status for digikam/i386 (4:8.4.0-3 to 4:8.4.0-3): Will attempt migration (Any information below is purely informational)
    • Depends: digikam/i386 exiv2
• digimend-dkms/riscv64 (13-1 to 13-1)
  • Migration status for digimend-dkms/riscv64 (13-1 to 13-1): Will attempt migration (Any information below is purely informational)
• din/riscv64 (58.1+ds-1 to 58.1+ds-1)
  • Migration status for din/riscv64 (58.1+ds-1 to 58.1+ds-1): Will attempt migration (Any information below is purely informational)
• diodon/riscv64 (1.13.0-1 to 1.13.0-1)
  • Migration status for diodon/riscv64 (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
• directfb/riscv64 (1.7.7-13 to 1.7.7-13)
  • Migration status for directfb/riscv64 (1.7.7-13 to 1.7.7-13): Will attempt migration (Any information below is purely informational)
• 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/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.0-4 to 3.0-4)
  • Migration status for distrobuilder/amd64 (3.0-4 to 3.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: distrobuilder/amd64 golang-1.23
• distrobuilder/arm64 (3.0-4 to 3.0-4)
  • Migration status for distrobuilder/arm64 (3.0-4 to 3.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: distrobuilder/arm64 golang-1.23
• distrobuilder/armel (3.0-4 to 3.0-4)
  • Migration status for distrobuilder/armel (3.0-4 to 3.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: distrobuilder/armel golang-1.23
• distrobuilder/armhf (3.0-4 to 3.0-4)
  • Migration status for distrobuilder/armhf (3.0-4 to 3.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: distrobuilder/armhf golang-1.23
• distrobuilder/i386 (3.0-4 to 3.0-4)
  • Migration status for distrobuilder/i386 (3.0-4 to 3.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: distrobuilder/i386 golang-1.23
• distrobuilder/mips64el (3.0-4 to 3.0-4)
  • Migration status for distrobuilder/mips64el (3.0-4 to 3.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: distrobuilder/mips64el golang-1.23
• distrobuilder/ppc64el (3.0-4 to 3.0-4)
  • Migration status for distrobuilder/ppc64el (3.0-4 to 3.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: distrobuilder/ppc64el golang-1.23
• distrobuilder/s390x (3.0-4 to 3.0-4)
  • Migration status for distrobuilder/s390x (3.0-4 to 3.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: distrobuilder/s390x golang-1.23
• djview4/riscv64 (4.12-3 to 4.12-3)
  • Migration status for djview4/riscv64 (4.12-3 to 4.12-3): Will attempt migration (Any information below is purely informational)
• 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/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
• dmtx-utils/riscv64 (0.7.6-1.1 to 0.7.6-1.1)
  • Migration status for dmtx-utils/riscv64 (0.7.6-1.1 to 0.7.6-1.1): Will attempt migration (Any information below is purely informational)
• dnscrypt-proxy/amd64 (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2)
  • Migration status for dnscrypt-proxy/amd64 (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/amd64 golang-1.23
• dnscrypt-proxy/arm64 (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2)
  • Migration status for dnscrypt-proxy/arm64 (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/arm64 golang-1.23
• dnscrypt-proxy/armel (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2)
  • Migration status for dnscrypt-proxy/armel (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/armel golang-1.23
• dnscrypt-proxy/armhf (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2)
  • Migration status for dnscrypt-proxy/armhf (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/armhf golang-1.23
• dnscrypt-proxy/i386 (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2)
  • Migration status for dnscrypt-proxy/i386 (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/i386 golang-1.23
• dnscrypt-proxy/mips64el (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2)
  • Migration status for dnscrypt-proxy/mips64el (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/mips64el golang-1.23
• dnscrypt-proxy/ppc64el (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2)
  • Migration status for dnscrypt-proxy/ppc64el (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2): Will attempt migration (Any information below is purely informational)
    • Built-Using: dnscrypt-proxy/ppc64el golang-1.23
• dnscrypt-proxy/s390x (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2)
  • Migration status for dnscrypt-proxy/s390x (2.0.45+ds1-1.2 to 2.0.45+ds1-1.2): Will attempt migration (Any information below is purely informational)
    • 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/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
• docbook2x/riscv64 (0.8.8-18 to 0.8.8-18)
  • Migration status for docbook2x/riscv64 (0.8.8-18 to 0.8.8-18): Will attempt migration (Any information below is purely informational)
• 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/mips64el (2.8.3+ds1-2 to 2.8.3+ds1-2)
  • Migration status for docker-registry/mips64el (2.8.3+ds1-2 to 2.8.3+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker-registry/mips64el 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): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker-registry/s390x golang-1.23
• docker.io/amd64 (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2)
  • Migration status for docker.io/amd64 (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker.io/amd64 golang-1.23
    • Built-Using: docker.io/amd64 golang-github-golang-jwt-jwt
• docker.io/arm64 (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2)
  • Migration status for docker.io/arm64 (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker.io/arm64 golang-1.23
    • Built-Using: docker.io/arm64 golang-github-golang-jwt-jwt
• docker.io/armel (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2)
  • Migration status for docker.io/armel (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker.io/armel golang-1.23
    • Built-Using: docker.io/armel golang-github-golang-jwt-jwt
• docker.io/armhf (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2)
  • Migration status for docker.io/armhf (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker.io/armhf golang-1.23
    • Built-Using: docker.io/armhf golang-github-golang-jwt-jwt
• docker.io/i386 (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2)
  • Migration status for docker.io/i386 (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker.io/i386 golang-1.23
    • Built-Using: docker.io/i386 golang-github-golang-jwt-jwt
• docker.io/ppc64el (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2)
  • Migration status for docker.io/ppc64el (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker.io/ppc64el golang-1.23
    • Built-Using: docker.io/ppc64el golang-github-golang-jwt-jwt
• docker.io/s390x (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2)
  • Migration status for docker.io/s390x (26.1.5+dfsg1-2 to 26.1.5+dfsg1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: docker.io/s390x golang-1.23
    • Built-Using: docker.io/s390x golang-github-golang-jwt-jwt
• dolphin-plugins/riscv64 (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for dolphin-plugins/riscv64 (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• dolphin/riscv64 (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for dolphin/riscv64 (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• doomsday/riscv64 (2.3.1+ds1-1 to 2.3.1+ds1-1)
  • Migration status for doomsday/riscv64 (2.3.1+ds1-1 to 2.3.1+ds1-1): Will attempt migration (Any information below is purely informational)
• dopewars/riscv64 (1.6.2-1 to 1.6.2-1)
  • Migration status for dopewars/riscv64 (1.6.2-1 to 1.6.2-1): Will attempt migration (Any information below is purely informational)
• dosbox/riscv64 (0.74-3-5 to 0.74-3-5)
  • Migration status for dosbox/riscv64 (0.74-3-5 to 0.74-3-5): Will attempt migration (Any information below is purely informational)
• doxygen/riscv64 (1.9.8+ds-2 to 1.9.8+ds-2)
  • Migration status for doxygen/riscv64 (1.9.8+ds-2 to 1.9.8+ds-2): Will attempt migration (Any information below is purely informational)
• dpuser/riscv64 (4.1+dfsg-2 to 4.1+dfsg-2)
  • Migration status for dpuser/riscv64 (4.1+dfsg-2 to 4.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• dragon/riscv64 (4:23.04.2-1 to 4:23.04.2-1)
  • Migration status for dragon/riscv64 (4:23.04.2-1 to 4:23.04.2-1): Will attempt migration (Any information below is purely informational)
• dragonfly-reverb/riscv64 (3.2.10-3 to 3.2.10-3)
  • Migration status for dragonfly-reverb/riscv64 (3.2.10-3 to 3.2.10-3): Will attempt migration (Any information below is purely informational)
• drawing/riscv64 (1.0.2-1 to 1.0.2-1)
  • Migration status for drawing/riscv64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• drawtiming/riscv64 (0.7.1-10 to 0.7.1-10)
  • Migration status for drawtiming/riscv64 (0.7.1-10 to 0.7.1-10): Will attempt migration (Any information below is purely informational)
• drawxtl/riscv64 (5.5-6.1 to 5.5-6.1)
  • Migration status for drawxtl/riscv64 (5.5-6.1 to 5.5-6.1): Will attempt migration (Any information below is purely informational)
• dreamchess/riscv64 (0.3.0-2 to 0.3.0-2)
  • Migration status for dreamchess/riscv64 (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• driftnet/riscv64 (1.5.0-0.2 to 1.5.0-0.2)
  • Migration status for driftnet/riscv64 (1.5.0-0.2 to 1.5.0-0.2): Will attempt migration (Any information below is purely informational)
• dsmidiwifi/riscv64 (2 to 2)
  • Migration status for dsmidiwifi/riscv64 (2 to 2): Will attempt migration (Any information below is purely informational)
• dspdfviewer/riscv64 (1.15.1-1.1 to 1.15.1-1.1)
  • Migration status for dspdfviewer/riscv64 (1.15.1-1.1 to 1.15.1-1.1): Will attempt migration (Any information below is purely informational)
• dtkcore/riscv64 (5.5.33-2 to 5.5.33-2)
  • Migration status for dtkcore/riscv64 (5.5.33-2 to 5.5.33-2): Will attempt migration (Any information below is purely informational)
• dtkgui/riscv64 (5.5.25-2 to 5.5.25-2)
  • Migration status for dtkgui/riscv64 (5.5.25-2 to 5.5.25-2): Will attempt migration (Any information below is purely informational)
• dtkwidget/riscv64 (5.5.48-3 to 5.5.48-3)
  • Migration status for dtkwidget/riscv64 (5.5.48-3 to 5.5.48-3): Will attempt migration (Any information below is purely informational)
• 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
• 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
• 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
• 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
• 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
• 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
• 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
• dumpet/riscv64 (2.1-15 to 2.1-15)
  • Migration status for dumpet/riscv64 (2.1-15 to 2.1-15): Will attempt migration (Any information below is purely informational)
• dune-common/riscv64 (2.9.0-6 to 2.9.0-6)
  • Migration status for dune-common/riscv64 (2.9.0-6 to 2.9.0-6): Will attempt migration (Any information below is purely informational)
• dune-functions/riscv64 (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-functions/riscv64 (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-geometry/riscv64 (2.9.0-4 to 2.9.0-4)
  • Migration status for dune-geometry/riscv64 (2.9.0-4 to 2.9.0-4): Will attempt migration (Any information below is purely informational)
• dune-grid-glue/riscv64 (2.9.0-3 to 2.9.0-3)
  • Migration status for dune-grid-glue/riscv64 (2.9.0-3 to 2.9.0-3): Will attempt migration (Any information below is purely informational)
• dune-grid/riscv64 (2.9.0-4 to 2.9.0-4)
  • Migration status for dune-grid/riscv64 (2.9.0-4 to 2.9.0-4): Will attempt migration (Any information below is purely informational)
• dune-localfunctions/riscv64 (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-localfunctions/riscv64 (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-typetree/riscv64 (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-typetree/riscv64 (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dune-uggrid/riscv64 (2.9.0-2 to 2.9.0-2)
  • Migration status for dune-uggrid/riscv64 (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• dunst/riscv64 (1.11.0-1 to 1.11.0-1)
  • Migration status for dunst/riscv64 (1.11.0-1 to 1.11.0-1): Will attempt migration (Any information below is purely informational)
• duo-unix/riscv64 (1.11.3-1.2 to 1.11.3-1.2)
  • Migration status for duo-unix/riscv64 (1.11.3-1.2 to 1.11.3-1.2): Will attempt migration (Any information below is purely informational)
• dupeguru/riscv64 (4.3.1-4 to 4.3.1-4)
  • Migration status for dupeguru/riscv64 (4.3.1-4 to 4.3.1-4): Will attempt migration (Any information below is purely informational)
• dustrac/riscv64 (2.1.1-2 to 2.1.1-2)
  • Migration status for dustrac/riscv64 (2.1.1-2 to 2.1.1-2): Will attempt migration (Any information below is purely informational)
• dvbtune/riscv64 (0.5.ds-5 to 0.5.ds-5)
  • Migration status for dvbtune/riscv64 (0.5.ds-5 to 0.5.ds-5): Will attempt migration (Any information below is purely informational)
• dvdauthor/riscv64 (0.7.2-2 to 0.7.2-2)
  • Migration status for dvdauthor/riscv64 (0.7.2-2 to 0.7.2-2): Will attempt migration (Any information below is purely informational)
• dvgrab/riscv64 (3.5+git20160707.1.e46042e-1 to 3.5+git20160707.1.e46042e-1)
  • Migration status for dvgrab/riscv64 (3.5+git20160707.1.e46042e-1 to 3.5+git20160707.1.e46042e-1): Will attempt migration (Any information below is purely informational)
• dyssol/riscv64 (1.1.1+ds1-2.1 to 1.1.1+ds1-2.1)
  • Migration status for dyssol/riscv64 (1.1.1+ds1-2.1 to 1.1.1+ds1-2.1): Will attempt migration (Any information below is purely informational)
• ea-utils/riscv64 (1.1.2+dfsg-9 to 1.1.2+dfsg-9)
  • Migration status for ea-utils/riscv64 (1.1.2+dfsg-9 to 1.1.2+dfsg-9): Will attempt migration (Any information below is purely informational)
• easychem/riscv64 (0.6-9 to 0.6-9)
  • Migration status for easychem/riscv64 (0.6-9 to 0.6-9): Will attempt migration (Any information below is purely informational)
• easygen/amd64 (5.3.0-1 to 5.3.0-1)
  • Migration status for easygen/amd64 (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: easygen/amd64 golang-1.23
• easygen/arm64 (5.3.0-1 to 5.3.0-1)
  • Migration status for easygen/arm64 (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: easygen/arm64 golang-1.23
• easygen/armel (5.3.0-1 to 5.3.0-1)
  • Migration status for easygen/armel (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: easygen/armel golang-1.23
• easygen/armhf (5.3.0-1 to 5.3.0-1)
  • Migration status for easygen/armhf (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: easygen/armhf golang-1.23
• easygen/i386 (5.3.0-1 to 5.3.0-1)
  • Migration status for easygen/i386 (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: easygen/i386 golang-1.23
• easygen/ppc64el (5.3.0-1 to 5.3.0-1)
  • Migration status for easygen/ppc64el (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: easygen/ppc64el golang-1.23
• easygen/s390x (5.3.0-1 to 5.3.0-1)
  • Migration status for easygen/s390x (5.3.0-1 to 5.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: easygen/s390x golang-1.23
• easyssh/riscv64 (1.7.9-4 to 1.7.9-4)
  • Migration status for easyssh/riscv64 (1.7.9-4 to 1.7.9-4): Will attempt migration (Any information below is purely informational)
• easytag/riscv64 (2.4.3-5 to 2.4.3-5)
  • Migration status for easytag/riscv64 (2.4.3-5 to 2.4.3-5): Will attempt migration (Any information below is purely informational)
• ebook-speaker/riscv64 (6.2.0-6 to 6.2.0-6)
  • Migration status for ebook-speaker/riscv64 (6.2.0-6 to 6.2.0-6): Will attempt migration (Any information below is purely informational)
• ebook-tools/riscv64 (0.2.2-6 to 0.2.2-6)
  • Migration status for ebook-tools/riscv64 (0.2.2-6 to 0.2.2-6): Will attempt migration (Any information below is purely informational)
• ebook2cwgui/riscv64 (0.1.2-7 to 0.1.2-7)
  • Migration status for ebook2cwgui/riscv64 (0.1.2-7 to 0.1.2-7): Will attempt migration (Any information below is purely informational)
• eccodes-python/riscv64 (2:1.7.0-1 to 2:1.7.0-1)
  • Migration status for eccodes-python/riscv64 (2:1.7.0-1 to 2:1.7.0-1): Will attempt migration (Any information below is purely informational)
• ecmwflibs/riscv64 (2:0.6.3-1 to 2:0.6.3-1)
  • Migration status for ecmwflibs/riscv64 (2:0.6.3-1 to 2:0.6.3-1): Will attempt migration (Any information below is purely informational)
• edenmath.app/riscv64 (1.1.1a-8 to 1.1.1a-8)
  • Migration status for edenmath.app/riscv64 (1.1.1a-8 to 1.1.1a-8): Will attempt migration (Any information below is purely informational)
• efm-langserver/amd64 (0.0.53-1 to 0.0.53-1)
  • Migration status for efm-langserver/amd64 (0.0.53-1 to 0.0.53-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: efm-langserver/amd64 golang-1.23
• efm-langserver/arm64 (0.0.53-1 to 0.0.53-1)
  • Migration status for efm-langserver/arm64 (0.0.53-1 to 0.0.53-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: efm-langserver/arm64 golang-1.23
• efm-langserver/armel (0.0.53-1 to 0.0.53-1)
  • Migration status for efm-langserver/armel (0.0.53-1 to 0.0.53-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: efm-langserver/armel golang-1.23
• efm-langserver/armhf (0.0.53-1 to 0.0.53-1)
  • Migration status for efm-langserver/armhf (0.0.53-1 to 0.0.53-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: efm-langserver/armhf golang-1.23
• efm-langserver/i386 (0.0.53-1 to 0.0.53-1)
  • Migration status for efm-langserver/i386 (0.0.53-1 to 0.0.53-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: efm-langserver/i386 golang-1.23
• efm-langserver/ppc64el (0.0.53-1 to 0.0.53-1)
  • Migration status for efm-langserver/ppc64el (0.0.53-1 to 0.0.53-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: efm-langserver/ppc64el golang-1.23
• efm-langserver/s390x (0.0.53-1 to 0.0.53-1)
  • Migration status for efm-langserver/s390x (0.0.53-1 to 0.0.53-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: efm-langserver/s390x golang-1.23
• einstein/riscv64 (2.0.dfsg.2-10 to 2.0.dfsg.2-10)
  • Migration status for einstein/riscv64 (2.0.dfsg.2-10 to 2.0.dfsg.2-10): Will attempt migration (Any information below is purely informational)
• elektroid/riscv64 (3.0.1-2 to 3.0.1-2)
  • Migration status for elektroid/riscv64 (3.0.1-2 to 3.0.1-2): Will attempt migration (Any information below is purely informational)
• elpi/amd64 (1.18.2-5 to 1.18.2-5)
  • Migration status for elpi/amd64 (1.18.2-5 to 1.18.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: elpi/amd64 ocaml-re (not considered)
    • Invalidated by dependency
    • Implicit dependency: elpi/amd64 coq-elpi/amd64 (not considered)
• elpi/arm64 (1.18.2-5 to 1.18.2-5)
  • Migration status for elpi/arm64 (1.18.2-5 to 1.18.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: elpi/arm64 ocaml-re (not considered)
    • Invalidated by dependency
    • Implicit dependency: elpi/arm64 coq-elpi/arm64 (not considered)
• elpi/ppc64el (1.18.2-5 to 1.18.2-5)
  • Migration status for elpi/ppc64el (1.18.2-5 to 1.18.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: elpi/ppc64el ocaml-re (not considered)
    • Invalidated by dependency
    • Implicit dependency: elpi/ppc64el coq-elpi/ppc64el (not considered)
• elpi/riscv64 (1.18.2-5 to 1.18.2-5)
  • Migration status for elpi/riscv64 (1.18.2-5 to 1.18.2-5): Will attempt migration (Any information below is purely informational)
• elpi/s390x (1.18.2-5 to 1.18.2-5)
  • Migration status for elpi/s390x (1.18.2-5 to 1.18.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: elpi/s390x ocaml-re (not considered)
    • Invalidated by dependency
    • Implicit dependency: elpi/s390x coq-elpi/s390x (not considered)
• elvish/amd64 (0.21.0-2 to 0.21.0-2)
  • Migration status for elvish/amd64 (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: elvish/amd64 golang-1.23
• elvish/arm64 (0.21.0-2 to 0.21.0-2)
  • Migration status for elvish/arm64 (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: elvish/arm64 golang-1.23
• elvish/armel (0.21.0-2 to 0.21.0-2)
  • Migration status for elvish/armel (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: elvish/armel golang-1.23
• elvish/armhf (0.21.0-2 to 0.21.0-2)
  • Migration status for elvish/armhf (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: elvish/armhf golang-1.23
• elvish/i386 (0.21.0-2 to 0.21.0-2)
  • Migration status for elvish/i386 (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: elvish/i386 golang-1.23
• elvish/ppc64el (0.21.0-2 to 0.21.0-2)
  • Migration status for elvish/ppc64el (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: elvish/ppc64el golang-1.23
• elvish/s390x (0.21.0-2 to 0.21.0-2)
  • Migration status for elvish/s390x (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: elvish/s390x golang-1.23
• emacspeak-ss/riscv64 (1.12.1-9 to 1.12.1-9)
  • Migration status for emacspeak-ss/riscv64 (1.12.1-9 to 1.12.1-9): Will attempt migration (Any information below is purely informational)
• emd/amd64 (1.0.1-3 to 1.0.1-3)
  • Migration status for emd/amd64 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: emd/amd64 golang-1.23
• emd/arm64 (1.0.1-3 to 1.0.1-3)
  • Migration status for emd/arm64 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: emd/arm64 golang-1.23
• emd/armel (1.0.1-3 to 1.0.1-3)
  • Migration status for emd/armel (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: emd/armel golang-1.23
• emd/armhf (1.0.1-3 to 1.0.1-3)
  • Migration status for emd/armhf (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: emd/armhf golang-1.23
• emd/i386 (1.0.1-3 to 1.0.1-3)
  • Migration status for emd/i386 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: emd/i386 golang-1.23
• emd/ppc64el (1.0.1-3 to 1.0.1-3)
  • Migration status for emd/ppc64el (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: emd/ppc64el golang-1.23
• emd/s390x (1.0.1-3 to 1.0.1-3)
  • Migration status for emd/s390x (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: emd/s390x golang-1.23
• emerald/riscv64 (0.8.18-4.2 to 0.8.18-4.2)
  • Migration status for emerald/riscv64 (0.8.18-4.2 to 0.8.18-4.2): Will attempt migration (Any information below is purely informational)
• emoslib/riscv64 (2:4.5.9-10 to 2:4.5.9-10)
  • Migration status for emoslib/riscv64 (2:4.5.9-10 to 2:4.5.9-10): Will attempt migration (Any information below is purely informational)
• emptty/amd64 (0.12.1-1 to 0.12.1-1)
  • Migration status for emptty/amd64 (0.12.1-1 to 0.12.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: emptty/amd64 golang-1.23
• emptty/arm64 (0.12.1-1 to 0.12.1-1)
  • Migration status for emptty/arm64 (0.12.1-1 to 0.12.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: emptty/arm64 golang-1.23
• emptty/armel (0.12.1-1 to 0.12.1-1)
  • Migration status for emptty/armel (0.12.1-1 to 0.12.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: emptty/armel golang-1.23
• emptty/armhf (0.12.1-1 to 0.12.1-1)
  • Migration status for emptty/armhf (0.12.1-1 to 0.12.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: emptty/armhf golang-1.23
• emptty/i386 (0.12.1-1 to 0.12.1-1)
  • Migration status for emptty/i386 (0.12.1-1 to 0.12.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: emptty/i386 golang-1.23
• emptty/ppc64el (0.12.1-1 to 0.12.1-1)
  • Migration status for emptty/ppc64el (0.12.1-1 to 0.12.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: emptty/ppc64el golang-1.23
• emptty/s390x (0.12.1-1 to 0.12.1-1)
  • Migration status for emptty/s390x (0.12.1-1 to 0.12.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: emptty/s390x golang-1.23
• enemylines3/riscv64 (1.25-1 to 1.25-1)
  • Migration status for enemylines3/riscv64 (1.25-1 to 1.25-1): Will attempt migration (Any information below is purely informational)
• enemylines7/riscv64 (0.6-6 to 0.6-6)
  • Migration status for enemylines7/riscv64 (0.6-6 to 0.6-6): Will attempt migration (Any information below is purely informational)
• engauge-digitizer/riscv64 (12.1+ds.1-1 to 12.1+ds.1-1)
  • Migration status for engauge-digitizer/riscv64 (12.1+ds.1-1 to 12.1+ds.1-1): Will attempt migration (Any information below is purely informational)
• engrampa/riscv64 (1.26.2-4 to 1.26.2-4)
  • Migration status for engrampa/riscv64 (1.26.2-4 to 1.26.2-4): Will attempt migration (Any information below is purely informational)
• enki-aseba/riscv64 (1:1.6.99-2 to 1:1.6.99-2)
  • Migration status for enki-aseba/riscv64 (1:1.6.99-2 to 1:1.6.99-2): Will attempt migration (Any information below is purely informational)
• entangle/riscv64 (3.0-4 to 3.0-4)
  • Migration status for entangle/riscv64 (3.0-4 to 3.0-4): Will attempt migration (Any information below is purely informational)
• eom/riscv64 (1.26.1-1 to 1.26.1-1)
  • Migration status for eom/riscv64 (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• eos-sdk/riscv64 (0~git20230107+ds-5.1 to 0~git20230107+ds-5.1)
  • Migration status for eos-sdk/riscv64 (0~git20230107+ds-5.1 to 0~git20230107+ds-5.1): Will attempt migration (Any information below is purely informational)
• ephoto/riscv64 (1.6.0-1 to 1.6.0-1)
  • Migration status for ephoto/riscv64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
• epix/riscv64 (1.2.22-2 to 1.2.22-2)
  • Migration status for epix/riscv64 (1.2.22-2 to 1.2.22-2): Will attempt migration (Any information below is purely informational)
• espeakedit/riscv64 (1.48.15-2 to 1.48.15-2)
  • Migration status for espeakedit/riscv64 (1.48.15-2 to 1.48.15-2): Will attempt migration (Any information below is purely informational)
• esys-particle/riscv64 (2.3.5+dfsg2-6 to 2.3.5+dfsg2-6)
  • Migration status for esys-particle/riscv64 (2.3.5+dfsg2-6 to 2.3.5+dfsg2-6): Will attempt migration (Any information below is purely informational)
• etcd/amd64 (3.5.15-7 to 3.5.15-7)
  • Migration status for etcd/amd64 (3.5.15-7 to 3.5.15-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: etcd/amd64 golang-1.23
    • Built-Using: etcd/amd64 golang-github-golang-jwt-jwt
• etcd/arm64 (3.5.15-7 to 3.5.15-7)
  • Migration status for etcd/arm64 (3.5.15-7 to 3.5.15-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: etcd/arm64 golang-1.23
    • Built-Using: etcd/arm64 golang-github-golang-jwt-jwt
• etcd/armel (3.5.15-7 to 3.5.15-7)
  • Migration status for etcd/armel (3.5.15-7 to 3.5.15-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: etcd/armel golang-1.23
    • Built-Using: etcd/armel golang-github-golang-jwt-jwt
• etcd/armhf (3.5.15-7 to 3.5.15-7)
  • Migration status for etcd/armhf (3.5.15-7 to 3.5.15-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: etcd/armhf golang-1.23
    • Built-Using: etcd/armhf golang-github-golang-jwt-jwt
• etcd/i386 (3.5.15-7 to 3.5.15-7)
  • Migration status for etcd/i386 (3.5.15-7 to 3.5.15-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: etcd/i386 golang-1.23
    • Built-Using: etcd/i386 golang-github-golang-jwt-jwt
• etcd/ppc64el (3.5.15-7 to 3.5.15-7)
  • Migration status for etcd/ppc64el (3.5.15-7 to 3.5.15-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: etcd/ppc64el golang-1.23
    • Built-Using: etcd/ppc64el golang-github-golang-jwt-jwt
• etcd/s390x (3.5.15-7 to 3.5.15-7)
  • Migration status for etcd/s390x (3.5.15-7 to 3.5.15-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: etcd/s390x golang-1.23
    • Built-Using: etcd/s390x golang-github-golang-jwt-jwt
• ethflux/amd64 (1.0-5 to 1.0-5)
  • Migration status for ethflux/amd64 (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: ethflux/amd64 golang-1.23
• ethflux/arm64 (1.0-5 to 1.0-5)
  • Migration status for ethflux/arm64 (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: ethflux/arm64 golang-1.23
• ethflux/armel (1.0-5 to 1.0-5)
  • Migration status for ethflux/armel (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: ethflux/armel golang-1.23
• ethflux/armhf (1.0-5 to 1.0-5)
  • Migration status for ethflux/armhf (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: ethflux/armhf golang-1.23
• ethflux/i386 (1.0-5 to 1.0-5)
  • Migration status for ethflux/i386 (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: ethflux/i386 golang-1.23
• ethflux/ppc64el (1.0-5 to 1.0-5)
  • Migration status for ethflux/ppc64el (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: ethflux/ppc64el golang-1.23
• ethflux/s390x (1.0-5 to 1.0-5)
  • Migration status for ethflux/s390x (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: ethflux/s390x golang-1.23
• etoile/riscv64 (0+20080616+dfsg-2.1 to 0+20080616+dfsg-2.1)
  • Migration status for etoile/riscv64 (0+20080616+dfsg-2.1 to 0+20080616+dfsg-2.1): Will attempt migration (Any information below is purely informational)
• etsf-io/riscv64 (1.0.4-5 to 1.0.4-5)
  • Migration status for etsf-io/riscv64 (1.0.4-5 to 1.0.4-5): Will attempt migration (Any information below is purely informational)
• ettercap/riscv64 (1:0.8.3.1-13 to 1:0.8.3.1-13)
  • Migration status for ettercap/riscv64 (1:0.8.3.1-13 to 1:0.8.3.1-13): Will attempt migration (Any information below is purely informational)
• etw/riscv64 (3.6+svn162-6 to 3.6+svn162-6)
  • Migration status for etw/riscv64 (3.6+svn162-6 to 3.6+svn162-6): Will attempt migration (Any information below is purely informational)
• euler/riscv64 (1.61.0-12 to 1.61.0-12)
  • Migration status for euler/riscv64 (1.61.0-12 to 1.61.0-12): Will attempt migration (Any information below is purely informational)
• evolver/riscv64 (2.70+ds-8 to 2.70+ds-8)
  • Migration status for evolver/riscv64 (2.70+ds-8 to 2.70+ds-8): Will attempt migration (Any information below is purely informational)
• evolvotron/riscv64 (0.8.1-1 to 0.8.1-1)
  • Migration status for evolvotron/riscv64 (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• eweouz/riscv64 (0.12 to 0.12)
  • Migration status for eweouz/riscv64 (0.12 to 0.12): Will attempt migration (Any information below is purely informational)
• exadrums/riscv64 (0.7.0-1 to 0.7.0-1)
  • Migration status for exadrums/riscv64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• examl/riscv64 (3.0.22-5 to 3.0.22-5)
  • Migration status for examl/riscv64 (3.0.22-5 to 3.0.22-5): Will attempt migration (Any information below is purely informational)
• exo/riscv64 (4.18.0-1 to 4.18.0-1)
  • Migration status for exo/riscv64 (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• extremetuxracer/riscv64 (0.8.3-1 to 0.8.3-1)
  • Migration status for extremetuxracer/riscv64 (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• ezquake/riscv64 (3.6.4-3 to 3.6.4-3)
  • Migration status for ezquake/riscv64 (3.6.4-3 to 3.6.4-3): Will attempt migration (Any information below is purely informational)
• ezstream/riscv64 (1.0.2-2 to 1.0.2-2)
  • Migration status for ezstream/riscv64 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• eztrace/riscv64 (2.1-7 to 2.1-7)
  • Migration status for eztrace/riscv64 (2.1-7 to 2.1-7): Will attempt migration (Any information below is purely informational)
• facedetect/riscv64 (0.1-3 to 0.1-3)
  • Migration status for facedetect/riscv64 (0.1-3 to 0.1-3): Will attempt migration (Any information below is purely informational)
• farstream-0.2/riscv64 (0.2.9-2 to 0.2.9-2)
  • Migration status for farstream-0.2/riscv64 (0.2.9-2 to 0.2.9-2): Will attempt migration (Any information below is purely informational)
• faustworks/riscv64 (0.5~repack0-6 to 0.5~repack0-6)
  • Migration status for faustworks/riscv64 (0.5~repack0-6 to 0.5~repack0-6): Will attempt migration (Any information below is purely informational)
• fceux/riscv64 (2.6.5+dfsg1-2 to 2.6.5+dfsg1-2)
  • Migration status for fceux/riscv64 (2.6.5+dfsg1-2 to 2.6.5+dfsg1-2): Will attempt migration (Any information below is purely informational)
• fcgiwrap_pu (1.1.0-16 to 1.1.0-14+deb12u1)
  • Migration status for fcgiwrap_pu (1.1.0-16 to 1.1.0-14+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: fcgiwrap is newer in the target suite (1.1.0-16 1.1.0-14+deb12u1)
• fcitx-anthy/riscv64 (0.2.4-1 to 0.2.4-1)
  • Migration status for fcitx-anthy/riscv64 (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• fcitx-autoeng-ng/riscv64 (0.1.1~git20150311-2 to 0.1.1~git20150311-2)
  • Migration status for fcitx-autoeng-ng/riscv64 (0.1.1~git20150311-2 to 0.1.1~git20150311-2): Will attempt migration (Any information below is purely informational)
• fcitx-chewing/riscv64 (0.2.3-2 to 0.2.3-2)
  • Migration status for fcitx-chewing/riscv64 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• fcitx-cloudpinyin/riscv64 (0.3.7-1 to 0.3.7-1)
  • Migration status for fcitx-cloudpinyin/riscv64 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• fcitx-configtool/riscv64 (0.4.10-3 to 0.4.10-3)
  • Migration status for fcitx-configtool/riscv64 (0.4.10-3 to 0.4.10-3): Will attempt migration (Any information below is purely informational)
• fcitx-dbus-status/riscv64 (2016062301-4 to 2016062301-4)
  • Migration status for fcitx-dbus-status/riscv64 (2016062301-4 to 2016062301-4): Will attempt migration (Any information below is purely informational)
• fcitx-fullwidthchar-enhance/riscv64 (0.0~git20150311-3 to 0.0~git20150311-3)
  • Migration status for fcitx-fullwidthchar-enhance/riscv64 (0.0~git20150311-3 to 0.0~git20150311-3): Will attempt migration (Any information below is purely informational)
• fcitx-googlepinyin/riscv64 (0.1.6-5 to 0.1.6-5)
  • Migration status for fcitx-googlepinyin/riscv64 (0.1.6-5 to 0.1.6-5): Will attempt migration (Any information below is purely informational)
• fcitx-imlist/riscv64 (0.5.1-9 to 0.5.1-9)
  • Migration status for fcitx-imlist/riscv64 (0.5.1-9 to 0.5.1-9): Will attempt migration (Any information below is purely informational)
• fcitx-kkc/riscv64 (0.1.4-3 to 0.1.4-3)
  • Migration status for fcitx-kkc/riscv64 (0.1.4-3 to 0.1.4-3): Will attempt migration (Any information below is purely informational)
• fcitx-m17n/riscv64 (0.2.4-3 to 0.2.4-3)
  • Migration status for fcitx-m17n/riscv64 (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
• fcitx-punc-ng/riscv64 (0.1.1~git20161101-2 to 0.1.1~git20161101-2)
  • Migration status for fcitx-punc-ng/riscv64 (0.1.1~git20161101-2 to 0.1.1~git20161101-2): Will attempt migration (Any information below is purely informational)
• fcitx-qimpanel/riscv64 (2.1.3-2 to 2.1.3-2)
  • Migration status for fcitx-qimpanel/riscv64 (2.1.3-2 to 2.1.3-2): Will attempt migration (Any information below is purely informational)
• fcitx-sayura/riscv64 (0.1.2-2 to 0.1.2-2)
  • Migration status for fcitx-sayura/riscv64 (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• fcitx-skk/riscv64 (0.1.4-3 to 0.1.4-3)
  • Migration status for fcitx-skk/riscv64 (0.1.4-3 to 0.1.4-3): Will attempt migration (Any information below is purely informational)
• fcitx-unikey/riscv64 (0.2.7+git20220410-1 to 0.2.7+git20220410-1)
  • Migration status for fcitx-unikey/riscv64 (0.2.7+git20220410-1 to 0.2.7+git20220410-1): Will attempt migration (Any information below is purely informational)
• fcitx/riscv64 (1:4.2.9.9-2 to 1:4.2.9.9-2)
  • Migration status for fcitx/riscv64 (1:4.2.9.9-2 to 1:4.2.9.9-2): Will attempt migration (Any information below is purely informational)
• fcitx5-qt/riscv64 (5.1.6-1 to 5.1.6-1)
  • Migration status for fcitx5-qt/riscv64 (5.1.6-1 to 5.1.6-1): Will attempt migration (Any information below is purely informational)
• fcitx5-tmux/riscv64 (0.0~git20220221.35daf5d-2 to 0.0~git20220221.35daf5d-2)
  • Migration status for fcitx5-tmux/riscv64 (0.0~git20220221.35daf5d-2 to 0.0~git20220221.35daf5d-2): Will attempt migration (Any information below is purely informational)
• fdroidcl/amd64 (0.7.0-1 to 0.7.0-1)
  • Migration status for fdroidcl/amd64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fdroidcl/amd64 golang-1.23
• fdroidcl/arm64 (0.7.0-1 to 0.7.0-1)
  • Migration status for fdroidcl/arm64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fdroidcl/arm64 golang-1.23
• fdroidcl/armel (0.7.0-1 to 0.7.0-1)
  • Migration status for fdroidcl/armel (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fdroidcl/armel golang-1.23
• fdroidcl/armhf (0.7.0-1 to 0.7.0-1)
  • Migration status for fdroidcl/armhf (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fdroidcl/armhf golang-1.23
• fdroidcl/i386 (0.7.0-1 to 0.7.0-1)
  • Migration status for fdroidcl/i386 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fdroidcl/i386 golang-1.23
• fdroidcl/ppc64el (0.7.0-1 to 0.7.0-1)
  • Migration status for fdroidcl/ppc64el (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fdroidcl/ppc64el golang-1.23
• feathernotes/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for feathernotes/riscv64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• featherpad/riscv64 (1.4.1-1 to 1.4.1-1)
  • Migration status for featherpad/riscv64 (1.4.1-1 to 1.4.1-1): Will attempt migration (Any information below is purely informational)
• felix-latin/riscv64 (2.0-14 to 2.0-14)
  • Migration status for felix-latin/riscv64 (2.0-14 to 2.0-14): Will attempt migration (Any information below is purely informational)
• fet/riscv64 (6.8.5-1 to 6.8.5-1)
  • Migration status for fet/riscv64 (6.8.5-1 to 6.8.5-1): Will attempt migration (Any information below is purely informational)
• fever/amd64 (1.3.6-1 to 1.3.6-1)
  • Migration status for fever/amd64 (1.3.6-1 to 1.3.6-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fever/amd64 golang-1.23
• fever/arm64 (1.3.6-1 to 1.3.6-1)
  • Migration status for fever/arm64 (1.3.6-1 to 1.3.6-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fever/arm64 golang-1.23
• fever/armel (1.3.6-1 to 1.3.6-1)
  • Migration status for fever/armel (1.3.6-1 to 1.3.6-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fever/armel golang-1.23
• fever/armhf (1.3.6-1 to 1.3.6-1)
  • Migration status for fever/armhf (1.3.6-1 to 1.3.6-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fever/armhf golang-1.23
• fever/i386 (1.3.6-1 to 1.3.6-1)
  • Migration status for fever/i386 (1.3.6-1 to 1.3.6-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fever/i386 golang-1.23
• fever/ppc64el (1.3.6-1 to 1.3.6-1)
  • Migration status for fever/ppc64el (1.3.6-1 to 1.3.6-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fever/ppc64el golang-1.23
• fever/s390x (1.3.6-1 to 1.3.6-1)
  • Migration status for fever/s390x (1.3.6-1 to 1.3.6-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fever/s390x golang-1.23
• ffcvt/amd64 (1.7.6-2 to 1.7.6-2)
  • Migration status for ffcvt/amd64 (1.7.6-2 to 1.7.6-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffcvt/amd64 golang-1.23
• ffcvt/arm64 (1.7.6-2 to 1.7.6-2)
  • Migration status for ffcvt/arm64 (1.7.6-2 to 1.7.6-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffcvt/arm64 golang-1.23
• ffcvt/armel (1.7.6-2 to 1.7.6-2)
  • Migration status for ffcvt/armel (1.7.6-2 to 1.7.6-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffcvt/armel golang-1.23
• ffcvt/armhf (1.7.6-2 to 1.7.6-2)
  • Migration status for ffcvt/armhf (1.7.6-2 to 1.7.6-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffcvt/armhf golang-1.23
• ffcvt/i386 (1.7.6-2 to 1.7.6-2)
  • Migration status for ffcvt/i386 (1.7.6-2 to 1.7.6-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffcvt/i386 golang-1.23
• ffcvt/ppc64el (1.7.6-2 to 1.7.6-2)
  • Migration status for ffcvt/ppc64el (1.7.6-2 to 1.7.6-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffcvt/ppc64el golang-1.23
• ffcvt/s390x (1.7.6-2 to 1.7.6-2)
  • Migration status for ffcvt/s390x (1.7.6-2 to 1.7.6-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffcvt/s390x golang-1.23
• ffindex/riscv64 (0.9.9.9-6.1 to 0.9.9.9-6.1)
  • Migration status for ffindex/riscv64 (0.9.9.9-6.1 to 0.9.9.9-6.1): Will attempt migration (Any information below is purely informational)
• ffmpegthumbnailer/riscv64 (2.2.2+git20240104+dfsg-1 to 2.2.2+git20240104+dfsg-1)
  • Migration status for ffmpegthumbnailer/riscv64 (2.2.2+git20240104+dfsg-1 to 2.2.2+git20240104+dfsg-1): Will attempt migration (Any information below is purely informational)
• ffmpegthumbs/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for ffmpegthumbs/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• ffuf/amd64 (2.1.0-1 to 2.1.0-1)
  • Migration status for ffuf/amd64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffuf/amd64 golang-1.23
• ffuf/arm64 (2.1.0-1 to 2.1.0-1)
  • Migration status for ffuf/arm64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffuf/arm64 golang-1.23
• ffuf/armel (2.1.0-1 to 2.1.0-1)
  • Migration status for ffuf/armel (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffuf/armel golang-1.23
• ffuf/armhf (2.1.0-1 to 2.1.0-1)
  • Migration status for ffuf/armhf (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffuf/armhf golang-1.23
• ffuf/i386 (2.1.0-1 to 2.1.0-1)
  • Migration status for ffuf/i386 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffuf/i386 golang-1.23
• ffuf/ppc64el (2.1.0-1 to 2.1.0-1)
  • Migration status for ffuf/ppc64el (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffuf/ppc64el golang-1.23
• ffuf/s390x (2.1.0-1 to 2.1.0-1)
  • Migration status for ffuf/s390x (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ffuf/s390x golang-1.23
• fiat-ecmwf/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for fiat-ecmwf/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• fifechan/riscv64 (0.1.5-3.1 to 0.1.5-3.1)
  • Migration status for fifechan/riscv64 (0.1.5-3.1 to 0.1.5-3.1): Will attempt migration (Any information below is purely informational)
• fig2dev/riscv64 (1:3.2.9-4 to 1:3.2.9-4)
  • Migration status for fig2dev/riscv64 (1:3.2.9-4 to 1:3.2.9-4): Will attempt migration (Any information below is purely informational)
• filelight/riscv64 (4:23.08.5-1 to 4:23.08.5-1)
  • Migration status for filelight/riscv64 (4:23.08.5-1 to 4:23.08.5-1): Will attempt migration (Any information below is purely informational)
• fillets-ng/riscv64 (1.0.1-4 to 1.0.1-4)
  • Migration status for fillets-ng/riscv64 (1.0.1-4 to 1.0.1-4): Will attempt migration (Any information below is purely informational)
• findimagedupes/riscv64 (2.20.1-3 to 2.20.1-3)
  • Migration status for findimagedupes/riscv64 (2.20.1-3 to 2.20.1-3): Will attempt migration (Any information below is purely informational)
• fio/riscv64 (3.37-1 to 3.37-1)
  • Migration status for fio/riscv64 (3.37-1 to 3.37-1): Will attempt migration (Any information below is purely informational)
• firefox-esr_pu (115.15.0esr-1 to 115.15.0esr-1~deb12u1)
  • Migration status for firefox-esr_pu (115.15.0esr-1 to 115.15.0esr-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: firefox-esr is newer in the target suite (115.15.0esr-1 115.15.0esr-1~deb12u1)
• fityk/riscv64 (1.3.2-3 to 1.3.2-3)
  • Migration status for fityk/riscv64 (1.3.2-3 to 1.3.2-3): Will attempt migration (Any information below is purely informational)
• five-or-more/riscv64 (1:3.32.3-1 to 1:3.32.3-1)
  • Migration status for five-or-more/riscv64 (1:3.32.3-1 to 1:3.32.3-1): Will attempt migration (Any information below is purely informational)
• fizmo-console/riscv64 (0.7.13-2 to 0.7.13-2)
  • Migration status for fizmo-console/riscv64 (0.7.13-2 to 0.7.13-2): Will attempt migration (Any information below is purely informational)
• fizmo-ncursesw/riscv64 (0.7.14-2 to 0.7.14-2)
  • Migration status for fizmo-ncursesw/riscv64 (0.7.14-2 to 0.7.14-2): Will attempt migration (Any information below is purely informational)
• fizmo-sdl2/riscv64 (0.8.5-2 to 0.8.5-2)
  • Migration status for fizmo-sdl2/riscv64 (0.8.5-2 to 0.8.5-2): Will attempt migration (Any information below is purely informational)
• flactag/riscv64 (2.0.4-6 to 2.0.4-6)
  • Migration status for flactag/riscv64 (2.0.4-6 to 2.0.4-6): Will attempt migration (Any information below is purely informational)
• flam3/riscv64 (3.1.1+ds2-2 to 3.1.1+ds2-2)
  • Migration status for flam3/riscv64 (3.1.1+ds2-2 to 3.1.1+ds2-2): Will attempt migration (Any information below is purely informational)
• flamerobin/riscv64 (0.9.10.ds.2-1 to 0.9.10.ds.2-1)
  • Migration status for flamerobin/riscv64 (0.9.10.ds.2-1 to 0.9.10.ds.2-1): Will attempt migration (Any information below is purely informational)
• flameshot/riscv64 (12.1.0-3 to 12.1.0-3)
  • Migration status for flameshot/riscv64 (12.1.0-3 to 12.1.0-3): Will attempt migration (Any information below is purely informational)
• flann/riscv64 (1.9.2+dfsg-2 to 1.9.2+dfsg-2)
  • Migration status for flann/riscv64 (1.9.2+dfsg-2 to 1.9.2+dfsg-2): Will attempt migration (Any information below is purely informational)
• flightcrew/riscv64 (0.9.3+dfsg-2.1 to 0.9.3+dfsg-2.1)
  • Migration status for flightcrew/riscv64 (0.9.3+dfsg-2.1 to 0.9.3+dfsg-2.1): Will attempt migration (Any information below is purely informational)
• flightgear/riscv64 (1:2020.3.18+dfsg-1.1 to 1:2020.3.18+dfsg-1.1)
  • Migration status for flightgear/riscv64 (1:2020.3.18+dfsg-1.1 to 1:2020.3.18+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• fluxbox/riscv64 (1.3.7-1 to 1.3.7-1)
  • Migration status for fluxbox/riscv64 (1.3.7-1 to 1.3.7-1): Will attempt migration (Any information below is purely informational)
• fmit/riscv64 (1.2.14-0.1 to 1.2.14-0.1)
  • Migration status for fmit/riscv64 (1.2.14-0.1 to 1.2.14-0.1): Will attempt migration (Any information below is purely informational)
• fonttools/riscv64 (4.46.0-1 to 4.46.0-1)
  • Migration status for fonttools/riscv64 (4.46.0-1 to 4.46.0-1): Will attempt migration (Any information below is purely informational)
• foobillardplus/riscv64 (3.43~svn170+dfsg-7 to 3.43~svn170+dfsg-7)
  • Migration status for foobillardplus/riscv64 (3.43~svn170+dfsg-7 to 3.43~svn170+dfsg-7): Will attempt migration (Any information below is purely informational)
• fookb/riscv64 (4.1-3 to 4.1-3)
  • Migration status for fookb/riscv64 (4.1-3 to 4.1-3): Will attempt migration (Any information below is purely informational)
• foomatic-db-engine/riscv64 (4.0.13-6 to 4.0.13-6)
  • Migration status for foomatic-db-engine/riscv64 (4.0.13-6 to 4.0.13-6): Will attempt migration (Any information below is purely informational)
• forge/riscv64 (1.0.1-3.1 to 1.0.1-3.1)
  • Migration status for forge/riscv64 (1.0.1-3.1 to 1.0.1-3.1): Will attempt migration (Any information below is purely informational)
• fotoxx/riscv64 (20.08-2 to 20.08-2)
  • Migration status for fotoxx/riscv64 (20.08-2 to 20.08-2): Will attempt migration (Any information below is purely informational)
• four-in-a-row/riscv64 (1:3.38.1-1 to 1:3.38.1-1)
  • Migration status for four-in-a-row/riscv64 (1:3.38.1-1 to 1:3.38.1-1): Will attempt migration (Any information below is purely informational)
• fox1.6/riscv64 (1.6.57-1 to 1.6.57-1)
  • Migration status for fox1.6/riscv64 (1.6.57-1 to 1.6.57-1): Will attempt migration (Any information below is purely informational)
• fqterm/riscv64 (0.9.10.1-4 to 0.9.10.1-4)
  • Migration status for fqterm/riscv64 (0.9.10.1-4 to 0.9.10.1-4): Will attempt migration (Any information below is purely informational)
• fracplanet/riscv64 (0.5.1-6 to 0.5.1-6)
  • Migration status for fracplanet/riscv64 (0.5.1-6 to 0.5.1-6): Will attempt migration (Any information below is purely informational)
• fractalnow/riscv64 (0.8.2-5 to 0.8.2-5)
  • Migration status for fractalnow/riscv64 (0.8.2-5 to 0.8.2-5): Will attempt migration (Any information below is purely informational)
• fractgen/riscv64 (2.1.13-1 to 2.1.13-1)
  • Migration status for fractgen/riscv64 (2.1.13-1 to 2.1.13-1): Will attempt migration (Any information below is purely informational)
• fraqtive/riscv64 (0.4.8.1-1 to 0.4.8.1-1)
  • Migration status for fraqtive/riscv64 (0.4.8.1-1 to 0.4.8.1-1): Will attempt migration (Any information below is purely informational)
• free42-nologo/riscv64 (3.1.8+ds-1 to 3.1.8+ds-1)
  • Migration status for free42-nologo/riscv64 (3.1.8+ds-1 to 3.1.8+ds-1): Will attempt migration (Any information below is purely informational)
• freedv/riscv64 (1.8.11-1 to 1.8.11-1)
  • Migration status for freedv/riscv64 (1.8.11-1 to 1.8.11-1): Will attempt migration (Any information below is purely informational)
• freefem++/riscv64 (4.14+dfsg-1 to 4.14+dfsg-1)
  • Migration status for freefem++/riscv64 (4.14+dfsg-1 to 4.14+dfsg-1): Will attempt migration (Any information below is purely informational)
• freegish/riscv64 (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2)
  • Migration status for freegish/riscv64 (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2): Will attempt migration (Any information below is purely informational)
• freeglut/riscv64 (3.4.0-1 to 3.4.0-1)
  • Migration status for freeglut/riscv64 (3.4.0-1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
• freesasa/riscv64 (2.1.2-4 to 2.1.2-4)
  • Migration status for freesasa/riscv64 (2.1.2-4 to 2.1.2-4): Will attempt migration (Any information below is purely informational)
• freespace2-launcher-wxlauncher/riscv64 (0.12.0~rc3+dfsg-1 to 0.12.0~rc3+dfsg-1)
  • Migration status for freespace2-launcher-wxlauncher/riscv64 (0.12.0~rc3+dfsg-1 to 0.12.0~rc3+dfsg-1): Will attempt migration (Any information below is purely informational)
• freetuxtv/riscv64 (0.6.8~dfsg1-2 to 0.6.8~dfsg1-2)
  • Migration status for freetuxtv/riscv64 (0.6.8~dfsg1-2 to 0.6.8~dfsg1-2): Will attempt migration (Any information below is purely informational)
• freewheeling/riscv64 (0.6.6-1 to 0.6.6-1)
  • Migration status for freewheeling/riscv64 (0.6.6-1 to 0.6.6-1): Will attempt migration (Any information below is purely informational)
• frei0r/riscv64 (1.8.0-1 to 1.8.0-1)
  • Migration status for frei0r/riscv64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• frescobaldi/riscv64 (3.3.0+ds1-2 to 3.3.0+ds1-2)
  • Migration status for frescobaldi/riscv64 (3.3.0+ds1-2 to 3.3.0+ds1-2): Will attempt migration (Any information below is purely informational)
• fritzing/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for fritzing/riscv64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• frogatto/riscv64 (1.3.1+dfsg-6 to 1.3.1+dfsg-6)
  • Migration status for frogatto/riscv64 (1.3.1+dfsg-6 to 1.3.1+dfsg-6): Will attempt migration (Any information below is purely informational)
• frogr/riscv64 (1.8.1-1 to 1.8.1-1)
  • Migration status for frogr/riscv64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• fscrypt/amd64 (0.3.4-2 to 0.3.4-2)
  • Migration status for fscrypt/amd64 (0.3.4-2 to 0.3.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: fscrypt/amd64 golang-1.23
• fscrypt/arm64 (0.3.4-2 to 0.3.4-2)
  • Migration status for fscrypt/arm64 (0.3.4-2 to 0.3.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: fscrypt/arm64 golang-1.23
• fscrypt/armel (0.3.4-2 to 0.3.4-2)
  • Migration status for fscrypt/armel (0.3.4-2 to 0.3.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: fscrypt/armel golang-1.23
• fscrypt/armhf (0.3.4-2 to 0.3.4-2)
  • Migration status for fscrypt/armhf (0.3.4-2 to 0.3.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: fscrypt/armhf golang-1.23
• fscrypt/i386 (0.3.4-2 to 0.3.4-2)
  • Migration status for fscrypt/i386 (0.3.4-2 to 0.3.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: fscrypt/i386 golang-1.23
• fscrypt/ppc64el (0.3.4-2 to 0.3.4-2)
  • Migration status for fscrypt/ppc64el (0.3.4-2 to 0.3.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: fscrypt/ppc64el golang-1.23
• fscrypt/s390x (0.3.4-2 to 0.3.4-2)
  • Migration status for fscrypt/s390x (0.3.4-2 to 0.3.4-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: fscrypt/s390x golang-1.23
• fstl/riscv64 (0.10.0-2 to 0.10.0-2)
  • Migration status for fstl/riscv64 (0.10.0-2 to 0.10.0-2): Will attempt migration (Any information below is purely informational)
• ftgl/riscv64 (2.4.0-3 to 2.4.0-3)
  • Migration status for ftgl/riscv64 (2.4.0-3 to 2.4.0-3): Will attempt migration (Any information below is purely informational)
• ftp.app/riscv64 (0.6-2 to 0.6-2)
  • Migration status for ftp.app/riscv64 (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
• fuse-emulator/riscv64 (1.6.0+dfsg1-2 to 1.6.0+dfsg1-2)
  • Migration status for fuse-emulator/riscv64 (1.6.0+dfsg1-2 to 1.6.0+dfsg1-2): Will attempt migration (Any information below is purely informational)
• fwbuilder/riscv64 (5.3.7-8 to 5.3.7-8)
  • Migration status for fwbuilder/riscv64 (5.3.7-8 to 5.3.7-8): Will attempt migration (Any information below is purely informational)
• fzf/amd64 (0.46.1-1 to 0.46.1-1)
  • Migration status for fzf/amd64 (0.46.1-1 to 0.46.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fzf/amd64 golang-1.23
• fzf/arm64 (0.46.1-1 to 0.46.1-1)
  • Migration status for fzf/arm64 (0.46.1-1 to 0.46.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fzf/arm64 golang-1.23
• fzf/armel (0.46.1-1 to 0.46.1-1)
  • Migration status for fzf/armel (0.46.1-1 to 0.46.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fzf/armel golang-1.23
• fzf/armhf (0.46.1-1 to 0.46.1-1)
  • Migration status for fzf/armhf (0.46.1-1 to 0.46.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fzf/armhf golang-1.23
• fzf/i386 (0.46.1-1 to 0.46.1-1)
  • Migration status for fzf/i386 (0.46.1-1 to 0.46.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fzf/i386 golang-1.23
• fzf/ppc64el (0.46.1-1 to 0.46.1-1)
  • Migration status for fzf/ppc64el (0.46.1-1 to 0.46.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fzf/ppc64el golang-1.23
• fzf/s390x (0.46.1-1 to 0.46.1-1)
  • Migration status for fzf/s390x (0.46.1-1 to 0.46.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: fzf/s390x golang-1.23
• g10k/amd64 (0.9.9-1 to 0.9.9-1)
  • Migration status for g10k/amd64 (0.9.9-1 to 0.9.9-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: g10k/amd64 golang-1.23
• g10k/arm64 (0.9.9-1 to 0.9.9-1)
  • Migration status for g10k/arm64 (0.9.9-1 to 0.9.9-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: g10k/arm64 golang-1.23
• g10k/armel (0.9.9-1 to 0.9.9-1)
  • Migration status for g10k/armel (0.9.9-1 to 0.9.9-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: g10k/armel golang-1.23
• g10k/armhf (0.9.9-1 to 0.9.9-1)
  • Migration status for g10k/armhf (0.9.9-1 to 0.9.9-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: g10k/armhf golang-1.23
• g10k/i386 (0.9.9-1 to 0.9.9-1)
  • Migration status for g10k/i386 (0.9.9-1 to 0.9.9-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: g10k/i386 golang-1.23
• g10k/ppc64el (0.9.9-1 to 0.9.9-1)
  • Migration status for g10k/ppc64el (0.9.9-1 to 0.9.9-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: g10k/ppc64el golang-1.23
• g10k/s390x (0.9.9-1 to 0.9.9-1)
  • Migration status for g10k/s390x (0.9.9-1 to 0.9.9-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: g10k/s390x golang-1.23
• galculator/riscv64 (2.1.4-1.2 to 2.1.4-1.2)
  • Migration status for galculator/riscv64 (2.1.4-1.2 to 2.1.4-1.2): Will attempt migration (Any information below is purely informational)
• galois/riscv64 (0.8-1 to 0.8-1)
  • Migration status for galois/riscv64 (0.8-1 to 0.8-1): Will attempt migration (Any information below is purely informational)
• gamine/riscv64 (1.6-1 to 1.6-1)
  • Migration status for gamine/riscv64 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
• garagemq/amd64 (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5)
  • Migration status for garagemq/amd64 (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: garagemq/amd64 golang-1.23
• garagemq/arm64 (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5)
  • Migration status for garagemq/arm64 (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: garagemq/arm64 golang-1.23
• garagemq/armel (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5)
  • Migration status for garagemq/armel (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: garagemq/armel golang-1.23
• garagemq/armhf (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5)
  • Migration status for garagemq/armhf (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: garagemq/armhf golang-1.23
• garagemq/i386 (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5)
  • Migration status for garagemq/i386 (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: garagemq/i386 golang-1.23
• garagemq/ppc64el (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5)
  • Migration status for garagemq/ppc64el (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: garagemq/ppc64el golang-1.23
• garagemq/s390x (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5)
  • Migration status for garagemq/s390x (0.0~git20200204.15e6a9d+ds-5 to 0.0~git20200204.15e6a9d+ds-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: garagemq/s390x golang-1.23
• garcon/riscv64 (4.18.1-1 to 4.18.1-1)
  • Migration status for garcon/riscv64 (4.18.1-1 to 4.18.1-1): Will attempt migration (Any information below is purely informational)
• gargoyle-free/riscv64 (2023.1+dfsg-4 to 2023.1+dfsg-4)
  • Migration status for gargoyle-free/riscv64 (2023.1+dfsg-4 to 2023.1+dfsg-4): Will attempt migration (Any information below is purely informational)
• gavl/riscv64 (2.0.0~svn6298-1 to 2.0.0~svn6298-1)
  • Migration status for gavl/riscv64 (2.0.0~svn6298-1 to 2.0.0~svn6298-1): Will attempt migration (Any information below is purely informational)
• gbdfed/riscv64 (1.6-4 to 1.6-4)
  • Migration status for gbdfed/riscv64 (1.6-4 to 1.6-4): Will attempt migration (Any information below is purely informational)
• gbemol/riscv64 (0.3.2-2 to 0.3.2-2)
  • Migration status for gbemol/riscv64 (0.3.2-2 to 0.3.2-2): Will attempt migration (Any information below is purely informational)
• gbgoffice/riscv64 (1.4-12 to 1.4-12)
  • Migration status for gbgoffice/riscv64 (1.4-12 to 1.4-12): Will attempt migration (Any information below is purely informational)
• gbonds/riscv64 (2.0.3-17 to 2.0.3-17)
  • Migration status for gbonds/riscv64 (2.0.3-17 to 2.0.3-17): Will attempt migration (Any information below is purely informational)
• gbrowse/riscv64 (2.56+dfsg-12 to 2.56+dfsg-12)
  • Migration status for gbrowse/riscv64 (2.56+dfsg-12 to 2.56+dfsg-12): Will attempt migration (Any information below is purely informational)
• gcolor3/riscv64 (2.4.0-2 to 2.4.0-2)
  • Migration status for gcolor3/riscv64 (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
• gconjugue/riscv64 (0.8.5-2 to 0.8.5-2)
  • Migration status for gconjugue/riscv64 (0.8.5-2 to 0.8.5-2): Will attempt migration (Any information below is purely informational)
• gcr/riscv64 (3.41.2-1 to 3.41.2-1)
  • Migration status for gcr/riscv64 (3.41.2-1 to 3.41.2-1): Will attempt migration (Any information below is purely informational)
• gdigi/riscv64 (0.4.0+git20200615+1c2c89f-3 to 0.4.0+git20200615+1c2c89f-3)
  • Migration status for gdigi/riscv64 (0.4.0+git20200615+1c2c89f-3 to 0.4.0+git20200615+1c2c89f-3): Will attempt migration (Any information below is purely informational)
• gdk-pixbuf-xlib/riscv64 (2.40.2-3 to 2.40.2-3)
  • Migration status for gdk-pixbuf-xlib/riscv64 (2.40.2-3 to 2.40.2-3): Will attempt migration (Any information below is purely informational)
• gdl/riscv64 (3.40.0-2 to 3.40.0-2)
  • Migration status for gdl/riscv64 (3.40.0-2 to 3.40.0-2): Will attempt migration (Any information below is purely informational)
• gdmap/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for gdmap/riscv64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• gdome2/riscv64 (0.8.1+debian-9 to 0.8.1+debian-9)
  • Migration status for gdome2/riscv64 (0.8.1+debian-9 to 0.8.1+debian-9): Will attempt migration (Any information below is purely informational)
• gdpc/riscv64 (2.2.5-16 to 2.2.5-16)
  • Migration status for gdpc/riscv64 (2.2.5-16 to 2.2.5-16): Will attempt migration (Any information below is purely informational)
• gdu/amd64 (5.25.0-1 to 5.25.0-1)
  • Migration status for gdu/amd64 (5.25.0-1 to 5.25.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gdu/amd64 golang-1.23
• gdu/arm64 (5.25.0-1 to 5.25.0-1)
  • Migration status for gdu/arm64 (5.25.0-1 to 5.25.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gdu/arm64 golang-1.23
• gdu/armel (5.25.0-1 to 5.25.0-1)
  • Migration status for gdu/armel (5.25.0-1 to 5.25.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gdu/armel golang-1.23
• gdu/armhf (5.25.0-1 to 5.25.0-1)
  • Migration status for gdu/armhf (5.25.0-1 to 5.25.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gdu/armhf golang-1.23
• gdu/i386 (5.25.0-1 to 5.25.0-1)
  • Migration status for gdu/i386 (5.25.0-1 to 5.25.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gdu/i386 golang-1.23
• gdu/ppc64el (5.25.0-1 to 5.25.0-1)
  • Migration status for gdu/ppc64el (5.25.0-1 to 5.25.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gdu/ppc64el golang-1.23
• gdu/s390x (5.25.0-1 to 5.25.0-1)
  • Migration status for gdu/s390x (5.25.0-1 to 5.25.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gdu/s390x golang-1.23
• gedit-plugins/riscv64 (46.0-2 to 46.0-2)
  • Migration status for gedit-plugins/riscv64 (46.0-2 to 46.0-2): Will attempt migration (Any information below is purely informational)
• gedit/riscv64 (46.2-3 to 46.2-3)
  • Migration status for gedit/riscv64 (46.2-3 to 46.2-3): Will attempt migration (Any information below is purely informational)
• geeqie/amd64 (1:2.4-2 to 1:2.4-2)
  • Migration status for geeqie/amd64 (1:2.4-2 to 1:2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: geeqie/amd64 exiv2
• geeqie/arm64 (1:2.4-2 to 1:2.4-2)
  • Migration status for geeqie/arm64 (1:2.4-2 to 1:2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: geeqie/arm64 exiv2
• geeqie/armel (1:2.4-2 to 1:2.4-2)
  • Migration status for geeqie/armel (1:2.4-2 to 1:2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: geeqie/armel exiv2
• geeqie/armhf (1:2.4-2 to 1:2.4-2)
  • Migration status for geeqie/armhf (1:2.4-2 to 1:2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: geeqie/armhf exiv2
• geeqie/i386 (1:2.4-2 to 1:2.4-2)
  • Migration status for geeqie/i386 (1:2.4-2 to 1:2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: geeqie/i386 exiv2
• geeqie/mips64el (1:2.4-2 to 1:2.4-2)
  • Migration status for geeqie/mips64el (1:2.4-2 to 1:2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: geeqie/mips64el exiv2
• geeqie/ppc64el (1:2.4-2 to 1:2.4-2)
  • Migration status for geeqie/ppc64el (1:2.4-2 to 1:2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: geeqie/ppc64el exiv2
• geeqie/riscv64 (1:2.4-2 to 1:2.4-2)
  • Migration status for geeqie/riscv64 (1:2.4-2 to 1:2.4-2): Will attempt migration (Any information below is purely informational)
• geeqie/s390x (1:2.4-2 to 1:2.4-2)
  • Migration status for geeqie/s390x (1:2.4-2 to 1:2.4-2): Will attempt migration (Any information below is purely informational)
    • Depends: geeqie/s390x exiv2
• geg/riscv64 (2.0.9-4 to 2.0.9-4)
  • Migration status for geg/riscv64 (2.0.9-4 to 2.0.9-4): Will attempt migration (Any information below is purely informational)
• gegl/riscv64 (1:0.4.48-2.5 to 1:0.4.48-2.5)
  • Migration status for gegl/riscv64 (1:0.4.48-2.5 to 1:0.4.48-2.5): Will attempt migration (Any information below is purely informational)
• gelemental/riscv64 (2.0.2-1.1 to 2.0.2-1.1)
  • Migration status for gelemental/riscv64 (2.0.2-1.1 to 2.0.2-1.1): Will attempt migration (Any information below is purely informational)
• gem/riscv64 (1:0.94-8 to 1:0.94-8)
  • Migration status for gem/riscv64 (1:0.94-8 to 1:0.94-8): Will attempt migration (Any information below is purely informational)
• genesisplusgx/riscv64 (1.7.4+git20221128-1 to 1.7.4+git20221128-1)
  • Migration status for genesisplusgx/riscv64 (1.7.4+git20221128-1 to 1.7.4+git20221128-1): Will attempt migration (Any information below is purely informational)
• genext2fs/riscv64 (1.5.0-3 to 1.5.0-3)
  • Migration status for genext2fs/riscv64 (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
• genius/riscv64 (1.0.27-1 to 1.0.27-1)
  • Migration status for genius/riscv64 (1.0.27-1 to 1.0.27-1): Will attempt migration (Any information below is purely informational)
• gentle/riscv64 (1.9.5~alpha1+dfsg-1 to 1.9.5~alpha1+dfsg-1)
  • Migration status for gentle/riscv64 (1.9.5~alpha1+dfsg-1 to 1.9.5~alpha1+dfsg-1): Will attempt migration (Any information below is purely informational)
• gentoo/riscv64 (0.20.7-3 to 0.20.7-3)
  • Migration status for gentoo/riscv64 (0.20.7-3 to 0.20.7-3): Will attempt migration (Any information below is purely informational)
• geoclue-2.0/riscv64 (2.7.1-2 to 2.7.1-2)
  • Migration status for geoclue-2.0/riscv64 (2.7.1-2 to 2.7.1-2): Will attempt migration (Any information below is purely informational)
• geomview/riscv64 (1.9.5-4.1 to 1.9.5-4.1)
  • Migration status for geomview/riscv64 (1.9.5-4.1 to 1.9.5-4.1): Will attempt migration (Any information below is purely informational)
• gerbera/amd64 (2.2.0+dfsg-1 to 2.2.0+dfsg-1)
  • Migration status for gerbera/amd64 (2.2.0+dfsg-1 to 2.2.0+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gerbera/amd64 exiv2
• gerbera/arm64 (2.2.0+dfsg-1 to 2.2.0+dfsg-1)
  • Migration status for gerbera/arm64 (2.2.0+dfsg-1 to 2.2.0+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gerbera/arm64 exiv2
• gerbera/armel (2.2.0+dfsg-1 to 2.2.0+dfsg-1)
  • Migration status for gerbera/armel (2.2.0+dfsg-1 to 2.2.0+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gerbera/armel exiv2
• gerbera/armhf (2.2.0+dfsg-1 to 2.2.0+dfsg-1)
  • Migration status for gerbera/armhf (2.2.0+dfsg-1 to 2.2.0+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gerbera/armhf exiv2
• gerbera/i386 (2.2.0+dfsg-1 to 2.2.0+dfsg-1)
  • Migration status for gerbera/i386 (2.2.0+dfsg-1 to 2.2.0+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gerbera/i386 exiv2
• gerbera/mips64el (2.2.0+dfsg-1 to 2.2.0+dfsg-1)
  • Migration status for gerbera/mips64el (2.2.0+dfsg-1 to 2.2.0+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gerbera/mips64el exiv2
• gerbera/ppc64el (2.2.0+dfsg-1 to 2.2.0+dfsg-1)
  • Migration status for gerbera/ppc64el (2.2.0+dfsg-1 to 2.2.0+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gerbera/ppc64el exiv2
• gerbera/s390x (2.2.0+dfsg-1 to 2.2.0+dfsg-1)
  • Migration status for gerbera/s390x (2.2.0+dfsg-1 to 2.2.0+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: gerbera/s390x exiv2
• gerbv/riscv64 (2.10.0-1 to 2.10.0-1)
  • Migration status for gerbv/riscv64 (2.10.0-1 to 2.10.0-1): Will attempt migration (Any information below is purely informational)
• getdns/amd64 (1.6.0-3.1 to 1.6.0-3.1)
  • Migration status for getdns/amd64 (1.6.0-3.1 to 1.6.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• getdns/arm64 (1.6.0-3.1 to 1.6.0-3.1)
  • Migration status for getdns/arm64 (1.6.0-3.1 to 1.6.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• getdns/armel (1.6.0-3.1 to 1.6.0-3.1)
  • Migration status for getdns/armel (1.6.0-3.1 to 1.6.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• getdns/armhf (1.6.0-3.1 to 1.6.0-3.1)
  • Migration status for getdns/armhf (1.6.0-3.1 to 1.6.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• getdns/i386 (1.6.0-3.1 to 1.6.0-3.1)
  • Migration status for getdns/i386 (1.6.0-3.1 to 1.6.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• getdns/mips64el (1.6.0-3.1 to 1.6.0-3.1)
  • Migration status for getdns/mips64el (1.6.0-3.1 to 1.6.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• getdns/ppc64el (1.6.0-3.1 to 1.6.0-3.1)
  • Migration status for getdns/ppc64el (1.6.0-3.1 to 1.6.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• getdns/riscv64 (1.6.0-3.1 to 1.6.0-3.1)
  • Migration status for getdns/riscv64 (1.6.0-3.1 to 1.6.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• getdns/s390x (1.6.0-3.1 to 1.6.0-3.1)
  • Migration status for getdns/s390x (1.6.0-3.1 to 1.6.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gexec/riscv64 (0.4-3 to 0.4-3)
  • Migration status for gexec/riscv64 (0.4-3 to 0.4-3): Will attempt migration (Any information below is purely informational)
• gexiv2/amd64 (0.14.3-1 to 0.14.3-1)
  • Migration status for gexiv2/amd64 (0.14.3-1 to 0.14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gexiv2/amd64 exiv2
• gexiv2/arm64 (0.14.3-1 to 0.14.3-1)
  • Migration status for gexiv2/arm64 (0.14.3-1 to 0.14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gexiv2/arm64 exiv2
• gexiv2/armel (0.14.3-1 to 0.14.3-1)
  • Migration status for gexiv2/armel (0.14.3-1 to 0.14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gexiv2/armel exiv2
• gexiv2/armhf (0.14.3-1 to 0.14.3-1)
  • Migration status for gexiv2/armhf (0.14.3-1 to 0.14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gexiv2/armhf exiv2
• gexiv2/i386 (0.14.3-1 to 0.14.3-1)
  • Migration status for gexiv2/i386 (0.14.3-1 to 0.14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gexiv2/i386 exiv2
• gexiv2/mips64el (0.14.3-1 to 0.14.3-1)
  • Migration status for gexiv2/mips64el (0.14.3-1 to 0.14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gexiv2/mips64el exiv2
• gexiv2/ppc64el (0.14.3-1 to 0.14.3-1)
  • Migration status for gexiv2/ppc64el (0.14.3-1 to 0.14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gexiv2/ppc64el exiv2
• gexiv2/riscv64 (0.14.3-1 to 0.14.3-1)
  • Migration status for gexiv2/riscv64 (0.14.3-1 to 0.14.3-1): Will attempt migration (Any information below is purely informational)
• gexiv2/s390x (0.14.3-1 to 0.14.3-1)
  • Migration status for gexiv2/s390x (0.14.3-1 to 0.14.3-1): Will attempt migration (Any information below is purely informational)
    • Depends: gexiv2/s390x exiv2
• ggd-utils/amd64 (1.0.0+ds-1 to 1.0.0+ds-1)
  • Migration status for ggd-utils/amd64 (1.0.0+ds-1 to 1.0.0+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ggd-utils/amd64 golang-1.23
• ggd-utils/arm64 (1.0.0+ds-1 to 1.0.0+ds-1)
  • Migration status for ggd-utils/arm64 (1.0.0+ds-1 to 1.0.0+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ggd-utils/arm64 golang-1.23
• ggd-utils/armel (1.0.0+ds-1 to 1.0.0+ds-1)
  • Migration status for ggd-utils/armel (1.0.0+ds-1 to 1.0.0+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ggd-utils/armel golang-1.23
• ggd-utils/armhf (1.0.0+ds-1 to 1.0.0+ds-1)
  • Migration status for ggd-utils/armhf (1.0.0+ds-1 to 1.0.0+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ggd-utils/armhf golang-1.23
• ggd-utils/i386 (1.0.0+ds-1 to 1.0.0+ds-1)
  • Migration status for ggd-utils/i386 (1.0.0+ds-1 to 1.0.0+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ggd-utils/i386 golang-1.23
• ggd-utils/ppc64el (1.0.0+ds-1 to 1.0.0+ds-1)
  • Migration status for ggd-utils/ppc64el (1.0.0+ds-1 to 1.0.0+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ggd-utils/ppc64el golang-1.23
• ggd-utils/s390x (1.0.0+ds-1 to 1.0.0+ds-1)
  • Migration status for ggd-utils/s390x (1.0.0+ds-1 to 1.0.0+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: ggd-utils/s390x golang-1.23
• ghex/riscv64 (46.0-1 to 46.0-1)
  • Migration status for ghex/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• ghostscript_pu (10.03.1~dfsg-2 to 10.0.0~dfsg-11+deb12u5)
  • Migration status for ghostscript_pu (10.03.1~dfsg-2 to 10.0.0~dfsg-11+deb12u5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ghostscript is newer in the target suite (10.03.1~dfsg-2 10.0.0~dfsg-11+deb12u5)
• giac/riscv64 (1.9.0.93+dfsg2-2 to 1.9.0.93+dfsg2-2)
  • Migration status for giac/riscv64 (1.9.0.93+dfsg2-2 to 1.9.0.93+dfsg2-2): Will attempt migration (Any information below is purely informational)
• gifwrap/amd64 (0.0.7-1 to 0.0.7-1)
  • Migration status for gifwrap/amd64 (0.0.7-1 to 0.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gifwrap/amd64 golang-1.23
• gifwrap/arm64 (0.0.7-1 to 0.0.7-1)
  • Migration status for gifwrap/arm64 (0.0.7-1 to 0.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gifwrap/arm64 golang-1.23
• gifwrap/armel (0.0.7-1 to 0.0.7-1)
  • Migration status for gifwrap/armel (0.0.7-1 to 0.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gifwrap/armel golang-1.23
• gifwrap/armhf (0.0.7-1 to 0.0.7-1)
  • Migration status for gifwrap/armhf (0.0.7-1 to 0.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gifwrap/armhf golang-1.23
• gifwrap/i386 (0.0.7-1 to 0.0.7-1)
  • Migration status for gifwrap/i386 (0.0.7-1 to 0.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gifwrap/i386 golang-1.23
• gifwrap/ppc64el (0.0.7-1 to 0.0.7-1)
  • Migration status for gifwrap/ppc64el (0.0.7-1 to 0.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gifwrap/ppc64el golang-1.23
• gifwrap/s390x (0.0.7-1 to 0.0.7-1)
  • Migration status for gifwrap/s390x (0.0.7-1 to 0.0.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gifwrap/s390x golang-1.23
• gigolo/riscv64 (0.5.3-1 to 0.5.3-1)
  • Migration status for gigolo/riscv64 (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
• gimagereader/riscv64 (3.4.2-2 to 3.4.2-2)
  • Migration status for gimagereader/riscv64 (3.4.2-2 to 3.4.2-2): Will attempt migration (Any information below is purely informational)
• gimp-texturize/riscv64 (2.2-4 to 2.2-4)
  • Migration status for gimp-texturize/riscv64 (2.2-4 to 2.2-4): Will attempt migration (Any information below is purely informational)
• gimplensfun/riscv64 (0.2.4-1.1 to 0.2.4-1.1)
  • Migration status for gimplensfun/riscv64 (0.2.4-1.1 to 0.2.4-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 riscv64 binaries not found
• girara/riscv64 (0.4.4-1 to 0.4.4-1)
  • Migration status for girara/riscv64 (0.4.4-1 to 0.4.4-1): Will attempt migration (Any information below is purely informational)
• git-credential-azure/amd64 (0.3.0-1 to 0.3.0-1)
  • Migration status for git-credential-azure/amd64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-azure/amd64 golang-1.23
    • Built-Using: git-credential-azure/amd64 golang-github-golang-jwt-jwt
• git-credential-azure/arm64 (0.3.0-1 to 0.3.0-1)
  • Migration status for git-credential-azure/arm64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-azure/arm64 golang-1.23
    • Built-Using: git-credential-azure/arm64 golang-github-golang-jwt-jwt
• git-credential-azure/armel (0.3.0-1 to 0.3.0-1)
  • Migration status for git-credential-azure/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-azure/armel golang-1.23
    • Built-Using: git-credential-azure/armel golang-github-golang-jwt-jwt
• git-credential-azure/armhf (0.3.0-1 to 0.3.0-1)
  • Migration status for git-credential-azure/armhf (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-azure/armhf golang-1.23
    • Built-Using: git-credential-azure/armhf golang-github-golang-jwt-jwt
• git-credential-azure/i386 (0.3.0-1 to 0.3.0-1)
  • Migration status for git-credential-azure/i386 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-azure/i386 golang-1.23
    • Built-Using: git-credential-azure/i386 golang-github-golang-jwt-jwt
• git-credential-azure/ppc64el (0.3.0-1 to 0.3.0-1)
  • Migration status for git-credential-azure/ppc64el (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-azure/ppc64el golang-1.23
    • Built-Using: git-credential-azure/ppc64el golang-github-golang-jwt-jwt
• git-credential-azure/s390x (0.3.0-1 to 0.3.0-1)
  • Migration status for git-credential-azure/s390x (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-azure/s390x golang-1.23
    • Built-Using: git-credential-azure/s390x golang-github-golang-jwt-jwt
• git-credential-oauth/amd64 (0.13.2-1 to 0.13.2-1)
  • Migration status for git-credential-oauth/amd64 (0.13.2-1 to 0.13.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-oauth/amd64 golang-1.23
• git-credential-oauth/arm64 (0.13.2-1 to 0.13.2-1)
  • Migration status for git-credential-oauth/arm64 (0.13.2-1 to 0.13.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-oauth/arm64 golang-1.23
• git-credential-oauth/armel (0.13.2-1 to 0.13.2-1)
  • Migration status for git-credential-oauth/armel (0.13.2-1 to 0.13.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-oauth/armel golang-1.23
• git-credential-oauth/armhf (0.13.2-1 to 0.13.2-1)
  • Migration status for git-credential-oauth/armhf (0.13.2-1 to 0.13.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-oauth/armhf golang-1.23
• git-credential-oauth/i386 (0.13.2-1 to 0.13.2-1)
  • Migration status for git-credential-oauth/i386 (0.13.2-1 to 0.13.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-oauth/i386 golang-1.23
• git-credential-oauth/ppc64el (0.13.2-1 to 0.13.2-1)
  • Migration status for git-credential-oauth/ppc64el (0.13.2-1 to 0.13.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-oauth/ppc64el golang-1.23
• git-credential-oauth/s390x (0.13.2-1 to 0.13.2-1)
  • Migration status for git-credential-oauth/s390x (0.13.2-1 to 0.13.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-credential-oauth/s390x golang-1.23
• git-lfs/amd64 (3.5.0-1 to 3.5.0-1)
  • Migration status for git-lfs/amd64 (3.5.0-1 to 3.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-lfs/amd64 golang-1.23
• git-lfs/arm64 (3.5.0-1 to 3.5.0-1)
  • Migration status for git-lfs/arm64 (3.5.0-1 to 3.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-lfs/arm64 golang-1.23
• git-lfs/armel (3.5.0-1 to 3.5.0-1)
  • Migration status for git-lfs/armel (3.5.0-1 to 3.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-lfs/armel golang-1.23
• git-lfs/armhf (3.5.0-1 to 3.5.0-1)
  • Migration status for git-lfs/armhf (3.5.0-1 to 3.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-lfs/armhf golang-1.23
• git-lfs/i386 (3.5.0-1 to 3.5.0-1)
  • Migration status for git-lfs/i386 (3.5.0-1 to 3.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-lfs/i386 golang-1.23
• git-lfs/ppc64el (3.5.0-1 to 3.5.0-1)
  • Migration status for git-lfs/ppc64el (3.5.0-1 to 3.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-lfs/ppc64el golang-1.23
• git-lfs/s390x (3.5.0-1 to 3.5.0-1)
  • Migration status for git-lfs/s390x (3.5.0-1 to 3.5.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-lfs/s390x golang-1.23
• git-sizer/amd64 (1.5.0-3 to 1.5.0-3)
  • Migration status for git-sizer/amd64 (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-sizer/amd64 golang-1.23
• git-sizer/arm64 (1.5.0-3 to 1.5.0-3)
  • Migration status for git-sizer/arm64 (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-sizer/arm64 golang-1.23
• git-sizer/armel (1.5.0-3 to 1.5.0-3)
  • Migration status for git-sizer/armel (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-sizer/armel golang-1.23
• git-sizer/armhf (1.5.0-3 to 1.5.0-3)
  • Migration status for git-sizer/armhf (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-sizer/armhf golang-1.23
• git-sizer/i386 (1.5.0-3 to 1.5.0-3)
  • Migration status for git-sizer/i386 (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-sizer/i386 golang-1.23
• git-sizer/ppc64el (1.5.0-3 to 1.5.0-3)
  • Migration status for git-sizer/ppc64el (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-sizer/ppc64el golang-1.23
• git-sizer/s390x (1.5.0-3 to 1.5.0-3)
  • Migration status for git-sizer/s390x (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: git-sizer/s390x golang-1.23
• gitg/riscv64 (44-1 to 44-1)
  • Migration status for gitg/riscv64 (44-1 to 44-1): Will attempt migration (Any information below is purely informational)
• gitleaks/amd64 (8.16.0-1 to 8.16.0-1)
  • Migration status for gitleaks/amd64 (8.16.0-1 to 8.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gitleaks/amd64 golang-1.23
• gitleaks/arm64 (8.16.0-1 to 8.16.0-1)
  • Migration status for gitleaks/arm64 (8.16.0-1 to 8.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gitleaks/arm64 golang-1.23
• gitleaks/armel (8.16.0-1 to 8.16.0-1)
  • Migration status for gitleaks/armel (8.16.0-1 to 8.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gitleaks/armel golang-1.23
• gitleaks/armhf (8.16.0-1 to 8.16.0-1)
  • Migration status for gitleaks/armhf (8.16.0-1 to 8.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gitleaks/armhf golang-1.23
• gitleaks/i386 (8.16.0-1 to 8.16.0-1)
  • Migration status for gitleaks/i386 (8.16.0-1 to 8.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gitleaks/i386 golang-1.23
• gitleaks/ppc64el (8.16.0-1 to 8.16.0-1)
  • Migration status for gitleaks/ppc64el (8.16.0-1 to 8.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gitleaks/ppc64el golang-1.23
• gitleaks/s390x (8.16.0-1 to 8.16.0-1)
  • Migration status for gitleaks/s390x (8.16.0-1 to 8.16.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gitleaks/s390x golang-1.23
• gjacktransport/riscv64 (0.6.4-1 to 0.6.4-1)
  • Migration status for gjacktransport/riscv64 (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
• gjiten/riscv64 (3.1-2 to 3.1-2)
  • Migration status for gjiten/riscv64 (3.1-2 to 3.1-2): Will attempt migration (Any information below is purely informational)
• gjs/riscv64 (1.80.2-1 to 1.80.2-1)
  • Migration status for gjs/riscv64 (1.80.2-1 to 1.80.2-1): Will attempt migration (Any information below is purely informational)
• gkdebconf/riscv64 (2.1.1 to 2.1.1)
  • Migration status for gkdebconf/riscv64 (2.1.1 to 2.1.1): Will attempt migration (Any information below is purely informational)
• gkrellkam/riscv64 (2.0.0-2 to 2.0.0-2)
  • Migration status for gkrellkam/riscv64 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• gkrellm-leds/riscv64 (0.8.0-2 to 0.8.0-2)
  • Migration status for gkrellm-leds/riscv64 (0.8.0-2 to 0.8.0-2): Will attempt migration (Any information below is purely informational)
• gkrellm-tz/riscv64 (0.8-2 to 0.8-2)
  • Migration status for gkrellm-tz/riscv64 (0.8-2 to 0.8-2): Will attempt migration (Any information below is purely informational)
• gkrellm-volume/riscv64 (2.1.13-1.1 to 2.1.13-1.1)
  • Migration status for gkrellm-volume/riscv64 (2.1.13-1.1 to 2.1.13-1.1): Will attempt migration (Any information below is purely informational)
• gkrellm/riscv64 (2.3.11-2 to 2.3.11-2)
  • Migration status for gkrellm/riscv64 (2.3.11-2 to 2.3.11-2): Will attempt migration (Any information below is purely informational)
• gkrellm2-cpufreq/riscv64 (0.6.4-6.1 to 0.6.4-6.1)
  • Migration status for gkrellm2-cpufreq/riscv64 (0.6.4-6.1 to 0.6.4-6.1): Will attempt migration (Any information below is purely informational)
• gkrellmwireless/riscv64 (2.0.3-2 to 2.0.3-2)
  • Migration status for gkrellmwireless/riscv64 (2.0.3-2 to 2.0.3-2): Will attempt migration (Any information below is purely informational)
• gkrelltop/riscv64 (2.2.13-1.2 to 2.2.13-1.2)
  • Migration status for gkrelltop/riscv64 (2.2.13-1.2 to 2.2.13-1.2): Will attempt migration (Any information below is purely informational)
• gkrelluim/riscv64 (0.3.2-2 to 0.3.2-2)
  • Migration status for gkrelluim/riscv64 (0.3.2-2 to 0.3.2-2): Will attempt migration (Any information below is purely informational)
• gkrellweather/riscv64 (2.0.8-2.2 to 2.0.8-2.2)
  • Migration status for gkrellweather/riscv64 (2.0.8-2.2 to 2.0.8-2.2): Will attempt migration (Any information below is purely informational)
• gl2ps/riscv64 (1.4.2+dfsg1-2 to 1.4.2+dfsg1-2)
  • Migration status for gl2ps/riscv64 (1.4.2+dfsg1-2 to 1.4.2+dfsg1-2): Will attempt migration (Any information below is purely informational)
• glasscoder/riscv64 (2.0.1-2 to 2.0.1-2)
  • Migration status for glasscoder/riscv64 (2.0.1-2 to 2.0.1-2): Will attempt migration (Any information below is purely informational)
• glbinding/riscv64 (2.1.1-2 to 2.1.1-2)
  • Migration status for glbinding/riscv64 (2.1.1-2 to 2.1.1-2): Will attempt migration (Any information below is purely informational)
• gle-graphics/riscv64 (4.3.4-1 to 4.3.4-1)
  • Migration status for gle-graphics/riscv64 (4.3.4-1 to 4.3.4-1): Will attempt migration (Any information below is purely informational)
• gle/riscv64 (3.1.2-1 to 3.1.2-1)
  • Migration status for gle/riscv64 (3.1.2-1 to 3.1.2-1): Will attempt migration (Any information below is purely informational)
• glew/riscv64 (2.2.0-4 to 2.2.0-4)
  • Migration status for glew/riscv64 (2.2.0-4 to 2.2.0-4): Will attempt migration (Any information below is purely informational)
• glewlwyd/riscv64 (2.7.6+ds-2 to 2.7.6+ds-2)
  • Migration status for glewlwyd/riscv64 (2.7.6+ds-2 to 2.7.6+ds-2): Will attempt migration (Any information below is purely informational)
• glewmx/riscv64 (1.13.0-5 to 1.13.0-5)
  • Migration status for glewmx/riscv64 (1.13.0-5 to 1.13.0-5): Will attempt migration (Any information below is purely informational)
• glfw3/riscv64 (3.4-1 to 3.4-1)
  • Migration status for glfw3/riscv64 (3.4-1 to 3.4-1): Will attempt migration (Any information below is purely informational)
• globjects/riscv64 (1.1.0-3 to 1.1.0-3)
  • Migration status for globjects/riscv64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• gloo/riscv64 (0.0~git20230519.597accf-2 to 0.0~git20230519.597accf-2)
  • Migration status for gloo/riscv64 (0.0~git20230519.597accf-2 to 0.0~git20230519.597accf-2): Will attempt migration (Any information below is purely informational)
• glpeces/riscv64 (5.2-3 to 5.2-3)
  • Migration status for glpeces/riscv64 (5.2-3 to 5.2-3): Will attempt migration (Any information below is purely informational)
• gltron/riscv64 (0.70final-12.4 to 0.70final-12.4)
  • Migration status for gltron/riscv64 (0.70final-12.4 to 0.70final-12.4): Will attempt migration (Any information below is purely informational)
• glw/riscv64 (8.0.0-3 to 8.0.0-3)
  • Migration status for glw/riscv64 (8.0.0-3 to 8.0.0-3): Will attempt migration (Any information below is purely informational)
• gm-assistant/riscv64 (1.2.4-1.1 to 1.2.4-1.1)
  • Migration status for gm-assistant/riscv64 (1.2.4-1.1 to 1.2.4-1.1): Will attempt migration (Any information below is purely informational)
• gmic/riscv64 (2.9.4-4 to 2.9.4-4)
  • Migration status for gmic/riscv64 (2.9.4-4 to 2.9.4-4): Will attempt migration (Any information below is purely informational)
• gmidimonitor/riscv64 (3.6+dfsg0-4 to 3.6+dfsg0-4)
  • Migration status for gmidimonitor/riscv64 (3.6+dfsg0-4 to 3.6+dfsg0-4): Will attempt migration (Any information below is purely informational)
• gmotionlive/riscv64 (1.0-3.1 to 1.0-3.1)
  • Migration status for gmotionlive/riscv64 (1.0-3.1 to 1.0-3.1): Will attempt migration (Any information below is purely informational)
• gmrun/riscv64 (0.9.2-3 to 0.9.2-3)
  • Migration status for gmrun/riscv64 (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
• gmt/riscv64 (6.5.0+dfsg-3 to 6.5.0+dfsg-3)
  • Migration status for gmt/riscv64 (6.5.0+dfsg-3 to 6.5.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• gmtp/riscv64 (1.3.11-3.1 to 1.3.11-3.1)
  • Migration status for gmtp/riscv64 (1.3.11-3.1 to 1.3.11-3.1): Will attempt migration (Any information below is purely informational)
• gmult/riscv64 (11.0-1 to 11.0-1)
  • Migration status for gmult/riscv64 (11.0-1 to 11.0-1): Will attempt migration (Any information below is purely informational)
• gnome-2048/riscv64 (3.38.2-3 to 3.38.2-3)
  • Migration status for gnome-2048/riscv64 (3.38.2-3 to 3.38.2-3): Will attempt migration (Any information below is purely informational)
• gnome-applets/riscv64 (3.52.0-1 to 3.52.0-1)
  • Migration status for gnome-applets/riscv64 (3.52.0-1 to 3.52.0-1): Will attempt migration (Any information below is purely informational)
• gnome-bluetooth/riscv64 (3.34.5-13 to 3.34.5-13)
  • Migration status for gnome-bluetooth/riscv64 (3.34.5-13 to 3.34.5-13): Will attempt migration (Any information below is purely informational)
• gnome-bluetooth3/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-bluetooth3/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• gnome-calendar/riscv64 (46.1-1 to 46.1-1)
  • Migration status for gnome-calendar/riscv64 (46.1-1 to 46.1-1): Will attempt migration (Any information below is purely informational)
• gnome-clocks/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-clocks/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• gnome-color-manager/riscv64 (3.36.0-2 to 3.36.0-2)
  • Migration status for gnome-color-manager/riscv64 (3.36.0-2 to 3.36.0-2): Will attempt migration (Any information below is purely informational)
• gnome-commander/amd64 (1.18.1-1 to 1.18.1-1)
  • Migration status for gnome-commander/amd64 (1.18.1-1 to 1.18.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnome-commander/amd64 exiv2
• gnome-commander/arm64 (1.18.1-1 to 1.18.1-1)
  • Migration status for gnome-commander/arm64 (1.18.1-1 to 1.18.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnome-commander/arm64 exiv2
• gnome-commander/armel (1.18.1-1 to 1.18.1-1)
  • Migration status for gnome-commander/armel (1.18.1-1 to 1.18.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnome-commander/armel exiv2
• gnome-commander/armhf (1.18.1-1 to 1.18.1-1)
  • Migration status for gnome-commander/armhf (1.18.1-1 to 1.18.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnome-commander/armhf exiv2
• gnome-commander/i386 (1.18.1-1 to 1.18.1-1)
  • Migration status for gnome-commander/i386 (1.18.1-1 to 1.18.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnome-commander/i386 exiv2
• gnome-commander/mips64el (1.18.1-1 to 1.18.1-1)
  • Migration status for gnome-commander/mips64el (1.18.1-1 to 1.18.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnome-commander/mips64el exiv2
• gnome-commander/ppc64el (1.18.1-1 to 1.18.1-1)
  • Migration status for gnome-commander/ppc64el (1.18.1-1 to 1.18.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnome-commander/ppc64el exiv2
• gnome-commander/s390x (1.18.1-1 to 1.18.1-1)
  • Migration status for gnome-commander/s390x (1.18.1-1 to 1.18.1-1): Will attempt migration (Any information below is purely informational)
    • Depends: gnome-commander/s390x exiv2
• gnome-desktop/riscv64 (44.0-5 to 44.0-5)
  • Migration status for gnome-desktop/riscv64 (44.0-5 to 44.0-5): Will attempt migration (Any information below is purely informational)
• gnome-dictionary/riscv64 (40.0-3 to 40.0-3)
  • Migration status for gnome-dictionary/riscv64 (40.0-3 to 40.0-3): Will attempt migration (Any information below is purely informational)
• gnome-firmware/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-firmware/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• gnome-flashback/riscv64 (3.52.1-2 to 3.52.1-2)
  • Migration status for gnome-flashback/riscv64 (3.52.1-2 to 3.52.1-2): Will attempt migration (Any information below is purely informational)
• gnome-font-downloader/riscv64 (10.0.0-3 to 10.0.0-3)
  • Migration status for gnome-font-downloader/riscv64 (10.0.0-3 to 10.0.0-3): Will attempt migration (Any information below is purely informational)
• gnome-hwp-support/riscv64 (0.2.0-2 to 0.2.0-2)
  • Migration status for gnome-hwp-support/riscv64 (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• gnome-klotski/riscv64 (1:3.38.2-1 to 1:3.38.2-1)
  • Migration status for gnome-klotski/riscv64 (1:3.38.2-1 to 1:3.38.2-1): Will attempt migration (Any information below is purely informational)
• gnome-logs/riscv64 (45.0-1 to 45.0-1)
  • Migration status for gnome-logs/riscv64 (45.0-1 to 45.0-1): Will attempt migration (Any information below is purely informational)
• gnome-mastermind/riscv64 (0.4.0-4 to 0.4.0-4)
  • Migration status for gnome-mastermind/riscv64 (0.4.0-4 to 0.4.0-4): Will attempt migration (Any information below is purely informational)
• gnome-mines/riscv64 (1:40.1-1 to 1:40.1-1)
  • Migration status for gnome-mines/riscv64 (1:40.1-1 to 1:40.1-1): Will attempt migration (Any information below is purely informational)
• gnome-multi-writer/riscv64 (3.32.1-2 to 3.32.1-2)
  • Migration status for gnome-multi-writer/riscv64 (3.32.1-2 to 3.32.1-2): Will attempt migration (Any information below is purely informational)
• gnome-nds-thumbnailer/riscv64 (3.0.0-3 to 3.0.0-3)
  • Migration status for gnome-nds-thumbnailer/riscv64 (3.0.0-3 to 3.0.0-3): Will attempt migration (Any information below is purely informational)
• gnome-nettool/riscv64 (42.0-1 to 42.0-1)
  • Migration status for gnome-nettool/riscv64 (42.0-1 to 42.0-1): Will attempt migration (Any information below is purely informational)
• gnome-online-accounts-gtk/riscv64 (3.50.2-1 to 3.50.2-1)
  • Migration status for gnome-online-accounts-gtk/riscv64 (3.50.2-1 to 3.50.2-1): Will attempt migration (Any information below is purely informational)
• gnome-panel/riscv64 (3.52.0-1 to 3.52.0-1)
  • Migration status for gnome-panel/riscv64 (3.52.0-1 to 3.52.0-1): Will attempt migration (Any information below is purely informational)
• gnome-pie/riscv64 (0.7.3-2 to 0.7.3-2)
  • Migration status for gnome-pie/riscv64 (0.7.3-2 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
• gnome-power-manager/riscv64 (43.0-2 to 43.0-2)
  • Migration status for gnome-power-manager/riscv64 (43.0-2 to 43.0-2): Will attempt migration (Any information below is purely informational)
• gnome-robots/riscv64 (1:40.0-2 to 1:40.0-2)
  • Migration status for gnome-robots/riscv64 (1:40.0-2 to 1:40.0-2): Will attempt migration (Any information below is purely informational)
• gnome-screensaver/riscv64 (3.6.1-13 to 3.6.1-13)
  • Migration status for gnome-screensaver/riscv64 (3.6.1-13 to 3.6.1-13): Will attempt migration (Any information below is purely informational)
• gnome-screenshot/riscv64 (41.0-2 to 41.0-2)
  • Migration status for gnome-screenshot/riscv64 (41.0-2 to 41.0-2): Will attempt migration (Any information below is purely informational)
• gnome-sushi/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-sushi/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• gnome-system-monitor/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-system-monitor/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• gnome-taquin/riscv64 (3.38.1-2 to 3.38.1-2)
  • Migration status for gnome-taquin/riscv64 (3.38.1-2 to 3.38.1-2): Will attempt migration (Any information below is purely informational)
• gnome-tetravex/riscv64 (1:3.38.2-3 to 1:3.38.2-3)
  • Migration status for gnome-tetravex/riscv64 (1:3.38.2-3 to 1:3.38.2-3): Will attempt migration (Any information below is purely informational)
• gnome-usage/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-usage/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• gnomint/riscv64 (1.3.0-4 to 1.3.0-4)
  • Migration status for gnomint/riscv64 (1.3.0-4 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
• gnss-sdr/riscv64 (0.0.19-2 to 0.0.19-2)
  • Migration status for gnss-sdr/riscv64 (0.0.19-2 to 0.0.19-2): Will attempt migration (Any information below is purely informational)
• gnss-share/amd64 (0.8.2-1 to 0.8.2-1)
  • Migration status for gnss-share/amd64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gnss-share/amd64 golang-1.23
• gnss-share/arm64 (0.8.2-1 to 0.8.2-1)
  • Migration status for gnss-share/arm64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gnss-share/arm64 golang-1.23
• gnss-share/armel (0.8.2-1 to 0.8.2-1)
  • Migration status for gnss-share/armel (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gnss-share/armel golang-1.23
• gnss-share/armhf (0.8.2-1 to 0.8.2-1)
  • Migration status for gnss-share/armhf (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gnss-share/armhf golang-1.23
• gnss-share/i386 (0.8.2-1 to 0.8.2-1)
  • Migration status for gnss-share/i386 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gnss-share/i386 golang-1.23
• gnss-share/ppc64el (0.8.2-1 to 0.8.2-1)
  • Migration status for gnss-share/ppc64el (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gnss-share/ppc64el golang-1.23
• gnss-share/s390x (0.8.2-1 to 0.8.2-1)
  • Migration status for gnss-share/s390x (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gnss-share/s390x golang-1.23
• gnucash/amd64 (1:5.8-1 to 1:5.8-1)
  • Migration status for gnucash/amd64 (1:5.8-1 to 1:5.8-1): Will attempt migration (Any information below is purely informational)
• gnucash/arm64 (1:5.8-1 to 1:5.8-1)
  • Migration status for gnucash/arm64 (1:5.8-1 to 1:5.8-1): Will attempt migration (Any information below is purely informational)
• gnucash/i386 (1:5.8-1 to 1:5.8-1)
  • Migration status for gnucash/i386 (1:5.8-1 to 1:5.8-1): Will attempt migration (Any information below is purely informational)
• gnucash/ppc64el (1:5.8-1 to 1:5.8-1)
  • Migration status for gnucash/ppc64el (1:5.8-1 to 1:5.8-1): Will attempt migration (Any information below is purely informational)
• gnucash/s390x (1:5.8-1 to 1:5.8-1)
  • Migration status for gnucash/s390x (1:5.8-1 to 1:5.8-1): Will attempt migration (Any information below is purely informational)
• gnumail/riscv64 (1.4.0-2 to 1.4.0-2)
  • Migration status for gnumail/riscv64 (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• gnurobbo/riscv64 (0.68+dfsg-6 to 0.68+dfsg-6)
  • Migration status for gnurobbo/riscv64 (0.68+dfsg-6 to 0.68+dfsg-6): Will attempt migration (Any information below is purely informational)
• gnusim8085/riscv64 (1.4.1-1 to 1.4.1-1)
  • Migration status for gnusim8085/riscv64 (1.4.1-1 to 1.4.1-1): Will attempt migration (Any information below is purely informational)
• gnustep-performance/riscv64 (0.6.0-3 to 0.6.0-3)
  • Migration status for gnustep-performance/riscv64 (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
• gnustep-sqlclient/riscv64 (1.9.0-3 to 1.9.0-3)
  • Migration status for gnustep-sqlclient/riscv64 (1.9.0-3 to 1.9.0-3): Will attempt migration (Any information below is purely informational)
• go-for-it/riscv64 (1.9.6-4 to 1.9.6-4)
  • Migration status for go-for-it/riscv64 (1.9.6-4 to 1.9.6-4): Will attempt migration (Any information below is purely informational)
• go-mmproxy/amd64 (2.1-1 to 2.1-1)
  • Migration status for go-mmproxy/amd64 (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mmproxy/amd64 golang-1.23
• go-mmproxy/arm64 (2.1-1 to 2.1-1)
  • Migration status for go-mmproxy/arm64 (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mmproxy/arm64 golang-1.23
• go-mmproxy/armel (2.1-1 to 2.1-1)
  • Migration status for go-mmproxy/armel (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mmproxy/armel golang-1.23
• go-mmproxy/i386 (2.1-1 to 2.1-1)
  • Migration status for go-mmproxy/i386 (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mmproxy/i386 golang-1.23
• go-mmproxy/ppc64el (2.1-1 to 2.1-1)
  • Migration status for go-mmproxy/ppc64el (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mmproxy/ppc64el golang-1.23
• go-mmproxy/s390x (2.1-1 to 2.1-1)
  • Migration status for go-mmproxy/s390x (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mmproxy/s390x golang-1.23
• go-mtpfs/amd64 (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1)
  • Migration status for go-mtpfs/amd64 (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mtpfs/amd64 golang-1.23
• go-mtpfs/arm64 (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1)
  • Migration status for go-mtpfs/arm64 (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mtpfs/arm64 golang-1.23
• go-mtpfs/armel (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1)
  • Migration status for go-mtpfs/armel (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mtpfs/armel golang-1.23
• go-mtpfs/i386 (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1)
  • Migration status for go-mtpfs/i386 (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mtpfs/i386 golang-1.23
• go-mtpfs/ppc64el (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1)
  • Migration status for go-mtpfs/ppc64el (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mtpfs/ppc64el golang-1.23
• go-mtpfs/s390x (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1)
  • Migration status for go-mtpfs/s390x (1.0.0+git20200111.42254b1-1 to 1.0.0+git20200111.42254b1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-mtpfs/s390x golang-1.23
• go-qrcode/amd64 (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4)
  • Migration status for go-qrcode/amd64 (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-qrcode/amd64 golang-1.23
• go-qrcode/arm64 (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4)
  • Migration status for go-qrcode/arm64 (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-qrcode/arm64 golang-1.23
• go-qrcode/armel (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4)
  • Migration status for go-qrcode/armel (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-qrcode/armel golang-1.23
• go-qrcode/i386 (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4)
  • Migration status for go-qrcode/i386 (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-qrcode/i386 golang-1.23
• go-qrcode/ppc64el (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4)
  • Migration status for go-qrcode/ppc64el (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-qrcode/ppc64el golang-1.23
• go-qrcode/s390x (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4)
  • Migration status for go-qrcode/s390x (0.0~git20200617.da1b656-4 to 0.0~git20200617.da1b656-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-qrcode/s390x golang-1.23
• go-rpmdb/amd64 (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3)
  • Migration status for go-rpmdb/amd64 (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-rpmdb/amd64 golang-1.23
• go-rpmdb/arm64 (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3)
  • Migration status for go-rpmdb/arm64 (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-rpmdb/arm64 golang-1.23
• go-rpmdb/armel (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3)
  • Migration status for go-rpmdb/armel (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-rpmdb/armel golang-1.23
• go-rpmdb/i386 (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3)
  • Migration status for go-rpmdb/i386 (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-rpmdb/i386 golang-1.23
• go-rpmdb/ppc64el (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3)
  • Migration status for go-rpmdb/ppc64el (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-rpmdb/ppc64el golang-1.23
• go-rpmdb/s390x (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3)
  • Migration status for go-rpmdb/s390x (0.0~git20210911.73bd0ce-3 to 0.0~git20210911.73bd0ce-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-rpmdb/s390x golang-1.23
• go-sendxmpp/amd64 (0.11.1-1 to 0.11.1-1)
  • Migration status for go-sendxmpp/amd64 (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-sendxmpp/amd64 golang-1.23
• go-sendxmpp/arm64 (0.11.1-1 to 0.11.1-1)
  • Migration status for go-sendxmpp/arm64 (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-sendxmpp/arm64 golang-1.23
• go-sendxmpp/armel (0.11.1-1 to 0.11.1-1)
  • Migration status for go-sendxmpp/armel (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-sendxmpp/armel golang-1.23
• go-sendxmpp/i386 (0.11.1-1 to 0.11.1-1)
  • Migration status for go-sendxmpp/i386 (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-sendxmpp/i386 golang-1.23
• go-sendxmpp/ppc64el (0.11.1-1 to 0.11.1-1)
  • Migration status for go-sendxmpp/ppc64el (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-sendxmpp/ppc64el golang-1.23
• go-sendxmpp/s390x (0.11.1-1 to 0.11.1-1)
  • Migration status for go-sendxmpp/s390x (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: go-sendxmpp/s390x golang-1.23
• gobgp/amd64 (3.29.0-1 to 3.29.0-1)
  • Migration status for gobgp/amd64 (3.29.0-1 to 3.29.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobgp/amd64 golang-1.23
• gobgp/arm64 (3.29.0-1 to 3.29.0-1)
  • Migration status for gobgp/arm64 (3.29.0-1 to 3.29.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobgp/arm64 golang-1.23
• gobgp/armel (3.29.0-1 to 3.29.0-1)
  • Migration status for gobgp/armel (3.29.0-1 to 3.29.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobgp/armel golang-1.23
• gobgp/i386 (3.29.0-1 to 3.29.0-1)
  • Migration status for gobgp/i386 (3.29.0-1 to 3.29.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobgp/i386 golang-1.23
• gobgp/ppc64el (3.29.0-1 to 3.29.0-1)
  • Migration status for gobgp/ppc64el (3.29.0-1 to 3.29.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobgp/ppc64el golang-1.23
• gobgp/s390x (3.29.0-1 to 3.29.0-1)
  • Migration status for gobgp/s390x (3.29.0-1 to 3.29.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobgp/s390x golang-1.23
• gobuster/amd64 (3.6.0-1 to 3.6.0-1)
  • Migration status for gobuster/amd64 (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobuster/amd64 golang-1.23
• gobuster/arm64 (3.6.0-1 to 3.6.0-1)
  • Migration status for gobuster/arm64 (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobuster/arm64 golang-1.23
• gobuster/armel (3.6.0-1 to 3.6.0-1)
  • Migration status for gobuster/armel (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobuster/armel golang-1.23
• gobuster/i386 (3.6.0-1 to 3.6.0-1)
  • Migration status for gobuster/i386 (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobuster/i386 golang-1.23
• gobuster/ppc64el (3.6.0-1 to 3.6.0-1)
  • Migration status for gobuster/ppc64el (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobuster/ppc64el golang-1.23
• gobuster/s390x (3.6.0-1 to 3.6.0-1)
  • Migration status for gobuster/s390x (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gobuster/s390x golang-1.23
• gocc/amd64 (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1)
  • Migration status for gocc/amd64 (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocc/amd64 golang-1.23
• gocc/arm64 (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1)
  • Migration status for gocc/arm64 (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocc/arm64 golang-1.23
• gocc/armel (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1)
  • Migration status for gocc/armel (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocc/armel golang-1.23
• gocc/i386 (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1)
  • Migration status for gocc/i386 (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocc/i386 golang-1.23
• gocc/ppc64el (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1)
  • Migration status for gocc/ppc64el (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocc/ppc64el golang-1.23
• gocc/s390x (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1)
  • Migration status for gocc/s390x (0.0~git20230228.2292f9e-1 to 0.0~git20230228.2292f9e-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocc/s390x golang-1.23
• gocryptfs/amd64 (2.4.0-1 to 2.4.0-1)
  • Migration status for gocryptfs/amd64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocryptfs/amd64 golang-1.23
• gocryptfs/arm64 (2.4.0-1 to 2.4.0-1)
  • Migration status for gocryptfs/arm64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocryptfs/arm64 golang-1.23
• gocryptfs/armel (2.4.0-1 to 2.4.0-1)
  • Migration status for gocryptfs/armel (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocryptfs/armel golang-1.23
• gocryptfs/i386 (2.4.0-1 to 2.4.0-1)
  • Migration status for gocryptfs/i386 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocryptfs/i386 golang-1.23
• gocryptfs/ppc64el (2.4.0-1 to 2.4.0-1)
  • Migration status for gocryptfs/ppc64el (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocryptfs/ppc64el golang-1.23
• gocryptfs/s390x (2.4.0-1 to 2.4.0-1)
  • Migration status for gocryptfs/s390x (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gocryptfs/s390x golang-1.23
• goffice/riscv64 (0.10.57-2 to 0.10.57-2)
  • Migration status for goffice/riscv64 (0.10.57-2 to 0.10.57-2): Will attempt migration (Any information below is purely informational)
• goiardi/amd64 (0.11.10-2 to 0.11.10-2)
  • Migration status for goiardi/amd64 (0.11.10-2 to 0.11.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: goiardi/amd64 golang-1.23
• goiardi/arm64 (0.11.10-2 to 0.11.10-2)
  • Migration status for goiardi/arm64 (0.11.10-2 to 0.11.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: goiardi/arm64 golang-1.23
• goiardi/armel (0.11.10-2 to 0.11.10-2)
  • Migration status for goiardi/armel (0.11.10-2 to 0.11.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: goiardi/armel golang-1.23
• goiardi/i386 (0.11.10-2 to 0.11.10-2)
  • Migration status for goiardi/i386 (0.11.10-2 to 0.11.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: goiardi/i386 golang-1.23
• goiardi/ppc64el (0.11.10-2 to 0.11.10-2)
  • Migration status for goiardi/ppc64el (0.11.10-2 to 0.11.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: goiardi/ppc64el golang-1.23
• goiardi/s390x (0.11.10-2 to 0.11.10-2)
  • Migration status for goiardi/s390x (0.11.10-2 to 0.11.10-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: goiardi/s390x golang-1.23
• gokey/amd64 (0.1.2-1 to 0.1.2-1)
  • Migration status for gokey/amd64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gokey/amd64 golang-1.23
• gokey/arm64 (0.1.2-1 to 0.1.2-1)
  • Migration status for gokey/arm64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gokey/arm64 golang-1.23
• gokey/armel (0.1.2-1 to 0.1.2-1)
  • Migration status for gokey/armel (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gokey/armel golang-1.23
• gokey/i386 (0.1.2-1 to 0.1.2-1)
  • Migration status for gokey/i386 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gokey/i386 golang-1.23
• gokey/ppc64el (0.1.2-1 to 0.1.2-1)
  • Migration status for gokey/ppc64el (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gokey/ppc64el golang-1.23
• gokey/s390x (0.1.2-1 to 0.1.2-1)
  • Migration status for gokey/s390x (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gokey/s390x golang-1.23
• golang-android-soong/amd64 (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4)
  • Migration status for golang-android-soong/amd64 (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-android-soong/amd64 golang-1.23
• golang-android-soong/arm64 (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4)
  • Migration status for golang-android-soong/arm64 (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-android-soong/arm64 golang-1.23
• golang-android-soong/armel (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4)
  • Migration status for golang-android-soong/armel (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-android-soong/armel golang-1.23
• golang-android-soong/i386 (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4)
  • Migration status for golang-android-soong/i386 (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-android-soong/i386 golang-1.23
• golang-android-soong/ppc64el (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4)
  • Migration status for golang-android-soong/ppc64el (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-android-soong/ppc64el golang-1.23
• golang-android-soong/s390x (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4)
  • Migration status for golang-android-soong/s390x (0.0~git20201014.17e97d9-4 to 0.0~git20201014.17e97d9-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-android-soong/s390x golang-1.23
• golang-bindata/amd64 (3.0.7+git20151023.72.a0ff256-4 to 3.0.7+git20151023.72.a0ff256-4)
  • Migration status for golang-bindata/amd64 (3.0.7+git20151023.72.a0ff256-4 to 3.0.7+git20151023.72.a0ff256-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-bindata/amd64 golang-1.23
• golang-bindata/arm64 (3.0.7+git20151023.72.a0ff256-4 to 3.0.7+git20151023.72.a0ff256-4)
  • Migration status for golang-bindata/arm64 (3.0.7+git20151023.72.a0ff256-4 to 3.0.7+git20151023.72.a0ff256-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-bindata/arm64 golang-1.23
• golang-bindata/armel (3.0.7+git20151023.72.a0ff256-4 to 3.0.7+git20151023.72.a0ff256-4)
  • Migration status for golang-bindata/armel (3.0.7+git20151023.72.a0ff256-4 to 3.0.7+git20151023.72.a0ff256-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-bindata/armel golang-1.23
• golang-bindata/i386 (3.0.7+git20151023.72.a0ff256-4 to 3.0.7+git20151023.72.a0ff256-4)
  • Migration status for golang-bindata/i386 (3.0.7+git20151023.72.a0ff256-4 to 3.0.7+git20151023.72.a0ff256-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-bindata/i386 golang-1.23
• golang-bindata/ppc64el (3.0.7+git20151023.72.a0ff256-4 to 3.0.7+git20151023.72.a0ff256-4)
  • Migration status for golang-bindata/ppc64el (3.0.7+git20151023.72.a0ff256-4 to 3.0.7+git20151023.72.a0ff256-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-bindata/ppc64el golang-1.23
• golang-connectrpc-connect/amd64 (1.13.0-1 to 1.13.0-1)
  • Migration status for golang-connectrpc-connect/amd64 (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-connectrpc-connect/amd64 golang-1.23
• golang-connectrpc-connect/arm64 (1.13.0-1 to 1.13.0-1)
  • Migration status for golang-connectrpc-connect/arm64 (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-connectrpc-connect/arm64 golang-1.23
• golang-connectrpc-connect/armel (1.13.0-1 to 1.13.0-1)
  • Migration status for golang-connectrpc-connect/armel (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-connectrpc-connect/armel golang-1.23
• golang-connectrpc-connect/i386 (1.13.0-1 to 1.13.0-1)
  • Migration status for golang-connectrpc-connect/i386 (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-connectrpc-connect/i386 golang-1.23
• golang-connectrpc-connect/ppc64el (1.13.0-1 to 1.13.0-1)
  • Migration status for golang-connectrpc-connect/ppc64el (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-connectrpc-connect/ppc64el golang-1.23
• golang-github-anacrolix-dms/amd64 (1.5.0-2 to 1.5.0-2)
  • Migration status for golang-github-anacrolix-dms/amd64 (1.5.0-2 to 1.5.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-anacrolix-dms/amd64 golang-1.23
• golang-github-anacrolix-dms/arm64 (1.5.0-2 to 1.5.0-2)
  • Migration status for golang-github-anacrolix-dms/arm64 (1.5.0-2 to 1.5.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-anacrolix-dms/arm64 golang-1.23
• golang-github-anacrolix-dms/armel (1.5.0-2 to 1.5.0-2)
  • Migration status for golang-github-anacrolix-dms/armel (1.5.0-2 to 1.5.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-anacrolix-dms/armel golang-1.23
• golang-github-anacrolix-dms/i386 (1.5.0-2 to 1.5.0-2)
  • Migration status for golang-github-anacrolix-dms/i386 (1.5.0-2 to 1.5.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-anacrolix-dms/i386 golang-1.23
• golang-github-anacrolix-dms/ppc64el (1.5.0-2 to 1.5.0-2)
  • Migration status for golang-github-anacrolix-dms/ppc64el (1.5.0-2 to 1.5.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-anacrolix-dms/ppc64el golang-1.23
• golang-github-anacrolix-missinggo/amd64 (2.1.0-7 to 2.1.0-7)
  • Migration status for golang-github-anacrolix-missinggo/amd64 (2.1.0-7 to 2.1.0-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-anacrolix-missinggo/amd64 golang-1.23
• golang-github-anacrolix-missinggo/armel (2.1.0-7 to 2.1.0-7)
  • Migration status for golang-github-anacrolix-missinggo/armel (2.1.0-7 to 2.1.0-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-anacrolix-missinggo/armel golang-1.23
• golang-github-anacrolix-missinggo/i386 (2.1.0-7 to 2.1.0-7)
  • Migration status for golang-github-anacrolix-missinggo/i386 (2.1.0-7 to 2.1.0-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-anacrolix-missinggo/i386 golang-1.23
• golang-github-anacrolix-missinggo/ppc64el (2.1.0-7 to 2.1.0-7)
  • Migration status for golang-github-anacrolix-missinggo/ppc64el (2.1.0-7 to 2.1.0-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-anacrolix-missinggo/ppc64el golang-1.23
• golang-github-avast-apkverifier/amd64 (0.0~git20191015.7330a51-11 to 0.0~git20191015.7330a51-11)
  • Migration status for golang-github-avast-apkverifier/amd64 (0.0~git20191015.7330a51-11 to 0.0~git20191015.7330a51-11): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-avast-apkverifier/amd64 golang-1.23
• golang-github-avast-apkverifier/i386 (0.0~git20191015.7330a51-11 to 0.0~git20191015.7330a51-11)
  • Migration status for golang-github-avast-apkverifier/i386 (0.0~git20191015.7330a51-11 to 0.0~git20191015.7330a51-11): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-avast-apkverifier/i386 golang-1.23
• golang-github-avast-apkverifier/ppc64el (0.0~git20191015.7330a51-11 to 0.0~git20191015.7330a51-11)
  • Migration status for golang-github-avast-apkverifier/ppc64el (0.0~git20191015.7330a51-11 to 0.0~git20191015.7330a51-11): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-avast-apkverifier/ppc64el golang-1.23
• golang-github-axgle-mahonia/amd64 (0.0~git20180208.3358181-4 to 0.0~git20180208.3358181-4)
  • Migration status for golang-github-axgle-mahonia/amd64 (0.0~git20180208.3358181-4 to 0.0~git20180208.3358181-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-axgle-mahonia/amd64 golang-1.23
• golang-github-axgle-mahonia/i386 (0.0~git20180208.3358181-4 to 0.0~git20180208.3358181-4)
  • Migration status for golang-github-axgle-mahonia/i386 (0.0~git20180208.3358181-4 to 0.0~git20180208.3358181-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-axgle-mahonia/i386 golang-1.23
• golang-github-axgle-mahonia/ppc64el (0.0~git20180208.3358181-4 to 0.0~git20180208.3358181-4)
  • Migration status for golang-github-axgle-mahonia/ppc64el (0.0~git20180208.3358181-4 to 0.0~git20180208.3358181-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-axgle-mahonia/ppc64el golang-1.23
• golang-github-aymerick-douceur/amd64 (0.2.0-3 to 0.2.0-3)
  • Migration status for golang-github-aymerick-douceur/amd64 (0.2.0-3 to 0.2.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-aymerick-douceur/amd64 golang-1.23
• golang-github-aymerick-douceur/i386 (0.2.0-3 to 0.2.0-3)
  • Migration status for golang-github-aymerick-douceur/i386 (0.2.0-3 to 0.2.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-aymerick-douceur/i386 golang-1.23
• golang-github-aymerick-douceur/ppc64el (0.2.0-3 to 0.2.0-3)
  • Migration status for golang-github-aymerick-douceur/ppc64el (0.2.0-3 to 0.2.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-aymerick-douceur/ppc64el golang-1.23
• golang-github-benbjohnson-tmpl/amd64 (0.0~git20160209.0.8e77bc5-7 to 0.0~git20160209.0.8e77bc5-7)
  • Migration status for golang-github-benbjohnson-tmpl/amd64 (0.0~git20160209.0.8e77bc5-7 to 0.0~git20160209.0.8e77bc5-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-benbjohnson-tmpl/amd64 golang-1.23
• golang-github-benbjohnson-tmpl/i386 (0.0~git20160209.0.8e77bc5-7 to 0.0~git20160209.0.8e77bc5-7)
  • Migration status for golang-github-benbjohnson-tmpl/i386 (0.0~git20160209.0.8e77bc5-7 to 0.0~git20160209.0.8e77bc5-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-benbjohnson-tmpl/i386 golang-1.23
• golang-github-benbjohnson-tmpl/ppc64el (0.0~git20160209.0.8e77bc5-7 to 0.0~git20160209.0.8e77bc5-7)
  • Migration status for golang-github-benbjohnson-tmpl/ppc64el (0.0~git20160209.0.8e77bc5-7 to 0.0~git20160209.0.8e77bc5-7): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-benbjohnson-tmpl/ppc64el golang-1.23
• golang-github-bmatsuo-lmdb-go/amd64 (1.8.0+git20170215.a14b5a3-4 to 1.8.0+git20170215.a14b5a3-4)
  • Migration status for golang-github-bmatsuo-lmdb-go/amd64 (1.8.0+git20170215.a14b5a3-4 to 1.8.0+git20170215.a14b5a3-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-bmatsuo-lmdb-go/amd64 golang-1.23
• golang-github-bmatsuo-lmdb-go/i386 (1.8.0+git20170215.a14b5a3-4 to 1.8.0+git20170215.a14b5a3-4)
  • Migration status for golang-github-bmatsuo-lmdb-go/i386 (1.8.0+git20170215.a14b5a3-4 to 1.8.0+git20170215.a14b5a3-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-bmatsuo-lmdb-go/i386 golang-1.23
• golang-github-bmatsuo-lmdb-go/ppc64el (1.8.0+git20170215.a14b5a3-4 to 1.8.0+git20170215.a14b5a3-4)
  • Migration status for golang-github-bmatsuo-lmdb-go/ppc64el (1.8.0+git20170215.a14b5a3-4 to 1.8.0+git20170215.a14b5a3-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-bmatsuo-lmdb-go/ppc64el golang-1.23
• golang-github-canonical-go-dqlite/amd64 (1.22.0-1 to 1.22.0-1)
  • Migration status for golang-github-canonical-go-dqlite/amd64 (1.22.0-1 to 1.22.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-canonical-go-dqlite/amd64 golang-1.23
• golang-github-canonical-go-dqlite/i386 (1.22.0-1 to 1.22.0-1)
  • Migration status for golang-github-canonical-go-dqlite/i386 (1.22.0-1 to 1.22.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-canonical-go-dqlite/i386 golang-1.23
• golang-github-canonical-go-dqlite/ppc64el (1.22.0-1 to 1.22.0-1)
  • Migration status for golang-github-canonical-go-dqlite/ppc64el (1.22.0-1 to 1.22.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-canonical-go-dqlite/ppc64el golang-1.23
• golang-github-cavaliergopher-grab/amd64 (3.0.1-3 to 3.0.1-3)
  • Migration status for golang-github-cavaliergopher-grab/amd64 (3.0.1-3 to 3.0.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cavaliergopher-grab/amd64 golang-1.23
• golang-github-cavaliergopher-grab/i386 (3.0.1-3 to 3.0.1-3)
  • Migration status for golang-github-cavaliergopher-grab/i386 (3.0.1-3 to 3.0.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cavaliergopher-grab/i386 golang-1.23
• golang-github-cavaliergopher-grab/ppc64el (3.0.1-3 to 3.0.1-3)
  • Migration status for golang-github-cavaliergopher-grab/ppc64el (3.0.1-3 to 3.0.1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cavaliergopher-grab/ppc64el golang-1.23
• golang-github-checkpoint-restore-checkpointctl/amd64 (1.2.1+ds1-4 to 1.2.1+ds1-4)
  • Migration status for golang-github-checkpoint-restore-checkpointctl/amd64 (1.2.1+ds1-4 to 1.2.1+ds1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-checkpoint-restore-checkpointctl/amd64 golang-1.23
• golang-github-checkpoint-restore-checkpointctl/i386 (1.2.1+ds1-4 to 1.2.1+ds1-4)
  • Migration status for golang-github-checkpoint-restore-checkpointctl/i386 (1.2.1+ds1-4 to 1.2.1+ds1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-checkpoint-restore-checkpointctl/i386 golang-1.23
• golang-github-checkpoint-restore-checkpointctl/ppc64el (1.2.1+ds1-4 to 1.2.1+ds1-4)
  • Migration status for golang-github-checkpoint-restore-checkpointctl/ppc64el (1.2.1+ds1-4 to 1.2.1+ds1-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-checkpoint-restore-checkpointctl/ppc64el golang-1.23
• golang-github-cheekybits-genny/amd64 (1.0.0-8 to 1.0.0-8)
  • Migration status for golang-github-cheekybits-genny/amd64 (1.0.0-8 to 1.0.0-8): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cheekybits-genny/amd64 golang-1.23
• golang-github-cheekybits-genny/i386 (1.0.0-8 to 1.0.0-8)
  • Migration status for golang-github-cheekybits-genny/i386 (1.0.0-8 to 1.0.0-8): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cheekybits-genny/i386 golang-1.23
• golang-github-cheekybits-genny/ppc64el (1.0.0-8 to 1.0.0-8)
  • Migration status for golang-github-cheekybits-genny/ppc64el (1.0.0-8 to 1.0.0-8): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cheekybits-genny/ppc64el golang-1.23
• golang-github-cloudflare-cfssl/amd64 (1.6.5-2 to 1.6.5-2)
  • Migration status for golang-github-cloudflare-cfssl/amd64 (1.6.5-2 to 1.6.5-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cloudflare-cfssl/amd64 golang-1.23
• golang-github-cloudflare-cfssl/ppc64el (1.6.5-2 to 1.6.5-2)
  • Migration status for golang-github-cloudflare-cfssl/ppc64el (1.6.5-2 to 1.6.5-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cloudflare-cfssl/ppc64el golang-1.23
• golang-github-cloudflare-redoctober/amd64 (0.0~git20161017.0.78e9720-5 to 0.0~git20161017.0.78e9720-5)
  • Migration status for golang-github-cloudflare-redoctober/amd64 (0.0~git20161017.0.78e9720-5 to 0.0~git20161017.0.78e9720-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cloudflare-redoctober/amd64 golang-1.23
• golang-github-cloudflare-redoctober/i386 (0.0~git20161017.0.78e9720-5 to 0.0~git20161017.0.78e9720-5)
  • Migration status for golang-github-cloudflare-redoctober/i386 (0.0~git20161017.0.78e9720-5 to 0.0~git20161017.0.78e9720-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cloudflare-redoctober/i386 golang-1.23
• golang-github-cloudflare-redoctober/ppc64el (0.0~git20161017.0.78e9720-5 to 0.0~git20161017.0.78e9720-5)
  • Migration status for golang-github-cloudflare-redoctober/ppc64el (0.0~git20161017.0.78e9720-5 to 0.0~git20161017.0.78e9720-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cloudflare-redoctober/ppc64el golang-1.23
• golang-github-colinmarc-hdfs/amd64 (2.3.0-2 to 2.3.0-2)
  • Migration status for golang-github-colinmarc-hdfs/amd64 (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-colinmarc-hdfs/amd64 golang-1.23
• golang-github-colinmarc-hdfs/ppc64el (2.3.0-2 to 2.3.0-2)
  • Migration status for golang-github-colinmarc-hdfs/ppc64el (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-colinmarc-hdfs/ppc64el golang-1.23
• golang-github-containerd-imgcrypt/amd64 (1.1.11-4 to 1.1.11-4)
  • Migration status for golang-github-containerd-imgcrypt/amd64 (1.1.11-4 to 1.1.11-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containerd-imgcrypt/amd64 golang-1.23
• golang-github-containerd-imgcrypt/ppc64el (1.1.11-4 to 1.1.11-4)
  • Migration status for golang-github-containerd-imgcrypt/ppc64el (1.1.11-4 to 1.1.11-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containerd-imgcrypt/ppc64el golang-1.23
• golang-github-containerd-stargz-snapshotter/amd64 (0.14.3-3 to 0.14.3-3)
  • Migration status for golang-github-containerd-stargz-snapshotter/amd64 (0.14.3-3 to 0.14.3-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containerd-stargz-snapshotter/amd64 golang-1.23
• golang-github-containerd-stargz-snapshotter/ppc64el (0.14.3-3 to 0.14.3-3)
  • Migration status for golang-github-containerd-stargz-snapshotter/ppc64el (0.14.3-3 to 0.14.3-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containerd-stargz-snapshotter/ppc64el golang-1.23
• golang-github-containernetworking-plugins/amd64 (1.1.1+ds1-3 to 1.1.1+ds1-3)
  • Migration status for golang-github-containernetworking-plugins/amd64 (1.1.1+ds1-3 to 1.1.1+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containernetworking-plugins/amd64 golang-1.23
• golang-github-containernetworking-plugins/ppc64el (1.1.1+ds1-3 to 1.1.1+ds1-3)
  • Migration status for golang-github-containernetworking-plugins/ppc64el (1.1.1+ds1-3 to 1.1.1+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containernetworking-plugins/ppc64el golang-1.23
• golang-github-containers-dnsname/amd64 (1.3.1+ds1-2 to 1.3.1+ds1-2)
  • Migration status for golang-github-containers-dnsname/amd64 (1.3.1+ds1-2 to 1.3.1+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containers-dnsname/amd64 golang-1.23
• golang-github-containers-dnsname/ppc64el (1.3.1+ds1-2 to 1.3.1+ds1-2)
  • Migration status for golang-github-containers-dnsname/ppc64el (1.3.1+ds1-2 to 1.3.1+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containers-dnsname/ppc64el golang-1.23
• golang-github-containers-luksy/amd64 (0.0~git20240812.2e7307c+ds1-1 to 0.0~git20240812.2e7307c+ds1-1)
  • Migration status for golang-github-containers-luksy/amd64 (0.0~git20240812.2e7307c+ds1-1 to 0.0~git20240812.2e7307c+ds1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containers-luksy/amd64 golang-1.23
• golang-github-containers-luksy/ppc64el (0.0~git20240812.2e7307c+ds1-1 to 0.0~git20240812.2e7307c+ds1-1)
  • Migration status for golang-github-containers-luksy/ppc64el (0.0~git20240812.2e7307c+ds1-1 to 0.0~git20240812.2e7307c+ds1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containers-luksy/ppc64el golang-1.23
• golang-github-containers-storage/amd64 (1.55.0+ds1-3 to 1.55.0+ds1-3)
  • Migration status for golang-github-containers-storage/amd64 (1.55.0+ds1-3 to 1.55.0+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containers-storage/amd64 golang-1.23
• golang-github-containers-storage/ppc64el (1.55.0+ds1-3 to 1.55.0+ds1-3)
  • Migration status for golang-github-containers-storage/ppc64el (1.55.0+ds1-3 to 1.55.0+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containers-storage/ppc64el golang-1.23
• golang-github-coreos-discovery-etcd-io/amd64 (2.0.0+git2019.04.19.git.78fb45d3c9-4 to 2.0.0+git2019.04.19.git.78fb45d3c9-4)
  • Migration status for golang-github-coreos-discovery-etcd-io/amd64 (2.0.0+git2019.04.19.git.78fb45d3c9-4 to 2.0.0+git2019.04.19.git.78fb45d3c9-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-coreos-discovery-etcd-io/amd64 golang-1.23
• golang-github-coreos-discovery-etcd-io/ppc64el (2.0.0+git2019.04.19.git.78fb45d3c9-4 to 2.0.0+git2019.04.19.git.78fb45d3c9-4)
  • Migration status for golang-github-coreos-discovery-etcd-io/ppc64el (2.0.0+git2019.04.19.git.78fb45d3c9-4 to 2.0.0+git2019.04.19.git.78fb45d3c9-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-coreos-discovery-etcd-io/ppc64el golang-1.23
• golang-github-cowsql-go-cowsql/amd64 (1.22.0-2 to 1.22.0-2)
  • Migration status for golang-github-cowsql-go-cowsql/amd64 (1.22.0-2 to 1.22.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cowsql-go-cowsql/amd64 golang-1.23
• golang-github-cowsql-go-cowsql/ppc64el (1.22.0-2 to 1.22.0-2)
  • Migration status for golang-github-cowsql-go-cowsql/ppc64el (1.22.0-2 to 1.22.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-cowsql-go-cowsql/ppc64el golang-1.23
• golang-github-crc-org-crc/amd64 (2.34.0+ds1-1 to 2.34.0+ds1-1)
  • Migration status for golang-github-crc-org-crc/amd64 (2.34.0+ds1-1 to 2.34.0+ds1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-crc-org-crc/amd64 golang-1.23
• golang-github-crc-org-crc/ppc64el (2.34.0+ds1-1 to 2.34.0+ds1-1)
  • Migration status for golang-github-crc-org-crc/ppc64el (2.34.0+ds1-1 to 2.34.0+ds1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-crc-org-crc/ppc64el golang-1.23
• golang-github-crc-org-crc/riscv64 (2.34.0+ds1-1 to 2.34.0+ds1-1)
  • Migration status for golang-github-crc-org-crc/riscv64 (2.34.0+ds1-1 to 2.34.0+ds1-1): Will attempt migration (Any information below is purely informational)
• golang-github-dataence-porter2/amd64 (0.0~git20150829.56e4718-5 to 0.0~git20150829.56e4718-5)
  • Migration status for golang-github-dataence-porter2/amd64 (0.0~git20150829.56e4718-5 to 0.0~git20150829.56e4718-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-dataence-porter2/amd64 golang-1.23
• golang-github-dataence-porter2/ppc64el (0.0~git20150829.56e4718-5 to 0.0~git20150829.56e4718-5)
  • Migration status for golang-github-dataence-porter2/ppc64el (0.0~git20150829.56e4718-5 to 0.0~git20150829.56e4718-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-dataence-porter2/ppc64el golang-1.23
• golang-github-dcso-bloom/amd64 (0.2.4-3 to 0.2.4-3)
  • Migration status for golang-github-dcso-bloom/amd64 (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-dcso-bloom/amd64 golang-1.23
• golang-github-dcso-bloom/ppc64el (0.2.4-3 to 0.2.4-3)
  • Migration status for golang-github-dcso-bloom/ppc64el (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-dcso-bloom/ppc64el golang-1.23
• golang-github-dnstap-golang-dnstap/amd64 (0.4.0-5 to 0.4.0-5)
  • Migration status for golang-github-dnstap-golang-dnstap/amd64 (0.4.0-5 to 0.4.0-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-dnstap-golang-dnstap/amd64 golang-1.23
• golang-github-dnstap-golang-dnstap/ppc64el (0.4.0-5 to 0.4.0-5)
  • Migration status for golang-github-dnstap-golang-dnstap/ppc64el (0.4.0-5 to 0.4.0-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-dnstap-golang-dnstap/ppc64el golang-1.23
• golang-github-docker-docker-credential-helpers/amd64 (0.6.4+ds1-1 to 0.6.4+ds1-1)
  • Migration status for golang-github-docker-docker-credential-helpers/amd64 (0.6.4+ds1-1 to 0.6.4+ds1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-docker-docker-credential-helpers/amd64 golang-1.23
• golang-github-docker-docker-credential-helpers/ppc64el (0.6.4+ds1-1 to 0.6.4+ds1-1)
  • Migration status for golang-github-docker-docker-credential-helpers/ppc64el (0.6.4+ds1-1 to 0.6.4+ds1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-docker-docker-credential-helpers/ppc64el golang-1.23
• golang-github-docker-docker-credential-helpers/riscv64 (0.6.4+ds1-1 to 0.6.4+ds1-1)
  • Migration status for golang-github-docker-docker-credential-helpers/riscv64 (0.6.4+ds1-1 to 0.6.4+ds1-1): Will attempt migration (Any information below is purely informational)
• golang-github-eknkc-amber/amd64 (0.0~git20171010.cdade1c-2 to 0.0~git20171010.cdade1c-2)
  • Migration status for golang-github-eknkc-amber/amd64 (0.0~git20171010.cdade1c-2 to 0.0~git20171010.cdade1c-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-eknkc-amber/amd64 golang-1.23
• golang-github-eknkc-amber/ppc64el (0.0~git20171010.cdade1c-2 to 0.0~git20171010.cdade1c-2)
  • Migration status for golang-github-eknkc-amber/ppc64el (0.0~git20171010.cdade1c-2 to 0.0~git20171010.cdade1c-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-eknkc-amber/ppc64el golang-1.23
• golang-github-emersion-go-msgauth/amd64 (0.6.6-2 to 0.6.6-2)
  • Migration status for golang-github-emersion-go-msgauth/amd64 (0.6.6-2 to 0.6.6-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-emersion-go-msgauth/amd64 golang-1.23
• golang-github-emersion-go-msgauth/ppc64el (0.6.6-2 to 0.6.6-2)
  • Migration status for golang-github-emersion-go-msgauth/ppc64el (0.6.6-2 to 0.6.6-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-emersion-go-msgauth/ppc64el golang-1.23
• golang-github-evanw-esbuild/amd64 (0.23.0-1 to 0.23.0-1)
  • Migration status for golang-github-evanw-esbuild/amd64 (0.23.0-1 to 0.23.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-evanw-esbuild/amd64 golang-1.23
• golang-github-evanw-esbuild/ppc64el (0.23.0-1 to 0.23.0-1)
  • Migration status for golang-github-evanw-esbuild/ppc64el (0.23.0-1 to 0.23.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-evanw-esbuild/ppc64el golang-1.23
• golang-github-fernet-fernet-go/amd64 (0.0~git20180830.9eac43b-2 to 0.0~git20180830.9eac43b-2)
  • Migration status for golang-github-fernet-fernet-go/amd64 (0.0~git20180830.9eac43b-2 to 0.0~git20180830.9eac43b-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-fernet-fernet-go/amd64 golang-1.23
• golang-github-fernet-fernet-go/ppc64el (0.0~git20180830.9eac43b-2 to 0.0~git20180830.9eac43b-2)
  • Migration status for golang-github-fernet-fernet-go/ppc64el (0.0~git20180830.9eac43b-2 to 0.0~git20180830.9eac43b-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-fernet-fernet-go/ppc64el golang-1.23
• golang-github-ffuf-pencode/amd64 (0.4-1 to 0.4-1)
  • Migration status for golang-github-ffuf-pencode/amd64 (0.4-1 to 0.4-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-ffuf-pencode/amd64 golang-1.23
• golang-github-ffuf-pencode/ppc64el (0.4-1 to 0.4-1)
  • Migration status for golang-github-ffuf-pencode/ppc64el (0.4-1 to 0.4-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-ffuf-pencode/ppc64el golang-1.23
• golang-github-francoispqt-gojay/amd64 (1.2.13-5 to 1.2.13-5)
  • Migration status for golang-github-francoispqt-gojay/amd64 (1.2.13-5 to 1.2.13-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-francoispqt-gojay/amd64 golang-1.23
• golang-github-francoispqt-gojay/ppc64el (1.2.13-5 to 1.2.13-5)
  • Migration status for golang-github-francoispqt-gojay/ppc64el (1.2.13-5 to 1.2.13-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-francoispqt-gojay/ppc64el golang-1.23
• golang-github-geertjohan-go.rice/amd64 (1.0.2-1 to 1.0.2-1)
  • Migration status for golang-github-geertjohan-go.rice/amd64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-geertjohan-go.rice/amd64 golang-1.23
• golang-github-geertjohan-go.rice/ppc64el (1.0.2-1 to 1.0.2-1)
  • Migration status for golang-github-geertjohan-go.rice/ppc64el (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-geertjohan-go.rice/ppc64el golang-1.23
• golang-github-glendc-go-external-ip/amd64 (0.1.0-2 to 0.1.0-2)
  • Migration status for golang-github-glendc-go-external-ip/amd64 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-glendc-go-external-ip/amd64 golang-1.23
• golang-github-glendc-go-external-ip/ppc64el (0.1.0-2 to 0.1.0-2)
  • Migration status for golang-github-glendc-go-external-ip/ppc64el (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-glendc-go-external-ip/ppc64el golang-1.23
• golang-github-go-debos-fakemachine/amd64 (0.0.10-1 to 0.0.10-1)
  • Migration status for golang-github-go-debos-fakemachine/amd64 (0.0.10-1 to 0.0.10-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-go-debos-fakemachine/amd64 golang-1.23
• golang-github-go-enry-go-license-detector/amd64 (4.3.0+git20221007.a3a1cc6-3 to 4.3.0+git20221007.a3a1cc6-3)
  • Migration status for golang-github-go-enry-go-license-detector/amd64 (4.3.0+git20221007.a3a1cc6-3 to 4.3.0+git20221007.a3a1cc6-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-go-enry-go-license-detector/amd64 golang-1.23
• golang-github-go-enry-go-license-detector/ppc64el (4.3.0+git20221007.a3a1cc6-3 to 4.3.0+git20221007.a3a1cc6-3)
  • Migration status for golang-github-go-enry-go-license-detector/ppc64el (4.3.0+git20221007.a3a1cc6-3 to 4.3.0+git20221007.a3a1cc6-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-go-enry-go-license-detector/ppc64el golang-1.23
• golang-github-go-git-go-git/amd64 (5.11.0-4 to 5.11.0-4)
  • Migration status for golang-github-go-git-go-git/amd64 (5.11.0-4 to 5.11.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-go-git-go-git/amd64 golang-1.23
• golang-github-go-git-go-git/ppc64el (5.11.0-4 to 5.11.0-4)
  • Migration status for golang-github-go-git-go-git/ppc64el (5.11.0-4 to 5.11.0-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-go-git-go-git/ppc64el golang-1.23
• golang-github-go-jose-go-jose/amd64 (4.0.4-1 to 4.0.4-1)
  • Migration status for golang-github-go-jose-go-jose/amd64 (4.0.4-1 to 4.0.4-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-go-jose-go-jose/amd64 golang-1.23
• golang-github-go-jose-go-jose/ppc64el (4.0.4-1 to 4.0.4-1)
  • Migration status for golang-github-go-jose-go-jose/ppc64el (4.0.4-1 to 4.0.4-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-go-jose-go-jose/ppc64el golang-1.23
• golang-github-golang-mock/amd64 (1.6.0-2 to 1.6.0-2)
  • Migration status for golang-github-golang-mock/amd64 (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-golang-mock/amd64 golang-1.23
• golang-github-golang-mock/ppc64el (1.6.0-2 to 1.6.0-2)
  • Migration status for golang-github-golang-mock/ppc64el (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-golang-mock/ppc64el golang-1.23
• golang-github-golang-protobuf-1-3/amd64 (1.3.5-4 to 1.3.5-4)
  • Migration status for golang-github-golang-protobuf-1-3/amd64 (1.3.5-4 to 1.3.5-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-golang-protobuf-1-3/amd64 golang-1.23
• golang-github-golang-protobuf-1-3/ppc64el (1.3.5-4 to 1.3.5-4)
  • Migration status for golang-github-golang-protobuf-1-3/ppc64el (1.3.5-4 to 1.3.5-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-golang-protobuf-1-3/ppc64el golang-1.23
• golang-github-google-blueprint/ppc64el (0.0~git20201007.25128be-2 to 0.0~git20201007.25128be-2)
  • Migration status for golang-github-google-blueprint/ppc64el (0.0~git20201007.25128be-2 to 0.0~git20201007.25128be-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-google-blueprint/ppc64el golang-1.23
• golang-github-google-wire/amd64 (0.6.0-1 to 0.6.0-1)
  • Migration status for golang-github-google-wire/amd64 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-google-wire/amd64 golang-1.23
• golang-github-google-wire/ppc64el (0.6.0-1 to 0.6.0-1)
  • Migration status for golang-github-google-wire/ppc64el (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-google-wire/ppc64el golang-1.23
• golang-github-googleapis-enterprise-certificate-proxy/amd64 (0.2.0-3 to 0.2.0-3)
  • Migration status for golang-github-googleapis-enterprise-certificate-proxy/amd64 (0.2.0-3 to 0.2.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-googleapis-enterprise-certificate-proxy/amd64 golang-1.23
• golang-github-googleapis-enterprise-certificate-proxy/ppc64el (0.2.0-3 to 0.2.0-3)
  • Migration status for golang-github-googleapis-enterprise-certificate-proxy/ppc64el (0.2.0-3 to 0.2.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-googleapis-enterprise-certificate-proxy/ppc64el golang-1.23
• golang-github-grpc-ecosystem-grpc-gateway/amd64 (2.20.0-2 to 2.20.0-2)
  • Migration status for golang-github-grpc-ecosystem-grpc-gateway/amd64 (2.20.0-2 to 2.20.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-grpc-ecosystem-grpc-gateway/amd64 golang-1.23
• golang-github-grpc-ecosystem-grpc-gateway/ppc64el (2.20.0-2 to 2.20.0-2)
  • Migration status for golang-github-grpc-ecosystem-grpc-gateway/ppc64el (2.20.0-2 to 2.20.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-grpc-ecosystem-grpc-gateway/ppc64el golang-1.23
• golang-github-gucumber-gucumber/amd64 (0.0~git20160715.0.71608e2-1.1 to 0.0~git20160715.0.71608e2-1.1)
  • Migration status for golang-github-gucumber-gucumber/amd64 (0.0~git20160715.0.71608e2-1.1 to 0.0~git20160715.0.71608e2-1.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-gucumber-gucumber/amd64 golang-1.23
• golang-github-gucumber-gucumber/ppc64el (0.0~git20160715.0.71608e2-1.1 to 0.0~git20160715.0.71608e2-1.1)
  • Migration status for golang-github-gucumber-gucumber/ppc64el (0.0~git20160715.0.71608e2-1.1 to 0.0~git20160715.0.71608e2-1.1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-gucumber-gucumber/ppc64el golang-1.23
• golang-github-hashicorp-serf/amd64 (0.10.1-1 to 0.10.1-1)
  • Migration status for golang-github-hashicorp-serf/amd64 (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-hashicorp-serf/amd64 golang-1.23
• golang-github-hashicorp-serf/ppc64el (0.10.1-1 to 0.10.1-1)
  • Migration status for golang-github-hashicorp-serf/ppc64el (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-hashicorp-serf/ppc64el golang-1.23
• golang-github-hashicorp-terraform-config-inspect/amd64 (0.0~git20230614.f32df32-2 to 0.0~git20230614.f32df32-2)
  • Migration status for golang-github-hashicorp-terraform-config-inspect/amd64 (0.0~git20230614.f32df32-2 to 0.0~git20230614.f32df32-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-hashicorp-terraform-config-inspect/amd64 golang-1.23
• golang-github-hashicorp-terraform-config-inspect/ppc64el (0.0~git20230614.f32df32-2 to 0.0~git20230614.f32df32-2)
  • Migration status for golang-github-hashicorp-terraform-config-inspect/ppc64el (0.0~git20230614.f32df32-2 to 0.0~git20230614.f32df32-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-hashicorp-terraform-config-inspect/ppc64el golang-1.23
• golang-github-hhatto-gorst/amd64 (0.0~git20181029.ca9f730-3 to 0.0~git20181029.ca9f730-3)
  • Migration status for golang-github-hhatto-gorst/amd64 (0.0~git20181029.ca9f730-3 to 0.0~git20181029.ca9f730-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-hhatto-gorst/amd64 golang-1.23
• golang-github-hhatto-gorst/ppc64el (0.0~git20181029.ca9f730-3 to 0.0~git20181029.ca9f730-3)
  • Migration status for golang-github-hhatto-gorst/ppc64el (0.0~git20181029.ca9f730-3 to 0.0~git20181029.ca9f730-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-hhatto-gorst/ppc64el golang-1.23
• golang-github-humanlogio-humanlog/amd64 (0.7.6+ds1-3 to 0.7.6+ds1-3)
  • Migration status for golang-github-humanlogio-humanlog/amd64 (0.7.6+ds1-3 to 0.7.6+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-humanlogio-humanlog/amd64 golang-1.23
• golang-github-humanlogio-humanlog/ppc64el (0.7.6+ds1-3 to 0.7.6+ds1-3)
  • Migration status for golang-github-humanlogio-humanlog/ppc64el (0.7.6+ds1-3 to 0.7.6+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-humanlogio-humanlog/ppc64el golang-1.23
• golang-github-inetaf-tcpproxy/ppc64el (0.0~git20231102.2862066-2 to 0.0~git20231102.2862066-2)
  • Migration status for golang-github-inetaf-tcpproxy/ppc64el (0.0~git20231102.2862066-2 to 0.0~git20231102.2862066-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-inetaf-tcpproxy/ppc64el golang-1.23
• golang-github-influxdata-yarpc/ppc64el (0.0.1-2 to 0.0.1-2)
  • Migration status for golang-github-influxdata-yarpc/ppc64el (0.0.1-2 to 0.0.1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-influxdata-yarpc/ppc64el golang-1.23
• golang-github-jhillyerd-enmime/amd64 (0.9.3-5 to 0.9.3-5)
  • Migration status for golang-github-jhillyerd-enmime/amd64 (0.9.3-5 to 0.9.3-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-jhillyerd-enmime/amd64 golang-1.23
• golang-github-jhillyerd-enmime/ppc64el (0.9.3-5 to 0.9.3-5)
  • Migration status for golang-github-jhillyerd-enmime/ppc64el (0.9.3-5 to 0.9.3-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-jhillyerd-enmime/ppc64el golang-1.23
• golang-github-katalix-go-l2tp/ppc64el (0.1.8-1 to 0.1.8-1)
  • Migration status for golang-github-katalix-go-l2tp/ppc64el (0.1.8-1 to 0.1.8-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-katalix-go-l2tp/ppc64el golang-1.23
• golang-github-mailru-easyjson/ppc64el (0.7.7-1 to 0.7.7-1)
  • Migration status for golang-github-mailru-easyjson/ppc64el (0.7.7-1 to 0.7.7-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-mailru-easyjson/ppc64el golang-1.23
• golang-github-mendersoftware-mender-artifact/ppc64el (3.9.0+ds1-1 to 3.9.0+ds1-1)
  • Migration status for golang-github-mendersoftware-mender-artifact/ppc64el (3.9.0+ds1-1 to 3.9.0+ds1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-mendersoftware-mender-artifact/ppc64el golang-1.23
• golang-github-micromdm-scep/ppc64el (2.1.0-3 to 2.1.0-3)
  • Migration status for golang-github-micromdm-scep/ppc64el (2.1.0-3 to 2.1.0-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-micromdm-scep/ppc64el golang-1.23
• golang-github-mightyguava-jl/ppc64el (0.1.0+git20220705+8771236337c6-1 to 0.1.0+git20220705+8771236337c6-1)
  • Migration status for golang-github-mightyguava-jl/ppc64el (0.1.0+git20220705+8771236337c6-1 to 0.1.0+git20220705+8771236337c6-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-mightyguava-jl/ppc64el golang-1.23
• golang-github-mozillazg-go-pinyin/ppc64el (0.20.0+ds.1-1 to 0.20.0+ds.1-1)
  • Migration status for golang-github-mozillazg-go-pinyin/ppc64el (0.20.0+ds.1-1 to 0.20.0+ds.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-mozillazg-go-pinyin/ppc64el golang-1.23
• golang-github-muka-go-bluetooth/ppc64el (5.60-3 to 5.60-3)
  • Migration status for golang-github-muka-go-bluetooth/ppc64el (5.60-3 to 5.60-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-muka-go-bluetooth/ppc64el golang-1.23
• golang-github-odeke-em-cli-spinner/ppc64el (0.0~git20150423.610063b-4 to 0.0~git20150423.610063b-4)
  • Migration status for golang-github-odeke-em-cli-spinner/ppc64el (0.0~git20150423.610063b-4 to 0.0~git20150423.610063b-4): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-odeke-em-cli-spinner/ppc64el golang-1.23
• golang-github-openshift-imagebuilder/ppc64el (1.2.14+ds1-2 to 1.2.14+ds1-2)
  • Migration status for golang-github-openshift-imagebuilder/ppc64el (1.2.14+ds1-2 to 1.2.14+ds1-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-openshift-imagebuilder/ppc64el golang-1.23
• golang-github-pelletier-go-toml/ppc64el (1.9.5-1 to 1.9.5-1)
  • Migration status for golang-github-pelletier-go-toml/ppc64el (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-pelletier-go-toml/ppc64el golang-1.23
• golang-github-rakyll-statik/ppc64el (0.1.1-5 to 0.1.1-5)
  • Migration status for golang-github-rakyll-statik/ppc64el (0.1.1-5 to 0.1.1-5): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-rakyll-statik/ppc64el golang-1.23
• golly/riscv64 (3.3-1.1 to 3.3-1.1)
  • Migration status for golly/riscv64 (3.3-1.1 to 3.3-1.1): Will attempt migration (Any information below is purely informational)
• goodvibes/riscv64 (0.8.0-1 to 0.8.0-1)
  • Migration status for goodvibes/riscv64 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• gopchop/riscv64 (1.1.8-7 to 1.1.8-7)
  • Migration status for gopchop/riscv64 (1.1.8-7 to 1.1.8-7): Will attempt migration (Any information below is purely informational)
• gource/riscv64 (0.54-1 to 0.54-1)
  • Migration status for gource/riscv64 (0.54-1 to 0.54-1): Will attempt migration (Any information below is purely informational)
• goxel/riscv64 (0.11.0-1.1 to 0.11.0-1.1)
  • Migration status for goxel/riscv64 (0.11.0-1.1 to 0.11.0-1.1): Will attempt migration (Any information below is purely informational)
• gparted/riscv64 (1.5.0-1 to 1.5.0-1)
  • Migration status for gparted/riscv64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
• gphoto2-cffi/riscv64 (0.4.3~a1-1.1 to 0.4.3~a1-1.1)
  • Migration status for gphoto2-cffi/riscv64 (0.4.3~a1-1.1 to 0.4.3~a1-1.1): Will attempt migration (Any information below is purely informational)
• gphotofs/riscv64 (0.5-6 to 0.5-6)
  • Migration status for gphotofs/riscv64 (0.5-6 to 0.5-6): Will attempt migration (Any information below is purely informational)
• gpick/riscv64 (0.2.6-1.1 to 0.2.6-1.1)
  • Migration status for gpick/riscv64 (0.2.6-1.1 to 0.2.6-1.1): Will attempt migration (Any information below is purely informational)
• gplanarity/riscv64 (17906-7 to 17906-7)
  • Migration status for gplanarity/riscv64 (17906-7 to 17906-7): Will attempt migration (Any information below is purely informational)
• gqrx-sdr/riscv64 (2.17.5-1 to 2.17.5-1)
  • Migration status for gqrx-sdr/riscv64 (2.17.5-1 to 2.17.5-1): Will attempt migration (Any information below is purely informational)
• gr-air-modes/riscv64 (0.0.20210211-3.1 to 0.0.20210211-3.1)
  • Migration status for gr-air-modes/riscv64 (0.0.20210211-3.1 to 0.0.20210211-3.1): Will attempt migration (Any information below is purely informational)
• gr-fosphor/riscv64 (3.9~git20240323.74d54fc-1 to 3.9~git20240323.74d54fc-1)
  • Migration status for gr-fosphor/riscv64 (3.9~git20240323.74d54fc-1 to 3.9~git20240323.74d54fc-1): Will attempt migration (Any information below is purely informational)
• gr-funcube/riscv64 (3.10.0~rc3-4 to 3.10.0~rc3-4)
  • Migration status for gr-funcube/riscv64 (3.10.0~rc3-4 to 3.10.0~rc3-4): Will attempt migration (Any information below is purely informational)
• gr-hpsdr/riscv64 (3.0-2 to 3.0-2)
  • Migration status for gr-hpsdr/riscv64 (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
• gr-iqbal/riscv64 (0.38.2-2 to 0.38.2-2)
  • Migration status for gr-iqbal/riscv64 (0.38.2-2 to 0.38.2-2): Will attempt migration (Any information below is purely informational)
• gr-limesdr/riscv64 (3.0.1.10.69-3 to 3.0.1.10.69-3)
  • Migration status for gr-limesdr/riscv64 (3.0.1.10.69-3 to 3.0.1.10.69-3): Will attempt migration (Any information below is purely informational)
• gr-radar/riscv64 (0.0.0.20220920-2 to 0.0.0.20220920-2)
  • Migration status for gr-radar/riscv64 (0.0.0.20220920-2 to 0.0.0.20220920-2): Will attempt migration (Any information below is purely informational)
• gr-rds/riscv64 (3.10-1 to 3.10-1)
  • Migration status for gr-rds/riscv64 (3.10-1 to 3.10-1): Will attempt migration (Any information below is purely informational)
• gr-satellites/riscv64 (5.5.0-2 to 5.5.0-2)
  • Migration status for gr-satellites/riscv64 (5.5.0-2 to 5.5.0-2): Will attempt migration (Any information below is purely informational)
• granatier/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for granatier/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• granite/riscv64 (6.2.0-3 to 6.2.0-3)
  • Migration status for granite/riscv64 (6.2.0-3 to 6.2.0-3): Will attempt migration (Any information below is purely informational)
• grantlee5/riscv64 (5.3.1-3 to 5.3.1-3)
  • Migration status for grantlee5/riscv64 (5.3.1-3 to 5.3.1-3): Will attempt migration (Any information below is purely informational)
• granule/riscv64 (1.4.0-7-10 to 1.4.0-7-10)
  • Migration status for granule/riscv64 (1.4.0-7-10 to 1.4.0-7-10): Will attempt migration (Any information below is purely informational)
• gravit/riscv64 (0.5.1+dfsg-6 to 0.5.1+dfsg-6)
  • Migration status for gravit/riscv64 (0.5.1+dfsg-6 to 0.5.1+dfsg-6): Will attempt migration (Any information below is purely informational)
• grdesktop/riscv64 (0.23+d040330-8 to 0.23+d040330-8)
  • Migration status for grdesktop/riscv64 (0.23+d040330-8 to 0.23+d040330-8): Will attempt migration (Any information below is purely informational)
• gri/riscv64 (2.12.27-1.2 to 2.12.27-1.2)
  • Migration status for gri/riscv64 (2.12.27-1.2 to 2.12.27-1.2): Will attempt migration (Any information below is purely informational)
• gridlock.app/riscv64 (1.10-5 to 1.10-5)
  • Migration status for gridlock.app/riscv64 (1.10-5 to 1.10-5): Will attempt migration (Any information below is purely informational)
• gridsite/riscv64 (3.0.0~20240125git1200598-1 to 3.0.0~20240125git1200598-1)
  • Migration status for gridsite/riscv64 (3.0.0~20240125git1200598-1 to 3.0.0~20240125git1200598-1): Will attempt migration (Any information below is purely informational)
• grig/riscv64 (0.9.0-1 to 0.9.0-1)
  • Migration status for grig/riscv64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• grilo-plugins/riscv64 (0.3.16-1.1 to 0.3.16-1.1)
  • Migration status for grilo-plugins/riscv64 (0.3.16-1.1 to 0.3.16-1.1): Will attempt migration (Any information below is purely informational)
• grilo/riscv64 (0.3.16-1 to 0.3.16-1)
  • Migration status for grilo/riscv64 (0.3.16-1 to 0.3.16-1): Will attempt migration (Any information below is purely informational)
• grimripper/riscv64 (3.0.2-4 to 3.0.2-4)
  • Migration status for grimripper/riscv64 (3.0.2-4 to 3.0.2-4): Will attempt migration (Any information below is purely informational)
• gromit/riscv64 (20041213-9 to 20041213-9)
  • Migration status for gromit/riscv64 (20041213-9 to 20041213-9): Will attempt migration (Any information below is purely informational)
• groundhog/riscv64 (1.4-11 to 1.4-11)
  • Migration status for groundhog/riscv64 (1.4-11 to 1.4-11): Will attempt migration (Any information below is purely informational)
• growl-for-linux/riscv64 (0.8.5-9.1 to 0.8.5-9.1)
  • Migration status for growl-for-linux/riscv64 (0.8.5-9.1 to 0.8.5-9.1): Will attempt migration (Any information below is purely informational)
• grsync/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for grsync/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• gsettings-qt/riscv64 (0.2-5 to 0.2-5)
  • Migration status for gsettings-qt/riscv64 (0.2-5 to 0.2-5): Will attempt migration (Any information below is purely informational)
• gsimplecal/riscv64 (2.5.1-1 to 2.5.1-1)
  • Migration status for gsimplecal/riscv64 (2.5.1-1 to 2.5.1-1): Will attempt migration (Any information below is purely informational)
• gsound/riscv64 (1.0.3-3.2 to 1.0.3-3.2)
  • Migration status for gsound/riscv64 (1.0.3-3.2 to 1.0.3-3.2): Will attempt migration (Any information below is purely informational)
• gspell/riscv64 (1.12.2-1 to 1.12.2-1)
  • Migration status for gspell/riscv64 (1.12.2-1 to 1.12.2-1): Will attempt migration (Any information below is purely informational)
• gst123/riscv64 (0.3.5-4 to 0.3.5-4)
  • Migration status for gst123/riscv64 (0.3.5-4 to 0.3.5-4): Will attempt migration (Any information below is purely informational)
• gstreamermm-1.0/riscv64 (1.10.0+dfsg-4 to 1.10.0+dfsg-4)
  • Migration status for gstreamermm-1.0/riscv64 (1.10.0+dfsg-4 to 1.10.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• gtamsanalyzer.app/riscv64 (0.42-8 to 0.42-8)
  • Migration status for gtamsanalyzer.app/riscv64 (0.42-8 to 0.42-8): Will attempt migration (Any information below is purely informational)
• gtg-trace/riscv64 (0.2-3-2 to 0.2-3-2)
  • Migration status for gtg-trace/riscv64 (0.2-3-2 to 0.2-3-2): Will attempt migration (Any information below is purely informational)
• gtk-chtheme/riscv64 (0.3.1-6.2 to 0.3.1-6.2)
  • Migration status for gtk-chtheme/riscv64 (0.3.1-6.2 to 0.3.1-6.2): Will attempt migration (Any information below is purely informational)
• gtk-im-libthai/riscv64 (0.2.2-2 to 0.2.2-2)
  • Migration status for gtk-im-libthai/riscv64 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
• gtk-layer-shell/riscv64 (0.8.2-1 to 0.8.2-1)
  • Migration status for gtk-layer-shell/riscv64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
• gtk-theme-switch/riscv64 (2.1.0-5 to 2.1.0-5)
  • Migration status for gtk-theme-switch/riscv64 (2.1.0-5 to 2.1.0-5): Will attempt migration (Any information below is purely informational)
• gtk-vnc/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for gtk-vnc/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• gtk2-engines-aurora/riscv64 (1.5.1-4.1 to 1.5.1-4.1)
  • Migration status for gtk2-engines-aurora/riscv64 (1.5.1-4.1 to 1.5.1-4.1): Will attempt migration (Any information below is purely informational)
• gtk2-engines-murrine/riscv64 (0.98.2-4 to 0.98.2-4)
  • Migration status for gtk2-engines-murrine/riscv64 (0.98.2-4 to 0.98.2-4): Will attempt migration (Any information below is purely informational)
• gtk2-engines-oxygen/riscv64 (1.4.6-1.1 to 1.4.6-1.1)
  • Migration status for gtk2-engines-oxygen/riscv64 (1.4.6-1.1 to 1.4.6-1.1): Will attempt migration (Any information below is purely informational)
• gtk2-engines/riscv64 (1:2.20.2-5 to 1:2.20.2-5)
  • Migration status for gtk2-engines/riscv64 (1:2.20.2-5 to 1:2.20.2-5): Will attempt migration (Any information below is purely informational)
• gtk2hs-buildtools/riscv64 (0.13.10.0-1 to 0.13.10.0-1)
  • Migration status for gtk2hs-buildtools/riscv64 (0.13.10.0-1 to 0.13.10.0-1): Will attempt migration (Any information below is purely informational)
• gtkatlantic/riscv64 (0.6.3-2 to 0.6.3-2)
  • Migration status for gtkatlantic/riscv64 (0.6.3-2 to 0.6.3-2): Will attempt migration (Any information below is purely informational)
• gtkballs/riscv64 (3.1.5+git20210713.6e53b66-1 to 3.1.5+git20210713.6e53b66-1)
  • Migration status for gtkballs/riscv64 (3.1.5+git20210713.6e53b66-1 to 3.1.5+git20210713.6e53b66-1): Will attempt migration (Any information below is purely informational)
• gtkcrypto/riscv64 (1.0.2-2 to 1.0.2-2)
  • Migration status for gtkcrypto/riscv64 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• gtkgreet/riscv64 (0.8-1 to 0.8-1)
  • Migration status for gtkgreet/riscv64 (0.8-1 to 0.8-1): Will attempt migration (Any information below is purely informational)
• gtklock/riscv64 (2.1.0-1 to 2.1.0-1)
  • Migration status for gtklock/riscv64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• gtklp/riscv64 (1.3.4-3 to 1.3.4-3)
  • Migration status for gtklp/riscv64 (1.3.4-3 to 1.3.4-3): Will attempt migration (Any information below is purely informational)
• gtkmm2.4/riscv64 (1:2.24.5-5.2 to 1:2.24.5-5.2)
  • Migration status for gtkmm2.4/riscv64 (1:2.24.5-5.2 to 1:2.24.5-5.2): Will attempt migration (Any information below is purely informational)
• gtkmm3.0/riscv64 (3.24.9-1 to 3.24.9-1)
  • Migration status for gtkmm3.0/riscv64 (3.24.9-1 to 3.24.9-1): Will attempt migration (Any information below is purely informational)
• gtkmm4.0/riscv64 (4.10.0-4 to 4.10.0-4)
  • Migration status for gtkmm4.0/riscv64 (4.10.0-4 to 4.10.0-4): Will attempt migration (Any information below is purely informational)
• gtksourceview4/riscv64 (4.8.4-5 to 4.8.4-5)
  • Migration status for gtksourceview4/riscv64 (4.8.4-5 to 4.8.4-5): Will attempt migration (Any information below is purely informational)
• gtkspell/riscv64 (2.0.16-1.3 to 2.0.16-1.3)
  • Migration status for gtkspell/riscv64 (2.0.16-1.3 to 2.0.16-1.3): Will attempt migration (Any information below is purely informational)
• gtkspell3/riscv64 (3.0.10-1 to 3.0.10-1)
  • Migration status for gtkspell3/riscv64 (3.0.10-1 to 3.0.10-1): Will attempt migration (Any information below is purely informational)
• gtkspellmm/riscv64 (3.0.5+dfsg-5 to 3.0.5+dfsg-5)
  • Migration status for gtkspellmm/riscv64 (3.0.5+dfsg-5 to 3.0.5+dfsg-5): Will attempt migration (Any information below is purely informational)
• guichan/riscv64 (0.8.2-21 to 0.8.2-21)
  • Migration status for guichan/riscv64 (0.8.2-21 to 0.8.2-21): Will attempt migration (Any information below is purely informational)
• guifications/riscv64 (2.16-2 to 2.16-2)
  • Migration status for guifications/riscv64 (2.16-2 to 2.16-2): Will attempt migration (Any information below is purely informational)
• guitarix/riscv64 (0.46.0+dfsg-1 to 0.46.0+dfsg-1)
  • Migration status for guitarix/riscv64 (0.46.0+dfsg-1 to 0.46.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• gulkan/riscv64 (0.15.1-2.2 to 0.15.1-2.2)
  • Migration status for gulkan/riscv64 (0.15.1-2.2 to 0.15.1-2.2): Will attempt migration (Any information below is purely informational)
• gunroar/riscv64 (0.15.dfsg1-10 to 0.15.dfsg1-10)
  • Migration status for gunroar/riscv64 (0.15.dfsg1-10 to 0.15.dfsg1-10): Will attempt migration (Any information below is purely informational)
• gupnp-dlna/riscv64 (0.12.0-4 to 0.12.0-4)
  • Migration status for gupnp-dlna/riscv64 (0.12.0-4 to 0.12.0-4): Will attempt migration (Any information below is purely informational)
• gupnp-igd/riscv64 (1.6.0-3 to 1.6.0-3)
  • Migration status for gupnp-igd/riscv64 (1.6.0-3 to 1.6.0-3): Will attempt migration (Any information below is purely informational)
• gupnp/riscv64 (1.6.6-1 to 1.6.6-1)
  • Migration status for gupnp/riscv64 (1.6.6-1 to 1.6.6-1): Will attempt migration (Any information below is purely informational)
• gvidm/riscv64 (0.8-15 to 0.8-15)
  • Migration status for gvidm/riscv64 (0.8-15 to 0.8-15): Will attempt migration (Any information below is purely informational)
• gwaei/riscv64 (3.6.2-9.2 to 3.6.2-9.2)
  • Migration status for gwaei/riscv64 (3.6.2-9.2 to 3.6.2-9.2): Will attempt migration (Any information below is purely informational)
• gwaterfall/riscv64 (0.1-5.2 to 0.1-5.2)
  • Migration status for gwaterfall/riscv64 (0.1-5.2 to 0.1-5.2): Will attempt migration (Any information below is purely informational)
• gweled/riscv64 (1.0~beta1-1 to 1.0~beta1-1)
  • Migration status for gweled/riscv64 (1.0~beta1-1 to 1.0~beta1-1): Will attempt migration (Any information below is purely informational)
• gwenview/amd64 (4:23.04.2-2 to 4:23.04.2-2)
  • Migration status for gwenview/amd64 (4:23.04.2-2 to 4:23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gwenview/amd64 exiv2
• gwenview/arm64 (4:23.04.2-2 to 4:23.04.2-2)
  • Migration status for gwenview/arm64 (4:23.04.2-2 to 4:23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gwenview/arm64 exiv2
• gwenview/armel (4:23.04.2-2 to 4:23.04.2-2)
  • Migration status for gwenview/armel (4:23.04.2-2 to 4:23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gwenview/armel exiv2
• gwenview/armhf (4:23.04.2-2 to 4:23.04.2-2)
  • Migration status for gwenview/armhf (4:23.04.2-2 to 4:23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gwenview/armhf exiv2
• gwenview/i386 (4:23.04.2-2 to 4:23.04.2-2)
  • Migration status for gwenview/i386 (4:23.04.2-2 to 4:23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gwenview/i386 exiv2
• gwenview/mips64el (4:23.04.2-2 to 4:23.04.2-2)
  • Migration status for gwenview/mips64el (4:23.04.2-2 to 4:23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gwenview/mips64el exiv2
• gwenview/ppc64el (4:23.04.2-2 to 4:23.04.2-2)
  • Migration status for gwenview/ppc64el (4:23.04.2-2 to 4:23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gwenview/ppc64el exiv2
• gwenview/s390x (4:23.04.2-2 to 4:23.04.2-2)
  • Migration status for gwenview/s390x (4:23.04.2-2 to 4:23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: gwenview/s390x exiv2
• gworldclock/riscv64 (1.4.4-11.1 to 1.4.4-11.1)
  • Migration status for gworldclock/riscv64 (1.4.4-11.1 to 1.4.4-11.1): Will attempt migration (Any information below is purely informational)
• gxkb/riscv64 (0.9.5-1 to 0.9.5-1)
  • Migration status for gxkb/riscv64 (0.9.5-1 to 0.9.5-1): Will attempt migration (Any information below is purely informational)
• gxmessage/riscv64 (3.4.3-2 to 3.4.3-2)
  • Migration status for gxmessage/riscv64 (3.4.3-2 to 3.4.3-2): Will attempt migration (Any information below is purely informational)
• gxneur/riscv64 (0.20.0-2.2 to 0.20.0-2.2)
  • Migration status for gxneur/riscv64 (0.20.0-2.2 to 0.20.0-2.2): Will attempt migration (Any information below is purely informational)
• gxtuner/riscv64 (3.0-3 to 3.0-3)
  • Migration status for gxtuner/riscv64 (3.0-3 to 3.0-3): Will attempt migration (Any information below is purely informational)
• gyrus/riscv64 (0.4.2-1.1 to 0.4.2-1.1)
  • Migration status for gyrus/riscv64 (0.4.2-1.1 to 0.4.2-1.1): Will attempt migration (Any information below is purely informational)
• hannah-foo2zjs/riscv64 (1:6 to 1:6)
  • Migration status for hannah-foo2zjs/riscv64 (1:6 to 1:6): Will attempt migration (Any information below is purely informational)
• haruna/riscv64 (0.12.3-1 to 0.12.3-1)
  • Migration status for haruna/riscv64 (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
• harvid/riscv64 (0.9.1-1 to 0.9.1-1)
  • Migration status for harvid/riscv64 (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• hash-slinger/riscv64 (3.1-1.2 to 3.1-1.2)
  • Migration status for hash-slinger/riscv64 (3.1-1.2 to 3.1-1.2): Will attempt migration (Any information below is purely informational)
• hashcheck/riscv64 (1.0.0-2 to 1.0.0-2)
  • Migration status for hashcheck/riscv64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• haskell-abstract-deque/riscv64 (0.3-12 to 0.3-12)
  • Migration status for haskell-abstract-deque/riscv64 (0.3-12 to 0.3-12): Will attempt migration (Any information below is purely informational)
• haskell-abstract-par/riscv64 (0.3.3-12 to 0.3.3-12)
  • Migration status for haskell-abstract-par/riscv64 (0.3.3-12 to 0.3.3-12): Will attempt migration (Any information below is purely informational)
• haskell-acid-state/riscv64 (0.16.1.3-1 to 0.16.1.3-1)
  • Migration status for haskell-acid-state/riscv64 (0.16.1.3-1 to 0.16.1.3-1): Will attempt migration (Any information below is purely informational)
• haskell-active/riscv64 (0.2.0.18-1 to 0.2.0.18-1)
  • Migration status for haskell-active/riscv64 (0.2.0.18-1 to 0.2.0.18-1): Will attempt migration (Any information below is purely informational)
• haskell-adjunctions/riscv64 (4.4.2-2 to 4.4.2-2)
  • Migration status for haskell-adjunctions/riscv64 (4.4.2-2 to 4.4.2-2): Will attempt migration (Any information below is purely informational)
• haskell-aeson-diff/riscv64 (1.1.0.13-2 to 1.1.0.13-2)
  • Migration status for haskell-aeson-diff/riscv64 (1.1.0.13-2 to 1.1.0.13-2): Will attempt migration (Any information below is purely informational)
• haskell-aeson-extra/riscv64 (0.5.1.2-1 to 0.5.1.2-1)
  • Migration status for haskell-aeson-extra/riscv64 (0.5.1.2-1 to 0.5.1.2-1): Will attempt migration (Any information below is purely informational)
• haskell-aeson-pretty/riscv64 (0.8.9-2 to 0.8.9-2)
  • Migration status for haskell-aeson-pretty/riscv64 (0.8.9-2 to 0.8.9-2): Will attempt migration (Any information below is purely informational)
• haskell-aeson-qq/riscv64 (0.8.4-2 to 0.8.4-2)
  • Migration status for haskell-aeson-qq/riscv64 (0.8.4-2 to 0.8.4-2): Will attempt migration (Any information below is purely informational)
• haskell-aeson/riscv64 (2.1.2.1-5 to 2.1.2.1-5)
  • Migration status for haskell-aeson/riscv64 (2.1.2.1-5 to 2.1.2.1-5): Will attempt migration (Any information below is purely informational)
• haskell-alsa-core/riscv64 (0.5.0.1-8 to 0.5.0.1-8)
  • Migration status for haskell-alsa-core/riscv64 (0.5.0.1-8 to 0.5.0.1-8): Will attempt migration (Any information below is purely informational)
• haskell-alsa-mixer/riscv64 (0.3.0-4 to 0.3.0-4)
  • Migration status for haskell-alsa-mixer/riscv64 (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• haskell-annotated-wl-pprint/riscv64 (0.7.0-6 to 0.7.0-6)
  • Migration status for haskell-annotated-wl-pprint/riscv64 (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• haskell-ansi-terminal-types/riscv64 (0.11.5-2 to 0.11.5-2)
  • Migration status for haskell-ansi-terminal-types/riscv64 (0.11.5-2 to 0.11.5-2): Will attempt migration (Any information below is purely informational)
• haskell-ansi-terminal/riscv64 (0.11.5-1 to 0.11.5-1)
  • Migration status for haskell-ansi-terminal/riscv64 (0.11.5-1 to 0.11.5-1): Will attempt migration (Any information below is purely informational)
• haskell-ansi-wl-pprint/riscv64 (0.6.9-6 to 0.6.9-6)
  • Migration status for haskell-ansi-wl-pprint/riscv64 (0.6.9-6 to 0.6.9-6): Will attempt migration (Any information below is purely informational)
• haskell-ap-normalize/riscv64 (0.1.0.1-3 to 0.1.0.1-3)
  • Migration status for haskell-ap-normalize/riscv64 (0.1.0.1-3 to 0.1.0.1-3): Will attempt migration (Any information below is purely informational)
• haskell-appar/riscv64 (0.1.8-4 to 0.1.8-4)
  • Migration status for haskell-appar/riscv64 (0.1.8-4 to 0.1.8-4): Will attempt migration (Any information below is purely informational)
• haskell-argon2/riscv64 (1.3.0.1-10 to 1.3.0.1-10)
  • Migration status for haskell-argon2/riscv64 (1.3.0.1-10 to 1.3.0.1-10): Will attempt migration (Any information below is purely informational)
• haskell-arrows/riscv64 (0.4.4.2-5 to 0.4.4.2-5)
  • Migration status for haskell-arrows/riscv64 (0.4.4.2-5 to 0.4.4.2-5): Will attempt migration (Any information below is purely informational)
• haskell-asn1-encoding/riscv64 (0.9.6-3 to 0.9.6-3)
  • Migration status for haskell-asn1-encoding/riscv64 (0.9.6-3 to 0.9.6-3): Will attempt migration (Any information below is purely informational)
• haskell-asn1-parse/riscv64 (0.9.5-4 to 0.9.5-4)
  • Migration status for haskell-asn1-parse/riscv64 (0.9.5-4 to 0.9.5-4): Will attempt migration (Any information below is purely informational)
• haskell-asn1-types/riscv64 (0.3.4-3 to 0.3.4-3)
  • Migration status for haskell-asn1-types/riscv64 (0.3.4-3 to 0.3.4-3): Will attempt migration (Any information below is purely informational)
• haskell-assert-failure/riscv64 (0.1.3.0-1 to 0.1.3.0-1)
  • Migration status for haskell-assert-failure/riscv64 (0.1.3.0-1 to 0.1.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-assoc/riscv64 (1.1-1 to 1.1-1)
  • Migration status for haskell-assoc/riscv64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-async/riscv64 (2.2.4-4 to 2.2.4-4)
  • Migration status for haskell-async/riscv64 (2.2.4-4 to 2.2.4-4): Will attempt migration (Any information below is purely informational)
• haskell-atomic-write/riscv64 (0.2.0.7-4 to 0.2.0.7-4)
  • Migration status for haskell-atomic-write/riscv64 (0.2.0.7-4 to 0.2.0.7-4): Will attempt migration (Any information below is purely informational)
• haskell-attoparsec-aeson/riscv64 (2.1.0.0-2 to 2.1.0.0-2)
  • Migration status for haskell-attoparsec-aeson/riscv64 (2.1.0.0-2 to 2.1.0.0-2): Will attempt migration (Any information below is purely informational)
• haskell-attoparsec-iso8601/riscv64 (1.1.0.0-1 to 1.1.0.0-1)
  • Migration status for haskell-attoparsec-iso8601/riscv64 (1.1.0.0-1 to 1.1.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-attoparsec/riscv64 (0.14.4-3 to 0.14.4-3)
  • Migration status for haskell-attoparsec/riscv64 (0.14.4-3 to 0.14.4-3): Will attempt migration (Any information below is purely informational)
• haskell-authenticate-oauth/riscv64 (1.7-2 to 1.7-2)
  • Migration status for haskell-authenticate-oauth/riscv64 (1.7-2 to 1.7-2): Will attempt migration (Any information below is purely informational)
• haskell-authenticate/riscv64 (1.3.5.2-1 to 1.3.5.2-1)
  • Migration status for haskell-authenticate/riscv64 (1.3.5.2-1 to 1.3.5.2-1): Will attempt migration (Any information below is purely informational)
• haskell-auto-update/riscv64 (0.1.6-3 to 0.1.6-3)
  • Migration status for haskell-auto-update/riscv64 (0.1.6-3 to 0.1.6-3): Will attempt migration (Any information below is purely informational)
• haskell-aws/riscv64 (0.24.1-1 to 0.24.1-1)
  • Migration status for haskell-aws/riscv64 (0.24.1-1 to 0.24.1-1): Will attempt migration (Any information below is purely informational)
• haskell-barbies/riscv64 (2.0.4.0-3 to 2.0.4.0-3)
  • Migration status for haskell-barbies/riscv64 (2.0.4.0-3 to 2.0.4.0-3): Will attempt migration (Any information below is purely informational)
• haskell-base-compat-batteries/riscv64 (0.12.3-1 to 0.12.3-1)
  • Migration status for haskell-base-compat-batteries/riscv64 (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
• haskell-base-compat/riscv64 (0.12.3-1 to 0.12.3-1)
  • Migration status for haskell-base-compat/riscv64 (0.12.3-1 to 0.12.3-1): Will attempt migration (Any information below is purely informational)
• haskell-base-orphans/riscv64 (0.9.1-1 to 0.9.1-1)
  • Migration status for haskell-base-orphans/riscv64 (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• haskell-base-prelude/riscv64 (1.6.1.1-1 to 1.6.1.1-1)
  • Migration status for haskell-base-prelude/riscv64 (1.6.1.1-1 to 1.6.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-base-unicode-symbols/riscv64 (0.2.4.2-3 to 0.2.4.2-3)
  • Migration status for haskell-base-unicode-symbols/riscv64 (0.2.4.2-3 to 0.2.4.2-3): Will attempt migration (Any information below is purely informational)
• haskell-base16-bytestring/riscv64 (1.0.2.0-2 to 1.0.2.0-2)
  • Migration status for haskell-base16-bytestring/riscv64 (1.0.2.0-2 to 1.0.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-base64-bytestring/riscv64 (1.2.1.0-2 to 1.2.1.0-2)
  • Migration status for haskell-base64-bytestring/riscv64 (1.2.1.0-2 to 1.2.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-basement/riscv64 (0.0.16-2 to 0.0.16-2)
  • Migration status for haskell-basement/riscv64 (0.0.16-2 to 0.0.16-2): Will attempt migration (Any information below is purely informational)
• haskell-basic-prelude/riscv64 (0.7.0-6 to 0.7.0-6)
  • Migration status for haskell-basic-prelude/riscv64 (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• haskell-bencode/riscv64 (0.6.1.1-3 to 0.6.1.1-3)
  • Migration status for haskell-bencode/riscv64 (0.6.1.1-3 to 0.6.1.1-3): Will attempt migration (Any information below is purely informational)
• haskell-bifunctors/riscv64 (5.5.15-1 to 5.5.15-1)
  • Migration status for haskell-bifunctors/riscv64 (5.5.15-1 to 5.5.15-1): Will attempt migration (Any information below is purely informational)
• haskell-bimap/riscv64 (0.5.0-2 to 0.5.0-2)
  • Migration status for haskell-bimap/riscv64 (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• haskell-binary-conduit/riscv64 (1.3.1-4 to 1.3.1-4)
  • Migration status for haskell-binary-conduit/riscv64 (1.3.1-4 to 1.3.1-4): Will attempt migration (Any information below is purely informational)
• haskell-binary-instances/riscv64 (1.0.4-1 to 1.0.4-1)
  • Migration status for haskell-binary-instances/riscv64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• haskell-binary-orphans/riscv64 (1.0.4.1-2 to 1.0.4.1-2)
  • Migration status for haskell-binary-orphans/riscv64 (1.0.4.1-2 to 1.0.4.1-2): Will attempt migration (Any information below is purely informational)
• haskell-bindings-dsl/riscv64 (1.0.25-5 to 1.0.25-5)
  • Migration status for haskell-bindings-dsl/riscv64 (1.0.25-5 to 1.0.25-5): Will attempt migration (Any information below is purely informational)
• haskell-bitvec/riscv64 (1.1.5.0-3 to 1.1.5.0-3)
  • Migration status for haskell-bitvec/riscv64 (1.1.5.0-3 to 1.1.5.0-3): Will attempt migration (Any information below is purely informational)
• haskell-bitwise/riscv64 (1.0.0.1-3 to 1.0.0.1-3)
  • Migration status for haskell-bitwise/riscv64 (1.0.0.1-3 to 1.0.0.1-3): Will attempt migration (Any information below is purely informational)
• haskell-blaze-builder/riscv64 (0.4.2.3-1 to 0.4.2.3-1)
  • Migration status for haskell-blaze-builder/riscv64 (0.4.2.3-1 to 0.4.2.3-1): Will attempt migration (Any information below is purely informational)
• haskell-blaze-html/riscv64 (0.9.1.2-3 to 0.9.1.2-3)
  • Migration status for haskell-blaze-html/riscv64 (0.9.1.2-3 to 0.9.1.2-3): Will attempt migration (Any information below is purely informational)
• haskell-blaze-markup/riscv64 (0.8.3.0-1 to 0.8.3.0-1)
  • Migration status for haskell-blaze-markup/riscv64 (0.8.3.0-1 to 0.8.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-blaze-svg/riscv64 (0.3.7-1 to 0.3.7-1)
  • Migration status for haskell-blaze-svg/riscv64 (0.3.7-1 to 0.3.7-1): Will attempt migration (Any information below is purely informational)
• haskell-blaze-textual/riscv64 (0.2.3.1-1 to 0.2.3.1-1)
  • Migration status for haskell-blaze-textual/riscv64 (0.2.3.1-1 to 0.2.3.1-1): Will attempt migration (Any information below is purely informational)
• haskell-bloomfilter/riscv64 (2.0.1.2-2 to 2.0.1.2-2)
  • Migration status for haskell-bloomfilter/riscv64 (2.0.1.2-2 to 2.0.1.2-2): Will attempt migration (Any information below is purely informational)
• haskell-bmp/riscv64 (1.2.6.3-7 to 1.2.6.3-7)
  • Migration status for haskell-bmp/riscv64 (1.2.6.3-7 to 1.2.6.3-7): Will attempt migration (Any information below is purely informational)
• haskell-bool-extras/riscv64 (0.4.0-11 to 0.4.0-11)
  • Migration status for haskell-bool-extras/riscv64 (0.4.0-11 to 0.4.0-11): Will attempt migration (Any information below is purely informational)
• haskell-boolean/riscv64 (0.2.4-6 to 0.2.4-6)
  • Migration status for haskell-boolean/riscv64 (0.2.4-6 to 0.2.4-6): Will attempt migration (Any information below is purely informational)
• haskell-boomerang/riscv64 (1.4.9-1 to 1.4.9-1)
  • Migration status for haskell-boomerang/riscv64 (1.4.9-1 to 1.4.9-1): Will attempt migration (Any information below is purely informational)
• haskell-boring/riscv64 (0.2.1-1 to 0.2.1-1)
  • Migration status for haskell-boring/riscv64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• haskell-boundedchan/riscv64 (1.0.3.0-12 to 1.0.3.0-12)
  • Migration status for haskell-boundedchan/riscv64 (1.0.3.0-12 to 1.0.3.0-12): Will attempt migration (Any information below is purely informational)
• haskell-boxes/riscv64 (0.1.5-5 to 0.1.5-5)
  • Migration status for haskell-boxes/riscv64 (0.1.5-5 to 0.1.5-5): Will attempt migration (Any information below is purely informational)
• haskell-brainfuck/riscv64 (0.1.0.3-9 to 0.1.0.3-9)
  • Migration status for haskell-brainfuck/riscv64 (0.1.0.3-9 to 0.1.0.3-9): Will attempt migration (Any information below is purely informational)
• haskell-brick/riscv64 (1.9-1 to 1.9-1)
  • Migration status for haskell-brick/riscv64 (1.9-1 to 1.9-1): Will attempt migration (Any information below is purely informational)
• haskell-broadcast-chan/riscv64 (0.2.1.2-2 to 0.2.1.2-2)
  • Migration status for haskell-broadcast-chan/riscv64 (0.2.1.2-2 to 0.2.1.2-2): Will attempt migration (Any information below is purely informational)
• haskell-bsb-http-chunked/riscv64 (0.0.0.4-5 to 0.0.0.4-5)
  • Migration status for haskell-bsb-http-chunked/riscv64 (0.0.0.4-5 to 0.0.0.4-5): Will attempt migration (Any information below is purely informational)
• haskell-bv-sized/riscv64 (1.0.5-1 to 1.0.5-1)
  • Migration status for haskell-bv-sized/riscv64 (1.0.5-1 to 1.0.5-1): Will attempt migration (Any information below is purely informational)
• haskell-byte-order/riscv64 (0.1.3.0-2 to 0.1.3.0-2)
  • Migration status for haskell-byte-order/riscv64 (0.1.3.0-2 to 0.1.3.0-2): Will attempt migration (Any information below is purely informational)
• haskell-byteable/riscv64 (0.1.1-12 to 0.1.1-12)
  • Migration status for haskell-byteable/riscv64 (0.1.1-12 to 0.1.1-12): Will attempt migration (Any information below is purely informational)
• haskell-bytedump/riscv64 (1.0-12 to 1.0-12)
  • Migration status for haskell-bytedump/riscv64 (1.0-12 to 1.0-12): Will attempt migration (Any information below is purely informational)
• haskell-byteorder/riscv64 (1.0.4-12 to 1.0.4-12)
  • Migration status for haskell-byteorder/riscv64 (1.0.4-12 to 1.0.4-12): Will attempt migration (Any information below is purely informational)
• haskell-bytes/riscv64 (0.17.3-1 to 0.17.3-1)
  • Migration status for haskell-bytes/riscv64 (0.17.3-1 to 0.17.3-1): Will attempt migration (Any information below is purely informational)
• haskell-bytestring-conversion/riscv64 (0.3.2-2 to 0.3.2-2)
  • Migration status for haskell-bytestring-conversion/riscv64 (0.3.2-2 to 0.3.2-2): Will attempt migration (Any information below is purely informational)
• haskell-bytestring-lexing/riscv64 (0.5.0.10-1 to 0.5.0.10-1)
  • Migration status for haskell-bytestring-lexing/riscv64 (0.5.0.10-1 to 0.5.0.10-1): Will attempt migration (Any information below is purely informational)
• haskell-bytestring-progress/riscv64 (1.4-4 to 1.4-4)
  • Migration status for haskell-bytestring-progress/riscv64 (1.4-4 to 1.4-4): Will attempt migration (Any information below is purely informational)
• haskell-bytestring-to-vector/riscv64 (0.3.0.1-5 to 0.3.0.1-5)
  • Migration status for haskell-bytestring-to-vector/riscv64 (0.3.0.1-5 to 0.3.0.1-5): Will attempt migration (Any information below is purely informational)
• haskell-bz2/riscv64 (1.0.1.0-2 to 1.0.1.0-2)
  • Migration status for haskell-bz2/riscv64 (1.0.1.0-2 to 1.0.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-bzlib/riscv64 (0.5.1.0-3 to 0.5.1.0-3)
  • Migration status for haskell-bzlib/riscv64 (0.5.1.0-3 to 0.5.1.0-3): Will attempt migration (Any information below is purely informational)
• haskell-cabal-doctest/riscv64 (1.0.9-2 to 1.0.9-2)
  • Migration status for haskell-cabal-doctest/riscv64 (1.0.9-2 to 1.0.9-2): Will attempt migration (Any information below is purely informational)
• haskell-cabal-install-solver/riscv64 (3.8.1.0-2 to 3.8.1.0-2)
  • Migration status for haskell-cabal-install-solver/riscv64 (3.8.1.0-2 to 3.8.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-cabal-install/riscv64 (3.8.1.0-1 to 3.8.1.0-1)
  • Migration status for haskell-cabal-install/riscv64 (3.8.1.0-1 to 3.8.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-cairo/riscv64 (0.13.10.0-1 to 0.13.10.0-1)
  • Migration status for haskell-cairo/riscv64 (0.13.10.0-1 to 0.13.10.0-1): Will attempt migration (Any information below is purely informational)
• haskell-call-stack/riscv64 (0.4.0-2 to 0.4.0-2)
  • Migration status for haskell-call-stack/riscv64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• haskell-casa-client/riscv64 (0.0.2-1 to 0.0.2-1)
  • Migration status for haskell-casa-client/riscv64 (0.0.2-1 to 0.0.2-1): Will attempt migration (Any information below is purely informational)
• haskell-casa-types/riscv64 (0.0.2-2 to 0.0.2-2)
  • Migration status for haskell-casa-types/riscv64 (0.0.2-2 to 0.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-case-insensitive/riscv64 (1.2.1.0-4 to 1.2.1.0-4)
  • Migration status for haskell-case-insensitive/riscv64 (1.2.1.0-4 to 1.2.1.0-4): Will attempt migration (Any information below is purely informational)
• haskell-cassava-megaparsec/riscv64 (2.0.4-3 to 2.0.4-3)
  • Migration status for haskell-cassava-megaparsec/riscv64 (2.0.4-3 to 2.0.4-3): Will attempt migration (Any information below is purely informational)
• haskell-cassava/riscv64 (0.5.3.0-2 to 0.5.3.0-2)
  • Migration status for haskell-cassava/riscv64 (0.5.3.0-2 to 0.5.3.0-2): Will attempt migration (Any information below is purely informational)
• haskell-categories/riscv64 (1.0.7-11 to 1.0.7-11)
  • Migration status for haskell-categories/riscv64 (1.0.7-11 to 1.0.7-11): Will attempt migration (Any information below is purely informational)
• haskell-cereal-conduit/riscv64 (0.8.0-6 to 0.8.0-6)
  • Migration status for haskell-cereal-conduit/riscv64 (0.8.0-6 to 0.8.0-6): Will attempt migration (Any information below is purely informational)
• haskell-cereal-vector/riscv64 (0.2.0.1-6 to 0.2.0.1-6)
  • Migration status for haskell-cereal-vector/riscv64 (0.2.0.1-6 to 0.2.0.1-6): Will attempt migration (Any information below is purely informational)
• haskell-cereal/riscv64 (0.5.8.3-2 to 0.5.8.3-2)
  • Migration status for haskell-cereal/riscv64 (0.5.8.3-2 to 0.5.8.3-2): Will attempt migration (Any information below is purely informational)
• haskell-cgi/riscv64 (3001.5.0.1-1 to 3001.5.0.1-1)
  • Migration status for haskell-cgi/riscv64 (3001.5.0.1-1 to 3001.5.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-charset/riscv64 (0.3.10-1 to 0.3.10-1)
  • Migration status for haskell-charset/riscv64 (0.3.10-1 to 0.3.10-1): Will attempt migration (Any information below is purely informational)
• haskell-chart-cairo/riscv64 (1.9.3-3 to 1.9.3-3)
  • Migration status for haskell-chart-cairo/riscv64 (1.9.3-3 to 1.9.3-3): Will attempt migration (Any information below is purely informational)
• haskell-chart/riscv64 (1.9.4-2 to 1.9.4-2)
  • Migration status for haskell-chart/riscv64 (1.9.4-2 to 1.9.4-2): Will attempt migration (Any information below is purely informational)
• haskell-chasingbottoms/riscv64 (1.3.1.12-3 to 1.3.1.12-3)
  • Migration status for haskell-chasingbottoms/riscv64 (1.3.1.12-3 to 1.3.1.12-3): Will attempt migration (Any information below is purely informational)
• haskell-chimera/riscv64 (0.3.3.0-1 to 0.3.3.0-1)
  • Migration status for haskell-chimera/riscv64 (0.3.3.0-1 to 0.3.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-chunked-data/riscv64 (0.3.1-6 to 0.3.1-6)
  • Migration status for haskell-chunked-data/riscv64 (0.3.1-6 to 0.3.1-6): Will attempt migration (Any information below is purely informational)
• haskell-cipher-camellia/riscv64 (0.0.2-12 to 0.0.2-12)
  • Migration status for haskell-cipher-camellia/riscv64 (0.0.2-12 to 0.0.2-12): Will attempt migration (Any information below is purely informational)
• haskell-citeproc/riscv64 (0.8.1-1 to 0.8.1-1)
  • Migration status for haskell-citeproc/riscv64 (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• haskell-clash-ghc/riscv64 (1.8.1-1 to 1.8.1-1)
  • Migration status for haskell-clash-ghc/riscv64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• haskell-clash-lib/riscv64 (1.8.1-1 to 1.8.1-1)
  • Migration status for haskell-clash-lib/riscv64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• haskell-clash-prelude/riscv64 (1.8.1-1 to 1.8.1-1)
  • Migration status for haskell-clash-prelude/riscv64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• haskell-classy-prelude-conduit/riscv64 (1.5.0-4 to 1.5.0-4)
  • Migration status for haskell-classy-prelude-conduit/riscv64 (1.5.0-4 to 1.5.0-4): Will attempt migration (Any information below is purely informational)
• haskell-classy-prelude/riscv64 (1.5.0.3-1 to 1.5.0.3-1)
  • Migration status for haskell-classy-prelude/riscv64 (1.5.0.3-1 to 1.5.0.3-1): Will attempt migration (Any information below is purely informational)
• haskell-clientsession/riscv64 (0.9.2.0-1 to 0.9.2.0-1)
  • Migration status for haskell-clientsession/riscv64 (0.9.2.0-1 to 0.9.2.0-1): Will attempt migration (Any information below is purely informational)
• haskell-clock/riscv64 (0.8.4-1 to 0.8.4-1)
  • Migration status for haskell-clock/riscv64 (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• haskell-cmark-gfm/riscv64 (0.2.5+ds1-2 to 0.2.5+ds1-2)
  • Migration status for haskell-cmark-gfm/riscv64 (0.2.5+ds1-2 to 0.2.5+ds1-2): Will attempt migration (Any information below is purely informational)
• haskell-cmark/riscv64 (0.6.1+ds1-1 to 0.6.1+ds1-1)
  • Migration status for haskell-cmark/riscv64 (0.6.1+ds1-1 to 0.6.1+ds1-1): Will attempt migration (Any information below is purely informational)
• haskell-cmdargs/riscv64 (0.10.22-1 to 0.10.22-1)
  • Migration status for haskell-cmdargs/riscv64 (0.10.22-1 to 0.10.22-1): Will attempt migration (Any information below is purely informational)
• haskell-code-page/riscv64 (0.2.1-2 to 0.2.1-2)
  • Migration status for haskell-code-page/riscv64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• haskell-colour/riscv64 (2.3.6-2 to 2.3.6-2)
  • Migration status for haskell-colour/riscv64 (2.3.6-2 to 2.3.6-2): Will attempt migration (Any information below is purely informational)
• haskell-commonmark-extensions/riscv64 (0.2.3.6-1 to 0.2.3.6-1)
  • Migration status for haskell-commonmark-extensions/riscv64 (0.2.3.6-1 to 0.2.3.6-1): Will attempt migration (Any information below is purely informational)
• haskell-commonmark-pandoc/riscv64 (0.2.1.3-1 to 0.2.1.3-1)
  • Migration status for haskell-commonmark-pandoc/riscv64 (0.2.1.3-1 to 0.2.1.3-1): Will attempt migration (Any information below is purely informational)
• haskell-commonmark/riscv64 (0.2.3-2 to 0.2.3-2)
  • Migration status for haskell-commonmark/riscv64 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• haskell-commutative-semigroups/riscv64 (0.1.0.1-2 to 0.1.0.1-2)
  • Migration status for haskell-commutative-semigroups/riscv64 (0.1.0.1-2 to 0.1.0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-comonad/riscv64 (5.0.8-2 to 5.0.8-2)
  • Migration status for haskell-comonad/riscv64 (5.0.8-2 to 5.0.8-2): Will attempt migration (Any information below is purely informational)
• haskell-concurrent-extra/riscv64 (0.7.0.12-3 to 0.7.0.12-3)
  • Migration status for haskell-concurrent-extra/riscv64 (0.7.0.12-3 to 0.7.0.12-3): Will attempt migration (Any information below is purely informational)
• haskell-concurrent-output/riscv64 (1.10.20-1 to 1.10.20-1)
  • Migration status for haskell-concurrent-output/riscv64 (1.10.20-1 to 1.10.20-1): Will attempt migration (Any information below is purely informational)
• haskell-concurrent-supply/riscv64 (0.1.8-8 to 0.1.8-8)
  • Migration status for haskell-concurrent-supply/riscv64 (0.1.8-8 to 0.1.8-8): Will attempt migration (Any information below is purely informational)
• haskell-cond/riscv64 (0.4.1.1-11 to 0.4.1.1-11)
  • Migration status for haskell-cond/riscv64 (0.4.1.1-11 to 0.4.1.1-11): Will attempt migration (Any information below is purely informational)
• haskell-conduit-extra/riscv64 (1.3.6-2 to 1.3.6-2)
  • Migration status for haskell-conduit-extra/riscv64 (1.3.6-2 to 1.3.6-2): Will attempt migration (Any information below is purely informational)
• haskell-conduit/riscv64 (1.3.5-1 to 1.3.5-1)
  • Migration status for haskell-conduit/riscv64 (1.3.5-1 to 1.3.5-1): Will attempt migration (Any information below is purely informational)
• haskell-config-ini/riscv64 (0.2.6.0-1 to 0.2.6.0-1)
  • Migration status for haskell-config-ini/riscv64 (0.2.6.0-1 to 0.2.6.0-1): Will attempt migration (Any information below is purely informational)
• haskell-config-schema/riscv64 (1.3.0.0-2 to 1.3.0.0-2)
  • Migration status for haskell-config-schema/riscv64 (1.3.0.0-2 to 1.3.0.0-2): Will attempt migration (Any information below is purely informational)
• haskell-config-value/riscv64 (0.8.3-3 to 0.8.3-3)
  • Migration status for haskell-config-value/riscv64 (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
• haskell-configfile/riscv64 (1.1.4-11 to 1.1.4-11)
  • Migration status for haskell-configfile/riscv64 (1.1.4-11 to 1.1.4-11): Will attempt migration (Any information below is purely informational)
• haskell-configurator/riscv64 (0.3.0.0-11 to 0.3.0.0-11)
  • Migration status for haskell-configurator/riscv64 (0.3.0.0-11 to 0.3.0.0-11): Will attempt migration (Any information below is purely informational)
• haskell-connection/riscv64 (0.3.1-4 to 0.3.1-4)
  • Migration status for haskell-connection/riscv64 (0.3.1-4 to 0.3.1-4): Will attempt migration (Any information below is purely informational)
• haskell-constraints-extras/riscv64 (0.4.0.0-1 to 0.4.0.0-1)
  • Migration status for haskell-constraints-extras/riscv64 (0.4.0.0-1 to 0.4.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-constraints/riscv64 (0.13.4-2 to 0.13.4-2)
  • Migration status for haskell-constraints/riscv64 (0.13.4-2 to 0.13.4-2): Will attempt migration (Any information below is purely informational)
• haskell-contravariant-extras/riscv64 (0.3.5.3-2 to 0.3.5.3-2)
  • Migration status for haskell-contravariant-extras/riscv64 (0.3.5.3-2 to 0.3.5.3-2): Will attempt migration (Any information below is purely informational)
• haskell-contravariant/riscv64 (1.5.5-2 to 1.5.5-2)
  • Migration status for haskell-contravariant/riscv64 (1.5.5-2 to 1.5.5-2): Will attempt migration (Any information below is purely informational)
• haskell-control-monad-free/riscv64 (0.6.2-5 to 0.6.2-5)
  • Migration status for haskell-control-monad-free/riscv64 (0.6.2-5 to 0.6.2-5): Will attempt migration (Any information below is purely informational)
• haskell-control-monad-loop/riscv64 (0.1-13 to 0.1-13)
  • Migration status for haskell-control-monad-loop/riscv64 (0.1-13 to 0.1-13): Will attempt migration (Any information below is purely informational)
• haskell-convertible/riscv64 (1.1.1.1-2 to 1.1.1.1-2)
  • Migration status for haskell-convertible/riscv64 (1.1.1.1-2 to 1.1.1.1-2): Will attempt migration (Any information below is purely informational)
• haskell-cookie/riscv64 (0.4.6-1 to 0.4.6-1)
  • Migration status for haskell-cookie/riscv64 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• haskell-cpu/riscv64 (0.1.2-12 to 0.1.2-12)
  • Migration status for haskell-cpu/riscv64 (0.1.2-12 to 0.1.2-12): Will attempt migration (Any information below is purely informational)
• haskell-criterion-measurement/riscv64 (0.2.1.0-1 to 0.2.1.0-1)
  • Migration status for haskell-criterion-measurement/riscv64 (0.2.1.0-1 to 0.2.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-criterion/riscv64 (1.6.1.0-1 to 1.6.1.0-1)
  • Migration status for haskell-criterion/riscv64 (1.6.1.0-1 to 1.6.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-crypto-api/riscv64 (0.13.3-5 to 0.13.3-5)
  • Migration status for haskell-crypto-api/riscv64 (0.13.3-5 to 0.13.3-5): Will attempt migration (Any information below is purely informational)
• haskell-crypto-cipher-tests/riscv64 (0.0.11-13 to 0.0.11-13)
  • Migration status for haskell-crypto-cipher-tests/riscv64 (0.0.11-13 to 0.0.11-13): Will attempt migration (Any information below is purely informational)
• haskell-crypto-cipher-types/riscv64 (0.0.9-12 to 0.0.9-12)
  • Migration status for haskell-crypto-cipher-types/riscv64 (0.0.9-12 to 0.0.9-12): Will attempt migration (Any information below is purely informational)
• haskell-crypto-pubkey-types/riscv64 (0.4.3-12 to 0.4.3-12)
  • Migration status for haskell-crypto-pubkey-types/riscv64 (0.4.3-12 to 0.4.3-12): Will attempt migration (Any information below is purely informational)
• haskell-crypto-random-api/riscv64 (0.2.0-13 to 0.2.0-13)
  • Migration status for haskell-crypto-random-api/riscv64 (0.2.0-13 to 0.2.0-13): Will attempt migration (Any information below is purely informational)
• haskell-crypto-random/riscv64 (0.0.9-11 to 0.0.9-11)
  • Migration status for haskell-crypto-random/riscv64 (0.0.9-11 to 0.0.9-11): Will attempt migration (Any information below is purely informational)
• haskell-cryptohash-conduit/riscv64 (0.1.1-13 to 0.1.1-13)
  • Migration status for haskell-cryptohash-conduit/riscv64 (0.1.1-13 to 0.1.1-13): Will attempt migration (Any information below is purely informational)
• haskell-cryptohash-cryptoapi/riscv64 (0.1.4-8 to 0.1.4-8)
  • Migration status for haskell-cryptohash-cryptoapi/riscv64 (0.1.4-8 to 0.1.4-8): Will attempt migration (Any information below is purely informational)
• haskell-cryptohash-md5/riscv64 (0.11.101.0-2 to 0.11.101.0-2)
  • Migration status for haskell-cryptohash-md5/riscv64 (0.11.101.0-2 to 0.11.101.0-2): Will attempt migration (Any information below is purely informational)
• haskell-cryptohash-sha1/riscv64 (0.11.101.0-2 to 0.11.101.0-2)
  • Migration status for haskell-cryptohash-sha1/riscv64 (0.11.101.0-2 to 0.11.101.0-2): Will attempt migration (Any information below is purely informational)
• haskell-cryptohash-sha256/riscv64 (0.11.102.1-2 to 0.11.102.1-2)
  • Migration status for haskell-cryptohash-sha256/riscv64 (0.11.102.1-2 to 0.11.102.1-2): Will attempt migration (Any information below is purely informational)
• haskell-cryptohash/riscv64 (0.11.9-10 to 0.11.9-10)
  • Migration status for haskell-cryptohash/riscv64 (0.11.9-10 to 0.11.9-10): Will attempt migration (Any information below is purely informational)
• haskell-crypton-x509-store/riscv64 (1.6.9-2 to 1.6.9-2)
  • Migration status for haskell-crypton-x509-store/riscv64 (1.6.9-2 to 1.6.9-2): Will attempt migration (Any information below is purely informational)
• haskell-crypton-x509-system/riscv64 (1.6.7-2 to 1.6.7-2)
  • Migration status for haskell-crypton-x509-system/riscv64 (1.6.7-2 to 1.6.7-2): Will attempt migration (Any information below is purely informational)
• haskell-crypton-x509-validation/riscv64 (1.6.12-2 to 1.6.12-2)
  • Migration status for haskell-crypton-x509-validation/riscv64 (1.6.12-2 to 1.6.12-2): Will attempt migration (Any information below is purely informational)
• haskell-crypton-x509/riscv64 (1.7.6-2 to 1.7.6-2)
  • Migration status for haskell-crypton-x509/riscv64 (1.7.6-2 to 1.7.6-2): Will attempt migration (Any information below is purely informational)
• haskell-crypton/riscv64 (0.33-2 to 0.33-2)
  • Migration status for haskell-crypton/riscv64 (0.33-2 to 0.33-2): Will attempt migration (Any information below is purely informational)
• haskell-cryptonite-conduit/riscv64 (0.2.2-7 to 0.2.2-7)
  • Migration status for haskell-cryptonite-conduit/riscv64 (0.2.2-7 to 0.2.2-7): Will attempt migration (Any information below is purely informational)
• haskell-cryptonite/riscv64 (0.30-2 to 0.30-2)
  • Migration status for haskell-cryptonite/riscv64 (0.30-2 to 0.30-2): Will attempt migration (Any information below is purely informational)
• haskell-cryptostore/riscv64 (0.3.0.1-1 to 0.3.0.1-1)
  • Migration status for haskell-cryptostore/riscv64 (0.3.0.1-1 to 0.3.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-css-text/riscv64 (0.1.3.0-6 to 0.1.3.0-6)
  • Migration status for haskell-css-text/riscv64 (0.1.3.0-6 to 0.1.3.0-6): Will attempt migration (Any information below is purely informational)
• haskell-csv-conduit/riscv64 (0.7.3.0-2 to 0.7.3.0-2)
  • Migration status for haskell-csv-conduit/riscv64 (0.7.3.0-2 to 0.7.3.0-2): Will attempt migration (Any information below is purely informational)
• haskell-csv/riscv64 (0.1.2-17 to 0.1.2-17)
  • Migration status for haskell-csv/riscv64 (0.1.2-17 to 0.1.2-17): Will attempt migration (Any information below is purely informational)
• haskell-curl/riscv64 (1.3.8-14 to 1.3.8-14)
  • Migration status for haskell-curl/riscv64 (1.3.8-14 to 1.3.8-14): Will attempt migration (Any information below is purely informational)
• haskell-curve25519/riscv64 (0.2.7-2 to 0.2.7-2)
  • Migration status for haskell-curve25519/riscv64 (0.2.7-2 to 0.2.7-2): Will attempt migration (Any information below is purely informational)
• haskell-data-accessor-mtl/riscv64 (0.2.0.5-1 to 0.2.0.5-1)
  • Migration status for haskell-data-accessor-mtl/riscv64 (0.2.0.5-1 to 0.2.0.5-1): Will attempt migration (Any information below is purely informational)
• haskell-data-accessor/riscv64 (0.2.3.1-1 to 0.2.3.1-1)
  • Migration status for haskell-data-accessor/riscv64 (0.2.3.1-1 to 0.2.3.1-1): Will attempt migration (Any information below is purely informational)
• haskell-data-binary-ieee754/riscv64 (0.4.4-12 to 0.4.4-12)
  • Migration status for haskell-data-binary-ieee754/riscv64 (0.4.4-12 to 0.4.4-12): Will attempt migration (Any information below is purely informational)
• haskell-data-clist/riscv64 (0.2-2 to 0.2-2)
  • Migration status for haskell-data-clist/riscv64 (0.2-2 to 0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-data-default-class/riscv64 (0.1.2.0-7 to 0.1.2.0-7)
  • Migration status for haskell-data-default-class/riscv64 (0.1.2.0-7 to 0.1.2.0-7): Will attempt migration (Any information below is purely informational)
• haskell-data-default-instances-base/riscv64 (0.1.0.1-7 to 0.1.0.1-7)
  • Migration status for haskell-data-default-instances-base/riscv64 (0.1.0.1-7 to 0.1.0.1-7): Will attempt migration (Any information below is purely informational)
• haskell-data-default-instances-containers/riscv64 (0.0.1-13 to 0.0.1-13)
  • Migration status for haskell-data-default-instances-containers/riscv64 (0.0.1-13 to 0.0.1-13): Will attempt migration (Any information below is purely informational)
• haskell-data-default-instances-dlist/riscv64 (0.0.1-12 to 0.0.1-12)
  • Migration status for haskell-data-default-instances-dlist/riscv64 (0.0.1-12 to 0.0.1-12): Will attempt migration (Any information below is purely informational)
• haskell-data-default-instances-old-locale/riscv64 (0.0.1-12 to 0.0.1-12)
  • Migration status for haskell-data-default-instances-old-locale/riscv64 (0.0.1-12 to 0.0.1-12): Will attempt migration (Any information below is purely informational)
• haskell-data-default/riscv64 (0.7.1.1-7 to 0.7.1.1-7)
  • Migration status for haskell-data-default/riscv64 (0.7.1.1-7 to 0.7.1.1-7): Will attempt migration (Any information below is purely informational)
• haskell-data-fix/riscv64 (0.3.2-2 to 0.3.2-2)
  • Migration status for haskell-data-fix/riscv64 (0.3.2-2 to 0.3.2-2): Will attempt migration (Any information below is purely informational)
• haskell-data-functor-logistic/riscv64 (0.0-2 to 0.0-2)
  • Migration status for haskell-data-functor-logistic/riscv64 (0.0-2 to 0.0-2): Will attempt migration (Any information below is purely informational)
• haskell-data-hash/riscv64 (0.2.0.1-9 to 0.2.0.1-9)
  • Migration status for haskell-data-hash/riscv64 (0.2.0.1-9 to 0.2.0.1-9): Will attempt migration (Any information below is purely informational)
• haskell-data-inttrie/riscv64 (0.1.4-5 to 0.1.4-5)
  • Migration status for haskell-data-inttrie/riscv64 (0.1.4-5 to 0.1.4-5): Will attempt migration (Any information below is purely informational)
• haskell-data-memocombinators/riscv64 (0.5.1-11 to 0.5.1-11)
  • Migration status for haskell-data-memocombinators/riscv64 (0.5.1-11 to 0.5.1-11): Will attempt migration (Any information below is purely informational)
• haskell-data-ordlist/riscv64 (0.4.7.0-10 to 0.4.7.0-10)
  • Migration status for haskell-data-ordlist/riscv64 (0.4.7.0-10 to 0.4.7.0-10): Will attempt migration (Any information below is purely informational)
• haskell-data-reify/riscv64 (0.6.3-5 to 0.6.3-5)
  • Migration status for haskell-data-reify/riscv64 (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
• haskell-dav/riscv64 (1.3.4-3 to 1.3.4-3)
  • Migration status for haskell-dav/riscv64 (1.3.4-3 to 1.3.4-3): Will attempt migration (Any information below is purely informational)
• haskell-dbus-hslogger/riscv64 (0.1.0.1-4 to 0.1.0.1-4)
  • Migration status for haskell-dbus-hslogger/riscv64 (0.1.0.1-4 to 0.1.0.1-4): Will attempt migration (Any information below is purely informational)
• haskell-dbus/riscv64 (1.2.29-1 to 1.2.29-1)
  • Migration status for haskell-dbus/riscv64 (1.2.29-1 to 1.2.29-1): Will attempt migration (Any information below is purely informational)
• haskell-debian/riscv64 (4.0.5-1 to 4.0.5-1)
  • Migration status for haskell-debian/riscv64 (4.0.5-1 to 4.0.5-1): Will attempt migration (Any information below is purely informational)
• haskell-dec/riscv64 (0.0.5-2 to 0.0.5-2)
  • Migration status for haskell-dec/riscv64 (0.0.5-2 to 0.0.5-2): Will attempt migration (Any information below is purely informational)
• haskell-decimal/riscv64 (0.5.2-2 to 0.5.2-2)
  • Migration status for haskell-decimal/riscv64 (0.5.2-2 to 0.5.2-2): Will attempt migration (Any information below is purely informational)
• haskell-deepseq-generics/riscv64 (0.2.0.0-8 to 0.2.0.0-8)
  • Migration status for haskell-deepseq-generics/riscv64 (0.2.0.0-8 to 0.2.0.0-8): Will attempt migration (Any information below is purely informational)
• haskell-deferred-folds/riscv64 (0.9.18.5-1 to 0.9.18.5-1)
  • Migration status for haskell-deferred-folds/riscv64 (0.9.18.5-1 to 0.9.18.5-1): Will attempt migration (Any information below is purely informational)
• haskell-dense-linear-algebra/riscv64 (0.1.0.0-5 to 0.1.0.0-5)
  • Migration status for haskell-dense-linear-algebra/riscv64 (0.1.0.0-5 to 0.1.0.0-5): Will attempt migration (Any information below is purely informational)
• haskell-dependent-map/riscv64 (0.4.0.0-3 to 0.4.0.0-3)
  • Migration status for haskell-dependent-map/riscv64 (0.4.0.0-3 to 0.4.0.0-3): Will attempt migration (Any information below is purely informational)
• haskell-dependent-sum-template/riscv64 (0.2.0.0-1 to 0.2.0.0-1)
  • Migration status for haskell-dependent-sum-template/riscv64 (0.2.0.0-1 to 0.2.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-dependent-sum/riscv64 (0.7.2.0-1 to 0.7.2.0-1)
  • Migration status for haskell-dependent-sum/riscv64 (0.7.2.0-1 to 0.7.2.0-1): Will attempt migration (Any information below is purely informational)
• haskell-deque/riscv64 (0.4.4-2 to 0.4.4-2)
  • Migration status for haskell-deque/riscv64 (0.4.4-2 to 0.4.4-2): Will attempt migration (Any information below is purely informational)
• haskell-deriving-aeson/riscv64 (0.2.9-1 to 0.2.9-1)
  • Migration status for haskell-deriving-aeson/riscv64 (0.2.9-1 to 0.2.9-1): Will attempt migration (Any information below is purely informational)
• haskell-deriving-compat/riscv64 (0.6.5-1 to 0.6.5-1)
  • Migration status for haskell-deriving-compat/riscv64 (0.6.5-1 to 0.6.5-1): Will attempt migration (Any information below is purely informational)
• haskell-diagrams-cairo/riscv64 (1.4.2.1-1 to 1.4.2.1-1)
  • Migration status for haskell-diagrams-cairo/riscv64 (1.4.2.1-1 to 1.4.2.1-1): Will attempt migration (Any information below is purely informational)
• haskell-diagrams-core/riscv64 (1.5.1-1 to 1.5.1-1)
  • Migration status for haskell-diagrams-core/riscv64 (1.5.1-1 to 1.5.1-1): Will attempt migration (Any information below is purely informational)
• haskell-diagrams-lib/riscv64 (1.4.6-2 to 1.4.6-2)
  • Migration status for haskell-diagrams-lib/riscv64 (1.4.6-2 to 1.4.6-2): Will attempt migration (Any information below is purely informational)
• haskell-diagrams-solve/riscv64 (0.1.3-2 to 0.1.3-2)
  • Migration status for haskell-diagrams-solve/riscv64 (0.1.3-2 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
• haskell-diagrams-svg/riscv64 (1.4.3.1-2 to 1.4.3.1-2)
  • Migration status for haskell-diagrams-svg/riscv64 (1.4.3.1-2 to 1.4.3.1-2): Will attempt migration (Any information below is purely informational)
• haskell-dice-entropy-conduit/riscv64 (1.0.0.3-3 to 1.0.0.3-3)
  • Migration status for haskell-dice-entropy-conduit/riscv64 (1.0.0.3-3 to 1.0.0.3-3): Will attempt migration (Any information below is purely informational)
• haskell-dice/riscv64 (0.1.1-2 to 0.1.1-2)
  • Migration status for haskell-dice/riscv64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• haskell-diff/riscv64 (0.4.1-2 to 0.4.1-2)
  • Migration status for haskell-diff/riscv64 (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• haskell-digest/riscv64 (0.0.1.7-1 to 0.0.1.7-1)
  • Migration status for haskell-digest/riscv64 (0.0.1.7-1 to 0.0.1.7-1): Will attempt migration (Any information below is purely informational)
• haskell-dimensional/riscv64 (1.5-1 to 1.5-1)
  • Migration status for haskell-dimensional/riscv64 (1.5-1 to 1.5-1): Will attempt migration (Any information below is purely informational)
• haskell-directory-tree/riscv64 (0.12.1-8 to 0.12.1-8)
  • Migration status for haskell-directory-tree/riscv64 (0.12.1-8 to 0.12.1-8): Will attempt migration (Any information below is purely informational)
• haskell-disk-free-space/riscv64 (0.1.0.1-8 to 0.1.0.1-8)
  • Migration status for haskell-disk-free-space/riscv64 (0.1.0.1-8 to 0.1.0.1-8): Will attempt migration (Any information below is purely informational)
• haskell-distributive/riscv64 (0.6.2.1-2 to 0.6.2.1-2)
  • Migration status for haskell-distributive/riscv64 (0.6.2.1-2 to 0.6.2.1-2): Will attempt migration (Any information below is purely informational)
• haskell-djinn-lib/riscv64 (0.0.1.4-2 to 0.0.1.4-2)
  • Migration status for haskell-djinn-lib/riscv64 (0.0.1.4-2 to 0.0.1.4-2): Will attempt migration (Any information below is purely informational)
• haskell-dlist-instances/riscv64 (0.1.1.1-8 to 0.1.1.1-8)
  • Migration status for haskell-dlist-instances/riscv64 (0.1.1.1-8 to 0.1.1.1-8): Will attempt migration (Any information below is purely informational)
• haskell-dlist/riscv64 (1.0-3 to 1.0-3)
  • Migration status for haskell-dlist/riscv64 (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• haskell-dns/riscv64 (4.1.1-2 to 4.1.1-2)
  • Migration status for haskell-dns/riscv64 (4.1.1-2 to 4.1.1-2): Will attempt migration (Any information below is purely informational)
• haskell-doclayout/riscv64 (0.4.0.1-1 to 0.4.0.1-1)
  • Migration status for haskell-doclayout/riscv64 (0.4.0.1-1 to 0.4.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-doctemplates/riscv64 (0.11-1 to 0.11-1)
  • Migration status for haskell-doctemplates/riscv64 (0.11-1 to 0.11-1): Will attempt migration (Any information below is purely informational)
• haskell-doctest-parallel/riscv64 (0.3.0.1-1 to 0.3.0.1-1)
  • Migration status for haskell-doctest-parallel/riscv64 (0.3.0.1-1 to 0.3.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-doctest/riscv64 (0.20.1-1 to 0.20.1-1)
  • Migration status for haskell-doctest/riscv64 (0.20.1-1 to 0.20.1-1): Will attempt migration (Any information below is purely informational)
• haskell-dotgen/riscv64 (0.4.3-3 to 0.4.3-3)
  • Migration status for haskell-dotgen/riscv64 (0.4.3-3 to 0.4.3-3): Will attempt migration (Any information below is purely informational)
• haskell-double-conversion/riscv64 (2.0.4.2+ds1-1 to 2.0.4.2+ds1-1)
  • Migration status for haskell-double-conversion/riscv64 (2.0.4.2+ds1-1 to 2.0.4.2+ds1-1): Will attempt migration (Any information below is purely informational)
• haskell-dual-tree/riscv64 (0.2.3.1-2 to 0.2.3.1-2)
  • Migration status for haskell-dual-tree/riscv64 (0.2.3.1-2 to 0.2.3.1-2): Will attempt migration (Any information below is purely informational)
• haskell-dynamic-state/riscv64 (0.3.1-5 to 0.3.1-5)
  • Migration status for haskell-dynamic-state/riscv64 (0.3.1-5 to 0.3.1-5): Will attempt migration (Any information below is purely informational)
• haskell-dyre/riscv64 (0.9.2-1 to 0.9.2-1)
  • Migration status for haskell-dyre/riscv64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• haskell-easy-file/riscv64 (0.2.5-1 to 0.2.5-1)
  • Migration status for haskell-easy-file/riscv64 (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• haskell-echo/riscv64 (0.1.4-2 to 0.1.4-2)
  • Migration status for haskell-echo/riscv64 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• haskell-ed25519/riscv64 (0.0.5.0-17 to 0.0.5.0-17)
  • Migration status for haskell-ed25519/riscv64 (0.0.5.0-17 to 0.0.5.0-17): Will attempt migration (Any information below is purely informational)
• haskell-edit-distance-vector/riscv64 (1.0.0.4-4 to 1.0.0.4-4)
  • Migration status for haskell-edit-distance-vector/riscv64 (1.0.0.4-4 to 1.0.0.4-4): Will attempt migration (Any information below is purely informational)
• haskell-edit-distance/riscv64 (0.2.2.1-13 to 0.2.2.1-13)
  • Migration status for haskell-edit-distance/riscv64 (0.2.2.1-13 to 0.2.2.1-13): Will attempt migration (Any information below is purely informational)
• haskell-either/riscv64 (5.0.2-2 to 5.0.2-2)
  • Migration status for haskell-either/riscv64 (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-email-validate/riscv64 (2.3.2.19-3 to 2.3.2.19-3)
  • Migration status for haskell-email-validate/riscv64 (2.3.2.19-3 to 2.3.2.19-3): Will attempt migration (Any information below is purely informational)
• haskell-emojis/riscv64 (0.1.3-1 to 0.1.3-1)
  • Migration status for haskell-emojis/riscv64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• haskell-enclosed-exceptions/riscv64 (1.0.3-5 to 1.0.3-5)
  • Migration status for haskell-enclosed-exceptions/riscv64 (1.0.3-5 to 1.0.3-5): Will attempt migration (Any information below is purely informational)
• haskell-entropy/riscv64 (0.4.1.10-2 to 0.4.1.10-2)
  • Migration status for haskell-entropy/riscv64 (0.4.1.10-2 to 0.4.1.10-2): Will attempt migration (Any information below is purely informational)
• haskell-enummapset/riscv64 (0.7.1.0-1 to 0.7.1.0-1)
  • Migration status for haskell-enummapset/riscv64 (0.7.1.0-1 to 0.7.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-equivalence/riscv64 (0.4.1-2 to 0.4.1-2)
  • Migration status for haskell-equivalence/riscv64 (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• haskell-erf/riscv64 (2.0.0.0-18 to 2.0.0.0-18)
  • Migration status for haskell-erf/riscv64 (2.0.0.0-18 to 2.0.0.0-18): Will attempt migration (Any information below is purely informational)
• haskell-errors/riscv64 (2.3.0-5 to 2.3.0-5)
  • Migration status for haskell-errors/riscv64 (2.3.0-5 to 2.3.0-5): Will attempt migration (Any information below is purely informational)
• haskell-esqueleto/riscv64 (3.5.10.3-1 to 3.5.10.3-1)
  • Migration status for haskell-esqueleto/riscv64 (3.5.10.3-1 to 3.5.10.3-1): Will attempt migration (Any information below is purely informational)
• haskell-exact-pi/riscv64 (0.5.0.2-2 to 0.5.0.2-2)
  • Migration status for haskell-exact-pi/riscv64 (0.5.0.2-2 to 0.5.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-exception-transformers/riscv64 (0.4.0.12-1 to 0.4.0.12-1)
  • Migration status for haskell-exception-transformers/riscv64 (0.4.0.12-1 to 0.4.0.12-1): Will attempt migration (Any information below is purely informational)
• haskell-executable-path/riscv64 (0.0.3.1-6 to 0.0.3.1-6)
  • Migration status for haskell-executable-path/riscv64 (0.0.3.1-6 to 0.0.3.1-6): Will attempt migration (Any information below is purely informational)
• haskell-expiring-cache-map/riscv64 (0.0.6.1-8 to 0.0.6.1-8)
  • Migration status for haskell-expiring-cache-map/riscv64 (0.0.6.1-8 to 0.0.6.1-8): Will attempt migration (Any information below is purely informational)
• haskell-extensible-exceptions/riscv64 (0.1.1.4-13 to 0.1.1.4-13)
  • Migration status for haskell-extensible-exceptions/riscv64 (0.1.1.4-13 to 0.1.1.4-13): Will attempt migration (Any information below is purely informational)
• haskell-extra/riscv64 (1.7.14-1 to 1.7.14-1)
  • Migration status for haskell-extra/riscv64 (1.7.14-1 to 1.7.14-1): Will attempt migration (Any information below is purely informational)
• haskell-failure/riscv64 (0.2.0.3-12 to 0.2.0.3-12)
  • Migration status for haskell-failure/riscv64 (0.2.0.3-12 to 0.2.0.3-12): Will attempt migration (Any information below is purely informational)
• haskell-fast-logger/riscv64 (3.2.2-2 to 3.2.2-2)
  • Migration status for haskell-fast-logger/riscv64 (3.2.2-2 to 3.2.2-2): Will attempt migration (Any information below is purely informational)
• haskell-fb/riscv64 (2.1.1.1-2 to 2.1.1.1-2)
  • Migration status for haskell-fb/riscv64 (2.1.1.1-2 to 2.1.1.1-2): Will attempt migration (Any information below is purely informational)
• haskell-fdo-notify/riscv64 (0.3.1-13 to 0.3.1-13)
  • Migration status for haskell-fdo-notify/riscv64 (0.3.1-13 to 0.3.1-13): Will attempt migration (Any information below is purely informational)
• haskell-feed/riscv64 (1.3.2.1-2 to 1.3.2.1-2)
  • Migration status for haskell-feed/riscv64 (1.3.2.1-2 to 1.3.2.1-2): Will attempt migration (Any information below is purely informational)
• haskell-fgl-arbitrary/riscv64 (0.2.0.6-3 to 0.2.0.6-3)
  • Migration status for haskell-fgl-arbitrary/riscv64 (0.2.0.6-3 to 0.2.0.6-3): Will attempt migration (Any information below is purely informational)
• haskell-fgl/riscv64 (5.8.1.1-1 to 5.8.1.1-1)
  • Migration status for haskell-fgl/riscv64 (5.8.1.1-1 to 5.8.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-file-embed/riscv64 (0.0.15.0-2 to 0.0.15.0-2)
  • Migration status for haskell-file-embed/riscv64 (0.0.15.0-2 to 0.0.15.0-2): Will attempt migration (Any information below is purely informational)
• haskell-file-location/riscv64 (0.4.9.1-5 to 0.4.9.1-5)
  • Migration status for haskell-file-location/riscv64 (0.4.9.1-5 to 0.4.9.1-5): Will attempt migration (Any information below is purely informational)
• haskell-filelock/riscv64 (0.1.1.7-1 to 0.1.1.7-1)
  • Migration status for haskell-filelock/riscv64 (0.1.1.7-1 to 0.1.1.7-1): Will attempt migration (Any information below is purely informational)
• haskell-filemanip/riscv64 (0.3.6.3-12 to 0.3.6.3-12)
  • Migration status for haskell-filemanip/riscv64 (0.3.6.3-12 to 0.3.6.3-12): Will attempt migration (Any information below is purely informational)
• haskell-filepath-bytestring/riscv64 (1.4.2.1.13-1 to 1.4.2.1.13-1)
  • Migration status for haskell-filepath-bytestring/riscv64 (1.4.2.1.13-1 to 1.4.2.1.13-1): Will attempt migration (Any information below is purely informational)
• haskell-filepattern/riscv64 (0.1.3-2 to 0.1.3-2)
  • Migration status for haskell-filepattern/riscv64 (0.1.3-2 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
• haskell-filestore/riscv64 (0.6.5-3 to 0.6.5-3)
  • Migration status for haskell-filestore/riscv64 (0.6.5-3 to 0.6.5-3): Will attempt migration (Any information below is purely informational)
• haskell-filtrable/riscv64 (0.1.6.0-3 to 0.1.6.0-3)
  • Migration status for haskell-filtrable/riscv64 (0.1.6.0-3 to 0.1.6.0-3): Will attempt migration (Any information below is purely informational)
• haskell-fingertree/riscv64 (0.1.5.0-2 to 0.1.5.0-2)
  • Migration status for haskell-fingertree/riscv64 (0.1.5.0-2 to 0.1.5.0-2): Will attempt migration (Any information below is purely informational)
• haskell-finite-field/riscv64 (0.10.0-2 to 0.10.0-2)
  • Migration status for haskell-finite-field/riscv64 (0.10.0-2 to 0.10.0-2): Will attempt migration (Any information below is purely informational)
• haskell-first-class-families/riscv64 (0.8.0.1-2 to 0.8.0.1-2)
  • Migration status for haskell-first-class-families/riscv64 (0.8.0.1-2 to 0.8.0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-fixed/riscv64 (0.3-3 to 0.3-3)
  • Migration status for haskell-fixed/riscv64 (0.3-3 to 0.3-3): Will attempt migration (Any information below is purely informational)
• haskell-flexible-defaults/riscv64 (0.0.3-3 to 0.0.3-3)
  • Migration status for haskell-flexible-defaults/riscv64 (0.0.3-3 to 0.0.3-3): Will attempt migration (Any information below is purely informational)
• haskell-floatinghex/riscv64 (0.5-2 to 0.5-2)
  • Migration status for haskell-floatinghex/riscv64 (0.5-2 to 0.5-2): Will attempt migration (Any information below is purely informational)
• haskell-fmlist/riscv64 (0.9.4-2 to 0.9.4-2)
  • Migration status for haskell-fmlist/riscv64 (0.9.4-2 to 0.9.4-2): Will attempt migration (Any information below is purely informational)
• haskell-focuslist/riscv64 (0.1.1.0-2 to 0.1.1.0-2)
  • Migration status for haskell-focuslist/riscv64 (0.1.1.0-2 to 0.1.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-fold-debounce/riscv64 (0.2.0.11-1 to 0.2.0.11-1)
  • Migration status for haskell-fold-debounce/riscv64 (0.2.0.11-1 to 0.2.0.11-1): Will attempt migration (Any information below is purely informational)
• haskell-foldable1-classes-compat/riscv64 (0.1-2 to 0.1-2)
  • Migration status for haskell-foldable1-classes-compat/riscv64 (0.1-2 to 0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-foldl/riscv64 (1.4.15-1 to 1.4.15-1)
  • Migration status for haskell-foldl/riscv64 (1.4.15-1 to 1.4.15-1): Will attempt migration (Any information below is purely informational)
• haskell-formatting/riscv64 (7.2.0-1 to 7.2.0-1)
  • Migration status for haskell-formatting/riscv64 (7.2.0-1 to 7.2.0-1): Will attempt migration (Any information below is purely informational)
• haskell-foundation/riscv64 (0.0.30-2 to 0.0.30-2)
  • Migration status for haskell-foundation/riscv64 (0.0.30-2 to 0.0.30-2): Will attempt migration (Any information below is purely informational)
• haskell-free/riscv64 (5.1.10-1 to 5.1.10-1)
  • Migration status for haskell-free/riscv64 (5.1.10-1 to 5.1.10-1): Will attempt migration (Any information below is purely informational)
• haskell-from-sum/riscv64 (0.2.3.0-3 to 0.2.3.0-3)
  • Migration status for haskell-from-sum/riscv64 (0.2.3.0-3 to 0.2.3.0-3): Will attempt migration (Any information below is purely informational)
• haskell-fsnotify/riscv64 (0.4.1.0-1 to 0.4.1.0-1)
  • Migration status for haskell-fsnotify/riscv64 (0.4.1.0-1 to 0.4.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-gd/riscv64 (3000.7.3-15 to 3000.7.3-15)
  • Migration status for haskell-gd/riscv64 (3000.7.3-15 to 3000.7.3-15): Will attempt migration (Any information below is purely informational)
• haskell-generic-data/riscv64 (1.1.0.0-1 to 1.1.0.0-1)
  • Migration status for haskell-generic-data/riscv64 (1.1.0.0-1 to 1.1.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-generic-deriving/riscv64 (1.14.5-1 to 1.14.5-1)
  • Migration status for haskell-generic-deriving/riscv64 (1.14.5-1 to 1.14.5-1): Will attempt migration (Any information below is purely informational)
• haskell-generic-lens-core/riscv64 (2.2.1.0-2 to 2.2.1.0-2)
  • Migration status for haskell-generic-lens-core/riscv64 (2.2.1.0-2 to 2.2.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-generic-lens/riscv64 (2.2.2.0-1 to 2.2.2.0-1)
  • Migration status for haskell-generic-lens/riscv64 (2.2.2.0-1 to 2.2.2.0-1): Will attempt migration (Any information below is purely informational)
• haskell-generic-random/riscv64 (1.5.0.1-2 to 1.5.0.1-2)
  • Migration status for haskell-generic-random/riscv64 (1.5.0.1-2 to 1.5.0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-generic-trie/riscv64 (0.3.2-1 to 0.3.2-1)
  • Migration status for haskell-generic-trie/riscv64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• haskell-generics-sop/riscv64 (0.5.1.3-1 to 0.5.1.3-1)
  • Migration status for haskell-generics-sop/riscv64 (0.5.1.3-1 to 0.5.1.3-1): Will attempt migration (Any information below is purely informational)
• haskell-geniplate-mirror/riscv64 (0.7.9-1 to 0.7.9-1)
  • Migration status for haskell-geniplate-mirror/riscv64 (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• haskell-genvalidity-containers/riscv64 (1.0.0.1-1 to 1.0.0.1-1)
  • Migration status for haskell-genvalidity-containers/riscv64 (1.0.0.1-1 to 1.0.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-genvalidity-hspec/riscv64 (1.0.0.3-1 to 1.0.0.3-1)
  • Migration status for haskell-genvalidity-hspec/riscv64 (1.0.0.3-1 to 1.0.0.3-1): Will attempt migration (Any information below is purely informational)
• haskell-genvalidity-property/riscv64 (1.0.0.0-3 to 1.0.0.0-3)
  • Migration status for haskell-genvalidity-property/riscv64 (1.0.0.0-3 to 1.0.0.0-3): Will attempt migration (Any information below is purely informational)
• haskell-genvalidity/riscv64 (1.1.0.0-1 to 1.1.0.0-1)
  • Migration status for haskell-genvalidity/riscv64 (1.1.0.0-1 to 1.1.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-getopt-generics/riscv64 (0.13.1.0-1 to 0.13.1.0-1)
  • Migration status for haskell-getopt-generics/riscv64 (0.13.1.0-1 to 0.13.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-ghc-events/riscv64 (0.19.0.1-1 to 0.19.0.1-1)
  • Migration status for haskell-ghc-events/riscv64 (0.19.0.1-1 to 0.19.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-ghc-exactprint/riscv64 (1.6.1.3-1 to 1.6.1.3-1)
  • Migration status for haskell-ghc-exactprint/riscv64 (1.6.1.3-1 to 1.6.1.3-1): Will attempt migration (Any information below is purely informational)
• haskell-ghc-lib-parser-ex/riscv64 (9.4.0.0-1 to 9.4.0.0-1)
  • Migration status for haskell-ghc-lib-parser-ex/riscv64 (9.4.0.0-1 to 9.4.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-ghc-lib-parser/riscv64 (9.4.7.20230826-1 to 9.4.7.20230826-1)
  • Migration status for haskell-ghc-lib-parser/riscv64 (9.4.7.20230826-1 to 9.4.7.20230826-1): Will attempt migration (Any information below is purely informational)
• haskell-ghc-paths/riscv64 (0.1.0.12-3 to 0.1.0.12-3)
  • Migration status for haskell-ghc-paths/riscv64 (0.1.0.12-3 to 0.1.0.12-3): Will attempt migration (Any information below is purely informational)
• haskell-ghc-tcplugins-extra/riscv64 (0.4.5-1 to 0.4.5-1)
  • Migration status for haskell-ghc-tcplugins-extra/riscv64 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
• haskell-ghc-typelits-extra/riscv64 (0.4.6-1 to 0.4.6-1)
  • Migration status for haskell-ghc-typelits-extra/riscv64 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• haskell-ghc-typelits-knownnat/riscv64 (0.7.9-1 to 0.7.9-1)
  • Migration status for haskell-ghc-typelits-knownnat/riscv64 (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• haskell-ghc-typelits-natnormalise/riscv64 (0.7.9-1 to 0.7.9-1)
  • Migration status for haskell-ghc-typelits-natnormalise/riscv64 (0.7.9-1 to 0.7.9-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-atk/riscv64 (2.0.27-1 to 2.0.27-1)
  • Migration status for haskell-gi-atk/riscv64 (2.0.27-1 to 2.0.27-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-cairo-connector/riscv64 (0.1.1-2 to 0.1.1-2)
  • Migration status for haskell-gi-cairo-connector/riscv64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• haskell-gi-cairo-render/riscv64 (0.1.2-2 to 0.1.2-2)
  • Migration status for haskell-gi-cairo-render/riscv64 (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• haskell-gi-cairo/riscv64 (1.0.29-1 to 1.0.29-1)
  • Migration status for haskell-gi-cairo/riscv64 (1.0.29-1 to 1.0.29-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-dbusmenu/riscv64 (0.4.13-1 to 0.4.13-1)
  • Migration status for haskell-gi-dbusmenu/riscv64 (0.4.13-1 to 0.4.13-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-freetype2/riscv64 (2.0.4-1 to 2.0.4-1)
  • Migration status for haskell-gi-freetype2/riscv64 (2.0.4-1 to 2.0.4-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-gdk/riscv64 (3.0.28-1 to 3.0.28-1)
  • Migration status for haskell-gi-gdk/riscv64 (3.0.28-1 to 3.0.28-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-gdkpixbuf/riscv64 (2.0.31-1 to 2.0.31-1)
  • Migration status for haskell-gi-gdkpixbuf/riscv64 (2.0.31-1 to 2.0.31-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-gdkx11/riscv64 (3.0.15-1 to 3.0.15-1)
  • Migration status for haskell-gi-gdkx11/riscv64 (3.0.15-1 to 3.0.15-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-gio/riscv64 (2.0.32-1 to 2.0.32-1)
  • Migration status for haskell-gi-gio/riscv64 (2.0.32-1 to 2.0.32-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-glib/riscv64 (2.0.29-1 to 2.0.29-1)
  • Migration status for haskell-gi-glib/riscv64 (2.0.29-1 to 2.0.29-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-gmodule/riscv64 (2.0.5-1 to 2.0.5-1)
  • Migration status for haskell-gi-gmodule/riscv64 (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-gobject/riscv64 (2.0.30-1 to 2.0.30-1)
  • Migration status for haskell-gi-gobject/riscv64 (2.0.30-1 to 2.0.30-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-harfbuzz/riscv64 (0.0.9-1 to 0.0.9-1)
  • Migration status for haskell-gi-harfbuzz/riscv64 (0.0.9-1 to 0.0.9-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-pango/riscv64 (1.0.29-1 to 1.0.29-1)
  • Migration status for haskell-gi-pango/riscv64 (1.0.29-1 to 1.0.29-1): Will attempt migration (Any information below is purely informational)
• haskell-gi-xlib/riscv64 (2.0.13-1 to 2.0.13-1)
  • Migration status for haskell-gi-xlib/riscv64 (2.0.13-1 to 2.0.13-1): Will attempt migration (Any information below is purely informational)
• haskell-gio/riscv64 (0.13.10.0-1 to 0.13.10.0-1)
  • Migration status for haskell-gio/riscv64 (0.13.10.0-1 to 0.13.10.0-1): Will attempt migration (Any information below is purely informational)
• haskell-git-lfs/riscv64 (1.2.1-1 to 1.2.1-1)
  • Migration status for haskell-git-lfs/riscv64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• haskell-githash/riscv64 (0.1.7.0-1 to 0.1.7.0-1)
  • Migration status for haskell-githash/riscv64 (0.1.7.0-1 to 0.1.7.0-1): Will attempt migration (Any information below is purely informational)
• haskell-github/riscv64 (0.28.0.1-1 to 0.28.0.1-1)
  • Migration status for haskell-github/riscv64 (0.28.0.1-1 to 0.28.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-gitrev/riscv64 (1.3.1-6 to 1.3.1-6)
  • Migration status for haskell-gitrev/riscv64 (1.3.1-6 to 1.3.1-6): Will attempt migration (Any information below is purely informational)
• haskell-glib/riscv64 (0.13.10.0-1 to 0.13.10.0-1)
  • Migration status for haskell-glib/riscv64 (0.13.10.0-1 to 0.13.10.0-1): Will attempt migration (Any information below is purely informational)
• haskell-glob/riscv64 (0.10.2-2 to 0.10.2-2)
  • Migration status for haskell-glob/riscv64 (0.10.2-2 to 0.10.2-2): Will attempt migration (Any information below is purely informational)
• haskell-gloss-rendering/riscv64 (1.13.1.2-1 to 1.13.1.2-1)
  • Migration status for haskell-gloss-rendering/riscv64 (1.13.1.2-1 to 1.13.1.2-1): Will attempt migration (Any information below is purely informational)
• haskell-gloss/riscv64 (1.13.2.2-1 to 1.13.2.2-1)
  • Migration status for haskell-gloss/riscv64 (1.13.2.2-1 to 1.13.2.2-1): Will attempt migration (Any information below is purely informational)
• haskell-gluraw/riscv64 (2.0.0.5-2 to 2.0.0.5-2)
  • Migration status for haskell-gluraw/riscv64 (2.0.0.5-2 to 2.0.0.5-2): Will attempt migration (Any information below is purely informational)
• haskell-glut/riscv64 (2.7.0.16-3 to 2.7.0.16-3)
  • Migration status for haskell-glut/riscv64 (2.7.0.16-3 to 2.7.0.16-3): Will attempt migration (Any information below is purely informational)
• haskell-graphscc/riscv64 (1.0.4-8 to 1.0.4-8)
  • Migration status for haskell-graphscc/riscv64 (1.0.4-8 to 1.0.4-8): Will attempt migration (Any information below is purely informational)
• haskell-graphviz/riscv64 (2999.20.1.0-2 to 2999.20.1.0-2)
  • Migration status for haskell-graphviz/riscv64 (2999.20.1.0-2 to 2999.20.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-gridtables/riscv64 (0.1.0.0-1 to 0.1.0.0-1)
  • Migration status for haskell-gridtables/riscv64 (0.1.0.0-1 to 0.1.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-groups/riscv64 (0.5.3-2 to 0.5.3-2)
  • Migration status for haskell-groups/riscv64 (0.5.3-2 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
• haskell-gsasl/riscv64 (0.3.7-3 to 0.3.7-3)
  • Migration status for haskell-gsasl/riscv64 (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• haskell-gtk-traymanager/riscv64 (1.0.1-6 to 1.0.1-6)
  • Migration status for haskell-gtk-traymanager/riscv64 (1.0.1-6 to 1.0.1-6): Will attempt migration (Any information below is purely informational)
• haskell-gtk/riscv64 (0.15.8-1 to 0.15.8-1)
  • Migration status for haskell-gtk/riscv64 (0.15.8-1 to 0.15.8-1): Will attempt migration (Any information below is purely informational)
• haskell-gtk3/riscv64 (0.15.8-1 to 0.15.8-1)
  • Migration status for haskell-gtk3/riscv64 (0.15.8-1 to 0.15.8-1): Will attempt migration (Any information below is purely informational)
• haskell-hackage-security/riscv64 (0.6.2.3-2 to 0.6.2.3-2)
  • Migration status for haskell-hackage-security/riscv64 (0.6.2.3-2 to 0.6.2.3-2): Will attempt migration (Any information below is purely informational)
• haskell-haddock-library/riscv64 (1.11.0-1 to 1.11.0-1)
  • Migration status for haskell-haddock-library/riscv64 (1.11.0-1 to 1.11.0-1): Will attempt migration (Any information below is purely informational)
• haskell-hakyll/riscv64 (4.16.2.0-2 to 4.16.2.0-2)
  • Migration status for haskell-hakyll/riscv64 (4.16.2.0-2 to 4.16.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-half/riscv64 (0.3.1-2 to 0.3.1-2)
  • Migration status for haskell-half/riscv64 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• haskell-happstack-hsp/riscv64 (7.3.7.7-1 to 7.3.7.7-1)
  • Migration status for haskell-happstack-hsp/riscv64 (7.3.7.7-1 to 7.3.7.7-1): Will attempt migration (Any information below is purely informational)
• haskell-happstack-jmacro/riscv64 (7.0.12.5-1 to 7.0.12.5-1)
  • Migration status for haskell-happstack-jmacro/riscv64 (7.0.12.5-1 to 7.0.12.5-1): Will attempt migration (Any information below is purely informational)
• haskell-happstack-server/riscv64 (7.8.0.2-2 to 7.8.0.2-2)
  • Migration status for haskell-happstack-server/riscv64 (7.8.0.2-2 to 7.8.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-harp/riscv64 (0.4.3.6-1 to 0.4.3.6-1)
  • Migration status for haskell-harp/riscv64 (0.4.3.6-1 to 0.4.3.6-1): Will attempt migration (Any information below is purely informational)
• haskell-hashable/riscv64 (1.4.3.0-1 to 1.4.3.0-1)
  • Migration status for haskell-hashable/riscv64 (1.4.3.0-1 to 1.4.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-hashtables/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for haskell-hashtables/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• haskell-haskell-gi-base/riscv64 (0.26.4-3 to 0.26.4-3)
  • Migration status for haskell-haskell-gi-base/riscv64 (0.26.4-3 to 0.26.4-3): Will attempt migration (Any information below is purely informational)
• haskell-haskell-gi/riscv64 (0.26.7-4 to 0.26.7-4)
  • Migration status for haskell-haskell-gi/riscv64 (0.26.7-4 to 0.26.7-4): Will attempt migration (Any information below is purely informational)
• haskell-haskell-src/riscv64 (1.0.4-2 to 1.0.4-2)
  • Migration status for haskell-haskell-src/riscv64 (1.0.4-2 to 1.0.4-2): Will attempt migration (Any information below is purely informational)
• haskell-haxr/riscv64 (3000.11.5-1 to 3000.11.5-1)
  • Migration status for haskell-haxr/riscv64 (3000.11.5-1 to 3000.11.5-1): Will attempt migration (Any information below is purely informational)
• haskell-hclip/riscv64 (3.0.0.4-10 to 3.0.0.4-10)
  • Migration status for haskell-hclip/riscv64 (3.0.0.4-10 to 3.0.0.4-10): Will attempt migration (Any information below is purely informational)
• haskell-hcwiid/riscv64 (0.0.6.1-6 to 0.0.6.1-6)
  • Migration status for haskell-hcwiid/riscv64 (0.0.6.1-6 to 0.0.6.1-6): Will attempt migration (Any information below is purely informational)
• haskell-hdbc-session/riscv64 (0.1.2.0-5 to 0.1.2.0-5)
  • Migration status for haskell-hdbc-session/riscv64 (0.1.2.0-5 to 0.1.2.0-5): Will attempt migration (Any information below is purely informational)
• haskell-heaps/riscv64 (0.4-2 to 0.4-2)
  • Migration status for haskell-heaps/riscv64 (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
• haskell-hedgehog-classes/riscv64 (0.2.5.4-1 to 0.2.5.4-1)
  • Migration status for haskell-hedgehog-classes/riscv64 (0.2.5.4-1 to 0.2.5.4-1): Will attempt migration (Any information below is purely informational)
• haskell-hedgehog/riscv64 (1.2-1 to 1.2-1)
  • Migration status for haskell-hedgehog/riscv64 (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• haskell-hedis/riscv64 (0.15.2-1 to 0.15.2-1)
  • Migration status for haskell-hedis/riscv64 (0.15.2-1 to 0.15.2-1): Will attempt migration (Any information below is purely informational)
• haskell-heist/riscv64 (1.1.1.1-1 to 1.1.1.1-1)
  • Migration status for haskell-heist/riscv64 (1.1.1.1-1 to 1.1.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-here/riscv64 (1.2.14-1 to 1.2.14-1)
  • Migration status for haskell-here/riscv64 (1.2.14-1 to 1.2.14-1): Will attempt migration (Any information below is purely informational)
• haskell-heredoc/riscv64 (0.2.0.0-8 to 0.2.0.0-8)
  • Migration status for haskell-heredoc/riscv64 (0.2.0.0-8 to 0.2.0.0-8): Will attempt migration (Any information below is purely informational)
• haskell-heterocephalus/riscv64 (1.0.5.7-2 to 1.0.5.7-2)
  • Migration status for haskell-heterocephalus/riscv64 (1.0.5.7-2 to 1.0.5.7-2): Will attempt migration (Any information below is purely informational)
• haskell-hex/riscv64 (0.2.0-2 to 0.2.0-2)
  • Migration status for haskell-hex/riscv64 (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-hgmp/riscv64 (0.1.2.1-1 to 0.1.2.1-1)
  • Migration status for haskell-hgmp/riscv64 (0.1.2.1-1 to 0.1.2.1-1): Will attempt migration (Any information below is purely informational)
• haskell-hi-file-parser/riscv64 (0.1.5.0-1 to 0.1.5.0-1)
  • Migration status for haskell-hi-file-parser/riscv64 (0.1.5.0-1 to 0.1.5.0-1): Will attempt migration (Any information below is purely informational)
• haskell-hierarchical-clustering/riscv64 (0.4.7-3 to 0.4.7-3)
  • Migration status for haskell-hierarchical-clustering/riscv64 (0.4.7-3 to 0.4.7-3): Will attempt migration (Any information below is purely informational)
• haskell-hinotify/riscv64 (0.4.1-2 to 0.4.1-2)
  • Migration status for haskell-hinotify/riscv64 (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• haskell-hint/riscv64 (0.9.0.7-1 to 0.9.0.7-1)
  • Migration status for haskell-hint/riscv64 (0.9.0.7-1 to 0.9.0.7-1): Will attempt migration (Any information below is purely informational)
• haskell-hjsmin/riscv64 (0.2.1-1 to 0.2.1-1)
  • Migration status for haskell-hjsmin/riscv64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• haskell-hledger-lib/riscv64 (1.30-1 to 1.30-1)
  • Migration status for haskell-hledger-lib/riscv64 (1.30-1 to 1.30-1): Will attempt migration (Any information below is purely informational)
• haskell-hledger/riscv64 (1.30.1-1 to 1.30.1-1)
  • Migration status for haskell-hledger/riscv64 (1.30.1-1 to 1.30.1-1): Will attempt migration (Any information below is purely informational)
• haskell-hmatrix-gsl/riscv64 (0.19.0.1-4 to 0.19.0.1-4)
  • Migration status for haskell-hmatrix-gsl/riscv64 (0.19.0.1-4 to 0.19.0.1-4): Will attempt migration (Any information below is purely informational)
• haskell-hmatrix/riscv64 (0.20.2-3 to 0.20.2-3)
  • Migration status for haskell-hmatrix/riscv64 (0.20.2-3 to 0.20.2-3): Will attempt migration (Any information below is purely informational)
• haskell-hoogle/riscv64 (5.0.18.3+dfsg1-5 to 5.0.18.3+dfsg1-5)
  • Migration status for haskell-hoogle/riscv64 (5.0.18.3+dfsg1-5 to 5.0.18.3+dfsg1-5): Will attempt migration (Any information below is purely informational)
• haskell-hookup/riscv64 (0.7-2 to 0.7-2)
  • Migration status for haskell-hookup/riscv64 (0.7-2 to 0.7-2): Will attempt migration (Any information below is purely informational)
• haskell-hopenpgp/riscv64 (2.9.8-2 to 2.9.8-2)
  • Migration status for haskell-hopenpgp/riscv64 (2.9.8-2 to 2.9.8-2): Will attempt migration (Any information below is purely informational)
• haskell-hosc/riscv64 (0.20-1 to 0.20-1)
  • Migration status for haskell-hosc/riscv64 (0.20-1 to 0.20-1): Will attempt migration (Any information below is purely informational)
• haskell-hostname/riscv64 (1.0-17 to 1.0-17)
  • Migration status for haskell-hostname/riscv64 (1.0-17 to 1.0-17): Will attempt migration (Any information below is purely informational)
• haskell-hourglass/riscv64 (0.2.12-6 to 0.2.12-6)
  • Migration status for haskell-hourglass/riscv64 (0.2.12-6 to 0.2.12-6): Will attempt migration (Any information below is purely informational)
• haskell-hpack/riscv64 (0.35.2-1 to 0.35.2-1)
  • Migration status for haskell-hpack/riscv64 (0.35.2-1 to 0.35.2-1): Will attempt migration (Any information below is purely informational)
• haskell-hs-bibutils/riscv64 (6.10.0.0-5 to 6.10.0.0-5)
  • Migration status for haskell-hs-bibutils/riscv64 (6.10.0.0-5 to 6.10.0.0-5): Will attempt migration (Any information below is purely informational)
• haskell-hsemail/riscv64 (2.2.1-2 to 2.2.1-2)
  • Migration status for haskell-hsemail/riscv64 (2.2.1-2 to 2.2.1-2): Will attempt migration (Any information below is purely informational)
• haskell-hsini/riscv64 (0.5.2.2-1 to 0.5.2.2-1)
  • Migration status for haskell-hsini/riscv64 (0.5.2.2-1 to 0.5.2.2-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-aeson/riscv64 (2.3.0.1-1 to 2.3.0.1-1)
  • Migration status for haskell-hslua-aeson/riscv64 (2.3.0.1-1 to 2.3.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-classes/riscv64 (2.3.0-1 to 2.3.0-1)
  • Migration status for haskell-hslua-classes/riscv64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-cli/riscv64 (1.4.1-1 to 1.4.1-1)
  • Migration status for haskell-hslua-cli/riscv64 (1.4.1-1 to 1.4.1-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-core/riscv64 (2.3.1-1 to 2.3.1-1)
  • Migration status for haskell-hslua-core/riscv64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-list/riscv64 (1.1.1-2 to 1.1.1-2)
  • Migration status for haskell-hslua-list/riscv64 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• haskell-hslua-marshalling/riscv64 (2.3.0-1 to 2.3.0-1)
  • Migration status for haskell-hslua-marshalling/riscv64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-module-doclayout/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for haskell-hslua-module-doclayout/riscv64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-hslua-module-path/riscv64 (1.1.0-1 to 1.1.0-1)
  • Migration status for haskell-hslua-module-path/riscv64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-module-system/riscv64 (1.1.0.1-1 to 1.1.0.1-1)
  • Migration status for haskell-hslua-module-system/riscv64 (1.1.0.1-1 to 1.1.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-module-text/riscv64 (1.1.0.1-1 to 1.1.0.1-1)
  • Migration status for haskell-hslua-module-text/riscv64 (1.1.0.1-1 to 1.1.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-module-version/riscv64 (1.1.0-1 to 1.1.0-1)
  • Migration status for haskell-hslua-module-version/riscv64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-module-zip/riscv64 (1.1.0-3 to 1.1.0-3)
  • Migration status for haskell-hslua-module-zip/riscv64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• haskell-hslua-objectorientation/riscv64 (2.3.0-1 to 2.3.0-1)
  • Migration status for haskell-hslua-objectorientation/riscv64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-packaging/riscv64 (2.3.0-1 to 2.3.0-1)
  • Migration status for haskell-hslua-packaging/riscv64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-hslua-repl/riscv64 (0.1.1-2 to 0.1.1-2)
  • Migration status for haskell-hslua-repl/riscv64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• haskell-hslua-typing/riscv64 (0.1.0-2 to 0.1.0-2)
  • Migration status for haskell-hslua-typing/riscv64 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-hslua/riscv64 (2.3.0-1 to 2.3.0-1)
  • Migration status for haskell-hslua/riscv64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-hsopenssl-x509-system/riscv64 (0.1.0.4-2 to 0.1.0.4-2)
  • Migration status for haskell-hsopenssl-x509-system/riscv64 (0.1.0.4-2 to 0.1.0.4-2): Will attempt migration (Any information below is purely informational)
• haskell-hsp/riscv64 (0.10.0-11 to 0.10.0-11)
  • Migration status for haskell-hsp/riscv64 (0.10.0-11 to 0.10.0-11): Will attempt migration (Any information below is purely informational)
• haskell-hspec-attoparsec/riscv64 (0.1.0.2-9 to 0.1.0.2-9)
  • Migration status for haskell-hspec-attoparsec/riscv64 (0.1.0.2-9 to 0.1.0.2-9): Will attempt migration (Any information below is purely informational)
• haskell-hspec-contrib/riscv64 (0.5.2-1 to 0.5.2-1)
  • Migration status for haskell-hspec-contrib/riscv64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• haskell-hspec-core/riscv64 (2.10.10-1 to 2.10.10-1)
  • Migration status for haskell-hspec-core/riscv64 (2.10.10-1 to 2.10.10-1): Will attempt migration (Any information below is purely informational)
• haskell-hspec-expectations/riscv64 (0.8.2-6 to 0.8.2-6)
  • Migration status for haskell-hspec-expectations/riscv64 (0.8.2-6 to 0.8.2-6): Will attempt migration (Any information below is purely informational)
• haskell-hspec-hedgehog/riscv64 (0.0.1.2-5 to 0.0.1.2-5)
  • Migration status for haskell-hspec-hedgehog/riscv64 (0.0.1.2-5 to 0.0.1.2-5): Will attempt migration (Any information below is purely informational)
• haskell-hspec-megaparsec/riscv64 (2.2.0-2 to 2.2.0-2)
  • Migration status for haskell-hspec-megaparsec/riscv64 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-hspec-smallcheck/riscv64 (0.5.3-1 to 0.5.3-1)
  • Migration status for haskell-hspec-smallcheck/riscv64 (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
• haskell-hspec-wai/riscv64 (0.11.1-2 to 0.11.1-2)
  • Migration status for haskell-hspec-wai/riscv64 (0.11.1-2 to 0.11.1-2): Will attempt migration (Any information below is purely informational)
• haskell-hspec/riscv64 (2.10.10-1 to 2.10.10-1)
  • Migration status for haskell-hspec/riscv64 (2.10.10-1 to 2.10.10-1): Will attempt migration (Any information below is purely informational)
• haskell-hstringtemplate/riscv64 (0.8.8-3 to 0.8.8-3)
  • Migration status for haskell-hstringtemplate/riscv64 (0.8.8-3 to 0.8.8-3): Will attempt migration (Any information below is purely informational)
• haskell-hsx-jmacro/riscv64 (7.3.8.2-2 to 7.3.8.2-2)
  • Migration status for haskell-hsx-jmacro/riscv64 (7.3.8.2-2 to 7.3.8.2-2): Will attempt migration (Any information below is purely informational)
• haskell-hsx2hs/riscv64 (0.14.1.11-1 to 0.14.1.11-1)
  • Migration status for haskell-hsx2hs/riscv64 (0.14.1.11-1 to 0.14.1.11-1): Will attempt migration (Any information below is purely informational)
• haskell-hsyslog/riscv64 (5.0.2-4 to 5.0.2-4)
  • Migration status for haskell-hsyslog/riscv64 (5.0.2-4 to 5.0.2-4): Will attempt migration (Any information below is purely informational)
• haskell-html-conduit/riscv64 (1.3.2.2-2 to 1.3.2.2-2)
  • Migration status for haskell-html-conduit/riscv64 (1.3.2.2-2 to 1.3.2.2-2): Will attempt migration (Any information below is purely informational)
• haskell-html/riscv64 (1.0.1.2-18 to 1.0.1.2-18)
  • Migration status for haskell-html/riscv64 (1.0.1.2-18 to 1.0.1.2-18): Will attempt migration (Any information below is purely informational)
• haskell-http-api-data/riscv64 (0.5-1 to 0.5-1)
  • Migration status for haskell-http-api-data/riscv64 (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
• haskell-http-client-restricted/riscv64 (0.0.5-2 to 0.0.5-2)
  • Migration status for haskell-http-client-restricted/riscv64 (0.0.5-2 to 0.0.5-2): Will attempt migration (Any information below is purely informational)
• haskell-http-client-tls/riscv64 (0.3.6.1-2 to 0.3.6.1-2)
  • Migration status for haskell-http-client-tls/riscv64 (0.3.6.1-2 to 0.3.6.1-2): Will attempt migration (Any information below is purely informational)
• haskell-http-client/riscv64 (0.7.14-1 to 0.7.14-1)
  • Migration status for haskell-http-client/riscv64 (0.7.14-1 to 0.7.14-1): Will attempt migration (Any information below is purely informational)
• haskell-http-common/riscv64 (0.8.3.4-2 to 0.8.3.4-2)
  • Migration status for haskell-http-common/riscv64 (0.8.3.4-2 to 0.8.3.4-2): Will attempt migration (Any information below is purely informational)
• haskell-http-conduit/riscv64 (2.3.8.1-2 to 2.3.8.1-2)
  • Migration status for haskell-http-conduit/riscv64 (2.3.8.1-2 to 2.3.8.1-2): Will attempt migration (Any information below is purely informational)
• haskell-http-date/riscv64 (0.0.11-2 to 0.0.11-2)
  • Migration status for haskell-http-date/riscv64 (0.0.11-2 to 0.0.11-2): Will attempt migration (Any information below is purely informational)
• haskell-http-download/riscv64 (0.2.0.0-4 to 0.2.0.0-4)
  • Migration status for haskell-http-download/riscv64 (0.2.0.0-4 to 0.2.0.0-4): Will attempt migration (Any information below is purely informational)
• haskell-http-link-header/riscv64 (1.2.1-2 to 1.2.1-2)
  • Migration status for haskell-http-link-header/riscv64 (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
• haskell-http-media/riscv64 (0.8.1.1-1 to 0.8.1.1-1)
  • Migration status for haskell-http-media/riscv64 (0.8.1.1-1 to 0.8.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-http-reverse-proxy/riscv64 (0.6.0.1-2 to 0.6.0.1-2)
  • Migration status for haskell-http-reverse-proxy/riscv64 (0.6.0.1-2 to 0.6.0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-http-streams/riscv64 (0.8.9.8-1 to 0.8.9.8-1)
  • Migration status for haskell-http-streams/riscv64 (0.8.9.8-1 to 0.8.9.8-1): Will attempt migration (Any information below is purely informational)
• haskell-http-types/riscv64 (0.12.3-6 to 0.12.3-6)
  • Migration status for haskell-http-types/riscv64 (0.12.3-6 to 0.12.3-6): Will attempt migration (Any information below is purely informational)
• haskell-http/riscv64 (1:4000.4.1-1 to 1:4000.4.1-1)
  • Migration status for haskell-http/riscv64 (1:4000.4.1-1 to 1:4000.4.1-1): Will attempt migration (Any information below is purely informational)
• haskell-http2/riscv64 (4.1.4-1 to 4.1.4-1)
  • Migration status for haskell-http2/riscv64 (4.1.4-1 to 4.1.4-1): Will attempt migration (Any information below is purely informational)
• haskell-hunit/riscv64 (1.6.2.0-2 to 1.6.2.0-2)
  • Migration status for haskell-hunit/riscv64 (1.6.2.0-2 to 1.6.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-hxt-charproperties/riscv64 (9.5.0.0-2 to 9.5.0.0-2)
  • Migration status for haskell-hxt-charproperties/riscv64 (9.5.0.0-2 to 9.5.0.0-2): Will attempt migration (Any information below is purely informational)
• haskell-hxt-curl/riscv64 (9.1.1.1-12 to 9.1.1.1-12)
  • Migration status for haskell-hxt-curl/riscv64 (9.1.1.1-12 to 9.1.1.1-12): Will attempt migration (Any information below is purely informational)
• haskell-hxt-http/riscv64 (9.1.5.2-13 to 9.1.5.2-13)
  • Migration status for haskell-hxt-http/riscv64 (9.1.5.2-13 to 9.1.5.2-13): Will attempt migration (Any information below is purely informational)
• haskell-hxt-regex-xmlschema/riscv64 (9.2.0.7-2 to 9.2.0.7-2)
  • Migration status for haskell-hxt-regex-xmlschema/riscv64 (9.2.0.7-2 to 9.2.0.7-2): Will attempt migration (Any information below is purely informational)
• haskell-hxt-relaxng/riscv64 (9.1.5.5-14 to 9.1.5.5-14)
  • Migration status for haskell-hxt-relaxng/riscv64 (9.1.5.5-14 to 9.1.5.5-14): Will attempt migration (Any information below is purely informational)
• haskell-hxt-tagsoup/riscv64 (9.1.4-8 to 9.1.4-8)
  • Migration status for haskell-hxt-tagsoup/riscv64 (9.1.4-8 to 9.1.4-8): Will attempt migration (Any information below is purely informational)
• haskell-hxt-unicode/riscv64 (9.0.2.4-11 to 9.0.2.4-11)
  • Migration status for haskell-hxt-unicode/riscv64 (9.0.2.4-11 to 9.0.2.4-11): Will attempt migration (Any information below is purely informational)
• haskell-hxt/riscv64 (9.3.1.22-2 to 9.3.1.22-2)
  • Migration status for haskell-hxt/riscv64 (9.3.1.22-2 to 9.3.1.22-2): Will attempt migration (Any information below is purely informational)
• haskell-iconv/riscv64 (0.4.1.3-10 to 0.4.1.3-10)
  • Migration status for haskell-iconv/riscv64 (0.4.1.3-10 to 0.4.1.3-10): Will attempt migration (Any information below is purely informational)
• haskell-idna/riscv64 (0.3.0-13 to 0.3.0-13)
  • Migration status for haskell-idna/riscv64 (0.3.0-13 to 0.3.0-13): Will attempt migration (Any information below is purely informational)
• haskell-ieee754/riscv64 (0.8.0-6 to 0.8.0-6)
  • Migration status for haskell-ieee754/riscv64 (0.8.0-6 to 0.8.0-6): Will attempt migration (Any information below is purely informational)
• haskell-ifelse/riscv64 (0.85-18 to 0.85-18)
  • Migration status for haskell-ifelse/riscv64 (0.85-18 to 0.85-18): Will attempt migration (Any information below is purely informational)
• haskell-incremental-parser/riscv64 (0.5.0.5-1 to 0.5.0.5-1)
  • Migration status for haskell-incremental-parser/riscv64 (0.5.0.5-1 to 0.5.0.5-1): Will attempt migration (Any information below is purely informational)
• haskell-indexed-profunctors/riscv64 (0.1.1.1-1 to 0.1.1.1-1)
  • Migration status for haskell-indexed-profunctors/riscv64 (0.1.1.1-1 to 0.1.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-indexed-traversable-instances/riscv64 (0.1.1.2-1 to 0.1.1.2-1)
  • Migration status for haskell-indexed-traversable-instances/riscv64 (0.1.1.2-1 to 0.1.1.2-1): Will attempt migration (Any information below is purely informational)
• haskell-indexed-traversable/riscv64 (0.1.3-1 to 0.1.3-1)
  • Migration status for haskell-indexed-traversable/riscv64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• haskell-infer-license/riscv64 (0.2.0-5 to 0.2.0-5)
  • Migration status for haskell-infer-license/riscv64 (0.2.0-5 to 0.2.0-5): Will attempt migration (Any information below is purely informational)
• haskell-infinite-list/riscv64 (0.1-2 to 0.1-2)
  • Migration status for haskell-infinite-list/riscv64 (0.1-2 to 0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-ini/riscv64 (0.4.2-2 to 0.4.2-2)
  • Migration status for haskell-ini/riscv64 (0.4.2-2 to 0.4.2-2): Will attempt migration (Any information below is purely informational)
• haskell-inline-c/riscv64 (0.9.1.10-1 to 0.9.1.10-1)
  • Migration status for haskell-inline-c/riscv64 (0.9.1.10-1 to 0.9.1.10-1): Will attempt migration (Any information below is purely informational)
• haskell-input-parsers/riscv64 (0.3.0.1-1 to 0.3.0.1-1)
  • Migration status for haskell-input-parsers/riscv64 (0.3.0.1-1 to 0.3.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-inspection-testing/riscv64 (0.5.0.2-1 to 0.5.0.2-1)
  • Migration status for haskell-inspection-testing/riscv64 (0.5.0.2-1 to 0.5.0.2-1): Will attempt migration (Any information below is purely informational)
• haskell-integer-logarithms/riscv64 (1.0.3.1-3 to 1.0.3.1-3)
  • Migration status for haskell-integer-logarithms/riscv64 (1.0.3.1-3 to 1.0.3.1-3): Will attempt migration (Any information below is purely informational)
• haskell-interpolate/riscv64 (0.2.1-3 to 0.2.1-3)
  • Migration status for haskell-interpolate/riscv64 (0.2.1-3 to 0.2.1-3): Will attempt migration (Any information below is purely informational)
• haskell-intervals/riscv64 (0.9.2-2 to 0.9.2-2)
  • Migration status for haskell-intervals/riscv64 (0.9.2-2 to 0.9.2-2): Will attempt migration (Any information below is purely informational)
• haskell-invariant/riscv64 (0.6.2-1 to 0.6.2-1)
  • Migration status for haskell-invariant/riscv64 (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
• haskell-io-storage/riscv64 (0.3-16 to 0.3-16)
  • Migration status for haskell-io-storage/riscv64 (0.3-16 to 0.3-16): Will attempt migration (Any information below is purely informational)
• haskell-io-streams-haproxy/riscv64 (1.0.1.0-5 to 1.0.1.0-5)
  • Migration status for haskell-io-streams-haproxy/riscv64 (1.0.1.0-5 to 1.0.1.0-5): Will attempt migration (Any information below is purely informational)
• haskell-io-streams/riscv64 (1.5.2.2-2 to 1.5.2.2-2)
  • Migration status for haskell-io-streams/riscv64 (1.5.2.2-2 to 1.5.2.2-2): Will attempt migration (Any information below is purely informational)
• haskell-iospec/riscv64 (0.3.1.2-1 to 0.3.1.2-1)
  • Migration status for haskell-iospec/riscv64 (0.3.1.2-1 to 0.3.1.2-1): Will attempt migration (Any information below is purely informational)
• haskell-iproute/riscv64 (1.7.12-2 to 1.7.12-2)
  • Migration status for haskell-iproute/riscv64 (1.7.12-2 to 1.7.12-2): Will attempt migration (Any information below is purely informational)
• haskell-ipynb/riscv64 (0.2-2 to 0.2-2)
  • Migration status for haskell-ipynb/riscv64 (0.2-2 to 0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-irc-core/riscv64 (2.12-1 to 2.12-1)
  • Migration status for haskell-irc-core/riscv64 (2.12-1 to 2.12-1): Will attempt migration (Any information below is purely informational)
• haskell-irc/riscv64 (0.6.1.0-12 to 0.6.1.0-12)
  • Migration status for haskell-irc/riscv64 (0.6.1.0-12 to 0.6.1.0-12): Will attempt migration (Any information below is purely informational)
• haskell-iso8601-time/riscv64 (0.1.5-5 to 0.1.5-5)
  • Migration status for haskell-iso8601-time/riscv64 (0.1.5-5 to 0.1.5-5): Will attempt migration (Any information below is purely informational)
• haskell-isocline/riscv64 (1.0.9-2 to 1.0.9-2)
  • Migration status for haskell-isocline/riscv64 (1.0.9-2 to 1.0.9-2): Will attempt migration (Any information below is purely informational)
• haskell-isomorphism-class/riscv64 (0.1.0.10-1 to 0.1.0.10-1)
  • Migration status for haskell-isomorphism-class/riscv64 (0.1.0.10-1 to 0.1.0.10-1): Will attempt migration (Any information below is purely informational)
• haskell-iwlib/riscv64 (0.1.2-2 to 0.1.2-2)
  • Migration status for haskell-iwlib/riscv64 (0.1.2-2 to 0.1.2-2): Will attempt migration (Any information below is purely informational)
• haskell-ixset-typed/riscv64 (0.5.1.0-2 to 0.5.1.0-2)
  • Migration status for haskell-ixset-typed/riscv64 (0.5.1.0-2 to 0.5.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-jira-wiki-markup/riscv64 (1.5.1-1 to 1.5.1-1)
  • Migration status for haskell-jira-wiki-markup/riscv64 (1.5.1-1 to 1.5.1-1): Will attempt migration (Any information below is purely informational)
• haskell-jmacro/riscv64 (0.6.18-1 to 0.6.18-1)
  • Migration status for haskell-jmacro/riscv64 (0.6.18-1 to 0.6.18-1): Will attempt migration (Any information below is purely informational)
• haskell-js-dgtable/riscv64 (0.5.2-4 to 0.5.2-4)
  • Migration status for haskell-js-dgtable/riscv64 (0.5.2-4 to 0.5.2-4): Will attempt migration (Any information below is purely informational)
• haskell-js-flot/riscv64 (0.8.3-11 to 0.8.3-11)
  • Migration status for haskell-js-flot/riscv64 (0.8.3-11 to 0.8.3-11): Will attempt migration (Any information below is purely informational)
• haskell-js-jquery/riscv64 (3.3.1-5 to 3.3.1-5)
  • Migration status for haskell-js-jquery/riscv64 (3.3.1-5 to 3.3.1-5): Will attempt migration (Any information below is purely informational)
• haskell-json/riscv64 (0.10-3 to 0.10-3)
  • Migration status for haskell-json/riscv64 (0.10-3 to 0.10-3): Will attempt migration (Any information below is purely informational)
• haskell-juicypixels/riscv64 (3.3.8-1 to 3.3.8-1)
  • Migration status for haskell-juicypixels/riscv64 (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
• haskell-jwt/riscv64 (0.11.0-2 to 0.11.0-2)
  • Migration status for haskell-jwt/riscv64 (0.11.0-2 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
• haskell-kan-extensions/riscv64 (5.2.5-2 to 5.2.5-2)
  • Migration status for haskell-kan-extensions/riscv64 (5.2.5-2 to 5.2.5-2): Will attempt migration (Any information below is purely informational)
• haskell-keys/riscv64 (3.12.3-3 to 3.12.3-3)
  • Migration status for haskell-keys/riscv64 (3.12.3-3 to 3.12.3-3): Will attempt migration (Any information below is purely informational)
• haskell-knob/riscv64 (0.2.2-1 to 0.2.2-1)
  • Migration status for haskell-knob/riscv64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• haskell-kvitable/riscv64 (1.0.2.1-1 to 1.0.2.1-1)
  • Migration status for haskell-kvitable/riscv64 (1.0.2.1-1 to 1.0.2.1-1): Will attempt migration (Any information below is purely informational)
• haskell-lambdabot-core/riscv64 (5.3.1.1-1 to 5.3.1.1-1)
  • Migration status for haskell-lambdabot-core/riscv64 (5.3.1.1-1 to 5.3.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-lambdabot-haskell-plugins/riscv64 (5.3.1.1-1 to 5.3.1.1-1)
  • Migration status for haskell-lambdabot-haskell-plugins/riscv64 (5.3.1.1-1 to 5.3.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-lambdabot-irc-plugins/riscv64 (5.3.1.1-1 to 5.3.1.1-1)
  • Migration status for haskell-lambdabot-irc-plugins/riscv64 (5.3.1.1-1 to 5.3.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-lambdabot-misc-plugins/riscv64 (5.3.1.1-1 to 5.3.1.1-1)
  • Migration status for haskell-lambdabot-misc-plugins/riscv64 (5.3.1.1-1 to 5.3.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-lambdabot-reference-plugins/riscv64 (5.3.1.1-1 to 5.3.1.1-1)
  • Migration status for haskell-lambdabot-reference-plugins/riscv64 (5.3.1.1-1 to 5.3.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-lambdabot-social-plugins/riscv64 (5.3.1.1-1 to 5.3.1.1-1)
  • Migration status for haskell-lambdabot-social-plugins/riscv64 (5.3.1.1-1 to 5.3.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-lambdabot-trusted/riscv64 (5.3.1.1-1 to 5.3.1.1-1)
  • Migration status for haskell-lambdabot-trusted/riscv64 (5.3.1.1-1 to 5.3.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-lambdahack/riscv64 (0.11.0.0-4 to 0.11.0.0-4)
  • Migration status for haskell-lambdahack/riscv64 (0.11.0.0-4 to 0.11.0.0-4): Will attempt migration (Any information below is purely informational)
• haskell-language-c/riscv64 (0.9.2-1 to 0.9.2-1)
  • Migration status for haskell-language-c/riscv64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• haskell-language-c99-simple/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for haskell-language-c99-simple/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-language-c99-util/riscv64 (0.2.0-2 to 0.2.0-2)
  • Migration status for haskell-language-c99-util/riscv64 (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-language-c99/riscv64 (0.2.0-2 to 0.2.0-2)
  • Migration status for haskell-language-c99/riscv64 (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-language-glsl/riscv64 (0.3.0-3 to 0.3.0-3)
  • Migration status for haskell-language-glsl/riscv64 (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
• haskell-language-javascript/riscv64 (0.7.1.0-3 to 0.7.1.0-3)
  • Migration status for haskell-language-javascript/riscv64 (0.7.1.0-3 to 0.7.1.0-3): Will attempt migration (Any information below is purely informational)
• haskell-language-python/riscv64 (0.5.8-3 to 0.5.8-3)
  • Migration status for haskell-language-python/riscv64 (0.5.8-3 to 0.5.8-3): Will attempt migration (Any information below is purely informational)
• haskell-lazy-csv/riscv64 (0.5.1-6 to 0.5.1-6)
  • Migration status for haskell-lazy-csv/riscv64 (0.5.1-6 to 0.5.1-6): Will attempt migration (Any information below is purely informational)
• haskell-lazysmallcheck/riscv64 (0.6-14 to 0.6-14)
  • Migration status for haskell-lazysmallcheck/riscv64 (0.6-14 to 0.6-14): Will attempt migration (Any information below is purely informational)
• haskell-lens-action/riscv64 (0.2.6-2 to 0.2.6-2)
  • Migration status for haskell-lens-action/riscv64 (0.2.6-2 to 0.2.6-2): Will attempt migration (Any information below is purely informational)
• haskell-lens-aeson/riscv64 (1.2.3-1 to 1.2.3-1)
  • Migration status for haskell-lens-aeson/riscv64 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
• haskell-lens-family-core/riscv64 (2.1.2-2 to 2.1.2-2)
  • Migration status for haskell-lens-family-core/riscv64 (2.1.2-2 to 2.1.2-2): Will attempt migration (Any information below is purely informational)
• haskell-lens/riscv64 (5.2.3-1 to 5.2.3-1)
  • Migration status for haskell-lens/riscv64 (5.2.3-1 to 5.2.3-1): Will attempt migration (Any information below is purely informational)
• haskell-lexer/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for haskell-lexer/riscv64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-libbf/riscv64 (0.6.6-2 to 0.6.6-2)
  • Migration status for haskell-libbf/riscv64 (0.6.6-2 to 0.6.6-2): Will attempt migration (Any information below is purely informational)
• haskell-libffi/riscv64 (0.2.1-1 to 0.2.1-1)
  • Migration status for haskell-libffi/riscv64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• haskell-libmpd/riscv64 (0.10.0.0-2 to 0.10.0.0-2)
  • Migration status for haskell-libmpd/riscv64 (0.10.0.0-2 to 0.10.0.0-2): Will attempt migration (Any information below is purely informational)
• haskell-libyaml/riscv64 (0.1.2-3 to 0.1.2-3)
  • Migration status for haskell-libyaml/riscv64 (0.1.2-3 to 0.1.2-3): Will attempt migration (Any information below is purely informational)
• haskell-lift-type/riscv64 (0.1.1.1-2 to 0.1.1.1-2)
  • Migration status for haskell-lift-type/riscv64 (0.1.1.1-2 to 0.1.1.1-2): Will attempt migration (Any information below is purely informational)
• haskell-lifted-async/riscv64 (0.10.2.4-1 to 0.10.2.4-1)
  • Migration status for haskell-lifted-async/riscv64 (0.10.2.4-1 to 0.10.2.4-1): Will attempt migration (Any information below is purely informational)
• haskell-lifted-base/riscv64 (0.2.3.12-5 to 0.2.3.12-5)
  • Migration status for haskell-lifted-base/riscv64 (0.2.3.12-5 to 0.2.3.12-5): Will attempt migration (Any information below is purely informational)
• haskell-linear/riscv64 (1.22-1 to 1.22-1)
  • Migration status for haskell-linear/riscv64 (1.22-1 to 1.22-1): Will attempt migration (Any information below is purely informational)
• haskell-list/riscv64 (0.6.2-2 to 0.6.2-2)
  • Migration status for haskell-list/riscv64 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• haskell-listlike/riscv64 (4.7.8.2-1 to 4.7.8.2-1)
  • Migration status for haskell-listlike/riscv64 (4.7.8.2-1 to 4.7.8.2-1): Will attempt migration (Any information below is purely informational)
• haskell-load-env/riscv64 (0.2.1.0-4 to 0.2.1.0-4)
  • Migration status for haskell-load-env/riscv64 (0.2.1.0-4 to 0.2.1.0-4): Will attempt migration (Any information below is purely informational)
• haskell-log-domain/riscv64 (0.13.2-2 to 0.13.2-2)
  • Migration status for haskell-log-domain/riscv64 (0.13.2-2 to 0.13.2-2): Will attempt migration (Any information below is purely informational)
• haskell-logging-facade/riscv64 (0.3.1-2 to 0.3.1-2)
  • Migration status for haskell-logging-facade/riscv64 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• haskell-logict/riscv64 (0.8.0.0-1 to 0.8.0.0-1)
  • Migration status for haskell-logict/riscv64 (0.8.0.0-1 to 0.8.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-lpeg/riscv64 (1.0.4-1 to 1.0.4-1)
  • Migration status for haskell-lpeg/riscv64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• haskell-lrucache/riscv64 (1.2.0.1-4 to 1.2.0.1-4)
  • Migration status for haskell-lrucache/riscv64 (1.2.0.1-4 to 1.2.0.1-4): Will attempt migration (Any information below is purely informational)
• haskell-lua-arbitrary/riscv64 (1.0.1.1-1 to 1.0.1.1-1)
  • Migration status for haskell-lua-arbitrary/riscv64 (1.0.1.1-1 to 1.0.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-lua/riscv64 (2.3.1+ds1-1 to 2.3.1+ds1-1)
  • Migration status for haskell-lua/riscv64 (2.3.1+ds1-1 to 2.3.1+ds1-1): Will attempt migration (Any information below is purely informational)
• haskell-lucid-svg/riscv64 (0.7.1.1-1 to 0.7.1.1-1)
  • Migration status for haskell-lucid-svg/riscv64 (0.7.1.1-1 to 0.7.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-lucid/riscv64 (2.11.20230408-1 to 2.11.20230408-1)
  • Migration status for haskell-lucid/riscv64 (2.11.20230408-1 to 2.11.20230408-1): Will attempt migration (Any information below is purely informational)
• haskell-lukko/riscv64 (0.1.1.3-4 to 0.1.1.3-4)
  • Migration status for haskell-lukko/riscv64 (0.1.1.3-4 to 0.1.1.3-4): Will attempt migration (Any information below is purely informational)
• haskell-lumberjack/riscv64 (1.0.3.0-1 to 1.0.3.0-1)
  • Migration status for haskell-lumberjack/riscv64 (1.0.3.0-1 to 1.0.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-lzma/riscv64 (0.0.1.0-1 to 0.0.1.0-1)
  • Migration status for haskell-lzma/riscv64 (0.0.1.0-1 to 0.0.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-managed/riscv64 (1.0.10-1 to 1.0.10-1)
  • Migration status for haskell-managed/riscv64 (1.0.10-1 to 1.0.10-1): Will attempt migration (Any information below is purely informational)
• haskell-map-syntax/riscv64 (0.3-8 to 0.3-8)
  • Migration status for haskell-map-syntax/riscv64 (0.3-8 to 0.3-8): Will attempt migration (Any information below is purely informational)
• haskell-markdown-unlit/riscv64 (0.5.1-2 to 0.5.1-2)
  • Migration status for haskell-markdown-unlit/riscv64 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• haskell-markdown/riscv64 (0.1.17.5-2 to 0.1.17.5-2)
  • Migration status for haskell-markdown/riscv64 (0.1.17.5-2 to 0.1.17.5-2): Will attempt migration (Any information below is purely informational)
• haskell-math-functions/riscv64 (0.3.4.2-2 to 0.3.4.2-2)
  • Migration status for haskell-math-functions/riscv64 (0.3.4.2-2 to 0.3.4.2-2): Will attempt migration (Any information below is purely informational)
• haskell-megaparsec/riscv64 (9.3.1-1 to 9.3.1-1)
  • Migration status for haskell-megaparsec/riscv64 (9.3.1-1 to 9.3.1-1): Will attempt migration (Any information below is purely informational)
• haskell-memoize/riscv64 (1.1.2-2 to 1.1.2-2)
  • Migration status for haskell-memoize/riscv64 (1.1.2-2 to 1.1.2-2): Will attempt migration (Any information below is purely informational)
• haskell-memory/riscv64 (0.18.0-2 to 0.18.0-2)
  • Migration status for haskell-memory/riscv64 (0.18.0-2 to 0.18.0-2): Will attempt migration (Any information below is purely informational)
• haskell-memotrie/riscv64 (0.6.11-1 to 0.6.11-1)
  • Migration status for haskell-memotrie/riscv64 (0.6.11-1 to 0.6.11-1): Will attempt migration (Any information below is purely informational)
• haskell-mersenne-random-pure64/riscv64 (0.2.2.0-6 to 0.2.2.0-6)
  • Migration status for haskell-mersenne-random-pure64/riscv64 (0.2.2.0-6 to 0.2.2.0-6): Will attempt migration (Any information below is purely informational)
• haskell-microlens-aeson/riscv64 (2.5.1-1 to 2.5.1-1)
  • Migration status for haskell-microlens-aeson/riscv64 (2.5.1-1 to 2.5.1-1): Will attempt migration (Any information below is purely informational)
• haskell-microlens-ghc/riscv64 (0.4.14.2-1 to 0.4.14.2-1)
  • Migration status for haskell-microlens-ghc/riscv64 (0.4.14.2-1 to 0.4.14.2-1): Will attempt migration (Any information below is purely informational)
• haskell-microlens-mtl/riscv64 (0.2.0.3-1 to 0.2.0.3-1)
  • Migration status for haskell-microlens-mtl/riscv64 (0.2.0.3-1 to 0.2.0.3-1): Will attempt migration (Any information below is purely informational)
• haskell-microlens-platform/riscv64 (0.4.3.4-1 to 0.4.3.4-1)
  • Migration status for haskell-microlens-platform/riscv64 (0.4.3.4-1 to 0.4.3.4-1): Will attempt migration (Any information below is purely informational)
• haskell-microlens-th/riscv64 (0.4.3.14-1 to 0.4.3.14-1)
  • Migration status for haskell-microlens-th/riscv64 (0.4.3.14-1 to 0.4.3.14-1): Will attempt migration (Any information below is purely informational)
• haskell-microlens/riscv64 (0.4.13.1-1 to 0.4.13.1-1)
  • Migration status for haskell-microlens/riscv64 (0.4.13.1-1 to 0.4.13.1-1): Will attempt migration (Any information below is purely informational)
• haskell-microspec/riscv64 (0.2.1.3-5 to 0.2.1.3-5)
  • Migration status for haskell-microspec/riscv64 (0.2.1.3-5 to 0.2.1.3-5): Will attempt migration (Any information below is purely informational)
• haskell-microstache/riscv64 (1.0.2.3-1 to 1.0.2.3-1)
  • Migration status for haskell-microstache/riscv64 (1.0.2.3-1 to 1.0.2.3-1): Will attempt migration (Any information below is purely informational)
• haskell-mime-mail-ses/riscv64 (0.4.3-2 to 0.4.3-2)
  • Migration status for haskell-mime-mail-ses/riscv64 (0.4.3-2 to 0.4.3-2): Will attempt migration (Any information below is purely informational)
• haskell-mime-mail/riscv64 (0.5.1-2 to 0.5.1-2)
  • Migration status for haskell-mime-mail/riscv64 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• haskell-mime-types/riscv64 (0.1.1.0-2 to 0.1.1.0-2)
  • Migration status for haskell-mime-types/riscv64 (0.1.1.0-2 to 0.1.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-mime/riscv64 (0.4.0.2-10 to 0.4.0.2-10)
  • Migration status for haskell-mime/riscv64 (0.4.0.2-10 to 0.4.0.2-10): Will attempt migration (Any information below is purely informational)
• haskell-minimorph/riscv64 (0.3.0.1-2 to 0.3.0.1-2)
  • Migration status for haskell-minimorph/riscv64 (0.3.0.1-2 to 0.3.0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-miniutter/riscv64 (0.5.1.2-2 to 0.5.1.2-2)
  • Migration status for haskell-miniutter/riscv64 (0.5.1.2-2 to 0.5.1.2-2): Will attempt migration (Any information below is purely informational)
• haskell-mmap/riscv64 (0.5.9-10 to 0.5.9-10)
  • Migration status for haskell-mmap/riscv64 (0.5.9-10 to 0.5.9-10): Will attempt migration (Any information below is purely informational)
• haskell-mmorph/riscv64 (1.2.0-2 to 1.2.0-2)
  • Migration status for haskell-mmorph/riscv64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-mockery/riscv64 (0.3.5-6 to 0.3.5-6)
  • Migration status for haskell-mockery/riscv64 (0.3.5-6 to 0.3.5-6): Will attempt migration (Any information below is purely informational)
• haskell-mod/riscv64 (0.2.0.1-1 to 0.2.0.1-1)
  • Migration status for haskell-mod/riscv64 (0.2.0.1-1 to 0.2.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-monad-chronicle/riscv64 (1.0.1-2 to 1.0.1-2)
  • Migration status for haskell-monad-chronicle/riscv64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-monad-control/riscv64 (1.0.3.1-2 to 1.0.3.1-2)
  • Migration status for haskell-monad-control/riscv64 (1.0.3.1-2 to 1.0.3.1-2): Will attempt migration (Any information below is purely informational)
• haskell-monad-journal/riscv64 (0.8.1-6 to 0.8.1-6)
  • Migration status for haskell-monad-journal/riscv64 (0.8.1-6 to 0.8.1-6): Will attempt migration (Any information below is purely informational)
• haskell-monad-logger/riscv64 (0.3.40-1 to 0.3.40-1)
  • Migration status for haskell-monad-logger/riscv64 (0.3.40-1 to 0.3.40-1): Will attempt migration (Any information below is purely informational)
• haskell-monad-loops/riscv64 (0.4.3-10 to 0.4.3-10)
  • Migration status for haskell-monad-loops/riscv64 (0.4.3-10 to 0.4.3-10): Will attempt migration (Any information below is purely informational)
• haskell-monad-memo/riscv64 (0.5.4-2 to 0.5.4-2)
  • Migration status for haskell-monad-memo/riscv64 (0.5.4-2 to 0.5.4-2): Will attempt migration (Any information below is purely informational)
• haskell-monad-par-extras/riscv64 (0.3.3-13 to 0.3.3-13)
  • Migration status for haskell-monad-par-extras/riscv64 (0.3.3-13 to 0.3.3-13): Will attempt migration (Any information below is purely informational)
• haskell-monad-par/riscv64 (0.3.6-1 to 0.3.6-1)
  • Migration status for haskell-monad-par/riscv64 (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
• haskell-monadlib/riscv64 (3.10.1-2 to 3.10.1-2)
  • Migration status for haskell-monadlib/riscv64 (3.10.1-2 to 3.10.1-2): Will attempt migration (Any information below is purely informational)
• haskell-monadlist/riscv64 (0.0.2-6 to 0.0.2-6)
  • Migration status for haskell-monadlist/riscv64 (0.0.2-6 to 0.0.2-6): Will attempt migration (Any information below is purely informational)
• haskell-monadprompt/riscv64 (1.0.0.5-12 to 1.0.0.5-12)
  • Migration status for haskell-monadprompt/riscv64 (1.0.0.5-12 to 1.0.0.5-12): Will attempt migration (Any information below is purely informational)
• haskell-monadrandom/riscv64 (0.6-1 to 0.6-1)
  • Migration status for haskell-monadrandom/riscv64 (0.6-1 to 0.6-1): Will attempt migration (Any information below is purely informational)
• haskell-monads-tf/riscv64 (0.1.0.3-8 to 0.1.0.3-8)
  • Migration status for haskell-monads-tf/riscv64 (0.1.0.3-8 to 0.1.0.3-8): Will attempt migration (Any information below is purely informational)
• haskell-mono-traversable-instances/riscv64 (0.1.1.0-3 to 0.1.1.0-3)
  • Migration status for haskell-mono-traversable-instances/riscv64 (0.1.1.0-3 to 0.1.1.0-3): Will attempt migration (Any information below is purely informational)
• haskell-mono-traversable/riscv64 (1.0.15.3-3 to 1.0.15.3-3)
  • Migration status for haskell-mono-traversable/riscv64 (1.0.15.3-3 to 1.0.15.3-3): Will attempt migration (Any information below is purely informational)
• haskell-monoid-extras/riscv64 (0.6.2-1 to 0.6.2-1)
  • Migration status for haskell-monoid-extras/riscv64 (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
• haskell-monoid-subclasses/riscv64 (1.2.4-1 to 1.2.4-1)
  • Migration status for haskell-monoid-subclasses/riscv64 (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
• haskell-mountpoints/riscv64 (1.0.2-8 to 1.0.2-8)
  • Migration status for haskell-mountpoints/riscv64 (1.0.2-8 to 1.0.2-8): Will attempt migration (Any information below is purely informational)
• haskell-mtlparse/riscv64 (0.1.4.0-12 to 0.1.4.0-12)
  • Migration status for haskell-mtlparse/riscv64 (0.1.4.0-12 to 0.1.4.0-12): Will attempt migration (Any information below is purely informational)
• haskell-mueval/riscv64 (0.9.3-7 to 0.9.3-7)
  • Migration status for haskell-mueval/riscv64 (0.9.3-7 to 0.9.3-7): Will attempt migration (Any information below is purely informational)
• haskell-multimap/riscv64 (1.2.1-5 to 1.2.1-5)
  • Migration status for haskell-multimap/riscv64 (1.2.1-5 to 1.2.1-5): Will attempt migration (Any information below is purely informational)
• haskell-multipart/riscv64 (0.2.1-2 to 0.2.1-2)
  • Migration status for haskell-multipart/riscv64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• haskell-multiset-comb/riscv64 (0.2.4.2-1 to 0.2.4.2-1)
  • Migration status for haskell-multiset-comb/riscv64 (0.2.4.2-1 to 0.2.4.2-1): Will attempt migration (Any information below is purely informational)
• haskell-multistate/riscv64 (0.8.0.4-2 to 0.8.0.4-2)
  • Migration status for haskell-multistate/riscv64 (0.8.0.4-2 to 0.8.0.4-2): Will attempt migration (Any information below is purely informational)
• haskell-murmur-hash/riscv64 (0.1.0.10-2 to 0.1.0.10-2)
  • Migration status for haskell-murmur-hash/riscv64 (0.1.0.10-2 to 0.1.0.10-2): Will attempt migration (Any information below is purely informational)
• haskell-musicbrainz/riscv64 (0.4.1-4 to 0.4.1-4)
  • Migration status for haskell-musicbrainz/riscv64 (0.4.1-4 to 0.4.1-4): Will attempt migration (Any information below is purely informational)
• haskell-mustache/riscv64 (2.4.2-1 to 2.4.2-1)
  • Migration status for haskell-mustache/riscv64 (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
• haskell-mutable-containers/riscv64 (0.3.4.1-2 to 0.3.4.1-2)
  • Migration status for haskell-mutable-containers/riscv64 (0.3.4.1-2 to 0.3.4.1-2): Will attempt migration (Any information below is purely informational)
• haskell-mwc-random/riscv64 (0.15.0.2-2 to 0.15.0.2-2)
  • Migration status for haskell-mwc-random/riscv64 (0.15.0.2-2 to 0.15.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-names-th/riscv64 (0.3.0.1-3 to 0.3.0.1-3)
  • Migration status for haskell-names-th/riscv64 (0.3.0.1-3 to 0.3.0.1-3): Will attempt migration (Any information below is purely informational)
• haskell-nanospec/riscv64 (0.2.2-5 to 0.2.2-5)
  • Migration status for haskell-nanospec/riscv64 (0.2.2-5 to 0.2.2-5): Will attempt migration (Any information below is purely informational)
• haskell-natural-transformation/riscv64 (0.4-8 to 0.4-8)
  • Migration status for haskell-natural-transformation/riscv64 (0.4-8 to 0.4-8): Will attempt migration (Any information below is purely informational)
• haskell-neat-interpolation/riscv64 (0.5.1.4-1 to 0.5.1.4-1)
  • Migration status for haskell-neat-interpolation/riscv64 (0.5.1.4-1 to 0.5.1.4-1): Will attempt migration (Any information below is purely informational)
• haskell-nettle/riscv64 (0.3.0-6 to 0.3.0-6)
  • Migration status for haskell-nettle/riscv64 (0.3.0-6 to 0.3.0-6): Will attempt migration (Any information below is purely informational)
• haskell-netwire/riscv64 (5.0.3-5 to 5.0.3-5)
  • Migration status for haskell-netwire/riscv64 (5.0.3-5 to 5.0.3-5): Will attempt migration (Any information below is purely informational)
• haskell-network-bsd/riscv64 (2.8.1.0-4 to 2.8.1.0-4)
  • Migration status for haskell-network-bsd/riscv64 (2.8.1.0-4 to 2.8.1.0-4): Will attempt migration (Any information below is purely informational)
• haskell-network-byte-order/riscv64 (0.1.7-1 to 0.1.7-1)
  • Migration status for haskell-network-byte-order/riscv64 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• haskell-network-conduit-tls/riscv64 (1.3.2-6 to 1.3.2-6)
  • Migration status for haskell-network-conduit-tls/riscv64 (1.3.2-6 to 1.3.2-6): Will attempt migration (Any information below is purely informational)
• haskell-network-control/riscv64 (0.0.2-2 to 0.0.2-2)
  • Migration status for haskell-network-control/riscv64 (0.0.2-2 to 0.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-network-info/riscv64 (0.2.1-2 to 0.2.1-2)
  • Migration status for haskell-network-info/riscv64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• haskell-network-multicast/riscv64 (0.3.2-3 to 0.3.2-3)
  • Migration status for haskell-network-multicast/riscv64 (0.3.2-3 to 0.3.2-3): Will attempt migration (Any information below is purely informational)
• haskell-network-run/riscv64 (0.2.6-1 to 0.2.6-1)
  • Migration status for haskell-network-run/riscv64 (0.2.6-1 to 0.2.6-1): Will attempt migration (Any information below is purely informational)
• haskell-network-uri/riscv64 (2.6.4.2-1 to 2.6.4.2-1)
  • Migration status for haskell-network-uri/riscv64 (2.6.4.2-1 to 2.6.4.2-1): Will attempt migration (Any information below is purely informational)
• haskell-network/riscv64 (3.1.4.0-1 to 3.1.4.0-1)
  • Migration status for haskell-network/riscv64 (3.1.4.0-1 to 3.1.4.0-1): Will attempt migration (Any information below is purely informational)
• haskell-newtype-generics/riscv64 (0.6.2-2 to 0.6.2-2)
  • Migration status for haskell-newtype-generics/riscv64 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• haskell-newtype/riscv64 (0.2.2.0-3 to 0.2.2.0-3)
  • Migration status for haskell-newtype/riscv64 (0.2.2.0-3 to 0.2.2.0-3): Will attempt migration (Any information below is purely informational)
• haskell-nonce/riscv64 (1.0.7-6 to 1.0.7-6)
  • Migration status for haskell-nonce/riscv64 (1.0.7-6 to 1.0.7-6): Will attempt migration (Any information below is purely informational)
• haskell-nothunks/riscv64 (0.1.4-2 to 0.1.4-2)
  • Migration status for haskell-nothunks/riscv64 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• haskell-numbers/riscv64 (3000.2.0.2-5 to 3000.2.0.2-5)
  • Migration status for haskell-numbers/riscv64 (3000.2.0.2-5 to 3000.2.0.2-5): Will attempt migration (Any information below is purely informational)
• haskell-numeric-extras/riscv64 (0.1-8 to 0.1-8)
  • Migration status for haskell-numeric-extras/riscv64 (0.1-8 to 0.1-8): Will attempt migration (Any information below is purely informational)
• haskell-numinstances/riscv64 (1.4-11 to 1.4-11)
  • Migration status for haskell-numinstances/riscv64 (1.4-11 to 1.4-11): Will attempt migration (Any information below is purely informational)
• haskell-numtype-dk/riscv64 (0.5.0.3-2 to 0.5.0.3-2)
  • Migration status for haskell-numtype-dk/riscv64 (0.5.0.3-2 to 0.5.0.3-2): Will attempt migration (Any information below is purely informational)
• haskell-objectname/riscv64 (1.1.0.2-2 to 1.1.0.2-2)
  • Migration status for haskell-objectname/riscv64 (1.1.0.2-2 to 1.1.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-oeis/riscv64 (0.3.10-3 to 0.3.10-3)
  • Migration status for haskell-oeis/riscv64 (0.3.10-3 to 0.3.10-3): Will attempt migration (Any information below is purely informational)
• haskell-ofx/riscv64 (0.4.4.0-3 to 0.4.4.0-3)
  • Migration status for haskell-ofx/riscv64 (0.4.4.0-3 to 0.4.4.0-3): Will attempt migration (Any information below is purely informational)
• haskell-old-locale/riscv64 (1.0.0.7-11 to 1.0.0.7-11)
  • Migration status for haskell-old-locale/riscv64 (1.0.0.7-11 to 1.0.0.7-11): Will attempt migration (Any information below is purely informational)
• haskell-old-time/riscv64 (1.1.0.3-13 to 1.1.0.3-13)
  • Migration status for haskell-old-time/riscv64 (1.1.0.3-13 to 1.1.0.3-13): Will attempt migration (Any information below is purely informational)
• haskell-onetuple/riscv64 (0.4.1.1-1 to 0.4.1.1-1)
  • Migration status for haskell-onetuple/riscv64 (0.4.1.1-1 to 0.4.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-only/riscv64 (0.1-5 to 0.1-5)
  • Migration status for haskell-only/riscv64 (0.1-5 to 0.1-5): Will attempt migration (Any information below is purely informational)
• haskell-oo-prototypes/riscv64 (0.1.0.0-10 to 0.1.0.0-10)
  • Migration status for haskell-oo-prototypes/riscv64 (0.1.0.0-10 to 0.1.0.0-10): Will attempt migration (Any information below is purely informational)
• haskell-open-browser/riscv64 (0.2.1.0-9 to 0.2.1.0-9)
  • Migration status for haskell-open-browser/riscv64 (0.2.1.0-9 to 0.2.1.0-9): Will attempt migration (Any information below is purely informational)
• haskell-opengl/riscv64 (3.0.3.0-4 to 3.0.3.0-4)
  • Migration status for haskell-opengl/riscv64 (3.0.3.0-4 to 3.0.3.0-4): Will attempt migration (Any information below is purely informational)
• haskell-openglraw/riscv64 (3.3.4.1-2 to 3.3.4.1-2)
  • Migration status for haskell-openglraw/riscv64 (3.3.4.1-2 to 3.3.4.1-2): Will attempt migration (Any information below is purely informational)
• haskell-openpgp-asciiarmor/riscv64 (0.1.2-4 to 0.1.2-4)
  • Migration status for haskell-openpgp-asciiarmor/riscv64 (0.1.2-4 to 0.1.2-4): Will attempt migration (Any information below is purely informational)
• haskell-openssl-streams/riscv64 (1.2.3.0-2 to 1.2.3.0-2)
  • Migration status for haskell-openssl-streams/riscv64 (1.2.3.0-2 to 1.2.3.0-2): Will attempt migration (Any information below is purely informational)
• haskell-operational/riscv64 (0.2.4.2-1 to 0.2.4.2-1)
  • Migration status for haskell-operational/riscv64 (0.2.4.2-1 to 0.2.4.2-1): Will attempt migration (Any information below is purely informational)
• haskell-optional-args/riscv64 (1.0.2-4 to 1.0.2-4)
  • Migration status for haskell-optional-args/riscv64 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• haskell-options/riscv64 (1.2.1.1-11 to 1.2.1.1-11)
  • Migration status for haskell-options/riscv64 (1.2.1.1-11 to 1.2.1.1-11): Will attempt migration (Any information below is purely informational)
• haskell-optparse-applicative/riscv64 (0.17.1.0-1 to 0.17.1.0-1)
  • Migration status for haskell-optparse-applicative/riscv64 (0.17.1.0-1 to 0.17.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-optparse-simple/riscv64 (0.1.1.4-2 to 0.1.1.4-2)
  • Migration status for haskell-optparse-simple/riscv64 (0.1.1.4-2 to 0.1.1.4-2): Will attempt migration (Any information below is purely informational)
• haskell-ordered-containers/riscv64 (0.2.3-1 to 0.2.3-1)
  • Migration status for haskell-ordered-containers/riscv64 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• haskell-ormolu/riscv64 (0.5.3.0-1 to 0.5.3.0-1)
  • Migration status for haskell-ormolu/riscv64 (0.5.3.0-1 to 0.5.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-pager/riscv64 (0.1.1.0-1 to 0.1.1.0-1)
  • Migration status for haskell-pager/riscv64 (0.1.1.0-1 to 0.1.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-pandoc-lua-engine/riscv64 (0.2.0.1-1 to 0.2.0.1-1)
  • Migration status for haskell-pandoc-lua-engine/riscv64 (0.2.0.1-1 to 0.2.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-pandoc-lua-marshal/riscv64 (0.2.2-1 to 0.2.2-1)
  • Migration status for haskell-pandoc-lua-marshal/riscv64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• haskell-pandoc-server/riscv64 (0.1.0.2-3 to 0.1.0.2-3)
  • Migration status for haskell-pandoc-server/riscv64 (0.1.0.2-3 to 0.1.0.2-3): Will attempt migration (Any information below is purely informational)
• haskell-pandoc-types/riscv64 (1.23.1-1 to 1.23.1-1)
  • Migration status for haskell-pandoc-types/riscv64 (1.23.1-1 to 1.23.1-1): Will attempt migration (Any information below is purely informational)
• haskell-pango/riscv64 (0.13.10.0-1 to 0.13.10.0-1)
  • Migration status for haskell-pango/riscv64 (0.13.10.0-1 to 0.13.10.0-1): Will attempt migration (Any information below is purely informational)
• haskell-panic/riscv64 (0.4.0.1-4 to 0.4.0.1-4)
  • Migration status for haskell-panic/riscv64 (0.4.0.1-4 to 0.4.0.1-4): Will attempt migration (Any information below is purely informational)
• haskell-pantry/riscv64 (0.8.3-1 to 0.8.3-1)
  • Migration status for haskell-pantry/riscv64 (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• haskell-parallel/riscv64 (3.2.2.0-5 to 3.2.2.0-5)
  • Migration status for haskell-parallel/riscv64 (3.2.2.0-5 to 3.2.2.0-5): Will attempt migration (Any information below is purely informational)
• haskell-parameterized-utils/riscv64 (2.1.7.0-1 to 2.1.7.0-1)
  • Migration status for haskell-parameterized-utils/riscv64 (2.1.7.0-1 to 2.1.7.0-1): Will attempt migration (Any information below is purely informational)
• haskell-parseargs/riscv64 (0.2.0.9-4 to 0.2.0.9-4)
  • Migration status for haskell-parseargs/riscv64 (0.2.0.9-4 to 0.2.0.9-4): Will attempt migration (Any information below is purely informational)
• haskell-parsec-numbers/riscv64 (0.1.0-5 to 0.1.0-5)
  • Migration status for haskell-parsec-numbers/riscv64 (0.1.0-5 to 0.1.0-5): Will attempt migration (Any information below is purely informational)
• haskell-parser-combinators/riscv64 (1.3.0-2 to 1.3.0-2)
  • Migration status for haskell-parser-combinators/riscv64 (1.3.0-2 to 1.3.0-2): Will attempt migration (Any information below is purely informational)
• haskell-parsers/riscv64 (0.12.11-2 to 0.12.11-2)
  • Migration status for haskell-parsers/riscv64 (0.12.11-2 to 0.12.11-2): Will attempt migration (Any information below is purely informational)
• haskell-path-io/riscv64 (1.8.1-1 to 1.8.1-1)
  • Migration status for haskell-path-io/riscv64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• haskell-path-pieces/riscv64 (0.2.1-10 to 0.2.1-10)
  • Migration status for haskell-path-pieces/riscv64 (0.2.1-10 to 0.2.1-10): Will attempt migration (Any information below is purely informational)
• haskell-path/riscv64 (0.9.2-2 to 0.9.2-2)
  • Migration status for haskell-path/riscv64 (0.9.2-2 to 0.9.2-2): Will attempt migration (Any information below is purely informational)
• haskell-patience/riscv64 (0.3-3 to 0.3-3)
  • Migration status for haskell-patience/riscv64 (0.3-3 to 0.3-3): Will attempt migration (Any information below is purely informational)
• haskell-pcap/riscv64 (0.4.5.2-16 to 0.4.5.2-16)
  • Migration status for haskell-pcap/riscv64 (0.4.5.2-16 to 0.4.5.2-16): Will attempt migration (Any information below is purely informational)
• haskell-pem/riscv64 (0.2.4-5 to 0.2.4-5)
  • Migration status for haskell-pem/riscv64 (0.2.4-5 to 0.2.4-5): Will attempt migration (Any information below is purely informational)
• haskell-persistent-postgresql/riscv64 (2.13.6.1-1 to 2.13.6.1-1)
  • Migration status for haskell-persistent-postgresql/riscv64 (2.13.6.1-1 to 2.13.6.1-1): Will attempt migration (Any information below is purely informational)
• haskell-persistent-sqlite/riscv64 (2.13.2.0-1 to 2.13.2.0-1)
  • Migration status for haskell-persistent-sqlite/riscv64 (2.13.2.0-1 to 2.13.2.0-1): Will attempt migration (Any information below is purely informational)
• haskell-persistent-template/riscv64 (2.12.0.0-2 to 2.12.0.0-2)
  • Migration status for haskell-persistent-template/riscv64 (2.12.0.0-2 to 2.12.0.0-2): Will attempt migration (Any information below is purely informational)
• haskell-persistent/riscv64 (2.14.6.0-1 to 2.14.6.0-1)
  • Migration status for haskell-persistent/riscv64 (2.14.6.0-1 to 2.14.6.0-1): Will attempt migration (Any information below is purely informational)
• haskell-pid1/riscv64 (0.1.3.1-1 to 0.1.3.1-1)
  • Migration status for haskell-pid1/riscv64 (0.1.3.1-1 to 0.1.3.1-1): Will attempt migration (Any information below is purely informational)
• haskell-pipes-attoparsec/riscv64 (0.6.0-1 to 0.6.0-1)
  • Migration status for haskell-pipes-attoparsec/riscv64 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• haskell-pipes-bytestring/riscv64 (2.1.7-2 to 2.1.7-2)
  • Migration status for haskell-pipes-bytestring/riscv64 (2.1.7-2 to 2.1.7-2): Will attempt migration (Any information below is purely informational)
• haskell-pipes-group/riscv64 (1.0.12-4 to 1.0.12-4)
  • Migration status for haskell-pipes-group/riscv64 (1.0.12-4 to 1.0.12-4): Will attempt migration (Any information below is purely informational)
• haskell-pipes-parse/riscv64 (3.0.9-2 to 3.0.9-2)
  • Migration status for haskell-pipes-parse/riscv64 (3.0.9-2 to 3.0.9-2): Will attempt migration (Any information below is purely informational)
• haskell-pipes-safe/riscv64 (2.3.4-2 to 2.3.4-2)
  • Migration status for haskell-pipes-safe/riscv64 (2.3.4-2 to 2.3.4-2): Will attempt migration (Any information below is purely informational)
• haskell-pipes/riscv64 (4.3.16-2 to 4.3.16-2)
  • Migration status for haskell-pipes/riscv64 (4.3.16-2 to 4.3.16-2): Will attempt migration (Any information below is purely informational)
• haskell-pointed/riscv64 (5.0.4-2 to 5.0.4-2)
  • Migration status for haskell-pointed/riscv64 (5.0.4-2 to 5.0.4-2): Will attempt migration (Any information below is purely informational)
• haskell-pointedlist/riscv64 (0.6.1-11 to 0.6.1-11)
  • Migration status for haskell-pointedlist/riscv64 (0.6.1-11 to 0.6.1-11): Will attempt migration (Any information below is purely informational)
• haskell-polyparse/riscv64 (1.13-3 to 1.13-3)
  • Migration status for haskell-polyparse/riscv64 (1.13-3 to 1.13-3): Will attempt migration (Any information below is purely informational)
• haskell-posix-pty/riscv64 (0.2.2-3 to 0.2.2-3)
  • Migration status for haskell-posix-pty/riscv64 (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• haskell-postgresql-libpq/riscv64 (0.9.5.0-1 to 0.9.5.0-1)
  • Migration status for haskell-postgresql-libpq/riscv64 (0.9.5.0-1 to 0.9.5.0-1): Will attempt migration (Any information below is purely informational)
• haskell-postgresql-simple/riscv64 (0.6.5.1-1 to 0.6.5.1-1)
  • Migration status for haskell-postgresql-simple/riscv64 (0.6.5.1-1 to 0.6.5.1-1): Will attempt migration (Any information below is purely informational)
• haskell-pqueue/riscv64 (1.4.3.0-1 to 1.4.3.0-1)
  • Migration status for haskell-pqueue/riscv64 (1.4.3.0-1 to 1.4.3.0-1): Will attempt migration (Any information below is purely informational)
• haskell-prelude-extras/riscv64 (0.4.0.3-8 to 0.4.0.3-8)
  • Migration status for haskell-prelude-extras/riscv64 (0.4.0.3-8 to 0.4.0.3-8): Will attempt migration (Any information below is purely informational)
• haskell-presburger/riscv64 (1.3.1-10 to 1.3.1-10)
  • Migration status for haskell-presburger/riscv64 (1.3.1-10 to 1.3.1-10): Will attempt migration (Any information below is purely informational)
• haskell-pretty-show/riscv64 (1.10-3 to 1.10-3)
  • Migration status for haskell-pretty-show/riscv64 (1.10-3 to 1.10-3): Will attempt migration (Any information below is purely informational)
• haskell-pretty-simple/riscv64 (4.1.2.0-2 to 4.1.2.0-2)
  • Migration status for haskell-pretty-simple/riscv64 (4.1.2.0-2 to 4.1.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-prettyclass/riscv64 (1.0.0.0-11 to 1.0.0.0-11)
  • Migration status for haskell-prettyclass/riscv64 (1.0.0.0-11 to 1.0.0.0-11): Will attempt migration (Any information below is purely informational)
• haskell-prettyprinter-ansi-terminal/riscv64 (1.1.3-2 to 1.1.3-2)
  • Migration status for haskell-prettyprinter-ansi-terminal/riscv64 (1.1.3-2 to 1.1.3-2): Will attempt migration (Any information below is purely informational)
• haskell-prettyprinter-convert-ansi-wl-pprint/riscv64 (1.1.2-2 to 1.1.2-2)
  • Migration status for haskell-prettyprinter-convert-ansi-wl-pprint/riscv64 (1.1.2-2 to 1.1.2-2): Will attempt migration (Any information below is purely informational)
• haskell-prettyprinter-interp/riscv64 (0.2.0.0-2 to 0.2.0.0-2)
  • Migration status for haskell-prettyprinter-interp/riscv64 (0.2.0.0-2 to 0.2.0.0-2): Will attempt migration (Any information below is purely informational)
• haskell-prettyprinter/riscv64 (1.7.1-2 to 1.7.1-2)
  • Migration status for haskell-prettyprinter/riscv64 (1.7.1-2 to 1.7.1-2): Will attempt migration (Any information below is purely informational)
• haskell-prim-uniq/riscv64 (0.2-3 to 0.2-3)
  • Migration status for haskell-prim-uniq/riscv64 (0.2-3 to 0.2-3): Will attempt migration (Any information below is purely informational)
• haskell-primes/riscv64 (0.2.1.0-15 to 0.2.1.0-15)
  • Migration status for haskell-primes/riscv64 (0.2.1.0-15 to 0.2.1.0-15): Will attempt migration (Any information below is purely informational)
• haskell-primitive-addr/riscv64 (0.1.0.2-2 to 0.1.0.2-2)
  • Migration status for haskell-primitive-addr/riscv64 (0.1.0.2-2 to 0.1.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-primitive-unaligned/riscv64 (0.1.1.2-4 to 0.1.1.2-4)
  • Migration status for haskell-primitive-unaligned/riscv64 (0.1.1.2-4 to 0.1.1.2-4): Will attempt migration (Any information below is purely informational)
• haskell-primitive/riscv64 (0.8.0.0-1 to 0.8.0.0-1)
  • Migration status for haskell-primitive/riscv64 (0.8.0.0-1 to 0.8.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-process-extras/riscv64 (0.7.4-6 to 0.7.4-6)
  • Migration status for haskell-process-extras/riscv64 (0.7.4-6 to 0.7.4-6): Will attempt migration (Any information below is purely informational)
• haskell-profunctors/riscv64 (5.6.2-2 to 5.6.2-2)
  • Migration status for haskell-profunctors/riscv64 (5.6.2-2 to 5.6.2-2): Will attempt migration (Any information below is purely informational)
• haskell-project-template/riscv64 (0.2.1.0-3 to 0.2.1.0-3)
  • Migration status for haskell-project-template/riscv64 (0.2.1.0-3 to 0.2.1.0-3): Will attempt migration (Any information below is purely informational)
• haskell-protobuf/riscv64 (0.2.1.3-4 to 0.2.1.3-4)
  • Migration status for haskell-protobuf/riscv64 (0.2.1.3-4 to 0.2.1.3-4): Will attempt migration (Any information below is purely informational)
• haskell-psqueue/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for haskell-psqueue/riscv64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• haskell-psqueues/riscv64 (0.2.7.3-2 to 0.2.7.3-2)
  • Migration status for haskell-psqueues/riscv64 (0.2.7.3-2 to 0.2.7.3-2): Will attempt migration (Any information below is purely informational)
• haskell-publicsuffixlist/riscv64 (0.1-15 to 0.1-15)
  • Migration status for haskell-publicsuffixlist/riscv64 (0.1-15 to 0.1-15): Will attempt migration (Any information below is purely informational)
• haskell-punycode/riscv64 (2.0-14 to 2.0-14)
  • Migration status for haskell-punycode/riscv64 (2.0-14 to 2.0-14): Will attempt migration (Any information below is purely informational)
• haskell-puremd5/riscv64 (2.1.4-2 to 2.1.4-2)
  • Migration status for haskell-puremd5/riscv64 (2.1.4-2 to 2.1.4-2): Will attempt migration (Any information below is purely informational)
• haskell-pwstore-fast/riscv64 (2.4.4-12 to 2.4.4-12)
  • Migration status for haskell-pwstore-fast/riscv64 (2.4.4-12 to 2.4.4-12): Will attempt migration (Any information below is purely informational)
• haskell-qrencode/riscv64 (1.0.4-13 to 1.0.4-13)
  • Migration status for haskell-qrencode/riscv64 (1.0.4-13 to 1.0.4-13): Will attempt migration (Any information below is purely informational)
• haskell-quickcheck-classes-base/riscv64 (0.6.2.0-4 to 0.6.2.0-4)
  • Migration status for haskell-quickcheck-classes-base/riscv64 (0.6.2.0-4 to 0.6.2.0-4): Will attempt migration (Any information below is purely informational)
• haskell-quickcheck-classes/riscv64 (0.6.5.0-2 to 0.6.5.0-2)
  • Migration status for haskell-quickcheck-classes/riscv64 (0.6.5.0-2 to 0.6.5.0-2): Will attempt migration (Any information below is purely informational)
• haskell-quickcheck-instances/riscv64 (0.3.30-1 to 0.3.30-1)
  • Migration status for haskell-quickcheck-instances/riscv64 (0.3.30-1 to 0.3.30-1): Will attempt migration (Any information below is purely informational)
• haskell-quickcheck-io/riscv64 (0.2.0-6 to 0.2.0-6)
  • Migration status for haskell-quickcheck-io/riscv64 (0.2.0-6 to 0.2.0-6): Will attempt migration (Any information below is purely informational)
• haskell-quickcheck-safe/riscv64 (0.1.0.6-4 to 0.1.0.6-4)
  • Migration status for haskell-quickcheck-safe/riscv64 (0.1.0.6-4 to 0.1.0.6-4): Will attempt migration (Any information below is purely informational)
• haskell-quickcheck-simple/riscv64 (0.1.1.1-3 to 0.1.1.1-3)
  • Migration status for haskell-quickcheck-simple/riscv64 (0.1.1.1-3 to 0.1.1.1-3): Will attempt migration (Any information below is purely informational)
• haskell-quickcheck-text/riscv64 (0.1.2.1-7 to 0.1.2.1-7)
  • Migration status for haskell-quickcheck-text/riscv64 (0.1.2.1-7 to 0.1.2.1-7): Will attempt migration (Any information below is purely informational)
• haskell-quickcheck-unicode/riscv64 (1.0.1.0-6 to 1.0.1.0-6)
  • Migration status for haskell-quickcheck-unicode/riscv64 (1.0.1.0-6 to 1.0.1.0-6): Will attempt migration (Any information below is purely informational)
• haskell-quickcheck/riscv64 (2.14.3-1 to 2.14.3-1)
  • Migration status for haskell-quickcheck/riscv64 (2.14.3-1 to 2.14.3-1): Will attempt migration (Any information below is purely informational)
• haskell-quote-quot/riscv64 (0.2.1.0-1 to 0.2.1.0-1)
  • Migration status for haskell-quote-quot/riscv64 (0.2.1.0-1 to 0.2.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-random-fu/riscv64 (0.3.0.1-1 to 0.3.0.1-1)
  • Migration status for haskell-random-fu/riscv64 (0.3.0.1-1 to 0.3.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-random-shuffle/riscv64 (0.0.4-13 to 0.0.4-13)
  • Migration status for haskell-random-shuffle/riscv64 (0.0.4-13 to 0.0.4-13): Will attempt migration (Any information below is purely informational)
• haskell-random/riscv64 (1.2.1.1-3 to 1.2.1.1-3)
  • Migration status for haskell-random/riscv64 (1.2.1.1-3 to 1.2.1.1-3): Will attempt migration (Any information below is purely informational)
• haskell-rank2classes/riscv64 (1.5.2-1 to 1.5.2-1)
  • Migration status for haskell-rank2classes/riscv64 (1.5.2-1 to 1.5.2-1): Will attempt migration (Any information below is purely informational)
• haskell-rate-limit/riscv64 (1.4.3-1 to 1.4.3-1)
  • Migration status for haskell-rate-limit/riscv64 (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• haskell-raw-strings-qq/riscv64 (1.1-5 to 1.1-5)
  • Migration status for haskell-raw-strings-qq/riscv64 (1.1-5 to 1.1-5): Will attempt migration (Any information below is purely informational)
• haskell-reactive-banana/riscv64 (1.3.2.0-2 to 1.3.2.0-2)
  • Migration status for haskell-reactive-banana/riscv64 (1.3.2.0-2 to 1.3.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-readable/riscv64 (0.3.1-9 to 0.3.1-9)
  • Migration status for haskell-readable/riscv64 (0.3.1-9 to 0.3.1-9): Will attempt migration (Any information below is purely informational)
• haskell-readargs/riscv64 (1.2.3-7 to 1.2.3-7)
  • Migration status for haskell-readargs/riscv64 (1.2.3-7 to 1.2.3-7): Will attempt migration (Any information below is purely informational)
• haskell-readline/riscv64 (1.0.3.0-13 to 1.0.3.0-13)
  • Migration status for haskell-readline/riscv64 (1.0.3.0-13 to 1.0.3.0-13): Will attempt migration (Any information below is purely informational)
• haskell-recaptcha/riscv64 (0.1.0.4-5 to 0.1.0.4-5)
  • Migration status for haskell-recaptcha/riscv64 (0.1.0.4-5 to 0.1.0.4-5): Will attempt migration (Any information below is purely informational)
• haskell-recursion-schemes/riscv64 (5.2.2.4-3 to 5.2.2.4-3)
  • Migration status for haskell-recursion-schemes/riscv64 (5.2.2.4-3 to 5.2.2.4-3): Will attempt migration (Any information below is purely informational)
• haskell-recv/riscv64 (0.1.0-1 to 0.1.0-1)
  • Migration status for haskell-recv/riscv64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-reducers/riscv64 (3.12.4-2 to 3.12.4-2)
  • Migration status for haskell-reducers/riscv64 (3.12.4-2 to 3.12.4-2): Will attempt migration (Any information below is purely informational)
• haskell-refact/riscv64 (0.3.0.2-8 to 0.3.0.2-8)
  • Migration status for haskell-refact/riscv64 (0.3.0.2-8 to 0.3.0.2-8): Will attempt migration (Any information below is purely informational)
• haskell-reflection/riscv64 (2.1.7-1 to 2.1.7-1)
  • Migration status for haskell-reflection/riscv64 (2.1.7-1 to 2.1.7-1): Will attempt migration (Any information below is purely informational)
• haskell-reform-happstack/riscv64 (0.2.5.6-1 to 0.2.5.6-1)
  • Migration status for haskell-reform-happstack/riscv64 (0.2.5.6-1 to 0.2.5.6-1): Will attempt migration (Any information below is purely informational)
• haskell-reform/riscv64 (0.2.7.5-2 to 0.2.7.5-2)
  • Migration status for haskell-reform/riscv64 (0.2.7.5-2 to 0.2.7.5-2): Will attempt migration (Any information below is purely informational)
• haskell-regex-applicative-text/riscv64 (0.1.0.1-10 to 0.1.0.1-10)
  • Migration status for haskell-regex-applicative-text/riscv64 (0.1.0.1-10 to 0.1.0.1-10): Will attempt migration (Any information below is purely informational)
• haskell-regex-applicative/riscv64 (0.3.4-2 to 0.3.4-2)
  • Migration status for haskell-regex-applicative/riscv64 (0.3.4-2 to 0.3.4-2): Will attempt migration (Any information below is purely informational)
• haskell-regex-base/riscv64 (0.94.0.2-2 to 0.94.0.2-2)
  • Migration status for haskell-regex-base/riscv64 (0.94.0.2-2 to 0.94.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-regex-compat/riscv64 (0.95.2.1-2 to 0.95.2.1-2)
  • Migration status for haskell-regex-compat/riscv64 (0.95.2.1-2 to 0.95.2.1-2): Will attempt migration (Any information below is purely informational)
• haskell-regex-posix/riscv64 (0.96.0.1-2 to 0.96.0.1-2)
  • Migration status for haskell-regex-posix/riscv64 (0.96.0.1-2 to 0.96.0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-regex-tdfa/riscv64 (1.3.2.2-1 to 1.3.2.2-1)
  • Migration status for haskell-regex-tdfa/riscv64 (1.3.2.2-1 to 1.3.2.2-1): Will attempt migration (Any information below is purely informational)
• haskell-regexpr/riscv64 (0.5.4-17 to 0.5.4-17)
  • Migration status for haskell-regexpr/riscv64 (0.5.4-17 to 0.5.4-17): Will attempt migration (Any information below is purely informational)
• haskell-reinterpret-cast/riscv64 (0.1.0-4 to 0.1.0-4)
  • Migration status for haskell-reinterpret-cast/riscv64 (0.1.0-4 to 0.1.0-4): Will attempt migration (Any information below is purely informational)
• haskell-repline/riscv64 (0.4.2.0-2 to 0.4.2.0-2)
  • Migration status for haskell-repline/riscv64 (0.4.2.0-2 to 0.4.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-resolv/riscv64 (0.2.0.2-1 to 0.2.0.2-1)
  • Migration status for haskell-resolv/riscv64 (0.2.0.2-1 to 0.2.0.2-1): Will attempt migration (Any information below is purely informational)
• haskell-resource-pool/riscv64 (0.4.0.0-1 to 0.4.0.0-1)
  • Migration status for haskell-resource-pool/riscv64 (0.4.0.0-1 to 0.4.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-resourcet/riscv64 (1.2.6-2 to 1.2.6-2)
  • Migration status for haskell-resourcet/riscv64 (1.2.6-2 to 1.2.6-2): Will attempt migration (Any information below is purely informational)
• haskell-retry/riscv64 (0.9.3.1-1 to 0.9.3.1-1)
  • Migration status for haskell-retry/riscv64 (0.9.3.1-1 to 0.9.3.1-1): Will attempt migration (Any information below is purely informational)
• haskell-rfc5051/riscv64 (0.2-3 to 0.2-3)
  • Migration status for haskell-rfc5051/riscv64 (0.2-3 to 0.2-3): Will attempt migration (Any information below is purely informational)
• haskell-rio-orphans/riscv64 (0.1.2.0-2 to 0.1.2.0-2)
  • Migration status for haskell-rio-orphans/riscv64 (0.1.2.0-2 to 0.1.2.0-2): Will attempt migration (Any information below is purely informational)
• haskell-rio-prettyprint/riscv64 (0.1.7.0-1 to 0.1.7.0-1)
  • Migration status for haskell-rio-prettyprint/riscv64 (0.1.7.0-1 to 0.1.7.0-1): Will attempt migration (Any information below is purely informational)
• haskell-rio/riscv64 (0.1.22.0-2 to 0.1.22.0-2)
  • Migration status for haskell-rio/riscv64 (0.1.22.0-2 to 0.1.22.0-2): Will attempt migration (Any information below is purely informational)
• haskell-rsa/riscv64 (2.4.1-3 to 2.4.1-3)
  • Migration status for haskell-rsa/riscv64 (2.4.1-3 to 2.4.1-3): Will attempt migration (Any information below is purely informational)
• haskell-rvar/riscv64 (0.3.0.2-1 to 0.3.0.2-1)
  • Migration status for haskell-rvar/riscv64 (0.3.0.2-1 to 0.3.0.2-1): Will attempt migration (Any information below is purely informational)
• haskell-s-cargot/riscv64 (0.1.6.0-1 to 0.1.6.0-1)
  • Migration status for haskell-s-cargot/riscv64 (0.1.6.0-1 to 0.1.6.0-1): Will attempt migration (Any information below is purely informational)
• haskell-safe-exceptions/riscv64 (0.1.7.4-1 to 0.1.7.4-1)
  • Migration status for haskell-safe-exceptions/riscv64 (0.1.7.4-1 to 0.1.7.4-1): Will attempt migration (Any information below is purely informational)
• haskell-safe/riscv64 (0.3.19-3 to 0.3.19-3)
  • Migration status for haskell-safe/riscv64 (0.3.19-3 to 0.3.19-3): Will attempt migration (Any information below is purely informational)
• haskell-safecopy/riscv64 (0.10.4.2-2 to 0.10.4.2-2)
  • Migration status for haskell-safecopy/riscv64 (0.10.4.2-2 to 0.10.4.2-2): Will attempt migration (Any information below is purely informational)
• haskell-safesemaphore/riscv64 (0.10.1-13 to 0.10.1-13)
  • Migration status for haskell-safesemaphore/riscv64 (0.10.1-13 to 0.10.1-13): Will attempt migration (Any information below is purely informational)
• haskell-sandi/riscv64 (0.5-5 to 0.5-5)
  • Migration status for haskell-sandi/riscv64 (0.5-5 to 0.5-5): Will attempt migration (Any information below is purely informational)
• haskell-say/riscv64 (0.1.0.1-5 to 0.1.0.1-5)
  • Migration status for haskell-say/riscv64 (0.1.0.1-5 to 0.1.0.1-5): Will attempt migration (Any information below is purely informational)
• haskell-sbv/riscv64 (10.2-1 to 10.2-1)
  • Migration status for haskell-sbv/riscv64 (10.2-1 to 10.2-1): Will attempt migration (Any information below is purely informational)
• haskell-scanner/riscv64 (0.3.1-3 to 0.3.1-3)
  • Migration status for haskell-scanner/riscv64 (0.3.1-3 to 0.3.1-3): Will attempt migration (Any information below is purely informational)
• haskell-scientific/riscv64 (0.3.7.0-2 to 0.3.7.0-2)
  • Migration status for haskell-scientific/riscv64 (0.3.7.0-2 to 0.3.7.0-2): Will attempt migration (Any information below is purely informational)
• haskell-scotty/riscv64 (0.12.1+dfsg-1 to 0.12.1+dfsg-1)
  • Migration status for haskell-scotty/riscv64 (0.12.1+dfsg-1 to 0.12.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• haskell-sdl/riscv64 (0.6.7.0-4 to 0.6.7.0-4)
  • Migration status for haskell-sdl/riscv64 (0.6.7.0-4 to 0.6.7.0-4): Will attempt migration (Any information below is purely informational)
• haskell-sdl2-image/riscv64 (2.1.0.0-3 to 2.1.0.0-3)
  • Migration status for haskell-sdl2-image/riscv64 (2.1.0.0-3 to 2.1.0.0-3): Will attempt migration (Any information below is purely informational)
• haskell-sdl2-mixer/riscv64 (1.2.0.0-3 to 1.2.0.0-3)
  • Migration status for haskell-sdl2-mixer/riscv64 (1.2.0.0-3 to 1.2.0.0-3): Will attempt migration (Any information below is purely informational)
• haskell-sdl2-ttf/riscv64 (2.1.3-2 to 2.1.3-2)
  • Migration status for haskell-sdl2-ttf/riscv64 (2.1.3-2 to 2.1.3-2): Will attempt migration (Any information below is purely informational)
• haskell-sdl2/riscv64 (2.5.5.0-1 to 2.5.5.0-1)
  • Migration status for haskell-sdl2/riscv64 (2.5.5.0-1 to 2.5.5.0-1): Will attempt migration (Any information below is purely informational)
• haskell-secret-sharing/riscv64 (1.0.1.2-3 to 1.0.1.2-3)
  • Migration status for haskell-secret-sharing/riscv64 (1.0.1.2-3 to 1.0.1.2-3): Will attempt migration (Any information below is purely informational)
• haskell-securemem/riscv64 (0.1.10-5 to 0.1.10-5)
  • Migration status for haskell-securemem/riscv64 (0.1.10-5 to 0.1.10-5): Will attempt migration (Any information below is purely informational)
• haskell-selective/riscv64 (0.7-1 to 0.7-1)
  • Migration status for haskell-selective/riscv64 (0.7-1 to 0.7-1): Will attempt migration (Any information below is purely informational)
• haskell-semialign/riscv64 (1.3-1 to 1.3-1)
  • Migration status for haskell-semialign/riscv64 (1.3-1 to 1.3-1): Will attempt migration (Any information below is purely informational)
• haskell-semigroupoids/riscv64 (5.3.7-2 to 5.3.7-2)
  • Migration status for haskell-semigroupoids/riscv64 (5.3.7-2 to 5.3.7-2): Will attempt migration (Any information below is purely informational)
• haskell-semigroups/riscv64 (0.20-2 to 0.20-2)
  • Migration status for haskell-semigroups/riscv64 (0.20-2 to 0.20-2): Will attempt migration (Any information below is purely informational)
• haskell-semirings/riscv64 (0.6-3 to 0.6-3)
  • Migration status for haskell-semirings/riscv64 (0.6-3 to 0.6-3): Will attempt migration (Any information below is purely informational)
• haskell-sendfile/riscv64 (0.7.11.4-2 to 0.7.11.4-2)
  • Migration status for haskell-sendfile/riscv64 (0.7.11.4-2 to 0.7.11.4-2): Will attempt migration (Any information below is purely informational)
• haskell-servant-client-core/riscv64 (0.19-2 to 0.19-2)
  • Migration status for haskell-servant-client-core/riscv64 (0.19-2 to 0.19-2): Will attempt migration (Any information below is purely informational)
• haskell-servant-client/riscv64 (0.19-2 to 0.19-2)
  • Migration status for haskell-servant-client/riscv64 (0.19-2 to 0.19-2): Will attempt migration (Any information below is purely informational)
• haskell-servant-server/riscv64 (0.19.2-2 to 0.19.2-2)
  • Migration status for haskell-servant-server/riscv64 (0.19.2-2 to 0.19.2-2): Will attempt migration (Any information below is purely informational)
• haskell-servant/riscv64 (0.19.1-1 to 0.19.1-1)
  • Migration status for haskell-servant/riscv64 (0.19.1-1 to 0.19.1-1): Will attempt migration (Any information below is purely informational)
• haskell-set-extra/riscv64 (1.4.1-6 to 1.4.1-6)
  • Migration status for haskell-set-extra/riscv64 (1.4.1-6 to 1.4.1-6): Will attempt migration (Any information below is purely informational)
• haskell-setenv/riscv64 (0.1.1.3-11 to 0.1.1.3-11)
  • Migration status for haskell-setenv/riscv64 (0.1.1.3-11 to 0.1.1.3-11): Will attempt migration (Any information below is purely informational)
• haskell-setlocale/riscv64 (1.0.0.10-2 to 1.0.0.10-2)
  • Migration status for haskell-setlocale/riscv64 (1.0.0.10-2 to 1.0.0.10-2): Will attempt migration (Any information below is purely informational)
• haskell-sha/riscv64 (1.6.4.4-5 to 1.6.4.4-5)
  • Migration status for haskell-sha/riscv64 (1.6.4.4-5 to 1.6.4.4-5): Will attempt migration (Any information below is purely informational)
• haskell-shake/riscv64 (0.19.7-2 to 0.19.7-2)
  • Migration status for haskell-shake/riscv64 (0.19.7-2 to 0.19.7-2): Will attempt migration (Any information below is purely informational)
• haskell-shakespeare/riscv64 (2.1.0.1-1 to 2.1.0.1-1)
  • Migration status for haskell-shakespeare/riscv64 (2.1.0.1-1 to 2.1.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-shell-conduit/riscv64 (5.0.0-2 to 5.0.0-2)
  • Migration status for haskell-shell-conduit/riscv64 (5.0.0-2 to 5.0.0-2): Will attempt migration (Any information below is purely informational)
• haskell-shelly/riscv64 (1.12.1-1 to 1.12.1-1)
  • Migration status for haskell-shelly/riscv64 (1.12.1-1 to 1.12.1-1): Will attempt migration (Any information below is purely informational)
• haskell-should-not-typecheck/riscv64 (2.1.0-8 to 2.1.0-8)
  • Migration status for haskell-should-not-typecheck/riscv64 (2.1.0-8 to 2.1.0-8): Will attempt migration (Any information below is purely informational)
• haskell-show-combinators/riscv64 (0.2.0.0-3 to 0.2.0.0-3)
  • Migration status for haskell-show-combinators/riscv64 (0.2.0.0-3 to 0.2.0.0-3): Will attempt migration (Any information below is purely informational)
• haskell-show/riscv64 (0.6-12 to 0.6-12)
  • Migration status for haskell-show/riscv64 (0.6-12 to 0.6-12): Will attempt migration (Any information below is purely informational)
• haskell-silently/riscv64 (1.2.5.3-2 to 1.2.5.3-2)
  • Migration status for haskell-silently/riscv64 (1.2.5.3-2 to 1.2.5.3-2): Will attempt migration (Any information below is purely informational)
• haskell-simple-reflect/riscv64 (0.3.3-5 to 0.3.3-5)
  • Migration status for haskell-simple-reflect/riscv64 (0.3.3-5 to 0.3.3-5): Will attempt migration (Any information below is purely informational)
• haskell-simple-sendfile/riscv64 (0.2.32-2 to 0.2.32-2)
  • Migration status for haskell-simple-sendfile/riscv64 (0.2.32-2 to 0.2.32-2): Will attempt migration (Any information below is purely informational)
• haskell-simple-smt/riscv64 (0.9.7-2 to 0.9.7-2)
  • Migration status for haskell-simple-smt/riscv64 (0.9.7-2 to 0.9.7-2): Will attempt migration (Any information below is purely informational)
• haskell-singleton-bool/riscv64 (0.1.6-2 to 0.1.6-2)
  • Migration status for haskell-singleton-bool/riscv64 (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• haskell-singletons/riscv64 (3.0.2-2 to 3.0.2-2)
  • Migration status for haskell-singletons/riscv64 (3.0.2-2 to 3.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-skein/riscv64 (1.0.9.4-8 to 1.0.9.4-8)
  • Migration status for haskell-skein/riscv64 (1.0.9.4-8 to 1.0.9.4-8): Will attempt migration (Any information below is purely informational)
• haskell-skylighting-core/riscv64 (0.13.4.1-1 to 0.13.4.1-1)
  • Migration status for haskell-skylighting-core/riscv64 (0.13.4.1-1 to 0.13.4.1-1): Will attempt migration (Any information below is purely informational)
• haskell-skylighting-format-ansi/riscv64 (0.1-2 to 0.1-2)
  • Migration status for haskell-skylighting-format-ansi/riscv64 (0.1-2 to 0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-skylighting-format-blaze-html/riscv64 (0.1.1.1-1 to 0.1.1.1-1)
  • Migration status for haskell-skylighting-format-blaze-html/riscv64 (0.1.1.1-1 to 0.1.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-skylighting-format-context/riscv64 (0.1.0.2-2 to 0.1.0.2-2)
  • Migration status for haskell-skylighting-format-context/riscv64 (0.1.0.2-2 to 0.1.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-skylighting-format-latex/riscv64 (0.1-2 to 0.1-2)
  • Migration status for haskell-skylighting-format-latex/riscv64 (0.1-2 to 0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-skylighting/riscv64 (0.13.4.1-2 to 0.13.4.1-2)
  • Migration status for haskell-skylighting/riscv64 (0.13.4.1-2 to 0.13.4.1-2): Will attempt migration (Any information below is purely informational)
• haskell-smallcheck/riscv64 (1.2.1.1-1 to 1.2.1.1-1)
  • Migration status for haskell-smallcheck/riscv64 (1.2.1.1-1 to 1.2.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-smtlib/riscv64 (1.1-3 to 1.1-3)
  • Migration status for haskell-smtlib/riscv64 (1.1-3 to 1.1-3): Will attempt migration (Any information below is purely informational)
• haskell-smtp-mail/riscv64 (0.3.0.0-3 to 0.3.0.0-3)
  • Migration status for haskell-smtp-mail/riscv64 (0.3.0.0-3 to 0.3.0.0-3): Will attempt migration (Any information below is purely informational)
• haskell-snap-core/riscv64 (1.0.5.1-1 to 1.0.5.1-1)
  • Migration status for haskell-snap-core/riscv64 (1.0.5.1-1 to 1.0.5.1-1): Will attempt migration (Any information below is purely informational)
• haskell-snap-server/riscv64 (1.1.2.1-1 to 1.1.2.1-1)
  • Migration status for haskell-snap-server/riscv64 (1.1.2.1-1 to 1.1.2.1-1): Will attempt migration (Any information below is purely informational)
• haskell-snap/riscv64 (1.1.3.2-1 to 1.1.3.2-1)
  • Migration status for haskell-snap/riscv64 (1.1.3.2-1 to 1.1.3.2-1): Will attempt migration (Any information below is purely informational)
• haskell-soap-tls/riscv64 (0.1.1.4-6 to 0.1.1.4-6)
  • Migration status for haskell-soap-tls/riscv64 (0.1.1.4-6 to 0.1.1.4-6): Will attempt migration (Any information below is purely informational)
• haskell-soap/riscv64 (0.2.3.6-6 to 0.2.3.6-6)
  • Migration status for haskell-soap/riscv64 (0.2.3.6-6 to 0.2.3.6-6): Will attempt migration (Any information below is purely informational)
• haskell-sockaddr/riscv64 (0.0.1-2 to 0.0.1-2)
  • Migration status for haskell-sockaddr/riscv64 (0.0.1-2 to 0.0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-socks/riscv64 (0.6.1-3 to 0.6.1-3)
  • Migration status for haskell-socks/riscv64 (0.6.1-3 to 0.6.1-3): Will attempt migration (Any information below is purely informational)
• haskell-some/riscv64 (1.0.4.1-1 to 1.0.4.1-1)
  • Migration status for haskell-some/riscv64 (1.0.4.1-1 to 1.0.4.1-1): Will attempt migration (Any information below is purely informational)
• haskell-sop-core/riscv64 (0.5.0.2-2 to 0.5.0.2-2)
  • Migration status for haskell-sop-core/riscv64 (0.5.0.2-2 to 0.5.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-split/riscv64 (0.2.3.5-2 to 0.2.3.5-2)
  • Migration status for haskell-split/riscv64 (0.2.3.5-2 to 0.2.3.5-2): Will attempt migration (Any information below is purely informational)
• haskell-splitmix/riscv64 (0.1.0.5-1 to 0.1.0.5-1)
  • Migration status for haskell-splitmix/riscv64 (0.1.0.5-1 to 0.1.0.5-1): Will attempt migration (Any information below is purely informational)
• haskell-spool/riscv64 (0.1-4 to 0.1-4)
  • Migration status for haskell-spool/riscv64 (0.1-4 to 0.1-4): Will attempt migration (Any information below is purely informational)
• haskell-sql-words/riscv64 (0.1.6.4-3 to 0.1.6.4-3)
  • Migration status for haskell-sql-words/riscv64 (0.1.6.4-3 to 0.1.6.4-3): Will attempt migration (Any information below is purely informational)
• haskell-src-exts-simple/riscv64 (1.23.0.0-3 to 1.23.0.0-3)
  • Migration status for haskell-src-exts-simple/riscv64 (1.23.0.0-3 to 1.23.0.0-3): Will attempt migration (Any information below is purely informational)
• haskell-src-exts-util/riscv64 (0.2.5-4 to 0.2.5-4)
  • Migration status for haskell-src-exts-util/riscv64 (0.2.5-4 to 0.2.5-4): Will attempt migration (Any information below is purely informational)
• haskell-src-exts/riscv64 (1.23.1-4 to 1.23.1-4)
  • Migration status for haskell-src-exts/riscv64 (1.23.1-4 to 1.23.1-4): Will attempt migration (Any information below is purely informational)
• haskell-src-meta/riscv64 (0.8.12-1 to 0.8.12-1)
  • Migration status for haskell-src-meta/riscv64 (0.8.12-1 to 0.8.12-1): Will attempt migration (Any information below is purely informational)
• haskell-stateref/riscv64 (0.3-11 to 0.3-11)
  • Migration status for haskell-stateref/riscv64 (0.3-11 to 0.3-11): Will attempt migration (Any information below is purely informational)
• haskell-statestack/riscv64 (0.3.1.1-1 to 0.3.1.1-1)
  • Migration status for haskell-statestack/riscv64 (0.3.1.1-1 to 0.3.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-statevar/riscv64 (1.2.2-2 to 1.2.2-2)
  • Migration status for haskell-statevar/riscv64 (1.2.2-2 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
• haskell-static-hash/riscv64 (0.0.2-2 to 0.0.2-2)
  • Migration status for haskell-static-hash/riscv64 (0.0.2-2 to 0.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-statistics/riscv64 (0.16.2.1-1 to 0.16.2.1-1)
  • Migration status for haskell-statistics/riscv64 (0.16.2.1-1 to 0.16.2.1-1): Will attempt migration (Any information below is purely informational)
• haskell-status-notifier-item/riscv64 (0.3.1.0-2 to 0.3.1.0-2)
  • Migration status for haskell-status-notifier-item/riscv64 (0.3.1.0-2 to 0.3.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-stm-chans/riscv64 (3.0.0.9-1 to 3.0.0.9-1)
  • Migration status for haskell-stm-chans/riscv64 (3.0.0.9-1 to 3.0.0.9-1): Will attempt migration (Any information below is purely informational)
• haskell-stm-delay/riscv64 (0.1.1.1-4 to 0.1.1.1-4)
  • Migration status for haskell-stm-delay/riscv64 (0.1.1.1-4 to 0.1.1.1-4): Will attempt migration (Any information below is purely informational)
• haskell-stmonadtrans/riscv64 (0.4.7-1 to 0.4.7-1)
  • Migration status for haskell-stmonadtrans/riscv64 (0.4.7-1 to 0.4.7-1): Will attempt migration (Any information below is purely informational)
• haskell-storable-complex/riscv64 (0.2.3.0-4 to 0.2.3.0-4)
  • Migration status for haskell-storable-complex/riscv64 (0.2.3.0-4 to 0.2.3.0-4): Will attempt migration (Any information below is purely informational)
• haskell-storable-record/riscv64 (0.0.7-1 to 0.0.7-1)
  • Migration status for haskell-storable-record/riscv64 (0.0.7-1 to 0.0.7-1): Will attempt migration (Any information below is purely informational)
• haskell-storable-tuple/riscv64 (0.1-1 to 0.1-1)
  • Migration status for haskell-storable-tuple/riscv64 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-store-core/riscv64 (0.4.4.6-1 to 0.4.4.6-1)
  • Migration status for haskell-store-core/riscv64 (0.4.4.6-1 to 0.4.4.6-1): Will attempt migration (Any information below is purely informational)
• haskell-store/riscv64 (0.7.18-1 to 0.7.18-1)
  • Migration status for haskell-store/riscv64 (0.7.18-1 to 0.7.18-1): Will attempt migration (Any information below is purely informational)
• haskell-stream/riscv64 (0.4.7.2-9 to 0.4.7.2-9)
  • Migration status for haskell-stream/riscv64 (0.4.7.2-9 to 0.4.7.2-9): Will attempt migration (Any information below is purely informational)
• haskell-streaming-commons/riscv64 (0.2.2.6-1 to 0.2.2.6-1)
  • Migration status for haskell-streaming-commons/riscv64 (0.2.2.6-1 to 0.2.2.6-1): Will attempt migration (Any information below is purely informational)
• haskell-strict-list/riscv64 (0.1.7.2-1 to 0.1.7.2-1)
  • Migration status for haskell-strict-list/riscv64 (0.1.7.2-1 to 0.1.7.2-1): Will attempt migration (Any information below is purely informational)
• haskell-strict/riscv64 (0.5-1 to 0.5-1)
  • Migration status for haskell-strict/riscv64 (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
• haskell-string-conversions/riscv64 (0.4.0.1-7 to 0.4.0.1-7)
  • Migration status for haskell-string-conversions/riscv64 (0.4.0.1-7 to 0.4.0.1-7): Will attempt migration (Any information below is purely informational)
• haskell-string-interpolate/riscv64 (0.3.2.1-3 to 0.3.2.1-3)
  • Migration status for haskell-string-interpolate/riscv64 (0.3.2.1-3 to 0.3.2.1-3): Will attempt migration (Any information below is purely informational)
• haskell-string-qq/riscv64 (0.0.5-1 to 0.0.5-1)
  • Migration status for haskell-string-qq/riscv64 (0.0.5-1 to 0.0.5-1): Will attempt migration (Any information below is purely informational)
• haskell-stringbuilder/riscv64 (0.5.1-5 to 0.5.1-5)
  • Migration status for haskell-stringbuilder/riscv64 (0.5.1-5 to 0.5.1-5): Will attempt migration (Any information below is purely informational)
• haskell-stringprep/riscv64 (1.0.0-13 to 1.0.0-13)
  • Migration status for haskell-stringprep/riscv64 (1.0.0-13 to 1.0.0-13): Will attempt migration (Any information below is purely informational)
• haskell-stringsearch/riscv64 (0.3.6.6-12 to 0.3.6.6-12)
  • Migration status for haskell-stringsearch/riscv64 (0.3.6.6-12 to 0.3.6.6-12): Will attempt migration (Any information below is purely informational)
• haskell-svg-builder/riscv64 (0.1.1-7 to 0.1.1-7)
  • Migration status for haskell-svg-builder/riscv64 (0.1.1-7 to 0.1.1-7): Will attempt migration (Any information below is purely informational)
• haskell-syb/riscv64 (0.7.2.4-1 to 0.7.2.4-1)
  • Migration status for haskell-syb/riscv64 (0.7.2.4-1 to 0.7.2.4-1): Will attempt migration (Any information below is purely informational)
• haskell-system-fileio/riscv64 (0.3.16.4-5 to 0.3.16.4-5)
  • Migration status for haskell-system-fileio/riscv64 (0.3.16.4-5 to 0.3.16.4-5): Will attempt migration (Any information below is purely informational)
• haskell-system-filepath/riscv64 (0.4.14-6 to 0.4.14-6)
  • Migration status for haskell-system-filepath/riscv64 (0.4.14-6 to 0.4.14-6): Will attempt migration (Any information below is purely informational)
• haskell-system-posix-redirect/riscv64 (1.1.0.1-4 to 1.1.0.1-4)
  • Migration status for haskell-system-posix-redirect/riscv64 (1.1.0.1-4 to 1.1.0.1-4): Will attempt migration (Any information below is purely informational)
• haskell-tabular/riscv64 (0.2.2.8-2 to 0.2.2.8-2)
  • Migration status for haskell-tabular/riscv64 (0.2.2.8-2 to 0.2.2.8-2): Will attempt migration (Any information below is purely informational)
• haskell-tagged/riscv64 (0.8.7-1 to 0.8.7-1)
  • Migration status for haskell-tagged/riscv64 (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
• haskell-tagshare/riscv64 (0.0-7 to 0.0-7)
  • Migration status for haskell-tagshare/riscv64 (0.0-7 to 0.0-7): Will attempt migration (Any information below is purely informational)
• haskell-tagsoup/riscv64 (0.14.8-4 to 0.14.8-4)
  • Migration status for haskell-tagsoup/riscv64 (0.14.8-4 to 0.14.8-4): Will attempt migration (Any information below is purely informational)
• haskell-tagstream-conduit/riscv64 (0.5.6-3 to 0.5.6-3)
  • Migration status for haskell-tagstream-conduit/riscv64 (0.5.6-3 to 0.5.6-3): Will attempt migration (Any information below is purely informational)
• haskell-tar-conduit/riscv64 (0.3.2.1-1 to 0.3.2.1-1)
  • Migration status for haskell-tar-conduit/riscv64 (0.3.2.1-1 to 0.3.2.1-1): Will attempt migration (Any information below is purely informational)
• haskell-tar/riscv64 (0.5.1.1-4 to 0.5.1.1-4)
  • Migration status for haskell-tar/riscv64 (0.5.1.1-4 to 0.5.1.1-4): Will attempt migration (Any information below is purely informational)
• haskell-tasty-ant-xml/riscv64 (1.1.9-1 to 1.1.9-1)
  • Migration status for haskell-tasty-ant-xml/riscv64 (1.1.9-1 to 1.1.9-1): Will attempt migration (Any information below is purely informational)
• haskell-tasty-checklist/riscv64 (1.0.6.0-1 to 1.0.6.0-1)
  • Migration status for haskell-tasty-checklist/riscv64 (1.0.6.0-1 to 1.0.6.0-1): Will attempt migration (Any information below is purely informational)
• haskell-tasty-discover/riscv64 (5.0.0-1 to 5.0.0-1)
  • Migration status for haskell-tasty-discover/riscv64 (5.0.0-1 to 5.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-tasty-expected-failure/riscv64 (0.12.3-2 to 0.12.3-2)
  • Migration status for haskell-tasty-expected-failure/riscv64 (0.12.3-2 to 0.12.3-2): Will attempt migration (Any information below is purely informational)
• haskell-tasty-golden/riscv64 (2.3.5-2 to 2.3.5-2)
  • Migration status for haskell-tasty-golden/riscv64 (2.3.5-2 to 2.3.5-2): Will attempt migration (Any information below is purely informational)
• haskell-tasty-hedgehog/riscv64 (1.4.0.1-1 to 1.4.0.1-1)
  • Migration status for haskell-tasty-hedgehog/riscv64 (1.4.0.1-1 to 1.4.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-tasty-hslua/riscv64 (1.1.0-1 to 1.1.0-1)
  • Migration status for haskell-tasty-hslua/riscv64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-tasty-hspec/riscv64 (1.2.0.3-1 to 1.2.0.3-1)
  • Migration status for haskell-tasty-hspec/riscv64 (1.2.0.3-1 to 1.2.0.3-1): Will attempt migration (Any information below is purely informational)
• haskell-tasty-hunit/riscv64 (0.10.1-1 to 0.10.1-1)
  • Migration status for haskell-tasty-hunit/riscv64 (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
• haskell-tasty-kat/riscv64 (0.0.3-12 to 0.0.3-12)
  • Migration status for haskell-tasty-kat/riscv64 (0.0.3-12 to 0.0.3-12): Will attempt migration (Any information below is purely informational)
• haskell-tasty-lua/riscv64 (1.1.0-1 to 1.1.0-1)
  • Migration status for haskell-tasty-lua/riscv64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-tasty-quickcheck/riscv64 (0.10.2-2 to 0.10.2-2)
  • Migration status for haskell-tasty-quickcheck/riscv64 (0.10.2-2 to 0.10.2-2): Will attempt migration (Any information below is purely informational)
• haskell-tasty-rerun/riscv64 (1.1.19-1 to 1.1.19-1)
  • Migration status for haskell-tasty-rerun/riscv64 (1.1.19-1 to 1.1.19-1): Will attempt migration (Any information below is purely informational)
• haskell-tasty-smallcheck/riscv64 (0.8.2-2 to 0.8.2-2)
  • Migration status for haskell-tasty-smallcheck/riscv64 (0.8.2-2 to 0.8.2-2): Will attempt migration (Any information below is purely informational)
• haskell-tasty-th/riscv64 (0.1.7-6 to 0.1.7-6)
  • Migration status for haskell-tasty-th/riscv64 (0.1.7-6 to 0.1.7-6): Will attempt migration (Any information below is purely informational)
• haskell-tasty/riscv64 (1.4.3-2 to 1.4.3-2)
  • Migration status for haskell-tasty/riscv64 (1.4.3-2 to 1.4.3-2): Will attempt migration (Any information below is purely informational)
• haskell-template-haskell-compat-v0208/riscv64 (0.1.9.2-1 to 0.1.9.2-1)
  • Migration status for haskell-template-haskell-compat-v0208/riscv64 (0.1.9.2-1 to 0.1.9.2-1): Will attempt migration (Any information below is purely informational)
• haskell-temporary/riscv64 (1.3-4 to 1.3-4)
  • Migration status for haskell-temporary/riscv64 (1.3-4 to 1.3-4): Will attempt migration (Any information below is purely informational)
• haskell-terminal-progress-bar/riscv64 (0.4.2-1 to 0.4.2-1)
  • Migration status for haskell-terminal-progress-bar/riscv64 (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• haskell-terminal-size/riscv64 (0.3.4-1 to 0.3.4-1)
  • Migration status for haskell-terminal-size/riscv64 (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
• haskell-test-framework-hunit/riscv64 (0.3.0.2-9 to 0.3.0.2-9)
  • Migration status for haskell-test-framework-hunit/riscv64 (0.3.0.2-9 to 0.3.0.2-9): Will attempt migration (Any information below is purely informational)
• haskell-test-framework-quickcheck2/riscv64 (0.3.0.5-6 to 0.3.0.5-6)
  • Migration status for haskell-test-framework-quickcheck2/riscv64 (0.3.0.5-6 to 0.3.0.5-6): Will attempt migration (Any information below is purely informational)
• haskell-test-framework/riscv64 (0.8.2.0-8 to 0.8.2.0-8)
  • Migration status for haskell-test-framework/riscv64 (0.8.2.0-8 to 0.8.2.0-8): Will attempt migration (Any information below is purely informational)
• haskell-texmath/riscv64 (0.12.8.3-1 to 0.12.8.3-1)
  • Migration status for haskell-texmath/riscv64 (0.12.8.3-1 to 0.12.8.3-1): Will attempt migration (Any information below is purely informational)
• haskell-text-ansi/riscv64 (0.2.1.1-2 to 0.2.1.1-2)
  • Migration status for haskell-text-ansi/riscv64 (0.2.1.1-2 to 0.2.1.1-2): Will attempt migration (Any information below is purely informational)
• haskell-text-binary/riscv64 (0.2.1.1-9 to 0.2.1.1-9)
  • Migration status for haskell-text-binary/riscv64 (0.2.1.1-9 to 0.2.1.1-9): Will attempt migration (Any information below is purely informational)
• haskell-text-builder-dev/riscv64 (0.3.3.2-1 to 0.3.3.2-1)
  • Migration status for haskell-text-builder-dev/riscv64 (0.3.3.2-1 to 0.3.3.2-1): Will attempt migration (Any information below is purely informational)
• haskell-text-builder/riscv64 (0.6.7-1 to 0.6.7-1)
  • Migration status for haskell-text-builder/riscv64 (0.6.7-1 to 0.6.7-1): Will attempt migration (Any information below is purely informational)
• haskell-text-conversions/riscv64 (0.3.1.1-2 to 0.3.1.1-2)
  • Migration status for haskell-text-conversions/riscv64 (0.3.1.1-2 to 0.3.1.1-2): Will attempt migration (Any information below is purely informational)
• haskell-text-icu/riscv64 (0.8.0.4-1 to 0.8.0.4-1)
  • Migration status for haskell-text-icu/riscv64 (0.8.0.4-1 to 0.8.0.4-1): Will attempt migration (Any information below is purely informational)
• haskell-text-manipulate/riscv64 (0.3.1.0-2 to 0.3.1.0-2)
  • Migration status for haskell-text-manipulate/riscv64 (0.3.1.0-2 to 0.3.1.0-2): Will attempt migration (Any information below is purely informational)
• haskell-text-metrics/riscv64 (0.3.2-2 to 0.3.2-2)
  • Migration status for haskell-text-metrics/riscv64 (0.3.2-2 to 0.3.2-2): Will attempt migration (Any information below is purely informational)
• haskell-text-postgresql/riscv64 (0.0.3.1-5 to 0.0.3.1-5)
  • Migration status for haskell-text-postgresql/riscv64 (0.0.3.1-5 to 0.0.3.1-5): Will attempt migration (Any information below is purely informational)
• haskell-text-short/riscv64 (0.1.5-2 to 0.1.5-2)
  • Migration status for haskell-text-short/riscv64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• haskell-text-show/riscv64 (3.10.4-1 to 3.10.4-1)
  • Migration status for haskell-text-show/riscv64 (3.10.4-1 to 3.10.4-1): Will attempt migration (Any information below is purely informational)
• haskell-text-zipper/riscv64 (0.13-1 to 0.13-1)
  • Migration status for haskell-text-zipper/riscv64 (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
• haskell-tf-random/riscv64 (0.5-12 to 0.5-12)
  • Migration status for haskell-tf-random/riscv64 (0.5-12 to 0.5-12): Will attempt migration (Any information below is purely informational)
• haskell-th-abstraction/riscv64 (0.4.5.0-2 to 0.4.5.0-2)
  • Migration status for haskell-th-abstraction/riscv64 (0.4.5.0-2 to 0.4.5.0-2): Will attempt migration (Any information below is purely informational)
• haskell-th-bang-compat/riscv64 (0.0.1.0-4 to 0.0.1.0-4)
  • Migration status for haskell-th-bang-compat/riscv64 (0.0.1.0-4 to 0.0.1.0-4): Will attempt migration (Any information below is purely informational)
• haskell-th-compat/riscv64 (0.1.4-2 to 0.1.4-2)
  • Migration status for haskell-th-compat/riscv64 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• haskell-th-constraint-compat/riscv64 (0.0.1.0-4 to 0.0.1.0-4)
  • Migration status for haskell-th-constraint-compat/riscv64 (0.0.1.0-4 to 0.0.1.0-4): Will attempt migration (Any information below is purely informational)
• haskell-th-data-compat/riscv64 (0.1.2.0-1 to 0.1.2.0-1)
  • Migration status for haskell-th-data-compat/riscv64 (0.1.2.0-1 to 0.1.2.0-1): Will attempt migration (Any information below is purely informational)
• haskell-th-desugar/riscv64 (1.14-1 to 1.14-1)
  • Migration status for haskell-th-desugar/riscv64 (1.14-1 to 1.14-1): Will attempt migration (Any information below is purely informational)
• haskell-th-env/riscv64 (0.1.1-1 to 0.1.1-1)
  • Migration status for haskell-th-env/riscv64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• haskell-th-expand-syns/riscv64 (0.4.11.0-1 to 0.4.11.0-1)
  • Migration status for haskell-th-expand-syns/riscv64 (0.4.11.0-1 to 0.4.11.0-1): Will attempt migration (Any information below is purely informational)
• haskell-th-extras/riscv64 (0.0.0.6-2 to 0.0.0.6-2)
  • Migration status for haskell-th-extras/riscv64 (0.0.0.6-2 to 0.0.0.6-2): Will attempt migration (Any information below is purely informational)
• haskell-th-lift-instances/riscv64 (0.1.20-2 to 0.1.20-2)
  • Migration status for haskell-th-lift-instances/riscv64 (0.1.20-2 to 0.1.20-2): Will attempt migration (Any information below is purely informational)
• haskell-th-lift/riscv64 (0.8.4-1 to 0.8.4-1)
  • Migration status for haskell-th-lift/riscv64 (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• haskell-th-orphans/riscv64 (0.13.14-2 to 0.13.14-2)
  • Migration status for haskell-th-orphans/riscv64 (0.13.14-2 to 0.13.14-2): Will attempt migration (Any information below is purely informational)
• haskell-th-reify-compat/riscv64 (0.0.1.5-4 to 0.0.1.5-4)
  • Migration status for haskell-th-reify-compat/riscv64 (0.0.1.5-4 to 0.0.1.5-4): Will attempt migration (Any information below is purely informational)
• haskell-th-reify-many/riscv64 (0.1.10-2 to 0.1.10-2)
  • Migration status for haskell-th-reify-many/riscv64 (0.1.10-2 to 0.1.10-2): Will attempt migration (Any information below is purely informational)
• haskell-th-utilities/riscv64 (0.2.5.0-2 to 0.2.5.0-2)
  • Migration status for haskell-th-utilities/riscv64 (0.2.5.0-2 to 0.2.5.0-2): Will attempt migration (Any information below is purely informational)
• haskell-these/riscv64 (1.2-1 to 1.2-1)
  • Migration status for haskell-these/riscv64 (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• haskell-threads/riscv64 (0.5.1.8-1 to 0.5.1.8-1)
  • Migration status for haskell-threads/riscv64 (0.5.1.8-1 to 0.5.1.8-1): Will attempt migration (Any information below is purely informational)
• haskell-time-compat/riscv64 (1.9.6.1-2 to 1.9.6.1-2)
  • Migration status for haskell-time-compat/riscv64 (1.9.6.1-2 to 1.9.6.1-2): Will attempt migration (Any information below is purely informational)
• haskell-time-locale-compat/riscv64 (0.1.1.5-4 to 0.1.1.5-4)
  • Migration status for haskell-time-locale-compat/riscv64 (0.1.1.5-4 to 0.1.1.5-4): Will attempt migration (Any information below is purely informational)
• haskell-time-manager/riscv64 (0.0.1-1 to 0.0.1-1)
  • Migration status for haskell-time-manager/riscv64 (0.0.1-1 to 0.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-time-parsers/riscv64 (0.2-1 to 0.2-1)
  • Migration status for haskell-time-parsers/riscv64 (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
• haskell-time-units/riscv64 (1.0.0-5 to 1.0.0-5)
  • Migration status for haskell-time-units/riscv64 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• haskell-timeit/riscv64 (2.0-3 to 2.0-3)
  • Migration status for haskell-timeit/riscv64 (2.0-3 to 2.0-3): Will attempt migration (Any information below is purely informational)
• haskell-tldr/riscv64 (0.9.2-5 to 0.9.2-5)
  • Migration status for haskell-tldr/riscv64 (0.9.2-5 to 0.9.2-5): Will attempt migration (Any information below is purely informational)
• haskell-tls-session-manager/riscv64 (0.0.4-3 to 0.0.4-3)
  • Migration status for haskell-tls-session-manager/riscv64 (0.0.4-3 to 0.0.4-3): Will attempt migration (Any information below is purely informational)
• haskell-tls/riscv64 (1.6.0-1 to 1.6.0-1)
  • Migration status for haskell-tls/riscv64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
• haskell-token-bucket/riscv64 (0.1.0.1-13 to 0.1.0.1-13)
  • Migration status for haskell-token-bucket/riscv64 (0.1.0.1-13 to 0.1.0.1-13): Will attempt migration (Any information below is purely informational)
• haskell-topograph/riscv64 (1.0.0.2-2 to 1.0.0.2-2)
  • Migration status for haskell-topograph/riscv64 (1.0.0.2-2 to 1.0.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-torrent/riscv64 (10000.1.3-1 to 10000.1.3-1)
  • Migration status for haskell-torrent/riscv64 (10000.1.3-1 to 10000.1.3-1): Will attempt migration (Any information below is purely informational)
• haskell-transformers-base/riscv64 (0.4.6-2 to 0.4.6-2)
  • Migration status for haskell-transformers-base/riscv64 (0.4.6-2 to 0.4.6-2): Will attempt migration (Any information below is purely informational)
• haskell-transformers-compat/riscv64 (0.7.2-1 to 0.7.2-1)
  • Migration status for haskell-transformers-compat/riscv64 (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• haskell-trifecta/riscv64 (2.1.3-1 to 2.1.3-1)
  • Migration status for haskell-trifecta/riscv64 (2.1.3-1 to 2.1.3-1): Will attempt migration (Any information below is purely informational)
• haskell-tuple/riscv64 (0.3.0.2-5 to 0.3.0.2-5)
  • Migration status for haskell-tuple/riscv64 (0.3.0.2-5 to 0.3.0.2-5): Will attempt migration (Any information below is purely informational)
• haskell-twitter-conduit/riscv64 (0.6.1-2 to 0.6.1-2)
  • Migration status for haskell-twitter-conduit/riscv64 (0.6.1-2 to 0.6.1-2): Will attempt migration (Any information below is purely informational)
• haskell-twitter-types-lens/riscv64 (0.11.0-2 to 0.11.0-2)
  • Migration status for haskell-twitter-types-lens/riscv64 (0.11.0-2 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
• haskell-twitter-types/riscv64 (0.11.0-2 to 0.11.0-2)
  • Migration status for haskell-twitter-types/riscv64 (0.11.0-2 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
• haskell-type-equality/riscv64 (1-4 to 1-4)
  • Migration status for haskell-type-equality/riscv64 (1-4 to 1-4): Will attempt migration (Any information below is purely informational)
• haskell-type-errors/riscv64 (0.2.0.2-1 to 0.2.0.2-1)
  • Migration status for haskell-type-errors/riscv64 (0.2.0.2-1 to 0.2.0.2-1): Will attempt migration (Any information below is purely informational)
• haskell-type-level-numbers/riscv64 (0.1.1.2-2 to 0.1.1.2-2)
  • Migration status for haskell-type-level-numbers/riscv64 (0.1.1.2-2 to 0.1.1.2-2): Will attempt migration (Any information below is purely informational)
• haskell-typed-process/riscv64 (0.2.11.1-1 to 0.2.11.1-1)
  • Migration status for haskell-typed-process/riscv64 (0.2.11.1-1 to 0.2.11.1-1): Will attempt migration (Any information below is purely informational)
• haskell-typst-symbols/riscv64 (0.1.4-1 to 0.1.4-1)
  • Migration status for haskell-typst-symbols/riscv64 (0.1.4-1 to 0.1.4-1): Will attempt migration (Any information below is purely informational)
• haskell-typst/riscv64 (0.1.0.0-2 to 0.1.0.0-2)
  • Migration status for haskell-typst/riscv64 (0.1.0.0-2 to 0.1.0.0-2): Will attempt migration (Any information below is purely informational)
• haskell-uglymemo/riscv64 (0.1.0.1-8 to 0.1.0.1-8)
  • Migration status for haskell-uglymemo/riscv64 (0.1.0.1-8 to 0.1.0.1-8): Will attempt migration (Any information below is purely informational)
• haskell-unbounded-delays/riscv64 (0.1.1.1-2 to 0.1.1.1-2)
  • Migration status for haskell-unbounded-delays/riscv64 (0.1.1.1-2 to 0.1.1.1-2): Will attempt migration (Any information below is purely informational)
• haskell-unexceptionalio/riscv64 (0.5.1-3 to 0.5.1-3)
  • Migration status for haskell-unexceptionalio/riscv64 (0.5.1-3 to 0.5.1-3): Will attempt migration (Any information below is purely informational)
• haskell-unicode-collation/riscv64 (0.1.3.5-1 to 0.1.3.5-1)
  • Migration status for haskell-unicode-collation/riscv64 (0.1.3.5-1 to 0.1.3.5-1): Will attempt migration (Any information below is purely informational)
• haskell-unicode-data/riscv64 (0.4.0.1-1 to 0.4.0.1-1)
  • Migration status for haskell-unicode-data/riscv64 (0.4.0.1-1 to 0.4.0.1-1): Will attempt migration (Any information below is purely informational)
• haskell-unicode-transforms/riscv64 (0.4.0.1-2 to 0.4.0.1-2)
  • Migration status for haskell-unicode-transforms/riscv64 (0.4.0.1-2 to 0.4.0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-uniplate/riscv64 (1.6.13-2 to 1.6.13-2)
  • Migration status for haskell-uniplate/riscv64 (1.6.13-2 to 1.6.13-2): Will attempt migration (Any information below is purely informational)
• haskell-universe-base/riscv64 (1.1.3.1-1 to 1.1.3.1-1)
  • Migration status for haskell-universe-base/riscv64 (1.1.3.1-1 to 1.1.3.1-1): Will attempt migration (Any information below is purely informational)
• haskell-unix-compat/riscv64 (0.7-1 to 0.7-1)
  • Migration status for haskell-unix-compat/riscv64 (0.7-1 to 0.7-1): Will attempt migration (Any information below is purely informational)
• haskell-unix-time/riscv64 (0.4.11-2 to 0.4.11-2)
  • Migration status for haskell-unix-time/riscv64 (0.4.11-2 to 0.4.11-2): Will attempt migration (Any information below is purely informational)
• haskell-unixutils/riscv64 (1.54.2-2 to 1.54.2-2)
  • Migration status for haskell-unixutils/riscv64 (1.54.2-2 to 1.54.2-2): Will attempt migration (Any information below is purely informational)
• haskell-unlambda/riscv64 (0.1.4.2-8 to 0.1.4.2-8)
  • Migration status for haskell-unlambda/riscv64 (0.1.4.2-8 to 0.1.4.2-8): Will attempt migration (Any information below is purely informational)
• haskell-unliftio-core/riscv64 (0.2.1.0-1 to 0.2.1.0-1)
  • Migration status for haskell-unliftio-core/riscv64 (0.2.1.0-1 to 0.2.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-unliftio/riscv64 (0.2.25.0-1 to 0.2.25.0-1)
  • Migration status for haskell-unliftio/riscv64 (0.2.25.0-1 to 0.2.25.0-1): Will attempt migration (Any information below is purely informational)
• haskell-unordered-containers/riscv64 (0.2.19.1-2 to 0.2.19.1-2)
  • Migration status for haskell-unordered-containers/riscv64 (0.2.19.1-2 to 0.2.19.1-2): Will attempt migration (Any information below is purely informational)
• haskell-unsafe/riscv64 (0.0-4 to 0.0-4)
  • Migration status for haskell-unsafe/riscv64 (0.0-4 to 0.0-4): Will attempt migration (Any information below is purely informational)
• haskell-uri-bytestring-aeson/riscv64 (0.1.0.8-3 to 0.1.0.8-3)
  • Migration status for haskell-uri-bytestring-aeson/riscv64 (0.1.0.8-3 to 0.1.0.8-3): Will attempt migration (Any information below is purely informational)
• haskell-uri-bytestring/riscv64 (0.3.3.1-2 to 0.3.3.1-2)
  • Migration status for haskell-uri-bytestring/riscv64 (0.3.3.1-2 to 0.3.3.1-2): Will attempt migration (Any information below is purely informational)
• haskell-uri-encode/riscv64 (1.5.0.7-2 to 1.5.0.7-2)
  • Migration status for haskell-uri-encode/riscv64 (1.5.0.7-2 to 1.5.0.7-2): Will attempt migration (Any information below is purely informational)
• haskell-url/riscv64 (2.1.3-11 to 2.1.3-11)
  • Migration status for haskell-url/riscv64 (2.1.3-11 to 2.1.3-11): Will attempt migration (Any information below is purely informational)
• haskell-utf8-light/riscv64 (0.4.4.0-1 to 0.4.4.0-1)
  • Migration status for haskell-utf8-light/riscv64 (0.4.4.0-1 to 0.4.4.0-1): Will attempt migration (Any information below is purely informational)
• haskell-utf8-string/riscv64 (1.0.2-2 to 1.0.2-2)
  • Migration status for haskell-utf8-string/riscv64 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-utility-ht/riscv64 (0.0.17-1 to 0.0.17-1)
  • Migration status for haskell-utility-ht/riscv64 (0.0.17-1 to 0.0.17-1): Will attempt migration (Any information below is purely informational)
• haskell-uuagc-cabal/riscv64 (1.3.0.0-1 to 1.3.0.0-1)
  • Migration status for haskell-uuagc-cabal/riscv64 (1.3.0.0-1 to 1.3.0.0-1): Will attempt migration (Any information below is purely informational)
• haskell-uuid-types/riscv64 (1.0.5.1-1 to 1.0.5.1-1)
  • Migration status for haskell-uuid-types/riscv64 (1.0.5.1-1 to 1.0.5.1-1): Will attempt migration (Any information below is purely informational)
• haskell-uuid/riscv64 (1.3.15-2 to 1.3.15-2)
  • Migration status for haskell-uuid/riscv64 (1.3.15-2 to 1.3.15-2): Will attempt migration (Any information below is purely informational)
• haskell-uulib/riscv64 (0.9.24-3 to 0.9.24-3)
  • Migration status for haskell-uulib/riscv64 (0.9.24-3 to 0.9.24-3): Will attempt migration (Any information below is purely informational)
• haskell-validity-containers/riscv64 (0.5.0.4-3 to 0.5.0.4-3)
  • Migration status for haskell-validity-containers/riscv64 (0.5.0.4-3 to 0.5.0.4-3): Will attempt migration (Any information below is purely informational)
• haskell-validity/riscv64 (0.12.0.2-1 to 0.12.0.2-1)
  • Migration status for haskell-validity/riscv64 (0.12.0.2-1 to 0.12.0.2-1): Will attempt migration (Any information below is purely informational)
• haskell-vault/riscv64 (0.3.1.5-3 to 0.3.1.5-3)
  • Migration status for haskell-vault/riscv64 (0.3.1.5-3 to 0.3.1.5-3): Will attempt migration (Any information below is purely informational)
• haskell-vector-algorithms/riscv64 (0.9.0.1-2 to 0.9.0.1-2)
  • Migration status for haskell-vector-algorithms/riscv64 (0.9.0.1-2 to 0.9.0.1-2): Will attempt migration (Any information below is purely informational)
• haskell-vector-binary-instances/riscv64 (0.2.5.2-2 to 0.2.5.2-2)
  • Migration status for haskell-vector-binary-instances/riscv64 (0.2.5.2-2 to 0.2.5.2-2): Will attempt migration (Any information below is purely informational)
• haskell-vector-builder/riscv64 (0.3.8.4-2 to 0.3.8.4-2)
  • Migration status for haskell-vector-builder/riscv64 (0.3.8.4-2 to 0.3.8.4-2): Will attempt migration (Any information below is purely informational)
• haskell-vector-hashtables/riscv64 (0.1.1.3-3 to 0.1.1.3-3)
  • Migration status for haskell-vector-hashtables/riscv64 (0.1.1.3-3 to 0.1.1.3-3): Will attempt migration (Any information below is purely informational)
• haskell-vector-instances/riscv64 (3.4.2-1 to 3.4.2-1)
  • Migration status for haskell-vector-instances/riscv64 (3.4.2-1 to 3.4.2-1): Will attempt migration (Any information below is purely informational)
• haskell-vector-space/riscv64 (0.16-3 to 0.16-3)
  • Migration status for haskell-vector-space/riscv64 (0.16-3 to 0.16-3): Will attempt migration (Any information below is purely informational)
• haskell-vector-stream/riscv64 (0.1.0.0-2 to 0.1.0.0-2)
  • Migration status for haskell-vector-stream/riscv64 (0.1.0.0-2 to 0.1.0.0-2): Will attempt migration (Any information below is purely informational)
• haskell-vector-th-unbox/riscv64 (0.2.2-2 to 0.2.2-2)
  • Migration status for haskell-vector-th-unbox/riscv64 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
• haskell-vector/riscv64 (0.13.1.0-1 to 0.13.1.0-1)
  • Migration status for haskell-vector/riscv64 (0.13.1.0-1 to 0.13.1.0-1): Will attempt migration (Any information below is purely informational)
• haskell-versions/riscv64 (6.0.2-1 to 6.0.2-1)
  • Migration status for haskell-versions/riscv64 (6.0.2-1 to 6.0.2-1): Will attempt migration (Any information below is purely informational)
• haskell-void/riscv64 (0.7.3-4 to 0.7.3-4)
  • Migration status for haskell-void/riscv64 (0.7.3-4 to 0.7.3-4): Will attempt migration (Any information below is purely informational)
• haskell-vty/riscv64 (5.38-1 to 5.38-1)
  • Migration status for haskell-vty/riscv64 (5.38-1 to 5.38-1): Will attempt migration (Any information below is purely informational)
• haskell-wai-app-file-cgi/riscv64 (3.1.10-2 to 3.1.10-2)
  • Migration status for haskell-wai-app-file-cgi/riscv64 (3.1.10-2 to 3.1.10-2): Will attempt migration (Any information below is purely informational)
• haskell-wai-app-static/riscv64 (3.1.8-1 to 3.1.8-1)
  • Migration status for haskell-wai-app-static/riscv64 (3.1.8-1 to 3.1.8-1): Will attempt migration (Any information below is purely informational)
• haskell-wai-conduit/riscv64 (3.0.0.4-5 to 3.0.0.4-5)
  • Migration status for haskell-wai-conduit/riscv64 (3.0.0.4-5 to 3.0.0.4-5): Will attempt migration (Any information below is purely informational)
• haskell-wai-cors/riscv64 (0.2.7-3 to 0.2.7-3)
  • Migration status for haskell-wai-cors/riscv64 (0.2.7-3 to 0.2.7-3): Will attempt migration (Any information below is purely informational)
• haskell-wai-extra/riscv64 (3.1.13.0-1 to 3.1.13.0-1)
  • Migration status for haskell-wai-extra/riscv64 (3.1.13.0-1 to 3.1.13.0-1): Will attempt migration (Any information below is purely informational)
• haskell-wai-handler-launch/riscv64 (3.0.3.1-3 to 3.0.3.1-3)
  • Migration status for haskell-wai-handler-launch/riscv64 (3.0.3.1-3 to 3.0.3.1-3): Will attempt migration (Any information below is purely informational)
• haskell-wai-http2-extra/riscv64 (0.1.3-3 to 0.1.3-3)
  • Migration status for haskell-wai-http2-extra/riscv64 (0.1.3-3 to 0.1.3-3): Will attempt migration (Any information below is purely informational)
• haskell-wai-logger/riscv64 (2.4.0-2 to 2.4.0-2)
  • Migration status for haskell-wai-logger/riscv64 (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
• haskell-wai-middleware-static/riscv64 (0.9.2-2 to 0.9.2-2)
  • Migration status for haskell-wai-middleware-static/riscv64 (0.9.2-2 to 0.9.2-2): Will attempt migration (Any information below is purely informational)
• haskell-wai-websockets/riscv64 (3.0.1.2-6 to 3.0.1.2-6)
  • Migration status for haskell-wai-websockets/riscv64 (3.0.1.2-6 to 3.0.1.2-6): Will attempt migration (Any information below is purely informational)
• haskell-wai/riscv64 (3.2.3-2 to 3.2.3-2)
  • Migration status for haskell-wai/riscv64 (3.2.3-2 to 3.2.3-2): Will attempt migration (Any information below is purely informational)
• haskell-warp-tls/riscv64 (3.3.6-1 to 3.3.6-1)
  • Migration status for haskell-warp-tls/riscv64 (3.3.6-1 to 3.3.6-1): Will attempt migration (Any information below is purely informational)
• haskell-warp/riscv64 (3.3.25-1 to 3.3.25-1)
  • Migration status for haskell-warp/riscv64 (3.3.25-1 to 3.3.25-1): Will attempt migration (Any information below is purely informational)
• haskell-wcwidth/riscv64 (0.0.2-4 to 0.0.2-4)
  • Migration status for haskell-wcwidth/riscv64 (0.0.2-4 to 0.0.2-4): Will attempt migration (Any information below is purely informational)
• haskell-web-routes-boomerang/riscv64 (0.28.4.4-1 to 0.28.4.4-1)
  • Migration status for haskell-web-routes-boomerang/riscv64 (0.28.4.4-1 to 0.28.4.4-1): Will attempt migration (Any information below is purely informational)
• haskell-web-routes-happstack/riscv64 (0.23.12.3-1 to 0.23.12.3-1)
  • Migration status for haskell-web-routes-happstack/riscv64 (0.23.12.3-1 to 0.23.12.3-1): Will attempt migration (Any information below is purely informational)
• haskell-web-routes-hsp/riscv64 (0.24.6.2-2 to 0.24.6.2-2)
  • Migration status for haskell-web-routes-hsp/riscv64 (0.24.6.2-2 to 0.24.6.2-2): Will attempt migration (Any information below is purely informational)
• haskell-web-routes-th/riscv64 (0.22.8.1-1 to 0.22.8.1-1)
  • Migration status for haskell-web-routes-th/riscv64 (0.22.8.1-1 to 0.22.8.1-1): Will attempt migration (Any information below is purely informational)
• haskell-web-routes/riscv64 (0.27.15-1 to 0.27.15-1)
  • Migration status for haskell-web-routes/riscv64 (0.27.15-1 to 0.27.15-1): Will attempt migration (Any information below is purely informational)
• haskell-websockets/riscv64 (0.12.7.3-2 to 0.12.7.3-2)
  • Migration status for haskell-websockets/riscv64 (0.12.7.3-2 to 0.12.7.3-2): Will attempt migration (Any information below is purely informational)
• haskell-weigh/riscv64 (0.0.16-3 to 0.0.16-3)
  • Migration status for haskell-weigh/riscv64 (0.0.16-3 to 0.0.16-3): Will attempt migration (Any information below is purely informational)
• haskell-what4/riscv64 (1.5.1-3 to 1.5.1-3)
  • Migration status for haskell-what4/riscv64 (1.5.1-3 to 1.5.1-3): Will attempt migration (Any information below is purely informational)
• haskell-wide-word/riscv64 (0.1.5.0-1 to 0.1.5.0-1)
  • Migration status for haskell-wide-word/riscv64 (0.1.5.0-1 to 0.1.5.0-1): Will attempt migration (Any information below is purely informational)
• haskell-witch/riscv64 (1.2.0.2-1 to 1.2.0.2-1)
  • Migration status for haskell-witch/riscv64 (1.2.0.2-1 to 1.2.0.2-1): Will attempt migration (Any information below is purely informational)
• haskell-with-location/riscv64 (0.1.0-8 to 0.1.0-8)
  • Migration status for haskell-with-location/riscv64 (0.1.0-8 to 0.1.0-8): Will attempt migration (Any information below is purely informational)
• haskell-witherable/riscv64 (0.4.2-3 to 0.4.2-3)
  • Migration status for haskell-witherable/riscv64 (0.4.2-3 to 0.4.2-3): Will attempt migration (Any information below is purely informational)
• haskell-wizards/riscv64 (1.0.3-4 to 1.0.3-4)
  • Migration status for haskell-wizards/riscv64 (1.0.3-4 to 1.0.3-4): Will attempt migration (Any information below is purely informational)
• haskell-wl-pprint-annotated/riscv64 (0.1.0.1-5 to 0.1.0.1-5)
  • Migration status for haskell-wl-pprint-annotated/riscv64 (0.1.0.1-5 to 0.1.0.1-5): Will attempt migration (Any information below is purely informational)
• haskell-wl-pprint-text/riscv64 (1.2.0.2-2 to 1.2.0.2-2)
  • Migration status for haskell-wl-pprint-text/riscv64 (1.2.0.2-2 to 1.2.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-word-trie/riscv64 (0.3.0-11 to 0.3.0-11)
  • Migration status for haskell-word-trie/riscv64 (0.3.0-11 to 0.3.0-11): Will attempt migration (Any information below is purely informational)
• haskell-word-wrap/riscv64 (0.5-2 to 0.5-2)
  • Migration status for haskell-word-wrap/riscv64 (0.5-2 to 0.5-2): Will attempt migration (Any information below is purely informational)
• haskell-word8/riscv64 (0.1.3-6 to 0.1.3-6)
  • Migration status for haskell-word8/riscv64 (0.1.3-6 to 0.1.3-6): Will attempt migration (Any information below is purely informational)
• haskell-wreq/riscv64 (0.5.4.2-1 to 0.5.4.2-1)
  • Migration status for haskell-wreq/riscv64 (0.5.4.2-1 to 0.5.4.2-1): Will attempt migration (Any information below is purely informational)
• haskell-x11-xft/riscv64 (0.3.4-3 to 0.3.4-3)
  • Migration status for haskell-x11-xft/riscv64 (0.3.4-3 to 0.3.4-3): Will attempt migration (Any information below is purely informational)
• haskell-x11/riscv64 (1.10.3-2 to 1.10.3-2)
  • Migration status for haskell-x11/riscv64 (1.10.3-2 to 1.10.3-2): Will attempt migration (Any information below is purely informational)
• haskell-x509-store/riscv64 (1.6.9-2 to 1.6.9-2)
  • Migration status for haskell-x509-store/riscv64 (1.6.9-2 to 1.6.9-2): Will attempt migration (Any information below is purely informational)
• haskell-x509-system/riscv64 (1.6.7-2 to 1.6.7-2)
  • Migration status for haskell-x509-system/riscv64 (1.6.7-2 to 1.6.7-2): Will attempt migration (Any information below is purely informational)
• haskell-x509-validation/riscv64 (1.6.12-2 to 1.6.12-2)
  • Migration status for haskell-x509-validation/riscv64 (1.6.12-2 to 1.6.12-2): Will attempt migration (Any information below is purely informational)
• haskell-x509/riscv64 (1.7.7-2 to 1.7.7-2)
  • Migration status for haskell-x509/riscv64 (1.7.7-2 to 1.7.7-2): Will attempt migration (Any information below is purely informational)
• haskell-xcb-types/riscv64 (0.13.0-1 to 0.13.0-1)
  • Migration status for haskell-xcb-types/riscv64 (0.13.0-1 to 0.13.0-1): Will attempt migration (Any information below is purely informational)
• haskell-xdg-basedir/riscv64 (0.2.2-13 to 0.2.2-13)
  • Migration status for haskell-xdg-basedir/riscv64 (0.2.2-13 to 0.2.2-13): Will attempt migration (Any information below is purely informational)
• haskell-xdg-desktop-entry/riscv64 (0.1.1.1-3 to 0.1.1.1-3)
  • Migration status for haskell-xdg-desktop-entry/riscv64 (0.1.1.1-3 to 0.1.1.1-3): Will attempt migration (Any information below is purely informational)
• haskell-xml-conduit-writer/riscv64 (0.1.1.4-1 to 0.1.1.4-1)
  • Migration status for haskell-xml-conduit-writer/riscv64 (0.1.1.4-1 to 0.1.1.4-1): Will attempt migration (Any information below is purely informational)
• haskell-xml-conduit/riscv64 (1.9.1.3-1 to 1.9.1.3-1)
  • Migration status for haskell-xml-conduit/riscv64 (1.9.1.3-1 to 1.9.1.3-1): Will attempt migration (Any information below is purely informational)
• haskell-xml-hamlet/riscv64 (0.5.0.2-2 to 0.5.0.2-2)
  • Migration status for haskell-xml-hamlet/riscv64 (0.5.0.2-2 to 0.5.0.2-2): Will attempt migration (Any information below is purely informational)
• haskell-xml-helpers/riscv64 (1.0.0-5 to 1.0.0-5)
  • Migration status for haskell-xml-helpers/riscv64 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• haskell-xml-html-qq/riscv64 (0.1.0.1-4 to 0.1.0.1-4)
  • Migration status for haskell-xml-html-qq/riscv64 (0.1.0.1-4 to 0.1.0.1-4): Will attempt migration (Any information below is purely informational)
• haskell-xml-types/riscv64 (0.3.8-3 to 0.3.8-3)
  • Migration status for haskell-xml-types/riscv64 (0.3.8-3 to 0.3.8-3): Will attempt migration (Any information below is purely informational)
• haskell-xml/riscv64 (1.3.14-12 to 1.3.14-12)
  • Migration status for haskell-xml/riscv64 (1.3.14-12 to 1.3.14-12): Will attempt migration (Any information below is purely informational)
• haskell-xmlgen/riscv64 (0.6.2.2-6 to 0.6.2.2-6)
  • Migration status for haskell-xmlgen/riscv64 (0.6.2.2-6 to 0.6.2.2-6): Will attempt migration (Any information below is purely informational)
• haskell-xmlhtml/riscv64 (0.2.5.4-1 to 0.2.5.4-1)
  • Migration status for haskell-xmlhtml/riscv64 (0.2.5.4-1 to 0.2.5.4-1): Will attempt migration (Any information below is purely informational)
• haskell-xss-sanitize/riscv64 (0.3.7.2-1 to 0.3.7.2-1)
  • Migration status for haskell-xss-sanitize/riscv64 (0.3.7.2-1 to 0.3.7.2-1): Will attempt migration (Any information below is purely informational)
• haskell-yaml/riscv64 (0.11.11.2-1 to 0.11.11.2-1)
  • Migration status for haskell-yaml/riscv64 (0.11.11.2-1 to 0.11.11.2-1): Will attempt migration (Any information below is purely informational)
• haskell-yesod-auth-hashdb/riscv64 (1.7.1.7-2 to 1.7.1.7-2)
  • Migration status for haskell-yesod-auth-hashdb/riscv64 (1.7.1.7-2 to 1.7.1.7-2): Will attempt migration (Any information below is purely informational)
• haskell-yesod-auth-oauth/riscv64 (1.6.1-2 to 1.6.1-2)
  • Migration status for haskell-yesod-auth-oauth/riscv64 (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
• haskell-yesod-auth/riscv64 (1.6.11.2-1 to 1.6.11.2-1)
  • Migration status for haskell-yesod-auth/riscv64 (1.6.11.2-1 to 1.6.11.2-1): Will attempt migration (Any information below is purely informational)
• haskell-yesod-core/riscv64 (1.6.24.5-1 to 1.6.24.5-1)
  • Migration status for haskell-yesod-core/riscv64 (1.6.24.5-1 to 1.6.24.5-1): Will attempt migration (Any information below is purely informational)
• haskell-yesod-default/riscv64 (1.2.0-13 to 1.2.0-13)
  • Migration status for haskell-yesod-default/riscv64 (1.2.0-13 to 1.2.0-13): Will attempt migration (Any information below is purely informational)
• haskell-yesod-form/riscv64 (1.7.6-1 to 1.7.6-1)
  • Migration status for haskell-yesod-form/riscv64 (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
• haskell-yesod-newsfeed/riscv64 (1.7.0.0-3 to 1.7.0.0-3)
  • Migration status for haskell-yesod-newsfeed/riscv64 (1.7.0.0-3 to 1.7.0.0-3): Will attempt migration (Any information below is purely informational)
• haskell-yesod-persistent/riscv64 (1.6.0.8-2 to 1.6.0.8-2)
  • Migration status for haskell-yesod-persistent/riscv64 (1.6.0.8-2 to 1.6.0.8-2): Will attempt migration (Any information below is purely informational)
• haskell-yesod-static/riscv64 (1.6.1.0-3 to 1.6.1.0-3)
  • Migration status for haskell-yesod-static/riscv64 (1.6.1.0-3 to 1.6.1.0-3): Will attempt migration (Any information below is purely informational)
• haskell-yesod-test/riscv64 (1.6.16-1 to 1.6.16-1)
  • Migration status for haskell-yesod-test/riscv64 (1.6.16-1 to 1.6.16-1): Will attempt migration (Any information below is purely informational)
• haskell-yesod/riscv64 (1.6.2.1-2 to 1.6.2.1-2)
  • Migration status for haskell-yesod/riscv64 (1.6.2.1-2 to 1.6.2.1-2): Will attempt migration (Any information below is purely informational)
• haskell-yi-core/riscv64 (0.19.2-3 to 0.19.2-3)
  • Migration status for haskell-yi-core/riscv64 (0.19.2-3 to 0.19.2-3): Will attempt migration (Any information below is purely informational)
• haskell-yi-frontend-pango/riscv64 (0.19.1-3 to 0.19.1-3)
  • Migration status for haskell-yi-frontend-pango/riscv64 (0.19.1-3 to 0.19.1-3): Will attempt migration (Any information below is purely informational)
• haskell-yi-frontend-vty/riscv64 (0.19.0-3 to 0.19.0-3)
  • Migration status for haskell-yi-frontend-vty/riscv64 (0.19.0-3 to 0.19.0-3): Will attempt migration (Any information below is purely informational)
• haskell-yi-keymap-emacs/riscv64 (0.19.0-3 to 0.19.0-3)
  • Migration status for haskell-yi-keymap-emacs/riscv64 (0.19.0-3 to 0.19.0-3): Will attempt migration (Any information below is purely informational)
• haskell-yi-keymap-vim/riscv64 (0.19.0-3 to 0.19.0-3)
  • Migration status for haskell-yi-keymap-vim/riscv64 (0.19.0-3 to 0.19.0-3): Will attempt migration (Any information below is purely informational)
• haskell-yi-language/riscv64 (0.19.0-3 to 0.19.0-3)
  • Migration status for haskell-yi-language/riscv64 (0.19.0-3 to 0.19.0-3): Will attempt migration (Any information below is purely informational)
• haskell-yi-misc-modes/riscv64 (0.19.0-3 to 0.19.0-3)
  • Migration status for haskell-yi-misc-modes/riscv64 (0.19.0-3 to 0.19.0-3): Will attempt migration (Any information below is purely informational)
• haskell-yi-mode-haskell/riscv64 (0.19.0-3 to 0.19.0-3)
  • Migration status for haskell-yi-mode-haskell/riscv64 (0.19.0-3 to 0.19.0-3): Will attempt migration (Any information below is purely informational)
• haskell-yi-mode-javascript/riscv64 (0.19.0-3 to 0.19.0-3)
  • Migration status for haskell-yi-mode-javascript/riscv64 (0.19.0-3 to 0.19.0-3): Will attempt migration (Any information below is purely informational)
• haskell-yi-rope/riscv64 (0.11-5 to 0.11-5)
  • Migration status for haskell-yi-rope/riscv64 (0.11-5 to 0.11-5): Will attempt migration (Any information below is purely informational)
• haskell-zenc/riscv64 (0.1.2-3 to 0.1.2-3)
  • Migration status for haskell-zenc/riscv64 (0.1.2-3 to 0.1.2-3): Will attempt migration (Any information below is purely informational)
• haskell-zeromq4-haskell/riscv64 (0.8.0-3 to 0.8.0-3)
  • Migration status for haskell-zeromq4-haskell/riscv64 (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• haskell-zip-archive/riscv64 (0.4.3-1 to 0.4.3-1)
  • Migration status for haskell-zip-archive/riscv64 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• haskell-zlib-bindings/riscv64 (0.1.1.5-12 to 0.1.1.5-12)
  • Migration status for haskell-zlib-bindings/riscv64 (0.1.1.5-12 to 0.1.1.5-12): Will attempt migration (Any information below is purely informational)
• haskell-zlib/riscv64 (0.6.3.0-2 to 0.6.3.0-2)
  • Migration status for haskell-zlib/riscv64 (0.6.3.0-2 to 0.6.3.0-2): Will attempt migration (Any information below is purely informational)
• haskell-zxcvbn-c/riscv64 (1.0.1-8 to 1.0.1-8)
  • Migration status for haskell-zxcvbn-c/riscv64 (1.0.1-8 to 1.0.1-8): Will attempt migration (Any information below is purely informational)
• hatari/riscv64 (2.4.1+dfsg-2 to 2.4.1+dfsg-2)
  • Migration status for hatari/riscv64 (2.4.1+dfsg-2 to 2.4.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• haxml/riscv64 (1:1.25.13-1 to 1:1.25.13-1)
  • Migration status for haxml/riscv64 (1:1.25.13-1 to 1:1.25.13-1): Will attempt migration (Any information below is purely informational)
• hdate-applet/riscv64 (0.15.11-4 to 0.15.11-4)
  • Migration status for hdate-applet/riscv64 (0.15.11-4 to 0.15.11-4): Will attempt migration (Any information below is purely informational)
• hdbc-postgresql/riscv64 (2.5.0.1-2 to 2.5.0.1-2)
  • Migration status for hdbc-postgresql/riscv64 (2.5.0.1-2 to 2.5.0.1-2): Will attempt migration (Any information below is purely informational)
• hdbc-sqlite3/riscv64 (2.3.3.1-10 to 2.3.3.1-10)
  • Migration status for hdbc-sqlite3/riscv64 (2.3.3.1-10 to 2.3.3.1-10): Will attempt migration (Any information below is purely informational)
• hdbc/riscv64 (2.4.0.4-2 to 2.4.0.4-2)
  • Migration status for hdbc/riscv64 (2.4.0.4-2 to 2.4.0.4-2): Will attempt migration (Any information below is purely informational)
• healpy/riscv64 (1.16.6-2 to 1.16.6-2)
  • Migration status for healpy/riscv64 (1.16.6-2 to 1.16.6-2): Will attempt migration (Any information below is purely informational)
• helpviewer.app/riscv64 (0.4-1 to 0.4-1)
  • Migration status for helpviewer.app/riscv64 (0.4-1 to 0.4-1): Will attempt migration (Any information below is purely informational)
• herculesstudio/riscv64 (1.5.0-6 to 1.5.0-6)
  • Migration status for herculesstudio/riscv64 (1.5.0-6 to 1.5.0-6): Will attempt migration (Any information below is purely informational)
• hevea/riscv64 (2.36-2 to 2.36-2)
  • Migration status for hevea/riscv64 (2.36-2 to 2.36-2): Will attempt migration (Any information below is purely informational)
• hex-a-hop/riscv64 (1.1.0+git20140926-2 to 1.1.0+git20140926-2)
  • Migration status for hex-a-hop/riscv64 (1.1.0+git20140926-2 to 1.1.0+git20140926-2): Will attempt migration (Any information below is purely informational)
• hexalate/riscv64 (1.2.2-1 to 1.2.2-1)
  • Migration status for hexalate/riscv64 (1.2.2-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
• hexchat/riscv64 (2.16.2-1 to 2.16.2-1)
  • Migration status for hexchat/riscv64 (2.16.2-1 to 2.16.2-1): Will attempt migration (Any information below is purely informational)
• hfd-service/riscv64 (0.2.2-1 to 0.2.2-1)
  • Migration status for hfd-service/riscv64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• hfst-ospell/riscv64 (0.5.4-1 to 0.5.4-1)
  • Migration status for hfst-ospell/riscv64 (0.5.4-1 to 0.5.4-1): Will attempt migration (Any information below is purely informational)
• hime/riscv64 (0.9.11+dfsg-4 to 0.9.11+dfsg-4)
  • Migration status for hime/riscv64 (0.9.11+dfsg-4 to 0.9.11+dfsg-4): Will attempt migration (Any information below is purely informational)
• hinge/riscv64 (0.5.0-7 to 0.5.0-7)
  • Migration status for hinge/riscv64 (0.5.0-7 to 0.5.0-7): Will attempt migration (Any information below is purely informational)
• hintview/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for hintview/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• hipify/riscv64 (6.0.2+dfsg-1 to 6.0.2+dfsg-1)
  • Migration status for hipify/riscv64 (6.0.2+dfsg-1 to 6.0.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• hitori/riscv64 (44.0-2 to 44.0-2)
  • Migration status for hitori/riscv64 (44.0-2 to 44.0-2): Will attempt migration (Any information below is purely informational)
• hlint/riscv64 (3.5-1 to 3.5-1)
  • Migration status for hlint/riscv64 (3.5-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
• holotz-castle/riscv64 (1.3.14-12 to 1.3.14-12)
  • Migration status for holotz-castle/riscv64 (1.3.14-12 to 1.3.14-12): Will attempt migration (Any information below is purely informational)
• hplip/amd64 (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1)
  • Migration status for hplip/amd64 (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hplip/arm64 (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1)
  • Migration status for hplip/arm64 (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hplip/armel (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1)
  • Migration status for hplip/armel (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hplip/armhf (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1)
  • Migration status for hplip/armhf (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hplip/i386 (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1)
  • Migration status for hplip/i386 (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hplip/mips64el (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1)
  • Migration status for hplip/mips64el (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hplip/ppc64el (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1)
  • Migration status for hplip/ppc64el (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hplip/riscv64 (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1)
  • Migration status for hplip/riscv64 (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hplip/s390x (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1)
  • Migration status for hplip/s390x (3.22.10+dfsg0-5.1 to 3.22.10+dfsg0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hscolour/riscv64 (1.24.4-5 to 1.24.4-5)
  • Migration status for hscolour/riscv64 (1.24.4-5 to 1.24.4-5): Will attempt migration (Any information below is purely informational)
• hsetroot/riscv64 (1.0.5-1 to 1.0.5-1)
  • Migration status for hsetroot/riscv64 (1.0.5-1 to 1.0.5-1): Will attempt migration (Any information below is purely informational)
• hslogger/riscv64 (1.3.1.0+dfsg-2 to 1.3.1.0+dfsg-2)
  • Migration status for hslogger/riscv64 (1.3.1.0+dfsg-2 to 1.3.1.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• hspell-gui/riscv64 (0.2.6-7 to 0.2.6-7)
  • Migration status for hspell-gui/riscv64 (0.2.6-7 to 0.2.6-7): Will attempt migration (Any information below is purely informational)
• html5-parser/riscv64 (0.4.12+ds-1 to 0.4.12+ds-1)
  • Migration status for html5-parser/riscv64 (0.4.12+ds-1 to 0.4.12+ds-1): Will attempt migration (Any information below is purely informational)
• httraqt/riscv64 (1.4.11-1 to 1.4.11-1)
  • Migration status for httraqt/riscv64 (1.4.11-1 to 1.4.11-1): Will attempt migration (Any information below is purely informational)
• hydra/riscv64 (9.5-1 to 9.5-1)
  • Migration status for hydra/riscv64 (9.5-1 to 9.5-1): Will attempt migration (Any information below is purely informational)
• hyperrogue/riscv64 (12.1q-1 to 12.1q-1)
  • Migration status for hyperrogue/riscv64 (12.1q-1 to 12.1q-1): Will attempt migration (Any information below is purely informational)
• i3lock-fancy/riscv64 (0.0~git20160228.0.0fcb933-3 to 0.0~git20160228.0.0fcb933-3)
  • Migration status for i3lock-fancy/riscv64 (0.0~git20160228.0.0fcb933-3 to 0.0~git20160228.0.0fcb933-3): Will attempt migration (Any information below is purely informational)
• iagno/riscv64 (1:3.38.1-2 to 1:3.38.1-2)
  • Migration status for iagno/riscv64 (1:3.38.1-2 to 1:3.38.1-2): Will attempt migration (Any information below is purely informational)
• iannix/riscv64 (0.9.20~dfsg1-1 to 0.9.20~dfsg1-1)
  • Migration status for iannix/riscv64 (0.9.20~dfsg1-1 to 0.9.20~dfsg1-1): Will attempt migration (Any information below is purely informational)
• ibus-client-clutter/riscv64 (0.0+git20090728.a936bacf-8 to 0.0+git20090728.a936bacf-8)
  • Migration status for ibus-client-clutter/riscv64 (0.0+git20090728.a936bacf-8 to 0.0+git20090728.a936bacf-8): Will attempt migration (Any information below is purely informational)
• ibus-hangul/riscv64 (1.5.5-2 to 1.5.5-2)
  • Migration status for ibus-hangul/riscv64 (1.5.5-2 to 1.5.5-2): Will attempt migration (Any information below is purely informational)
• ibus-input-pad/riscv64 (1.4.99.20140916-3 to 1.4.99.20140916-3)
  • Migration status for ibus-input-pad/riscv64 (1.4.99.20140916-3 to 1.4.99.20140916-3): Will attempt migration (Any information below is purely informational)
• ibus-kkc/riscv64 (1.5.22-4 to 1.5.22-4)
  • Migration status for ibus-kkc/riscv64 (1.5.22-4 to 1.5.22-4): Will attempt migration (Any information below is purely informational)
• ibus-libthai/riscv64 (0.1.5-1 to 0.1.5-1)
  • Migration status for ibus-libthai/riscv64 (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• ibus-skk/riscv64 (1.4.3-3 to 1.4.3-3)
  • Migration status for ibus-skk/riscv64 (1.4.3-3 to 1.4.3-3): Will attempt migration (Any information below is purely informational)
• ibus-sunpinyin/riscv64 (2.0.3+git20210228-1 to 2.0.3+git20210228-1)
  • Migration status for ibus-sunpinyin/riscv64 (2.0.3+git20210228-1 to 2.0.3+git20210228-1): Will attempt migration (Any information below is purely informational)
• ibus-table-extraphrase/riscv64 (1.3.9.20110826-5 to 1.3.9.20110826-5)
  • Migration status for ibus-table-extraphrase/riscv64 (1.3.9.20110826-5 to 1.3.9.20110826-5): Will attempt migration (Any information below is purely informational)
• ibus-unikey/riscv64 (0.7.0~beta1-2 to 0.7.0~beta1-2)
  • Migration status for ibus-unikey/riscv64 (0.7.0~beta1-2 to 0.7.0~beta1-2): Will attempt migration (Any information below is purely informational)
• icecast2/riscv64 (2.4.4-4 to 2.4.4-4)
  • Migration status for icecast2/riscv64 (2.4.4-4 to 2.4.4-4): Will attempt migration (Any information below is purely informational)
• icecc-monitor/riscv64 (3.3-2 to 3.3-2)
  • Migration status for icecc-monitor/riscv64 (3.3-2 to 3.3-2): Will attempt migration (Any information below is purely informational)
• icecc/riscv64 (1.4-1 to 1.4-1)
  • Migration status for icecc/riscv64 (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• ices2/riscv64 (2.0.3-1 to 2.0.3-1)
  • Migration status for ices2/riscv64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• icu-ext/riscv64 (1.8.0-1 to 1.8.0-1)
  • Migration status for icu-ext/riscv64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• identity4c/riscv64 (1.0-1.1 to 1.0-1.1)
  • Migration status for identity4c/riscv64 (1.0-1.1 to 1.0-1.1): Will attempt migration (Any information below is purely informational)
• ifcplusplus/riscv64 (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4)
  • Migration status for ifcplusplus/riscv64 (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4): Will attempt migration (Any information below is purely informational)
• ignition-common/riscv64 (4.7.0+ds2-2.1 to 4.7.0+ds2-2.1)
  • Migration status for ignition-common/riscv64 (4.7.0+ds2-2.1 to 4.7.0+ds2-2.1): Will attempt migration (Any information below is purely informational)
• ignition-fuel-tools/riscv64 (7.0.0+ds-3.1 to 7.0.0+ds-3.1)
  • Migration status for ignition-fuel-tools/riscv64 (7.0.0+ds-3.1 to 7.0.0+ds-3.1): Will attempt migration (Any information below is purely informational)
• ignition-transport/riscv64 (11.0.0+ds-4 to 11.0.0+ds-4)
  • Migration status for ignition-transport/riscv64 (11.0.0+ds-4 to 11.0.0+ds-4): Will attempt migration (Any information below is purely informational)
• ii-esu/riscv64 (1.0a.dfsg2-2 to 1.0a.dfsg2-2)
  • Migration status for ii-esu/riscv64 (1.0a.dfsg2-2 to 1.0a.dfsg2-2): Will attempt migration (Any information below is purely informational)
• ikiwiki-hosting_pu (0.20220717-1 to 0.20220716-2+deb12u1)
  • Migration status for ikiwiki-hosting_pu (0.20220717-1 to 0.20220716-2+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ikiwiki-hosting is newer in the target suite (0.20220717-1 0.20220716-2+deb12u1)
• imagination/riscv64 (3.6-2 to 3.6-2)
  • Migration status for imagination/riscv64 (3.6-2 to 3.6-2): Will attempt migration (Any information below is purely informational)
• imexam/riscv64 (0.9.1-6 to 0.9.1-6)
  • Migration status for imexam/riscv64 (0.9.1-6 to 0.9.1-6): Will attempt migration (Any information below is purely informational)
• imgvtopgm/riscv64 (2.1-2 to 2.1-2)
  • Migration status for imgvtopgm/riscv64 (2.1-2 to 2.1-2): Will attempt migration (Any information below is purely informational)
• imlib2/riscv64 (1.12.1-1.1 to 1.12.1-1.1)
  • Migration status for imlib2/riscv64 (1.12.1-1.1 to 1.12.1-1.1): Will attempt migration (Any information below is purely informational)
• indi-gphoto/riscv64 (3.2+20221221172841-2 to 3.2+20221221172841-2)
  • Migration status for indi-gphoto/riscv64 (3.2+20221221172841-2 to 3.2+20221221172841-2): Will attempt migration (Any information below is purely informational)
• indi-webcam/riscv64 (1.0+20221222161740-1 to 1.0+20221222161740-1)
  • Migration status for indi-webcam/riscv64 (1.0+20221222161740-1 to 1.0+20221222161740-1): Will attempt migration (Any information below is purely informational)
• indicator-sensors/riscv64 (1.4-1 to 1.4-1)
  • Migration status for indicator-sensors/riscv64 (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• injeqt/riscv64 (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for injeqt/riscv64 (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
• ink/riscv64 (0.5.3-6 to 0.5.3-6)
  • Migration status for ink/riscv64 (0.5.3-6 to 0.5.3-6): Will attempt migration (Any information below is purely informational)
• input-pad/riscv64 (1.0.99.20210817-2 to 1.0.99.20210817-2)
  • Migration status for input-pad/riscv64 (1.0.99.20210817-2 to 1.0.99.20210817-2): Will attempt migration (Any information below is purely informational)
• inspectrum/riscv64 (0.3.1-1 to 0.3.1-1)
  • Migration status for inspectrum/riscv64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• instead/riscv64 (3.3.2-1.1 to 3.3.2-1.1)
  • Migration status for instead/riscv64 (3.3.2-1.1 to 3.3.2-1.1): Will attempt migration (Any information below is purely informational)
• iortcw/riscv64 (1.51.c+dfsg1-7 to 1.51.c+dfsg1-7)
  • Migration status for iortcw/riscv64 (1.51.c+dfsg1-7 to 1.51.c+dfsg1-7): Will attempt migration (Any information below is purely informational)
• ipqalc/riscv64 (1.5.3+git20200816.523b207-3 to 1.5.3+git20200816.523b207-3)
  • Migration status for ipqalc/riscv64 (1.5.3+git20200816.523b207-3 to 1.5.3+git20200816.523b207-3): Will attempt migration (Any information below is purely informational)
• ir.lv2/riscv64 (1.3.4~dfsg0-3 to 1.3.4~dfsg0-3)
  • Migration status for ir.lv2/riscv64 (1.3.4~dfsg0-3 to 1.3.4~dfsg0-3): Will attempt migration (Any information below is purely informational)
• irrlicht/riscv64 (1.8.5+ds2-1.1 to 1.8.5+ds2-1.1)
  • Migration status for irrlicht/riscv64 (1.8.5+ds2-1.1 to 1.8.5+ds2-1.1): Will attempt migration (Any information below is purely informational)
• itinerary/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for itinerary/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• iwgtk/riscv64 (0.9-1 to 0.9-1)
  • Migration status for iwgtk/riscv64 (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
• jack-keyboard/riscv64 (2.7.2-1 to 2.7.2-1)
  • Migration status for jack-keyboard/riscv64 (2.7.2-1 to 2.7.2-1): Will attempt migration (Any information below is purely informational)
• jag/riscv64 (0.3.8-2 to 0.3.8-2)
  • Migration status for jag/riscv64 (0.3.8-2 to 0.3.8-2): Will attempt migration (Any information below is purely informational)
• jalv/riscv64 (1.6.8-1 to 1.6.8-1)
  • Migration status for jalv/riscv64 (1.6.8-1 to 1.6.8-1): Will attempt migration (Any information below is purely informational)
• java-atk-wrapper/riscv64 (0.40.0-3 to 0.40.0-3)
  • Migration status for java-atk-wrapper/riscv64 (0.40.0-3 to 0.40.0-3): Will attempt migration (Any information below is purely informational)
• java3d/riscv64 (1.5.2+dfsg-18 to 1.5.2+dfsg-18)
  • Migration status for java3d/riscv64 (1.5.2+dfsg-18 to 1.5.2+dfsg-18): Will attempt migration (Any information below is purely informational)
• jdim/riscv64 (0.10.1-1 to 0.10.1-1)
  • Migration status for jdim/riscv64 (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
• jesred/riscv64 (1.2pl1-23 to 1.2pl1-23)
  • Migration status for jesred/riscv64 (1.2pl1-23 to 1.2pl1-23): Will attempt migration (Any information below is purely informational)
• jgmenu/riscv64 (4.4.1-2 to 4.4.1-2)
  • Migration status for jgmenu/riscv64 (4.4.1-2 to 4.4.1-2): Will attempt migration (Any information below is purely informational)
• jhead/riscv64 (1:3.08-2 to 1:3.08-2)
  • Migration status for jhead/riscv64 (1:3.08-2 to 1:3.08-2): Will attempt migration (Any information below is purely informational)
• jigzo/riscv64 (0.6.1-7.1 to 0.6.1-7.1)
  • Migration status for jigzo/riscv64 (0.6.1-7.1 to 0.6.1-7.1): Will attempt migration (Any information below is purely informational)
• jitterdebugger/riscv64 (0.3.1+git20200117.b90ff3a-5 to 0.3.1+git20200117.b90ff3a-5)
  • Migration status for jitterdebugger/riscv64 (0.3.1+git20200117.b90ff3a-5 to 0.3.1+git20200117.b90ff3a-5): Will attempt migration (Any information below is purely informational)
• jmagick/riscv64 (6.6.9~20130201-svn99-5 to 6.6.9~20130201-svn99-5)
  • Migration status for jmagick/riscv64 (6.6.9~20130201-svn99-5 to 6.6.9~20130201-svn99-5): Will attempt migration (Any information below is purely informational)
• jreen/riscv64 (1.2.0+ds-2 to 1.2.0+ds-2)
  • Migration status for jreen/riscv64 (1.2.0+ds-2 to 1.2.0+ds-2): Will attempt migration (Any information below is purely informational)
• js-of-ocaml/amd64 (5.8.2-2 to 5.8.2-2)
  • Migration status for js-of-ocaml/amd64 (5.8.2-2 to 5.8.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libjs-of-ocaml/5.8.2-2+b4/amd64 to testing makes libcohttp-lwt-jsoo-ocaml/5.3.0-1+b13/amd64 uninstallable
    • migrating libjs-of-ocaml/5.8.2-2+b4/amd64 to testing makes nurpawiki/1.2.4-4+b14/amd64 uninstallable
    • migrating libjs-of-ocaml-dev/5.8.2-2+b4/amd64 to testing makes libcohttp-lwt-jsoo-ocaml-dev/5.3.0-1+b13/amd64 uninstallable
    • migrating libjs-of-ocaml-dev/5.8.2-2+b4/amd64 to testing makes libeliom-ocaml-dev/10.4.1-1+b5/amd64 uninstallable
    • Depends: js-of-ocaml/amd64 tyxml/amd64 (not considered)
    • Implicit dependency: js-of-ocaml/amd64 ocaml-logs/amd64
• js-of-ocaml/arm64 (5.8.2-2 to 5.8.2-2)
  • Migration status for js-of-ocaml/arm64 (5.8.2-2 to 5.8.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libjs-of-ocaml/5.8.2-2+b4/arm64 to testing makes libcohttp-lwt-jsoo-ocaml/5.3.0-1+b13/arm64 uninstallable
    • migrating libjs-of-ocaml/5.8.2-2+b4/arm64 to testing makes nurpawiki/1.2.4-4+b14/arm64 uninstallable
    • migrating libjs-of-ocaml-dev/5.8.2-2+b4/arm64 to testing makes libcohttp-lwt-jsoo-ocaml-dev/5.3.0-1+b13/arm64 uninstallable
    • migrating libjs-of-ocaml-dev/5.8.2-2+b4/arm64 to testing makes libeliom-ocaml-dev/10.4.1-1+b5/arm64 uninstallable
    • Depends: js-of-ocaml/arm64 tyxml/arm64 (not considered)
    • Implicit dependency: js-of-ocaml/arm64 ocaml-logs/arm64
• js-of-ocaml/ppc64el (5.8.2-2 to 5.8.2-2)
  • Migration status for js-of-ocaml/ppc64el (5.8.2-2 to 5.8.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libjs-of-ocaml/5.8.2-2+b4/ppc64el to testing makes libcohttp-lwt-jsoo-ocaml/5.3.0-1+b13/ppc64el uninstallable
    • migrating libjs-of-ocaml/5.8.2-2+b4/ppc64el to testing makes nurpawiki/1.2.4-4+b14/ppc64el uninstallable
    • migrating libjs-of-ocaml-dev/5.8.2-2+b4/ppc64el to testing makes libcohttp-lwt-jsoo-ocaml-dev/5.3.0-1+b13/ppc64el uninstallable
    • migrating libjs-of-ocaml-dev/5.8.2-2+b4/ppc64el to testing makes libeliom-ocaml-dev/10.4.1-1+b5/ppc64el uninstallable
    • Depends: js-of-ocaml/ppc64el tyxml/ppc64el (not considered)
    • Implicit dependency: js-of-ocaml/ppc64el ocaml-logs/ppc64el
• js-of-ocaml/riscv64 (5.8.2-2 to 5.8.2-2)
  • Migration status for js-of-ocaml/riscv64 (5.8.2-2 to 5.8.2-2): Will attempt migration (Any information below is purely informational)
• js-of-ocaml/s390x (5.8.2-2 to 5.8.2-2)
  • Migration status for js-of-ocaml/s390x (5.8.2-2 to 5.8.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libjs-of-ocaml/5.8.2-2+b4/s390x to testing makes libcohttp-lwt-jsoo-ocaml/5.3.0-1+b13/s390x uninstallable
    • migrating libjs-of-ocaml/5.8.2-2+b4/s390x to testing makes nurpawiki/1.2.4-4+b14/s390x uninstallable
    • migrating libjs-of-ocaml-dev/5.8.2-2+b4/s390x to testing makes libcohttp-lwt-jsoo-ocaml-dev/5.3.0-1+b13/s390x uninstallable
    • migrating libjs-of-ocaml-dev/5.8.2-2+b4/s390x to testing makes libeliom-ocaml-dev/10.4.1-1+b5/s390x uninstallable
    • Depends: js-of-ocaml/s390x tyxml/s390x (not considered)
    • Implicit dependency: js-of-ocaml/s390x ocaml-logs/s390x
• js8call/riscv64 (2.2.0+ds-5 to 2.2.0+ds-5)
  • Migration status for js8call/riscv64 (2.2.0+ds-5 to 2.2.0+ds-5): Will attempt migration (Any information below is purely informational)
• jstest-gtk/riscv64 (0.1.1~git20180602-2 to 0.1.1~git20180602-2)
  • Migration status for jstest-gtk/riscv64 (0.1.1~git20180602-2 to 0.1.1~git20180602-2): Will attempt migration (Any information below is purely informational)
• jtdx/riscv64 (2.2.159+improved-2 to 2.2.159+improved-2)
  • Migration status for jtdx/riscv64 (2.2.159+improved-2 to 2.2.159+improved-2): Will attempt migration (Any information below is purely informational)
• juffed/riscv64 (0.10-89-g3690b60-8.1 to 0.10-89-g3690b60-8.1)
  • Migration status for juffed/riscv64 (0.10-89-g3690b60-8.1 to 0.10-89-g3690b60-8.1): Will attempt migration (Any information below is purely informational)
• juk/riscv64 (4:23.08.2-1 to 4:23.08.2-1)
  • Migration status for juk/riscv64 (4:23.08.2-1 to 4:23.08.2-1): Will attempt migration (Any information below is purely informational)
• jumpnbump/riscv64 (1.61-4 to 1.61-4)
  • Migration status for jumpnbump/riscv64 (1.61-4 to 1.61-4): Will attempt migration (Any information below is purely informational)
• jwm/riscv64 (2.4.3-1 to 2.4.3-1)
  • Migration status for jwm/riscv64 (2.4.3-1 to 2.4.3-1): Will attempt migration (Any information below is purely informational)
• k4dirstat/riscv64 (3.4.3-1 to 3.4.3-1)
  • Migration status for k4dirstat/riscv64 (3.4.3-1 to 3.4.3-1): Will attempt migration (Any information below is purely informational)
• kaccounts-integration/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kaccounts-integration/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kaccounts-providers/riscv64 (4:22.12.3-2 to 4:22.12.3-2)
  • Migration status for kaccounts-providers/riscv64 (4:22.12.3-2 to 4:22.12.3-2): Will attempt migration (Any information below is purely informational)
• kactivities-kf5/riscv64 (5.115.0-3 to 5.115.0-3)
  • Migration status for kactivities-kf5/riscv64 (5.115.0-3 to 5.115.0-3): Will attempt migration (Any information below is purely informational)
• kactivities-stats/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kactivities-stats/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kaddressbook/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kaddressbook/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kaffeine/riscv64 (2.0.18+git20230226.439cd0d-1 to 2.0.18+git20230226.439cd0d-1)
  • Migration status for kaffeine/riscv64 (2.0.18+git20230226.439cd0d-1 to 2.0.18+git20230226.439cd0d-1): Will attempt migration (Any information below is purely informational)
• kalarm/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kalarm/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kalgebra/riscv64 (4:22.12.3-2 to 4:22.12.3-2)
  • Migration status for kalgebra/riscv64 (4:22.12.3-2 to 4:22.12.3-2): Will attempt migration (Any information below is purely informational)
• kalk/riscv64 (23.08.3-1 to 23.08.3-1)
  • Migration status for kalk/riscv64 (23.08.3-1 to 23.08.3-1): Will attempt migration (Any information below is purely informational)
• kalzium/riscv64 (4:23.08.5-1 to 4:23.08.5-1)
  • Migration status for kalzium/riscv64 (4:23.08.5-1 to 4:23.08.5-1): Will attempt migration (Any information below is purely informational)
• kamera/riscv64 (4:23.08.2-1 to 4:23.08.2-1)
  • Migration status for kamera/riscv64 (4:23.08.2-1 to 4:23.08.2-1): Will attempt migration (Any information below is purely informational)
• kamoso/riscv64 (23.08.2-1 to 23.08.2-1)
  • Migration status for kamoso/riscv64 (23.08.2-1 to 23.08.2-1): Will attempt migration (Any information below is purely informational)
• kanagram/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kanagram/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kanatest/riscv64 (0.4.10~git20200611.860e790-1 to 0.4.10~git20200611.860e790-1)
  • Migration status for kanatest/riscv64 (0.4.10~git20200611.860e790-1 to 0.4.10~git20200611.860e790-1): Will attempt migration (Any information below is purely informational)
• kapman/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kapman/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kapptemplate/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kapptemplate/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• karchive/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for karchive/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• katarakt/riscv64 (0.2-4 to 0.2-4)
  • Migration status for katarakt/riscv64 (0.2-4 to 0.2-4): Will attempt migration (Any information below is purely informational)
• kate/riscv64 (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for kate/riscv64 (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• katomic/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for katomic/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kauth/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kauth/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kbackup/riscv64 (23.08.2-1 to 23.08.2-1)
  • Migration status for kbackup/riscv64 (23.08.2-1 to 23.08.2-1): Will attempt migration (Any information below is purely informational)
• kbibtex/riscv64 (0.10.0-2 to 0.10.0-2)
  • Migration status for kbibtex/riscv64 (0.10.0-2 to 0.10.0-2): Will attempt migration (Any information below is purely informational)
• kblackbox/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kblackbox/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kblocks/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kblocks/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kbookmarks/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kbookmarks/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kbounce/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kbounce/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kbreakout/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kbreakout/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kbruch/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kbruch/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kcachegrind/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kcachegrind/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kcalc/riscv64 (4:23.08.2-1 to 4:23.08.2-1)
  • Migration status for kcalc/riscv64 (4:23.08.2-1 to 4:23.08.2-1): Will attempt migration (Any information below is purely informational)
• kcalcore/riscv64 (5:5.115.0-2 to 5:5.115.0-2)
  • Migration status for kcalcore/riscv64 (5:5.115.0-2 to 5:5.115.0-2): Will attempt migration (Any information below is purely informational)
• kcalutils/riscv64 (4:22.12.3-2 to 4:22.12.3-2)
  • Migration status for kcalutils/riscv64 (4:22.12.3-2 to 4:22.12.3-2): Will attempt migration (Any information below is purely informational)
• kcharselect/riscv64 (4:23.08.2-1 to 4:23.08.2-1)
  • Migration status for kcharselect/riscv64 (4:23.08.2-1 to 4:23.08.2-1): Will attempt migration (Any information below is purely informational)
• kcheckers/riscv64 (0.8.1-6 to 0.8.1-6)
  • Migration status for kcheckers/riscv64 (0.8.1-6 to 0.8.1-6): Will attempt migration (Any information below is purely informational)
• kclock/riscv64 (23.08.0-1 to 23.08.0-1)
  • Migration status for kclock/riscv64 (23.08.0-1 to 23.08.0-1): Will attempt migration (Any information below is purely informational)
• kcm-fcitx/riscv64 (0.5.6+git20221120-1 to 0.5.6+git20221120-1)
  • Migration status for kcm-fcitx/riscv64 (0.5.6+git20221120-1 to 0.5.6+git20221120-1): Will attempt migration (Any information below is purely informational)
• kcodecs/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kcodecs/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kcollectd/riscv64 (0.12.1-1 to 0.12.1-1)
  • Migration status for kcollectd/riscv64 (0.12.1-1 to 0.12.1-1): Will attempt migration (Any information below is purely informational)
• kcolorchooser/riscv64 (4:23.08.2-1 to 4:23.08.2-1)
  • Migration status for kcolorchooser/riscv64 (4:23.08.2-1 to 4:23.08.2-1): Will attempt migration (Any information below is purely informational)
• kcompletion/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kcompletion/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kconfig-frontends/riscv64 (4.11.0.1+dfsg-6 to 4.11.0.1+dfsg-6)
  • Migration status for kconfig-frontends/riscv64 (4.11.0.1+dfsg-6 to 4.11.0.1+dfsg-6): Will attempt migration (Any information below is purely informational)
• kconfig/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kconfig/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kconfigwidgets/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kconfigwidgets/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kcontacts/riscv64 (5:5.115.0-2 to 5:5.115.0-2)
  • Migration status for kcontacts/riscv64 (5:5.115.0-2 to 5:5.115.0-2): Will attempt migration (Any information below is purely informational)
• kcoreaddons/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kcoreaddons/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kcrash/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kcrash/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kcron/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kcron/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kdav/riscv64 (1:5.115.0-2 to 1:5.115.0-2)
  • Migration status for kdav/riscv64 (1:5.115.0-2 to 1:5.115.0-2): Will attempt migration (Any information below is purely informational)
• kdb/riscv64 (3.2.0-7 to 3.2.0-7)
  • Migration status for kdb/riscv64 (3.2.0-7 to 3.2.0-7): Will attempt migration (Any information below is purely informational)
• kdbusaddons/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kdbusaddons/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kde-dev-utils/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kde-dev-utils/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kde-inotify-survey/riscv64 (23.08.5-1 to 23.08.5-1)
  • Migration status for kde-inotify-survey/riscv64 (23.08.5-1 to 23.08.5-1): Will attempt migration (Any information below is purely informational)
• kdebugsettings/riscv64 (23.08.2-1 to 23.08.2-1)
  • Migration status for kdebugsettings/riscv64 (23.08.2-1 to 23.08.2-1): Will attempt migration (Any information below is purely informational)
• kdeclarative/riscv64 (5.115.0-3 to 5.115.0-3)
  • Migration status for kdeclarative/riscv64 (5.115.0-3 to 5.115.0-3): Will attempt migration (Any information below is purely informational)
• kded/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kded/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kdegraphics-thumbnailers/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kdegraphics-thumbnailers/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kdelibs4support/riscv64 (5.115.0-3 to 5.115.0-3)
  • Migration status for kdelibs4support/riscv64 (5.115.0-3 to 5.115.0-3): Will attempt migration (Any information below is purely informational)
• kdenetwork-filesharing/riscv64 (4:23.08.3-1 to 4:23.08.3-1)
  • Migration status for kdenetwork-filesharing/riscv64 (4:23.08.3-1 to 4:23.08.3-1): Will attempt migration (Any information below is purely informational)
• kdepim-runtime/riscv64 (4:22.12.3-2 to 4:22.12.3-2)
  • Migration status for kdepim-runtime/riscv64 (4:22.12.3-2 to 4:22.12.3-2): Will attempt migration (Any information below is purely informational)
• kdesdk-kioslaves/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kdesdk-kioslaves/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kdesdk-thumbnailers/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kdesdk-thumbnailers/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kdesignerplugin/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kdesignerplugin/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kdesu/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kdesu/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kdesvn/riscv64 (2.1.0-3 to 2.1.0-3)
  • Migration status for kdesvn/riscv64 (2.1.0-3 to 2.1.0-3): Will attempt migration (Any information below is purely informational)
• kdevelop-pg-qt/riscv64 (2.2.2-1 to 2.2.2-1)
  • Migration status for kdevelop-pg-qt/riscv64 (2.2.2-1 to 2.2.2-1): Will attempt migration (Any information below is purely informational)
• kdewebkit/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kdewebkit/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kdf/riscv64 (4:23.08.3-1 to 4:23.08.3-1)
  • Migration status for kdf/riscv64 (4:23.08.3-1 to 4:23.08.3-1): Will attempt migration (Any information below is purely informational)
• kdiagram/riscv64 (2.8.0-1 to 2.8.0-1)
  • Migration status for kdiagram/riscv64 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
• kdialog/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kdialog/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kdiamond/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kdiamond/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kdnssd-kf5/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kdnssd-kf5/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kdocker/riscv64 (5.4-1 to 5.4-1)
  • Migration status for kdocker/riscv64 (5.4-1 to 5.4-1): Will attempt migration (Any information below is purely informational)
• kdoctools/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kdoctools/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kdsingleapplication/riscv64 (1.0.0-2 to 1.0.0-2)
  • Migration status for kdsingleapplication/riscv64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• kdsoap/riscv64 (1.9.1+dfsg-5 to 1.9.1+dfsg-5)
  • Migration status for kdsoap/riscv64 (1.9.1+dfsg-5 to 1.9.1+dfsg-5): Will attempt migration (Any information below is purely informational)
• keditbookmarks/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for keditbookmarks/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kemoticons/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kemoticons/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• keurocalc/riscv64 (1.3.0-4 to 1.3.0-4)
  • Migration status for keurocalc/riscv64 (1.3.0-4 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
• kexi/riscv64 (1:3.2.0-4 to 1:3.2.0-4)
  • Migration status for kexi/riscv64 (1:3.2.0-4 to 1:3.2.0-4): Will attempt migration (Any information below is purely informational)
• keybinder-3.0/riscv64 (0.3.2-1.1 to 0.3.2-1.1)
  • Migration status for keybinder-3.0/riscv64 (0.3.2-1.1 to 0.3.2-1.1): Will attempt migration (Any information below is purely informational)
• kf6-kfilemetadata/amd64 (6.5.0-2 to 6.5.0-2)
  • Migration status for kf6-kfilemetadata/amd64 (6.5.0-2 to 6.5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kf6-kfilemetadata/amd64 exiv2
• kf6-kfilemetadata/arm64 (6.5.0-2 to 6.5.0-2)
  • Migration status for kf6-kfilemetadata/arm64 (6.5.0-2 to 6.5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kf6-kfilemetadata/arm64 exiv2
• kf6-kfilemetadata/armel (6.5.0-2 to 6.5.0-2)
  • Migration status for kf6-kfilemetadata/armel (6.5.0-2 to 6.5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kf6-kfilemetadata/armel exiv2
• kf6-kfilemetadata/armhf (6.5.0-2 to 6.5.0-2)
  • Migration status for kf6-kfilemetadata/armhf (6.5.0-2 to 6.5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kf6-kfilemetadata/armhf exiv2
• kf6-kfilemetadata/i386 (6.5.0-2 to 6.5.0-2)
  • Migration status for kf6-kfilemetadata/i386 (6.5.0-2 to 6.5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kf6-kfilemetadata/i386 exiv2
• kf6-kfilemetadata/mips64el (6.5.0-2 to 6.5.0-2)
  • Migration status for kf6-kfilemetadata/mips64el (6.5.0-2 to 6.5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kf6-kfilemetadata/mips64el exiv2
• kf6-kfilemetadata/ppc64el (6.5.0-2 to 6.5.0-2)
  • Migration status for kf6-kfilemetadata/ppc64el (6.5.0-2 to 6.5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kf6-kfilemetadata/ppc64el exiv2
• kf6-kfilemetadata/s390x (6.5.0-2 to 6.5.0-2)
  • Migration status for kf6-kfilemetadata/s390x (6.5.0-2 to 6.5.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kf6-kfilemetadata/s390x exiv2
• kfilemetadata-kf5/amd64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kfilemetadata-kf5/amd64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kfilemetadata-kf5/amd64 exiv2
• kfilemetadata-kf5/arm64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kfilemetadata-kf5/arm64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kfilemetadata-kf5/arm64 exiv2
• kfilemetadata-kf5/armel (5.115.0-2 to 5.115.0-2)
  • Migration status for kfilemetadata-kf5/armel (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kfilemetadata-kf5/armel exiv2
• kfilemetadata-kf5/armhf (5.115.0-2 to 5.115.0-2)
  • Migration status for kfilemetadata-kf5/armhf (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kfilemetadata-kf5/armhf exiv2
• kfilemetadata-kf5/i386 (5.115.0-2 to 5.115.0-2)
  • Migration status for kfilemetadata-kf5/i386 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kfilemetadata-kf5/i386 exiv2
• kfilemetadata-kf5/mips64el (5.115.0-2 to 5.115.0-2)
  • Migration status for kfilemetadata-kf5/mips64el (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kfilemetadata-kf5/mips64el exiv2
• kfilemetadata-kf5/ppc64el (5.115.0-2 to 5.115.0-2)
  • Migration status for kfilemetadata-kf5/ppc64el (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kfilemetadata-kf5/ppc64el exiv2
• kfilemetadata-kf5/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kfilemetadata-kf5/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kfilemetadata-kf5/s390x (5.115.0-2 to 5.115.0-2)
  • Migration status for kfilemetadata-kf5/s390x (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
    • Depends: kfilemetadata-kf5/s390x exiv2
• kfind/riscv64 (4:23.08.3-1 to 4:23.08.3-1)
  • Migration status for kfind/riscv64 (4:23.08.3-1 to 4:23.08.3-1): Will attempt migration (Any information below is purely informational)
• kfloppy/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kfloppy/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kfourinline/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kfourinline/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kgames/riscv64 (2.3-1 to 2.3-1)
  • Migration status for kgames/riscv64 (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• kgeography/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kgeography/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kgeotag/riscv64 (1.5.0-1 to 1.5.0-1)
  • Migration status for kgeotag/riscv64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
• kgoldrunner/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kgoldrunner/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• khangman/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for khangman/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• khelpcenter/riscv64 (4:23.08.3-1 to 4:23.08.3-1)
  • Migration status for khelpcenter/riscv64 (4:23.08.3-1 to 4:23.08.3-1): Will attempt migration (Any information below is purely informational)
• kholidays/riscv64 (1:5.115.0-2 to 1:5.115.0-2)
  • Migration status for kholidays/riscv64 (1:5.115.0-2 to 1:5.115.0-2): Will attempt migration (Any information below is purely informational)
• ki18n/riscv64 (5.115.1-2 to 5.115.1-2)
  • Migration status for ki18n/riscv64 (5.115.1-2 to 5.115.1-2): Will attempt migration (Any information below is purely informational)
• kickoff/riscv64 (0.1.1 to 0.1.1)
  • Migration status for kickoff/riscv64 (0.1.1 to 0.1.1): Will attempt migration (Any information below is purely informational)
• kiconthemes/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kiconthemes/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kid3/riscv64 (3.9.5-1 to 3.9.5-1)
  • Migration status for kid3/riscv64 (3.9.5-1 to 3.9.5-1): Will attempt migration (Any information below is purely informational)
• kidentitymanagement/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kidentitymanagement/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kidletime/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kidletime/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kig/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kig/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kigo/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kigo/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kildclient/riscv64 (3.2.1-1 to 3.2.1-1)
  • Migration status for kildclient/riscv64 (3.2.1-1 to 3.2.1-1): Will attempt migration (Any information below is purely informational)
• kile/riscv64 (4:2.9.93-2 to 4:2.9.93-2)
  • Migration status for kile/riscv64 (4:2.9.93-2 to 4:2.9.93-2): Will attempt migration (Any information below is purely informational)
• killbots/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for killbots/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kimageformats/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kimageformats/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kimap/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kimap/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kinit/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kinit/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kio-admin/riscv64 (1.0.0-1 to 1.0.0-1)
  • Migration status for kio-admin/riscv64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• kio-fuse/riscv64 (5.0.1-1 to 5.0.1-1)
  • Migration status for kio-fuse/riscv64 (5.0.1-1 to 5.0.1-1): Will attempt migration (Any information below is purely informational)
• kio-gopher/riscv64 (0.1.99-3 to 0.1.99-3)
  • Migration status for kio-gopher/riscv64 (0.1.99-3 to 0.1.99-3): Will attempt migration (Any information below is purely informational)
• kipi-plugins/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kipi-plugins/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kirigami-gallery/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kirigami-gallery/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kirigami2/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kirigami2/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kiriki/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kiriki/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kitemmodels/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kitemmodels/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kitemviews/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kitemviews/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kiten/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kiten/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kiwix-tools/riscv64 (3.5.0-2 to 3.5.0-2)
  • Migration status for kiwix-tools/riscv64 (3.5.0-2 to 3.5.0-2): Will attempt migration (Any information below is purely informational)
• kjobwidgets/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kjobwidgets/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kjots/riscv64 (4:5.1.0-5 to 4:5.1.0-5)
  • Migration status for kjots/riscv64 (4:5.1.0-5 to 4:5.1.0-5): Will attempt migration (Any information below is purely informational)
• kjumpingcube/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kjumpingcube/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• klavaro/riscv64 (3.11-1 to 3.11-1)
  • Migration status for klavaro/riscv64 (3.11-1 to 3.11-1): Will attempt migration (Any information below is purely informational)
• klettres/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for klettres/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• klickety/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for klickety/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• klines/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for klines/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• klog/riscv64 (2.3.4-1 to 2.3.4-1)
  • Migration status for klog/riscv64 (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• kmag/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kmag/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kmahjongg/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kmahjongg/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kmailtransport/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kmailtransport/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kmbox/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kmbox/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kmediaplayer/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kmediaplayer/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kmetronome/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for kmetronome/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• kmime/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kmime/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kmines/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kmines/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kmix/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kmix/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kmousetool/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kmousetool/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kmouth/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kmouth/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kmplayer/riscv64 (1:0.12.0b+de96d9e-1 to 1:0.12.0b+de96d9e-1)
  • Migration status for kmplayer/riscv64 (1:0.12.0b+de96d9e-1 to 1:0.12.0b+de96d9e-1): Will attempt migration (Any information below is purely informational)
• kmplot/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kmplot/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kmymoney/riscv64 (5.1.3-1 to 5.1.3-1)
  • Migration status for kmymoney/riscv64 (5.1.3-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
• knavalbattle/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for knavalbattle/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• knetwalk/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for knetwalk/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• knewstuff/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for knewstuff/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• knights/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for knights/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• knotes/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for knotes/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• knotifications/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for knotifications/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• knotifyconfig/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for knotifyconfig/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• knowthelist/riscv64 (2.3.1-1 to 2.3.1-1)
  • Migration status for knowthelist/riscv64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• koko/amd64 (23.08.5+ds.1-2 to 23.08.5+ds.1-2)
  • Migration status for koko/amd64 (23.08.5+ds.1-2 to 23.08.5+ds.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: koko/amd64 exiv2
• koko/arm64 (23.08.5+ds.1-2 to 23.08.5+ds.1-2)
  • Migration status for koko/arm64 (23.08.5+ds.1-2 to 23.08.5+ds.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: koko/arm64 exiv2
• koko/armel (23.08.5+ds.1-2 to 23.08.5+ds.1-2)
  • Migration status for koko/armel (23.08.5+ds.1-2 to 23.08.5+ds.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: koko/armel exiv2
• koko/armhf (23.08.5+ds.1-2 to 23.08.5+ds.1-2)
  • Migration status for koko/armhf (23.08.5+ds.1-2 to 23.08.5+ds.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: koko/armhf exiv2
• koko/i386 (23.08.5+ds.1-2 to 23.08.5+ds.1-2)
  • Migration status for koko/i386 (23.08.5+ds.1-2 to 23.08.5+ds.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: koko/i386 exiv2
• koko/mips64el (23.08.5+ds.1-2 to 23.08.5+ds.1-2)
  • Migration status for koko/mips64el (23.08.5+ds.1-2 to 23.08.5+ds.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: koko/mips64el exiv2
• koko/ppc64el (23.08.5+ds.1-2 to 23.08.5+ds.1-2)
  • Migration status for koko/ppc64el (23.08.5+ds.1-2 to 23.08.5+ds.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: koko/ppc64el exiv2
• koko/riscv64 (23.08.5+ds.1-2 to 23.08.5+ds.1-2)
  • Migration status for koko/riscv64 (23.08.5+ds.1-2 to 23.08.5+ds.1-2): Will attempt migration (Any information below is purely informational)
• koko/s390x (23.08.5+ds.1-2 to 23.08.5+ds.1-2)
  • Migration status for koko/s390x (23.08.5+ds.1-2 to 23.08.5+ds.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: koko/s390x exiv2
• kolf/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kolf/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kollision/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kollision/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kolourpaint/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kolourpaint/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kompare/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kompare/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• konclude/riscv64 (0.7.0+1138+git20220514~dfsg-1 to 0.7.0+1138+git20220514~dfsg-1)
  • Migration status for konclude/riscv64 (0.7.0+1138+git20220514~dfsg-1 to 0.7.0+1138+git20220514~dfsg-1): Will attempt migration (Any information below is purely informational)
• kongress/riscv64 (1.0.1-2 to 1.0.1-2)
  • Migration status for kongress/riscv64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• konqueror/riscv64 (4:22.12.3-2 to 4:22.12.3-2)
  • Migration status for konqueror/riscv64 (4:22.12.3-2 to 4:22.12.3-2): Will attempt migration (Any information below is purely informational)
• konquest/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for konquest/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• konsole/riscv64 (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for konsole/riscv64 (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• kontactinterface/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kontactinterface/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kontrast/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kontrast/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• konversation/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for konversation/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kookbook/riscv64 (0.2.1-3 to 0.2.1-3)
  • Migration status for kookbook/riscv64 (0.2.1-3 to 0.2.1-3): Will attempt migration (Any information below is purely informational)
• kopeninghours/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kopeninghours/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• korganizer/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for korganizer/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kosmindoormap/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kosmindoormap/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kotlin/amd64 (1.3.31+ds1-1 to 1.3.31+ds1-1)
  • Migration status for kotlin/amd64 (1.3.31+ds1-1 to 1.3.31+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kotlin/arm64 (1.3.31+ds1-1 to 1.3.31+ds1-1)
  • Migration status for kotlin/arm64 (1.3.31+ds1-1 to 1.3.31+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kotlin/armel (1.3.31+ds1-1 to 1.3.31+ds1-1)
  • Migration status for kotlin/armel (1.3.31+ds1-1 to 1.3.31+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kotlin/armhf (1.3.31+ds1-1 to 1.3.31+ds1-1)
  • Migration status for kotlin/armhf (1.3.31+ds1-1 to 1.3.31+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kotlin/i386 (1.3.31+ds1-1 to 1.3.31+ds1-1)
  • Migration status for kotlin/i386 (1.3.31+ds1-1 to 1.3.31+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kotlin/mips64el (1.3.31+ds1-1 to 1.3.31+ds1-1)
  • Migration status for kotlin/mips64el (1.3.31+ds1-1 to 1.3.31+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kotlin/ppc64el (1.3.31+ds1-1 to 1.3.31+ds1-1)
  • Migration status for kotlin/ppc64el (1.3.31+ds1-1 to 1.3.31+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kotlin/riscv64 (1.3.31+ds1-1 to 1.3.31+ds1-1)
  • Migration status for kotlin/riscv64 (1.3.31+ds1-1 to 1.3.31+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kotlin/s390x (1.3.31+ds1-1 to 1.3.31+ds1-1)
  • Migration status for kotlin/s390x (1.3.31+ds1-1 to 1.3.31+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kpackage/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kpackage/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kparts/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kparts/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kpat/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kpat/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kpeople/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kpeople/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kpeoplevcard/riscv64 (0.1-3 to 0.1-3)
  • Migration status for kpeoplevcard/riscv64 (0.1-3 to 0.1-3): Will attempt migration (Any information below is purely informational)
• kphotoalbum/amd64 (5.12.0-1 to 5.12.0-1)
  • Migration status for kphotoalbum/amd64 (5.12.0-1 to 5.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: kphotoalbum/amd64 exiv2
• kphotoalbum/arm64 (5.12.0-1 to 5.12.0-1)
  • Migration status for kphotoalbum/arm64 (5.12.0-1 to 5.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: kphotoalbum/arm64 exiv2
• kphotoalbum/armel (5.12.0-1 to 5.12.0-1)
  • Migration status for kphotoalbum/armel (5.12.0-1 to 5.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: kphotoalbum/armel exiv2
• kphotoalbum/armhf (5.12.0-1 to 5.12.0-1)
  • Migration status for kphotoalbum/armhf (5.12.0-1 to 5.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: kphotoalbum/armhf exiv2
• kphotoalbum/i386 (5.12.0-1 to 5.12.0-1)
  • Migration status for kphotoalbum/i386 (5.12.0-1 to 5.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: kphotoalbum/i386 exiv2
• kphotoalbum/mips64el (5.12.0-1 to 5.12.0-1)
  • Migration status for kphotoalbum/mips64el (5.12.0-1 to 5.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: kphotoalbum/mips64el exiv2
• kphotoalbum/ppc64el (5.12.0-1 to 5.12.0-1)
  • Migration status for kphotoalbum/ppc64el (5.12.0-1 to 5.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: kphotoalbum/ppc64el exiv2
• kphotoalbum/riscv64 (5.12.0-1 to 5.12.0-1)
  • Migration status for kphotoalbum/riscv64 (5.12.0-1 to 5.12.0-1): Will attempt migration (Any information below is purely informational)
• kphotoalbum/s390x (5.12.0-1 to 5.12.0-1)
  • Migration status for kphotoalbum/s390x (5.12.0-1 to 5.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: kphotoalbum/s390x exiv2
• kpimtextedit/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kpimtextedit/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kpkpass/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kpkpass/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kplotting/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kplotting/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kpmcore/riscv64 (23.08.3-1 to 23.08.3-1)
  • Migration status for kpmcore/riscv64 (23.08.3-1 to 23.08.3-1): Will attempt migration (Any information below is purely informational)
• kproperty/riscv64 (3.2.0-2 to 3.2.0-2)
  • Migration status for kproperty/riscv64 (3.2.0-2 to 3.2.0-2): Will attempt migration (Any information below is purely informational)
• kpty/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kpty/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kpublictransport/riscv64 (23.04.3-1 to 23.04.3-1)
  • Migration status for kpublictransport/riscv64 (23.04.3-1 to 23.04.3-1): Will attempt migration (Any information below is purely informational)
• kqtquickcharts/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kqtquickcharts/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kquickcharts/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kquickcharts/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kquickimageeditor/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for kquickimageeditor/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• krb5-auth-dialog/riscv64 (43.0-1 to 43.0-1)
  • Migration status for krb5-auth-dialog/riscv64 (43.0-1 to 43.0-1): Will attempt migration (Any information below is purely informational)
• krdc/riscv64 (4:23.08.3-1 to 4:23.08.3-1)
  • Migration status for krdc/riscv64 (4:23.08.3-1 to 4:23.08.3-1): Will attempt migration (Any information below is purely informational)
• krename/amd64 (5.0.2-2 to 5.0.2-2)
  • Migration status for krename/amd64 (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krename/amd64 exiv2
• krename/arm64 (5.0.2-2 to 5.0.2-2)
  • Migration status for krename/arm64 (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krename/arm64 exiv2
• krename/armel (5.0.2-2 to 5.0.2-2)
  • Migration status for krename/armel (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krename/armel exiv2
• krename/armhf (5.0.2-2 to 5.0.2-2)
  • Migration status for krename/armhf (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krename/armhf exiv2
• krename/i386 (5.0.2-2 to 5.0.2-2)
  • Migration status for krename/i386 (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krename/i386 exiv2
• krename/mips64el (5.0.2-2 to 5.0.2-2)
  • Migration status for krename/mips64el (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krename/mips64el exiv2
• krename/ppc64el (5.0.2-2 to 5.0.2-2)
  • Migration status for krename/ppc64el (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krename/ppc64el exiv2
• krename/riscv64 (5.0.2-2 to 5.0.2-2)
  • Migration status for krename/riscv64 (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
• krename/s390x (5.0.2-2 to 5.0.2-2)
  • Migration status for krename/s390x (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: krename/s390x exiv2
• kreport/riscv64 (3.2.0-3 to 3.2.0-3)
  • Migration status for kreport/riscv64 (3.2.0-3 to 3.2.0-3): Will attempt migration (Any information below is purely informational)
• krfb/riscv64 (4:22.12.3-2 to 4:22.12.3-2)
  • Migration status for krfb/riscv64 (4:22.12.3-2 to 4:22.12.3-2): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• krita/amd64 (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1)
  • Migration status for krita/amd64 (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: krita/amd64 exiv2
• krita/arm64 (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1)
  • Migration status for krita/arm64 (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: krita/arm64 exiv2
• krita/armel (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1)
  • Migration status for krita/armel (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: krita/armel exiv2
• krita/armhf (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1)
  • Migration status for krita/armhf (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: krita/armhf exiv2
• krita/i386 (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1)
  • Migration status for krita/i386 (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: krita/i386 exiv2
• krita/mips64el (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1)
  • Migration status for krita/mips64el (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: krita/mips64el exiv2
• krita/ppc64el (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1)
  • Migration status for krita/ppc64el (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: krita/ppc64el exiv2
• krita/s390x (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1)
  • Migration status for krita/s390x (1:5.2.3+dfsg-1 to 1:5.2.3+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: krita/s390x exiv2
• kronometer/riscv64 (2.3.0-1 to 2.3.0-1)
  • Migration status for kronometer/riscv64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• kross-interpreters/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kross-interpreters/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kross/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kross/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kruler/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kruler/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• krusader/riscv64 (2:2.8.1-1 to 2:2.8.1-1)
  • Migration status for krusader/riscv64 (2:2.8.1-1 to 2:2.8.1-1): Will attempt migration (Any information below is purely informational)
• ksanecore/riscv64 (23.08.1-2 to 23.08.1-2)
  • Migration status for ksanecore/riscv64 (23.08.1-2 to 23.08.1-2): Will attempt migration (Any information below is purely informational)
• kservice/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kservice/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kshisen/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kshisen/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kshutdown/riscv64 (5.2-2 to 5.2-2)
  • Migration status for kshutdown/riscv64 (5.2-2 to 5.2-2): Will attempt migration (Any information below is purely informational)
• ksirk/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for ksirk/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• ksmtp/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ksmtp/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• ksnakeduel/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for ksnakeduel/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kspaceduel/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kspaceduel/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• ksquares/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for ksquares/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kst/riscv64 (2.0.8-6 to 2.0.8-6)
  • Migration status for kst/riscv64 (2.0.8-6 to 2.0.8-6): Will attempt migration (Any information below is purely informational)
• kstars/riscv64 (5:3.6.2-2 to 5:3.6.2-2)
  • Migration status for kstars/riscv64 (5:3.6.2-2 to 5:3.6.2-2): Will attempt migration (Any information below is purely informational)
• ksudoku/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for ksudoku/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• ksyntax-highlighting/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for ksyntax-highlighting/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• ksystemlog/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for ksystemlog/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kteatime/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kteatime/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktechlab/riscv64 (0.51.0-2 to 0.51.0-2)
  • Migration status for ktechlab/riscv64 (0.51.0-2 to 0.51.0-2): Will attempt migration (Any information below is purely informational)
• ktexteditor/riscv64 (5.115.0-3 to 5.115.0-3)
  • Migration status for ktexteditor/riscv64 (5.115.0-3 to 5.115.0-3): Will attempt migration (Any information below is purely informational)
• ktextwidgets/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for ktextwidgets/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• ktikz/riscv64 (0.13.2+ds1-1 to 0.13.2+ds1-1)
  • Migration status for ktikz/riscv64 (0.13.2+ds1-1 to 0.13.2+ds1-1): Will attempt migration (Any information below is purely informational)
• ktimer/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for ktimer/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktimetracker/riscv64 (4:5.0.1-3 to 4:5.0.1-3)
  • Migration status for ktimetracker/riscv64 (4:5.0.1-3 to 4:5.0.1-3): Will attempt migration (Any information below is purely informational)
• ktnef/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for ktnef/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktorrent/riscv64 (22.12.3-2 to 22.12.3-2)
  • Migration status for ktorrent/riscv64 (22.12.3-2 to 22.12.3-2): Will attempt migration (Any information below is purely informational)
• ktouch/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for ktouch/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktrip/riscv64 (23.01.0-1 to 23.01.0-1)
  • Migration status for ktrip/riscv64 (23.01.0-1 to 23.01.0-1): Will attempt migration (Any information below is purely informational)
• ktuberling/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for ktuberling/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kturtle/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kturtle/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kubrick/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kubrick/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kunitconversion/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kunitconversion/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kup-backup/riscv64 (0.9.1-1 to 0.9.1-1)
  • Migration status for kup-backup/riscv64 (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• kwalletcli/riscv64 (3.03-1 to 3.03-1)
  • Migration status for kwalletcli/riscv64 (3.03-1 to 3.03-1): Will attempt migration (Any information below is purely informational)
• kwalletmanager/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kwalletmanager/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kwave/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for kwave/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• kwidgetsaddons/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kwidgetsaddons/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kwindowsystem/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kwindowsystem/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kwordquiz/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kwordquiz/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kworkflow/riscv64 (20191112-1.2 to 20191112-1.2)
  • Migration status for kworkflow/riscv64 (20191112-1.2 to 20191112-1.2): Will attempt migration (Any information below is purely informational)
• kxmlgui/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kxmlgui/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kxmlrpcclient/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kxmlrpcclient/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• kxstitch/riscv64 (2.2.0-3 to 2.2.0-3)
  • Migration status for kxstitch/riscv64 (2.2.0-3 to 2.2.0-3): Will attempt migration (Any information below is purely informational)
• kylin-scanner/riscv64 (1.0.0-1.1 to 1.0.0-1.1)
  • Migration status for kylin-scanner/riscv64 (1.0.0-1.1 to 1.0.0-1.1): Will attempt migration (Any information below is purely informational)
• kylin-video/riscv64 (3.1.3-5 to 3.1.3-5)
  • Migration status for kylin-video/riscv64 (3.1.3-5 to 3.1.3-5): Will attempt migration (Any information below is purely informational)
• l3afpad/riscv64 (0.8.18.1.11-4 to 0.8.18.1.11-4)
  • Migration status for l3afpad/riscv64 (0.8.18.1.11-4 to 0.8.18.1.11-4): Will attempt migration (Any information below is purely informational)
• laby/riscv64 (0.7.0-2 to 0.7.0-2)
  • Migration status for laby/riscv64 (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
• lam/riscv64 (7.1.4-7.2 to 7.1.4-7.2)
  • Migration status for lam/riscv64 (7.1.4-7.2 to 7.1.4-7.2): Will attempt migration (Any information below is purely informational)
• lamarc/riscv64 (2.1.10.1+dfsg-7 to 2.1.10.1+dfsg-7)
  • Migration status for lamarc/riscv64 (2.1.10.1+dfsg-7 to 2.1.10.1+dfsg-7): Will attempt migration (Any information below is purely informational)
• latex2rtf/riscv64 (2.3.18a-5 to 2.3.18a-5)
  • Migration status for latex2rtf/riscv64 (2.3.18a-5 to 2.3.18a-5): Will attempt migration (Any information below is purely informational)
• latte-dock/riscv64 (0.10.9-1 to 0.10.9-1)
  • Migration status for latte-dock/riscv64 (0.10.9-1 to 0.10.9-1): Will attempt migration (Any information below is purely informational)
• ldap2dns/riscv64 (0.3.1-6 to 0.3.1-6)
  • Migration status for ldap2dns/riscv64 (0.3.1-6 to 0.3.1-6): Will attempt migration (Any information below is purely informational)
• ldap2zone/riscv64 (0.2-12 to 0.2-12)
  • Migration status for ldap2zone/riscv64 (0.2-12 to 0.2-12): Will attempt migration (Any information below is purely informational)
• leela-zero/riscv64 (0.17-1 to 0.17-1)
  • Migration status for leela-zero/riscv64 (0.17-1 to 0.17-1): Will attempt migration (Any information below is purely informational)
• leocad/riscv64 (21.06-1 to 21.06-1)
  • Migration status for leocad/riscv64 (21.06-1 to 21.06-1): Will attempt migration (Any information below is purely informational)
• lepton-eda/riscv64 (1.9.18-2 to 1.9.18-2)
  • Migration status for lepton-eda/riscv64 (1.9.18-2 to 1.9.18-2): Will attempt migration (Any information below is purely informational)
• libabw/riscv64 (0.1.3-1 to 0.1.3-1)
  • Migration status for libabw/riscv64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• libaccounts-glib/riscv64 (1.27-1 to 1.27-1)
  • Migration status for libaccounts-glib/riscv64 (1.27-1 to 1.27-1): Will attempt migration (Any information below is purely informational)
• libad9361-iio/riscv64 (0.3-2 to 0.3-2)
  • Migration status for libad9361-iio/riscv64 (0.3-2 to 0.3-2): Will attempt migration (Any information below is purely informational)
• libalien-wxwidgets-perl/riscv64 (0.69+dfsg-6 to 0.69+dfsg-6)
  • Migration status for libalien-wxwidgets-perl/riscv64 (0.69+dfsg-6 to 0.69+dfsg-6): Will attempt migration (Any information below is purely informational)
• libam7xxx/riscv64 (0.1.7-1.1 to 0.1.7-1.1)
  • Migration status for libam7xxx/riscv64 (0.1.7-1.1 to 0.1.7-1.1): Will attempt migration (Any information below is purely informational)
• libapache-authenhook-perl/riscv64 (2.00-04+pristine-8 to 2.00-04+pristine-8)
  • Migration status for libapache-authenhook-perl/riscv64 (2.00-04+pristine-8 to 2.00-04+pristine-8): Will attempt migration (Any information below is purely informational)
• libapache-mod-evasive/riscv64 (1.10.1-6 to 1.10.1-6)
  • Migration status for libapache-mod-evasive/riscv64 (1.10.1-6 to 1.10.1-6): Will attempt migration (Any information below is purely informational)
• libapache-mod-jk/riscv64 (1:1.2.49-1 to 1:1.2.49-1)
  • Migration status for libapache-mod-jk/riscv64 (1:1.2.49-1 to 1:1.2.49-1): Will attempt migration (Any information below is purely informational)
• libapache-mod-musicindex/riscv64 (1.4.1-3.1 to 1.4.1-3.1)
  • Migration status for libapache-mod-musicindex/riscv64 (1.4.1-3.1 to 1.4.1-3.1): Will attempt migration (Any information below is purely informational)
• libapache-mod-removeip/riscv64 (1.0b-5.4 to 1.0b-5.4)
  • Migration status for libapache-mod-removeip/riscv64 (1.0b-5.4 to 1.0b-5.4): Will attempt migration (Any information below is purely informational)
• libapache-ssllookup-perl/riscv64 (2.00-04-4 to 2.00-04-4)
  • Migration status for libapache-ssllookup-perl/riscv64 (2.00-04-4 to 2.00-04-4): Will attempt migration (Any information below is purely informational)
• libapache2-mod-auth-gssapi/riscv64 (1.6.4-3 to 1.6.4-3)
  • Migration status for libapache2-mod-auth-gssapi/riscv64 (1.6.4-3 to 1.6.4-3): Will attempt migration (Any information below is purely informational)
• libapache2-mod-auth-plain/riscv64 (2.0.53 to 2.0.53)
  • Migration status for libapache2-mod-auth-plain/riscv64 (2.0.53 to 2.0.53): Will attempt migration (Any information below is purely informational)
• libapache2-mod-auth-pubtkt/riscv64 (0.13-1 to 0.13-1)
  • Migration status for libapache2-mod-auth-pubtkt/riscv64 (0.13-1 to 0.13-1): Will attempt migration (Any information below is purely informational)
• libapache2-mod-auth-tkt/riscv64 (2.3.99~b1-1 to 2.3.99~b1-1)
  • Migration status for libapache2-mod-auth-tkt/riscv64 (2.3.99~b1-1 to 2.3.99~b1-1): Will attempt migration (Any information below is purely informational)
• libapache2-mod-authn-yolo/riscv64 (1.1-1 to 1.1-1)
  • Migration status for libapache2-mod-authn-yolo/riscv64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
• libapache2-mod-authn-yubikey/riscv64 (1.0-3 to 1.0-3)
  • Migration status for libapache2-mod-authn-yubikey/riscv64 (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• libapache2-mod-authnz-external/riscv64 (3.3.2-2 to 3.3.2-2)
  • Migration status for libapache2-mod-authnz-external/riscv64 (3.3.2-2 to 3.3.2-2): Will attempt migration (Any information below is purely informational)
• libapache2-mod-authnz-pam/riscv64 (1.2.3-1 to 1.2.3-1)
  • Migration status for libapache2-mod-authnz-pam/riscv64 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
• libapache2-mod-authz-unixgroup/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for libapache2-mod-authz-unixgroup/riscv64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• libapache2-mod-bw/riscv64 (0.92-13 to 0.92-13)
  • Migration status for libapache2-mod-bw/riscv64 (0.92-13 to 0.92-13): Will attempt migration (Any information below is purely informational)
• libapache2-mod-fcgid/riscv64 (1:2.3.9-4 to 1:2.3.9-4)
  • Migration status for libapache2-mod-fcgid/riscv64 (1:2.3.9-4 to 1:2.3.9-4): Will attempt migration (Any information below is purely informational)
• libapache2-mod-form/riscv64 (0~svn146-1.1 to 0~svn146-1.1)
  • Migration status for libapache2-mod-form/riscv64 (0~svn146-1.1 to 0~svn146-1.1): Will attempt migration (Any information below is purely informational)
• libapache2-mod-geoip/riscv64 (1.2.10-1 to 1.2.10-1)
  • Migration status for libapache2-mod-geoip/riscv64 (1.2.10-1 to 1.2.10-1): Will attempt migration (Any information below is purely informational)
• libapache2-mod-intercept-form-submit/riscv64 (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for libapache2-mod-intercept-form-submit/riscv64 (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
• libapache2-mod-ldap-userdir/riscv64 (1.1.19-2.1 to 1.1.19-2.1)
  • Migration status for libapache2-mod-ldap-userdir/riscv64 (1.1.19-2.1 to 1.1.19-2.1): Will attempt migration (Any information below is purely informational)
• libapache2-mod-lisp/riscv64 (1.3.1-2 to 1.3.1-2)
  • Migration status for libapache2-mod-lisp/riscv64 (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
• libapache2-mod-lookup-identity/riscv64 (1.0.0-1 to 1.0.0-1)
  • Migration status for libapache2-mod-lookup-identity/riscv64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• libapache2-mod-oauth2/riscv64 (3.3.1-1 to 3.3.1-1)
  • Migration status for libapache2-mod-oauth2/riscv64 (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• libapache2-mod-perl2/riscv64 (2.0.13-1 to 2.0.13-1)
  • Migration status for libapache2-mod-perl2/riscv64 (2.0.13-1 to 2.0.13-1): Will attempt migration (Any information below is purely informational)
• libapache2-mod-python/riscv64 (3.5.0.1-3 to 3.5.0.1-3)
  • Migration status for libapache2-mod-python/riscv64 (3.5.0.1-3 to 3.5.0.1-3): Will attempt migration (Any information below is purely informational)
• libapache2-mod-rpaf/riscv64 (0.6-14 to 0.6-14)
  • Migration status for libapache2-mod-rpaf/riscv64 (0.6-14 to 0.6-14): Will attempt migration (Any information below is purely informational)
• libapache2-mod-sts/riscv64 (3.4.0-2 to 3.4.0-2)
  • Migration status for libapache2-mod-sts/riscv64 (3.4.0-2 to 3.4.0-2): Will attempt migration (Any information below is purely informational)
• libaperture-0/riscv64 (0.1.0+git20221220-1 to 0.1.0+git20221220-1)
  • Migration status for libaperture-0/riscv64 (0.1.0+git20221220-1 to 0.1.0+git20221220-1): Will attempt migration (Any information below is purely informational)
• libapreq2/riscv64 (2.17-5 to 2.17-5)
  • Migration status for libapreq2/riscv64 (2.17-5 to 2.17-5): Will attempt migration (Any information below is purely informational)
• libast/riscv64 (0.7-10 to 0.7-10)
  • Migration status for libast/riscv64 (0.7-10 to 0.7-10): Will attempt migration (Any information below is purely informational)
• libaudclient/riscv64 (3.5~rc2-2 to 3.5~rc2-2)
  • Migration status for libaudclient/riscv64 (3.5~rc2-2 to 3.5~rc2-2): Will attempt migration (Any information below is purely informational)
• libayatana-indicator/riscv64 (0.9.4-1 to 0.9.4-1)
  • Migration status for libayatana-indicator/riscv64 (0.9.4-1 to 0.9.4-1): Will attempt migration (Any information below is purely informational)
• libbluray/riscv64 (1:1.3.4-1 to 1:1.3.4-1)
  • Migration status for libbluray/riscv64 (1:1.3.4-1 to 1:1.3.4-1): Will attempt migration (Any information below is purely informational)
• libcanberra/riscv64 (0.30-17 to 0.30-17)
  • Migration status for libcanberra/riscv64 (0.30-17 to 0.30-17): Will attempt migration (Any information below is purely informational)
• libchamplain/riscv64 (0.12.21-1 to 0.12.21-1)
  • Migration status for libchamplain/riscv64 (0.12.21-1 to 0.12.21-1): Will attempt migration (Any information below is purely informational)
• libchipcard/riscv64 (5.1.6-2 to 5.1.6-2)
  • Migration status for libchipcard/riscv64 (5.1.6-2 to 5.1.6-2): Will attempt migration (Any information below is purely informational)
• libcitadel/riscv64 (917-5 to 917-5)
  • Migration status for libcitadel/riscv64 (917-5 to 917-5): Will attempt migration (Any information below is purely informational)
• libcitygml/riscv64 (2.5.2-1 to 2.5.2-1)
  • Migration status for libcitygml/riscv64 (2.5.2-1 to 2.5.2-1): Will attempt migration (Any information below is purely informational)
• libclang-perl/riscv64 (0.09-6 to 0.09-6)
  • Migration status for libclang-perl/riscv64 (0.09-6 to 0.09-6): Will attempt migration (Any information below is purely informational)
• libcmis/riscv64 (0.6.2-2.1 to 0.6.2-2.1)
  • Migration status for libcmis/riscv64 (0.6.2-2.1 to 0.6.2-2.1): Will attempt migration (Any information below is purely informational)
• libcommuni/riscv64 (3.7.0-2.1 to 3.7.0-2.1)
  • Migration status for libcommuni/riscv64 (3.7.0-2.1 to 3.7.0-2.1): Will attempt migration (Any information below is purely informational)
• libcompizconfig/riscv64 (2:0.8.18-3 to 2:0.8.18-3)
  • Migration status for libcompizconfig/riscv64 (2:0.8.18-3 to 2:0.8.18-3): Will attempt migration (Any information below is purely informational)
• libcomps/riscv64 (0.1.21-1 to 0.1.21-1)
  • Migration status for libcomps/riscv64 (0.1.21-1 to 0.1.21-1): Will attempt migration (Any information below is purely informational)
• libconfig-augeas-perl/riscv64 (1.000-3 to 1.000-3)
  • Migration status for libconfig-augeas-perl/riscv64 (1.000-3 to 1.000-3): Will attempt migration (Any information below is purely informational)
• libcoverart/riscv64 (1.0.0+git20150706-9 to 1.0.0+git20150706-9)
  • Migration status for libcoverart/riscv64 (1.0.0+git20150706-9 to 1.0.0+git20150706-9): Will attempt migration (Any information below is purely informational)
• libcvd/riscv64 (0.0~git20221020150751.30e8cfc+ds1-1 to 0.0~git20221020150751.30e8cfc+ds1-1)
  • Migration status for libcvd/riscv64 (0.0~git20221020150751.30e8cfc+ds1-1 to 0.0~git20221020150751.30e8cfc+ds1-1): Will attempt migration (Any information below is purely informational)
• libdazzle/riscv64 (3.44.0-1 to 3.44.0-1)
  • Migration status for libdazzle/riscv64 (3.44.0-1 to 3.44.0-1): Will attempt migration (Any information below is purely informational)
• libdbusmenu/riscv64 (18.10.20180917~bzr492+repack1-3.1 to 18.10.20180917~bzr492+repack1-3.1)
  • Migration status for libdbusmenu/riscv64 (18.10.20180917~bzr492+repack1-3.1 to 18.10.20180917~bzr492+repack1-3.1): Will attempt migration (Any information below is purely informational)
• libdmapsharing/riscv64 (3.9.13-2 to 3.9.13-2)
  • Migration status for libdmapsharing/riscv64 (3.9.13-2 to 3.9.13-2): Will attempt migration (Any information below is purely informational)
• libdrilbo/riscv64 (0.2.11-2.1 to 0.2.11-2.1)
  • Migration status for libdrilbo/riscv64 (0.2.11-2.1 to 0.2.11-2.1): Will attempt migration (Any information below is purely informational)
• libdrumstick/riscv64 (2.9.0-1.1 to 2.9.0-1.1)
  • Migration status for libdrumstick/riscv64 (2.9.0-1.1 to 2.9.0-1.1): Will attempt migration (Any information below is purely informational)
• libe-book/riscv64 (0.1.3-2 to 0.1.3-2)
  • Migration status for libe-book/riscv64 (0.1.3-2 to 0.1.3-2): Will attempt migration (Any information below is purely informational)
• libebook-tools-perl/riscv64 (0.5.4-1.3 to 0.5.4-1.3)
  • Migration status for libebook-tools-perl/riscv64 (0.5.4-1.3 to 0.5.4-1.3): Will attempt migration (Any information below is purely informational)
• libetonyek/riscv64 (0.1.10-5 to 0.1.10-5)
  • Migration status for libetonyek/riscv64 (0.1.10-5 to 0.1.10-5): Will attempt migration (Any information below is purely informational)
• libexif-gtk/riscv64 (0.5.0-2 to 0.5.0-2)
  • Migration status for libexif-gtk/riscv64 (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• libextractor/amd64 (1:1.13-4 to 1:1.13-4)
  • Migration status for libextractor/amd64 (1:1.13-4 to 1:1.13-4): Will attempt migration (Any information below is purely informational)
    • Depends: libextractor/amd64 exiv2
• libextractor/arm64 (1:1.13-4 to 1:1.13-4)
  • Migration status for libextractor/arm64 (1:1.13-4 to 1:1.13-4): Will attempt migration (Any information below is purely informational)
    • Depends: libextractor/arm64 exiv2
• libextractor/armel (1:1.13-4 to 1:1.13-4)
  • Migration status for libextractor/armel (1:1.13-4 to 1:1.13-4): Will attempt migration (Any information below is purely informational)
    • Depends: libextractor/armel exiv2
• libextractor/armhf (1:1.13-4 to 1:1.13-4)
  • Migration status for libextractor/armhf (1:1.13-4 to 1:1.13-4): Will attempt migration (Any information below is purely informational)
    • Depends: libextractor/armhf exiv2
• libextractor/i386 (1:1.13-4 to 1:1.13-4)
  • Migration status for libextractor/i386 (1:1.13-4 to 1:1.13-4): Will attempt migration (Any information below is purely informational)
    • Depends: libextractor/i386 exiv2
• libextractor/mips64el (1:1.13-4 to 1:1.13-4)
  • Migration status for libextractor/mips64el (1:1.13-4 to 1:1.13-4): Will attempt migration (Any information below is purely informational)
    • Depends: libextractor/mips64el exiv2
• libextractor/ppc64el (1:1.13-4 to 1:1.13-4)
  • Migration status for libextractor/ppc64el (1:1.13-4 to 1:1.13-4): Will attempt migration (Any information below is purely informational)
    • Depends: libextractor/ppc64el exiv2
• libextractor/riscv64 (1:1.13-4 to 1:1.13-4)
  • Migration status for libextractor/riscv64 (1:1.13-4 to 1:1.13-4): Will attempt migration (Any information below is purely informational)
• libextractor/s390x (1:1.13-4 to 1:1.13-4)
  • Migration status for libextractor/s390x (1:1.13-4 to 1:1.13-4): Will attempt migration (Any information below is purely informational)
    • Depends: libextractor/s390x exiv2
• libfizmo/riscv64 (0.7.15-2.1 to 0.7.15-2.1)
  • Migration status for libfizmo/riscv64 (0.7.15-2.1 to 0.7.15-2.1): Will attempt migration (Any information below is purely informational)
• libfm/riscv64 (1.3.2-4.1 to 1.3.2-4.1)
  • Migration status for libfm/riscv64 (1.3.2-4.1 to 1.3.2-4.1): Will attempt migration (Any information below is purely informational)
• libfreenect/riscv64 (1:0.5.3-3.2 to 1:0.5.3-3.2)
  • Migration status for libfreenect/riscv64 (1:0.5.3-3.2 to 1:0.5.3-3.2): Will attempt migration (Any information below is purely informational)
• libg3d/riscv64 (0.0.8-37 to 0.0.8-37)
  • Migration status for libg3d/riscv64 (0.0.8-37 to 0.0.8-37): Will attempt migration (Any information below is purely informational)
• libgdata/riscv64 (0.18.1-7 to 0.18.1-7)
  • Migration status for libgdata/riscv64 (0.18.1-7 to 0.18.1-7): Will attempt migration (Any information below is purely informational)
• libgdf/riscv64 (0.1.3-11.1 to 0.1.3-11.1)
  • Migration status for libgdf/riscv64 (0.1.3-11.1 to 0.1.3-11.1): Will attempt migration (Any information below is purely informational)
• libgedit-amtk/riscv64 (5.8.0-4 to 5.8.0-4)
  • Migration status for libgedit-amtk/riscv64 (5.8.0-4 to 5.8.0-4): Will attempt migration (Any information below is purely informational)
• libgedit-gtksourceview/riscv64 (299.0.4-3 to 299.0.4-3)
  • Migration status for libgedit-gtksourceview/riscv64 (299.0.4-3 to 299.0.4-3): Will attempt migration (Any information below is purely informational)
• libgepub/riscv64 (0.7.1-2 to 0.7.1-2)
  • Migration status for libgepub/riscv64 (0.7.1-2 to 0.7.1-2): Will attempt migration (Any information below is purely informational)
• libgltf/riscv64 (0.1.0-3 to 0.1.0-3)
  • Migration status for libgltf/riscv64 (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• libgnome-games-support/riscv64 (2.0.0-2 to 2.0.0-2)
  • Migration status for libgnome-games-support/riscv64 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• libgnome-games-support1/riscv64 (1.8.2-5 to 1.8.2-5)
  • Migration status for libgnome-games-support1/riscv64 (1.8.2-5 to 1.8.2-5): Will attempt migration (Any information below is purely informational)
• libgnomecanvas/riscv64 (2.30.3-4.1 to 2.30.3-4.1)
  • Migration status for libgnomecanvas/riscv64 (2.30.3-4.1 to 2.30.3-4.1): Will attempt migration (Any information below is purely informational)
• libgnomekbd/riscv64 (3.28.1-1 to 3.28.1-1)
  • Migration status for libgnomekbd/riscv64 (3.28.1-1 to 3.28.1-1): Will attempt migration (Any information below is purely informational)
• libgnt/riscv64 (2.14.4-1.2 to 2.14.4-1.2)
  • Migration status for libgnt/riscv64 (2.14.4-1.2 to 2.14.4-1.2): Will attempt migration (Any information below is purely informational)
• libgraph-nauty-perl/amd64 (0.5.1-2 to 0.5.1-2)
  • Migration status for libgraph-nauty-perl/amd64 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libgraph-nauty-perl/amd64 nauty
• libgraph-nauty-perl/arm64 (0.5.1-2 to 0.5.1-2)
  • Migration status for libgraph-nauty-perl/arm64 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libgraph-nauty-perl/arm64 nauty
• libgraph-nauty-perl/armel (0.5.1-2 to 0.5.1-2)
  • Migration status for libgraph-nauty-perl/armel (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libgraph-nauty-perl/armel nauty
• libgraph-nauty-perl/armhf (0.5.1-2 to 0.5.1-2)
  • Migration status for libgraph-nauty-perl/armhf (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libgraph-nauty-perl/armhf nauty
• libgraph-nauty-perl/i386 (0.5.1-2 to 0.5.1-2)
  • Migration status for libgraph-nauty-perl/i386 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libgraph-nauty-perl/i386 nauty
• libgraph-nauty-perl/mips64el (0.5.1-2 to 0.5.1-2)
  • Migration status for libgraph-nauty-perl/mips64el (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libgraph-nauty-perl/mips64el nauty
• libgraph-nauty-perl/ppc64el (0.5.1-2 to 0.5.1-2)
  • Migration status for libgraph-nauty-perl/ppc64el (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libgraph-nauty-perl/ppc64el nauty
• libgraph-nauty-perl/riscv64 (0.5.1-2 to 0.5.1-2)
  • Migration status for libgraph-nauty-perl/riscv64 (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
• libgraph-nauty-perl/s390x (0.5.1-2 to 0.5.1-2)
  • Migration status for libgraph-nauty-perl/s390x (0.5.1-2 to 0.5.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libgraph-nauty-perl/s390x nauty
• libgsf/riscv64 (1.14.52-1 to 1.14.52-1)
  • Migration status for libgsf/riscv64 (1.14.52-1 to 1.14.52-1): Will attempt migration (Any information below is purely informational)
• libgtkada/riscv64 (24.0.0-3 to 24.0.0-3)
  • Migration status for libgtkada/riscv64 (24.0.0-3 to 24.0.0-3): Will attempt migration (Any information below is purely informational)
• libgtkdatabox/riscv64 (1:1.0.0-2.1 to 1:1.0.0-2.1)
  • Migration status for libgtkdatabox/riscv64 (1:1.0.0-2.1 to 1:1.0.0-2.1): Will attempt migration (Any information below is purely informational)
• libgtksourceviewmm/riscv64 (3.18.0-4 to 3.18.0-4)
  • Migration status for libgtksourceviewmm/riscv64 (3.18.0-4 to 3.18.0-4): Will attempt migration (Any information below is purely informational)
• libgxps/riscv64 (0.3.2-4 to 0.3.2-4)
  • Migration status for libgxps/riscv64 (0.3.2-4 to 0.3.2-4): Will attempt migration (Any information below is purely informational)
• libhandy-1/riscv64 (1.8.3-1 to 1.8.3-1)
  • Migration status for libhandy-1/riscv64 (1.8.3-1 to 1.8.3-1): Will attempt migration (Any information below is purely informational)
• libhipi-perl/riscv64 (0.92-1 to 0.92-1)
  • Migration status for libhipi-perl/riscv64 (0.92-1 to 0.92-1): Will attempt migration (Any information below is purely informational)
• libhmsbeagle/riscv64 (3.1.2+dfsg-13 to 3.1.2+dfsg-13)
  • Migration status for libhmsbeagle/riscv64 (3.1.2+dfsg-13 to 3.1.2+dfsg-13): Will attempt migration (Any information below is purely informational)
• libimage-imlib2-perl/riscv64 (2.03-1.2 to 2.03-1.2)
  • Migration status for libimage-imlib2-perl/riscv64 (2.03-1.2 to 2.03-1.2): Will attempt migration (Any information below is purely informational)
• libimage-sane-perl/riscv64 (5-2 to 5-2)
  • Migration status for libimage-sane-perl/riscv64 (5-2 to 5-2): Will attempt migration (Any information below is purely informational)
• libinfinity/riscv64 (0.7.2-2.1 to 0.7.2-2.1)
  • Migration status for libinfinity/riscv64 (0.7.2-2.1 to 0.7.2-2.1): Will attempt migration (Any information below is purely informational)
• libinklevel/riscv64 (0.9.5-2 to 0.9.5-2)
  • Migration status for libinklevel/riscv64 (0.9.5-2 to 0.9.5-2): Will attempt migration (Any information below is purely informational)
• libinline-java-perl/riscv64 (0.67-1 to 0.67-1)
  • Migration status for libinline-java-perl/riscv64 (0.67-1 to 0.67-1): Will attempt migration (Any information below is purely informational)
• libjdns/riscv64 (2.0.3-3.1 to 2.0.3-3.1)
  • Migration status for libjdns/riscv64 (2.0.3-3.1 to 2.0.3-3.1): Will attempt migration (Any information below is purely informational)
• libkcddb/riscv64 (4:23.08.1-1 to 4:23.08.1-1)
  • Migration status for libkcddb/riscv64 (4:23.08.1-1 to 4:23.08.1-1): Will attempt migration (Any information below is purely informational)
• libkcompactdisc/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkcompactdisc/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkdegames/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkdegames/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkeduvocdocument/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkeduvocdocument/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkexiv2/amd64 (24.05.1-2 to 24.05.1-2)
  • Migration status for libkexiv2/amd64 (24.05.1-2 to 24.05.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkexiv2/amd64 exiv2
• libkexiv2/arm64 (24.05.1-2 to 24.05.1-2)
  • Migration status for libkexiv2/arm64 (24.05.1-2 to 24.05.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkexiv2/arm64 exiv2
• libkexiv2/armel (24.05.1-2 to 24.05.1-2)
  • Migration status for libkexiv2/armel (24.05.1-2 to 24.05.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkexiv2/armel exiv2
• libkexiv2/armhf (24.05.1-2 to 24.05.1-2)
  • Migration status for libkexiv2/armhf (24.05.1-2 to 24.05.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkexiv2/armhf exiv2
• libkexiv2/i386 (24.05.1-2 to 24.05.1-2)
  • Migration status for libkexiv2/i386 (24.05.1-2 to 24.05.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkexiv2/i386 exiv2
• libkexiv2/mips64el (24.05.1-2 to 24.05.1-2)
  • Migration status for libkexiv2/mips64el (24.05.1-2 to 24.05.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkexiv2/mips64el exiv2
• libkexiv2/ppc64el (24.05.1-2 to 24.05.1-2)
  • Migration status for libkexiv2/ppc64el (24.05.1-2 to 24.05.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkexiv2/ppc64el exiv2
• libkexiv2/s390x (24.05.1-2 to 24.05.1-2)
  • Migration status for libkexiv2/s390x (24.05.1-2 to 24.05.1-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkexiv2/s390x exiv2
• libkf5calendarsupport/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkf5calendarsupport/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkf5eventviews/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkf5eventviews/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkf5grantleetheme/riscv64 (22.12.3-2 to 22.12.3-2)
  • Migration status for libkf5grantleetheme/riscv64 (22.12.3-2 to 22.12.3-2): Will attempt migration (Any information below is purely informational)
• libkf5gravatar/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkf5gravatar/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkf5incidenceeditor/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for libkf5incidenceeditor/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkf5kdcraw/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for libkf5kdcraw/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkf5kexiv2/amd64 (23.04.2-2 to 23.04.2-2)
  • Migration status for libkf5kexiv2/amd64 (23.04.2-2 to 23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkf5kexiv2/amd64 exiv2
• libkf5kexiv2/arm64 (23.04.2-2 to 23.04.2-2)
  • Migration status for libkf5kexiv2/arm64 (23.04.2-2 to 23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkf5kexiv2/arm64 exiv2
• libkf5kexiv2/armel (23.04.2-2 to 23.04.2-2)
  • Migration status for libkf5kexiv2/armel (23.04.2-2 to 23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkf5kexiv2/armel exiv2
• libkf5kexiv2/armhf (23.04.2-2 to 23.04.2-2)
  • Migration status for libkf5kexiv2/armhf (23.04.2-2 to 23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkf5kexiv2/armhf exiv2
• libkf5kexiv2/i386 (23.04.2-2 to 23.04.2-2)
  • Migration status for libkf5kexiv2/i386 (23.04.2-2 to 23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkf5kexiv2/i386 exiv2
• libkf5kexiv2/mips64el (23.04.2-2 to 23.04.2-2)
  • Migration status for libkf5kexiv2/mips64el (23.04.2-2 to 23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkf5kexiv2/mips64el exiv2
• libkf5kexiv2/ppc64el (23.04.2-2 to 23.04.2-2)
  • Migration status for libkf5kexiv2/ppc64el (23.04.2-2 to 23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkf5kexiv2/ppc64el exiv2
• libkf5kexiv2/riscv64 (23.04.2-2 to 23.04.2-2)
  • Migration status for libkf5kexiv2/riscv64 (23.04.2-2 to 23.04.2-2): Will attempt migration (Any information below is purely informational)
• libkf5kexiv2/s390x (23.04.2-2 to 23.04.2-2)
  • Migration status for libkf5kexiv2/s390x (23.04.2-2 to 23.04.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: libkf5kexiv2/s390x exiv2
• libkf5kipi/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkf5kipi/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkf5kmahjongg/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkf5kmahjongg/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkf5libkdepim/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkf5libkdepim/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkf5mailimporter/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkf5mailimporter/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkf5pimcommon/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkf5pimcommon/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkf5sane/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for libkf5sane/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkgapi/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for libkgapi/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkiwix/riscv64 (12.1.1-1.1 to 12.1.1-1.1)
  • Migration status for libkiwix/riscv64 (12.1.1-1.1 to 12.1.1-1.1): Will attempt migration (Any information below is purely informational)
• libkomparediff2/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkomparediff2/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• libktorrent/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for libktorrent/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• libkysdk-applications/riscv64 (2.2.1.1-3 to 2.2.1.1-3)
  • Migration status for libkysdk-applications/riscv64 (2.2.1.1-3 to 2.2.1.1-3): Will attempt migration (Any information below is purely informational)
• liblangtag/riscv64 (0.6.7-1 to 0.6.7-1)
  • Migration status for liblangtag/riscv64 (0.6.7-1 to 0.6.7-1): Will attempt migration (Any information below is purely informational)
• liblastfm/riscv64 (1.1.0-5 to 1.1.0-5)
  • Migration status for liblastfm/riscv64 (1.1.0-5 to 1.1.0-5): Will attempt migration (Any information below is purely informational)
• libleidenalg/riscv64 (0.11.1-2 to 0.11.1-2)
  • Migration status for libleidenalg/riscv64 (0.11.1-2 to 0.11.1-2): Will attempt migration (Any information below is purely informational)
• liblrdf/riscv64 (0.6.1-4 to 0.6.1-4)
  • Migration status for liblrdf/riscv64 (0.6.1-4 to 0.6.1-4): Will attempt migration (Any information below is purely informational)
• liblxi/riscv64 (1.20-2 to 1.20-2)
  • Migration status for liblxi/riscv64 (1.20-2 to 1.20-2): Will attempt migration (Any information below is purely informational)
• libmatekbd/riscv64 (1.26.1-1 to 1.26.1-1)
  • Migration status for libmatekbd/riscv64 (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• libmateweather/riscv64 (1.26.3-3.1 to 1.26.3-3.1)
  • Migration status for libmateweather/riscv64 (1.26.3-3.1 to 1.26.3-3.1): Will attempt migration (Any information below is purely informational)
• libmediaart/riscv64 (1.9.6-1 to 1.9.6-1)
  • Migration status for libmediaart/riscv64 (1.9.6-1 to 1.9.6-1): Will attempt migration (Any information below is purely informational)
• libmediawiki/riscv64 (5.38.0-1 to 5.38.0-1)
  • Migration status for libmediawiki/riscv64 (5.38.0-1 to 5.38.0-1): Will attempt migration (Any information below is purely informational)
• libmialm/riscv64 (1.0.9-3.1 to 1.0.9-3.1)
  • Migration status for libmialm/riscv64 (1.0.9-3.1 to 1.0.9-3.1): Will attempt migration (Any information below is purely informational)
• libminc/riscv64 (2.4.06-2.1 to 2.4.06-2.1)
  • Migration status for libminc/riscv64 (2.4.06-2.1 to 2.4.06-2.1): Will attempt migration (Any information below is purely informational)
• libmlocale/riscv64 (0.7.7-2 to 0.7.7-2)
  • Migration status for libmlocale/riscv64 (0.7.7-2 to 0.7.7-2): Will attempt migration (Any information below is purely informational)
• libmodulemd/riscv64 (2.14.0-3 to 2.14.0-3)
  • Migration status for libmodulemd/riscv64 (2.14.0-3 to 2.14.0-3): Will attempt migration (Any information below is purely informational)
• libmonospaceif/riscv64 (0.7.15-2.1 to 0.7.15-2.1)
  • Migration status for libmonospaceif/riscv64 (0.7.15-2.1 to 0.7.15-2.1): Will attempt migration (Any information below is purely informational)
• libmygpo-qt/riscv64 (1.1.0-4.1 to 1.1.0-4.1)
  • Migration status for libmygpo-qt/riscv64 (1.1.0-4.1 to 1.1.0-4.1): Will attempt migration (Any information below is purely informational)
• libnfo/riscv64 (1.0.1-3 to 1.0.1-3)
  • Migration status for libnfo/riscv64 (1.0.1-3 to 1.0.1-3): Will attempt migration (Any information below is purely informational)
• libnginx-mod-http-dav-ext/riscv64 (1:3.0.0-5 to 1:3.0.0-5)
  • Migration status for libnginx-mod-http-dav-ext/riscv64 (1:3.0.0-5 to 1:3.0.0-5): Will attempt migration (Any information below is purely informational)
• libnginx-mod-http-modsecurity/riscv64 (1.0.3-2 to 1.0.3-2)
  • Migration status for libnginx-mod-http-modsecurity/riscv64 (1.0.3-2 to 1.0.3-2): Will attempt migration (Any information below is purely informational)
• libnice/riscv64 (0.1.21-2 to 0.1.21-2)
  • Migration status for libnice/riscv64 (0.1.21-2 to 0.1.21-2): Will attempt migration (Any information below is purely informational)
• libnotify/riscv64 (0.8.3-1 to 0.8.3-1)
  • Migration status for libnotify/riscv64 (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• libodfgen/riscv64 (0.1.8-2 to 0.1.8-2)
  • Migration status for libodfgen/riscv64 (0.1.8-2 to 0.1.8-2): Will attempt migration (Any information below is purely informational)
• libofx/riscv64 (1:0.10.9-1.1 to 1:0.10.9-1.1)
  • Migration status for libofx/riscv64 (1:0.10.9-1.1 to 1:0.10.9-1.1): Will attempt migration (Any information below is purely informational)
• libopengl-perl/riscv64 (0.7000+dfsg-8 to 0.7000+dfsg-8)
  • Migration status for libopengl-perl/riscv64 (0.7000+dfsg-8 to 0.7000+dfsg-8): Will attempt migration (Any information below is purely informational)
• libopengl-xscreensaver-perl/riscv64 (0.05-2 to 0.05-2)
  • Migration status for libopengl-xscreensaver-perl/riscv64 (0.05-2 to 0.05-2): Will attempt migration (Any information below is purely informational)
• libopenraw/riscv64 (0.1.2-0.4 to 0.1.2-0.4)
  • Migration status for libopenraw/riscv64 (0.1.2-0.4 to 0.1.2-0.4): Will attempt migration (Any information below is purely informational)
• libosinfo/riscv64 (1.11.0-2 to 1.11.0-2)
  • Migration status for libosinfo/riscv64 (1.11.0-2 to 1.11.0-2): Will attempt migration (Any information below is purely informational)
• libpam-mount/riscv64 (2.20-3 to 2.20-3)
  • Migration status for libpam-mount/riscv64 (2.20-3 to 2.20-3): Will attempt migration (Any information below is purely informational)
• libpdl-netcdf-perl/riscv64 (4.24-1 to 4.24-1)
  • Migration status for libpdl-netcdf-perl/riscv64 (4.24-1 to 4.24-1): Will attempt migration (Any information below is purely informational)
• libpeas/riscv64 (1.36.0-3 to 1.36.0-3)
  • Migration status for libpeas/riscv64 (1.36.0-3 to 1.36.0-3): Will attempt migration (Any information below is purely informational)
• libpixelif/riscv64 (0.8.4-3.2 to 0.8.4-3.2)
  • Migration status for libpixelif/riscv64 (0.8.4-3.2 to 0.8.4-3.2): Will attempt migration (Any information below is purely informational)
• libpst/riscv64 (0.6.76-1.1 to 0.6.76-1.1)
  • Migration status for libpst/riscv64 (0.6.76-1.1 to 0.6.76-1.1): Will attempt migration (Any information below is purely informational)
• libqapt/riscv64 (3.0.5-2 to 3.0.5-2)
  • Migration status for libqapt/riscv64 (3.0.5-2 to 3.0.5-2): Will attempt migration (Any information below is purely informational)
• libqglviewer/riscv64 (2.8.0+dfsg1-2.1 to 2.8.0+dfsg1-2.1)
  • Migration status for libqglviewer/riscv64 (2.8.0+dfsg1-2.1 to 2.8.0+dfsg1-2.1): Will attempt migration (Any information below is purely informational)
• libqofono/riscv64 (0.122-2 to 0.122-2)
  • Migration status for libqofono/riscv64 (0.122-2 to 0.122-2): Will attempt migration (Any information below is purely informational)
• libqt5qxlsx/riscv64 (1.4.4-1.1 to 1.4.4-1.1)
  • Migration status for libqt5qxlsx/riscv64 (1.4.4-1.1 to 1.4.4-1.1): Will attempt migration (Any information below is purely informational)
• libqtdbustest/riscv64 (0.3.2-3 to 0.3.2-3)
  • Migration status for libqtdbustest/riscv64 (0.3.2-3 to 0.3.2-3): Will attempt migration (Any information below is purely informational)
• libqtxdg/riscv64 (3.12.0-1 to 3.12.0-1)
  • Migration status for libqtxdg/riscv64 (3.12.0-1 to 3.12.0-1): Will attempt migration (Any information below is purely informational)
• libquazip/riscv64 (0.9.1-4 to 0.9.1-4)
  • Migration status for libquazip/riscv64 (0.9.1-4 to 0.9.1-4): Will attempt migration (Any information below is purely informational)
• libquazip1-qt5/riscv64 (1.4-1.1 to 1.4-1.1)
  • Migration status for libquazip1-qt5/riscv64 (1.4-1.1 to 1.4-1.1): Will attempt migration (Any information below is purely informational)
• libquazip1-qt6/riscv64 (1.4-1.1 to 1.4-1.1)
  • Migration status for libquazip1-qt6/riscv64 (1.4-1.1 to 1.4-1.1): Will attempt migration (Any information below is purely informational)
• libquicktime/riscv64 (2:1.2.4-16 to 2:1.2.4-16)
  • Migration status for libquicktime/riscv64 (2:1.2.4-16 to 2:1.2.4-16): Will attempt migration (Any information below is purely informational)
• librasterlite2/riscv64 (1.1.0~beta1-3 to 1.1.0~beta1-3)
  • Migration status for librasterlite2/riscv64 (1.1.0~beta1-3 to 1.1.0~beta1-3): Will attempt migration (Any information below is purely informational)
• librcc/riscv64 (0.2.13+ds-2 to 0.2.13+ds-2)
  • Migration status for librcc/riscv64 (0.2.13+ds-2 to 0.2.13+ds-2): Will attempt migration (Any information below is purely informational)
• librecad/riscv64 (2.2.0.2-1 to 2.2.0.2-1)
  • Migration status for librecad/riscv64 (2.2.0.2-1 to 2.2.0.2-1): Will attempt migration (Any information below is purely informational)
• librest/riscv64 (0.9.1-6 to 0.9.1-6)
  • Migration status for librest/riscv64 (0.9.1-6 to 0.9.1-6): Will attempt migration (Any information below is purely informational)
• libretro-beetle-vb/riscv64 (0.9.36.1+git20160623-2 to 0.9.36.1+git20160623-2)
  • Migration status for libretro-beetle-vb/riscv64 (0.9.36.1+git20160623-2 to 0.9.36.1+git20160623-2): Will attempt migration (Any information below is purely informational)
• libretro-beetle-wswan/riscv64 (0.9.35.1+git20160623-2 to 0.9.35.1+git20160623-2)
  • Migration status for libretro-beetle-wswan/riscv64 (0.9.35.1+git20160623-2 to 0.9.35.1+git20160623-2): Will attempt migration (Any information below is purely informational)
• libretro-bsnes-mercury/riscv64 (094+git20220807-8 to 094+git20220807-8)
  • Migration status for libretro-bsnes-mercury/riscv64 (094+git20220807-8 to 094+git20220807-8): Will attempt migration (Any information below is purely informational)
• libretro-desmume/riscv64 (0.9.11+git20160819+dfsg1-2 to 0.9.11+git20160819+dfsg1-2)
  • Migration status for libretro-desmume/riscv64 (0.9.11+git20160819+dfsg1-2 to 0.9.11+git20160819+dfsg1-2): Will attempt migration (Any information below is purely informational)
• libretro-gambatte/riscv64 (0.5.0+git20160522+dfsg1-2.1 to 0.5.0+git20160522+dfsg1-2.1)
  • Migration status for libretro-gambatte/riscv64 (0.5.0+git20160522+dfsg1-2.1 to 0.5.0+git20160522+dfsg1-2.1): Will attempt migration (Any information below is purely informational)
• libretro-snes9x/riscv64 (1.61+dfsg-1 to 1.61+dfsg-1)
  • Migration status for libretro-snes9x/riscv64 (1.61+dfsg-1 to 1.61+dfsg-1): Will attempt migration (Any information below is purely informational)
• librsvg/riscv64 (2.58.0+dfsg-1 to 2.58.0+dfsg-1)
  • Migration status for librsvg/riscv64 (2.58.0+dfsg-1 to 2.58.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• libs3/riscv64 (2.0-4 to 2.0-4)
  • Migration status for libs3/riscv64 (2.0-4 to 2.0-4): Will attempt migration (Any information below is purely informational)
• libsavitar/riscv64 (5.0.0-4.1 to 5.0.0-4.1)
  • Migration status for libsavitar/riscv64 (5.0.0-4.1 to 5.0.0-4.1): Will attempt migration (Any information below is purely informational)
• libsdl-perl/riscv64 (2.548-5 to 2.548-5)
  • Migration status for libsdl-perl/riscv64 (2.548-5 to 2.548-5): Will attempt migration (Any information below is purely informational)
• libsdl-sge/riscv64 (030809dfsg-11 to 030809dfsg-11)
  • Migration status for libsdl-sge/riscv64 (030809dfsg-11 to 030809dfsg-11): Will attempt migration (Any information below is purely informational)
• libsndifsdl2/riscv64 (0.8.3-2 to 0.8.3-2)
  • Migration status for libsndifsdl2/riscv64 (0.8.3-2 to 0.8.3-2): Will attempt migration (Any information below is purely informational)
• libsoil/riscv64 (1.07~20080707.dfsg-4 to 1.07~20080707.dfsg-4)
  • Migration status for libsoil/riscv64 (1.07~20080707.dfsg-4 to 1.07~20080707.dfsg-4): Will attempt migration (Any information below is purely informational)
• libsoup2.4/riscv64 (2.74.3-7 to 2.74.3-7)
  • Migration status for libsoup2.4/riscv64 (2.74.3-7 to 2.74.3-7): Will attempt migration (Any information below is purely informational)
• libtimezonemap/riscv64 (0.4.6-7 to 0.4.6-7)
  • Migration status for libtimezonemap/riscv64 (0.4.6-7 to 0.4.6-7): Will attempt migration (Any information below is purely informational)
• libunity/riscv64 (7.1.4+19.04.20190319-6.1 to 7.1.4+19.04.20190319-6.1)
  • Migration status for libunity/riscv64 (7.1.4+19.04.20190319-6.1 to 7.1.4+19.04.20190319-6.1): Will attempt migration (Any information below is purely informational)
• libvirt-dbus/riscv64 (1.4.1-3 to 1.4.1-3)
  • Migration status for libvirt-dbus/riscv64 (1.4.1-3 to 1.4.1-3): Will attempt migration (Any information below is purely informational)
• libvirt-glib/riscv64 (5.0.0-2 to 5.0.0-2)
  • Migration status for libvirt-glib/riscv64 (5.0.0-2 to 5.0.0-2): Will attempt migration (Any information below is purely informational)
• libvisio/riscv64 (0.1.7-1 to 0.1.7-1)
  • Migration status for libvisio/riscv64 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• libvisual-plugins/riscv64 (1:0.4.2+dfsg-2 to 1:0.4.2+dfsg-2)
  • Migration status for libvisual-plugins/riscv64 (1:0.4.2+dfsg-2 to 1:0.4.2+dfsg-2): Will attempt migration (Any information below is purely informational)
• libvoikko/riscv64 (4.3.2-1 to 4.3.2-1)
  • Migration status for libvoikko/riscv64 (4.3.2-1 to 4.3.2-1): Will attempt migration (Any information below is purely informational)
• libwebcam/riscv64 (0.2.5-4 to 0.2.5-4)
  • Migration status for libwebcam/riscv64 (0.2.5-4 to 0.2.5-4): Will attempt migration (Any information below is purely informational)
• libwildmagic/riscv64 (5.17+cleaned1-7 to 5.17+cleaned1-7)
  • Migration status for libwildmagic/riscv64 (5.17+cleaned1-7 to 5.17+cleaned1-7): Will attempt migration (Any information below is purely informational)
• libwmf/riscv64 (0.2.13-1.1 to 0.2.13-1.1)
  • Migration status for libwmf/riscv64 (0.2.13-1.1 to 0.2.13-1.1): Will attempt migration (Any information below is purely informational)
• libwnck3/riscv64 (43.0-3 to 43.0-3)
  • Migration status for libwnck3/riscv64 (43.0-3 to 43.0-3): Will attempt migration (Any information below is purely informational)
• libwpe/riscv64 (1.16.0-1 to 1.16.0-1)
  • Migration status for libwpe/riscv64 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• libwx-glcanvas-perl/riscv64 (0.09-8 to 0.09-8)
  • Migration status for libwx-glcanvas-perl/riscv64 (0.09-8 to 0.09-8): Will attempt migration (Any information below is purely informational)
• libwx-perl/riscv64 (1:0.9932-8 to 1:0.9932-8)
  • Migration status for libwx-perl/riscv64 (1:0.9932-8 to 1:0.9932-8): Will attempt migration (Any information below is purely informational)
• libwx-scintilla-perl/riscv64 (0.39-6 to 0.39-6)
  • Migration status for libwx-scintilla-perl/riscv64 (0.39-6 to 0.39-6): Will attempt migration (Any information below is purely informational)
• libxklavier/riscv64 (5.4-5 to 5.4-5)
  • Migration status for libxklavier/riscv64 (5.4-5 to 5.4-5): Will attempt migration (Any information below is purely informational)
• libxml++2.6/riscv64 (2.42.3-1 to 2.42.3-1)
  • Migration status for libxml++2.6/riscv64 (2.42.3-1 to 2.42.3-1): Will attempt migration (Any information below is purely informational)
• libxtrx/riscv64 (0.0.1+git20191219.98458ce-3 to 0.0.1+git20191219.98458ce-3)
  • Migration status for libxtrx/riscv64 (0.0.1+git20191219.98458ce-3 to 0.0.1+git20191219.98458ce-3): Will attempt migration (Any information below is purely informational)
• libzbd/riscv64 (2.0.4-1.1 to 2.0.4-1.1)
  • Migration status for libzbd/riscv64 (2.0.4-1.1 to 2.0.4-1.1): Will attempt migration (Any information below is purely informational)
• lifeograph/riscv64 (2.0.3-1 to 2.0.3-1)
  • Migration status for lifeograph/riscv64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• light-locker/riscv64 (1.8.0-3 to 1.8.0-3)
  • Migration status for light-locker/riscv64 (1.8.0-3 to 1.8.0-3): Will attempt migration (Any information below is purely informational)
• lightdm-gtk-greeter/riscv64 (2.0.9-1 to 2.0.9-1)
  • Migration status for lightdm-gtk-greeter/riscv64 (2.0.9-1 to 2.0.9-1): Will attempt migration (Any information below is purely informational)
• lightdm-remote-session-freerdp2/riscv64 (2.0.0-1 to 2.0.0-1)
  • Migration status for lightdm-remote-session-freerdp2/riscv64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• lightdm-remote-session-x2go/riscv64 (0.0.2.0-2 to 0.0.2.0-2)
  • Migration status for lightdm-remote-session-x2go/riscv64 (0.0.2.0-2 to 0.0.2.0-2): Will attempt migration (Any information below is purely informational)
• lightsoff/riscv64 (1:46.0-1 to 1:46.0-1)
  • Migration status for lightsoff/riscv64 (1:46.0-1 to 1:46.0-1): Will attempt migration (Any information below is purely informational)
• links2/riscv64 (2.29-1 to 2.29-1)
  • Migration status for links2/riscv64 (2.29-1 to 2.29-1): Will attempt migration (Any information below is purely informational)
• litmus/riscv64 (0.13-5 to 0.13-5)
  • Migration status for litmus/riscv64 (0.13-5 to 0.13-5): Will attempt migration (Any information below is purely informational)
• littlewizard/riscv64 (1.2.2-4.1 to 1.2.2-4.1)
  • Migration status for littlewizard/riscv64 (1.2.2-4.1 to 1.2.2-4.1): Will attempt migration (Any information below is purely informational)
• lldpd/riscv64 (1.0.18-1 to 1.0.18-1)
  • Migration status for lldpd/riscv64 (1.0.18-1 to 1.0.18-1): Will attempt migration (Any information below is purely informational)
• llvm-defaults/riscv64 (0.58.1 to 0.58.1)
  • Migration status for llvm-defaults/riscv64 (0.58.1 to 0.58.1): Will attempt migration (Any information below is purely informational)
• llvm-toolchain-16/riscv64 (1:16.0.6-27 to 1:16.0.6-27)
  • Migration status for llvm-toolchain-16/riscv64 (1:16.0.6-27 to 1:16.0.6-27): Will attempt migration (Any information below is purely informational)
• lmms/riscv64 (1.2.2+dfsg1-6 to 1.2.2+dfsg1-6)
  • Migration status for lmms/riscv64 (1.2.2+dfsg1-6 to 1.2.2+dfsg1-6): Will attempt migration (Any information below is purely informational)
• loggedfs/riscv64 (0.9+ds-4 to 0.9+ds-4)
  • Migration status for loggedfs/riscv64 (0.9+ds-4 to 0.9+ds-4): Will attempt migration (Any information below is purely informational)
• logstalgia/riscv64 (1.1.4-1 to 1.1.4-1)
  • Migration status for logstalgia/riscv64 (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
• lokalize/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for lokalize/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• lomiri-action-api/riscv64 (1.1.3-1 to 1.1.3-1)
  • Migration status for lomiri-action-api/riscv64 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• lomiri-app-launch/riscv64 (0.1.9-3 to 0.1.9-3)
  • Migration status for lomiri-app-launch/riscv64 (0.1.9-3 to 0.1.9-3): Will attempt migration (Any information below is purely informational)
• lomiri-camera-app/amd64 (4.0.6+dfsg-1 to 4.0.6+dfsg-1)
  • Migration status for lomiri-camera-app/amd64 (4.0.6+dfsg-1 to 4.0.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-camera-app/amd64 exiv2
• lomiri-camera-app/arm64 (4.0.6+dfsg-1 to 4.0.6+dfsg-1)
  • Migration status for lomiri-camera-app/arm64 (4.0.6+dfsg-1 to 4.0.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-camera-app/arm64 exiv2
• lomiri-camera-app/armel (4.0.6+dfsg-1 to 4.0.6+dfsg-1)
  • Migration status for lomiri-camera-app/armel (4.0.6+dfsg-1 to 4.0.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-camera-app/armel exiv2
• lomiri-camera-app/armhf (4.0.6+dfsg-1 to 4.0.6+dfsg-1)
  • Migration status for lomiri-camera-app/armhf (4.0.6+dfsg-1 to 4.0.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-camera-app/armhf exiv2
• lomiri-camera-app/i386 (4.0.6+dfsg-1 to 4.0.6+dfsg-1)
  • Migration status for lomiri-camera-app/i386 (4.0.6+dfsg-1 to 4.0.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-camera-app/i386 exiv2
• lomiri-camera-app/ppc64el (4.0.6+dfsg-1 to 4.0.6+dfsg-1)
  • Migration status for lomiri-camera-app/ppc64el (4.0.6+dfsg-1 to 4.0.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-camera-app/ppc64el exiv2
• lomiri-camera-app/s390x (4.0.6+dfsg-1 to 4.0.6+dfsg-1)
  • Migration status for lomiri-camera-app/s390x (4.0.6+dfsg-1 to 4.0.6+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-camera-app/s390x exiv2
• lomiri-notifications/riscv64 (1.3.0-1 to 1.3.0-1)
  • Migration status for lomiri-notifications/riscv64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• lomiri-settings-components/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for lomiri-settings-components/riscv64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• lomiri-telephony-service/riscv64 (0.5.3-2 to 0.5.3-2)
  • Migration status for lomiri-telephony-service/riscv64 (0.5.3-2 to 0.5.3-2): Will attempt migration (Any information below is purely informational)
• lomiri-terminal-app/riscv64 (2.0.2-3 to 2.0.2-3)
  • Migration status for lomiri-terminal-app/riscv64 (2.0.2-3 to 2.0.2-3): Will attempt migration (Any information below is purely informational)
• lomiri-thumbnailer/riscv64 (3.0.3-1 to 3.0.3-1)
  • Migration status for lomiri-thumbnailer/riscv64 (3.0.3-1 to 3.0.3-1): Will attempt migration (Any information below is purely informational)
• lomiri-ui-extras/amd64 (0.6.3-2 to 0.6.3-2)
  • Migration status for lomiri-ui-extras/amd64 (0.6.3-2 to 0.6.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-ui-extras/amd64 exiv2
• lomiri-ui-extras/arm64 (0.6.3-2 to 0.6.3-2)
  • Migration status for lomiri-ui-extras/arm64 (0.6.3-2 to 0.6.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-ui-extras/arm64 exiv2
• lomiri-ui-extras/armel (0.6.3-2 to 0.6.3-2)
  • Migration status for lomiri-ui-extras/armel (0.6.3-2 to 0.6.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-ui-extras/armel exiv2
• lomiri-ui-extras/armhf (0.6.3-2 to 0.6.3-2)
  • Migration status for lomiri-ui-extras/armhf (0.6.3-2 to 0.6.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-ui-extras/armhf exiv2
• lomiri-ui-extras/i386 (0.6.3-2 to 0.6.3-2)
  • Migration status for lomiri-ui-extras/i386 (0.6.3-2 to 0.6.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-ui-extras/i386 exiv2
• lomiri-ui-extras/mips64el (0.6.3-2 to 0.6.3-2)
  • Migration status for lomiri-ui-extras/mips64el (0.6.3-2 to 0.6.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-ui-extras/mips64el exiv2
• lomiri-ui-extras/ppc64el (0.6.3-2 to 0.6.3-2)
  • Migration status for lomiri-ui-extras/ppc64el (0.6.3-2 to 0.6.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-ui-extras/ppc64el exiv2
• lomiri-ui-extras/riscv64 (0.6.3-2 to 0.6.3-2)
  • Migration status for lomiri-ui-extras/riscv64 (0.6.3-2 to 0.6.3-2): Will attempt migration (Any information below is purely informational)
• lomiri-ui-extras/s390x (0.6.3-2 to 0.6.3-2)
  • Migration status for lomiri-ui-extras/s390x (0.6.3-2 to 0.6.3-2): Will attempt migration (Any information below is purely informational)
    • Depends: lomiri-ui-extras/s390x exiv2
• looktxt/riscv64 (1.4.1-3 to 1.4.1-3)
  • Migration status for looktxt/riscv64 (1.4.1-3 to 1.4.1-3): Will attempt migration (Any information below is purely informational)
• lshw/riscv64 (02.19.git.2021.06.19.996aaad9c7-2 to 02.19.git.2021.06.19.996aaad9c7-2)
  • Migration status for lshw/riscv64 (02.19.git.2021.06.19.996aaad9c7-2 to 02.19.git.2021.06.19.996aaad9c7-2): Will attempt migration (Any information below is purely informational)
• lskat/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for lskat/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• ltrsift/riscv64 (1.0.2-10 to 1.0.2-10)
  • Migration status for ltrsift/riscv64 (1.0.2-10 to 1.0.2-10): Will attempt migration (Any information below is purely informational)
• lttoolbox/riscv64 (3.7.6-1 to 3.7.6-1)
  • Migration status for lttoolbox/riscv64 (3.7.6-1 to 3.7.6-1): Will attempt migration (Any information below is purely informational)
• luckybackup/riscv64 (0.5.0-7 to 0.5.0-7)
  • Migration status for luckybackup/riscv64 (0.5.0-7 to 0.5.0-7): Will attempt migration (Any information below is purely informational)
• lugaru/riscv64 (1.2-6 to 1.2-6)
  • Migration status for lugaru/riscv64 (1.2-6 to 1.2-6): Will attempt migration (Any information below is purely informational)
• luminance-hdr/amd64 (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3)
  • Migration status for luminance-hdr/amd64 (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3): Will attempt migration (Any information below is purely informational)
    • Depends: luminance-hdr/amd64 exiv2
• luminance-hdr/arm64 (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3)
  • Migration status for luminance-hdr/arm64 (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3): Will attempt migration (Any information below is purely informational)
    • Depends: luminance-hdr/arm64 exiv2
• luminance-hdr/armel (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3)
  • Migration status for luminance-hdr/armel (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3): Will attempt migration (Any information below is purely informational)
    • Depends: luminance-hdr/armel exiv2
• luminance-hdr/armhf (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3)
  • Migration status for luminance-hdr/armhf (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3): Will attempt migration (Any information below is purely informational)
    • Depends: luminance-hdr/armhf exiv2
• luminance-hdr/i386 (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3)
  • Migration status for luminance-hdr/i386 (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3): Will attempt migration (Any information below is purely informational)
    • Depends: luminance-hdr/i386 exiv2
• luminance-hdr/mips64el (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3)
  • Migration status for luminance-hdr/mips64el (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3): Will attempt migration (Any information below is purely informational)
    • Depends: luminance-hdr/mips64el exiv2
• luminance-hdr/ppc64el (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3)
  • Migration status for luminance-hdr/ppc64el (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3): Will attempt migration (Any information below is purely informational)
    • Depends: luminance-hdr/ppc64el exiv2
• luminance-hdr/riscv64 (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3)
  • Migration status for luminance-hdr/riscv64 (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3): Will attempt migration (Any information below is purely informational)
• luminance-hdr/s390x (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3)
  • Migration status for luminance-hdr/s390x (2.6.1.1+dfsg-3 to 2.6.1.1+dfsg-3): Will attempt migration (Any information below is purely informational)
    • Depends: luminance-hdr/s390x exiv2
• lunar-calendar/riscv64 (3.0.1-2 to 3.0.1-2)
  • Migration status for lunar-calendar/riscv64 (3.0.1-2 to 3.0.1-2): Will attempt migration (Any information below is purely informational)
• luola/riscv64 (1.3.2-14 to 1.3.2-14)
  • Migration status for luola/riscv64 (1.3.2-14 to 1.3.2-14): Will attempt migration (Any information below is purely informational)
• lusernet.app/riscv64 (0.4.3-1 to 0.4.3-1)
  • Migration status for lusernet.app/riscv64 (0.4.3-1 to 0.4.3-1): Will attempt migration (Any information below is purely informational)
• lxappearance-obconf/riscv64 (0.2.3-2.1 to 0.2.3-2.1)
  • Migration status for lxappearance-obconf/riscv64 (0.2.3-2.1 to 0.2.3-2.1): Will attempt migration (Any information below is purely informational)
• lxappearance/riscv64 (0.6.3-5 to 0.6.3-5)
  • Migration status for lxappearance/riscv64 (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
• lxhotkey/riscv64 (0.1.1-2 to 0.1.1-2)
  • Migration status for lxhotkey/riscv64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• lxi-tools/riscv64 (2.7-1 to 2.7-1)
  • Migration status for lxi-tools/riscv64 (2.7-1 to 2.7-1): Will attempt migration (Any information below is purely informational)
• lxinput/riscv64 (0.3.5-2 to 0.3.5-2)
  • Migration status for lxinput/riscv64 (0.3.5-2 to 0.3.5-2): Will attempt migration (Any information below is purely informational)
• lxlauncher/riscv64 (0.2.5-1.1 to 0.2.5-1.1)
  • Migration status for lxlauncher/riscv64 (0.2.5-1.1 to 0.2.5-1.1): Will attempt migration (Any information below is purely informational)
• lxpanel/riscv64 (0.10.1-4 to 0.10.1-4)
  • Migration status for lxpanel/riscv64 (0.10.1-4 to 0.10.1-4): Will attempt migration (Any information below is purely informational)
• lxqt-metapackages/riscv64 (32 to 32)
  • Migration status for lxqt-metapackages/riscv64 (32 to 32): Will attempt migration (Any information below is purely informational)
• lxrandr/riscv64 (0.3.2-1.1 to 0.3.2-1.1)
  • Migration status for lxrandr/riscv64 (0.3.2-1.1 to 0.3.2-1.1): Will attempt migration (Any information below is purely informational)
• lxsession/riscv64 (0.5.5-3 to 0.5.5-3)
  • Migration status for lxsession/riscv64 (0.5.5-3 to 0.5.5-3): Will attempt migration (Any information below is purely informational)
• lxtask/riscv64 (0.1.10-2 to 0.1.10-2)
  • Migration status for lxtask/riscv64 (0.1.10-2 to 0.1.10-2): Will attempt migration (Any information below is purely informational)
• lxterminal/riscv64 (0.4.0-2 to 0.4.0-2)
  • Migration status for lxterminal/riscv64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• m17n-lib/riscv64 (1.8.4-1 to 1.8.4-1)
  • Migration status for m17n-lib/riscv64 (1.8.4-1 to 1.8.4-1): Will attempt migration (Any information below is purely informational)
• macopix/riscv64 (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3)
  • Migration status for macopix/riscv64 (3.4.0+dfsg.1-3 to 3.4.0+dfsg.1-3): Will attempt migration (Any information below is purely informational)
• magic-haskell/riscv64 (1.1-11 to 1.1-11)
  • Migration status for magic-haskell/riscv64 (1.1-11 to 1.1-11): Will attempt migration (Any information below is purely informational)
• mah-jong/riscv64 (1.16-1 to 1.16-1)
  • Migration status for mah-jong/riscv64 (1.16-1 to 1.16-1): Will attempt migration (Any information below is purely informational)
• maim/riscv64 (5.7.4-2 to 5.7.4-2)
  • Migration status for maim/riscv64 (5.7.4-2 to 5.7.4-2): Will attempt migration (Any information below is purely informational)
• makexvpics/riscv64 (1.0.1-4 to 1.0.1-4)
  • Migration status for makexvpics/riscv64 (1.0.1-4 to 1.0.1-4): Will attempt migration (Any information below is purely informational)
• maliit-framework/riscv64 (2.3.0-4 to 2.3.0-4)
  • Migration status for maliit-framework/riscv64 (2.3.0-4 to 2.3.0-4): Will attempt migration (Any information below is purely informational)
• maliit-inputcontext-gtk/riscv64 (0.99.1+git20151116.72d7576-3 to 0.99.1+git20151116.72d7576-3)
  • Migration status for maliit-inputcontext-gtk/riscv64 (0.99.1+git20151116.72d7576-3 to 0.99.1+git20151116.72d7576-3): Will attempt migration (Any information below is purely informational)
• mandelbulber2/riscv64 (2.20-2 to 2.20-2)
  • Migration status for mandelbulber2/riscv64 (2.20-2 to 2.20-2): Will attempt migration (Any information below is purely informational)
• mangler/riscv64 (1.2.5-5.1 to 1.2.5-5.1)
  • Migration status for mangler/riscv64 (1.2.5-5.1 to 1.2.5-5.1): Will attempt migration (Any information below is purely informational)
• marble/riscv64 (4:22.12.3-2 to 4:22.12.3-2)
  • Migration status for marble/riscv64 (4:22.12.3-2 to 4:22.12.3-2): Will attempt migration (Any information below is purely informational)
• marco/riscv64 (1.26.2-4 to 1.26.2-4)
  • Migration status for marco/riscv64 (1.26.2-4 to 1.26.2-4): Will attempt migration (Any information below is purely informational)
• markdownpart/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for markdownpart/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• marsshooter/riscv64 (0.7.6-7 to 0.7.6-7)
  • Migration status for marsshooter/riscv64 (0.7.6-7 to 0.7.6-7): Will attempt migration (Any information below is purely informational)
• massif-visualizer/riscv64 (0.7.0-4 to 0.7.0-4)
  • Migration status for massif-visualizer/riscv64 (0.7.0-4 to 0.7.0-4): Will attempt migration (Any information below is purely informational)
• matchbox-panel-manager/riscv64 (0.1+git20041202-1 to 0.1+git20041202-1)
  • Migration status for matchbox-panel-manager/riscv64 (0.1+git20041202-1 to 0.1+git20041202-1): Will attempt migration (Any information below is purely informational)
• mate-calc/riscv64 (1.26.0-1 to 1.26.0-1)
  • Migration status for mate-calc/riscv64 (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• mate-control-center/riscv64 (1.26.1-1.1 to 1.26.1-1.1)
  • Migration status for mate-control-center/riscv64 (1.26.1-1.1 to 1.26.1-1.1): Will attempt migration (Any information below is purely informational)
• mate-desktop/riscv64 (1.26.2-1.1 to 1.26.2-1.1)
  • Migration status for mate-desktop/riscv64 (1.26.2-1.1 to 1.26.2-1.1): Will attempt migration (Any information below is purely informational)
• mate-dock-applet/riscv64 (21.10.0-1 to 21.10.0-1)
  • Migration status for mate-dock-applet/riscv64 (21.10.0-1 to 21.10.0-1): Will attempt migration (Any information below is purely informational)
• mate-indicator-applet/riscv64 (1.26.0-1 to 1.26.0-1)
  • Migration status for mate-indicator-applet/riscv64 (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• mate-media/riscv64 (1.26.2-1 to 1.26.2-1)
  • Migration status for mate-media/riscv64 (1.26.2-1 to 1.26.2-1): Will attempt migration (Any information below is purely informational)
• mate-netbook/riscv64 (1.26.0-1 to 1.26.0-1)
  • Migration status for mate-netbook/riscv64 (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• mate-notification-daemon/riscv64 (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-notification-daemon/riscv64 (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• mate-polkit/riscv64 (1.26.1-4 to 1.26.1-4)
  • Migration status for mate-polkit/riscv64 (1.26.1-4 to 1.26.1-4): Will attempt migration (Any information below is purely informational)
• mate-screensaver/riscv64 (1.26.2-1 to 1.26.2-1)
  • Migration status for mate-screensaver/riscv64 (1.26.2-1 to 1.26.2-1): Will attempt migration (Any information below is purely informational)
• mate-sensors-applet/riscv64 (1.26.0-1 to 1.26.0-1)
  • Migration status for mate-sensors-applet/riscv64 (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• mate-session-manager/riscv64 (1.26.1-2 to 1.26.1-2)
  • Migration status for mate-session-manager/riscv64 (1.26.1-2 to 1.26.1-2): Will attempt migration (Any information below is purely informational)
• mate-system-monitor/riscv64 (1.26.3-1 to 1.26.3-1)
  • Migration status for mate-system-monitor/riscv64 (1.26.3-1 to 1.26.3-1): Will attempt migration (Any information below is purely informational)
• mate-terminal/riscv64 (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-terminal/riscv64 (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• mate-user-admin/riscv64 (1.7.0-1 to 1.7.0-1)
  • Migration status for mate-user-admin/riscv64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• mate-user-share/riscv64 (1.26.0-1 to 1.26.0-1)
  • Migration status for mate-user-share/riscv64 (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• mate-utils/riscv64 (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-utils/riscv64 (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
• mate-window-applets/riscv64 (21.04.0-1 to 21.04.0-1)
  • Migration status for mate-window-applets/riscv64 (21.04.0-1 to 21.04.0-1): Will attempt migration (Any information below is purely informational)
• matekbd-keyboard-display/riscv64 (23.11.1-1 to 23.11.1-1)
  • Migration status for matekbd-keyboard-display/riscv64 (23.11.1-1 to 23.11.1-1): Will attempt migration (Any information below is purely informational)
• mazeofgalious/riscv64 (0.62.dfsg2-5 to 0.62.dfsg2-5)
  • Migration status for mazeofgalious/riscv64 (0.62.dfsg2-5 to 0.62.dfsg2-5): Will attempt migration (Any information below is purely informational)
• mednaffe/riscv64 (0.9.3-1 to 0.9.3-1)
  • Migration status for mednaffe/riscv64 (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
• megaglest/riscv64 (3.13.0-9 to 3.13.0-9)
  • Migration status for megaglest/riscv64 (3.13.0-9 to 3.13.0-9): Will attempt migration (Any information below is purely informational)
• menu-cache/riscv64 (1.1.0-1.1 to 1.1.0-1.1)
  • Migration status for menu-cache/riscv64 (1.1.0-1.1 to 1.1.0-1.1): Will attempt migration (Any information below is purely informational)
• mesa-demos/riscv64 (9.0.0-2 to 9.0.0-2)
  • Migration status for mesa-demos/riscv64 (9.0.0-2 to 9.0.0-2): Will attempt migration (Any information below is purely informational)
• metacity/riscv64 (1:3.52.0-1 to 1:3.52.0-1)
  • Migration status for metacity/riscv64 (1:3.52.0-1 to 1:3.52.0-1): Will attempt migration (Any information below is purely informational)
• metadata-cleaner/riscv64 (2.5.2+ds-1 to 2.5.2+ds-1)
  • Migration status for metadata-cleaner/riscv64 (2.5.2+ds-1 to 2.5.2+ds-1): Will attempt migration (Any information below is purely informational)
• meteo-qt/riscv64 (3.3-2.1 to 3.3-2.1)
  • Migration status for meteo-qt/riscv64 (3.3-2.1 to 3.3-2.1): Will attempt migration (Any information below is purely informational)
• mftrace/riscv64 (1.2.20+git20191022.3b4bc2e-3 to 1.2.20+git20191022.3b4bc2e-3)
  • Migration status for mftrace/riscv64 (1.2.20+git20191022.3b4bc2e-3 to 1.2.20+git20191022.3b4bc2e-3): Will attempt migration (Any information below is purely informational)
• mgp/riscv64 (1.13a+upstream20090219-12 to 1.13a+upstream20090219-12)
  • Migration status for mgp/riscv64 (1.13a+upstream20090219-12 to 1.13a+upstream20090219-12): Will attempt migration (Any information below is purely informational)
• mhwaveedit/riscv64 (1.4.24-1 to 1.4.24-1)
  • Migration status for mhwaveedit/riscv64 (1.4.24-1 to 1.4.24-1): Will attempt migration (Any information below is purely informational)
• miceamaze/riscv64 (4.2.1-3 to 4.2.1-3)
  • Migration status for miceamaze/riscv64 (4.2.1-3 to 4.2.1-3): Will attempt migration (Any information below is purely informational)
• midisnoop/riscv64 (0.1.2+git20141108.bc30f600187e-1 to 0.1.2+git20141108.bc30f600187e-1)
  • Migration status for midisnoop/riscv64 (0.1.2+git20141108.bc30f600187e-1 to 0.1.2+git20141108.bc30f600187e-1): Will attempt migration (Any information below is purely informational)
• minc-tools/riscv64 (2.3.00+dfsg-10 to 2.3.00+dfsg-10)
  • Migration status for minc-tools/riscv64 (2.3.00+dfsg-10 to 2.3.00+dfsg-10): Will attempt migration (Any information below is purely informational)
• minitube/riscv64 (3.9.3-2 to 3.9.3-2)
  • Migration status for minitube/riscv64 (3.9.3-2 to 3.9.3-2): Will attempt migration (Any information below is purely informational)
• minuet/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for minuet/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• mirage/riscv64 (0.11.2-1 to 0.11.2-1)
  • Migration status for mirage/riscv64 (0.11.2-1 to 0.11.2-1): Will attempt migration (Any information below is purely informational)
• missingh/riscv64 (1.6.0.1-1 to 1.6.0.1-1)
  • Migration status for missingh/riscv64 (1.6.0.1-1 to 1.6.0.1-1): Will attempt migration (Any information below is purely informational)
• mod-mime-xattr/riscv64 (0.4-8 to 0.4-8)
  • Migration status for mod-mime-xattr/riscv64 (0.4-8 to 0.4-8): Will attempt migration (Any information below is purely informational)
• mod-vhost-ldap/riscv64 (2.4.0-1 to 2.4.0-1)
  • Migration status for mod-vhost-ldap/riscv64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
• mod-wsgi/riscv64 (5.0.0-1 to 5.0.0-1)
  • Migration status for mod-wsgi/riscv64 (5.0.0-1 to 5.0.0-1): Will attempt migration (Any information below is purely informational)
• modemmanager-qt/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for modemmanager-qt/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• mokomaze/riscv64 (0.7.1-1 to 0.7.1-1)
  • Migration status for mokomaze/riscv64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• molequeue/riscv64 (0.9.0-1 to 0.9.0-1)
  • Migration status for molequeue/riscv64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• monado/riscv64 (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2)
  • Migration status for monado/riscv64 (21.0.0+git2905.e26a272c1~dfsg1-2 to 21.0.0+git2905.e26a272c1~dfsg1-2): Will attempt migration (Any information below is purely informational)
• mongrel2/riscv64 (1.12.2-3 to 1.12.2-3)
  • Migration status for mongrel2/riscv64 (1.12.2-3 to 1.12.2-3): Will attempt migration (Any information below is purely informational)
• morris/riscv64 (0.3-1 to 0.3-1)
  • Migration status for morris/riscv64 (0.3-1 to 0.3-1): Will attempt migration (Any information below is purely informational)
• mosh/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for mosh/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• mousepad/riscv64 (0.6.2-1 to 0.6.2-1)
  • Migration status for mousepad/riscv64 (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
• mousetrap/riscv64 (1.0c-2 to 1.0c-2)
  • Migration status for mousetrap/riscv64 (1.0c-2 to 1.0c-2): Will attempt migration (Any information below is purely informational)
• mousetweaks/riscv64 (3.32.0-4 to 3.32.0-4)
  • Migration status for mousetweaks/riscv64 (3.32.0-4 to 3.32.0-4): Will attempt migration (Any information below is purely informational)
• movit/riscv64 (1.7.1-1 to 1.7.1-1)
  • Migration status for movit/riscv64 (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
• mp3diags/riscv64 (1.5.01-2 to 1.5.01-2)
  • Migration status for mp3diags/riscv64 (1.5.01-2 to 1.5.01-2): Will attempt migration (Any information below is purely informational)
• mp3splt/riscv64 (2.6.2+20170630-3.2 to 2.6.2+20170630-3.2)
  • Migration status for mp3splt/riscv64 (2.6.2+20170630-3.2 to 2.6.2+20170630-3.2): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• mpm-itk/riscv64 (2.4.7-04-1 to 2.4.7-04-1)
  • Migration status for mpm-itk/riscv64 (2.4.7-04-1 to 2.4.7-04-1): Will attempt migration (Any information below is purely informational)
• mpsolve/riscv64 (3.2.1-10.1 to 3.2.1-10.1)
  • Migration status for mpsolve/riscv64 (3.2.1-10.1 to 3.2.1-10.1): Will attempt migration (Any information below is purely informational)
• mpv/riscv64 (0.38.0-1 to 0.38.0-1)
  • Migration status for mpv/riscv64 (0.38.0-1 to 0.38.0-1): Will attempt migration (Any information below is purely informational)
• mrbayes/riscv64 (3.2.7a-7 to 3.2.7a-7)
  • Migration status for mrbayes/riscv64 (3.2.7a-7 to 3.2.7a-7): Will attempt migration (Any information below is purely informational)
• mrmpi/riscv64 (1.0~20140404-3 to 1.0~20140404-3)
  • Migration status for mrmpi/riscv64 (1.0~20140404-3 to 1.0~20140404-3): Will attempt migration (Any information below is purely informational)
• msi-keyboard/riscv64 (1.1-2 to 1.1-2)
  • Migration status for msi-keyboard/riscv64 (1.1-2 to 1.1-2): Will attempt migration (Any information below is purely informational)
• msitools/riscv64 (0.103+repack-1 to 0.103+repack-1)
  • Migration status for msitools/riscv64 (0.103+repack-1 to 0.103+repack-1): Will attempt migration (Any information below is purely informational)
• mssh/riscv64 (2.2-5.1 to 2.2-5.1)
  • Migration status for mssh/riscv64 (2.2-5.1 to 2.2-5.1): Will attempt migration (Any information below is purely informational)
• mtr/riscv64 (0.95-1.1 to 0.95-1.1)
  • Migration status for mtr/riscv64 (0.95-1.1 to 0.95-1.1): Will attempt migration (Any information below is purely informational)
• mu-cade/riscv64 (0.11.dfsg1-13 to 0.11.dfsg1-13)
  • Migration status for mu-cade/riscv64 (0.11.dfsg1-13 to 0.11.dfsg1-13): Will attempt migration (Any information below is purely informational)
• mudita24/riscv64 (1.0.3+svn13-7 to 1.0.3+svn13-7)
  • Migration status for mudita24/riscv64 (1.0.3+svn13-7 to 1.0.3+svn13-7): Will attempt migration (Any information below is purely informational)
• muffin/riscv64 (6.0.1-3 to 6.0.1-3)
  • Migration status for muffin/riscv64 (6.0.1-3 to 6.0.1-3): Will attempt migration (Any information below is purely informational)
• mumps/riscv64 (5.6.2-2.1 to 5.6.2-2.1)
  • Migration status for mumps/riscv64 (5.6.2-2.1 to 5.6.2-2.1): Will attempt migration (Any information below is purely informational)
• munipack/riscv64 (0.6.1-1 to 0.6.1-1)
  • Migration status for munipack/riscv64 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• murasaki/riscv64 (1.68.6-13 to 1.68.6-13)
  • Migration status for murasaki/riscv64 (1.68.6-13 to 1.68.6-13): Will attempt migration (Any information below is purely informational)
• muse/riscv64 (4.2.1-1 to 4.2.1-1)
  • Migration status for muse/riscv64 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• musescore-sftools/riscv64 (20201011-1 to 20201011-1)
  • Migration status for musescore-sftools/riscv64 (20201011-1 to 20201011-1): Will attempt migration (Any information below is purely informational)
• musescore2/riscv64 (2.3.2+dfsg4-15 to 2.3.2+dfsg4-15)
  • Migration status for musescore2/riscv64 (2.3.2+dfsg4-15 to 2.3.2+dfsg4-15): Will attempt migration (Any information below is purely informational)
• mustang-plug/riscv64 (1.2-3 to 1.2-3)
  • Migration status for mustang-plug/riscv64 (1.2-3 to 1.2-3): Will attempt migration (Any information below is purely informational)
• mygui/riscv64 (3.4.2+dfsg-1.1 to 3.4.2+dfsg-1.1)
  • Migration status for mygui/riscv64 (3.4.2+dfsg-1.1 to 3.4.2+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• mypaint/riscv64 (2.0.1-10 to 2.0.1-10)
  • Migration status for mypaint/riscv64 (2.0.1-10 to 2.0.1-10): Will attempt migration (Any information below is purely informational)
• mysecureshell/riscv64 (2.0-2 to 2.0-2)
  • Migration status for mysecureshell/riscv64 (2.0-2 to 2.0-2): Will attempt migration (Any information below is purely informational)
• mystiq/riscv64 (20.03.23-3 to 20.03.23-3)
  • Migration status for mystiq/riscv64 (20.03.23-3 to 20.03.23-3): Will attempt migration (Any information below is purely informational)
• nabi/riscv64 (1.0.1-2 to 1.0.1-2)
  • Migration status for nabi/riscv64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• naev/riscv64 (0.8.2-1 to 0.8.2-1)
  • Migration status for naev/riscv64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
• nautic/riscv64 (1.5-6 to 1.5-6)
  • Migration status for nautic/riscv64 (1.5-6 to 1.5-6): Will attempt migration (Any information below is purely informational)
• nautilus-share/riscv64 (0.7.5-0.3 to 0.7.5-0.3)
  • Migration status for nautilus-share/riscv64 (0.7.5-0.3 to 0.7.5-0.3): Will attempt migration (Any information below is purely informational)
• nd/riscv64 (0.8.2-8.1 to 0.8.2-8.1)
  • Migration status for nd/riscv64 (0.8.2-8.1 to 0.8.2-8.1): Will attempt migration (Any information below is purely informational)
• nemo/riscv64 (6.0.2-2 to 6.0.2-2)
  • Migration status for nemo/riscv64 (6.0.2-2 to 6.0.2-2): Will attempt migration (Any information below is purely informational)
• neon27/riscv64 (0.33.0-1.1 to 0.33.0-1.1)
  • Migration status for neon27/riscv64 (0.33.0-1.1 to 0.33.0-1.1): Will attempt migration (Any information below is purely informational)
• neovim-qt/riscv64 (0.2.18-1 to 0.2.18-1)
  • Migration status for neovim-qt/riscv64 (0.2.18-1 to 0.2.18-1): Will attempt migration (Any information below is purely informational)
• nestopia/riscv64 (1.52.1+dfsg-1 to 1.52.1+dfsg-1)
  • Migration status for nestopia/riscv64 (1.52.1+dfsg-1 to 1.52.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• netcdf-cxx/riscv64 (4.3.1-4 to 4.3.1-4)
  • Migration status for netcdf-cxx/riscv64 (4.3.1-4 to 4.3.1-4): Will attempt migration (Any information below is purely informational)
• netcdf-fortran/riscv64 (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3)
  • Migration status for netcdf-fortran/riscv64 (4.6.0+really4.5.4+ds-3 to 4.6.0+really4.5.4+ds-3): Will attempt migration (Any information below is purely informational)
• nethack/riscv64 (3.6.7-1 to 3.6.7-1)
  • Migration status for nethack/riscv64 (3.6.7-1 to 3.6.7-1): Will attempt migration (Any information below is purely informational)
• netmate/riscv64 (0.2.0-12 to 0.2.0-12)
  • Migration status for netmate/riscv64 (0.2.0-12 to 0.2.0-12): Will attempt migration (Any information below is purely informational)
• netpipe/riscv64 (3.7.2-9 to 3.7.2-9)
  • Migration status for netpipe/riscv64 (3.7.2-9 to 3.7.2-9): Will attempt migration (Any information below is purely informational)
• netrek-client-cow/riscv64 (3.3.2-1 to 3.3.2-1)
  • Migration status for netrek-client-cow/riscv64 (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
• network-manager-applet/riscv64 (1.36.0-1 to 1.36.0-1)
  • Migration status for network-manager-applet/riscv64 (1.36.0-1 to 1.36.0-1): Will attempt migration (Any information below is purely informational)
• network-manager-iodine/riscv64 (1.2.0-3.3 to 1.2.0-3.3)
  • Migration status for network-manager-iodine/riscv64 (1.2.0-3.3 to 1.2.0-3.3): Will attempt migration (Any information below is purely informational)
• network-manager-ssh/riscv64 (1.2.11-1.1 to 1.2.11-1.1)
  • Migration status for network-manager-ssh/riscv64 (1.2.11-1.1 to 1.2.11-1.1): Will attempt migration (Any information below is purely informational)
• network-manager-strongswan/riscv64 (1.6.0-3 to 1.6.0-3)
  • Migration status for network-manager-strongswan/riscv64 (1.6.0-3 to 1.6.0-3): Will attempt migration (Any information below is purely informational)
• networkmanager-qt/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for networkmanager-qt/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• neverball/riscv64 (1.6.0+git20180603-3 to 1.6.0+git20180603-3)
  • Migration status for neverball/riscv64 (1.6.0+git20180603-3 to 1.6.0+git20180603-3): Will attempt migration (Any information below is purely informational)
• nextpnr/riscv64 (0.7-1 to 0.7-1)
  • Migration status for nextpnr/riscv64 (0.7-1 to 0.7-1): Will attempt migration (Any information below is purely informational)
• nexus/riscv64 (4.4.3-6 to 4.4.3-6)
  • Migration status for nexus/riscv64 (4.4.3-6 to 4.4.3-6): Will attempt migration (Any information below is purely informational)
• nip2/riscv64 (8.9.1-1 to 8.9.1-1)
  • Migration status for nip2/riscv64 (8.9.1-1 to 8.9.1-1): Will attempt migration (Any information below is purely informational)
• nitrogen/riscv64 (1.6.1-2 to 1.6.1-2)
  • Migration status for nitrogen/riscv64 (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
• nitrokey-authenticator/riscv64 (1.2.4-2 to 1.2.4-2)
  • Migration status for nitrokey-authenticator/riscv64 (1.2.4-2 to 1.2.4-2): Will attempt migration (Any information below is purely informational)
• nixnote2/riscv64 (2.1.10+dfsg1-2 to 2.1.10+dfsg1-2)
  • Migration status for nixnote2/riscv64 (2.1.10+dfsg1-2 to 2.1.10+dfsg1-2): Will attempt migration (Any information below is purely informational)
• njplot/riscv64 (2.4-9 to 2.4-9)
  • Migration status for njplot/riscv64 (2.4-9 to 2.4-9): Will attempt migration (Any information below is purely informational)
• nlkt/riscv64 (0.3.2.6-2.1 to 0.3.2.6-2.1)
  • Migration status for nlkt/riscv64 (0.3.2.6-2.1 to 0.3.2.6-2.1): Will attempt migration (Any information below is purely informational)
• nm-tray/riscv64 (0.5.0-2 to 0.5.0-2)
  • Migration status for nm-tray/riscv64 (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• noblenote/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for noblenote/riscv64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• node-opencv/riscv64 (7.0.0+git20200316.f0a03a4b-1 to 7.0.0+git20200316.f0a03a4b-1)
  • Migration status for node-opencv/riscv64 (7.0.0+git20200316.f0a03a4b-1 to 7.0.0+git20200316.f0a03a4b-1): Will attempt migration (Any information below is purely informational)
• node-shiny-server/riscv64 (1.5.20.1002-2 to 1.5.20.1002-2)
  • Migration status for node-shiny-server/riscv64 (1.5.20.1002-2 to 1.5.20.1002-2): Will attempt migration (Any information below is purely informational)
• node-xterm_pu (5.3.0-3 to 3.8.1+~cs0.9.0-1+deb12u1)
  • Migration status for node-xterm_pu (5.3.0-3 to 3.8.1+~cs0.9.0-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: node-xterm is newer in the target suite (5.3.0-3 3.8.1+~cs0.9.0-1+deb12u1)
• norm/riscv64 (1.5.9+dfsg-3.1 to 1.5.9+dfsg-3.1)
  • Migration status for norm/riscv64 (1.5.9+dfsg-3.1 to 1.5.9+dfsg-3.1): Will attempt migration (Any information below is purely informational)
• notification-daemon/riscv64 (3.20.0-4 to 3.20.0-4)
  • Migration status for notification-daemon/riscv64 (3.20.0-4 to 3.20.0-4): Will attempt migration (Any information below is purely informational)
• nss-tls/riscv64 (1.1-3 to 1.1-3)
  • Migration status for nss-tls/riscv64 (1.1-3 to 1.1-3): Will attempt migration (Any information below is purely informational)
• nsxiv/riscv64 (32-1 to 32-1)
  • Migration status for nsxiv/riscv64 (32-1 to 32-1): Will attempt migration (Any information below is purely informational)
• nted/riscv64 (1.10.18-13 to 1.10.18-13)
  • Migration status for nted/riscv64 (1.10.18-13 to 1.10.18-13): Will attempt migration (Any information below is purely informational)
• ntfs-3g_pu (1:2022.10.3-4 to 1:2022.10.3-1+deb12u1)
  • Migration status for ntfs-3g_pu (1:2022.10.3-4 to 1:2022.10.3-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: ntfs-3g is newer in the target suite (1:2022.10.3-4 1:2022.10.3-1+deb12u1)
• numptyphysics/riscv64 (0.3.10-0.2 to 0.3.10-0.2)
  • Migration status for numptyphysics/riscv64 (0.3.10-0.2 to 0.3.10-0.2): Will attempt migration (Any information below is purely informational)
• nuntius-linux/riscv64 (0.2.0-5 to 0.2.0-5)
  • Migration status for nuntius-linux/riscv64 (0.2.0-5 to 0.2.0-5): Will attempt migration (Any information below is purely informational)
• nwchem/riscv64 (7.2.2-2 to 7.2.2-2)
  • Migration status for nwchem/riscv64 (7.2.2-2 to 7.2.2-2): Will attempt migration (Any information below is purely informational)
• nwg-bar/riscv64 (0.1.6-1 to 0.1.6-1)
  • Migration status for nwg-bar/riscv64 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• nx-libs/riscv64 (2:3.5.99.27-1.1 to 2:3.5.99.27-1.1)
  • Migration status for nx-libs/riscv64 (2:3.5.99.27-1.1 to 2:3.5.99.27-1.1): Will attempt migration (Any information below is purely informational)
• nzbget/riscv64 (21.0+dfsg-4 to 21.0+dfsg-4)
  • Migration status for nzbget/riscv64 (21.0+dfsg-4 to 21.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• oar/riscv64 (2.5.10-2 to 2.5.10-2)
  • Migration status for oar/riscv64 (2.5.10-2 to 2.5.10-2): Will attempt migration (Any information below is purely informational)
• oasis3/riscv64 (3.mct+dfsg.121022-16 to 3.mct+dfsg.121022-16)
  • Migration status for oasis3/riscv64 (3.mct+dfsg.121022-16 to 3.mct+dfsg.121022-16): Will attempt migration (Any information below is purely informational)
• obconf/riscv64 (1:2.0.4+git20150213-3 to 1:2.0.4+git20150213-3)
  • Migration status for obconf/riscv64 (1:2.0.4+git20150213-3 to 1:2.0.4+git20150213-3): Will attempt migration (Any information below is purely informational)
• obsession/riscv64 (20140608-2 to 20140608-2)
  • Migration status for obsession/riscv64 (20140608-2 to 20140608-2): Will attempt migration (Any information below is purely informational)
• ocaml-alcotest/amd64 (1.8.0-1 to 1.8.0-1)
  • Migration status for ocaml-alcotest/amd64 (1.8.0-1 to 1.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-alcotest/amd64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-alcotest/arm64 (1.8.0-1 to 1.8.0-1)
  • Migration status for ocaml-alcotest/arm64 (1.8.0-1 to 1.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-alcotest/arm64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-alcotest/armel (1.8.0-1 to 1.8.0-1)
  • Migration status for ocaml-alcotest/armel (1.8.0-1 to 1.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-alcotest/armel ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-alcotest/armhf (1.8.0-1 to 1.8.0-1)
  • Migration status for ocaml-alcotest/armhf (1.8.0-1 to 1.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-alcotest/armhf ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-alcotest/i386 (1.8.0-1 to 1.8.0-1)
  • Migration status for ocaml-alcotest/i386 (1.8.0-1 to 1.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-alcotest/i386 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-alcotest/mips64el (1.8.0-1 to 1.8.0-1)
  • Migration status for ocaml-alcotest/mips64el (1.8.0-1 to 1.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-alcotest/mips64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-alcotest/ppc64el (1.8.0-1 to 1.8.0-1)
  • Migration status for ocaml-alcotest/ppc64el (1.8.0-1 to 1.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-alcotest/ppc64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-alcotest/riscv64 (1.8.0-1 to 1.8.0-1)
  • Migration status for ocaml-alcotest/riscv64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-alcotest/s390x (1.8.0-1 to 1.8.0-1)
  • Migration status for ocaml-alcotest/s390x (1.8.0-1 to 1.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-alcotest/s390x ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-atd/amd64 (2.15.0-2 to 2.15.0-2)
  • Migration status for ocaml-atd/amd64 (2.15.0-2 to 2.15.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-atd/amd64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-atd/arm64 (2.15.0-2 to 2.15.0-2)
  • Migration status for ocaml-atd/arm64 (2.15.0-2 to 2.15.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-atd/arm64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-atd/armel (2.15.0-2 to 2.15.0-2)
  • Migration status for ocaml-atd/armel (2.15.0-2 to 2.15.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-atd/armel ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-atd/armhf (2.15.0-2 to 2.15.0-2)
  • Migration status for ocaml-atd/armhf (2.15.0-2 to 2.15.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-atd/armhf ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-atd/i386 (2.15.0-2 to 2.15.0-2)
  • Migration status for ocaml-atd/i386 (2.15.0-2 to 2.15.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-atd/i386 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-atd/mips64el (2.15.0-2 to 2.15.0-2)
  • Migration status for ocaml-atd/mips64el (2.15.0-2 to 2.15.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-atd/mips64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-atd/ppc64el (2.15.0-2 to 2.15.0-2)
  • Migration status for ocaml-atd/ppc64el (2.15.0-2 to 2.15.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-atd/ppc64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-atd/riscv64 (2.15.0-2 to 2.15.0-2)
  • Migration status for ocaml-atd/riscv64 (2.15.0-2 to 2.15.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-atd/s390x (2.15.0-2 to 2.15.0-2)
  • Migration status for ocaml-atd/s390x (2.15.0-2 to 2.15.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-atd/s390x ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-augeas/riscv64 (0.6-1 to 0.6-1)
  • Migration status for ocaml-augeas/riscv64 (0.6-1 to 0.6-1): Will attempt migration (Any information below is purely informational)
• ocaml-duppy/amd64 (0.9.4-1 to 0.9.4-1)
  • Migration status for ocaml-duppy/amd64 (0.9.4-1 to 0.9.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-duppy/amd64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-duppy/arm64 (0.9.4-1 to 0.9.4-1)
  • Migration status for ocaml-duppy/arm64 (0.9.4-1 to 0.9.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-duppy/arm64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-duppy/armel (0.9.4-1 to 0.9.4-1)
  • Migration status for ocaml-duppy/armel (0.9.4-1 to 0.9.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-duppy/armel ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-duppy/armhf (0.9.4-1 to 0.9.4-1)
  • Migration status for ocaml-duppy/armhf (0.9.4-1 to 0.9.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-duppy/armhf ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-duppy/i386 (0.9.4-1 to 0.9.4-1)
  • Migration status for ocaml-duppy/i386 (0.9.4-1 to 0.9.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-duppy/i386 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-duppy/mips64el (0.9.4-1 to 0.9.4-1)
  • Migration status for ocaml-duppy/mips64el (0.9.4-1 to 0.9.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-duppy/mips64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-duppy/ppc64el (0.9.4-1 to 0.9.4-1)
  • Migration status for ocaml-duppy/ppc64el (0.9.4-1 to 0.9.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-duppy/ppc64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-duppy/riscv64 (0.9.4-1 to 0.9.4-1)
  • Migration status for ocaml-duppy/riscv64 (0.9.4-1 to 0.9.4-1): Will attempt migration (Any information below is purely informational)
• ocaml-duppy/s390x (0.9.4-1 to 0.9.4-1)
  • Migration status for ocaml-duppy/s390x (0.9.4-1 to 0.9.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-duppy/s390x ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-expect/amd64 (0.0.6-4 to 0.0.6-4)
  • Migration status for ocaml-expect/amd64 (0.0.6-4 to 0.0.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-expect/amd64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-expect/arm64 (0.0.6-4 to 0.0.6-4)
  • Migration status for ocaml-expect/arm64 (0.0.6-4 to 0.0.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-expect/arm64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-expect/armel (0.0.6-4 to 0.0.6-4)
  • Migration status for ocaml-expect/armel (0.0.6-4 to 0.0.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-expect/armel ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-expect/armhf (0.0.6-4 to 0.0.6-4)
  • Migration status for ocaml-expect/armhf (0.0.6-4 to 0.0.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-expect/armhf ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-expect/i386 (0.0.6-4 to 0.0.6-4)
  • Migration status for ocaml-expect/i386 (0.0.6-4 to 0.0.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-expect/i386 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-expect/mips64el (0.0.6-4 to 0.0.6-4)
  • Migration status for ocaml-expect/mips64el (0.0.6-4 to 0.0.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-expect/mips64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-expect/ppc64el (0.0.6-4 to 0.0.6-4)
  • Migration status for ocaml-expect/ppc64el (0.0.6-4 to 0.0.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-expect/ppc64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-expect/riscv64 (0.0.6-4 to 0.0.6-4)
  • Migration status for ocaml-expect/riscv64 (0.0.6-4 to 0.0.6-4): Will attempt migration (Any information below is purely informational)
• ocaml-expect/s390x (0.0.6-4 to 0.0.6-4)
  • Migration status for ocaml-expect/s390x (0.0.6-4 to 0.0.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-expect/s390x ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-gavl/riscv64 (0.1.6-2 to 0.1.6-2)
  • Migration status for ocaml-gavl/riscv64 (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• ocaml-gstreamer/riscv64 (0.3.1-4 to 0.3.1-4)
  • Migration status for ocaml-gstreamer/riscv64 (0.3.1-4 to 0.3.1-4): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/amd64 (1.2-7 to 1.2-7)
  • Migration status for ocaml-inifiles/amd64 (1.2-7 to 1.2-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-inifiles/amd64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-inifiles/arm64 (1.2-7 to 1.2-7)
  • Migration status for ocaml-inifiles/arm64 (1.2-7 to 1.2-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-inifiles/arm64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-inifiles/armel (1.2-7 to 1.2-7)
  • Migration status for ocaml-inifiles/armel (1.2-7 to 1.2-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-inifiles/armel ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-inifiles/armhf (1.2-7 to 1.2-7)
  • Migration status for ocaml-inifiles/armhf (1.2-7 to 1.2-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-inifiles/armhf ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-inifiles/i386 (1.2-7 to 1.2-7)
  • Migration status for ocaml-inifiles/i386 (1.2-7 to 1.2-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-inifiles/i386 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-inifiles/mips64el (1.2-7 to 1.2-7)
  • Migration status for ocaml-inifiles/mips64el (1.2-7 to 1.2-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-inifiles/mips64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-inifiles/ppc64el (1.2-7 to 1.2-7)
  • Migration status for ocaml-inifiles/ppc64el (1.2-7 to 1.2-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-inifiles/ppc64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-inifiles/riscv64 (1.2-7 to 1.2-7)
  • Migration status for ocaml-inifiles/riscv64 (1.2-7 to 1.2-7): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/s390x (1.2-7 to 1.2-7)
  • Migration status for ocaml-inifiles/s390x (1.2-7 to 1.2-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-inifiles/s390x ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-lastfm/amd64 (0.3.4-1 to 0.3.4-1)
  • Migration status for ocaml-lastfm/amd64 (0.3.4-1 to 0.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-lastfm/amd64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-lastfm/arm64 (0.3.4-1 to 0.3.4-1)
  • Migration status for ocaml-lastfm/arm64 (0.3.4-1 to 0.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-lastfm/arm64 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-lastfm/armel (0.3.4-1 to 0.3.4-1)
  • Migration status for ocaml-lastfm/armel (0.3.4-1 to 0.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-lastfm/armel ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-lastfm/armhf (0.3.4-1 to 0.3.4-1)
  • Migration status for ocaml-lastfm/armhf (0.3.4-1 to 0.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-lastfm/armhf ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-lastfm/i386 (0.3.4-1 to 0.3.4-1)
  • Migration status for ocaml-lastfm/i386 (0.3.4-1 to 0.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-lastfm/i386 ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-lastfm/mips64el (0.3.4-1 to 0.3.4-1)
  • Migration status for ocaml-lastfm/mips64el (0.3.4-1 to 0.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-lastfm/mips64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-lastfm/ppc64el (0.3.4-1 to 0.3.4-1)
  • Migration status for ocaml-lastfm/ppc64el (0.3.4-1 to 0.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-lastfm/ppc64el ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-lastfm/riscv64 (0.3.4-1 to 0.3.4-1)
  • Migration status for ocaml-lastfm/riscv64 (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
• ocaml-lastfm/s390x (0.3.4-1 to 0.3.4-1)
  • Migration status for ocaml-lastfm/s390x (0.3.4-1 to 0.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-lastfm/s390x ocaml-re (not considered)
    • Invalidated by dependency
• ocaml-libvirt/riscv64 (0.6.1.5-2 to 0.6.1.5-2)
  • Migration status for ocaml-libvirt/riscv64 (0.6.1.5-2 to 0.6.1.5-2): Will attempt migration (Any information below is purely informational)
• ocaml-logs/amd64 (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/amd64 (0.7.0-3 to 0.7.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/amd64 js-of-ocaml/amd64 (not considered)
    • Invalidated by dependency
• ocaml-logs/arm64 (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/arm64 (0.7.0-3 to 0.7.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/arm64 js-of-ocaml/arm64 (not considered)
    • Invalidated by dependency
• ocaml-logs/ppc64el (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/ppc64el (0.7.0-3 to 0.7.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/ppc64el js-of-ocaml/ppc64el (not considered)
    • Invalidated by dependency
• ocaml-logs/riscv64 (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/riscv64 (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-logs/s390x (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-logs/s390x (0.7.0-3 to 0.7.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-logs/s390x js-of-ocaml/s390x (not considered)
    • Invalidated by dependency
• ocaml-odoc/amd64 (2.4.2-3 to 2.4.2-3)
  • Migration status for ocaml-odoc/amd64 (2.4.2-3 to 2.4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-odoc/amd64 tyxml/amd64 (not considered)
    • Invalidated by dependency
• ocaml-odoc/arm64 (2.4.2-3 to 2.4.2-3)
  • Migration status for ocaml-odoc/arm64 (2.4.2-3 to 2.4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-odoc/arm64 tyxml/arm64 (not considered)
    • Invalidated by dependency
• ocaml-odoc/ppc64el (2.4.2-3 to 2.4.2-3)
  • Migration status for ocaml-odoc/ppc64el (2.4.2-3 to 2.4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-odoc/ppc64el tyxml/ppc64el (not considered)
    • Invalidated by dependency
• ocaml-odoc/riscv64 (2.4.2-3 to 2.4.2-3)
  • Migration status for ocaml-odoc/riscv64 (2.4.2-3 to 2.4.2-3): Will attempt migration (Any information below is purely informational)
• ocaml-odoc/s390x (2.4.2-3 to 2.4.2-3)
  • Migration status for ocaml-odoc/s390x (2.4.2-3 to 2.4.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocaml-odoc/s390x tyxml/s390x (not considered)
    • Invalidated by dependency
• ocamldap/amd64 (2.5.1-1 to 2.5.1-1)
  • Migration status for ocamldap/amd64 (2.5.1-1 to 2.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamldap/amd64 ocaml-re (not considered)
    • Invalidated by dependency
• ocamldap/arm64 (2.5.1-1 to 2.5.1-1)
  • Migration status for ocamldap/arm64 (2.5.1-1 to 2.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamldap/arm64 ocaml-re (not considered)
    • Invalidated by dependency
• ocamldap/armel (2.5.1-1 to 2.5.1-1)
  • Migration status for ocamldap/armel (2.5.1-1 to 2.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamldap/armel ocaml-re (not considered)
    • Invalidated by dependency
• ocamldap/armhf (2.5.1-1 to 2.5.1-1)
  • Migration status for ocamldap/armhf (2.5.1-1 to 2.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamldap/armhf ocaml-re (not considered)
    • Invalidated by dependency
• ocamldap/i386 (2.5.1-1 to 2.5.1-1)
  • Migration status for ocamldap/i386 (2.5.1-1 to 2.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamldap/i386 ocaml-re (not considered)
    • Invalidated by dependency
• ocamldap/mips64el (2.5.1-1 to 2.5.1-1)
  • Migration status for ocamldap/mips64el (2.5.1-1 to 2.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamldap/mips64el ocaml-re (not considered)
    • Invalidated by dependency
• ocamldap/ppc64el (2.5.1-1 to 2.5.1-1)
  • Migration status for ocamldap/ppc64el (2.5.1-1 to 2.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamldap/ppc64el ocaml-re (not considered)
    • Invalidated by dependency
• ocamldap/riscv64 (2.5.1-1 to 2.5.1-1)
  • Migration status for ocamldap/riscv64 (2.5.1-1 to 2.5.1-1): Will attempt migration (Any information below is purely informational)
• ocamldap/s390x (2.5.1-1 to 2.5.1-1)
  • Migration status for ocamldap/s390x (2.5.1-1 to 2.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamldap/s390x ocaml-re (not considered)
    • Invalidated by dependency
• ocamlformat/amd64 (0.26.2-1 to 0.26.2-1)
  • Migration status for ocamlformat/amd64 (0.26.2-1 to 0.26.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlformat/amd64 ocaml-re (not considered)
    • Invalidated by dependency
• ocamlformat/arm64 (0.26.2-1 to 0.26.2-1)
  • Migration status for ocamlformat/arm64 (0.26.2-1 to 0.26.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlformat/arm64 ocaml-re (not considered)
    • Invalidated by dependency
• ocamlformat/armel (0.26.2-1 to 0.26.2-1)
  • Migration status for ocamlformat/armel (0.26.2-1 to 0.26.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlformat/armel ocaml-re (not considered)
    • Invalidated by dependency
• ocamlformat/armhf (0.26.2-1 to 0.26.2-1)
  • Migration status for ocamlformat/armhf (0.26.2-1 to 0.26.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlformat/armhf ocaml-re (not considered)
    • Invalidated by dependency
• ocamlformat/i386 (0.26.2-1 to 0.26.2-1)
  • Migration status for ocamlformat/i386 (0.26.2-1 to 0.26.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlformat/i386 ocaml-re (not considered)
    • Invalidated by dependency
• ocamlformat/mips64el (0.26.2-1 to 0.26.2-1)
  • Migration status for ocamlformat/mips64el (0.26.2-1 to 0.26.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlformat/mips64el ocaml-re (not considered)
    • Invalidated by dependency
• ocamlformat/ppc64el (0.26.2-1 to 0.26.2-1)
  • Migration status for ocamlformat/ppc64el (0.26.2-1 to 0.26.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlformat/ppc64el ocaml-re (not considered)
    • Invalidated by dependency
• ocamlformat/riscv64 (0.26.2-1 to 0.26.2-1)
  • Migration status for ocamlformat/riscv64 (0.26.2-1 to 0.26.2-1): Will attempt migration (Any information below is purely informational)
• ocamlformat/s390x (0.26.2-1 to 0.26.2-1)
  • Migration status for ocamlformat/s390x (0.26.2-1 to 0.26.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlformat/s390x ocaml-re (not considered)
    • Invalidated by dependency
• oci-seccomp-bpf-hook/riscv64 (1.2.10+ds-1 to 1.2.10+ds-1)
  • Migration status for oci-seccomp-bpf-hook/riscv64 (1.2.10+ds-1 to 1.2.10+ds-1): Will attempt migration (Any information below is purely informational)
• octave-audio/riscv64 (2.0.8-2 to 2.0.8-2)
  • Migration status for octave-audio/riscv64 (2.0.8-2 to 2.0.8-2): Will attempt migration (Any information below is purely informational)
• octave-communications/riscv64 (1.2.6-2 to 1.2.6-2)
  • Migration status for octave-communications/riscv64 (1.2.6-2 to 1.2.6-2): Will attempt migration (Any information below is purely informational)
• octave-control/riscv64 (4.0.1-1 to 4.0.1-1)
  • Migration status for octave-control/riscv64 (4.0.1-1 to 4.0.1-1): Will attempt migration (Any information below is purely informational)
• octave-dicom/riscv64 (0.6.0-3 to 0.6.0-3)
  • Migration status for octave-dicom/riscv64 (0.6.0-3 to 0.6.0-3): Will attempt migration (Any information below is purely informational)
• octave-econometrics/riscv64 (1:1.1.2-4 to 1:1.1.2-4)
  • Migration status for octave-econometrics/riscv64 (1:1.1.2-4 to 1:1.1.2-4): Will attempt migration (Any information below is purely informational)
• octave-general/riscv64 (2.1.3-1 to 2.1.3-1)
  • Migration status for octave-general/riscv64 (2.1.3-1 to 2.1.3-1): Will attempt migration (Any information below is purely informational)
• octave-geometry/riscv64 (4.1.0-1 to 4.1.0-1)
  • Migration status for octave-geometry/riscv64 (4.1.0-1 to 4.1.0-1): Will attempt migration (Any information below is purely informational)
• octave-gsl/riscv64 (2.1.1-7 to 2.1.1-7)
  • Migration status for octave-gsl/riscv64 (2.1.1-7 to 2.1.1-7): Will attempt migration (Any information below is purely informational)
• octave-image-acquisition/riscv64 (0.2.2-7 to 0.2.2-7)
  • Migration status for octave-image-acquisition/riscv64 (0.2.2-7 to 0.2.2-7): Will attempt migration (Any information below is purely informational)
• octave-image/riscv64 (2.14.0-5 to 2.14.0-5)
  • Migration status for octave-image/riscv64 (2.14.0-5 to 2.14.0-5): Will attempt migration (Any information below is purely informational)
• octave-instrument-control/riscv64 (0.9.3-1 to 0.9.3-1)
  • Migration status for octave-instrument-control/riscv64 (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
• octave-interval/riscv64 (3.2.1-6 to 3.2.1-6)
  • Migration status for octave-interval/riscv64 (3.2.1-6 to 3.2.1-6): Will attempt migration (Any information below is purely informational)
• octave-io/riscv64 (2.6.4-3 to 2.6.4-3)
  • Migration status for octave-io/riscv64 (2.6.4-3 to 2.6.4-3): Will attempt migration (Any information below is purely informational)
• octave-lssa/riscv64 (0.1.4-2 to 0.1.4-2)
  • Migration status for octave-lssa/riscv64 (0.1.4-2 to 0.1.4-2): Will attempt migration (Any information below is purely informational)
• octave-ltfat/riscv64 (2.6.0+dfsg-6 to 2.6.0+dfsg-6)
  • Migration status for octave-ltfat/riscv64 (2.6.0+dfsg-6 to 2.6.0+dfsg-6): Will attempt migration (Any information below is purely informational)
• octave-mapping/riscv64 (1.4.2-3 to 1.4.2-3)
  • Migration status for octave-mapping/riscv64 (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
• octave-nan/riscv64 (3.7.0-4 to 3.7.0-4)
  • Migration status for octave-nan/riscv64 (3.7.0-4 to 3.7.0-4): Will attempt migration (Any information below is purely informational)
• octave-netcdf/riscv64 (1.0.17-2 to 1.0.17-2)
  • Migration status for octave-netcdf/riscv64 (1.0.17-2 to 1.0.17-2): Will attempt migration (Any information below is purely informational)
• octave-nurbs/riscv64 (1.4.3-3 to 1.4.3-3)
  • Migration status for octave-nurbs/riscv64 (1.4.3-3 to 1.4.3-3): Will attempt migration (Any information below is purely informational)
• octave-octclip/riscv64 (2.0.3-1 to 2.0.3-1)
  • Migration status for octave-octclip/riscv64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• octave-octproj/riscv64 (3.0.2-1 to 3.0.2-1)
  • Migration status for octave-octproj/riscv64 (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
• octave-optim/riscv64 (1.6.2-3 to 1.6.2-3)
  • Migration status for octave-optim/riscv64 (1.6.2-3 to 1.6.2-3): Will attempt migration (Any information below is purely informational)
• octave-optiminterp/riscv64 (0.3.7-3 to 0.3.7-3)
  • Migration status for octave-optiminterp/riscv64 (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• octave-parallel/riscv64 (4.0.2-1 to 4.0.2-1)
  • Migration status for octave-parallel/riscv64 (4.0.2-1 to 4.0.2-1): Will attempt migration (Any information below is purely informational)
• octave-quaternion/riscv64 (2.4.0-10 to 2.4.0-10)
  • Migration status for octave-quaternion/riscv64 (2.4.0-10 to 2.4.0-10): Will attempt migration (Any information below is purely informational)
• octave-secs2d/riscv64 (0.0.8-16 to 0.0.8-16)
  • Migration status for octave-secs2d/riscv64 (0.0.8-16 to 0.0.8-16): Will attempt migration (Any information below is purely informational)
• octave-signal/riscv64 (1.4.5-2 to 1.4.5-2)
  • Migration status for octave-signal/riscv64 (1.4.5-2 to 1.4.5-2): Will attempt migration (Any information below is purely informational)
• octave-sockets/riscv64 (1.4.1-4 to 1.4.1-4)
  • Migration status for octave-sockets/riscv64 (1.4.1-4 to 1.4.1-4): Will attempt migration (Any information below is purely informational)
• octave-sparsersb/riscv64 (1.0.9-7 to 1.0.9-7)
  • Migration status for octave-sparsersb/riscv64 (1.0.9-7 to 1.0.9-7): Will attempt migration (Any information below is purely informational)
• octave-strings/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for octave-strings/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• octave-struct/riscv64 (1.0.18-3 to 1.0.18-3)
  • Migration status for octave-struct/riscv64 (1.0.18-3 to 1.0.18-3): Will attempt migration (Any information below is purely informational)
• octave-vibes/riscv64 (0.2.0-9 to 0.2.0-9)
  • Migration status for octave-vibes/riscv64 (0.2.0-9 to 0.2.0-9): Will attempt migration (Any information below is purely informational)
• octave-video/riscv64 (2.1.1-3 to 2.1.1-3)
  • Migration status for octave-video/riscv64 (2.1.1-3 to 2.1.1-3): Will attempt migration (Any information below is purely informational)
• octave-zeromq/riscv64 (1.5.6-4 to 1.5.6-4)
  • Migration status for octave-zeromq/riscv64 (1.5.6-4 to 1.5.6-4): Will attempt migration (Any information below is purely informational)
• odc/riscv64 (1.5.2-1 to 1.5.2-1)
  • Migration status for odc/riscv64 (1.5.2-1 to 1.5.2-1): Will attempt migration (Any information below is purely informational)
• odr-padenc/riscv64 (3.0.0-2 to 3.0.0-2)
  • Migration status for odr-padenc/riscv64 (3.0.0-2 to 3.0.0-2): Will attempt migration (Any information below is purely informational)
• ogre-1.12/riscv64 (1.12.10+dfsg2-6 to 1.12.10+dfsg2-6)
  • Migration status for ogre-1.12/riscv64 (1.12.10+dfsg2-6 to 1.12.10+dfsg2-6): Will attempt migration (Any information below is purely informational)
• okular/riscv64 (4:23.08.1-2 to 4:23.08.1-2)
  • Migration status for okular/riscv64 (4:23.08.1-2 to 4:23.08.1-2): Will attempt migration (Any information below is purely informational)
• onscripter/riscv64 (20220816-1 to 20220816-1)
  • Migration status for onscripter/riscv64 (20220816-1 to 20220816-1): Will attempt migration (Any information below is purely informational)
• open-coarrays/riscv64 (2.10.2+ds-2.1 to 2.10.2+ds-2.1)
  • Migration status for open-coarrays/riscv64 (2.10.2+ds-2.1 to 2.10.2+ds-2.1): Will attempt migration (Any information below is purely informational)
• openarena/riscv64 (0.8.8+dfsg-7 to 0.8.8+dfsg-7)
  • Migration status for openarena/riscv64 (0.8.8+dfsg-7 to 0.8.8+dfsg-7): Will attempt migration (Any information below is purely informational)
• openbox/riscv64 (3.6.1-12 to 3.6.1-12)
  • Migration status for openbox/riscv64 (3.6.1-12 to 3.6.1-12): Will attempt migration (Any information below is purely informational)
• opencfu/riscv64 (4.0.0+dfsg-2 to 4.0.0+dfsg-2)
  • Migration status for opencfu/riscv64 (4.0.0+dfsg-2 to 4.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• opencity/riscv64 (0.0.6.5stable-5 to 0.0.6.5stable-5)
  • Migration status for opencity/riscv64 (0.0.6.5stable-5 to 0.0.6.5stable-5): Will attempt migration (Any information below is purely informational)
• opencl-clang-17/riscv64 (17.0.0-3 to 17.0.0-3)
  • Migration status for opencl-clang-17/riscv64 (17.0.0-3 to 17.0.0-3): Will attempt migration (Any information below is purely informational)
• openclonk/riscv64 (8.1-4 to 8.1-4)
  • Migration status for openclonk/riscv64 (8.1-4 to 8.1-4): Will attempt migration (Any information below is purely informational)
• opencsg/riscv64 (1.5.0-1 to 1.5.0-1)
  • Migration status for opencsg/riscv64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
• opendrop/riscv64 (3.3.1-6 to 3.3.1-6)
  • Migration status for opendrop/riscv64 (3.3.1-6 to 3.3.1-6): Will attempt migration (Any information below is purely informational)
• openhpi/riscv64 (3.8.0-2.2 to 3.8.0-2.2)
  • Migration status for openhpi/riscv64 (3.8.0-2.2 to 3.8.0-2.2): Will attempt migration (Any information below is purely informational)
• openmpi/riscv64 (4.1.6-13.3 to 4.1.6-13.3)
  • Migration status for openmpi/riscv64 (4.1.6-13.3 to 4.1.6-13.3): Will attempt migration (Any information below is purely informational)
• openmrac/riscv64 (1.2-3 to 1.2-3)
  • Migration status for openmrac/riscv64 (1.2-3 to 1.2-3): Will attempt migration (Any information below is purely informational)
• openms/riscv64 (2.6.0+cleaned1-4 to 2.6.0+cleaned1-4)
  • Migration status for openms/riscv64 (2.6.0+cleaned1-4 to 2.6.0+cleaned1-4): Will attempt migration (Any information below is purely informational)
• openmsx-catapult/riscv64 (19.0-1 to 19.0-1)
  • Migration status for openmsx-catapult/riscv64 (19.0-1 to 19.0-1): Will attempt migration (Any information below is purely informational)
• openmsx-debugger/riscv64 (0.1~git20230804-1 to 0.1~git20230804-1)
  • Migration status for openmsx-debugger/riscv64 (0.1~git20230804-1 to 0.1~git20230804-1): Will attempt migration (Any information below is purely informational)
• openmsx/riscv64 (19.1+dfsg-1 to 19.1+dfsg-1)
  • Migration status for openmsx/riscv64 (19.1+dfsg-1 to 19.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• openni-sensor-pointclouds/riscv64 (5.1.0.41.11-1 to 5.1.0.41.11-1)
  • Migration status for openni-sensor-pointclouds/riscv64 (5.1.0.41.11-1 to 5.1.0.41.11-1): Will attempt migration (Any information below is purely informational)
• openni-sensor-primesense/riscv64 (5.1.0.41-14 to 5.1.0.41-14)
  • Migration status for openni-sensor-primesense/riscv64 (5.1.0.41-14 to 5.1.0.41-14): Will attempt migration (Any information below is purely informational)
• openni/riscv64 (1.5.4.0+dfsg-7.1 to 1.5.4.0+dfsg-7.1)
  • Migration status for openni/riscv64 (1.5.4.0+dfsg-7.1 to 1.5.4.0+dfsg-7.1): Will attempt migration (Any information below is purely informational)
• openni2/riscv64 (2.2.0.33+dfsg-18 to 2.2.0.33+dfsg-18)
  • Migration status for openni2/riscv64 (2.2.0.33+dfsg-18 to 2.2.0.33+dfsg-18): Will attempt migration (Any information below is purely informational)
• openorienteering-mapper/riscv64 (0.9.5-3.1 to 0.9.5-3.1)
  • Migration status for openorienteering-mapper/riscv64 (0.9.5-3.1 to 0.9.5-3.1): Will attempt migration (Any information below is purely informational)
• openpref/riscv64 (0.1.3-3 to 0.1.3-3)
  • Migration status for openpref/riscv64 (0.1.3-3 to 0.1.3-3): Will attempt migration (Any information below is purely informational)
• openscenegraph/riscv64 (3.6.5+dfsg1-8 to 3.6.5+dfsg1-8)
  • Migration status for openscenegraph/riscv64 (3.6.5+dfsg1-8 to 3.6.5+dfsg1-8): Will attempt migration (Any information below is purely informational)
• openslide-python/riscv64 (1.3.1-2 to 1.3.1-2)
  • Migration status for openslide-python/riscv64 (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
• openslide/riscv64 (3.4.1+dfsg-7 to 3.4.1+dfsg-7)
  • Migration status for openslide/riscv64 (3.4.1+dfsg-7 to 3.4.1+dfsg-7): Will attempt migration (Any information below is purely informational)
• openssl_pu (3.3.2-1 to 3.0.14-1~deb12u2)
  • Migration status for openssl_pu (3.3.2-1 to 3.0.14-1~deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: openssl is newer in the target suite (3.3.2-1 3.0.14-1~deb12u2)
• openssn/riscv64 (1.4-4 to 1.4-4)
  • Migration status for openssn/riscv64 (1.4-4 to 1.4-4): Will attempt migration (Any information below is purely informational)
• openuniverse/riscv64 (1.0beta3.1+dfsg-7.1 to 1.0beta3.1+dfsg-7.1)
  • Migration status for openuniverse/riscv64 (1.0beta3.1+dfsg-7.1 to 1.0beta3.1+dfsg-7.1): Will attempt migration (Any information below is purely informational)
• openxr-sdk-source/riscv64 (1.0.20~dfsg1-1 to 1.0.20~dfsg1-1)
  • Migration status for openxr-sdk-source/riscv64 (1.0.20~dfsg1-1 to 1.0.20~dfsg1-1): Will attempt migration (Any information below is purely informational)
• openyahtzee/riscv64 (1.9.3-5 to 1.9.3-5)
  • Migration status for openyahtzee/riscv64 (1.9.3-5 to 1.9.3-5): Will attempt migration (Any information below is purely informational)
• ophcrack/riscv64 (3.8.0-3 to 3.8.0-3)
  • Migration status for ophcrack/riscv64 (3.8.0-3 to 3.8.0-3): Will attempt migration (Any information below is purely informational)
• orage/riscv64 (4.18.0-1 to 4.18.0-1)
  • Migration status for orage/riscv64 (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• orthanc-mysql/riscv64 (5.0+dfsg-1 to 5.0+dfsg-1)
  • Migration status for orthanc-mysql/riscv64 (5.0+dfsg-1 to 5.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• orthanc-neuro/riscv64 (1.1+dfsg-1 to 1.1+dfsg-1)
  • Migration status for orthanc-neuro/riscv64 (1.1+dfsg-1 to 1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• orthanc-postgresql/riscv64 (5.0+dfsg-2 to 5.0+dfsg-2)
  • Migration status for orthanc-postgresql/riscv64 (5.0+dfsg-2 to 5.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• orthanc-webviewer/riscv64 (2.9+dfsg-1 to 2.9+dfsg-1)
  • Migration status for orthanc-webviewer/riscv64 (2.9+dfsg-1 to 2.9+dfsg-1): Will attempt migration (Any information below is purely informational)
• os-autoinst/riscv64 (4.6.1712854180.1bf07142-4 to 4.6.1712854180.1bf07142-4)
  • Migration status for os-autoinst/riscv64 (4.6.1712854180.1bf07142-4 to 4.6.1712854180.1bf07142-4): Will attempt migration (Any information below is purely informational)
• osdlyrics/riscv64 (0.5.15+dfsg-2 to 0.5.15+dfsg-2)
  • Migration status for osdlyrics/riscv64 (0.5.15+dfsg-2 to 0.5.15+dfsg-2): Will attempt migration (Any information below is purely informational)
• osinfo-db-tools/riscv64 (1.11.0-1 to 1.11.0-1)
  • Migration status for osinfo-db-tools/riscv64 (1.11.0-1 to 1.11.0-1): Will attempt migration (Any information below is purely informational)
• osm-gps-map/riscv64 (1.2.0-2 to 1.2.0-2)
  • Migration status for osm-gps-map/riscv64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• osmcoastline/riscv64 (2.4.0-2 to 2.4.0-2)
  • Migration status for osmcoastline/riscv64 (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
• osmose-emulator/riscv64 (1.6-1 to 1.6-1)
  • Migration status for osmose-emulator/riscv64 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
• osra/riscv64 (2.1.3-3 to 2.1.3-3)
  • Migration status for osra/riscv64 (2.1.3-3 to 2.1.3-3): Will attempt migration (Any information below is purely informational)
• ostinato/riscv64 (1.3.0-1 to 1.3.0-1)
  • Migration status for ostinato/riscv64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• otf/riscv64 (1.12.5+dfsg-8 to 1.12.5+dfsg-8)
  • Migration status for otf/riscv64 (1.12.5+dfsg-8 to 1.12.5+dfsg-8): Will attempt migration (Any information below is purely informational)
• ots/riscv64 (0.5.0-9 to 0.5.0-9)
  • Migration status for ots/riscv64 (0.5.0-9 to 0.5.0-9): Will attempt migration (Any information below is purely informational)
• p4est/riscv64 (2.3.6-1 to 2.3.6-1)
  • Migration status for p4est/riscv64 (2.3.6-1 to 2.3.6-1): Will attempt migration (Any information below is purely informational)
• pacman-package-manager/riscv64 (6.0.2-6 to 6.0.2-6)
  • Migration status for pacman-package-manager/riscv64 (6.0.2-6 to 6.0.2-6): Will attempt migration (Any information below is purely informational)
• pairtools/riscv64 (1.0.3-1 to 1.0.3-1)
  • Migration status for pairtools/riscv64 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• palapeli/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for palapeli/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• pam-u2f/riscv64 (1.3.0-1 to 1.3.0-1)
  • Migration status for pam-u2f/riscv64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• pantomime/riscv64 (1.4.0+dfsg-2 to 1.4.0+dfsg-2)
  • Migration status for pantomime/riscv64 (1.4.0+dfsg-2 to 1.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• paprefs/riscv64 (1.2-1 to 1.2-1)
  • Migration status for paprefs/riscv64 (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• parmetis/riscv64 (4.0.3-7 to 4.0.3-7)
  • Migration status for parmetis/riscv64 (4.0.3-7 to 4.0.3-7): Will attempt migration (Any information below is purely informational)
• parole/riscv64 (4.18.1-1 to 4.18.1-1)
  • Migration status for parole/riscv64 (4.18.1-1 to 4.18.1-1): Will attempt migration (Any information below is purely informational)
• parolottero/riscv64 (1.0-1.1 to 1.0-1.1)
  • Migration status for parolottero/riscv64 (1.0-1.1 to 1.0-1.1): Will attempt migration (Any information below is purely informational)
• parsec47/riscv64 (0.2.dfsg1-9 to 0.2.dfsg1-9)
  • Migration status for parsec47/riscv64 (0.2.dfsg1-9 to 0.2.dfsg1-9): Will attempt migration (Any information below is purely informational)
• partitionmanager/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for partitionmanager/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• passenger/riscv64 (6.0.20+ds-1 to 6.0.20+ds-1)
  • Migration status for passenger/riscv64 (6.0.20+ds-1 to 6.0.20+ds-1): Will attempt migration (Any information below is purely informational)
• passwordsafe/riscv64 (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
  • Migration status for passwordsafe/riscv64 (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• pasystray/riscv64 (0.8.2-1 to 0.8.2-1)
  • Migration status for pasystray/riscv64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
• pavumeter/riscv64 (0.9.3-4 to 0.9.3-4)
  • Migration status for pavumeter/riscv64 (0.9.3-4 to 0.9.3-4): Will attempt migration (Any information below is purely informational)
• pax-britannica/riscv64 (1.0.0-5 to 1.0.0-5)
  • Migration status for pax-britannica/riscv64 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• pcmanfm/riscv64 (1.3.2-4 to 1.3.2-4)
  • Migration status for pcmanfm/riscv64 (1.3.2-4 to 1.3.2-4): Will attempt migration (Any information below is purely informational)
• pd-readanysf/riscv64 (0.43-6 to 0.43-6)
  • Migration status for pd-readanysf/riscv64 (0.43-6 to 0.43-6): Will attempt migration (Any information below is purely informational)
• pdf-presenter-console/riscv64 (4.6.0-3 to 4.6.0-3)
  • Migration status for pdf-presenter-console/riscv64 (4.6.0-3 to 4.6.0-3): Will attempt migration (Any information below is purely informational)
• pdf2djvu/amd64 (0.9.18.2-2.1 to 0.9.18.2-2.1)
  • Migration status for pdf2djvu/amd64 (0.9.18.2-2.1 to 0.9.18.2-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pdf2djvu/amd64 exiv2
• pdf2djvu/arm64 (0.9.18.2-2.1 to 0.9.18.2-2.1)
  • Migration status for pdf2djvu/arm64 (0.9.18.2-2.1 to 0.9.18.2-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pdf2djvu/arm64 exiv2
• pdf2djvu/armel (0.9.18.2-2.1 to 0.9.18.2-2.1)
  • Migration status for pdf2djvu/armel (0.9.18.2-2.1 to 0.9.18.2-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pdf2djvu/armel exiv2
• pdf2djvu/armhf (0.9.18.2-2.1 to 0.9.18.2-2.1)
  • Migration status for pdf2djvu/armhf (0.9.18.2-2.1 to 0.9.18.2-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pdf2djvu/armhf exiv2
• pdf2djvu/i386 (0.9.18.2-2.1 to 0.9.18.2-2.1)
  • Migration status for pdf2djvu/i386 (0.9.18.2-2.1 to 0.9.18.2-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pdf2djvu/i386 exiv2
• pdf2djvu/mips64el (0.9.18.2-2.1 to 0.9.18.2-2.1)
  • Migration status for pdf2djvu/mips64el (0.9.18.2-2.1 to 0.9.18.2-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pdf2djvu/mips64el exiv2
• pdf2djvu/ppc64el (0.9.18.2-2.1 to 0.9.18.2-2.1)
  • Migration status for pdf2djvu/ppc64el (0.9.18.2-2.1 to 0.9.18.2-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pdf2djvu/ppc64el exiv2
• pdf2djvu/s390x (0.9.18.2-2.1 to 0.9.18.2-2.1)
  • Migration status for pdf2djvu/s390x (0.9.18.2-2.1 to 0.9.18.2-2.1): Will attempt migration (Any information below is purely informational)
    • Depends: pdf2djvu/s390x exiv2
• pdfchain/riscv64 (1:0.4.4.2-2 to 1:0.4.4.2-2)
  • Migration status for pdfchain/riscv64 (1:0.4.4.2-2 to 1:0.4.4.2-2): Will attempt migration (Any information below is purely informational)
• pdfsandwich/riscv64 (0.1.7-2 to 0.1.7-2)
  • Migration status for pdfsandwich/riscv64 (0.1.7-2 to 0.1.7-2): Will attempt migration (Any information below is purely informational)
• pdp/riscv64 (1:0.14.1+darcs20180201-6 to 1:0.14.1+darcs20180201-6)
  • Migration status for pdp/riscv64 (1:0.14.1+darcs20180201-6 to 1:0.14.1+darcs20180201-6): Will attempt migration (Any information below is purely informational)
• pdsh/riscv64 (2.34-3 to 2.34-3)
  • Migration status for pdsh/riscv64 (2.34-3 to 2.34-3): Will attempt migration (Any information below is purely informational)
• peek/riscv64 (1.5.1+git20230114-1 to 1.5.1+git20230114-1)
  • Migration status for peek/riscv64 (1.5.1+git20230114-1 to 1.5.1+git20230114-1): Will attempt migration (Any information below is purely informational)
• peg-e/riscv64 (1.3.2-1 to 1.3.2-1)
  • Migration status for peg-e/riscv64 (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
• peg-solitaire/riscv64 (2.2-4 to 2.2-4)
  • Migration status for peg-solitaire/riscv64 (2.2-4 to 2.2-4): Will attempt migration (Any information below is purely informational)
• pekwm/riscv64 (0.1.18-1 to 0.1.18-1)
  • Migration status for pekwm/riscv64 (0.1.18-1 to 0.1.18-1): Will attempt migration (Any information below is purely informational)
• peony-extensions/riscv64 (3.2.4-1 to 3.2.4-1)
  • Migration status for peony-extensions/riscv64 (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
• peony/riscv64 (4.0.0.1-1 to 4.0.0.1-1)
  • Migration status for peony/riscv64 (4.0.0.1-1 to 4.0.0.1-1): Will attempt migration (Any information below is purely informational)
• peruse/riscv64 (1.80+dfsg-2 to 1.80+dfsg-2)
  • Migration status for peruse/riscv64 (1.80+dfsg-2 to 1.80+dfsg-2): Will attempt migration (Any information below is purely informational)
• pg-fact-loader/riscv64 (2.0.1-3 to 2.0.1-3)
  • Migration status for pg-fact-loader/riscv64 (2.0.1-3 to 2.0.1-3): Will attempt migration (Any information below is purely informational)
• pg-qualstats/riscv64 (2.1.0-1 to 2.1.0-1)
  • Migration status for pg-qualstats/riscv64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• pg-rage-terminator/riscv64 (0.1.7-9 to 0.1.7-9)
  • Migration status for pg-rage-terminator/riscv64 (0.1.7-9 to 0.1.7-9): Will attempt migration (Any information below is purely informational)
• pg-rational/riscv64 (0.0.2-6 to 0.0.2-6)
  • Migration status for pg-rational/riscv64 (0.0.2-6 to 0.0.2-6): Will attempt migration (Any information below is purely informational)
• pg-repack/riscv64 (1.5.0-1 to 1.5.0-1)
  • Migration status for pg-repack/riscv64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
• pg-roaringbitmap/riscv64 (0.5.4-2 to 0.5.4-2)
  • Migration status for pg-roaringbitmap/riscv64 (0.5.4-2 to 0.5.4-2): Will attempt migration (Any information below is purely informational)
• pg-similarity/riscv64 (1.0-7 to 1.0-7)
  • Migration status for pg-similarity/riscv64 (1.0-7 to 1.0-7): Will attempt migration (Any information below is purely informational)
• pg-snakeoil/riscv64 (1.4-1 to 1.4-1)
  • Migration status for pg-snakeoil/riscv64 (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• pg-stat-kcache/riscv64 (2.2.3-1 to 2.2.3-1)
  • Migration status for pg-stat-kcache/riscv64 (2.2.3-1 to 2.2.3-1): Will attempt migration (Any information below is purely informational)
• pgaudit-16/riscv64 (16.0-1 to 16.0-1)
  • Migration status for pgaudit-16/riscv64 (16.0-1 to 16.0-1): Will attempt migration (Any information below is purely informational)
• pgextwlist/riscv64 (1.17-2 to 1.17-2)
  • Migration status for pgextwlist/riscv64 (1.17-2 to 1.17-2): Will attempt migration (Any information below is purely informational)
• pgfincore/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for pgfincore/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• pgl-ddl-deploy/riscv64 (2.2.1-1 to 2.2.1-1)
  • Migration status for pgl-ddl-deploy/riscv64 (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
• pglogical/riscv64 (2.4.4-1 to 2.4.4-1)
  • Migration status for pglogical/riscv64 (2.4.4-1 to 2.4.4-1): Will attempt migration (Any information below is purely informational)
• pgmemcache/riscv64 (2.3.0-13 to 2.3.0-13)
  • Migration status for pgmemcache/riscv64 (2.3.0-13 to 2.3.0-13): Will attempt migration (Any information below is purely informational)
• pgn2web/riscv64 (0.4-3.1 to 0.4-3.1)
  • Migration status for pgn2web/riscv64 (0.4-3.1 to 0.4-3.1): Will attempt migration (Any information below is purely informational)
• pgocaml/amd64 (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/amd64 (4.4.0-1 to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libpgocaml-ocaml/4.4.0-1+b9/amd64 to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/amd64 uninstallable
    • migrating libpgocaml-ocaml-dev/4.4.0-1+b9/amd64 to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/amd64 uninstallable
    • Depends: pgocaml/amd64 calendar/amd64 (not considered)
    • Depends: pgocaml/amd64 ocaml-re (not considered)
• pgocaml/arm64 (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/arm64 (4.4.0-1 to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libpgocaml-ocaml/4.4.0-1+b9/arm64 to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/arm64 uninstallable
    • migrating libpgocaml-ocaml-dev/4.4.0-1+b9/arm64 to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/arm64 uninstallable
    • Depends: pgocaml/arm64 calendar/arm64 (not considered)
    • Depends: pgocaml/arm64 ocaml-re (not considered)
• pgocaml/armel (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/armel (4.4.0-1 to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libpgocaml-ocaml/4.4.0-1+b9/armel to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b16/armel uninstallable
    • migrating libpgocaml-ocaml-dev/4.4.0-1+b9/armel to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b16/armel uninstallable
    • Depends: pgocaml/armel calendar/armel (not considered)
    • Depends: pgocaml/armel ocaml-re (not considered)
• pgocaml/armhf (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/armhf (4.4.0-1 to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libpgocaml-ocaml/4.4.0-1+b9/armhf to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/armhf uninstallable
    • migrating libpgocaml-ocaml-dev/4.4.0-1+b9/armhf to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/armhf uninstallable
    • Depends: pgocaml/armhf calendar/armhf (not considered)
    • Depends: pgocaml/armhf ocaml-re (not considered)
• pgocaml/i386 (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/i386 (4.4.0-1 to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libpgocaml-ocaml/4.4.0-1+b9/i386 to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/i386 uninstallable
    • migrating libpgocaml-ocaml-dev/4.4.0-1+b9/i386 to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/i386 uninstallable
    • Depends: pgocaml/i386 calendar/i386 (not considered)
    • Depends: pgocaml/i386 ocaml-re (not considered)
• pgocaml/mips64el (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/mips64el (4.4.0-1 to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libpgocaml-ocaml/4.4.0-1+b9/mips64el to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b16/mips64el uninstallable
    • migrating libpgocaml-ocaml-dev/4.4.0-1+b9/mips64el to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b16/mips64el uninstallable
    • Depends: pgocaml/mips64el calendar/mips64el (not considered)
    • Depends: pgocaml/mips64el ocaml-re (not considered)
• pgocaml/ppc64el (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/ppc64el (4.4.0-1 to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libpgocaml-ocaml/4.4.0-1+b9/ppc64el to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/ppc64el uninstallable
    • migrating libpgocaml-ocaml-dev/4.4.0-1+b9/ppc64el to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/ppc64el uninstallable
    • Depends: pgocaml/ppc64el calendar/ppc64el (not considered)
    • Depends: pgocaml/ppc64el ocaml-re (not considered)
• pgocaml/riscv64 (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/riscv64 (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
• pgocaml/s390x (4.4.0-1 to 4.4.0-1)
  • Migration status for pgocaml/s390x (4.4.0-1 to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libpgocaml-ocaml/4.4.0-1+b9/s390x to testing makes libocsipersist-pgsql-ocaml/1.1.0-3+b18/s390x uninstallable
    • migrating libpgocaml-ocaml-dev/4.4.0-1+b9/s390x to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/s390x uninstallable
    • Depends: pgocaml/s390x calendar/s390x (not considered)
    • Depends: pgocaml/s390x ocaml-re (not considered)
• pgpcre/riscv64 (0.20190509-7 to 0.20190509-7)
  • Migration status for pgpcre/riscv64 (0.20190509-7 to 0.20190509-7): Will attempt migration (Any information below is purely informational)
• pgpointcloud/riscv64 (1.2.5-1 to 1.2.5-1)
  • Migration status for pgpointcloud/riscv64 (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
• pgsphere/riscv64 (1.5.1-1 to 1.5.1-1)
  • Migration status for pgsphere/riscv64 (1.5.1-1 to 1.5.1-1): Will attempt migration (Any information below is purely informational)
• pgsql-asn1oid/riscv64 (1.6-1 to 1.6-1)
  • Migration status for pgsql-asn1oid/riscv64 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
• pgsql-http/riscv64 (1.6.0-4 to 1.6.0-4)
  • Migration status for pgsql-http/riscv64 (1.6.0-4 to 1.6.0-4): Will attempt migration (Any information below is purely informational)
• phlipple/riscv64 (0.8.5-5.1 to 0.8.5-5.1)
  • Migration status for phlipple/riscv64 (0.8.5-5.1 to 0.8.5-5.1): Will attempt migration (Any information below is purely informational)
• phonon-backend-gstreamer/riscv64 (4:4.10.0-2 to 4:4.10.0-2)
  • Migration status for phonon-backend-gstreamer/riscv64 (4:4.10.0-2 to 4:4.10.0-2): Will attempt migration (Any information below is purely informational)
• phonon-backend-vlc/riscv64 (0.12.0-3 to 0.12.0-3)
  • Migration status for phonon-backend-vlc/riscv64 (0.12.0-3 to 0.12.0-3): Will attempt migration (Any information below is purely informational)
• phonon/riscv64 (4:4.12.0-3.1 to 4:4.12.0-3.1)
  • Migration status for phonon/riscv64 (4:4.12.0-3.1 to 4:4.12.0-3.1): Will attempt migration (Any information below is purely informational)
• phonopy/riscv64 (2.23.1-1 to 2.23.1-1)
  • Migration status for phonopy/riscv64 (2.23.1-1 to 2.23.1-1): Will attempt migration (Any information below is purely informational)
• photoflare/riscv64 (1.6.13-1 to 1.6.13-1)
  • Migration status for photoflare/riscv64 (1.6.13-1 to 1.6.13-1): Will attempt migration (Any information below is purely informational)
• photoqt/amd64 (4.6+ds-1 to 4.6+ds-1)
  • Migration status for photoqt/amd64 (4.6+ds-1 to 4.6+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: photoqt/amd64 exiv2
• photoqt/arm64 (4.6+ds-1 to 4.6+ds-1)
  • Migration status for photoqt/arm64 (4.6+ds-1 to 4.6+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: photoqt/arm64 exiv2
• photoqt/armel (4.6+ds-1 to 4.6+ds-1)
  • Migration status for photoqt/armel (4.6+ds-1 to 4.6+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: photoqt/armel exiv2
• photoqt/armhf (4.6+ds-1 to 4.6+ds-1)
  • Migration status for photoqt/armhf (4.6+ds-1 to 4.6+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: photoqt/armhf exiv2
• photoqt/mips64el (4.6+ds-1 to 4.6+ds-1)
  • Migration status for photoqt/mips64el (4.6+ds-1 to 4.6+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: photoqt/mips64el exiv2
• photoqt/ppc64el (4.6+ds-1 to 4.6+ds-1)
  • Migration status for photoqt/ppc64el (4.6+ds-1 to 4.6+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: photoqt/ppc64el exiv2
• photoqt/s390x (4.6+ds-1 to 4.6+ds-1)
  • Migration status for photoqt/s390x (4.6+ds-1 to 4.6+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: photoqt/s390x exiv2
• phototonic/amd64 (2.1-4 to 2.1-4)
  • Migration status for phototonic/amd64 (2.1-4 to 2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: phototonic/amd64 exiv2
• phototonic/arm64 (2.1-4 to 2.1-4)
  • Migration status for phototonic/arm64 (2.1-4 to 2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: phototonic/arm64 exiv2
• phototonic/armel (2.1-4 to 2.1-4)
  • Migration status for phototonic/armel (2.1-4 to 2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: phototonic/armel exiv2
• phototonic/armhf (2.1-4 to 2.1-4)
  • Migration status for phototonic/armhf (2.1-4 to 2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: phototonic/armhf exiv2
• phototonic/i386 (2.1-4 to 2.1-4)
  • Migration status for phototonic/i386 (2.1-4 to 2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: phototonic/i386 exiv2
• phototonic/mips64el (2.1-4 to 2.1-4)
  • Migration status for phototonic/mips64el (2.1-4 to 2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: phototonic/mips64el exiv2
• phototonic/ppc64el (2.1-4 to 2.1-4)
  • Migration status for phototonic/ppc64el (2.1-4 to 2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: phototonic/ppc64el exiv2
• phototonic/s390x (2.1-4 to 2.1-4)
  • Migration status for phototonic/s390x (2.1-4 to 2.1-4): Will attempt migration (Any information below is purely informational)
    • Depends: phototonic/s390x exiv2
• php-geos/riscv64 (1.0.0-7 to 1.0.0-7)
  • Migration status for php-geos/riscv64 (1.0.0-7 to 1.0.0-7): Will attempt migration (Any information below is purely informational)
• php-gnupg/riscv64 (1.5.1-3 to 1.5.1-3)
  • Migration status for php-gnupg/riscv64 (1.5.1-3 to 1.5.1-3): Will attempt migration (Any information below is purely informational)
• php-horde-lz4/riscv64 (1.0.10-10 to 1.0.10-10)
  • Migration status for php-horde-lz4/riscv64 (1.0.10-10 to 1.0.10-10): Will attempt migration (Any information below is purely informational)
• php-luasandbox/riscv64 (4.1.2-1 to 4.1.2-1)
  • Migration status for php-luasandbox/riscv64 (4.1.2-1 to 4.1.2-1): Will attempt migration (Any information below is purely informational)
• php-pcov/riscv64 (1.0.11-5 to 1.0.11-5)
  • Migration status for php-pcov/riscv64 (1.0.11-5 to 1.0.11-5): Will attempt migration (Any information below is purely informational)
• php-ps/riscv64 (1.4.4+1.3.7-7 to 1.4.4+1.3.7-7)
  • Migration status for php-ps/riscv64 (1.4.4+1.3.7-7 to 1.4.4+1.3.7-7): Will attempt migration (Any information below is purely informational)
• php-psr/riscv64 (1.2.0-5 to 1.2.0-5)
  • Migration status for php-psr/riscv64 (1.2.0-5 to 1.2.0-5): Will attempt migration (Any information below is purely informational)
• php-stomp/riscv64 (2.0.3-2 to 2.0.3-2)
  • Migration status for php-stomp/riscv64 (2.0.3-2 to 2.0.3-2): Will attempt migration (Any information below is purely informational)
• php-uploadprogress/riscv64 (2.0.2+1.1.4-8 to 2.0.2+1.1.4-8)
  • Migration status for php-uploadprogress/riscv64 (2.0.2+1.1.4-8 to 2.0.2+1.1.4-8): Will attempt migration (Any information below is purely informational)
• php-uuid/riscv64 (1.2.0-12 to 1.2.0-12)
  • Migration status for php-uuid/riscv64 (1.2.0-12 to 1.2.0-12): Will attempt migration (Any information below is purely informational)
• php-wmerrors/riscv64 (2.0.0-1 to 2.0.0-1)
  • Migration status for php-wmerrors/riscv64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• php-xmlrpc/riscv64 (3:1.0.0~rc3-6 to 3:1.0.0~rc3-6)
  • Migration status for php-xmlrpc/riscv64 (3:1.0.0~rc3-6 to 3:1.0.0~rc3-6): Will attempt migration (Any information below is purely informational)
• php-yac/riscv64 (2.3.1+0.9.2-5 to 2.3.1+0.9.2-5)
  • Migration status for php-yac/riscv64 (2.3.1+0.9.2-5 to 2.3.1+0.9.2-5): Will attempt migration (Any information below is purely informational)
• phyml/riscv64 (3:3.3.20220408-3 to 3:3.3.20220408-3)
  • Migration status for phyml/riscv64 (3:3.3.20220408-3 to 3:3.3.20220408-3): Will attempt migration (Any information below is purely informational)
• pianobooster/riscv64 (1.0.0-3 to 1.0.0-3)
  • Migration status for pianobooster/riscv64 (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
• picmi/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for picmi/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• picplanner/riscv64 (0.4.0-1 to 0.4.0-1)
  • Migration status for picplanner/riscv64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• pidgin-audacious/riscv64 (2.0.0-8 to 2.0.0-8)
  • Migration status for pidgin-audacious/riscv64 (2.0.0-8 to 2.0.0-8): Will attempt migration (Any information below is purely informational)
• pidgin-awayonlock/riscv64 (0.5.2-1.1 to 0.5.2-1.1)
  • Migration status for pidgin-awayonlock/riscv64 (0.5.2-1.1 to 0.5.2-1.1): Will attempt migration (Any information below is purely informational)
• pidgin-extprefs/riscv64 (0.7-4 to 0.7-4)
  • Migration status for pidgin-extprefs/riscv64 (0.7-4 to 0.7-4): Will attempt migration (Any information below is purely informational)
• pidgin-festival/riscv64 (2.4-3.1 to 2.4-3.1)
  • Migration status for pidgin-festival/riscv64 (2.4-3.1 to 2.4-3.1): Will attempt migration (Any information below is purely informational)
• pidgin-gnome-keyring/riscv64 (2.0-3 to 2.0-3)
  • Migration status for pidgin-gnome-keyring/riscv64 (2.0-3 to 2.0-3): Will attempt migration (Any information below is purely informational)
• pidgin-latex/riscv64 (1.5.0-1 to 1.5.0-1)
  • Migration status for pidgin-latex/riscv64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
• pidgin-privacy-please/riscv64 (0.7.1-5 to 0.7.1-5)
  • Migration status for pidgin-privacy-please/riscv64 (0.7.1-5 to 0.7.1-5): Will attempt migration (Any information below is purely informational)
• pidgin/riscv64 (2.14.13-1 to 2.14.13-1)
  • Migration status for pidgin/riscv64 (2.14.13-1 to 2.14.13-1): Will attempt migration (Any information below is purely informational)
• pike8.0/riscv64 (8.0.1738-1.4 to 8.0.1738-1.4)
  • Migration status for pike8.0/riscv64 (8.0.1738-1.4 to 8.0.1738-1.4): Will attempt migration (Any information below is purely informational)
• pillow-sane/riscv64 (2.9.1-3 to 2.9.1-3)
  • Migration status for pillow-sane/riscv64 (2.9.1-3 to 2.9.1-3): Will attempt migration (Any information below is purely informational)
• pinball-table-gnu/riscv64 (0.0.20230219-1 to 0.0.20230219-1)
  • Migration status for pinball-table-gnu/riscv64 (0.0.20230219-1 to 0.0.20230219-1): Will attempt migration (Any information below is purely informational)
• pinball-table-hurd/riscv64 (0.0.20230219-1 to 0.0.20230219-1)
  • Migration status for pinball-table-hurd/riscv64 (0.0.20230219-1 to 0.0.20230219-1): Will attempt migration (Any information below is purely informational)
• pinball/riscv64 (0.3.20230219-1 to 0.3.20230219-1)
  • Migration status for pinball/riscv64 (0.3.20230219-1 to 0.3.20230219-1): Will attempt migration (Any information below is purely informational)
• pineapple-pictures/amd64 (0.8.0-1 to 0.8.0-1)
  • Migration status for pineapple-pictures/amd64 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pineapple-pictures/amd64 exiv2
• pineapple-pictures/arm64 (0.8.0-1 to 0.8.0-1)
  • Migration status for pineapple-pictures/arm64 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pineapple-pictures/arm64 exiv2
• pineapple-pictures/armel (0.8.0-1 to 0.8.0-1)
  • Migration status for pineapple-pictures/armel (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pineapple-pictures/armel exiv2
• pineapple-pictures/armhf (0.8.0-1 to 0.8.0-1)
  • Migration status for pineapple-pictures/armhf (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pineapple-pictures/armhf exiv2
• pineapple-pictures/i386 (0.8.0-1 to 0.8.0-1)
  • Migration status for pineapple-pictures/i386 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pineapple-pictures/i386 exiv2
• pineapple-pictures/mips64el (0.8.0-1 to 0.8.0-1)
  • Migration status for pineapple-pictures/mips64el (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pineapple-pictures/mips64el exiv2
• pineapple-pictures/ppc64el (0.8.0-1 to 0.8.0-1)
  • Migration status for pineapple-pictures/ppc64el (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pineapple-pictures/ppc64el exiv2
• pineapple-pictures/s390x (0.8.0-1 to 0.8.0-1)
  • Migration status for pineapple-pictures/s390x (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: pineapple-pictures/s390x exiv2
• pinentry-x2go/riscv64 (0.7.5.10-1 to 0.7.5.10-1)
  • Migration status for pinentry-x2go/riscv64 (0.7.5.10-1 to 0.7.5.10-1): Will attempt migration (Any information below is purely informational)
• pingus/riscv64 (0.7.6-6 to 0.7.6-6)
  • Migration status for pingus/riscv64 (0.7.6-6 to 0.7.6-6): Will attempt migration (Any information below is purely informational)
• pinhole/riscv64 (0.1.0+git20221220-1 to 0.1.0+git20221220-1)
  • Migration status for pinhole/riscv64 (0.1.0+git20221220-1 to 0.1.0+git20221220-1): Will attempt migration (Any information below is purely informational)
• pink-pony/riscv64 (1.4.1-3.1 to 1.4.1-3.1)
  • Migration status for pink-pony/riscv64 (1.4.1-3.1 to 1.4.1-3.1): Will attempt migration (Any information below is purely informational)
• pinot/amd64 (1.21-3 to 1.21-3)
  • Migration status for pinot/amd64 (1.21-3 to 1.21-3): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/amd64 exiv2
• pinot/arm64 (1.21-3 to 1.21-3)
  • Migration status for pinot/arm64 (1.21-3 to 1.21-3): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/arm64 exiv2
• pinot/armel (1.21-3 to 1.21-3)
  • Migration status for pinot/armel (1.21-3 to 1.21-3): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/armel exiv2
• pinot/armhf (1.21-3 to 1.21-3)
  • Migration status for pinot/armhf (1.21-3 to 1.21-3): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/armhf exiv2
• pinot/i386 (1.21-3 to 1.21-3)
  • Migration status for pinot/i386 (1.21-3 to 1.21-3): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/i386 exiv2
• pinot/mips64el (1.21-3 to 1.21-3)
  • Migration status for pinot/mips64el (1.21-3 to 1.21-3): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/mips64el exiv2
• pinot/ppc64el (1.21-3 to 1.21-3)
  • Migration status for pinot/ppc64el (1.21-3 to 1.21-3): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/ppc64el exiv2
• pinot/s390x (1.21-3 to 1.21-3)
  • Migration status for pinot/s390x (1.21-3 to 1.21-3): Will attempt migration (Any information below is purely informational)
    • Depends: pinot/s390x exiv2
• pinpoint/riscv64 (1:0.1.8-6 to 1:0.1.8-6)
  • Migration status for pinpoint/riscv64 (1:0.1.8-6 to 1:0.1.8-6): Will attempt migration (Any information below is purely informational)
• pioneers/riscv64 (15.6-1 to 15.6-1)
  • Migration status for pioneers/riscv64 (15.6-1 to 15.6-1): Will attempt migration (Any information below is purely informational)
• pitivi/riscv64 (2023.03-1 to 2023.03-1)
  • Migration status for pitivi/riscv64 (2023.03-1 to 2023.03-1): Will attempt migration (Any information below is purely informational)
• pivy/riscv64 (0.6.9~a0-1 to 0.6.9~a0-1)
  • Migration status for pivy/riscv64 (0.6.9~a0-1 to 0.6.9~a0-1): Will attempt migration (Any information below is purely informational)
• pixelize/riscv64 (2.0.0~git20220108.d1f9da9-1 to 2.0.0~git20220108.d1f9da9-1)
  • Migration status for pixelize/riscv64 (2.0.0~git20220108.d1f9da9-1 to 2.0.0~git20220108.d1f9da9-1): Will attempt migration (Any information below is purely informational)
• pkg-haskell-tools/riscv64 (0.12.5 to 0.12.5)
  • Migration status for pkg-haskell-tools/riscv64 (0.12.5 to 0.12.5): Will attempt migration (Any information below is purely informational)
• pktools/riscv64 (2.6.7.6+ds-6 to 2.6.7.6+ds-6)
  • Migration status for pktools/riscv64 (2.6.7.6+ds-6 to 2.6.7.6+ds-6): Will attempt migration (Any information below is purely informational)
• planetblupi/riscv64 (1.15.1-1 to 1.15.1-1)
  • Migration status for planetblupi/riscv64 (1.15.1-1 to 1.15.1-1): Will attempt migration (Any information below is purely informational)
• plank/riscv64 (0.11.89-6 to 0.11.89-6)
  • Migration status for plank/riscv64 (0.11.89-6 to 0.11.89-6): Will attempt migration (Any information below is purely informational)
• plasma-dialer/riscv64 (23.01.0-1 to 23.01.0-1)
  • Migration status for plasma-dialer/riscv64 (23.01.0-1 to 23.01.0-1): Will attempt migration (Any information below is purely informational)
• plasma-gamemode/riscv64 (0.0~git20220224.3adea2bd-2 to 0.0~git20220224.3adea2bd-2)
  • Migration status for plasma-gamemode/riscv64 (0.0~git20220224.3adea2bd-2 to 0.0~git20220224.3adea2bd-2): Will attempt migration (Any information below is purely informational)
• plasma-gmailfeed/riscv64 (1.2-1 to 1.2-1)
  • Migration status for plasma-gmailfeed/riscv64 (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• plasma-mobile/riscv64 (5.27.10-1 to 5.27.10-1)
  • Migration status for plasma-mobile/riscv64 (5.27.10-1 to 5.27.10-1): Will attempt migration (Any information below is purely informational)
• plasma-phonebook/riscv64 (23.01.0-1 to 23.01.0-1)
  • Migration status for plasma-phonebook/riscv64 (23.01.0-1 to 23.01.0-1): Will attempt migration (Any information below is purely informational)
• plasma-settings/riscv64 (23.01.0-1 to 23.01.0-1)
  • Migration status for plasma-settings/riscv64 (23.01.0-1 to 23.01.0-1): Will attempt migration (Any information below is purely informational)
• plee-the-bear/riscv64 (0.6.0-8 to 0.6.0-8)
  • Migration status for plee-the-bear/riscv64 (0.6.0-8 to 0.6.0-8): Will attempt migration (Any information below is purely informational)
• plib/riscv64 (1.8.5-14.1 to 1.8.5-14.1)
  • Migration status for plib/riscv64 (1.8.5-14.1 to 1.8.5-14.1): Will attempt migration (Any information below is purely informational)
• plopfolio.app/riscv64 (0.1.0-8 to 0.1.0-8)
  • Migration status for plopfolio.app/riscv64 (0.1.0-8 to 0.1.0-8): Will attempt migration (Any information below is purely informational)
• plplot/riscv64 (5.15.0+dfsg2-11 to 5.15.0+dfsg2-11)
  • Migration status for plplot/riscv64 (5.15.0+dfsg2-11 to 5.15.0+dfsg2-11): Will attempt migration (Any information below is purely informational)
• plume-creator/riscv64 (0.66+dfsg1-3.2 to 0.66+dfsg1-3.2)
  • Migration status for plume-creator/riscv64 (0.66+dfsg1-3.2 to 0.66+dfsg1-3.2): Will attempt migration (Any information below is purely informational)
• pnmixer/riscv64 (0.7.2-1 to 0.7.2-1)
  • Migration status for pnmixer/riscv64 (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• pokerth/riscv64 (1.1.2-3 to 1.1.2-3)
  • Migration status for pokerth/riscv64 (1.1.2-3 to 1.1.2-3): Will attempt migration (Any information below is purely informational)
• polari/riscv64 (46.0-1 to 46.0-1)
  • Migration status for polari/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• policykit-1-gnome/riscv64 (0.105-8 to 0.105-8)
  • Migration status for policykit-1-gnome/riscv64 (0.105-8 to 0.105-8): Will attempt migration (Any information below is purely informational)
• polyphone/riscv64 (2.2.0.20210109+dfsg1-3 to 2.2.0.20210109+dfsg1-3)
  • Migration status for polyphone/riscv64 (2.2.0.20210109+dfsg1-3 to 2.2.0.20210109+dfsg1-3): Will attempt migration (Any information below is purely informational)
• populations/riscv64 (1.2.33+svn0120106+dfsg-7 to 1.2.33+svn0120106+dfsg-7)
  • Migration status for populations/riscv64 (1.2.33+svn0120106+dfsg-7 to 1.2.33+svn0120106+dfsg-7): Will attempt migration (Any information below is purely informational)
• posixsignalmanager/riscv64 (0.3-4 to 0.3-4)
  • Migration status for posixsignalmanager/riscv64 (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
• postgresql-16-age/riscv64 (1.5.0~rc0-2 to 1.5.0~rc0-2)
  • Migration status for postgresql-16-age/riscv64 (1.5.0~rc0-2 to 1.5.0~rc0-2): Will attempt migration (Any information below is purely informational)
• postgresql-hll/riscv64 (2.18-1 to 2.18-1)
  • Migration status for postgresql-hll/riscv64 (2.18-1 to 2.18-1): Will attempt migration (Any information below is purely informational)
• postgresql-numeral/riscv64 (1.3-6 to 1.3-6)
  • Migration status for postgresql-numeral/riscv64 (1.3-6 to 1.3-6): Will attempt migration (Any information below is purely informational)
• postgresql-periods/riscv64 (1.2.2-2 to 1.2.2-2)
  • Migration status for postgresql-periods/riscv64 (1.2.2-2 to 1.2.2-2): Will attempt migration (Any information below is purely informational)
• postgresql-pgmp/riscv64 (1.0.5-2 to 1.0.5-2)
  • Migration status for postgresql-pgmp/riscv64 (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• postgresql-pllua/riscv64 (1:2.0.12-2 to 1:2.0.12-2)
  • Migration status for postgresql-pllua/riscv64 (1:2.0.12-2 to 1:2.0.12-2): Will attempt migration (Any information below is purely informational)
• postgresql-plproxy/riscv64 (2.11.0-11 to 2.11.0-11)
  • Migration status for postgresql-plproxy/riscv64 (2.11.0-11 to 2.11.0-11): Will attempt migration (Any information below is purely informational)
• postgresql-plsh/riscv64 (1.20220917-2 to 1.20220917-2)
  • Migration status for postgresql-plsh/riscv64 (1.20220917-2 to 1.20220917-2): Will attempt migration (Any information below is purely informational)
• postgresql-prioritize/riscv64 (1.0.4-11 to 1.0.4-11)
  • Migration status for postgresql-prioritize/riscv64 (1.0.4-11 to 1.0.4-11): Will attempt migration (Any information below is purely informational)
• postgresql-rum/riscv64 (1.3.13-2 to 1.3.13-2)
  • Migration status for postgresql-rum/riscv64 (1.3.13-2 to 1.3.13-2): Will attempt migration (Any information below is purely informational)
• postgresql-set-user/riscv64 (4.0.1-2 to 4.0.1-2)
  • Migration status for postgresql-set-user/riscv64 (4.0.1-2 to 4.0.1-2): Will attempt migration (Any information below is purely informational)
• postgresql-unit/riscv64 (7.8-1 to 7.8-1)
  • Migration status for postgresql-unit/riscv64 (7.8-1 to 7.8-1): Will attempt migration (Any information below is purely informational)
• powa-archivist/riscv64 (4.2.2-1 to 4.2.2-1)
  • Migration status for powa-archivist/riscv64 (4.2.2-1 to 4.2.2-1): Will attempt migration (Any information below is purely informational)
• poxml/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for poxml/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• pqiv/riscv64 (2.13.1-1 to 2.13.1-1)
  • Migration status for pqiv/riscv64 (2.13.1-1 to 2.13.1-1): Will attempt migration (Any information below is purely informational)
• pqmarble/riscv64 (1.3.0-6 to 1.3.0-6)
  • Migration status for pqmarble/riscv64 (1.3.0-6 to 1.3.0-6): Will attempt migration (Any information below is purely informational)
• praelector/riscv64 (0.5-3 to 0.5-3)
  • Migration status for praelector/riscv64 (0.5-3 to 0.5-3): Will attempt migration (Any information below is purely informational)
• pragha/riscv64 (1.3.4-2 to 1.3.4-2)
  • Migration status for pragha/riscv64 (1.3.4-2 to 1.3.4-2): Will attempt migration (Any information below is purely informational)
• prefix/riscv64 (1.2.10-2 to 1.2.10-2)
  • Migration status for prefix/riscv64 (1.2.10-2 to 1.2.10-2): Will attempt migration (Any information below is purely informational)
• preprepare/riscv64 (0.9-8 to 0.9-8)
  • Migration status for preprepare/riscv64 (0.9-8 to 0.9-8): Will attempt migration (Any information below is purely informational)
• preview.app/riscv64 (0.8.5-11 to 0.8.5-11)
  • Migration status for preview.app/riscv64 (0.8.5-11 to 0.8.5-11): Will attempt migration (Any information below is purely informational)
• previsat/riscv64 (3.5.1.7+dfsg1-5 to 3.5.1.7+dfsg1-5)
  • Migration status for previsat/riscv64 (3.5.1.7+dfsg1-5 to 3.5.1.7+dfsg1-5): Will attempt migration (Any information below is purely informational)
• primus/riscv64 (0~20150328-16 to 0~20150328-16)
  • Migration status for primus/riscv64 (0~20150328-16 to 0~20150328-16): Will attempt migration (Any information below is purely informational)
• print-manager/riscv64 (4:23.08.3-1 to 4:23.08.3-1)
  • Migration status for print-manager/riscv64 (4:23.08.3-1 to 4:23.08.3-1): Will attempt migration (Any information below is purely informational)
• prison-kf5/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for prison-kf5/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• pristine-tar/riscv64 (1.50+nmu2 to 1.50+nmu2)
  • Migration status for pristine-tar/riscv64 (1.50+nmu2 to 1.50+nmu2): Will attempt migration (Any information below is purely informational)
• proalign/riscv64 (0.603-5 to 0.603-5)
  • Migration status for proalign/riscv64 (0.603-5 to 0.603-5): Will attempt migration (Any information below is purely informational)
• procmeter3/riscv64 (3.6-3.1 to 3.6-3.1)
  • Migration status for procmeter3/riscv64 (3.6-3.1 to 3.6-3.1): Will attempt migration (Any information below is purely informational)
• proftpd-mod-tar/riscv64 (0.4-2 to 0.4-2)
  • Migration status for proftpd-mod-tar/riscv64 (0.4-2 to 0.4-2): Will attempt migration (Any information below is purely informational)
• projectl/riscv64 (1.001.dfsg2-1 to 1.001.dfsg2-1)
  • Migration status for projectl/riscv64 (1.001.dfsg2-1 to 1.001.dfsg2-1): Will attempt migration (Any information below is purely informational)
• projectm/riscv64 (3.1.12-4 to 3.1.12-4)
  • Migration status for projectm/riscv64 (3.1.12-4 to 3.1.12-4): Will attempt migration (Any information below is purely informational)
• prometheus-libvirt-exporter/riscv64 (0.2.0-1 to 0.2.0-1)
  • Migration status for prometheus-libvirt-exporter/riscv64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• propellor/riscv64 (5.17-1 to 5.17-1)
  • Migration status for propellor/riscv64 (5.17-1 to 5.17-1): Will attempt migration (Any information below is purely informational)
• psautohint/riscv64 (2.4.0-1 to 2.4.0-1)
  • Migration status for psautohint/riscv64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
• psi-notify/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for psi-notify/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• psi-plugins/riscv64 (1.5-2 to 1.5-2)
  • Migration status for psi-plugins/riscv64 (1.5-2 to 1.5-2): Will attempt migration (Any information below is purely informational)
• psi-plus/riscv64 (1.4.554-5 to 1.4.554-5)
  • Migration status for psi-plus/riscv64 (1.4.554-5 to 1.4.554-5): Will attempt migration (Any information below is purely informational)
• psi/riscv64 (1.5+dfsg1-1.1 to 1.5+dfsg1-1.1)
  • Migration status for psi/riscv64 (1.5+dfsg1-1.1 to 1.5+dfsg1-1.1): Will attempt migration (Any information below is purely informational)
• pspp/riscv64 (2.0.1-1 to 2.0.1-1)
  • Migration status for pspp/riscv64 (2.0.1-1 to 2.0.1-1): Will attempt migration (Any information below is purely informational)
• pstoedit/riscv64 (4.01-1 to 4.01-1)
  • Migration status for pstoedit/riscv64 (4.01-1 to 4.01-1): Will attempt migration (Any information below is purely informational)
• ptask/riscv64 (1.0.0-1.1 to 1.0.0-1.1)
  • Migration status for ptask/riscv64 (1.0.0-1.1 to 1.0.0-1.1): Will attempt migration (Any information below is purely informational)
• pugl/riscv64 (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4)
  • Migration status for pugl/riscv64 (0~svn32+dfsg0-4 to 0~svn32+dfsg0-4): Will attempt migration (Any information below is purely informational)
• pulseeffects/riscv64 (4.8.7-2 to 4.8.7-2)
  • Migration status for pulseeffects/riscv64 (4.8.7-2 to 4.8.7-2): Will attempt migration (Any information below is purely informational)
• pulseview/riscv64 (0.4.2-3 to 0.4.2-3)
  • Migration status for pulseview/riscv64 (0.4.2-3 to 0.4.2-3): Will attempt migration (Any information below is purely informational)
• pumpa/riscv64 (0.9.3-1 to 0.9.3-1)
  • Migration status for pumpa/riscv64 (0.9.3-1 to 0.9.3-1): Will attempt migration (Any information below is purely informational)
• puppetserver_pu (8.4.0-7 to 7.9.5-2+deb12u1)
  • Migration status for puppetserver_pu (8.4.0-7 to 7.9.5-2+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: puppetserver is newer in the target suite (8.4.0-7 7.9.5-2+deb12u1)
• purple-discord/riscv64 (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1)
  • Migration status for purple-discord/riscv64 (0.9.2023.10.23.git.f8b0c59-1 to 0.9.2023.10.23.git.f8b0c59-1): Will attempt migration (Any information below is purely informational)
• purple-mm-sms/riscv64 (0.1.7-1 to 0.1.7-1)
  • Migration status for purple-mm-sms/riscv64 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• purple-plugin-pack/riscv64 (2.8.0-1 to 2.8.0-1)
  • Migration status for purple-plugin-pack/riscv64 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
• purple-rocketchat/riscv64 (0.1~hg20200403.800ef89-1 to 0.1~hg20200403.800ef89-1)
  • Migration status for purple-rocketchat/riscv64 (0.1~hg20200403.800ef89-1 to 0.1~hg20200403.800ef89-1): Will attempt migration (Any information below is purely informational)
• purple-xmpp-carbons/riscv64 (0.2.3-1.1 to 0.2.3-1.1)
  • Migration status for purple-xmpp-carbons/riscv64 (0.2.3-1.1 to 0.2.3-1.1): Will attempt migration (Any information below is purely informational)
• puzzle-jigsaw/riscv64 (1.0.2+git20201007.527c529+dfsg-4 to 1.0.2+git20201007.527c529+dfsg-4)
  • Migration status for puzzle-jigsaw/riscv64 (1.0.2+git20201007.527c529+dfsg-4 to 1.0.2+git20201007.527c529+dfsg-4): Will attempt migration (Any information below is purely informational)
• py3exiv2/amd64 (0.12.0-1 to 0.12.0-1)
  • Migration status for py3exiv2/amd64 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: py3exiv2/amd64 exiv2
• py3exiv2/arm64 (0.12.0-1 to 0.12.0-1)
  • Migration status for py3exiv2/arm64 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: py3exiv2/arm64 exiv2
• py3exiv2/armel (0.12.0-1 to 0.12.0-1)
  • Migration status for py3exiv2/armel (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: py3exiv2/armel exiv2
• py3exiv2/armhf (0.12.0-1 to 0.12.0-1)
  • Migration status for py3exiv2/armhf (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: py3exiv2/armhf exiv2
• py3exiv2/i386 (0.12.0-1 to 0.12.0-1)
  • Migration status for py3exiv2/i386 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: py3exiv2/i386 exiv2
• py3exiv2/mips64el (0.12.0-1 to 0.12.0-1)
  • Migration status for py3exiv2/mips64el (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: py3exiv2/mips64el exiv2
• py3exiv2/ppc64el (0.12.0-1 to 0.12.0-1)
  • Migration status for py3exiv2/ppc64el (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: py3exiv2/ppc64el exiv2
• py3exiv2/riscv64 (0.12.0-1 to 0.12.0-1)
  • Migration status for py3exiv2/riscv64 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• py3exiv2/s390x (0.12.0-1 to 0.12.0-1)
  • Migration status for py3exiv2/s390x (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
    • Depends: py3exiv2/s390x exiv2
• pybik/riscv64 (3.0-6 to 3.0-6)
  • Migration status for pybik/riscv64 (3.0-6 to 3.0-6): Will attempt migration (Any information below is purely informational)
• pyfltk/riscv64 (1.3.9+repack-3 to 1.3.9+repack-3)
  • Migration status for pyfltk/riscv64 (1.3.9+repack-3 to 1.3.9+repack-3): Will attempt migration (Any information below is purely informational)
• pygalmesh/riscv64 (0.10.6-2 to 0.10.6-2)
  • Migration status for pygalmesh/riscv64 (0.10.6-2 to 0.10.6-2): Will attempt migration (Any information below is purely informational)
• pymatgen_pu (2024.6.10+dfsg1-8 to 2022.11.7+dfsg1-11+deb12u1)
  • Migration status for pymatgen_pu (2024.6.10+dfsg1-8 to 2022.11.7+dfsg1-11+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: pymatgen is newer in the target suite (2024.6.10+dfsg1-8 2022.11.7+dfsg1-11+deb12u1)
• pynauty/amd64 (2.8.8.1+ds-1 to 2.8.8.1+ds-1)
  • Migration status for pynauty/amd64 (2.8.8.1+ds-1 to 2.8.8.1+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: pynauty/amd64 nauty
• pynauty/arm64 (2.8.8.1+ds-1 to 2.8.8.1+ds-1)
  • Migration status for pynauty/arm64 (2.8.8.1+ds-1 to 2.8.8.1+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: pynauty/arm64 nauty
• pynauty/armel (2.8.8.1+ds-1 to 2.8.8.1+ds-1)
  • Migration status for pynauty/armel (2.8.8.1+ds-1 to 2.8.8.1+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: pynauty/armel nauty
• pynauty/armhf (2.8.8.1+ds-1 to 2.8.8.1+ds-1)
  • Migration status for pynauty/armhf (2.8.8.1+ds-1 to 2.8.8.1+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: pynauty/armhf nauty
• pynauty/i386 (2.8.8.1+ds-1 to 2.8.8.1+ds-1)
  • Migration status for pynauty/i386 (2.8.8.1+ds-1 to 2.8.8.1+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: pynauty/i386 nauty
• 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)
    • Depends: pynauty/mips64el nauty
• pynauty/ppc64el (2.8.8.1+ds-1 to 2.8.8.1+ds-1)
  • Migration status for pynauty/ppc64el (2.8.8.1+ds-1 to 2.8.8.1+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: pynauty/ppc64el nauty
• 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)
    • Depends: pynauty/s390x nauty
• pynest2d/riscv64 (5.0.0-3 to 5.0.0-3)
  • Migration status for pynest2d/riscv64 (5.0.0-3 to 5.0.0-3): Will attempt migration (Any information below is purely informational)
• pyqt-qwt/riscv64 (1.02.02-2 to 1.02.02-2)
  • Migration status for pyqt-qwt/riscv64 (1.02.02-2 to 1.02.02-2): Will attempt migration (Any information below is purely informational)
• pyscanfcs/riscv64 (0.3.6+ds-4 to 0.3.6+ds-4)
  • Migration status for pyscanfcs/riscv64 (0.3.6+ds-4 to 0.3.6+ds-4): Will attempt migration (Any information below is purely informational)
• pystemd/riscv64 (0.13.2-2 to 0.13.2-2)
  • Migration status for pystemd/riscv64 (0.13.2-2 to 0.13.2-2): Will attempt migration (Any information below is purely informational)
• python-caja/riscv64 (1.26.0-1 to 1.26.0-1)
  • Migration status for python-caja/riscv64 (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
• python-cartopy/riscv64 (0.23.0+dfsg-1 to 0.23.0+dfsg-1)
  • Migration status for python-cartopy/riscv64 (0.23.0+dfsg-1 to 0.23.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• python-cdo/riscv64 (1.6.0-2 to 1.6.0-2)
  • Migration status for python-cdo/riscv64 (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
• python-dicompylercore/riscv64 (0.5.6-1 to 0.5.6-1)
  • Migration status for python-dicompylercore/riscv64 (0.5.6-1 to 0.5.6-1): Will attempt migration (Any information below is purely informational)
• python-django_pu (3:4.2.16-1 to 3:3.2.19-1+deb12u2)
  • Migration status for python-django_pu (3:4.2.16-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.16-1 3:3.2.19-1+deb12u2)
• python-freesasa/riscv64 (2.1.0-3 to 2.1.0-3)
  • Migration status for python-freesasa/riscv64 (2.1.0-3 to 2.1.0-3): Will attempt migration (Any information below is purely informational)
• python-gphoto2/riscv64 (1.9.0-1 to 1.9.0-1)
  • Migration status for python-gphoto2/riscv64 (1.9.0-1 to 1.9.0-1): Will attempt migration (Any information below is purely informational)
• python-leidenalg/riscv64 (0.10.2-1 to 0.10.2-1)
  • Migration status for python-leidenalg/riscv64 (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• python-ltfatpy/riscv64 (1.0.16-10 to 1.0.16-10)
  • Migration status for python-ltfatpy/riscv64 (1.0.16-10 to 1.0.16-10): Will attempt migration (Any information below is purely informational)
• python-memprof/riscv64 (0.3.6-5.1 to 0.3.6-5.1)
  • Migration status for python-memprof/riscv64 (0.3.6-5.1 to 0.3.6-5.1): Will attempt migration (Any information below is purely informational)
• python-pgmagick/riscv64 (0.7.6-1 to 0.7.6-1)
  • Migration status for python-pgmagick/riscv64 (0.7.6-1 to 0.7.6-1): Will attempt migration (Any information below is purely informational)
• python-poppler-qt5/riscv64 (21.3.0-3 to 21.3.0-3)
  • Migration status for python-poppler-qt5/riscv64 (21.3.0-3 to 21.3.0-3): Will attempt migration (Any information below is purely informational)
• python-pyani/riscv64 (0.2.12-3 to 0.2.12-3)
  • Migration status for python-pyani/riscv64 (0.2.12-3 to 0.2.12-3): Will attempt migration (Any information below is purely informational)
• python-sqt/riscv64 (0.8.0-8 to 0.8.0-8)
  • Migration status for python-sqt/riscv64 (0.8.0-8 to 0.8.0-8): Will attempt migration (Any information below is purely informational)
• python-vispy/riscv64 (0.14.1-2 to 0.14.1-2)
  • Migration status for python-vispy/riscv64 (0.14.1-2 to 0.14.1-2): Will attempt migration (Any information below is purely informational)
• python-wordcloud/riscv64 (1.9.3+dfsg-1 to 1.9.3+dfsg-1)
  • Migration status for python-wordcloud/riscv64 (1.9.3+dfsg-1 to 1.9.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• python3.11_pu (- to 3.11.2-6+deb12u3)
  • Migration status for python3.11_pu (- to 3.11.2-6+deb12u3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • idle-python3.11/amd64 has unsatisfiable dependency
    • python3.11-full/amd64 has unsatisfiable dependency
    • python3.11-venv/amd64 has unsatisfiable dependency
    • idle-python3.11/arm64 has unsatisfiable dependency
    • python3.11-full/arm64 has unsatisfiable dependency
    • python3.11-venv/arm64 has unsatisfiable dependency
    • libpython3.11-dbg/armel has unsatisfiable dependency
    • libpython3.11-stdlib/armel has unsatisfiable dependency
    • python3.11-full/armel has unsatisfiable dependency
    • python3.11-venv/armel has unsatisfiable dependency
    • libpython3.11-dbg/armhf has unsatisfiable dependency
    • libpython3.11-stdlib/armhf has unsatisfiable dependency
    • python3.11-full/armhf has unsatisfiable dependency
    • python3.11-venv/armhf has unsatisfiable dependency
    • python3.11-full/i386 has unsatisfiable dependency
    • python3.11-venv/i386 has unsatisfiable dependency
    • python3.11-full/mips64el has unsatisfiable dependency
    • python3.11-venv/mips64el has unsatisfiable dependency
    • python3.11-full/ppc64el has unsatisfiable dependency
    • python3.11-venv/ppc64el has unsatisfiable dependency
    • python3.11-full/s390x has unsatisfiable dependency
    • python3.11-venv/s390x has unsatisfiable dependency
    • Impossible Depends: python3.11_pu -> libssl3/3.1.5-1/armel
    • Impossible Depends: python3.11_pu -> libssl3/3.1.5-1/armhf
    • NEEDS APPROVAL BY RM
• pythonmagick/riscv64 (0.9.19-10 to 0.9.19-10)
  • Migration status for pythonmagick/riscv64 (0.9.19-10 to 0.9.19-10): Will attempt migration (Any information below is purely informational)
• pyxplot/riscv64 (0.9.2-14 to 0.9.2-14)
  • Migration status for pyxplot/riscv64 (0.9.2-14 to 0.9.2-14): Will attempt migration (Any information below is purely informational)
• pyxrd/riscv64 (0.8.4-3 to 0.8.4-3)
  • Migration status for pyxrd/riscv64 (0.8.4-3 to 0.8.4-3): Will attempt migration (Any information below is purely informational)
• pyzmq/riscv64 (24.0.1-5 to 24.0.1-5)
  • Migration status for pyzmq/riscv64 (24.0.1-5 to 24.0.1-5): Will attempt migration (Any information below is purely informational)
• pyzoltan/riscv64 (1.0.1-9 to 1.0.1-9)
  • Migration status for pyzoltan/riscv64 (1.0.1-9 to 1.0.1-9): Will attempt migration (Any information below is purely informational)
• q4wine/riscv64 (1.3.13-1 to 1.3.13-1)
  • Migration status for q4wine/riscv64 (1.3.13-1 to 1.3.13-1): Will attempt migration (Any information below is purely informational)
• qabcs/riscv64 (1.0.2-6 to 1.0.2-6)
  • Migration status for qabcs/riscv64 (1.0.2-6 to 1.0.2-6): Will attempt migration (Any information below is purely informational)
• qastools/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for qastools/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• qbrew/riscv64 (0.4.1-8 to 0.4.1-8)
  • Migration status for qbrew/riscv64 (0.4.1-8 to 0.4.1-8): Will attempt migration (Any information below is purely informational)
• qcalcfilehash/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for qcalcfilehash/riscv64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• qcodeeditor/riscv64 (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2)
  • Migration status for qcodeeditor/riscv64 (1.0+1gitdc644d-2 to 1.0+1gitdc644d-2): Will attempt migration (Any information below is purely informational)
• qcomicbook/riscv64 (0.9.1-3 to 0.9.1-3)
  • Migration status for qcomicbook/riscv64 (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• qconf/riscv64 (2.5-1 to 2.5-1)
  • Migration status for qconf/riscv64 (2.5-1 to 2.5-1): Will attempt migration (Any information below is purely informational)
• qcustomplot/riscv64 (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1)
  • Migration status for qcustomplot/riscv64 (2.1.0+dfsg1-3.1 to 2.1.0+dfsg1-3.1): Will attempt migration (Any information below is purely informational)
• qdacco/riscv64 (1.1.2-1 to 1.1.2-1)
  • Migration status for qdacco/riscv64 (1.1.2-1 to 1.1.2-1): Will attempt migration (Any information below is purely informational)
• qdirstat/riscv64 (1.9-1 to 1.9-1)
  • Migration status for qdirstat/riscv64 (1.9-1 to 1.9-1): Will attempt migration (Any information below is purely informational)
• qdjango/riscv64 (0.6.2-3.3 to 0.6.2-3.3)
  • Migration status for qdjango/riscv64 (0.6.2-3.3 to 0.6.2-3.3): Will attempt migration (Any information below is purely informational)
• qelectrotech/riscv64 (1:0.9-2 to 1:0.9-2)
  • Migration status for qelectrotech/riscv64 (1:0.9-2 to 1:0.9-2): Will attempt migration (Any information below is purely informational)
• qflipper/riscv64 (1.3.3-1 to 1.3.3-1)
  • Migration status for qflipper/riscv64 (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
• qgis/amd64 (3.34.10+dfsg-1 to 3.34.10+dfsg-1)
  • Migration status for qgis/amd64 (3.34.10+dfsg-1 to 3.34.10+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Depends: qgis/amd64 exiv2
• qgis/arm64 (3.34.10+dfsg-1 to 3.34.10+dfsg-1)
  • Migration status for qgis/arm64 (3.34.10+dfsg-1 to 3.34.10+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Depends: qgis/arm64 exiv2
• qgis/armel (3.34.10+dfsg-1 to 3.34.10+dfsg-1)
  • Migration status for qgis/armel (3.34.10+dfsg-1 to 3.34.10+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch armel binaries not found
    • Depends: qgis/armel exiv2
• qgis/armhf (3.34.10+dfsg-1 to 3.34.10+dfsg-1)
  • Migration status for qgis/armhf (3.34.10+dfsg-1 to 3.34.10+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: qgis/armhf exiv2
• qgis/i386 (3.34.10+dfsg-1 to 3.34.10+dfsg-1)
  • Migration status for qgis/i386 (3.34.10+dfsg-1 to 3.34.10+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch i386 binaries not found
    • Depends: qgis/i386 exiv2
• qgis/mips64el (3.34.10+dfsg-1 to 3.34.10+dfsg-1)
  • Migration status for qgis/mips64el (3.34.10+dfsg-1 to 3.34.10+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: qgis/mips64el exiv2
• qgis/ppc64el (3.34.10+dfsg-1 to 3.34.10+dfsg-1)
  • Migration status for qgis/ppc64el (3.34.10+dfsg-1 to 3.34.10+dfsg-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Depends: qgis/ppc64el exiv2
• qgis/s390x (3.34.10+dfsg-1 to 3.34.10+dfsg-1)
  • Migration status for qgis/s390x (3.34.10+dfsg-1 to 3.34.10+dfsg-1): Will attempt migration (Any information below is purely informational)
    • Depends: qgis/s390x exiv2
• qgit/riscv64 (2.10-2 to 2.10-2)
  • Migration status for qgit/riscv64 (2.10-2 to 2.10-2): Will attempt migration (Any information below is purely informational)
• qgo/riscv64 (2.1~git-20180413-1 to 2.1~git-20180413-1)
  • Migration status for qgo/riscv64 (2.1~git-20180413-1 to 2.1~git-20180413-1): Will attempt migration (Any information below is purely informational)
• qhttpengine/riscv64 (0.1.0+dfsg1-1.1 to 0.1.0+dfsg1-1.1)
  • Migration status for qhttpengine/riscv64 (0.1.0+dfsg1-1.1 to 0.1.0+dfsg1-1.1): Will attempt migration (Any information below is purely informational)
• qimgv/amd64 (1.0.2+git20240112-2 to 1.0.2+git20240112-2)
  • Migration status for qimgv/amd64 (1.0.2+git20240112-2 to 1.0.2+git20240112-2): Will attempt migration (Any information below is purely informational)
    • Depends: qimgv/amd64 exiv2
• qimgv/arm64 (1.0.2+git20240112-2 to 1.0.2+git20240112-2)
  • Migration status for qimgv/arm64 (1.0.2+git20240112-2 to 1.0.2+git20240112-2): Will attempt migration (Any information below is purely informational)
    • Depends: qimgv/arm64 exiv2
• qimgv/armel (1.0.2+git20240112-2 to 1.0.2+git20240112-2)
  • Migration status for qimgv/armel (1.0.2+git20240112-2 to 1.0.2+git20240112-2): Will attempt migration (Any information below is purely informational)
    • Depends: qimgv/armel exiv2
• qimgv/armhf (1.0.2+git20240112-2 to 1.0.2+git20240112-2)
  • Migration status for qimgv/armhf (1.0.2+git20240112-2 to 1.0.2+git20240112-2): Will attempt migration (Any information below is purely informational)
    • Depends: qimgv/armhf exiv2
• qimgv/i386 (1.0.2+git20240112-2 to 1.0.2+git20240112-2)
  • Migration status for qimgv/i386 (1.0.2+git20240112-2 to 1.0.2+git20240112-2): Will attempt migration (Any information below is purely informational)
    • Depends: qimgv/i386 exiv2
• qimgv/mips64el (1.0.2+git20240112-2 to 1.0.2+git20240112-2)
  • Migration status for qimgv/mips64el (1.0.2+git20240112-2 to 1.0.2+git20240112-2): Will attempt migration (Any information below is purely informational)
    • Depends: qimgv/mips64el exiv2
• qimgv/ppc64el (1.0.2+git20240112-2 to 1.0.2+git20240112-2)
  • Migration status for qimgv/ppc64el (1.0.2+git20240112-2 to 1.0.2+git20240112-2): Will attempt migration (Any information below is purely informational)
    • Depends: qimgv/ppc64el exiv2
• qimgv/riscv64 (1.0.2+git20240112-2 to 1.0.2+git20240112-2)
  • Migration status for qimgv/riscv64 (1.0.2+git20240112-2 to 1.0.2+git20240112-2): Will attempt migration (Any information below is purely informational)
• qimgv/s390x (1.0.2+git20240112-2 to 1.0.2+git20240112-2)
  • Migration status for qimgv/s390x (1.0.2+git20240112-2 to 1.0.2+git20240112-2): Will attempt migration (Any information below is purely informational)
    • Depends: qimgv/s390x exiv2
• qiv/riscv64 (2.3.3-1.1 to 2.3.3-1.1)
  • Migration status for qiv/riscv64 (2.3.3-1.1 to 2.3.3-1.1): Will attempt migration (Any information below is purely informational)
• qjackrcd/riscv64 (1.2.0-2 to 1.2.0-2)
  • Migration status for qjackrcd/riscv64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• qjoypad/riscv64 (4.3.1-3 to 4.3.1-3)
  • Migration status for qjoypad/riscv64 (4.3.1-3 to 4.3.1-3): Will attempt migration (Any information below is purely informational)
• qlipper/riscv64 (1:5.1.2-2 to 1:5.1.2-2)
  • Migration status for qlipper/riscv64 (1:5.1.2-2 to 1:5.1.2-2): Will attempt migration (Any information below is purely informational)
• qmath3d/riscv64 (0~1.0-6 to 0~1.0-6)
  • Migration status for qmath3d/riscv64 (0~1.0-6 to 0~1.0-6): Will attempt migration (Any information below is purely informational)
• qmidiroute/riscv64 (0.4.0-2 to 0.4.0-2)
  • Migration status for qmidiroute/riscv64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• qmlkonsole/riscv64 (23.08.3-1 to 23.08.3-1)
  • Migration status for qmlkonsole/riscv64 (23.08.3-1 to 23.08.3-1): Will attempt migration (Any information below is purely informational)
• qmmp/riscv64 (1.6.2-1 to 1.6.2-1)
  • Migration status for qmmp/riscv64 (1.6.2-1 to 1.6.2-1): Will attempt migration (Any information below is purely informational)
• qnapi/riscv64 (0.2.3-2 to 0.2.3-2)
  • Migration status for qnapi/riscv64 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• qnetload/riscv64 (1.3.6-1 to 1.3.6-1)
  • Migration status for qnetload/riscv64 (1.3.6-1 to 1.3.6-1): Will attempt migration (Any information below is purely informational)
• qnetstatview/riscv64 (1.5.8-2 to 1.5.8-2)
  • Migration status for qnetstatview/riscv64 (1.5.8-2 to 1.5.8-2): Will attempt migration (Any information below is purely informational)
• qoauth/riscv64 (2.0.1~1-3 to 2.0.1~1-3)
  • Migration status for qoauth/riscv64 (2.0.1~1-3 to 2.0.1~1-3): Will attempt migration (Any information below is purely informational)
• qonk/riscv64 (0.3.1-3.2 to 0.3.1-3.2)
  • Migration status for qonk/riscv64 (0.3.1-3.2 to 0.3.1-3.2): Will attempt migration (Any information below is purely informational)
• qps/riscv64 (2.8.0-1 to 2.8.0-1)
  • Migration status for qps/riscv64 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
• qpxtool/riscv64 (0.8.1-2.1 to 0.8.1-2.1)
  • Migration status for qpxtool/riscv64 (0.8.1-2.1 to 0.8.1-2.1): Will attempt migration (Any information below is purely informational)
• qqc2-desktop-style/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for qqc2-desktop-style/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• qqc2-suru-style/riscv64 (0.20230206-1 to 0.20230206-1)
  • Migration status for qqc2-suru-style/riscv64 (0.20230206-1 to 0.20230206-1): Will attempt migration (Any information below is purely informational)
• qscintilla2/riscv64 (2.14.1+dfsg-1 to 2.14.1+dfsg-1)
  • Migration status for qscintilla2/riscv64 (2.14.1+dfsg-1 to 2.14.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• qspeakers/riscv64 (1.6.9-1 to 1.6.9-1)
  • Migration status for qspeakers/riscv64 (1.6.9-1 to 1.6.9-1): Will attempt migration (Any information below is purely informational)
• qsstv/riscv64 (9.5.8-3 to 9.5.8-3)
  • Migration status for qsstv/riscv64 (9.5.8-3 to 9.5.8-3): Will attempt migration (Any information below is purely informational)
• qt-advanced-docking-system/riscv64 (3.8.3-1 to 3.8.3-1)
  • Migration status for qt-advanced-docking-system/riscv64 (3.8.3-1 to 3.8.3-1): Will attempt migration (Any information below is purely informational)
• qt-color-widgets/riscv64 (2.2.0-2 to 2.2.0-2)
  • Migration status for qt-color-widgets/riscv64 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• qt-gstreamer/riscv64 (1.2.0-5.2 to 1.2.0-5.2)
  • Migration status for qt-gstreamer/riscv64 (1.2.0-5.2 to 1.2.0-5.2): Will attempt migration (Any information below is purely informational)
• qt-qml-models/riscv64 (0~0.0-1 to 0~0.0-1)
  • Migration status for qt-qml-models/riscv64 (0~0.0-1 to 0~0.0-1): Will attempt migration (Any information below is purely informational)
• qt5-style-kvantum/riscv64 (1.0.10-1 to 1.0.10-1)
  • Migration status for qt5-style-kvantum/riscv64 (1.0.10-1 to 1.0.10-1): Will attempt migration (Any information below is purely informational)
• qt6ct/riscv64 (0.9-2 to 0.9-2)
  • Migration status for qt6ct/riscv64 (0.9-2 to 0.9-2): Will attempt migration (Any information below is purely informational)
• qtads/riscv64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for qtads/riscv64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• qtcurve/riscv64 (1.9-7 to 1.9-7)
  • Migration status for qtcurve/riscv64 (1.9-7 to 1.9-7): Will attempt migration (Any information below is purely informational)
• qtdbusextended/riscv64 (0.0.3-7 to 0.0.3-7)
  • Migration status for qtdbusextended/riscv64 (0.0.3-7 to 0.0.3-7): Will attempt migration (Any information below is purely informational)
• qterm/riscv64 (1:0.7.4-3 to 1:0.7.4-3)
  • Migration status for qterm/riscv64 (1:0.7.4-3 to 1:0.7.4-3): Will attempt migration (Any information below is purely informational)
• qtfeedback-opensource-src/riscv64 (5.0~git20180903.a14bd0b-6 to 5.0~git20180903.a14bd0b-6)
  • Migration status for qtfeedback-opensource-src/riscv64 (5.0~git20180903.a14bd0b-6 to 5.0~git20180903.a14bd0b-6): Will attempt migration (Any information below is purely informational)
• qthid-fcd-controller/riscv64 (4.1-6 to 4.1-6)
  • Migration status for qthid-fcd-controller/riscv64 (4.1-6 to 4.1-6): Will attempt migration (Any information below is purely informational)
• qtmpris/riscv64 (1.0.6-2 to 1.0.6-2)
  • Migration status for qtmpris/riscv64 (1.0.6-2 to 1.0.6-2): Will attempt migration (Any information below is purely informational)
• qtop/riscv64 (2.3.4-3 to 2.3.4-3)
  • Migration status for qtop/riscv64 (2.3.4-3 to 2.3.4-3): Will attempt migration (Any information below is purely informational)
• qtscrob/riscv64 (0.11+git-5 to 0.11+git-5)
  • Migration status for qtscrob/riscv64 (0.11+git-5 to 0.11+git-5): Will attempt migration (Any information below is purely informational)
• qtspell/riscv64 (1.0.1-2 to 1.0.1-2)
  • Migration status for qtspell/riscv64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• qtstyleplugins-src/riscv64 (5.0.0+git23.g335dbec-6 to 5.0.0+git23.g335dbec-6)
  • Migration status for qtstyleplugins-src/riscv64 (5.0.0+git23.g335dbec-6 to 5.0.0+git23.g335dbec-6): Will attempt migration (Any information below is purely informational)
• qtxdg-tools/riscv64 (3.12.0-1 to 3.12.0-1)
  • Migration status for qtxdg-tools/riscv64 (3.12.0-1 to 3.12.0-1): Will attempt migration (Any information below is purely informational)
• quadrapassel/riscv64 (1:40.2-1 to 1:40.2-1)
  • Migration status for quadrapassel/riscv64 (1:40.2-1 to 1:40.2-1): Will attempt migration (Any information below is purely informational)
• quassel/riscv64 (1:0.14.0-2 to 1:0.14.0-2)
  • Migration status for quassel/riscv64 (1:0.14.0-2 to 1:0.14.0-2): Will attempt migration (Any information below is purely informational)
• quickflux/riscv64 (1.1.3+git20201110.2a37acf-2 to 1.1.3+git20201110.2a37acf-2)
  • Migration status for quickflux/riscv64 (1.1.3+git20201110.2a37acf-2 to 1.1.3+git20201110.2a37acf-2): Will attempt migration (Any information below is purely informational)
• quitcount/riscv64 (3.1.4-3 to 3.1.4-3)
  • Migration status for quitcount/riscv64 (3.1.4-3 to 3.1.4-3): Will attempt migration (Any information below is purely informational)
• quiterss/riscv64 (0.19.4+dfsg-1 to 0.19.4+dfsg-1)
  • Migration status for quiterss/riscv64 (0.19.4+dfsg-1 to 0.19.4+dfsg-1): Will attempt migration (Any information below is purely informational)
• qutemol/riscv64 (0.4.1~cvs20081111-15 to 0.4.1~cvs20081111-15)
  • Migration status for qutemol/riscv64 (0.4.1~cvs20081111-15 to 0.4.1~cvs20081111-15): Will attempt migration (Any information below is purely informational)
• quvi/riscv64 (0.9.5-0.2 to 0.9.5-0.2)
  • Migration status for quvi/riscv64 (0.9.5-0.2 to 0.9.5-0.2): Will attempt migration (Any information below is purely informational)
• qviaggiatreno/riscv64 (2013.7.3-12 to 2013.7.3-12)
  • Migration status for qviaggiatreno/riscv64 (2013.7.3-12 to 2013.7.3-12): Will attempt migration (Any information below is purely informational)
• qwo/riscv64 (0.5-4 to 0.5-4)
  • Migration status for qwo/riscv64 (0.5-4 to 0.5-4): Will attempt migration (Any information below is purely informational)
• qwt/riscv64 (6.1.4-2 to 6.1.4-2)
  • Migration status for qwt/riscv64 (6.1.4-2 to 6.1.4-2): Will attempt migration (Any information below is purely informational)
• qwtplot3d/riscv64 (0.2.7+svn191+gcc7-3 to 0.2.7+svn191+gcc7-3)
  • Migration status for qwtplot3d/riscv64 (0.2.7+svn191+gcc7-3 to 0.2.7+svn191+gcc7-3): Will attempt migration (Any information below is purely informational)
• qxmpp/riscv64 (1.5.5-0.4 to 1.5.5-0.4)
  • Migration status for qxmpp/riscv64 (1.5.5-0.4 to 1.5.5-0.4): Will attempt migration (Any information below is purely informational)
• qxw/riscv64 (20200708-2 to 20200708-2)
  • Migration status for qxw/riscv64 (20200708-2 to 20200708-2): Will attempt migration (Any information below is purely informational)
• r-cran-adegenet/riscv64 (2.1.10-1 to 2.1.10-1)
  • Migration status for r-cran-adegenet/riscv64 (2.1.10-1 to 2.1.10-1): Will attempt migration (Any information below is purely informational)
• r-cran-adephylo/riscv64 (1.1-16-1 to 1.1-16-1)
  • Migration status for r-cran-adephylo/riscv64 (1.1-16-1 to 1.1-16-1): Will attempt migration (Any information below is purely informational)
• r-cran-av/riscv64 (0.9.0+dfsg-1 to 0.9.0+dfsg-1)
  • Migration status for r-cran-av/riscv64 (0.9.0+dfsg-1 to 0.9.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-base64url/riscv64 (1.4-2 to 1.4-2)
  • Migration status for r-cran-base64url/riscv64 (1.4-2 to 1.4-2): Will attempt migration (Any information below is purely informational)
• r-cran-batchtools/riscv64 (0.9.17+dfsg-1 to 0.9.17+dfsg-1)
  • Migration status for r-cran-batchtools/riscv64 (0.9.17+dfsg-1 to 0.9.17+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-bbmisc/riscv64 (1.13-1 to 1.13-1)
  • Migration status for r-cran-bbmisc/riscv64 (1.13-1 to 1.13-1): Will attempt migration (Any information below is purely informational)
• r-cran-boolnet/riscv64 (2.1.9-1 to 2.1.9-1)
  • Migration status for r-cran-boolnet/riscv64 (2.1.9-1 to 2.1.9-1): Will attempt migration (Any information below is purely informational)
• r-cran-checkmate/riscv64 (2.3.1-1 to 2.3.1-1)
  • Migration status for r-cran-checkmate/riscv64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-ecodist/riscv64 (2.1.3-1 to 2.1.3-1)
  • Migration status for r-cran-ecodist/riscv64 (2.1.3-1 to 2.1.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-gridtext/riscv64 (0.1.5-2 to 0.1.5-2)
  • Migration status for r-cran-gridtext/riscv64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• r-cran-haplo.stats/riscv64 (1.9.5.1-1 to 1.9.5.1-1)
  • Migration status for r-cran-haplo.stats/riscv64 (1.9.5.1-1 to 1.9.5.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-huge/riscv64 (1.3.5-2 to 1.3.5-2)
  • Migration status for r-cran-huge/riscv64 (1.3.5-2 to 1.3.5-2): Will attempt migration (Any information below is purely informational)
• r-cran-igraph/riscv64 (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-igraph/riscv64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-influencer/riscv64 (0.1.5-1 to 0.1.5-1)
  • Migration status for r-cran-influencer/riscv64 (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-leidenbase/riscv64 (0.1.27-1 to 0.1.27-1)
  • Migration status for r-cran-leidenbase/riscv64 (0.1.27-1 to 0.1.27-1): Will attempt migration (Any information below is purely informational)
• r-cran-lexrankr/riscv64 (0.5.2-8 to 0.5.2-8)
  • Migration status for r-cran-lexrankr/riscv64 (0.5.2-8 to 0.5.2-8): Will attempt migration (Any information below is purely informational)
• r-cran-luminescence/riscv64 (0.9.23-1 to 0.9.23-1)
  • Migration status for r-cran-luminescence/riscv64 (0.9.23-1 to 0.9.23-1): Will attempt migration (Any information below is purely informational)
• r-cran-m2r/riscv64 (1.0.2+dfsg-4 to 1.0.2+dfsg-4)
  • Migration status for r-cran-m2r/riscv64 (1.0.2+dfsg-4 to 1.0.2+dfsg-4): Will attempt migration (Any information below is purely informational)
• r-cran-maotai/riscv64 (0.2.5-1 to 0.2.5-1)
  • Migration status for r-cran-maotai/riscv64 (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-markovchain/riscv64 (0.9.5-1 to 0.9.5-1)
  • Migration status for r-cran-markovchain/riscv64 (0.9.5-1 to 0.9.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-matchit/riscv64 (4.5.5-1 to 4.5.5-1)
  • Migration status for r-cran-matchit/riscv64 (4.5.5-1 to 4.5.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-mice/riscv64 (3.16.0-1 to 3.16.0-1)
  • Migration status for r-cran-mice/riscv64 (3.16.0-1 to 3.16.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-mlr/riscv64 (2.19.1+dfsg-1 to 2.19.1+dfsg-1)
  • Migration status for r-cran-mlr/riscv64 (2.19.1+dfsg-1 to 2.19.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-ncdf4/riscv64 (1.22-1 to 1.22-1)
  • Migration status for r-cran-ncdf4/riscv64 (1.22-1 to 1.22-1): Will attempt migration (Any information below is purely informational)
• r-cran-paramhelpers/riscv64 (1.14.1-1 to 1.14.1-1)
  • Migration status for r-cran-paramhelpers/riscv64 (1.14.1-1 to 1.14.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-pbdzmq/riscv64 (0.3.11+dfsg-1 to 0.3.11+dfsg-1)
  • Migration status for r-cran-pbdzmq/riscv64 (0.3.11+dfsg-1 to 0.3.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-pec/riscv64 (2023.04.12-1 to 2023.04.12-1)
  • Migration status for r-cran-pec/riscv64 (2023.04.12-1 to 2023.04.12-1): Will attempt migration (Any information below is purely informational)
• r-cran-phangorn/riscv64 (2.11.1+dfsg-1 to 2.11.1+dfsg-1)
  • Migration status for r-cran-phangorn/riscv64 (2.11.1+dfsg-1 to 2.11.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-phylobase/riscv64 (0.8.12-1 to 0.8.12-1)
  • Migration status for r-cran-phylobase/riscv64 (0.8.12-1 to 0.8.12-1): Will attempt migration (Any information below is purely informational)
• r-cran-projpred/riscv64 (2.8.0+dfsg-1 to 2.8.0+dfsg-1)
  • Migration status for r-cran-projpred/riscv64 (2.8.0+dfsg-1 to 2.8.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-prophet/riscv64 (1.0+dfsg-5 to 1.0+dfsg-5)
  • Migration status for r-cran-prophet/riscv64 (1.0+dfsg-5 to 1.0+dfsg-5): Will attempt migration (Any information below is purely informational)
• r-cran-qgraph/riscv64 (1.9.8-2 to 1.9.8-2)
  • Migration status for r-cran-qgraph/riscv64 (1.9.8-2 to 1.9.8-2): Will attempt migration (Any information below is purely informational)
• r-cran-raster/riscv64 (3.6-26-1 to 3.6-26-1)
  • Migration status for r-cran-raster/riscv64 (3.6-26-1 to 3.6-26-1): Will attempt migration (Any information below is purely informational)
• r-cran-relsurv/riscv64 (2.2-9-1 to 2.2-9-1)
  • Migration status for r-cran-relsurv/riscv64 (2.2-9-1 to 2.2-9-1): Will attempt migration (Any information below is purely informational)
• r-cran-riskregression/riscv64 (2023.12.21+ds-1 to 2023.12.21+ds-1)
  • Migration status for r-cran-riskregression/riscv64 (2023.12.21+ds-1 to 2023.12.21+ds-1): Will attempt migration (Any information below is purely informational)
• r-cran-rnetcdf/riscv64 (2.9-1-1 to 2.9-1-1)
  • Migration status for r-cran-rnetcdf/riscv64 (2.9-1-1 to 2.9-1-1): Will attempt migration (Any information below is purely informational)
• r-cran-rstan/riscv64 (2.32.5-2 to 2.32.5-2)
  • Migration status for r-cran-rstan/riscv64 (2.32.5-2 to 2.32.5-2): Will attempt migration (Any information below is purely informational)
• r-cran-rstanarm/riscv64 (2.32.1-2 to 2.32.1-2)
  • Migration status for r-cran-rstanarm/riscv64 (2.32.1-2 to 2.32.1-2): Will attempt migration (Any information below is purely informational)
• r-cran-rsvg/riscv64 (2.6.0-1 to 2.6.0-1)
  • Migration status for r-cran-rsvg/riscv64 (2.6.0-1 to 2.6.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-tcr/riscv64 (2.3.2+ds-1 to 2.3.2+ds-1)
  • Migration status for r-cran-tcr/riscv64 (2.3.2+ds-1 to 2.3.2+ds-1): Will attempt migration (Any information below is purely informational)
• r-cran-treespace/riscv64 (1.1.4.3+dfsg-1 to 1.1.4.3+dfsg-1)
  • Migration status for r-cran-treespace/riscv64 (1.1.4.3+dfsg-1 to 1.1.4.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-vdiffr/riscv64 (1.0.7-1 to 1.0.7-1)
  • Migration status for r-cran-vdiffr/riscv64 (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
• r-cran-webgestaltr/riscv64 (0.4.6-1 to 0.4.6-1)
  • Migration status for r-cran-webgestaltr/riscv64 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• r-cran-xml2/riscv64 (1.3.6-1 to 1.3.6-1)
  • Migration status for r-cran-xml2/riscv64 (1.3.6-1 to 1.3.6-1): Will attempt migration (Any information below is purely informational)
• radium-compressor/riscv64 (0.5.1+git20190909-1 to 0.5.1+git20190909-1)
  • Migration status for radium-compressor/riscv64 (0.5.1+git20190909-1 to 0.5.1+git20190909-1): Will attempt migration (Any information below is purely informational)
• raincat/riscv64 (1.2.1-1 to 1.2.1-1)
  • Migration status for raincat/riscv64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• rancid/riscv64 (3.13-3 to 3.13-3)
  • Migration status for rancid/riscv64 (3.13-3 to 3.13-3): Will attempt migration (Any information below is purely informational)
• rapache/riscv64 (1.2.10-2 to 1.2.10-2)
  • Migration status for rapache/riscv64 (1.2.10-2 to 1.2.10-2): Will attempt migration (Any information below is purely informational)
• rarcrack/riscv64 (0.2-1.1 to 0.2-1.1)
  • Migration status for rarcrack/riscv64 (0.2-1.1 to 0.2-1.1): Will attempt migration (Any information below is purely informational)
• rasmol/riscv64 (2.7.6.0-3 to 2.7.6.0-3)
  • Migration status for rasmol/riscv64 (2.7.6.0-3 to 2.7.6.0-3): Will attempt migration (Any information below is purely informational)
• rasqal/riscv64 (0.9.33-2.1 to 0.9.33-2.1)
  • Migration status for rasqal/riscv64 (0.9.33-2.1 to 0.9.33-2.1): Will attempt migration (Any information below is purely informational)
• raster3d/riscv64 (3.0-7-2 to 3.0-7-2)
  • Migration status for raster3d/riscv64 (3.0-7-2 to 3.0-7-2): Will attempt migration (Any information below is purely informational)
• rasterio/riscv64 (1.3.10-2 to 1.3.10-2)
  • Migration status for rasterio/riscv64 (1.3.10-2 to 1.3.10-2): Will attempt migration (Any information below is purely informational)
• rawtherapee/amd64 (5.10-1 to 5.10-1)
  • Migration status for rawtherapee/amd64 (5.10-1 to 5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rawtherapee/amd64 exiv2
• rawtherapee/arm64 (5.10-1 to 5.10-1)
  • Migration status for rawtherapee/arm64 (5.10-1 to 5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rawtherapee/arm64 exiv2
• rawtherapee/armel (5.10-1 to 5.10-1)
  • Migration status for rawtherapee/armel (5.10-1 to 5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rawtherapee/armel exiv2
• rawtherapee/armhf (5.10-1 to 5.10-1)
  • Migration status for rawtherapee/armhf (5.10-1 to 5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rawtherapee/armhf exiv2
• rawtherapee/i386 (5.10-1 to 5.10-1)
  • Migration status for rawtherapee/i386 (5.10-1 to 5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rawtherapee/i386 exiv2
• rawtherapee/mips64el (5.10-1 to 5.10-1)
  • Migration status for rawtherapee/mips64el (5.10-1 to 5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rawtherapee/mips64el exiv2
• rawtherapee/ppc64el (5.10-1 to 5.10-1)
  • Migration status for rawtherapee/ppc64el (5.10-1 to 5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rawtherapee/ppc64el exiv2
• rawtherapee/riscv64 (5.10-1 to 5.10-1)
  • Migration status for rawtherapee/riscv64 (5.10-1 to 5.10-1): Will attempt migration (Any information below is purely informational)
• rawtherapee/s390x (5.10-1 to 5.10-1)
  • Migration status for rawtherapee/s390x (5.10-1 to 5.10-1): Will attempt migration (Any information below is purely informational)
    • Depends: rawtherapee/s390x exiv2
• ray/riscv64 (2.3.1-8 to 2.3.1-8)
  • Migration status for ray/riscv64 (2.3.1-8 to 2.3.1-8): Will attempt migration (Any information below is purely informational)
• rebar/riscv64 (2.6.4-4 to 2.6.4-4)
  • Migration status for rebar/riscv64 (2.6.4-4 to 2.6.4-4): Will attempt migration (Any information below is purely informational)
• recoverjpeg/riscv64 (2.6.3-5 to 2.6.3-5)
  • Migration status for recoverjpeg/riscv64 (2.6.3-5 to 2.6.3-5): Will attempt migration (Any information below is purely informational)
• redeclipse/riscv64 (1.6.0-1 to 1.6.0-1)
  • Migration status for redeclipse/riscv64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
• redland-bindings/riscv64 (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6)
  • Migration status for redland-bindings/riscv64 (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6): Will attempt migration (Any information below is purely informational)
• redshift-qt/riscv64 (0.6-3 to 0.6-3)
  • Migration status for redshift-qt/riscv64 (0.6-3 to 0.6-3): Will attempt migration (Any information below is purely informational)
• refnx/riscv64 (0.1.38-1 to 0.1.38-1)
  • Migration status for refnx/riscv64 (0.1.38-1 to 0.1.38-1): Will attempt migration (Any information below is purely informational)
• reform-firedecor/riscv64 (2023-10-23-4 to 2023-10-23-4)
  • Migration status for reform-firedecor/riscv64 (2023-10-23-4 to 2023-10-23-4): Will attempt migration (Any information below is purely informational)
• regexxer/riscv64 (0.10-6 to 0.10-6)
  • Migration status for regexxer/riscv64 (0.10-6 to 0.10-6): Will attempt migration (Any information below is purely informational)
• relion/riscv64 (3.1.3-3 to 3.1.3-3)
  • Migration status for relion/riscv64 (3.1.3-3 to 3.1.3-3): Will attempt migration (Any information below is purely informational)
• remote-logon-service/riscv64 (1.0.2.90-4 to 1.0.2.90-4)
  • Migration status for remote-logon-service/riscv64 (1.0.2.90-4 to 1.0.2.90-4): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• repmgr/riscv64 (5.4.1-1 to 5.4.1-1)
  • Migration status for repmgr/riscv64 (5.4.1-1 to 5.4.1-1): Will attempt migration (Any information below is purely informational)
• reprepro/riscv64 (5.3.1-5 to 5.3.1-5)
  • Migration status for reprepro/riscv64 (5.3.1-5 to 5.3.1-5): Will attempt migration (Any information below is purely informational)
• reprepro_pu (5.3.1-5 to 5.3.1-1+deb12u2)
  • Migration status for reprepro_pu (5.3.1-5 to 5.3.1-1+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: reprepro is newer in the target suite (5.3.1-5 5.3.1-1+deb12u2)
• revelation/riscv64 (0.5.5-1 to 0.5.5-1)
  • Migration status for revelation/riscv64 (0.5.5-1 to 0.5.5-1): Will attempt migration (Any information below is purely informational)
• rfdump/riscv64 (1.6-9.1 to 1.6-9.1)
  • Migration status for rfdump/riscv64 (1.6-9.1 to 1.6-9.1): Will attempt migration (Any information below is purely informational)
• rgbpaint/riscv64 (0.8.7-6.1 to 0.8.7-6.1)
  • Migration status for rgbpaint/riscv64 (0.8.7-6.1 to 0.8.7-6.1): Will attempt migration (Any information below is purely informational)
• rgl/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for rgl/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• rheolef/riscv64 (7.2-3 to 7.2-3)
  • Migration status for rheolef/riscv64 (7.2-3 to 7.2-3): Will attempt migration (Any information below is purely informational)
• rhythmbox/riscv64 (3.4.7-2 to 3.4.7-2)
  • Migration status for rhythmbox/riscv64 (3.4.7-2 to 3.4.7-2): Will attempt migration (Any information below is purely informational)
• ristretto/riscv64 (0.13.2-1 to 0.13.2-1)
  • Migration status for ristretto/riscv64 (0.13.2-1 to 0.13.2-1): Will attempt migration (Any information below is purely informational)
• rjava/riscv64 (1.0-11-1 to 1.0-11-1)
  • Migration status for rjava/riscv64 (1.0-11-1 to 1.0-11-1): Will attempt migration (Any information below is purely informational)
• rlvm/riscv64 (0.14-5.2 to 0.14-5.2)
  • Migration status for rlvm/riscv64 (0.14-5.2 to 0.14-5.2): Will attempt migration (Any information below is purely informational)
• robocut/riscv64 (1.0.11-1 to 1.0.11-1)
  • Migration status for robocut/riscv64 (1.0.11-1 to 1.0.11-1): Will attempt migration (Any information below is purely informational)
• rocm-compilersupport/riscv64 (6.0+git20231212.4510c28+dfsg-3 to 6.0+git20231212.4510c28+dfsg-3)
  • Migration status for rocm-compilersupport/riscv64 (6.0+git20231212.4510c28+dfsg-3 to 6.0+git20231212.4510c28+dfsg-3): Will attempt migration (Any information below is purely informational)
• rocs/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for rocs/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• rofi/riscv64 (1.7.5-0.1 to 1.7.5-0.1)
  • Migration status for rofi/riscv64 (1.7.5-0.1 to 1.7.5-0.1): Will attempt migration (Any information below is purely informational)
• ros-diagnostics/riscv64 (1.11.0+ds-7 to 1.11.0+ds-7)
  • Migration status for ros-diagnostics/riscv64 (1.11.0+ds-7 to 1.11.0+ds-7): Will attempt migration (Any information below is purely informational)
• ros-image-common/riscv64 (1.12.0-12.1 to 1.12.0-12.1)
  • Migration status for ros-image-common/riscv64 (1.12.0-12.1 to 1.12.0-12.1): Will attempt migration (Any information below is purely informational)
• ros-image-pipeline/riscv64 (1.17.0-1 to 1.17.0-1)
  • Migration status for ros-image-pipeline/riscv64 (1.17.0-1 to 1.17.0-1): Will attempt migration (Any information below is purely informational)
• ros-image-transport-plugins/riscv64 (1.15.0-3 to 1.15.0-3)
  • Migration status for ros-image-transport-plugins/riscv64 (1.15.0-3 to 1.15.0-3): Will attempt migration (Any information below is purely informational)
• ros-kdl-parser/riscv64 (1.14.2-2 to 1.14.2-2)
  • Migration status for ros-kdl-parser/riscv64 (1.14.2-2 to 1.14.2-2): Will attempt migration (Any information below is purely informational)
• ros-laser-geometry/riscv64 (1.6.7-5 to 1.6.7-5)
  • Migration status for ros-laser-geometry/riscv64 (1.6.7-5 to 1.6.7-5): Will attempt migration (Any information below is purely informational)
• ros-opencv-apps/riscv64 (2.0.2-9 to 2.0.2-9)
  • Migration status for ros-opencv-apps/riscv64 (2.0.2-9 to 2.0.2-9): Will attempt migration (Any information below is purely informational)
• ros-robot-state-publisher/riscv64 (1.15.2-5 to 1.15.2-5)
  • Migration status for ros-robot-state-publisher/riscv64 (1.15.2-5 to 1.15.2-5): Will attempt migration (Any information below is purely informational)
• ros-urdf/riscv64 (1.13.2-8 to 1.13.2-8)
  • Migration status for ros-urdf/riscv64 (1.13.2-8 to 1.13.2-8): Will attempt migration (Any information below is purely informational)
• rrdtool/riscv64 (1.7.2-4.1 to 1.7.2-4.1)
  • Migration status for rrdtool/riscv64 (1.7.2-4.1 to 1.7.2-4.1): Will attempt migration (Any information below is purely informational)
• rrootage/riscv64 (0.23a-13 to 0.23a-13)
  • Migration status for rrootage/riscv64 (0.23a-13 to 0.23a-13): Will attempt migration (Any information below is purely informational)
• rsibreak/riscv64 (4:0.12.15-1 to 4:0.12.15-1)
  • Migration status for rsibreak/riscv64 (4:0.12.15-1 to 4:0.12.15-1): Will attempt migration (Any information below is purely informational)
• rsplib/riscv64 (3.4.4-1.1 to 3.4.4-1.1)
  • Migration status for rsplib/riscv64 (3.4.4-1.1 to 3.4.4-1.1): Will attempt migration (Any information below is purely informational)
• rss-glx/riscv64 (0.9.1-6.5 to 0.9.1-6.5)
  • Migration status for rss-glx/riscv64 (0.9.1-6.5 to 0.9.1-6.5): Will attempt migration (Any information below is purely informational)
• rtklib/riscv64 (2.4.3.b34+dfsg-1 to 2.4.3.b34+dfsg-1)
  • Migration status for rtklib/riscv64 (2.4.3.b34+dfsg-1 to 2.4.3.b34+dfsg-1): 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-grib/riscv64 (0.4.0-6 to 0.4.0-6)
  • Migration status for ruby-grib/riscv64 (0.4.0-6 to 0.4.0-6): Will attempt migration (Any information below is purely informational)
• ruby-mimemagic/riscv64 (0.4.3-1 to 0.4.3-1)
  • Migration status for ruby-mimemagic/riscv64 (0.4.3-1 to 0.4.3-1): 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-nokogiri/riscv64 (1.16.4+dfsg-1 to 1.16.4+dfsg-1)
  • Migration status for ruby-nokogiri/riscv64 (1.16.4+dfsg-1 to 1.16.4+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-nokogumbo/riscv64 (2.0.5-1 to 2.0.5-1)
  • Migration status for ruby-nokogumbo/riscv64 (2.0.5-1 to 2.0.5-1): 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-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-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)
• runcircos-gui/riscv64 (0.0+git20200528.82dda8c-1 to 0.0+git20200528.82dda8c-1)
  • Migration status for runcircos-gui/riscv64 (0.0+git20200528.82dda8c-1 to 0.0+git20200528.82dda8c-1): Will attempt migration (Any information below is purely informational)
• rust-actix-rt/riscv64 (2.8.0-1 to 2.8.0-1)
  • Migration status for rust-actix-rt/riscv64 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-ammonia/riscv64 (3.3.0-1 to 3.3.0-1)
  • Migration status for rust-ammonia/riscv64 (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-arboard/riscv64 (3.4.0-1 to 3.4.0-1)
  • Migration status for rust-arboard/riscv64 (3.4.0-1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-askama/riscv64 (0.12.1-4 to 0.12.1-4)
  • Migration status for rust-askama/riscv64 (0.12.1-4 to 0.12.1-4): Will attempt migration (Any information below is purely informational)
• rust-async-std-resolver/riscv64 (0.24.0-1 to 0.24.0-1)
  • Migration status for rust-async-std-resolver/riscv64 (0.24.0-1 to 0.24.0-1): Will attempt migration (Any information below is purely informational)
• rust-barrel/riscv64 (0.7.0-3 to 0.7.0-3)
  • Migration status for rust-barrel/riscv64 (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
• rust-bat/riscv64 (0.24.0-1 to 0.24.0-1)
  • Migration status for rust-bat/riscv64 (0.24.0-1 to 0.24.0-1): Will attempt migration (Any information below is purely informational)
• rust-better-panic/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-better-panic/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-capstone-sys/riscv64 (0.15.0-2 to 0.15.0-2)
  • Migration status for rust-capstone-sys/riscv64 (0.15.0-2 to 0.15.0-2): Will attempt migration (Any information below is purely informational)
• rust-capstone/riscv64 (0.11.0-2 to 0.11.0-2)
  • Migration status for rust-capstone/riscv64 (0.11.0-2 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
• rust-cmake/riscv64 (0.1.45-1 to 0.1.45-1)
  • Migration status for rust-cmake/riscv64 (0.1.45-1 to 0.1.45-1): Will attempt migration (Any information below is purely informational)
• rust-crypto-hash/riscv64 (0.3.4-1 to 0.3.4-1)
  • Migration status for rust-crypto-hash/riscv64 (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
• rust-cssparser/riscv64 (0.31.2-2 to 0.31.2-2)
  • Migration status for rust-cssparser/riscv64 (0.31.2-2 to 0.31.2-2): Will attempt migration (Any information below is purely informational)
• rust-curl-sys/riscv64 (0.4.67-2 to 0.4.67-2)
  • Migration status for rust-curl-sys/riscv64 (0.4.67-2 to 0.4.67-2): Will attempt migration (Any information below is purely informational)
• rust-curl/riscv64 (0.4.44-4 to 0.4.44-4)
  • Migration status for rust-curl/riscv64 (0.4.44-4 to 0.4.44-4): Will attempt migration (Any information below is purely informational)
• rust-debbugs/riscv64 (0.1.1-1 to 0.1.1-1)
  • Migration status for rust-debbugs/riscv64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-diesel-migrations/riscv64 (2.0.0-2 to 2.0.0-2)
  • Migration status for rust-diesel-migrations/riscv64 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• rust-diesel/riscv64 (2.0.3-4 to 2.0.3-4)
  • Migration status for rust-diesel/riscv64 (2.0.3-4 to 2.0.3-4): Will attempt migration (Any information below is purely informational)
• rust-doxygen-rs/riscv64 (0.4.2-1 to 0.4.2-1)
  • Migration status for rust-doxygen-rs/riscv64 (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• rust-erbium-core/riscv64 (1.0.5-4 to 1.0.5-4)
  • Migration status for rust-erbium-core/riscv64 (1.0.5-4 to 1.0.5-4): Will attempt migration (Any information below is purely informational)
• rust-exacl/riscv64 (0.10.0-1 to 0.10.0-1)
  • Migration status for rust-exacl/riscv64 (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• rust-expat-sys/riscv64 (2.1.6-3 to 2.1.6-3)
  • Migration status for rust-expat-sys/riscv64 (2.1.6-3 to 2.1.6-3): Will attempt migration (Any information below is purely informational)
• rust-fernet/riscv64 (0.2.0+really0.1.4-3 to 0.2.0+really0.1.4-3)
  • Migration status for rust-fernet/riscv64 (0.2.0+really0.1.4-3 to 0.2.0+really0.1.4-3): Will attempt migration (Any information below is purely informational)
• rust-font-kit/riscv64 (0.11.0-2 to 0.11.0-2)
  • Migration status for rust-font-kit/riscv64 (0.11.0-2 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
• rust-freetype-rs/riscv64 (0.26.0-1 to 0.26.0-1)
  • Migration status for rust-freetype-rs/riscv64 (0.26.0-1 to 0.26.0-1): Will attempt migration (Any information below is purely informational)
• rust-freetype-sys/riscv64 (0.13.1-1 to 0.13.1-1)
  • Migration status for rust-freetype-sys/riscv64 (0.13.1-1 to 0.13.1-1): Will attempt migration (Any information below is purely informational)
• rust-freetype/riscv64 (0.7.0-4 to 0.7.0-4)
  • Migration status for rust-freetype/riscv64 (0.7.0-4 to 0.7.0-4): Will attempt migration (Any information below is purely informational)
• rust-fts-sys/riscv64 (0.2.7-1 to 0.2.7-1)
  • Migration status for rust-fts-sys/riscv64 (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• rust-git-absorb/riscv64 (0.6.11-1 to 0.6.11-1)
  • Migration status for rust-git-absorb/riscv64 (0.6.11-1 to 0.6.11-1): Will attempt migration (Any information below is purely informational)
• rust-git2-curl/riscv64 (0.19.0-1 to 0.19.0-1)
  • Migration status for rust-git2-curl/riscv64 (0.19.0-1 to 0.19.0-1): Will attempt migration (Any information below is purely informational)
• rust-gix-attributes/riscv64 (0.22.2-1 to 0.22.2-1)
  • Migration status for rust-gix-attributes/riscv64 (0.22.2-1 to 0.22.2-1): Will attempt migration (Any information below is purely informational)
• rust-gix-commitgraph/riscv64 (0.24.2-1 to 0.24.2-1)
  • Migration status for rust-gix-commitgraph/riscv64 (0.24.2-1 to 0.24.2-1): Will attempt migration (Any information below is purely informational)
• rust-gix-credentials/riscv64 (0.24.2-1 to 0.24.2-1)
  • Migration status for rust-gix-credentials/riscv64 (0.24.2-1 to 0.24.2-1): Will attempt migration (Any information below is purely informational)
• rust-gix-fs/riscv64 (0.10.2-1 to 0.10.2-1)
  • Migration status for rust-gix-fs/riscv64 (0.10.2-1 to 0.10.2-1): Will attempt migration (Any information below is purely informational)
• rust-gix-glob/riscv64 (0.16.2-1 to 0.16.2-1)
  • Migration status for rust-gix-glob/riscv64 (0.16.2-1 to 0.16.2-1): Will attempt migration (Any information below is purely informational)
• rust-gix-ignore/riscv64 (0.11.2-1 to 0.11.2-1)
  • Migration status for rust-gix-ignore/riscv64 (0.11.2-1 to 0.11.2-1): Will attempt migration (Any information below is purely informational)
• rust-gix-lock/riscv64 (13.1.1-1 to 13.1.1-1)
  • Migration status for rust-gix-lock/riscv64 (13.1.1-1 to 13.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-gix-mailmap/riscv64 (0.23.0-1 to 0.23.0-1)
  • Migration status for rust-gix-mailmap/riscv64 (0.23.0-1 to 0.23.0-1): Will attempt migration (Any information below is purely informational)
• rust-gix-tempfile/riscv64 (13.1.1-1 to 13.1.1-1)
  • Migration status for rust-gix-tempfile/riscv64 (13.1.1-1 to 13.1.1-1): Will attempt migration (Any information below is purely informational)
• rust-gix-url/riscv64 (0.27.3-1 to 0.27.3-1)
  • Migration status for rust-gix-url/riscv64 (0.27.3-1 to 0.27.3-1): Will attempt migration (Any information below is purely informational)
• rust-hafas-rs/riscv64 (0.2.1-1 to 0.2.1-1)
  • Migration status for rust-hafas-rs/riscv64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• rust-harfbuzz-rs/riscv64 (1.2.0-2 to 1.2.0-2)
  • Migration status for rust-harfbuzz-rs/riscv64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-harfbuzz-sys/riscv64 (0.5.0+really.0.4.1-5 to 0.5.0+really.0.4.1-5)
  • Migration status for rust-harfbuzz-sys/riscv64 (0.5.0+really.0.4.1-5 to 0.5.0+really.0.4.1-5): Will attempt migration (Any information below is purely informational)
• rust-hickory-client/riscv64 (0.24.1-1 to 0.24.1-1)
  • Migration status for rust-hickory-client/riscv64 (0.24.1-1 to 0.24.1-1): Will attempt migration (Any information below is purely informational)
• rust-hickory-resolver/riscv64 (0.24.1-1 to 0.24.1-1)
  • Migration status for rust-hickory-resolver/riscv64 (0.24.1-1 to 0.24.1-1): Will attempt migration (Any information below is purely informational)
• rust-html2md/riscv64 (0.2.14-1 to 0.2.14-1)
  • Migration status for rust-html2md/riscv64 (0.2.14-1 to 0.2.14-1): Will attempt migration (Any information below is purely informational)
• rust-html2pango/riscv64 (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-html2pango/riscv64 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-html2text/riscv64 (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-html2text/riscv64 (0.4.4-1 to 0.4.4-1): Will attempt migration (Any information below is purely informational)
• rust-html5ever/riscv64 (0.26.0-1 to 0.26.0-1)
  • Migration status for rust-html5ever/riscv64 (0.26.0-1 to 0.26.0-1): Will attempt migration (Any information below is purely informational)
• rust-hyper-tls/riscv64 (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-hyper-tls/riscv64 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-io-uring/riscv64 (0.6.1-1 to 0.6.1-1)
  • Migration status for rust-io-uring/riscv64 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• rust-libcst/riscv64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-libcst/riscv64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-libraw-rs-sys/riscv64 (0.0.4-1 to 0.0.4-1)
  • Migration status for rust-libraw-rs-sys/riscv64 (0.0.4-1 to 0.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-libraw-rs/riscv64 (0.0.4-1 to 0.0.4-1)
  • Migration status for rust-libraw-rs/riscv64 (0.0.4-1 to 0.0.4-1): Will attempt migration (Any information below is purely informational)
• rust-libsqlite3-sys/riscv64 (0.26.0-1 to 0.26.0-1)
  • Migration status for rust-libsqlite3-sys/riscv64 (0.26.0-1 to 0.26.0-1): Will attempt migration (Any information below is purely informational)
• rust-libssh2-sys/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-libssh2-sys/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-loopdev/riscv64 (0.4.0-4 to 0.4.0-4)
  • Migration status for rust-loopdev/riscv64 (0.4.0-4 to 0.4.0-4): Will attempt migration (Any information below is purely informational)
• rust-markup5ever-rcdom/riscv64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-markup5ever-rcdom/riscv64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-markup5ever/riscv64 (0.11.0-2 to 0.11.0-2)
  • Migration status for rust-markup5ever/riscv64 (0.11.0-2 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
• rust-native-tls/riscv64 (0.2.11-2 to 0.2.11-2)
  • Migration status for rust-native-tls/riscv64 (0.2.11-2 to 0.2.11-2): Will attempt migration (Any information below is purely informational)
• rust-nettle-sys/riscv64 (2.2.0-2 to 2.2.0-2)
  • Migration status for rust-nettle-sys/riscv64 (2.2.0-2 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
• rust-nettle/riscv64 (7.3.0-1 to 7.3.0-1)
  • Migration status for rust-nettle/riscv64 (7.3.0-1 to 7.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-oauth2/riscv64 (4.4.1-2 to 4.4.1-2)
  • Migration status for rust-oauth2/riscv64 (4.4.1-2 to 4.4.1-2): Will attempt migration (Any information below is purely informational)
• rust-onig-sys/riscv64 (69.8.1-1 to 69.8.1-1)
  • Migration status for rust-onig-sys/riscv64 (69.8.1-1 to 69.8.1-1): Will attempt migration (Any information below is purely informational)
• rust-onig/riscv64 (6.3.2-1 to 6.3.2-1)
  • Migration status for rust-onig/riscv64 (6.3.2-1 to 6.3.2-1): Will attempt migration (Any information below is purely informational)
• rust-openpgp-keylist/riscv64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-openpgp-keylist/riscv64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-openssl-sys/riscv64 (0.9.101-1 to 0.9.101-1)
  • Migration status for rust-openssl-sys/riscv64 (0.9.101-1 to 0.9.101-1): Will attempt migration (Any information below is purely informational)
• rust-openssl/riscv64 (0.10.64-1 to 0.10.64-1)
  • Migration status for rust-openssl/riscv64 (0.10.64-1 to 0.10.64-1): Will attempt migration (Any information below is purely informational)
• rust-osmesa-sys/riscv64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-osmesa-sys/riscv64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• rust-palette/riscv64 (0.7.5-1 to 0.7.5-1)
  • Migration status for rust-palette/riscv64 (0.7.5-1 to 0.7.5-1): Will attempt migration (Any information below is purely informational)
• rust-parsec-client/riscv64 (0.16.0-1 to 0.16.0-1)
  • Migration status for rust-parsec-client/riscv64 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
• rust-parsec-tool/riscv64 (0.7.0-4 to 0.7.0-4)
  • Migration status for rust-parsec-tool/riscv64 (0.7.0-4 to 0.7.0-4): Will attempt migration (Any information below is purely informational)
• rust-phf-codegen/riscv64 (0.11.2-1 to 0.11.2-1)
  • Migration status for rust-phf-codegen/riscv64 (0.11.2-1 to 0.11.2-1): Will attempt migration (Any information below is purely informational)
• rust-phf-macros/riscv64 (0.11.2-1 to 0.11.2-1)
  • Migration status for rust-phf-macros/riscv64 (0.11.2-1 to 0.11.2-1): Will attempt migration (Any information below is purely informational)
• rust-prometheus/riscv64 (0.13.3-2 to 0.13.3-2)
  • Migration status for rust-prometheus/riscv64 (0.13.3-2 to 0.13.3-2): Will attempt migration (Any information below is purely informational)
• rust-psa-crypto-sys/riscv64 (0.9.3-2 to 0.9.3-2)
  • Migration status for rust-psa-crypto-sys/riscv64 (0.9.3-2 to 0.9.3-2): Will attempt migration (Any information below is purely informational)
• rust-psa-crypto/riscv64 (0.9.2-3 to 0.9.2-3)
  • Migration status for rust-psa-crypto/riscv64 (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
• rust-pyproject-toml/riscv64 (0.7.0-2 to 0.7.0-2)
  • Migration status for rust-pyproject-toml/riscv64 (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
• rust-python-pkginfo/riscv64 (0.5.5-1 to 0.5.5-1)
  • Migration status for rust-python-pkginfo/riscv64 (0.5.5-1 to 0.5.5-1): Will attempt migration (Any information below is purely informational)
• rust-rb-sys-build/riscv64 (0.9.97-1 to 0.9.97-1)
  • Migration status for rust-rb-sys-build/riscv64 (0.9.97-1 to 0.9.97-1): Will attempt migration (Any information below is purely informational)
• rust-rb-sys/riscv64 (0.9.97-1 to 0.9.97-1)
  • Migration status for rust-rb-sys/riscv64 (0.9.97-1 to 0.9.97-1): Will attempt migration (Any information below is purely informational)
• rust-rusqlite/riscv64 (0.29.0-3 to 0.29.0-3)
  • Migration status for rust-rusqlite/riscv64 (0.29.0-3 to 0.29.0-3): Will attempt migration (Any information below is purely informational)
• rust-rust-cast/riscv64 (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-rust-cast/riscv64 (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-rusty-paserk/s390x (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-rusty-paserk/s390x (0.4.0-1 to 0.4.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-rusty-paserk/s390x rust-rusty-paseto (not considered)
    • Invalidated by dependency
    • Depends: rust-rusty-paserk/s390x rust-curve25519-dalek (not considered)
• rust-selectors/riscv64 (0.25.0-2 to 0.25.0-2)
  • Migration status for rust-selectors/riscv64 (0.25.0-2 to 0.25.0-2): Will attempt migration (Any information below is purely informational)
• rust-sequoia-autocrypt/riscv64 (0.25.1-1 to 0.25.1-1)
  • Migration status for rust-sequoia-autocrypt/riscv64 (0.25.1-1 to 0.25.1-1): Will attempt migration (Any information below is purely informational)
• rust-sequoia-net/riscv64 (0.28.0-1 to 0.28.0-1)
  • Migration status for rust-sequoia-net/riscv64 (0.28.0-1 to 0.28.0-1): Will attempt migration (Any information below is purely informational)
• rust-sequoia-openpgp-mt/riscv64 (0.1.0-2 to 0.1.0-2)
  • Migration status for rust-sequoia-openpgp-mt/riscv64 (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-sequoia-policy-config/riscv64 (0.6.0-4 to 0.6.0-4)
  • Migration status for rust-sequoia-policy-config/riscv64 (0.6.0-4 to 0.6.0-4): Will attempt migration (Any information below is purely informational)
• rust-servo-fontconfig-sys/riscv64 (5.1.0-2 to 5.1.0-2)
  • Migration status for rust-servo-fontconfig-sys/riscv64 (5.1.0-2 to 5.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-servo-fontconfig/riscv64 (0.5.1-1 to 0.5.1-1)
  • Migration status for rust-servo-fontconfig/riscv64 (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• rust-servo-freetype-sys/riscv64 (4.0.5-3 to 4.0.5-3)
  • Migration status for rust-servo-freetype-sys/riscv64 (4.0.5-3 to 4.0.5-3): Will attempt migration (Any information below is purely informational)
• rust-shared-library/riscv64 (0.1.9-2 to 0.1.9-2)
  • Migration status for rust-shared-library/riscv64 (0.1.9-2 to 0.1.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
• rust-sqlx-sqlite/riscv64 (0.7.3-1 to 0.7.3-1)
  • Migration status for rust-sqlx-sqlite/riscv64 (0.7.3-1 to 0.7.3-1): Will attempt migration (Any information below is purely informational)
• rust-ssh2/riscv64 (0.9.4-1 to 0.9.4-1)
  • Migration status for rust-ssh2/riscv64 (0.9.4-1 to 0.9.4-1): Will attempt migration (Any information below is purely informational)
• rust-string-cache-codegen/riscv64 (0.5.2-2 to 0.5.2-2)
  • Migration status for rust-string-cache-codegen/riscv64 (0.5.2-2 to 0.5.2-2): Will attempt migration (Any information below is purely informational)
• rust-syntect/riscv64 (5.1.0-2 to 5.1.0-2)
  • Migration status for rust-syntect/riscv64 (5.1.0-2 to 5.1.0-2): Will attempt migration (Any information below is purely informational)
• rust-sys-mount/riscv64 (3.0.1-1 to 3.0.1-1)
  • Migration status for rust-sys-mount/riscv64 (3.0.1-1 to 3.0.1-1): Will attempt migration (Any information below is purely informational)
• rust-tera/riscv64 (1.19.1-3 to 1.19.1-3)
  • Migration status for rust-tera/riscv64 (1.19.1-3 to 1.19.1-3): Will attempt migration (Any information below is purely informational)
• rust-terminfo/riscv64 (0.8.0-1 to 0.8.0-1)
  • Migration status for rust-terminfo/riscv64 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• rust-tiny-http/riscv64 (0.12.0-1 to 0.12.0-1)
  • Migration status for rust-tiny-http/riscv64 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-native-tls/riscv64 (0.3.1-1 to 0.3.1-1)
  • Migration status for rust-tokio-native-tls/riscv64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-openssl/riscv64 (0.6.3-1 to 0.6.3-1)
  • Migration status for rust-tokio-openssl/riscv64 (0.6.3-1 to 0.6.3-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-tungstenite/riscv64 (0.20.1-1 to 0.20.1-1)
  • Migration status for rust-tokio-tungstenite/riscv64 (0.20.1-1 to 0.20.1-1): Will attempt migration (Any information below is purely informational)
• rust-tokio-uring/riscv64 (0.4.0-3 to 0.4.0-3)
  • Migration status for rust-tokio-uring/riscv64 (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• rust-tree-sitter-cli/riscv64 (0.20.8-5 to 0.20.8-5)
  • Migration status for rust-tree-sitter-cli/riscv64 (0.20.8-5 to 0.20.8-5): Will attempt migration (Any information below is purely informational)
• rust-trust-dns-client/riscv64 (0.22.0-5 to 0.22.0-5)
  • Migration status for rust-trust-dns-client/riscv64 (0.22.0-5 to 0.22.0-5): Will attempt migration (Any information below is purely informational)
• rust-trust-dns-resolver/riscv64 (0.22.0-4 to 0.22.0-4)
  • Migration status for rust-trust-dns-resolver/riscv64 (0.22.0-4 to 0.22.0-4): Will attempt migration (Any information below is purely informational)
• rust-tss-esapi-sys/riscv64 (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-tss-esapi-sys/riscv64 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• rust-tss-esapi/riscv64 (7.4.0-1 to 7.4.0-1)
  • Migration status for rust-tss-esapi/riscv64 (7.4.0-1 to 7.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-tungstenite/riscv64 (0.20.1-2 to 0.20.1-2)
  • Migration status for rust-tungstenite/riscv64 (0.20.1-2 to 0.20.1-2): Will attempt migration (Any information below is purely informational)
• rust-unzip/riscv64 (0.1.0-1 to 0.1.0-1)
  • Migration status for rust-unzip/riscv64 (0.1.0-1 to 0.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-urlshortener/riscv64 (3.0.2-2 to 3.0.2-2)
  • Migration status for rust-urlshortener/riscv64 (3.0.2-2 to 3.0.2-2): Will attempt migration (Any information below is purely informational)
• rust-wayland-commons/riscv64 (0.29.5-2 to 0.29.5-2)
  • Migration status for rust-wayland-commons/riscv64 (0.29.5-2 to 0.29.5-2): Will attempt migration (Any information below is purely informational)
• rust-wayland-egl-0.29/riscv64 (0.29.5-2 to 0.29.5-2)
  • Migration status for rust-wayland-egl-0.29/riscv64 (0.29.5-2 to 0.29.5-2): Will attempt migration (Any information below is purely informational)
• rust-wayland-protocols-0.29/riscv64 (0.29.5-2 to 0.29.5-2)
  • Migration status for rust-wayland-protocols-0.29/riscv64 (0.29.5-2 to 0.29.5-2): Will attempt migration (Any information below is purely informational)
• rust-x11-dl/riscv64 (2.21.0-1 to 2.21.0-1)
  • Migration status for rust-x11-dl/riscv64 (2.21.0-1 to 2.21.0-1): Will attempt migration (Any information below is purely informational)
• rust-x11/riscv64 (2.19.1-1 to 2.19.1-1)
  • Migration status for rust-x11/riscv64 (2.19.1-1 to 2.19.1-1): Will attempt migration (Any information below is purely informational)
• rust-xkb/riscv64 (0.3.0-2 to 0.3.0-2)
  • Migration status for rust-xkb/riscv64 (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• rust-xkbcommon-sys/riscv64 (1.4.1-2 to 1.4.1-2)
  • Migration status for rust-xkbcommon-sys/riscv64 (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
• rust-xml5ever/riscv64 (0.17.0-1 to 0.17.0-1)
  • Migration status for rust-xml5ever/riscv64 (0.17.0-1 to 0.17.0-1): Will attempt migration (Any information below is purely informational)
• rust-zbar-rust/riscv64 (0.0.21-1 to 0.0.21-1)
  • Migration status for rust-zbar-rust/riscv64 (0.0.21-1 to 0.0.21-1): Will attempt migration (Any information below is purely informational)
• rust-zmq-sys/riscv64 (0.11.0-2 to 0.11.0-2)
  • Migration status for rust-zmq-sys/riscv64 (0.11.0-2 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
• rust-zmq/riscv64 (0.9.2-3 to 0.9.2-3)
  • Migration status for rust-zmq/riscv64 (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
• rxvt-unicode/riscv64 (9.31-3 to 9.31-3)
  • Migration status for rxvt-unicode/riscv64 (9.31-3 to 9.31-3): Will attempt migration (Any information below is purely informational)
• s3d/riscv64 (0.2.2.1-6 to 0.2.2.1-6)
  • Migration status for s3d/riscv64 (0.2.2.1-6 to 0.2.2.1-6): Will attempt migration (Any information below is purely informational)
• s3fs-fuse/riscv64 (1.93-1 to 1.93-1)
  • Migration status for s3fs-fuse/riscv64 (1.93-1 to 1.93-1): Will attempt migration (Any information below is purely informational)
• sachesi/riscv64 (2.0.4+ds-8 to 2.0.4+ds-8)
  • Migration status for sachesi/riscv64 (2.0.4+ds-8 to 2.0.4+ds-8): Will attempt migration (Any information below is purely informational)
• sailcut/riscv64 (1.4.1-2.1 to 1.4.1-2.1)
  • Migration status for sailcut/riscv64 (1.4.1-2.1 to 1.4.1-2.1): Will attempt migration (Any information below is purely informational)
• sane-frontends/riscv64 (1.0.14-18 to 1.0.14-18)
  • Migration status for sane-frontends/riscv64 (1.0.14-18 to 1.0.14-18): Will attempt migration (Any information below is purely informational)
• sasm/riscv64 (3.14.0+ds-1 to 3.14.0+ds-1)
  • Migration status for sasm/riscv64 (3.14.0+ds-1 to 3.14.0+ds-1): Will attempt migration (Any information below is purely informational)
• sbjson/riscv64 (2.3.2-4.1 to 2.3.2-4.1)
  • Migration status for sbjson/riscv64 (2.3.2-4.1 to 2.3.2-4.1): Will attempt migration (Any information below is purely informational)
• scalapack/riscv64 (2.2.1-3.1 to 2.2.1-3.1)
  • Migration status for scalapack/riscv64 (2.2.1-3.1 to 2.2.1-3.1): Will attempt migration (Any information below is purely informational)
• scim-anthy/riscv64 (1.2.7-7 to 1.2.7-7)
  • Migration status for scim-anthy/riscv64 (1.2.7-7 to 1.2.7-7): Will attempt migration (Any information below is purely informational)
• scim-chewing/riscv64 (0.5.1-5 to 0.5.1-5)
  • Migration status for scim-chewing/riscv64 (0.5.1-5 to 0.5.1-5): Will attempt migration (Any information below is purely informational)
• scim-m17n/riscv64 (0.2.3-6 to 0.2.3-6)
  • Migration status for scim-m17n/riscv64 (0.2.3-6 to 0.2.3-6): Will attempt migration (Any information below is purely informational)
• scim-pinyin/riscv64 (0.5.92-5 to 0.5.92-5)
  • Migration status for scim-pinyin/riscv64 (0.5.92-5 to 0.5.92-5): Will attempt migration (Any information below is purely informational)
• scim-skk/riscv64 (0.5.2-7.3 to 0.5.2-7.3)
  • Migration status for scim-skk/riscv64 (0.5.2-7.3 to 0.5.2-7.3): Will attempt migration (Any information below is purely informational)
• scim-tables/riscv64 (0.5.14-2.1 to 0.5.14-2.1)
  • Migration status for scim-tables/riscv64 (0.5.14-2.1 to 0.5.14-2.1): Will attempt migration (Any information below is purely informational)
• scim-thai/riscv64 (0.1.4-5 to 0.1.4-5)
  • Migration status for scim-thai/riscv64 (0.1.4-5 to 0.1.4-5): Will attempt migration (Any information below is purely informational)
• scim-unikey/riscv64 (0.3.1+debian-4 to 0.3.1+debian-4)
  • Migration status for scim-unikey/riscv64 (0.3.1+debian-4 to 0.3.1+debian-4): Will attempt migration (Any information below is purely informational)
• scim/riscv64 (1.4.18+git20211204-0.2 to 1.4.18+git20211204-0.2)
  • Migration status for scim/riscv64 (1.4.18+git20211204-0.2 to 1.4.18+git20211204-0.2): Will attempt migration (Any information below is purely informational)
• sciteproj/riscv64 (1.71-1 to 1.71-1)
  • Migration status for sciteproj/riscv64 (1.71-1 to 1.71-1): Will attempt migration (Any information below is purely informational)
• scorched3d/riscv64 (44+dfsg-8 to 44+dfsg-8)
  • Migration status for scorched3d/riscv64 (44+dfsg-8 to 44+dfsg-8): Will attempt migration (Any information below is purely informational)
• screen-message/riscv64 (0.26-3 to 0.26-3)
  • Migration status for screen-message/riscv64 (0.26-3 to 0.26-3): Will attempt migration (Any information below is purely informational)
• scscp-imcce/riscv64 (1.0.3+ds-7 to 1.0.3+ds-7)
  • Migration status for scscp-imcce/riscv64 (1.0.3+ds-7 to 1.0.3+ds-7): Will attempt migration (Any information below is purely informational)
• scummvm-tools/riscv64 (2.7.0-1 to 2.7.0-1)
  • Migration status for scummvm-tools/riscv64 (2.7.0-1 to 2.7.0-1): Will attempt migration (Any information below is purely informational)
• scummvm/riscv64 (2.8.1+dfsg-1 to 2.8.1+dfsg-1)
  • Migration status for scummvm/riscv64 (2.8.1+dfsg-1 to 2.8.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• sdl-ball/riscv64 (1.04+dfsg-1 to 1.04+dfsg-1)
  • Migration status for sdl-ball/riscv64 (1.04+dfsg-1 to 1.04+dfsg-1): Will attempt migration (Any information below is purely informational)
• sdl-kitchensink/riscv64 (1.0.12-1 to 1.0.12-1)
  • Migration status for sdl-kitchensink/riscv64 (1.0.12-1 to 1.0.12-1): Will attempt migration (Any information below is purely informational)
• sdl-sound1.2/riscv64 (1.0.3-9 to 1.0.3-9)
  • Migration status for sdl-sound1.2/riscv64 (1.0.3-9 to 1.0.3-9): Will attempt migration (Any information below is purely informational)
• sdl-ttf2.0/riscv64 (2.0.11-6 to 2.0.11-6)
  • Migration status for sdl-ttf2.0/riscv64 (2.0.11-6 to 2.0.11-6): Will attempt migration (Any information below is purely informational)
• sdlgfx/riscv64 (2.0.25-12 to 2.0.25-12)
  • Migration status for sdlgfx/riscv64 (2.0.25-12 to 2.0.25-12): Will attempt migration (Any information below is purely informational)
• sdlpango/riscv64 (0.1.2-8 to 0.1.2-8)
  • Migration status for sdlpango/riscv64 (0.1.2-8 to 0.1.2-8): Will attempt migration (Any information below is purely informational)
• searchandrescue/riscv64 (1.5.0+dfsg-0.2 to 1.5.0+dfsg-0.2)
  • Migration status for searchandrescue/riscv64 (1.5.0+dfsg-0.2 to 1.5.0+dfsg-0.2): Will attempt migration (Any information below is purely informational)
• searchmonkey/riscv64 (0.8.3-1.2 to 0.8.3-1.2)
  • Migration status for searchmonkey/riscv64 (0.8.3-1.2 to 0.8.3-1.2): Will attempt migration (Any information below is purely informational)
• sensors-applet/riscv64 (3.0.0+git6-0.6 to 3.0.0+git6-0.6)
  • Migration status for sensors-applet/riscv64 (3.0.0+git6-0.6 to 3.0.0+git6-0.6): Will attempt migration (Any information below is purely informational)
• sentry-python/amd64 (1.40.4-3 to 1.40.4-3)
  • Migration status for sentry-python/amd64 (1.40.4-3 to 1.40.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sentry-python/arm64 (1.40.4-3 to 1.40.4-3)
  • Migration status for sentry-python/arm64 (1.40.4-3 to 1.40.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sentry-python/armel (1.40.4-3 to 1.40.4-3)
  • Migration status for sentry-python/armel (1.40.4-3 to 1.40.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sentry-python/armhf (1.40.4-3 to 1.40.4-3)
  • Migration status for sentry-python/armhf (1.40.4-3 to 1.40.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sentry-python/i386 (1.40.4-3 to 1.40.4-3)
  • Migration status for sentry-python/i386 (1.40.4-3 to 1.40.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sentry-python/mips64el (1.40.4-3 to 1.40.4-3)
  • Migration status for sentry-python/mips64el (1.40.4-3 to 1.40.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sentry-python/ppc64el (1.40.4-3 to 1.40.4-3)
  • Migration status for sentry-python/ppc64el (1.40.4-3 to 1.40.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sentry-python/riscv64 (1.40.4-3 to 1.40.4-3)
  • Migration status for sentry-python/riscv64 (1.40.4-3 to 1.40.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sentry-python/s390x (1.40.4-3 to 1.40.4-3)
  • Migration status for sentry-python/s390x (1.40.4-3 to 1.40.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• seqtools/riscv64 (4.44.1+dfsg-7.1 to 4.44.1+dfsg-7.1)
  • Migration status for seqtools/riscv64 (4.44.1+dfsg-7.1 to 4.44.1+dfsg-7.1): Will attempt migration (Any information below is purely informational)
• ser-player/riscv64 (1.7.3-2 to 1.7.3-2)
  • Migration status for ser-player/riscv64 (1.7.3-2 to 1.7.3-2): Will attempt migration (Any information below is purely informational)
• setools/riscv64 (4.4.4-1 to 4.4.4-1)
  • Migration status for setools/riscv64 (4.4.4-1 to 4.4.4-1): Will attempt migration (Any information below is purely informational)
• sffview/riscv64 (0.5.0-6 to 0.5.0-6)
  • Migration status for sffview/riscv64 (0.5.0-6 to 0.5.0-6): Will attempt migration (Any information below is purely informational)
• sfwbar/riscv64 (1.0~beta13-1 to 1.0~beta13-1)
  • Migration status for sfwbar/riscv64 (1.0~beta13-1 to 1.0~beta13-1): Will attempt migration (Any information below is purely informational)
• sgt-puzzles/riscv64 (20230410.71cf891-2 to 20230410.71cf891-2)
  • Migration status for sgt-puzzles/riscv64 (20230410.71cf891-2 to 20230410.71cf891-2): Will attempt migration (Any information below is purely informational)
• shellex/riscv64 (0.3-1 to 0.3-1)
  • Migration status for shellex/riscv64 (0.3-1 to 0.3-1): Will attempt migration (Any information below is purely informational)
• shelxle/riscv64 (1.0.1552-1 to 1.0.1552-1)
  • Migration status for shelxle/riscv64 (1.0.1552-1 to 1.0.1552-1): Will attempt migration (Any information below is purely informational)
• shibboleth-resolver/riscv64 (3.1.0-3 to 3.1.0-3)
  • Migration status for shibboleth-resolver/riscv64 (3.1.0-3 to 3.1.0-3): Will attempt migration (Any information below is purely informational)
• shibboleth-sp/riscv64 (3.4.1+dfsg-2.1 to 3.4.1+dfsg-2.1)
  • Migration status for shibboleth-sp/riscv64 (3.4.1+dfsg-2.1 to 3.4.1+dfsg-2.1): Will attempt migration (Any information below is purely informational)
• shogivar/riscv64 (1.55b-3 to 1.55b-3)
  • Migration status for shogivar/riscv64 (1.55b-3 to 1.55b-3): Will attempt migration (Any information below is purely informational)
• shutdown-qapps/riscv64 (1.7.4-1 to 1.7.4-1)
  • Migration status for shutdown-qapps/riscv64 (1.7.4-1 to 1.7.4-1): Will attempt migration (Any information below is purely informational)
• signon-kwallet-extension/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for signon-kwallet-extension/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• signon-plugin-oauth2/riscv64 (0.25-2 to 0.25-2)
  • Migration status for signon-plugin-oauth2/riscv64 (0.25-2 to 0.25-2): Will attempt migration (Any information below is purely informational)
• signon-ui/riscv64 (0.17+16.04.20151125-1 to 0.17+16.04.20151125-1)
  • Migration status for signon-ui/riscv64 (0.17+16.04.20151125-1 to 0.17+16.04.20151125-1): Will attempt migration (Any information below is purely informational)
• signond/riscv64 (8.61-1 to 8.61-1)
  • Migration status for signond/riscv64 (8.61-1 to 8.61-1): Will attempt migration (Any information below is purely informational)
• sigviewer/riscv64 (0.6.4-3 to 0.6.4-3)
  • Migration status for sigviewer/riscv64 (0.6.4-3 to 0.6.4-3): Will attempt migration (Any information below is purely informational)
• silverjuke/riscv64 (18.2.1-4.1 to 18.2.1-4.1)
  • Migration status for silverjuke/riscv64 (18.2.1-4.1 to 18.2.1-4.1): Will attempt migration (Any information below is purely informational)
• simavr/riscv64 (1.6+dfsg-3 to 1.6+dfsg-3)
  • Migration status for simavr/riscv64 (1.6+dfsg-3 to 1.6+dfsg-3): Will attempt migration (Any information below is purely informational)
• simgear/riscv64 (1:2020.3.18+dfsg-2.1 to 1:2020.3.18+dfsg-2.1)
  • Migration status for simgear/riscv64 (1:2020.3.18+dfsg-2.1 to 1:2020.3.18+dfsg-2.1): Will attempt migration (Any information below is purely informational)
• simple-image-filter/riscv64 (1.1.2-1 to 1.1.2-1)
  • Migration status for simple-image-filter/riscv64 (1.1.2-1 to 1.1.2-1): Will attempt migration (Any information below is purely informational)
• sioyek/riscv64 (2.0.0+dfsg-4 to 2.0.0+dfsg-4)
  • Migration status for sioyek/riscv64 (2.0.0+dfsg-4 to 2.0.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• skanlite/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for skanlite/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• skanpage/riscv64 (23.08.1-2 to 23.08.1-2)
  • Migration status for skanpage/riscv64 (23.08.1-2 to 23.08.1-2): Will attempt migration (Any information below is purely informational)
• skinedit/riscv64 (1.28~git20220826.cda2db4-1 to 1.28~git20220826.cda2db4-1)
  • Migration status for skinedit/riscv64 (1.28~git20220826.cda2db4-1 to 1.28~git20220826.cda2db4-1): Will attempt migration (Any information below is purely informational)
• skrooge/riscv64 (2.32.0-1 to 2.32.0-1)
  • Migration status for skrooge/riscv64 (2.32.0-1 to 2.32.0-1): Will attempt migration (Any information below is purely informational)
• slimevolley/riscv64 (2.4.2+dfsg-3 to 2.4.2+dfsg-3)
  • Migration status for slimevolley/riscv64 (2.4.2+dfsg-3 to 2.4.2+dfsg-3): Will attempt migration (Any information below is purely informational)
• slop/riscv64 (7.6-4 to 7.6-4)
  • Migration status for slop/riscv64 (7.6-4 to 7.6-4): Will attempt migration (Any information below is purely informational)
• sludge/riscv64 (2.2.2-5 to 2.2.2-5)
  • Migration status for sludge/riscv64 (2.2.2-5 to 2.2.2-5): Will attempt migration (Any information below is purely informational)
• slxfig/riscv64 (0.2.0~.138-1 to 0.2.0~.138-1)
  • Migration status for slxfig/riscv64 (0.2.0~.138-1 to 0.2.0~.138-1): Will attempt migration (Any information below is purely informational)
• smb4k/riscv64 (3.2.5-1 to 3.2.5-1)
  • Migration status for smb4k/riscv64 (3.2.5-1 to 3.2.5-1): Will attempt migration (Any information below is purely informational)
• smpeg/riscv64 (0.4.5+cvs20030824-9.1 to 0.4.5+cvs20030824-9.1)
  • Migration status for smpeg/riscv64 (0.4.5+cvs20030824-9.1 to 0.4.5+cvs20030824-9.1): Will attempt migration (Any information below is purely informational)
• smplayer/riscv64 (23.12.0+ds0-1 to 23.12.0+ds0-1)
  • Migration status for smplayer/riscv64 (23.12.0+ds0-1 to 23.12.0+ds0-1): Will attempt migration (Any information below is purely informational)
• smtube/riscv64 (21.7.0-1 to 21.7.0-1)
  • Migration status for smtube/riscv64 (21.7.0-1 to 21.7.0-1): Will attempt migration (Any information below is purely informational)
• snapd-glib/riscv64 (1.64-1 to 1.64-1)
  • Migration status for snapd-glib/riscv64 (1.64-1 to 1.64-1): Will attempt migration (Any information below is purely informational)
• socnetv/riscv64 (2.8-1 to 2.8-1)
  • Migration status for socnetv/riscv64 (2.8-1 to 2.8-1): Will attempt migration (Any information below is purely informational)
• solfege/riscv64 (3.23.4-12 to 3.23.4-12)
  • Migration status for solfege/riscv64 (3.23.4-12 to 3.23.4-12): Will attempt migration (Any information below is purely informational)
• sollya/riscv64 (8.0+ds-2 to 8.0+ds-2)
  • Migration status for sollya/riscv64 (8.0+ds-2 to 8.0+ds-2): Will attempt migration (Any information below is purely informational)
• solvespace/riscv64 (3.1+ds1-3.1 to 3.1+ds1-3.1)
  • Migration status for solvespace/riscv64 (3.1+ds1-3.1 to 3.1+ds1-3.1): Will attempt migration (Any information below is purely informational)
• sonnet/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for sonnet/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• soqt/riscv64 (1.6.0+ds1-3.1 to 1.6.0+ds1-3.1)
  • Migration status for soqt/riscv64 (1.6.0+ds1-3.1 to 1.6.0+ds1-3.1): Will attempt migration (Any information below is purely informational)
• sound-juicer/riscv64 (3.40.0-1 to 3.40.0-1)
  • Migration status for sound-juicer/riscv64 (3.40.0-1 to 3.40.0-1): Will attempt migration (Any information below is purely informational)
• soundmodem/riscv64 (0.20-7 to 0.20-7)
  • Migration status for soundmodem/riscv64 (0.20-7 to 0.20-7): Will attempt migration (Any information below is purely informational)
• spacebar/riscv64 (23.01.0-1 to 23.01.0-1)
  • Migration status for spacebar/riscv64 (23.01.0-1 to 23.01.0-1): Will attempt migration (Any information below is purely informational)
• sparse/riscv64 (0.6.4-4 to 0.6.4-4)
  • Migration status for sparse/riscv64 (0.6.4-4 to 0.6.4-4): Will attempt migration (Any information below is purely informational)
• spatialite-gui/riscv64 (2.1.0~beta1-2 to 2.1.0~beta1-2)
  • Migration status for spatialite-gui/riscv64 (2.1.0~beta1-2 to 2.1.0~beta1-2): Will attempt migration (Any information below is purely informational)
• spatialite-tools/riscv64 (5.1.0a-1 to 5.1.0a-1)
  • Migration status for spatialite-tools/riscv64 (5.1.0a-1 to 5.1.0a-1): Will attempt migration (Any information below is purely informational)
• spatialite/riscv64 (5.1.0-3 to 5.1.0-3)
  • Migration status for spatialite/riscv64 (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
• spice-gtk/riscv64 (0.42-2.1 to 0.42-2.1)
  • Migration status for spice-gtk/riscv64 (0.42-2.1 to 0.42-2.1): Will attempt migration (Any information below is purely informational)
• spotlighter/riscv64 (0.3-1.2 to 0.3-1.2)
  • Migration status for spotlighter/riscv64 (0.3-1.2 to 0.3-1.2): Will attempt migration (Any information below is purely informational)
• spread-sheet-widget/riscv64 (0.10-4.1 to 0.10-4.1)
  • Migration status for spread-sheet-widget/riscv64 (0.10-4.1 to 0.10-4.1): Will attempt migration (Any information below is purely informational)
• sqliteodbc/riscv64 (0.99991-1 to 0.99991-1)
  • Migration status for sqliteodbc/riscv64 (0.99991-1 to 0.99991-1): Will attempt migration (Any information below is purely informational)
• ssh-agent-filter/riscv64 (0.5.2-1 to 0.5.2-1)
  • Migration status for ssh-agent-filter/riscv64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• ssh-askpass-fullscreen/riscv64 (1.3-1 to 1.3-1)
  • Migration status for ssh-askpass-fullscreen/riscv64 (1.3-1 to 1.3-1): Will attempt migration (Any information below is purely informational)
• ssh-contact/riscv64 (0.7-1.1 to 0.7-1.1)
  • Migration status for ssh-contact/riscv64 (0.7-1.1 to 0.7-1.1): Will attempt migration (Any information below is purely informational)
• ssh-cron/riscv64 (1.04.01-1 to 1.04.01-1)
  • Migration status for ssh-cron/riscv64 (1.04.01-1 to 1.04.01-1): Will attempt migration (Any information below is purely informational)
• sshfs-fuse/riscv64 (3.7.3-1.1 to 3.7.3-1.1)
  • Migration status for sshfs-fuse/riscv64 (3.7.3-1.1 to 3.7.3-1.1): Will attempt migration (Any information below is purely informational)
• stellarium/amd64 (24.2-1 to 24.2-1)
  • Migration status for stellarium/amd64 (24.2-1 to 24.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: stellarium/amd64 exiv2
• stellarium/arm64 (24.2-1 to 24.2-1)
  • Migration status for stellarium/arm64 (24.2-1 to 24.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: stellarium/arm64 exiv2
• stellarium/armel (24.2-1 to 24.2-1)
  • Migration status for stellarium/armel (24.2-1 to 24.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: stellarium/armel exiv2
• stellarium/armhf (24.2-1 to 24.2-1)
  • Migration status for stellarium/armhf (24.2-1 to 24.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: stellarium/armhf exiv2
• stellarium/i386 (24.2-1 to 24.2-1)
  • Migration status for stellarium/i386 (24.2-1 to 24.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: stellarium/i386 exiv2
• stellarium/mips64el (24.2-1 to 24.2-1)
  • Migration status for stellarium/mips64el (24.2-1 to 24.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: stellarium/mips64el exiv2
• stellarium/ppc64el (24.2-1 to 24.2-1)
  • Migration status for stellarium/ppc64el (24.2-1 to 24.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: stellarium/ppc64el exiv2
• stellarium/s390x (24.2-1 to 24.2-1)
  • Migration status for stellarium/s390x (24.2-1 to 24.2-1): Will attempt migration (Any information below is purely informational)
    • Depends: stellarium/s390x exiv2
• step/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for step/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• stoken/riscv64 (0.92-1.1 to 0.92-1.1)
  • Migration status for stoken/riscv64 (0.92-1.1 to 0.92-1.1): Will attempt migration (Any information below is purely informational)
• stormbaancoureur/riscv64 (2.1.6-3.1 to 2.1.6-3.1)
  • Migration status for stormbaancoureur/riscv64 (2.1.6-3.1 to 2.1.6-3.1): Will attempt migration (Any information below is purely informational)
• stretchplayer/riscv64 (0.503-4 to 0.503-4)
  • Migration status for stretchplayer/riscv64 (0.503-4 to 0.503-4): Will attempt migration (Any information below is purely informational)
• structure-synth/riscv64 (1.5.0-7 to 1.5.0-7)
  • Migration status for structure-synth/riscv64 (1.5.0-7 to 1.5.0-7): Will attempt migration (Any information below is purely informational)
• subtitleeditor/riscv64 (0.54.0-6 to 0.54.0-6)
  • Migration status for subtitleeditor/riscv64 (0.54.0-6 to 0.54.0-6): Will attempt migration (Any information below is purely informational)
• sudoku-solver/riscv64 (1.0.1-4 to 1.0.1-4)
  • Migration status for sudoku-solver/riscv64 (1.0.1-4 to 1.0.1-4): Will attempt migration (Any information below is purely informational)
• sugar-datastore/riscv64 (0.121-2 to 0.121-2)
  • Migration status for sugar-datastore/riscv64 (0.121-2 to 0.121-2): Will attempt migration (Any information below is purely informational)
• sugar-toolkit-gtk3/riscv64 (0.121-1 to 0.121-1)
  • Migration status for sugar-toolkit-gtk3/riscv64 (0.121-1 to 0.121-1): Will attempt migration (Any information below is purely informational)
• sumo/riscv64 (1.18.0+dfsg-3 to 1.18.0+dfsg-3)
  • Migration status for sumo/riscv64 (1.18.0+dfsg-3 to 1.18.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• sundials/riscv64 (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3)
  • Migration status for sundials/riscv64 (6.4.1+dfsg1-3 to 6.4.1+dfsg1-3): Will attempt migration (Any information below is purely informational)
• superkb/riscv64 (0.23-5 to 0.23-5)
  • Migration status for superkb/riscv64 (0.23-5 to 0.23-5): Will attempt migration (Any information below is purely informational)
• supertransball2/riscv64 (1.5-11 to 1.5-11)
  • Migration status for supertransball2/riscv64 (1.5-11 to 1.5-11): Will attempt migration (Any information below is purely informational)
• supertux/riscv64 (0.6.3-2 to 0.6.3-2)
  • Migration status for supertux/riscv64 (0.6.3-2 to 0.6.3-2): Will attempt migration (Any information below is purely informational)
• surf/riscv64 (2.1+git20221016-6 to 2.1+git20221016-6)
  • Migration status for surf/riscv64 (2.1+git20221016-6 to 2.1+git20221016-6): Will attempt migration (Any information below is purely informational)
• svgpart/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for svgpart/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• svn-all-fast-export/riscv64 (1.0.18+git20221225-1 to 1.0.18+git20221225-1)
  • Migration status for svn-all-fast-export/riscv64 (1.0.18+git20221225-1 to 1.0.18+git20221225-1): Will attempt migration (Any information below is purely informational)
• swami/riscv64 (2.2.2-2.1 to 2.2.2-2.1)
  • Migration status for swami/riscv64 (2.2.2-2.1 to 2.2.2-2.1): Will attempt migration (Any information below is purely informational)
• swappy/riscv64 (1.5.1-1 to 1.5.1-1)
  • Migration status for swappy/riscv64 (1.5.1-1 to 1.5.1-1): Will attempt migration (Any information below is purely informational)
• swaybg/riscv64 (1.2.1-1 to 1.2.1-1)
  • Migration status for swaybg/riscv64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• sweeper/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for sweeper/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• swell-foop/riscv64 (1:46.0-1 to 1:46.0-1)
  • Migration status for swell-foop/riscv64 (1:46.0-1 to 1:46.0-1): Will attempt migration (Any information below is purely informational)
• swi-prolog/riscv64 (9.0.4+dfsg-4 to 9.0.4+dfsg-4)
  • Migration status for swi-prolog/riscv64 (9.0.4+dfsg-4 to 9.0.4+dfsg-4): Will attempt migration (Any information below is purely informational)
• swish-e/riscv64 (2.4.7-6.2 to 2.4.7-6.2)
  • Migration status for swish-e/riscv64 (2.4.7-6.2 to 2.4.7-6.2): Will attempt migration (Any information below is purely informational)
• sxiv/riscv64 (26-1 to 26-1)
  • Migration status for sxiv/riscv64 (26-1 to 26-1): Will attempt migration (Any information below is purely informational)
• sxmo-utils/riscv64 (1.12.0-7 to 1.12.0-7)
  • Migration status for sxmo-utils/riscv64 (1.12.0-7 to 1.12.0-7): Will attempt migration (Any information below is purely informational)
• sylph-searcher/riscv64 (1.2.0-15 to 1.2.0-15)
  • Migration status for sylph-searcher/riscv64 (1.2.0-15 to 1.2.0-15): Will attempt migration (Any information below is purely informational)
• synapse/riscv64 (0.2.99.4-4 to 0.2.99.4-4)
  • Migration status for synapse/riscv64 (0.2.99.4-4 to 0.2.99.4-4): Will attempt migration (Any information below is purely informational)
• synaptic/riscv64 (0.91.3 to 0.91.3)
  • Migration status for synaptic/riscv64 (0.91.3 to 0.91.3): Will attempt migration (Any information below is purely informational)
• tablelog/riscv64 (0.6.4-2 to 0.6.4-2)
  • Migration status for tablelog/riscv64 (0.6.4-2 to 0.6.4-2): Will attempt migration (Any information below is purely informational)
• tachyon/riscv64 (0.99~b6+dsx-12 to 0.99~b6+dsx-12)
  • Migration status for tachyon/riscv64 (0.99~b6+dsx-12 to 0.99~b6+dsx-12): Will attempt migration (Any information below is purely informational)
• tagua/riscv64 (1.0~alpha2-16-g618c6a0-3 to 1.0~alpha2-16-g618c6a0-3)
  • Migration status for tagua/riscv64 (1.0~alpha2-16-g618c6a0-3 to 1.0~alpha2-16-g618c6a0-3): Will attempt migration (Any information below is purely informational)
• taktuk/riscv64 (3.7.7-3.1 to 3.7.7-3.1)
  • Migration status for taktuk/riscv64 (3.7.7-3.1 to 3.7.7-3.1): Will attempt migration (Any information below is purely informational)
• tali/riscv64 (1:40.9-1 to 1:40.9-1)
  • Migration status for tali/riscv64 (1:40.9-1 to 1:40.9-1): Will attempt migration (Any information below is purely informational)
• talksoup.app/riscv64 (1.1-1 to 1.1-1)
  • Migration status for talksoup.app/riscv64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
• tanglet/riscv64 (1.6.5-2 to 1.6.5-2)
  • Migration status for tanglet/riscv64 (1.6.5-2 to 1.6.5-2): Will attempt migration (Any information below is purely informational)
• tango/riscv64 (9.5.0+dfsg1-1.1 to 9.5.0+dfsg1-1.1)
  • Migration status for tango/riscv64 (9.5.0+dfsg1-1.1 to 9.5.0+dfsg1-1.1): Will attempt migration (Any information below is purely informational)
• taopm/riscv64 (1.0-7 to 1.0-7)
  • Migration status for taopm/riscv64 (1.0-7 to 1.0-7): Will attempt migration (Any information below is purely informational)
• tatan/riscv64 (1.0.dfsg2-1 to 1.0.dfsg2-1)
  • Migration status for tatan/riscv64 (1.0.dfsg2-1 to 1.0.dfsg2-1): Will attempt migration (Any information below is purely informational)
• tdfsb/riscv64 (0.0.10-4 to 0.0.10-4)
  • Migration status for tdfsb/riscv64 (0.0.10-4 to 0.0.10-4): Will attempt migration (Any information below is purely informational)
• tdigest/riscv64 (1.4.1-1 to 1.4.1-1)
  • Migration status for tdigest/riscv64 (1.4.1-1 to 1.4.1-1): Will attempt migration (Any information below is purely informational)
• tds-fdw/riscv64 (2.0.3-3 to 2.0.3-3)
  • Migration status for tds-fdw/riscv64 (2.0.3-3 to 2.0.3-3): Will attempt migration (Any information below is purely informational)
• teeworlds/riscv64 (0.7.5-2 to 0.7.5-2)
  • Migration status for teeworlds/riscv64 (0.7.5-2 to 0.7.5-2): Will attempt migration (Any information below is purely informational)
• telegnome/riscv64 (0.3.6-5 to 0.3.6-5)
  • Migration status for telegnome/riscv64 (0.3.6-5 to 0.3.6-5): Will attempt migration (Any information below is purely informational)
• telepathy-accounts-signon/riscv64 (2.1-1 to 2.1-1)
  • Migration status for telepathy-accounts-signon/riscv64 (2.1-1 to 2.1-1): Will attempt migration (Any information below is purely informational)
• telepathy-farstream/riscv64 (0.6.2-1.2 to 0.6.2-1.2)
  • Migration status for telepathy-farstream/riscv64 (0.6.2-1.2 to 0.6.2-1.2): Will attempt migration (Any information below is purely informational)
• telepathy-qt/riscv64 (0.9.8+ds-4 to 0.9.8+ds-4)
  • Migration status for telepathy-qt/riscv64 (0.9.8+ds-4 to 0.9.8+ds-4): Will attempt migration (Any information below is purely informational)
• tenace/riscv64 (0.17-1 to 0.17-1)
  • Migration status for tenace/riscv64 (0.17-1 to 0.17-1): Will attempt migration (Any information below is purely informational)
• tepl/riscv64 (6.8.0-2 to 6.8.0-2)
  • Migration status for tepl/riscv64 (6.8.0-2 to 6.8.0-2): Will attempt migration (Any information below is purely informational)
• terminatorx/riscv64 (4.2.0-3 to 4.2.0-3)
  • Migration status for terminatorx/riscv64 (4.2.0-3 to 4.2.0-3): Will attempt migration (Any information below is purely informational)
• terminology/riscv64 (1.13.0-2 to 1.13.0-2)
  • Migration status for terminology/riscv64 (1.13.0-2 to 1.13.0-2): Will attempt migration (Any information below is purely informational)
• termit/riscv64 (3.1-3 to 3.1-3)
  • Migration status for termit/riscv64 (3.1-3 to 3.1-3): Will attempt migration (Any information below is purely informational)
• tesseract/riscv64 (5.3.4-1.1 to 5.3.4-1.1)
  • Migration status for tesseract/riscv64 (5.3.4-1.1 to 5.3.4-1.1): Will attempt migration (Any information below is purely informational)
• therion/riscv64 (6.2.1-1 to 6.2.1-1)
  • Migration status for therion/riscv64 (6.2.1-1 to 6.2.1-1): Will attempt migration (Any information below is purely informational)
• threadweaver/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for threadweaver/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• threeb/riscv64 (0.0~git20220106110332.a3144e0-6 to 0.0~git20220106110332.a3144e0-6)
  • Migration status for threeb/riscv64 (0.0~git20220106110332.a3144e0-6 to 0.0~git20220106110332.a3144e0-6): Will attempt migration (Any information below is purely informational)
• thrift/riscv64 (0.19.0-2.1 to 0.19.0-2.1)
  • Migration status for thrift/riscv64 (0.19.0-2.1 to 0.19.0-2.1): Will attempt migration (Any information below is purely informational)
• thunar-archive-plugin/riscv64 (0.5.2-1 to 0.5.2-1)
  • Migration status for thunar-archive-plugin/riscv64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• thunar-dropbox-plugin/riscv64 (0.3.1-2 to 0.3.1-2)
  • Migration status for thunar-dropbox-plugin/riscv64 (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
• thunar-media-tags-plugin/riscv64 (0.4.0-1 to 0.4.0-1)
  • Migration status for thunar-media-tags-plugin/riscv64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• thunar-vcs-plugin/riscv64 (0.2.0-2 to 0.2.0-2)
  • Migration status for thunar-vcs-plugin/riscv64 (0.2.0-2 to 0.2.0-2): Will attempt migration (Any information below is purely informational)
• thunar-volman/riscv64 (4.18.0-1 to 4.18.0-1)
  • Migration status for thunar-volman/riscv64 (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• thunarx-python/riscv64 (0.5.2-2 to 0.5.2-2)
  • Migration status for thunarx-python/riscv64 (0.5.2-2 to 0.5.2-2): Will attempt migration (Any information below is purely informational)
• thunderbird_pu (1:128.1.1esr-1 to 1:115.15.0-1~deb12u1)
  • Migration status for thunderbird_pu (1:128.1.1esr-1 to 1:115.15.0-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: thunderbird is newer in the target suite (1:128.1.1esr-1 1:115.15.0-1~deb12u1)
• tickr/riscv64 (0.7.1-1 to 0.7.1-1)
  • Migration status for tickr/riscv64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• tikzit/riscv64 (2.1.6-4 to 2.1.6-4)
  • Migration status for tikzit/riscv64 (2.1.6-4 to 2.1.6-4): Will attempt migration (Any information below is purely informational)
• tilda/riscv64 (2.0.0-1 to 2.0.0-1)
  • Migration status for tilda/riscv64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• tiled-qt/riscv64 (1.8.2-1 to 1.8.2-1)
  • Migration status for tiled-qt/riscv64 (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
• tilp2/riscv64 (1.19~git20231112.5a2ea63-1 to 1.19~git20231112.5a2ea63-1)
  • Migration status for tilp2/riscv64 (1.19~git20231112.5a2ea63-1 to 1.19~git20231112.5a2ea63-1): Will attempt migration (Any information below is purely informational)
• timemachine/riscv64 (0.3.3-3 to 0.3.3-3)
  • Migration status for timemachine/riscv64 (0.3.3-3 to 0.3.3-3): Will attempt migration (Any information below is purely informational)
• timg/riscv64 (1.6.0-1 to 1.6.0-1)
  • Migration status for timg/riscv64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
• timidity/riscv64 (2.14.0-8.2 to 2.14.0-8.2)
  • Migration status for timidity/riscv64 (2.14.0-8.2 to 2.14.0-8.2): Will attempt migration (Any information below is purely informational)
• tint2/riscv64 (17.0.1-1.1 to 17.0.1-1.1)
  • Migration status for tint2/riscv64 (17.0.1-1.1 to 17.0.1-1.1): Will attempt migration (Any information below is purely informational)
• tintii/riscv64 (2.10.0-3 to 2.10.0-3)
  • Migration status for tintii/riscv64 (2.10.0-3 to 2.10.0-3): Will attempt migration (Any information below is purely informational)
• tiptop/riscv64 (2.3.1-5 to 2.3.1-5)
  • Migration status for tiptop/riscv64 (2.3.1-5 to 2.3.1-5): Will attempt migration (Any information below is purely informational)
• titanion/riscv64 (0.3.dfsg1-8 to 0.3.dfsg1-8)
  • Migration status for titanion/riscv64 (0.3.dfsg1-8 to 0.3.dfsg1-8): Will attempt migration (Any information below is purely informational)
• tmispell-voikko/riscv64 (0.7.1-5 to 0.7.1-5)
  • Migration status for tmispell-voikko/riscv64 (0.7.1-5 to 0.7.1-5): Will attempt migration (Any information below is purely informational)
• tnseq-transit/riscv64 (3.3.4-1 to 3.3.4-1)
  • Migration status for tnseq-transit/riscv64 (3.3.4-1 to 3.3.4-1): Will attempt migration (Any information below is purely informational)
• toastinfo/riscv64 (1.5-1 to 1.5-1)
  • Migration status for toastinfo/riscv64 (1.5-1 to 1.5-1): Will attempt migration (Any information below is purely informational)
• tomatoes/riscv64 (1.55-10 to 1.55-10)
  • Migration status for tomatoes/riscv64 (1.55-10 to 1.55-10): Will attempt migration (Any information below is purely informational)
• tone-generator/riscv64 (1.6.1-4 to 1.6.1-4)
  • Migration status for tone-generator/riscv64 (1.6.1-4 to 1.6.1-4): Will attempt migration (Any information below is purely informational)
• toppic/riscv64 (1.5.3+dfsg1-1 to 1.5.3+dfsg1-1)
  • Migration status for toppic/riscv64 (1.5.3+dfsg1-1 to 1.5.3+dfsg1-1): Will attempt migration (Any information below is purely informational)
• torcs/riscv64 (1.3.7+dfsg-5 to 1.3.7+dfsg-5)
  • Migration status for torcs/riscv64 (1.3.7+dfsg-5 to 1.3.7+dfsg-5): Will attempt migration (Any information below is purely informational)
• torus-trooper/riscv64 (0.22.dfsg1-13 to 0.22.dfsg1-13)
  • Migration status for torus-trooper/riscv64 (0.22.dfsg1-13 to 0.22.dfsg1-13): Will attempt migration (Any information below is purely informational)
• totem-pl-parser/riscv64 (3.26.6-1 to 3.26.6-1)
  • Migration status for totem-pl-parser/riscv64 (3.26.6-1 to 3.26.6-1): Will attempt migration (Any information below is purely informational)
• totem/riscv64 (43.0-3 to 43.0-3)
  • Migration status for totem/riscv64 (43.0-3 to 43.0-3): Will attempt migration (Any information below is purely informational)
• tpm2-initramfs-tool/riscv64 (0.2.2-2.1 to 0.2.2-2.1)
  • Migration status for tpm2-initramfs-tool/riscv64 (0.2.2-2.1 to 0.2.2-2.1): Will attempt migration (Any information below is purely informational)
• tpm2-openssl/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for tpm2-openssl/riscv64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• trabucco/riscv64 (1.5-1 to 1.5-1)
  • Migration status for trabucco/riscv64 (1.5-1 to 1.5-1): Will attempt migration (Any information below is purely informational)
• traceshark/riscv64 (0.9.14~beta-1 to 0.9.14~beta-1)
  • Migration status for traceshark/riscv64 (0.9.14~beta-1 to 0.9.14~beta-1): Will attempt migration (Any information below is purely informational)
• trackballs/riscv64 (1.3.4-1 to 1.3.4-1)
  • Migration status for trackballs/riscv64 (1.3.4-1 to 1.3.4-1): Will attempt migration (Any information below is purely informational)
• trafficserver_pu (- to 9.2.5+ds-0+deb12u1)
  • Migration status for trafficserver_pu (- to 9.2.5+ds-0+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • trafficserver/amd64 has unsatisfiable dependency
    • trafficserver-experimental-plugins/amd64 has unsatisfiable dependency
    • trafficserver/arm64 has unsatisfiable dependency
    • trafficserver-experimental-plugins/arm64 has unsatisfiable dependency
    • trafficserver unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • trafficserver unsatisfiable Build-Depends(-Arch) on amd64: libluajit2-5.1-dev [!x32] | lua [x32]
    • trafficserver unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • trafficserver unsatisfiable Build-Depends(-Arch) on arm64: libluajit2-5.1-dev [!x32] | lua [x32]
    • NEEDS APPROVAL BY RM
• transcend/riscv64 (0.3.dfsg2-4 to 0.3.dfsg2-4)
  • Migration status for transcend/riscv64 (0.3.dfsg2-4 to 0.3.dfsg2-4): Will attempt migration (Any information below is purely informational)
• transfuse/riscv64 (0.5.8-1 to 0.5.8-1)
  • Migration status for transfuse/riscv64 (0.5.8-1 to 0.5.8-1): Will attempt migration (Any information below is purely informational)
• transmission-remote-gtk/riscv64 (1.5.1-1 to 1.5.1-1)
  • Migration status for transmission-remote-gtk/riscv64 (1.5.1-1 to 1.5.1-1): Will attempt migration (Any information below is purely informational)
• traverso/riscv64 (0.49.6-1 to 0.49.6-1)
  • Migration status for traverso/riscv64 (0.49.6-1 to 0.49.6-1): Will attempt migration (Any information below is purely informational)
• trayer/riscv64 (1.1.8-4 to 1.1.8-4)
  • Migration status for trayer/riscv64 (1.1.8-4 to 1.1.8-4): Will attempt migration (Any information below is purely informational)
• treesheets/riscv64 (1:1.0.2-1.1 to 1:1.0.2-1.1)
  • Migration status for treesheets/riscv64 (1:1.0.2-1.1 to 1:1.0.2-1.1): Will attempt migration (Any information below is purely informational)
• treeviewx/riscv64 (0.5.1+git20100823.7e4d0e9-4 to 0.5.1+git20100823.7e4d0e9-4)
  • Migration status for treeviewx/riscv64 (0.5.1+git20100823.7e4d0e9-4 to 0.5.1+git20100823.7e4d0e9-4): Will attempt migration (Any information below is purely informational)
• tremotesf/riscv64 (2.6.2-1 to 2.6.2-1)
  • Migration status for tremotesf/riscv64 (2.6.2-1 to 2.6.2-1): Will attempt migration (Any information below is purely informational)
• trend/riscv64 (1.4-3 to 1.4-3)
  • Migration status for trend/riscv64 (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
• trigger-rally/riscv64 (0.6.6.1-3 to 0.6.6.1-3)
  • Migration status for trigger-rally/riscv64 (0.6.6.1-3 to 0.6.6.1-3): Will attempt migration (Any information below is purely informational)
• tsung/riscv64 (1.7.0-3.1 to 1.7.0-3.1)
  • Migration status for tsung/riscv64 (1.7.0-3.1 to 1.7.0-3.1): Will attempt migration (Any information below is purely informational)
• tth/riscv64 (4.16+ds-1 to 4.16+ds-1)
  • Migration status for tth/riscv64 (4.16+ds-1 to 4.16+ds-1): Will attempt migration (Any information below is purely informational)
• ttygif/riscv64 (1.5.0-1 to 1.5.0-1)
  • Migration status for ttygif/riscv64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
• tuiwidgets/riscv64 (0.2.1-1 to 0.2.1-1)
  • Migration status for tuiwidgets/riscv64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• tumbler/riscv64 (4.18.1-1.1 to 4.18.1-1.1)
  • Migration status for tumbler/riscv64 (4.18.1-1.1 to 4.18.1-1.1): Will attempt migration (Any information below is purely informational)
• tumiki-fighters/riscv64 (0.2.dfsg1-10 to 0.2.dfsg1-10)
  • Migration status for tumiki-fighters/riscv64 (0.2.dfsg1-10 to 0.2.dfsg1-10): Will attempt migration (Any information below is purely informational)
• tupi/riscv64 (0.2+git08-5 to 0.2+git08-5)
  • Migration status for tupi/riscv64 (0.2+git08-5 to 0.2+git08-5): Will attempt migration (Any information below is purely informational)
• tvtime/riscv64 (1.0.11-8 to 1.0.11-8)
  • Migration status for tvtime/riscv64 (1.0.11-8 to 1.0.11-8): Will attempt migration (Any information below is purely informational)
• tycho2/riscv64 (2-4 to 2-4)
  • Migration status for tycho2/riscv64 (2-4 to 2-4): Will attempt migration (Any information below is purely informational)
• tyxml/amd64 (4.6.0-1 to 4.6.0-1)
  • Migration status for tyxml/amd64 (4.6.0-1 to 4.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libtyxml-ocaml/4.6.0-1+b2/amd64 to testing makes nurpawiki/1.2.4-4+b14/amd64 uninstallable
    • migrating libtyxml-ocaml-dev/4.6.0-1+b2/amd64 to testing makes libeliom-ocaml-dev/10.4.1-1+b5/amd64 uninstallable
    • Depends: tyxml/amd64 ocaml-re (not considered)
    • Implicit dependency: tyxml/amd64 ben/amd64
    • Implicit dependency: tyxml/amd64 js-of-ocaml/amd64 (not considered)
    • Implicit dependency: tyxml/amd64 ocaml-odoc/amd64
• tyxml/arm64 (4.6.0-1 to 4.6.0-1)
  • Migration status for tyxml/arm64 (4.6.0-1 to 4.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libtyxml-ocaml/4.6.0-1+b2/arm64 to testing makes nurpawiki/1.2.4-4+b14/arm64 uninstallable
    • migrating libtyxml-ocaml-dev/4.6.0-1+b2/arm64 to testing makes libeliom-ocaml-dev/10.4.1-1+b5/arm64 uninstallable
    • Depends: tyxml/arm64 ocaml-re (not considered)
    • Implicit dependency: tyxml/arm64 ben/arm64
    • Implicit dependency: tyxml/arm64 js-of-ocaml/arm64 (not considered)
    • Implicit dependency: tyxml/arm64 ocaml-odoc/arm64
• tyxml/armel (4.6.0-1 to 4.6.0-1)
  • Migration status for tyxml/armel (4.6.0-1 to 4.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tyxml/armel ocaml-re (not considered)
    • Invalidated by dependency
• tyxml/armhf (4.6.0-1 to 4.6.0-1)
  • Migration status for tyxml/armhf (4.6.0-1 to 4.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tyxml/armhf ocaml-re (not considered)
    • Invalidated by dependency
• tyxml/i386 (4.6.0-1 to 4.6.0-1)
  • Migration status for tyxml/i386 (4.6.0-1 to 4.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tyxml/i386 ocaml-re (not considered)
    • Invalidated by dependency
• tyxml/mips64el (4.6.0-1 to 4.6.0-1)
  • Migration status for tyxml/mips64el (4.6.0-1 to 4.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tyxml/mips64el ocaml-re (not considered)
    • Invalidated by dependency
• tyxml/ppc64el (4.6.0-1 to 4.6.0-1)
  • Migration status for tyxml/ppc64el (4.6.0-1 to 4.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libtyxml-ocaml/4.6.0-1+b2/ppc64el to testing makes nurpawiki/1.2.4-4+b14/ppc64el uninstallable
    • migrating libtyxml-ocaml-dev/4.6.0-1+b2/ppc64el to testing makes libeliom-ocaml-dev/10.4.1-1+b5/ppc64el uninstallable
    • Depends: tyxml/ppc64el ocaml-re (not considered)
    • Implicit dependency: tyxml/ppc64el ben/ppc64el
    • Implicit dependency: tyxml/ppc64el js-of-ocaml/ppc64el (not considered)
    • Implicit dependency: tyxml/ppc64el ocaml-odoc/ppc64el
• tyxml/riscv64 (4.6.0-1 to 4.6.0-1)
  • Migration status for tyxml/riscv64 (4.6.0-1 to 4.6.0-1): Will attempt migration (Any information below is purely informational)
• tyxml/s390x (4.6.0-1 to 4.6.0-1)
  • Migration status for tyxml/s390x (4.6.0-1 to 4.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libtyxml-ocaml/4.6.0-1+b2/s390x to testing makes nurpawiki/1.2.4-4+b14/s390x uninstallable
    • migrating libtyxml-ocaml-dev/4.6.0-1+b2/s390x to testing makes libeliom-ocaml-dev/10.4.1-1+b5/s390x uninstallable
    • Depends: tyxml/s390x ocaml-re (not considered)
    • Implicit dependency: tyxml/s390x ben/s390x
    • Implicit dependency: tyxml/s390x js-of-ocaml/s390x (not considered)
    • Implicit dependency: tyxml/s390x ocaml-odoc/s390x
• tzc/riscv64 (2.6.15-5.4 to 2.6.15-5.4)
  • Migration status for tzc/riscv64 (2.6.15-5.4 to 2.6.15-5.4): Will attempt migration (Any information below is purely informational)
• udisks2-qt5/riscv64 (5.0.6-1 to 5.0.6-1)
  • Migration status for udisks2-qt5/riscv64 (5.0.6-1 to 5.0.6-1): Will attempt migration (Any information below is purely informational)
• uefitool/riscv64 (0.28.0+A66-1 to 0.28.0+A66-1)
  • Migration status for uefitool/riscv64 (0.28.0+A66-1 to 0.28.0+A66-1): Will attempt migration (Any information below is purely informational)
• ufo-core/riscv64 (0.16.0.52.gbd831ab-1 to 0.16.0.52.gbd831ab-1)
  • Migration status for ufo-core/riscv64 (0.16.0.52.gbd831ab-1 to 0.16.0.52.gbd831ab-1): Will attempt migration (Any information below is purely informational)
• ufo-filters/riscv64 (0.16.0.159.g483ce16-1 to 0.16.0.159.g483ce16-1)
  • Migration status for ufo-filters/riscv64 (0.16.0.159.g483ce16-1 to 0.16.0.159.g483ce16-1): Will attempt migration (Any information below is purely informational)
• ufoai/riscv64 (2.5-7 to 2.5-7)
  • Migration status for ufoai/riscv64 (2.5-7 to 2.5-7): Will attempt migration (Any information below is purely informational)
• uget/riscv64 (2.2.3-2 to 2.2.3-2)
  • Migration status for uget/riscv64 (2.2.3-2 to 2.2.3-2): Will attempt migration (Any information below is purely informational)
• uim-chewing/riscv64 (0.1.0-7 to 0.1.0-7)
  • Migration status for uim-chewing/riscv64 (0.1.0-7 to 0.1.0-7): Will attempt migration (Any information below is purely informational)
• ukopp/riscv64 (4.9-3 to 4.9-3)
  • Migration status for ukopp/riscv64 (4.9-3 to 4.9-3): Will attempt migration (Any information below is purely informational)
• ukui-app-widget/riscv64 (4.0.0.1-1 to 4.0.0.1-1)
  • Migration status for ukui-app-widget/riscv64 (4.0.0.1-1 to 4.0.0.1-1): Will attempt migration (Any information below is purely informational)
• ukui-bluetooth/riscv64 (1.0.2.1-1 to 1.0.2.1-1)
  • Migration status for ukui-bluetooth/riscv64 (1.0.2.1-1 to 1.0.2.1-1): Will attempt migration (Any information below is purely informational)
• ukui-control-center/riscv64 (3.22.1.28-1 to 3.22.1.28-1)
  • Migration status for ukui-control-center/riscv64 (3.22.1.28-1 to 3.22.1.28-1): Will attempt migration (Any information below is purely informational)
• ukui-greeter/riscv64 (3.0.3.1-1 to 3.0.3.1-1)
  • Migration status for ukui-greeter/riscv64 (3.0.3.1-1 to 3.0.3.1-1): Will attempt migration (Any information below is purely informational)
• ukui-interface/riscv64 (1.0.1-2 to 1.0.1-2)
  • Migration status for ukui-interface/riscv64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• ukui-menu/riscv64 (3.0.3-1 to 3.0.3-1)
  • Migration status for ukui-menu/riscv64 (3.0.3-1 to 3.0.3-1): Will attempt migration (Any information below is purely informational)
• ukui-notebook/riscv64 (3.1.1-1 to 3.1.1-1)
  • Migration status for ukui-notebook/riscv64 (3.1.1-1 to 3.1.1-1): Will attempt migration (Any information below is purely informational)
• ukui-notification-daemon/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for ukui-notification-daemon/riscv64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ukui-panel/riscv64 (4.0.0.4-1 to 4.0.0.4-1)
  • Migration status for ukui-panel/riscv64 (4.0.0.4-1 to 4.0.0.4-1): Will attempt migration (Any information below is purely informational)
• ukui-session-manager/riscv64 (4.0.0.1-1 to 4.0.0.1-1)
  • Migration status for ukui-session-manager/riscv64 (4.0.0.1-1 to 4.0.0.1-1): Will attempt migration (Any information below is purely informational)
• ukui-sidebar/riscv64 (3.1.2-1 to 3.1.2-1)
  • Migration status for ukui-sidebar/riscv64 (3.1.2-1 to 3.1.2-1): Will attempt migration (Any information below is purely informational)
• ukui-system-monitor/riscv64 (1.0.4-1 to 1.0.4-1)
  • Migration status for ukui-system-monitor/riscv64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• ukui-window-switch/riscv64 (3.0.1-1 to 3.0.1-1)
  • Migration status for ukui-window-switch/riscv64 (3.0.1-1 to 3.0.1-1): Will attempt migration (Any information below is purely informational)
• ulcc/riscv64 (1.0.2-3 to 1.0.2-3)
  • Migration status for ulcc/riscv64 (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• ultracopier/riscv64 (2.2.6.0-1.1 to 2.2.6.0-1.1)
  • Migration status for ultracopier/riscv64 (2.2.6.0-1.1 to 2.2.6.0-1.1): Will attempt migration (Any information below is purely informational)
• umbrello/riscv64 (4:23.08.2-1 to 4:23.08.2-1)
  • Migration status for umbrello/riscv64 (4:23.08.2-1 to 4:23.08.2-1): Will attempt migration (Any information below is purely informational)
• unifont/riscv64 (1:15.1.01-1 to 1:15.1.01-1)
  • Migration status for unifont/riscv64 (1:15.1.01-1 to 1:15.1.01-1): Will attempt migration (Any information below is purely informational)
• universal-ctags/riscv64 (5.9.20210829.0-1 to 5.9.20210829.0-1)
  • Migration status for universal-ctags/riscv64 (5.9.20210829.0-1 to 5.9.20210829.0-1): Will attempt migration (Any information below is purely informational)
• unpaper/riscv64 (7.0.0-3 to 7.0.0-3)
  • Migration status for unpaper/riscv64 (7.0.0-3 to 7.0.0-3): Will attempt migration (Any information below is purely informational)
• uprightdiff/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for uprightdiff/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• usbauth-notifier/riscv64 (1.0.4-2.1 to 1.0.4-2.1)
  • Migration status for usbauth-notifier/riscv64 (1.0.4-2.1 to 1.0.4-2.1): Will attempt migration (Any information below is purely informational)
• usbguard-notifier/riscv64 (0.1.0-3 to 0.1.0-3)
  • Migration status for usbguard-notifier/riscv64 (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• usbview/riscv64 (3.1-1 to 3.1-1)
  • Migration status for usbview/riscv64 (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
• usermode/riscv64 (1.114-3 to 1.114-3)
  • Migration status for usermode/riscv64 (1.114-3 to 1.114-3): Will attempt migration (Any information below is purely informational)
• utf8gen/riscv64 (1.1-4 to 1.1-4)
  • Migration status for utf8gen/riscv64 (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• vagalume/riscv64 (0.8.6-3 to 0.8.6-3)
  • Migration status for vagalume/riscv64 (0.8.6-3 to 0.8.6-3): Will attempt migration (Any information below is purely informational)
• vagrant/riscv64 (2.3.7+git20230731.5fc64cde+dfsg-2 to 2.3.7+git20230731.5fc64cde+dfsg-2)
  • Migration status for vagrant/riscv64 (2.3.7+git20230731.5fc64cde+dfsg-2 to 2.3.7+git20230731.5fc64cde+dfsg-2): Will attempt migration (Any information below is purely informational)
• val-and-rick/riscv64 (0.1a.dfsg1-7 to 0.1a.dfsg1-7)
  • Migration status for val-and-rick/riscv64 (0.1a.dfsg1-7 to 0.1a.dfsg1-7): Will attempt migration (Any information below is purely informational)
• vala-panel/riscv64 (0.5.0-2 to 0.5.0-2)
  • Migration status for vala-panel/riscv64 (0.5.0-2 to 0.5.0-2): Will attempt migration (Any information below is purely informational)
• vala/riscv64 (0.56.17-1 to 0.56.17-1)
  • Migration status for vala/riscv64 (0.56.17-1 to 0.56.17-1): Will attempt migration (Any information below is purely informational)
• valabind/riscv64 (1.8.0-1 to 1.8.0-1)
  • Migration status for valabind/riscv64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• vcdimager/riscv64 (2.0.1+dfsg-6 to 2.0.1+dfsg-6)
  • Migration status for vcdimager/riscv64 (2.0.1+dfsg-6 to 2.0.1+dfsg-6): Will attempt migration (Any information below is purely informational)
• vdr-plugin-dvbhddevice/riscv64 (2.2.0-15 to 2.2.0-15)
  • Migration status for vdr-plugin-dvbhddevice/riscv64 (2.2.0-15 to 2.2.0-15): Will attempt migration (Any information below is purely informational)
• vdr-plugin-dvbsddevice/riscv64 (2.2.0-15 to 2.2.0-15)
  • Migration status for vdr-plugin-dvbsddevice/riscv64 (2.2.0-15 to 2.2.0-15): Will attempt migration (Any information below is purely informational)
• vdr-plugin-dvd/riscv64 (0.3.6~b03+git20211216-2 to 0.3.6~b03+git20211216-2)
  • Migration status for vdr-plugin-dvd/riscv64 (0.3.6~b03+git20211216-2 to 0.3.6~b03+git20211216-2): Will attempt migration (Any information below is purely informational)
• vdr-plugin-epgsearch/riscv64 (2.4.1-2 to 2.4.1-2)
  • Migration status for vdr-plugin-epgsearch/riscv64 (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
• vdr-plugin-epgsync/riscv64 (1.0.1-8 to 1.0.1-8)
  • Migration status for vdr-plugin-epgsync/riscv64 (1.0.1-8 to 1.0.1-8): Will attempt migration (Any information below is purely informational)
• vdr-plugin-femon/riscv64 (2.4.0-5 to 2.4.0-5)
  • Migration status for vdr-plugin-femon/riscv64 (2.4.0-5 to 2.4.0-5): Will attempt migration (Any information below is purely informational)
• vdr-plugin-fritzbox/riscv64 (1.5.4-2 to 1.5.4-2)
  • Migration status for vdr-plugin-fritzbox/riscv64 (1.5.4-2 to 1.5.4-2): Will attempt migration (Any information below is purely informational)
• vdr-plugin-live/riscv64 (3.1.3-3 to 3.1.3-3)
  • Migration status for vdr-plugin-live/riscv64 (3.1.3-3 to 3.1.3-3): Will attempt migration (Any information below is purely informational)
• vdr-plugin-osdserver/riscv64 (0.1.3-22 to 0.1.3-22)
  • Migration status for vdr-plugin-osdserver/riscv64 (0.1.3-22 to 0.1.3-22): Will attempt migration (Any information below is purely informational)
• vdr-plugin-osdteletext/riscv64 (2.3.1-1 to 2.3.1-1)
  • Migration status for vdr-plugin-osdteletext/riscv64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• vdr-plugin-remote/riscv64 (0.7.0-6 to 0.7.0-6)
  • Migration status for vdr-plugin-remote/riscv64 (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• vdr-plugin-satip/riscv64 (2.4.1-2 to 2.4.1-2)
  • Migration status for vdr-plugin-satip/riscv64 (2.4.1-2 to 2.4.1-2): Will attempt migration (Any information below is purely informational)
• vdr-plugin-skinenigmang/riscv64 (0.1.2+git20190720-4 to 0.1.2+git20190720-4)
  • Migration status for vdr-plugin-skinenigmang/riscv64 (0.1.2+git20190720-4 to 0.1.2+git20190720-4): Will attempt migration (Any information below is purely informational)
• vdr-plugin-streamdev/riscv64 (0.6.1+git20180514-5 to 0.6.1+git20180514-5)
  • Migration status for vdr-plugin-streamdev/riscv64 (0.6.1+git20180514-5 to 0.6.1+git20180514-5): Will attempt migration (Any information below is purely informational)
• vdr-plugin-svdrposd/riscv64 (1.0.0-11 to 1.0.0-11)
  • Migration status for vdr-plugin-svdrposd/riscv64 (1.0.0-11 to 1.0.0-11): Will attempt migration (Any information below is purely informational)
• vdr-plugin-svdrpservice/riscv64 (1.0.0-10 to 1.0.0-10)
  • Migration status for vdr-plugin-svdrpservice/riscv64 (1.0.0-10 to 1.0.0-10): Will attempt migration (Any information below is purely informational)
• vdr-plugin-vnsiserver/riscv64 (1:1.8.0+git20211205-2 to 1:1.8.0+git20211205-2)
  • Migration status for vdr-plugin-vnsiserver/riscv64 (1:1.8.0+git20211205-2 to 1:1.8.0+git20211205-2): Will attempt migration (Any information below is purely informational)
• vdr-plugin-xineliboutput/riscv64 (2.2.0+git20211212-2.2 to 2.2.0+git20211212-2.2)
  • Migration status for vdr-plugin-xineliboutput/riscv64 (2.2.0+git20211212-2.2 to 2.2.0+git20211212-2.2): Will attempt migration (Any information below is purely informational)
• vdr/riscv64 (2.6.0-1.1 to 2.6.0-1.1)
  • Migration status for vdr/riscv64 (2.6.0-1.1 to 2.6.0-1.1): Will attempt migration (Any information below is purely informational)
• veroroute/riscv64 (2.38-1 to 2.38-1)
  • Migration status for veroroute/riscv64 (2.38-1 to 2.38-1): Will attempt migration (Any information below is purely informational)
• veusz/riscv64 (3.6.2-1.1 to 3.6.2-1.1)
  • Migration status for veusz/riscv64 (3.6.2-1.1 to 3.6.2-1.1): Will attempt migration (Any information below is purely informational)
• vibes/riscv64 (0.2.3+dfsg-2 to 0.2.3+dfsg-2)
  • Migration status for vibes/riscv64 (0.2.3+dfsg-2 to 0.2.3+dfsg-2): Will attempt migration (Any information below is purely informational)
• viewnior/amd64 (1.8-5 to 1.8-5)
  • Migration status for viewnior/amd64 (1.8-5 to 1.8-5): Will attempt migration (Any information below is purely informational)
    • Depends: viewnior/amd64 exiv2
• viewnior/arm64 (1.8-5 to 1.8-5)
  • Migration status for viewnior/arm64 (1.8-5 to 1.8-5): Will attempt migration (Any information below is purely informational)
    • Depends: viewnior/arm64 exiv2
• viewnior/armel (1.8-5 to 1.8-5)
  • Migration status for viewnior/armel (1.8-5 to 1.8-5): Will attempt migration (Any information below is purely informational)
    • Depends: viewnior/armel exiv2
• viewnior/armhf (1.8-5 to 1.8-5)
  • Migration status for viewnior/armhf (1.8-5 to 1.8-5): Will attempt migration (Any information below is purely informational)
    • Depends: viewnior/armhf exiv2
• viewnior/i386 (1.8-5 to 1.8-5)
  • Migration status for viewnior/i386 (1.8-5 to 1.8-5): Will attempt migration (Any information below is purely informational)
    • Depends: viewnior/i386 exiv2
• viewnior/mips64el (1.8-5 to 1.8-5)
  • Migration status for viewnior/mips64el (1.8-5 to 1.8-5): Will attempt migration (Any information below is purely informational)
    • Depends: viewnior/mips64el exiv2
• viewnior/ppc64el (1.8-5 to 1.8-5)
  • Migration status for viewnior/ppc64el (1.8-5 to 1.8-5): Will attempt migration (Any information below is purely informational)
    • Depends: viewnior/ppc64el exiv2
• viewnior/s390x (1.8-5 to 1.8-5)
  • Migration status for viewnior/s390x (1.8-5 to 1.8-5): Will attempt migration (Any information below is purely informational)
    • Depends: viewnior/s390x exiv2
• vino/riscv64 (3.22.0-6 to 3.22.0-6)
  • Migration status for vino/riscv64 (3.22.0-6 to 3.22.0-6): Will attempt migration (Any information below is purely informational)
• virt-p2v/riscv64 (1.42.3-1 to 1.42.3-1)
  • Migration status for virt-p2v/riscv64 (1.42.3-1 to 1.42.3-1): Will attempt migration (Any information below is purely informational)
• virt-top/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for virt-top/riscv64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• virt-v2v/riscv64 (2.4.0-2 to 2.4.0-2)
  • Migration status for virt-v2v/riscv64 (2.4.0-2 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
• virt-viewer/riscv64 (11.0-3 to 11.0-3)
  • Migration status for virt-viewer/riscv64 (11.0-3 to 11.0-3): Will attempt migration (Any information below is purely informational)
• viruskiller/riscv64 (1.03-1+dfsg1-3 to 1.03-1+dfsg1-3)
  • Migration status for viruskiller/riscv64 (1.03-1+dfsg1-3 to 1.03-1+dfsg1-3): Will attempt migration (Any information below is purely informational)
• visp/riscv64 (3.6.0-2.1 to 3.6.0-2.1)
  • Migration status for visp/riscv64 (3.6.0-2.1 to 3.6.0-2.1): Will attempt migration (Any information below is purely informational)
• vlfeat/riscv64 (0.9.21+full-2.1 to 0.9.21+full-2.1)
  • Migration status for vlfeat/riscv64 (0.9.21+full-2.1 to 0.9.21+full-2.1): Will attempt migration (Any information below is purely informational)
• vmdb2_pu (0.40-2 to 0.27+really.0.26-1+deb12u1)
  • Migration status for vmdb2_pu (0.40-2 to 0.27+really.0.26-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: vmdb2 is newer in the target suite (0.40-2 0.27+really.0.26-1+deb12u1)
• vmpk/riscv64 (0.9.0-1 to 0.9.0-1)
  • Migration status for vmpk/riscv64 (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
• vokoscreen-ng/riscv64 (3.7.0-1 to 3.7.0-1)
  • Migration status for vokoscreen-ng/riscv64 (3.7.0-1 to 3.7.0-1): Will attempt migration (Any information below is purely informational)
• volumeicon/riscv64 (0.5.1+git20230228-1 to 0.5.1+git20230228-1)
  • Migration status for volumeicon/riscv64 (0.5.1+git20230228-1 to 0.5.1+git20230228-1): Will attempt migration (Any information below is purely informational)
• vprerex/riscv64 (1:6.5.1-1 to 1:6.5.1-1)
  • Migration status for vprerex/riscv64 (1:6.5.1-1 to 1:6.5.1-1): Will attempt migration (Any information below is purely informational)
• vte/riscv64 (1:0.28.2-6.1 to 1:0.28.2-6.1)
  • Migration status for vte/riscv64 (1:0.28.2-6.1 to 1:0.28.2-6.1): Will attempt migration (Any information below is purely informational)
• w3m/riscv64 (0.5.3+git20230121-2 to 0.5.3+git20230121-2)
  • Migration status for w3m/riscv64 (0.5.3+git20230121-2 to 0.5.3+git20230121-2): Will attempt migration (Any information below is purely informational)
• wal2json/riscv64 (2.6-1 to 2.6-1)
  • Migration status for wal2json/riscv64 (2.6-1 to 2.6-1): Will attempt migration (Any information below is purely informational)
• warmux/riscv64 (1:11.04.1+repack2-4 to 1:11.04.1+repack2-4)
  • Migration status for warmux/riscv64 (1:11.04.1+repack2-4 to 1:11.04.1+repack2-4): Will attempt migration (Any information below is purely informational)
• wavbreaker/riscv64 (0.16-3 to 0.16-3)
  • Migration status for wavbreaker/riscv64 (0.16-3 to 0.16-3): Will attempt migration (Any information below is purely informational)
• wayvnc/riscv64 (0.8.0-1 to 0.8.0-1)
  • Migration status for wayvnc/riscv64 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• wbar/riscv64 (2.3.4-13 to 2.3.4-13)
  • Migration status for wbar/riscv64 (2.3.4-13 to 2.3.4-13): Will attempt migration (Any information below is purely informational)
• wdisplays/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for wdisplays/riscv64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• wdm/riscv64 (1.28-27 to 1.28-27)
  • Migration status for wdm/riscv64 (1.28-27 to 1.28-27): Will attempt migration (Any information below is purely informational)
• webissues/riscv64 (1.1.5-10 to 1.1.5-10)
  • Migration status for webissues/riscv64 (1.1.5-10 to 1.1.5-10): Will attempt migration (Any information below is purely informational)
• wfview/riscv64 (1.64-2 to 1.64-2)
  • Migration status for wfview/riscv64 (1.64-2 to 1.64-2): Will attempt migration (Any information below is purely informational)
• wings3d/riscv64 (2.3-1 to 2.3-1)
  • Migration status for wings3d/riscv64 (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• wiredpanda/riscv64 (4.1.12-1 to 4.1.12-1)
  • Migration status for wiredpanda/riscv64 (4.1.12-1 to 4.1.12-1): Will attempt migration (Any information below is purely informational)
• wizznic/riscv64 (0.9.9+dfsg-2 to 0.9.9+dfsg-2)
  • Migration status for wizznic/riscv64 (0.9.9+dfsg-2 to 0.9.9+dfsg-2): Will attempt migration (Any information below is purely informational)
• wkhtmltopdf/riscv64 (0.12.6-2 to 0.12.6-2)
  • Migration status for wkhtmltopdf/riscv64 (0.12.6-2 to 0.12.6-2): Will attempt migration (Any information below is purely informational)
• wmaker/riscv64 (0.96.0-2 to 0.96.0-2)
  • Migration status for wmaker/riscv64 (0.96.0-2 to 0.96.0-2): Will attempt migration (Any information below is purely informational)
• wmauda/riscv64 (0.9-4 to 0.9-4)
  • Migration status for wmauda/riscv64 (0.9-4 to 0.9-4): Will attempt migration (Any information below is purely informational)
• wmcliphist/riscv64 (2.1-4 to 2.1-4)
  • Migration status for wmcliphist/riscv64 (2.1-4 to 2.1-4): Will attempt migration (Any information below is purely informational)
• wmdrawer/riscv64 (0.10.5-6.1 to 0.10.5-6.1)
  • Migration status for wmdrawer/riscv64 (0.10.5-6.1 to 0.10.5-6.1): Will attempt migration (Any information below is purely informational)
• wmforecast/riscv64 (1.9.0-1 to 1.9.0-1)
  • Migration status for wmforecast/riscv64 (1.9.0-1 to 1.9.0-1): Will attempt migration (Any information below is purely informational)
• wmhdplop/riscv64 (0.9.12-1.1 to 0.9.12-1.1)
  • Migration status for wmhdplop/riscv64 (0.9.12-1.1 to 0.9.12-1.1): Will attempt migration (Any information below is purely informational)
• wmressel/riscv64 (0.10-1 to 0.10-1)
  • Migration status for wmressel/riscv64 (0.10-1 to 0.10-1): Will attempt migration (Any information below is purely informational)
• wmshutdown/riscv64 (1.6-2 to 1.6-2)
  • Migration status for wmshutdown/riscv64 (1.6-2 to 1.6-2): Will attempt migration (Any information below is purely informational)
• wmstickynotes/riscv64 (0.7-5 to 0.7-5)
  • Migration status for wmstickynotes/riscv64 (0.7-5 to 0.7-5): Will attempt migration (Any information below is purely informational)
• wofi/riscv64 (1.4.1-1 to 1.4.1-1)
  • Migration status for wofi/riscv64 (1.4.1-1 to 1.4.1-1): Will attempt migration (Any information below is purely informational)
• wordwarvi/riscv64 (1.0.4-2 to 1.0.4-2)
  • Migration status for wordwarvi/riscv64 (1.0.4-2 to 1.0.4-2): Will attempt migration (Any information below is purely informational)
• wpebackend-fdo/riscv64 (1.14.2-1 to 1.14.2-1)
  • Migration status for wpebackend-fdo/riscv64 (1.14.2-1 to 1.14.2-1): Will attempt migration (Any information below is purely informational)
• wrapperfactory.app/riscv64 (0.1.0-5 to 0.1.0-5)
  • Migration status for wrapperfactory.app/riscv64 (0.1.0-5 to 0.1.0-5): Will attempt migration (Any information below is purely informational)
• writerperfect/riscv64 (0.9.6-3 to 0.9.6-3)
  • Migration status for writerperfect/riscv64 (0.9.6-3 to 0.9.6-3): Will attempt migration (Any information below is purely informational)
• wv/riscv64 (1.2.9-8 to 1.2.9-8)
  • Migration status for wv/riscv64 (1.2.9-8 to 1.2.9-8): Will attempt migration (Any information below is purely informational)
• wxastrocapture/riscv64 (1.8.1+git20140821.796e1a1+dfsg-2 to 1.8.1+git20140821.796e1a1+dfsg-2)
  • Migration status for wxastrocapture/riscv64 (1.8.1+git20140821.796e1a1+dfsg-2 to 1.8.1+git20140821.796e1a1+dfsg-2): Will attempt migration (Any information below is purely informational)
• wxedid/riscv64 (0.0.21-4 to 0.0.21-4)
  • Migration status for wxedid/riscv64 (0.0.21-4 to 0.0.21-4): Will attempt migration (Any information below is purely informational)
• wxhexeditor/riscv64 (0.24+repack-2 to 0.24+repack-2)
  • Migration status for wxhexeditor/riscv64 (0.24+repack-2 to 0.24+repack-2): Will attempt migration (Any information below is purely informational)
• wxmaxima/riscv64 (24.02.1-1 to 24.02.1-1)
  • Migration status for wxmaxima/riscv64 (24.02.1-1 to 24.02.1-1): Will attempt migration (Any information below is purely informational)
• wxsqlite3/riscv64 (3.4.1~dfsg-9.1 to 3.4.1~dfsg-9.1)
  • Migration status for wxsqlite3/riscv64 (3.4.1~dfsg-9.1 to 3.4.1~dfsg-9.1): Will attempt migration (Any information below is purely informational)
• wys/riscv64 (0.1.12-1 to 0.1.12-1)
  • Migration status for wys/riscv64 (0.1.12-1 to 0.1.12-1): Will attempt migration (Any information below is purely informational)
• x2godesktopsharing/riscv64 (3.2.0.0-2 to 3.2.0.0-2)
  • Migration status for x2godesktopsharing/riscv64 (3.2.0.0-2 to 3.2.0.0-2): Will attempt migration (Any information below is purely informational)
• x2gokdrive/riscv64 (0.0.0.3-1 to 0.0.0.3-1)
  • Migration status for x2gokdrive/riscv64 (0.0.0.3-1 to 0.0.0.3-1): Will attempt migration (Any information below is purely informational)
• x2gokdriveclient/riscv64 (0.0.0.1-1 to 0.0.0.1-1)
  • Migration status for x2gokdriveclient/riscv64 (0.0.0.1-1 to 0.0.0.1-1): Will attempt migration (Any information below is purely informational)
• x2goserver/riscv64 (4.1.0.6-1.1 to 4.1.0.6-1.1)
  • Migration status for x2goserver/riscv64 (4.1.0.6-1.1 to 4.1.0.6-1.1): Will attempt migration (Any information below is purely informational)
• xaos/riscv64 (4.3.2-1 to 4.3.2-1)
  • Migration status for xaos/riscv64 (4.3.2-1 to 4.3.2-1): Will attempt migration (Any information below is purely informational)
• xarchiver/riscv64 (1:0.5.4.23-1 to 1:0.5.4.23-1)
  • Migration status for xarchiver/riscv64 (1:0.5.4.23-1 to 1:0.5.4.23-1): Will attempt migration (Any information below is purely informational)
• xastir/riscv64 (2.2.0-1 to 2.2.0-1)
  • Migration status for xastir/riscv64 (2.2.0-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
• xboard/riscv64 (4.9.1-2 to 4.9.1-2)
  • Migration status for xboard/riscv64 (4.9.1-2 to 4.9.1-2): Will attempt migration (Any information below is purely informational)
• xcfa/riscv64 (5.0.2-2 to 5.0.2-2)
  • Migration status for xcfa/riscv64 (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
• xchm/riscv64 (2:1.36-1 to 2:1.36-1)
  • Migration status for xchm/riscv64 (2:1.36-1 to 2:1.36-1): Will attempt migration (Any information below is purely informational)
• xcowsay/riscv64 (1.6-1 to 1.6-1)
  • Migration status for xcowsay/riscv64 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
• xdaliclock/riscv64 (2.48-1 to 2.48-1)
  • Migration status for xdaliclock/riscv64 (2.48-1 to 2.48-1): Will attempt migration (Any information below is purely informational)
• xdebug/riscv64 (3.2.0+3.1.6+2.9.8+2.8.1+2.5.5-3 to 3.2.0+3.1.6+2.9.8+2.8.1+2.5.5-3)
  • Migration status for xdebug/riscv64 (3.2.0+3.1.6+2.9.8+2.8.1+2.5.5-3 to 3.2.0+3.1.6+2.9.8+2.8.1+2.5.5-3): Will attempt migration (Any information below is purely informational)
• xdemorse/riscv64 (3.6.7-1 to 3.6.7-1)
  • Migration status for xdemorse/riscv64 (3.6.7-1 to 3.6.7-1): Will attempt migration (Any information below is purely informational)
• xdg-desktop-portal-gtk/riscv64 (1.15.1-1 to 1.15.1-1)
  • Migration status for xdg-desktop-portal-gtk/riscv64 (1.15.1-1 to 1.15.1-1): Will attempt migration (Any information below is purely informational)
• xdg-desktop-portal-wlr/riscv64 (0.7.1-1 to 0.7.1-1)
  • Migration status for xdg-desktop-portal-wlr/riscv64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• xdg-desktop-portal/riscv64 (1.18.4-1 to 1.18.4-1)
  • Migration status for xdg-desktop-portal/riscv64 (1.18.4-1 to 1.18.4-1): Will attempt migration (Any information below is purely informational)
• xdg-user-dirs-gtk/riscv64 (0.11-1 to 0.11-1)
  • Migration status for xdg-user-dirs-gtk/riscv64 (0.11-1 to 0.11-1): Will attempt migration (Any information below is purely informational)
• xdmf/riscv64 (3.0+git20190531-13.1 to 3.0+git20190531-13.1)
  • Migration status for xdmf/riscv64 (3.0+git20190531-13.1 to 3.0+git20190531-13.1): Will attempt migration (Any information below is purely informational)
• xdx/riscv64 (2.91-2 to 2.91-2)
  • Migration status for xdx/riscv64 (2.91-2 to 2.91-2): Will attempt migration (Any information below is purely informational)
• xeus-python/riscv64 (0.15.10+~0.6.1-2 to 0.15.10+~0.6.1-2)
  • Migration status for xeus-python/riscv64 (0.15.10+~0.6.1-2 to 0.15.10+~0.6.1-2): Will attempt migration (Any information below is purely informational)
• xeus-zmq/riscv64 (1.1.1-2 to 1.1.1-2)
  • Migration status for xeus-zmq/riscv64 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• xf86-input-mtrack/riscv64 (0.3.1-1.3 to 0.3.1-1.3)
  • Migration status for xf86-input-mtrack/riscv64 (0.3.1-1.3 to 0.3.1-1.3): Will attempt migration (Any information below is purely informational)
• xf86-input-multitouch/riscv64 (1.0~rc3-2.1 to 1.0~rc3-2.1)
  • Migration status for xf86-input-multitouch/riscv64 (1.0~rc3-2.1 to 1.0~rc3-2.1): Will attempt migration (Any information below is purely informational)
• xf86-input-xwiimote/riscv64 (0.5-1 to 0.5-1)
  • Migration status for xf86-input-xwiimote/riscv64 (0.5-1 to 0.5-1): Will attempt migration (Any information below is purely informational)
• xfce4-appfinder/riscv64 (4.18.0-1 to 4.18.0-1)
  • Migration status for xfce4-appfinder/riscv64 (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• xfce4-battery-plugin/riscv64 (1.1.5-1 to 1.1.5-1)
  • Migration status for xfce4-battery-plugin/riscv64 (1.1.5-1 to 1.1.5-1): Will attempt migration (Any information below is purely informational)
• xfce4-clipman-plugin/riscv64 (2:1.6.6-1 to 2:1.6.6-1)
  • Migration status for xfce4-clipman-plugin/riscv64 (2:1.6.6-1 to 2:1.6.6-1): Will attempt migration (Any information below is purely informational)
• xfce4-cpufreq-plugin/riscv64 (1.2.8-2 to 1.2.8-2)
  • Migration status for xfce4-cpufreq-plugin/riscv64 (1.2.8-2 to 1.2.8-2): Will attempt migration (Any information below is purely informational)
• xfce4-cpugraph-plugin/riscv64 (1.2.10-1 to 1.2.10-1)
  • Migration status for xfce4-cpugraph-plugin/riscv64 (1.2.10-1 to 1.2.10-1): Will attempt migration (Any information below is purely informational)
• xfce4-datetime-plugin/riscv64 (0.8.3-1 to 0.8.3-1)
  • Migration status for xfce4-datetime-plugin/riscv64 (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• xfce4-dict/riscv64 (0.8.6-1 to 0.8.6-1)
  • Migration status for xfce4-dict/riscv64 (0.8.6-1 to 0.8.6-1): Will attempt migration (Any information below is purely informational)
• xfce4-diskperf-plugin/riscv64 (2.7.0-1 to 2.7.0-1)
  • Migration status for xfce4-diskperf-plugin/riscv64 (2.7.0-1 to 2.7.0-1): Will attempt migration (Any information below is purely informational)
• xfce4-eyes-plugin/riscv64 (4.6.0-1 to 4.6.0-1)
  • Migration status for xfce4-eyes-plugin/riscv64 (4.6.0-1 to 4.6.0-1): Will attempt migration (Any information below is purely informational)
• xfce4-fsguard-plugin/riscv64 (1.1.3-1 to 1.1.3-1)
  • Migration status for xfce4-fsguard-plugin/riscv64 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• xfce4-genmon-plugin/riscv64 (4.1.1-1 to 4.1.1-1)
  • Migration status for xfce4-genmon-plugin/riscv64 (4.1.1-1 to 4.1.1-1): Will attempt migration (Any information below is purely informational)
• xfce4-goodies/riscv64 (4.18.2 to 4.18.2)
  • Migration status for xfce4-goodies/riscv64 (4.18.2 to 4.18.2): Will attempt migration (Any information below is purely informational)
• xfce4-indicator-plugin/riscv64 (2.4.2-1 to 2.4.2-1)
  • Migration status for xfce4-indicator-plugin/riscv64 (2.4.2-1 to 2.4.2-1): Will attempt migration (Any information below is purely informational)
• xfce4-mailwatch-plugin/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for xfce4-mailwatch-plugin/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• xfce4-mount-plugin/riscv64 (1.1.6-1 to 1.1.6-1)
  • Migration status for xfce4-mount-plugin/riscv64 (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• xfce4-mpc-plugin/riscv64 (0.5.3-1 to 0.5.3-1)
  • Migration status for xfce4-mpc-plugin/riscv64 (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
• xfce4-netload-plugin/riscv64 (1.4.1-1 to 1.4.1-1)
  • Migration status for xfce4-netload-plugin/riscv64 (1.4.1-1 to 1.4.1-1): Will attempt migration (Any information below is purely informational)
• xfce4-places-plugin/riscv64 (1.8.3-1 to 1.8.3-1)
  • Migration status for xfce4-places-plugin/riscv64 (1.8.3-1 to 1.8.3-1): Will attempt migration (Any information below is purely informational)
• xfce4-pulseaudio-plugin/riscv64 (0.4.8-1 to 0.4.8-1)
  • Migration status for xfce4-pulseaudio-plugin/riscv64 (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• xfce4-screensaver/riscv64 (4.18.3-1 to 4.18.3-1)
  • Migration status for xfce4-screensaver/riscv64 (4.18.3-1 to 4.18.3-1): Will attempt migration (Any information below is purely informational)
• xfce4-sensors-plugin/riscv64 (1.4.4-1 to 1.4.4-1)
  • Migration status for xfce4-sensors-plugin/riscv64 (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
• xfce4-smartbookmark-plugin/riscv64 (0.5.2-1 to 0.5.2-1)
  • Migration status for xfce4-smartbookmark-plugin/riscv64 (0.5.2-1 to 0.5.2-1): Will attempt migration (Any information below is purely informational)
• xfce4-systemload-plugin/riscv64 (1.3.2-2 to 1.3.2-2)
  • Migration status for xfce4-systemload-plugin/riscv64 (1.3.2-2 to 1.3.2-2): Will attempt migration (Any information below is purely informational)
• xfce4-taskmanager/riscv64 (1.5.7-1 to 1.5.7-1)
  • Migration status for xfce4-taskmanager/riscv64 (1.5.7-1 to 1.5.7-1): Will attempt migration (Any information below is purely informational)
• xfce4-terminal/riscv64 (1.1.3-1 to 1.1.3-1)
  • Migration status for xfce4-terminal/riscv64 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• xfce4-timer-plugin/riscv64 (1.7.2-1 to 1.7.2-1)
  • Migration status for xfce4-timer-plugin/riscv64 (1.7.2-1 to 1.7.2-1): Will attempt migration (Any information below is purely informational)
• xfce4-verve-plugin/riscv64 (2.0.3-1 to 2.0.3-1)
  • Migration status for xfce4-verve-plugin/riscv64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• xfce4-wavelan-plugin/riscv64 (0.6.3-1 to 0.6.3-1)
  • Migration status for xfce4-wavelan-plugin/riscv64 (0.6.3-1 to 0.6.3-1): Will attempt migration (Any information below is purely informational)
• xfce4-weather-plugin/riscv64 (0.11.2-1 to 0.11.2-1)
  • Migration status for xfce4-weather-plugin/riscv64 (0.11.2-1 to 0.11.2-1): Will attempt migration (Any information below is purely informational)
• xfce4-whiskermenu-plugin/riscv64 (2.8.3-1 to 2.8.3-1)
  • Migration status for xfce4-whiskermenu-plugin/riscv64 (2.8.3-1 to 2.8.3-1): Will attempt migration (Any information below is purely informational)
• xfce4-windowck-plugin/riscv64 (0.5.1-1 to 0.5.1-1)
  • Migration status for xfce4-windowck-plugin/riscv64 (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• xfce4-xkb-plugin/riscv64 (1:0.8.3-1 to 1:0.8.3-1)
  • Migration status for xfce4-xkb-plugin/riscv64 (1:0.8.3-1 to 1:0.8.3-1): Will attempt migration (Any information below is purely informational)
• xfdesktop4/riscv64 (4.18.1-1 to 4.18.1-1)
  • Migration status for xfdesktop4/riscv64 (4.18.1-1 to 4.18.1-1): Will attempt migration (Any information below is purely informational)
• xfe/riscv64 (1.46.1-1 to 1.46.1-1)
  • Migration status for xfe/riscv64 (1.46.1-1 to 1.46.1-1): Will attempt migration (Any information below is purely informational)
• xfwm4/riscv64 (4.18.0-1 to 4.18.0-1)
  • Migration status for xfwm4/riscv64 (4.18.0-1 to 4.18.0-1): Will attempt migration (Any information below is purely informational)
• xiccd/riscv64 (0.3.0-2 to 0.3.0-2)
  • Migration status for xiccd/riscv64 (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• xine-ui/riscv64 (0.99.14+hg20240403-1 to 0.99.14+hg20240403-1)
  • Migration status for xine-ui/riscv64 (0.99.14+hg20240403-1 to 0.99.14+hg20240403-1): Will attempt migration (Any information below is purely informational)
• xiphos/riscv64 (4.2.1+dfsg1-8 to 4.2.1+dfsg1-8)
  • Migration status for xiphos/riscv64 (4.2.1+dfsg1-8 to 4.2.1+dfsg1-8): Will attempt migration (Any information below is purely informational)
• xjadeo/riscv64 (0.8.12-1 to 0.8.12-1)
  • Migration status for xjadeo/riscv64 (0.8.12-1 to 0.8.12-1): Will attempt migration (Any information below is purely informational)
• xlog/riscv64 (2.0.24-3 to 2.0.24-3)
  • Migration status for xlog/riscv64 (2.0.24-3 to 2.0.24-3): Will attempt migration (Any information below is purely informational)
• xmlstarlet/riscv64 (1.6.1-4 to 1.6.1-4)
  • Migration status for xmlstarlet/riscv64 (1.6.1-4 to 1.6.1-4): Will attempt migration (Any information below is purely informational)
• xmonad-contrib/riscv64 (0.17.1-2 to 0.17.1-2)
  • Migration status for xmonad-contrib/riscv64 (0.17.1-2 to 0.17.1-2): Will attempt migration (Any information below is purely informational)
• xmonad-extras/riscv64 (0.17.0-2 to 0.17.0-2)
  • Migration status for xmonad-extras/riscv64 (0.17.0-2 to 0.17.0-2): Will attempt migration (Any information below is purely informational)
• xmonad-wallpaper/riscv64 (0.0.1.5-3 to 0.0.1.5-3)
  • Migration status for xmonad-wallpaper/riscv64 (0.0.1.5-3 to 0.0.1.5-3): Will attempt migration (Any information below is purely informational)
• xmonad/riscv64 (0.17.2-1 to 0.17.2-1)
  • Migration status for xmonad/riscv64 (0.17.2-1 to 0.17.2-1): Will attempt migration (Any information below is purely informational)
• xmoto/riscv64 (0.6.2+repack-2 to 0.6.2+repack-2)
  • Migration status for xmoto/riscv64 (0.6.2+repack-2 to 0.6.2+repack-2): Will attempt migration (Any information below is purely informational)
• xmpi/riscv64 (2.2.3b8-14 to 2.2.3b8-14)
  • Migration status for xmpi/riscv64 (2.2.3b8-14 to 2.2.3b8-14): Will attempt migration (Any information below is purely informational)
• xournal/riscv64 (1:0.4.8.2016-7 to 1:0.4.8.2016-7)
  • Migration status for xournal/riscv64 (1:0.4.8.2016-7 to 1:0.4.8.2016-7): Will attempt migration (Any information below is purely informational)
• xournalpp/riscv64 (1.2.3-1 to 1.2.3-1)
  • Migration status for xournalpp/riscv64 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
• xpad/riscv64 (5.8.0-1 to 5.8.0-1)
  • Migration status for xpad/riscv64 (5.8.0-1 to 5.8.0-1): Will attempt migration (Any information below is purely informational)
• xpenguins/riscv64 (3.2.1-2 to 3.2.1-2)
  • Migration status for xpenguins/riscv64 (3.2.1-2 to 3.2.1-2): Will attempt migration (Any information below is purely informational)
• xpuzzles/riscv64 (7.7.1-1.2 to 7.7.1-1.2)
  • Migration status for xpuzzles/riscv64 (7.7.1-1.2 to 7.7.1-1.2): Will attempt migration (Any information below is purely informational)
• xqf/riscv64 (1.0.6-5 to 1.0.6-5)
  • Migration status for xqf/riscv64 (1.0.6-5 to 1.0.6-5): Will attempt migration (Any information below is purely informational)
• xracer/riscv64 (0.96.9.1-12 to 0.96.9.1-12)
  • Migration status for xracer/riscv64 (0.96.9.1-12 to 0.96.9.1-12): Will attempt migration (Any information below is purely informational)
• xsane/riscv64 (0.999-12 to 0.999-12)
  • Migration status for xsane/riscv64 (0.999-12 to 0.999-12): Will attempt migration (Any information below is purely informational)
• xscreensaver/riscv64 (6.08+dfsg1-1 to 6.08+dfsg1-1)
  • Migration status for xscreensaver/riscv64 (6.08+dfsg1-1 to 6.08+dfsg1-1): Will attempt migration (Any information below is purely informational)
• xsensors/riscv64 (0.80-1 to 0.80-1)
  • Migration status for xsensors/riscv64 (0.80-1 to 0.80-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-input-elographics/riscv64 (1:1.4.3-1 to 1:1.4.3-1)
  • Migration status for xserver-xorg-input-elographics/riscv64 (1:1.4.3-1 to 1:1.4.3-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-input-evdev/riscv64 (1:2.10.6-2 to 1:2.10.6-2)
  • Migration status for xserver-xorg-input-evdev/riscv64 (1:2.10.6-2 to 1:2.10.6-2): Will attempt migration (Any information below is purely informational)
• xserver-xorg-input-keyboard/riscv64 (1:1.9.0-1 to 1:1.9.0-1)
  • Migration status for xserver-xorg-input-keyboard/riscv64 (1:1.9.0-1 to 1:1.9.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-input-libinput/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for xserver-xorg-input-libinput/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-input-mouse/riscv64 (1:1.9.3-1 to 1:1.9.3-1)
  • Migration status for xserver-xorg-input-mouse/riscv64 (1:1.9.3-1 to 1:1.9.3-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-input-synaptics/riscv64 (1.9.2-1 to 1.9.2-1)
  • Migration status for xserver-xorg-input-synaptics/riscv64 (1.9.2-1 to 1.9.2-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-amdgpu/riscv64 (23.0.0-1 to 23.0.0-1)
  • Migration status for xserver-xorg-video-amdgpu/riscv64 (23.0.0-1 to 23.0.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-ati/riscv64 (1:22.0.0-1 to 1:22.0.0-1)
  • Migration status for xserver-xorg-video-ati/riscv64 (1:22.0.0-1 to 1:22.0.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-dummy/riscv64 (1:0.4.0-1 to 1:0.4.0-1)
  • Migration status for xserver-xorg-video-dummy/riscv64 (1:0.4.0-1 to 1:0.4.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-fbdev/riscv64 (1:0.5.0-2 to 1:0.5.0-2)
  • Migration status for xserver-xorg-video-fbdev/riscv64 (1:0.5.0-2 to 1:0.5.0-2): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-mach64/riscv64 (6.9.7-1 to 6.9.7-1)
  • Migration status for xserver-xorg-video-mach64/riscv64 (6.9.7-1 to 6.9.7-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-mga/riscv64 (1:2.0.0-1 to 1:2.0.0-1)
  • Migration status for xserver-xorg-video-mga/riscv64 (1:2.0.0-1 to 1:2.0.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-neomagic/riscv64 (1:1.3.0-2 to 1:1.3.0-2)
  • Migration status for xserver-xorg-video-neomagic/riscv64 (1:1.3.0-2 to 1:1.3.0-2): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-nouveau/riscv64 (1:1.0.17-3 to 1:1.0.17-3)
  • Migration status for xserver-xorg-video-nouveau/riscv64 (1:1.0.17-3 to 1:1.0.17-3): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-r128/riscv64 (6.12.1-1 to 6.12.1-1)
  • Migration status for xserver-xorg-video-r128/riscv64 (6.12.1-1 to 6.12.1-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-savage/riscv64 (1:2.3.9-5 to 1:2.3.9-5)
  • Migration status for xserver-xorg-video-savage/riscv64 (1:2.3.9-5 to 1:2.3.9-5): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-siliconmotion/riscv64 (1:1.7.9-4 to 1:1.7.9-4)
  • Migration status for xserver-xorg-video-siliconmotion/riscv64 (1:1.7.9-4 to 1:1.7.9-4): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-sisusb/riscv64 (1:0.9.7-3 to 1:0.9.7-3)
  • Migration status for xserver-xorg-video-sisusb/riscv64 (1:0.9.7-3 to 1:0.9.7-3): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-tdfx/riscv64 (1:1.5.0-5 to 1:1.5.0-5)
  • Migration status for xserver-xorg-video-tdfx/riscv64 (1:1.5.0-5 to 1:1.5.0-5): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-trident/riscv64 (1:1.4.0-1 to 1:1.4.0-1)
  • Migration status for xserver-xorg-video-trident/riscv64 (1:1.4.0-1 to 1:1.4.0-1): Will attempt migration (Any information below is purely informational)
• xserver-xorg-video-vesa/riscv64 (1:2.6.0-1 to 1:2.6.0-1)
  • Migration status for xserver-xorg-video-vesa/riscv64 (1:2.6.0-1 to 1:2.6.0-1): Will attempt migration (Any information below is purely informational)
• xsnow/riscv64 (1:3.7.8-1 to 1:3.7.8-1)
  • Migration status for xsnow/riscv64 (1:3.7.8-1 to 1:3.7.8-1): Will attempt migration (Any information below is purely informational)
• xsunpinyin/riscv64 (2.0.3-9 to 2.0.3-9)
  • Migration status for xsunpinyin/riscv64 (2.0.3-9 to 2.0.3-9): Will attempt migration (Any information below is purely informational)
• xsynth-dssi/riscv64 (0.9.4-4 to 0.9.4-4)
  • Migration status for xsynth-dssi/riscv64 (0.9.4-4 to 0.9.4-4): Will attempt migration (Any information below is purely informational)
• xteddy/riscv64 (2.2-5 to 2.2-5)
  • Migration status for xteddy/riscv64 (2.2-5 to 2.2-5): Will attempt migration (Any information below is purely informational)
• xwax/riscv64 (1.9-1 to 1.9-1)
  • Migration status for xwax/riscv64 (1.9-1 to 1.9-1): Will attempt migration (Any information below is purely informational)
• xxdiff/riscv64 (1:5.1+git20240417+dfsg-1 to 1:5.1+git20240417+dfsg-1)
  • Migration status for xxdiff/riscv64 (1:5.1+git20240417+dfsg-1 to 1:5.1+git20240417+dfsg-1): Will attempt migration (Any information below is purely informational)
• xye/riscv64 (0.12.2+dfsg-12 to 0.12.2+dfsg-12)
  • Migration status for xye/riscv64 (0.12.2+dfsg-12 to 0.12.2+dfsg-12): Will attempt migration (Any information below is purely informational)
• xygrib/riscv64 (1.2.6.1-3 to 1.2.6.1-3)
  • Migration status for xygrib/riscv64 (1.2.6.1-3 to 1.2.6.1-3): Will attempt migration (Any information below is purely informational)
• xylib/riscv64 (1.6-3.1 to 1.6-3.1)
  • Migration status for xylib/riscv64 (1.6-3.1 to 1.6-3.1): Will attempt migration (Any information below is purely informational)
• xymon/riscv64 (4.3.30-3 to 4.3.30-3)
  • Migration status for xymon/riscv64 (4.3.30-3 to 4.3.30-3): Will attempt migration (Any information below is purely informational)
• xyscan/riscv64 (4.66-1 to 4.66-1)
  • Migration status for xyscan/riscv64 (4.66-1 to 4.66-1): Will attempt migration (Any information below is purely informational)
• xzgv/riscv64 (0.9.2-2 to 0.9.2-2)
  • Migration status for xzgv/riscv64 (0.9.2-2 to 0.9.2-2): Will attempt migration (Any information below is purely informational)
• yabause/riscv64 (0.9.15-3 to 0.9.15-3)
  • Migration status for yabause/riscv64 (0.9.15-3 to 0.9.15-3): Will attempt migration (Any information below is purely informational)
• yagf/riscv64 (0.9.5+repack1-1 to 0.9.5+repack1-1)
  • Migration status for yagf/riscv64 (0.9.5+repack1-1 to 0.9.5+repack1-1): Will attempt migration (Any information below is purely informational)
• yakuake/riscv64 (23.08.1-1 to 23.08.1-1)
  • Migration status for yakuake/riscv64 (23.08.1-1 to 23.08.1-1): Will attempt migration (Any information below is purely informational)
• yasw/riscv64 (0.6-2 to 0.6-2)
  • Migration status for yasw/riscv64 (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
• yelp/riscv64 (42.2-1 to 42.2-1)
  • Migration status for yelp/riscv64 (42.2-1 to 42.2-1): Will attempt migration (Any information below is purely informational)
• 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)
• yorick-av/riscv64 (0.0.6-1 to 0.0.6-1)
  • Migration status for yorick-av/riscv64 (0.0.6-1 to 0.0.6-1): Will attempt migration (Any information below is purely informational)
• youtubedl-gui/riscv64 (3.0-2 to 3.0-2)
  • Migration status for youtubedl-gui/riscv64 (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
• yubikey-manager-qt/riscv64 (1.2.5-1 to 1.2.5-1)
  • Migration status for yubikey-manager-qt/riscv64 (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
• yubioath-desktop/riscv64 (5.1.0-3 to 5.1.0-3)
  • Migration status for yubioath-desktop/riscv64 (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
• yuma123/riscv64 (2.13-2.1 to 2.13-2.1)
  • Migration status for yuma123/riscv64 (2.13-2.1 to 2.13-2.1): Will attempt migration (Any information below is purely informational)
• yuview/riscv64 (2.14-1 to 2.14-1)
  • Migration status for yuview/riscv64 (2.14-1 to 2.14-1): Will attempt migration (Any information below is purely informational)
• zam-plugins/riscv64 (4.2+ds-1 to 4.2+ds-1)
  • Migration status for zam-plugins/riscv64 (4.2+ds-1 to 4.2+ds-1): Will attempt migration (Any information below is purely informational)
• zanshin/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for zanshin/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• zatacka/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for zatacka/riscv64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• zaz/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for zaz/riscv64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• zegrapher/riscv64 (3.1.1-4 to 3.1.1-4)
  • Migration status for zegrapher/riscv64 (3.1.1-4 to 3.1.1-4): Will attempt migration (Any information below is purely informational)
• zeitgeist/riscv64 (1.0.4-5 to 1.0.4-5)
  • Migration status for zeitgeist/riscv64 (1.0.4-5 to 1.0.4-5): Will attempt migration (Any information below is purely informational)
• zephyr/riscv64 (3.1.2-1.1 to 3.1.2-1.1)
  • Migration status for zephyr/riscv64 (3.1.2-1.1 to 3.1.2-1.1): Will attempt migration (Any information below is purely informational)
• zeroc-ice/riscv64 (3.7.10-2.3 to 3.7.10-2.3)
  • Migration status for zeroc-ice/riscv64 (3.7.10-2.3 to 3.7.10-2.3): Will attempt migration (Any information below is purely informational)
• zeroconf-ioslave/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for zeroconf-ioslave/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• zeromq3/riscv64 (4.3.5-1 to 4.3.5-1)
  • Migration status for zeromq3/riscv64 (4.3.5-1 to 4.3.5-1): Will attempt migration (Any information below is purely informational)
• zint/riscv64 (2.13.0-1 to 2.13.0-1)
  • Migration status for zint/riscv64 (2.13.0-1 to 2.13.0-1): Will attempt migration (Any information below is purely informational)
• zipper.app/riscv64 (1.5-3 to 1.5-3)
  • Migration status for zipper.app/riscv64 (1.5-3 to 1.5-3): Will attempt migration (Any information below is purely informational)
• zomg/riscv64 (0.8.2-1 to 0.8.2-1)
  • Migration status for zomg/riscv64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
• zpspell/riscv64 (0.4.3-5 to 0.4.3-5)
  • Migration status for zpspell/riscv64 (0.4.3-5 to 0.4.3-5): Will attempt migration (Any information below is purely informational)
• zulucrypt/riscv64 (6.2.0-1 to 6.2.0-1)
  • Migration status for zulucrypt/riscv64 (6.2.0-1 to 6.2.0-1): Will attempt migration (Any information below is purely informational)
• zurl/riscv64 (1.12.0-1.1 to 1.12.0-1.1)
  • Migration status for zurl/riscv64 (1.12.0-1.1 to 1.12.0-1.1): Will attempt migration (Any information below is purely informational)
• architecture-properties (0.1.1 to 0.2)
  • Migration status for architecture-properties (0.1.1 to 0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for architecture-properties/0.2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch amd64 binaries uploaded by nthykier
    • Not built on buildd: arch all binaries uploaded by nthykier, a new source-only upload is needed to allow migration
    • missing build on riscv64
    • 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/a/architecture-properties.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cruft-ng (0.9.63 to 0.9.64)
  • Migration status for cruft-ng (0.9.63 to 0.9.64): 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 cruft-ng/0.9.64: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cruft-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• dctrl2xml (- to 0.21)
  • Migration status for dctrl2xml (- to 0.21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ssgelm@gmail.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/d/dctrl2xml.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 ♻
• fastdds (3.0.0+ds-3 to 3.0.1+ds-1)
  • Migration status for fastdds (3.0.0+ds-3 to 3.0.1+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on riscv64
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for fastdds/3.0.1+ds-1: amd64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fastdds.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• fuse3 (3.14.0-7 to 3.14.0-8)
  • Migration status for fuse3 (3.14.0-7 to 3.14.0-8): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on 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:
    • Updating fuse3 will fix bugs in testing: #1081537, #918984
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fuse3.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 ♻
• gcin (- to 2.9.0+dfsg1-3.1)
  • Migration status for gcin (- to 2.9.0+dfsg1-3.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 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/gcin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ghc (9.4.7-5 to 9.6.6-1)
  • Migration status for ghc (9.4.7-5 to 9.6.6-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 s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): ghc haskell-hadrian
  • Additional info:
    • Updating ghc will fix bugs in testing: #1079099
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-connections (47~beta-1 to 47.0-1)
  • Migration status for gnome-connections (47~beta-1 to 47.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • missing build on riscv64
    • 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/g/gnome-connections.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• govee-local-api (- to 1.5.1-1)
  • Migration status for govee-local-api (- to 1.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for govee-local-api/1.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for govee-local-api/n/a: riscv64: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/govee-local-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 ♻
• gthumb (3:3.12.6-1 to 3:3.12.6-2)
  • Migration status for gthumb (3:3.12.6-1 to 3:3.12.6-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on 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:
    • Updating gthumb will fix bugs in testing: #1080998
    • 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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gvfs (1.55.90-1 to 1.56.0-1)
  • Migration status for gvfs (1.55.90-1 to 1.56.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/g/gvfs.html
    • autopkgtest for gvfs/1.56.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for gvfs/n/a: riscv64: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• haskell-hadrian (9.4.7-3 to 9.6.6-1)
  • Migration status for haskell-hadrian (9.4.7-3 to 9.6.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hadrian.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 ♻
• hwdata (0.385-1 to 0.387-1)
  • Migration status for hwdata (0.385-1 to 0.387-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/h/hwdata.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 ♻
• libfishcamp (- to 1.2+20220607003151-3)
  • Migration status for libfishcamp (- to 1.2+20220607003151-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libfishcamp would introduce bugs in testing: #1072730, #1072731
    • missing build on i386
    • arch:i386 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)
• libtangence-perl (0.32-1 to 0.33-1)
  • Migration status for libtangence-perl (0.32-1 to 0.33-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
    • Build-Depends-Indep: libtangence-perl libmeta-perl
    • Depends: libtangence-perl libmeta-perl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtangence-perl.html
    • autopkgtest for libtangence-perl/0.33-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libtangence-perl/n/a: riscv64: Failed (not a regression)
    • 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
• markdown-exec (1.9.2-1 to 1.9.3-1)
  • Migration status for markdown-exec (1.9.2-1 to 1.9.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/markdown-exec.html
    • autopkgtest for markdown-exec/1.9.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for markdown-exec/n/a: riscv64: Failed (not a regression)
    • 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
• meater-python (- to 0.0.8-1)
  • Migration status for meater-python (- to 0.0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by edward@4angle.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/m/meater-python.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 ♻
• mkdocs-autorefs (1.1.0-1 to 1.2.0-1)
  • Migration status for mkdocs-autorefs (1.1.0-1 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mkdocs-autorefs/1.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for mkdocs-autorefs/n/a: 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/m/mkdocs-autorefs.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 ♻
• mkdocstrings-python-legacy (0.2.3-6 to 0.2.4-1)
  • Migration status for mkdocstrings-python-legacy (0.2.3-6 to 0.2.4-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/m/mkdocstrings-python-legacy.html
    • autopkgtest for mkdocstrings-python-legacy/0.2.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for mkdocstrings-python-legacy/n/a: riscv64: Failed (not a regression)
    • 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
• ncmpc (0.49-1 to 0.50-1)
  • Migration status for ncmpc (0.49-1 to 0.50-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
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ncmpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• normaliz (3.10.3+ds-1 to 3.10.3+ds-2)
  • Migration status for normaliz (3.10.3+ds-1 to 3.10.3+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libnormaliz-dev/amd64 has unsatisfiable dependency
    • libnormaliz-dev/arm64 has unsatisfiable dependency
    • libnormaliz-dev/ppc64el has unsatisfiable dependency
    • libnormaliz-dev/s390x has unsatisfiable dependency
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on riscv64
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
    • Depends: normaliz nauty
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/n/normaliz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ocaml-kdf (- to 1.0.0-1)
  • Migration status for ocaml-kdf (- to 1.0.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-kdf.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 ♻
• pass-audit (- to 1.2-1.2)
  • Migration status for pass-audit (- to 1.2-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/p/pass-audit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pg-auto-failover (2.1-2 to 2.1-3)
  • Migration status for pg-auto-failover (2.1-2 to 2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pg-auto-failover unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • pg-auto-failover unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • pg-auto-failover 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 riscv64
    • missing build on s390x
    • Not built on buildd: upload info for arch amd64 binaries not found
    • 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 pg-auto-failover/2.1-3: amd64: Pass, ppc64el: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-auto-failover.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 ♻
• pg-catcheck (1.4.0-1 to 1.4.0-2)
  • Migration status for pg-catcheck (1.4.0-1 to 1.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pg-catcheck unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • pg-catcheck unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • pg-catcheck unsatisfiable Build-Depends(-Arch) on i386: architecture-is-64-bit
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on riscv64
    • missing build on s390x
    • Not built on buildd: upload info for arch amd64 binaries not found
    • 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 pg-catcheck/1.4.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-catcheck.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 ♻
• pg-dirtyread (2.7-1 to 2.7-2)
  • Migration status for pg-dirtyread (2.7-1 to 2.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pg-dirtyread unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • pg-dirtyread unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • pg-dirtyread 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 riscv64
    • missing build on s390x
    • Not built on buildd: upload info for arch amd64 binaries not found
    • 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 pg-dirtyread/2.7-2: amd64: Pass, ppc64el: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-dirtyread.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 ♻
• pg-partman (5.1.0-1 to 5.1.0-2)
  • Migration status for pg-partman (5.1.0-1 to 5.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pg-partman unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • pg-partman unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • pg-partman 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 riscv64
    • missing build on s390x
    • Not built on buildd: upload info for arch amd64 binaries not found
    • 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 pg-partman/5.1.0-2: amd64: Pass, ppc64el: Pass
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): pg-partman pgtap
  • Additional info:
    • Updating pg-partman will fix bugs in testing: #1081581
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-partman.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 ♻
• picom (10.2-3 to 11.2-0.1)
  • Migration status for picom (10.2-3 to 11.2-0.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on i386
    • 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: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/p/picom.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 ♻
• pycec (- to 0.5.2-1)
  • Migration status for pycec (- to 0.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pycec/0.5.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pycec/n/a: riscv64: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycec.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 ♻
• pyisy (- to 3.1.14-1)
  • Migration status for pyisy (- to 3.1.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyisy.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 ♻
• pykodi (- to 0.2.7-1)
  • Migration status for pykodi (- to 0.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
    • Too young, only 0 of 5 days old
    • Depends: pykodi python-jsonrpc-async (not considered)
    • Depends: pykodi python-jsonrpc-websocket (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pykodi.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-cassandra-driver (- to 3.29.2-1)
  • Migration status for python-cassandra-driver (- to 3.29.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-cassandra-driver would introduce bugs in testing: #1076838
    • 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/p/python-cassandra-driver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-executing (2.0.1-0.1 to 2.1.0-0.1)
  • Migration status for python-executing (2.0.1-0.1 to 2.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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-executing.html
    • autopkgtest for python-executing/2.1.0-0.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-executing/n/a: riscv64: Failed (not a regression)
    • 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
• python-jsonrpc-async (- to 2.1.2-1)
  • Migration status for python-jsonrpc-async (- to 2.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-jsonrpc-async/2.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 ♻, s390x: Regression or new test ♻
    • autopkgtest for python-jsonrpc-async/n/a: riscv64: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
    • Too young, only 0 of 5 days old
    • Build-Depends-Indep: python-jsonrpc-async python-jsonrpc-base (not considered)
    • Depends: python-jsonrpc-async python-jsonrpc-base (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jsonrpc-async.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-jsonrpc-base (- to 2.2.0-1)
  • Migration status for python-jsonrpc-base (- to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jsonrpc-base.html
    • autopkgtest for python-jsonrpc-base/2.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-jsonrpc-websocket (- to 3.1.5-1)
  • Migration status for python-jsonrpc-websocket (- to 3.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-jsonrpc-websocket/3.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-jsonrpc-websocket/n/a: riscv64: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
    • Too young, only 0 of 5 days old
    • Build-Depends-Indep: python-jsonrpc-websocket python-jsonrpc-async (not considered)
    • Depends: python-jsonrpc-websocket python-jsonrpc-base (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jsonrpc-websocket.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-nexusformat (- to 1.0.6-1)
  • Migration status for python-nexusformat (- to 1.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-nexusformat/1.0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-nexusformat/n/a: riscv64: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by lolando, a new source-only upload is needed to allow migration
    • Too young, only 0 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nexusformat.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-sanix (- to 1.0.6-1)
  • Migration status for python-sanix (- 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
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sanix.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 ♻
• qt5ct (- to 1.8-2)
  • Migration status for qt5ct (- to 1.8-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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qt5ct.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 ♻
• r-cran-tidygraph (1.3.1-1 to 1.3.1-2)
  • Migration status for r-cran-tidygraph (1.3.1-1 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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tidygraph.html
    • autopkgtest for r-cran-tidygraph/1.3.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for r-cran-tidygraph/n/a: riscv64: Failed (not a regression)
    • 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
• rsshfs (- to 0.0~git20140617205143.9758f70-3)
  • Migration status for rsshfs (- to 0.0~git20140617205143.9758f70-3): 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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsshfs.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-puppetfile-resolver (- to 0.6.3-1)
  • Migration status for ruby-puppetfile-resolver (- to 0.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-puppetfile-resolver/0.6.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ruby-puppetfile-resolver/n/a: riscv64: Regression or new test ♻
    • 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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-puppetfile-resolver.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 ♻
• rust-char-reader (- to 0.1.1-1)
  • Migration status for rust-char-reader (- to 0.1.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 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
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-char-reader.html
    • autopkgtest for rust-char-reader/0.1.1-1: amd64: Pass, arm64: Pass, armel: 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-confy (- to 0.6.1-1)
  • Migration status for rust-confy (- to 0.6.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 amd64 binaries not found
    • Not built on buildd: upload info for arch armel binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-confy.html
    • autopkgtest for rust-confy/0.6.1-1: amd64: Pass, armel: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-custom-error (- to 1.9.2-1)
  • Migration status for rust-custom-error (- to 1.9.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch armel binaries not found
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-custom-error.html
    • autopkgtest for rust-custom-error/1.9.2-1: amd64: Pass, armel: 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-devicemapper-sys (- to 0.3.0-1)
  • Migration status for rust-devicemapper-sys (- to 0.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 amd64 binaries not found
    • Not built on buildd: upload info for arch armel binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-devicemapper-sys.html
    • autopkgtest for rust-devicemapper-sys/0.3.0-1: amd64: Pass, armel: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-notify-rust (- to 4.11.3-1)
  • Migration status for rust-notify-rust (- to 4.11.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-notify-rust/4.11.3-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • autopkgtest for rust-notify-rust/blocked-on-ci-infra: riscv64: Regression or new test ♻
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-notify-rust.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-openpgp-card-rpgp (- to 0.1.2-1)
  • Migration status for rust-openpgp-card-rpgp (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-openpgp-card-rpgp rust-pgp (not considered)
    • Build-Depends(-Arch): rust-openpgp-card-rpgp rust-rsa (not considered)
    • Depends: rust-openpgp-card-rpgp rust-pgp (not considered)
    • Depends: rust-openpgp-card-rpgp rust-rsa (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-openpgp-card-rpgp.html
    • autopkgtest for rust-openpgp-card-rpgp/0.1.2-1: amd64: 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 ♻
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• rust-openpgp-card-state (- to 0.2.1-1)
  • Migration status for rust-openpgp-card-state (- to 0.2.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 amd64 binaries not found
    • Too young, only 0 of 2 days old
    • Build-Depends(-Arch): rust-openpgp-card-state rust-confy (not considered)
    • Build-Depends(-Arch): rust-openpgp-card-state rust-keyring
    • Depends: rust-openpgp-card-state rust-confy (not considered)
    • Depends: rust-openpgp-card-state rust-keyring
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-openpgp-card-state.html
    • autopkgtest for rust-openpgp-card-state/0.2.1-1: 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
• rust-rasciigraph (- to 0.2.0-1)
  • Migration status for rust-rasciigraph (- to 0.2.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rasciigraph.html
    • autopkgtest for rust-rasciigraph/0.2.0-1: amd64: Pass, arm64: 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-rpgpie (- to 0.1.2-1)
  • Migration status for rust-rpgpie (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Too young, only 0 of 2 days old
    • Build-Depends(-Arch): rust-rpgpie rust-openpgp-card-rpgp (not considered)
    • Build-Depends(-Arch): rust-rpgpie rust-openpgp-card-state (not considered)
    • Build-Depends(-Arch): rust-rpgpie rust-pgp (not considered)
    • Depends: rust-rpgpie rust-openpgp-card-rpgp (not considered)
    • Depends: rust-rpgpie rust-openpgp-card-state (not considered)
    • Depends: rust-rpgpie rust-pgp (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rpgpie.html
    • autopkgtest for rust-rpgpie/0.1.2-1: 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
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• rust-rpgpie-sop (- to 0.3.7-1)
  • Migration status for rust-rpgpie-sop (- to 0.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Too young, only 0 of 2 days old
    • Build-Depends(-Arch): rust-rpgpie-sop rust-pgp (not considered)
    • Build-Depends(-Arch): rust-rpgpie-sop rust-rpgpie (not considered)
    • Depends: rust-rpgpie-sop rust-pgp (not considered)
    • Depends: rust-rpgpie-sop rust-rpgpie (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rpgpie-sop.html
    • autopkgtest for rust-rpgpie-sop/0.3.7-1: 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
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• rust-secular (- to 1.0.1-1)
  • Migration status for rust-secular (- to 1.0.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 amd64 binaries not found
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-secular.html
    • autopkgtest for rust-secular/1.0.1-1: amd64: 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-statrs (- to 0.17.1-1)
  • Migration status for rust-statrs (- to 0.17.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 amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-statrs.html
    • autopkgtest for rust-statrs/0.17.1-1: amd64: Pass, arm64: 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
• scaphandre (- to 1.0.0-5)
  • Migration status for scaphandre (- to 1.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • scaphandre has no binaries on any arch
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• scilab (2024.1.0+dfsg-4 to 2024.1.0+dfsg-5)
  • Migration status for scilab (2024.1.0+dfsg-4 to 2024.1.0+dfsg-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scilab.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 scilab/2024.1.0+dfsg-5: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• splix (2.0.0+svn315-7 to 2.0.0+svn315-8)
  • Migration status for splix (2.0.0+svn315-7 to 2.0.0+svn315-8): 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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/splix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• waybar (0.10.4-2 to 0.11.0-1)
  • Migration status for waybar (0.10.4-2 to 0.11.0-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
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/waybar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• webassets (3:2.0-0.1 to 3:2.0-0.2)
  • Migration status for webassets (3:2.0-0.1 to 3:2.0-0.2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webassets.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 ♻
• abyss (2.3.8-1 to 2.3.9-1)
  • Migration status for abyss (2.3.8-1 to 2.3.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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/abyss.html
    • autopkgtest for abyss/2.3.9-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
• asedriveiiie (3.7-10 to 3.7-11)
  • Migration status for asedriveiiie (3.7-10 to 3.7-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/a/asedriveiiie.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• autofs (5.1.9-1.1 to 5.1.9-1.2)
  • Migration status for autofs (5.1.9-1.1 to 5.1.9-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:
    • Updating autofs will fix bugs in testing: #1078408
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autofs.html
    • autopkgtest for autofs/5.1.9-1.2: amd64: Pass, 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 ♻
• autolink (- to 0.10.0-1.1)
  • Migration status for autolink (- to 0.10.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/a/autolink.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• calibre (7.17.0+ds-4 to 7.18.0+ds-1)
  • Migration status for calibre (7.17.0+ds-4 to 7.18.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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calibre.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for calibre/7.18.0+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass
    • Waiting for reproducibility test results 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
• cds-healpix-java (0.30.2+ds-1 to 0.30.3+ds-1)
  • Migration status for cds-healpix-java (0.30.2+ds-1 to 0.30.3+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cds-healpix-java.html
    • autopkgtest for cds-healpix-java/0.30.3+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for cds-healpix-java/n/a: riscv64: Failed (not a regression)
    • Waiting for reproducibility test results 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
• cheese (44.1-1 to 44.1-2)
  • Migration status for cheese (44.1-1 to 44.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating cheese will fix bugs in testing: #1074878, #1081598
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cheese.html
    • autopkgtest for cheese/44.1-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 ♻)
    • 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 ♻
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• cpuinfo (0.0~git20240830.fa1c679-3 to 0.0~git20240830.fa1c679-4)
  • Migration status for cpuinfo (0.0~git20240830.fa1c679-3 to 0.0~git20240830.fa1c679-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/c/cpuinfo.html
    • autopkgtest for cpuinfo/0.0~git20240830.fa1c679-4: amd64: Pass, arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Pass, 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 ♻
• ctdopts (1.5-4 to 1.5-5)
  • Migration status for ctdopts (1.5-4 to 1.5-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/c/ctdopts.html
    • autopkgtest for ctdopts/1.5-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ctdopts/n/a: riscv64: Failed (not a regression)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• curl (8.9.1-2 to 8.10.0-2)
  • Migration status for curl (8.9.1-2 to 8.10.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for afflib/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for balboa/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for cockpit/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for cryfs/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for curl/8.10.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for curl/n/a: riscv64: Failed (not a regression)
    • autopkgtest for cwltool/3.1.20240708091337-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for elinks/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for feh/3.10.2-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for flask-caching/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for fwupd/1.9.24-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for hippotat/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for isc-kea/2.4.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for isc-kea/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for libsoup3/3.6.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for munin/2.0.76-1: amd64: Failed (not a regression), arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • autopkgtest for nodejs/20.17.0+dfsg-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for nova/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for opentracker/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for openvswitch/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for privoxy/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for pycurl/7.45.3-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-bioc-rhtslib/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-curl/5.2.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 ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rspamd/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rsyslog/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-ethon/0.16.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for spamassassin/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for swupdate/2024.05.2+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for weborf/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for xerces-c/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curl.html
    • Waiting for reproducibility test results on armhf - info ♻
• cwltest (2.5.20240714110256-1 to 2.5.20240906231108-1)
  • Migration status for cwltest (2.5.20240714110256-1 to 2.5.20240906231108-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cwltest.html
    • autopkgtest for cwltest/2.5.20240906231108-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
• cwltool (3.1.20240708091337-1 to 3.1.20240909164951-1)
  • Migration status for cwltool (3.1.20240708091337-1 to 3.1.20240909164951-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cwltool.html
    • autopkgtest for cwltool/3.1.20240909164951-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 ♻
    • 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
• dh-rust (0.0.8 to 0.0.10)
  • Migration status for dh-rust (0.0.8 to 0.0.10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-rust.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• egl-wayland (1:1.1.15-1 to 1:1.1.16-1)
  • Migration status for egl-wayland (1:1.1.15-1 to 1:1.1.16-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/egl-wayland.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 ♻
• exult (1.8-2 to 1.10-2)
  • Migration status for exult (1.8-2 to 1.10-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• fastddsgen (4.0.0+dfsg-1 to 4.0.1+dfsg-1)
  • Migration status for fastddsgen (4.0.0+dfsg-1 to 4.0.1+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fastddsgen.html
    • autopkgtest for fastddsgen/4.0.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for fastddsgen/n/a: riscv64: Failed (not a regression)
    • Waiting for reproducibility test results 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
• ft2-clone (1.85+ds-1 to 1.86+ds-1)
  • Migration status for ft2-clone (1.85+ds-1 to 1.86+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gcc-13-doc (13.2.0-1 to 13.3.0-1)
  • Migration status for gcc-13-doc (13.2.0-1 to 13.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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gnome-chess (1:47~beta-1 to 1:47.0-1)
  • Migration status for gnome-chess (1:47~beta-1 to 1:47.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/g/gnome-chess.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 ♻
• gnome-shell-extension-easyscreencast (1.9.0-1 to 1.9.0-2)
  • Migration status for gnome-shell-extension-easyscreencast (1.9.0-1 to 1.9.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/g/gnome-shell-extension-easyscreencast.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 ♻
• gnome-shell-extension-espresso (10-2 to 10-3)
  • Migration status for gnome-shell-extension-espresso (10-2 to 10-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-espresso.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-freon (56+dfsg-2 to 56+dfsg-3)
  • Migration status for gnome-shell-extension-freon (56+dfsg-2 to 56+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-freon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-hard-disk-led (38-2 to 38-3)
  • Migration status for gnome-shell-extension-hard-disk-led (38-2 to 38-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/g/gnome-shell-extension-hard-disk-led.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-impatience (0.5.1-1 to 0.5.1-2)
  • Migration status for gnome-shell-extension-impatience (0.5.1-1 to 0.5.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-impatience.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-no-annoyance (- to 0+20240813-8312e01-1)
  • Migration status for gnome-shell-extension-no-annoyance (- to 0+20240813-8312e01-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-shell-extension-no-annoyance would introduce bugs in testing: #1052105, #1081638
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-no-annoyance.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gnome-shell-extension-runcat (27-2 to 27-3)
  • Migration status for gnome-shell-extension-runcat (27-2 to 27-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/g/gnome-shell-extension-runcat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• golang-defaults (2:1.22~3 to 2:1.23~2)
  • Migration status for golang-defaults (2:1.22~3 to 2:1.23~2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sng/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Depends: golang-defaults golang-1.23
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-defaults.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 ♻
• gramofile (- to 1.6-14)
  • Migration status for gramofile (- to 1.6-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gramofile/1.6-14: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for gramofile/n/a: riscv64: Regression or new test ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gramofile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• graphene (1.10.8-3 to 1.10.8-4)
  • Migration status for graphene (1.10.8-3 to 1.10.8-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/g/graphene.html
    • autopkgtest for graphene/1.10.8-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for graphene/n/a: riscv64: Failed (not a regression)
    • Waiting for reproducibility test results 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
• h3-pg (4.1.3-3 to 4.1.3-4)
  • Migration status for h3-pg (4.1.3-3 to 4.1.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • h3-pg unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • h3-pg unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • h3-pg 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 h3-pg/4.1.3-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for h3-pg/n/a: riscv64: Failed (not a regression)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/h3-pg.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 ♻
• homebank (5.8.1-1 to 5.8.3-1)
  • Migration status for homebank (5.8.1-1 to 5.8.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/h/homebank.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• hypopg (1.4.1-1 to 1.4.1-2)
  • Migration status for hypopg (1.4.1-1 to 1.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • hypopg unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • hypopg unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • hypopg 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 hypopg/1.4.1-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for hypopg/n/a: riscv64: Failed (not a regression)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hypopg.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 ♻
• icingaweb2-module-toplevelview (0.3.4-1 to 0.4.0-1)
  • Migration status for icingaweb2-module-toplevelview (0.3.4-1 to 0.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-toplevelview.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• importlib-resources (6.0.1-1 to 6.4.5-1)
  • Migration status for importlib-resources (6.0.1-1 to 6.4.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for alembic/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for domdf-python-tools/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for hdmf/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for importlib-resources/6.4.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for importlib-resources/n/a: riscv64: Failed (not a regression)
    • autopkgtest for python-limits/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-schema-salad/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for riscemu/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for swagger-spec-validator/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating importlib-resources will fix bugs in testing: #1076534
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/importlib-resources.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 ♻
• intel-compute-runtime (- to 24.35.30872.18-1)
  • Migration status for intel-compute-runtime (- to 24.35.30872.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-compute-runtime would introduce bugs in testing: #1081100
    • autopkgtest for intel-compute-runtime/24.35.30872.18-1: amd64: Regression or new test ♻
    • Too young, only 1 of 5 days old
    • 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
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• ip4r (2.4.2-2 to 2.4.2-3)
  • Migration status for ip4r (2.4.2-2 to 2.4.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ip4r.html
    • autopkgtest for ip4r/2.4.2-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
• ipywidgets (8.1.3-1 to 8.1.5-1)
  • Migration status for ipywidgets (8.1.3-1 to 8.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ipywidgets.html
    • autopkgtest for ipywidgets/8.1.5-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
• jsquery (1.2-1 to 1.2-2)
  • Migration status for jsquery (1.2-1 to 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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsquery.html
    • autopkgtest for jsquery/1.2-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
• jupyter-sphinx-theme (0.0.6+ds1-11 to 0.0.6+ds1-12)
  • Migration status for jupyter-sphinx-theme (0.0.6+ds1-11 to 0.0.6+ds1-12): 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/j/jupyter-sphinx-theme.html
    • autopkgtest for jupyter-sphinx-theme/0.0.6+ds1-12: 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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• kdiff3 (1.11.2-1 to 1.11.4-1)
  • Migration status for kdiff3 (1.11.2-1 to 1.11.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdiff3.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 ♻
• kicad (8.0.4+dfsg-1 to 8.0.5+dfsg-1)
  • Migration status for kicad (8.0.4+dfsg-1 to 8.0.5+dfsg-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 kicad/8.0.5+dfsg-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kicad.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 ♻
• kicad-footprints (8.0.4-1 to 8.0.5-1)
  • Migration status for kicad-footprints (8.0.4-1 to 8.0.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kicad-footprints.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kicad-packages3d (8.0.4-1 to 8.0.5-1)
  • Migration status for kicad-packages3d (8.0.4-1 to 8.0.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kicad-packages3d.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 ♻
• kicad-symbols (8.0.4-1 to 8.0.5-1)
  • Migration status for kicad-symbols (8.0.4-1 to 8.0.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kicad-symbols.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 ♻
• kodi (2:21.1+dfsg-4 to 2:21.1+dfsg-5)
  • Migration status for kodi (2:21.1+dfsg-4 to 2:21.1+dfsg-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/k/kodi.html
    • autopkgtest for kodi/2:21.1+dfsg-5: 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
• kweathercore (- to 24.08.1-1)
  • Migration status for kweathercore (- to 24.08.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/kweathercore.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 ♻
• lem (- to 2022-12-10+dfsg2-1)
  • Migration status for lem (- to 2022-12-10+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by costamagnagianfranco@yahoo.it
    • Too young, only 1 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lem.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 ♻
• libblockdev (3.1.1-2 to 3.2.0-1)
  • Migration status for libblockdev (3.1.1-2 to 3.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libblockdev/3.2.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for libblockdev/n/a: riscv64: Failed (not a regression)
    • Not built on buildd: arch amd64 binaries uploaded by biebl
    • Not built on buildd: arch all binaries uploaded by biebl, a new source-only upload is needed to allow 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/libb/libblockdev.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 ♻
• libbpf (1.4.5-1 to 1.4.6-1)
  • Migration status for libbpf (1.4.5-1 to 1.4.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for openvswitch/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbpf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libdockapp (1:0.7.3-2 to 1:0.7.3-3)
  • Migration status for libdockapp (1:0.7.3-2 to 1:0.7.3-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for libdockapp/1:0.7.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdockapp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libgc (1:8.2.6-2 to 1:8.2.8-1)
  • Migration status for libgc (1:8.2.6-2 to 1:8.2.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libmanette (0.2.7-1 to 0.2.9-1)
  • Migration status for libmanette (0.2.7-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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmanette.html
    • autopkgtest for libmanette/0.2.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libmanette/n/a: riscv64: Failed (not a regression)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libmeta-perl (0.004-2 to 0.008-1)
  • Migration status for libmeta-perl (0.004-2 to 0.008-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/libm/libmeta-perl.html
    • autopkgtest for libmeta-perl/0.008-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libmeta-perl/n/a: riscv64: Failed (not a regression)
    • Waiting for reproducibility test results 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
• libsbig (4.9.9-4 to 4.9.9-6)
  • Migration status for libsbig (4.9.9-4 to 4.9.9-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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• libwww-telegram-botapi-perl (- to 0.12-2)
  • Migration status for libwww-telegram-botapi-perl (- to 0.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libwww-telegram-botapi-perl/0.12-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for libwww-telegram-botapi-perl/n/a: riscv64: Regression or new test ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libw/libwww-telegram-botapi-perl.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 ♻
• lomiri-gallery-app (3.0.2-1 to 3.1.0-2)
  • Migration status for lomiri-gallery-app (3.0.2-1 to 3.1.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Depends: lomiri-gallery-app exiv2
  • Additional info:
    • Updating lomiri-gallery-app will fix bugs in testing: #1076761
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-gallery-app.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 ♻
• lomiri-mediaplayer-app (1.0.4+dfsg-1 to 1.1.0+dfsg-2)
  • Migration status for lomiri-mediaplayer-app (1.0.4+dfsg-1 to 1.1.0+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-mediaplayer-app.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 ♻
• lomiri-music-app (3.0.4-1 to 3.1.1-2)
  • Migration status for lomiri-music-app (3.0.4-1 to 3.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-music-app.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 ♻
• lomiri-session (0.3-2 to 0.3-5)
  • Migration status for lomiri-session (0.3-2 to 0.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/l/lomiri-session.html
    • Too young, only 1 of 5 days old
    • Depends: lomiri-session lomiri-content-hub (not considered)
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lrzsz (- to 0.12.21rc-0.1)
  • Migration status for lrzsz (- to 0.12.21rc-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/lrzsz.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 ♻
• lxqt-archiver (0.9.1-0.1 to 0.9.1-1)
  • Migration status for lxqt-archiver (0.9.1-0.1 to 0.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 1 of 5 days old
  • Additional info:
    • Updating lxqt-archiver will fix bugs in testing: #1078292
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-archiver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxqt-config (1.4.0-1 to 1.4.0-2)
  • Migration status for lxqt-config (1.4.0-1 to 1.4.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating lxqt-config will fix bugs in testing: #1078293
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-config.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mandos (1.8.16-1.2 to 1.8.17-1)
  • Migration status for mandos (1.8.16-1.2 to 1.8.17-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating mandos will fix bugs in testing: #1079588
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mandos.html
    • autopkgtest for mandos/1.8.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
• mawk (1.3.4.20240819-3 to 1.3.4.20240905-1)
  • Migration status for mawk (1.3.4.20240819-3 to 1.3.4.20240905-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for audit/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for mawk/1.3.4.20240905-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for mawk/n/a: riscv64: Failed (not a regression)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mawk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• memcached (1.6.29-1 to 1.6.31-1)
  • Migration status for memcached (1.6.29-1 to 1.6.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for memcached/1.6.31-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-limits/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/memcached.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 ♻
• metkit (1.11.14-1 to 1.11.19+ds-1)
  • Migration status for metkit (1.11.14-1 to 1.11.19+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Depends: metkit eccodes (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/metkit.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 ♻
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• mimeo (1.5.1-17 to 1.5.1-18)
  • Migration status for mimeo (1.5.1-17 to 1.5.1-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mimeo/1.5.1-18: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for mimeo/n/a: riscv64: Failed (not a regression)
    • Not built on buildd: arch all binaries uploaded by myon, 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/m/mimeo.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 ♻
• mistune0 (0.8.4-3 to 0.8.4-4)
  • Migration status for mistune0 (0.8.4-3 to 0.8.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 5 days old
  • Additional info:
    • Updating mistune0 will fix bugs in testing: #1018410
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mistune0.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 ♻
• mmdebstrap (1.5.2-1 to 1.5.3-1)
  • Migration status for mmdebstrap (1.5.2-1 to 1.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dash/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for debusine/0.5.0: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • autopkgtest for dropbear/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for mmdebstrap/1.5.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for mmdebstrap/n/a: riscv64: Failed (not a regression)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mmdebstrap.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 ♻
• music (1.2.1-0.3 to 1.2.1-0.4)
  • Migration status for music (1.2.1-0.3 to 1.2.1-0.4): 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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/music.html
    • Waiting for reproducibility test results on armhf - info ♻
• ndcube (2.2.1-1 to 2.2.2-1)
  • Migration status for ndcube (2.2.1-1 to 2.2.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ndcube.html
    • autopkgtest for ndcube/2.2.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 ♻
    • 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
• nqp (2022.12+dfsg-1 to 2022.12+dfsg-1.1)
  • Migration status for nqp (2022.12+dfsg-1 to 2022.12+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nqp/2022.12+dfsg-1.1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for nqp/n/a: riscv64: Failed (not a regression)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nqp.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 ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• okteta (5:0.26.16-1 to 5:0.26.17-1)
  • Migration status for okteta (5:0.26.16-1 to 5:0.26.17-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/okteta.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• omnidb-plpgsql-debugger (3.0.0.20201026-5 to 3.0.0.20201026-6)
  • Migration status for omnidb-plpgsql-debugger (3.0.0.20201026-5 to 3.0.0.20201026-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • omnidb-plpgsql-debugger unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • omnidb-plpgsql-debugger unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • omnidb-plpgsql-debugger 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 omnidb-plpgsql-debugger/3.0.0.20201026-6: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for omnidb-plpgsql-debugger/n/a: riscv64: Failed (not a regression)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/omnidb-plpgsql-debugger.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 ♻
• onednn (3.5.3-1 to 3.5.3-2)
  • Migration status for onednn (3.5.3-1 to 3.5.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/o/onednn.html
    • autopkgtest for onednn/3.5.3-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for onednn/n/a: riscv64: Failed (not a regression)
    • 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
• onevpl-intel-gpu (23.2.3-1 to 24.3.3-1)
  • Migration status for onevpl-intel-gpu (23.2.3-1 to 24.3.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/o/onevpl-intel-gpu.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 ♻
• open3d (- to 0.18.0+ds-5)
  • Migration status for open3d (- to 0.18.0+ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • open3d unsatisfiable Build-Depends(-Arch) on s390x: libfilament-dev
    • open3d unsatisfiable Build-Depends(-Arch) on s390x: libfilament-tools
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for open3d/0.18.0+ds-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 ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open3d.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
• openwince-jtag (- to 0.5.1-11)
  • Migration status for openwince-jtag (- to 0.5.1-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/o/openwince-jtag.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 ♻
• orafce (4.10.3-1 to 4.12.0-1)
  • Migration status for orafce (4.10.3-1 to 4.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • orafce unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • orafce unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • orafce 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 orafce/4.12.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for orafce/n/a: riscv64: Failed (not a regression)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orafce.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 ♻
• orc (1:0.4.39-3 to 1:0.4.40-1)
  • Migration status for orc (1:0.4.39-3 to 1:0.4.40-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/orc.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 ♻
• osmo-sgsn (- to 1.12.0+dfsg1-4)
  • Migration status for osmo-sgsn (- to 1.12.0+dfsg1-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/o/osmo-sgsn.html
    • autopkgtest for osmo-sgsn/1.12.0+dfsg1-4: 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 ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• pd-lua (0.12.8+ds-1 to 0.12.15+ds-1)
  • Migration status for pd-lua (0.12.8+ds-1 to 0.12.15+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/p/pd-lua.html
    • autopkgtest for pd-lua/0.12.15+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
• pgq (3.5-3 to 3.5-4)
  • Migration status for pgq (3.5-3 to 3.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pgq unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • pgq unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • pgq 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 pgq/3.5-4: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgq.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 ♻
• picotool (1.1.2-3 to 2.0.0-3)
  • Migration status for picotool (1.1.2-3 to 2.0.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): picotool pico-sdk
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picotool.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• plasma-wayland-protocols (1.13.0-1 to 1.14.0-1)
  • Migration status for plasma-wayland-protocols (1.13.0-1 to 1.14.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plasma-wayland-protocols.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• poetry-core (1.9.0-1 to 1.9.0-2)
  • Migration status for poetry-core (1.9.0-1 to 1.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for poetry/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for poetry-core/1.9.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for poetry-core/n/a: riscv64: Failed (not a regression)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating poetry-core will fix bugs in testing: #1081311
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poetry-core.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 ♻
• postgresql-debversion (1.1.2-3 to 1.2.0-1)
  • Migration status for postgresql-debversion (1.1.2-3 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • postgresql-debversion unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • postgresql-debversion unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • postgresql-debversion 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 postgresql-debversion/1.2.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for postgresql-debversion/n/a: riscv64: Failed (not a regression)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postgresql-debversion.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 ♻
• pulseaudio-qt (1.5.0-3 to 1.6.0-1)
  • Migration status for pulseaudio-qt (1.5.0-3 to 1.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pulseaudio-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 ♻
• purify (- to 4.1.0-1)
  • Migration status for purify (- 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 5 days old
    • Build-Depends(-Arch): purify sopt (not considered)
    • Depends: purify sopt (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/purify.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 ♻
• pyasn (1.6.1-4 to 1.6.1-5)
  • Migration status for pyasn (1.6.1-4 to 1.6.1-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyasn.html
    • autopkgtest for pyasn/1.6.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pyasn/n/a: riscv64: Failed (not a regression)
    • 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
• pydantic (2.8.2-1 to 2.9.1-2)
  • Migration status for pydantic (2.8.2-1 to 2.9.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for debusine/0.5.0: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Failed (not a regression)
    • autopkgtest for pydantic/2.9.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pydantic/n/a: riscv64: Failed (not a regression)
    • autopkgtest for python-maison/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): pydantic pydantic-core
    • Depends: pydantic pydantic-core
    • Implicit dependency: pydantic pydantic-settings
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydantic.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 ♻
• pydantic-core (2.20.1-1 to 2.23.3-1)
  • Migration status for pydantic-core (2.20.1-1 to 2.23.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/pydantic-core.html
    • autopkgtest for pydantic-core/2.23.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pydantic-settings (2.4.0-2 to 2.5.2-1)
  • Migration status for pydantic-settings (2.4.0-2 to 2.5.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): pydantic-settings pydantic (not considered)
    • Depends: pydantic-settings pydantic (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydantic-settings.html
    • autopkgtest for pydantic-settings/2.5.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pyregion (2.2.0-3 to 2.2.0-4)
  • Migration status for pyregion (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 2 days old
  • Additional info:
    • Updating pyregion will fix bugs in testing: #1075410
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyregion.html
    • autopkgtest for pyregion/2.2.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pyregion/n/a: riscv64: Failed (not a regression)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-cmake-build-extension (0.6.0-2 to 0.6.1-1)
  • Migration status for python-cmake-build-extension (0.6.0-2 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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cmake-build-extension.html
    • autopkgtest for python-cmake-build-extension/0.6.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-cmake-build-extension/n/a: riscv64: Failed (not a regression)
    • Waiting for reproducibility test results 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
• python-csa (- to 0.1.12-1.3)
  • Migration status for python-csa (- to 0.1.12-1.3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-csa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-hdf5storage (0.1.19-1 to 0.1.19-2)
  • Migration status for python-hdf5storage (0.1.19-1 to 0.1.19-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-hdf5storage/0.1.19-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-hdf5storage/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-hdf5storage.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 ♻
• python-skbio (0.6.1-3 to 0.6.2-2)
  • Migration status for python-skbio (0.6.1-3 to 0.6.2-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for python-skbio/0.6.2-2: amd64: Pass, arm64: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating python-skbio will fix bugs in testing: #1081601
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-skbio.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 ♻
• python-xarray (2024.07.0-2 to 2024.09.0-1)
  • Migration status for python-xarray (2024.07.0-2 to 2024.09.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/python-xarray.html
    • autopkgtest for python-xarray/2024.09.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for python-xarray/n/a: riscv64: Failed (not a regression)
    • 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 ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• python3-proselint (0.13.0-1 to 0.14.0-1)
  • Migration status for python3-proselint (0.13.0-1 to 0.14.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3-proselint.html
    • autopkgtest for python3-proselint/0.14.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• qtkeychain (0.14.3-1 to 0.14.3-2)
  • Migration status for qtkeychain (0.14.3-1 to 0.14.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtkeychain.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 ♻
• qwertone (- to 0.4.0-2)
  • Migration status for qwertone (- 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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qwertone.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 ♻
• r-cran-deriv (4.1.3-2 to 4.1.6-1)
  • Migration status for r-cran-deriv (4.1.3-2 to 4.1.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-deriv.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 ♻
• r-cran-rcpparmadillo (14.0.0-1-1 to 14.0.2-1-1)
  • Migration status for r-cran-rcpparmadillo (14.0.0-1-1 to 14.0.2-1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-bayesm/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-collapse/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-rlinsolve/n/a: riscv64: 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/r-cran-rcpparmadillo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rakudo (2022.12-1 to 2022.12-1.1)
  • Migration status for rakudo (2022.12-1 to 2022.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/rakudo.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 ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• restic (0.17.0-1 to 0.17.1-1)
  • Migration status for restic (0.17.0-1 to 0.17.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
    • Too young, only 1 of 5 days old
    • Built-Using: restic golang-1.23
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/restic.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 ♻
• routes (2.5.1-4 to 2.5.1-5)
  • Migration status for routes (2.5.1-4 to 2.5.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for heat/1:22.0.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for nova/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for routes/2.5.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for routes/n/a: riscv64: Failed (not a regression)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/routes.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 ♻
• rows (0.4.2~0-2.1 to 0.4.2~0-2.2)
  • Migration status for rows (0.4.2~0-2.1 to 0.4.2~0-2.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rows.html
    • autopkgtest for rows/0.4.2~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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-deluxe (0.5.0-1 to 0.5.0-2)
  • Migration status for rust-deluxe (0.5.0-1 to 0.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-deluxe/0.5.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-deluxe/blocked-on-ci-infra: riscv64: 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/rust-deluxe.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-eza (0.19.1-1 to 0.19.3-1)
  • Migration status for rust-eza (0.19.1-1 to 0.19.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
    • Build-Depends(-Arch): rust-eza rust-nu-ansi-term (not considered)
    • Build-Depends(-Arch): rust-eza rust-uzers
    • Depends: rust-eza rust-nu-ansi-term (not considered)
    • Depends: rust-eza rust-uzers
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-eza.html
    • autopkgtest for rust-eza/0.19.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-eza/blocked-on-ci-infra: riscv64: Failed (not a regression)
    • 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-futures (0.3.30-1 to 0.3.30-2)
  • Migration status for rust-futures (0.3.30-1 to 0.3.30-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-futures/0.3.30-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-futures/blocked-on-ci-infra: riscv64: Failed (not a regression)
    • autopkgtest for rust-sequoia-keystore-gpg-agent/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-sequoia-keystore-softkeys/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Depends: rust-futures rust-futures-io (not considered)
    • Depends: rust-futures rust-futures-util
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-futures.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-futures-io (0.3.30-1 to 0.3.30-2)
  • Migration status for rust-futures-io (0.3.30-1 to 0.3.30-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-calloop/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-futures-io/0.3.30-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-futures-io/blocked-on-ci-infra: riscv64: Failed (not a regression)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-futures-io.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-futures-util (0.3.30-1 to 0.3.30-2)
  • Migration status for rust-futures-util (0.3.30-1 to 0.3.30-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-futures-util.html
    • autopkgtest for rust-futures-util/0.3.30-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-futures-util/blocked-on-ci-infra: riscv64: Failed (not a regression)
    • 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
• rust-impl-trait-for-tuples (0.2.2-1 to 0.2.2-2)
  • Migration status for rust-impl-trait-for-tuples (0.2.2-1 to 0.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-impl-trait-for-tuples/0.2.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-impl-trait-for-tuples/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating rust-impl-trait-for-tuples will fix bugs in testing: #1077865
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-impl-trait-for-tuples.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-mockall-derive (0.12.1-1 to 0.12.1-2)
  • Migration status for rust-mockall-derive (0.12.1-1 to 0.12.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-mockall-derive/0.12.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-mockall-derive/blocked-on-ci-infra: riscv64: 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/rust-mockall-derive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-nu-ansi-term (0.50.0-1 to 0.50.1-1)
  • Migration status for rust-nu-ansi-term (0.50.0-1 to 0.50.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-nu-ansi-term/0.50.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-nu-ansi-term/blocked-on-ci-infra: riscv64: Failed (not a regression)
    • autopkgtest for rust-tracing-subscriber/blocked-on-ci-infra: riscv64: 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/rust-nu-ansi-term.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-rhai (1.18.0-2 to 1.19.0-1)
  • Migration status for rust-rhai (1.18.0-2 to 1.19.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-handlebars/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-rhai/1.19.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-rhai/blocked-on-ci-infra: riscv64: 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/rust-rhai.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-rusty-paseto (0.7.1-2 to 0.7.1-3)
  • Migration status for rust-rusty-paseto (0.7.1-2 to 0.7.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-rusty-paseto/0.7.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-rusty-paseto/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Depends: rust-rusty-paseto rust-curve25519-dalek (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rusty-paseto.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-soketto (- to 0.8.0-2)
  • Migration status for rust-soketto (- to 0.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-soketto/0.8.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-soketto/blocked-on-ci-infra: riscv64: Regression or new test ♻
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-soketto rust-futures (not considered)
    • Depends: rust-soketto rust-futures (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-soketto.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-svgtypes (0.5.0-2 to 0.15.1-2)
  • Migration status for rust-svgtypes (0.5.0-2 to 0.15.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-svgtypes.html
    • autopkgtest for rust-svgtypes/0.15.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for rust-svgtypes/blocked-on-ci-infra: riscv64: Failed (not a regression)
    • 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
• siril (1.2.1-1 to 1.2.4-1)
  • Migration status for siril (1.2.1-1 to 1.2.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Depends: siril exiv2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/siril.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 ♻
• skopeo (1.13.3+ds1-2 to 1.16.1+ds1-1)
  • Migration status for skopeo (1.13.3+ds1-2 to 1.16.1+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: skopeo golang-1.22
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/skopeo.html
    • autopkgtest for skopeo/1.16.1+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for skopeo/n/a: riscv64: Failed (not a regression)
    • 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
• snapper (0.10.6-1.1 to 0.10.6-1.2)
  • Migration status for snapper (0.10.6-1.1 to 0.10.6-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for freedombox/24.18: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating snapper will fix bugs in testing: #1073699
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snapper.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 ♻
• spirv-llvm-translator-17 (17.0.1-1 to 17.0.4-1)
  • Migration status for spirv-llvm-translator-17 (17.0.1-1 to 17.0.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spirv-llvm-translator-17.html
    • autopkgtest for spirv-llvm-translator-17/17.0.4-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for spirv-llvm-translator-17/n/a: riscv64: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• testrepository (0.0.20-8 to 0.0.21-3)
  • Migration status for testrepository (0.0.20-8 to 0.0.21-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/t/testrepository.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 ♻
• vim-link-vim (1.0.3+git20240716-1 to 1.0.3+git20240911-1)
  • Migration status for vim-link-vim (1.0.3+git20240716-1 to 1.0.3+git20240911-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/v/vim-link-vim.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• whipper (0.10.0-4 to 0.10.0-5)
  • Migration status for whipper (0.10.0-4 to 0.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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whipper.html
    • autopkgtest for whipper/0.10.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
• xterm (393-1 to 394-1)
  • Migration status for xterm (393-1 to 394-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xterm.html
    • autopkgtest for xterm/394-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for xterm/n/a: riscv64: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• yubihsm-connector (3.0.4-3 to 3.0.5-1)
  • Migration status for yubihsm-connector (3.0.4-3 to 3.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for yubihsm-connector/3.0.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for yubihsm-connector/n/a: riscv64: Regression or new test ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yubihsm-connector.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 ♻
• apache-opennlp (2.3.3-1 to 2.4.0-1)
  • Migration status for apache-opennlp (2.3.3-1 to 2.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apache-opennlp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ausweisapp2 (2.2.0-2 to 2.2.1-1)
  • Migration status for ausweisapp2 (2.2.0-2 to 2.2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ausweisapp2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• bgw-replstatus (1.0.7-2 to 1.0.7-3)
  • Migration status for bgw-replstatus (1.0.7-2 to 1.0.7-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bgw-replstatus.html
    • autopkgtest for bgw-replstatus/1.0.7-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
    • 2 days old (needed 2 days)
• binutils (2.43.1-3 to 2.43.1-4)
  • Migration status for binutils (2.43.1-3 to 2.43.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for binutils/2.43.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for binutils/blocked-on-ci-infra: riscv64: Failed (not a regression)
    • autopkgtest for chkrootkit/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cecil (0.9.5+dfsg-6 to 0.9.6+dfsg-1)
  • Migration status for cecil (0.9.5+dfsg-6 to 0.9.6+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cecil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• check-smart-attributes (- to 1.6-156-g498eafa-2)
  • Migration status for check-smart-attributes (- to 1.6-156-g498eafa-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/check-smart-attributes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• checkinstall (- to 1.6.2+git20170426.d24a630-5)
  • Migration status for checkinstall (- to 1.6.2+git20170426.d24a630-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/c/checkinstall.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• codfis (0.4.7-2 to 0.4.7-3)
  • Migration status for codfis (0.4.7-2 to 0.4.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/c/codfis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cppad (2024.00.00.5-1 to 2024.00.00.7-1)
  • Migration status for cppad (2024.00.00.5-1 to 2024.00.00.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/c/cppad.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• credcheck (2.8-1 to 2.8-2)
  • Migration status for credcheck (2.8-1 to 2.8-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/credcheck.html
    • autopkgtest for credcheck/2.8-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
    • 2 days old (needed 2 days)
• cwl-utils (0.33-1 to 0.34-1)
  • Migration status for cwl-utils (0.33-1 to 0.34-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cwl-utils.html
    • autopkgtest for cwl-utils/0.34-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)
• dh-make-elpa (0.19.4 to 0.19.5)
  • Migration status for dh-make-elpa (0.19.4 to 0.19.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-make-elpa.html
    • autopkgtest for dh-make-elpa/0.19.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• elementpath (4.4.0-1 to 4.5.0-1)
  • Migration status for elementpath (4.4.0-1 to 4.5.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elementpath.html
    • autopkgtest for elementpath/4.5.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)
• emacs-buttercup (1.35-3 to 1.36-1)
  • Migration status for emacs-buttercup (1.35-3 to 1.36-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/emacs-buttercup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• extra-window-functions (1.0-5 to 1.0-6)
  • Migration status for extra-window-functions (1.0-5 to 1.0-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/extra-window-functions.html
    • autopkgtest for extra-window-functions/1.0-6: 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)
• ezurio-qcacld-2.0-dkms (0.0~git20240408.aa96a9f+dfsg-1 to 0.0~git20240408.aa96a9f+dfsg-2)
  • Migration status for ezurio-qcacld-2.0-dkms (0.0~git20240408.aa96a9f+dfsg-1 to 0.0~git20240408.aa96a9f+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ezurio-qcacld-2.0-dkms.html
    • autopkgtest for ezurio-qcacld-2.0-dkms/0.0~git20240408.aa96a9f+dfsg-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
• fife (0.4.2-7 to 0.4.2-8)
  • Migration status for fife (0.4.2-7 to 0.4.2-8): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fife.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• first-last-agg (0.1.4-4-gd63ea3b-7 to 0.1.4-4-gd63ea3b-8)
  • Migration status for first-last-agg (0.1.4-4-gd63ea3b-7 to 0.1.4-4-gd63ea3b-8): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/first-last-agg.html
    • autopkgtest for first-last-agg/0.1.4-4-gd63ea3b-8: 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)
• freecontact (1.0.21-13.1 to 1.0.21-14)
  • Migration status for freecontact (1.0.21-13.1 to 1.0.21-14): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freecontact.html
    • autopkgtest for freecontact/1.0.21-14: 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)
• gimp-gap (- to 2.6.0+dfsg-9)
  • Migration status for gimp-gap (- to 2.6.0+dfsg-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/g/gimp-gap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• golang-1.23 (- to 1.23.1-3)
  • Migration status for golang-1.23 (- to 1.23.1-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.1-3: 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)
• golang-github-golang-jwt-jwt (5.0.0+really4.5.0-1 to 5.0.0+really4.5.0-2)
  • Migration status for golang-github-golang-jwt-jwt (5.0.0+really4.5.0-1 to 5.0.0+really4.5.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-golang-jwt-jwt golang-1.22
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-golang-jwt-jwt.html
    • autopkgtest for golang-github-golang-jwt-jwt/5.0.0+really4.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 ♻
    • 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)
• gtk4-layer-shell (1.0.2-4 to 1.0.3-1)
  • Migration status for gtk4-layer-shell (1.0.2-4 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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk4-layer-shell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• heat (1:22.0.0-3 to 1:22.0.0-4)
  • Migration status for heat (1:22.0.0-3 to 1:22.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 2 of 5 days old
  • Additional info:
    • Updating heat will fix bugs in testing: #1081443
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/heat.html
    • autopkgtest for heat/1:22.0.0-4: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• hovercraft (2.7-6 to 2.7-7)
  • Migration status for hovercraft (2.7-6 to 2.7-7): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating hovercraft will fix bugs in testing: #1080275
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hovercraft.html
    • autopkgtest for hovercraft/2.7-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)
• icmake (12.02.00-1 to 12.02.01-1)
  • Migration status for icmake (12.02.00-1 to 12.02.01-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icmake.html
    • autopkgtest for icmake/12.02.01-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)
• indi-pentax (- to 1.0+20221221102411-2)
  • Migration status for indi-pentax (- to 1.0+20221221102411-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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• kbuild (1:0.1.9998svn3606+dfsg-2 to 1:0.1.9998svn3608+dfsg-1)
  • Migration status for kbuild (1:0.1.9998svn3606+dfsg-2 to 1:0.1.9998svn3608+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/k/kbuild.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• libnop (0.0~git20200728.45dfe0f-4 to 0.0~git20200728.45dfe0f-5)
  • Migration status for libnop (0.0~git20200728.45dfe0f-4 to 0.0~git20200728.45dfe0f-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating libnop will fix bugs in testing: #1079562
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• licenserecon (1.18 to 1.19)
  • Migration status for licenserecon (1.18 to 1.19): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/licenserecon.html
    • autopkgtest for licenserecon/1.19: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: 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)
• lomiri-docviewer-app (3.0.4+dfsg-3 to 3.1.0+dfsg-1)
  • Migration status for lomiri-docviewer-app (3.0.4+dfsg-3 to 3.1.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-docviewer-app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxqt-globalkeys (1.4.0-1 to 1.4.0-2)
  • Migration status for lxqt-globalkeys (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 2 of 5 days old
  • Additional info:
    • Updating lxqt-globalkeys will fix bugs in testing: #1078294
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-globalkeys.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxqt-sudo (1.4.0-1 to 1.4.0-2)
  • Migration status for lxqt-sudo (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 2 of 5 days old
  • Additional info:
    • Updating lxqt-sudo will fix bugs in testing: #1078303
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-sudo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• 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 ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meep-mpi-default.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• meshtastic (2.4.0-1 to 2.4.1-1)
  • Migration status for meshtastic (2.4.0-1 to 2.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/m/meshtastic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• morfessor (2.0.6-3 to 2.0.6-4)
  • Migration status for morfessor (2.0.6-3 to 2.0.6-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating morfessor will fix bugs in testing: #1080276
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/morfessor.html
    • autopkgtest for morfessor/2.0.6-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)
• mpi4py (3.1.6-9 to 4.0.0-3)
  • Migration status for mpi4py (3.1.6-9 to 4.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-10: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mpi4py/4.0.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for mpi4py/n/a: riscv64: Failed (not a regression)
    • autopkgtest for netgen/6.2.2401+dfsg1-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pyzoltan/1.0.1-9: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: 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 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 s390x binaries not found
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpi4py.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
• ne (3.3.2-1 to 3.3.3-1)
  • Migration status for ne (3.3.2-1 to 3.3.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/n/ne.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• osc (1.9.1-1 to 1.9.1-2)
  • Migration status for osc (1.9.1-1 to 1.9.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:
    • Updating osc will fix bugs in testing: #1081339
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/osc.html
    • autopkgtest for osc/1.9.1-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 ♻, 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 ♻
• pam-python (1.1.0~git20220701.1d4e111-0.6 to 1.1.0~git20220701.1d4e111-2)
  • Migration status for pam-python (1.1.0~git20220701.1d4e111-0.6 to 1.1.0~git20220701.1d4e111-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating pam-python will fix bugs in testing: #1076955
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pam-python.html
    • autopkgtest for pam-python/1.1.0~git20220701.1d4e111-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
    • Required age is not allowed to drop below 2 days
    • 2 days old (needed 2 days)
• pcmanfm-qt (1.4.0-2 to 1.4.0-3)
  • Migration status for pcmanfm-qt (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 2 of 5 days old
  • Additional info:
    • Updating pcmanfm-qt will fix bugs in testing: #1078306
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcmanfm-qt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pgrouting (3.6.2-1 to 3.6.2-2)
  • Migration status for pgrouting (3.6.2-1 to 3.6.2-2): Will attempt migration (Any information below is purely informational)
    • Depends: pgrouting postgis
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgrouting.html
    • autopkgtest for pgrouting/3.6.2-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
    • 2 days old (needed 2 days)
• pgsql-ogr-fdw (1.1.5-1 to 1.1.5-2)
  • Migration status for pgsql-ogr-fdw (1.1.5-1 to 1.1.5-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgsql-ogr-fdw.html
    • autopkgtest for pgsql-ogr-fdw/1.1.5-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
    • 2 days old (needed 2 days)
• pgtap (1.3.3-1 to 1.3.3-3)
  • Migration status for pgtap (1.3.3-1 to 1.3.3-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/pgtap.html
    • autopkgtest for pgtap/1.3.3-3: 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• php-nyholm-psr7 (1.8.1-3 to 1.8.2-1)
  • Migration status for php-nyholm-psr7 (1.8.1-3 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-nyholm-psr7.html
    • autopkgtest for php-nyholm-psr7/1.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
    • 2 days old (needed 2 days)
• php-symfony-polyfill (1.30.0-1 to 1.31.0-1)
  • Migration status for php-symfony-polyfill (1.30.0-1 to 1.31.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-symfony-polyfill.html
    • autopkgtest for php-symfony-polyfill/1.31.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)
• pico-sdk (1.5.1-4 to 2.0.0-2)
  • Migration status for pico-sdk (1.5.1-4 to 2.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: pico-sdk picotool (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pico-sdk.html
    • autopkgtest for pico-sdk/2.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)
• picolibc (1.8.6-2 to 1.8.7-1)
  • Migration status for picolibc (1.8.6-2 to 1.8.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:
    • Updating picolibc will fix bugs in testing: #1077452
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picolibc.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • autopkgtest for picolibc/1.8.7-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: Pass, ppc64el: Pass, 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 ♻
    • Reproducible on i386 - info ♻
• platformdirs (4.2.2-1 to 4.3.2-1)
  • Migration status for platformdirs (4.2.2-1 to 4.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for platformdirs/4.3.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for poetry/1.8.3+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for vorta/0.9.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for xraydb/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/platformdirs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• podiff (- to 1.4-3)
  • Migration status for podiff (- to 1.4-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/podiff.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• postgis (3.4.3+dfsg-1 to 3.4.3+dfsg-2)
  • Migration status for postgis (3.4.3+dfsg-1 to 3.4.3+dfsg-2): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: postgis pgrouting
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postgis.html
    • autopkgtest for postgis/3.4.3+dfsg-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
    • 2 days old (needed 2 days)
• powerman (2.3.27-5 to 2.4.3-1)
  • Migration status for powerman (2.3.27-5 to 2.4.3-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
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/powerman.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• prometheus-xmpp-alerts (0.5.3-1.2 to 0.5.3-1.3)
  • Migration status for prometheus-xmpp-alerts (0.5.3-1.2 to 0.5.3-1.3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating prometheus-xmpp-alerts will fix bugs in testing: #1079750
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-xmpp-alerts.html
    • autopkgtest for prometheus-xmpp-alerts/0.5.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• prosody-modules (0.0~hg20240530.1927d4d27a26+dfsg-1 to 0.0~hg20240911.c61a82f80e57+dfsg-1)
  • Migration status for prosody-modules (0.0~hg20240530.1927d4d27a26+dfsg-1 to 0.0~hg20240911.c61a82f80e57+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/p/prosody-modules.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• psycopg2 (2.9.9-1 to 2.9.9-2)
  • Migration status for psycopg2 (2.9.9-1 to 2.9.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for heat/1:22.0.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for psycopg2/2.9.9-2: 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/psycopg2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pycdio (2.1.1-1.1 to 2.1.1-1.2)
  • Migration status for pycdio (2.1.1-1.1 to 2.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/p/pycdio.html
    • Waiting for reproducibility test results on armhf - info ♻
• pysuez (- to 0.2.0-2)
  • Migration status for pysuez (- 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/p/pysuez.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pytest-freezer (- to 0.4.8-2)
  • Migration status for pytest-freezer (- to 0.4.8-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-freezer.html
    • autopkgtest for pytest-freezer/0.4.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-apptools (5.2.1-2 to 5.3.0-2)
  • Migration status for python-apptools (5.2.1-2 to 5.3.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 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-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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-bluecurrent-api (- to 1.2.3-1)
  • Migration status for python-bluecurrent-api (- to 1.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bluecurrent-api.html
    • autopkgtest for python-bluecurrent-api/1.2.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-cads-api-client (- to 1.3.1-1)
  • Migration status for python-cads-api-client (- to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by gspreemann@gmail.com, a new source-only upload is needed to allow migration
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): python-cads-api-client python-multiurl (not considered)
    • Depends: python-cads-api-client python-multiurl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cads-api-client.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-cymruwhois (1.6-4 to 1.6-4.1)
  • Migration status for python-cymruwhois (1.6-4 to 1.6-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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cymruwhois.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-django-otp (1.5.0-1 to 1.5.4-1)
  • Migration status for python-django-otp (1.5.0-1 to 1.5.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-otp.html
    • autopkgtest for python-django-otp/1.5.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
• python-django-pgtrigger (4.11.1-1 to 4.12.1-1)
  • Migration status for python-django-pgtrigger (4.11.1-1 to 4.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-django-pgtrigger/4.12.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: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-pgtrigger.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-django-zeal (1.3.0-1 to 1.4.0-1)
  • Migration status for python-django-zeal (1.3.0-1 to 1.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-zeal.html
    • autopkgtest for python-django-zeal/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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-freecontact (1.1-6 to 1.1-7)
  • Migration status for python-freecontact (1.1-6 to 1.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-freecontact would introduce bugs in testing: #1081639
    • 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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-freecontact.html
    • Waiting for reproducibility test results on armhf - info ♻
• python-googlemaps (- to 4.10.0-1)
  • Migration status for python-googlemaps (- to 4.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-googlemaps.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-hole (- to 0.8.0-2)
  • Migration status for python-hole (- to 0.8.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-hole.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-jq (1.7.0+dfsg-2 to 1.8.0+dfsg-1)
  • Migration status for python-jq (1.7.0+dfsg-2 to 1.8.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 2 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jq.html
    • autopkgtest for python-jq/1.8.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-memray (1.13.4+dfsg-4 to 1.14.0+dfsg-1)
  • Migration status for python-memray (1.13.4+dfsg-4 to 1.14.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-memray.html
    • autopkgtest for python-memray/1.14.0+dfsg-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 armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-nuheat (- to 1.0.1-2)
  • Migration status for python-nuheat (- to 1.0.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nuheat.html
    • autopkgtest for python-nuheat/1.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 ♻
    • 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-oldmemo (1.0.3-2 to 1.0.3-3)
  • Migration status for python-oldmemo (1.0.3-2 to 1.0.3-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-oldmemo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-omemo (1.0.4-1 to 1.0.4-2)
  • Migration status for python-omemo (1.0.4-1 to 1.0.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-omemo.html
    • autopkgtest for python-omemo/1.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 ♻
    • 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-pkginfo (1.10.0-1 to 1.11.1-1)
  • Migration status for python-pkginfo (1.10.0-1 to 1.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating python3-pkginfo/1.11.1-1/amd64 to testing makes twine/5.1.1-1/amd64 uninstallable
    • migrating python3-pkginfo/1.11.1-1/arm64 to testing makes twine/5.1.1-1/arm64 uninstallable
    • autopkgtest for poetry/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-pkginfo/1.11.1-1: 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-pkginfo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-proton-vpn-killswitch (- to 0.4.0-2)
  • Migration status for python-proton-vpn-killswitch (- to 0.4.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-proton-vpn-killswitch.html
    • autopkgtest for python-proton-vpn-killswitch/0.4.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)
• python-proton-vpn-logger (- to 0.2.1-2)
  • Migration status for python-proton-vpn-logger (- to 0.2.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-proton-vpn-logger.html
    • autopkgtest for python-proton-vpn-logger/0.2.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)
• python-pyproj (3.6.1-4 to 3.6.1-5)
  • Migration status for python-pyproj (3.6.1-4 to 3.6.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/p/python-pyproj.html
    • autopkgtest for python-pyproj/3.6.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-romy (- to 0.0.10-2)
  • Migration status for python-romy (- to 0.0.10-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-romy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-rxv (- to 0.7.0-1)
  • Migration status for python-rxv (- to 0.7.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-rxv.html
    • autopkgtest for python-rxv/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 ♻
    • 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-samsungctl (- to 0.7.1-1)
  • Migration status for python-samsungctl (- to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-samsungctl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-sfml (2.3.2.dev1+dfsg-1 to 2.3.2.dev1+dfsg-2)
  • Migration status for python-sfml (2.3.2.dev1+dfsg-1 to 2.3.2.dev1+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sfml.html
    • autopkgtest for python-sfml/2.3.2.dev1+dfsg-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
• python-technove (- to 1.3.1-2)
  • Migration status for python-technove (- to 1.3.1-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-technove.html
    • autopkgtest for python-technove/1.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• python-time-machine (2.13.0-2 to 2.14.1-1)
  • Migration status for python-time-machine (2.13.0-2 to 2.14.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-time-machine.html
    • autopkgtest for python-time-machine/2.14.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-tksheet (7.2.12-2 to 7.2.15-1)
  • Migration status for python-tksheet (7.2.12-2 to 7.2.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tsu.yubo@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-tksheet.html
    • autopkgtest for python-tksheet/7.2.15-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-traits (6.4.3-1 to 6.4.3-2)
  • Migration status for python-traits (6.4.3-1 to 6.4.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-traits.html
    • autopkgtest for python-traits/6.4.3-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
• python-ttn-client (- to 1.2.1-2)
  • Migration status for python-ttn-client (- to 1.2.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ttn-client.html
    • Waiting for reproducibility test results on armhf - info ♻
• python-wrapt (1.15.0-2 to 1.15.0-3)
  • Migration status for python-wrapt (1.15.0-2 to 1.15.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-can/4.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for python-wrapt/1.15.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for smart-open/7.0.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for vcr.py/6.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-wrapt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-zeroconf (0.133.0-1 to 0.134.0-1)
  • Migration status for python-zeroconf (0.133.0-1 to 0.134.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-zeroconf.html
    • autopkgtest for python-zeroconf/0.134.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)
• pytkdocs (0.16.1-7 to 0.16.2-1)
  • Migration status for pytkdocs (0.16.1-7 to 0.16.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytkdocs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• qasync (0.27.1-2 to 0.27.1-3)
  • Migration status for qasync (0.27.1-2 to 0.27.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 7 days old
    • Build-Depends(-Arch): qasync pyside6 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qasync.html
    • autopkgtest for qasync/0.27.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• qlogo (0.92+git.1.29a5ca2-2 to 0.961-1)
  • Migration status for qlogo (0.92+git.1.29a5ca2-2 to 0.961-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/q/qlogo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-cli (3.6.2-1 to 3.6.3-1)
  • Migration status for r-cran-cli (3.6.2-1 to 3.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-cli/3.6.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • autopkgtest for r-cran-clock/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-conflicted/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-dtplyr/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-ggforce/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-purrr/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-sessioninfo/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-tidygraph/1.3.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, s390x: Pass
    • autopkgtest for r-cran-tidyselect/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-cli.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 ♻
• regenmaschine (- to 2024.3.0-2)
  • Migration status for regenmaschine (- to 2024.3.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/regenmaschine.html
    • autopkgtest for regenmaschine/2024.3.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)
• rman (- to 3.2-10)
  • Migration status for rman (- to 3.2-10): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rman.html
    • autopkgtest for rman/3.2-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 ♻
    • 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)
• rpi-bad-power (- to 0.1.0-2)
  • Migration status for rpi-bad-power (- to 0.1.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rpi-bad-power.html
    • autopkgtest for rpi-bad-power/0.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-calloop (0.12.4-2 to 0.12.4-3)
  • Migration status for rust-calloop (0.12.4-2 to 0.12.4-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-calloop.html
    • autopkgtest for rust-calloop/0.12.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-imap-codec (1.0.0-7 to 2.0.0~alpha5+20240908-6)
  • Migration status for rust-imap-codec (1.0.0-7 to 2.0.0~alpha5+20240908-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-imap-codec/2.0.0~alpha5+20240908-6: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), 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/r/rust-imap-codec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-keyring (- to 3.2.1-1)
  • Migration status for rust-keyring (- to 3.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 2 of 5 days old
    • 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
    • autopkgtest for rust-keyring/3.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-lazycell (1.3.0-3 to 1.3.0-4)
  • Migration status for rust-lazycell (1.3.0-3 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-lazycell.html
    • autopkgtest for rust-lazycell/1.3.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 ♻
    • 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-libyml (- to 0.0.5-1)
  • Migration status for rust-libyml (- to 0.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-libyml/0.0.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 ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libyml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-num-complex (0.4.0-2 to 0.4.6-2)
  • Migration status for rust-num-complex (0.4.0-2 to 0.4.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-num-complex/0.4.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-uom/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating rust-num-complex will fix bugs in testing: #1081452
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-num-complex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-serde (1.0.203-1 to 1.0.210-2)
  • Migration status for rust-serde (1.0.203-1 to 1.0.210-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-deb822-lossless/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-debversion/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-lazycell/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-procfs/0.14.2-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-ratatui/0.28.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for rust-rhai/1.18.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • autopkgtest for rust-roaring/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-rusty-paseto/0.7.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-serde/1.0.210-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-serde-xml-rs/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-tracing-subscriber/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-uom/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-vmm-sys-util/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): rust-serde rust-serde-derive (not considered)
    • Depends: rust-serde rust-serde-derive (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-serde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ruuvitag-ble (- to 0.1.2-2)
  • Migration status for ruuvitag-ble (- to 0.1.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruuvitag-ble.html
    • autopkgtest for ruuvitag-ble/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 ♻
    • 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)
• sfcgal (1.5.2-1 to 1.5.2-2)
  • Migration status for sfcgal (1.5.2-1 to 1.5.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/s/sfcgal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• silversearcher-ag-el (0.48-1.1 to 0.48-2)
  • Migration status for silversearcher-ag-el (0.48-1.1 to 0.48-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/silversearcher-ag-el.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• simgrid (3.35-2 to 3.36-1)
  • Migration status for simgrid (3.35-2 to 3.36-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/simgrid.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• simplisafe-python (- to 2024.1.0-2)
  • Migration status for simplisafe-python (- to 2024.1.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simplisafe-python.html
    • autopkgtest for simplisafe-python/2024.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• sopt (- to 4.1.0+dfsg-1)
  • Migration status for sopt (- to 4.1.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sopt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• sphinx-argparse-cli (1.17.0-1 to 1.18.1-1)
  • Migration status for sphinx-argparse-cli (1.17.0-1 to 1.18.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-argparse-cli.html
    • autopkgtest for sphinx-argparse-cli/1.18.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
• sshguard (2.4.2-1 to 2.4.3-1)
  • Migration status for sshguard (2.4.2-1 to 2.4.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:
    • Updating sshguard will fix bugs in testing: #1080140
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sshguard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• stdio-mgr (- to 1.0.1-2)
  • Migration status for stdio-mgr (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for stdio-mgr/1.0.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for stdio-mgr/n/a: riscv64: Regression or new test ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stdio-mgr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• sysvinit (3.10-1 to 3.10-2)
  • Migration status for sysvinit (3.10-1 to 3.10-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysvinit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• theme-d-intr (0.14.2-1 to 0.15.0-1)
  • Migration status for theme-d-intr (0.14.2-1 to 0.15.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/theme-d-intr.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 ♻
    • Reproducible on i386 - info ♻
• tiktoken (- to 0.7.0-1)
  • Migration status for tiktoken (- to 0.7.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiktoken.html
    • autopkgtest for tiktoken/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 ♻
    • 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)
• tomopy (- to 1.15.0+ds1-3)
  • Migration status for tomopy (- to 1.15.0+ds1-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for tomopy/1.15.0+ds1-3: amd64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• toposort (1.10-1 to 1.10-2)
  • Migration status for toposort (1.10-1 to 1.10-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/toposort.html
    • autopkgtest for toposort/1.10-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)
• tuigreet (0.9.1-1 to 0.9.1-3)
  • Migration status for tuigreet (0.9.1-1 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 2 of 5 days old
  • Additional info:
    • Updating tuigreet will fix bugs in testing: #1081202
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tuigreet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• undertime (4.1.0 to 4.2.0)
  • Migration status for undertime (4.1.0 to 4.2.0): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/undertime.html
    • autopkgtest for undertime/4.2.0: 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)
• xfsprogs (6.8.0-2.2 to 6.10.1-1)
  • Migration status for xfsprogs (6.8.0-2.2 to 6.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 2 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfsprogs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• xnnpack (0.0~git20221221.51a9875-1 to 0.0~git20240821.87ee0b4-2)
  • Migration status for xnnpack (0.0~git20221221.51a9875-1 to 0.0~git20240821.87ee0b4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for onnxruntime/1.16.3+dfsg-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xnnpack.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• xserver-xorg-video-cirrus (1:1.5.3-1 to 1:1.6.0-1)
  • Migration status for xserver-xorg-video-cirrus (1:1.5.3-1 to 1:1.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-cirrus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• yubihsm-shell (2.5.0-3 to 2.6.0-3)
  • Migration status for yubihsm-shell (2.5.0-3 to 2.6.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yubihsm-shell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• aioairzone (0.8.2-1 to 0.9.2-1)
  • Migration status for aioairzone (0.8.2-1 to 0.9.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aioairzone.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• apt-setup (1:0.186 to 1:0.187)
  • Migration status for apt-setup (1:0.186 to 1:0.187): 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)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cc-cedict (0.0~repack20240703-1 to 0.0~repack20240910-1)
  • Migration status for cc-cedict (0.0~repack20240703-1 to 0.0~repack20240910-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/cc-cedict.html
    • autopkgtest for cc-cedict/0.0~repack20240910-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
• chirp (1:20240901-1 to 1:20240905-1)
  • Migration status for chirp (1:20240901-1 to 1:20240905-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/chirp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• chromium (128.0.6613.113-1~deb13u1 to 128.0.6613.137-1)
  • Migration status for chromium (128.0.6613.113-1~deb13u1 to 128.0.6613.137-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): chromium libxml2 (not considered)
    • Depends: chromium libxml2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chromium.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility 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 ♻
    • 3 days old (needed 2 days)
• chuck (1.5.2.4-1 to 1.5.2.5-1)
  • Migration status for chuck (1.5.2.4-1 to 1.5.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/c/chuck.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ddcui (0.3.0-1 to 0.5.4-2)
  • Migration status for ddcui (0.3.0-1 to 0.5.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating ddcui will fix bugs in testing: #1081112
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/ddcui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• directx-headers (1.613.0-1 to 1.614.1-1)
  • Migration status for directx-headers (1.613.0-1 to 1.614.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/d/directx-headers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• django-oauth-toolkit (2.4.0-2 to 3.0.1-1)
  • Migration status for django-oauth-toolkit (2.4.0-2 to 3.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-oauth-toolkit.html
    • autopkgtest for django-oauth-toolkit/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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• djvubind (1.2.1-6 to 1.2.1-7)
  • Migration status for djvubind (1.2.1-6 to 1.2.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/djvubind.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• dnscap (2.2.0-2 to 2.2.1-1)
  • Migration status for dnscap (2.2.0-2 to 2.2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• dracut (103-1.1 to 103-2)
  • Migration status for dracut (103-1.1 to 103-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/dracut.html
    • Too young, only 3 of 10 days old
  • Additional info:
    • autopkgtest for dracut/103-2: amd64: Failed (not a regression), 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 ♻
• easyh10 (- to 1.5-7)
  • Migration status for easyh10 (- to 1.5-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/easyh10.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• elisa-player (23.08.5-1 to 23.08.5-2)
  • Migration status for elisa-player (23.08.5-1 to 23.08.5-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 elisa-player will fix bugs in testing: #1080104
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elisa-player.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• evdi (- to 1.14.6+dfsg-1)
  • Migration status for evdi (- to 1.14.6+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/evdi.html
    • autopkgtest for evdi/1.14.6+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
• fdroidserver (- to 2.3~a2-1)
  • Migration status for fdroidserver (- to 2.3~a2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: fdroidserver androguard (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fdroidserver.html
    • autopkgtest for fdroidserver/2.3~a2-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)
• finalcif (- to 137+dfsg-2)
  • Migration status for finalcif (- to 137+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/f/finalcif.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for finalcif/137+dfsg-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, riscv64: 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 ♻
• flent (2.1.1-3 to 2.2.0-1)
  • Migration status for flent (2.1.1-3 to 2.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:
    • Updating flent will fix bugs in testing: #1080274
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• geronimo-concurrent-1.0-spec (1.0~alpha-1-1.1 to 1.0~alpha-1-2)
  • Migration status for geronimo-concurrent-1.0-spec (1.0~alpha-1-1.1 to 1.0~alpha-1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geronimo-concurrent-1.0-spec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gerritlib (0.10.0-1 to 0.11.0-1)
  • Migration status for gerritlib (0.10.0-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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gerritlib.html
    • autopkgtest for gerritlib/0.11.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), 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 ♻
    • Reproducible on i386 - info ♻
• gftp (- to 2.9.1~beta-3)
  • Migration status for gftp (- to 2.9.1~beta-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gftp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gitbatch (- to 0.6.1-1)
  • Migration status for gitbatch (- to 0.6.1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: gitbatch golang-1.22
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitbatch.html
    • autopkgtest for gitbatch/0.6.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)
• gnome-disk-utility (46.0-1 to 46.1-1)
  • Migration status for gnome-disk-utility (46.0-1 to 46.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/g/gnome-disk-utility.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-session (46.0-7 to 46.0-8)
  • Migration status for gnome-session (46.0-7 to 46.0-8): 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-session.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• golang-github-gopacket-gopacket (1.2.0-2 to 1.3.0-1)
  • Migration status for golang-github-gopacket-gopacket (1.2.0-2 to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-gopacket-gopacket/1.3.0-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
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating golang-github-gopacket-gopacket will fix bugs in testing: #1077451
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gopacket-gopacket.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• got (0.101-1 to 0.103-1)
  • Migration status for got (0.101-1 to 0.103-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/got.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• graphite-web (1.1.10-6 to 1.1.10-8)
  • Migration status for graphite-web (1.1.10-6 to 1.1.10-8): 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/graphite-web.html
    • autopkgtest for graphite-web/1.1.10-8: 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 ♻
    • Reproducible on i386 - info ♻
• gromit-mpx (1.6.0-1 to 1.7.0-1)
  • Migration status for gromit-mpx (1.6.0-1 to 1.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gromit-mpx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• guile-gcrypt (0.4.0-3 to 0.4.0-4)
  • Migration status for guile-gcrypt (0.4.0-3 to 0.4.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/g/guile-gcrypt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• haskell-copilot (3.19.1-1 to 4.0-1)
  • Migration status for haskell-copilot (3.19.1-1 to 4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): haskell-copilot haskell-copilot-c99
    • Build-Depends(-Arch): haskell-copilot haskell-copilot-core
    • Build-Depends(-Arch): haskell-copilot haskell-copilot-language
    • Build-Depends(-Arch): haskell-copilot haskell-copilot-libraries
    • Build-Depends(-Arch): haskell-copilot haskell-copilot-prettyprinter
    • Build-Depends(-Arch): haskell-copilot haskell-copilot-theorem
    • Depends: haskell-copilot haskell-copilot-c99
    • Depends: haskell-copilot haskell-copilot-core
    • Depends: haskell-copilot haskell-copilot-language
    • Depends: haskell-copilot haskell-copilot-libraries
    • Depends: haskell-copilot haskell-copilot-prettyprinter
    • Depends: haskell-copilot haskell-copilot-theorem
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-copilot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• haskell-copilot-c99 (3.19.1-1 to 4.0-1)
  • Migration status for haskell-copilot-c99 (3.19.1-1 to 4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): haskell-copilot-c99 haskell-copilot-core
    • Depends: haskell-copilot-c99 haskell-copilot-core
    • Implicit dependency: haskell-copilot-c99 haskell-copilot
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-copilot-c99.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• haskell-copilot-core (3.19.1-1 to 4.0-1)
  • Migration status for haskell-copilot-core (3.19.1-1 to 4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Implicit dependency: haskell-copilot-core haskell-copilot
    • Implicit dependency: haskell-copilot-core haskell-copilot-c99
    • Implicit dependency: haskell-copilot-core haskell-copilot-interpreter
    • Implicit dependency: haskell-copilot-core haskell-copilot-language
    • Implicit dependency: haskell-copilot-core haskell-copilot-prettyprinter
    • Implicit dependency: haskell-copilot-core haskell-copilot-theorem
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-copilot-core.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• haskell-copilot-interpreter (3.19.1-1 to 4.0-1)
  • Migration status for haskell-copilot-interpreter (3.19.1-1 to 4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): haskell-copilot-interpreter haskell-copilot-core
    • Depends: haskell-copilot-interpreter haskell-copilot-core
    • Implicit dependency: haskell-copilot-interpreter haskell-copilot-language
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-copilot-interpreter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• haskell-copilot-language (3.19.1-1 to 4.0-1)
  • Migration status for haskell-copilot-language (3.19.1-1 to 4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): haskell-copilot-language haskell-copilot-core
    • Build-Depends(-Arch): haskell-copilot-language haskell-copilot-interpreter
    • Build-Depends(-Arch): haskell-copilot-language haskell-copilot-theorem
    • Depends: haskell-copilot-language haskell-copilot-core
    • Depends: haskell-copilot-language haskell-copilot-interpreter
    • Depends: haskell-copilot-language haskell-copilot-theorem
    • Implicit dependency: haskell-copilot-language haskell-copilot
    • Implicit dependency: haskell-copilot-language haskell-copilot-libraries
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-copilot-language.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• haskell-copilot-libraries (3.19.1-1 to 4.0-1)
  • Migration status for haskell-copilot-libraries (3.19.1-1 to 4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): haskell-copilot-libraries haskell-copilot-language
    • Depends: haskell-copilot-libraries haskell-copilot-language
    • Implicit dependency: haskell-copilot-libraries haskell-copilot
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-copilot-libraries.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• haskell-copilot-prettyprinter (3.19.1-1 to 4.0-1)
  • Migration status for haskell-copilot-prettyprinter (3.19.1-1 to 4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): haskell-copilot-prettyprinter haskell-copilot-core
    • Depends: haskell-copilot-prettyprinter haskell-copilot-core
    • Implicit dependency: haskell-copilot-prettyprinter haskell-copilot
    • Implicit dependency: haskell-copilot-prettyprinter haskell-copilot-theorem
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-copilot-prettyprinter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• haskell-copilot-theorem (3.19.1-1 to 4.0-1)
  • Migration status for haskell-copilot-theorem (3.19.1-1 to 4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): haskell-copilot-theorem haskell-copilot-core
    • Build-Depends(-Arch): haskell-copilot-theorem haskell-copilot-prettyprinter
    • Depends: haskell-copilot-theorem haskell-copilot-core
    • Depends: haskell-copilot-theorem haskell-copilot-prettyprinter
    • Implicit dependency: haskell-copilot-theorem haskell-copilot
    • Implicit dependency: haskell-copilot-theorem haskell-copilot-language
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-copilot-theorem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• htmldoc (1.9.18-1 to 1.9.18-2)
  • Migration status for htmldoc (1.9.18-1 to 1.9.18-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/htmldoc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• hw-detect (1.161 to 1.162)
  • Migration status for hw-detect (1.161 to 1.162): 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)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• instaloader (4.12.1+ds-1 to 4.13.1+ds-1)
  • Migration status for instaloader (4.12.1+ds-1 to 4.13.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/i/instaloader.html
    • autopkgtest for instaloader/4.13.1+ds-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), 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 ♻
• intel-graphics-compiler (- to 1.0.17537.20-1)
  • Migration status for intel-graphics-compiler (- to 1.0.17537.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-graphics-compiler would introduce bugs in testing: #1061213
    • Too young, only 3 of 5 days old
    • 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
• irony-mode (1.6.0-4 to 1.6.1-1)
  • Migration status for irony-mode (1.6.0-4 to 1.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): irony-mode llvm-toolchain-19 (not considered)
    • Depends: irony-mode llvm-toolchain-19 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/irony-mode.html
    • autopkgtest for irony-mode/1.6.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)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• juman (- to 7.0-3.9)
  • Migration status for juman (- to 7.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/juman.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
• kdevelop-python (- to 23.08.1-2)
  • Migration status for kdevelop-python (- to 23.08.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
    • Build-Depends(-Arch): kdevelop-python kdevelop (not considered)
    • Depends: kdevelop-python kdevelop (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdevelop-python.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kirigami-addons (0.11.0-2 to 1.3.0-2)
  • Migration status for kirigami-addons (0.11.0-2 to 1.3.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kirigami-addons.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libtgowt (0~git20230615.a45d8b8+dfsg-2 to 0~git20230615.a45d8b8+dfsg-2.1)
  • Migration status for libtgowt (0~git20230615.a45d8b8+dfsg-2 to 0~git20230615.a45d8b8+dfsg-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 libtgowt will fix bugs in testing: #1078287
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtgowt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lintian (2.118.1 to 2.118.2)
  • Migration status for lintian (2.118.1 to 2.118.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 lintian will fix bugs in testing: #1081316
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lintian.html
    • autopkgtest for lintian/2.118.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), 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 ♻
• litecli (1.11.1-1 to 1.12.3-1)
  • Migration status for litecli (1.11.1-1 to 1.12.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/l/litecli.html
    • autopkgtest for litecli/1.12.3-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), 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 ♻
• lomiri-filemanager-app (1.0.4+dfsg-3 to 1.1.1+dfsg-1)
  • Migration status for lomiri-filemanager-app (1.0.4+dfsg-3 to 1.1.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/l/lomiri-filemanager-app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxqt-about (1.4.0-1 to 1.4.0-2)
  • Migration status for lxqt-about (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 3 of 5 days old
  • Additional info:
    • Updating lxqt-about will fix bugs in testing: #1078290
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-about.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxqt-openssh-askpass (1.4.0-1 to 1.4.0-2)
  • Migration status for lxqt-openssh-askpass (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 3 of 5 days old
  • Additional info:
    • Updating lxqt-openssh-askpass will fix bugs in testing: #1078297
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-openssh-askpass.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxqt-panel (1.4.0-1 to 1.4.0-2)
  • Migration status for lxqt-panel (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 3 of 5 days old
  • Additional info:
    • Updating lxqt-panel will fix bugs in testing: #1078298
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-panel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxqt-qtplugin (1.4.0-2 to 1.4.0-3)
  • Migration status for lxqt-qtplugin (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
  • Additional info:
    • Updating lxqt-qtplugin will fix bugs in testing: #1078301
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-qtplugin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lxqt-runner (1.4.0-1 to 1.4.0-2)
  • Migration status for lxqt-runner (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 3 of 5 days old
  • Additional info:
    • Updating lxqt-runner will fix bugs in testing: #1078302
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-runner.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• macchanger (1.7.0-5.4 to 1.7.0-6)
  • Migration status for macchanger (1.7.0-5.4 to 1.7.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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/macchanger.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mediawiki2latex (8.10-1 to 8.12-1)
  • Migration status for mediawiki2latex (8.10-1 to 8.12-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/mediawiki2latex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mvtnorm (1.3-0-1 to 1.3-1-1)
  • Migration status for mvtnorm (1.3-0-1 to 1.3-1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-mutoss/0.1-13-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Regression or new test ♻ (reference ♻), 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/m/mvtnorm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• netdata (- to 1.47.1-1)
  • Migration status for netdata (- to 1.47.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netdata would introduce bugs in testing: #1042533, #1045145
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): netdata h2o (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• nvidia-graphics-drivers-legacy-340xx (- to 340.108-22)
  • Migration status for nvidia-graphics-drivers-legacy-340xx (- to 340.108-22): 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, #1073628, #973599, #979671, #987217, #991352
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for nvidia-graphics-drivers-legacy-340xx/340.108-22: amd64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• odil (0.12.2-4.1 to 0.12.2-5)
  • Migration status for odil (0.12.2-4.1 to 0.12.2-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/o/odil.html
    • autopkgtest for odil/0.12.2-5: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: Failed (not a regression), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• opencpn (1:5.10.0+dfsg-5 to 1:5.10.2+dfsg-1)
  • Migration status for opencpn (1:5.10.0+dfsg-5 to 1:5.10.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/o/opencpn.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 ♻
• opendkim (- to 2.11.0~beta2-9.1)
  • Migration status for opendkim (- to 2.11.0~beta2-9.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): opendkim libopendbx (not considered)
    • Depends: opendkim libopendbx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opendkim.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• openrc (0.54.2-1 to 0.55-1)
  • Migration status for openrc (0.54.2-1 to 0.55-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/openrc.html
    • autopkgtest for openrc/0.55-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: Failed (not a regression), s390x: Failed (not a regression)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• opensbi (1.5-1 to 1.5.1-1)
  • Migration status for opensbi (1.5-1 to 1.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensbi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• partman-auto (166 to 167)
  • Migration status for partman-auto (166 to 167): 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)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• partman-auto-lvm (95 to 96)
  • Migration status for partman-auto-lvm (95 to 96): 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)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• partman-crypto (125 to 126)
  • Migration status for partman-crypto (125 to 126): 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)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pavucontrol-qt (1.4.0-1 to 1.4.0-2)
  • Migration status for pavucontrol-qt (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 3 of 5 days old
  • Additional info:
    • Updating pavucontrol-qt will fix bugs in testing: #1078305
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pavucontrol-qt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pg-comparator (2.3.2-4 to 2.3.2-5)
  • Migration status for pg-comparator (2.3.2-4 to 2.3.2-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/p/pg-comparator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• port-for (0.7.2-2 to 0.7.3-1)
  • Migration status for port-for (0.7.2-2 to 0.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/port-for.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• postgresql-common (262 to 263)
  • Migration status for postgresql-common (262 to 263): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for djangorestframework-gis/1.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pgstat/1.2.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for php-horde-db/2.4.1-8: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for postgresql-common/263: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-django-pgschemas/0.15.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: Failed (not a regression), 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/postgresql-common.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• prometheus-pgbackrest-exporter (0.17.0+ds1-1 to 0.18.0+ds1-1)
  • Migration status for prometheus-pgbackrest-exporter (0.17.0+ds1-1 to 0.18.0+ds1-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: prometheus-pgbackrest-exporter golang-1.22
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-pgbackrest-exporter.html
    • autopkgtest for prometheus-pgbackrest-exporter/0.18.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• py3status (3.58-1 to 3.59-1)
  • Migration status for py3status (3.58-1 to 3.59-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/py3status.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pyside6 (- to 6.6.2-4)
  • Migration status for pyside6 (- to 6.6.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pyside6/6.6.2-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for pyside6/n/a: riscv64: Regression or new test ♻
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyside6.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
• pystring (1.1.4-1 to 1.1.4-2)
  • Migration status for pystring (1.1.4-1 to 1.1.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/p/pystring.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-autopage (0.4.0-3 to 0.4.0-3.1)
  • Migration status for python-autopage (0.4.0-3 to 0.4.0-3.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating python-autopage will fix bugs in testing: #1080278
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-autopage.html
    • Waiting for reproducibility test results on armhf - info ♻
• python-bioregistry (- to 0.11.12-3)
  • Migration status for python-bioregistry (- to 0.11.12-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): python-bioregistry bootstrap-flask (not considered)
    • Build-Depends(-Arch): python-bioregistry fastapi (not considered)
    • Build-Depends(-Arch): python-bioregistry python-curies
    • Build-Depends(-Arch): python-bioregistry python-rdflib-endpoint
    • Depends: python-bioregistry python-curies
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bioregistry.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-cron-descriptor (1.4.3-1 to 1.4.5-1)
  • Migration status for python-cron-descriptor (1.4.3-1 to 1.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 3 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cron-descriptor.html
    • autopkgtest for python-cron-descriptor/1.4.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
• python-cryptography (42.0.5-2 to 43.0.0-1)
  • Migration status for python-cryptography (42.0.5-2 to 43.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for heat/1:22.0.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for octavia/14.0.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: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-cryptography/43.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-pgpy/0.6.0-1.2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for twisted/24.3.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating python-cryptography will fix bugs in testing: #1080395
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cryptography.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-curies (- to 0.7.10-3)
  • Migration status for python-curies (- to 0.7.10-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): python-curies fastapi (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-curies.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-nmap (0.7.1-0.1 to 0.7.1-0.2)
  • Migration status for python-nmap (0.7.1-0.1 to 0.7.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/python-nmap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-pysubs2 (1.7.1-2 to 1.7.3-1)
  • Migration status for python-pysubs2 (1.7.1-2 to 1.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pysubs2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• qdiskinfo (0.3+git20240822+ds-1 to 0.3+git20240909+ds-1)
  • Migration status for qdiskinfo (0.3+git20240822+ds-1 to 0.3+git20240909+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/q/qdiskinfo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• qterminal (1.4.0-1 to 1.4.0-2)
  • Migration status for qterminal (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 3 of 5 days old
  • Additional info:
    • Updating qterminal will fix bugs in testing: #1078312
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qterminal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• qtermwidget (1.4.0-1 to 1.4.0-2)
  • Migration status for qtermwidget (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 3 of 5 days old
  • Additional info:
    • Updating qtermwidget will fix bugs in testing: #1078313
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtermwidget.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-microbenchmark (1.4.10-2 to 1.5.0-1)
  • Migration status for r-cran-microbenchmark (1.4.10-2 to 1.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-microbenchmark.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-rcppspdlog (0.0.17-1 to 0.0.18-1)
  • Migration status for r-cran-rcppspdlog (0.0.17-1 to 0.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rcppspdlog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-seurat (- to 5.1.0-1)
  • Migration status for r-cran-seurat (- to 5.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-seurat/5.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: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): r-cran-seurat r-cran-seuratobject
    • Depends: r-cran-seurat r-cran-seuratobject
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-seurat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-seuratobject (5.0.1-2 to 5.0.2-1)
  • Migration status for r-cran-seuratobject (5.0.1-2 to 5.0.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-seuratobject.html
    • autopkgtest for r-cran-seuratobject/5.0.2-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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-wk (0.9.1-1 to 0.9.3-1)
  • Migration status for r-cran-wk (0.9.1-1 to 0.9.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-wk.html
    • autopkgtest for r-cran-wk/0.9.3-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 ♻
    • Reproducible on i386 - info ♻
• rabbitvcs (0.19-2 to 0.19-3)
  • Migration status for rabbitvcs (0.19-2 to 0.19-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rabbitvcs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• range-v3 (0.12.0-1 to 0.12.0-1.1)
  • Migration status for range-v3 (0.12.0-1 to 0.12.0-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating range-v3 will fix bugs in testing: #1077433
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/range-v3.html
    • No reference result, but not reproducibility on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • No reference result, but not reproducibility on i386 - info ♻
• rocdbgapi (5.7.1-1 to 5.7.1-2)
  • Migration status for rocdbgapi (5.7.1-1 to 5.7.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rocdbgapi.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 ♻
• rootskel (1.136 to 1.137)
  • Migration status for rootskel (1.136 to 1.137): 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
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducibility regression on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-ab-glyph (0.2.21-2 to 0.2.28-1)
  • Migration status for rust-ab-glyph (0.2.21-2 to 0.2.28-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-ab-glyph rust-owned-ttf-parser (not considered)
    • Depends: rust-ab-glyph rust-owned-ttf-parser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ab-glyph.html
    • autopkgtest for rust-ab-glyph/0.2.28-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)
• rust-cast-sender (- to 0.2.0-2)
  • Migration status for rust-cast-sender (- 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 3 of 5 days old
    • Build-Depends(-Arch): rust-cast-sender rust-async-native-tls
    • Depends: rust-cast-sender rust-async-native-tls
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-cast-sender.html
    • autopkgtest for rust-cast-sender/0.2.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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-concurrent-arena (- to 0.1.9-1)
  • Migration status for rust-concurrent-arena (- to 0.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-concurrent-arena/0.1.9-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, 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/r/rust-concurrent-arena.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-laurel (0.6.2-2 to 0.6.3-1)
  • Migration status for rust-laurel (0.6.2-2 to 0.6.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-laurel rust-nix (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-laurel.html
    • autopkgtest for rust-laurel/0.6.3-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 ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-nix (0.27.1-4 to 0.27.1-5)
  • Migration status for rust-nix (0.27.1-4 to 0.27.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-calloop/0.12.4-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: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for rust-nix/0.27.1-5: 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/r/rust-nix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-owned-ttf-parser (0.19.0-1 to 0.24.0-1)
  • Migration status for rust-owned-ttf-parser (0.19.0-1 to 0.24.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-owned-ttf-parser rust-ttf-parser (not considered)
    • Depends: rust-owned-ttf-parser rust-ttf-parser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Implicit dependency: rust-owned-ttf-parser rust-ab-glyph
    • Implicit dependency: rust-owned-ttf-parser rust-rusttype
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-owned-ttf-parser.html
    • autopkgtest for rust-owned-ttf-parser/0.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-rusttype (0.9.3-3 to 0.9.3-4)
  • Migration status for rust-rusttype (0.9.3-3 to 0.9.3-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-rusttype rust-owned-ttf-parser (not considered)
    • Depends: rust-rusttype rust-owned-ttf-parser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rusttype.html
    • autopkgtest for rust-rusttype/0.9.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 ♻
    • 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)
• rust-sniffglue (0.16.0-3 to 0.16.1-1)
  • Migration status for rust-sniffglue (0.16.0-3 to 0.16.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-sniffglue rust-nix (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): rust-sniffglue rust-tls-parser
    • Build-Depends(-Arch): rust-sniffglue rust-uzers
    • Depends: rust-sniffglue rust-tls-parser
    • Depends: rust-sniffglue rust-uzers
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sniffglue.html
    • autopkgtest for rust-sniffglue/0.16.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)
• rust-speakersafetyd (1.0.0-1 to 1.0.1-1)
  • Migration status for rust-speakersafetyd (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 3 of 5 days old
    • Built-Using: rust-speakersafetyd rust-nix (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-speakersafetyd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• sagemath-database-conway-polynomials (0.10-1.1 to 0.10-2)
  • Migration status for sagemath-database-conway-polynomials (0.10-1.1 to 0.10-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/s/sagemath-database-conway-polynomials.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• skeema (1.11.2+ds-1 to 1.12.0+ds-1)
  • Migration status for skeema (1.11.2+ds-1 to 1.12.0+ds-1): Will attempt migration (Any information below is purely informational)
    • Built-Using: skeema golang-1.22
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/skeema.html
    • autopkgtest for skeema/1.12.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
    • 3 days old (needed 2 days)
• sphinx-autobuild (2021.3.14-3 to 2024.09.03-1)
  • Migration status for sphinx-autobuild (2021.3.14-3 to 2024.09.03-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/sphinx-autobuild.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• sqlglot (25.18.0-1 to 25.20.1-1)
  • Migration status for sqlglot (25.18.0-1 to 25.20.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/sqlglot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• stringtemplate4 (4.0.8-2.1 to 4.0.8-3)
  • Migration status for stringtemplate4 (4.0.8-2.1 to 4.0.8-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stringtemplate4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• systemd (256.5-1 to 256.6-1)
  • Migration status for systemd (256.5-1 to 256.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/s/systemd.html
    • autopkgtest for systemd/256.6-1: amd64: Failed (not a regression), 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 ♻
• tftp-hpa (5.2+20240610-1 to 5.2+20240610-2)
  • Migration status for tftp-hpa (5.2+20240610-1 to 5.2+20240610-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tftp-hpa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• thunderbird (1:128.1.1esr-1 to 1:128.2.0esr-1)
  • Migration status for thunderbird (1:128.1.1esr-1 to 1:128.2.0esr-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/thunderbird.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • autopkgtest for thunderbird/1:128.2.0esr-1: amd64: Pass, arm64: 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
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• user-setup (1.98 to 1.99)
  • Migration status for user-setup (1.98 to 1.99): 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/user-setup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• vim-youcompleteme (0+20231230+git71166ea+ds-2 to 0+20240827+gitb6e8c64+ds-1)
  • Migration status for vim-youcompleteme (0+20231230+git71166ea+ds-2 to 0+20240827+gitb6e8c64+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for vim-youcompleteme/0+20240827+gitb6e8c64+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for vim-youcompleteme/blocked-on-ci-infra: riscv64: Failed (not a regression)
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-youcompleteme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• wasi-libc (0.0~git20240411.9e8c542-3 to 0.0~git20240411.9e8c542-4)
  • Migration status for wasi-libc (0.0~git20240411.9e8c542-3 to 0.0~git20240411.9e8c542-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/w/wasi-libc.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• webcamoid (- to 9.1.1-1.1)
  • Migration status for webcamoid (- to 9.1.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating webcamoid would introduce bugs in testing: #1053808
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webcamoid.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
• weston (13.0.3-1 to 14.0.0-1)
  • Migration status for weston (13.0.3-1 to 14.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating weston would introduce bugs in testing: #1081515
    • autopkgtest for gtk4/4.14.4+ds-8: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for weston/14.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Pass, ppc64el: Pass, 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/w/weston.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• xserver-xorg-input-joystick (1:1.6.3-1.1 to 1:1.6.4-1)
  • Migration status for xserver-xorg-input-joystick (1:1.6.3-1.1 to 1:1.6.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/x/xserver-xorg-input-joystick.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• yara (4.5.1-1 to 4.5.2-1)
  • Migration status for yara (4.5.1-1 to 4.5.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yara.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ycmd (0+20240618+gite81c15e+ds-1 to 0+20240823+git8b61f19+ds-1)
  • Migration status for ycmd (0+20240618+gite81c15e+ds-1 to 0+20240823+git8b61f19+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/y/ycmd.html
    • autopkgtest for ycmd/0+20240823+git8b61f19+ds-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 ♻
    • Reproducible on i386 - info ♻
• addresses-for-gnustep (0.4.8-3 to 0.4.8-4)
  • Migration status for addresses-for-gnustep (0.4.8-3 to 0.4.8-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 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/addresses-for-gnustep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• androguard (- to 3.4.0~a1-15)
  • Migration status for androguard (- to 3.4.0~a1-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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/androguard.html
    • autopkgtest for androguard/3.4.0~a1-15: amd64: Pass, arm64: Pass, armel: 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 ♻
• babeltrace (1.5.11-3 to 1.5.11-4)
  • Migration status for babeltrace (1.5.11-3 to 1.5.11-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/babeltrace.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• babeltrace2 (2.0.6-1 to 2.0.6-2)
  • Migration status for babeltrace2 (2.0.6-1 to 2.0.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/b/babeltrace2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• blender (- to 4.2.1+dfsg-1)
  • Migration status for blender (- to 4.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 4 of 5 days old
    • Build-Depends(-Arch): blender embree
    • Build-Depends(-Arch): blender opencolorio
    • Build-Depends(-Arch): blender openimageio
    • Build-Depends(-Arch): blender openvdb (not considered)
    • Depends: blender embree
    • Depends: blender opencolorio
    • Depends: blender openimageio
    • Depends: blender openvdb (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blender.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• clipit (- to 1.4.5+git20210313-3)
  • Migration status for clipit (- to 1.4.5+git20210313-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clipit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cppo (1.6.9-4 to 1.7.0-1)
  • Migration status for cppo (1.6.9-4 to 1.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cppo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• creduce (2.11.0~20240312-1 to 2.11.0~20240909-1)
  • Migration status for creduce (2.11.0~20240312-1 to 2.11.0~20240909-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): creduce llvm-toolchain-19 (not considered)
    • Depends: creduce llvm-toolchain-19 (not considered)
  • 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 ♻
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• crun (1.16.1-1 to 1.17-1)
  • Migration status for crun (1.16.1-1 to 1.17-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/crun.html
    • autopkgtest for crun/1.17-1: amd64: Pass, 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 ♻
• cvise (2.10.0-1 to 2.10.0+20240909-1)
  • Migration status for cvise (2.10.0-1 to 2.10.0+20240909-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): cvise llvm-toolchain-19 (not considered)
    • Depends: cvise llvm-toolchain-19 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cvise.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• dbuskit (0.1.1-3 to 0.1.1-4)
  • Migration status for dbuskit (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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dbuskit.html
    • autopkgtest for dbuskit/0.1.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: 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 ♻
• debmirror (1:2.41 to 1:2.42)
  • Migration status for debmirror (1:2.41 to 1:2.42): 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/debmirror.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• dict-elements (20001107-a-9.1 to 20240910094116-1)
  • Migration status for dict-elements (20001107-a-9.1 to 20240910094116-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/dict-elements.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• dvi2dvi (- to 2.0alpha-12)
  • Migration status for dvi2dvi (- to 2.0alpha-12): 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/dvi2dvi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• electrum (4.5.5+dfsg-1 to 4.5.5+dfsg-2)
  • Migration status for electrum (4.5.5+dfsg-1 to 4.5.5+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/electrum.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ell (0.67-1 to 0.69-2)
  • Migration status for ell (0.67-1 to 0.69-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ell would introduce bugs in testing: #1081252
    • migrating libell0/0.69-2/amd64 to testing makes libmptcpd3/0.12-4/amd64 uninstallable
    • migrating libell0/0.69-2/amd64 to testing makes mptcpd/0.12-4/amd64 uninstallable
    • migrating libell0/0.69-2/amd64 to testing makes mptcpd-plugins/0.12-4/amd64 uninstallable
    • migrating libell0/0.69-2/arm64 to testing makes libmptcpd3/0.12-4/arm64 uninstallable
    • migrating libell0/0.69-2/arm64 to testing makes mptcpd/0.12-4/arm64 uninstallable
    • migrating libell0/0.69-2/arm64 to testing makes mptcpd-plugins/0.12-4/arm64 uninstallable
    • migrating libell0/0.69-2/armel to testing makes libmptcpd3/0.12-4/armel uninstallable
    • migrating libell0/0.69-2/armel to testing makes mptcpd/0.12-4/armel uninstallable
    • migrating libell0/0.69-2/armel to testing makes mptcpd-plugins/0.12-4/armel uninstallable
    • migrating libell0/0.69-2/armhf to testing makes libmptcpd3/0.12-4/armhf uninstallable
    • migrating libell0/0.69-2/armhf to testing makes mptcpd/0.12-4/armhf uninstallable
    • migrating libell0/0.69-2/armhf to testing makes mptcpd-plugins/0.12-4/armhf uninstallable
    • migrating libell0/0.69-2/i386 to testing makes libmptcpd3/0.12-4/i386 uninstallable
    • migrating libell0/0.69-2/i386 to testing makes mptcpd/0.12-4/i386 uninstallable
    • migrating libell0/0.69-2/i386 to testing makes mptcpd-plugins/0.12-4/i386 uninstallable
    • migrating libell0/0.69-2/mips64el to testing makes libmptcpd3/0.12-4/mips64el uninstallable
    • migrating libell0/0.69-2/mips64el to testing makes mptcpd/0.12-4/mips64el uninstallable
    • migrating libell0/0.69-2/mips64el to testing makes mptcpd-plugins/0.12-4/mips64el uninstallable
    • migrating libell0/0.69-2/ppc64el to testing makes libmptcpd3/0.12-4/ppc64el uninstallable
    • migrating libell0/0.69-2/ppc64el to testing makes mptcpd/0.12-4/ppc64el uninstallable
    • migrating libell0/0.69-2/ppc64el to testing makes mptcpd-plugins/0.12-4/ppc64el uninstallable
    • migrating libell0/0.69-2/s390x to testing makes libmptcpd3/0.12-4/s390x uninstallable
    • migrating libell0/0.69-2/s390x to testing makes mptcpd/0.12-4/s390x uninstallable
    • migrating libell0/0.69-2/s390x to testing makes mptcpd-plugins/0.12-4/s390x uninstallable
    • Too young, only 4 of 5 days old
    • Implicit dependency: ell iwd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ell.html
    • autopkgtest for ell/0.69-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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• epoptes (23.08-1 to 23.08-2)
  • Migration status for epoptes (23.08-1 to 23.08-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating epoptes will fix bugs in testing: #1081025
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epoptes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• evolution (3.53.2-1 to 3.53.3-1)
  • Migration status for evolution (3.53.2-1 to 3.53.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/e/evolution.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• evolution-ews (3.53.2-1 to 3.53.3-1)
  • Migration status for evolution-ews (3.53.2-1 to 3.53.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
    • Build-Depends(-Arch): evolution-ews evolution
    • Depends: evolution-ews evolution
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/evolution-ews.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• firmware-sof (2023.12.1-1.1 to 2024.06-1)
  • Migration status for firmware-sof (2023.12.1-1.1 to 2024.06-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)
• freecdb (- to 0.78)
  • Migration status for freecdb (- to 0.78): 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/freecdb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• freedombox (24.18 to 24.19)
  • Migration status for freedombox (24.18 to 24.19): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for freedombox/24.19: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freedombox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• fuse (2.9.9-8.2 to 2.9.9-9)
  • Migration status for fuse (2.9.9-8.2 to 2.9.9-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/f/fuse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• g-golf (0.8.0~rc5-1 to 0.8.0~rc5-2)
  • Migration status for g-golf (0.8.0~rc5-1 to 0.8.0~rc5-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/g-golf.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 ♻
• glab (1.45.0-1 to 1.46.0-1)
  • Migration status for glab (1.45.0-1 to 1.46.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Built-Using: glab golang-1.22
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glab.html
    • autopkgtest for glab/1.46.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 ♻
    • Reproducibility regression on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• golang-github-containers-buildah (1.37.1+ds1-2 to 1.37.2+ds1-3)
  • Migration status for golang-github-containers-buildah (1.37.1+ds1-2 to 1.37.2+ds1-3): Will attempt migration (Any information below is purely informational)
    • Built-Using: golang-github-containers-buildah golang-1.22
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-containers-buildah.html
    • autopkgtest for golang-github-containers-buildah/1.37.2+ds1-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
    • 4 days old (needed 2 days)
• grr.app (1.0-1 to 1.0-2)
  • Migration status for grr.app (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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grr.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• hugin (2023.0.0+dfsg-1 to 2024.0~beta1+dfsg-1)
  • Migration status for hugin (2023.0.0+dfsg-1 to 2024.0~beta1+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 7 days old
    • Depends: hugin exiv2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hugin.html
    • autopkgtest for hugin/2024.0~beta1+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
• invesalius (- to 3.1.99998-5)
  • Migration status for invesalius (- to 3.1.99998-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/i/invesalius.html
    • autopkgtest for invesalius/3.1.99998-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 ♻
• iwd (2.19-1 to 2.21-1)
  • Migration status for iwd (2.19-1 to 2.21-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): iwd ell (not considered)
    • Depends: iwd ell (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iwd.html
    • autopkgtest for iwd/2.21-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
    • 4 days old (needed 2 days)
• josm (0.0.svn19207+dfsg-1 to 0.0.svn19207+dfsg-2)
  • Migration status for josm (0.0.svn19207+dfsg-1 to 0.0.svn19207+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/j/josm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kannel (1.4.5-17 to 1.4.5-18)
  • Migration status for kannel (1.4.5-17 to 1.4.5-18): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on armel
    • missing build on armhf
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating kannel will fix bugs in testing: #1080146
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kannel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libbeam-java (1.3.5-2 to 1.3.6-1)
  • Migration status for libbeam-java (1.3.5-2 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/libb/libbeam-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libcds (2.3.3-4.1 to 2.3.3-5)
  • Migration status for libcds (2.3.3-4.1 to 2.3.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/libc/libcds.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libctl (4.5.1-2.1 to 4.5.1-3)
  • Migration status for libctl (4.5.1-2.1 to 4.5.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/libc/libctl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libdrm (2.4.122-1 to 2.4.123-1)
  • Migration status for libdrm (2.4.122-1 to 2.4.123-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/libd/libdrm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libldac (2.0.2.3+git20200429+ed310a0-4 to 2.0.2.3+git20200429+ed310a0-5)
  • Migration status for libldac (2.0.2.3+git20200429+ed310a0-4 to 2.0.2.3+git20200429+ed310a0-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/libl/libldac.html
    • autopkgtest for libldac/2.0.2.3+git20200429+ed310a0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libpod (5.2.1+ds1-4 to 5.2.2+ds1-2)
  • Migration status for libpod (5.2.1+ds1-4 to 5.2.2+ds1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): libpod golang-github-containers-buildah
    • Built-Using: libpod golang-1.22
    • Built-Using: libpod golang-github-containers-buildah
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpod.html
    • autopkgtest for libpod/5.2.2+ds1-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: 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 ♻
• libzypp (17.35.9-1 to 17.35.10-1)
  • Migration status for libzypp (17.35.9-1 to 17.35.10-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/libz/libzypp.html
    • No reference result, but not reproducibility on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • No reference result, but not reproducibility on i386 - info ♻
• linuxdoc-tools (0.9.83-3 to 0.9.84-1)
  • Migration status for linuxdoc-tools (0.9.83-3 to 0.9.84-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linuxdoc-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lomiri-online-accounts-plugins (- to 0.17-2)
  • Migration status for lomiri-online-accounts-plugins (- to 0.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lomiri-online-accounts-plugin-foursquare/amd64 has unsatisfiable dependency
    • lomiri-online-accounts-plugin-identica/amd64 has unsatisfiable dependency
    • lomiri-online-accounts-plugin-instagram/amd64 has unsatisfiable dependency
    • lomiri-online-accounts-plugin-linkedin/amd64 has unsatisfiable dependency
    • lomiri-online-accounts-plugin-sina/amd64 has unsatisfiable dependency
    • lomiri-online-accounts-plugin-sohu/amd64 has unsatisfiable dependency
    • lomiri-online-accounts-plugin-foursquare/arm64 has unsatisfiable dependency
    • lomiri-online-accounts-plugin-identica/arm64 has unsatisfiable dependency
    • lomiri-online-accounts-plugin-instagram/arm64 has unsatisfiable dependency
    • lomiri-online-accounts-plugin-linkedin/arm64 has unsatisfiable dependency
    • lomiri-online-accounts-plugin-sina/arm64 has unsatisfiable dependency
    • lomiri-online-accounts-plugin-sohu/arm64 has unsatisfiable dependency
    • Too young, only 4 of 5 days old
  • 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 amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mctc-lib (0.3.1-3 to 0.3.2-1)
  • Migration status for mctc-lib (0.3.1-3 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mctc-lib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• meli (- to 0.8.7+20240903+dfsg-2)
  • Migration status for meli (- to 0.8.7+20240903+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
    • Build-Depends(-Arch): meli rust-imap-codec (not considered)
    • Build-Depends(-Arch): meli rust-notify-rust (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• mpich (4.2.0-11 to 4.2.0-14)
  • Migration status for mpich (4.2.0-11 to 4.2.0-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpich.html
    • autopkgtest for mpich/4.2.0-14: 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 ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• ocaml-asn1-combinators (0.3.1-1 to 0.3.2-1)
  • Migration status for ocaml-asn1-combinators (0.3.1-1 to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libasn1-combinators-ocaml/0.3.2-1/amd64 to testing makes libca-certs-ocaml/1.0.0-1+b1/amd64 uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/amd64 to testing makes libx509-ocaml/1.0.2-1/amd64 uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/amd64 to testing makes libca-certs-ocaml-dev/1.0.0-1+b1/amd64 uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/amd64 to testing makes libx509-ocaml-dev/1.0.2-1/amd64 uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/arm64 to testing makes libca-certs-ocaml/1.0.0-1+b1/arm64 uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/arm64 to testing makes libx509-ocaml/1.0.2-1/arm64 uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/arm64 to testing makes libca-certs-ocaml-dev/1.0.0-1+b1/arm64 uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/arm64 to testing makes libx509-ocaml-dev/1.0.2-1/arm64 uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/armel to testing makes libca-certs-ocaml/1.0.0-1+b1/armel uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/armel to testing makes libx509-ocaml/1.0.2-1/armel uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/armel to testing makes libca-certs-ocaml-dev/1.0.0-1+b1/armel uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/armel to testing makes libx509-ocaml-dev/1.0.2-1/armel uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/armhf to testing makes libca-certs-ocaml/1.0.0-1+b1/armhf uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/armhf to testing makes libx509-ocaml/1.0.2-1/armhf uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/armhf to testing makes libca-certs-ocaml-dev/1.0.0-1+b1/armhf uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/armhf to testing makes libx509-ocaml-dev/1.0.2-1/armhf uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/i386 to testing makes libca-certs-ocaml/1.0.0-1+b1/i386 uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/i386 to testing makes libx509-ocaml/1.0.2-1/i386 uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/i386 to testing makes libca-certs-ocaml-dev/1.0.0-1+b1/i386 uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/i386 to testing makes libx509-ocaml-dev/1.0.2-1/i386 uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/mips64el to testing makes libca-certs-ocaml/1.0.0-1+b1/mips64el uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/mips64el to testing makes libx509-ocaml/1.0.2-1/mips64el uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/mips64el to testing makes libca-certs-ocaml-dev/1.0.0-1+b1/mips64el uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/mips64el to testing makes libx509-ocaml-dev/1.0.2-1/mips64el uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/ppc64el to testing makes libca-certs-ocaml/1.0.0-1+b1/ppc64el uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/ppc64el to testing makes libx509-ocaml/1.0.2-1/ppc64el uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/ppc64el to testing makes libca-certs-ocaml-dev/1.0.0-1+b1/ppc64el uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/ppc64el to testing makes libx509-ocaml-dev/1.0.2-1/ppc64el uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/s390x to testing makes libca-certs-ocaml/1.0.0-1+b1/s390x uninstallable
    • migrating libasn1-combinators-ocaml/0.3.2-1/s390x to testing makes libx509-ocaml/1.0.2-1/s390x uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/s390x to testing makes libca-certs-ocaml-dev/1.0.0-1+b1/s390x uninstallable
    • migrating libasn1-combinators-ocaml-dev/0.3.2-1/s390x to testing makes libx509-ocaml-dev/1.0.2-1/s390x uninstallable
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-asn1-combinators.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ocaml-mccs (1.1+17-1 to 1.1+18-1)
  • Migration status for ocaml-mccs (1.1+17-1 to 1.1+18-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/ocaml-mccs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ocaml-re (1.11.0-1 to 1.12.0-1)
  • Migration status for ocaml-re (1.11.0-1 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ocaml-re would introduce bugs in testing: #1081360
    • migrating libre-ocaml-dev/1.12.0-1/amd64 to testing makes libcohttp-ocaml-dev/5.3.0-1+b13/amd64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/amd64 to testing makes libdose3-ocaml-dev/7.0.0-5+b3/amd64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/amd64 to testing makes libeliom-ocaml-dev/10.4.1-1+b5/amd64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/amd64 to testing makes libocsigenserver-ocaml-dev/5.1.2-2+b5/amd64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/amd64 to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/amd64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/amd64 to testing makes libocsipersist-sqlite-ocaml-dev/1.1.0-3+b18/amd64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/arm64 to testing makes libcohttp-ocaml-dev/5.3.0-1+b13/arm64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/arm64 to testing makes libdose3-ocaml-dev/7.0.0-5+b3/arm64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/arm64 to testing makes libeliom-ocaml-dev/10.4.1-1+b5/arm64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/arm64 to testing makes libocsigenserver-ocaml-dev/5.1.2-2+b5/arm64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/arm64 to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/arm64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/arm64 to testing makes libocsipersist-sqlite-ocaml-dev/1.1.0-3+b18/arm64 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armel to testing makes libcohttp-ocaml-dev/5.3.0-1+b10/armel uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armel to testing makes libdose3-ocaml-dev/7.0.0-5+b3/armel uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armel to testing makes libeliom-ocaml-dev/10.4.1-1+b4/armel uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armel to testing makes libocsigenserver-ocaml-dev/5.1.2-2+b5/armel uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armel to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b16/armel uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armel to testing makes libocsipersist-sqlite-ocaml-dev/1.1.0-3+b16/armel uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armhf to testing makes libcohttp-ocaml-dev/5.3.0-1+b13/armhf uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armhf to testing makes libdose3-ocaml-dev/7.0.0-5+b3/armhf uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armhf to testing makes libeliom-ocaml-dev/10.4.1-1+b5/armhf uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armhf to testing makes libocsigenserver-ocaml-dev/5.1.2-2+b5/armhf uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armhf to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/armhf uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/armhf to testing makes libocsipersist-sqlite-ocaml-dev/1.1.0-3+b18/armhf uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/i386 to testing makes libcohttp-ocaml-dev/5.3.0-1+b13/i386 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/i386 to testing makes libdose3-ocaml-dev/7.0.0-5+b3/i386 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/i386 to testing makes libeliom-ocaml-dev/10.4.1-1+b5/i386 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/i386 to testing makes libocsigenserver-ocaml-dev/5.1.2-2+b5/i386 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/i386 to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/i386 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/i386 to testing makes libocsipersist-sqlite-ocaml-dev/1.1.0-3+b18/i386 uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/mips64el to testing makes libcohttp-ocaml-dev/5.3.0-1+b10/mips64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/mips64el to testing makes libdose3-ocaml-dev/7.0.0-5+b3/mips64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/mips64el to testing makes libeliom-ocaml-dev/10.4.1-1+b4/mips64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/mips64el to testing makes libocsigenserver-ocaml-dev/5.1.2-2+b5/mips64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/mips64el to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b16/mips64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/mips64el to testing makes libocsipersist-sqlite-ocaml-dev/1.1.0-3+b16/mips64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/ppc64el to testing makes libcohttp-ocaml-dev/5.3.0-1+b13/ppc64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/ppc64el to testing makes libdose3-ocaml-dev/7.0.0-5+b3/ppc64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/ppc64el to testing makes libeliom-ocaml-dev/10.4.1-1+b5/ppc64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/ppc64el to testing makes libocsigenserver-ocaml-dev/5.1.2-2+b5/ppc64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/ppc64el to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/ppc64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/ppc64el to testing makes libocsipersist-sqlite-ocaml-dev/1.1.0-3+b18/ppc64el uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/s390x to testing makes libcohttp-ocaml-dev/5.3.0-1+b13/s390x uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/s390x to testing makes libdose3-ocaml-dev/7.0.0-5+b3/s390x uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/s390x to testing makes libeliom-ocaml-dev/10.4.1-1+b5/s390x uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/s390x to testing makes libocsigenserver-ocaml-dev/5.1.2-2+b5/s390x uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/s390x to testing makes libocsipersist-pgsql-ocaml-dev/1.1.0-3+b18/s390x uninstallable
    • migrating libre-ocaml-dev/1.12.0-1/s390x to testing makes libocsipersist-sqlite-ocaml-dev/1.1.0-3+b18/s390x uninstallable
    • autopkgtest for ocaml-re/1.12.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
    • Implicit dependency: ocaml-re ben/amd64
    • Implicit dependency: ocaml-re ben/arm64
    • Implicit dependency: ocaml-re ben/armel
    • Implicit dependency: ocaml-re ben/armhf
    • Implicit dependency: ocaml-re ben/i386
    • Implicit dependency: ocaml-re ben/mips64el
    • Implicit dependency: ocaml-re ben/ppc64el
    • Implicit dependency: ocaml-re ben/s390x
    • Implicit dependency: ocaml-re calendar/amd64 (not considered)
    • Implicit dependency: ocaml-re calendar/arm64 (not considered)
    • Implicit dependency: ocaml-re calendar/armel (not considered)
    • Implicit dependency: ocaml-re calendar/armhf (not considered)
    • Implicit dependency: ocaml-re calendar/i386 (not considered)
    • Implicit dependency: ocaml-re calendar/mips64el (not considered)
    • Implicit dependency: ocaml-re calendar/ppc64el (not considered)
    • Implicit dependency: ocaml-re calendar/s390x (not considered)
    • Implicit dependency: ocaml-re camlp5/amd64
    • Implicit dependency: ocaml-re camlp5/arm64
    • Implicit dependency: ocaml-re camlp5/armel
    • Implicit dependency: ocaml-re camlp5/armhf
    • Implicit dependency: ocaml-re camlp5/i386
    • Implicit dependency: ocaml-re camlp5/mips64el
    • Implicit dependency: ocaml-re camlp5/ppc64el
    • Implicit dependency: ocaml-re camlp5/s390x
    • Implicit dependency: ocaml-re elpi/amd64
    • Implicit dependency: ocaml-re elpi/arm64
    • Implicit dependency: ocaml-re elpi/ppc64el
    • Implicit dependency: ocaml-re elpi/s390x
    • Implicit dependency: ocaml-re ocaml-alcotest/amd64
    • Implicit dependency: ocaml-re ocaml-alcotest/arm64
    • Implicit dependency: ocaml-re ocaml-alcotest/armel
    • Implicit dependency: ocaml-re ocaml-alcotest/armhf
    • Implicit dependency: ocaml-re ocaml-alcotest/i386
    • Implicit dependency: ocaml-re ocaml-alcotest/mips64el
    • Implicit dependency: ocaml-re ocaml-alcotest/ppc64el
    • Implicit dependency: ocaml-re ocaml-alcotest/s390x
    • Implicit dependency: ocaml-re ocaml-atd/amd64
    • Implicit dependency: ocaml-re ocaml-atd/arm64
    • Implicit dependency: ocaml-re ocaml-atd/armel
    • Implicit dependency: ocaml-re ocaml-atd/armhf
    • Implicit dependency: ocaml-re ocaml-atd/i386
    • Implicit dependency: ocaml-re ocaml-atd/mips64el
    • Implicit dependency: ocaml-re ocaml-atd/ppc64el
    • Implicit dependency: ocaml-re ocaml-atd/s390x
    • Implicit dependency: ocaml-re ocaml-duppy/amd64
    • Implicit dependency: ocaml-re ocaml-duppy/arm64
    • Implicit dependency: ocaml-re ocaml-duppy/armel
    • Implicit dependency: ocaml-re ocaml-duppy/armhf
    • Implicit dependency: ocaml-re ocaml-duppy/i386
    • Implicit dependency: ocaml-re ocaml-duppy/mips64el
    • Implicit dependency: ocaml-re ocaml-duppy/ppc64el
    • Implicit dependency: ocaml-re ocaml-duppy/s390x
    • Implicit dependency: ocaml-re ocaml-expect/amd64
    • Implicit dependency: ocaml-re ocaml-expect/arm64
    • Implicit dependency: ocaml-re ocaml-expect/armel
    • Implicit dependency: ocaml-re ocaml-expect/armhf
    • Implicit dependency: ocaml-re ocaml-expect/i386
    • Implicit dependency: ocaml-re ocaml-expect/mips64el
    • Implicit dependency: ocaml-re ocaml-expect/ppc64el
    • Implicit dependency: ocaml-re ocaml-expect/s390x
    • Implicit dependency: ocaml-re ocaml-inifiles/amd64
    • Implicit dependency: ocaml-re ocaml-inifiles/arm64
    • Implicit dependency: ocaml-re ocaml-inifiles/armel
    • Implicit dependency: ocaml-re ocaml-inifiles/armhf
    • Implicit dependency: ocaml-re ocaml-inifiles/i386
    • Implicit dependency: ocaml-re ocaml-inifiles/mips64el
    • Implicit dependency: ocaml-re ocaml-inifiles/ppc64el
    • Implicit dependency: ocaml-re ocaml-inifiles/s390x
    • Implicit dependency: ocaml-re ocaml-lastfm/amd64
    • Implicit dependency: ocaml-re ocaml-lastfm/arm64
    • Implicit dependency: ocaml-re ocaml-lastfm/armel
    • Implicit dependency: ocaml-re ocaml-lastfm/armhf
    • Implicit dependency: ocaml-re ocaml-lastfm/i386
    • Implicit dependency: ocaml-re ocaml-lastfm/mips64el
    • Implicit dependency: ocaml-re ocaml-lastfm/ppc64el
    • Implicit dependency: ocaml-re ocaml-lastfm/s390x
    • Implicit dependency: ocaml-re ocamldap/amd64
    • Implicit dependency: ocaml-re ocamldap/arm64
    • Implicit dependency: ocaml-re ocamldap/armel
    • Implicit dependency: ocaml-re ocamldap/armhf
    • Implicit dependency: ocaml-re ocamldap/i386
    • Implicit dependency: ocaml-re ocamldap/mips64el
    • Implicit dependency: ocaml-re ocamldap/ppc64el
    • Implicit dependency: ocaml-re ocamldap/s390x
    • Implicit dependency: ocaml-re ocamlformat/amd64
    • Implicit dependency: ocaml-re ocamlformat/arm64
    • Implicit dependency: ocaml-re ocamlformat/armel
    • Implicit dependency: ocaml-re ocamlformat/armhf
    • Implicit dependency: ocaml-re ocamlformat/i386
    • Implicit dependency: ocaml-re ocamlformat/mips64el
    • Implicit dependency: ocaml-re ocamlformat/ppc64el
    • Implicit dependency: ocaml-re ocamlformat/s390x
    • Implicit dependency: ocaml-re pgocaml/amd64 (not considered)
    • Implicit dependency: ocaml-re pgocaml/arm64 (not considered)
    • Implicit dependency: ocaml-re pgocaml/armel (not considered)
    • Implicit dependency: ocaml-re pgocaml/armhf (not considered)
    • Implicit dependency: ocaml-re pgocaml/i386 (not considered)
    • Implicit dependency: ocaml-re pgocaml/mips64el (not considered)
    • Implicit dependency: ocaml-re pgocaml/ppc64el (not considered)
    • Implicit dependency: ocaml-re pgocaml/s390x (not considered)
    • Implicit dependency: ocaml-re tyxml/amd64 (not considered)
    • Implicit dependency: ocaml-re tyxml/arm64 (not considered)
    • Implicit dependency: ocaml-re tyxml/armel
    • Implicit dependency: ocaml-re tyxml/armhf
    • Implicit dependency: ocaml-re tyxml/i386
    • Implicit dependency: ocaml-re tyxml/mips64el
    • Implicit dependency: ocaml-re tyxml/ppc64el (not considered)
    • Implicit dependency: ocaml-re tyxml/s390x (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-re.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• openjdk-11 (- to 11.0.25~5ea-1)
  • Migration status for openjdk-11 (- to 11.0.25~5ea-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.25~5ea-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 ♻
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• openjdk-17 (17.0.12+7-2 to 17.0.13~6ea-1)
  • Migration status for openjdk-17 (17.0.12+7-2 to 17.0.13~6ea-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/openjdk-17.html
    • autopkgtest for openjdk-17/17.0.13~6ea-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), 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 ♻
• openvlbi (3.0.2-2.1 to 3.0.2-3)
  • Migration status for openvlbi (3.0.2-2.1 to 3.0.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvlbi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• power-profiles-daemon (0.22-1 to 0.23-1)
  • Migration status for power-profiles-daemon (0.22-1 to 0.23-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/power-profiles-daemon.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• puredata (0.55.0+ds-1 to 0.55.1+ds-1)
  • Migration status for puredata (0.55.0+ds-1 to 0.55.1+ds-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puredata.html
    • autopkgtest for puredata/0.55.1+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
    • 4 days old (needed 2 days)
• python-calmjs.parse (1.2.5-3 to 1.2.5-4)
  • Migration status for python-calmjs.parse (1.2.5-3 to 1.2.5-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating python-calmjs.parse will fix bugs in testing: #1080226
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-calmjs.parse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-calmjs.types (1.0.1-3 to 1.0.1-4)
  • Migration status for python-calmjs.types (1.0.1-3 to 1.0.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating python-calmjs.types will fix bugs in testing: #1080227
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-calmjs.types.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-django-pyscss (2.0.3-2 to 2.0.3-3)
  • Migration status for python-django-pyscss (2.0.3-2 to 2.0.3-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-django-pyscss will fix bugs in testing: #1079262
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-pyscss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-editor (1.0.3-7 to 1.0.3-8)
  • Migration status for python-editor (1.0.3-7 to 1.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 4 of 5 days old
  • Additional info:
    • Updating python-editor will fix bugs in testing: #1080279
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-editor.html
    • autopkgtest for python-editor/1.0.3-8: 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-flask-seeder (1.2.0-3 to 1.2.0-4)
  • Migration status for python-flask-seeder (1.2.0-3 to 1.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 4 of 5 days old
  • Additional info:
    • Updating python-flask-seeder will fix bugs in testing: #1080280
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-flask-seeder.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-hypothesis (6.111.2-1 to 6.112.0-1)
  • Migration status for python-hypothesis (6.111.2-1 to 6.112.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-hypothesis/6.112.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-hypothesis/blocked-on-ci-infra: riscv64: Failed (not a regression)
    • autopkgtest for twisted/24.3.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Failed (not a regression), 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-hypothesis.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-mujson (1.4-2 to 1.4-3)
  • Migration status for python-mujson (1.4-2 to 1.4-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating python-mujson will fix bugs in testing: #1080281
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mujson.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-pyhcl (0.4.4-3 to 0.4.4-4)
  • Migration status for python-pyhcl (0.4.4-3 to 0.4.4-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:
    • Updating python-pyhcl will fix bugs in testing: #1080283
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyhcl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-rosettasciio (- to 0.4-3)
  • Migration status for python-rosettasciio (- to 0.4-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-rosettasciio python-sparse (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-rosettasciio.html
    • autopkgtest for python-rosettasciio/0.4-3: amd64: Pass, armhf: Pass, ppc64el: Pass
    • Waiting for reproducibility test results on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• python-spur (0.3.21-3 to 0.3.23-1)
  • Migration status for python-spur (0.3.21-3 to 0.3.23-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for locket/n/a: riscv64: 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-spur.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-threadloop (- to 1.0.2-2)
  • Migration status for python-threadloop (- to 1.0.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/python-threadloop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-xstatic (1.0.3-2 to 1.0.3-3)
  • Migration status for python-xstatic (1.0.3-2 to 1.0.3-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-xstatic will fix bugs in testing: #1080284
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xstatic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-xstatic-magic-search (0.2.5.1-4 to 0.2.5.1-5)
  • Migration status for python-xstatic-magic-search (0.2.5.1-4 to 0.2.5.1-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:
    • Updating python-xstatic-magic-search will fix bugs in testing: #1080285
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xstatic-magic-search.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-xstatic-mdi (1.6.50.2-3 to 1.6.50.2-4)
  • Migration status for python-xstatic-mdi (1.6.50.2-3 to 1.6.50.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:
    • Updating python-xstatic-mdi will fix bugs in testing: #1080286
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xstatic-mdi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python3-stdlib-extensions (3.12.5-3 to 3.12.6-1)
  • Migration status for python3-stdlib-extensions (3.12.5-3 to 3.12.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/p/python3-stdlib-extensions.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• qt6-serialbus (6.6.2-2 to 6.6.2-3)
  • Migration status for qt6-serialbus (6.6.2-2 to 6.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qt6-serialbus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-broom.mixed (0.2.9.4-1 to 0.2.9.5-1)
  • Migration status for r-cran-broom.mixed (0.2.9.4-1 to 0.2.9.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/r/r-cran-broom.mixed.html
    • autopkgtest for r-cran-broom.mixed/0.2.9.5-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 ♻
    • Reproducible on i386 - info ♻
• r-cran-geepack (1.3.10-1 to 1.3.11.1-1)
  • Migration status for r-cran-geepack (1.3.10-1 to 1.3.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-geepack/1.3.11.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for r-cran-lava/1.7.3+dfsg-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Regression or new test ♻ (reference ♻), 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/r/r-cran-geepack.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• r-cran-hdf5r (1.3.9+dfsg-2 to 1.3.11+dfsg-1)
  • Migration status for r-cran-hdf5r (1.3.9+dfsg-2 to 1.3.11+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-cran-hdf5r.html
    • autopkgtest for r-cran-hdf5r/1.3.11+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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• razercfg (0.43-3 to 0.43-4)
  • Migration status for razercfg (0.43-3 to 0.43-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/r/razercfg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rsskit (0.4-1 to 0.4-2)
  • Migration status for rsskit (0.4-1 to 0.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsskit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-async-native-tls (- to 0.5.0-1)
  • Migration status for rust-async-native-tls (- to 0.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-native-tls.html
    • autopkgtest for rust-async-native-tls/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-curve25519-dalek (4.1.3+20240618+dfsg-6 to 4.1.3+20240618+dfsg-7)
  • Migration status for rust-curve25519-dalek (4.1.3+20240618+dfsg-6 to 4.1.3+20240618+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-curve25519-dalek/4.1.3+20240618+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: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for rust-rusty-paseto/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-curve25519-dalek.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-dbus-secret-service (- to 4.0.2-1)
  • Migration status for rust-dbus-secret-service (- to 4.0.2-1): 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.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • autopkgtest for rust-dbus-secret-service/blocked-on-ci-infra: riscv64: Regression or new test ♻
    • Too young, only 4 of 5 days old
  • 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-gstreamer-video (0.23.0-3 to 0.23.0-5)
  • Migration status for rust-gstreamer-video (0.23.0-3 to 0.23.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gstreamer-video.html
    • autopkgtest for rust-gstreamer-video/0.23.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• rust-pgp (- to 0.13.2-2)
  • Migration status for rust-pgp (- to 0.13.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-pgp/0.13.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): rust-pgp rust-buffer-redux
    • Build-Depends(-Arch): rust-pgp rust-k256 (not considered)
    • Build-Depends(-Arch): rust-pgp rust-ocb3 (not considered)
    • Build-Depends(-Arch): rust-pgp rust-rsa (not considered)
    • Depends: rust-pgp rust-buffer-redux
    • Depends: rust-pgp rust-curve25519-dalek (not considered)
    • Depends: rust-pgp rust-k256 (not considered)
    • Depends: rust-pgp rust-ocb3 (not considered)
    • Depends: rust-pgp rust-rsa (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pgp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• rust-plotters (0.3.5-2 to 0.3.5-4)
  • Migration status for rust-plotters (0.3.5-2 to 0.3.5-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): rust-plotters rust-ttf-parser
    • Depends: rust-plotters rust-ttf-parser
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-plotters.html
    • autopkgtest for rust-plotters/0.3.5-4: 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 ♻
    • Reproducible on i386 - info ♻
• rust-secret-service (- to 4.0.0-1)
  • Migration status for rust-secret-service (- to 4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-secret-service/4.0.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-secret-service.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-sequoia-keystore-tpm (- to 0.1.0-1)
  • Migration status for rust-sequoia-keystore-tpm (- to 0.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-sequoia-keystore-tpm rust-sequoia-keystore-backend (not considered)
    • Depends: rust-sequoia-keystore-tpm rust-sequoia-keystore-backend (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-keystore-tpm.html
    • autopkgtest for rust-sequoia-keystore-tpm/0.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• rust-serde-derive (1.0.203-1 to 1.0.210-1)
  • Migration status for rust-serde-derive (1.0.203-1 to 1.0.210-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-serde-derive/1.0.210-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for rust-vmm-sys-util/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • Too young, only 4 of 5 days old
    • Implicit dependency: rust-serde-derive rust-serde (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-serde-derive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-ttf-parser (0.19.1-2 to 0.24.1-1)
  • Migration status for rust-ttf-parser (0.19.1-2 to 0.24.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
    • Implicit dependency: rust-ttf-parser rust-owned-ttf-parser
    • Implicit dependency: rust-ttf-parser rust-plotters
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ttf-parser.html
    • autopkgtest for rust-ttf-parser/0.24.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: No tests, superficial or marked flaky ♻ (reference ♻), 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 ♻
• setuptools (70.3.0-2 to 74.1.2-2)
  • Migration status for setuptools (70.3.0-2 to 74.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/s/setuptools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• sip-tester (1:3.7.2-1 to 1:3.7.3-1)
  • Migration status for sip-tester (1:3.7.2-1 to 1:3.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sip-tester would introduce bugs in testing: #1081521
    • 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sip-tester.html
    • Waiting for reproducibility test results on armhf - info ♻
• sphinxcontrib-programoutput (0.17-3 to 0.17-4)
  • Migration status for sphinxcontrib-programoutput (0.17-3 to 0.17-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:
    • Updating sphinxcontrib-programoutput will fix bugs in testing: #1080237
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinxcontrib-programoutput.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• spirv-llvm-translator-14 (- to 14.0.4-2)
  • Migration status for spirv-llvm-translator-14 (- to 14.0.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Build-Depends(-Arch): spirv-llvm-translator-14 llvm-toolchain-14 (not considered)
    • Depends: spirv-llvm-translator-14 llvm-toolchain-14 (not considered)
  • 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.4-2: 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• sslsniff (0.8-9 to 0.8+git20111017-1)
  • Migration status for sslsniff (0.8-9 to 0.8+git20111017-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/sslsniff.html
    • autopkgtest for sslsniff/0.8+git20111017-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 ♻
• stravalib (- to 2.0-1)
  • Migration status for stravalib (- to 2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for stravalib/2.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 ♻
• swiftlang (- to 5.7.3-2)
  • Migration status for swiftlang (- to 5.7.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swiftlang.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• systempreferences.app (1.2.0-2 to 1.2.1-1)
  • Migration status for systempreferences.app (1.2.0-2 to 1.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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/systempreferences.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• tcpspy (- to 1.7d-16)
  • Migration status for tcpspy (- to 1.7d-16): 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/tcpspy.html
    • autopkgtest for tcpspy/1.7d-16: 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 ♻
• termshark (2.4.0-1 to 2.4.0-2)
  • Migration status for termshark (2.4.0-1 to 2.4.0-2): Will attempt migration (Any information below is purely informational)
    • Built-Using: termshark golang-1.22
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/termshark.html
    • autopkgtest for termshark/2.4.0-2: 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 ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• tntnet (3.0-3.1 to 3.0-4)
  • Migration status for tntnet (3.0-3.1 to 3.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/t/tntnet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• tuba (0.8.2-2 to 0.8.4-1)
  • Migration status for tuba (0.8.2-2 to 0.8.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tuba.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• unit-translator (- to 0.3-1)
  • Migration status for unit-translator (- to 0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for unit-translator/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 ♻
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unit-translator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• util-linux (2.40.2-7 to 2.40.2-8)
  • Migration status for util-linux (2.40.2-7 to 2.40.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for netavark/1.12.1-3: amd64: Regression or new test ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for sssd/2.9.5-3: 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.2-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: 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/u/util-linux.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• vo-aacenc (0.1.3-2 to 0.1.3-3)
  • Migration status for vo-aacenc (0.1.3-2 to 0.1.3-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/v/vo-aacenc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• x-tile (3.3+git20220708.9ec59c9-1 to 3.3+git20220708.9ec59c9-2)
  • Migration status for x-tile (3.3+git20220708.9ec59c9-1 to 3.3+git20220708.9ec59c9-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/x/x-tile.html
    • autopkgtest for x-tile/3.3+git20220708.9ec59c9-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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• zypper (1.14.76-1 to 1.14.77-1)
  • Migration status for zypper (1.14.76-1 to 1.14.77-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): zypper libzypp
    • Depends: zypper libzypp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zypper.html
    • autopkgtest for zypper/1.14.77-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), 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 ♻
• amdgcn-tools-18 (18.1 to 18.2)
  • Migration status for amdgcn-tools-18 (18.1 to 18.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): amdgcn-tools-18 llvm-toolchain-19 (not considered)
    • Depends: amdgcn-tools-18 llvm-toolchain-19 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amdgcn-tools-18.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 5 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• apscheduler (3.10.4-1 to 3.10.4-2)
  • Migration status for apscheduler (3.10.4-1 to 3.10.4-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating apscheduler will fix bugs in testing: #1080272
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apscheduler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• atuin (- to 18.3.0-2)
  • Migration status for atuin (- to 18.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): atuin rust-rusty-paseto (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): atuin dh-shell-completions (not considered)
    • Build-Depends(-Arch): atuin rust-rusty-paserk/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/atuin.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• azote (- to 1.12.9-2)
  • Migration status for azote (- to 1.12.9-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/azote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• bpm-tools (0.3-4 to 0.3-5)
  • Migration status for bpm-tools (0.3-4 to 0.3-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bpm-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• buteo-sync-plugin-carddav (- to 0.1.10-2)
  • Migration status for buteo-sync-plugin-carddav (- to 0.1.10-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): buteo-sync-plugin-carddav nemo-qml-plugin-contacts (not considered)
    • Depends: buteo-sync-plugin-carddav nemo-qml-plugin-contacts (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/buteo-sync-plugin-carddav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• clonezilla (5.6.16-1 to 5.6.18-1)
  • Migration status for clonezilla (5.6.16-1 to 5.6.18-1): Will attempt migration (Any information below is purely informational)
  • 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 ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• cwiid (0.6.91-9 to 0.6.91-10)
  • Migration status for cwiid (0.6.91-9 to 0.6.91-10): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cwiid.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• cyborg (- to 12.0.0-1)
  • Migration status for cyborg (- to 12.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/c/cyborg.html
    • autopkgtest for cyborg/12.0.0-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 ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• dbus-deviation (0.6.0-2 to 0.6.1+git20240205+f5e6774af579-1)
  • Migration status for dbus-deviation (0.6.0-2 to 0.6.1+git20240205+f5e6774af579-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating dbus-deviation will fix bugs in testing: #1080101
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dbus-deviation.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• dh-clojure (- to 0.0.0)
  • Migration status for dh-clojure (- to 0.0.0): 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-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 ♻
    • 5 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• dh-shell-completions (- to 0.0.2)
  • Migration status for dh-shell-completions (- to 0.0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-shell-completions.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• drbl (5.3.3-1 to 5.3.4-1)
  • Migration status for drbl (5.3.3-1 to 5.3.4-1): Will attempt migration (Any information below is purely informational)
  • 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 ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• eccodes (2.36.1-1 to 2.37.0-1)
  • Migration status for eccodes (2.36.1-1 to 2.37.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eccodes.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 ♻
    • 5 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• expeyes (5.3.1+repack-6 to 5.3.1+repack-8)
  • Migration status for expeyes (5.3.1+repack-6 to 5.3.1+repack-8): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/expeyes.html
    • autopkgtest for expeyes/5.3.1+repack-8: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: Pass, 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 armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• fnonlinear (4021.81-1 to 4041.82-1)
  • Migration status for fnonlinear (4021.81-1 to 4041.82-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fnonlinear.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• freetype-py (2.4.0-2 to 2.5.1-1)
  • Migration status for freetype-py (2.4.0-2 to 2.5.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freetype-py.html
    • autopkgtest for freetype-py/2.5.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
    • 5 days old (needed 5 days)
• gnome-boxes (47~beta-1 to 47~beta-2)
  • Migration status for gnome-boxes (47~beta-1 to 47~beta-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-boxes.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• gnubg (1.07.001-3 to 1.08.003-1)
  • Migration status for gnubg (1.07.001-3 to 1.08.003-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gnubg gtkglext (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnubg.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 ♻
    • 5 days old (needed 5 days)
• goban (- to 1.1-8)
  • Migration status for goban (- to 1.1-8): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goban.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• golang-1.22 (1.22.6-1 to 1.22.7-1)
  • Migration status for golang-1.22 (1.22.6-1 to 1.22.7-1): 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.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 5 days old (needed 5 days)
• graph-tool (- to 2.77+ds-1)
  • Migration status for graph-tool (- to 2.77+ds-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 graph-tool/2.77+ds-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends-Indep: graph-tool basemap (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graph-tool.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 5 days old (needed 5 days)
• htmx (- to 2.0.2-2)
  • Migration status for htmx (- to 2.0.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/htmx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• indie-wiki-buddy (- to 3.10.1-1)
  • Migration status for indie-wiki-buddy (- to 3.10.1-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/indie-wiki-buddy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• isl (0.26-3 to 0.27-1)
  • Migration status for isl (0.26-3 to 0.27-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/isl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• kf6-extra-cmake-modules (- to 6.6.0-1)
  • Migration status for kf6-extra-cmake-modules (- to 6.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by zecoucou@free.fr
    • Not built on buildd: arch all binaries uploaded by zecoucou@free.fr, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kf6-extra-cmake-modules.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• kooha (- to 2.3.0-2)
  • Migration status for kooha (- to 2.3.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kooha.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• libcommandable-perl (0.12-1 to 0.14-1)
  • Migration status for libcommandable-perl (0.12-1 to 0.14-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: libcommandable-perl libattribute-storage-perl (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcommandable-perl.html
    • autopkgtest for libcommandable-perl/0.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• libhinawa (4.0.2-1 to 4.0.2-2)
  • Migration status for libhinawa (4.0.2-1 to 4.0.2-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhinawa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 5 days old (needed 5 days)
• libnet-sip-perl (0.837-1 to 0.838-1)
  • Migration status for libnet-sip-perl (0.837-1 to 0.838-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnet-sip-perl.html
    • autopkgtest for libnet-sip-perl/0.838-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 ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• librepcb (- to 1.1.0+dfsg-1)
  • Migration status for librepcb (- to 1.1.0+dfsg-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/librepcb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• libvirt (10.6.0-1 to 10.7.0-2)
  • Migration status for libvirt (10.6.0-1 to 10.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libvirt/10.7.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for oz/0.17.0-5.4: amd64: Regression or new test ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
  • Additional info:
    • Updating libvirt will fix bugs in testing: #1064126, #1080218
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvirt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• linux (6.10.6-1 to 6.10.9-1)
  • Migration status for linux (6.10.6-1 to 6.10.9-1): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: linux linux-signed-amd64
    • Implicit dependency: linux linux-signed-arm64
  • Additional info:
    • Updating linux will fix bugs in testing: #1079394
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux.html
    • autopkgtest for linux/6.10.9-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
    • 5 days old (needed 5 days)
• linux-signed-amd64 (6.10.6+1 to 6.10.9+1)
  • Migration status for linux-signed-amd64 (6.10.6+1 to 6.10.9+1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): linux-signed-amd64 linux
    • Built-Using: linux-signed-amd64 linux
    • Depends: linux-signed-amd64 linux
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-signed-amd64.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 5 days old (needed 5 days)
• linux-signed-arm64 (6.10.6+1 to 6.10.9+1)
  • Migration status for linux-signed-arm64 (6.10.6+1 to 6.10.9+1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): linux-signed-arm64 linux
    • Built-Using: linux-signed-arm64 linux
    • Depends: linux-signed-arm64 linux
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 5 days old (needed 5 days)
• llvm-toolchain-17 (1:17.0.6-15 to 1:17.0.6-18)
  • Migration status for llvm-toolchain-17 (1:17.0.6-15 to 1:17.0.6-18): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvm-toolchain-17.html
    • autopkgtest for llvm-toolchain-17/1:17.0.6-18: 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• llvm-toolchain-18 (1:18.1.8-9 to 1:18.1.8-11)
  • Migration status for llvm-toolchain-18 (1:18.1.8-9 to 1:18.1.8-11): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for llvm-toolchain-18/1:18.1.8-11: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Test in progress (will not be considered a regression), riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvm-toolchain-18.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• llvm-toolchain-19 (- to 1:19.1.0~++rc4-5)
  • Migration status for llvm-toolchain-19 (- to 1:19.1.0~++rc4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for llvm-toolchain-19/1:19.1.0~++rc4-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Test in progress (will not be considered a regression), riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvm-toolchain-19.html
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• lomiri-content-hub (- to 2.0.0-2)
  • Migration status for lomiri-content-hub (- to 2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lomiri-content-hub/2.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/l/lomiri-content-hub.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• lomiri-indicator-transfer (1.1.0-3 to 1.1.0-4)
  • Migration status for lomiri-indicator-transfer (1.1.0-3 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-indicator-transfer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• lxml-html-clean (0.2.1-1 to 0.2.2-1)
  • Migration status for lxml-html-clean (0.2.1-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxml-html-clean.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• macaulay2 (1.24.05+ds-4 to 1.24.05+ds-5)
  • Migration status for macaulay2 (1.24.05+ds-4 to 1.24.05+ds-5): 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 macaulay2/1.24.05+ds-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Failed (not a regression), ppc64el: Failed (not a regression), s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/macaulay2.html
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 5 days old (needed 5 days)
• manif (0.0.5-2 to 0.0.5-5)
  • Migration status for manif (0.0.5-2 to 0.0.5-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/manif.html
    • autopkgtest for manif/0.0.5-5: amd64: Pass, arm64: Pass, armel: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• meta-kde (5:148 to 5:149)
  • Migration status for meta-kde (5:148 to 5:149): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 5 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meta-kde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mimedefang (3.4.1-1 to 3.5-1)
  • Migration status for mimedefang (3.4.1-1 to 3.5-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mimedefang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• modsecurity (3.0.12-1.1 to 3.0.13-1)
  • Migration status for modsecurity (3.0.12-1.1 to 3.0.13-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/modsecurity.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• modsecurity-apache (2.9.7-1 to 2.9.8-1)
  • Migration status for modsecurity-apache (2.9.7-1 to 2.9.8-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/modsecurity-apache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• modsecurity-crs (3.3.5-2 to 3.3.6-1)
  • Migration status for modsecurity-crs (3.3.5-2 to 3.3.6-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/modsecurity-crs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• mrbuild (1.12-1 to 1.13-1)
  • Migration status for mrbuild (1.12-1 to 1.13-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrbuild.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• mrpt (1:2.13.7+ds-2 to 1:2.13.8+ds-1)
  • Migration status for mrpt (1:2.13.7+ds-2 to 1:2.13.8+ds-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrpt.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• nauty (2.8.8+ds-5 to 2.8.9+ds-1)
  • Migration status for nauty (2.8.8+ds-5 to 2.8.9+ds-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating nauty will fix bugs in testing: #1080117
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nauty.html
    • autopkgtest for nauty/2.8.9+ds-1: 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• nbdkit (1.40.2-2 to 1.40.3-1)
  • Migration status for nbdkit (1.40.2-2 to 1.40.3-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • missing build on mips64el
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nbdkit.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 5 days old (needed 5 days)
• ncbi-tools6 (6.1.20170106+dfsg2-3 to 6.1.20170106+dfsg2-4)
  • Migration status for ncbi-tools6 (6.1.20170106+dfsg2-3 to 6.1.20170106+dfsg2-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating ncbi-tools6 will fix bugs in testing: #1078825
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ncbi-tools6.html
    • autopkgtest for ncbi-tools6/6.1.20170106+dfsg2-4: 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 ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 5 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• partclone (0.3.32+repack-2 to 0.3.32+repack-3)
  • Migration status for partclone (0.3.32+repack-2 to 0.3.32+repack-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/partclone.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• picard (2.12.2-1 to 2.12.3-1)
  • Migration status for picard (2.12.2-1 to 2.12.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• precious (0.7.3-1 to 0.7.3-2)
  • Migration status for precious (0.7.3-1 to 0.7.3-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/precious.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• py-canary (- to 0.5.4-1)
  • Migration status for py-canary (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/py-canary.html
    • autopkgtest for py-canary/0.5.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
    • 5 days old (needed 2 days)
• pycsspeechtts (- to 1.0.8-1)
  • Migration status for pycsspeechtts (- to 1.0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycsspeechtts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• pykulersky (- to 0.5.5-1)
  • Migration status for pykulersky (- to 0.5.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pykulersky.html
    • autopkgtest for pykulersky/0.5.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
    • 5 days old (needed 2 days)
• python-aenum (- to 3.1.15-2)
  • Migration status for python-aenum (- to 3.1.15-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aenum.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-aiopvpc (4.3.1-2 to 4.3.1-3)
  • Migration status for python-aiopvpc (4.3.1-2 to 4.3.1-3): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiopvpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-aiosenz (- to 1.0.0-2)
  • Migration status for python-aiosenz (- 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/p/python-aiosenz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-aiosomecomfort (- to 0.0.25-2)
  • Migration status for python-aiosomecomfort (- to 0.0.25-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiosomecomfort.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-aiotractive (- to 0.6.0-2)
  • Migration status for python-aiotractive (- to 0.6.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiotractive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-aiovlc (- to 0.4.2-2)
  • Migration status for python-aiovlc (- to 0.4.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: python-aiovlc ruff (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiovlc.html
    • autopkgtest for python-aiovlc/0.4.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 ♻, ppc64el: Pass, 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 ♻
    • 5 days old (needed 5 days)
• python-amberelectric (- to 2.0.0-2)
  • Migration status for python-amberelectric (- to 2.0.0-2): Will attempt migration (Any information below is purely informational)
    • Build-Depends-Indep: python-amberelectric python-aenum
    • Depends: python-amberelectric python-aenum
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-amberelectric.html
    • autopkgtest for python-amberelectric/2.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
    • 5 days old (needed 2 days)
• python-asyncarve (- to 0.1.1-1)
  • Migration status for python-asyncarve (- 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 zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-asyncarve.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 ♻
    • 5 days old (needed 5 days)
• python-asyncsleepiq (- to 1.5.3-1)
  • Migration status for python-asyncsleepiq (- to 1.5.3-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-asyncsleepiq.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 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: Regression or new test ♻, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
    • Build-Depends-Indep: python-bellows python-pure-pcapy3 (not considered)
    • Depends: python-bellows python-pure-pcapy3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bellows.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-bimmer-connected (- to 0.16.3-1)
  • Migration status for python-bimmer-connected (- to 0.16.3-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-bimmer-connected.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-crownstone-cloud (- to 1.4.11-2)
  • Migration status for python-crownstone-cloud (- to 1.4.11-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-crownstone-cloud.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-fnv-hash-fast (- to 0.5.0-2)
  • Migration status for python-fnv-hash-fast (- to 0.5.0-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fnv-hash-fast.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-glances-api (- to 0.4.1-1)
  • Migration status for python-glances-api (- 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 edward@4angle.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-glances-api.html
    • autopkgtest for python-glances-api/0.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 5 days old (needed 2 days)
• python-globus-sdk (3.44.0-1 to 3.45.0-1)
  • Migration status for python-globus-sdk (3.44.0-1 to 3.45.0-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-globus-sdk.html
    • autopkgtest for python-globus-sdk/3.45.0-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-hyperion-py (- to 0.7.5-2)
  • Migration status for python-hyperion-py (- to 0.7.5-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-hyperion-py.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-jaeger-client (- to 4.8.0-1)
  • Migration status for python-jaeger-client (- to 4.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-jaeger-client/4.8.0-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
    • Build-Depends-Indep: python-jaeger-client python-threadloop
    • Depends: python-jaeger-client python-threadloop
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jaeger-client.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-multiurl (- to 0.3.1-1)
  • Migration status for python-multiurl (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by gspreemann@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-multiurl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-parsl (2024.08.26+ds-1 to 2024.09.02+ds-1)
  • Migration status for python-parsl (2024.08.26+ds-1 to 2024.09.02+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-parsl ipyparallel (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-parsl.html
    • autopkgtest for python-parsl/2024.09.02+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
    • 5 days old (needed 2 days)
• python-potr (1.0.2-5 to 1.0.2-6)
  • Migration status for python-potr (1.0.2-5 to 1.0.2-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating python-potr will fix bugs in testing: #1080282
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-potr.html
    • autopkgtest for python-potr/1.0.2-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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-pure-pcapy3 (- to 1.0.1-1)
  • Migration status for python-pure-pcapy3 (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pure-pcapy3.html
    • autopkgtest for python-pure-pcapy3/1.0.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: 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 ♻
    • 5 days old (needed 5 days)
• python-ratelimitqueue (- to 0.2.2-1.1)
  • Migration status for python-ratelimitqueue (- to 0.2.2-1.1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ratelimitqueue.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-tktooltip (3.0.0-2 to 3.0.0-3)
  • Migration status for python-tktooltip (3.0.0-2 to 3.0.0-3): Will attempt migration (Any information below is purely informational)
  • 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 ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• qr-tools (2.1~bzr52-1 to 2.1~bzr52-2)
  • Migration status for qr-tools (2.1~bzr52-1 to 2.1~bzr52-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qr-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• qtmir (0.8.0~git20240306.de639c3-2 to 0.8.0~git20240306.de639c3-3)
  • Migration status for qtmir (0.8.0~git20240306.de639c3-2 to 0.8.0~git20240306.de639c3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): qtmir lomiri-content-hub (not considered)
    • Depends: qtmir lomiri-content-hub (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtmir.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• r-cran-httr2 (1.0.2-1 to 1.0.3-1)
  • Migration status for r-cran-httr2 (1.0.2-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-httr2.html
    • autopkgtest for r-cran-httr2/1.0.3-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 ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• ruby3.3 (3.3.4-2 to 3.3.5-2)
  • Migration status for ruby3.3 (3.3.4-2 to 3.3.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby3.3/3.3.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for ruby3.3/n/a: riscv64: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating ruby3.3 will fix bugs in testing: #1077462
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby3.3.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 5 days old (needed 5 days)
• rust-adblock (- to 0.8.6-1)
  • Migration status for rust-adblock (- to 0.8.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-adblock-dev/amd64 has unsatisfiable dependency
    • librust-adblock-dev/arm64 has unsatisfiable dependency
    • librust-adblock-dev/armel has unsatisfiable dependency
    • librust-adblock-dev/armhf has unsatisfiable dependency
    • librust-adblock-dev/i386 has unsatisfiable dependency
    • librust-adblock-dev/mips64el has unsatisfiable dependency
    • librust-adblock-dev/ppc64el has unsatisfiable dependency
    • librust-adblock-dev/s390x has unsatisfiable dependency
    • autopkgtest for rust-adblock/0.8.6-1: riscv64: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-adblock.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-dysk (2.9.0-2 to 2.9.1-1)
  • Migration status for rust-dysk (2.9.0-2 to 2.9.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 amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-dysk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-inquire (- to 0.7.5-2)
  • Migration status for rust-inquire (- to 0.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-inquire/0.7.5-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-inquire.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-r-description (- to 0.1.0-1)
  • Migration status for rust-r-description (- to 0.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-r-description.html
    • Build-Depends(-Arch): rust-r-description rust-deb822-lossless
    • Depends: rust-r-description rust-deb822-lossless
  • Additional info:
    • autopkgtest for rust-r-description/0.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
    • 5 days old (needed 2 days)
• rust-tls-parser (0.11.0-3 to 0.12.1-1)
  • Migration status for rust-tls-parser (0.11.0-3 to 0.12.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-tls-parser rust-sniffglue (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tls-parser.html
    • autopkgtest for rust-tls-parser/0.12.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
    • 5 days old (needed 2 days)
• secrets (- to 9.6-2)
  • Migration status for secrets (- to 9.6-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/secrets.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• selinux-gui (- to 3.7-2)
  • Migration status for selinux-gui (- to 3.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • policycoreutils-gui/amd64 has unsatisfiable dependency
    • policycoreutils-gui/arm64 has unsatisfiable dependency
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/selinux-gui.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 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 ♻
    • 5 days old (needed 5 days)
• sphinx-jinja2-compat (- to 0.3.0-1)
  • Migration status for sphinx-jinja2-compat (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by 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/s/sphinx-jinja2-compat.html
    • autopkgtest for sphinx-jinja2-compat/0.3.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 ♻
    • 5 days old (needed 5 days)
• spirv-llvm-translator-19 (- to 19.~~+git20240826-4)
  • Migration status for spirv-llvm-translator-19 (- to 19.~~+git20240826-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): spirv-llvm-translator-19 llvm-toolchain-19 (not considered)
    • Depends: spirv-llvm-translator-19 llvm-toolchain-19 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spirv-llvm-translator-19.html
    • autopkgtest for spirv-llvm-translator-19/19.~~+git20240826-4: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: Pass, 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 ♻
    • 5 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• sword (1.9.0+dfsg-6 to 1.9.0+dfsg-7)
  • Migration status for sword (1.9.0+dfsg-6 to 1.9.0+dfsg-7): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sword.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• theme-d (5.1.2-1 to 5.1.3-1)
  • Migration status for theme-d (5.1.2-1 to 5.1.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/theme-d.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• tipp10 (3.3.1-1 to 3.3.2-1)
  • Migration status for tipp10 (3.3.1-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tipp10.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• unearth (0.17.1-1 to 0.17.2-1)
  • Migration status for unearth (0.17.1-1 to 0.17.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unearth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• vdr-plugin-markad (3.4.12-1 to 4.1.7-1)
  • Migration status for vdr-plugin-markad (3.4.12-1 to 4.1.7-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdr-plugin-markad.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 ♻
    • 5 days old (needed 5 days)
• webkit2gtk (2.44.3-1 to 2.44.4-1)
  • Migration status for webkit2gtk (2.44.3-1 to 2.44.4-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webkit2gtk.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 5 days old (needed 5 days)
• xdg-desktop-portal-hyprland (- to 1.3.3-1)
  • Migration status for xdg-desktop-portal-hyprland (- to 1.3.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdg-desktop-portal-hyprland.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• asterisk (- to 1:20.9.3~dfsg+~cs6.14.60671435-1)
  • Migration status for asterisk (- to 1:20.9.3~dfsg+~cs6.14.60671435-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asterisk would introduce bugs in testing: #1031046
    • Build-Depends(-Arch): asterisk dahdi-linux (not considered)
    • Build-Depends(-Arch): asterisk dahdi-tools (not considered)
    • Build-Depends(-Arch): asterisk libss7 (not considered)
    • Build-Depends(-Arch): asterisk openr2 (not considered)
    • Depends: asterisk dahdi-tools (not considered)
    • Depends: asterisk libss7 (not considered)
    • Depends: asterisk openr2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk.html
    • autopkgtest for asterisk/1:20.9.3~dfsg+~cs6.14.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 ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 6 days old (needed 2 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• kpatch (0.9.9-2 to 0.9.9-3)
  • Migration status for kpatch (0.9.9-2 to 0.9.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Updating kpatch will fix bugs in testing: #1079032
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kpatch.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 6 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• kwayland-kf5 (- to 4:5.115.0-4)
  • Migration status for kwayland-kf5 (- to 4:5.115.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for kwayland/4:5.115.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for kwayland-kf5/4:5.115.0-4: 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/k/kwayland-kf5.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• libattribute-storage-perl (0.10-1 to 0.12-1)
  • Migration status for libattribute-storage-perl (0.10-1 to 0.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libattribute-storage-perl/0.12-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for libcircle-be-perl/0.173320-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: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • Build-Depends(-Arch): libattribute-storage-perl libmeta-perl
    • Depends: libattribute-storage-perl libmeta-perl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libattribute-storage-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• libsysstat (0.4.6-3 to 1.0.0-1~exp1)
  • Migration status for libsysstat (0.4.6-3 to 1.0.0-1~exp1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsysstat unsatisfiable Build-Depends(-Arch) on amd64: lxqt-build-tools (>= 2.0.0+really2.0.0~)
    • libsysstat unsatisfiable Build-Depends(-Arch) on arm64: lxqt-build-tools (>= 2.0.0+really2.0.0~)
    • libsysstat unsatisfiable Build-Depends(-Arch) on armel: lxqt-build-tools (>= 2.0.0+really2.0.0~)
    • libsysstat unsatisfiable Build-Depends(-Arch) on armhf: lxqt-build-tools (>= 2.0.0+really2.0.0~)
    • libsysstat unsatisfiable Build-Depends(-Arch) on i386: lxqt-build-tools (>= 2.0.0+really2.0.0~)
    • libsysstat unsatisfiable Build-Depends(-Arch) on mips64el: lxqt-build-tools (>= 2.0.0+really2.0.0~)
    • libsysstat unsatisfiable Build-Depends(-Arch) on ppc64el: lxqt-build-tools (>= 2.0.0+really2.0.0~)
    • libsysstat unsatisfiable Build-Depends(-Arch) on riscv64: lxqt-build-tools (>= 2.0.0+really2.0.0~)
    • libsysstat unsatisfiable Build-Depends(-Arch) on s390x: lxqt-build-tools (>= 2.0.0+really2.0.0~)
    • Not built on buildd: arch amd64 binaries uploaded by ajqlee
    • 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: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/libs/libsysstat.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)
• merkaartor (0.19.0+ds-5 to 0.20.0+ds-1)
  • Migration status for merkaartor (0.19.0+ds-5 to 0.20.0+ds-1): Will attempt migration (Any information below is purely informational)
    • Depends: merkaartor exiv2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/merkaartor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• openimageio (- to 2.5.15.0+dfsg-1)
  • Migration status for openimageio (- to 2.5.15.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): openimageio openvdb (not considered)
    • Depends: openimageio openvdb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): openimageio opencolorio
    • Depends: openimageio opencolorio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openimageio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• paperwork (- to 2.2.5-1)
  • Migration status for paperwork (- to 2.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for paperwork/2.2.5-1: 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/p/paperwork.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 6 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 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 ♻
    • 6 days old (needed 5 days)
• python-energyzero (- to 2.1.1-2)
  • Migration status for python-energyzero (- to 2.1.1-2): Will attempt migration (Any information below is purely informational)
    • Build-Depends-Indep: python-energyzero pytest-freezer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-energyzero.html
    • autopkgtest for python-energyzero/2.1.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
    • 6 days old (needed 2 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• rust-quote (1.0.36-1 to 1.0.37-1)
  • Migration status for rust-quote (1.0.36-1 to 1.0.37-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-impl-trait-for-tuples/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-mockall-derive/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-quote/1.0.37-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/rust-quote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• rust-rust-decimal (1.23.1-2 to 1.36.0-1)
  • Migration status for rust-rust-decimal (1.23.1-2 to 1.36.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-rhai/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-rust-decimal/1.36.0-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/rust-rust-decimal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• rust-sequoia-keystore (0.5.1-2 to 0.6.1-1)
  • Migration status for rust-sequoia-keystore (0.5.1-2 to 0.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-sequoia-keystore-dev/amd64 has unsatisfiable dependency
    • librust-sequoia-keystore-dev/arm64 has unsatisfiable dependency
    • librust-sequoia-keystore-dev/armel has unsatisfiable dependency
    • librust-sequoia-keystore-dev/armhf has unsatisfiable dependency
    • librust-sequoia-keystore-dev/i386 has unsatisfiable dependency
    • librust-sequoia-keystore-dev/mips64el has unsatisfiable dependency
    • librust-sequoia-keystore-dev/ppc64el has unsatisfiable dependency
    • librust-sequoia-keystore-dev/s390x has unsatisfiable dependency
    • autopkgtest for rust-sequoia-keystore/blocked-on-ci-infra: riscv64: Failed (not a regression)
    • Build-Depends(-Arch): rust-sequoia-keystore rust-sequoia-keystore-backend
    • Build-Depends(-Arch): rust-sequoia-keystore rust-sequoia-keystore-gpg-agent
    • Build-Depends(-Arch): rust-sequoia-keystore rust-sequoia-keystore-softkeys
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-sequoia-keystore.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• rust-syn (2.0.68-1 to 2.0.77-1)
  • Migration status for rust-syn (2.0.68-1 to 2.0.77-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-deluxe/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 ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-deluxe/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-mockall-derive/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-syn/2.0.77-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/rust-syn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• speech-dispatcher-contrib (0.11.5-4 to 0.11.5-5)
  • Migration status for speech-dispatcher-contrib (0.11.5-4 to 0.11.5-5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • 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
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 6 days old (needed 5 days)
• amgcl (1.4.3-6 to 1.4.3-7)
  • Migration status for amgcl (1.4.3-6 to 1.4.3-7): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 7 days old (needed 5 days)
• django-recurrence (1.11.1-1 to 1.12-2)
  • Migration status for django-recurrence (1.11.1-1 to 1.12-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-recurrence.html
    • autopkgtest for django-recurrence/1.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 7 days)
• firefox (- to 130.0-2)
  • Migration status for firefox (- to 130.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating firefox would introduce bugs in testing: #1017919, #817954, #992263, #993659
    • missing build on armhf
    • missing build on mips64el
    • arch:armhf 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 ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 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
  • 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 arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• gst-plugins-base1.0 (1.24.7-2 to 1.24.7-4)
  • Migration status for gst-plugins-base1.0 (1.24.7-2 to 1.24.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gst-plugins-base1.0.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• lxqt-session (1.3.0-1 to 1.4.0-2)
  • Migration status for lxqt-session (1.3.0-1 to 1.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lxqt-session would introduce bugs in testing: #1077186
  • Additional info:
    • Updating lxqt-session will fix bugs in testing: #1079554
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxqt-session.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 7 days old (needed 5 days)
• ospray (- to 3.1.0-2)
  • Migration status for ospray (- to 3.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): ospray embree (not considered)
    • Depends: ospray embree (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ospray.html
    • autopkgtest for ospray/3.1.0-2: amd64: Pass, arm64: 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
    • 7 days old (needed 2 days)
• python-msgspec (0.18.6-1 to 0.18.6+1-6)
  • Migration status for python-msgspec (0.18.6-1 to 0.18.6+1-6): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-msgspec.html
    • autopkgtest for python-msgspec/0.18.6+1-6: 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
    • 7 days old (needed 2 days)
• python-yalexs (8.5.5-1 to 8.6.4-1)
  • Migration status for python-yalexs (8.5.5-1 to 8.6.4-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends-Indep: python-yalexs pytest-freezer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-yalexs.html
    • autopkgtest for python-yalexs/8.6.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
    • 7 days old (needed 2 days)
• rust-ctrlc (3.4.2-1 to 3.4.5-1)
  • Migration status for rust-ctrlc (3.4.2-1 to 3.4.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ctrlc/3.4.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-just/1.35.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ctrlc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• rust-lsd (1.0.0-2 to 1.1.5-1)
  • Migration status for rust-lsd (1.0.0-2 to 1.1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-lsd rust-uzers (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-lsd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• rust-sequoia-keystore-backend (0.5.0-1 to 0.6.0-1)
  • Migration status for rust-sequoia-keystore-backend (0.5.0-1 to 0.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-sequoia-keystore-backend rust-sequoia-keystore (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: rust-sequoia-keystore-backend rust-sequoia-keystore-gpg-agent
    • Implicit dependency: rust-sequoia-keystore-backend rust-sequoia-keystore-softkeys
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-keystore-backend.html
    • autopkgtest for rust-sequoia-keystore-backend/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
    • 7 days old (needed 2 days)
• rust-sequoia-keystore-gpg-agent (0.3.0-1 to 0.4.0-1)
  • Migration status for rust-sequoia-keystore-gpg-agent (0.3.0-1 to 0.4.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-sequoia-keystore-gpg-agent rust-sequoia-keystore (not considered)
    • Invalidated by implicit-dependency
    • Build-Depends(-Arch): rust-sequoia-keystore-gpg-agent rust-sequoia-keystore-backend
    • Depends: rust-sequoia-keystore-gpg-agent rust-sequoia-keystore-backend
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-keystore-gpg-agent.html
    • autopkgtest for rust-sequoia-keystore-gpg-agent/0.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• rust-sequoia-keystore-softkeys (0.5.0-1 to 0.6.0-1)
  • Migration status for rust-sequoia-keystore-softkeys (0.5.0-1 to 0.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-sequoia-keystore-softkeys rust-sequoia-keystore (not considered)
    • Invalidated by implicit-dependency
    • Build-Depends(-Arch): rust-sequoia-keystore-softkeys rust-sequoia-keystore-backend
    • Depends: rust-sequoia-keystore-softkeys rust-sequoia-keystore-backend
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-keystore-softkeys.html
    • autopkgtest for rust-sequoia-keystore-softkeys/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
    • 7 days old (needed 2 days)
• exiv2 (0.27.6-1 to 0.28.3+dfsg-2)
  • Migration status for exiv2 (0.27.6-1 to 0.28.3+dfsg-2): Will attempt migration (Any information below is purely informational)
  • 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 ♻
    • 8 days old (needed 5 days)
• halide (18.0.0-6 to 18.0.0-8)
  • Migration status for halide (18.0.0-6 to 18.0.0-8): 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 halide/18.0.0-8: amd64: Pass, arm64: Pass
  • Additional info:
    • Updating halide will fix bugs in testing: #1081599
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/halide.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • No reference result, but not reproducibility on i386 - info ♻
    • 8 days old (needed 5 days)
• libfiu (- to 1.2-3)
  • Migration status for libfiu (- to 1.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libfiu would introduce bugs in testing: #1066938
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libfiu.html
    • autopkgtest for libfiu/1.2-3: amd64: Pass, arm64: 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
    • 8 days old (needed 2 days)
• mopac7 (- to 1.15-7)
  • Migration status for mopac7 (- to 1.15-7): 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/m/mopac7.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-netsnmpagent (0.6.0-4 to 0.6.0-5)
  • Migration status for python-netsnmpagent (0.6.0-4 to 0.6.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 8 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-netsnmpagent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-xtermcolor (1.2.1-3 to 1.2.1-4)
  • Migration status for python-xtermcolor (1.2.1-3 to 1.2.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 8 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xtermcolor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• qemu (1:9.0.2+ds-2 to 1:9.1.0+ds-3)
  • Migration status for qemu (1:9.0.2+ds-2 to 1:9.1.0+ds-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch i386 binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Not built on buildd: upload info for arch s390x binaries not found
    • Built-Using: qemu gcc-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qemu.html
    • autopkgtest for qemu/1:9.1.0+ds-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Failed (not a regression), 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 ♻
    • 8 days old (needed 5 days)
• r-cran-filehash (2.4-5-1 to 2.4-6-1)
  • Migration status for r-cran-filehash (2.4-5-1 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 ♻ (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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-filehash.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• r-cran-sjplot (- to 2.8.16+dfsg-1)
  • Migration status for r-cran-sjplot (- to 2.8.16+dfsg-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-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-sjstats
    • 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-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
    • 8 days old (needed 2 days)
• rust-debversion (0.4.1-1 to 0.4.3-1)
  • Migration status for rust-debversion (0.4.1-1 to 0.4.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-debversion.html
  • Additional info:
    • autopkgtest for rust-debversion/0.4.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• rust-serde-json (1.0.117-1 to 1.0.128-1)
  • Migration status for rust-serde-json (1.0.117-1 to 1.0.128-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-serde-json-dev/1.0.128-1/amd64 to testing makes librust-just-dev/1.35.0-1/amd64 uninstallable
    • migrating librust-serde-json-dev/1.0.128-1/arm64 to testing makes librust-just-dev/1.35.0-1/arm64 uninstallable
    • migrating librust-serde-json-dev/1.0.128-1/armel to testing makes librust-just-dev/1.35.0-1/armel uninstallable
    • migrating librust-serde-json-dev/1.0.128-1/armhf to testing makes librust-just-dev/1.35.0-1/armhf uninstallable
    • migrating librust-serde-json-dev/1.0.128-1/i386 to testing makes librust-just-dev/1.35.0-1/i386 uninstallable
    • migrating librust-serde-json-dev/1.0.128-1/mips64el to testing makes librust-just-dev/1.35.0-1/mips64el uninstallable
    • migrating librust-serde-json-dev/1.0.128-1/ppc64el to testing makes librust-just-dev/1.35.0-1/ppc64el uninstallable
    • migrating librust-serde-json-dev/1.0.128-1/s390x to testing makes librust-just-dev/1.35.0-1/s390x uninstallable
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-serde-json.html
    • autopkgtest for rust-serde-json/1.0.128-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
    • 8 days old (needed 2 days)
• dh-puppet (- to 1.1)
  • Migration status for dh-puppet (- to 1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-puppet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• gr-framework (- to 0.73.7+dfsg-1)
  • Migration status for gr-framework (- to 0.73.7+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kenhys@xdump.org
    • Not built on buildd: arch all binaries uploaded by kenhys@xdump.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gr-framework.html
    • autopkgtest for gr-framework/0.73.7+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
    • 9 days old (needed 2 days)
• libdata-validate-domain-perl (0.10-1.1 to 0.15-1)
  • Migration status for libdata-validate-domain-perl (0.10-1.1 to 0.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lintian/2.118.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: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdata-validate-domain-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• libreoffice (4:24.2.5-4 to 4:24.2.6-1)
  • Migration status for libreoffice (4:24.2.5-4 to 4:24.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libreoffice/4:24.2.6-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Test in progress (will not be considered a regression), armhf: Pass, 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)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libreoffice.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 ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• rust-breezyshim (0.1.167-1 to 0.1.181-1)
  • Migration status for rust-breezyshim (0.1.167-1 to 0.1.181-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-breezyshim.html
    • Depends: rust-breezyshim rust-debian-changelog
    • Depends: rust-breezyshim rust-dirty-tracker (not considered)
  • Additional info:
    • autopkgtest for rust-breezyshim/0.1.181-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• rust-deb822-lossless (0.1.14-1 to 0.1.23-1)
  • Migration status for rust-deb822-lossless (0.1.14-1 to 0.1.23-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-deb822-lossless.html
  • Additional info:
    • autopkgtest for rust-deb822-lossless/0.1.23-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
    • 9 days old (needed 2 days)
• rust-debian-changelog (0.1.11-2 to 0.1.13-1)
  • Migration status for rust-debian-changelog (0.1.11-2 to 0.1.13-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-debian-changelog.html
  • Additional info:
    • autopkgtest for rust-debian-changelog/0.1.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• rust-debian-control (0.1.18-1 to 0.1.28-1)
  • Migration status for rust-debian-control (0.1.18-1 to 0.1.28-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-debian-control.html
    • Build-Depends(-Arch): rust-debian-control rust-deb822-lossless
    • Depends: rust-debian-control rust-deb822-lossless
  • Additional info:
    • autopkgtest for rust-debian-control/0.1.28-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
    • 9 days old (needed 2 days)
• rust-uzers (0.11.3-1 to 0.12.1-1)
  • Migration status for rust-uzers (0.11.3-1 to 0.12.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-uzers rust-sniffglue (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: rust-uzers rust-eza
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-uzers.html
    • autopkgtest for rust-uzers/0.12.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
    • 9 days old (needed 2 days)
• skimage (0.22.0-3 to 0.24.0-3)
  • Migration status for skimage (0.22.0-3 to 0.24.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating skimage would introduce bugs in testing: #1076289
    • missing build on mips64el
  • Additional info:
    • Updating skimage will fix bugs in testing: #1070437, #1071782, #1072271
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/skimage.html
    • autopkgtest for skimage/0.24.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • No reference result, but not reproducibility on amd64 - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • No reference result, but not reproducibility on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• dogtail (0.9.11-13 to 1.0.0-3)
  • Migration status for dogtail (0.9.11-13 to 1.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dogtail/1.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for liferea/1.15.7-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dogtail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• json-glib (1.8.0-2 to 1.10.0+ds-1)
  • Migration status for json-glib (1.8.0-2 to 1.10.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for json-glib/1.10.0+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for libgdata/0.18.1-7: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/json-glib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• nipy (- to 0.6.0-2)
  • Migration status for nipy (- to 0.6.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for nipy/0.6.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nipy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• octave-statistics (1.6.7-1 to 1.7.0-1)
  • Migration status for octave-statistics (1.6.7-1 to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • octave-statistics/arm64 has unsatisfiable dependency
    • octave-statistics/i386 has unsatisfiable dependency
    • octave-statistics/ppc64el has unsatisfiable dependency
    • octave-statistics/s390x has unsatisfiable dependency
    • missing build on amd64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-statistics.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 ♻
    • 10 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• pythonprop (- to 0.30.1-2)
  • Migration status for pythonprop (- to 0.30.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pythonprop voacapl (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pythonprop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• r-cran-performance (- to 0.12.3-1)
  • Migration status for r-cran-performance (- to 0.12.3-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.12.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/r/r-cran-performance.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• srpc (0.10.3-1 to 0.10.3-2)
  • Migration status for srpc (0.10.3-1 to 0.10.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for srpc/0.10.3-2: 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/s/srpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• vim (2:9.1.0496-1 to 2:9.1.0709-1)
  • Migration status for vim (2:9.1.0496-1 to 2:9.1.0709-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 vim/2:9.1.0709-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/v/vim.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 10 days old (needed 5 days)
• mame (0.266+dfsg.1-1 to 0.269+dfsg.1-1)
  • Migration status for mame (0.266+dfsg.1-1 to 0.269+dfsg.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mame.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 11 days old (needed 5 days)
• qtractor (- to 1.2.0-1)
  • Migration status for qtractor (- to 1.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): qtractor aubio (not considered)
    • Depends: qtractor aubio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtractor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 11 days old (needed 5 days)
• r-cran-glmmtmb (1.1.8+dfsg-3 to 1.1.9+dfsg-2)
  • Migration status for r-cran-glmmtmb (1.1.8+dfsg-3 to 1.1.9+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-glmmtmb/1.1.9+dfsg-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • Depends: r-cran-glmmtmb r-cran-tmb (not considered)
  • Additional info:
    • Updating r-cran-glmmtmb will fix bugs in testing: #1081305
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-glmmtmb.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 ♻
    • 11 days old (needed 5 days)
• r-cran-tmb (1.9.11-2 to 1.9.14-2)
  • Migration status for r-cran-tmb (1.9.11-2 to 1.9.14-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-glmmtmb/1.1.8+dfsg-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-tmb/1.9.14-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • r-cran-tmb unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • r-cran-tmb unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • r-cran-tmb 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:
    • Updating r-cran-tmb will fix bugs in testing: #1077860
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tmb.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 ♻
    • 11 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:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/w/weakforced.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 11 days old (needed 5 days)
    • Remove hint for (transitive) dependency: getdns
• xoscope (- to 2.3-2)
  • Migration status for xoscope (- to 2.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xoscope comedilib (not considered)
    • Depends: xoscope comedilib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xoscope.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 11 days old (needed 5 days)
• dante (- to 1.4.3+dfsg-2)
  • Migration status for dante (- to 1.4.3+dfsg-2): 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-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 ♻
    • 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• dolfinx-mpc (- to 0.8.0.post1-5)
  • Migration status for dolfinx-mpc (- to 0.8.0.post1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): dolfinx-mpc fenics-dolfinx (not considered)
    • Depends: dolfinx-mpc fenics-dolfinx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dolfinx-mpc.html
    • autopkgtest for dolfinx-mpc/0.8.0.post1-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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• libepoxy (1.5.10-1 to 1.5.10-2)
  • Migration status for libepoxy (1.5.10-1 to 1.5.10-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
    • 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libepoxy.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 12 days old (needed 5 days)
• r-cran-uwot (0.1.16-2 to 0.2.2-1)
  • Migration status for r-cran-uwot (0.1.16-2 to 0.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-uwot/0.2.2-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-uwot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• refpolicy (2:2.20240723-2 to 2:2.20240830-1)
  • Migration status for refpolicy (2:2.20240723-2 to 2:2.20240830-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: refpolicy selinux-python (not considered)
    • Depends: refpolicy selinux-python (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/refpolicy.html
    • autopkgtest for refpolicy/2:2.20240830-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
    • 12 days old (needed 2 days)
• ruby-attr-encrypted (3.1.0-4 to 4.1.0-1)
  • Migration status for ruby-attr-encrypted (3.1.0-4 to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-attr-encrypted/4.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for ruby-devise-two-factor/4.0.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: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-attr-encrypted.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• selinux-dbus (3.5-1 to 3.7-1)
  • Migration status for selinux-dbus (3.5-1 to 3.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: selinux-dbus selinux-python (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/selinux-dbus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• selinux-python (3.5-1 to 3.7-1)
  • Migration status for selinux-python (3.5-1 to 3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating selinux-python would introduce bugs in testing: #1080420
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/selinux-python.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• trocla (0.5.1-2 to 0.5.1-3)
  • Migration status for trocla (0.5.1-2 to 0.5.1-3): 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/t/trocla.html
    • autopkgtest for trocla/0.5.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 days)
• twisted (24.3.0-3 to 24.7.0-2)
  • Migration status for twisted (24.3.0-3 to 24.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating twisted would introduce bugs in testing: #1081419
    • autopkgtest for libervia-backend/0.9.0~hg4294-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 twisted/24.7.0-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/twisted.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• gromacs (2024.2-1 to 2024.3-1)
  • Migration status for gromacs (2024.2-1 to 2024.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gromacs/2024.3-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gromacs.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 ♻
    • 13 days old (needed 5 days)
• ruby-typhoeus (1.4.0-3 to 1.4.0-4)
  • Migration status for ruby-typhoeus (1.4.0-3 to 1.4.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-typhoeus ruby-faraday-typhoeus (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-typhoeus.html
    • autopkgtest for ruby-typhoeus/1.4.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 13 days old (needed 2 days)
• debian-installer (20230607+deb12u6 to 20230607+deb12u7)
  • Migration status for debian-installer (20230607+deb12u6 to 20230607+deb12u7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • debian-installer unsatisfiable Build-Depends(-Arch) on amd64: linux-image-6.1.0-25-amd64 [amd64]
    • debian-installer unsatisfiable Build-Depends(-Arch) on arm64: linux-image-6.1.0-25-arm64 [arm64]
    • debian-installer unsatisfiable Build-Depends(-Arch) on i386: shim-signed [amd64 i386 arm64]
    • debian-installer unsatisfiable Build-Depends(-Arch) on i386: linux-image-6.1.0-25-686 [i386]
    • debian-installer unsatisfiable Build-Depends(-Arch) on i386: linux-image-6.1.0-25-686-pae [i386]
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-installer.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 14 days old (needed 5 days)
• ideep (- to 0.0~git20240814.41d636c-1)
  • Migration status for ideep (- to 0.0~git20240814.41d636c-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ideep/0.0~git20240814.41d636c-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ideep.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 ♻
    • 14 days old (needed 5 days)
• loggerhead (- to 2.0.1+bzr548-1)
  • Migration status for loggerhead (- to 2.0.1+bzr548-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating loggerhead would introduce bugs in testing: #1074655
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/loggerhead.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 14 days old (needed 5 days)
• lomiri-calendar-app (- to 1.0.2-2)
  • Migration status for lomiri-calendar-app (- to 1.0.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lomiri-calendar-app lomiri-sync-monitor (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 14 days old (needed 5 days)
• lomiri-sync-monitor (- to 0.6.0-3)
  • Migration status for lomiri-sync-monitor (- to 0.6.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lomiri-sync-monitor syncevolution (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-sync-monitor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• pass-extension-copyq (- to 0~20240825-1)
  • Migration status for pass-extension-copyq (- to 0~20240825-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by czchen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pass-extension-copyq.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• pass-report (- to 0.4-1)
  • Migration status for pass-report (- to 0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by czchen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pass-report.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• python-rokuecp (- to 0.19.4-1)
  • Migration status for python-rokuecp (- to 0.19.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-rokuecp/0.19.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 ♻
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
    • Build-Depends-Indep: python-rokuecp pytest-freezer
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-rokuecp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• python-sushy-oem-idrac (- to 5.0.0-1)
  • Migration status for python-sushy-oem-idrac (- to 5.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/p/python-sushy-oem-idrac.html
    • autopkgtest for python-sushy-oem-idrac/5.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• python-taskipy (- to 1.13.0-1)
  • Migration status for python-taskipy (- to 1.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-taskipy/1.13.0-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
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-taskipy.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 ♻
    • 14 days old (needed 5 days)
• renson-endura-delta (- to 1.7.1-1)
  • Migration status for renson-endura-delta (- to 1.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by edward@4angle.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/renson-endura-delta.html
    • autopkgtest for renson-endura-delta/1.7.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
    • 14 days old (needed 2 days)
• ruby-faraday-typhoeus (- to 1.1.0-1)
  • Migration status for ruby-faraday-typhoeus (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by boutil, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-faraday-typhoeus.html
    • autopkgtest for ruby-faraday-typhoeus/1.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
    • 14 days old (needed 2 days)
• ruby-whitequark-parser (3.1.3.0-1 to 3.3.4.2-1)
  • Migration status for ruby-whitequark-parser (3.1.3.0-1 to 3.3.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-proc-to-ast/0.1.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-proc-to-ast/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-rspec-parameterized/0.4.2-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-whitequark-parser/3.3.4.2-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/ruby-whitequark-parser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• gcc-14 (14.2.0-3 to 14.2.0-4)
  • Migration status for gcc-14 (14.2.0-3 to 14.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gcc-14/14.2.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for netavark/1.12.1-3: amd64: Regression or new test ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating gcc-14 will fix bugs in testing: #1078786
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-14.html
    • 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 ♻
    • 15 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 15 days old (needed 5 days)
• liborcus (0.19.2-3 to 0.19.2-4)
  • Migration status for liborcus (0.19.2-3 to 0.19.2-4): 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 liborcus/0.19.2-4: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/liborcus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 15 days old (needed 5 days)
• shotcut (24.06.26+git20240816+ds-1 to 24.08.29+ds-1)
  • Migration status for shotcut (24.06.26+git20240816+ds-1 to 24.08.29+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
    • 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 ♻
    • 15 days old (needed 5 days)
• xrdp (0.9.24-5 to 0.10.1-3)
  • Migration status for xrdp (0.9.24-5 to 0.10.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for freerdp3/3.6.3+dfsg1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Pass, 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 xrdp will fix bugs in testing: #1079330
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xrdp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• agda (- to 2.6.3-2)
  • Migration status for agda (- to 2.6.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: agda agda-stdlib (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/agda.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 ♻
    • 16 days old (needed 5 days)
• fenics-dolfinx (- to 1:0.8.0-11)
  • Migration status for fenics-dolfinx (- to 1:0.8.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fenics-dolfinx.html
    • autopkgtest for fenics-dolfinx/1:0.8.0-11: amd64: Pass, arm64: Pass, armel: Pass, 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
    • 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)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• gcc-snapshot (- to 1:20240829-1)
  • Migration status for gcc-snapshot (- to 1:20240829-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-snapshot would introduce bugs in testing: #321449, #651291
    • missing build on armel
    • missing build on mips64el
    • missing build on riscv64
    • arch:armel not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for gcc-snapshot/1:20240829-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/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 ♻
    • 16 days old (needed 5 days)
• glslang (14.2.0-1 to 14.3.0-1)
  • Migration status for glslang (14.2.0-1 to 14.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): glslang spirv-tools (not considered)
    • Depends: glslang spirv-tools (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glslang.html
    • autopkgtest for glslang/14.3.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
    • 16 days old (needed 5 days)
• gsad (- to 22.11.0-1)
  • Migration status for gsad (- to 22.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gsad would introduce bugs in testing: #1076967
    • Build-Depends(-Arch): gsad gvm-libs (not considered)
    • Depends: gsad gvm-libs (not considered)
    • 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• gvm-tools (- to 24.7.0-1)
  • Migration status for gvm-tools (- to 24.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): 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.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• python-gvm (- to 24.7.0-1)
  • Migration status for python-gvm (- to 24.7.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.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 16 days old (needed 2 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• spirv-tools (2024.2~rc1-1 to 2024.3-1)
  • Migration status for spirv-tools (2024.2~rc1-1 to 2024.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for spirv-llvm-translator-17/17.0.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for spirv-llvm-translator-18/18.1.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), 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/s/spirv-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• vulkan-validationlayers (1.3.283.0-1 to 1.3.290.0-1)
  • Migration status for vulkan-validationlayers (1.3.283.0-1 to 1.3.290.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 spirv-tools (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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 16 days old (needed 5 days)
• debian-hamradio (0.8 to 0.9)
  • Migration status for debian-hamradio (0.8 to 0.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by d@vehibberd.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-hamradio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• ghdl (- to 4.1.0+dfsg-2)
  • Migration status for ghdl (- to 4.1.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ghdl/4.1.0+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻
    • missing build on mips64el
    • Not built on buildd: upload info for arch ppc64el binaries not found
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghdl.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 17 days old (needed 5 days)
• gvmd (- to 23.8.1-1)
  • Migration status for gvmd (- to 23.8.1-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/23.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 17 days old (needed 2 days)
• openvas-scanner (- to 23.8.5-1)
  • Migration status for openvas-scanner (- to 23.8.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• python-pefile (2023.2.7-3 to 2024.8.26-1)
  • Migration status for python-pefile (2023.2.7-3 to 2024.8.26-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pefile.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 17 days old (needed 5 days)
• python-quantities (0.15.0-2 to 0.16.0-1)
  • Migration status for python-quantities (0.15.0-2 to 0.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for neo/0.13.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 python-quantities/0.16.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), 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/p/python-quantities.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• rust-subversion (- to 0.0.3-4)
  • Migration status for rust-subversion (- to 0.0.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-subversion/0.0.3-4: amd64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-subversion.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 17 days old (needed 5 days)
• uronode (2.15-3 to 2.15-4)
  • Migration status for uronode (2.15-3 to 2.15-4): 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/u/uronode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• varnam-schemes (- to 1.8.0-3)
  • Migration status for varnam-schemes (- to 1.8.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for varnam-schemes/1.8.0-3: 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/v/varnam-schemes.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• voacapl (- to 0.7.6-2)
  • Migration status for voacapl (- to 0.7.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for voacapl/0.7.6-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/v/voacapl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• python-jenkins (- to 1.4.0-5)
  • Migration status for python-jenkins (- to 1.4.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-jenkins would introduce bugs in testing: #1073383
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jenkins.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• rust-buffer-redux (- to 1.0.2-1)
  • Migration status for rust-buffer-redux (- 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): rust-buffer-redux rust-slice-ring-buffer (not considered)
    • Depends: rust-buffer-redux rust-slice-ring-buffer (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-buffer-redux.html
    • autopkgtest for rust-buffer-redux/1.0.2-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
    • 18 days old (needed 2 days)
• rust-reis (- to 0.2.0-2)
  • Migration status for rust-reis (- to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-reis/0.2.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-reis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• hurd (- to 1:0.9.git20240714-3)
  • Migration status for hurd (- to 1:0.9.git20240714-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hurd would introduce bugs in testing: #650080, #838244, #943307
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libc0.3-dev (>= 2.33-2~1)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-disk-dev (>= 0~20211031-2)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-usb-dev
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libacpica-dev
    • Not built on buildd: arch all binaries uploaded by sthibault, a new source-only upload is needed to allow migration
    • Not touching package due to block request by freeze (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hurd.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 19 days old (needed 5 days)
• astra-toolbox (- to 2.1.0-5)
  • Migration status for astra-toolbox (- to 2.1.0-5): 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)
    • 20 days old (needed 5 days)
• blimps (- to 3.9+ds-3)
  • Migration status for blimps (- to 3.9+ds-3): 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)
    • 20 days old (needed 5 days)
• ruby-redis (4.8.0-2 to 5.2.0-3)
  • Migration status for ruby-redis (4.8.0-2 to 5.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-fakeredis/0.8.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 ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-fakeredis/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-redis/5.2.0-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 ♻)
    • autopkgtest for ruby-redis-namespace/1.11.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-redis-namespace/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-rollout/2.5.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-rollout/n/a: riscv64: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 20 days old (needed 5 days)
• chafa (1.14.0-1.1 to 1.14.2-1)
  • Migration status for chafa (1.14.0-1.1 to 1.14.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chafa would introduce bugs in testing: #1079950
  • Additional info:
    • Updating chafa will fix bugs in testing: #1077933
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chafa.html
    • autopkgtest for chafa/1.14.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), 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 ♻
    • 21 days old (needed 5 days)
• kirigami-addons5 (- to 0.11.0-4)
  • Migration status for kirigami-addons5 (- to 0.11.0-4): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kirigami-addons5.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• notify-osd (- to 0.9.35+20.04.20191129-1)
  • Migration status for notify-osd (- to 0.9.35+20.04.20191129-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for notify-osd/0.9.35+20.04.20191129-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/notify-osd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 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:
    • Updating trafficserver would introduce bugs in testing: #999938
    • Build-Depends(-Arch): trafficserver pcre3 (not considered)
    • Depends: trafficserver pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trafficserver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 21 days old (needed 5 days)
• yorick-ynfft (- to 1.0.4-2)
  • Migration status for yorick-ynfft (- to 1.0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): yorick-ynfft nfft (not considered)
    • Depends: yorick-ynfft nfft (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-ynfft.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• bitshuffle (0.5.1-1.2 to 0.5.1-1.3)
  • Migration status for bitshuffle (0.5.1-1.2 to 0.5.1-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Impossible Build-Depends(-Arch): bitshuffle -> libhdf5-openmpi-dev/1.10.10+repack-3.3+b1/armel
    • Impossible Build-Depends(-Arch): bitshuffle -> libhdf5-openmpi-dev/1.10.10+repack-3.3+b1/armhf
    • Impossible Build-Depends(-Arch): bitshuffle -> libhdf5-openmpi-dev/1.10.10+repack-3.3+b1/i386
  • Additional info:
    • Updating bitshuffle will fix bugs in testing: #1074848
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bitshuffle.html
    • autopkgtest for bitshuffle/0.5.1-1.3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • No reference result, but not reproducibility on amd64 - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Waiting for reproducibility reference results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 22 days old (needed 2 days)
• cutesv (2.1.0-2 to 2.1.1-1)
  • Migration status for cutesv (2.1.0-2 to 2.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cutesv/2.1.1-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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cutesv.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 ♻
    • Reproducible on i386 - info ♻
    • 22 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 22 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 22 days old (needed 2 days)
• gosa (- to 2.8~git20230203.10abe45+dfsg-17)
  • Migration status for gosa (- to 2.8~git20230203.10abe45+dfsg-17): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa smarty4 (not considered)
    • Invalidated by dependency
  • 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 22 days old (needed 5 days)
• gwyddion (2.64-1.1 to 2.66-1)
  • Migration status for gwyddion (2.64-1.1 to 2.66-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gwyddion gtkglext (not considered)
    • Depends: gwyddion gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gwyddion.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 22 days old (needed 5 days)
• openafs (- to 1.8.12.1-1)
  • Migration status for openafs (- to 1.8.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openafs would introduce bugs in testing: #1072708
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openafs.html
    • autopkgtest for openafs/1.8.12.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 22 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• python-androidtv (- to 0.0.73-1)
  • Migration status for python-androidtv (- to 0.0.73-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-androidtv.html
    • autopkgtest for python-androidtv/0.0.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 22 days old (needed 2 days)
• python-bsblan (- to 0.6.2-2)
  • Migration status for python-bsblan (- to 0.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-bsblan/0.6.2-2: 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/p/python-bsblan.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)
• blktrace (1.2.0-5 to 1.3.0-0.1)
  • Migration status for blktrace (1.2.0-5 to 1.3.0-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blktrace.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• django-allauth (0.58.2-2 to 64.1.0-1)
  • Migration status for django-allauth (0.58.2-2 to 64.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for django-allauth/64.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for django-mailman3/1.3.15-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/d/django-allauth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 days old (needed 5 days)
• gfan (0.6.2-7 to 0.7-1)
  • Migration status for gfan (0.6.2-7 to 0.7-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for gfan/0.7-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfan.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 23 days old (needed 5 days)
• postsrsd (- to 1.10-2.2)
  • Migration status for postsrsd (- to 1.10-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating postsrsd would introduce bugs in testing: #1068053
    • autopkgtest for postsrsd/1.10-2.2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postsrsd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 days old (needed 5 days)
• pytest-services (- to 2.2.1+ds-4)
  • Migration status for pytest-services (- to 2.2.1+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pytest-services/2.2.1+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 ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): pytest-services mysql-8.0 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-services.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 days old (needed 5 days)
• python-huum (- to 0.7.10-3)
  • Migration status for python-huum (- to 0.7.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-huum/0.7.10-3: 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/p/python-huum.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 23 days old (needed 5 days)
• guix (- to 1.4.0-7)
  • Migration status for guix (- to 1.4.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): guix guile-gnutls (not considered)
    • Depends: guix guile-gnutls (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 days)
• m2crypto (0.41.0+ds-3 to 0.42.0-1)
  • Migration status for m2crypto (0.41.0+ds-3 to 0.42.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
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • autopkgtest for m2crypto/0.42.0-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/m2crypto.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • 24 days old (needed 5 days)
• python-attrs (23.2.0-2 to 24.2.0-1)
  • Migration status for python-attrs (23.2.0-2 to 24.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-attrs/24.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-cattrs/23.2.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: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-klein/23.12.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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-attrs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 days)
• rsyslog (8.2406.0-1 to 8.2408.0-1)
  • Migration status for rsyslog (8.2406.0-1 to 8.2408.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 rsyslog/8.2408.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsyslog.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 days)
• ruby-sqlite3 (1.6.9-1 to 1.6.9-2)
  • Migration status for ruby-sqlite3 (1.6.9-1 to 1.6.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-sqlite3/1.6.9-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-sqlite3/n/a: riscv64: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-sqlite3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 days)
• ruby-msgpack (1.4.2-2 to 1.7.2-1)
  • Migration status for ruby-msgpack (1.4.2-2 to 1.7.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for ruby-msgpack/1.7.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-msgpack.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 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
    • 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
    • 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 i386 binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/singularity-container.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• cyrus-imapd (- to 3.10.0-1)
  • Migration status for cyrus-imapd (- to 3.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cyrus-imapd would introduce bugs in testing: #1068223
    • autopkgtest for cyrus-imapd/3.10.0-1: amd64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for cyrus-imapd/blocked-on-ci-infra: arm64: 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
    • Build-Depends(-Arch): cyrus-imapd opendkim
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cyrus-imapd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 26 days old (needed 5 days)
• golang-github-vulcand-oxy (1.3.0-3 to 2.0.0-1)
  • Migration status for golang-github-vulcand-oxy (1.3.0-3 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-vulcand-oxy/2.0.0-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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-vulcand-oxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 26 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 26 days old (needed 5 days)
• pcre3 (- to 2:8.39-15.1)
  • Migration status for pcre3 (- to 2:8.39-15.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pcre3 would introduce bugs in testing: #1063571, #1071970
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcre3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 26 days old (needed 5 days)
• rust-log (0.4.21-3 to 0.4.22-1)
  • Migration status for rust-log (0.4.21-3 to 0.4.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-delog/0.1.7-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-delog/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-log/0.4.22-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-serde-xml-rs/blocked-on-ci-infra: riscv64: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-log.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 26 days old (needed 5 days)
• sonic-visualiser (4.5.2-2 to 5.0-1)
  • Migration status for sonic-visualiser (4.5.2-2 to 5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sonic-visualiser would introduce bugs in testing: #1080495
    • 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 26 days old (needed 5 days)
• accounts-qml-module (0.7+git20231028.05e79eb-1 to 0.7+git20231028.05e79eb-5)
  • Migration status for accounts-qml-module (0.7+git20231028.05e79eb-1 to 0.7+git20231028.05e79eb-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by mike.gabriel@das-netzwerkteam.de
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/accounts-qml-module.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 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)
    • 27 days old (needed 5 days)
• haxe (1:4.3.4-2 to 1:4.3.6-1)
  • Migration status for haxe (1:4.3.4-2 to 1:4.3.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haxe ocaml-luv (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haxe.html
    • autopkgtest for haxe/1:4.3.6-1: 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 armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 27 days old (needed 2 days)
• r-bioc-alabaster.base (- to 1.4.2+ds-3)
  • Migration status for r-bioc-alabaster.base (- to 1.4.2+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-alabaster.base/1.4.2+ds-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): r-bioc-alabaster.base r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-alabaster.base r-bioc-rhdf5 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-alabaster.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 ♻
    • 27 days old (needed 5 days)
• r-bioc-alabaster.matrix (- to 1.4.2+ds-1)
  • Migration status for r-bioc-alabaster.matrix (- to 1.4.2+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-alabaster.matrix/1.4.2+ds-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): r-bioc-alabaster.matrix r-bioc-alabaster.base (not considered)
    • Build-Depends(-Arch): r-bioc-alabaster.matrix r-bioc-hdf5array
    • Build-Depends(-Arch): r-bioc-alabaster.matrix r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-alabaster.matrix r-bioc-alabaster.base (not considered)
    • Depends: r-bioc-alabaster.matrix r-bioc-hdf5array
    • Depends: r-bioc-alabaster.matrix r-bioc-rhdf5 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-alabaster.matrix.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 ♻
    • 27 days old (needed 5 days)
• r-bioc-alabaster.ranges (- to 1.4.2+ds-2)
  • Migration status for r-bioc-alabaster.ranges (- to 1.4.2+ds-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-alabaster.ranges r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-alabaster.ranges r-bioc-rhdf5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-alabaster.ranges r-bioc-alabaster.base (not considered)
    • Depends: r-bioc-alabaster.ranges r-bioc-alabaster.base (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-alabaster.ranges.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-alabaster.ranges/1.4.2+ds-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
    • 27 days old (needed 2 days)
• r-bioc-alabaster.sce (- to 1.4.0+ds-1)
  • Migration status for r-bioc-alabaster.sce (- to 1.4.0+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-alabaster.sce r-bioc-alabaster.se (not considered)
    • Depends: r-bioc-alabaster.sce r-bioc-alabaster.se (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-alabaster.sce r-bioc-alabaster.base (not considered)
    • Depends: r-bioc-alabaster.sce r-bioc-alabaster.base (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-alabaster.sce.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-alabaster.sce/1.4.0+ds-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
    • 27 days old (needed 2 days)
• r-bioc-alabaster.se (- to 1.4.1+ds-1)
  • Migration status for r-bioc-alabaster.se (- to 1.4.1+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-alabaster.se r-bioc-alabaster.ranges (not considered)
    • Depends: r-bioc-alabaster.se r-bioc-alabaster.ranges (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-alabaster.se r-bioc-alabaster.base (not considered)
    • Build-Depends(-Arch): r-bioc-alabaster.se r-bioc-alabaster.matrix (not considered)
    • Depends: r-bioc-alabaster.se r-bioc-alabaster.base (not considered)
    • Depends: r-bioc-alabaster.se r-bioc-alabaster.matrix (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-alabaster.se.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-alabaster.se/1.4.1+ds-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
    • 27 days old (needed 2 days)
• r-bioc-biomformat (- to 1.32.0+dfsg-1)
  • Migration status for r-bioc-biomformat (- to 1.32.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): r-bioc-biomformat r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-biomformat r-bioc-rhdf5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biomformat.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-biomformat/1.32.0+dfsg-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
    • 27 days old (needed 2 days)
• r-bioc-bsseq (- to 1.40.0+dfsg-1)
  • Migration status for r-bioc-bsseq (- to 1.40.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): r-bioc-bsseq r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-bsseq r-bioc-rhdf5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-hdf5array
    • Depends: r-bioc-bsseq r-bioc-hdf5array
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-bsseq.html
    • autopkgtest for r-bioc-bsseq/1.40.0+dfsg-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
    • 27 days old (needed 2 days)
• r-bioc-demixt (- to 1.20.0+dfsg-1)
  • Migration status for r-bioc-demixt (- to 1.20.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): r-bioc-demixt r-bioc-dss (not considered)
    • Depends: r-bioc-demixt r-bioc-dss (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-demixt.html
    • autopkgtest for r-bioc-demixt/1.20.0+dfsg-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
    • 27 days old (needed 2 days)
• r-bioc-dropletutils (- to 1.24.0+ds-1)
  • Migration status for r-bioc-dropletutils (- to 1.24.0+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-dropletutils r-bioc-rhdf5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-hdf5array
    • Depends: r-bioc-dropletutils r-bioc-hdf5array
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-dropletutils.html
    • autopkgtest for r-bioc-dropletutils/1.24.0+ds-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Ignored failure, 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 ♻
    • 27 days old (needed 5 days)
• r-bioc-dss (- to 2.52.0+dfsg-1)
  • Migration status for r-bioc-dss (- to 2.52.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): r-bioc-dss r-bioc-bsseq (not considered)
    • Depends: r-bioc-dss r-bioc-bsseq (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-dss.html
    • autopkgtest for r-bioc-dss/2.52.0+dfsg-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
    • 27 days old (needed 2 days)
• r-bioc-glmgampoi (- to 1.16.0+dfsg-1)
  • Migration status for r-bioc-glmgampoi (- to 1.16.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): r-bioc-glmgampoi r-bioc-hdf5array (not considered)
    • Depends: r-bioc-glmgampoi r-bioc-hdf5array (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-glmgampoi.html
    • autopkgtest for r-bioc-glmgampoi/1.16.0+dfsg-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
    • 27 days old (needed 2 days)
• r-bioc-gsva (- to 1.52.3+ds-1)
  • Migration status for r-bioc-gsva (- to 1.52.3+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-gsva r-bioc-hdf5array (not considered)
    • Depends: r-bioc-gsva r-bioc-hdf5array (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-gsva.html
    • autopkgtest for r-bioc-gsva/1.52.3+ds-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
    • 27 days old (needed 2 days)
• r-bioc-hdf5array (- to 1.32.1-1)
  • Migration status for r-bioc-hdf5array (- to 1.32.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-bioc-hdf5array r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-hdf5array r-bioc-rhdf5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-hdf5array.html
    • autopkgtest for r-bioc-hdf5array/1.32.1-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
    • 27 days old (needed 2 days)
• r-bioc-ioniser (- to 2.28.0+dfsg-1)
  • Migration status for r-bioc-ioniser (- to 2.28.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): r-bioc-ioniser r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-ioniser r-bioc-rhdf5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-ioniser.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-ioniser/2.28.0+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 27 days old (needed 2 days)
• r-bioc-mofa (- to 1.6.1+dfsg-13)
  • Migration status for r-bioc-mofa (- to 1.6.1+dfsg-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-mofa r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-mofa r-bioc-rhdf5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-mofa.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-mofa/1.6.1+dfsg-13: 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 ♻, 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 ♻
    • 27 days old (needed 5 days)
• r-bioc-netsam (- to 1.44.0-1)
  • Migration status for r-bioc-netsam (- to 1.44.0-1): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): r-bioc-netsam r-cran-wgcna
    • Depends: r-bioc-netsam r-cran-wgcna
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-netsam.html
    • autopkgtest for r-bioc-netsam/1.44.0-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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 27 days old (needed 5 days)
• r-bioc-phyloseq (- to 1.48.0+dfsg-1)
  • Migration status for r-bioc-phyloseq (- to 1.48.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): r-bioc-phyloseq r-bioc-biomformat (not considered)
    • Depends: r-bioc-phyloseq r-bioc-biomformat (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-phyloseq.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-phyloseq/1.48.0+dfsg-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
    • 27 days old (needed 2 days)
• r-bioc-purecn (- to 2.10.0+dfsg-1)
  • Migration status for r-bioc-purecn (- to 2.10.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): r-bioc-purecn r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-purecn r-bioc-rhdf5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-purecn.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-purecn/2.10.0+dfsg-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
    • 27 days old (needed 2 days)
• r-bioc-scrnaseq (- to 2.18.0+ds-1)
  • Migration status for r-bioc-scrnaseq (- to 2.18.0+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-hdf5array (not considered)
    • Depends: r-bioc-scrnaseq r-bioc-hdf5array (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-alabaster.base (not considered)
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-alabaster.matrix (not considered)
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-alabaster.sce
    • Depends: r-bioc-scrnaseq r-bioc-alabaster.base (not considered)
    • Depends: r-bioc-scrnaseq r-bioc-alabaster.matrix (not considered)
    • Depends: r-bioc-scrnaseq r-bioc-alabaster.sce
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-scrnaseq.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-scrnaseq/2.18.0+ds-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
    • 27 days old (needed 2 days)
• r-bioc-tcgabiolinks (- to 2.32.0+dfsg-1)
  • Migration status for r-bioc-tcgabiolinks (- to 2.32.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-tcgabiolinks/2.32.0+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-tcgabiolinks.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 ♻
    • 27 days old (needed 5 days)
• sfst (1.4.7b-1 to 1.5.8-2)
  • Migration status for sfst (1.4.7b-1 to 1.5.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sfst would introduce bugs in testing: #1079107
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sfst.html
    • autopkgtest for sfst/1.5.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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 27 days old (needed 7 days)
• git-delta (0.17.0-5 to 0.18.0-1)
  • Migration status for git-delta (0.17.0-5 to 0.18.0-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 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/g/git-delta.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 28 days old (needed 5 days)
• jpy (0.17.0-1 to 0.18.0-1)
  • Migration status for jpy (0.17.0-1 to 0.18.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • 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/j/jpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• r-bioc-rhdf5 (- to 2.48.0+dfsg-1)
  • Migration status for r-bioc-rhdf5 (- to 2.48.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-rhdf5/2.48.0+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rhdf5.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 28 days old (needed 5 days)
• cinnamon-desktop-environment (5.8.0 to 6.0.1)
  • Migration status for cinnamon-desktop-environment (5.8.0 to 6.0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cinnamon-desktop-environment.html
  • Additional info:
    • Updating cinnamon-desktop-environment will fix bugs in testing: #1081450
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• coremltools (- to 8.0~b2-1)
  • Migration status for coremltools (- to 8.0~b2-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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• indi-playerone (- to 0.9+20230105184731-2)
  • Migration status for indi-playerone (- to 0.9+20230105184731-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 armhf
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): indi-playerone libplayerone (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 29 days old (needed 5 days)
• lomiri-ui-toolkit (1.3.5100+dfsg-1 to 1.3.5100+dfsg-2)
  • Migration status for lomiri-ui-toolkit (1.3.5100+dfsg-1 to 1.3.5100+dfsg-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
  • Additional info:
    • Updating lomiri-ui-toolkit will fix bugs in testing: #1078725
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-ui-toolkit.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 29 days old (needed 5 days)
• mir (2.14.1-6 to 2.14.1-7)
  • Migration status for mir (2.14.1-6 to 2.14.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mir would introduce bugs in testing: #1081267
    • 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
    • autopkgtest for mir/2.14.1-7: amd64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Build-Depends(-Arch): mir wlcs (not considered)
  • Additional info:
    • Updating mir will fix bugs in testing: #1075277
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mir.html
    • Waiting for reproducibility reference results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility reference results on i386 - info ♻
    • 29 days old (needed 5 days)
• sepp (- to 4.5.4+dfsg-1)
  • Migration status for sepp (- to 4.5.4+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sepp pplacer (not considered)
    • Depends: sepp pplacer (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sepp.html
    • autopkgtest for sepp/4.5.4+dfsg-1: amd64: Pass, arm64: 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
    • 29 days old (needed 2 days)
• generate-ninja (0.0~git20240328.93ee9b9-1 to 0.0~git20240813.54f5b53-1)
  • Migration status for generate-ninja (0.0~git20240328.93ee9b9-1 to 0.0~git20240813.54f5b53-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 generate-ninja/0.0~git20240813.54f5b53-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/generate-ninja.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• golang-go.uber-mock (- to 0.4.0-1)
  • Migration status for golang-go.uber-mock (- 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 i@zhsj.me, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-go.uber-mock.html
    • autopkgtest for golang-go.uber-mock/0.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 30 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-ldapmanager gosa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gosa-plugins-ldapmanager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• microsocks (1.0.3-2 to 1.0.4-2)
  • Migration status for microsocks (1.0.3-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:
    • Build-Depends(-Arch): microsocks python-test-tunnel (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Updating microsocks will fix bugs in testing: #1081602
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/microsocks.html
    • autopkgtest for microsocks/1.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
    • 30 days old (needed 2 days)
• python-django-timescaledb (- to 0.2.13-1)
  • Migration status for python-django-timescaledb (- to 0.2.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-django-timescaledb/0.2.13-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-timescaledb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 10 days)
• rust-slice-ring-buffer (- to 0.3.4-1)
  • Migration status for rust-slice-ring-buffer (- to 0.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-slice-ring-buffer/0.3.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: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-slice-ring-buffer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• sqlite3 (3.46.0-1 to 3.46.1-1)
  • Migration status for sqlite3 (3.46.0-1 to 3.46.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-sqlite3/1.6.9-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/s/sqlite3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• bpftop (- to 0.5.2-1)
  • Migration status for bpftop (- to 0.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bpftop would introduce bugs in testing: #1081685
    • autopkgtest for bpftop/0.5.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: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bpftop.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• dahdi-linux (- to 1:3.1.0+git20230717~dfsg-7)
  • Migration status for dahdi-linux (- to 1:3.1.0+git20230717~dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dahdi-linux/1:3.1.0+git20230717~dfsg-7: amd64: Regression or new test ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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/d/dahdi-linux.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 ♻
    • 31 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• kdevelop (- to 4:23.08.1-4)
  • Migration status for kdevelop (- to 4:23.08.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kdevelop would introduce bugs in testing: #1061689
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdevelop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• ncl (- to 6.6.2.dfsg.1-8)
  • Migration status for ncl (- to 6.6.2.dfsg.1-8): 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
    • Build-Depends(-Arch): ncl hdf-eos5 (not considered)
    • Build-Depends(-Arch): ncl libgctp (not considered)
    • Build-Depends(-Arch): ncl spherepack (not considered)
    • Depends: ncl hdf-eos5 (not considered)
    • Depends: ncl libgctp (not considered)
    • Depends: ncl spherepack (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ncl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 31 days old (needed 5 days)
• python-rdflib-endpoint (- to 0.5.1-2)
  • Migration status for python-rdflib-endpoint (- to 0.5.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-rdflib-endpoint fastapi (not considered)
    • Depends: python-rdflib-endpoint fastapi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-rdflib-endpoint.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• python-test-tunnel (- to 0.1.1-2)
  • Migration status for python-test-tunnel (- to 0.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-test-tunnel/0.1.1-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/p/python-test-tunnel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• rust-ring (0.17.5-1 to 0.17.8-1)
  • Migration status for rust-ring (0.17.5-1 to 0.17.8-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 rust-ring/0.17.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating rust-ring will fix bugs in testing: #1081600
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ring.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 31 days old (needed 5 days)
• ui-utilcpp (- to 1.10.4-1)
  • Migration status for ui-utilcpp (- to 1.10.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): ui-utilcpp ucommon (not considered)
    • Depends: ui-utilcpp ucommon (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ui-utilcpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• yalexs-ble (- to 2.4.3-2)
  • Migration status for yalexs-ble (- to 2.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for yalexs-ble/2.4.3-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/y/yalexs-ble.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 31 days old (needed 5 days)
• adios (- to 1.13.1-37)
  • Migration status for adios (- to 1.13.1-37): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating adios would introduce bugs in testing: #1081052
    • Impossible Build-Depends(-Arch): adios -> libhdf5-openmpi-dev/1.10.10+repack-3.3+b1/armel
    • Impossible Build-Depends(-Arch): adios -> libhdf5-openmpi-dev/1.10.10+repack-3.3+b1/armhf
    • Impossible Build-Depends(-Arch): adios -> libhdf5-openmpi-dev/1.10.10+repack-3.3+b1/i386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adios.html
    • autopkgtest for adios/1.13.1-37: 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
    • 32 days old (needed 2 days)
• ansible-core (2.17.1-1 to 2.17.3-1)
  • Migration status for ansible-core (2.17.1-1 to 2.17.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ansible-core/2.17.3-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ansible-core/blocked-on-ci-infra: riscv64: Failed (not a regression)
  • Additional info:
    • Updating ansible-core will fix bugs in testing: #1079672
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ansible-core.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• delve (1.22.1-1 to 1.23.0-1)
  • Migration status for delve (1.22.1-1 to 1.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for delve/1.23.0-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), i386: Pass
    • Built-Using: delve golang-1.23
  • Additional info:
    • Updating delve will fix bugs in testing: #1081603
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/delve.html
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• golang-github-hugelgupf-p9 (- to 0.3.0-2)
  • Migration status for golang-github-hugelgupf-p9 (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by siretart, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by siretart
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hugelgupf-p9.html
    • autopkgtest for golang-github-hugelgupf-p9/0.3.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
    • 32 days old (needed 2 days)
• lenovolegionlinux (- to 0.0.16+ds-1)
  • Migration status for lenovolegionlinux (- to 0.0.16+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lenovolegionlinux would introduce bugs in testing: #1070824
    • autopkgtest for lenovolegionlinux/0.0.16+ds-1: amd64: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lenovolegionlinux.html
    • Reproducible on amd64 - info ♻
    • 32 days old (needed 5 days)
• libgctp (- to 2.0.0-10)
  • Migration status for libgctp (- to 2.0.0-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgctp would introduce bugs in testing: #1078866
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgctp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• python-pyfunceble (- to 4.2.25.dev-1)
  • Migration status for python-pyfunceble (- to 4.2.25.dev-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mitya57@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyfunceble.html
    • autopkgtest for python-pyfunceble/4.2.25.dev-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
    • 32 days old (needed 2 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 ♻
    • 32 days old (needed 5 days)
• genomicsdb (- to 1.5.3-3)
  • Migration status for genomicsdb (- to 1.5.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libgenomicsdb-java/arm64 has unsatisfiable dependency
    • autopkgtest for genomicsdb/1.5.3-3: amd64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/genomicsdb.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 33 days old (needed 5 days)
• qtsystems-opensource-src (5.0~git20230712.81e08ee+dfsg-1 to 5.0~git20230712.81e08ee+dfsg-2)
  • Migration status for qtsystems-opensource-src (5.0~git20230712.81e08ee+dfsg-1 to 5.0~git20230712.81e08ee+dfsg-2): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtsystems-opensource-src.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 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
    • Not built on buildd: arch arm64 binaries uploaded by tar
  • 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 ♻
    • 33 days old (needed 5 days)
• aionotion (- to 2024.3.1-2)
  • Migration status for aionotion (- to 2024.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for aionotion/2024.3.1-2: 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/a/aionotion.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 34 days old (needed 5 days)
• far2l (2.6.2~beta+ds-1 to 2.6.3~beta+ds-1)
  • Migration status for far2l (2.6.2~beta+ds-1 to 2.6.3~beta+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
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Updating far2l will fix bugs in testing: #1081451
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/far2l.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 34 days old (needed 5 days)
• pygeofilter (- to 0.2.4-2)
  • Migration status for pygeofilter (- to 0.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pygeofilter geoalchemy2 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pygeofilter.html
    • autopkgtest for pygeofilter/0.2.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
    • 34 days old (needed 2 days)
• python-aiobotocore (- to 2.13.1-1)
  • Migration status for python-aiobotocore (- to 2.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python-aiobotocore unsatisfiable Build-Depends-Indep on amd64: python3-moto
    • 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-aiobotocore.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 ♻
    • 34 days old (needed 5 days)
• rust-k256 (- to 0.13.3-1)
  • Migration status for rust-k256 (- to 0.13.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-k256/0.13.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/r/rust-k256.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 34 days old (needed 5 days)
• rust-ocb3 (- to 0.1.0-1)
  • Migration status for rust-ocb3 (- to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ocb3/0.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/r/rust-ocb3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 34 days old (needed 5 days)
• stream-zip (- to 0.0.82-2)
  • Migration status for stream-zip (- to 0.0.82-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for stream-zip/0.0.82-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/s/stream-zip.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 ♻
    • 34 days old (needed 5 days)
• xorgxrdp (1:0.9.19-1 to 1:0.10.2-1)
  • Migration status for xorgxrdp (1:0.9.19-1 to 1:0.10.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xorgxrdp xrdp (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xorgxrdp.html
    • autopkgtest for xorgxrdp/1:0.10.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)
• libervia-templates (- to 0.9.0~hg400+dfsg-1)
  • Migration status for libervia-templates (- to 0.9.0~hg400+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libervia-templates would introduce bugs in testing: #1077419
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libervia-templates.html
    • autopkgtest for libervia-templates/0.9.0~hg400+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 35 days old (needed 5 days)
• nabu (- to 2024.1.9-1)
  • Migration status for nabu (- to 2024.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nabu/2024.1.9-1: amd64: Pass, 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: No tests, superficial or marked flaky ♻
  • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 35 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-460 (- to 460.106.00-17)
  • Migration status for nvidia-graphics-drivers-tesla-460 (- to 460.106.00-17): 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-17: 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 ♻
    • 35 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• packagesearch (- to 2.8.3)
  • Migration status for packagesearch (- to 2.8.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: packagesearch debtags (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 35 days old (needed 5 days)
• audit (1:3.1.2-4 to 1:4.0.1-1)
  • Migration status for audit (1:3.1.2-4 to 1:4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating audit would introduce bugs in testing: #1078810
    • autopkgtest for audit/1:4.0.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • missing build on mips64el
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating audit will fix bugs in testing: #1081306
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/audit.html
    • 36 days old (needed 5 days)
• gvm-libs (- to 22.10.0-1.1)
  • Migration status for gvm-libs (- to 22.10.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gvm-libs would introduce bugs in testing: #986529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvm-libs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 36 days old (needed 5 days)
• libcaptcha-recaptcha-v3-perl (- to 0.05-1)
  • Migration status for libcaptcha-recaptcha-v3-perl (- to 0.05-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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/libc/libcaptcha-recaptcha-v3-perl.html
    • autopkgtest for libcaptcha-recaptcha-v3-perl/0.05-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
    • 36 days old (needed 7 days)
• ruby-stackprof (0.2.25-2 to 0.2.26-1)
  • Migration status for ruby-stackprof (0.2.25-2 to 0.2.26-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-stackprof would introduce bugs in testing: #1078501, #994456
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • 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:i386 not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for ruby-stackprof/0.2.26-1: amd64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Updating ruby-stackprof will fix bugs in testing: #1081304
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-stackprof.html
    • 36 days old (needed 5 days)
• ampliconnoise (- to 1.29-13)
  • Migration status for ampliconnoise (- to 1.29-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ampliconnoise/1.29-13: 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/a/ampliconnoise.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• cups-pk-helper (0.2.6-1 to 0.2.6-2)
  • Migration status for cups-pk-helper (0.2.6-1 to 0.2.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cups-pk-helper would introduce bugs in testing: #1079125, #1079293
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cups-pk-helper.html
  • Additional info:
    • Updating cups-pk-helper will fix bugs in testing: #1081121
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• pyferret (- to 7.6.5-6)
  • Migration status for pyferret (- to 7.6.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pyferret/7.6.5-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): pyferret ferret-vis (not considered)
    • Depends: pyferret ferret-vis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyferret.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 ♻
    • 37 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• r-cran-effectsize (- to 0.8.9+dfsg-1)
  • Migration status for r-cran-effectsize (- to 0.8.9+dfsg-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-effectsize r-cran-performance (not considered)
    • Depends: r-cran-effectsize r-cran-performance (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-effectsize.html
    • autopkgtest for r-cran-effectsize/0.8.9+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
    • 37 days old (needed 2 days)
• r-cran-psychtools (2.4.2-1 to 2.4.3-1)
  • Migration status for r-cran-psychtools (2.4.2-1 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:
    • Updating r-cran-psychtools will fix bugs in testing: #1081118
    • 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 ♻
    • 37 days old (needed 5 days)
• r-cran-survey (4.2-1-1 to 4.4-2-1)
  • Migration status for r-cran-survey (4.2-1-1 to 4.4-2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-gb2/2.1.1-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-gb2/n/a: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-cran-survey/4.4-2-1: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating r-cran-survey will fix bugs in testing: #1081117
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-survey.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• mccode (- to 0.0~git20240801183257.cdaa431+ds5-2)
  • Migration status for mccode (- to 0.0~git20240801183257.cdaa431+ds5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Depends: mccode cif2hkl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mccode.html
    • autopkgtest for mccode/0.0~git20240801183257.cdaa431+ds5-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
    • 38 days old (needed 2 days)
    • Remove hint for (transitive) dependency: cif2hkl, mccode
• nvidia-graphics-drivers-tesla-450 (- to 450.248.02-7)
  • Migration status for nvidia-graphics-drivers-tesla-450 (- to 450.248.02-7): 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-7: 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 ♻
    • 38 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• onionshare (2.6.2-2 to 2.6.2-3)
  • Migration status for onionshare (2.6.2-2 to 2.6.2-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): onionshare pyside6 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onionshare.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 38 days old (needed 5 days)
• python-aiohomekit (- to 3.2.1-2)
  • Migration status for python-aiohomekit (- to 3.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiohomekit would introduce bugs in testing: #1081352
    • Build-Depends-Indep: python-aiohomekit aiocoap (not considered)
    • Depends: python-aiohomekit aiocoap (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiohomekit.html
    • uninstallable on arch i386 (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 ♻
    • 38 days old (needed 5 days)
• r-cran-smcfcs (1.7.1+dfsg-1 to 1.8.0+dfsg-1)
  • Migration status for r-cran-smcfcs (1.7.1+dfsg-1 to 1.8.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-smcfcs/1.8.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 ♻)
  • Additional info:
    • Updating r-cran-smcfcs will fix bugs in testing: #1081031
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-smcfcs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 38 days old (needed 5 days)
• ruby-github-markup (- to 1.7.0+dfsg-6.1)
  • Migration status for ruby-github-markup (- to 1.7.0+dfsg-6.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-github-markup ruby-html-pipeline (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-github-markup.html
    • autopkgtest for ruby-github-markup/1.7.0+dfsg-6.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
    • 38 days old (needed 2 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 ♻
    • 38 days old (needed 5 days)
• async-upnp-client (- to 0.40.0-1)
  • Migration status for async-upnp-client (- to 0.40.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating async-upnp-client would introduce bugs in testing: #1081334
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/async-upnp-client.html
    • 39 days old (needed 5 days)
• ats2-lang (- to 0.4.2-2)
  • Migration status for ats2-lang (- to 0.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by mrd
    • Not built on buildd: arch all binaries uploaded by mrd, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ats2-lang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 39 days old (needed 5 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 ♻
    • 39 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 ♻
    • 39 days old (needed 5 days)
• python-pyqtgraph (0.13.7-1 to 0.13.7-4)
  • Migration status for python-pyqtgraph (0.13.7-1 to 0.13.7-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-pyqtgraph pyside6 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Updating python-pyqtgraph will fix bugs in testing: #1080992
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyqtgraph.html
    • autopkgtest for python-pyqtgraph/0.13.7-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), 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 ♻
    • 39 days old (needed 5 days)
• rust-dirty-tracker (- to 0.3.0-1)
  • Migration status for rust-dirty-tracker (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-dirty-tracker/0.3.0-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/rust-dirty-tracker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 39 days old (needed 5 days)
• slurm-wlm-contrib (- to 24.05.2-1)
  • Migration status for slurm-wlm-contrib (- to 24.05.2-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)
    • 39 days old (needed 5 days)
• pynfft (- to 1.3.2-10)
  • Migration status for pynfft (- to 1.3.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pynfft would introduce bugs in testing: #1077919
    • Build-Depends(-Arch): pynfft nfft (not considered)
    • Depends: pynfft nfft (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynfft.html
    • autopkgtest for pynfft/1.3.2-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
    • 40 days old (needed 2 days)
• python-pvo (- to 2.1.1-2)
  • Migration status for python-pvo (- to 2.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-pvo/2.1.1-2: 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/p/python-pvo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 40 days old (needed 5 days)
• rust-env-logger-0.7 (- to 0.7.1-5)
  • Migration status for rust-env-logger-0.7 (- to 0.7.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-env-logger-0.7 would introduce bugs in testing: #1054156
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-env-logger-0.7.html
    • autopkgtest for rust-env-logger-0.7/0.7.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
    • 40 days old (needed 2 days)
• ipyparallel (- to 8.8.0-3)
  • Migration status for ipyparallel (- to 8.8.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ipyparallel/8.8.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): ipyparallel entrypoints (not considered)
    • Depends: ipyparallel entrypoints (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ipyparallel.html
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 41 days old (needed 5 days)
• ledmon (- to 0.97-1.1)
  • Migration status for ledmon (- to 0.97-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ledmon would introduce bugs in testing: #1077904
    • 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/l/ledmon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 41 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-418 (- to 418.226.00-16)
  • Migration status for nvidia-graphics-drivers-tesla-418 (- to 418.226.00-16): 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
    • autopkgtest for nvidia-graphics-drivers-tesla-418/418.226.00-16: 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
    • 41 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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 ♻
    • 42 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: python-open-meteo ruff (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-open-meteo.html
    • uninstallable on arch i386 (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 ♻
    • 42 days old (needed 5 days)
• bdebstrap (- to 0.7.0-1)
  • Migration status for bdebstrap (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for bdebstrap/0.7.0-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/b/bdebstrap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 43 days old (needed 5 days)
• certmonger (- to 0.79.19-1.1)
  • Migration status for certmonger (- to 0.79.19-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating certmonger would introduce bugs in testing: #1077766
    • 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/c/certmonger.html
    • 43 days old (needed 5 days)
• opensnitch (- to 1.5.8.1-2)
  • Migration status for opensnitch (- to 1.5.8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensnitch would introduce bugs in testing: #1074241
    • missing build on ppc64el
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 binaries not found
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for opensnitch/1.5.8.1-2: amd64: Pass, arm64: Pass, armhf: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensnitch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 43 days old (needed 5 days)
• python-thinc (- to 9.0.0-2)
  • Migration status for python-thinc (- to 9.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): python-thinc python-srsly (not considered)
    • Depends: python-thinc python-srsly (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: python-thinc python-catalogue
    • Depends: python-thinc python-confection (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-thinc.html
    • autopkgtest for python-thinc/9.0.0-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 ♻, 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 ♻
    • 43 days old (needed 5 days)
• freeipa (- to 4.11.1-2.1)
  • Migration status for freeipa (- to 4.11.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freeipa would introduce bugs in testing: #1018359
    • Depends: freeipa certmonger (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freeipa.html
    • autopkgtest for freeipa/4.11.1-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 ♻
    • 44 days old (needed 5 days)
• python-catalogue (- to 2.1.0-6)
  • Migration status for python-catalogue (- to 2.1.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-catalogue python-srsly (not considered)
    • Depends: python-catalogue python-srsly (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-catalogue.html
    • autopkgtest for python-catalogue/2.1.0-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 ♻
    • 44 days old (needed 5 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: 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: Regression or new test ♻
    • Build-Depends(-Arch): python-confection python-srsly (not considered)
    • Depends: python-confection python-srsly (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-confection.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 44 days old (needed 5 days)
• ruby-optimist (3.0.0-2 to 3.1.0-1)
  • Migration status for ruby-optimist (3.0.0-2 to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lolcat/100.0.1-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for ruby-optimist/3.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not built on buildd: arch all binaries uploaded by abhijith@openmailbox.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating ruby-optimist will fix bugs in testing: #1080990
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-optimist.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 44 days old (needed 5 days)
• exchange-calendars (- to 4.5.5-2)
  • Migration status for exchange-calendars (- to 4.5.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for exchange-calendars/4.5.5-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/e/exchange-calendars.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 45 days old (needed 5 days)
• mysql-8.0 (- to 8.0.39-1)
  • Migration status for mysql-8.0 (- to 8.0.39-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-8.0 would introduce bugs in testing: #853008
    • autopkgtest for mysql-8.0/8.0.39-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: Pass, 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
    • 45 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:
    • 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 ♻
    • 45 days old (needed 5 days)
• pcp (- to 6.3.0-1)
  • Migration status for pcp (- to 6.3.0-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 ♻
    • 46 days old (needed 5 days)
• bfh-metapackages (- to 20211009-27)
  • Migration status for bfh-metapackages (- to 20211009-27): 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
    • Depends: bfh-metapackages lnav (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bfh-metapackages.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 47 days old (needed 5 days)
• hdf-eos5 (- to 2:2.0-4)
  • Migration status for hdf-eos5 (- to 2:2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hdf-eos5 would introduce bugs in testing: #1078366
    • Build-Depends(-Arch): hdf-eos5 libgctp (not considered)
    • Depends: hdf-eos5 libgctp (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hdf-eos5.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 ♻
    • 47 days old (needed 5 days)
• newsboat (- to 2.36-1)
  • Migration status for newsboat (- to 2.36-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating newsboat would introduce bugs in testing: #1077951
    • autopkgtest for newsboat/2.36-1: 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/n/newsboat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 47 days old (needed 5 days)
• progress-linux-metapackages (- to 20221002-16)
  • Migration status for progress-linux-metapackages (- to 20221002-16): 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
    • Depends: progress-linux-metapackages lnav (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/progress-linux-metapackages.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 47 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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 ♻
    • 47 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 ♻
    • 48 days old (needed 5 days)
• pageedit (2.0.0+dfsg-1 to 2.2.0+dfsg-1)
  • Migration status for pageedit (2.0.0+dfsg-1 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:
    • Updating pageedit will fix bugs in testing: #1080987
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pageedit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 48 days old (needed 5 days)
• sigil (2.0.1+dfsg1-1 to 2.2.1+dfsg-1)
  • Migration status for sigil (2.0.1+dfsg1-1 to 2.2.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sigil unsatisfiable Build-Depends(-Arch) on mips64el: qt6-webengine-dev
    • missing build on mips64el
  • Additional info:
    • Updating sigil will fix bugs in testing: #1080986
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sigil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 days old (needed 5 days)
• smifb2 (- to 2.3.0.9.g20b8ef5-1)
  • Migration status for smifb2 (- to 2.3.0.9.g20b8ef5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smifb2 would introduce bugs in testing: #1077842
    • autopkgtest for smifb2/2.3.0.9.g20b8ef5-1: 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 ♻
    • 48 days old (needed 5 days)
• lnav (- to 0.12.2-1)
  • Migration status for lnav (- to 0.12.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lnav would introduce bugs in testing: #1067018, #1067284
    • 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/l/lnav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 49 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-390xx (- to 390.157-8)
  • Migration status for nvidia-graphics-drivers-legacy-390xx (- to 390.157-8): 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
    • 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-8: amd64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • 49 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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 ♻
    • 50 days old (needed 5 days)
• debian-codesearch-cli (- to 1.0.0)
  • Migration status for debian-codesearch-cli (- to 1.0.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-codesearch-cli.html
    • autopkgtest for debian-codesearch-cli/1.0.0: 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 ♻
    • 50 days old (needed 5 days)
• emacs-jedi (- to 0.2.8+git20220410.81c5a42-2)
  • Migration status for emacs-jedi (- to 0.2.8+git20220410.81c5a42-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-jedi would introduce bugs in testing: #994171
    • Build-Depends(-Arch): emacs-jedi auto-complete-el (not considered)
    • Depends: emacs-jedi auto-complete-el (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-jedi.html
    • autopkgtest for emacs-jedi/0.2.8+git20220410.81c5a42-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
    • 50 days old (needed 2 days)
• flask-security (- to 5.5.0-1)
  • Migration status for flask-security (- to 5.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Build-Depends(-Arch): flask-security flask-wtf (not considered)
    • Depends: flask-security flask-wtf (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-security.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 50 days old (needed 5 days)
    • Remove hint for (transitive) dependency: flask-security, flask-wtf
• golang-github-google-s2a-go (- to 0.1.7-3)
  • Migration status for golang-github-google-s2a-go (- to 0.1.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-google-s2a-go/0.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/g/golang-github-google-s2a-go.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 50 days old (needed 5 days)
• magit-forge-el (- to 0.3.2+git20231227.1.299bbaa-2)
  • Migration status for magit-forge-el (- to 0.3.2+git20231227.1.299bbaa-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating magit-forge-el would introduce bugs in testing: #1068900
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magit-forge-el.html
    • autopkgtest for magit-forge-el/0.3.2+git20231227.1.299bbaa-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
    • 50 days old (needed 2 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
    • 50 days old (needed 2 days)
• php-guzzlehttp-uri-template (- to 1.0.3-1)
  • Migration status for php-guzzlehttp-uri-template (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-guzzlehttp-uri-template.html
    • autopkgtest for php-guzzlehttp-uri-template/1.0.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
    • 50 days old (needed 2 days)
• rg-el (- to 2.3.0-3)
  • Migration status for rg-el (- to 2.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rg-el/2.3.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rg-el.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 50 days old (needed 5 days)
• rtags (- to 2.38-12)
  • Migration status for rtags (- to 2.38-12): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rtags auto-complete-el (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rtags.html
    • autopkgtest for rtags/2.38-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 50 days old (needed 2 days)
• scala-mode-el (- to 1:1.1.0-4)
  • Migration status for scala-mode-el (- to 1:1.1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scala-mode-el would introduce bugs in testing: #1052917
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scala-mode-el.html
    • 50 days old (needed 5 days)
• thin (1.8.1-2 to 1.8.2-1)
  • Migration status for thin (1.8.1-2 to 1.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating thin would introduce bugs in testing: #1078358
  • Additional info:
    • Updating thin will fix bugs in testing: #1079724
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/thin.html
    • autopkgtest for thin/1.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 50 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
    • 51 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
    • 51 days old (needed 2 days)
• helpful-el (- to 0.21-3)
  • Migration status for helpful-el (- to 0.21-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating helpful-el would introduce bugs in testing: #1077351
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/helpful-el.html
    • autopkgtest for helpful-el/0.21-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
    • 51 days old (needed 2 days)
• cinder (- to 2:24.0.0-8)
  • Migration status for cinder (- to 2:24.0.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cinder/2:24.0.0-8: 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: 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) - https://piuparts.debian.org/sid/source/c/cinder.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 ♻
    • 52 days old (needed 5 days)
• golang-github-gizak-termui (- to 3.1.0-1)
  • Migration status for golang-github-gizak-termui (- to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gizak-termui.html
    • autopkgtest for golang-github-gizak-termui/3.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
    • 52 days old (needed 2 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:
    • Updating numba would introduce bugs in testing: #1033907, #1077047
    • autopkgtest for numba/0.59.1+dfsg-3: amd64: Pass
    • autopkgtest for numba/blocked-on-ci-infra: ppc64el: Regression or new test ♻
    • 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)
    • Depends: numba llvmlite (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/numba.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 52 days old (needed 5 days)
• ruby-semver-dialects (- to 2.0.2-2)
  • Migration status for ruby-semver-dialects (- to 2.0.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-semver-dialects ruby-deb-version (not considered)
    • Depends: ruby-semver-dialects ruby-deb-version (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-semver-dialects.html
    • autopkgtest for ruby-semver-dialects/2.0.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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 52 days old (needed 5 days)
• ruby-timecop (0.9.8-1 to 0.9.10-1)
  • Migration status for ruby-timecop (0.9.8-1 to 0.9.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-timecop/0.9.10-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-timecop will fix bugs in testing: #1079550
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-timecop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 52 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
    • 52 days old (needed 5 days)
• fence-agents (- to 4.15.0-1)
  • Migration status for fence-agents (- to 4.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fence-agents/4.15.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: Pass, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by Valentin.Vidic@CARNet.hr, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): fence-agents python-oauth2client (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fence-agents.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 53 days old (needed 5 days)
• r-cran-stars (- to 0.6-6-1)
  • Migration status for r-cran-stars (- to 0.6-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-stars r-cran-sf (not considered)
    • Depends: r-cran-stars r-cran-sf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-stars.html
    • autopkgtest for r-cran-stars/0.6-6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 53 days old (needed 5 days)
• rapiddisk (- to 9.1.0-3)
  • Migration status for rapiddisk (- to 9.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rapiddisk would introduce bugs in testing: #1069945, #1070418
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/rapiddisk.html
    • autopkgtest for rapiddisk/9.1.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:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 53 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
    • 53 days old (needed 5 days)
• coot (- to 1.1.09+dfsg-2)
  • Migration status for coot (- to 1.1.09+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for coot/1.1.09+dfsg-2: amd64: Pass, arm64: Pass, armhf: Regression or new test ♻, ppc64el: Pass
    • Build-Depends(-Arch): coot clipper
    • Build-Depends(-Arch): coot libccp4 (not considered)
    • Build-Depends(-Arch): coot ssm
    • Depends: coot clipper
    • Depends: coot ssm
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coot.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 54 days old (needed 5 days)
• fonts-cascadia-code (- to 2404.23+ds-1)
  • Migration status for fonts-cascadia-code (- to 2404.23+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-cascadia-code would introduce bugs in testing: #1077328
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-cascadia-code.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 54 days old (needed 5 days)
• jenkins-job-builder (- to 3.11.0-7)
  • Migration status for jenkins-job-builder (- to 3.11.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for jenkins-job-builder/3.11.0-7: amd64: Regression or new test ♻, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends-Indep: jenkins-job-builder python-jenkins (not considered)
    • Depends: jenkins-job-builder python-jenkins (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jenkins-job-builder.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 54 days old (needed 5 days)
• pynpoint (- to 0.11.0-3)
  • Migration status for pynpoint (- to 0.11.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pynpoint numba (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynpoint.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 54 days old (needed 5 days)
• r-cran-spdep (- to 1.3-5+dfsg-1)
  • Migration status for r-cran-spdep (- to 1.3-5+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-spdep r-cran-sf (not considered)
    • Depends: r-cran-spdep r-cran-sf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spdep.html
    • autopkgtest for r-cran-spdep/1.3-5+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
    • 54 days old (needed 2 days)
• btm (- to 0.9.6+20240202-2)
  • Migration status for btm (- to 0.9.6+20240202-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating btm would introduce bugs in testing: #1078497
    • btm unsatisfiable Build-Depends(-Arch) on amd64: librust-ratatui-0.25+default-dev
    • btm unsatisfiable Build-Depends(-Arch) on amd64: librust-toml-edit-dev (<< 0.22)
    • btm unsatisfiable Build-Depends(-Arch) on arm64: librust-ratatui-0.25+default-dev
    • btm unsatisfiable Build-Depends(-Arch) on arm64: librust-toml-edit-dev (<< 0.22)
    • btm unsatisfiable Build-Depends(-Arch) on armel: librust-ratatui-0.25+default-dev
    • btm unsatisfiable Build-Depends(-Arch) on armel: librust-toml-edit-dev (<< 0.22)
    • btm unsatisfiable Build-Depends(-Arch) on armhf: librust-ratatui-0.25+default-dev
    • btm unsatisfiable Build-Depends(-Arch) on armhf: librust-toml-edit-dev (<< 0.22)
    • btm unsatisfiable Build-Depends(-Arch) on i386: librust-ratatui-0.25+default-dev
    • btm unsatisfiable Build-Depends(-Arch) on i386: librust-toml-edit-dev (<< 0.22)
    • btm unsatisfiable Build-Depends(-Arch) on mips64el: librust-ratatui-0.25+default-dev
    • btm unsatisfiable Build-Depends(-Arch) on mips64el: librust-toml-edit-dev (<< 0.22)
    • btm unsatisfiable Build-Depends(-Arch) on ppc64el: librust-ratatui-0.25+default-dev
    • btm unsatisfiable Build-Depends(-Arch) on ppc64el: librust-toml-edit-dev (<< 0.22)
    • btm unsatisfiable Build-Depends(-Arch) on riscv64: librust-ratatui-0.25+default-dev
    • btm unsatisfiable Build-Depends(-Arch) on riscv64: librust-toml-edit-dev (<< 0.22)
    • btm unsatisfiable Build-Depends(-Arch) on s390x: librust-ratatui-0.25+default-dev
    • btm unsatisfiable Build-Depends(-Arch) on s390x: librust-toml-edit-dev (<< 0.22)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btm.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 ♻
    • 55 days old (needed 5 days)
• freerdp2 (2.11.5+dfsg1-1 to 2.11.7+dfsg1-2)
  • Migration status for freerdp2 (2.11.5+dfsg1-1 to 2.11.7+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freerdp2 would introduce bugs in testing: #1079025
    • autopkgtest for freerdp2/2.11.7+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:
    • Updating freerdp2 will fix bugs in testing: #1069728, #1079009
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freerdp2.html
    • 56 days old (needed 5 days)
• gosa-plugins-rolemanagement (- to 2.8~git20211022.90f50d1-1)
  • Migration status for gosa-plugins-rolemanagement (- to 2.8~git20211022.90f50d1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
    • Depends: gosa-plugins-rolemanagement gosa
  • 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 ♻
    • 56 days old (needed 5 days)
• heudiconv (- to 1.1.6-1)
  • Migration status for heudiconv (- to 1.1.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): heudiconv nipype (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/heudiconv.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 56 days old (needed 5 days)
• openjdk-8 (- to 8u422-b05-1)
  • Migration status for openjdk-8 (- to 8u422-b05-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-8 would introduce bugs in testing: #989736
    • autopkgtest for openjdk-8/blocked-on-ci-infra: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-8.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 56 days old (needed 5 days)
• ddcci-driver-linux (- to 0.4.4-2)
  • Migration status for ddcci-driver-linux (- to 0.4.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ddcci-driver-linux would introduce bugs in testing: #1077212
    • autopkgtest for ddcci-driver-linux/0.4.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/ddcci-driver-linux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 57 days old (needed 5 days)
• faketime (0.9.10-2.1 to 0.9.10-2.2)
  • Migration status for faketime (0.9.10-2.1 to 0.9.10-2.2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • 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 faketime/0.9.10-2.2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating faketime will fix bugs in testing: #1079346
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/faketime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 57 days old (needed 5 days)
• pydrive2 (- to 1.20.0-1)
  • Migration status for pydrive2 (- to 1.20.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pydrive2 python-oauth2client (not considered)
    • Depends: pydrive2 python-oauth2client (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • 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 ♻
    • 57 days old (needed 5 days)
• rust-microformats (- to 0.6.2-1)
  • Migration status for rust-microformats (- to 0.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-microformats would introduce bugs in testing: #1050087
    • autopkgtest for rust-microformats/0.6.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/r/rust-microformats.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 57 days old (needed 5 days)
• cdlclient (- to 0.10.1-1)
  • Migration status for cdlclient (- to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cdlclient/0.10.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, 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/c/cdlclient.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 58 days old (needed 5 days)
• ruby-ronn (0.9.1-3 to 0.10.1-1)
  • Migration status for ruby-ronn (0.9.1-3 to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-ronn/0.10.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: Pass, s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating ruby-ronn will fix bugs in testing: #1073364
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ronn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 58 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tulip sip4 (not considered)
    • Depends: tulip sip4 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tulip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 58 days old (needed 5 days)
• booth (- to 1.1-4)
  • Migration status for booth (- to 1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for booth/1.1-4: amd64: Pass, arm64: Regression or new test ♻, 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/b/booth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 59 days old (needed 5 days)
• buteo-sync-plugins (- to 0.8.35-3)
  • Migration status for buteo-sync-plugins (- to 0.8.35-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): buteo-sync-plugins nemo-qml-plugin-contacts (not considered)
    • Depends: buteo-sync-plugins nemo-qml-plugin-contacts (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/buteo-sync-plugins.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 59 days old (needed 5 days)
• dxvk (- to 2.4-2)
  • Migration status for dxvk (- to 2.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dxvk would introduce bugs in testing: #982159
    • autopkgtest for dxvk/2.4-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, i386: Regression or new test ♻
    • Build-Depends(-Arch): dxvk wine-development (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dxvk.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 59 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ffcv numba (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/ffcv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 59 days old (needed 5 days)
• r-cran-epir (- to 2.0.75+dfsg-1)
  • Migration status for r-cran-epir (- to 2.0.75+dfsg-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-epir r-cran-sf (not considered)
    • Depends: r-cran-epir r-cran-sf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-epir.html
    • autopkgtest for r-cran-epir/2.0.75+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 ♻
    • Required age reduced by 3 days because of autopkgtest
    • 59 days old (needed 2 days)
• r-cran-rpact (- to 4.0.0-1)
  • Migration status for r-cran-rpact (- to 4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-rpact/4.0.0-1: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
  • 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 ♻
    • 59 days old (needed 5 days)
• virtualbox (- to 7.0.20-dfsg-1)
  • Migration status for virtualbox (- to 7.0.20-dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtualbox would introduce bugs in testing: #1057014, #794466
    • autopkgtest for virtualbox/7.0.20-dfsg-1: amd64: No tests, superficial or marked flaky ♻, i386: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 59 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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 ♻
    • 60 days old (needed 5 days)
• txdbus (1.1.0-3 to 1.1.0-5)
  • Migration status for txdbus (1.1.0-3 to 1.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for txdbus/1.1.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
    • Not built on buildd: upload info for arch all binaries not found, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating txdbus will fix bugs in testing: #1074642, #1079006
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/txdbus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 60 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 s390x (which is allowed), not running autopkgtest there
    • 60 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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 ♻
    • 61 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
    • autopkgtest for sks/1.1.6+git20210302.c3ba6d5a-4.1: amd64: Pass, arm64: 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/s/sks.html
    • uninstallable on arch armel, not running autopkgtest there
    • 61 days old (needed 5 days)
• libplayerone (- to 3.1.0+20221218103507-2)
  • Migration status for libplayerone (- to 3.1.0+20221218103507-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libplayerone would introduce bugs in testing: #1076374, #1076375
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 62 days old (needed 5 days)
• nvidia-nccl (2.18.5-1-2 to 2.22.3-1-1)
  • Migration status for nvidia-nccl (2.18.5-1-2 to 2.22.3-1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating nvidia-nccl will fix bugs in testing: #1079007
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 62 days old (needed 5 days)
• contactsd (- to 1.4.14-2)
  • Migration status for contactsd (- to 1.4.14-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): contactsd nemo-qml-plugin-contacts (not considered)
    • Depends: contactsd nemo-qml-plugin-contacts (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/contactsd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 63 days old (needed 5 days)
• libgeo-libproj-ffi-perl (- to 1.00-1)
  • Migration status for libgeo-libproj-ffi-perl (- to 1.00-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libgeo-libproj-ffi-perl/1.00-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 frankie, a new source-only upload is needed to allow migration
  • 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 ♻
    • 63 days old (needed 5 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
    • 63 days old (needed 5 days)
• multispeech (- to 4.6.2-1)
  • Migration status for multispeech (- to 4.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by mitya57@gmail.com
    • Not built on buildd: arch all binaries uploaded by mitya57@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/multispeech.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 63 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 ♻
    • 63 days old (needed 5 days)
• rust-wasmtime (- to 19.0.0+dfsg-3)
  • Migration status for rust-wasmtime (- to 19.0.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-wasmtime would introduce bugs in testing: #1078317
    • autopkgtest for rust-wasmtime/19.0.0+dfsg-3: 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 ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-wasmtime.html
    • 63 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
    • Reproducible on armhf - info ♻
    • 64 days old (needed 5 days)
• hypercorn (0.14.4-1 to 0.17.3-1)
  • Migration status for hypercorn (0.14.4-1 to 0.17.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): hypercorn node-mermaid (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Updating hypercorn will fix bugs in testing: #1057351
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hypercorn.html
    • autopkgtest for hypercorn/0.17.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
    • 65 days old (needed 2 days)
• libccrtp (- to 2.0.9-4.1)
  • Migration status for libccrtp (- to 2.0.9-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libccrtp ucommon (not considered)
    • Depends: libccrtp ucommon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libccrtp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 67 days old (needed 5 days)
• mailfront (- to 2.12-3)
  • Migration status for mailfront (- to 2.12-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): mailfront freecdb (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): mailfront cvm (not considered)
    • Depends: mailfront cvm (not considered)
  • 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 ♻
    • 67 days old (needed 5 days)
• php-doctrine-persistence (3.3.2-3 to 3.3.3-1)
  • Migration status for php-doctrine-persistence (3.3.2-3 to 3.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating php-doctrine-persistence will fix bugs in testing: #1078926
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-doctrine-persistence.html
    • autopkgtest for php-doctrine-persistence/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
    • 67 days old (needed 2 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 ♻
    • 67 days old (needed 5 days)
• collectd (- to 5.12.0-18.1)
  • Migration status for collectd (- to 5.12.0-18.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating collectd would introduce bugs in testing: #1081073
    • autopkgtest for collectd/5.12.0-18.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): collectd libesmtp (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/collectd.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 ♻
    • 68 days old (needed 5 days)
• libxml-libxml-perl (2.0207+dfsg+really+2.0134-1 to 2.0207+dfsg+really+2.0134-4)
  • Migration status for libxml-libxml-perl (2.0207+dfsg+really+2.0134-1 to 2.0207+dfsg+really+2.0134-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: libxml-libxml-perl libxml2 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Updating libxml-libxml-perl will fix bugs in testing: #1072012
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxml-libxml-perl.html
    • autopkgtest for libxml-libxml-perl/2.0207+dfsg+really+2.0134-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
    • 68 days old (needed 2 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
    • Reproducible on armhf - info ♻
    • 68 days old (needed 5 days)
• git-ubuntu (- to 1.1-1)
  • Migration status for git-ubuntu (- to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for git-ubuntu/1.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 ♻
    • Not built on buildd: arch all binaries uploaded by bdrung, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-ubuntu.html
    • 69 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:
    • 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)
    • Depends: python-cogent numba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cogent.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 ♻
    • 70 days old (needed 5 days)
• slic3r-prusa (- to 2.8.0+dfsg-1)
  • Migration status for slic3r-prusa (- to 2.8.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for slic3r-prusa/2.8.0+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): slic3r-prusa openvdb (not considered)
    • Depends: slic3r-prusa openvdb (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r-prusa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 70 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
    • 71 days old (needed 5 days)
• php-zmq (- to 1.1.3-25)
  • Migration status for php-zmq (- to 1.1.3-25): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-zmq would introduce bugs in testing: #1075386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-zmq.html
    • Reproducible on armhf - info ♻
    • 71 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• ruby-redis-cluster-client (- to 0.10.0-1)
  • Migration status for ruby-redis-cluster-client (- to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-cluster-client.html
    • autopkgtest for ruby-redis-cluster-client/0.10.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 71 days old (needed 5 days)
• rust-cntr (- to 1.5.3-2)
  • Migration status for rust-cntr (- to 1.5.3-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Not built on buildd: upload info for arch i386 binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Build-Depends(-Arch): rust-cntr rust-cntr-fuse (not considered)
    • Depends: rust-cntr rust-cntr-fuse (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cntr.html
    • autopkgtest for rust-cntr/1.5.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
    • 71 days old (needed 2 days)
• rust-regex-cursor (- to 0.1.4-1)
  • Migration status for rust-regex-cursor (- to 0.1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-regex-cursor rust-ropey (not considered)
    • Depends: rust-regex-cursor rust-ropey (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-regex-cursor.html
    • autopkgtest for rust-regex-cursor/0.1.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
    • 71 days old (needed 2 days)
• tpm2-pytss (- to 2.3.0-1)
  • Migration status for tpm2-pytss (- to 2.3.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tpm2-pytss tpm2-tss (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpm2-pytss.html
    • autopkgtest for tpm2-pytss/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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 71 days old (needed 2 days)
• budgie-indicator-applet (- to 0.7.2-4)
  • Migration status for budgie-indicator-applet (- to 0.7.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): budgie-indicator-applet budgie-desktop (not considered)
    • Depends: budgie-indicator-applet budgie-desktop (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/budgie-indicator-applet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 72 days old (needed 5 days)
• djbdns (- to 1:1.05-16)
  • Migration status for djbdns (- to 1:1.05-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating djbdns would introduce bugs in testing: #1081076
    • autopkgtest for djbdns/1:1.05-16: 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 armhf - info ♻
    • 72 days old (needed 5 days)
• flask-babel (- to 4.1.0-1)
  • Migration status for flask-babel (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Updating flask-babel would introduce bugs in testing: #1077443
    • autopkgtest for flask-babel/4.1.0-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for flask-babel/n/a: riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-babel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 72 days old (needed 5 days)
    • Remove hint for (transitive) dependency: flask-babel
• genx (- to 3.6.23-1)
  • Migration status for genx (- to 3.6.23-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-genx/ppc64el has unsatisfiable dependency
    • autopkgtest for genx/3.6.23-1: amd64: Pass
    • Build-Depends(-Arch): genx numba (not considered)
    • Depends: genx numba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/genx.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • 72 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:
    • autopkgtest for yaramod/3.21.0-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yaramod.html
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 72 days old (needed 5 days)
• geophar (- to 18.10+dfsg1-4)
  • Migration status for geophar (- to 18.10+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating geophar would introduce bugs in testing: #1078365
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geophar.html
    • autopkgtest for geophar/18.10+dfsg1-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
    • 73 days old (needed 2 days)
• napari (- to 0.5.0~a5-1)
  • Migration status for napari (- to 0.5.0~a5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating napari would introduce bugs in testing: #1076970
    • autopkgtest for napari/0.5.0~a5-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 magicgui (not considered)
    • Build-Depends(-Arch): napari python-npe2 (not considered)
    • Depends: napari magicgui (not considered)
    • Depends: napari python-npe2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • 73 days old (needed 5 days)
• python-npe2 (- to 0.7.6-1)
  • Migration status for python-npe2 (- to 0.7.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-npe2/0.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 ♻
    • Build-Depends(-Arch): python-npe2 magicgui (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-npe2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 73 days old (needed 5 days)
• rocm-hipamd (5.7.1-3 to 5.7.1-4)
  • Migration status for rocm-hipamd (5.7.1-3 to 5.7.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kaol
    • Not built on buildd: arch all binaries uploaded by kaol, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating rocm-hipamd will fix bugs in testing: #1077859
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rocm-hipamd.html
    • autopkgtest for rocm-hipamd/5.7.1-4: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: 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 ♻
    • 73 days old (needed 5 days)
• rust-ruma-state-res (- to 0.8.0-3)
  • Migration status for rust-ruma-state-res (- to 0.8.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ruma-state-res/0.8.0-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): rust-ruma-state-res rust-ruma-common (not considered)
    • Depends: rust-ruma-state-res rust-criterion-0.3 (not considered)
    • Depends: rust-ruma-state-res rust-ruma-common (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - 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 ♻
    • 73 days old (needed 5 days)
• z88 (- to 13.0.0+dfsg2-7)
  • Migration status for z88 (- to 13.0.0+dfsg2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating z88 would introduce bugs in testing: #1077953
    • Build-Depends(-Arch): z88 gtkglext (not considered)
    • Depends: z88 gtkglext (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/z88.html
    • Reproducible on armhf - info ♻
    • 73 days old (needed 5 days)
• libtie-aliashash-perl (- to 1.02-1)
  • Migration status for libtie-aliashash-perl (- to 1.02-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by frankie, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtie-aliashash-perl.html
    • autopkgtest for libtie-aliashash-perl/1.02-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
    • 74 days old (needed 2 days)
• pulseaudio-dlna (- to 0.6.4.1-0.2)
  • Migration status for pulseaudio-dlna (- to 0.6.4.1-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pulseaudio-dlna would introduce bugs in testing: #1016288
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pulseaudio-dlna.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 74 days old (needed 5 days)
• pydevd (- to 3.1.0+ds-2)
  • Migration status for pydevd (- to 3.1.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Updating pydevd would introduce bugs in testing: #1077521
    • autopkgtest for pydevd/3.1.0+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pydevd/n/a: riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydevd.html
    • 74 days old (needed 5 days)
    • Remove hint for (transitive) dependency: pydevd
• dogecoin (- to 1.14.7-2)
  • Migration status for dogecoin (- to 1.14.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dogecoin would introduce bugs in testing: #1034806, #1076687
    • Impossible Depends: dogecoin -> libminiupnpc17/2.2.6-1+b1/amd64
    • Impossible Depends: dogecoin -> libminiupnpc17/2.2.6-1+b1/arm64
    • Impossible Depends: dogecoin -> libminiupnpc17/2.2.6-1+b1/armel
    • Impossible Depends: dogecoin -> libminiupnpc17/2.2.6-1+b1/armhf
    • Impossible Depends: dogecoin -> libminiupnpc17/2.2.6-1+b1/i386
    • Impossible Depends: dogecoin -> libminiupnpc17/2.2.6-1+b1/mips64el
    • Impossible Depends: dogecoin -> libminiupnpc17/2.2.6-1+b1/ppc64el
    • Impossible Depends: dogecoin -> libminiupnpc17/2.2.6-1+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dogecoin.html
    • Reproducible on armhf - info ♻
    • 75 days old (needed 5 days)
• elkcode (- to 9.6.8-1)
  • Migration status for elkcode (- to 9.6.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): elkcode wannier90 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elkcode.html
    • autopkgtest for elkcode/9.6.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 75 days old (needed 2 days)
• ergo (- to 3.8.2-1)
  • Migration status for ergo (- to 3.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ergo would introduce bugs in testing: #1056672
    • Build-Depends(-Arch): ergo atlas (not considered)
    • Depends: ergo atlas (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ergo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 75 days old (needed 5 days)
• golang-github-cronokirby-saferith (- to 0.33.0-3)
  • Migration status for golang-github-cronokirby-saferith (- to 0.33.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-cronokirby-saferith/0.33.0-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/g/golang-github-cronokirby-saferith.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 75 days old (needed 5 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
    • 75 days old (needed 2 days)
• netatalk (- to 3.1.18~ds-2)
  • Migration status for netatalk (- to 3.1.18~ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netatalk would introduce bugs in testing: #1073724
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netatalk.html
    • autopkgtest for netatalk/3.1.18~ds-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 75 days old (needed 5 days)
• rust-criterion-0.3 (- to 0.3.6-10)
  • Migration status for rust-criterion-0.3 (- to 0.3.6-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-criterion-0.3 would introduce bugs in testing: #1074104
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-criterion-0.3.html
    • autopkgtest for rust-criterion-0.3/0.3.6-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
    • 75 days old (needed 2 days)
• rust-ntp-udp (- to 1.1.3-2)
  • Migration status for rust-ntp-udp (- to 1.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-ntp-udp would introduce bugs in testing: #1056028
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ntp-udp.html
    • autopkgtest for rust-ntp-udp/1.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 75 days old (needed 2 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: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for symfit/n/a: riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/symfit.html
    • 75 days old (needed 5 days)
• bioxtasraw (- to 2.2.2-1)
  • Migration status for bioxtasraw (- 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): bioxtasraw numba (not considered)
    • Depends: bioxtasraw numba (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bioxtasraw.html
    • autopkgtest for bioxtasraw/2.2.2-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 76 days old (needed 5 days)
• colorcet (3.0.1-1 to 3.1.0-1)
  • Migration status for colorcet (3.0.1-1 to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for colorcet/3.1.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for colorcet/n/a: riscv64: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating colorcet will fix bugs in testing: #1077931
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/colorcet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 76 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
    • 76 days old (needed 2 days)
• golang-github-goccy-go-json (- to 0.10.3-2)
  • Migration status for golang-github-goccy-go-json (- to 0.10.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-goccy-go-json/0.10.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/g/golang-github-goccy-go-json.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 76 days old (needed 5 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 ♻
    • 76 days old (needed 5 days)
• grip (- to 4.6.1-1)
  • Migration status for grip (- to 4.6.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): grip octicons (not considered)
    • Depends: grip octicons (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grip.html
    • autopkgtest for grip/4.6.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
    • 76 days old (needed 2 days)
• hol-light (- to 20231021-2)
  • Migration status for hol-light (- to 20231021-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • hol-light/amd64 has unsatisfiable dependency
    • hol-light/arm64 has unsatisfiable dependency
    • hol-light/armel has unsatisfiable dependency
    • hol-light/armhf has unsatisfiable dependency
    • hol-light/i386 has unsatisfiable dependency
    • hol-light/mips64el has unsatisfiable dependency
    • hol-light/ppc64el has unsatisfiable dependency
    • hol-light/s390x has unsatisfiable dependency
    • Updating hol-light would introduce bugs in testing: #1073882
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hol-light.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 76 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 ♻
    • 76 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 ♻
    • 76 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 76 days old (needed 5 days)
• python-pyvista (- to 0.43.10-5)
  • Migration status for python-pyvista (- to 0.43.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-pyvista/0.43.10-5: 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: 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)
• 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 ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • 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 i386 binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Build-Depends(-Arch): rust-ntpd rust-ntp-udp (not considered)
    • Depends: rust-ntpd rust-ntp-udp (not considered)
  • 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 ♻
    • 77 days old (needed 5 days)
• sitecopy (- to 1:0.16.6-13)
  • Migration status for sitecopy (- to 1:0.16.6-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sitecopy would introduce bugs in testing: #1077410
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sitecopy.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 77 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: 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 ♻
    • Depends: gpscorrelate exiv2
  • 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 ♻
    • 78 days old (needed 5 days)
• plakativ (- to 0.5.2-3)
  • Migration status for plakativ (- to 0.5.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for plakativ/0.5.2-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • 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 ♻
    • 78 days old (needed 5 days)
• qgnomeplatform (- to 0.9.2-3)
  • Migration status for qgnomeplatform (- to 0.9.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qgnomeplatform would introduce bugs in testing: #1077421
    • 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qgnomeplatform.html
    • Reproducible on armhf - info ♻
    • 78 days old (needed 5 days)
• recoll (- to 1.39.0-1)
  • Migration status for recoll (- to 1.39.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating recoll would introduce bugs in testing: #1074451
    • recoll unsatisfiable Build-Depends(-Arch) on armel: qt6-webengine-dev
    • recoll unsatisfiable Build-Depends(-Arch) on mips64el: qt6-webengine-dev
    • recoll unsatisfiable Build-Depends(-Arch) on ppc64el: qt6-webengine-dev
    • recoll unsatisfiable Build-Depends(-Arch) on riscv64: qt6-webengine-dev
    • recoll unsatisfiable Build-Depends(-Arch) on s390x: qt6-webengine-dev
    • Not built on buildd: arch all binaries uploaded by kartik, a new source-only upload is needed to allow migration
    • 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/r/recoll.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 78 days old (needed 5 days)
• rust-cntr-fuse (- to 0.4.2-1)
  • Migration status for rust-cntr-fuse (- to 0.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-cntr-fuse/0.4.2-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-cntr-fuse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 78 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
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 79 days old (needed 5 days)
• embree (- to 4.3.2+dfsg-1)
  • Migration status for embree (- to 4.3.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): embree openimageio (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/embree.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 79 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 ♻
    • 79 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:
    • Updating q2cli would introduce bugs in testing: #1076080
    • autopkgtest for q2cli/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): q2cli qiime (not considered)
    • Depends: q2cli python3.11_pu (not considered)
    • Depends: q2cli q2-feature-table (not considered)
    • Depends: q2cli qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2cli.html
    • 79 days old (needed 5 days)
• magicgui (- to 0.7.2-4)
  • Migration status for magicgui (- to 0.7.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating magicgui would introduce bugs in testing: #1074724
    • autopkgtest for magicgui/0.7.2-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/m/magicgui.html
    • 80 days old (needed 5 days)
• orange3 (- to 3.37.0-1)
  • Migration status for orange3 (- to 3.37.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orange3/3.37.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Depends: orange3 opentsne (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orange3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 80 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 ♻
    • 80 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 ♻
    • 80 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
    • 80 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 ♻
    • 80 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
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 80 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 ♻
    • 80 days old (needed 5 days)
• r-cran-xslt (- to 1.4.5-1)
  • Migration status for r-cran-xslt (- to 1.4.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-xslt/1.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: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-xslt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 80 days old (needed 5 days)
• odoo (- to 16.0.0+dfsg.2-3)
  • Migration status for odoo (- to 16.0.0+dfsg.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating odoo would introduce bugs in testing: #1061261
    • Depends: odoo pypdf2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odoo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 81 days old (needed 5 days)
• pynx (- to 2024.1-1)
  • Migration status for pynx (- to 2024.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pynx numba (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): pynx nabu (not considered)
  • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 81 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 ♻
    • 81 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 ♻
    • 81 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 ♻
    • 81 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 ♻
    • 81 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 ♻
    • 81 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
    • 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 ♻
    • 81 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:
    • sdpam/armhf has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdpa.html
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 81 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• xmms2 (- to 0.8+dfsg-26)
  • Migration status for xmms2 (- to 0.8+dfsg-26): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xmms2 would introduce bugs in testing: #1072462, #1075672
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmms2.html
    • Reproducible on armhf - info ♻
    • 81 days old (needed 5 days)
• gkrellm-reminder (- to 2.0.0-3.2)
  • Migration status for gkrellm-reminder (- to 2.0.0-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gkrellm-reminder would introduce bugs in testing: #1075005
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gkrellm-reminder.html
    • Reproducible on armhf - info ♻
    • 82 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 ♻
    • 83 days old (needed 5 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
    • 84 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 ♻
    • 85 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
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 85 days old (needed 2 days)
• laminar (- to 1.1-1.1)
  • Migration status for laminar (- to 1.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating laminar would introduce bugs in testing: #1019455, #1075992, #1080075
    • 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/l/laminar.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 86 days old (needed 5 days)
• libgeo-converter-wkt2kml-perl (- to 0.0.3-1)
  • Migration status for libgeo-converter-wkt2kml-perl (- to 0.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by frankie, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgeo-converter-wkt2kml-perl.html
    • autopkgtest for libgeo-converter-wkt2kml-perl/0.0.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
    • 86 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
    • Reproducible on armhf - info ♻
    • 86 days old (needed 5 days)
• juce (- to 8.0.0+ds-1)
  • Migration status for juce (- to 8.0.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating juce would introduce bugs in testing: #1064024
    • autopkgtest for juce/8.0.0+ds-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/juce.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 88 days old (needed 5 days)
• lintian-brush (- to 0.157)
  • Migration status for lintian-brush (- to 0.157): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lintian-brush would introduce bugs in testing: #1076245, #1078752
    • 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
    • Build-Depends(-Arch): lintian-brush ognibuild (not considered)
    • Build-Depends(-Arch): lintian-brush upstream-ontologist (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lintian-brush.html
    • 88 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
    • Depends: r-cran-sjstats r-cran-effectsize
  • 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
    • 88 days old (needed 2 days)
• buildlog-consultant (- to 0.0.37-1)
  • Migration status for buildlog-consultant (- to 0.0.37-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating buildlog-consultant would introduce bugs in testing: #1064719
    • buildlog-consultant unsatisfiable Build-Depends(-Arch) on amd64: librust-pyo3-file-dev
    • buildlog-consultant unsatisfiable Build-Depends(-Arch) on arm64: librust-pyo3-file-dev
    • buildlog-consultant unsatisfiable Build-Depends(-Arch) on armel: librust-pyo3-file-dev
    • buildlog-consultant unsatisfiable Build-Depends(-Arch) on armhf: librust-pyo3-file-dev
    • buildlog-consultant unsatisfiable Build-Depends(-Arch) on i386: librust-pyo3-file-dev
    • buildlog-consultant unsatisfiable Build-Depends(-Arch) on mips64el: librust-pyo3-file-dev
    • buildlog-consultant unsatisfiable Build-Depends(-Arch) on ppc64el: librust-pyo3-file-dev
    • buildlog-consultant unsatisfiable Build-Depends(-Arch) on riscv64: librust-pyo3-file-dev
    • buildlog-consultant unsatisfiable Build-Depends(-Arch) on s390x: librust-pyo3-file-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/buildlog-consultant.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 ♻
    • 89 days old (needed 5 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 ♻
    • 89 days old (needed 5 days)
• r-cran-transformr (- to 0.1.5-1)
  • Migration status for r-cran-transformr (- to 0.1.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-transformr r-cran-sf (not considered)
    • Depends: r-cran-transformr r-cran-sf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-transformr.html
    • autopkgtest for r-cran-transformr/0.1.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
    • 89 days old (needed 2 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
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 89 days old (needed 5 days)
• libxml-libxslt-perl (2.002001-1 to 2.003000-1)
  • Migration status for libxml-libxslt-perl (2.002001-1 to 2.003000-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libxml-grddl-perl/0.004-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 ♻), riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for libxml-libxslt-perl/2.003000-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: Pass, s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating libxml-libxslt-perl will fix bugs in testing: #1076488
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxml-libxslt-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 90 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:
    • 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
    • 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 ♻
    • 91 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
    • Reproducible on armhf - info ♻
    • 91 days old (needed 5 days)
• pgtt (- to 4.0-1)
  • Migration status for pgtt (- to 4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pgtt would introduce bugs in testing: #1073801
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgtt.html
    • autopkgtest for pgtt/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 armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 91 days old (needed 2 days)
• pyliblo (- to 0.10.0-6)
  • Migration status for pyliblo (- to 0.10.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyliblo would introduce bugs in testing: #1075409
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyliblo.html
    • autopkgtest for pyliblo/0.10.0-6: 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
    • 91 days old (needed 2 days)
• raysession (- to 0.14.3-2)
  • Migration status for raysession (- to 0.14.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: raysession pyliblo (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raysession.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 91 days old (needed 5 days)
• silver-platter (- to 0.5.23-1)
  • Migration status for silver-platter (- to 0.5.23-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating silver-platter would introduce bugs in testing: #1081102
    • autopkgtest for silver-platter/0.5.23-1: amd64: Regression or new test ♻, i386: Regression or new test ♻
    • Build-Depends(-Arch): silver-platter lintian-brush (not considered)
    • Build-Depends(-Arch): silver-platter upstream-ontologist (not considered)
    • Depends: silver-platter upstream-ontologist (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/silver-platter.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 91 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 ♻
    • 92 days old (needed 5 days)
• ploticus (- to 2.42-6)
  • Migration status for ploticus (- to 2.42-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ploticus would introduce bugs in testing: #1075391
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ploticus.html
    • Reproducible on armhf - info ♻
    • 92 days old (needed 5 days)
• sjeng (- to 11.2-13)
  • Migration status for sjeng (- to 11.2-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sjeng would introduce bugs in testing: #1075513
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sjeng.html
    • Reproducible on armhf - info ♻
    • 92 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
    • Reproducible on armhf - info ♻
    • 92 days old (needed 5 days)
• 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
    • 93 days old (needed 2 days)
• pagure (- to 5.11.3+dfsg-3)
  • Migration status for pagure (- to 5.11.3+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): pagure flask-wtf (not considered)
    • Build-Depends(-Arch): pagure python-jenkins (not considered)
    • Depends: pagure flask-wtf (not considered)
    • Depends: pagure trololio (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pagure.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 93 days old (needed 5 days)
    • Remove hint for (transitive) dependency: flask-wtf
• xdm (- to 1:1.1.11-3.1)
  • Migration status for xdm (- to 1:1.1.11-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xdm would introduce bugs in testing: #1075656
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdm.html
    • Reproducible on armhf - info ♻
    • 93 days old (needed 5 days)
• gnome-shell-extension-manager (- to 0.5.1-2)
  • Migration status for gnome-shell-extension-manager (- to 0.5.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-shell-extension-manager would introduce bugs in testing: #1075027
    • Build-Depends(-Arch): gnome-shell-extension-manager text-engine (not considered)
    • Depends: gnome-shell-extension-manager text-engine (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-manager.html
    • Reproducible on armhf - info ♻
    • 94 days old (needed 5 days)
• package-update-indicator (- to 9-2)
  • Migration status for package-update-indicator (- to 9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating package-update-indicator would introduce bugs in testing: #1074716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/package-update-indicator.html
    • Reproducible on armhf - info ♻
    • 94 days old (needed 5 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 ♻
    • 94 days old (needed 5 days)
• randtype (- to 1.13-11.1)
  • Migration status for randtype (- to 1.13-11.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating randtype would introduce bugs in testing: #1075434
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/randtype.html
    • Reproducible on armhf - info ♻
    • 94 days old (needed 5 days)
• fscacher (- to 0.4.1-1)
  • Migration status for fscacher (- to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fscacher would introduce bugs in testing: #1079398
    • autopkgtest for fscacher/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 ♻
    • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fscacher.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 95 days old (needed 5 days)
• ocean-sound-theme (- to 6.0.5-1)
  • Migration status for ocean-sound-theme (- to 6.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zecoucou@free.fr, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocean-sound-theme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 95 days old (needed 5 days)
• sacad (- to 2.7.5-2)
  • Migration status for sacad (- to 2.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sacad/2.7.5-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): sacad web-cache (not considered)
    • Depends: sacad web-cache (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sacad.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 95 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
    • Reproducible on armhf - info ♻
    • 95 days old (needed 5 days)
• web-cache (- to 1.1.0-2)
  • Migration status for web-cache (- to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for web-cache/1.1.0-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/w/web-cache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 95 days old (needed 5 days)
• gmemusage (- to 0.2-11.1)
  • Migration status for gmemusage (- to 0.2-11.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gmemusage would introduce bugs in testing: #1055607, #1077947
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gmemusage.html
    • Reproducible on armhf - info ♻
    • 96 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
    • Reproducible on armhf - info ♻
    • 96 days old (needed 5 days)
• r-cran-backports (1.4.1-1 to 1.5.0-1)
  • Migration status for r-cran-backports (1.4.1-1 to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-backports would introduce bugs in testing: #1077463
    • autopkgtest for r-cran-backports/1.5.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating r-cran-backports will fix bugs in testing: #1076299
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-backports.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 96 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
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gridengine.html
  • Additional info:
    • Reproducible on arm64 - info ♻
    • 97 days old (needed 5 days)
• liggghts (- to 3.8.0+repack1-10)
  • Migration status for liggghts (- to 3.8.0+repack1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liggghts would introduce bugs in testing: #1076233
    • autopkgtest for liggghts/3.8.0+repack1-10: 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/l/liggghts.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 97 days old (needed 5 days)
• android-sdk-meta (- to 28.0.2+10+nmu1)
  • Migration status for android-sdk-meta (- to 28.0.2+10+nmu1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: android-sdk-meta android-platform-build (not considered)
    • Invalidated by dependency
    • Depends: android-sdk-meta android-platform-art (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-sdk-meta.html
    • autopkgtest for android-sdk-meta/28.0.2+10+nmu1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 98 days old (needed 2 days)
• ognibuild (- to 0.0.20-1)
  • Migration status for ognibuild (- to 0.0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ognibuild would introduce bugs in testing: #1081087
    • Build-Depends(-Arch): ognibuild buildlog-consultant (not considered)
    • Depends: ognibuild buildlog-consultant (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ognibuild.html
    • Reproducible on armhf - info ♻
    • 98 days old (needed 5 days)
• gcc-sh-elf (- to 8.1)
  • Migration status for gcc-sh-elf (- to 8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gcc-sh-elf/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/g/gcc-sh-elf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 99 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 ♻
    • 99 days old (needed 5 days)
• rust-launchpadlib (- to 0.2.0-1)
  • Migration status for rust-launchpadlib (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-launchpadlib-dev/amd64 has unsatisfiable dependency
    • librust-launchpadlib-dev/arm64 has unsatisfiable dependency
    • librust-launchpadlib-dev/armel has unsatisfiable dependency
    • librust-launchpadlib-dev/armhf has unsatisfiable dependency
    • librust-launchpadlib-dev/i386 has unsatisfiable dependency
    • librust-launchpadlib-dev/mips64el has unsatisfiable dependency
    • librust-launchpadlib-dev/ppc64el has unsatisfiable dependency
    • librust-launchpadlib-dev/s390x has unsatisfiable dependency
    • Updating rust-launchpadlib would introduce bugs in testing: #1072773
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on amd64: librust-clap-4.4+default-dev | librust-clap-4.3+default-dev | librust-clap-4.2+default-dev | librust-clap-4.1+default-dev | librust-clap-4.0+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on amd64: librust-clap-4.4+derive-dev | librust-clap-4.3+derive-dev | librust-clap-4.2+derive-dev | librust-clap-4.1+derive-dev | librust-clap-4.0+derive-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on amd64: librust-debversion-0.3+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on amd64: librust-debversion-0.3+serde-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on arm64: librust-clap-4.4+default-dev | librust-clap-4.3+default-dev | librust-clap-4.2+default-dev | librust-clap-4.1+default-dev | librust-clap-4.0+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on arm64: librust-clap-4.4+derive-dev | librust-clap-4.3+derive-dev | librust-clap-4.2+derive-dev | librust-clap-4.1+derive-dev | librust-clap-4.0+derive-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on arm64: librust-debversion-0.3+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on arm64: librust-debversion-0.3+serde-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on armel: librust-clap-4.4+default-dev | librust-clap-4.3+default-dev | librust-clap-4.2+default-dev | librust-clap-4.1+default-dev | librust-clap-4.0+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on armel: librust-clap-4.4+derive-dev | librust-clap-4.3+derive-dev | librust-clap-4.2+derive-dev | librust-clap-4.1+derive-dev | librust-clap-4.0+derive-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on armel: librust-debversion-0.3+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on armel: librust-debversion-0.3+serde-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on armhf: librust-clap-4.4+default-dev | librust-clap-4.3+default-dev | librust-clap-4.2+default-dev | librust-clap-4.1+default-dev | librust-clap-4.0+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on armhf: librust-clap-4.4+derive-dev | librust-clap-4.3+derive-dev | librust-clap-4.2+derive-dev | librust-clap-4.1+derive-dev | librust-clap-4.0+derive-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on armhf: librust-debversion-0.3+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on armhf: librust-debversion-0.3+serde-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on i386: librust-clap-4.4+default-dev | librust-clap-4.3+default-dev | librust-clap-4.2+default-dev | librust-clap-4.1+default-dev | librust-clap-4.0+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on i386: librust-clap-4.4+derive-dev | librust-clap-4.3+derive-dev | librust-clap-4.2+derive-dev | librust-clap-4.1+derive-dev | librust-clap-4.0+derive-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on i386: librust-debversion-0.3+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on i386: librust-debversion-0.3+serde-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on mips64el: librust-clap-4.4+default-dev | librust-clap-4.3+default-dev | librust-clap-4.2+default-dev | librust-clap-4.1+default-dev | librust-clap-4.0+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on mips64el: librust-clap-4.4+derive-dev | librust-clap-4.3+derive-dev | librust-clap-4.2+derive-dev | librust-clap-4.1+derive-dev | librust-clap-4.0+derive-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on mips64el: librust-debversion-0.3+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on mips64el: librust-debversion-0.3+serde-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on ppc64el: librust-clap-4.4+default-dev | librust-clap-4.3+default-dev | librust-clap-4.2+default-dev | librust-clap-4.1+default-dev | librust-clap-4.0+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on ppc64el: librust-clap-4.4+derive-dev | librust-clap-4.3+derive-dev | librust-clap-4.2+derive-dev | librust-clap-4.1+derive-dev | librust-clap-4.0+derive-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on ppc64el: librust-debversion-0.3+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on ppc64el: librust-debversion-0.3+serde-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on riscv64: librust-clap-4.4+default-dev | librust-clap-4.3+default-dev | librust-clap-4.2+default-dev | librust-clap-4.1+default-dev | librust-clap-4.0+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on riscv64: librust-clap-4.4+derive-dev | librust-clap-4.3+derive-dev | librust-clap-4.2+derive-dev | librust-clap-4.1+derive-dev | librust-clap-4.0+derive-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on riscv64: librust-debversion-0.3+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on riscv64: librust-debversion-0.3+serde-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on s390x: librust-clap-4.4+default-dev | librust-clap-4.3+default-dev | librust-clap-4.2+default-dev | librust-clap-4.1+default-dev | librust-clap-4.0+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on s390x: librust-clap-4.4+derive-dev | librust-clap-4.3+derive-dev | librust-clap-4.2+derive-dev | librust-clap-4.1+derive-dev | librust-clap-4.0+derive-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on s390x: librust-debversion-0.3+default-dev
    • rust-launchpadlib unsatisfiable Build-Depends(-Arch) on s390x: librust-debversion-0.3+serde-dev
    • autopkgtest for rust-launchpadlib/0.2.0-1: riscv64: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-launchpadlib.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 ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 99 days old (needed 5 days)
• carl9170fw (- to 1.9.9-399-gcd480b9-1.2)
  • Migration status for carl9170fw (- to 1.9.9-399-gcd480b9-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): carl9170fw gcc-sh-elf (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/carl9170fw.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 100 days old (needed 5 days)
• mplayer (- to 2:1.5+svn38542-1)
  • Migration status for mplayer (- to 2:1.5+svn38542-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mplayer would introduce bugs in testing: #1075294
    • Impossible Depends: mplayer -> libavformat-extra60/7:6.1.1-5+b1/armhf
    • Impossible Depends: mplayer -> libavformat-extra60/7:6.1.1-5+b1/i386
    • Impossible Depends: mplayer -> libavformat-extra60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: mplayer -> libavformat-extra60/7:6.1.1-5+b1/s390x
    • Impossible Depends: mplayer -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: mplayer -> libavformat60/7:6.1.1-5+b1/armhf
    • Impossible Depends: mplayer -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: mplayer -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: mplayer -> libavformat60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: mplayer -> libavformat60/7:6.1.1-5+b1/s390x
    • Impossible Depends: mplayer -> libpostproc57/7:6.1.1-5+b1/amd64
    • Impossible Depends: mplayer -> libpostproc57/7:6.1.1-5+b1/arm64
    • Impossible Depends: mplayer -> libpostproc57/7:6.1.1-5+b1/armel
    • Impossible Depends: mplayer -> libpostproc57/7:6.1.1-5+b1/armhf
    • Impossible Depends: mplayer -> libpostproc57/7:6.1.1-5+b1/i386
    • Impossible Depends: mplayer -> libpostproc57/7:6.1.1-5+b1/mips64el
    • Impossible Depends: mplayer -> libpostproc57/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: mplayer -> libpostproc57/7:6.1.1-5+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mplayer.html
    • 100 days old (needed 5 days)
• nemo-qml-plugin-contacts (- to 0.3.28-3)
  • Migration status for nemo-qml-plugin-contacts (- to 0.3.28-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libcontactcache-qt5-bin/amd64 has unsatisfiable dependency
    • libcontactcache-qt5-bin/arm64 has unsatisfiable dependency
    • libcontactcache-qt5-bin/armel has unsatisfiable dependency
    • libcontactcache-qt5-bin/armhf has unsatisfiable dependency
    • libcontactcache-qt5-bin/i386 has unsatisfiable dependency
    • libcontactcache-qt5-bin/mips64el has unsatisfiable dependency
    • libcontactcache-qt5-bin/ppc64el has unsatisfiable dependency
    • libcontactcache-qt5-bin/s390x has unsatisfiable dependency
    • Not built on buildd: arch amd64 binaries uploaded by mike.gabriel@das-netzwerkteam.de
    • Not built on buildd: arch all binaries uploaded by mike.gabriel@das-netzwerkteam.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/n/nemo-qml-plugin-contacts.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 100 days old (needed 5 days)
• upstream-ontologist (- to 0.1.37-1)
  • Migration status for upstream-ontologist (- to 0.1.37-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating upstream-ontologist would introduce bugs in testing: #1078418
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/upstream-ontologist.html
    • Reproducible on armhf - info ♻
    • 100 days old (needed 5 days)
• xstarfish (- to 1.1+ds-3)
  • Migration status for xstarfish (- to 1.1+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xstarfish would introduce bugs in testing: #1075686
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xstarfish.html
    • Reproducible on armhf - info ♻
    • 100 days old (needed 5 days)
• open-infrastructure-system-tools (- to 20190301-lts1-4)
  • Migration status for open-infrastructure-system-tools (- to 20190301-lts1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating open-infrastructure-system-tools would introduce bugs in testing: #1073663
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open-infrastructure-system-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 101 days old (needed 5 days)
• satdump (- to 1.2.0-2)
  • Migration status for satdump (- to 1.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): satdump nng (not considered)
    • Depends: satdump nng (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • 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 ♻
    • Reproducible on i386 - info ♻
    • 101 days old (needed 5 days)
• blackbox-terminal (- to 0.14.0-4)
  • Migration status for blackbox-terminal (- to 0.14.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating blackbox-terminal would introduce bugs in testing: #1066441
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blackbox-terminal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 102 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
    • Not built on buildd: arch arm64 binaries uploaded by tar
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kokkos.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 102 days old (needed 5 days)
• ruby-cssbundling-rails (- to 1.4.0-2)
  • Migration status for ruby-cssbundling-rails (- to 1.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-cssbundling-rails would introduce bugs in testing: #1075886
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-cssbundling-rails.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 102 days old (needed 5 days)
• v86d (- to 0.1.10-5)
  • Migration status for v86d (- to 0.1.10-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): v86d libx86 (not considered)
    • Depends: v86d libx86 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/v86d.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 102 days old (needed 5 days)
• libxml2 (2.9.14+dfsg-1.3 to 2.12.7+dfsg-3)
  • Migration status for libxml2 (2.9.14+dfsg-1.3 to 2.12.7+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libxml2 would introduce bugs in testing: #1073508
    • Implicit dependency: libxml2 libxml-libxml-perl
  • Additional info:
    • Updating libxml2 will fix bugs in testing: #1074338
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxml2.html
    • autopkgtest for libxml2/2.12.7+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
    • 103 days old (needed 2 days)
• powder (- to 118+dfsg1-4)
  • Migration status for powder (- to 118+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • powder has no binaries on any arch
    • nothing built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 103 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 ♻
    • 104 days old (needed 5 days)
• adios4dolfinx (- to 0.8.1.post0-2)
  • Migration status for adios4dolfinx (- to 0.8.1.post0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for adios4dolfinx/0.8.1.post0-2: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): adios4dolfinx fenics-dolfinx (not considered)
    • Build-Depends(-Arch): adios4dolfinx ipyparallel (not considered)
    • Depends: adios4dolfinx fenics-dolfinx (not considered)
  • 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 ♻
    • 105 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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
    • Reproducible on armhf - info ♻
    • 105 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
    • Reproducible on armhf - info ♻
    • 105 days old (needed 5 days)
• ngspetsc (- to 0.0~git20240318.f83b50a-3)
  • Migration status for ngspetsc (- to 0.0~git20240318.f83b50a-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ngspetsc fenics (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ngspetsc.html
    • autopkgtest for ngspetsc/0.0~git20240318.f83b50a-3: 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 ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 105 days old (needed 2 days)
• python-pynndescent (- to 0.5.11-1)
  • Migration status for python-pynndescent (- to 0.5.11-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-pynndescent numba (not considered)
    • Depends: python-pynndescent numba (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): python-pynndescent llvmlite (not considered)
    • Depends: python-pynndescent llvmlite (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pynndescent.html
    • autopkgtest for python-pynndescent/0.5.11-1: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 105 days old (needed 2 days)
• tpm2-tss (4.0.1-7.2 to 4.1.3-1)
  • Migration status for tpm2-tss (4.0.1-7.2 to 4.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tpm2-tss would introduce bugs in testing: #1070720
    • 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:
    • Updating tpm2-tss will fix bugs in testing: #1073221
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpm2-tss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 106 days old (needed 5 days)
• omega-rpg (- to 1:0.90-pa9-18)
  • Migration status for omega-rpg (- to 1:0.90-pa9-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating omega-rpg would introduce bugs in testing: #1075330
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/omega-rpg.html
    • Reproducible on armhf - info ♻
    • 107 days old (needed 5 days)
• tabnet (- to 4.1.0+ds-2)
  • Migration status for tabnet (- to 4.1.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for tabnet/4.1.0+ds-2: 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 ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/tabnet.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 ♻
    • 107 days old (needed 5 days)
• bidentd (- to 1.1.4-1.3)
  • Migration status for bidentd (- to 1.1.4-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bidentd would introduce bugs in testing: #1071749
  • 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 ♻
    • 108 days old (needed 5 days)
• libccp4 (- to 8.0.0-3)
  • Migration status for libccp4 (- to 8.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libccp4 would introduce bugs in testing: #1075155
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libccp4.html
    • Reproducible on armhf - info ♻
    • 108 days old (needed 5 days)
• linuxtv-dvb-apps (- to 1.1.1+rev1500-1.5)
  • Migration status for linuxtv-dvb-apps (- to 1.1.1+rev1500-1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating linuxtv-dvb-apps would introduce bugs in testing: #1075227
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linuxtv-dvb-apps.html
    • Reproducible on armhf - info ♻
    • 108 days old (needed 5 days)
• partman-hfs (- to 12)
  • Migration status for partman-hfs (- to 12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • partman-hfs/amd64 has unsatisfiable dependency
    • partman-hfs/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 108 days old (needed 5 days)
• guake-indicator (- to 1.4.5-3)
  • Migration status for guake-indicator (- to 1.4.5-3): 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guake-indicator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 109 days old (needed 5 days)
• meta-plasma-mobile (- to 6)
  • Migration status for meta-plasma-mobile (- to 6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: meta-plasma-mobile wacomtablet (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meta-plasma-mobile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 109 days old (needed 5 days)
• mu-editor (- to 1.0.3+dfsg-6.1)
  • Migration status for mu-editor (- to 1.0.3+dfsg-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mu-editor would introduce bugs in testing: #1081083
    • autopkgtest for mu-editor/1.0.3+dfsg-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): mu-editor python-uflash
    • Depends: mu-editor python-guizero (not considered)
    • Depends: mu-editor python-uflash
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mu-editor.html
    • Reproducible on armhf - info ♻
    • 110 days old (needed 5 days)
• telepathy-ofono (- to 0.3.1-3)
  • Migration status for telepathy-ofono (- to 0.3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telepathy-ofono would introduce bugs in testing: #1075561
    • Depends: telepathy-ofono ofono (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telepathy-ofono.html
    • Reproducible on armhf - info ♻
    • 110 days old (needed 5 days)
• tt-rss (- to 21~git20210204.b4cbc79+dfsg-1.3)
  • Migration status for tt-rss (- to 21~git20210204.b4cbc79+dfsg-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tt-rss would introduce bugs in testing: #1021656, #1054608
  • 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 ♻
    • 110 days old (needed 5 days)
• xtrx-dkms (- to 0.0.1+git20190320.5ae3a3e-3.5)
  • Migration status for xtrx-dkms (- to 0.0.1+git20190320.5ae3a3e-3.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xtrx-dkms would introduce bugs in testing: #1077678
    • autopkgtest for xtrx-dkms/0.0.1+git20190320.5ae3a3e-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 ♻
  • 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 ♻
    • 110 days old (needed 5 days)
• gnunet (- to 0.20.0-5)
  • Migration status for gnunet (- to 0.20.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnunet would introduce bugs in testing: #1075031
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnunet.html
    • Reproducible on armhf - info ♻
    • 111 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
    • 111 days old (needed 2 days)
• nrpe-ng (- to 0.2.0-1.2)
  • Migration status for nrpe-ng (- to 0.2.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nrpe-ng would introduce bugs in testing: #1018425
    • 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/n/nrpe-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 111 days old (needed 5 days)
• squid-deb-proxy (- to 0.8.16)
  • Migration status for squid-deb-proxy (- to 0.8.16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating squid-deb-proxy would introduce bugs in testing: #932501
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squid-deb-proxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 111 days old (needed 5 days)
• falcosecurity-libs (- to 0.15.1-4)
  • Migration status for falcosecurity-libs (- to 0.15.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating falcosecurity-libs would introduce bugs in testing: #1034881, #1067619, #1068731, #1077840
    • autopkgtest for falcosecurity-libs/0.15.1-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on riscv64
    • 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: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/f/falcosecurity-libs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 112 days old (needed 5 days)
• mgetty (- to 1.2.1-1.3)
  • Migration status for mgetty (- to 1.2.1-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mgetty would introduce bugs in testing: #1075266
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mgetty.html
    • Reproducible on armhf - info ♻
    • 112 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
    • Reproducible on armhf - info ♻
    • 112 days old (needed 5 days)
• ofono (- to 1.31-4)
  • Migration status for ofono (- to 1.31-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ofono would introduce bugs in testing: #1073646, #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 ♻
    • 113 days old (needed 5 days)
• openscap (- to 1.3.10+dfsg-3)
  • Migration status for openscap (- to 1.3.10+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): openscap libopendbx (not considered)
    • Depends: openscap libopendbx (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openscap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 113 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
    • 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 ♻
    • 113 days old (needed 5 days)
• resampy (- to 0.4.3+ds-3)
  • Migration status for resampy (- to 0.4.3+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating resampy would introduce bugs in testing: #1081099
    • Not built on buildd: upload info for arch all binaries not found, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): resampy numba (not considered)
    • Depends: resampy numba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resampy.html
    • autopkgtest for resampy/0.4.3+ds-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻, s390x: Pass
    • 113 days old (needed 5 days)
• mariadb-connector-python (- to 1.1.10-1)
  • Migration status for mariadb-connector-python (- to 1.1.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mariadb-connector-python would introduce bugs in testing: #1075256
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mariadb-connector-python.html
    • Reproducible on armhf - info ♻
    • 114 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
    • 114 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
    • Reproducible on armhf - info ♻
    • 114 days old (needed 5 days)
• catdvi (- to 0.14-15)
  • Migration status for catdvi (- to 0.14-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating catdvi would introduce bugs in testing: #1074865
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/catdvi.html
    • Reproducible on armhf - info ♻
    • 115 days old (needed 5 days)
• datalad-next (- to 1.4.1-1)
  • Migration status for datalad-next (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for datalad-next/1.4.1-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: 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/datalad-next.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 115 days old (needed 5 days)
• pam-ssh-agent-auth (- to 0.10.3-9)
  • Migration status for pam-ssh-agent-auth (- to 0.10.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pam-ssh-agent-auth would introduce bugs in testing: #1075358
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pam-ssh-agent-auth.html
    • Reproducible on armhf - info ♻
    • 115 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
    • 115 days old (needed 5 days)
• r-cran-spatstat (- to 3.0-8-1)
  • Migration status for r-cran-spatstat (- to 3.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): r-cran-spatstat r-cran-spatstat.model (not considered)
    • Depends: r-cran-spatstat r-cran-spatstat.model (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-spatstat r-cran-spatstat.linnet
    • Depends: r-cran-spatstat r-cran-spatstat.linnet
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.html
    • autopkgtest for r-cran-spatstat/3.0-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 116 days old (needed 2 days)
• r-cran-spatstat.linnet (- to 3.1-5-1)
  • Migration status for r-cran-spatstat.linnet (- to 3.1-5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-spatstat.linnet r-cran-spatstat.model (not considered)
    • Depends: r-cran-spatstat.linnet r-cran-spatstat.model (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.linnet.html
    • autopkgtest for r-cran-spatstat.linnet/3.1-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
    • 117 days old (needed 2 days)
• r-cran-spatstat.model (- to 3.2-11-1)
  • Migration status for r-cran-spatstat.model (- to 3.2-11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-spatstat.model would introduce bugs in testing: #1069051
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.model.html
    • autopkgtest for r-cran-spatstat.model/3.2-11-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)
• geoalchemy2 (- to 0.15.1-1)
  • Migration status for geoalchemy2 (- to 0.15.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for geoalchemy2/0.15.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/g/geoalchemy2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 118 days old (needed 5 days)
• scap-security-guide (- to 0.1.73-1)
  • Migration status for scap-security-guide (- to 0.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): scap-security-guide openscap (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scap-security-guide.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 ♻
    • 118 days old (needed 5 days)
• nam (- to 1.15-7)
  • Migration status for nam (- to 1.15-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nam would introduce bugs in testing: #1075302
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nam.html
    • Reproducible on armhf - info ♻
    • 120 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/s390x has unsatisfiable dependency
    • Updating olive-editor would introduce bugs in testing: #1072441
    • Build-Depends(-Arch): olive-editor opencolorio
    • Build-Depends(-Arch): olive-editor openimageio
  • 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 s390x, not running autopkgtest there
    • 120 days old (needed 5 days)
• rust-ruma-common (- to 0.10.5-5)
  • Migration status for rust-ruma-common (- to 0.10.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ruma-common/0.10.5-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Depends: rust-ruma-common rust-criterion-0.3 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-ruma-common.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 121 days old (needed 5 days)
• pytorch-geometric (- to 2.4.0-2)
  • Migration status for pytorch-geometric (- to 2.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pytorch-geometric/2.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 ♻
    • Build-Depends(-Arch): pytorch-geometric pytorch (not considered)
    • Build-Depends(-Arch): pytorch-geometric pytorch-cluster (not considered)
    • Build-Depends(-Arch): pytorch-geometric pytorch-sparse (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-geometric.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 ♻
    • 122 days old (needed 5 days)
• praat (- to 6.4.12+dfsg-3)
  • Migration status for praat (- to 6.4.12+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating praat would introduce bugs in testing: #1077929
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/praat.html
    • autopkgtest for praat/6.4.12+dfsg-3: 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
    • 123 days old (needed 2 days)
• python-fastparquet (- to 2024.2.0-2)
  • Migration status for python-fastparquet (- to 2024.2.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-fastparquet python-cramjam (not considered)
    • Depends: python-fastparquet python-cramjam (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fastparquet.html
    • autopkgtest for python-fastparquet/2024.2.0-2: amd64: Pass, arm64: 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
    • 123 days old (needed 2 days)
• sonic-pi (- to 3.2.2~repack-9)
  • Migration status for sonic-pi (- to 3.2.2~repack-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sonic-pi would introduce bugs in testing: #1079808
    • autopkgtest for sonic-pi/3.2.2~repack-9: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻
    • Build-Depends(-Arch): sonic-pi aubio (not considered)
    • Build-Depends(-Arch): sonic-pi ruby-aubio
    • Depends: sonic-pi ruby-aubio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sonic-pi.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 123 days old (needed 5 days)
• cashbox (- to 0.3)
  • Migration status for cashbox (- to 0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by bs, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cashbox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 125 days old (needed 5 days)
• latencytop (- to 0.5.0-3)
  • Migration status for latencytop (- to 0.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating latencytop would introduce bugs in testing: #1075130
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/latencytop.html
    • Reproducible on armhf - info ♻
    • 126 days old (needed 5 days)
• verilator (- to 5.024-1)
  • Migration status for verilator (- to 5.024-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating verilator would introduce bugs in testing: #1071425
    • Not built on buildd: upload info for arch amd64 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/verilator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 126 days old (needed 5 days)
• tua (- to 4.3-15)
  • Migration status for tua (- to 4.3-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tua would introduce bugs in testing: #1075587
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tua.html
    • Reproducible on armhf - info ♻
    • 127 days old (needed 5 days)
• xshisen (- to 1:1.51-9)
  • Migration status for xshisen (- to 1:1.51-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xshisen would introduce bugs in testing: #1075684
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xshisen.html
    • Reproducible on armhf - info ♻
    • 127 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 ♻
    • 128 days old (needed 5 days)
• fenics (- to 2:0.8.0.1)
  • Migration status for fenics (- to 2:0.8.0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: fenics fenics-dolfinx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fenics.html
    • autopkgtest for fenics/2:0.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
    • 128 days old (needed 2 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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
    • Reproducible on armhf - info ♻
    • 128 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
    • Reproducible on armhf - info ♻
    • 129 days old (needed 5 days)
• rust-yaxpeax-arch (- to 0.2.7-1)
  • Migration status for rust-yaxpeax-arch (- to 0.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-yaxpeax-arch/0.2.7-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-yaxpeax-arch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 129 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:
    • autopkgtest for rust-yaxpeax-x86/1.2.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-yaxpeax-x86 rust-yaxpeax-arch (not considered)
    • Depends: rust-yaxpeax-x86 rust-yaxpeax-arch (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-yaxpeax-x86.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 129 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
    • Reproducible on armhf - info ♻
    • 129 days old (needed 5 days)
• dico (- to 2.11-4.2)
  • Migration status for dico (- to 2.11-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dico would introduce bugs in testing: #1080584
    • Build-Depends(-Arch): dico wordnet (not considered)
    • Depends: dico wordnet (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dico.html
    • Reproducible on armhf - info ♻
    • 130 days old (needed 5 days)
• fbterm-ucimf (- to 0.2.9-7)
  • Migration status for fbterm-ucimf (- to 0.2.9-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fbterm-ucimf fbterm (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fbterm-ucimf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 130 days old (needed 5 days)
• r-cran-sf (- to 1.0-16+dfsg-1)
  • Migration status for r-cran-sf (- to 1.0-16+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-sf would introduce bugs in testing: #1071106
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sf.html
    • autopkgtest for r-cran-sf/1.0-16+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
    • 130 days old (needed 2 days)
• baresip (- to 1.1.0-1)
  • Migration status for baresip (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating baresip would introduce bugs in testing: #1072401
    • Impossible Depends: baresip -> libavdevice60/7:6.1.1-5+b1/amd64
    • Impossible Depends: baresip -> libavdevice60/7:6.1.1-5+b1/arm64
    • Impossible Depends: baresip -> libavdevice60/7:6.1.1-5+b1/armel
    • Impossible Depends: baresip -> libavdevice60/7:6.1.1-5+b1/armhf
    • Impossible Depends: baresip -> libavdevice60/7:6.1.1-5+b1/i386
    • Impossible Depends: baresip -> libavdevice60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: baresip -> libavdevice60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: baresip -> libavdevice60/7:6.1.1-5+b1/s390x
    • Impossible Depends: baresip -> libavfilter-extra9/7:6.1.1-5+b1/arm64
    • Impossible Depends: baresip -> libavfilter-extra9/7:6.1.1-5+b1/armel
    • Impossible Depends: baresip -> libavfilter-extra9/7:6.1.1-5+b1/i386
    • Impossible Depends: baresip -> libavfilter-extra9/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: baresip -> libavfilter9/7:6.1.1-5+b1/amd64
    • Impossible Depends: baresip -> libavfilter9/7:6.1.1-5+b1/armhf
    • Impossible Depends: baresip -> libavfilter9/7:6.1.1-5+b1/mips64el
    • Impossible Depends: baresip -> libavfilter9/7:6.1.1-5+b1/s390x
    • Impossible Depends: baresip -> libavformat-extra60/7:6.1.1-5+b1/s390x
    • Impossible Depends: baresip -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: baresip -> libavformat60/7:6.1.1-5+b1/armhf
    • Impossible Depends: baresip -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: baresip -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: baresip -> libavformat60/7:6.1.1-5+b1/ppc64el
    • Build-Depends(-Arch): baresip libre (not considered)
    • Build-Depends(-Arch): baresip rem
    • Depends: baresip libre (not considered)
    • Depends: baresip rem
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/baresip.html
    • Reproducible on armhf - info ♻
    • 131 days old (needed 5 days)
• kraft (- to 1.2.1-1)
  • Migration status for kraft (- to 1.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kraft would introduce bugs in testing: #1029734
    • Depends: kraft pypdf2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kraft.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 131 days old (needed 5 days)
• libre (- to 2.0.1-2)
  • Migration status for libre (- to 2.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libre would introduce bugs in testing: #1075201
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libre.html
    • Reproducible on armhf - info ♻
    • 131 days old (needed 5 days)
• rem (- to 1.0.0-2)
  • Migration status for rem (- 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): rem libre (not considered)
    • Depends: rem libre (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • 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 ♻
    • 131 days old (needed 5 days)
• rust-pdf (- to 0.8.0-1)
  • Migration status for rust-pdf (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-pdf-dev/amd64 has unsatisfiable dependency
    • librust-pdf-dev/arm64 has unsatisfiable dependency
    • librust-pdf-dev/armel has unsatisfiable dependency
    • librust-pdf-dev/armhf has unsatisfiable dependency
    • librust-pdf-dev/i386 has unsatisfiable dependency
    • librust-pdf-dev/mips64el has unsatisfiable dependency
    • librust-pdf-dev/ppc64el has unsatisfiable dependency
    • librust-pdf-dev/s390x has unsatisfiable dependency
    • autopkgtest for rust-pdf/0.8.0-1: riscv64: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): rust-pdf rust-datasize (not considered)
    • Build-Depends(-Arch): rust-pdf rust-istring
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-pdf.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 131 days old (needed 5 days)
• euslisp (- to 9.30+dfsg-3)
  • Migration status for euslisp (- to 9.30+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for euslisp/9.30+dfsg-3: amd64: Pass, arm64: Pass, 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/e/euslisp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 132 days old (needed 5 days)
• rust-primal (- to 0.3.2-1)
  • Migration status for rust-primal (- to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-primal/0.3.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-primal rust-primal-sieve (not considered)
    • Depends: rust-primal rust-primal-sieve (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-primal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 132 days old (needed 5 days)
• rust-primal-sieve (- to 0.3.6-1)
  • Migration status for rust-primal-sieve (- to 0.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-primal-sieve/0.3.6-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: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-primal-sieve.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 132 days old (needed 5 days)
• scm (- to 5f3-6)
  • Migration status for scm (- to 5f3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scm would introduce bugs in testing: #1081101
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): scm slib (not considered)
    • Depends: scm slib (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scm.html
    • Reproducible on armhf - info ♻
    • 132 days old (needed 5 days)
• fenicsx-performance-tests (- to 0.8.0-1)
  • Migration status for fenicsx-performance-tests (- to 0.8.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): fenicsx-performance-tests fenics-dolfinx (not considered)
    • Depends: fenicsx-performance-tests fenics-dolfinx (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fenicsx-performance-tests.html
    • autopkgtest for fenicsx-performance-tests/0.8.0-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
    • 133 days old (needed 2 days)
• gtranslator (- to 46.1-1)
  • Migration status for gtranslator (- to 46.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gtranslator libgda5 (not considered)
    • Depends: gtranslator libgda5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtranslator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 133 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
    • Reproducible on armhf - info ♻
    • 133 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
    • 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:
    • Piuparts tested OK - 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
    • Waiting for reproducibility test results on armhf - info ♻
    • 133 days old (needed 5 days)
• microdc2 (- to 0.15.6-6)
  • Migration status for microdc2 (- to 0.15.6-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating microdc2 would introduce bugs in testing: #1075271
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/microdc2.html
    • Reproducible on armhf - info ♻
    • 133 days old (needed 5 days)
• xscavenger (- to 1.4.5-7)
  • Migration status for xscavenger (- to 1.4.5-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xscavenger would introduce bugs in testing: #1075680
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xscavenger.html
    • Reproducible on armhf - info ♻
    • 133 days old (needed 5 days)
• gtkam (- to 1.0-5)
  • Migration status for gtkam (- to 1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtkam would introduce bugs in testing: #1075053
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtkam.html
    • Reproducible on armhf - info ♻
    • 135 days old (needed 5 days)
• python-omegaconf (- to 2.3.0-1)
  • Migration status for python-omegaconf (- to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • autopkgtest for python-omegaconf/2.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for python-omegaconf/n/a: riscv64: Regression or new test ♻
    • Build-Depends-Indep: python-omegaconf pydevd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-omegaconf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 135 days old (needed 5 days)
    • Remove hint for (transitive) dependency: python-omegaconf
• rxtx (2.2.0+dfsg-2 to 2.2.0+dfsg-3)
  • Migration status for rxtx (2.2.0+dfsg-2 to 2.2.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rxtx would introduce bugs in testing: #1070417
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • 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: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
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Updating rxtx will fix bugs in testing: #1066703, #1073167
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rxtx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 136 days old (needed 5 days)
• django-pipeline (- to 3.0.0-2)
  • Migration status for django-pipeline (- to 3.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for django-pipeline/3.0.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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 ♻
    • 137 days old (needed 5 days)
• spectools (- to 201601r1-5)
  • Migration status for spectools (- to 201601r1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spectools would introduce bugs in testing: #1075531
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spectools.html
    • Reproducible on armhf - info ♻
    • 137 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
    • 137 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 ♻
    • 138 days old (needed 5 days)
• gxr-openvr (- to 0.15.1-2.1)
  • Migration status for gxr-openvr (- to 0.15.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gxr-openvr would introduce bugs in testing: #1078236
    • Build-Depends(-Arch): gxr-openvr gxr (not considered)
    • Build-Depends(-Arch): gxr-openvr openvr (not considered)
    • Depends: gxr-openvr gxr (not considered)
    • Depends: gxr-openvr openvr (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 138 days old (needed 5 days)
• haskell-futhark (- to 0.25.15-2)
  • Migration status for haskell-futhark (- to 0.25.15-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-futhark haskell-srcloc (not considered)
    • Build-Depends-Indep: haskell-futhark haskell-srcloc (not considered)
    • Depends: haskell-futhark haskell-srcloc (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends(-Arch): haskell-futhark haskell-fgl-visualize (not considered)
    • Build-Depends(-Arch): haskell-futhark haskell-futhark-data (not considered)
    • Build-Depends(-Arch): haskell-futhark haskell-futhark-manifest (not considered)
    • Build-Depends(-Arch): haskell-futhark haskell-futhark-server (not considered)
    • Build-Depends(-Arch): haskell-futhark haskell-language-c-quote
    • Build-Depends(-Arch): haskell-futhark haskell-mainland-pretty (not considered)
    • Build-Depends-Indep: haskell-futhark haskell-fgl-visualize (not considered)
    • Build-Depends-Indep: haskell-futhark haskell-futhark-data (not considered)
    • Build-Depends-Indep: haskell-futhark haskell-futhark-manifest (not considered)
    • Build-Depends-Indep: haskell-futhark haskell-futhark-server (not considered)
    • Build-Depends-Indep: haskell-futhark haskell-language-c-quote
    • Build-Depends-Indep: haskell-futhark haskell-mainland-pretty (not considered)
    • Depends: haskell-futhark haskell-fgl-visualize (not considered)
    • Depends: haskell-futhark haskell-futhark-data (not considered)
    • Depends: haskell-futhark haskell-futhark-manifest (not considered)
    • Depends: haskell-futhark haskell-futhark-server (not considered)
    • Depends: haskell-futhark haskell-language-c-quote
    • Depends: haskell-futhark haskell-mainland-pretty (not considered)
  • 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 ♻
    • 138 days old (needed 5 days)
• mathgl (- to 8.0.1-8)
  • Migration status for mathgl (- to 8.0.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mathgl would introduce bugs in testing: #1066978
    • autopkgtest for mathgl/8.0.1-8: 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 ♻
    • 138 days old (needed 5 days)
• raku-readline (- to 0.1.6-3.1)
  • Migration status for raku-readline (- to 0.1.6-3.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Build-Depends(-Arch): raku-readline dh-raku (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-readline.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 ♻
    • 138 days old (needed 5 days)
• garmin-forerunner-tools (- to 0.10repacked-15)
  • Migration status for garmin-forerunner-tools (- to 0.10repacked-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating garmin-forerunner-tools would introduce bugs in testing: #1074979
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/garmin-forerunner-tools.html
    • Reproducible on armhf - info ♻
    • 139 days old (needed 5 days)
• haskell-futhark-manifest (- to 1.4.0.0-1)
  • Migration status for haskell-futhark-manifest (- to 1.4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kaol
    • Not built on buildd: arch all binaries uploaded by kaol, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-futhark-manifest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 139 days old (needed 5 days)
• libnss-db (- to 2.2.3pre1-10)
  • Migration status for libnss-db (- to 2.2.3pre1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libnss-db would introduce bugs in testing: #1057850
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnss-db.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 139 days old (needed 5 days)
• litecoin (- to 0.21.3-1)
  • Migration status for litecoin (- to 0.21.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating litecoin would introduce bugs in testing: #1072478, #1076689
    • Impossible Depends: litecoin -> libminiupnpc17/2.2.6-1+b1/amd64
    • Impossible Depends: litecoin -> libminiupnpc17/2.2.6-1+b1/arm64
    • Impossible Depends: litecoin -> libminiupnpc17/2.2.6-1+b1/armel
    • Impossible Depends: litecoin -> libminiupnpc17/2.2.6-1+b1/armhf
    • Impossible Depends: litecoin -> libminiupnpc17/2.2.6-1+b1/i386
    • Impossible Depends: litecoin -> libminiupnpc17/2.2.6-1+b1/mips64el
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/litecoin.html
    • Reproducible on armhf - info ♻
    • 139 days old (needed 5 days)
• python-beartype (- to 0.18.5-1)
  • Migration status for python-beartype (- to 0.18.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-beartype would introduce bugs in testing: #1077404
    • autopkgtest for python-beartype/0.18.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/python-beartype.html
    • Reproducible on armhf - info ♻
    • 139 days old (needed 5 days)
• quelcom (- to 0.4.0-18)
  • Migration status for quelcom (- to 0.4.0-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quelcom would introduce bugs in testing: #1074737
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quelcom.html
    • autopkgtest for quelcom/0.4.0-18: 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
    • 139 days old (needed 2 days)
• eln (- to 1.5.4-1)
  • Migration status for eln (- to 1.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eln would introduce bugs in testing: #1074219
    • eln unsatisfiable Build-Depends(-Arch) on armel: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on armel: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on armel: qml6-module-qtwebengine
    • eln unsatisfiable Build-Depends(-Arch) on mips64el: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on mips64el: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on mips64el: qml6-module-qtwebengine
    • eln unsatisfiable Build-Depends(-Arch) on ppc64el: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on ppc64el: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on ppc64el: qml6-module-qtwebengine
    • eln unsatisfiable Build-Depends(-Arch) on s390x: qt6-pdf-dev
    • eln unsatisfiable Build-Depends(-Arch) on s390x: qml6-module-qtwebengine-controlsdelegates
    • eln unsatisfiable Build-Depends(-Arch) on s390x: qml6-module-qtwebengine
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eln.html
    • 140 days old (needed 5 days)
• khronos-opengl-man4 (- to 1.0~svn33624-2)
  • Migration status for khronos-opengl-man4 (- to 1.0~svn33624-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): khronos-opengl-man4 w3-dtd-mathml (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khronos-opengl-man4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 140 days old (needed 5 days)
• ldapvi (- to 1.7-11)
  • Migration status for ldapvi (- to 1.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ldapvi would introduce bugs in testing: #1075132
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ldapvi.html
    • Reproducible on armhf - info ♻
    • 140 days old (needed 5 days)
• rust-webpki-roots (- to 0.26.1-1)
  • Migration status for rust-webpki-roots (- to 0.26.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-webpki-roots would introduce bugs in testing: #1069946
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-webpki-roots.html
    • autopkgtest for rust-webpki-roots/0.26.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 ♻
    • 140 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/s390x has unsatisfiable dependency
    • Updating rust-yoke would introduce bugs in testing: #1073151
    • autopkgtest for rust-yoke/0.7.3-1: riscv64: No tests, superficial or marked flaky ♻
    • 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 s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 140 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:
    • librust-zerofrom+derive-dev/amd64 has unsatisfiable dependency
    • librust-zerofrom+derive-dev/arm64 has unsatisfiable dependency
    • librust-zerofrom+derive-dev/armel has unsatisfiable dependency
    • librust-zerofrom+derive-dev/armhf has unsatisfiable dependency
    • librust-zerofrom+derive-dev/i386 has unsatisfiable dependency
    • librust-zerofrom+derive-dev/mips64el has unsatisfiable dependency
    • librust-zerofrom+derive-dev/ppc64el has unsatisfiable dependency
    • librust-zerofrom+derive-dev/s390x has unsatisfiable dependency
    • Updating rust-zerofrom would introduce bugs in testing: #1073146
    • autopkgtest for rust-zerofrom/0.1.3-1: riscv64: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-zerofrom.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 140 days old (needed 5 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:
    • Updating nim would introduce bugs in testing: #1071691
    • Build-Depends(-Arch): nim pcre3 (not considered)
    • Depends: nim pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim.html
    • autopkgtest for nim/1.6.14-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 141 days old (needed 2 days)
• sslh (- to 2.1.1-1)
  • Migration status for sslh (- to 2.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sslh would introduce bugs in testing: #851877
    • missing build on i386
    • missing build on mips64el
    • 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/s/sslh.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 ♻
    • 141 days old (needed 5 days)
• bootstrap-flask (- to 2.4.0+ds-1)
  • Migration status for bootstrap-flask (- to 2.4.0+ds-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): bootstrap-flask flask-wtf (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bootstrap-flask.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 142 days old (needed 5 days)
    • Remove hint for (transitive) dependency: bootstrap-flask
• ftxui (- to 5.0.0-2)
  • Migration status for ftxui (- to 5.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): ftxui iwyu (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/ftxui.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 142 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
    • 142 days old (needed 2 days)
• gloo-cuda (- to 0.0~git20230519.597accf-3)
  • Migration status for gloo-cuda (- to 0.0~git20230519.597accf-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for gloo-cuda/0.0~git20230519.597accf-3: amd64: Pass
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 142 days old (needed 5 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
    • 142 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 ♻
    • 142 days old (needed 5 days)
• pytorch (- to 2.1.2+dfsg-4)
  • Migration status for pytorch (- to 2.1.2+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-torch/amd64 has unsatisfiable dependency
    • python3-torch/arm64 has unsatisfiable dependency
    • python3-torch/s390x has unsatisfiable dependency
    • Updating pytorch would introduce bugs in testing: #1071655, #1072969, #1078795, #1078808
    • Impossible Depends: pytorch -> libavformat-extra60/7:6.1.1-5+b1/s390x
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): pytorch ideep (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pytorch.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 142 days old (needed 5 days)
• ardour (- to 1:8.6.0+ds-1)
  • Migration status for ardour (- to 1:8.6.0+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ardour aubio (not considered)
    • Depends: ardour aubio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ardour.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 143 days old (needed 5 days)
• faiss (- to 1.8.0-5)
  • Migration status for faiss (- to 1.8.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating faiss would introduce bugs in testing: #1074944
    • autopkgtest for faiss/1.8.0-5: 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/f/faiss.html
    • 143 days old (needed 5 days)
• gvm (- to 23.11.2)
  • Migration status for gvm (- to 23.11.2): 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 (not considered)
    • 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 ♻
    • 143 days old (needed 5 days)
• iwyu (- to 8.22-1)
  • Migration status for iwyu (- to 8.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iwyu would introduce bugs in testing: #1077666
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iwyu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 143 days old (needed 5 days)
• pg-gvm (- to 22.6.5-1)
  • Migration status for pg-gvm (- to 22.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pg-gvm gvm-libs (not considered)
    • Depends: pg-gvm gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-gvm.html
    • autopkgtest for pg-gvm/22.6.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
    • 143 days old (needed 2 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
    • 143 days old (needed 2 days)
• ui-gxmlcpp (- to 1.4.6-2)
  • Migration status for ui-gxmlcpp (- to 1.4.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): ui-gxmlcpp ui-utilcpp (not considered)
    • Depends: ui-gxmlcpp ui-utilcpp (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ui-gxmlcpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 143 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• cpdb-backend-cups (- to 2.0b5-1)
  • Migration status for cpdb-backend-cups (- to 2.0b5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): cpdb-backend-cups libcupsfilters (not considered)
    • Depends: cpdb-backend-cups libcupsfilters (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpdb-backend-cups.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 144 days old (needed 5 days)
• haskell-language-c-quote (- to 0.13.0.1-2)
  • Migration status for haskell-language-c-quote (- to 0.13.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): haskell-language-c-quote haskell-srcloc (not considered)
    • Build-Depends-Indep: haskell-language-c-quote haskell-srcloc (not considered)
    • Depends: haskell-language-c-quote haskell-srcloc (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends(-Arch): haskell-language-c-quote haskell-exception-mtl (not considered)
    • Build-Depends(-Arch): haskell-language-c-quote haskell-mainland-pretty (not considered)
    • Build-Depends-Indep: haskell-language-c-quote haskell-exception-mtl (not considered)
    • Build-Depends-Indep: haskell-language-c-quote haskell-mainland-pretty (not considered)
    • Depends: haskell-language-c-quote haskell-exception-mtl (not considered)
    • Depends: haskell-language-c-quote haskell-mainland-pretty (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-language-c-quote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 144 days old (needed 5 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 ♻
    • 144 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
    • Reproducible on armhf - info ♻
    • 144 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 ♻
    • Reproducible on armhf - info ♻
    • 145 days old (needed 5 days)
• gnunet-gtk (- to 0.20.0-4)
  • Migration status for gnunet-gtk (- to 0.20.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gnunet-gtk gnunet (not considered)
    • Depends: gnunet-gtk gnunet (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnunet-gtk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• haskell-exception-mtl (- to 0.4.0.2-1)
  • Migration status for haskell-exception-mtl (- to 0.4.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kaol
    • Not built on buildd: arch all binaries uploaded by kaol, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-exception-mtl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• haskell-fgl-visualize (- to 0.1.0.1-1)
  • Migration status for haskell-fgl-visualize (- to 0.1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kaol
    • Not built on buildd: arch all binaries uploaded by kaol, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-fgl-visualize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• haskell-futhark-data (- to 1.1.0.1-1)
  • Migration status for haskell-futhark-data (- to 1.1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kaol
    • Not built on buildd: arch all binaries uploaded by kaol, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-futhark-data.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• haskell-futhark-server (- to 1.2.2.1-1)
  • Migration status for haskell-futhark-server (- to 1.2.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kaol
    • Not built on buildd: arch all binaries uploaded by kaol, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): haskell-futhark-server haskell-futhark-data (not considered)
    • Build-Depends-Indep: haskell-futhark-server haskell-futhark-data (not considered)
    • Depends: haskell-futhark-server haskell-futhark-data (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-futhark-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• haskell-mainland-pretty (- to 0.7.1-1)
  • Migration status for haskell-mainland-pretty (- to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kaol
    • Not built on buildd: arch all binaries uploaded by kaol, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): haskell-mainland-pretty haskell-srcloc (not considered)
    • Build-Depends-Indep: haskell-mainland-pretty haskell-srcloc (not considered)
    • Depends: haskell-mainland-pretty haskell-srcloc (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-mainland-pretty.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• haskell-srcloc (- to 0.6.0.1-1)
  • Migration status for haskell-srcloc (- to 0.6.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by kaol
    • Not built on buildd: arch all binaries uploaded by kaol, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-srcloc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• deepin-movie-reborn (- to 5.10.8-2.1)
  • Migration status for deepin-movie-reborn (- to 5.10.8-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating deepin-movie-reborn would introduce bugs in testing: #1078277
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepin-movie-reborn.html
    • Reproducible on armhf - info ♻
    • 146 days old (needed 5 days)
• libcupsfilters (- to 2.0.0-1)
  • Migration status for libcupsfilters (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libcupsfilters would introduce bugs in testing: #1069630
    • autopkgtest for libcupsfilters/2.0.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 alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcupsfilters.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 146 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 ♻
    • 146 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/s390x has unsatisfiable dependency
    • Updating cegui-mk2 would introduce bugs in testing: #1073309
  • 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 s390x, not running autopkgtest there
    • 147 days old (needed 5 days)
• exiflooter (- to 1.0.0+git20231228.22e4700-1)
  • Migration status for exiflooter (- to 1.0.0+git20231228.22e4700-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating exiflooter would introduce bugs in testing: #1079703
    • autopkgtest for exiflooter/1.0.0+git20231228.22e4700-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: 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 ♻
    • Not built on buildd: upload info for arch mips64el binaries not found
    • Built-Using: exiflooter golang-1.23
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/exiflooter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 147 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:
    • Updating pplatex would introduce bugs in testing: #1070288
    • Build-Depends(-Arch): pplatex pcre3 (not considered)
    • Depends: pplatex pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pplatex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 147 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 ♻
    • 147 days old (needed 5 days)
• rust-ropey (- to 1.6.1-1)
  • Migration status for rust-ropey (- to 1.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ropey/1.6.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): rust-ropey rust-str-indices (not considered)
    • Depends: rust-ropey rust-str-indices (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ropey.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 148 days old (needed 5 days)
• openstack-trove (- to 1:21.0.1-2)
  • Migration status for openstack-trove (- to 1:21.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openstack-trove would introduce bugs in testing: #1073009
    • autopkgtest for openstack-trove/1:21.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 ♻
    • Build-Depends-Indep: openstack-trove migrate (not considered)
    • Build-Depends-Indep: openstack-trove python-cassandra-driver (not considered)
    • Build-Depends-Indep: openstack-trove python-proboscis (not considered)
    • Depends: openstack-trove migrate (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openstack-trove.html
    • 149 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
    • Reproducible on armhf - info ♻
    • 150 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): librem5-flash-image python-jenkins (not considered)
    • Depends: librem5-flash-image python-jenkins (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 150 days old (needed 5 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
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 150 days old (needed 2 days)
• xvier (- to 1.0-10)
  • Migration status for xvier (- to 1.0-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xvier would introduce bugs in testing: #1075691
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xvier.html
    • Reproducible on armhf - info ♻
    • 150 days old (needed 5 days)
• gss (- to 1.0.4-3)
  • Migration status for gss (- to 1.0.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gss would introduce bugs in testing: #1076885
    • autopkgtest for gss/1.0.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gss.html
    • 151 days old (needed 5 days)
• pantalaimon (- to 0.10.5-2)
  • Migration status for pantalaimon (- to 0.10.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pantalaimon would introduce bugs in testing: #1069068
    • Not built on buildd: arch all binaries uploaded by debian@abeckmann.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pantalaimon.html
    • autopkgtest for pantalaimon/0.10.5-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 ♻
    • 151 days old (needed 5 days)
• filter (- to 2.6.3+ds1-4)
  • Migration status for filter (- to 2.6.3+ds1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating filter would introduce bugs in testing: #1074956
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/filter.html
    • Reproducible on armhf - info ♻
    • 152 days old (needed 5 days)
• rust-opendal (- to 0.44.1-1)
  • Migration status for rust-opendal (- to 0.44.1-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/armel 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
    • autopkgtest for rust-opendal/0.44.1-1: riscv64: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): rust-opendal rust-reqsign
  • 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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 152 days old (needed 5 days)
• seriousproton (- to 2020.01.15+dfsg-1.1)
  • Migration status for seriousproton (- to 2020.01.15+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating seriousproton would introduce bugs in testing: #1057114
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/seriousproton.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 152 days old (needed 5 days)
• tinydyndns (- to 0.4.2.debian1-3)
  • Migration status for tinydyndns (- to 0.4.2.debian1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tinydyndns would introduce bugs in testing: #1075576
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tinydyndns.html
    • Reproducible on armhf - info ♻
    • 152 days old (needed 5 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
    • Reproducible on armhf - info ♻
    • 153 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)
    • 154 days old (needed 5 days)
• lua-svn (- to 0.4.0-11)
  • Migration status for lua-svn (- to 0.4.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lua-svn would introduce bugs in testing: #1075240
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-svn.html
    • Reproducible on armhf - info ♻
    • 154 days old (needed 5 days)
• mediastreamer2 (- to 1:5.2.0+dfsg-4)
  • Migration status for mediastreamer2 (- to 1:5.2.0+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mediastreamer2 bcmatroska2 (not considered)
    • Depends: mediastreamer2 bcmatroska2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mediastreamer2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 154 days old (needed 5 days)
• paramspider (- to 1.0.1-1)
  • Migration status for paramspider (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating paramspider would introduce bugs in testing: #1079708
    • autopkgtest for paramspider/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 ♻
    • Not built on buildd: arch all binaries uploaded by sergiodj@sergiodj.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paramspider.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 154 days old (needed 5 days)
• planner (- to 0.14.92-1)
  • Migration status for planner (- to 0.14.92-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): planner libgda5 (not considered)
    • Depends: planner libgda5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/planner.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 154 days old (needed 5 days)
• basemap (- to 1.2.2+dfsg-5)
  • Migration status for basemap (- to 1.2.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating basemap would introduce bugs in testing: #1074839, #1076957
    • autopkgtest for basemap/1.2.2+dfsg-5: 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/basemap.html
    • Reproducible on armhf - info ♻
    • 155 days old (needed 5 days)
• t4kcommon (- to 0.1.1-11.2)
  • Migration status for t4kcommon (- to 0.1.1-11.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating t4kcommon would introduce bugs in testing: #1075548
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/t4kcommon.html
    • Reproducible on armhf - info ♻
    • 155 days old (needed 5 days)
• eclib (- to 20240408-1)
  • Migration status for eclib (- to 20240408-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 157 days old (needed 5 days)
• file-kanji (- to 1.1-21)
  • Migration status for file-kanji (- to 1.1-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating file-kanji would introduce bugs in testing: #1074957
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/file-kanji.html
    • autopkgtest for file-kanji/1.1-21: 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
    • 157 days old (needed 2 days)
• pglistener (- to 5.1-2)
  • Migration status for pglistener (- to 5.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pglistener libnss-db (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pglistener.html
    • autopkgtest for pglistener/5.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
    • 157 days old (needed 2 days)
• pympress (- to 1.8.5-1)
  • Migration status for pympress (- to 1.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pympress would introduce bugs in testing: #1076908
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pympress.html
    • autopkgtest for pympress/1.8.5-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 157 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: #1077815
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/form.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 158 days old (needed 5 days)
• deepin-terminal (- to 5.9.40+dfsg-2)
  • Migration status for deepin-terminal (- to 5.9.40+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating deepin-terminal would introduce bugs in testing: #1078279
    • Depends: deepin-terminal zssh
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepin-terminal.html
    • Reproducible on armhf - info ♻
    • 159 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 ♻
    • 159 days old (needed 5 days)
• vitrage (- to 12.0.0-1)
  • Migration status for vitrage (- to 12.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vitrage would introduce bugs in testing: #1072250
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/v/vitrage.html
    • autopkgtest for vitrage/12.0.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:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 159 days old (needed 5 days)
• zaqar (- to 18.0.0-1)
  • Migration status for zaqar (- to 18.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zaqar would introduce bugs in testing: #1073468
    • autopkgtest for zaqar/18.0.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/z/zaqar.html
    • 159 days old (needed 5 days)
• libvformat (- to 1.13-12.2)
  • Migration status for libvformat (- to 1.13-12.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libvformat would introduce bugs in testing: #1075216
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvformat.html
    • Reproducible on armhf - info ♻
    • 160 days old (needed 5 days)
• rust-istring (- to 0.3.3-1)
  • Migration status for rust-istring (- to 0.3.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-istring rust-datasize (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-istring.html
    • autopkgtest for rust-istring/0.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
    • 160 days old (needed 2 days)
• rust-str-indices (- to 0.4.3-1)
  • Migration status for rust-str-indices (- to 0.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-str-indices/0.4.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/r/rust-str-indices.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 160 days old (needed 5 days)
• sysdig (- to 0.36.0+repack-1)
  • Migration status for sysdig (- to 0.36.0+repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sysdig would introduce bugs in testing: #1066959
    • sysdig unsatisfiable Build-Depends(-Arch) on armel: libfalcosecurity0-dev (>= 0.11.3)
    • sysdig unsatisfiable Build-Depends(-Arch) on armhf: libfalcosecurity0-dev (>= 0.11.3)
    • sysdig unsatisfiable Build-Depends(-Arch) on i386: libfalcosecurity0-dev (>= 0.11.3)
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on riscv64
    • 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:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): sysdig falcosecurity-libs (not considered)
    • Depends: sysdig falcosecurity-libs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysdig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 160 days old (needed 5 days)
• checkpw (- to 1.02-4)
  • Migration status for checkpw (- to 1.02-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating checkpw would introduce bugs in testing: #1074879
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/checkpw.html
    • Reproducible on armhf - info ♻
    • 161 days old (needed 5 days)
• mumble (- to 1.5.517-2)
  • Migration status for mumble (- to 1.5.517-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mumble would introduce bugs in testing: #1071058, #1073741
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mumble.html
    • autopkgtest for mumble/1.5.517-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 ♻
    • 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 ♻
    • 161 days old (needed 5 days)
• ocaml-ffmpeg (- to 1.1.11-1)
  • Migration status for ocaml-ffmpeg (- to 1.1.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libffmpeg-ocaml/amd64 has unsatisfiable dependency
    • libffmpeg-ocaml-dev/amd64 has unsatisfiable dependency
    • libffmpeg-ocaml/arm64 has unsatisfiable dependency
    • libffmpeg-ocaml-dev/arm64 has unsatisfiable dependency
    • libffmpeg-ocaml/armel has unsatisfiable dependency
    • libffmpeg-ocaml-dev/armel has unsatisfiable dependency
    • libffmpeg-ocaml/armhf has unsatisfiable dependency
    • libffmpeg-ocaml-dev/armhf has unsatisfiable dependency
    • libffmpeg-ocaml/i386 has unsatisfiable dependency
    • libffmpeg-ocaml-dev/i386 has unsatisfiable dependency
    • libffmpeg-ocaml/mips64el has unsatisfiable dependency
    • libffmpeg-ocaml-dev/mips64el has unsatisfiable dependency
    • libffmpeg-ocaml/ppc64el has unsatisfiable dependency
    • libffmpeg-ocaml-dev/ppc64el has unsatisfiable dependency
    • libffmpeg-ocaml/s390x has unsatisfiable dependency
    • libffmpeg-ocaml-dev/s390x has unsatisfiable dependency
    • Updating ocaml-ffmpeg would introduce bugs in testing: #1072440
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-ffmpeg.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 161 days old (needed 5 days)
• procyon (- to 0.6.0-2)
  • Migration status for procyon (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating procyon would introduce bugs in testing: #1057532
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/procyon.html
    • Reproducible on armhf - info ♻
    • 161 days old (needed 5 days)
• lomiri-system-settings-security-privacy (- to 1.0.2-3)
  • Migration status for lomiri-system-settings-security-privacy (- to 1.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lomiri-system-settings-security-privacy would introduce bugs in testing: #1080214
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lomiri-system-settings-security-privacy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 162 days old (needed 5 days)
• wily (- to 0.13.42-2)
  • Migration status for wily (- to 0.13.42-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wily would introduce bugs in testing: #1075639
    • 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 s390x binaries not found
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wily.html
    • Reproducible on armhf - info ♻
    • 162 days old (needed 5 days)
• gauche (- to 0.9.14-5)
  • Migration status for gauche (- to 0.9.14-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gauche slib (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gauche.html
    • 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 ♻
    • 163 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
    • Reproducible on armhf - info ♻
    • 164 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 ♻
    • 164 days old (needed 5 days)
• libopendbx (- to 1.4.6-17)
  • Migration status for libopendbx (- to 1.4.6-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libopendbx would introduce bugs in testing: #1075196
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libopendbx.html
    • Reproducible on armhf - info ♻
    • 164 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
    • Reproducible on armhf - info ♻
    • 164 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 python-docformatter (not considered)
    • Build-Depends(-Arch): python-xsdata ruff (not considered)
    • Depends: python-xsdata python-docformatter (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 ♻
    • 164 days old (needed 5 days)
• xtrkcad (- to 1:5.2.0Beta2.1-2)
  • Migration status for xtrkcad (- to 1:5.2.0Beta2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xtrkcad would introduce bugs in testing: #1074722
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xtrkcad.html
    • Reproducible on armhf - info ♻
    • 164 days old (needed 5 days)
• libjpeg9 (- to 1:9f-1)
  • Migration status for libjpeg9 (- to 1:9f-1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 166 days old (needed 5 days)
• atril (- to 1.26.2-3)
  • Migration status for atril (- to 1.26.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating atril would introduce bugs in testing: #1074828
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/atril.html
    • Reproducible on armhf - info ♻
    • 168 days old (needed 5 days)
• borgmatic (- to 1.8.9-1)
  • Migration status for borgmatic (- to 1.8.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): borgmatic pykwalify (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/borgmatic.html
    • autopkgtest for borgmatic/1.8.9-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 169 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: 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
    • 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 ♻
    • 169 days old (needed 5 days)
• xdvik-ja (- to 22.87.06+j1.42-3)
  • Migration status for xdvik-ja (- to 22.87.06+j1.42-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xdvik-ja would introduce bugs in testing: #1075658
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdvik-ja.html
    • Reproducible on armhf - info ♻
    • 169 days old (needed 5 days)
• 0ad (- to 0.0.26-5)
  • Migration status for 0ad (- to 0.0.26-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating 0ad would introduce bugs in testing: #1064726
    • 0ad unsatisfiable Build-Depends(-Arch) on amd64: python3-distutils
    • 0ad unsatisfiable Build-Depends(-Arch) on arm64: python3-distutils
    • 0ad unsatisfiable Build-Depends(-Arch) on armhf: python3-distutils
    • 0ad unsatisfiable Build-Depends(-Arch) on i386: python3-distutils
    • Impossible Depends: 0ad -> libminiupnpc17/2.2.6-1+b1/amd64
    • Impossible Depends: 0ad -> libminiupnpc17/2.2.6-1+b1/arm64
    • Impossible Depends: 0ad -> libminiupnpc17/2.2.6-1+b1/armhf
    • Impossible Depends: 0ad -> libminiupnpc17/2.2.6-1+b1/i386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/0/0ad.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 ♻
    • 170 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
    • 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
    • 170 days old (needed 5 days)
• mpg321 (- to 0.3.2-3.3)
  • Migration status for mpg321 (- to 0.3.2-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mpg321 would introduce bugs in testing: #1075291
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpg321.html
    • Reproducible on armhf - info ♻
    • 170 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 ♻
    • 170 days old (needed 5 days)
• morph-browser (- to 1.1.0+dfsg-2)
  • Migration status for morph-browser (- to 1.1.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating morph-browser would introduce bugs in testing: #1074221
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/morph-browser.html
    • 171 days old (needed 5 days)
• pcsxr (- to 1.9.94-6)
  • Migration status for pcsxr (- to 1.9.94-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pcsxr would introduce bugs in testing: #1075366
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcsxr.html
    • Reproducible on armhf - info ♻
    • 171 days old (needed 5 days)
• tdiary-contrib (- to 5.3.0-1)
  • Migration status for tdiary-contrib (- to 5.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tdiary-contrib would introduce bugs in testing: #1077128
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tdiary-contrib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 171 days old (needed 5 days)
• android-platform-art (- to 14.0.0+r15-2)
  • Migration status for android-platform-art (- to 14.0.0+r15-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-art would introduce bugs in testing: #1072129
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-art.html
    • autopkgtest for android-platform-art/14.0.0+r15-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
    • 172 days old (needed 2 days)
• baler (- to 1.4.0-1)
  • Migration status for baler (- to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating baler would introduce bugs in testing: #1080550
    • Build-Depends(-Arch): baler pytorch (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/baler.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 173 days old (needed 5 days)
• squeekboard (- to 1.24.0-1)
  • Migration status for squeekboard (- to 1.24.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating squeekboard would introduce bugs in testing: #1064373
    • squeekboard unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk+v3-24-dev (>= 0.18)
    • squeekboard unsatisfiable Build-Depends(-Arch) on amd64: librust-serde-yaml-0.8-dev (>= 0.8)
    • squeekboard unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk+v3-24-dev (>= 0.18)
    • squeekboard unsatisfiable Build-Depends(-Arch) on arm64: librust-serde-yaml-0.8-dev (>= 0.8)
    • squeekboard unsatisfiable Build-Depends(-Arch) on armel: librust-gtk+v3-24-dev (>= 0.18)
    • squeekboard unsatisfiable Build-Depends(-Arch) on armel: librust-serde-yaml-0.8-dev (>= 0.8)
    • squeekboard unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk+v3-24-dev (>= 0.18)
    • squeekboard unsatisfiable Build-Depends(-Arch) on armhf: librust-serde-yaml-0.8-dev (>= 0.8)
    • squeekboard unsatisfiable Build-Depends(-Arch) on i386: librust-gtk+v3-24-dev (>= 0.18)
    • squeekboard unsatisfiable Build-Depends(-Arch) on i386: librust-serde-yaml-0.8-dev (>= 0.8)
    • squeekboard unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk+v3-24-dev (>= 0.18)
    • squeekboard unsatisfiable Build-Depends(-Arch) on mips64el: librust-serde-yaml-0.8-dev (>= 0.8)
    • squeekboard unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk+v3-24-dev (>= 0.18)
    • squeekboard unsatisfiable Build-Depends(-Arch) on ppc64el: librust-serde-yaml-0.8-dev (>= 0.8)
    • squeekboard unsatisfiable Build-Depends(-Arch) on riscv64: librust-gtk+v3-24-dev (>= 0.18)
    • squeekboard unsatisfiable Build-Depends(-Arch) on riscv64: librust-serde-yaml-0.8-dev (>= 0.8)
    • squeekboard unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk+v3-24-dev (>= 0.18)
    • squeekboard unsatisfiable Build-Depends(-Arch) on s390x: librust-serde-yaml-0.8-dev (>= 0.8)
    • Build-Depends(-Arch): squeekboard rust-gtk-sys (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squeekboard.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 ♻
    • 173 days old (needed 5 days)
• libgda5 (- to 5.2.10-4.1)
  • Migration status for libgda5 (- to 5.2.10-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgda5 would introduce bugs in testing: #1075169
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgda5.html
    • Reproducible on armhf - info ♻
    • 175 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 ♻
    • 175 days old (needed 5 days)
• liquidsoap (- to 2.2.4-1)
  • Migration status for liquidsoap (- to 2.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liquidsoap/amd64 has unsatisfiable dependency
    • liquidsoap/arm64 has unsatisfiable dependency
    • liquidsoap/armel has unsatisfiable dependency
    • liquidsoap/armhf has unsatisfiable dependency
    • liquidsoap/i386 has unsatisfiable dependency
    • liquidsoap/mips64el has unsatisfiable dependency
    • liquidsoap/ppc64el has unsatisfiable dependency
    • liquidsoap/s390x has unsatisfiable dependency
    • Updating liquidsoap would introduce bugs in testing: #1064128, #1072432, #1077110
    • autopkgtest for liquidsoap/2.2.4-1: riscv64: Regression or new test ♻
    • Build-Depends(-Arch): liquidsoap ocaml-ffmpeg (not considered)
    • Build-Depends(-Arch): liquidsoap ocaml-lo (not considered)
    • Build-Depends(-Arch): liquidsoap pcre-ocaml (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/liquidsoap.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 ♻
    • 176 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
    • 176 days old (needed 2 days)
• ruby-hdfeos5 (- to 1.2-12)
  • Migration status for ruby-hdfeos5 (- to 1.2-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-hdfeos5 would introduce bugs in testing: #1075463
    • Build-Depends(-Arch): ruby-hdfeos5 hdf-eos5 (not considered)
    • Build-Depends(-Arch): ruby-hdfeos5 libgctp (not considered)
    • Depends: ruby-hdfeos5 hdf-eos5 (not considered)
    • Depends: ruby-hdfeos5 libgctp (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-hdfeos5.html
    • autopkgtest for ruby-hdfeos5/1.2-12: 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
    • 176 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-premailer-rails ruby-premailer (not considered)
    • Depends: ruby-premailer-rails ruby-premailer (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 176 days old (needed 2 days)
• edlio (- to 0.2.0-2)
  • Migration status for edlio (- to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating edlio would introduce bugs in testing: #1073453
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/edlio.html
    • autopkgtest for edlio/0.2.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on armhf - info ♻
    • 178 days old (needed 5 days)
• notion (- to 4.0.2+dfsg-7)
  • Migration status for notion (- to 4.0.2+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating notion would introduce bugs in testing: #1075318
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/notion.html
    • Reproducible on armhf - info ♻
    • 179 days old (needed 5 days)
• ucommon (- to 7.0.1-0.3)
  • Migration status for ucommon (- to 7.0.1-0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ucommon would introduce bugs in testing: #1068887, #1081107
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ucommon.html
    • 179 days old (needed 5 days)
• hyperkitty (- to 1.3.9-1)
  • Migration status for hyperkitty (- to 1.3.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyperkitty would introduce bugs in testing: #1073392
    • autopkgtest for hyperkitty/1.3.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyperkitty.html
    • Reproducible on armhf - info ♻
    • 180 days old (needed 5 days)
• yuzu (- to 0-1335+ds-1.4)
  • Migration status for yuzu (- to 0-1335+ds-1.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • yuzu/amd64 has unsatisfiable dependency
    • yuzu/arm64 has unsatisfiable dependency
    • Updating yuzu would introduce bugs in testing: #1077401
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yuzu.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 180 days old (needed 5 days)
• fcitx-fbterm (- to 0.2.0-5)
  • Migration status for fcitx-fbterm (- to 0.2.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fcitx-fbterm fbterm (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fcitx-fbterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 181 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
    • 181 days old (needed 5 days)
• asmail (- to 2.1-6)
  • Migration status for asmail (- to 2.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asmail would introduce bugs in testing: #1074822
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asmail.html
    • Reproducible on armhf - info ♻
    • 182 days old (needed 5 days)
• calculix-ccx (- to 2.21-1)
  • Migration status for calculix-ccx (- to 2.21-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): calculix-ccx spooles (not considered)
    • Depends: calculix-ccx spooles (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calculix-ccx.html
    • autopkgtest for calculix-ccx/2.21-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)
• ferret-vis (- to 7.6.0-7)
  • Migration status for ferret-vis (- to 7.6.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ferret-vis would introduce bugs in testing: #1074953, #1077100
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/ferret-vis.html
    • 182 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• xcolors (- to 1.5a-9)
  • Migration status for xcolors (- to 1.5a-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xcolors would introduce bugs in testing: #1075653
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcolors.html
    • Reproducible on armhf - info ♻
    • 182 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 184 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• locust (- to 2.24.0-1)
  • Migration status for locust (- to 2.24.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): locust geventhttpclient (not considered)
    • Depends: locust geventhttpclient (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/locust.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 185 days old (needed 5 days)
• libreswan (- to 4.14-1)
  • Migration status for libreswan (- to 4.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libreswan would introduce bugs in testing: #1073665
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libreswan.html
    • autopkgtest for libreswan/4.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
    • 186 days old (needed 2 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
    • 188 days old (needed 5 days)
• gitlab (- to 16.8.4-1)
  • Migration status for gitlab (- to 16.8.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab would introduce bugs in testing: #1009942, #1077946, #983915
    • autopkgtest for gitlab/16.8.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 ♻
    • Not built on buildd: arch all binaries uploaded by vivekkj@disroot.org, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by vivekkj@disroot.org
    • Depends: gitlab ruby-batch-loader (not considered)
    • Depends: gitlab ruby-elasticsearch-model (not considered)
    • Depends: gitlab ruby-github-markup
    • Depends: gitlab ruby-gitlab-markup (not considered)
    • Depends: gitlab ruby-gon (not considered)
    • Depends: gitlab ruby-graphlient (not considered)
    • Depends: gitlab ruby-html-pipeline (not considered)
    • Depends: gitlab ruby-premailer-rails
    • Depends: gitlab ruby-prometheus-client-mmap (not considered)
    • Depends: gitlab ruby-ruby-magic-static (not considered)
    • Depends: gitlab ruby-ruby-openai (not considered)
    • Depends: gitlab ruby-semver-dialects
    • Depends: gitlab ruby-task-list
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab.html
    • Reproducible on armhf - info ♻
    • 188 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 ♻
    • 189 days old (needed 5 days)
• php-fig-log-test (- to 1.1.0-2)
  • Migration status for php-fig-log-test (- to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-fig-log-test has no binaries on any arch
    • Updating php-fig-log-test would introduce bugs in testing: #1070545
    • php-fig-log-test unsatisfiable Build-Depends(-Arch) on amd64: php-psr-log (>= 2.0)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 190 days old (needed 5 days)
• qstardict (- to 1.4.1-2)
  • Migration status for qstardict (- to 1.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qstardict would introduce bugs in testing: #1078385
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qstardict.html
    • Reproducible on armhf - info ♻
    • 190 days old (needed 5 days)
• shaarli (- to 0.13.0+dfsg-3)
  • Migration status for shaarli (- to 0.13.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): shaarli php-oscarotero-gettext (not considered)
    • Depends: shaarli php-oscarotero-gettext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shaarli.html
    • autopkgtest for shaarli/0.13.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
    • 190 days old (needed 2 days)
• gitlabracadabra (- to 2.1.0)
  • Migration status for gitlabracadabra (- to 2.1.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlabracadabra would introduce bugs in testing: #1073420
    • autopkgtest for gitlabracadabra/2.1.0: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlabracadabra.html
    • Reproducible on armhf - info ♻
    • 191 days old (needed 5 days)
• nng (- to 1.7.3-1)
  • Migration status for nng (- to 1.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libnng1/armel has unsatisfiable dependency
    • Updating nng would introduce bugs in testing: #1063604
    • missing build on ppc64el
    • missing build on s390x
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nng.html
    • uninstallable on arch armel, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 191 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:
    • Updating phpcpd would introduce bugs in testing: #1070618
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpcpd.html
    • autopkgtest for phpcpd/6.0.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
    • 191 days old (needed 2 days)
• fastapi (- to 0.110.0-1)
  • Migration status for fastapi (- to 0.110.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fastapi would introduce bugs in testing: #1073445
    • autopkgtest for fastapi/0.110.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/f/fastapi.html
    • 192 days old (needed 5 days)
• anki (- to 2.1.15+dfsg-4)
  • Migration status for anki (- to 2.1.15+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • anki/amd64 has unsatisfiable dependency
    • anki/arm64 has unsatisfiable dependency
    • Updating anki would introduce bugs in testing: #1053541, #1065822, #1067702, #1077548, #1080508, #958853
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/anki.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 193 days old (needed 5 days)
• geventhttpclient (- to 2.0.11-2)
  • Migration status for geventhttpclient (- to 2.0.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating geventhttpclient would introduce bugs in testing: #1074990
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geventhttpclient.html
    • autopkgtest for geventhttpclient/2.0.11-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
    • 195 days old (needed 2 days)
• guacamole-server (- to 1.3.0-1.3)
  • Migration status for guacamole-server (- to 1.3.0-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guacamole-server would introduce bugs in testing: #1005154, #1079964, #1081523
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guacamole-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 195 days old (needed 5 days)
• mysql-connector-python (- to 8.0.15-4)
  • Migration status for mysql-connector-python (- to 8.0.15-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-connector-python would introduce bugs in testing: #1076136, #1077767, #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 ♻
    • 196 days old (needed 5 days)
• openvdb (- to 10.0.1-2.1)
  • Migration status for openvdb (- to 10.0.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openvdb would introduce bugs in testing: #1061216
    • Build-Depends(-Arch): openvdb llvm-toolchain-14 (not considered)
    • Depends: openvdb llvm-toolchain-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvdb.html
    • 196 days old (needed 5 days)
• linphone (- to 5.2.0-4.3)
  • Migration status for linphone (- to 5.2.0-4.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): linphone mediastreamer2 (not considered)
    • Depends: linphone mediastreamer2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linphone.html
    • 197 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)
    • 197 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 ♻
    • 197 days old (needed 5 days)
• pth (- to 2.0.7-22.1)
  • Migration status for pth (- to 2.0.7-22.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pth would introduce bugs in testing: #1075400
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pth.html
    • Reproducible on armhf - info ♻
    • 197 days old (needed 5 days)
• pytorch-cuda (- to 2.1.2+dfsg-3)
  • Migration status for pytorch-cuda (- to 2.1.2+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-torch-cuda/amd64 has unsatisfiable dependency
    • Updating pytorch-cuda would introduce bugs in testing: #1065943
    • pytorch-cuda unsatisfiable Build-Depends(-Arch) on amd64: libflatbuffers-dev (<< 2.0.9~)
    • pytorch-cuda unsatisfiable Build-Depends(-Arch) on amd64: python3-distutils
    • pytorch-cuda unsatisfiable Build-Depends(-Arch) on ppc64el: libflatbuffers-dev (<< 2.0.9~)
    • pytorch-cuda unsatisfiable Build-Depends(-Arch) on ppc64el: python3-distutils
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): pytorch-cuda gloo-cuda (not considered)
    • Build-Depends(-Arch): pytorch-cuda ideep (not considered)
    • Depends: pytorch-cuda gloo-cuda (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • 197 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/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 s390x, not running autopkgtest there
    • 197 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
    • Reproducible on armhf - info ♻
    • 197 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 ♻
    • 197 days old (needed 5 days)
• spherepack (- to 3.3~a1-5.1)
  • Migration status for spherepack (- to 3.3~a1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spherepack would introduce bugs in testing: #1076926
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spherepack.html
    • autopkgtest for spherepack/3.3~a1-5.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 197 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:
    • Updating spooles would introduce bugs in testing: #1075534
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spooles.html
    • autopkgtest for spooles/2.2-14.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
    • 197 days old (needed 2 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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 ♻
    • 197 days old (needed 5 days)
• tgl (- to 2.0.1+git20160323.ffb04cac-3.1)
  • Migration status for tgl (- to 2.0.1+git20160323.ffb04cac-3.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • 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 ♻
    • 197 days old (needed 5 days)
• zssh (- to 1.5c.debian.1-10)
  • Migration status for zssh (- to 1.5c.debian.1-10): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: zssh lrzsz (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zssh.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 197 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 ♻
    • 198 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 ♻
    • 198 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:
    • autopkgtest for chemps2/1.8.12-3.1: arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for chemps2/blocked-on-ci-infra: amd64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chemps2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 198 days old (needed 5 days)
• comedilib (- to 0.11.0+5-1.1)
  • Migration status for comedilib (- to 0.11.0+5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating comedilib would introduce bugs in testing: #1058848, #1072752
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/comedilib.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 ♻
    • 198 days old (needed 5 days)
• dsh (- to 0.25.10-1.6)
  • Migration status for dsh (- to 0.25.10-1.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dsh would introduce bugs in testing: #1074921
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dsh.html
    • Reproducible on armhf - info ♻
    • 198 days old (needed 5 days)
• gerris (- to 20131206+dfsg-19.1)
  • Migration status for gerris (- to 20131206+dfsg-19.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gerris would introduce bugs in testing: #1074988
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gerris.html
    • autopkgtest for gerris/20131206+dfsg-19.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
    • 198 days old (needed 2 days)
• gfsview (- to 20121130+dfsg-8.1)
  • Migration status for gfsview (- to 20121130+dfsg-8.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gfsview gerris (not considered)
    • Depends: gfsview gerris (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfsview.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 198 days old (needed 5 days)
• gnuastro (- to 0.22-3.1)
  • Migration status for gnuastro (- to 0.22-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnuastro would introduce bugs in testing: #1052763
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnuastro.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 198 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:
    • Updating grok would introduce bugs in testing: #1000065, #1065556
    • 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 grok/1.20110708.1-7.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): grok pcre3 (not considered)
    • Depends: grok pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grok.html
    • 198 days old (needed 5 days)
• http-relay (- to 2.1.3-1)
  • Migration status for http-relay (- to 2.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by gladky.anton@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/http-relay.html
    • autopkgtest for http-relay/2.1.3-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 198 days old (needed 5 days)
• lammps (- to 20240207+dfsg-1.1)
  • Migration status for lammps (- to 20240207+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lammps would introduce bugs in testing: #1076465
    • autopkgtest for lammps/20240207+dfsg-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/l/lammps.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 198 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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 ♻
    • 198 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 ♻
    • 198 days old (needed 5 days)
• libktoblzcheck (- to 1.53-3.1)
  • Migration status for libktoblzcheck (- to 1.53-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libktoblzcheck would introduce bugs in testing: #1074673
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libktoblzcheck.html
    • autopkgtest for libktoblzcheck/1.53-3.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
    • 198 days old (needed 2 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:
    • Updating libonvif would introduce bugs in testing: #1072430
    • Impossible Depends: libonvif -> libavfilter-extra9/7:6.1.1-5+b1/mips64el
    • Impossible Depends: libonvif -> libavfilter-extra9/7:6.1.1-5+b1/s390x
    • Impossible Depends: libonvif -> libavfilter9/7:6.1.1-5+b1/amd64
    • Impossible Depends: libonvif -> libavfilter9/7:6.1.1-5+b1/arm64
    • Impossible Depends: libonvif -> libavfilter9/7:6.1.1-5+b1/armel
    • Impossible Depends: libonvif -> libavfilter9/7:6.1.1-5+b1/armhf
    • Impossible Depends: libonvif -> libavfilter9/7:6.1.1-5+b1/i386
    • Impossible Depends: libonvif -> libavfilter9/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: libonvif -> libavformat-extra60/7:6.1.1-5+b1/armel
    • Impossible Depends: libonvif -> libavformat-extra60/7:6.1.1-5+b1/i386
    • Impossible Depends: libonvif -> libavformat60/7:6.1.1-5+b1/armhf
    • Impossible Depends: libonvif -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: libonvif -> libavformat60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: libonvif -> libavformat60/7:6.1.1-5+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libonvif.html
    • Reproducible on armhf - info ♻
    • 198 days old (needed 5 days)
• libopenshot (- to 0.3.2+dfsg1-2.1)
  • Migration status for libopenshot (- to 0.3.2+dfsg1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libopenshot would introduce bugs in testing: #1072431
    • Impossible Depends: libopenshot -> libavformat-extra60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: libopenshot -> libavformat60/7:6.1.1-5+b1/armhf
    • Impossible Depends: libopenshot -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: libopenshot -> libavformat60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: libopenshot -> libavformat60/7:6.1.1-5+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libopenshot.html
    • Reproducible on armhf - info ♻
    • 198 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
    • 198 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
    • Reproducible on armhf - info ♻
    • 198 days old (needed 5 days)
• libstorj (- to 1.0.3-1.3)
  • Migration status for libstorj (- to 1.0.3-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libstorj would introduce bugs in testing: #1075210
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libstorj.html
    • Reproducible on armhf - info ♻
    • 198 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:
    • Updating libsynthesis would introduce bugs in testing: #1000047
    • Build-Depends(-Arch): libsynthesis pcre3 (not considered)
    • Depends: libsynthesis pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsynthesis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 198 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 ♻
    • 198 days old (needed 5 days)
• libtar (- to 1.2.20-8.1)
  • Migration status for libtar (- to 1.2.20-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libtar would introduce bugs in testing: #1072586
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 198 days old (needed 5 days)
• libtcod (- to 1.18.1+dfsg-1.1)
  • Migration status for libtcod (- to 1.18.1+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libtcod would introduce bugs in testing: #1075212
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtcod.html
    • autopkgtest for libtcod/1.18.1+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 armhf - info ♻
    • 198 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 198 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 ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 198 days old (needed 5 days)
• moosefs (- to 3.0.117-1.1)
  • Migration status for moosefs (- to 3.0.117-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating moosefs would introduce bugs in testing: #1073707
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/moosefs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 198 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
    • 198 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
    • Depends: ogre-1.9 blender
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ogre-1.9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 198 days old (needed 5 days)
• oidc-agent (- to 4.2.6-1.1)
  • Migration status for oidc-agent (- to 4.2.6-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oidc-agent yad (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oidc-agent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 198 days old (needed 5 days)
• opencolorio (- to 2.1.3+dfsg-1.1)
  • Migration status for opencolorio (- to 2.1.3+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): opencolorio openimageio (not considered)
    • Depends: opencolorio openimageio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencolorio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 198 days old (needed 5 days)
• php-oscarotero-gettext (- to 4.8.7-2)
  • Migration status for php-oscarotero-gettext (- to 4.8.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-oscarotero-gettext would introduce bugs in testing: #1073425
    • autopkgtest for php-oscarotero-gettext/4.8.7-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/p/php-oscarotero-gettext.html
    • Reproducible on armhf - info ♻
    • 198 days old (needed 5 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 ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 198 days old (needed 5 days)
• xpaint (- to 2.9.1.4-4.1)
  • Migration status for xpaint (- to 2.9.1.4-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xpaint would introduce bugs in testing: #1075677
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xpaint.html
    • Reproducible on armhf - info ♻
    • 198 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
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 198 days old (needed 2 days)
• aa3d (- to 1.0-8.2)
  • Migration status for aa3d (- to 1.0-8.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aa3d would introduce bugs in testing: #1066274
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aa3d.html
    • 199 days old (needed 5 days)
• amideco (- to 0.31e-3.3)
  • Migration status for amideco (- to 0.31e-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating amideco would introduce bugs in testing: #1074808
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amideco.html
    • Reproducible on armhf - info ♻
    • 199 days old (needed 5 days)
• apbs (- to 3.4.1-5.1)
  • Migration status for apbs (- to 3.4.1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apbs would introduce bugs in testing: #1033528, #1077646
    • autopkgtest for apbs/3.4.1-5.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 ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • autopkgtest for apbs/blocked-on-ci-infra: armel: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apbs.html
    • Reproducible on armhf - info ♻
    • 199 days old (needed 5 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:
    • Updating armnn would introduce bugs in testing: #1074820
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/armnn.html
    • autopkgtest for armnn/23.08-4.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 199 days old (needed 2 days)
• ascd (- to 0.13.2-7.1)
  • Migration status for ascd (- to 0.13.2-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ascd would introduce bugs in testing: #1074819
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ascd.html
    • Reproducible on armhf - info ♻
    • 199 days old (needed 5 days)
• aview (- to 1.3.0rc1-9.2)
  • Migration status for aview (- to 1.3.0rc1-9.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aview would introduce bugs in testing: #1066359
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aview.html
    • 199 days old (needed 5 days)
• boost1.74 (- to 1.74.0+ds1-23.1)
  • Migration status for boost1.74 (- to 1.74.0+ds1-23.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating boost1.74 would introduce bugs in testing: #1060102
    • autopkgtest for boost1.74/1.74.0+ds1-23.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/b/boost1.74.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 199 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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:
    • autopkgtest for brial/1.2.12-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:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/brial.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 199 days old (needed 5 days)
• cctbx (- to 2023.12+ds2+~3.17.0+ds1-4)
  • Migration status for cctbx (- to 2023.12+ds2+~3.17.0+ds1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cctbx would introduce bugs in testing: #1076084
    • autopkgtest for cctbx/2023.12+ds2+~3.17.0+ds1-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Ignored failure, s390x: Regression or new test ♻
    • Build-Depends(-Arch): cctbx clipper
    • Build-Depends(-Arch): cctbx ssm
    • Depends: cctbx libccp4 (not considered)
    • Depends: cctbx ssm
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cctbx.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 199 days old (needed 5 days)
• ctpl (- to 0.3.4+dfsg-4.1)
  • Migration status for ctpl (- to 0.3.4+dfsg-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ctpl would introduce bugs in testing: #1074895
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ctpl.html
    • Reproducible on armhf - info ♻
    • 199 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
    • Build-Depends(-Arch): cvm freecdb
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cvm.html
    • Reproducible on armhf - info ♻
    • 199 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
    • Reproducible on armhf - info ♻
    • 199 days old (needed 5 days)
• dart (- to 6.12.1+dfsg4-13.1)
  • Migration status for dart (- to 6.12.1+dfsg4-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dart would introduce bugs in testing: #1076730
    • autopkgtest for dart/6.12.1+dfsg4-13.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/d/dart.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 199 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• eiskaltdcpp (- to 2.4.2-1.1)
  • Migration status for eiskaltdcpp (- to 2.4.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eiskaltdcpp would introduce bugs in testing: #1000100, #1076688
    • Impossible Depends: eiskaltdcpp -> libminiupnpc17/2.2.6-1+b1/amd64
    • Impossible Depends: eiskaltdcpp -> libminiupnpc17/2.2.6-1+b1/arm64
    • Impossible Depends: eiskaltdcpp -> libminiupnpc17/2.2.6-1+b1/armel
    • Impossible Depends: eiskaltdcpp -> libminiupnpc17/2.2.6-1+b1/armhf
    • Impossible Depends: eiskaltdcpp -> libminiupnpc17/2.2.6-1+b1/i386
    • Impossible Depends: eiskaltdcpp -> libminiupnpc17/2.2.6-1+b1/mips64el
    • Impossible Depends: eiskaltdcpp -> libminiupnpc17/2.2.6-1+b1/ppc64el
    • Impossible Depends: eiskaltdcpp -> libminiupnpc17/2.2.6-1+b1/s390x
    • Build-Depends(-Arch): eiskaltdcpp pcre3 (not considered)
    • Depends: eiskaltdcpp pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eiskaltdcpp.html
    • Reproducible on armhf - info ♻
    • 199 days old (needed 5 days)
• guvcview (- to 2.0.8-2.1)
  • Migration status for guvcview (- to 2.0.8-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guvcview would introduce bugs in testing: #1072421
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guvcview.html
    • Reproducible on armhf - info ♻
    • 199 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gxr.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 199 days old (needed 5 days)
• h2o (- to 2.2.5+dfsg2-8.1)
  • Migration status for h2o (- to 2.2.5+dfsg2-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating h2o would introduce bugs in testing: #1075058
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/h2o.html
    • autopkgtest for h2o/2.2.5+dfsg2-8.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
    • 199 days old (needed 2 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 ♻
    • 199 days old (needed 5 days)
• ignition-physics (- to 5.1.0+ds1-4.2)
  • Migration status for ignition-physics (- to 5.1.0+ds1-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ignition-physics would introduce bugs in testing: #1075087
    • Build-Depends(-Arch): ignition-physics dart (not considered)
    • Depends: ignition-physics dart (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ignition-physics.html
    • Reproducible on armhf - info ♻
    • 199 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• libghemical (- to 3.0.0-4.4)
  • Migration status for libghemical (- to 3.0.0-4.4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libghemical mpqc (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): libghemical mopac7
    • Depends: libghemical mopac7
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libghemical.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 199 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
    • Depends: tlog curl (not considered)
  • 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 ♻
    • 199 days old (needed 5 days)
• rust-futures-rustls (- to 0.24.0-3)
  • Migration status for rust-futures-rustls (- to 0.24.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rust-futures-rustls has no binaries on any arch
    • Updating rust-futures-rustls would introduce bugs in testing: #1069216
    • rust-futures-rustls unsatisfiable Build-Depends(-Arch) on amd64: librust-smol-1+default-dev
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 200 days old (needed 5 days)
• matomo-device-detector (- to 6.3.0-1)
  • Migration status for matomo-device-detector (- to 6.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • matomo-device-detector/amd64 has unsatisfiable dependency
    • matomo-device-detector/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/matomo-device-detector.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 203 days old (needed 5 days)
• python-guizero (- to 1.5.0+dfsg-1)
  • Migration status for python-guizero (- to 1.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-guizero would introduce bugs in testing: #1070434
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-guizero.html
    • autopkgtest for python-guizero/1.5.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
    • 203 days old (needed 2 days)
• wannier90 (- to 3.1.0+ds-8)
  • Migration status for wannier90 (- to 3.1.0+ds-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wannier90 would introduce bugs in testing: #1074524
    • autopkgtest for wannier90/3.1.0+ds-8: 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 ♻
    • autopkgtest for wannier90/blocked-on-ci-infra: armel: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wannier90.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 203 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
    • 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: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-riddle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 204 days old (needed 5 days)
• ikos (- to 3.2-3)
  • Migration status for ikos (- to 3.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ikos has no binaries on any arch
    • nothing built yet, autopkgtest delayed
    • Build-Depends(-Arch): ikos llvm-toolchain-14 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 206 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:
    • python3-siconos/amd64 has unsatisfiable dependency
    • python3-siconos/arm64 has unsatisfiable dependency
    • python3-siconos/ppc64el has unsatisfiable dependency
    • Updating siconos would introduce bugs in testing: #1066316
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/siconos.html
    • autopkgtest for siconos/4.4.0+dfsg-4: riscv64: Regression or new test ♻
  • 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, not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 206 days old (needed 5 days)
• nipype (- to 1.8.6-3)
  • Migration status for nipype (- to 1.8.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-nipype/amd64 has unsatisfiable dependency
    • python3-nipype/arm64 has unsatisfiable dependency
    • Updating nipype would introduce bugs in testing: #1064732, #1081079
    • autopkgtest for nipype/1.8.6-3: riscv64: Regression or new test ♻
    • nipype unsatisfiable Build-Depends(-Arch) on amd64: python3-funcsigs
    • Build-Depends(-Arch): nipype nipy (not considered)
    • Build-Depends(-Arch): nipype nitime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nipype.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • 208 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 ♻
    • 208 days old (needed 5 days)
• r-cran-areal (- to 0.1.8+dfsg-2)
  • Migration status for r-cran-areal (- to 0.1.8+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-areal r-cran-sf (not considered)
    • Depends: r-cran-areal r-cran-sf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-areal.html
    • autopkgtest for r-cran-areal/0.1.8+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
    • 209 days old (needed 2 days)
• r-cran-ncdfgeom (- to 1.1.6+dfsg-1)
  • Migration status for r-cran-ncdfgeom (- to 1.1.6+dfsg-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-ncdfgeom r-cran-sf (not considered)
    • Depends: r-cran-ncdfgeom r-cran-sf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-ncdfgeom r-cran-areal
    • Build-Depends(-Arch): r-cran-ncdfgeom r-cran-stars
    • Depends: r-cran-ncdfgeom r-cran-areal
    • Depends: r-cran-ncdfgeom r-cran-stars
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-ncdfgeom.html
    • autopkgtest for r-cran-ncdfgeom/1.1.6+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
    • 209 days old (needed 2 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
    • 209 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 ♻
    • 210 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 ♻
    • 210 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 ♻
    • 210 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 ♻
    • 210 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 ♻
    • 210 days old (needed 5 days)
• budgie-desktop (- to 10.8.2-3)
  • Migration status for budgie-desktop (- to 10.8.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • budgie-core/amd64 has unsatisfiable dependency
    • budgie-core/arm64 has unsatisfiable dependency
    • budgie-core/armel has unsatisfiable dependency
    • budgie-core/armhf has unsatisfiable dependency
    • budgie-core/i386 has unsatisfiable dependency
    • budgie-core/mips64el has unsatisfiable dependency
    • budgie-core/ppc64el has unsatisfiable dependency
    • budgie-core/s390x has unsatisfiable dependency
    • Updating budgie-desktop would introduce bugs in testing: #1067117
    • autopkgtest for budgie-desktop/10.8.2-3: riscv64: Regression or new test ♻
    • budgie-desktop unsatisfiable Build-Depends(-Arch) on amd64: libmutter-12-dev
    • budgie-desktop unsatisfiable Build-Depends(-Arch) on arm64: libmutter-12-dev
    • budgie-desktop unsatisfiable Build-Depends(-Arch) on armel: libmutter-12-dev
    • budgie-desktop unsatisfiable Build-Depends(-Arch) on armhf: libmutter-12-dev
    • budgie-desktop unsatisfiable Build-Depends(-Arch) on i386: libmutter-12-dev
    • budgie-desktop unsatisfiable Build-Depends(-Arch) on mips64el: libmutter-12-dev
    • budgie-desktop unsatisfiable Build-Depends(-Arch) on ppc64el: libmutter-12-dev
    • budgie-desktop unsatisfiable Build-Depends(-Arch) on riscv64: libmutter-12-dev
    • budgie-desktop unsatisfiable Build-Depends(-Arch) on s390x: libmutter-12-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/budgie-desktop.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 ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 211 days old (needed 5 days)
• libcbor (0.10.2-1.1 to 0.10.2-1.2)
  • Migration status for libcbor (0.10.2-1.1 to 0.10.2-1.2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
  • Additional info:
    • Updating libcbor will fix bugs in testing: #1070818
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcbor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 211 days old (needed 5 days)
• simdjson (- to 3.6.4-1)
  • Migration status for simdjson (- to 3.6.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simdjson would introduce bugs in testing: #1075510, #1077417
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simdjson.html
    • autopkgtest for simdjson/3.6.4-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
    • 211 days old (needed 2 days)
• snapraid (- to 12.3-1)
  • Migration status for snapraid (- to 12.3-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/snapraid.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 211 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 ♻
    • 212 days old (needed 5 days)
• prometheus-pgbouncer-exporter (- to 1.7-3)
  • Migration status for prometheus-pgbouncer-exporter (- to 1.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prometheus-pgbouncer-exporter would introduce bugs in testing: #1073739, #991879
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prometheus-pgbouncer-exporter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 213 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 ♻
    • 213 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 214 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:
    • Updating prody would introduce bugs in testing: #1058454, #1071807
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for prody/2.4.1+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prody.html
    • 214 days old (needed 5 days)
• deblur (- to 1.1.1-1)
  • Migration status for deblur (- to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/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-1: 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 ♻
    • 215 days old (needed 5 days)
• nfft (- to 3.5.3-3)
  • Migration status for nfft (- to 3.5.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nfft would introduce bugs in testing: #1063922, #1081084
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nfft.html
    • autopkgtest for nfft/3.5.3-3: 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
    • 215 days old (needed 2 days)
• routine-update (- to 0.2)
  • Migration status for routine-update (- to 0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/routine-update.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 215 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• tahoe-lafs (- to 1.17.0-1)
  • Migration status for tahoe-lafs (- to 1.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • tahoe-lafs/amd64 has unsatisfiable dependency
    • tahoe-lafs/arm64 has unsatisfiable dependency
    • Updating tahoe-lafs would introduce bugs in testing: #1063827
    • autopkgtest for tahoe-lafs/1.17.0-1: riscv64: Regression or new test ♻
    • tahoe-lafs unsatisfiable Build-Depends(-Arch) on amd64: python3-future
    • Not built on buildd: arch all binaries uploaded by andrius.merkys@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/tahoe-lafs.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 215 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:
    • 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)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psychopy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 216 days old (needed 5 days)
• ruby-graphlient (- to 0.7.0-1)
  • Migration status for ruby-graphlient (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-graphlient would introduce bugs in testing: #1068392
    • Build-Depends(-Arch): ruby-graphlient ruby-faraday-middleware (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-graphlient.html
    • autopkgtest for ruby-graphlient/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 ♻
    • 216 days old (needed 5 days)
• bookletimposer (- to 0.3.1-4)
  • Migration status for bookletimposer (- to 0.3.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bookletimposer would introduce bugs in testing: #1029733
    • autopkgtest for bookletimposer/0.3.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 ♻
    • Depends: bookletimposer pypdf2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bookletimposer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 217 days old (needed 5 days)
• diaspora-installer (- to 0.7.18.2+debian4)
  • Migration status for diaspora-installer (- to 0.7.18.2+debian4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating diaspora-installer would introduce bugs in testing: #1071624
    • autopkgtest for diaspora-installer/0.7.18.2+debian4: amd64: Regression or new test ♻, arm64: 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/diaspora-installer.html
    • 217 days old (needed 5 days)
• reprozip (- to 1.3-2)
  • Migration status for reprozip (- to 1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating reprozip would introduce bugs in testing: #1075445
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/reprozip.html
    • autopkgtest for reprozip/1.3-2: amd64: Pass, i386: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 217 days old (needed 2 days)
• budgie-extras (- to 1.8.0-1)
  • Migration status for budgie-extras (- to 1.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): budgie-extras budgie-desktop (not considered)
    • Depends: budgie-extras budgie-desktop (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/budgie-extras.html
    • autopkgtest for budgie-extras/1.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
    • 218 days old (needed 2 days)
• ruby-premailer (- to 1.22.0-1)
  • Migration status for ruby-premailer (- to 1.22.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.22.0-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/r/ruby-premailer.html
    • 218 days old (needed 5 days)
• aubio (- to 0.4.9-4.4)
  • Migration status for aubio (- to 0.4.9-4.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aubio would introduce bugs in testing: #1072399, #1074827
    • Impossible Depends: aubio -> libavformat-extra60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: aubio -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: aubio -> libavformat60/7:6.1.1-5+b1/armhf
    • Impossible Depends: aubio -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: aubio -> libavformat60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: aubio -> libavformat60/7:6.1.1-5+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aubio.html
    • autopkgtest for aubio/0.4.9-4.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
    • 220 days old (needed 2 days)
• gnunet-fuse (- to 0.20.0-3)
  • Migration status for gnunet-fuse (- to 0.20.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gnunet-fuse gnunet (not considered)
    • Depends: gnunet-fuse gnunet (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnunet-fuse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 220 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
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 220 days old (needed 2 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 ♻
    • 221 days old (needed 5 days)
• rust-sqlx-mysql (- to 0.7.3-1)
  • Migration status for rust-sqlx-mysql (- to 0.7.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-sqlx-mysql rust-rsa (not considered)
    • Depends: rust-sqlx-mysql rust-rsa (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-mysql.html
    • autopkgtest for rust-sqlx-mysql/0.7.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
    • 221 days old (needed 2 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
    • autopkgtest for abinit/9.10.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/a/abinit.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 222 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/s390x has unsatisfiable dependency
    • Updating giada would introduce bugs in testing: #1073997
    • Build-Depends(-Arch): giada juce (not considered)
    • Built-Using: giada juce (not considered)
  • Additional info:
    • Piuparts tested OK - 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 s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 222 days old (needed 5 days)
• kylin-process-manager (- to 4.0.0.0-1)
  • Migration status for kylin-process-manager (- to 4.0.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kylin-process-manager-daemon/amd64 has unsatisfiable dependency
    • kylin-process-manager-daemon/arm64 has unsatisfiable dependency
    • kylin-process-manager-daemon/armel has unsatisfiable dependency
    • kylin-process-manager-daemon/armhf has unsatisfiable dependency
    • kylin-process-manager-daemon/mips64el has unsatisfiable dependency
    • kylin-process-manager-daemon/ppc64el has unsatisfiable dependency
    • kylin-process-manager-daemon/s390x has unsatisfiable dependency
    • Updating kylin-process-manager would introduce bugs in testing: #1063399, #1073777
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/kylin-process-manager.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 s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 223 days old (needed 5 days)
• pidgin-skype (- to 20240122+gitab786a3+dfsg-2)
  • Migration status for pidgin-skype (- to 20240122+gitab786a3+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pidgin-skype telepathy-haze (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pidgin-skype.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 223 days old (needed 5 days)
• ruby-asana (- to 0.10.13-2)
  • Migration status for ruby-asana (- to 0.10.13-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-asana would introduce bugs in testing: #1068391
    • Build-Depends(-Arch): ruby-asana ruby-faraday-middleware (not considered)
    • Build-Depends(-Arch): ruby-asana ruby-faraday-middleware-multi-json (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-asana.html
    • autopkgtest for ruby-asana/0.10.13-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 ♻
    • 223 days old (needed 5 days)
• dials (- to 3.17.0+dfsg3-3)
  • Migration status for dials (- to 3.17.0+dfsg3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dials libccp4 (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): dials cctbx (not considered)
    • Depends: dials cctbx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dials.html
    • autopkgtest for dials/3.17.0+dfsg3-3: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 224 days old (needed 2 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 ♻
    • 224 days old (needed 5 days)
• mystic (- to 0.4.2-1)
  • Migration status for mystic (- to 0.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mystic would introduce bugs in testing: #1066046
    • autopkgtest for mystic/0.4.2-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/m/mystic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 225 days old (needed 5 days)
• atlas (- to 3.10.3-14)
  • Migration status for atlas (- to 3.10.3-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating atlas would introduce bugs in testing: #1066361, #1070013
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/atlas.html
    • 227 days old (needed 5 days)
• ruby3.2 (- to 3.2.3-1)
  • Migration status for ruby3.2 (- to 3.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby3.2 would introduce bugs in testing: #1064685, #1067069, #1069968, #1075923
    • autopkgtest for ruby3.2/3.2.3-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Impossible Depends: ruby3.2 -> libssl3/3.0.14-1~deb12u2/armhf
    • Impossible Depends: ruby3.2 -> libssl3/3.1.5-1/armel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby3.2.html
    • 227 days old (needed 5 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 ♻
    • 229 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 ♻
    • 231 days old (needed 5 days)
• bup (- to 0.33.3-1)
  • Migration status for bup (- to 0.33.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bup would introduce bugs in testing: #1074858
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bup.html
    • Reproducible on armhf - info ♻
    • 231 days old (needed 5 days)
• r-cran-gbm (- to 2.1.9-1)
  • Migration status for r-cran-gbm (- to 2.1.9-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.1.9-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 ♻
    • 231 days old (needed 5 days)
• 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
    • 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 s390x (which is allowed), not running autopkgtest there
    • 231 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 ♻
    • 232 days old (needed 5 days)
• promod3 (- to 3.4.0+ds-1)
  • Migration status for promod3 (- to 3.4.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • promod3/arm64 has unsatisfiable dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/promod3.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 233 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:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-redhopper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 233 days old (needed 5 days)
• rust-reqsign (- to 0.14.6-1)
  • Migration status for rust-reqsign (- to 0.14.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-reqsign rust-rsa (not considered)
    • Depends: rust-reqsign rust-rsa (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-reqsign.html
    • autopkgtest for rust-reqsign/0.14.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 ♻
    • 233 days old (needed 5 days)
• plaso (- to 20201007-3)
  • Migration status for plaso (- to 20201007-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): plaso dfwinreg (not considered)
    • Depends: plaso dfwinreg (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): plaso dfvfs (not considered)
    • Depends: plaso dfvfs (not considered)
  • 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 ♻
    • 235 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
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 236 days old (needed 2 days)
• libdata-find-perl (- to 0.03-2)
  • Migration status for libdata-find-perl (- to 0.03-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by frankie, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdata-find-perl.html
    • autopkgtest for libdata-find-perl/0.03-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)
• libgeo-wkt-simple-perl (- to 0.05-1)
  • Migration status for libgeo-wkt-simple-perl (- to 0.05-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by frankie, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgeo-wkt-simple-perl.html
    • autopkgtest for libgeo-wkt-simple-perl/0.05-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
    • 236 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/s390x has unsatisfiable dependency
    • Updating mlpy would introduce bugs in testing: #1075279
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/m/mlpy.html
    • autopkgtest for mlpy/3.5.0+ds-3: riscv64: No tests, superficial or marked flaky ♻
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 236 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:
    • Piuparts tested OK - 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 ♻
    • 236 days old (needed 5 days)
• pyfftw (- to 0.13.1-2)
  • Migration status for pyfftw (- to 0.13.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyfftw would introduce bugs in testing: #1071810
    • autopkgtest for pyfftw/0.13.1-2: 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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfftw.html
    • 236 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
    • Build-Depends(-Arch): python-refurb fastapi (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-refurb.html
    • autopkgtest for python-refurb/1.27.0-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
    • 236 days old (needed 2 days)
• videotrans (- to 1.6.1-9)
  • Migration status for videotrans (- to 1.6.1-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: videotrans mplayer (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/videotrans.html
    • autopkgtest for videotrans/1.6.1-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 236 days old (needed 2 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
    • Reproducible on armhf - info ♻
    • 238 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 arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 238 days old (needed 5 days)
• opennds (- to 10.2.0+dfsg-1)
  • Migration status for opennds (- to 10.2.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opennds would introduce bugs in testing: #1073664
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opennds.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 238 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
    • 238 days old (needed 5 days)
• python-pamqp (- to 3.3.0-1)
  • Migration status for python-pamqp (- to 3.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-pamqp/3.3.0-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/p/python-pamqp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 238 days old (needed 5 days)
• ring (- to 20231201.0~ds1-1)
  • Migration status for ring (- to 20231201.0~ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • jami/amd64 has unsatisfiable dependency
    • jami/arm64 has unsatisfiable dependency
    • jami/armel has unsatisfiable dependency
    • jami/armhf has unsatisfiable dependency
    • jami/i386 has unsatisfiable dependency
    • jami/mips64el has unsatisfiable dependency
    • jami/ppc64el has unsatisfiable dependency
    • Updating ring would introduce bugs in testing: #1072450, #1073942
    • autopkgtest for ring/20231201.0~ds1-1: riscv64: Regression or new test ♻, s390x: Pass
    • Impossible Depends: ring -> libavdevice60/7:6.1.1-5+b1/amd64
    • Impossible Depends: ring -> libavdevice60/7:6.1.1-5+b1/arm64
    • Impossible Depends: ring -> libavdevice60/7:6.1.1-5+b1/armel
    • Impossible Depends: ring -> libavdevice60/7:6.1.1-5+b1/armhf
    • Impossible Depends: ring -> libavdevice60/7:6.1.1-5+b1/i386
    • Impossible Depends: ring -> libavdevice60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: ring -> libavdevice60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: ring -> libavdevice60/7:6.1.1-5+b1/s390x
    • Impossible Depends: ring -> libavfilter-extra9/7:6.1.1-5+b1/mips64el
    • Impossible Depends: ring -> libavfilter9/7:6.1.1-5+b1/amd64
    • Impossible Depends: ring -> libavfilter9/7:6.1.1-5+b1/arm64
    • Impossible Depends: ring -> libavfilter9/7:6.1.1-5+b1/armel
    • Impossible Depends: ring -> libavfilter9/7:6.1.1-5+b1/armhf
    • Impossible Depends: ring -> libavfilter9/7:6.1.1-5+b1/i386
    • Impossible Depends: ring -> libavfilter9/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: ring -> libavfilter9/7:6.1.1-5+b1/s390x
    • Impossible Depends: ring -> libavformat-extra60/7:6.1.1-5+b1/armhf
    • Impossible Depends: ring -> libavformat-extra60/7:6.1.1-5+b1/i386
    • Impossible Depends: ring -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: ring -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: ring -> libavformat60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: ring -> libavformat60/7:6.1.1-5+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ring.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch 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
    • 238 days old (needed 5 days)
• python-molotov (- to 2.7-1)
  • Migration status for python-molotov (- to 2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-molotov/2.7-1: 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 ♻
    • 239 days old (needed 5 days)
• golang-github-sassoftware-go-rpmutils (- to 0.2.0-1)
  • Migration status for golang-github-sassoftware-go-rpmutils (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-sassoftware-go-rpmutils.html
    • autopkgtest for golang-github-sassoftware-go-rpmutils/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
    • 241 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 ♻
    • 241 days old (needed 5 days)
• gcalcli (- to 4.3.0-2)
  • Migration status for gcalcli (- 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: gcalcli python-oauth2client (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcalcli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 242 days old (needed 5 days)
• wmxmms2 (- to 0.6+repack-4)
  • Migration status for wmxmms2 (- to 0.6+repack-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): wmxmms2 xmms2 (not considered)
    • Depends: wmxmms2 xmms2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wmxmms2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 243 days old (needed 5 days)
• compyle (- to 0.8.1-8)
  • Migration status for compyle (- to 0.8.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating compyle would introduce bugs in testing: #1067301
    • autopkgtest for compyle/0.8.1-8: 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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/compyle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 244 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
    • 244 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ostree-push.html
    • autopkgtest for ostree-push/1.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
    • 244 days old (needed 2 days)
• python-sparse (- to 0.15.1-1)
  • Migration status for python-sparse (- to 0.15.1-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.15.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 ♻
    • Build-Depends(-Arch): python-sparse numba (not considered)
    • Depends: python-sparse numba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sparse.html
    • 244 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
    • Reproducible on armhf - info ♻
    • 245 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
    • Reproducible on armhf - info ♻
    • 245 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 ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • autopkgtest for python-aiortc/blocked-on-ci-infra: amd64: Regression or new test ♻
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 245 days old (needed 5 days)
• gssproxy (- to 0.9.2-2)
  • Migration status for gssproxy (- to 0.9.2-2): 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-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
    • 246 days old (needed 2 days)
• rust-transmission-client (- to 0.1.4-1)
  • Migration status for rust-transmission-client (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-transmission-client-dev/amd64 has unsatisfiable dependency
    • librust-transmission-client-dev/arm64 has unsatisfiable dependency
    • librust-transmission-client-dev/armel has unsatisfiable dependency
    • librust-transmission-client-dev/armhf has unsatisfiable dependency
    • librust-transmission-client-dev/i386 has unsatisfiable dependency
    • librust-transmission-client-dev/mips64el has unsatisfiable dependency
    • librust-transmission-client-dev/ppc64el has unsatisfiable dependency
    • librust-transmission-client-dev/s390x has unsatisfiable dependency
    • Updating rust-transmission-client would introduce bugs in testing: #1071892
    • rust-transmission-client unsatisfiable Build-Depends(-Arch) on amd64: librust-isahc-1+default-dev (>= 1.3-~~)
    • rust-transmission-client unsatisfiable Build-Depends(-Arch) on arm64: librust-isahc-1+default-dev (>= 1.3-~~)
    • rust-transmission-client unsatisfiable Build-Depends(-Arch) on armel: librust-isahc-1+default-dev (>= 1.3-~~)
    • rust-transmission-client unsatisfiable Build-Depends(-Arch) on armhf: librust-isahc-1+default-dev (>= 1.3-~~)
    • rust-transmission-client unsatisfiable Build-Depends(-Arch) on i386: librust-isahc-1+default-dev (>= 1.3-~~)
    • rust-transmission-client unsatisfiable Build-Depends(-Arch) on mips64el: librust-isahc-1+default-dev (>= 1.3-~~)
    • rust-transmission-client unsatisfiable Build-Depends(-Arch) on ppc64el: librust-isahc-1+default-dev (>= 1.3-~~)
    • rust-transmission-client unsatisfiable Build-Depends(-Arch) on riscv64: librust-isahc-1+default-dev (>= 1.3-~~)
    • rust-transmission-client unsatisfiable Build-Depends(-Arch) on s390x: librust-isahc-1+default-dev (>= 1.3-~~)
    • autopkgtest for rust-transmission-client/0.1.4-1: riscv64: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-transmission-client.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 246 days old (needed 5 days)
• kiwi (- to 9.25.22-1)
  • Migration status for kiwi (- to 9.25.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kiwi would introduce bugs in testing: #1069389
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kiwi.html
    • 247 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:
    • Updating python-cramjam would introduce bugs in testing: #1061310
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cramjam.html
    • autopkgtest for python-cramjam/2.7.0.1+ds1-2: amd64: Pass, arm64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 248 days old (needed 2 days)
• r-cran-lwgeom (- to 0.2-13-3)
  • Migration status for r-cran-lwgeom (- to 0.2-13-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-lwgeom r-cran-sf (not considered)
    • Depends: r-cran-lwgeom r-cran-sf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-lwgeom.html
    • autopkgtest for r-cran-lwgeom/0.2-13-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
    • 248 days old (needed 2 days)
• mailman-hyperkitty (- to 1.2.1-2)
  • Migration status for mailman-hyperkitty (- to 1.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): mailman-hyperkitty mailman3 (not considered)
    • Depends: mailman-hyperkitty mailman3 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailman-hyperkitty.html
    • autopkgtest for mailman-hyperkitty/1.2.1-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
    • 249 days old (needed 2 days)
• pysph (- to 1.0~b1-8)
  • Migration status for pysph (- to 1.0~b1-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pysph compyle (not considered)
    • Depends: pysph compyle (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysph.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for pysph/1.0~b1-8: amd64: Pass, arm64: Pass
    • 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
    • 250 days old (needed 2 days)
• rally (- to 3.3.0-4)
  • Migration status for rally (- to 3.3.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rally would introduce bugs in testing: #1076916
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rally.html
    • autopkgtest for rally/3.3.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 ♻
    • Reproducible on armhf - info ♻
    • 250 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-loompy numba (not considered)
    • Depends: python-loompy numba (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-loompy.html
    • autopkgtest for python-loompy/3.0.7+dfsg-3: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 251 days old (needed 2 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
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/a/apt-verify.html
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 252 days old (needed 5 days)
• haskell-misfortune (- to 0.1.2.1-3)
  • Migration status for haskell-misfortune (- to 0.1.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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)
    • Depends: haskell-misfortune pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-misfortune.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 252 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
    • autopkgtest for codraft/2.2.1-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/codraft.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 253 days old (needed 5 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: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): intake entrypoints (not considered)
    • Depends: intake entrypoints (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intake.html
    • 253 days old (needed 5 days)
• python-pattern (- to 2.6+git20180818-4.1)
  • Migration status for python-pattern (- to 2.6+git20180818-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-pattern wordnet (not considered)
    • Depends: python-pattern wordnet (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pattern.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 254 days old (needed 5 days)
• ruby-deb-version (- to 1.0.2-1)
  • Migration status for ruby-deb-version (- to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-deb-version.html
    • autopkgtest for ruby-deb-version/1.0.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 255 days old (needed 5 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
    • 256 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
    • 258 days old (needed 5 days)
• courier (- to 1.0.16-3.2)
  • Migration status for courier (- to 1.0.16-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • courier-base/armel has unsatisfiable dependency
    • courier-imap/armel has unsatisfiable dependency
    • courier-mlm/armel has unsatisfiable dependency
    • courier-mta/armel has unsatisfiable dependency
    • sqwebmail/armel has unsatisfiable dependency
    • courier-base/armhf has unsatisfiable dependency
    • courier-imap/armhf has unsatisfiable dependency
    • courier-mlm/armhf has unsatisfiable dependency
    • courier-mta/armhf has unsatisfiable dependency
    • sqwebmail/armhf has unsatisfiable dependency
    • Updating courier would introduce bugs in testing: #1000053, #1069307
    • autopkgtest for courier/1.0.16-3.2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): courier courier-authlib (not considered)
    • Build-Depends(-Arch): courier mgetty (not considered)
    • Build-Depends(-Arch): courier pcre3 (not considered)
    • Depends: courier courier-authlib (not considered)
    • Depends: courier maildrop (not considered)
    • Depends: courier mgetty (not considered)
    • Depends: courier pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 258 days old (needed 5 days)
• devicexlib (- to 0.8.2-1)
  • Migration status for devicexlib (- to 0.8.2-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 ♻
    • 259 days old (needed 5 days)
• lapackpp (- to 2023.11.05-1)
  • Migration status for lapackpp (- to 2023.11.05-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 armhf - info ♻
    • 259 days old (needed 5 days)
• libgridxc (- to 2.0.1-1)
  • Migration status for libgridxc (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgridxc would introduce bugs in testing: #1055110
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgridxc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 259 days old (needed 5 days)
• heaptrack (- to 1.5.0+dfsg1-2)
  • Migration status for heaptrack (- to 1.5.0+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating heaptrack would introduce bugs in testing: #1075065
    • autopkgtest for heaptrack/1.5.0+dfsg1-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/h/heaptrack.html
    • Reproducible on armhf - info ♻
    • 260 days old (needed 5 days)
• warzone2100 (- to 4.4.2-1)
  • Migration status for warzone2100 (- to 4.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating warzone2100 would introduce bugs in testing: #1075631
    • Impossible Depends: warzone2100 -> libminiupnpc17/2.2.6-1+b1/amd64
    • Impossible Depends: warzone2100 -> libminiupnpc17/2.2.6-1+b1/arm64
    • Impossible Depends: warzone2100 -> libminiupnpc17/2.2.6-1+b1/armel
    • Impossible Depends: warzone2100 -> libminiupnpc17/2.2.6-1+b1/armhf
    • Impossible Depends: warzone2100 -> libminiupnpc17/2.2.6-1+b1/i386
    • Impossible Depends: warzone2100 -> libminiupnpc17/2.2.6-1+b1/mips64el
    • Impossible Depends: warzone2100 -> libminiupnpc17/2.2.6-1+b1/ppc64el
    • Impossible Depends: warzone2100 -> libminiupnpc17/2.2.6-1+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/warzone2100.html
    • 260 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:
    • Updating casparcg-server would introduce bugs in testing: #1077504
    • Impossible Depends: casparcg-server -> libavdevice60/7:6.1.1-5+b1/amd64
    • Impossible Depends: casparcg-server -> libavdevice60/7:6.1.1-5+b1/arm64
    • Impossible Depends: casparcg-server -> libavfilter-extra9/7:6.1.1-5+b1/arm64
    • Impossible Depends: casparcg-server -> libavfilter9/7:6.1.1-5+b1/amd64
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 263 days old (needed 5 days)
• ruby-arr-pm (- to 0.0.12-1)
  • Migration status for ruby-arr-pm (- to 0.0.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): ruby-arr-pm ruby-flores (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-arr-pm.html
    • autopkgtest for ruby-arr-pm/0.0.12-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 265 days old (needed 2 days)
• ruby-flores (- to 0.0.8-1)
  • Migration status for ruby-flores (- to 0.0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-flores.html
    • autopkgtest for ruby-flores/0.0.8-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 265 days old (needed 2 days)
• golang-github-henrybear327-go-proton-api (- to 1.0.0-3)
  • Migration status for golang-github-henrybear327-go-proton-api (- to 1.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-henrybear327-go-proton-api would introduce bugs in testing: #1075766
    • autopkgtest for golang-github-henrybear327-go-proton-api/1.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 ♻
    • 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
    • 266 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
    • 266 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 ♻
    • 266 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
    • 267 days old (needed 5 days)
• ohcount (- to 4.0.0-4)
  • Migration status for ohcount (- to 4.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ohcount would introduce bugs in testing: #1051900, #1079834
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ohcount.html
    • 267 days old (needed 5 days)
• nitime (- to 0.10.2-2)
  • Migration status for nitime (- to 0.10.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nitime/0.10.2-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, 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/n/nitime.html
    • New but not reproducible on amd64 - info ♻
    • 268 days old (needed 5 days)
• rust-heed (- to 0.20.0~alpha.9-1)
  • Migration status for rust-heed (- to 0.20.0~alpha.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-heed/0.20.0~alpha.9-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-heed.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 269 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)
    • 270 days old (needed 5 days)
• ifplugd (- to 0.28-19.7)
  • Migration status for ifplugd (- to 0.28-19.7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ifplugd would introduce bugs in testing: #1057784
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ifplugd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 270 days old (needed 5 days)
• r-cran-wgcna (- to 1.72-5-1)
  • Migration status for r-cran-wgcna (- to 1.72-5-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-wgcna.html
    • autopkgtest for r-cran-wgcna/1.72-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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 270 days old (needed 2 days)
• snippy (- to 4.6.0+dfsg-4)
  • Migration status for snippy (- to 4.6.0+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): snippy freebayes (not considered)
    • Depends: snippy freebayes (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • 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-4: 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 ♻
    • 270 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
    • 270 days old (needed 5 days)
• xraylarch (- to 0.9.74+ds1-1)
  • Migration status for xraylarch (- to 0.9.74+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xraylarch would introduce bugs in testing: #1071898
    • Build-Depends(-Arch): xraylarch python-mp-api (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.74+ds1-1: amd64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 270 days old (needed 2 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: #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 ♻
    • Reproducible on armhf - info ♻
    • 274 days old (needed 5 days)
• python-proboscis (- to 1.2.6.0-8)
  • Migration status for python-proboscis (- to 1.2.6.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-proboscis would introduce bugs in testing: #1071922
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-proboscis.html
    • autopkgtest for python-proboscis/1.2.6.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 ♻
    • 275 days old (needed 5 days)
• pytorch-sparse (- to 0.6.18-2)
  • Migration status for pytorch-sparse (- to 0.6.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-torch-sparse/amd64 has unsatisfiable dependency
    • python3-torch-sparse/arm64 has unsatisfiable dependency
    • python3-torch-sparse/ppc64el has unsatisfiable dependency
    • python3-torch-sparse/s390x has unsatisfiable dependency
    • Updating pytorch-sparse would introduce bugs in testing: #1081097
    • Build-Depends(-Arch): pytorch-sparse pytorch (not considered)
    • Build-Depends(-Arch): pytorch-sparse pytorch-scatter (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pytorch-sparse.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 ♻
    • 275 days old (needed 5 days)
• fapolicyd (- to 1.3.2+20231212+git973a86d1b4-1)
  • Migration status for fapolicyd (- to 1.3.2+20231212+git973a86d1b4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fapolicyd would introduce bugs in testing: #1037547, #1073690
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fapolicyd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 276 days old (needed 5 days)
• pytorch-scatter (- to 2.1.2-1)
  • Migration status for pytorch-scatter (- to 2.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-torch-scatter/amd64 has unsatisfiable dependency
    • python3-torch-scatter/arm64 has unsatisfiable dependency
    • python3-torch-scatter/ppc64el has unsatisfiable dependency
    • python3-torch-scatter/s390x has unsatisfiable dependency
    • Updating pytorch-scatter would introduce bugs in testing: #1081096
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pytorch-scatter.html
    • Build-Depends(-Arch): pytorch-scatter pytorch (not considered)
  • 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
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 276 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
    • 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 277 days old (needed 5 days)
• python-epimodels (- to 0.4.0-2)
  • Migration status for python-epimodels (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-epimodels/0.4.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): python-epimodels numba (not considered)
    • Depends: python-epimodels numba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-epimodels.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 277 days old (needed 5 days)
• pytorch-cluster (- to 1.6.3-1)
  • Migration status for pytorch-cluster (- to 1.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-torch-cluster/amd64 has unsatisfiable dependency
    • python3-torch-cluster/arm64 has unsatisfiable dependency
    • python3-torch-cluster/ppc64el has unsatisfiable dependency
    • python3-torch-cluster/s390x has unsatisfiable dependency
    • Updating pytorch-cluster would introduce bugs in testing: #1081094
    • Build-Depends(-Arch): pytorch-cluster pytorch (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pytorch-cluster.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 ♻
    • 277 days old (needed 5 days)
• pandoc-sidenote (- to 0.23.0-1)
  • Migration status for pandoc-sidenote (- to 0.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pandoc-sidenote would introduce bugs in testing: #1055980
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pandoc-sidenote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 278 days old (needed 5 days)
• gitit (- to 0.15.1.1+dfsg-1)
  • Migration status for gitit (- to 0.15.1.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): 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 ♻
    • 279 days old (needed 5 days)
• liquidctl (- to 1.13.0-2)
  • Migration status for liquidctl (- to 1.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liquidctl would introduce bugs in testing: #1064743
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/liquidctl.html
    • 279 days old (needed 5 days)
• pppconfig (- to 2.3.28)
  • Migration status for pppconfig (- to 2.3.28): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pppconfig would introduce bugs in testing: #1072606
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pppconfig.html
    • Reproducible on armhf - info ♻
    • 279 days old (needed 5 days)
• scanbd (- to 1.5.1-7)
  • Migration status for scanbd (- to 1.5.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scanbd would introduce bugs in testing: #1058749
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scanbd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 279 days old (needed 5 days)
• 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-har-validator.html
    • 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: 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 ♻
    • 282 days old (needed 5 days)
• mosdepth (- to 0.3.6+ds-1)
  • Migration status for mosdepth (- to 0.3.6+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mosdepth would introduce bugs in testing: #1075288
    • Build-Depends(-Arch): mosdepth nim (not considered)
    • Build-Depends(-Arch): mosdepth nim-docopt (not considered)
    • Build-Depends(-Arch): mosdepth nim-hts (not considered)
    • 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.6+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 armhf - info ♻
    • 283 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 ♻
    • 284 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
    • Build-Depends(-Arch): python-array-api-compat pytorch (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-array-api-compat.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 ♻
    • 284 days old (needed 5 days)
• amiga-fdisk (- to 0.04-17)
  • Migration status for amiga-fdisk (- to 0.04-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating amiga-fdisk would introduce bugs in testing: #1074807
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amiga-fdisk.html
    • Reproducible on armhf - info ♻
    • 285 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 ♻
    • 285 days old (needed 5 days)
• circlator (- to 1.5.6-11)
  • Migration status for circlator (- to 1.5.6-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): circlator canu (not considered)
    • Depends: circlator canu (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/circlator.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for circlator/1.5.6-11: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: 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
    • 286 days old (needed 2 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:
    • Updating comskip would introduce bugs in testing: #1072406
    • Impossible Depends: comskip -> libavformat-extra60/7:6.1.1-5+b1/armhf
    • Impossible Depends: comskip -> libavformat-extra60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: comskip -> libavformat-extra60/7:6.1.1-5+b1/s390x
    • Impossible Depends: comskip -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: comskip -> libavformat60/7:6.1.1-5+b1/armhf
    • Impossible Depends: comskip -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: comskip -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: comskip -> libavformat60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: comskip -> libavformat60/7:6.1.1-5+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/comskip.html
    • Reproducible on armhf - info ♻
    • 286 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 ♻
    • Reproducible on armhf - info ♻
    • 286 days old (needed 5 days)
• openmolcas (- to 23.10-1)
  • Migration status for openmolcas (- to 23.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for openmolcas/23.10-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmolcas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 286 days old (needed 5 days)
• ruby-tioga (- to 1.19.1-5)
  • Migration status for ruby-tioga (- to 1.19.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-tioga would introduce bugs in testing: #1075479
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-tioga.html
    • Reproducible on armhf - info ♻
    • 287 days old (needed 5 days)
• python-html-sanitizer (- to 2.2-1)
  • Migration status for python-html-sanitizer (- to 2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-html-sanitizer would introduce bugs in testing: #1008366, #1070710, #1071455, #1080054
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-html-sanitizer.html
    • autopkgtest for python-html-sanitizer/2.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 292 days old (needed 5 days)
• r-cran-spatialreg (- to 1.3-1+dfsg-1)
  • Migration status for r-cran-spatialreg (- to 1.3-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): r-cran-spatialreg r-cran-sf (not considered)
    • Depends: r-cran-spatialreg r-cran-sf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-spatialreg r-cran-spdep
    • Depends: r-cran-spatialreg r-cran-spdep
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatialreg.html
    • autopkgtest for r-cran-spatialreg/1.3-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
    • 292 days old (needed 2 days)
• simple-whip-server (- to 0.0~git20231003-1)
  • Migration status for simple-whip-server (- to 0.0~git20231003-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 ♻
    • 292 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:
    • Updating recutils would introduce bugs in testing: #1066370
    • Impossible Depends: recutils -> libreadline8/8.2-3+b1/armel
    • Impossible Depends: recutils -> libreadline8/8.2-3+b1/armhf
    • Depends: recutils curl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/recutils.html
    • 293 days old (needed 5 days)
• flask-wtf (- to 1.2.1-1)
  • Migration status for flask-wtf (- to 1.2.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
    • autopkgtest for flask-wtf/1.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for flask-wtf/n/a: riscv64: Regression or new test ♻
    • Build-Depends(-Arch): flask-wtf flask-babel (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-wtf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 294 days old (needed 5 days)
    • Remove hint for (transitive) dependency: flask-wtf
• 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/s390x has unsatisfiable dependency
    • Updating mysql-workbench would introduce bugs in testing: #1000093, #1074563
    • Build-Depends(-Arch): mysql-workbench pcre3 (not considered)
  • 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 s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 295 days old (needed 5 days)
• rust-datasize (- to 0.2.13-1)
  • Migration status for rust-datasize (- to 0.2.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-datasize/0.2.13-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-datasize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 295 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 ♻
    • 295 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: 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-wikibase-cli.html
    • 296 days old (needed 5 days)
• bespokesynth (- to 1.2.1+dfsg-4)
  • Migration status for bespokesynth (- to 1.2.1+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bespokesynth/mips64el has unsatisfiable dependency
    • Build-Depends(-Arch): bespokesynth juce (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bespokesynth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 297 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 ♻
    • 298 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
    • Reproducible on armhf - info ♻
    • 298 days old (needed 5 days)
• ruby-rspec-parameterized-core (- to 1.0.0-1)
  • Migration status for ruby-rspec-parameterized-core (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kanashiro, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized-core.html
    • autopkgtest for ruby-rspec-parameterized-core/1.0.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 299 days old (needed 5 days)
• ruby-rspec-parameterized-table-syntax (- to 1.0.1-1)
  • Migration status for ruby-rspec-parameterized-table-syntax (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kanashiro, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core (not considered)
    • Depends: ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized-table-syntax.html
    • autopkgtest for ruby-rspec-parameterized-table-syntax/1.0.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 299 days old (needed 5 days)
• geany-plugins (- to 2.0-4)
  • Migration status for geany-plugins (- to 2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • geany-plugin-markdown/amd64 has unsatisfiable dependency
    • geany-plugin-webhelper/amd64 has unsatisfiable dependency
    • geany-plugin-markdown/arm64 has unsatisfiable dependency
    • geany-plugin-webhelper/arm64 has unsatisfiable dependency
    • geany-plugin-markdown/armel has unsatisfiable dependency
    • geany-plugin-webhelper/armel has unsatisfiable dependency
    • geany-plugin-markdown/armhf has unsatisfiable dependency
    • geany-plugin-webhelper/armhf has unsatisfiable dependency
    • geany-plugin-markdown/i386 has unsatisfiable dependency
    • geany-plugin-webhelper/i386 has unsatisfiable dependency
    • geany-plugin-markdown/mips64el has unsatisfiable dependency
    • geany-plugin-webhelper/mips64el has unsatisfiable dependency
    • geany-plugin-markdown/ppc64el has unsatisfiable dependency
    • geany-plugin-webhelper/ppc64el has unsatisfiable dependency
    • geany-plugin-markdown/s390x has unsatisfiable dependency
    • geany-plugin-webhelper/s390x has unsatisfiable dependency
    • Updating geany-plugins would introduce bugs in testing: #1061406
    • geany-plugins unsatisfiable Build-Depends(-Arch) on amd64: libwebkit2gtk-4.0-dev
    • geany-plugins unsatisfiable Build-Depends(-Arch) on arm64: libwebkit2gtk-4.0-dev
    • geany-plugins unsatisfiable Build-Depends(-Arch) on armel: libwebkit2gtk-4.0-dev
    • geany-plugins unsatisfiable Build-Depends(-Arch) on armhf: libwebkit2gtk-4.0-dev
    • geany-plugins unsatisfiable Build-Depends(-Arch) on i386: libwebkit2gtk-4.0-dev
    • geany-plugins unsatisfiable Build-Depends(-Arch) on mips64el: libwebkit2gtk-4.0-dev
    • geany-plugins unsatisfiable Build-Depends(-Arch) on ppc64el: libwebkit2gtk-4.0-dev
    • geany-plugins unsatisfiable Build-Depends(-Arch) on riscv64: libwebkit2gtk-4.0-dev
    • geany-plugins unsatisfiable Build-Depends(-Arch) on s390x: libwebkit2gtk-4.0-dev
    • Build-Depends(-Arch): geany-plugins ctpl (not considered)
    • Depends: geany-plugins ctpl (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/geany-plugins.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 ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 301 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 ♻
    • 302 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 ♻, riscv64: 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 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 ♻
    • 303 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
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/y/ypy.html
    • 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:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 303 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
    • autopkgtest for python-diagrams/0.23.4-1: riscv64: Regression or new test ♻
  • 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 s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 305 days old (needed 5 days)
• cp2k (- to 2023.2-2)
  • Migration status for cp2k (- to 2023.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cp2k/armel has unsatisfiable dependency
    • cp2k/armhf has unsatisfiable dependency
    • cp2k/i386 has unsatisfiable dependency
    • Updating cp2k would introduce bugs in testing: #1060949
    • 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)
    • autopkgtest for cp2k/2023.2-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cp2k.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
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 306 days old (needed 5 days)
• gnome-video-trimmer (- to 0.8.2-2)
  • Migration status for gnome-video-trimmer (- to 0.8.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-video-trimmer would introduce bugs in testing: #1071874
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on amd64: librust-ashpd-0.6+gtk4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-0.18+log-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-0.18+log-macros-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk4-0.7-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on amd64: librust-libadwaita-0.5+v1-4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on arm64: librust-ashpd-0.6+gtk4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-0.18+log-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-0.18+log-macros-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk4-0.7-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on arm64: librust-libadwaita-0.5+v1-4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on armhf: librust-ashpd-0.6+gtk4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-0.18+log-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-0.18+log-macros-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk4-0.7-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on armhf: librust-libadwaita-0.5+v1-4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on i386: librust-ashpd-0.6+gtk4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on i386: librust-glib-0.18+log-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on i386: librust-glib-0.18+log-macros-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on i386: librust-gtk4-0.7-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on i386: librust-libadwaita-0.5+v1-4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on mips64el: librust-ashpd-0.6+gtk4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-0.18+log-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-0.18+log-macros-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk4-0.7-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on mips64el: librust-libadwaita-0.5+v1-4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-ashpd-0.6+gtk4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-0.18+log-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-0.18+log-macros-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk4-0.7-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on ppc64el: librust-libadwaita-0.5+v1-4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on riscv64: librust-ashpd-0.6+gtk4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on riscv64: librust-glib-0.18+log-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on riscv64: librust-glib-0.18+log-macros-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on riscv64: librust-gtk4-0.7-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on riscv64: librust-libadwaita-0.5+v1-4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on s390x: librust-ashpd-0.6+gtk4-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-0.18+log-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-0.18+log-macros-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk4-0.7-dev
    • gnome-video-trimmer unsatisfiable Build-Depends(-Arch) on s390x: librust-libadwaita-0.5+v1-4-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-video-trimmer.html
    • autopkgtest for gnome-video-trimmer/0.8.2-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 ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 307 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 ♻
    • 307 days old (needed 5 days)
• budgie-desktop-environment (- to 0.1.1-1)
  • Migration status for budgie-desktop-environment (- to 0.1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: budgie-desktop-environment budgie-desktop (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/budgie-desktop-environment.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 308 days old (needed 5 days)
• django-assets (- to 2.0-3)
  • Migration status for django-assets (- to 2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-assets would introduce bugs in testing: #1056243, #1056288
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-assets.html
    • 310 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
    • Build-Depends(-Arch): umap-learn numba (not considered)
    • Build-Depends(-Arch): umap-learn python-pynndescent
    • Depends: umap-learn numba (not considered)
    • Depends: umap-learn python-pynndescent
  • 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 s390x (which is allowed), not running autopkgtest there
    • autopkgtest for umap-learn/0.5.4+dfsg-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 310 days old (needed 5 days)
• lambdabot (- to 5.3.1.1-1)
  • Migration status for lambdabot (- to 5.3.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): 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 ♻
    • Reproducible on i386 - info ♻
    • 313 days old (needed 5 days)
• haskell-lambdabot-novelty-plugins (- to 5.3.1.1-1)
  • Migration status for haskell-lambdabot-novelty-plugins (- to 5.3.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): 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 ♻
    • 314 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
    • 314 days old (needed 5 days)
• agda-stdlib (- to 1.7.3-1)
  • Migration status for agda-stdlib (- to 1.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating agda-stdlib would introduce bugs in testing: #1076387
    • Build-Depends(-Arch): agda-stdlib agda
    • Depends: agda-stdlib agda
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/agda-stdlib.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 ♻
    • 315 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
    • Reproducible on armhf - info ♻
    • 315 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-distribution ruby-gsl (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-distribution.html
    • autopkgtest for ruby-distribution/0.8.0+dfsg-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
    • 317 days old (needed 2 days)
• rust-imperative (- to 1.0.5-1)
  • Migration status for rust-imperative (- to 1.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-imperative-dev/amd64 has unsatisfiable dependency
    • Updating rust-imperative would introduce bugs in testing: #1071889
    • rust-imperative unsatisfiable Build-Depends(-Arch) on amd64: librust-rust-stemmers-1+default-dev (>= 1.2.0-~~)
    • Not built on buildd: arch amd64 binaries uploaded by jelmer
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-imperative.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 319 days old (needed 5 days)
• raku-json-fast (- to 0.19-1)
  • Migration status for raku-json-fast (- to 0.19-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-json-fast dh-raku (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-json-fast.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 320 days old (needed 5 days)
• raku-json-marshal (- to 0.0.25-1)
  • Migration status for raku-json-marshal (- to 0.0.25-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-json-marshal dh-raku (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): raku-json-marshal raku-json-fast
    • Build-Depends(-Arch): raku-json-marshal raku-json-name
    • Build-Depends(-Arch): raku-json-marshal raku-json-optin
    • Depends: raku-json-marshal raku-json-fast
    • Depends: raku-json-marshal raku-json-name
    • Depends: raku-json-marshal raku-json-optin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-json-marshal.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 ♻
    • 320 days old (needed 5 days)
• raku-json-unmarshal (- to 0.15-1)
  • Migration status for raku-json-unmarshal (- to 0.15-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-json-unmarshal dh-raku (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): raku-json-unmarshal raku-json-fast
    • Build-Depends(-Arch): raku-json-unmarshal raku-json-name
    • Build-Depends(-Arch): raku-json-unmarshal raku-json-optin
    • Depends: raku-json-unmarshal raku-json-fast
    • Depends: raku-json-unmarshal raku-json-name
    • Depends: raku-json-unmarshal raku-json-optin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-json-unmarshal.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 320 days old (needed 5 days)
• wlcs (- to 1.6.1-1)
  • Migration status for wlcs (- to 1.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wlcs would introduce bugs in testing: #1075640
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wlcs.html
    • Reproducible on armhf - info ♻
    • 320 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
    • Reproducible on armhf - info ♻
    • 322 days old (needed 5 days)
• milter-greylist (- to 4.6.4-3)
  • Migration status for milter-greylist (- to 4.6.4-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): milter-greylist opendkim (not considered)
    • Depends: milter-greylist opendkim (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/milter-greylist.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 322 days old (needed 5 days)
• raku-getopt-long (- to 0.4.2-1)
  • Migration status for raku-getopt-long (- to 0.4.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-getopt-long dh-raku (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-getopt-long.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 ♻
    • 322 days old (needed 5 days)
• guerillabackup (- to 0.5.0-1)
  • Migration status for guerillabackup (- to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guerillabackup would introduce bugs in testing: #1073671
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guerillabackup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 323 days old (needed 5 days)
• haskell-hledger-web (- to 1.30-1)
  • Migration status for haskell-hledger-web (- to 1.30-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 ♻
    • 323 days old (needed 5 days)
• libpsml (- to 2.0.1-1)
  • Migration status for libpsml (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libpsml-dev/amd64 has unsatisfiable dependency
    • Updating libpsml would introduce bugs in testing: #1071043
    • libpsml unsatisfiable Build-Depends(-Arch) on amd64: libxmlf90-dev
    • Not built on buildd: arch amd64 binaries uploaded by mbanck
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libp/libpsml.html
    • uninstallable on arch amd64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 324 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 ♻
    • Reproducible on armhf - info ♻
    • 324 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: Pass, 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 ♻
    • 324 days old (needed 5 days)
• raku-file-find (- to 0.2.0-1)
  • Migration status for raku-file-find (- 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): raku-file-find dh-raku (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-file-find.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 324 days old (needed 5 days)
• haskell-hoauth2 (- to 2.8.0-1)
  • Migration status for haskell-hoauth2 (- to 2.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): 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 ♻
    • 325 days old (needed 5 days)
• orange-spectroscopy (- to 0.6.10-4)
  • Migration status for orange-spectroscopy (- to 0.6.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orange-spectroscopy/0.6.10-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Depends: orange-spectroscopy orange3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orange-spectroscopy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 325 days old (needed 5 days)
• rust-ruma-push-gateway-api (- to 0.6.0-1)
  • Migration status for rust-ruma-push-gateway-api (- to 0.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): rust-ruma-push-gateway-api rust-ruma-common (not considered)
    • Depends: rust-ruma-push-gateway-api rust-ruma-common (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ruma-push-gateway-api.html
    • autopkgtest for rust-ruma-push-gateway-api/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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 325 days old (needed 2 days)
• taffybar (- to 4.0.1-1)
  • Migration status for taffybar (- to 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): taffybar haskell-gtk-strut (not considered)
    • Build-Depends-Indep: taffybar haskell-gtk-strut (not considered)
    • Depends: taffybar haskell-gtk-strut (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends(-Arch): taffybar haskell-gi-gtk (not considered)
    • Build-Depends(-Arch): taffybar haskell-gi-gtk-hs (not considered)
    • Build-Depends(-Arch): taffybar haskell-gtk-sni-tray
    • Build-Depends-Indep: taffybar haskell-gi-gtk (not considered)
    • Build-Depends-Indep: taffybar haskell-gi-gtk-hs (not considered)
    • Build-Depends-Indep: taffybar haskell-gtk-sni-tray
    • Depends: taffybar haskell-gi-gtk (not considered)
    • Depends: taffybar haskell-gi-gtk-hs (not considered)
    • Depends: taffybar haskell-gtk-sni-tray
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/taffybar.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 ♻
    • 325 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
    • Reproducible on armhf - info ♻
    • 326 days old (needed 5 days)
• haskell-arithmoi (- to 0.12.1.0-2)
  • Migration status for haskell-arithmoi (- to 0.12.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-arithmoi haskell-integer-roots (not considered)
    • Build-Depends-Indep: haskell-arithmoi haskell-integer-roots (not considered)
    • Depends: haskell-arithmoi haskell-integer-roots (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-arithmoi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 326 days old (needed 5 days)
• haskell-cryptol (- to 3.0.0-1)
  • Migration status for haskell-cryptol (- to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armel: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on armhf: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on i386: libghc-arithmoi-prof
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-arithmoi-dev (>= 0.12)
    • haskell-cryptol unsatisfiable Build-Depends(-Arch) on s390x: libghc-arithmoi-prof
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-cryptol haskell-arithmoi
    • Build-Depends-Indep: haskell-cryptol haskell-arithmoi
    • Depends: haskell-cryptol haskell-arithmoi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cryptol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 326 days old (needed 5 days)
• haskell-dhall (- to 1.41.2-1)
  • Migration status for haskell-dhall (- to 1.41.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-dhall haskell-cborg (not considered)
    • Build-Depends(-Arch): haskell-dhall haskell-cborg-json (not considered)
    • Build-Depends(-Arch): haskell-dhall haskell-serialise (not considered)
    • Build-Depends-Indep: haskell-dhall haskell-cborg (not considered)
    • Build-Depends-Indep: haskell-dhall haskell-cborg-json (not considered)
    • Build-Depends-Indep: haskell-dhall haskell-serialise (not considered)
    • Depends: haskell-dhall haskell-cborg (not considered)
    • Depends: haskell-dhall haskell-cborg-json (not considered)
    • Depends: haskell-dhall haskell-serialise (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-dhall.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 326 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
    • 327 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 ♻
    • 327 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: Pass, arm64: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/canu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 329 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
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 329 days old (needed 2 days)
• rust-tikv-jemalloc-ctl (- to 0.5.4-1)
  • Migration status for rust-tikv-jemalloc-ctl (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-tikv-jemalloc-ctl/0.5.4-1: amd64: 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/r/rust-tikv-jemalloc-ctl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 330 days old (needed 5 days)
• orpie (- to 1.6.1-2)
  • Migration status for orpie (- to 1.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating orpie would introduce bugs in testing: #1073906
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orpie.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 332 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
    • 333 days old (needed 2 days)
• dh-raku (- to 0.16)
  • Migration status for dh-raku (- to 0.16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-raku.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 334 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• golang-github-jedisct1-go-hpke-compact (- to 0.9.2-1)
  • Migration status for golang-github-jedisct1-go-hpke-compact (- to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sergiodj@sergiodj.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jedisct1-go-hpke-compact.html
    • autopkgtest for golang-github-jedisct1-go-hpke-compact/0.9.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 334 days old (needed 2 days)
• haskell-gtk-sni-tray (- to 0.1.8.1-2)
  • Migration status for haskell-gtk-sni-tray (- to 0.1.8.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-gtk-sni-tray haskell-gtk-strut (not considered)
    • Build-Depends-Indep: haskell-gtk-sni-tray haskell-gtk-strut (not considered)
    • Depends: haskell-gtk-sni-tray haskell-gtk-strut (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends(-Arch): haskell-gtk-sni-tray haskell-gi-dbusmenugtk3 (not considered)
    • Build-Depends(-Arch): haskell-gtk-sni-tray haskell-gi-gtk (not considered)
    • Build-Depends-Indep: haskell-gtk-sni-tray haskell-gi-dbusmenugtk3 (not considered)
    • Build-Depends-Indep: haskell-gtk-sni-tray haskell-gi-gtk (not considered)
    • Depends: haskell-gtk-sni-tray haskell-gi-dbusmenugtk3 (not considered)
    • Depends: haskell-gtk-sni-tray haskell-gi-gtk (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gtk-sni-tray.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 ♻
    • 334 days old (needed 5 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
    • 334 days old (needed 5 days)
• haskell-gi-dbusmenugtk3 (- to 0.4.14-1)
  • Migration status for haskell-gi-dbusmenugtk3 (- to 0.4.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gi-dbusmenugtk3-dev/armel has unsatisfiable dependency
    • libghc-gi-dbusmenugtk3-prof/armel has unsatisfiable dependency
    • Build-Depends(-Arch): haskell-gi-dbusmenugtk3 haskell-gi-gtk (not considered)
    • Build-Depends-Indep: haskell-gi-dbusmenugtk3 haskell-gi-gtk (not considered)
    • Depends: haskell-gi-dbusmenugtk3 haskell-gi-gtk (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-dbusmenugtk3.html
    • uninstallable on arch armel, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 335 days old (needed 5 days)
• haskell-gi-gtk-hs (- to 0.3.16-1)
  • Migration status for haskell-gi-gtk-hs (- to 0.3.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gi-gtk-hs-dev/armel has unsatisfiable dependency
    • libghc-gi-gtk-hs-prof/armel has unsatisfiable dependency
    • Build-Depends(-Arch): haskell-gi-gtk-hs haskell-gi-gtk (not considered)
    • Build-Depends-Indep: haskell-gi-gtk-hs haskell-gi-gtk (not considered)
    • Depends: haskell-gi-gtk-hs haskell-gi-gtk (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gtk-hs.html
    • uninstallable on arch armel, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 335 days old (needed 5 days)
• haskell-gi-vte (- to 2.91.31-1)
  • Migration status for haskell-gi-vte (- to 2.91.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gi-vte-dev/armel has unsatisfiable dependency
    • libghc-gi-vte-prof/armel has unsatisfiable dependency
    • Build-Depends(-Arch): haskell-gi-vte haskell-gi-gtk (not considered)
    • Build-Depends-Indep: haskell-gi-vte haskell-gi-gtk (not considered)
    • Depends: haskell-gi-vte haskell-gi-gtk (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-vte.html
    • uninstallable on arch armel, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 335 days old (needed 5 days)
• haskell-gtk-strut (- to 0.1.3.2-2)
  • Migration status for haskell-gtk-strut (- to 0.1.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gtk-strut-dev/armel has unsatisfiable dependency
    • libghc-gtk-strut-prof/armel has unsatisfiable dependency
    • Build-Depends(-Arch): haskell-gtk-strut haskell-gi-gtk (not considered)
    • Build-Depends-Indep: haskell-gtk-strut haskell-gi-gtk (not considered)
    • Depends: haskell-gtk-strut haskell-gi-gtk (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gtk-strut.html
    • uninstallable on arch armel, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 335 days old (needed 5 days)
• haskell-termonad (- to 4.5.0.0-1)
  • Migration status for haskell-termonad (- to 4.5.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-termonad haskell-gi-vte (not considered)
    • Build-Depends-Indep: haskell-termonad haskell-gi-vte (not considered)
    • Depends: haskell-termonad haskell-gi-vte (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends(-Arch): haskell-termonad haskell-gi-gtk (not considered)
    • Build-Depends-Indep: haskell-termonad haskell-gi-gtk (not considered)
    • Depends: haskell-termonad haskell-gi-gtk (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-termonad.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 335 days old (needed 5 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
    • 336 days old (needed 5 days)
• haskell-gi-gtk (- to 3.0.41-1)
  • Migration status for haskell-gi-gtk (- to 3.0.41-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gi-gtk-dev/armel has unsatisfiable dependency
    • libghc-gi-gtk-prof/armel has unsatisfiable dependency
    • Updating haskell-gi-gtk would introduce bugs in testing: #1069312
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-gi-gtk.html
    • uninstallable on arch armel, not running autopkgtest there
    • 336 days old (needed 5 days)
• cdecl (- to 2.5-13.1)
  • Migration status for cdecl (- to 2.5-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cdecl would introduce bugs in testing: #1074872
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cdecl.html
    • 337 days old (needed 5 days)
• postmark (- to 1.53-2.1)
  • Migration status for postmark (- to 1.53-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating postmark would introduce bugs in testing: #1066666
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postmark.html
    • 337 days old (needed 5 days)
• r-cran-exactextractr (- to 0.10.0-1)
  • Migration status for r-cran-exactextractr (- to 0.10.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-exactextractr r-cran-sf (not considered)
    • Depends: r-cran-exactextractr r-cran-sf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-exactextractr.html
    • autopkgtest for r-cran-exactextractr/0.10.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
    • 337 days old (needed 2 days)
• openshot-qt (- to 3.1.1+dfsg1-1)
  • Migration status for openshot-qt (- to 3.1.1+dfsg1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: openshot-qt libopenshot (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openshot-qt.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • autopkgtest for openshot-qt/3.1.1+dfsg1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 338 days old (needed 5 days)
• cif2hkl (- to 1.4.3+ds1-1)
  • Migration status for cif2hkl (- to 1.4.3+ds1-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): cif2hkl fort77 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cif2hkl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 340 days old (needed 5 days)
    • Remove hint for (transitive) dependency: cif2hkl
• 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
    • Reproducible on armhf - info ♻
    • 340 days old (needed 5 days)
• haskell-integer-roots (- to 1.0.2.0-2)
  • Migration status for haskell-integer-roots (- to 1.0.2.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-integer-roots.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 340 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
    • 342 days old (needed 2 days)
• haskell-cborg-json (- to 0.2.5.0-2)
  • Migration status for haskell-cborg-json (- to 0.2.5.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-cborg-json haskell-cborg (not considered)
    • Build-Depends-Indep: haskell-cborg-json haskell-cborg (not considered)
    • Depends: haskell-cborg-json haskell-cborg (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cborg-json.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 343 days old (needed 5 days)
• haskell-serialise (- to 0.2.6.0-2)
  • Migration status for haskell-serialise (- to 0.2.6.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): haskell-serialise haskell-cborg (not considered)
    • Build-Depends-Indep: haskell-serialise haskell-cborg (not considered)
    • Depends: haskell-serialise haskell-cborg (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-serialise.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 343 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
    • 344 days old (needed 5 days)
• haskell-cborg (- to 0.2.9.0-1)
  • Migration status for haskell-cborg (- to 0.2.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-cborg would introduce bugs in testing: #1016062
    • missing build on armel
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-cborg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 344 days old (needed 5 days)
• pdfposter (- to 0.8.1-2)
  • Migration status for pdfposter (- to 0.8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pdfposter would introduce bugs in testing: #1029738
    • Build-Depends-Indep: pdfposter pypdf2 (not considered)
    • Depends: pdfposter pypdf2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdfposter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 346 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 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 ghdl (not considered)
    • Build-Depends(-Arch): yosys-plugin-ghdl yosys (not considered)
  • Additional info:
    • Piuparts tested OK - 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 ♻
    • Reproducible on i386 - info ♻
    • 350 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 ♻
    • 351 days old (needed 5 days)
• rust-gtk-sys (- to 0.18.0-2)
  • Migration status for rust-gtk-sys (- to 0.18.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-gtk-sys-dev/amd64 has unsatisfiable dependency
    • librust-gtk-sys-dev/arm64 has unsatisfiable dependency
    • librust-gtk-sys-dev/armel has unsatisfiable dependency
    • librust-gtk-sys-dev/armhf has unsatisfiable dependency
    • librust-gtk-sys-dev/i386 has unsatisfiable dependency
    • librust-gtk-sys-dev/mips64el has unsatisfiable dependency
    • librust-gtk-sys-dev/ppc64el has unsatisfiable dependency
    • librust-gtk-sys-dev/s390x has unsatisfiable dependency
    • Updating rust-gtk-sys would introduce bugs in testing: #1071886
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on amd64: librust-atk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on amd64: librust-cairo-sys-rs-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on amd64: librust-gdk-pixbuf-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on amd64: librust-gdk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on amd64: librust-gio-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on amd64: librust-glib-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on amd64: librust-gobject-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on amd64: librust-pango-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on amd64: librust-system-deps-6+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on arm64: librust-atk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on arm64: librust-cairo-sys-rs-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on arm64: librust-gdk-pixbuf-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on arm64: librust-gdk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on arm64: librust-gio-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on arm64: librust-glib-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on arm64: librust-gobject-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on arm64: librust-pango-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on arm64: librust-system-deps-6+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armel: librust-atk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armel: librust-cairo-sys-rs-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armel: librust-gdk-pixbuf-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armel: librust-gdk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armel: librust-gio-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armel: librust-glib-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armel: librust-gobject-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armel: librust-pango-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armel: librust-system-deps-6+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armhf: librust-atk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armhf: librust-cairo-sys-rs-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armhf: librust-gdk-pixbuf-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armhf: librust-gdk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armhf: librust-gio-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armhf: librust-glib-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armhf: librust-gobject-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armhf: librust-pango-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on armhf: librust-system-deps-6+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on i386: librust-atk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on i386: librust-cairo-sys-rs-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on i386: librust-gdk-pixbuf-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on i386: librust-gdk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on i386: librust-gio-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on i386: librust-glib-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on i386: librust-gobject-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on i386: librust-pango-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on i386: librust-system-deps-6+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on mips64el: librust-atk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on mips64el: librust-cairo-sys-rs-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on mips64el: librust-gdk-pixbuf-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on mips64el: librust-gdk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on mips64el: librust-gio-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on mips64el: librust-glib-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on mips64el: librust-gobject-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on mips64el: librust-pango-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on mips64el: librust-system-deps-6+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on ppc64el: librust-atk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on ppc64el: librust-cairo-sys-rs-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gdk-pixbuf-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gdk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gio-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glib-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gobject-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on ppc64el: librust-pango-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on ppc64el: librust-system-deps-6+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on riscv64: librust-atk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on riscv64: librust-cairo-sys-rs-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on riscv64: librust-gdk-pixbuf-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on riscv64: librust-gdk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on riscv64: librust-gio-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on riscv64: librust-glib-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on riscv64: librust-gobject-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on riscv64: librust-pango-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on riscv64: librust-system-deps-6+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on s390x: librust-atk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on s390x: librust-cairo-sys-rs-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on s390x: librust-gdk-pixbuf-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on s390x: librust-gdk-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on s390x: librust-gio-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on s390x: librust-glib-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on s390x: librust-gobject-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on s390x: librust-pango-sys-0.18+default-dev
    • rust-gtk-sys unsatisfiable Build-Depends(-Arch) on s390x: librust-system-deps-6+default-dev
    • autopkgtest for rust-gtk-sys/0.18.0-2: riscv64: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gtk-sys.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 ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 351 days old (needed 5 days)
• gamescope (- to 3.12.5-1)
  • Migration status for gamescope (- to 3.12.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gamescope/amd64 has unsatisfiable dependency
    • gamescope/arm64 has unsatisfiable dependency
    • gamescope/armhf has unsatisfiable dependency
    • gamescope/i386 has unsatisfiable dependency
    • gamescope/mips64el has unsatisfiable dependency
    • gamescope/ppc64el has unsatisfiable dependency
    • gamescope/s390x has unsatisfiable dependency
    • Updating gamescope would introduce bugs in testing: #1058493, #1074130
    • Build-Depends(-Arch): gamescope openvr (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 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
    • 352 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
    • 352 days old (needed 5 days)
• kdevelop-php (- to 23.08.1-1)
  • Migration status for kdevelop-php (- to 23.08.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kdevelop-php kdevelop (not considered)
    • Depends: kdevelop-php kdevelop (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdevelop-php.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 ♻
    • 355 days old (needed 5 days)
• yosys (- to 0.33-5)
  • Migration status for yosys (- to 0.33-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yosys would introduce bugs in testing: #1069424
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yosys.html
    • autopkgtest for yosys/0.33-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 356 days old (needed 2 days)
• gnome-shell-extension-panel-osd (- to 1.0.50.gc032923-4)
  • Migration status for gnome-shell-extension-panel-osd (- to 1.0.50.gc032923-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnome-shell-extension-panel-osd/amd64 has unsatisfiable dependency
    • gnome-shell-extension-panel-osd/arm64 has unsatisfiable dependency
    • gnome-shell-extension-panel-osd/armel has unsatisfiable dependency
    • gnome-shell-extension-panel-osd/armhf has unsatisfiable dependency
    • gnome-shell-extension-panel-osd/i386 has unsatisfiable dependency
    • gnome-shell-extension-panel-osd/mips64el has unsatisfiable dependency
    • gnome-shell-extension-panel-osd/ppc64el has unsatisfiable dependency
    • gnome-shell-extension-panel-osd/s390x has unsatisfiable dependency
    • Updating gnome-shell-extension-panel-osd would introduce bugs in testing: #1054511
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-panel-osd.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 357 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 ♻
    • 357 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 ♻
    • 357 days old (needed 5 days)
• skorch (- to 0.15.0-1)
  • Migration status for skorch (- to 0.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating skorch would introduce bugs in testing: #1081103
    • autopkgtest for skorch/0.15.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 ♻
    • Build-Depends(-Arch): skorch pytorch (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/skorch.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 ♻
    • 358 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:
    • Updating python-pyo would introduce bugs in testing: #1075420
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyo.html
    • autopkgtest for python-pyo/1.0.5-5: 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
    • 359 days old (needed 2 days)
• spacefm (- to 1.0.6-7)
  • Migration status for spacefm (- to 1.0.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spacefm would introduce bugs in testing: #1075530
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spacefm.html
    • Reproducible on armhf - info ♻
    • 359 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
    • Reproducible on armhf - info ♻
    • 360 days old (needed 5 days)
• rust-rsa (- to 0.9.2-2)
  • Migration status for rust-rsa (- to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-rsa would introduce bugs in testing: #1057096
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rsa.html
    • autopkgtest for rust-rsa/0.9.2-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 360 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-systems gosa (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 361 days old (needed 5 days)
• guile-gnutls (- to 4.0.0-1)
  • Migration status for guile-gnutls (- to 4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guile-gnutls would introduce bugs in testing: #1069390
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guile-gnutls.html
    • 361 days old (needed 5 days)
• invada-studio-plugins-lv2 (- to 1.2.0+repack0-9)
  • Migration status for invada-studio-plugins-lv2 (- to 1.2.0+repack0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating invada-studio-plugins-lv2 would introduce bugs in testing: #1075091
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/invada-studio-plugins-lv2.html
    • Reproducible on armhf - info ♻
    • 361 days old (needed 5 days)
• 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
    • 361 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
    • Reproducible on armhf - info ♻
    • 361 days old (needed 5 days)
• giggle (- to 0.7-6)
  • Migration status for giggle (- to 0.7-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating giggle would introduce bugs in testing: #1074997
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/giggle.html
    • Reproducible on armhf - info ♻
    • 362 days old (needed 5 days)
• lxmusic (- to 0.4.7-2)
  • Migration status for lxmusic (- to 0.4.7-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lxmusic xmms2 (not considered)
    • Depends: lxmusic xmms2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lxmusic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 363 days old (needed 5 days)
• obs-ashmanix-countdown (- to 1.3.3-1)
  • Migration status for obs-ashmanix-countdown (- to 1.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • obs-ashmanix-countdown/armel has unsatisfiable dependency
    • obs-ashmanix-countdown/armhf has unsatisfiable dependency
    • Updating obs-ashmanix-countdown would introduce bugs in testing: #1060938, #1071165
    • autopkgtest for obs-ashmanix-countdown/1.3.3-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: 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/obs-ashmanix-countdown.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 365 days old (needed 5 days)
• performous (- to 1.3.0+ds-1)
  • Migration status for performous (- to 1.3.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating performous would introduce bugs in testing: #1072444
    • Impossible Depends: performous -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: performous -> libavformat60/7:6.1.1-5+b1/armhf
    • Impossible Depends: performous -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: performous -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: performous -> libavformat60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: performous -> libavformat60/7:6.1.1-5+b1/s390x
    • Build-Depends(-Arch): performous aubio (not considered)
    • Depends: performous aubio (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/performous.html
    • Reproducible on armhf - info ♻
    • 365 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/s390x has unsatisfiable dependency
    • Updating xpra would introduce bugs in testing: #1067627, #1072463
    • autopkgtest for xpra/3.1.5+dfsg1-0.2: riscv64: Regression or new test ♻
  • 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 s390x, not running autopkgtest there
    • 365 days old (needed 5 days)
• cecilia (- to 5.4.1-2)
  • Migration status for cecilia (- to 5.4.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: cecilia python-pyo (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 367 days old (needed 5 days)
• moc (- to 1:2.6.0~svn-r3005-3.1)
  • Migration status for moc (- to 1:2.6.0~svn-r3005-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating moc would introduce bugs in testing: #1072436
    • Impossible Depends: moc -> libavformat-extra60/7:6.1.1-5+b1/armhf
    • Impossible Depends: moc -> libavformat-extra60/7:6.1.1-5+b1/s390x
    • Impossible Depends: moc -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: moc -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: moc -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: moc -> libavformat60/7:6.1.1-5+b1/ppc64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/moc.html
    • Reproducible on armhf - info ♻
    • 367 days old (needed 5 days)
• ppx-tools (- to 6.6-4)
  • Migration status for ppx-tools (- to 6.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libppx-tools-ocaml-dev/amd64 has unsatisfiable dependency
    • libppx-tools-ocaml-dev/arm64 has unsatisfiable dependency
    • libppx-tools-ocaml-dev/armel has unsatisfiable dependency
    • libppx-tools-ocaml-dev/armhf has unsatisfiable dependency
    • libppx-tools-ocaml-dev/i386 has unsatisfiable dependency
    • libppx-tools-ocaml-dev/mips64el has unsatisfiable dependency
    • libppx-tools-ocaml-dev/ppc64el has unsatisfiable dependency
    • libppx-tools-ocaml-dev/s390x has unsatisfiable dependency
    • Updating ppx-tools would introduce bugs in testing: #1078383
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ppx-tools.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 367 days old (needed 5 days)
• soundgrain (- to 6.0.1-5)
  • Migration status for soundgrain (- to 6.0.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: soundgrain python-pyo (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 367 days old (needed 5 days)
• opentsne (- to 1.0.0-1)
  • Migration status for opentsne (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opentsne would introduce bugs in testing: #1004706, #1056827
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for opentsne/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opentsne.html
    • 368 days old (needed 5 days)
• icmpush (- to 2.2-7)
  • Migration status for icmpush (- to 2.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating icmpush would introduce bugs in testing: #1075080
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icmpush.html
    • Reproducible on armhf - info ♻
    • 369 days old (needed 5 days)
• rust-abscissa-derive (- to 0.7.0-1)
  • Migration status for rust-abscissa-derive (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-abscissa-derive-dev/amd64 has unsatisfiable dependency
    • librust-abscissa-derive-dev/arm64 has unsatisfiable dependency
    • librust-abscissa-derive-dev/armel has unsatisfiable dependency
    • librust-abscissa-derive-dev/armhf has unsatisfiable dependency
    • librust-abscissa-derive-dev/i386 has unsatisfiable dependency
    • librust-abscissa-derive-dev/mips64el has unsatisfiable dependency
    • librust-abscissa-derive-dev/ppc64el has unsatisfiable dependency
    • librust-abscissa-derive-dev/s390x has unsatisfiable dependency
    • Updating rust-abscissa-derive would introduce bugs in testing: #1069796
    • rust-abscissa-derive unsatisfiable Build-Depends(-Arch) on amd64: librust-synstructure-0.12+default-dev
    • rust-abscissa-derive unsatisfiable Build-Depends(-Arch) on arm64: librust-synstructure-0.12+default-dev
    • rust-abscissa-derive unsatisfiable Build-Depends(-Arch) on armel: librust-synstructure-0.12+default-dev
    • rust-abscissa-derive unsatisfiable Build-Depends(-Arch) on armhf: librust-synstructure-0.12+default-dev
    • rust-abscissa-derive unsatisfiable Build-Depends(-Arch) on i386: librust-synstructure-0.12+default-dev
    • rust-abscissa-derive unsatisfiable Build-Depends(-Arch) on mips64el: librust-synstructure-0.12+default-dev
    • rust-abscissa-derive unsatisfiable Build-Depends(-Arch) on ppc64el: librust-synstructure-0.12+default-dev
    • rust-abscissa-derive unsatisfiable Build-Depends(-Arch) on riscv64: librust-synstructure-0.12+default-dev
    • rust-abscissa-derive unsatisfiable Build-Depends(-Arch) on s390x: librust-synstructure-0.12+default-dev
    • autopkgtest for rust-abscissa-derive/0.7.0-1: riscv64: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-abscissa-derive.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 ♻
    • 369 days old (needed 5 days)
• golang-github-jesseduffield-go-git (- to 5.1.2+git20221018.fdd53fe-1)
  • Migration status for golang-github-jesseduffield-go-git (- to 5.1.2+git20221018.fdd53fe-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by openarungeek@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-go-git.html
    • autopkgtest for golang-github-jesseduffield-go-git/5.1.2+git20221018.fdd53fe-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 370 days old (needed 2 days)
• haskell-hsyaml-aeson (- to 0.2.0.1-2)
  • Migration status for haskell-hsyaml-aeson (- to 0.2.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-hsyaml-aeson would introduce bugs in testing: #1054961
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on riscv64: libghc-vector-dev (<< 0.13)
    • haskell-hsyaml-aeson unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on 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-hsyaml-aeson.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 370 days old (needed 5 days)
• python-docformatter (- to 1.7.5-1)
  • Migration status for python-docformatter (- to 1.7.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-docformatter would introduce bugs in testing: #1056469
    • autopkgtest for python-docformatter/1.7.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-docformatter.html
    • 371 days old (needed 5 days)
• pytorch-ignite (- to 0.4.12-1)
  • Migration status for pytorch-ignite (- to 0.4.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytorch-ignite would introduce bugs in testing: #1081095
    • Build-Depends(-Arch): pytorch-ignite pytorch (not considered)
    • Depends: pytorch-ignite python3.11_pu (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pytorch-ignite.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 ♻
    • 371 days old (needed 5 days)
• pytorch-text (- to 0.15.2-1)
  • Migration status for pytorch-text (- to 0.15.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-torchtext/amd64 has unsatisfiable dependency
    • python3-torchtext/arm64 has unsatisfiable dependency
    • python3-torchtext/ppc64el has unsatisfiable dependency
    • python3-torchtext/s390x has unsatisfiable dependency
    • Updating pytorch-text would introduce bugs in testing: #1081098
    • Build-Depends(-Arch): pytorch-text pytorch (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pytorch-text.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 371 days old (needed 5 days)
• haskell-base64 (- to 0.4.2.4-3)
  • Migration status for haskell-base64 (- to 0.4.2.4-3): 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 ♻
    • 372 days old (needed 5 days)
• nomacs (- to 3.17.2282+dfsg-2)
  • Migration status for nomacs (- to 3.17.2282+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nomacs would introduce bugs in testing: #1014124, #1081086, #974616
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nomacs.html
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 373 days old (needed 5 days)
• python-aiojobs (- to 1.1.0-2)
  • Migration status for python-aiojobs (- to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiojobs would introduce bugs in testing: #1060944
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiojobs.html
    • autopkgtest for python-aiojobs/1.1.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 373 days old (needed 5 days)
• vuls (- to 0.6.1-5)
  • Migration status for vuls (- to 0.6.1-5): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch i386 binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • 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-github-go-redis-redis (not considered)
    • 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
    • 373 days old (needed 2 days)
• pytorch-vision (- to 0.15.2-1)
  • Migration status for pytorch-vision (- to 0.15.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-torchvision/amd64 has unsatisfiable dependency
    • python3-torchvision/arm64 has unsatisfiable dependency
    • python3-torchvision/ppc64el has unsatisfiable dependency
    • python3-torchvision/s390x has unsatisfiable dependency
    • Updating pytorch-vision would introduce bugs in testing: #1051811, #1063950, #1065722
    • Build-Depends(-Arch): pytorch-vision pytorch (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pytorch-vision.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 374 days old (needed 5 days)
• clickhouse (- to 18.16.1+ds-7.4)
  • Migration status for clickhouse (- to 18.16.1+ds-7.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • clickhouse-client/amd64 has unsatisfiable dependency
    • clickhouse-common/amd64 has unsatisfiable dependency
    • clickhouse-server/amd64 has unsatisfiable dependency
    • clickhouse-tools/amd64 has unsatisfiable dependency
    • clickhouse-client/arm64 has unsatisfiable dependency
    • clickhouse-common/arm64 has unsatisfiable dependency
    • clickhouse-server/arm64 has unsatisfiable dependency
    • clickhouse-tools/arm64 has unsatisfiable dependency
    • clickhouse-client/ppc64el has unsatisfiable dependency
    • clickhouse-common/ppc64el has unsatisfiable dependency
    • clickhouse-server/ppc64el has unsatisfiable dependency
    • clickhouse-tools/ppc64el has unsatisfiable dependency
    • clickhouse-client/s390x has unsatisfiable dependency
    • clickhouse-common/s390x has unsatisfiable dependency
    • clickhouse-server/s390x has unsatisfiable dependency
    • clickhouse-tools/s390x has unsatisfiable dependency
    • Updating clickhouse would introduce bugs in testing: #1059261, #1066987, #1070658, #1077820
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/c/clickhouse.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
    • 375 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11-cross-mipsen.html
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 376 days old (needed 5 days)
• yubikey-luks (- to 0.5.1+29.g5df2b95-6.2)
  • Migration status for yubikey-luks (- to 0.5.1+29.g5df2b95-6.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yubikey-luks would introduce bugs in testing: #1073697
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yubikey-luks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 376 days old (needed 5 days)
• gnome-shell-extension-weather (- to 121-1)
  • Migration status for gnome-shell-extension-weather (- to 121-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnome-shell-extension-weather/amd64 has unsatisfiable dependency
    • gnome-shell-extension-weather/arm64 has unsatisfiable dependency
    • Updating gnome-shell-extension-weather would introduce bugs in testing: #1052111
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-weather.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 377 days old (needed 5 days)
• haskell-regex-pcre (- to 0.95.0.0-4)
  • Migration status for haskell-regex-pcre (- to 0.95.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-regex-pcre would introduce bugs in testing: #1000067
    • Build-Depends(-Arch): haskell-regex-pcre pcre3 (not considered)
    • Depends: haskell-regex-pcre pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-regex-pcre.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 378 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
    • Reproducible on armhf - info ♻
    • 379 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: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ormar fastapi (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ormar.html
    • 379 days old (needed 5 days)
• gnome-shell-extension-gamemode (- to 8-3)
  • Migration status for gnome-shell-extension-gamemode (- to 8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnome-shell-extension-gamemode/amd64 has unsatisfiable dependency
    • gnome-shell-extension-gamemode/arm64 has unsatisfiable dependency
    • Updating gnome-shell-extension-gamemode would introduce bugs in testing: #1052098
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-gamemode.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 s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 382 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
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-vertical-overview.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 s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 382 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/s390x has unsatisfiable dependency
    • mia-tools/s390x has unsatisfiable dependency
    • Updating mia would introduce bugs in testing: #1075270
  • Additional info:
    • Piuparts tested OK - 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 s390x, not running autopkgtest there
    • 382 days old (needed 5 days)
• worker (- to 4.12.1-1)
  • Migration status for worker (- to 4.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • worker/armel has unsatisfiable dependency
    • Build-Depends(-Arch): worker avfs (not considered)
    • Depends: worker avfs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/worker.html
    • uninstallable on arch armel, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 383 days old (needed 5 days)
• lookatme (- to 2.5.4-2)
  • Migration status for lookatme (- to 2.5.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lookatme would introduce bugs in testing: #1061029
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lookatme.html
    • 386 days old (needed 5 days)
• bind-dyndb-ldap (- to 11.10-6)
  • Migration status for bind-dyndb-ldap (- to 11.10-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bind9-dyndb-ldap/amd64 has unsatisfiable dependency
    • bind9-dyndb-ldap/arm64 has unsatisfiable dependency
    • bind9-dyndb-ldap/armel has unsatisfiable dependency
    • bind9-dyndb-ldap/armhf has unsatisfiable dependency
    • bind9-dyndb-ldap/i386 has unsatisfiable dependency
    • bind9-dyndb-ldap/mips64el has unsatisfiable dependency
    • bind9-dyndb-ldap/ppc64el has unsatisfiable dependency
    • bind9-dyndb-ldap/s390x has unsatisfiable dependency
    • Updating bind-dyndb-ldap would introduce bugs in testing: #1064294
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/b/bind-dyndb-ldap.html
    • autopkgtest for bind-dyndb-ldap/11.10-6: riscv64: Regression or new test ♻
    • 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:
    • 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
    • 387 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-sudo gosa (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 387 days old (needed 5 days)
• 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)
    • 387 days old (needed 5 days)
• rally-openstack (- to 2.2.0-3)
  • Migration status for rally-openstack (- to 2.2.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: rally-openstack rally (not considered)
    • Depends: rally-openstack rally (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rally-openstack.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 389 days old (needed 5 days)
• socket-wrapper (- to 1.4.2-3)
  • Migration status for socket-wrapper (- to 1.4.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating socket-wrapper would introduce bugs in testing: #1069450
    • autopkgtest for socket-wrapper/1.4.2-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/socket-wrapper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 389 days old (needed 5 days)
• undertow (- to 2.3.8-2)
  • Migration status for undertow (- to 2.3.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating undertow would introduce bugs in testing: #1068816
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/undertow.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 389 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
    • 390 days old (needed 2 days)
• libesmtp (- to 1.1.0-3.1)
  • Migration status for libesmtp (- to 1.1.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libesmtp would introduce bugs in testing: #1068782, #1071322
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libesmtp.html
    • 390 days old (needed 5 days)
• python-mp-api (- to 0.34.3-1)
  • Migration status for python-mp-api (- to 0.34.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-mp-api would introduce bugs in testing: #1078531
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mp-api.html
    • autopkgtest for python-mp-api/0.34.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
    • 391 days old (needed 2 days)
• r-cran-gstat (- to 2.1-1-2)
  • Migration status for r-cran-gstat (- to 2.1-1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-gstat/2.1-1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): r-cran-gstat r-cran-sf (not considered)
    • Build-Depends(-Arch): r-cran-gstat r-cran-sftime
    • Build-Depends(-Arch): r-cran-gstat r-cran-stars
    • Depends: r-cran-gstat r-cran-sf (not considered)
    • Depends: r-cran-gstat r-cran-sftime
    • Depends: r-cran-gstat r-cran-stars
  • 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 ♻
    • 391 days old (needed 5 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 ♻
    • 392 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
    • 392 days old (needed 5 days)
• libbloom (- to 1.6-7)
  • Migration status for libbloom (- to 1.6-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libbloom ploticus (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbloom.html
    • autopkgtest for libbloom/1.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
    • 393 days old (needed 2 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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-oauth2client.html
    • 393 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: 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): go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: go-cve-dictionary golang-1.23
    • Built-Using: go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: go-cve-dictionary golang-github-golang-jwt-jwt
    • 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
    • 394 days old (needed 2 days)
• golang-github-jesseduffield-termbox-go (- to 0.0~git20200823.a2289ed-1)
  • Migration status for golang-github-jesseduffield-termbox-go (- to 0.0~git20200823.a2289ed-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-termbox-go would introduce bugs in testing: #1032114
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-termbox-go.html
    • autopkgtest for golang-github-jesseduffield-termbox-go/0.0~git20200823.a2289ed-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 394 days old (needed 2 days)
• gost (- to 0.1.2-2)
  • Migration status for gost (- to 0.1.2-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Not built on buildd: upload info for arch 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
    • 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
    • 394 days old (needed 2 days)
• goval-dictionary (- to 0.2.0-6)
  • Migration status for goval-dictionary (- to 0.2.0-6): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Not built on buildd: upload info for arch amd64 binaries not found
    • Not built on buildd: upload info for arch arm64 binaries not found
    • Not built on buildd: upload info for arch 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
    • 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
    • 394 days old (needed 2 days)
• ocaml-lo (- to 0.2.0-4)
  • Migration status for ocaml-lo (- to 0.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liblo-ocaml/amd64 has unsatisfiable dependency
    • liblo-ocaml-dev/amd64 has unsatisfiable dependency
    • liblo-ocaml/arm64 has unsatisfiable dependency
    • liblo-ocaml-dev/arm64 has unsatisfiable dependency
    • liblo-ocaml/armel has unsatisfiable dependency
    • liblo-ocaml-dev/armel has unsatisfiable dependency
    • liblo-ocaml/armhf has unsatisfiable dependency
    • liblo-ocaml-dev/armhf has unsatisfiable dependency
    • liblo-ocaml/i386 has unsatisfiable dependency
    • liblo-ocaml-dev/i386 has unsatisfiable dependency
    • liblo-ocaml/mips64el has unsatisfiable dependency
    • liblo-ocaml-dev/mips64el has unsatisfiable dependency
    • liblo-ocaml/ppc64el has unsatisfiable dependency
    • liblo-ocaml-dev/ppc64el has unsatisfiable dependency
    • liblo-ocaml/s390x has unsatisfiable dependency
    • liblo-ocaml-dev/s390x has unsatisfiable dependency
    • Updating ocaml-lo would introduce bugs in testing: #1075329
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-lo.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 394 days old (needed 5 days)
• ocaml-luv (- to 0.5.12-2)
  • Migration status for ocaml-luv (- to 0.5.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libluv-ocaml/amd64 has unsatisfiable dependency
    • libluv-ocaml-dev/amd64 has unsatisfiable dependency
    • libluv-unix-ocaml/amd64 has unsatisfiable dependency
    • libluv-unix-ocaml-dev/amd64 has unsatisfiable dependency
    • libluv-ocaml/arm64 has unsatisfiable dependency
    • libluv-ocaml-dev/arm64 has unsatisfiable dependency
    • libluv-unix-ocaml/arm64 has unsatisfiable dependency
    • libluv-unix-ocaml-dev/arm64 has unsatisfiable dependency
    • libluv-ocaml/armel has unsatisfiable dependency
    • libluv-ocaml-dev/armel has unsatisfiable dependency
    • libluv-unix-ocaml/armel has unsatisfiable dependency
    • libluv-unix-ocaml-dev/armel has unsatisfiable dependency
    • libluv-ocaml/armhf has unsatisfiable dependency
    • libluv-ocaml-dev/armhf has unsatisfiable dependency
    • libluv-unix-ocaml/armhf has unsatisfiable dependency
    • libluv-unix-ocaml-dev/armhf has unsatisfiable dependency
    • libluv-ocaml/i386 has unsatisfiable dependency
    • libluv-ocaml-dev/i386 has unsatisfiable dependency
    • libluv-unix-ocaml/i386 has unsatisfiable dependency
    • libluv-unix-ocaml-dev/i386 has unsatisfiable dependency
    • libluv-ocaml/mips64el has unsatisfiable dependency
    • libluv-ocaml-dev/mips64el has unsatisfiable dependency
    • libluv-unix-ocaml/mips64el has unsatisfiable dependency
    • libluv-unix-ocaml-dev/mips64el has unsatisfiable dependency
    • libluv-ocaml/ppc64el has unsatisfiable dependency
    • libluv-ocaml-dev/ppc64el has unsatisfiable dependency
    • libluv-unix-ocaml/ppc64el has unsatisfiable dependency
    • libluv-unix-ocaml-dev/ppc64el has unsatisfiable dependency
    • libluv-ocaml/s390x has unsatisfiable dependency
    • libluv-ocaml-dev/s390x has unsatisfiable dependency
    • libluv-unix-ocaml/s390x has unsatisfiable dependency
    • libluv-unix-ocaml-dev/s390x has unsatisfiable dependency
    • Updating ocaml-luv would introduce bugs in testing: #1073023, #1081124
    • autopkgtest for ocaml-luv/0.5.12-2: riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-luv.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 394 days old (needed 5 days)
• pcre-ocaml (- to 7.5.0-3)
  • Migration status for pcre-ocaml (- to 7.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pcre-ocaml would introduce bugs in testing: #1000004
    • Build-Depends(-Arch): pcre-ocaml pcre3 (not considered)
    • Depends: pcre-ocaml pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcre-ocaml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 394 days old (needed 5 days)
• proofgeneral (- to 4.5-1)
  • Migration status for proofgeneral (- to 4.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating proofgeneral would introduce bugs in testing: #1077126
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/proofgeneral.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 394 days old (needed 5 days)
• go-exploitdb (- to 0.0~git20181130.7c961e7-3)
  • Migration status for go-exploitdb (- to 0.0~git20181130.7c961e7-3): 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): go-exploitdb golang-github-go-redis-redis (not considered)
    • Built-Using: go-exploitdb golang-1.23
    • Built-Using: go-exploitdb golang-github-go-redis-redis (not considered)
    • Built-Using: go-exploitdb golang-github-golang-jwt-jwt
    • 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
    • 395 days old (needed 2 days)
• priv-wrapper (- to 1.0.1-3)
  • Migration status for priv-wrapper (- to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating priv-wrapper would introduce bugs in testing: #1069486
    • autopkgtest for priv-wrapper/1.0.1-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/p/priv-wrapper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 395 days old (needed 5 days)
• python-discord (- to 2.3.2+dfsg-2)
  • Migration status for python-discord (- to 2.3.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-discord would introduce bugs in testing: #1057608
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-discord.html
    • autopkgtest for python-discord/2.3.2+dfsg-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 395 days old (needed 5 days)
• redmine-plugin-local-avatars (- to 1.0.6-1)
  • Migration status for redmine-plugin-local-avatars (- to 1.0.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-local-avatars redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-local-avatars.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 395 days old (needed 5 days)
• redmine-plugin-pretend (- to 1.0-2)
  • Migration status for redmine-plugin-pretend (- to 1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-pretend redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-pretend.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 395 days old (needed 5 days)
• samhain (- to 4.1.4-2.1)
  • Migration status for samhain (- to 4.1.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • samhain/armel has unsatisfiable dependency
    • samhain/armhf has unsatisfiable dependency
    • Updating samhain would introduce bugs in testing: #1066529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/samhain.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 395 days old (needed 5 days)
• libengine-gost-openssl (- to 3.0.2-1)
  • Migration status for libengine-gost-openssl (- to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libengine-gost-openssl would introduce bugs in testing: #1054922
    • Impossible Depends: libengine-gost-openssl -> libssl3/3.0.14-1~deb12u2/armhf
    • Impossible Depends: libengine-gost-openssl -> libssl3/3.1.5-1/armel
    • Impossible Depends: libengine-gost-openssl -> libssl3/3.1.5-1/armhf
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libengine-gost-openssl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 396 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
    • Depends: xemacs21 xemacs21-packages
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xemacs21.html
    • 396 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 ♻
    • 397 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 ♻
    • Depends: searx flask-babel (not considered)
  • 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 ♻
    • 397 days old (needed 5 days)
    • Remove hint for (transitive) dependency: flask-babel
• slbackup-php (- to 0.4.5-5)
  • Migration status for slbackup-php (- to 0.4.5-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: slbackup-php smarty3 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slbackup-php.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 400 days old (needed 5 days)
• tomcatjss (- to 8.4.0-2)
  • Migration status for tomcatjss (- to 8.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomcatjss would introduce bugs in testing: #1031816
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomcatjss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 400 days old (needed 5 days)
• fanwor (- to 1.16-1)
  • Migration status for fanwor (- to 1.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fanwor would introduce bugs in testing: #1055538
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fanwor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 401 days old (needed 5 days)
• slashem (- to 0.0.7E7F3-11)
  • Migration status for slashem (- to 0.0.7E7F3-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating slashem would introduce bugs in testing: #1075515
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slashem.html
    • Reproducible on armhf - info ♻
    • 402 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:
    • Updating rmlint would introduce bugs in testing: #1065947
    • Impossible Depends: rmlint -> libelf1/0.190-1+b1/armel
    • Impossible Depends: rmlint -> libelf1/0.190-1+b1/armhf
    • Impossible Depends: rmlint -> libglib2.0-0/2.78.4-1/armel
    • Impossible Depends: rmlint -> libglib2.0-0/2.78.4-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rmlint.html
    • autopkgtest for rmlint/2.9.0-2.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
    • 403 days old (needed 2 days)
• ipfm (- to 0.11.5-4.4)
  • Migration status for ipfm (- to 0.11.5-4.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ipfm would introduce bugs in testing: #1075092
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ipfm.html
    • Reproducible on armhf - info ♻
    • 404 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:
    • Updating ddnet would introduce bugs in testing: #1072409
    • Impossible Depends: ddnet -> libavformat-extra60/7:6.1.1-5+b1/armhf
    • Impossible Depends: ddnet -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: ddnet -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: ddnet -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: ddnet -> libavformat60/7:6.1.1-5+b1/ppc64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/ddnet.html
    • autopkgtest for ddnet/16.4-1.2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 405 days old (needed 2 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 ♻
    • 406 days old (needed 5 days)
• criu (- to 3.17.1-3)
  • Migration status for criu (- to 3.17.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating criu would introduce bugs in testing: #1054814
    • Impossible Depends: criu -> libgnutls30/3.8.3-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/criu.html
    • 406 days old (needed 5 days)
• the (- to 3.3~rc1-3.2)
  • Migration status for the (- to 3.3~rc1-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating the would introduce bugs in testing: #1075570
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/the.html
    • Reproducible on armhf - info ♻
    • 406 days old (needed 5 days)
• avfs (- to 1.1.5-1)
  • Migration status for avfs (- to 1.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating avfs would introduce bugs in testing: #1061322, #1068264
    • missing build on armel
    • arch:armel not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/avfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 407 days old (needed 5 days)
• mtpaint (- to 3.50-0.1)
  • Migration status for mtpaint (- to 3.50-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mtpaint would introduce bugs in testing: #1075296
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mtpaint.html
    • Reproducible on armhf - info ♻
    • 409 days old (needed 5 days)
• linphone-desktop (- to 5.0.2-4)
  • Migration status for linphone-desktop (- to 5.0.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: linphone-desktop mediastreamer2 (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): linphone-desktop linphone
    • Depends: linphone-desktop linphone
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linphone-desktop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 412 days old (needed 5 days)
• msopenh264 (- to 5.2.0-2)
  • Migration status for msopenh264 (- 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): msopenh264 mediastreamer2 (not considered)
    • Depends: msopenh264 mediastreamer2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/msopenh264.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 412 days old (needed 5 days)
• bcmatroska2 (- to 5.2.0-2)
  • Migration status for bcmatroska2 (- to 5.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bcmatroska2 would introduce bugs in testing: #1074838
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bcmatroska2.html
    • Reproducible on armhf - info ♻
    • 413 days old (needed 5 days)
• trinity (- to 1.9+git20230728.e71872454d26-1)
  • Migration status for trinity (- to 1.9+git20230728.e71872454d26-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating trinity would introduce bugs in testing: #1066413
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trinity.html
    • autopkgtest for trinity/1.9+git20230728.e71872454d26-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 ♻
    • 413 days old (needed 5 days)
• aspectc++ (- to 1:2.3+git20230726-1)
  • Migration status for aspectc++ (- to 1:2.3+git20230726-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aspectc++ would introduce bugs in testing: #1070443, #1076205
    • Build-Depends(-Arch): aspectc++ llvm-toolchain-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aspectc++.html
    • autopkgtest for aspectc++/1:2.3+git20230726-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
    • 416 days old (needed 2 days)
• r-cran-geoknife (- to 1.6.11+dfsg-1)
  • Migration status for r-cran-geoknife (- to 1.6.11+dfsg-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-geoknife r-cran-sf (not considered)
    • Depends: r-cran-geoknife r-cran-sf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-geoknife.html
    • autopkgtest for r-cran-geoknife/1.6.11+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
    • 419 days old (needed 2 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:
    • Updating openmw would introduce bugs in testing: #1072443, #1075344
    • Impossible Depends: openmw -> libavformat-extra60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: openmw -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: openmw -> libavformat60/7:6.1.1-5+b1/armhf
    • Impossible Depends: openmw -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: openmw -> libavformat60/7:6.1.1-5+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmw.html
    • Reproducible on armhf - info ♻
    • 420 days old (needed 5 days)
• openjdk-20 (- to 20.0.2+9-1)
  • Migration status for openjdk-20 (- to 20.0.2+9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-20 would introduce bugs in testing: #1031889, #1069315
    • autopkgtest for openjdk-20/20.0.2+9-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: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Impossible Build-Depends(-Arch): openjdk-20 -> libgtk-3-0/3.24.41-1/armel
    • Impossible Build-Depends(-Arch): openjdk-20 -> libgtk-3-0/3.24.41-1/armhf
    • Impossible Depends: openjdk-20 -> libasound2/1.2.10-3/armel
    • Impossible Depends: openjdk-20 -> libasound2/1.2.10-3/armhf
    • Impossible Depends: openjdk-20 -> libcups2/2.4.7-1+b1/armel
    • Impossible Depends: openjdk-20 -> libcups2/2.4.7-1+b1/armhf
    • Impossible Depends: openjdk-20 -> libglib2.0-0/2.78.4-1/armel
    • Impossible Depends: openjdk-20 -> libglib2.0-0/2.78.4-1/armhf
    • Impossible Depends: openjdk-20 -> libgtk-3-0/3.24.41-1/armel
    • Impossible Depends: openjdk-20 -> libgtk-3-0/3.24.41-1/armhf
    • Impossible Depends: openjdk-20 -> libpng16-16/1.6.43-1/armel
    • Impossible Depends: openjdk-20 -> libpng16-16/1.6.43-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-20.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 421 days old (needed 5 days)
• pyrlp (- to 0.5.1-4)
  • Migration status for pyrlp (- to 0.5.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyrlp would introduce bugs in testing: #1056442
    • autopkgtest for pyrlp/0.5.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyrlp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 421 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 syncevolution
    • Depends: debian-parl unicode-screensaver (not considered)
  • 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
    • 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 ♻
    • 423 days old (needed 5 days)
• meta-kde-telepathy (- to 22.12.3.2)
  • Migration status for meta-kde-telepathy (- to 22.12.3.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: meta-kde-telepathy ktp-text-ui (not considered)
    • Invalidated by dependency
    • Depends: meta-kde-telepathy ktp-accounts-kcm
    • Depends: meta-kde-telepathy ktp-approver
    • Depends: meta-kde-telepathy ktp-auth-handler
    • Depends: meta-kde-telepathy ktp-call-ui
    • Depends: meta-kde-telepathy ktp-contact-list
    • Depends: meta-kde-telepathy ktp-contact-runner
    • Depends: meta-kde-telepathy ktp-desktop-applets
    • Depends: meta-kde-telepathy ktp-filetransfer-handler
    • Depends: meta-kde-telepathy ktp-kded-integration-module
    • Depends: meta-kde-telepathy ktp-send-file
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meta-kde-telepathy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 423 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
    • Build-Depends(-Arch): iem-plugin-suite juce (not considered)
    • Built-Using: iem-plugin-suite juce (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iem-plugin-suite.html
    • Reproducible on armhf - info ♻
    • 424 days old (needed 5 days)
• gammaray (- to 2.11.3-4)
  • Migration status for gammaray (- to 2.11.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gammaray would introduce bugs in testing: #1017144
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gammaray.html
    • Reproducible on armhf - info ♻
    • 425 days old (needed 5 days)
• pcm (- to 202307-1)
  • Migration status for pcm (- to 202307-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pcm simdjson (not considered)
    • Depends: pcm simdjson (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcm.html
    • Reproducible on amd64 - info ♻
    • 426 days old (needed 5 days)
• renderdoc (- to 1.27+dfsg-1)
  • Migration status for renderdoc (- to 1.27+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating renderdoc would introduce bugs in testing: #1067012, #999924
    • Build-Depends(-Arch): renderdoc pcre3 (not considered)
    • Depends: renderdoc python3.11_pu (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 427 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
    • Reproducible on armhf - info ♻
    • 427 days old (needed 5 days)
• wacomtablet (- to 3.2.0-5)
  • Migration status for wacomtablet (- to 3.2.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wacomtablet would introduce bugs in testing: #1069495
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wacomtablet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 427 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 ♻
    • 428 days old (needed 5 days)
• ruby-appraiser-rubocop (- to 1.0.1-2)
  • Migration status for ruby-appraiser-rubocop (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-appraiser-rubocop/amd64 has unsatisfiable dependency
    • ruby-appraiser-rubocop/arm64 has unsatisfiable dependency
    • Updating ruby-appraiser-rubocop would introduce bugs in testing: #1054166
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-appraiser-rubocop.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 428 days old (needed 5 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
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 429 days old (needed 2 days)
• golang-github-hashicorp-terraform-registry-address (- to 0.2.0-1)
  • Migration status for golang-github-hashicorp-terraform-registry-address (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by foka, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hashicorp-terraform-registry-address.html
    • autopkgtest for golang-github-hashicorp-terraform-registry-address/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 430 days old (needed 2 days)
• redmine (- to 5.0.4-7)
  • Migration status for redmine (- to 5.0.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating redmine would introduce bugs in testing: #1040927, #1052877, #1055474
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/redmine.html
    • autopkgtest for redmine/5.0.4-7: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): redmine ruby-html-pipeline (not considered)
    • Build-Depends(-Arch): redmine ruby-task-list
    • Depends: redmine ruby-html-pipeline (not considered)
    • Depends: redmine ruby-task-list
  • Additional info:
    • 432 days old (needed 5 days)
• kanboard (- to 1.2.31+ds2-1)
  • Migration status for kanboard (- to 1.2.31+ds2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kanboard would introduce bugs in testing: #1051989, #1052638, #1072791, #1079245
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kanboard.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for kanboard/1.2.31+ds2-1: amd64: Pass, arm64: Pass, ppc64el: Pass, 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
    • 433 days old (needed 2 days)
• tpm2-pkcs11 (- to 1.9.0-0.2)
  • Migration status for tpm2-pkcs11 (- to 1.9.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tpm2-pkcs11 would introduce bugs in testing: #1078324
    • Build-Depends(-Arch): tpm2-pkcs11 tpm2-pytss
    • Depends: tpm2-pkcs11 tpm2-pytss
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpm2-pkcs11.html
    • autopkgtest for tpm2-pkcs11/1.9.0-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
    • 434 days old (needed 2 days)
• ruby-kdl (- to 1.0.3-1)
  • Migration status for ruby-kdl (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by kanashiro, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-kdl.html
    • autopkgtest for ruby-kdl/1.0.3-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 435 days old (needed 5 days)
• openjdk-19 (- to 19.0.2+7-4)
  • Migration status for openjdk-19 (- to 19.0.2+7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-19 would introduce bugs in testing: #1016376, #1042582
    • autopkgtest for openjdk-19/19.0.2+7-4: 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: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Impossible Build-Depends(-Arch): openjdk-19 -> libgtk-3-0/3.24.41-1/armel
    • Impossible Build-Depends(-Arch): openjdk-19 -> libgtk-3-0/3.24.41-1/armhf
    • Impossible Depends: openjdk-19 -> libasound2/1.2.10-3/armel
    • Impossible Depends: openjdk-19 -> libasound2/1.2.10-3/armhf
    • Impossible Depends: openjdk-19 -> libcups2/2.4.7-1+b1/armel
    • Impossible Depends: openjdk-19 -> libcups2/2.4.7-1+b1/armhf
    • Impossible Depends: openjdk-19 -> libglib2.0-0/2.78.4-1/armel
    • Impossible Depends: openjdk-19 -> libglib2.0-0/2.78.4-1/armhf
    • Impossible Depends: openjdk-19 -> libgtk-3-0/3.24.41-1/armel
    • Impossible Depends: openjdk-19 -> libgtk-3-0/3.24.41-1/armhf
    • Impossible Depends: openjdk-19 -> libpng16-16/1.6.43-1/armel
    • Impossible Depends: openjdk-19 -> libpng16-16/1.6.43-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-19.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 436 days old (needed 5 days)
• r-cran-sftime (- to 0.2-0-6)
  • Migration status for r-cran-sftime (- to 0.2-0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-sftime r-cran-sf (not considered)
    • Depends: r-cran-sftime r-cran-sf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sftime.html
    • autopkgtest for r-cran-sftime/0.2-0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 436 days old (needed 5 days)
• cura (- to 5.0.0-3)
  • Migration status for cura (- to 5.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cura would introduce bugs in testing: #1076871
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cura.html
    • Reproducible on armhf - info ♻
    • 438 days old (needed 5 days)
    • Remove hint for (transitive) dependency: sentry-python
• binutils-msp430 (- to 2.40.50~ti1)
  • Migration status for binutils-msp430 (- to 2.40.50~ti1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils-msp430 would introduce bugs in testing: #1042343, #1080505
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-msp430.html
    • 439 days old (needed 5 days)
• freecol (- to 1.1.0-1)
  • Migration status for freecol (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freecol would introduce bugs in testing: #1073467
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freecol.html
    • Reproducible on armhf - info ♻
    • 439 days old (needed 5 days)
• printrun (- to 2.0.1-1)
  • Migration status for printrun (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating printrun would introduce bugs in testing: #1050157
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/printrun.html
    • autopkgtest for printrun/2.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 439 days old (needed 2 days)
• apt-clone (- to 0.4.3+nmu2)
  • Migration status for apt-clone (- to 0.4.3+nmu2): 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+nmu2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for apt-clone/n/a: riscv64: 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 ♻
    • 440 days old (needed 5 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
    • Reproducible on armhf - info ♻
    • 440 days old (needed 5 days)
• apertium-all-dev (- to 3.8.1-3)
  • Migration status for apertium-all-dev (- to 3.8.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: apertium-all-dev hfst (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-all-dev.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 443 days old (needed 5 days)
• migrate (- to 0.13.0-4)
  • Migration status for migrate (- to 0.13.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating migrate would introduce bugs in testing: #1074659
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/migrate.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 443 days old (needed 5 days)
• ruby-rack-session (- to 2.0.0-1)
  • Migration status for ruby-rack-session (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-rack-session.html
    • ruby-rack-session unsatisfiable Build-Depends(-Arch) on amd64: ruby-rack (>= 3.0.0~)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 444 days old (needed 5 days)
• ruby-rackup (- to 2.1.0-1)
  • Migration status for ruby-rackup (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-rackup.html
    • ruby-rackup unsatisfiable Build-Depends(-Arch) on amd64: ruby-rack (>= 3.0.0~)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 444 days old (needed 5 days)
• r-cran-sparr (- to 2.3-10-1)
  • Migration status for r-cran-sparr (- to 2.3-10-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-sparr r-cran-spatstat (not considered)
    • Depends: r-cran-sparr r-cran-spatstat (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sparr.html
    • autopkgtest for r-cran-sparr/2.3-10-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
    • 445 days old (needed 2 days)
• rabbit (- to 3.0.2-1)
  • Migration status for rabbit (- to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rabbit would introduce bugs in testing: #1077124
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rabbit.html
    • autopkgtest for rabbit/3.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
    • 446 days old (needed 2 days)
• foxtrotgps (- to 1.2.2+bzr332-1)
  • Migration status for foxtrotgps (- to 1.2.2+bzr332-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): foxtrotgps libglade2 (not considered)
    • Depends: foxtrotgps libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foxtrotgps.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 448 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
    • 451 days old (needed 2 days)
• xserver-xorg-video-qxl (- to 0.1.6-1)
  • Migration status for xserver-xorg-video-qxl (- to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-qxl would introduce bugs in testing: #1042862
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-qxl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 451 days old (needed 5 days)
• clipper (- to 2.1.20201109-2)
  • Migration status for clipper (- to 2.1.20201109-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): clipper libccp4 (not considered)
    • Depends: clipper libccp4 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clipper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 452 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-netgroups gosa (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 452 days old (needed 5 days)
• python-django-ical (- to 1.9.2-1)
  • Migration status for python-django-ical (- to 1.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-ical would introduce bugs in testing: #1052796
    • autopkgtest for python-django-ical/1.9.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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
    • 452 days old (needed 5 days)
• golang-github-gonvenience-ytbx (- to 1.4.4-1)
  • Migration status for golang-github-gonvenience-ytbx (- to 1.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by czchen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gonvenience-ytbx.html
    • autopkgtest for golang-github-gonvenience-ytbx/1.4.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 453 days old (needed 2 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
    • Reproducible on armhf - info ♻
    • 453 days old (needed 5 days)
• octave-database (- to 2.4.4-8)
  • Migration status for octave-database (- to 2.4.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octave-database would introduce bugs in testing: #1004158
    • autopkgtest for octave-database/2.4.4-8: amd64: Regression or new test ♻, arm64: 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/o/octave-database.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 453 days old (needed 5 days)
• octave-tisean (- to 0.2.3.hg.2021.11.29-1)
  • Migration status for octave-tisean (- to 0.2.3.hg.2021.11.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • octave-tisean/amd64 has unsatisfiable dependency
    • octave-tisean/mips64el has unsatisfiable dependency
    • Updating octave-tisean would introduce bugs in testing: #1080045, #874116
    • missing build on armel
    • missing build on s390x
    • arch:armel not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/octave-tisean.html
    • uninstallable on arch amd64, not running autopkgtest there
    • 453 days old (needed 5 days)
• xmodem (- to 0.4.7+dfsg-1)
  • Migration status for xmodem (- to 0.4.7+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): xmodem lrzsz (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmodem.html
    • autopkgtest for xmodem/0.4.7+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 453 days old (needed 5 days)
• python-udatetime (- to 0.0.17-1)
  • Migration status for python-udatetime (- to 0.0.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-udatetime would introduce bugs in testing: #1069519
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-udatetime.html
    • autopkgtest for python-udatetime/0.0.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 ♻
    • 454 days old (needed 5 days)
• sequeler (- to 0.8.2-1)
  • Migration status for sequeler (- to 0.8.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sequeler libgda5 (not considered)
    • Depends: sequeler libgda5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sequeler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 454 days old (needed 5 days)
• python-pyvmomi (- to 6.7.1-6)
  • Migration status for python-pyvmomi (- to 6.7.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyvmomi would introduce bugs in testing: #1052793
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyvmomi.html
    • 455 days old (needed 5 days)
• liboqs (- to 0.8.0-1)
  • Migration status for liboqs (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liboqs would introduce bugs in testing: #1000303, #1065802, #1073250
    • Impossible Depends: liboqs -> libssl3/3.1.5-1/armel
    • Impossible Depends: liboqs -> libssl3/3.1.5-1/armhf
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/liboqs.html
    • 456 days old (needed 5 days)
• simutrans (- to 123.0.1-3)
  • Migration status for simutrans (- to 123.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simutrans would introduce bugs in testing: #1076693
    • Impossible Depends: simutrans -> libminiupnpc17/2.2.6-1+b1/amd64
    • Impossible Depends: simutrans -> libminiupnpc17/2.2.6-1+b1/arm64
    • Impossible Depends: simutrans -> libminiupnpc17/2.2.6-1+b1/armel
    • Impossible Depends: simutrans -> libminiupnpc17/2.2.6-1+b1/armhf
    • Impossible Depends: simutrans -> libminiupnpc17/2.2.6-1+b1/i386
    • Impossible Depends: simutrans -> libminiupnpc17/2.2.6-1+b1/mips64el
    • Impossible Depends: simutrans -> libminiupnpc17/2.2.6-1+b1/ppc64el
    • Impossible Depends: simutrans -> libminiupnpc17/2.2.6-1+b1/s390x
    • Depends: simutrans simutrans-pak64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simutrans.html
    • Reproducible on armhf - info ♻
    • 456 days old (needed 5 days)
• smarty3 (- to 3.1.48-1)
  • Migration status for smarty3 (- to 3.1.48-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smarty3 would introduce bugs in testing: #1072530
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smarty3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 456 days old (needed 5 days)
• smarty4 (- to 4.3.1-1)
  • Migration status for smarty4 (- to 4.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smarty4 would introduce bugs in testing: #1072529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smarty4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 456 days old (needed 5 days)
• pcb (- to 1:4.3.0-3)
  • Migration status for pcb (- to 1:4.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pcb would introduce bugs in testing: #1081090
    • Build-Depends(-Arch): pcb gtkglext (not considered)
    • Depends: pcb gtkglext (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcb.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 457 days old (needed 5 days)
• rust-hdrhistogram (- to 7.5.2-1)
  • Migration status for rust-hdrhistogram (- to 7.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-hdrhistogram would introduce bugs in testing: #1014034, #1080406
    • autopkgtest for rust-hdrhistogram/7.5.2-1: amd64: Pass, arm64: Pass, armel: Pass, 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/r/rust-hdrhistogram.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 457 days old (needed 5 days)
• ruby-jekyll-remote-theme (- to 0.4.3-4)
  • Migration status for ruby-jekyll-remote-theme (- to 0.4.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-remote-theme would introduce bugs in testing: #1031548, #1032541
    • autopkgtest for ruby-jekyll-remote-theme/0.4.3-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): ruby-jekyll-remote-theme ruby-jekyll-github-metadata (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-remote-theme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 458 days old (needed 5 days)
• ruby-ruby-magic-static (- to 0.6.0-2)
  • Migration status for ruby-ruby-magic-static (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-ruby-magic-static/armel has unsatisfiable dependency
    • ruby-ruby-magic-static/armhf has unsatisfiable dependency
    • Updating ruby-ruby-magic-static would introduce bugs in testing: #1052749
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • autopkgtest for ruby-ruby-magic-static/0.6.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ruby-magic-static.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 459 days old (needed 5 days)
• mlterm (- to 3.9.3-1)
  • Migration status for mlterm (- to 3.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mlterm would introduce bugs in testing: #1075281
    • Build-Depends(-Arch): mlterm freewnn (not considered)
    • Depends: mlterm freewnn (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlterm.html
    • 468 days old (needed 5 days)
• buildstream (- to 1.6.9-1)
  • Migration status for buildstream (- to 1.6.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating buildstream would introduce bugs in testing: #1074674
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/buildstream.html
    • 478 days old (needed 5 days)
• dvi2ps-fontdata (- to 1.0.1-3.2)
  • Migration status for dvi2ps-fontdata (- to 1.0.1-3.2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: dvi2ps-fontdata dvi2dvi (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvi2ps-fontdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 481 days old (needed 5 days)
• twinkle (- to 1:1.10.2+dfsg-2)
  • Migration status for twinkle (- to 1:1.10.2+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): twinkle ucommon (not considered)
    • Depends: twinkle ucommon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): twinkle libccrtp
    • Depends: twinkle libccrtp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/twinkle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 482 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
    • Reproducible on armhf - info ♻
    • 485 days old (needed 5 days)
• libapache-mod-auth-radius (- to 1.5.8-2)
  • Migration status for libapache-mod-auth-radius (- to 1.5.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache-mod-auth-radius would introduce bugs in testing: #1075137
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache-mod-auth-radius.html
    • Reproducible on armhf - info ♻
    • 486 days old (needed 5 days)
• gnome-dvb-daemon (- to 1:0.2.91~git20170110-5)
  • Migration status for gnome-dvb-daemon (- to 1:0.2.91~git20170110-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-dvb-daemon would introduce bugs in testing: #1075024
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-dvb-daemon.html
    • Reproducible on armhf - info ♻
    • 487 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
    • 487 days old (needed 5 days)
• bazel-bootstrap (- to 4.2.3+ds-9)
  • Migration status for bazel-bootstrap (- to 4.2.3+ds-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bazel-bootstrap/amd64 has unsatisfiable dependency
    • bazel-bootstrap/arm64 has unsatisfiable dependency
    • bazel-bootstrap/mips64el has unsatisfiable dependency
    • bazel-bootstrap/ppc64el has unsatisfiable dependency
    • bazel-bootstrap/s390x has unsatisfiable dependency
    • Updating bazel-bootstrap would introduce bugs in testing: #1057490, #1068202
    • autopkgtest for bazel-bootstrap/4.2.3+ds-9: riscv64: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bazel-bootstrap.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 ♻
    • 488 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/s390x has unsatisfiable dependency
    • Updating ogmrip would introduce bugs in testing: #1074275
  • Additional info:
    • Piuparts tested OK - 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 s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 488 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
    • Build-Depends(-Arch): tuxmath t4kcommon (not considered)
    • Depends: tuxmath t4kcommon (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tuxmath.html
    • Reproducible on armhf - info ♻
    • 490 days old (needed 5 days)
• ruby-ruby-openai (- to 3.7.0-2)
  • Migration status for ruby-ruby-openai (- to 3.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ruby-openai.html
    • autopkgtest for ruby-ruby-openai/3.7.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 491 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:
    • Updating mate-equake-applet would introduce bugs in testing: #1066183
    • Impossible Depends: mate-equake-applet -> libglib2.0-0/2.78.4-1/armel
    • Impossible Depends: mate-equake-applet -> libglib2.0-0/2.78.4-1/armhf
    • Impossible Depends: mate-equake-applet -> libgtk-3-0/3.24.41-1/armel
    • Impossible Depends: mate-equake-applet -> libgtk-3-0/3.24.41-1/armhf
    • Depends: mate-equake-applet curl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-equake-applet.html
    • 494 days old (needed 5 days)
• libanyevent-riperedis-perl (- to 0.48-1)
  • Migration status for libanyevent-riperedis-perl (- to 0.48-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by az, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libanyevent-riperedis-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 496 days old (needed 5 days)
• matomo-component-network (- to 2.0.1-1)
  • Migration status for matomo-component-network (- to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-component-network.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 496 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
    • 498 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
    • Reproducible on armhf - info ♻
    • 504 days old (needed 5 days)
• hfst (- to 3.16.0-5)
  • Migration status for hfst (- to 3.16.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hfst would introduce bugs in testing: #1075066
    • Build-Depends(-Arch): hfst openfst (not considered)
    • Depends: hfst openfst (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hfst.html
    • Reproducible on armhf - info ♻
    • 505 days old (needed 5 days)
• php-maxmind-web-service-common (- to 0.9.0-1)
  • Migration status for php-maxmind-web-service-common (- to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-maxmind-web-service-common.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 510 days old (needed 5 days)
• image-factory (- to 1.0.2-1.1)
  • Migration status for image-factory (- to 1.0.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating image-factory would introduce bugs in testing: #1060982
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/image-factory.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 513 days old (needed 5 days)
• covered (- to 0.7.10-4)
  • Migration status for covered (- to 0.7.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating covered would introduce bugs in testing: #1078009
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/covered.html
    • Reproducible on armhf - info ♻
    • 515 days old (needed 5 days)
• php-jshrink (- to 1.6.5-1)
  • Migration status for php-jshrink (- to 1.6.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-jshrink.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 517 days old (needed 5 days)
• php-sparkline (- to 2.2.0-1)
  • Migration status for php-sparkline (- to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sparkline would introduce bugs in testing: #1034403
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sparkline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 521 days old (needed 5 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
    • 525 days old (needed 5 days)
• ucblogo (- to 6.2.4-1)
  • Migration status for ucblogo (- to 6.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ucblogo would introduce bugs in testing: #1075594
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ucblogo.html
    • Reproducible on armhf - info ♻
    • 532 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocrfeeder.html
    • Reproducible on armhf - info ♻
    • 538 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
    • 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
    • 541 days old (needed 5 days)
• ldaptive (- to 2.1.1+ds-1)
  • Migration status for ldaptive (- to 2.1.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jello, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ldaptive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 547 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
    • 551 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 flask-security (not considered)
    • 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 ♻
    • 553 days old (needed 5 days)
    • Remove hint for (transitive) dependency: flask-babel, flask-security, flask-wtf
• igdiscover (- to 0.11-4)
  • Migration status for igdiscover (- to 0.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating igdiscover would introduce bugs in testing: #1032975, #1081341
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/igdiscover.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for igdiscover/0.11-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • 554 days old (needed 5 days)
• ganeti (- to 3.0.2-3)
  • Migration status for ganeti (- to 3.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ganeti would introduce bugs in testing: #1042264
    • Build-Depends(-Arch): ganeti haskell-regex-pcre (not considered)
    • Depends: ganeti curl (not considered)
    • Depends: ganeti pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganeti.html
    • autopkgtest for ganeti/3.0.2-3: amd64: Ignored failure, arm64: Ignored failure, armel: Ignored failure, armhf: Ignored failure, i386: Ignored failure, ppc64el: Ignored failure, s390x: Ignored failure
    • 557 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 espresso (not considered)
    • Invalidated by dependency
    • Depends: debian-pan mathgl (not considered)
  • 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 ♻
    • 558 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, #1073430
  • 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 ♻
    • 561 days old (needed 5 days)
• ktp-accounts-kcm (- to 22.12.3-1)
  • Migration status for ktp-accounts-kcm (- to 22.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-accounts-kcm telepathy-logger (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): ktp-accounts-kcm ktp-common-internals (not considered)
    • Build-Depends(-Arch): ktp-accounts-kcm telepathy-logger-qt (not considered)
    • Depends: ktp-accounts-kcm ktp-common-internals (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-accounts-kcm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
• ktp-approver (- to 22.12.3-1)
  • Migration status for ktp-approver (- to 22.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-approver telepathy-logger-qt (not considered)
    • Invalidated by build-dependency
    • Depends: ktp-approver ktp-common-internals (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-approver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
• ktp-auth-handler (- to 22.12.3-1)
  • Migration status for ktp-auth-handler (- to 22.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-auth-handler telepathy-logger-qt (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): ktp-auth-handler ktp-common-internals (not considered)
    • Depends: ktp-auth-handler ktp-common-internals (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-auth-handler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
• ktp-call-ui (- to 22.12.3-1)
  • Migration status for ktp-call-ui (- to 22.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-call-ui telepathy-logger-qt (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): ktp-call-ui ktp-common-internals (not considered)
    • Depends: ktp-call-ui ktp-common-internals (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-call-ui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
• ktp-common-internals (- to 22.12.3-1)
  • Migration status for ktp-common-internals (- to 22.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-common-internals telepathy-logger-qt (not considered)
    • Depends: ktp-common-internals telepathy-logger-qt (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-common-internals.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• ktp-contact-list (- to 22.12.3-1)
  • Migration status for ktp-contact-list (- to 22.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-contact-list telepathy-logger (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): ktp-contact-list ktp-common-internals (not considered)
    • Build-Depends(-Arch): ktp-contact-list telepathy-logger-qt (not considered)
    • Depends: ktp-contact-list ktp-common-internals (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-contact-list.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
• ktp-contact-runner (- to 22.12.3-1)
  • Migration status for ktp-contact-runner (- to 22.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-contact-runner telepathy-logger-qt (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): ktp-contact-runner ktp-common-internals (not considered)
    • Depends: ktp-contact-runner ktp-common-internals (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-contact-runner.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
• ktp-desktop-applets (- to 22.12.3-1)
  • Migration status for ktp-desktop-applets (- to 22.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-desktop-applets ktp-common-internals (not considered)
    • Depends: ktp-desktop-applets ktp-common-internals (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-desktop-applets.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
• ktp-filetransfer-handler (- to 22.12.3-1)
  • Migration status for ktp-filetransfer-handler (- to 22.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-filetransfer-handler telepathy-logger-qt (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): ktp-filetransfer-handler ktp-common-internals (not considered)
    • Depends: ktp-filetransfer-handler ktp-common-internals (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-filetransfer-handler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
• ktp-kded-integration-module (- to 22.12.3-1)
  • Migration status for ktp-kded-integration-module (- to 22.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-kded-integration-module telepathy-logger-qt (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): ktp-kded-integration-module ktp-common-internals (not considered)
    • Depends: ktp-kded-integration-module ktp-common-internals (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-kded-integration-module.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
• ktp-send-file (- to 22.12.3-1)
  • Migration status for ktp-send-file (- to 22.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-send-file telepathy-logger-qt (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): ktp-send-file ktp-common-internals (not considered)
    • Depends: ktp-send-file ktp-common-internals (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-send-file.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 days old (needed 5 days)
• ktp-text-ui (- to 22.12.3-1)
  • Migration status for ktp-text-ui (- to 22.12.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ktp-text-ui telepathy-logger (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): ktp-text-ui ktp-common-internals (not considered)
    • Build-Depends(-Arch): ktp-text-ui telepathy-logger-qt (not considered)
    • Depends: ktp-text-ui ktp-common-internals (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktp-text-ui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 562 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: #1032166
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-timeline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 563 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 aubio (not considered)
    • Depends: denemo aubio (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/denemo.html
    • Reproducible on armhf - info ♻
    • 564 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)
    • Build-Depends(-Arch): vart xrt (not considered)
    • Depends: vart xir (not considered)
    • Depends: vart xrt (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vart.html
    • 564 days old (needed 5 days)
• xrt (- to 202210.2.13.466+dfsg-8)
  • Migration status for xrt (- to 202210.2.13.466+dfsg-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xrt would introduce bugs in testing: #1037903
    • Depends: xrt boost1.74 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xrt.html
    • 564 days old (needed 5 days)
• lgeneral (- to 1.4.4-2)
  • Migration status for lgeneral (- to 1.4.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lgeneral would introduce bugs in testing: #1066397
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lgeneral.html
    • 566 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
    • 568 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)
    • 568 days old (needed 5 days)
• vertx-docgen (- to 0.9.4-2)
  • Migration status for vertx-docgen (- to 0.9.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vertx-docgen openjdk-11 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vertx-docgen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 568 days old (needed 5 days)
• zoneminder (- to 1.36.33+dfsg1-1)
  • Migration status for zoneminder (- to 1.36.33+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zoneminder would introduce bugs in testing: #1072464, #999919
    • Impossible Depends: zoneminder -> libavformat-extra60/7:6.1.1-5+b1/armhf
    • Impossible Depends: zoneminder -> libavformat-extra60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: zoneminder -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: zoneminder -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: zoneminder -> libavformat60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: zoneminder -> libavformat60/7:6.1.1-5+b1/s390x
    • Build-Depends(-Arch): zoneminder pcre3 (not considered)
    • Depends: zoneminder pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zoneminder.html
    • Reproducible on armhf - info ♻
    • 568 days old (needed 5 days)
• droidlysis (- to 3.4.1-1)
  • Migration status for droidlysis (- to 3.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: droidlysis procyon (not considered)
    • Invalidated by dependency
    • Depends: droidlysis androguard
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/droidlysis.html
    • autopkgtest for droidlysis/3.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
    • 570 days old (needed 2 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
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/fava.html
    • Build-Depends(-Arch): fava flask-babel (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 s390x (which is allowed), not running autopkgtest there
    • 570 days old (needed 5 days)
    • Remove hint for (transitive) dependency: flask-babel
• golang-github-crewjam-saml (- to 0.4.12-2)
  • Migration status for golang-github-crewjam-saml (- to 0.4.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-crewjam-saml would introduce bugs in testing: #1033753, #1033864, #1054223
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-crewjam-saml.html
    • autopkgtest for golang-github-crewjam-saml/0.4.12-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 570 days old (needed 2 days)
• python-lua (- to 0.6-1)
  • Migration status for python-lua (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-lua/0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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 ♻
    • 571 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
    • Reproducible on armhf - info ♻
    • 573 days old (needed 5 days)
• afnix (- to 3.8.0-1)
  • Migration status for afnix (- to 3.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating afnix would introduce bugs in testing: #1031749, #1037570
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/afnix.html
    • 576 days old (needed 5 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
    • Depends: alien-arena curl (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 576 days old (needed 5 days)
• facet-analyser (- to 0.0~git20221121142040.6be10b8+ds1-3)
  • Migration status for facet-analyser (- to 0.0~git20221121142040.6be10b8+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • facet-analyser/amd64 has unsatisfiable dependency
    • Updating facet-analyser would introduce bugs in testing: #1040334
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/facet-analyser.html
  • 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 ♻
    • 577 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
  • 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
    • 578 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/s390x has unsatisfiable dependency
    • Updating dogtag-pki would introduce bugs in testing: #1054480, #1065850
    • 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
    • autopkgtest for dogtag-pki/11.2.1-2: riscv64: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): dogtag-pki tomcatjss (not considered)
  • 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 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 ♻
    • 582 days old (needed 5 days)
• php-horde-wicked (- to 2.0.8-9)
  • Migration status for php-horde-wicked (- to 2.0.8-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-wicked php-horde-rpc (not considered)
    • Invalidated by dependency
    • Depends: php-horde-wicked php-horde
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-wicked.html
    • autopkgtest for php-horde-wicked/2.0.8-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 582 days old (needed 2 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/s390x has unsatisfiable dependency
    • Updating pytorch-audio would introduce bugs in testing: #1071137
    • autopkgtest for pytorch-audio/0.13.1-1: ppc64el: Regression or new test ♻
    • Impossible Depends: pytorch-audio -> libavdevice60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: pytorch-audio -> libavfilter-extra9/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: pytorch-audio -> libavformat60/7:6.1.1-5+b1/ppc64el
    • Build-Depends(-Arch): pytorch-audio pytorch (not considered)
    • Depends: pytorch-audio python3.11_pu (not considered)
    • Depends: pytorch-audio pytorch (not considered)
  • 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 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 ♻
    • 582 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
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/a/adv-17v35x.html
    • 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:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 583 days old (needed 5 days)
• ruby-jekyll-github-metadata (- to 2.15.0-1)
  • Migration status for ruby-jekyll-github-metadata (- to 2.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-github-metadata would introduce bugs in testing: #1037529, #1059710
    • autopkgtest for ruby-jekyll-github-metadata/2.15.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-jekyll-github-metadata.html
    • 583 days old (needed 5 days)
• haskell-raaz (- to 0.2.1-2.1)
  • Migration status for haskell-raaz (- to 0.2.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-raaz-dev/amd64 has unsatisfiable dependency
    • libghc-raaz-doc/amd64 has unsatisfiable dependency
    • libghc-raaz-prof/amd64 has unsatisfiable dependency
    • libghc-raaz-dev/arm64 has unsatisfiable dependency
    • libghc-raaz-doc/arm64 has unsatisfiable dependency
    • libghc-raaz-prof/arm64 has unsatisfiable dependency
    • libghc-raaz-dev/armel has unsatisfiable dependency
    • libghc-raaz-prof/armel has unsatisfiable dependency
    • libghc-raaz-dev/armhf has unsatisfiable dependency
    • libghc-raaz-prof/armhf has unsatisfiable dependency
    • libghc-raaz-dev/i386 has unsatisfiable dependency
    • libghc-raaz-prof/i386 has unsatisfiable dependency
    • libghc-raaz-dev/mips64el has unsatisfiable dependency
    • libghc-raaz-prof/mips64el has unsatisfiable dependency
    • libghc-raaz-dev/ppc64el has unsatisfiable dependency
    • libghc-raaz-prof/ppc64el has unsatisfiable dependency
    • libghc-raaz-dev/s390x has unsatisfiable dependency
    • libghc-raaz-prof/s390x has unsatisfiable dependency
    • Updating haskell-raaz would introduce bugs in testing: #1053980, #1054978
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • haskell-raaz unsatisfiable Build-Depends(-Arch) on 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 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 ♻
    • 584 days old (needed 5 days)
• padatious (- to 0.4.8-2.1)
  • Migration status for padatious (- to 0.4.8-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating padatious would introduce bugs in testing: #1066733
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/padatious.html
    • autopkgtest for padatious/0.4.8-2.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 584 days old (needed 5 days)
• ruby-clockwork (- to 3.0.1-1)
  • Migration status for ruby-clockwork (- to 3.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-clockwork would introduce bugs in testing: #1066730
    • autopkgtest for ruby-clockwork/3.0.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/r/ruby-clockwork.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 584 days old (needed 5 days)
• sagemath (- to 9.5-6)
  • Migration status for sagemath (- to 9.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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: 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: 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: jupyter-nbextension-jupyter-js-widgets
    • Build-Depends(-Arch): sagemath brial (not considered)
    • Build-Depends(-Arch): sagemath eclib (not considered)
    • Build-Depends(-Arch): sagemath palp (not considered)
    • Build-Depends(-Arch): sagemath pcre3 (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 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 ♻
    • 584 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/s390x has unsatisfiable dependency
    • Updating segyio would introduce bugs in testing: #1055728
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/segyio.html
    • autopkgtest for segyio/1.8.3-1.2: riscv64: Regression or new test ♻
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • 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
    • 584 days old (needed 5 days)
• bacula-doc (- to 9.6.7-2)
  • Migration status for bacula-doc (- to 9.6.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bacula-doc would introduce bugs in testing: #1073463
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bacula-doc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 585 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 ipyparallel (not considered)
    • Depends: hyperspy numba (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 ♻
    • 585 days old (needed 5 days)
• ruby-gitlab-markup (- to 1.9.0-1)
  • Migration status for ruby-gitlab-markup (- to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gitlab-markup would introduce bugs in testing: #1053838
    • autopkgtest for ruby-gitlab-markup/1.9.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): ruby-gitlab-markup ruby-html-pipeline (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-markup.html
    • Reproducible on armhf - info ♻
    • 585 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
    • 585 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 ♻
    • 586 days old (needed 5 days)
• python-aioxmpp (- to 0.13.3-1)
  • Migration status for python-aioxmpp (- to 0.13.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aioxmpp would introduce bugs in testing: #1042239
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioxmpp.html
    • 586 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 ♻
    • 586 days old (needed 5 days)
• eclipse-wtp (- to 3.18-6)
  • Migration status for eclipse-wtp (- to 3.18-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eclipse-wtp would introduce bugs in testing: #1076877
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-wtp.html
    • autopkgtest for eclipse-wtp/3.18-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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 587 days old (needed 5 days)
• gfpoken (- to 1-4)
  • Migration status for gfpoken (- to 1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gfpoken would introduce bugs in testing: #1081126
    • Build-Depends(-Arch): gfpoken blender
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfpoken.html
    • 587 days old (needed 5 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
    • Reproducible on armhf - info ♻
    • 587 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 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 ♻
    • 587 days old (needed 5 days)
• density-fitness (- to 1.0.8-4)
  • Migration status for density-fitness (- to 1.0.8-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): density-fitness libpdb-redo (not considered)
    • Depends: density-fitness libpdb-redo (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: density-fitness clipper
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/density-fitness.html
    • autopkgtest for density-fitness/1.0.8-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
    • 588 days old (needed 2 days)
• freesas (- to 0.9.0-6)
  • Migration status for freesas (- to 0.9.0-6): 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
    • Updating freesas would introduce bugs in testing: #1069225
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/freesas.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
    • 588 days old (needed 5 days)
• haskell-diagrams (- to 1.4.0.1-1)
  • Migration status for haskell-diagrams (- to 1.4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-diagrams would introduce bugs in testing: #1057716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-diagrams.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 588 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 ♻
    • 588 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
    • Depends: php-horde-imp php-horde
    • Depends: php-horde-imp php-horde-editor (not considered)
    • Depends: php-horde-imp php-horde-mail-autoconfig (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-imp.html
    • autopkgtest for php-horde-imp/6.2.27-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 588 days old (needed 2 days)
• scmutils (- to 0~20230125+dfsg-1)
  • Migration status for scmutils (- to 0~20230125+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): scmutils mit-scheme (not considered)
    • Depends: scmutils mit-scheme (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scmutils.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 ♻
    • 588 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:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Updating kotlinx-atomicfu would introduce bugs in testing: #1078395
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kotlinx-atomicfu.html
    • Reproducible on armhf - info ♻
    • 589 days old (needed 5 days)
    • Remove hint for (transitive) dependency: kotlinx-atomicfu
• 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:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Updating kotlinx-coroutines would introduce bugs in testing: #1078414
    • Build-Depends(-Arch): kotlinx-coroutines kotlinx-atomicfu (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kotlinx-coroutines.html
    • Reproducible on armhf - info ♻
    • 589 days old (needed 5 days)
    • Remove hint for (transitive) dependency: kotlinx-coroutines
• libpdb-redo (- to 3.0.5-2)
  • Migration status for libpdb-redo (- to 3.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): libpdb-redo libccp4 (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): libpdb-redo clipper
    • Depends: libpdb-redo clipper
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpdb-redo.html
    • autopkgtest for libpdb-redo/3.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
    • 589 days old (needed 2 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: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polyml.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 589 days old (needed 5 days)
• smb2www (- to 980804-45)
  • Migration status for smb2www (- to 980804-45): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smb2www would introduce bugs in testing: #1072608
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smb2www.html
    • 590 days old (needed 5 days)
• gnome-photos (- to 43.0-2)
  • Migration status for gnome-photos (- to 43.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnome-photos/armel has unsatisfiable dependency
    • gnome-photos-tests/armel has unsatisfiable dependency
    • gnome-photos/armhf has unsatisfiable dependency
    • gnome-photos-tests/armhf has unsatisfiable dependency
    • Updating gnome-photos would introduce bugs in testing: #1040202, #1040746
    • autopkgtest for gnome-photos/43.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-photos.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 591 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
    • 591 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-pwreset gosa (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 592 days old (needed 5 days)
• psi4 (- to 1:1.3.2+dfsg-5)
  • Migration status for psi4 (- to 1:1.3.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for psi4/1:1.3.2+dfsg-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, 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
    • 593 days old (needed 5 days)
• binutils-m68hc1x (- to 1:3.5.0)
  • Migration status for binutils-m68hc1x (- to 1:3.5.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils-m68hc1x would introduce bugs in testing: #1042317
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-m68hc1x.html
    • 594 days old (needed 5 days)
• mvdsv (- to 0.35-6)
  • Migration status for mvdsv (- to 0.35-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mvdsv would introduce bugs in testing: #1050187
    • Build-Depends(-Arch): mvdsv pcre3 (not considered)
    • Depends: mvdsv pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mvdsv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 594 days old (needed 5 days)
• valentina (- to 0.7.52~dfsg-1)
  • Migration status for valentina (- to 0.7.52~dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating valentina would introduce bugs in testing: #1070900
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/valentina.html
    • autopkgtest for valentina/0.7.52~dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 594 days old (needed 2 days)
• php-horde (- to 5.2.23+debian0-6)
  • Migration status for php-horde (- to 5.2.23+debian0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde php-horde-rpc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 595 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gosa-plugins-mailaddress gosa (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 596 days old (needed 5 days)
• 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
    • Depends: ktx mvdsv (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktx.html
    • 596 days old (needed 5 days)
• ruby-faraday-middleware (- to 1.2.0-4)
  • Migration status for ruby-faraday-middleware (- to 1.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-faraday-middleware would introduce bugs in testing: #1025092
    • autopkgtest for ruby-faraday-middleware/1.2.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/r/ruby-faraday-middleware.html
    • 596 days old (needed 5 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 ♻
    • 597 days old (needed 5 days)
• php-horde-passwd (- to 5.0.7-9)
  • Migration status for php-horde-passwd (- to 5.0.7-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-passwd php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-passwd.html
    • autopkgtest for php-horde-passwd/5.0.7-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 597 days old (needed 2 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
    • Reproducible on armhf - info ♻
    • 598 days old (needed 5 days)
• ruby-aubio (- to 0.3.6-3)
  • Migration status for ruby-aubio (- to 0.3.6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-aubio aubio (not considered)
    • Depends: ruby-aubio aubio (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-aubio.html
    • autopkgtest for ruby-aubio/0.3.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 598 days old (needed 2 days)
• text-engine (- to 0.1.1-4)
  • Migration status for text-engine (- to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating text-engine would introduce bugs in testing: #1075566
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/text-engine.html
    • Reproducible on armhf - info ♻
    • 598 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
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 599 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 ♻
    • 599 days old (needed 5 days)
• lava (- to 2023.01-2)
  • Migration status for lava (- to 2023.01-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lava would introduce bugs in testing: #1041342, #1073729
    • autopkgtest for lava/2023.01-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Depends: lava djangorestframework-filters (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 ♻
    • 599 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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:
    • Updating vtk-dicom would introduce bugs in testing: #1063195
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vtk-dicom.html
    • autopkgtest for vtk-dicom/0.8.14-3.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 599 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
    • 600 days old (needed 5 days)
• sfepy (- to 2021.4-4)
  • Migration status for sfepy (- to 2021.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sfepy would introduce bugs in testing: #1056887
    • autopkgtest for sfepy/2021.4-4: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): sfepy python-sparse (not considered)
    • Depends: sfepy python-sparse (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sfepy.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 600 days old (needed 5 days)
• glirc (- to 2.39.0.1-1)
  • Migration status for glirc (- to 2.39.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glirc would introduce bugs in testing: #1054966
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on amd64: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on arm64: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on armel: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on armhf: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on i386: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vty-dev (<< 5.36)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-irc-core-dev (<< 2.12)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-lens-dev (<< 5.2)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
    • glirc unsatisfiable Build-Depends(-Arch) on s390x: libghc-vty-dev (<< 5.36)
    • Impossible Depends: glirc -> libssl3/3.0.14-1~deb12u2/armel
    • Impossible Depends: glirc -> libssl3/3.0.14-1~deb12u2/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glirc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 601 days old (needed 5 days)
• darcs (- to 2.16.5-1)
  • Migration status for darcs (- to 2.16.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating darcs would introduce bugs in testing: #1054953
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
    • Depends: darcs curl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/darcs.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 ♻
    • 602 days old (needed 5 days)
• scrcpy (- to 1.25-1)
  • Migration status for scrcpy (- to 1.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scrcpy would introduce bugs in testing: #1050097
    • autopkgtest for scrcpy/1.25-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Impossible Depends: scrcpy -> libavdevice60/7:6.1.1-5+b1/amd64
    • Impossible Depends: scrcpy -> libavdevice60/7:6.1.1-5+b1/arm64
    • Impossible Depends: scrcpy -> libavdevice60/7:6.1.1-5+b1/armel
    • Impossible Depends: scrcpy -> libavdevice60/7:6.1.1-5+b1/armhf
    • Impossible Depends: scrcpy -> libavdevice60/7:6.1.1-5+b1/i386
    • Impossible Depends: scrcpy -> libavdevice60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: scrcpy -> libavdevice60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: scrcpy -> libavdevice60/7:6.1.1-5+b1/s390x
    • Impossible Depends: scrcpy -> libavformat-extra60/7:6.1.1-5+b1/armhf
    • Impossible Depends: scrcpy -> libavformat-extra60/7:6.1.1-5+b1/s390x
    • Impossible Depends: scrcpy -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: scrcpy -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: scrcpy -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: scrcpy -> libavformat60/7:6.1.1-5+b1/ppc64el
    • Build-Depends-Indep: scrcpy android-framework-23 (not considered)
    • Build-Depends-Indep: scrcpy android-sdk-meta
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scrcpy.html
    • 602 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:
    • Updating janus would introduce bugs in testing: #1072424
    • autopkgtest for janus/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 ♻
    • Impossible Depends: janus -> libavformat-extra60/7:6.1.1-5+b1/armel
    • Impossible Depends: janus -> libavformat-extra60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: janus -> libavformat60/7:6.1.1-5+b1/armhf
    • Impossible Depends: janus -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: janus -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: janus -> libavformat60/7:6.1.1-5+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/janus.html
    • Reproducible on armhf - info ♻
    • 603 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
    • 604 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 malai (not considered)
    • Depends: latexdraw malai (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • 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 ♻
    • 605 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: Regression or new test ♻, 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/f/firejail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 606 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: Regression or new test ♻, arm64: Regression or new test ♻, 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/v/vim-ultisnips.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 606 days old (needed 5 days)
• mathomatic (- to 16.0.5-5)
  • Migration status for mathomatic (- to 16.0.5-5): Will attempt migration (Any information below is purely informational)
    • Build-Depends(-Arch): mathomatic rman
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mathomatic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 607 days old (needed 5 days)
• balsa (- to 2.6.4-2)
  • Migration status for balsa (- to 2.6.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for balsa/2.6.4-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): balsa libesmtp (not considered)
  • 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 ♻
    • 609 days old (needed 5 days)
• cumin (- to 4.2.0-1)
  • Migration status for cumin (- to 4.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cumin would introduce bugs in testing: #1042262
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cumin.html
    • 609 days old (needed 5 days)
• python-dtcwt (- to 0.12.0-5)
  • Migration status for python-dtcwt (- to 0.12.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-dtcwt would introduce bugs in testing: #1067329
    • autopkgtest for python-dtcwt/0.12.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/p/python-dtcwt.html
    • 609 days old (needed 5 days)
• jacal (- to 1c8-1)
  • Migration status for jacal (- to 1c8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: jacal slib (not considered)
    • Invalidated by dependency
    • Depends: jacal scm (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jacal.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 611 days old (needed 5 days)
• mit-scheme (- to 12.1-3)
  • Migration status for mit-scheme (- to 12.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mit-scheme would introduce bugs in testing: #1057426
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mit-scheme.html
    • 611 days old (needed 5 days)
• opencl-clang-14 (- to 14.0.0-4)
  • Migration status for opencl-clang-14 (- to 14.0.0-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): opencl-clang-14 spirv-llvm-translator-14 (not considered)
    • Depends: opencl-clang-14 spirv-llvm-translator-14 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): opencl-clang-14 llvm-toolchain-14 (not considered)
    • Depends: opencl-clang-14 llvm-toolchain-14 (not considered)
  • 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 ♻
    • 611 days old (needed 5 days)
• php-pinba (- to 1.1.2-16)
  • Migration status for php-pinba (- to 1.1.2-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-pinba would introduce bugs in testing: #1075384
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-pinba.html
    • Reproducible on armhf - info ♻
    • 611 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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)
    • 613 days old (needed 5 days)
• libobjcryst (- to 2022.1.4+ds1-2)
  • Migration status for libobjcryst (- to 2022.1.4+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libobjcryst newmat (not considered)
    • Depends: libobjcryst newmat (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): libobjcryst cctbx (not considered)
    • Depends: libobjcryst cctbx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libobjcryst.html
    • autopkgtest for libobjcryst/2022.1.4+ds1-2: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 614 days old (needed 2 days)
• pyobjcryst (- to 2.2.5-1)
  • Migration status for pyobjcryst (- to 2.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pyobjcryst/amd64 has unsatisfiable dependency
    • Updating pyobjcryst would introduce bugs in testing: #1081092
    • Build-Depends(-Arch): pyobjcryst libobjcryst
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pyobjcryst.html
    • uninstallable on arch amd64, not running autopkgtest there
    • 614 days old (needed 5 days)
• stimfit (- to 0.16.0-1.2)
  • Migration status for stimfit (- to 0.16.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • stimfit/amd64 has unsatisfiable dependency
    • stimfit/arm64 has unsatisfiable dependency
    • python3-stfio/armel has unsatisfiable dependency
    • stimfit/armel has unsatisfiable dependency
    • python3-stfio/armhf has unsatisfiable dependency
    • stimfit/armhf has unsatisfiable dependency
    • stimfit/i386 has unsatisfiable dependency
    • stimfit/mips64el has unsatisfiable dependency
    • stimfit/ppc64el has unsatisfiable dependency
    • stimfit/s390x has unsatisfiable dependency
    • Updating stimfit would introduce bugs in testing: #1068032
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/s/stimfit.html
    • Build-Depends(-Arch): stimfit sip4 (not considered)
    • Depends: stimfit python3.11_pu (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 s390x, not running autopkgtest there
    • 614 days old (needed 5 days)
• guessnet (- to 0.58)
  • Migration status for guessnet (- to 0.58): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): guessnet libwibble (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guessnet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 615 days old (needed 5 days)
• libwibble (- to 1.1-3)
  • Migration status for libwibble (- to 1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libwibble would introduce bugs in testing: #1070014
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libw/libwibble.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 615 days old (needed 5 days)
• python-srsly (- to 2.4.5-1)
  • Migration status for python-srsly (- to 2.4.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-srsly would introduce bugs in testing: #1056874
    • Build-Depends(-Arch): python-srsly python-catalogue
    • Depends: python-srsly python-catalogue
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-srsly.html
    • 615 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)
    • 617 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)
    • 617 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)
    • 617 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)
    • 617 days old (needed 5 days)
• php-horde-sesha (- to 1.0.0~rc3-9)
  • Migration status for php-horde-sesha (- to 1.0.0~rc3-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-sesha php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-sesha.html
    • autopkgtest for php-horde-sesha/1.0.0~rc3-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 617 days old (needed 2 days)
• tycho (- to 1.6.0-3)
  • Migration status for tycho (- to 1.6.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libtycho-java/amd64 has unsatisfiable dependency
    • libtycho-java/arm64 has unsatisfiable dependency
    • Updating tycho would introduce bugs in testing: #1031686, #1033428, #1050407
    • tycho unsatisfiable Build-Depends(-Arch) on amd64: libeclipse-osgi-util-java
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/tycho.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 617 days old (needed 5 days)
• nuitka (- to 1.3.5+ds-1)
  • Migration status for nuitka (- to 1.3.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nuitka would introduce bugs in testing: #1030440, #1035782
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nuitka.html
    • 618 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)
    • 618 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
    • Depends: php-horde-turba php-horde
    • Depends: php-horde-turba php-horde-dav
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-turba.html
    • autopkgtest for php-horde-turba/4.2.29-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 618 days old (needed 2 days)
• ruby-html-pipeline (- to 2.14.3-1)
  • Migration status for ruby-html-pipeline (- to 2.14.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-html-pipeline would introduce bugs in testing: #1053837
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-html-pipeline.html
    • autopkgtest for ruby-html-pipeline/2.14.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 618 days old (needed 2 days)
• ruby-task-list (- to 2.3.2-2)
  • Migration status for ruby-task-list (- to 2.3.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-task-list ruby-html-pipeline (not considered)
    • Depends: ruby-task-list ruby-html-pipeline (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-task-list.html
    • autopkgtest for ruby-task-list/2.3.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 618 days old (needed 2 days)
• php-horde-ingo (- to 3.2.16-9)
  • Migration status for php-horde-ingo (- to 3.2.16-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-ingo php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ingo.html
    • autopkgtest for php-horde-ingo/3.2.16-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 619 days old (needed 2 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
    • Reproducible on armhf - info ♻
    • 619 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
    • Depends: php-horde-kronolith php-horde
    • Depends: php-horde-kronolith php-horde-dav
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kronolith.html
    • autopkgtest for php-horde-kronolith/4.2.29-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 620 days old (needed 2 days)
• ruby-gh (- to 0.18.0-5)
  • Migration status for ruby-gh (- to 0.18.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-gh/amd64 has unsatisfiable dependency
    • ruby-gh/arm64 has unsatisfiable dependency
    • Updating ruby-gh would introduce bugs in testing: #1025090
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-gh.html
    • autopkgtest for ruby-gh/0.18.0-5: riscv64: Regression or new test ♻
    • Build-Depends(-Arch): ruby-gh ruby-faraday-middleware (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 s390x (which is allowed), not running autopkgtest there
    • 620 days old (needed 5 days)
• safeclib (- to 3.7.1-2)
  • Migration status for safeclib (- to 3.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating safeclib would introduce bugs in testing: #1042344, #1062879
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/safeclib.html
    • 621 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
    • 621 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
  • 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 ♻
    • 623 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
    • 624 days old (needed 5 days)
• tiemu (- to 3.04~git20220826.cda2db4+dfsg-2)
  • Migration status for tiemu (- to 3.04~git20220826.cda2db4+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tiemu would introduce bugs in testing: #1081105
    • Build-Depends(-Arch): tiemu libglade2 (not considered)
    • Depends: tiemu libglade2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiemu.html
    • Reproducible on armhf - info ♻
    • 624 days old (needed 5 days)
• eclipse-collections (- to 11.0.0.M3-3)
  • Migration status for eclipse-collections (- to 11.0.0.M3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eclipse-collections would introduce bugs in testing: #1031467
    • Build-Depends(-Arch): eclipse-collections tycho (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-collections.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 625 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:
    • Updating kbtin would introduce bugs in testing: #1061076
    • autopkgtest for kbtin/2.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Impossible Depends: kbtin -> libgnutls30/3.8.3-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kbtin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 626 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
    • Reproducible on armhf - info ♻
    • 627 days old (needed 5 days)
• bismuth (- to 3.1.4-4)
  • Migration status for bismuth (- to 3.1.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bismuth would introduce bugs in testing: #1071050
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bismuth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 628 days old (needed 5 days)
• php-horde-ansel (- to 3.0.10+debian1-3)
  • Migration status for php-horde-ansel (- to 3.0.10+debian1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-ansel php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ansel.html
    • autopkgtest for php-horde-ansel/3.0.10+debian1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 628 days old (needed 2 days)
• golang-github-bradenhilton-mozillainstallhash (- to 1.0.0-1)
  • Migration status for golang-github-bradenhilton-mozillainstallhash (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): golang-github-bradenhilton-mozillainstallhash golang-github-bradenhilton-cityhash (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bradenhilton-mozillainstallhash.html
    • autopkgtest for golang-github-bradenhilton-mozillainstallhash/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 629 days old (needed 2 days)
• gfm (- to 1.09~git20220826.71eaa92-1)
  • Migration status for gfm (- to 1.09~git20220826.71eaa92-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gfm libglade2 (not considered)
    • Depends: gfm libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 630 days old (needed 5 days)
• speedcrunch (- to 0.12.0-6)
  • Migration status for speedcrunch (- to 0.12.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): speedcrunch quark-sphinx-theme (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/speedcrunch.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 630 days old (needed 5 days)
• cpm (- to 0.32-1.5)
  • Migration status for cpm (- to 0.32-1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cpm/armel has unsatisfiable dependency
    • cpm/armhf has unsatisfiable dependency
    • Updating cpm would introduce bugs in testing: #851594
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpm.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 631 days old (needed 5 days)
• uwsgi-plugin-mongo (- to 0.0.9)
  • Migration status for uwsgi-plugin-mongo (- to 0.0.9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): uwsgi-plugin-mongo mongo-cxx-driver-legacy (not considered)
    • Depends: uwsgi-plugin-mongo mongo-cxx-driver-legacy (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uwsgi-plugin-mongo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 631 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
    • Reproducible on armhf - info ♻
    • 632 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 ♻
    • 632 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:
    • Updating alsa-oss would introduce bugs in testing: #1066825
    • Impossible Depends: alsa-oss -> libasound2/1.2.10-3/armel
    • Impossible Depends: alsa-oss -> libasound2/1.2.10-3/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/alsa-oss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 633 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
    • Reproducible on armhf - info ♻
    • 634 days old (needed 5 days)
• multiplex (- to 0.6.0-1)
  • Migration status for multiplex (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating multiplex would introduce bugs in testing: #1027462
    • autopkgtest for multiplex/0.6.0-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/m/multiplex.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 634 days old (needed 5 days)
• tpot (- to 0.11.7+dfsg-5)
  • Migration status for tpot (- to 0.11.7+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tpot would introduce bugs in testing: #1027205, #1071814
    • autopkgtest for tpot/0.11.7+dfsg-5: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): tpot pytorch (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tpot.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 ♻
    • 638 days old (needed 5 days)
• lodepng (- to 0.0~git20220618.b4ed2cd-3)
  • Migration status for lodepng (- to 0.0~git20220618.b4ed2cd-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lodepng would introduce bugs in testing: #1064557
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lodepng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 639 days old (needed 5 days)
• mujoco (- to 2.2.2-3)
  • Migration status for mujoco (- to 2.2.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mujoco lodepng (not considered)
    • Depends: mujoco lodepng (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mujoco.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 639 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 ♻
    • 643 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
    • Build-Depends(-Arch): atitvout libx86 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 644 days old (needed 5 days)
• bst-external (- to 0.29.0-2)
  • Migration status for bst-external (- to 0.29.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): bst-external buildstream (not considered)
    • Depends: bst-external buildstream (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bst-external.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 644 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 s390x (which is allowed), not running autopkgtest there
    • 644 days old (needed 5 days)
• python-certbot-dns-google (- to 2.0.0-2)
  • Migration status for python-certbot-dns-google (- to 2.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-google python-oauth2client (not considered)
    • Depends: python-certbot-dns-google python-oauth2client (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-google.html
    • autopkgtest for python-certbot-dns-google/2.0.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 645 days old (needed 5 days)
• golang-github-jesseduffield-rollrus (- to 0.0~git20190701.dd028cb-4)
  • Migration status for golang-github-jesseduffield-rollrus (- to 0.0~git20190701.dd028cb-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-rollrus would introduce bugs in testing: #1032112
    • Build-Depends-Indep: golang-github-jesseduffield-rollrus golang-github-jesseduffield-roll (not considered)
    • Depends: golang-github-jesseduffield-rollrus golang-github-jesseduffield-roll (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-rollrus.html
    • autopkgtest for golang-github-jesseduffield-rollrus/0.0~git20190701.dd028cb-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 646 days old (needed 2 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:
    • Updating linssid would introduce bugs in testing: #1067913
    • Impossible Depends: linssid -> libqt5core5a/5.15.10+dfsg-7/armel
    • Impossible Depends: linssid -> libqt5core5a/5.15.10+dfsg-7/armhf
    • Impossible Depends: linssid -> libqt5widgets5/5.15.10+dfsg-7/armel
    • Impossible Depends: linssid -> libqt5widgets5/5.15.10+dfsg-7/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linssid.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 646 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 ♻
    • 646 days old (needed 5 days)
• r-other-wasabi (- to 1.0.1-3)
  • Migration status for r-other-wasabi (- to 1.0.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-other-wasabi r-bioc-rhdf5 (not considered)
    • Depends: r-other-wasabi r-bioc-rhdf5 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-other-wasabi.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-other-wasabi/1.0.1-3: amd64: Pass, arm64: 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
    • 647 days old (needed 2 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
    • Reproducible on armhf - info ♻
    • 647 days old (needed 5 days)
• blasr (- to 5.3.5+dfsg-6)
  • Migration status for blasr (- to 5.3.5+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating blasr would introduce bugs in testing: #1067374
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blasr.html
    • autopkgtest for blasr/5.3.5+dfsg-6: 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
    • 648 days old (needed 2 days)
• golang-github-bradenhilton-cityhash (- to 1.0.0-1)
  • Migration status for golang-github-bradenhilton-cityhash (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bradenhilton-cityhash.html
    • autopkgtest for golang-github-bradenhilton-cityhash/1.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 649 days old (needed 2 days)
• jsurf-alggeo (- to 0.4.1+ds-4)
  • Migration status for jsurf-alggeo (- to 0.4.1+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jsurf-alggeo would introduce bugs in testing: #1053037
    • autopkgtest for jsurf-alggeo/0.4.1+ds-4: 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 armhf - info ♻
    • Reproducible on i386 - info ♻
    • 649 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
    • Reproducible on armhf - info ♻
    • 650 days old (needed 5 days)
• entrypoints (- to 0.4-2)
  • Migration status for entrypoints (- to 0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating entrypoints would introduce bugs in testing: #1052826
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/entrypoints.html
    • autopkgtest for entrypoints/0.4-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
    • 651 days old (needed 2 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:
    • Updating mpqc would introduce bugs in testing: #1075293, #1077120
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpqc.html
    • 651 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• node-puppeteer (- to 13.4.1+dfsg-2)
  • Migration status for node-puppeteer (- to 13.4.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-puppeteer would introduce bugs in testing: #1026868, #1071802
    • autopkgtest for node-puppeteer/13.4.1+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-puppeteer.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 651 days old (needed 5 days)
• sbox-dtc (- to 1.11.7-1.1)
  • Migration status for sbox-dtc (- to 1.11.7-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sbox-dtc would introduce bugs in testing: #1066471
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbox-dtc.html
    • 651 days old (needed 5 days)
• tuxtype (- to 1.8.3-5.1)
  • Migration status for tuxtype (- to 1.8.3-5.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tuxtype t4kcommon (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tuxtype.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 651 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
    • 653 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/s390x has unsatisfiable dependency
    • Updating libapache-db-perl would introduce bugs in testing: #1040396
    • autopkgtest for libapache-db-perl/0.18-2: riscv64: Regression or new test ♻
    • 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 s390x, not running autopkgtest there
    • 654 days old (needed 5 days)
• pyjunitxml (- to 0.7-2)
  • Migration status for pyjunitxml (- to 0.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyjunitxml would introduce bugs in testing: #1057356
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyjunitxml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 654 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
    • 656 days old (needed 5 days)
• flask-appbuilder (- to 4.1.4+ds-3)
  • Migration status for flask-appbuilder (- to 4.1.4+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-flask-appbuilder/amd64 has unsatisfiable dependency
    • python3-flask-appbuilder/arm64 has unsatisfiable dependency
    • Updating flask-appbuilder would introduce bugs in testing: #1020739, #1036167, #1040069
    • autopkgtest for flask-appbuilder/4.1.4+ds-3: riscv64: Regression or new test ♻
    • flask-appbuilder unsatisfiable Build-Depends(-Arch) on amd64: python3-marshmallow-enum
    • Build-Depends(-Arch): flask-appbuilder flask-babel (not considered)
    • Build-Depends(-Arch): flask-appbuilder flask-wtf (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/flask-appbuilder.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 656 days old (needed 5 days)
    • Remove hint for (transitive) dependency: flask-babel, flask-wtf
• 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 ♻
    • 656 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
    • 656 days old (needed 5 days)
• python-aio-pika (- to 8.2.5-1)
  • Migration status for python-aio-pika (- to 8.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): python-aio-pika python-pamqp (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): python-aio-pika python-aiormq
    • Depends: python-aio-pika python-aiormq
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aio-pika.html
    • autopkgtest for python-aio-pika/8.2.5-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 656 days old (needed 5 days)
• python-aioamqp (- to 0.15.0-2)
  • Migration status for python-aioamqp (- to 0.15.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-aioamqp python-pamqp (not considered)
    • Depends: python-aioamqp python-pamqp (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioamqp.html
    • autopkgtest for python-aioamqp/0.15.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 656 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 ♻
    • 657 days old (needed 5 days)
• 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asmix.html
    • 660 days old (needed 5 days)
• beav (- to 1:1.40-18.4)
  • Migration status for beav (- to 1:1.40-18.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating beav would introduce bugs in testing: #1074840
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/beav.html
    • Reproducible on armhf - info ♻
    • 660 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 ♻
    • 660 days old (needed 5 days)
• aces3 (- to 3.0.8-9)
  • Migration status for aces3 (- to 3.0.8-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aces3 would introduce bugs in testing: #1074799
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aces3.html
    • Reproducible on armhf - info ♻
    • 661 days old (needed 5 days)
• golang-github-jesseduffield-go-getter (- to 0.0~git20180822.906e156-5)
  • Migration status for golang-github-jesseduffield-go-getter (- to 0.0~git20180822.906e156-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-go-getter would introduce bugs in testing: #1032107
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-go-getter.html
    • autopkgtest for golang-github-jesseduffield-go-getter/0.0~git20180822.906e156-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 662 days old (needed 2 days)
• golang-github-jesseduffield-roll (- to 0.0~git20190629.695be2e-3)
  • Migration status for golang-github-jesseduffield-roll (- to 0.0~git20190629.695be2e-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-roll would introduce bugs in testing: #1032113
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-roll.html
    • autopkgtest for golang-github-jesseduffield-roll/0.0~git20190629.695be2e-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 662 days old (needed 2 days)
• golang-github-keybase-go-ps (- to 0.0~git20190827.91aafc9-1)
  • Migration status for golang-github-keybase-go-ps (- to 0.0~git20190827.91aafc9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-keybase-go-ps.html
    • autopkgtest for golang-github-keybase-go-ps/0.0~git20190827.91aafc9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 662 days old (needed 2 days)
• golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2)
  • Migration status for golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-leanovate-gopter/0.2.9+git20210201.bbbf00e-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, 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 ♻
    • 662 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
    • 662 days old (needed 2 days)
• golang-github-jesseduffield-yaml (- to 2.2.2+git20190702.b900b7e-3)
  • Migration status for golang-github-jesseduffield-yaml (- to 2.2.2+git20190702.b900b7e-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-yaml would introduce bugs in testing: #1032190
    • autopkgtest for golang-github-jesseduffield-yaml/2.2.2+git20190702.b900b7e-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-yaml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 663 days old (needed 5 days)
• golang-github-muesli-combinator (- to 0.3.0-1)
  • Migration status for golang-github-muesli-combinator (- to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-muesli-combinator.html
    • autopkgtest for golang-github-muesli-combinator/0.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 663 days old (needed 2 days)
• golang-github-twpayne-go-pinentry (- to 0.2.0-1)
  • Migration status for golang-github-twpayne-go-pinentry (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-pinentry.html
    • autopkgtest for golang-github-twpayne-go-pinentry/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 663 days old (needed 2 days)
• golang-github-twpayne-go-shell (- to 0.3.1-1)
  • Migration status for golang-github-twpayne-go-shell (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-shell.html
    • autopkgtest for golang-github-twpayne-go-shell/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 663 days old (needed 2 days)
• golang-github-twpayne-go-vfs (- to 4.1.0-1)
  • Migration status for golang-github-twpayne-go-vfs (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-vfs.html
    • autopkgtest for golang-github-twpayne-go-vfs/4.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 663 days old (needed 2 days)
• golang-github-twpayne-go-xdg (- to 6.0.0-1)
  • Migration status for golang-github-twpayne-go-xdg (- to 6.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ryanakca@kubuntu.org, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): golang-github-twpayne-go-xdg golang-github-twpayne-go-vfs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twpayne-go-xdg.html
    • autopkgtest for golang-github-twpayne-go-xdg/6.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 663 days old (needed 2 days)
• ns2 (- to 2.35+dfsg-5)
  • Migration status for ns2 (- to 2.35+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ns2 would introduce bugs in testing: #1075321
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ns2.html
    • 663 days old (needed 5 days)
• opensysusers (- to 0.7.3-2)
  • Migration status for opensysusers (- to 0.7.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensysusers would introduce bugs in testing: #1055514, #1055517
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensysusers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 663 days old (needed 5 days)
• rust-fxprof-processed-profile (- to 0.4.0-2)
  • Migration status for rust-fxprof-processed-profile (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-fxprof-processed-profile would introduce bugs in testing: #1030997
    • autopkgtest for rust-fxprof-processed-profile/0.4.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fxprof-processed-profile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 663 days old (needed 5 days)
• sawfish-themes (- to 0.13.0-2)
  • Migration status for sawfish-themes (- to 0.13.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: sawfish-themes sawfish (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sawfish-themes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 663 days old (needed 5 days)
• shush (- to 1.2.3-5.1)
  • Migration status for shush (- to 1.2.3-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shush would introduce bugs in testing: #999964
    • Build-Depends(-Arch): shush pcre3 (not considered)
    • Depends: shush pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shush.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 663 days old (needed 5 days)
• xxkb (- to 1.11.1-2)
  • Migration status for xxkb (- to 1.11.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xxkb would introduce bugs in testing: #1075694
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xxkb.html
    • Reproducible on armhf - info ♻
    • 663 days old (needed 5 days)
• syncmaildir (- to 1.3.0-2)
  • Migration status for syncmaildir (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating syncmaildir would introduce bugs in testing: #1000322, #1078828
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syncmaildir.html
    • Reproducible on armhf - info ♻
    • 665 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
    • 666 days old (needed 2 days)
• tipp (- to 1.0+dfsg-3)
  • Migration status for tipp (- to 1.0+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tipp sepp (not considered)
    • Depends: tipp sepp (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tipp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 667 days old (needed 5 days)
• platformio (- to 4.3.4-3)
  • Migration status for platformio (- to 4.3.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating platformio would introduce bugs in testing: #1053285, #1080046, #988716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/platformio.html
    • autopkgtest for platformio/4.3.4-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 668 days old (needed 5 days)
• geotranz (- to 3.7-3)
  • Migration status for geotranz (- to 3.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating geotranz would introduce bugs in testing: #1052574
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geotranz.html
    • Reproducible on armhf - info ♻
    • 669 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
    • Reproducible on armhf - info ♻
    • 669 days old (needed 5 days)
• pidgin-nateon (- to 0.0.0.svn147-2)
  • Migration status for pidgin-nateon (- to 0.0.0.svn147-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pidgin-nateon would introduce bugs in testing: #1075388
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pidgin-nateon.html
    • Reproducible on armhf - info ♻
    • 670 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 ♻
    • 670 days old (needed 5 days)
• php-laravel-lumen-framework (- to 8.3.4-1)
  • Migration status for php-laravel-lumen-framework (- to 8.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-laravel-lumen-framework/amd64 has unsatisfiable dependency
    • php-laravel-lumen-framework/arm64 has unsatisfiable dependency
    • Updating php-laravel-lumen-framework would introduce bugs in testing: #1039731
    • autopkgtest for php-laravel-lumen-framework/8.3.4-1: riscv64: Regression or new test ♻
    • Build-Depends(-Arch): php-laravel-lumen-framework php-laravel-framework (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-laravel-lumen-framework.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 671 days old (needed 5 days)
• php-laravel-framework (- to 8.83.26+dfsg-2)
  • Migration status for php-laravel-framework (- to 8.83.26+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-illuminate-console/amd64 has unsatisfiable dependency
    • php-illuminate-cookie/amd64 has unsatisfiable dependency
    • php-illuminate-database/amd64 has unsatisfiable dependency
    • php-illuminate-filesystem/amd64 has unsatisfiable dependency
    • php-illuminate-http/amd64 has unsatisfiable dependency
    • php-illuminate-queue/amd64 has unsatisfiable dependency
    • php-illuminate-routing/amd64 has unsatisfiable dependency
    • php-illuminate-session/amd64 has unsatisfiable dependency
    • php-illuminate-validation/amd64 has unsatisfiable dependency
    • php-laravel-framework/amd64 has unsatisfiable dependency
    • php-illuminate-console/arm64 has unsatisfiable dependency
    • php-illuminate-cookie/arm64 has unsatisfiable dependency
    • php-illuminate-database/arm64 has unsatisfiable dependency
    • php-illuminate-filesystem/arm64 has unsatisfiable dependency
    • php-illuminate-http/arm64 has unsatisfiable dependency
    • php-illuminate-queue/arm64 has unsatisfiable dependency
    • php-illuminate-routing/arm64 has unsatisfiable dependency
    • php-illuminate-session/arm64 has unsatisfiable dependency
    • php-illuminate-validation/arm64 has unsatisfiable dependency
    • php-laravel-framework/arm64 has unsatisfiable dependency
    • Updating php-laravel-framework would introduce bugs in testing: #1051985
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/php-laravel-framework.html
    • autopkgtest for php-laravel-framework/8.83.26+dfsg-2: riscv64: Regression or new test ♻
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 672 days old (needed 5 days)
• fruit (- to 2.1.dfsg-10)
  • Migration status for fruit (- to 2.1.dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fruit would introduce bugs in testing: #1014187, #1079960
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fruit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 674 days old (needed 5 days)
• node-request (- to 2.88.1-6)
  • Migration status for node-request (- to 2.88.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-request would introduce bugs in testing: #956423
    • Build-Depends(-Arch): node-request node-har-validator (not considered)
    • Depends: node-request node-har-validator (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-request.html
    • autopkgtest for node-request/2.88.1-6: 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
    • 674 days old (needed 2 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 ♻
    • 675 days old (needed 5 days)
• uni2ascii (- to 4.18-6)
  • Migration status for uni2ascii (- to 4.18-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating uni2ascii would introduce bugs in testing: #1075604
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uni2ascii.html
    • Reproducible on armhf - info ♻
    • 675 days old (needed 5 days)
• raku-librarycheck (- to 0.0.11-1)
  • Migration status for raku-librarycheck (- to 0.0.11-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-librarycheck dh-raku (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-librarycheck.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 677 days old (needed 5 days)
• raku-license-spdx (- to 3.18.0-1)
  • Migration status for raku-license-spdx (- to 3.18.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-license-spdx dh-raku (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): raku-license-spdx raku-json-class
    • Depends: raku-license-spdx raku-json-class
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-license-spdx.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 ♻
    • 677 days old (needed 5 days)
• libjpeg6b (- to 1:6b2-3.1)
  • Migration status for libjpeg6b (- to 1:6b2-3.1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
    • Build-Depends(-Arch): libjpeg6b automake1.11 (not considered)
  • 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 ♻
    • 678 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
    • 678 days old (needed 5 days)
• raku-json-class (- to 0.0.19-1)
  • Migration status for raku-json-class (- to 0.0.19-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-json-class dh-raku (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): raku-json-class raku-json-fast
    • Build-Depends(-Arch): raku-json-class raku-json-marshal
    • Build-Depends(-Arch): raku-json-class raku-json-name
    • Build-Depends(-Arch): raku-json-class raku-json-optin
    • Build-Depends(-Arch): raku-json-class raku-json-unmarshal
    • Depends: raku-json-class raku-json-marshal
    • Depends: raku-json-class raku-json-name
    • Depends: raku-json-class raku-json-optin
    • Depends: raku-json-class raku-json-unmarshal
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-json-class.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 ♻
    • 678 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 ♻
    • 679 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
    • Reproducible on armhf - info ♻
    • 679 days old (needed 5 days)
• raku-file-which (- to 1.0.4-1)
  • Migration status for raku-file-which (- to 1.0.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-file-which dh-raku (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-file-which.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 679 days old (needed 5 days)
• objcryst-fox (- to 2022.1-1)
  • Migration status for objcryst-fox (- to 2022.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): objcryst-fox newmat (not considered)
    • Depends: objcryst-fox newmat (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): objcryst-fox cctbx (not considered)
    • Depends: objcryst-fox cctbx (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/objcryst-fox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 680 days old (needed 5 days)
• texmaker (- to 5.1.3+dfsg-1)
  • Migration status for texmaker (- to 5.1.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating texmaker would introduce bugs in testing: #1075565
    • 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 i386 binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
    • Not built on buildd: upload info for arch s390x binaries not found
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/texmaker.html
    • Reproducible on armhf - info ♻
    • 681 days old (needed 5 days)
• readucks (- to 0.0.3-5)
  • Migration status for readucks (- to 0.0.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for readucks/0.0.3-5: 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 ♻
    • 682 days old (needed 5 days)
• lexd (- to 1.3.1-1)
  • Migration status for lexd (- to 1.3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lexd hfst (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lexd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 683 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
    • 684 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
    • 685 days old (needed 2 days)
• knxd (- to 0.14.54.1)
  • Migration status for knxd (- to 0.14.54.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating knxd would introduce bugs in testing: #1075116
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/knxd.html
    • 689 days old (needed 5 days)
• orca-sops (- to 1.0.2-4)
  • Migration status for orca-sops (- to 1.0.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: orca-sops yad (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orca-sops.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 692 days old (needed 5 days)
• courier-filter-perl (- to 0.200+ds-6)
  • Migration status for courier-filter-perl (- to 0.200+ds-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for courier-filter-perl/0.200+ds-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: 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 ♻
    • Depends: courier-filter-perl courier (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier-filter-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 693 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/s390x has unsatisfiable dependency
    • Updating openboard would introduce bugs in testing: #1072442, #1074332
  • Additional info:
    • Piuparts tested OK - 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 s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 693 days old (needed 5 days)
• xmlcopyeditor (- to 1.3.0.0-1.1)
  • Migration status for xmlcopyeditor (- to 1.3.0.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xmlcopyeditor would introduce bugs in testing: #1073341
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmlcopyeditor.html
    • 694 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
    • Build-Depends(-Arch): flask-mongoengine flask-wtf (not considered)
    • Depends: flask-mongoengine flask-wtf (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-mongoengine.html
    • 697 days old (needed 5 days)
    • Remove hint for (transitive) dependency: flask-wtf
• devpi-common (- to 3.2.2-3)
  • Migration status for devpi-common (- to 3.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating devpi-common would introduce bugs in testing: #1030453, #1080509
    • autopkgtest for devpi-common/3.2.2-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/devpi-common.html
    • 698 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
    • Depends: dradio curl (not considered)
    • Depends: dradio mplayer (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dradio.html
    • 698 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
    • 698 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
    • 699 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
    • 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: 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/libe/libextutils-cbuilder-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 699 days old (needed 5 days)
• raku (- to 6.d.7)
  • Migration status for raku (- to 6.d.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: raku raku-readline (not considered)
    • Invalidated by dependency
    • Depends: raku prove6
    • Depends: raku raku-file-find
    • Depends: raku raku-file-which
    • Depends: raku raku-getopt-long
    • Depends: raku raku-hash-merge
    • Depends: raku raku-json-class
    • Depends: raku raku-json-fast
    • Depends: raku raku-json-marshal
    • Depends: raku raku-json-name
    • Depends: raku raku-json-optin
    • Depends: raku raku-json-unmarshal
    • Depends: raku raku-librarycheck
    • Depends: raku raku-log
    • Depends: raku raku-meta6 (not considered)
    • Depends: raku raku-tap-harness
    • Depends: raku raku-test-meta
    • Depends: raku raku-uri
    • Depends: raku raku-zef
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 699 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 ♻
    • 700 days old (needed 5 days)
    • Remove hint for (transitive) dependency: bioperl-run
• matrix-sydent (- to 2.5.1-1.1)
  • Migration status for matrix-sydent (- to 2.5.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating matrix-sydent would introduce bugs in testing: #1029442, #1035844, #1071799, #1078915, #1080078
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/m/matrix-sydent.html
  • Additional info:
    • autopkgtest for matrix-sydent/2.5.1-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 700 days old (needed 5 days)
• openscap-daemon (- to 0.1.10-3.1)
  • Migration status for openscap-daemon (- to 0.1.10-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openscap-daemon/amd64 has unsatisfiable dependency
    • openscap-daemon/arm64 has unsatisfiable dependency
    • Updating openscap-daemon would introduce bugs in testing: #1035384, #1065912, #1071918, #1080076
    • autopkgtest for openscap-daemon/0.1.10-3.1: riscv64: Regression or new test ♻
    • openscap-daemon unsatisfiable Build-Depends(-Arch) on amd64: python3-distutils
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openscap-daemon.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 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 ♻
    • 700 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
    • Reproducible on armhf - info ♻
    • 701 days old (needed 5 days)
• bcbio (- to 1.2.9-2)
  • Migration status for bcbio (- to 1.2.9-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): bcbio r-other-wasabi (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): bcbio freebayes (not considered)
    • Build-Depends(-Arch): bcbio hts-nim-tools (not considered)
    • Build-Depends(-Arch): bcbio mosdepth (not considered)
    • Build-Depends(-Arch): bcbio r-bioc-purecn
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for bcbio/1.2.9-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • 702 days old (needed 5 days)
• sendfile (- to 2.1b.20080616-10)
  • Migration status for sendfile (- to 2.1b.20080616-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sendfile would introduce bugs in testing: #1075501
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sendfile.html
    • Reproducible on armhf - info ♻
    • 702 days old (needed 5 days)
• ssmtp (- to 2.64-11)
  • Migration status for ssmtp (- to 2.64-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ssmtp would introduce bugs in testing: #1075538
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/ssmtp.html
    • Reproducible on armhf - info ♻
    • 702 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
    • Reproducible on armhf - info ♻
    • 702 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 ♻
    • Reproducible on armhf - info ♻
    • 703 days old (needed 5 days)
• telegram-cli (- to 1.3.1+git20160323.6547c0b21-3.1)
  • Migration status for telegram-cli (- to 1.3.1+git20160323.6547c0b21-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telegram-cli would introduce bugs in testing: #1018754
    • Build-Depends(-Arch): telegram-cli tgl (not considered)
    • Depends: telegram-cli tgl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telegram-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 703 days old (needed 5 days)
• mozillavpn (- to 2.9.0-1)
  • Migration status for mozillavpn (- to 2.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mozillavpn/armel has unsatisfiable dependency
    • mozillavpn/armhf has unsatisfiable dependency
    • Updating mozillavpn would introduce bugs in testing: #1026957, #1027506, #1043004, #1080077
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/m/mozillavpn.html
    • missing build on mips64el
  • Additional info:
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 704 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
    • autopkgtest for ruby-elasticsearch-model/7.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/ruby-elasticsearch-model.html
    • 708 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
    • 711 days old (needed 5 days)
• theli (- to 3.1.4-1)
  • Migration status for theli (- to 3.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • theli/amd64 has unsatisfiable dependency
    • theli/arm64 has unsatisfiable dependency
    • theli/mips64el has unsatisfiable dependency
    • theli/ppc64el has unsatisfiable dependency
    • theli/s390x has unsatisfiable dependency
    • Updating theli would introduce bugs in testing: #1056689, #1069982
    • Build-Depends(-Arch): theli atlas (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/theli.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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 711 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
    • 712 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
    • Reproducible on armhf - info ♻
    • 712 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
    • Reproducible on armhf - info ♻
    • 714 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
    • Reproducible on armhf - info ♻
    • 717 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
    • 719 days old (needed 5 days)
• python-aiormq (- to 6.4.2-1)
  • Migration status for python-aiormq (- to 6.4.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-aiormq python-pamqp (not considered)
    • Depends: python-aiormq python-pamqp (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiormq.html
    • autopkgtest for python-aiormq/6.4.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 720 days old (needed 5 days)
• netkit-rwho (- to 0.17-15)
  • Migration status for netkit-rwho (- to 0.17-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netkit-rwho would introduce bugs in testing: #1074175
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netkit-rwho.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 721 days old (needed 5 days)
• keras (- to 2.3.1+dfsg2-1)
  • Migration status for keras (- to 2.3.1+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-keras/amd64 has unsatisfiable dependency
    • python3-keras/arm64 has unsatisfiable dependency
    • Updating keras would introduce bugs in testing: #1026738, #1065884
    • autopkgtest for keras/2.3.1+dfsg2-1: riscv64: Regression or new test ♻
    • keras unsatisfiable Build-Depends(-Arch) on amd64: python3-theano
    • keras unsatisfiable Build-Depends(-Arch) on amd64: python3-distutils
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/keras.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 722 days old (needed 5 days)
• raku-tap-harness (- to 0.3.8-2)
  • Migration status for raku-tap-harness (- to 0.3.8-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-tap-harness dh-raku (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-tap-harness.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 ♻
    • 722 days old (needed 5 days)
• uhub (- to 0.4.1-3.2)
  • Migration status for uhub (- to 0.4.1-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating uhub would introduce bugs in testing: #1066247
    • Impossible Depends: uhub -> libssl3/3.1.5-1/armel
    • Impossible Depends: uhub -> libssl3/3.1.5-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uhub.html
    • 723 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: #813866
    • Build-Depends(-Arch): php-fdomdocument phpcpd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fdomdocument.html
    • autopkgtest for php-fdomdocument/1.6.7-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
    • 725 days old (needed 2 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: #813861
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/phpdox.html
    • autopkgtest for phpdox/0.12.0-6: riscv64: Regression or new test ♻
    • Build-Depends(-Arch): phpdox php-fdomdocument (not considered)
    • Build-Depends(-Arch): phpdox php-fxsl (not considered)
    • Build-Depends(-Arch): phpdox phpcpd (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 s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 725 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:
    • Updating eclipse-titan would introduce bugs in testing: #1071679, #1073307
    • Depends: eclipse-titan pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-titan.html
    • 729 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 729 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
    • 730 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
    • Reproducible on armhf - info ♻
    • 730 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
    • Reproducible on armhf - info ♻
    • 730 days old (needed 5 days)
• raku-meta6 (- to 0.0.29-1)
  • Migration status for raku-meta6 (- to 0.0.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating raku-meta6 would introduce bugs in testing: #1057611
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • Build-Depends(-Arch): raku-meta6 dh-raku (not considered)
    • Build-Depends(-Arch): raku-meta6 prove6
    • Build-Depends(-Arch): raku-meta6 raku-json-class
    • Build-Depends(-Arch): raku-meta6 raku-json-fast
    • Build-Depends(-Arch): raku-meta6 raku-json-name
    • Depends: raku-meta6 raku-json-class
    • Depends: raku-meta6 raku-json-name
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-meta6.html
    • 733 days old (needed 5 days)
• raku-test-meta (- to 0.0.17-1)
  • Migration status for raku-test-meta (- to 0.0.17-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-test-meta raku-meta6 (not considered)
    • Depends: raku-test-meta raku-meta6 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): raku-test-meta dh-raku (not considered)
    • Build-Depends(-Arch): raku-test-meta prove6
    • Build-Depends(-Arch): raku-test-meta raku-license-spdx
    • Build-Depends(-Arch): raku-test-meta raku-uri
    • Depends: raku-test-meta raku-license-spdx
    • Depends: raku-test-meta raku-uri
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-test-meta.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 ♻
    • 733 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 ♻
    • 734 days old (needed 5 days)
• watchman (- to 4.9.0-7)
  • Migration status for watchman (- to 4.9.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating watchman would introduce bugs in testing: #999930
    • Build-Depends(-Arch): watchman pcre3 (not considered)
    • Depends: watchman pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/watchman.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 734 days old (needed 5 days)
• libgovirt (- to 0.3.9-2)
  • Migration status for libgovirt (- to 0.3.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libgovirt would introduce bugs in testing: #1030904
    • Impossible Depends: libgovirt -> libglib2.0-0/2.78.4-1/armel
    • Impossible Depends: libgovirt -> libglib2.0-0/2.78.4-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgovirt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 739 days old (needed 5 days)
• prove6 (- to 0.0.12-7)
  • Migration status for prove6 (- to 0.0.12-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): prove6 dh-raku (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): prove6 raku-getopt-long
    • Build-Depends(-Arch): prove6 raku-tap-harness
    • Depends: prove6 raku-getopt-long
    • Depends: prove6 raku-tap-harness
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prove6.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 ♻
    • 740 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-leveldown.html
    • autopkgtest for node-leveldown/5.6.0+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
    • 745 days old (needed 2 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
    • 751 days old (needed 5 days)
• cpl-plugin-visir (- to 4.4.2+dfsg-1)
  • Migration status for cpl-plugin-visir (- to 4.4.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpl-plugin-visir would introduce bugs in testing: #1071689
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpl-plugin-visir.html
    • autopkgtest for cpl-plugin-visir/4.4.2+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 754 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
    • Reproducible on armhf - info ♻
    • 757 days old (needed 5 days)
• openfst (- to 1.7.9-5)
  • Migration status for openfst (- to 1.7.9-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openfst would introduce bugs in testing: #1075340
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openfst.html
    • Reproducible on armhf - info ♻
    • 758 days old (needed 5 days)
• cpl-plugin-muse (- to 2.8.7+dfsg-3)
  • Migration status for cpl-plugin-muse (- to 2.8.7+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cpl-plugin-muse/amd64 has unsatisfiable dependency
    • cpl-plugin-muse/arm64 has unsatisfiable dependency
    • cpl-plugin-muse/armel has unsatisfiable dependency
    • cpl-plugin-muse/armhf has unsatisfiable dependency
    • cpl-plugin-muse/i386 has unsatisfiable dependency
    • cpl-plugin-muse/mips64el has unsatisfiable dependency
    • cpl-plugin-muse/ppc64el has unsatisfiable dependency
    • cpl-plugin-muse/s390x has unsatisfiable dependency
    • Updating cpl-plugin-muse would introduce bugs in testing: #1069508, #1071682
    • autopkgtest for cpl-plugin-muse/2.8.7+dfsg-3: riscv64: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/c/cpl-plugin-muse.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 760 days old (needed 5 days)
• cpl-plugin-uves (- to 6.1.8+dfsg-2)
  • Migration status for cpl-plugin-uves (- to 6.1.8+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cpl-plugin-uves/amd64 has unsatisfiable dependency
    • cpl-plugin-uves/arm64 has unsatisfiable dependency
    • cpl-plugin-uves/armel has unsatisfiable dependency
    • cpl-plugin-uves/armhf has unsatisfiable dependency
    • cpl-plugin-uves/i386 has unsatisfiable dependency
    • cpl-plugin-uves/mips64el has unsatisfiable dependency
    • cpl-plugin-uves/ppc64el has unsatisfiable dependency
    • cpl-plugin-uves/s390x has unsatisfiable dependency
    • Updating cpl-plugin-uves would introduce bugs in testing: #1071685, #1077254
    • autopkgtest for cpl-plugin-uves/6.1.8+dfsg-2: riscv64: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/c/cpl-plugin-uves.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 760 days old (needed 5 days)
• cpl-plugin-vimos (- to 4.1.7+dfsg-2)
  • Migration status for cpl-plugin-vimos (- to 4.1.7+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cpl-plugin-vimos/armel has unsatisfiable dependency
    • cpl-plugin-vimos/armhf has unsatisfiable dependency
    • Updating cpl-plugin-vimos would introduce bugs in testing: #1071688
    • autopkgtest for cpl-plugin-vimos/4.1.7+dfsg-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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/c/cpl-plugin-vimos.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 ♻
    • 760 days old (needed 5 days)
• deepin-music (- to 6.2.18-1)
  • Migration status for deepin-music (- to 6.2.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating deepin-music would introduce bugs in testing: #1078278
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepin-music.html
    • Reproducible on armhf - info ♻
    • 760 days old (needed 5 days)
• django-cachalot (- to 2.4.3-2)
  • Migration status for django-cachalot (- to 2.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-cachalot would introduce bugs in testing: #1055207
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/django-cachalot.html
    • django-cachalot unsatisfiable Build-Depends(-Arch) on amd64: python3-django (<< 3:3.3~)
    • Impossible Depends: django-cachalot -> python3-django/3:3.2.19-1+deb12u2/amd64
    • Impossible Depends: django-cachalot -> python3-django/3:3.2.19-1+deb12u2/arm64
  • Additional info:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 760 days old (needed 5 days)
• cpl-plugin-amber (- to 4.4.3+dfsg-1)
  • Migration status for cpl-plugin-amber (- to 4.4.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpl-plugin-amber would introduce bugs in testing: #1071677, #746988
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpl-plugin-amber.html
    • autopkgtest for cpl-plugin-amber/4.4.3+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 761 days old (needed 5 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
    • Reproducible on armhf - info ♻
    • 761 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 ♻
    • 762 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:
    • Updating debian-design would introduce bugs in testing: #1081074
    • debian-design unsatisfiable Build-Depends(-Arch) on amd64: boxer-data (<< 10.10)
    • Depends: debian-design blender
    • Depends: debian-design bookletimposer (not considered)
    • Depends: debian-design gtk-vector-screenshot (not considered)
    • Depends: debian-design pdfposter (not considered)
    • Depends: debian-design unicode-screensaver (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-design.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • 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 ♻
    • 764 days old (needed 5 days)
• raku-json-name (- to 0.0.7-3)
  • Migration status for raku-json-name (- to 0.0.7-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-json-name dh-raku (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): raku-json-name prove6
    • Build-Depends(-Arch): raku-json-name raku-json-optin
    • Depends: raku-json-name raku-json-optin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-json-name.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 ♻
    • 764 days old (needed 5 days)
• s3ql (- to 3.7.3+dfsg-2)
  • Migration status for s3ql (- to 3.7.3+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): s3ql python-dugong (not considered)
    • Depends: s3ql python-dugong (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/s3ql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 765 days old (needed 5 days)
• kluppe (- to 0.6.20-1.2)
  • Migration status for kluppe (- to 0.6.20-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kluppe/armel has unsatisfiable dependency
    • kluppe/armhf has unsatisfiable dependency
    • Updating kluppe would introduce bugs in testing: #1067546
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kluppe.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 ♻
    • 766 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
    • 766 days old (needed 5 days)
• haskell-happstack-authenticate (- to 2.6.1-1)
  • Migration status for haskell-happstack-authenticate (- to 2.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-happstack-authenticate-dev/amd64 has unsatisfiable dependency
    • libghc-happstack-authenticate-doc/amd64 has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/amd64 has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/arm64 has unsatisfiable dependency
    • libghc-happstack-authenticate-doc/arm64 has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/arm64 has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/armel has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/armel has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/armhf has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/armhf has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/i386 has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/i386 has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/mips64el has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/mips64el has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/ppc64el has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/ppc64el has unsatisfiable dependency
    • libghc-happstack-authenticate-dev/s390x has unsatisfiable dependency
    • libghc-happstack-authenticate-prof/s390x has unsatisfiable dependency
    • Updating haskell-happstack-authenticate would introduce bugs in testing: #1054957, #1057719
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on amd64: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on amd64: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on amd64: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on arm64: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on arm64: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on arm64: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armel: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armel: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armel: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armhf: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armhf: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on armhf: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on i386: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on i386: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on i386: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on mips64el: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on mips64el: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on mips64el: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-shakespeare-dev (<< 2.1)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on s390x: libghc-happstack-server-dev (<< 7.8)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on s390x: libghc-lens-dev (<< 5.2)
    • haskell-happstack-authenticate unsatisfiable Build-Depends(-Arch) on s390x: libghc-shakespeare-dev (<< 2.1)
    • Build-Depends(-Arch): haskell-happstack-authenticate haskell-userid (not considered)
    • Build-Depends-Indep: haskell-happstack-authenticate haskell-userid (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-happstack-authenticate.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 767 days old (needed 5 days)
• node-expat (- to 2.4.0+ds-2)
  • Migration status for node-expat (- to 2.4.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • node-node-expat/amd64 has unsatisfiable dependency
    • node-node-expat/arm64 has unsatisfiable dependency
    • node-node-expat/armel has unsatisfiable dependency
    • node-node-expat/armhf has unsatisfiable dependency
    • node-node-expat/i386 has unsatisfiable dependency
    • node-node-expat/mips64el has unsatisfiable dependency
    • node-node-expat/ppc64el has unsatisfiable dependency
    • node-node-expat/s390x has unsatisfiable dependency
    • Updating node-expat would introduce bugs in testing: #1064047
    • autopkgtest for node-expat/2.4.0+ds-2: riscv64: Regression or new test ♻
    • 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/n/node-expat.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
    • 767 days old (needed 5 days)
• raku-json-optin (- to 0.0.2-2)
  • Migration status for raku-json-optin (- 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): raku-json-optin dh-raku (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): raku-json-optin prove6
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-json-optin.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 ♻
    • 768 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
    • 772 days old (needed 5 days)
• smlsharp (- to 4.0.0+git20211227.5af5945b-2)
  • Migration status for smlsharp (- to 4.0.0+git20211227.5af5945b-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smlsharp would introduce bugs in testing: #1071781
    • Build-Depends(-Arch): smlsharp massivethreads (not considered)
    • Depends: smlsharp massivethreads (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smlsharp.html
    • 772 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
    • 772 days old (needed 5 days)
• haskell-userid (- to 0.1.3.7-1)
  • Migration status for haskell-userid (- to 0.1.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-userid-dev/amd64 has unsatisfiable dependency
    • libghc-userid-doc/amd64 has unsatisfiable dependency
    • libghc-userid-prof/amd64 has unsatisfiable dependency
    • libghc-userid-dev/arm64 has unsatisfiable dependency
    • libghc-userid-doc/arm64 has unsatisfiable dependency
    • libghc-userid-prof/arm64 has unsatisfiable dependency
    • libghc-userid-dev/armel has unsatisfiable dependency
    • libghc-userid-prof/armel has unsatisfiable dependency
    • libghc-userid-dev/armhf has unsatisfiable dependency
    • libghc-userid-prof/armhf has unsatisfiable dependency
    • libghc-userid-dev/i386 has unsatisfiable dependency
    • libghc-userid-prof/i386 has unsatisfiable dependency
    • libghc-userid-dev/mips64el has unsatisfiable dependency
    • libghc-userid-prof/mips64el has unsatisfiable dependency
    • libghc-userid-dev/ppc64el has unsatisfiable dependency
    • libghc-userid-prof/ppc64el has unsatisfiable dependency
    • libghc-userid-dev/s390x has unsatisfiable dependency
    • libghc-userid-prof/s390x has unsatisfiable dependency
    • Updating haskell-userid would introduce bugs in testing: #1054977, #1057718
    • haskell-userid unsatisfiable Build-Depends(-Arch) on amd64: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on arm64: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on armel: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on armhf: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on i386: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on mips64el: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on riscv64: libghc-aeson-dev (<< 2.1)
    • haskell-userid unsatisfiable Build-Depends(-Arch) on s390x: libghc-aeson-dev (<< 2.1)
    • 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-userid.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 775 days old (needed 5 days)
• ortools (- to 8.2+ds-6)
  • Migration status for ortools (- to 8.2+ds-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libortools8/amd64 has unsatisfiable dependency
    • ortools-flatzinc/amd64 has unsatisfiable dependency
    • ortools-samples/amd64 has unsatisfiable dependency
    • python3-ortools/amd64 has unsatisfiable dependency
    • libortools8/arm64 has unsatisfiable dependency
    • ortools-flatzinc/arm64 has unsatisfiable dependency
    • ortools-samples/arm64 has unsatisfiable dependency
    • python3-ortools/arm64 has unsatisfiable dependency
    • libortools8/ppc64el has unsatisfiable dependency
    • ortools-flatzinc/ppc64el has unsatisfiable dependency
    • ortools-samples/ppc64el has unsatisfiable dependency
    • python3-ortools/ppc64el has unsatisfiable dependency
    • Updating ortools would introduce bugs in testing: #1024790, #1040564
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/ortools.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 775 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-doc/amd64 has unsatisfiable dependency
    • libghc-hindent-doc/arm64 has unsatisfiable dependency
    • libghc-hindent-dev/mips64el has unsatisfiable dependency
    • libghc-hindent-prof/mips64el has unsatisfiable dependency
    • Updating haskell-hindent would introduce bugs in testing: #1053982
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hindent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 776 days old (needed 5 days)
• openvpn-auth-ldap (- to 2.0.4-3)
  • Migration status for openvpn-auth-ldap (- to 2.0.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openvpn-auth-ldap would introduce bugs in testing: #1075345
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvpn-auth-ldap.html
    • autopkgtest for openvpn-auth-ldap/2.0.4-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 777 days old (needed 5 days)
• rabbiter (- to 2.0.4-6)
  • Migration status for rabbiter (- to 2.0.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rabbiter rabbit (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rabbiter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 779 days old (needed 5 days)
• haskell-ircbot (- to 0.6.6.1-1)
  • Migration status for haskell-ircbot (- to 0.6.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-ircbot-dev/amd64 has unsatisfiable dependency
    • libghc-ircbot-doc/amd64 has unsatisfiable dependency
    • libghc-ircbot-prof/amd64 has unsatisfiable dependency
    • libghc-ircbot-dev/arm64 has unsatisfiable dependency
    • libghc-ircbot-doc/arm64 has unsatisfiable dependency
    • libghc-ircbot-prof/arm64 has unsatisfiable dependency
    • libghc-ircbot-dev/armel has unsatisfiable dependency
    • libghc-ircbot-prof/armel has unsatisfiable dependency
    • libghc-ircbot-dev/armhf has unsatisfiable dependency
    • libghc-ircbot-prof/armhf has unsatisfiable dependency
    • libghc-ircbot-dev/i386 has unsatisfiable dependency
    • libghc-ircbot-prof/i386 has unsatisfiable dependency
    • libghc-ircbot-dev/mips64el has unsatisfiable dependency
    • libghc-ircbot-prof/mips64el has unsatisfiable dependency
    • libghc-ircbot-dev/ppc64el has unsatisfiable dependency
    • libghc-ircbot-prof/ppc64el has unsatisfiable dependency
    • libghc-ircbot-dev/s390x has unsatisfiable dependency
    • libghc-ircbot-prof/s390x has unsatisfiable dependency
    • Updating haskell-ircbot would introduce bugs in testing: #1054947, #1057720
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on amd64: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on arm64: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on armel: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on armhf: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on i386: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on mips64el: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on riscv64: libghc-optparse-applicative-dev (<< 0.17)
    • haskell-ircbot unsatisfiable Build-Depends(-Arch) on s390x: libghc-optparse-applicative-dev (<< 0.17)
    • 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-ircbot.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 783 days old (needed 5 days)
• maildrop (- to 2.9.3-2.1)
  • Migration status for maildrop (- to 2.9.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • maildrop/armel has unsatisfiable dependency
    • maildrop/armhf has unsatisfiable dependency
    • Updating maildrop would introduce bugs in testing: #1000129, #1068031
    • Build-Depends(-Arch): maildrop courier-authlib (not considered)
    • Build-Depends(-Arch): maildrop pcre3 (not considered)
    • Depends: maildrop courier-authlib (not considered)
    • Depends: maildrop pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/maildrop.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 783 days old (needed 5 days)
• threadscope (- to 0.2.14.1-1)
  • Migration status for threadscope (- to 0.2.14.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • threadscope/armel has unsatisfiable dependency
    • threadscope/armhf has unsatisfiable dependency
    • Updating threadscope would introduce bugs in testing: #1054939
    • threadscope unsatisfiable Build-Depends(-Arch) on amd64: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on arm64: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on armel: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on armhf: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on i386: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on mips64el: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-ghc-events-dev (<< 0.18)
    • threadscope unsatisfiable Build-Depends(-Arch) on s390x: libghc-ghc-events-dev (<< 0.18)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/threadscope.html
    • 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 ♻
    • 783 days old (needed 5 days)
• haskell-reform-hsp (- to 0.2.7.2-2)
  • Migration status for haskell-reform-hsp (- to 0.2.7.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-reform-hsp-dev/amd64 has unsatisfiable dependency
    • libghc-reform-hsp-doc/amd64 has unsatisfiable dependency
    • libghc-reform-hsp-prof/amd64 has unsatisfiable dependency
    • libghc-reform-hsp-dev/arm64 has unsatisfiable dependency
    • libghc-reform-hsp-doc/arm64 has unsatisfiable dependency
    • libghc-reform-hsp-prof/arm64 has unsatisfiable dependency
    • libghc-reform-hsp-dev/armel has unsatisfiable dependency
    • libghc-reform-hsp-prof/armel has unsatisfiable dependency
    • libghc-reform-hsp-dev/armhf has unsatisfiable dependency
    • libghc-reform-hsp-prof/armhf has unsatisfiable dependency
    • libghc-reform-hsp-dev/i386 has unsatisfiable dependency
    • libghc-reform-hsp-prof/i386 has unsatisfiable dependency
    • libghc-reform-hsp-dev/mips64el has unsatisfiable dependency
    • libghc-reform-hsp-prof/mips64el has unsatisfiable dependency
    • libghc-reform-hsp-dev/ppc64el has unsatisfiable dependency
    • libghc-reform-hsp-prof/ppc64el has unsatisfiable dependency
    • libghc-reform-hsp-dev/s390x has unsatisfiable dependency
    • libghc-reform-hsp-prof/s390x has unsatisfiable dependency
    • Updating haskell-reform-hsp would introduce bugs in testing: #1054865, #1056758
    • 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-reform-hsp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 785 days old (needed 5 days)
• haskell-tidal (- to 1.7.10-1)
  • Migration status for haskell-tidal (- to 1.7.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-tidal-dev/amd64 has unsatisfiable dependency
    • libghc-tidal-doc/amd64 has unsatisfiable dependency
    • libghc-tidal-prof/amd64 has unsatisfiable dependency
    • libghc-tidal-dev/arm64 has unsatisfiable dependency
    • libghc-tidal-doc/arm64 has unsatisfiable dependency
    • libghc-tidal-prof/arm64 has unsatisfiable dependency
    • libghc-tidal-dev/armel has unsatisfiable dependency
    • libghc-tidal-prof/armel has unsatisfiable dependency
    • libghc-tidal-dev/armhf has unsatisfiable dependency
    • libghc-tidal-prof/armhf has unsatisfiable dependency
    • libghc-tidal-dev/i386 has unsatisfiable dependency
    • libghc-tidal-prof/i386 has unsatisfiable dependency
    • libghc-tidal-dev/mips64el has unsatisfiable dependency
    • libghc-tidal-prof/mips64el has unsatisfiable dependency
    • libghc-tidal-dev/ppc64el has unsatisfiable dependency
    • libghc-tidal-prof/ppc64el has unsatisfiable dependency
    • libghc-tidal-dev/s390x has unsatisfiable dependency
    • libghc-tidal-prof/s390x has unsatisfiable dependency
    • Updating haskell-tidal would introduce bugs in testing: #1054931, #1057722
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on amd64: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on amd64: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on arm64: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on arm64: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armel: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armel: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armhf: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on armhf: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on i386: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on i386: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on mips64el: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on mips64el: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on riscv64: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on riscv64: libghc-primitive-dev (<< 0.8)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on s390x: libghc-hosc-dev (<< 0.20)
    • haskell-tidal unsatisfiable Build-Depends(-Arch) on s390x: libghc-primitive-dev (<< 0.8)
    • 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-tidal.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 785 days old (needed 5 days)
• ruby-jekyll-coffeescript (- to 1.2.2-3)
  • Migration status for ruby-jekyll-coffeescript (- to 1.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-coffeescript would introduce bugs in testing: #1030873
    • Depends: ruby-jekyll-coffeescript ruby-coffee-script (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-coffeescript.html
    • autopkgtest for ruby-jekyll-coffeescript/1.2.2-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 785 days old (needed 5 days)
• raku-hash-merge (- to 2.0.0-2)
  • Migration status for raku-hash-merge (- to 2.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-hash-merge dh-raku (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): raku-hash-merge prove6
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-hash-merge.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 ♻
    • 786 days old (needed 5 days)
• gcc-11-doc (- to 11.3.0-1)
  • Migration status for gcc-11-doc (- to 11.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-11-doc would introduce bugs in testing: #1057560
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 788 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
    • 789 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
    • autopkgtest for node-multiparty/blocked-on-ci-infra: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-multiparty.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 ♻
    • 789 days old (needed 5 days)
• ruby-mpi (- to 0.3.2-4)
  • Migration status for ruby-mpi (- to 0.3.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-mpi would introduce bugs in testing: #1076063, #1077402
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-mpi.html
    • Reproducible on armhf - info ♻
    • 789 days old (needed 5 days)
• sumaclust (- to 1.0.36+ds-2)
  • Migration status for sumaclust (- to 1.0.36+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sumaclust would introduce bugs in testing: #1075545
    • autopkgtest for sumaclust/1.0.36+ds-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): sumaclust sumalibs (not considered)
    • Depends: sumaclust sumalibs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sumaclust.html
    • Reproducible on armhf - info ♻
    • 794 days old (needed 5 days)
• sumatra (- to 1.0.36+ds-2)
  • Migration status for sumatra (- to 1.0.36+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sumatra sumalibs (not considered)
    • Depends: sumatra sumalibs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sumatra.html
    • autopkgtest for sumatra/1.0.36+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
    • 794 days old (needed 2 days)
• r-cran-bios2cor (- to 2.2.1-1)
  • Migration status for r-cran-bios2cor (- to 2.2.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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.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
    • 796 days old (needed 2 days)
• php-horde-rpc (- to 2.1.9-2)
  • Migration status for php-horde-rpc (- to 2.1.9-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-rpc php-horde-dav (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-rpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 799 days old (needed 5 days)
• apertium-cy-en (- to 0.1.1~r57554-9)
  • Migration status for apertium-cy-en (- to 0.1.1~r57554-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-cy-en would introduce bugs in testing: #1016320, #1080407
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-cy-en.html
    • autopkgtest for apertium-cy-en/0.1.1~r57554-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 801 days old (needed 2 days)
• apertium-hin (- to 0.1.0~r59158-4)
  • Migration status for apertium-hin (- to 0.1.0~r59158-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): apertium-hin hfst (not considered)
    • Depends: apertium-hin hfst (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-hin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 days old (needed 5 days)
• apertium-urd (- to 0.1.0~r61311-3)
  • Migration status for apertium-urd (- to 0.1.0~r61311-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): apertium-urd hfst (not considered)
    • Depends: apertium-urd hfst (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-urd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 801 days old (needed 5 days)
• apertium-mlt-ara (- to 0.2.0~r62623-3)
  • Migration status for apertium-mlt-ara (- to 0.2.0~r62623-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-mlt-ara would introduce bugs in testing: #1016336, #1080405
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-mlt-ara.html
    • 802 days old (needed 5 days)
• tuxpaint (- to 1:0.9.28-sdl2-1)
  • Migration status for tuxpaint (- to 1:0.9.28-sdl2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tuxpaint would introduce bugs in testing: #1075590
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tuxpaint.html
    • 802 days old (needed 5 days)
• apertium-urd-hin (- to 0.1.0~r64379-4)
  • Migration status for apertium-urd-hin (- to 0.1.0~r64379-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): apertium-urd-hin apertium-urd (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): apertium-urd-hin apertium-hin
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-urd-hin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 803 days old (needed 5 days)
• apertium-hbs-eng (- to 0.5.1-2)
  • Migration status for apertium-hbs-eng (- 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): apertium-hbs-eng hfst (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-hbs-eng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 804 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tboot.html
    • autopkgtest for tboot/1.10.5-4: amd64: No tests, superficial or marked flaky ♻
    • 805 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
    • Reproducible on armhf - info ♻
    • 806 days old (needed 5 days)
• libwordnet-querydata-perl (- to 1.49-2)
  • Migration status for libwordnet-querydata-perl (- to 1.49-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: libwordnet-querydata-perl wordnet (not considered)
    • Depends: libwordnet-querydata-perl wordnet (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libw/libwordnet-querydata-perl.html
    • autopkgtest for libwordnet-querydata-perl/1.49-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
    • 808 days old (needed 2 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:
    • Updating dvbcut would introduce bugs in testing: #1072411
    • Impossible Depends: dvbcut -> libavformat-extra60/7:6.1.1-5+b1/armel
    • Impossible Depends: dvbcut -> libavformat-extra60/7:6.1.1-5+b1/ppc64el
    • Impossible Depends: dvbcut -> libavformat60/7:6.1.1-5+b1/armhf
    • Impossible Depends: dvbcut -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: dvbcut -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: dvbcut -> libavformat60/7:6.1.1-5+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvbcut.html
    • Reproducible on armhf - info ♻
    • 810 days old (needed 5 days)
• raku-log (- to 0.3.1-4)
  • Migration status for raku-log (- to 0.3.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-log dh-raku (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-log.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 ♻
    • 810 days old (needed 5 days)
• raku-uri (- to 0.3.5-3)
  • Migration status for raku-uri (- to 0.3.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-uri dh-raku (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): raku-uri prove6
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-uri.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 ♻
    • 811 days old (needed 5 days)
• ippsample (- to 0.0~git20220607.72f89b3-1)
  • Migration status for ippsample (- to 0.0~git20220607.72f89b3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ippsample would introduce bugs in testing: #1042570, #1069333
    • Impossible Depends: ippsample -> libcups2/2.4.7-1+b1/armel
    • Impossible Depends: ippsample -> libcups2/2.4.7-1+b1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ippsample.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 816 days old (needed 5 days)
• kel-agent (- to 0.4.6-2)
  • Migration status for kel-agent (- to 0.4.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kel-agent would introduce bugs in testing: #1033710
    • autopkgtest for kel-agent/0.4.6-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • kel-agent/arm64 has unsatisfiable Built-Using on golang-1.21 1.21.3-1
    • Build-Depends(-Arch): kel-agent golang-github-k0swe-wsjtx-go (not considered)
    • Built-Using: kel-agent golang-github-k0swe-wsjtx-go (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kel-agent.html
    • 816 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
    • 816 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sql-formatter.html
    • autopkgtest for php-sql-formatter/1.2.17+dct1.1.3-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
    • 817 days old (needed 2 days)
• python-libguess (- to 1.1-5)
  • Migration status for python-libguess (- to 1.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-libguess libguess (not considered)
    • Depends: python-libguess libguess (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-libguess.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 818 days old (needed 5 days)
• apertium-crh-tur (- to 0.3.0-2)
  • Migration status for apertium-crh-tur (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-crh-tur would introduce bugs in testing: #1016319, #1080410
    • Build-Depends(-Arch): apertium-crh-tur hfst (not considered)
    • Depends: apertium-crh-tur hfst (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-crh-tur.html
    • 819 days old (needed 5 days)
• efitools (- to 1.9.2-3)
  • Migration status for efitools (- to 1.9.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating efitools would introduce bugs in testing: #1069410
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/efitools.html
    • 820 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/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 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 ♻
    • 821 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:
    • Updating classified-ads would introduce bugs in testing: #1076686, #1077359
    • Impossible Depends: classified-ads -> libminiupnpc17/2.2.6-1+b1/amd64
    • Impossible Depends: classified-ads -> libminiupnpc17/2.2.6-1+b1/arm64
    • Impossible Depends: classified-ads -> libminiupnpc17/2.2.6-1+b1/armel
    • Impossible Depends: classified-ads -> libminiupnpc17/2.2.6-1+b1/armhf
    • Impossible Depends: classified-ads -> libminiupnpc17/2.2.6-1+b1/i386
    • Impossible Depends: classified-ads -> libminiupnpc17/2.2.6-1+b1/mips64el
    • Impossible Depends: classified-ads -> libminiupnpc17/2.2.6-1+b1/ppc64el
    • Impossible Depends: classified-ads -> libminiupnpc17/2.2.6-1+b1/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/classified-ads.html
    • Reproducible on armhf - info ♻
    • 823 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
    • 823 days old (needed 2 days)
• libdevel-bt-perl (- to 0.06-5)
  • Migration status for libdevel-bt-perl (- to 0.06-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libdevel-bt-perl/amd64 has unsatisfiable dependency
    • libdevel-bt-perl/arm64 has unsatisfiable dependency
    • libdevel-bt-perl/armel has unsatisfiable dependency
    • libdevel-bt-perl/armhf has unsatisfiable dependency
    • libdevel-bt-perl/i386 has unsatisfiable dependency
    • libdevel-bt-perl/mips64el has unsatisfiable dependency
    • libdevel-bt-perl/ppc64el has unsatisfiable dependency
    • libdevel-bt-perl/s390x has unsatisfiable dependency
    • Updating libdevel-bt-perl would introduce bugs in testing: #1022133
    • autopkgtest for libdevel-bt-perl/0.06-5: riscv64: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libd/libdevel-bt-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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 823 days old (needed 5 days)
• lice5 (- to 1:5.3.0-1.1)
  • Migration status for lice5 (- to 1:5.3.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lice5 epic5 (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 823 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 ♻
    • 823 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 ♻
    • 823 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 ♻
    • 823 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 ♻
    • 823 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 ♻
    • 823 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 ♻
    • 823 days old (needed 5 days)
• php-net-nntp (- to 1.5.0-2.1)
  • Migration status for php-net-nntp (- to 1.5.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-nntp would introduce bugs in testing: #1065718
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-nntp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 823 days old (needed 5 days)
• php-text-wiki (- to 1.2.1-3.1)
  • Migration status for php-text-wiki (- to 1.2.1-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-text-wiki would introduce bugs in testing: #1065720
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-text-wiki.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 823 days old (needed 5 days)
• golang-github-k0swe-wsjtx-go (- to 4.0.1-1)
  • Migration status for golang-github-k0swe-wsjtx-go (- to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-k0swe-wsjtx-go would introduce bugs in testing: #1066758
    • autopkgtest for golang-github-k0swe-wsjtx-go/4.0.1-1: 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/g/golang-github-k0swe-wsjtx-go.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 825 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 ♻
    • 826 days old (needed 5 days)
• lmod (- to 8.6.19-1)
  • Migration status for lmod (- to 8.6.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lmod would introduce bugs in testing: #1052807
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lmod.html
    • autopkgtest for lmod/8.6.19-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 830 days old (needed 2 days)
• dynamic-motd (- to 0.04-1)
  • Migration status for dynamic-motd (- to 0.04-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dynamic-motd would introduce bugs in testing: #1029394
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/dynamic-motd.html
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 831 days old (needed 5 days)
• fcitx5-fbterm (- to 0.0~git20220315.620980b-2)
  • Migration status for fcitx5-fbterm (- to 0.0~git20220315.620980b-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: fcitx5-fbterm fbterm (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fcitx5-fbterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 832 days old (needed 5 days)
• golang-github-bsm-pool (- to 0.8.0-6)
  • Migration status for golang-github-bsm-pool (- to 0.8.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-bsm-pool would introduce bugs in testing: #1017816
    • autopkgtest for golang-github-bsm-pool/0.8.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bsm-pool.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 832 days old (needed 5 days)
• rust-ioctl-sys (- to 0.8.0-1)
  • Migration status for rust-ioctl-sys (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ioctl-sys/0.8.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, 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 ♻
    • 835 days old (needed 5 days)
• golang-github-bsm-redeo (- to 2.1.1-5)
  • Migration status for golang-github-bsm-redeo (- to 2.1.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-bsm-redeo golang-github-bsm-pool (not considered)
    • Depends: golang-github-bsm-redeo golang-github-bsm-pool (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bsm-redeo.html
    • autopkgtest for golang-github-bsm-redeo/2.1.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 836 days old (needed 2 days)
• kanboard-cli (- to 0.0.2-3)
  • Migration status for kanboard-cli (- to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kanboard-cli would introduce bugs in testing: #1060954
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kanboard-cli.html
    • 841 days old (needed 5 days)
• node-matrix-js-sdk (- to 9.11.0+~cs9.9.16-2)
  • Migration status for node-matrix-js-sdk (- to 9.11.0+~cs9.9.16-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-matrix-js-sdk would introduce bugs in testing: #1018970, #1021136, #1033621, #1080047, #958692, #994213
    • Build-Depends(-Arch): node-matrix-js-sdk node-request (not considered)
    • Depends: node-matrix-js-sdk node-request (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-matrix-js-sdk.html
    • autopkgtest for node-matrix-js-sdk/9.11.0+~cs9.9.16-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 842 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
    • 842 days old (needed 5 days)
• golang-github-siddontang-goredis (- to 0.0~git20150324.0.760763f-6)
  • Migration status for golang-github-siddontang-goredis (- to 0.0~git20150324.0.760763f-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-siddontang-goredis golang-github-alicebob-miniredis (not considered)
    • Depends: golang-github-siddontang-goredis golang-github-alicebob-miniredis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-siddontang-goredis.html
    • autopkgtest for golang-github-siddontang-goredis/0.0~git20150324.0.760763f-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 843 days old (needed 2 days)
• python-aiohttp-apispec (- to 3.0.0~b2+ds1-2)
  • Migration status for python-aiohttp-apispec (- to 3.0.0~b2+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-aiohttp-apispec/3.0.0~b2+ds1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, 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/p/python-aiohttp-apispec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 843 days old (needed 5 days)
• rust-assert-cli (- to 0.6.3-4)
  • Migration status for rust-assert-cli (- to 0.6.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-assert-cli/0.6.3-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for rust-assert-cli/blocked-on-ci-infra: riscv64: Regression or new test ♻
    • Build-Depends(-Arch): rust-assert-cli rust-failure (not considered)
    • Build-Depends(-Arch): rust-assert-cli rust-failure-derive (not considered)
    • Depends: rust-assert-cli rust-failure (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-assert-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 ♻
    • 844 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 ♻
    • 845 days old (needed 5 days)
• debpear (- to 0.5+nmu1)
  • Migration status for debpear (- to 0.5+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debpear would introduce bugs in testing: #1065710
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debpear.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 847 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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 ♻
    • 847 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 ♻
    • 850 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
  • 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 ♻
    • 853 days old (needed 5 days)
• xarclock (- to 1.0-19)
  • Migration status for xarclock (- to 1.0-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xarclock would introduce bugs in testing: #1075647
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xarclock.html
    • Reproducible on armhf - info ♻
    • 853 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
    • 856 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
    • 856 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
    • 856 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
    • Reproducible on armhf - info ♻
    • 856 days old (needed 5 days)
• raku-zef (- to 0.13.8-1)
  • Migration status for raku-zef (- to 0.13.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): raku-zef dh-raku (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): raku-zef prove6
    • Build-Depends(-Arch): raku-zef raku-getopt-long
    • Build-Depends(-Arch): raku-zef raku-tap-harness
    • Depends: raku-zef raku-getopt-long
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-zef.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 ♻
    • 856 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
    • 858 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
    • 858 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 ♻
    • 864 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
    • Build-Depends(-Arch): unburden-home-dir pcre3 (not considered)
  • 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
    • 871 days old (needed 2 days)
• vncsnapshot (- to 1.2a-5.2)
  • Migration status for vncsnapshot (- to 1.2a-5.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vncsnapshot would introduce bugs in testing: #1075626
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vncsnapshot.html
    • Reproducible on armhf - info ♻
    • 880 days old (needed 5 days)
• aiocoap (- to 0.4.3-0.1)
  • Migration status for aiocoap (- to 0.4.3-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aiocoap would introduce bugs in testing: #1013528
    • autopkgtest for aiocoap/0.4.3-0.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiocoap.html
    • 883 days old (needed 5 days)
• coyote (- to 2022.04.12-1)
  • Migration status for coyote (- to 2022.04.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating coyote would introduce bugs in testing: #1073520
    • autopkgtest for coyote/2022.04.12-1: amd64: Pass, arm64: Pass, riscv64: Pass
    • autopkgtest for coyote/blocked-on-ci-infra: ppc64el: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coyote.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 884 days old (needed 5 days)
• courier-authlib (- to 0.71.4-1)
  • Migration status for courier-authlib (- to 0.71.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating courier-authlib would introduce bugs in testing: #987009
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/courier-authlib.html
    • autopkgtest for courier-authlib/0.71.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 885 days old (needed 2 days)
• redmine-plugin-custom-css (- to 0.1.7+dfsg-1.1)
  • Migration status for redmine-plugin-custom-css (- to 0.1.7+dfsg-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: redmine-plugin-custom-css redmine (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/redmine-plugin-custom-css.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 886 days old (needed 5 days)
• lives (- to 3.0.2-1.2)
  • Migration status for lives (- to 3.0.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lives/amd64 has unsatisfiable dependency
    • lives-plugins/amd64 has unsatisfiable dependency
    • lives/arm64 has unsatisfiable dependency
    • lives-plugins/arm64 has unsatisfiable dependency
    • lives/armel has unsatisfiable dependency
    • lives-plugins/armel has unsatisfiable dependency
    • lives/armhf has unsatisfiable dependency
    • lives-plugins/armhf has unsatisfiable dependency
    • lives/i386 has unsatisfiable dependency
    • lives-plugins/i386 has unsatisfiable dependency
    • lives/mips64el has unsatisfiable dependency
    • lives-plugins/mips64el has unsatisfiable dependency
    • lives/ppc64el has unsatisfiable dependency
    • lives-plugins/ppc64el has unsatisfiable dependency
    • lives/s390x has unsatisfiable dependency
    • lives-plugins/s390x has unsatisfiable dependency
    • Updating lives would introduce bugs in testing: #1013421, #1057362
    • Impossible Depends: lives -> libglib2.0-0/2.78.4-1/armel
    • Impossible Depends: lives -> libglib2.0-0/2.78.4-1/armhf
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lives.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 888 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 ♻
    • 890 days old (needed 5 days)
• dia2code (- to 0.8.3-4.2)
  • Migration status for dia2code (- to 0.8.3-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dia2code would introduce bugs in testing: #1066667
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dia2code.html
    • 892 days old (needed 5 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
    • Reproducible on armhf - info ♻
    • 895 days old (needed 5 days)
• unicode-screensaver (- to 0.5.2-4)
  • Migration status for unicode-screensaver (- to 0.5.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unicode-screensaver would introduce bugs in testing: #1075606
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unicode-screensaver.html
    • Reproducible on armhf - info ♻
    • 895 days old (needed 5 days)
• deepin-album (- to 5.9.1+dfsg-1)
  • Migration status for deepin-album (- to 5.9.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating deepin-album would introduce bugs in testing: #1078276
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepin-album.html
    • Reproducible on armhf - info ♻
    • 897 days old (needed 5 days)
• i2masschroq (- to 0.4.54-1)
  • Migration status for i2masschroq (- to 0.4.54-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • i2masschroq/amd64 has unsatisfiable dependency
    • i2masschroq/arm64 has unsatisfiable dependency
    • i2masschroq/armel has unsatisfiable dependency
    • i2masschroq/armhf has unsatisfiable dependency
    • i2masschroq/i386 has unsatisfiable dependency
    • i2masschroq/mips64el has unsatisfiable dependency
    • i2masschroq/ppc64el has unsatisfiable dependency
    • i2masschroq/s390x has unsatisfiable dependency
    • Updating i2masschroq would introduce bugs in testing: #1028527
    • Not built on buildd: arch amd64 binaries uploaded by lopippo
    • Not built on buildd: arch all binaries uploaded by lopippo, a new source-only upload is needed to allow migration
    • Impossible Depends: i2masschroq -> libqt5core5a/5.15.10+dfsg-7/armel
    • Impossible Depends: i2masschroq -> libqt5core5a/5.15.10+dfsg-7/armhf
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/i/i2masschroq.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 897 days old (needed 5 days)
• xrstools (- to 0.15.0+git20210910+c147919d-3)
  • Migration status for xrstools (- to 0.15.0+git20210910+c147919d-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-xrstools/amd64 has unsatisfiable dependency
    • Updating xrstools would introduce bugs in testing: #1022504, #1056895
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/x/xrstools.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • 901 days old (needed 5 days)
• node-node-forge (- to 1.3.0~dfsg-1)
  • Migration status for node-node-forge (- to 1.3.0~dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-node-forge would introduce bugs in testing: #1002861
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-node-forge.html
    • autopkgtest for node-node-forge/1.3.0~dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 906 days old (needed 5 days)
• node-mermaid (- to 8.14.0+~cs11.4.14-1)
  • Migration status for node-mermaid (- to 8.14.0+~cs11.4.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-mermaid would introduce bugs in testing: #1001549, #1022630, #1036688
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mermaid.html
    • autopkgtest for node-mermaid/8.14.0+~cs11.4.14-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 908 days old (needed 2 days)
• fort77 (- to 1.15-12)
  • Migration status for fort77 (- to 1.15-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Updating fort77 would introduce bugs in testing: #1077390
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fort77.html
    • Reproducible on armhf - info ♻
    • 911 days old (needed 5 days)
    • Remove hint for (transitive) dependency: fort77
• qiskit-ibmq-provider (- to 0.4.6-4)
  • Migration status for qiskit-ibmq-provider (- to 0.4.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qiskit-ibmq-provider would introduce bugs in testing: #1025181, #1071812
    • autopkgtest for qiskit-ibmq-provider/0.4.6-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): qiskit-ibmq-provider qiskit-terra (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/q/qiskit-ibmq-provider.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 ♻
    • 916 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
    • 916 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/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
    • autopkgtest for rust-weedle/0.12.0-2: riscv64: No tests, superficial or marked flaky ♻
  • 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 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 ♻
    • 921 days old (needed 5 days)
• xmountains (- to 2.10-2)
  • Migration status for xmountains (- to 2.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xmountains would introduce bugs in testing: #1075674
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmountains.html
    • Reproducible on armhf - info ♻
    • 924 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 ♻
    • 934 days old (needed 5 days)
• garli (- to 2.1-7)
  • Migration status for garli (- to 2.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for garli/2.1-7: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for garli/blocked-on-ci-infra: armel: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/garli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 936 days old (needed 5 days)
• notcurses (- to 3.0.7+dfsg.1-1)
  • Migration status for notcurses (- to 3.0.7+dfsg.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating notcurses would introduce bugs in testing: #1001661, #1015747, #1072438
    • autopkgtest for notcurses/3.0.7+dfsg.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Impossible Depends: notcurses -> libavformat-extra60/7:6.1.1-5+b1/armhf
    • Impossible Depends: notcurses -> libavformat-extra60/7:6.1.1-5+b1/s390x
    • Impossible Depends: notcurses -> libavformat60/7:6.1.1-5+b1/armel
    • Impossible Depends: notcurses -> libavformat60/7:6.1.1-5+b1/i386
    • Impossible Depends: notcurses -> libavformat60/7:6.1.1-5+b1/mips64el
    • Impossible Depends: notcurses -> libavformat60/7:6.1.1-5+b1/ppc64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/notcurses.html
    • Reproducible on armhf - info ♻
    • 936 days old (needed 5 days)
• thin-provisioning-tools (- to 0.9.0-2)
  • Migration status for thin-provisioning-tools (- to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • thin-provisioning-tools/amd64 has unsatisfiable dependency
    • thin-provisioning-tools/arm64 has unsatisfiable dependency
    • thin-provisioning-tools/armel has unsatisfiable dependency
    • thin-provisioning-tools/armhf has unsatisfiable dependency
    • thin-provisioning-tools/i386 has unsatisfiable dependency
    • thin-provisioning-tools/mips64el has unsatisfiable dependency
    • thin-provisioning-tools/ppc64el has unsatisfiable dependency
    • thin-provisioning-tools/s390x has unsatisfiable dependency
    • Updating thin-provisioning-tools would introduce bugs in testing: #1041089
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/thin-provisioning-tools.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
    • 938 days old (needed 5 days)
• freeart (- to 3.3.0+ds1-3)
  • Migration status for freeart (- to 3.3.0+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-freeart/amd64 has unsatisfiable dependency
    • python3-freeart/arm64 has unsatisfiable dependency
    • python3-freeart/armel has unsatisfiable dependency
    • python3-freeart/armhf has unsatisfiable dependency
    • python3-freeart/i386 has unsatisfiable dependency
    • python3-freeart/mips64el has unsatisfiable dependency
    • python3-freeart/ppc64el has unsatisfiable dependency
    • Updating freeart would introduce bugs in testing: #1013606, #1056801
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/f/freeart.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 940 days old (needed 5 days)
• atheme-services (- to 7.2.12-1)
  • Migration status for atheme-services (- to 7.2.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating atheme-services would introduce bugs in testing: #1061308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/atheme-services.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 942 days old (needed 5 days)
• lbzip2 (- to 2.5-2.3)
  • Migration status for lbzip2 (- to 2.5-2.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lbzip2 would introduce bugs in testing: #1066240
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lbzip2.html
    • 943 days old (needed 5 days)
• node-devtools-protocol (- to 0.0.801017-1)
  • Migration status for node-devtools-protocol (- to 0.0.801017-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by andrius.merkys@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-devtools-protocol.html
    • autopkgtest for node-devtools-protocol/0.0.801017-1: amd64: No 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 ♻
    • 944 days old (needed 5 days)
• node-functional.js (- to 0.8.0-1)
  • Migration status for node-functional.js (- to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-functional.js would introduce bugs in testing: #1014605
    • Not built on buildd: arch all binaries uploaded by stephanlachnit@protonmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-functional.js.html
    • autopkgtest for node-functional.js/0.8.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 944 days old (needed 5 days)
• node-grunt-timer (- to 0.6.0-1)
  • Migration status for node-grunt-timer (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by stephanlachnit@protonmail.com, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): node-grunt-timer node-functional.js (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
    • autopkgtest for node-grunt-timer/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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 944 days old (needed 2 days)
• smrtanalysis (- to 0~20210112)
  • Migration status for smrtanalysis (- to 0~20210112): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: smrtanalysis blasr (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smrtanalysis.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 ♻
    • 944 days old (needed 5 days)
• r-cran-kernelheaping (- to 2.3.0-1)
  • Migration status for r-cran-kernelheaping (- to 2.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): r-cran-kernelheaping r-cran-sparr (not considered)
    • Depends: r-cran-kernelheaping r-cran-sparr (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-kernelheaping.html
    • autopkgtest for r-cran-kernelheaping/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 armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 945 days old (needed 2 days)
• pngphoon (- to 1.3-3)
  • Migration status for pngphoon (- to 1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pngphoon would introduce bugs in testing: #1065972
    • Impossible Depends: pngphoon -> libpng16-16/1.6.43-1/armel
    • Impossible Depends: pngphoon -> libpng16-16/1.6.43-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pngphoon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 948 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
    • 948 days old (needed 5 days)
• rust-exitfailure (- to 0.5.1-1)
  • Migration status for rust-exitfailure (- to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-exitfailure/0.5.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 ♻
    • autopkgtest for rust-exitfailure/blocked-on-ci-infra: riscv64: Regression or new test ♻
    • Build-Depends(-Arch): rust-exitfailure rust-failure (not considered)
    • Depends: rust-exitfailure rust-failure (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-exitfailure.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 ♻
    • 949 days old (needed 5 days)
• asterisk-flite (- to 3.0-4)
  • Migration status for asterisk-flite (- to 3.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): asterisk-flite asterisk (not considered)
    • Depends: asterisk-flite asterisk (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-flite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 951 days old (needed 5 days)
• 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
    • 953 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)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/t/tomogui.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 955 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 ♻
    • 960 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 ♻
    • 960 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 ♻
    • 961 days old (needed 5 days)
• moviepy (- to 1.0.3-2)
  • Migration status for moviepy (- to 1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating moviepy would introduce bugs in testing: #1004642, #1080051
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/moviepy.html
    • 963 days old (needed 5 days)
• xcb (- to 2.4-8)
  • Migration status for xcb (- to 2.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xcb would introduce bugs in testing: #1050607, #1081108
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcb.html
    • 969 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 ♻
    • 970 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: Regression or new test ♻, arm64: Regression or new test ♻, 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/i/idseq-bench.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 971 days old (needed 5 days)
• vstream-client (- to 1.2-7)
  • Migration status for vstream-client (- to 1.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vstream-client would introduce bugs in testing: #1075628
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vstream-client.html
    • 971 days old (needed 5 days)
• vdr-plugin-mp3 (- to 0.10.4-2)
  • Migration status for vdr-plugin-mp3 (- to 0.10.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: vdr-plugin-mp3 mplayer (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 975 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
    • 976 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 ♻
    • 977 days old (needed 5 days)
• massivethreads (- to 1.00-4)
  • Migration status for massivethreads (- to 1.00-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating massivethreads would introduce bugs in testing: #1014566
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/massivethreads.html
    • 979 days old (needed 5 days)
• rust-wasm-bindgen-webidl (- to 0.2.75-1)
  • Migration status for rust-wasm-bindgen-webidl (- to 0.2.75-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-wasm-bindgen-webidl-dev/amd64 has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/arm64 has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/armel has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/armhf has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/i386 has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/mips64el has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/ppc64el has unsatisfiable dependency
    • librust-wasm-bindgen-webidl-dev/s390x has unsatisfiable dependency
    • Updating rust-wasm-bindgen-webidl would introduce bugs in testing: #1035417
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on amd64: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on amd64: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on arm64: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on arm64: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armel: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armel: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armhf: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on armhf: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on i386: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on i386: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on mips64el: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on mips64el: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on ppc64el: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on ppc64el: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on s390x: librust-heck-0.3+default-dev
    • rust-wasm-bindgen-webidl unsatisfiable Build-Depends(-Arch) on s390x: librust-wasm-bindgen-backend-0.2.78+default-dev | librust-wasm-bindgen-backend-0.2.77+default-dev | librust-wasm-bindgen-backend-0.2.76+default-dev | librust-wasm-bindgen-backend-0.2.75+default-dev
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/amd64
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/arm64
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/armel
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/armhf
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/i386
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/mips64el
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/ppc64el
    • Impossible Build-Depends(-Arch): rust-wasm-bindgen-webidl -> librust-env-logger+default-dev/0.9.3-1/s390x
    • Build-Depends(-Arch): rust-wasm-bindgen-webidl rust-weedle (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-wasm-bindgen-webidl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 979 days old (needed 5 days)
• golang-github-go-redis-redis (- to 6.15.0-2)
  • Migration status for golang-github-go-redis-redis (- to 6.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-go-redis-redis would introduce bugs in testing: #985011
    • autopkgtest for golang-github-go-redis-redis/blocked-on-ci-infra: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-go-redis-redis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 980 days old (needed 5 days)
• ssvnc (- to 1.0.29-6)
  • Migration status for ssvnc (- to 1.0.29-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ssvnc would introduce bugs in testing: #1053080
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/ssvnc.html
    • Reproducible on armhf - info ♻
    • 981 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
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 982 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
    • Reproducible on armhf - info ♻
    • 983 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
    • 983 days old (needed 5 days)
• jnettop (- to 0.13.0-1.2)
  • Migration status for jnettop (- to 0.13.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jnettop would introduce bugs in testing: #1075103
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jnettop.html
    • Reproducible on armhf - info ♻
    • 985 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
    • autopkgtest for python-duckpy/3.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/p/python-duckpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 985 days old (needed 5 days)
• tiledarray (- to 1.0.0-1)
  • Migration status for tiledarray (- to 1.0.0-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 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
    • 985 days old (needed 5 days)
• mlucas (- to 20.1.1-1)
  • Migration status for mlucas (- to 20.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mlucas would introduce bugs in testing: #1013910, #1014547, #1027776, #1080048, #1081082
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlucas.html
    • 986 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
    • Build-Depends(-Arch): php-fxsl phpcpd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fxsl.html
    • autopkgtest for php-fxsl/1.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
    • 987 days old (needed 2 days)
• zmodemjs (- to 0.1.10+dfsg-2)
  • Migration status for zmodemjs (- to 0.1.10+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zmodemjs would introduce bugs in testing: #1005454
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zmodemjs.html
    • 989 days old (needed 5 days)
• indi-fishcamp (- to 1.1-1)
  • Migration status for indi-fishcamp (- 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): indi-fishcamp libfishcamp (not considered)
    • Depends: indi-fishcamp libfishcamp (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 990 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/ssed.html
    • autopkgtest for ssed/3.62-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
    • 991 days old (needed 2 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
    • 995 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
    • Reproducible on armhf - info ♻
    • 998 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1000 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
    • 1001 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
    • 1002 days old (needed 5 days)
• pidgin-sipe (- to 1.25.0-2.1)
  • Migration status for pidgin-sipe (- to 1.25.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pidgin-sipe/armel has unsatisfiable dependency
    • pidgin-sipe/armhf has unsatisfiable dependency
    • Updating pidgin-sipe would introduce bugs in testing: #1067783, #1081531
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pidgin-sipe.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1011 days old (needed 5 days)
• libguess (- to 1.2-5)
  • Migration status for libguess (- to 1.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libguess gauche (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libguess.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1012 days old (needed 5 days)
• epigrass (- to 3.0.3+dfsg-2)
  • Migration status for epigrass (- to 3.0.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating epigrass would introduce bugs in testing: #1079958, #995966, #998265
    • autopkgtest for epigrass/3.0.3+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: epigrass numba (not considered)
    • Depends: epigrass python-epimodels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epigrass.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1013 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/s390x has unsatisfiable dependency
    • Updating ruby-gsl would introduce bugs in testing: #1075462, #1076659
    • autopkgtest for ruby-gsl/2.1.0.3+dfsg1-5: riscv64: Pass
  • 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 s390x, not running autopkgtest there
    • Reproducible on armhf - info ♻
    • 1015 days old (needed 5 days)
• php-sabredav (- to 1.8.12-10)
  • Migration status for php-sabredav (- to 1.8.12-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-sabredav php-sabre-vobject (not considered)
    • Depends: php-sabredav php-sabre-vobject (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabredav.html
    • autopkgtest for php-sabredav/1.8.12-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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)
• ruby-diaspora-federation (- to 0.2.7-1)
  • Migration status for ruby-diaspora-federation (- to 0.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-diaspora-federation would introduce bugs in testing: #1006031
    • autopkgtest for ruby-diaspora-federation/0.2.7-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-diaspora-federation ruby-faraday-middleware (not considered)
    • Depends: ruby-diaspora-federation ruby-faraday-middleware (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-diaspora-federation.html
    • 1023 days old (needed 5 days)
• paper-css (- to 0.4.1+ds-1)
  • Migration status for paper-css (- to 0.4.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paper-css.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1027 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: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mongodb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1028 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
    • 1028 days old (needed 5 days)
• jquery-datetimepicker (- to 2.5.20+ds-1)
  • Migration status for jquery-datetimepicker (- to 2.5.20+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jquery-datetimepicker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 days old (needed 5 days)
• jquery-sortablejs (- to 1.0.0-1)
  • Migration status for jquery-sortablejs (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jquery-sortablejs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1029 days old (needed 5 days)
• materialize (- to 1.1.0~alpha+ds-1)
  • Migration status for materialize (- to 1.1.0~alpha+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating materialize would introduce bugs in testing: #1012320
    • materialize unsatisfiable Build-Depends(-Arch) on amd64: libjs-anime
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/materialize.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1029 days old (needed 5 days)
• ruby-batch-loader (- to 2.0.1+dfsg-3)
  • Migration status for ruby-batch-loader (- to 2.0.1+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-batch-loader would introduce bugs in testing: #1064754
    • autopkgtest for ruby-batch-loader/2.0.1+dfsg-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-batch-loader.html
    • 1029 days old (needed 5 days)
• node-solid-keychain (- to 0.1.3-3.1)
  • Migration status for node-solid-keychain (- to 0.1.3-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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: Regression or new test ♻, 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
    • 1033 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
    • 1037 days old (needed 5 days)
• sumalibs (- to 1.0.36-3)
  • Migration status for sumalibs (- to 1.0.36-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sumalibs would introduce bugs in testing: #1075544
    • autopkgtest for sumalibs/1.0.36-3: 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/s/sumalibs.html
    • Reproducible on armhf - info ♻
    • 1038 days old (needed 5 days)
• hyperic-sigar (- to 1.6.4+dfsg-7)
  • Migration status for hyperic-sigar (- to 1.6.4+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyperic-sigar would introduce bugs in testing: #1066435
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyperic-sigar.html
    • 1040 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 ♻
    • 1043 days old (needed 5 days)
• django-otp-yubikey (- to 1.0.0.post1-1)
  • Migration status for django-otp-yubikey (- to 1.0.0.post1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-otp-yubikey.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1046 days old (needed 5 days)
• django-widget-tweaks (- to 1.4.8-1)
  • Migration status for django-widget-tweaks (- to 1.4.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-widget-tweaks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1046 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
    • Reproducible on armhf - info ♻
    • 1048 days old (needed 5 days)
• golang-github-gambol99-go-marathon (- to 0.7.1-1)
  • Migration status for golang-github-gambol99-go-marathon (- to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alois@micard.lu, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gambol99-go-marathon.html
    • autopkgtest for golang-github-gambol99-go-marathon/0.7.1-1: amd64: Pass, arm64: Pass, 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
    • 1051 days old (needed 2 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
    • Reproducible on armhf - info ♻
    • 1052 days old (needed 5 days)
• taskd (- to 1.1.0+dfsg-4)
  • Migration status for taskd (- to 1.1.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating taskd would introduce bugs in testing: #1067462
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/taskd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1052 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
    • autopkgtest for ruby-github-pages-health-check/1.16.1-3: riscv64: Regression or new test ♻
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1054 days old (needed 5 days)
• esmtp (- to 1.2-18)
  • Migration status for esmtp (- to 1.2-18): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): esmtp libesmtp (not considered)
    • Depends: esmtp libesmtp (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/esmtp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1056 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
    • Reproducible on armhf - info ♻
    • 1057 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1058 days old (needed 5 days)
• soundkonverter (- to 3.0.1-3)
  • Migration status for soundkonverter (- to 3.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating soundkonverter would introduce bugs in testing: #1076142
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/soundkonverter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1058 days old (needed 5 days)
• kdrill (- to 6.5deb2-13)
  • Migration status for kdrill (- to 6.5deb2-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kdrill/armel has unsatisfiable dependency
    • kdrill/armhf has unsatisfiable dependency
    • Updating kdrill would introduce bugs in testing: #1066689
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdrill.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1059 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 ♻
    • 1060 days old (needed 5 days)
• nim-hts (- to 0.3.19+ds-1)
  • Migration status for nim-hts (- to 0.3.19+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nim-hts would introduce bugs in testing: #1081123
    • autopkgtest for nim-hts/0.3.19+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: Regression or new test ♻, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): nim-hts nim (not considered)
    • Depends: nim-hts nim (not considered)
  • 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
    • 1061 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
    • 1064 days old (needed 5 days)
• obs-websocket (- to 4.9.0-2)
  • Migration status for obs-websocket (- to 4.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • obs-websocket/armel has unsatisfiable dependency
    • obs-websocket/armhf has unsatisfiable dependency
    • Updating obs-websocket would introduce bugs in testing: #1006040
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-websocket.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1065 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/armel has unsatisfiable dependency
    • prads/armhf has unsatisfiable dependency
    • Updating prads would introduce bugs in testing: #1069335, #1081091, #999984
    • autopkgtest for prads/0.3.3-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Build-Depends(-Arch): prads pcre3 (not considered)
    • Depends: prads pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prads.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1065 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)
    • Depends: gabedit gtkglext (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
    • 1066 days old (needed 5 days)
• php-webimpress-safe-writer (- to 2.2.0-1)
  • Migration status for php-webimpress-safe-writer (- to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-webimpress-safe-writer would introduce bugs in testing: #1073572, #1079843, #981233
    • autopkgtest for php-webimpress-safe-writer/2.2.0-1: 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/p/php-webimpress-safe-writer.html
    • Reproducible on armhf - info ♻
    • 1067 days old (needed 5 days)
• tcm (- to 2.20+TSQD-7)
  • Migration status for tcm (- to 2.20+TSQD-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tcm would introduce bugs in testing: #1075555
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tcm.html
    • 1067 days old (needed 5 days)
• info-beamer (- to 1.0~pre3+dfsg-0.2)
  • Migration status for info-beamer (- to 1.0~pre3+dfsg-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • info-beamer/amd64 has unsatisfiable dependency
    • info-beamer/arm64 has unsatisfiable dependency
    • info-beamer/armel has unsatisfiable dependency
    • info-beamer/armhf has unsatisfiable dependency
    • info-beamer/i386 has unsatisfiable dependency
    • info-beamer/mips64el has unsatisfiable dependency
    • info-beamer/ppc64el has unsatisfiable dependency
    • info-beamer/s390x has unsatisfiable dependency
    • Updating info-beamer would introduce bugs in testing: #1004823
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/i/info-beamer.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1069 days old (needed 5 days)
• trololio (- to 1.0-3)
  • Migration status for trololio (- to 1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating trololio would introduce bugs in testing: #1059673
    • autopkgtest for trololio/1.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/t/trololio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1069 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/armel has unsatisfiable dependency
    • epic5/armhf 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 armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1071 days old (needed 5 days)
• sphinx-rst-builder (- to 0.0.3-3)
  • Migration status for sphinx-rst-builder (- to 0.0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sphinx-rst-builder would introduce bugs in testing: #1042587
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-rst-builder.html
    • 1071 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 ♻
    • 1074 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
    • 1076 days old (needed 5 days)
• nvchecker (- to 2.5-1)
  • Migration status for nvchecker (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nvchecker/2.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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 ♻
    • 1076 days old (needed 5 days)
• ggcov (- to 0.10-4)
  • Migration status for ggcov (- to 0.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ggcov/armel has unsatisfiable dependency
    • ggcov/armhf has unsatisfiable dependency
    • Updating ggcov would introduce bugs in testing: #1020263
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ggcov.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1080 days old (needed 5 days)
• libsx (- to 2.08-5)
  • Migration status for libsx (- to 2.08-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libsx libxaw3dxft (not considered)
    • Depends: libsx libxaw3dxft (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1080 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 ♻
    • 1084 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
    • 1086 days old (needed 5 days)
• ap-utils (- to 1.5-5)
  • Migration status for ap-utils (- to 1.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ap-utils would introduce bugs in testing: #1057542
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ap-utils.html
    • 1088 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)
    • 1096 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
    • 1098 days old (needed 2 days)
• shotdetect (- to 1.0.86-6)
  • Migration status for shotdetect (- to 1.0.86-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • shotdetect/amd64 has unsatisfiable dependency
    • shotdetect/arm64 has unsatisfiable dependency
    • shotdetect/armel has unsatisfiable dependency
    • shotdetect/armhf has unsatisfiable dependency
    • shotdetect/i386 has unsatisfiable dependency
    • shotdetect/mips64el has unsatisfiable dependency
    • shotdetect/ppc64el has unsatisfiable dependency
    • shotdetect/s390x has unsatisfiable dependency
    • Updating shotdetect would introduce bugs in testing: #1004719
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/shotdetect.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1098 days old (needed 5 days)
• jakarta-jmeter (- to 2.13-5)
  • Migration status for jakarta-jmeter (- to 2.13-5): 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): jakarta-jmeter dnsjava (not considered)
    • Depends: jakarta-jmeter dnsjava (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jakarta-jmeter.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 ♻
    • 1100 days old (needed 5 days)
    • Remove hint for (transitive) dependency: dnsjava, jakarta-jmeter
• eclipse-tracecompass (- to 7.0.0+repack-1)
  • Migration status for eclipse-tracecompass (- to 7.0.0+repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • eclipse-tracecompass/amd64 has unsatisfiable dependency
    • eclipse-tracecompass/arm64 has unsatisfiable dependency
    • Updating eclipse-tracecompass would introduce bugs in testing: #1010983, #1035594
    • autopkgtest for eclipse-tracecompass/7.0.0+repack-1: riscv64: Regression or new test ♻
    • eclipse-tracecompass unsatisfiable Build-Depends(-Arch) on amd64: libequinox-p2-ui-sdk-java
    • Build-Depends(-Arch): eclipse-tracecompass eclipse-cdt (not considered)
    • Build-Depends(-Arch): eclipse-tracecompass eclipse-remote
    • Build-Depends(-Arch): eclipse-tracecompass eclipse-wtp (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/eclipse-tracecompass.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1110 days old (needed 5 days)
• artha (- to 1.0.5-3)
  • Migration status for artha (- to 1.0.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): artha wordnet (not considered)
    • Depends: artha wordnet (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/artha.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1115 days old (needed 5 days)
• palp (- to 2.20-2)
  • Migration status for palp (- to 2.20-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating palp would introduce bugs in testing: #1066232
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/palp.html
    • 1115 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 ♻
    • 1117 days old (needed 5 days)
• morty (- to 0.2.0-3)
  • Migration status for morty (- to 0.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating morty would introduce bugs in testing: #1052139
    • 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 i386 binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/morty.html
    • autopkgtest for morty/0.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1120 days old (needed 2 days)
• wordnet (- to 1:3.0-37)
  • Migration status for wordnet (- to 1:3.0-37): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wordnet would introduce bugs in testing: #1066461
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wordnet.html
    • 1126 days old (needed 5 days)
• sctk (- to 2.4.10-20151007-1312Z+dfsg2-3.1)
  • Migration status for sctk (- to 2.4.10-20151007-1312Z+dfsg2-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sctk would introduce bugs in testing: #1066360
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sctk.html
    • 1138 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 ♻
    • 1154 days old (needed 5 days)
• mialmpick (- to 0.2.15-2)
  • Migration status for mialmpick (- to 0.2.15-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mialmpick libglade2 (not considered)
    • Depends: mialmpick libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): mialmpick gtkglext (not considered)
    • Depends: mialmpick gtkglext (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 ♻
    • 1200 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whizzytex.html
    • autopkgtest for whizzytex/1.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
    • 1203 days old (needed 2 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:
    • Updating scrollz would introduce bugs in testing: #1066483
    • Impossible Depends: scrollz -> libgnutls30/3.8.3-1/armel
    • Impossible Depends: scrollz -> libgnutls30/3.8.3-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scrollz.html
    • 1207 days old (needed 5 days)
• slic3r (- to 1.3.0+dfsg1-5)
  • Migration status for slic3r (- to 1.3.0+dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating slic3r would introduce bugs in testing: #1034848, #1081104
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r.html
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 1237 days old (needed 5 days)
• fuse-posixovl (- to 1.3-1)
  • Migration status for fuse-posixovl (- to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fuse-posixovl would introduce bugs in testing: #1071308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fuse-posixovl.html
    • 1241 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 ♻
    • 1255 days old (needed 5 days)
• spdx-licenses (- to 3.8+dfsg-3)
  • Migration status for spdx-licenses (- to 3.8+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spdx-licenses would introduce bugs in testing: #1079848, #975120
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spdx-licenses.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1256 days old (needed 5 days)
• dwarf-fortress (- to 0.47.04+dfsg1-1)
  • Migration status for dwarf-fortress (- to 0.47.04+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dwarf-fortress would introduce bugs in testing: #1069983
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1262 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 ♻
    • 1273 days old (needed 5 days)
• cde (- to 0.1+git9-g551e54d-1.2)
  • Migration status for cde (- to 0.1+git9-g551e54d-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cde would introduce bugs in testing: #1074871
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cde.html
    • 1283 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
    • Reproducible on armhf - info ♻
    • 1292 days old (needed 5 days)
• rust-rust-code-analysis-cli (- to 0.0.19-1)
  • Migration status for rust-rust-code-analysis-cli (- to 0.0.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-rust-code-analysis-cli would introduce bugs in testing: #1017649, #1080403
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-serde-yaml-0.8+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on arm64: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on arm64: librust-serde-yaml-0.8+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on armhf: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on armhf: librust-serde-yaml-0.8+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on i386: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on i386: librust-serde-yaml-0.8+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on mips64el: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on mips64el: librust-serde-yaml-0.8+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on ppc64el: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on ppc64el: librust-serde-yaml-0.8+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on s390x: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on s390x: librust-serde-yaml-0.8+default-dev
    • Build-Depends(-Arch): rust-rust-code-analysis-cli rust-rust-code-analysis (not considered)
    • Built-Using: rust-rust-code-analysis-cli rust-rust-code-analysis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rust-code-analysis-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 ♻
    • 1300 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
    • Updating hotspot would introduce bugs in testing: #1025573
  • Additional info:
    • Piuparts tested OK - 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1301 days old (needed 5 days)
• xmakemol (- to 5.16-10)
  • Migration status for xmakemol (- to 5.16-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xmakemol would introduce bugs in testing: #1075670
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmakemol.html
    • Reproducible on armhf - info ♻
    • 1302 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 ♻
    • 1303 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 ♻
    • 1306 days old (needed 5 days)
• espresso (- to 6.7-2)
  • Migration status for espresso (- to 6.7-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): espresso wannier90 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/espresso.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1307 days old (needed 5 days)
• slib (- to 3b6-3)
  • Migration status for slib (- to 3b6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for slib/3b6-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): slib mit-scheme (not considered)
    • Build-Depends(-Arch): slib scm (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slib.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 ♻
    • 1307 days old (needed 5 days)
• sa-exim (- to 4.2.1-20)
  • Migration status for sa-exim (- to 4.2.1-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sa-exim would introduce bugs in testing: #1075485
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sa-exim.html
    • Reproducible on armhf - info ♻
    • 1308 days old (needed 5 days)
• mydumper (- to 0.10.1-1)
  • Migration status for mydumper (- to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mydumper would introduce bugs in testing: #1000014
    • Build-Depends(-Arch): mydumper pcre3 (not considered)
    • Depends: mydumper pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mydumper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1312 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 ♻
    • 1313 days old (needed 5 days)
• zeek (- to 3.2.3+ds2-2)
  • Migration status for zeek (- to 3.2.3+ds2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • zeek/amd64 has unsatisfiable dependency
    • zeek/arm64 has unsatisfiable dependency
    • zeek/armel has unsatisfiable dependency
    • zeek/armhf has unsatisfiable dependency
    • zeek/i386 has unsatisfiable dependency
    • zeek/mips64el has unsatisfiable dependency
    • zeek/ppc64el has unsatisfiable dependency
    • zeek/s390x has unsatisfiable dependency
    • Updating zeek would introduce bugs in testing: #1002760
    • Build-Depends(-Arch): zeek broker (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/z/zeek.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 1313 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
    • Reproducible on armhf - info ♻
    • 1314 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
    • 1314 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
    • Reproducible on armhf - info ♻
    • 1314 days old (needed 5 days)
• pbsuite (- to 15.8.24+dfsg-7)
  • Migration status for pbsuite (- to 15.8.24+dfsg-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pbsuite blasr (not considered)
    • Invalidated by dependency
  • 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
    • autopkgtest for pbsuite/15.8.24+dfsg-7: amd64: Pass, arm64: 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
    • 1314 days old (needed 2 days)
• spyder-memory-profiler (- to 0.2.1-1)
  • Migration status for spyder-memory-profiler (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spyder-memory-profiler would introduce bugs in testing: #1035493, #1071813
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/spyder-memory-profiler.html
    • autopkgtest for spyder-memory-profiler/0.2.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • 1314 days old (needed 5 days)
• mplayer-blue (- to 1.13-2)
  • Migration status for mplayer-blue (- to 1.13-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mplayer-blue mplayer (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mplayer-blue.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1315 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
    • 1315 days old (needed 5 days)
• scmail (- to 1.3-4.1)
  • Migration status for scmail (- to 1.3-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): scmail gauche (not considered)
    • Depends: scmail gauche (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scmail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1315 days old (needed 5 days)
• apertium-kaz-tat (- to 0.2.1-1)
  • Migration status for apertium-kaz-tat (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-kaz-tat would introduce bugs in testing: #1005670, #1080408
    • Build-Depends(-Arch): apertium-kaz-tat hfst (not considered)
    • Depends: apertium-kaz-tat hfst (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-kaz-tat.html
    • 1317 days old (needed 5 days)
• apertium-sme-nob (- to 0.6.1+ds.1-2)
  • Migration status for apertium-sme-nob (- to 0.6.1+ds.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-sme-nob would introduce bugs in testing: #1008348, #1080411
    • apertium-sme-nob unsatisfiable Build-Depends(-Arch) on amd64: foma-bin
    • Build-Depends(-Arch): apertium-sme-nob hfst (not considered)
    • Depends: apertium-sme-nob hfst (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-sme-nob.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 ♻
    • 1317 days old (needed 5 days)
• rust-libnotcurses-sys (- to 2.1.8-1)
  • Migration status for rust-libnotcurses-sys (- to 2.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-libnotcurses-sys would introduce bugs in testing: #985813
    • autopkgtest for rust-libnotcurses-sys/blocked-on-ci-infra: amd64: Regression or new test ♻
    • Build-Depends(-Arch): rust-libnotcurses-sys notcurses (not considered)
    • Depends: rust-libnotcurses-sys notcurses (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libnotcurses-sys.html
    • 1317 days old (needed 5 days)
• openkim-models (- to 1:2021.01.28-2)
  • Migration status for openkim-models (- to 1:2021.01.28-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openkim-models would introduce bugs in testing: #1073680
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openkim-models.html
    • autopkgtest for openkim-models/1:2021.01.28-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
    • 1318 days old (needed 2 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• golang-github-alicebob-miniredis (- to 2.2.1-5)
  • Migration status for golang-github-alicebob-miniredis (- to 2.2.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-alicebob-miniredis golang-github-bsm-redeo (not considered)
    • Depends: golang-github-alicebob-miniredis golang-github-bsm-redeo (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-alicebob-miniredis.html
    • autopkgtest for golang-github-alicebob-miniredis/2.2.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1319 days old (needed 2 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
    • 1319 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)
    • 1319 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 ♻
    • 1320 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
    • 1320 days old (needed 5 days)
• backdoor-factory (- to 3.4.2+dfsg-5)
  • Migration status for backdoor-factory (- to 3.4.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating backdoor-factory would introduce bugs in testing: #1027037, #1080503
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/backdoor-factory.html
    • autopkgtest for backdoor-factory/3.4.2+dfsg-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1321 days old (needed 2 days)
• dfvfs (- to 20201219-1)
  • Migration status for dfvfs (- to 20201219-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dfvfs would introduce bugs in testing: #998527
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dfvfs.html
    • 1325 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
    • 1325 days old (needed 2 days)
• sagan (- to 1.2.0-1.2)
  • Migration status for sagan (- to 1.2.0-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sagan would introduce bugs in testing: #999968
    • Build-Depends(-Arch): sagan libesmtp (not considered)
    • Build-Depends(-Arch): sagan pcre3 (not considered)
    • Depends: sagan pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sagan.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1326 days old (needed 5 days)
• vg (- to 1.30.0+ds-1)
  • Migration status for vg (- to 1.30.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vg/amd64 has unsatisfiable dependency
    • vg/mips64el has unsatisfiable dependency
    • Updating vg would introduce bugs in testing: #1013061, #1081347
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vg.html
    • uninstallable on arch amd64, not running autopkgtest there
    • 1326 days old (needed 5 days)
• pong2 (- to 0.1.3-3)
  • Migration status for pong2 (- to 0.1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pong2 would introduce bugs in testing: #1075394
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pong2.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1329 days old (needed 5 days)
• rcs-blame (- to 1.3.1-4.2)
  • Migration status for rcs-blame (- to 1.3.1-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rcs-blame would introduce bugs in testing: #1069531
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rcs-blame.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1329 days old (needed 5 days)
• python-dugong (- to 3.8.1+dfsg-1)
  • Migration status for python-dugong (- to 3.8.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-dugong would introduce bugs in testing: #1002102
    • autopkgtest for python-dugong/blocked-on-ci-infra: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dugong.html
    • 1330 days old (needed 5 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 ♻
    • 1335 days old (needed 5 days)
• scram (- to 0.16.2-3)
  • Migration status for scram (- to 0.16.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scram would introduce bugs in testing: #1073328
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scram.html
    • 1337 days old (needed 5 days)
• gauche-c-wrapper (- to 0.6.1-12)
  • Migration status for gauche-c-wrapper (- to 0.6.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gauche-c-wrapper/amd64 has unsatisfiable dependency
    • gauche-c-wrapper/arm64 has unsatisfiable dependency
    • gauche-c-wrapper/armel has unsatisfiable dependency
    • gauche-c-wrapper/armhf has unsatisfiable dependency
    • gauche-c-wrapper/i386 has unsatisfiable dependency
    • gauche-c-wrapper/mips64el has unsatisfiable dependency
    • gauche-c-wrapper/ppc64el has unsatisfiable dependency
    • gauche-c-wrapper/s390x has unsatisfiable dependency
    • Updating gauche-c-wrapper would introduce bugs in testing: #1071045
    • Build-Depends(-Arch): gauche-c-wrapper gauche
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gauche-c-wrapper.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
    • 1338 days old (needed 5 days)
• khronos-opencl-man (- to 1.0~svn33624-5)
  • Migration status for khronos-opencl-man (- to 1.0~svn33624-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): khronos-opencl-man w3-dtd-mathml (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/khronos-opencl-man.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1338 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
    • Updating qstopmotion would introduce bugs in testing: #1058520
  • 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 ♻
    • 1338 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
    • 1342 days old (needed 5 days)
• subvertpy (- to 0.11.0-1)
  • Migration status for subvertpy (- to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-subvertpy/amd64 has unsatisfiable dependency
    • python3-subvertpy/arm64 has unsatisfiable dependency
    • python3-subvertpy/armel has unsatisfiable dependency
    • python3-subvertpy/armhf has unsatisfiable dependency
    • python3-subvertpy/i386 has unsatisfiable dependency
    • python3-subvertpy/mips64el has unsatisfiable dependency
    • python3-subvertpy/ppc64el has unsatisfiable dependency
    • python3-subvertpy/s390x has unsatisfiable dependency
    • Updating subvertpy would introduce bugs in testing: #1009423
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/subvertpy.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1342 days old (needed 5 days)
• android-platform-external-doclava (- to 6.0.1+r55-1.1)
  • Migration status for android-platform-external-doclava (- to 6.0.1+r55-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-external-doclava would introduce bugs in testing: #1012103
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-external-doclava.html
    • 1344 days old (needed 5 days)
• jodd (- to 3.8.6-1.1)
  • Migration status for jodd (- to 3.8.6-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jodd would introduce bugs in testing: #1071797, #1079847, #961298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jodd.html
    • 1344 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
    • 1344 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
    • 1344 days old (needed 5 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 ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1344 days old (needed 5 days)
• focalinux (- to 2010-09-3.1)
  • Migration status for focalinux (- to 2010-09-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating focalinux would introduce bugs in testing: #1051055
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/focalinux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1345 days old (needed 5 days)
• giblib (- to 1.2.4-13)
  • Migration status for giblib (- to 1.2.4-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • giblib1/armel has unsatisfiable dependency
    • giblib1/armhf has unsatisfiable dependency
    • Updating giblib would introduce bugs in testing: #1018021
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/giblib.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1345 days old (needed 5 days)
• hiki (- to 1.0.0-2.1)
  • Migration status for hiki (- to 1.0.0-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: hiki ruby-uconv (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hiki.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1345 days old (needed 5 days)
• jquery-simpletreemenu (- to 1.5.0-2.1)
  • Migration status for jquery-simpletreemenu (- to 1.5.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jquery-simpletreemenu would introduce bugs in testing: #979940
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jquery-simpletreemenu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1345 days old (needed 5 days)
• ltx (- to 2.6.2-1.1)
  • Migration status for ltx (- to 2.6.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ltx would introduce bugs in testing: #1064710
    • Build-Depends(-Arch): ltx node-expat (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ltx.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 ♻
    • 1345 days old (needed 5 days)
• golang-github-filosottile-b2 (- to 0.0~git20170207.b197f7a-1)
  • Migration status for golang-github-filosottile-b2 (- to 0.0~git20170207.b197f7a-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-filosottile-b2.html
    • autopkgtest for golang-github-filosottile-b2/0.0~git20170207.b197f7a-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1346 days old (needed 2 days)
• golang-github-gopherjs-jsbuiltin (- to 0.0~git20180426.5009155-1)
  • Migration status for golang-github-gopherjs-jsbuiltin (- to 0.0~git20180426.5009155-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gopherjs-jsbuiltin.html
    • autopkgtest for golang-github-gopherjs-jsbuiltin/0.0~git20180426.5009155-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1346 days old (needed 2 days)
• golang-github-nf-cr2 (- to 0.0~git20180623.4699471-1)
  • Migration status for golang-github-nf-cr2 (- to 0.0~git20180623.4699471-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-nf-cr2.html
    • autopkgtest for golang-github-nf-cr2/0.0~git20180623.4699471-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1346 days old (needed 2 days)
• golang-github-tomnomnom-linkheader (- to 0.1.0+git20180905.02ca582-1)
  • Migration status for golang-github-tomnomnom-linkheader (- to 0.1.0+git20180905.02ca582-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alexandre@alexandreviau.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-tomnomnom-linkheader.html
    • autopkgtest for golang-github-tomnomnom-linkheader/0.1.0+git20180905.02ca582-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1346 days old (needed 2 days)
• geekcode (- to 1.7.3-8)
  • Migration status for geekcode (- to 1.7.3-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating geekcode would introduce bugs in testing: #1066682
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geekcode.html
    • 1347 days old (needed 5 days)
• sawfish (- to 1:1.11.90-1.2)
  • Migration status for sawfish (- to 1:1.11.90-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sawfish rep-gtk (not considered)
    • Depends: sawfish rep-gtk (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sawfish.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 ♻
    • 1347 days old (needed 5 days)
• automake1.11 (- to 1:1.11.6-6)
  • Migration status for automake1.11 (- to 1:1.11.6-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating automake1.11 would introduce bugs in testing: #1038944
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/automake1.11.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1348 days old (needed 5 days)
• fbterm (- to 1.7-5)
  • Migration status for fbterm (- to 1.7-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): fbterm libx86 (not considered)
    • Depends: fbterm libx86 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fbterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1348 days old (needed 5 days)
• php-net-ipv6 (- to 1.3.0b4-1.1)
  • Migration status for php-net-ipv6 (- to 1.3.0b4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-ipv6 would introduce bugs in testing: #1004531
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-ipv6.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1348 days old (needed 5 days)
• php-net-whois (- to 1.0.5-3.2)
  • Migration status for php-net-whois (- to 1.0.5-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-whois would introduce bugs in testing: #1065712
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-whois.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1348 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 ♻
    • 1348 days old (needed 5 days)
• proxy-suite (- to 1.9.2.4-10.1)
  • Migration status for proxy-suite (- to 1.9.2.4-10.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating proxy-suite would introduce bugs in testing: #1066374
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/proxy-suite.html
    • 1348 days old (needed 5 days)
• ruby-faraday-middleware-multi-json (- to 0.0.6-2.1)
  • Migration status for ruby-faraday-middleware-multi-json (- to 0.0.6-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-faraday-middleware-multi-json would introduce bugs in testing: #1064767
    • autopkgtest for ruby-faraday-middleware-multi-json/0.0.6-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-faraday-middleware-multi-json ruby-faraday-middleware (not considered)
    • Depends: ruby-faraday-middleware-multi-json ruby-faraday-middleware (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-faraday-middleware-multi-json.html
    • 1348 days old (needed 5 days)
• ruby-nfc (- to 3.1.2-2)
  • Migration status for ruby-nfc (- to 3.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-nfc would introduce bugs in testing: #1075468
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-nfc.html
    • Reproducible on armhf - info ♻
    • 1349 days old (needed 5 days)
• wiliki (- to 0.6.2-1.1)
  • Migration status for wiliki (- to 0.6.2-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): wiliki gauche (not considered)
    • Depends: wiliki gauche (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wiliki.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1349 days old (needed 5 days)
• android-framework-23 (- to 6.0.1+r72-6)
  • Migration status for android-framework-23 (- to 6.0.1+r72-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-framework-23 would introduce bugs in testing: #1011567
    • Build-Depends(-Arch): android-framework-23 android-platform-build (not considered)
    • 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
    • 1350 days old (needed 2 days)
• android-platform-build (- to 1:10.0.0+r36-1)
  • Migration status for android-platform-build (- to 1:10.0.0+r36-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-build would introduce bugs in testing: #1042042, #1050437
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-build.html
    • 1350 days old (needed 5 days)
• auto-complete-el (- to 1.5.1-0.2)
  • Migration status for auto-complete-el (- to 1.5.1-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating auto-complete-el would introduce bugs in testing: #1077096
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/auto-complete-el.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1350 days old (needed 5 days)
• latexila (- to 3.22.0-1.1)
  • Migration status for latexila (- to 3.22.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating latexila would introduce bugs in testing: #1075131
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/latexila.html
    • Reproducible on armhf - info ♻
    • 1350 days old (needed 5 days)
• leap-archive-keyring (- to 2017.11.24+nmu1)
  • Migration status for leap-archive-keyring (- to 2017.11.24+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating leap-archive-keyring would introduce bugs in testing: #1079961, #880220
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/leap-archive-keyring.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1350 days old (needed 5 days)
• monkeysphere (- to 0.43-3.1)
  • Migration status for monkeysphere (- to 0.43-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • agent-transfer/amd64 has unsatisfiable dependency
    • agent-transfer/arm64 has unsatisfiable dependency
    • agent-transfer/armel has unsatisfiable dependency
    • agent-transfer/armhf has unsatisfiable dependency
    • agent-transfer/i386 has unsatisfiable dependency
    • agent-transfer/mips64el has unsatisfiable dependency
    • agent-transfer/ppc64el has unsatisfiable dependency
    • agent-transfer/s390x has unsatisfiable dependency
    • Updating monkeysphere would introduce bugs in testing: #1011900, #1071941
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/monkeysphere.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
    • 1350 days old (needed 5 days)
• nautilus-scripts-manager (- to 2.0-1.1)
  • Migration status for nautilus-scripts-manager (- to 2.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nautilus-scripts-manager would introduce bugs in testing: #1033761
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus-scripts-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1350 days old (needed 5 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 ♻
    • 1350 days old (needed 5 days)
• pysolfc-cardsets (- to 2.0+dfsg2-2.1)
  • Migration status for pysolfc-cardsets (- to 2.0+dfsg2-2.1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysolfc-cardsets.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1350 days old (needed 5 days)
• resvg (- to 0.8.0-4)
  • Migration status for resvg (- to 0.8.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-resvg-dev/amd64 has unsatisfiable dependency
    • librust-usvg-dev/amd64 has unsatisfiable dependency
    • librust-resvg-dev/arm64 has unsatisfiable dependency
    • librust-usvg-dev/arm64 has unsatisfiable dependency
    • librust-resvg-dev/armhf has unsatisfiable dependency
    • librust-usvg-dev/armhf has unsatisfiable dependency
    • librust-resvg-dev/i386 has unsatisfiable dependency
    • librust-usvg-dev/i386 has unsatisfiable dependency
    • librust-resvg-dev/mips64el has unsatisfiable dependency
    • librust-usvg-dev/mips64el has unsatisfiable dependency
    • librust-resvg-dev/ppc64el has unsatisfiable dependency
    • librust-usvg-dev/ppc64el has unsatisfiable dependency
    • librust-resvg-dev/s390x has unsatisfiable dependency
    • librust-usvg-dev/s390x has unsatisfiable dependency
    • Updating resvg would introduce bugs in testing: #1002188
    • resvg unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk-0+default-dev (>= 0.5.0-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on amd64: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on amd64: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on amd64: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk-0+default-dev (>= 0.5.0-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on arm64: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on arm64: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on arm64: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk-0+default-dev (>= 0.5.0-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on armhf: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on armhf: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on armhf: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on i386: librust-gtk-0+default-dev (>= 0.5.0-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on i386: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on i386: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on i386: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk-0+default-dev (>= 0.5.0-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on mips64el: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on mips64el: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on mips64el: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk-0+default-dev (>= 0.5.0-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on ppc64el: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on ppc64el: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on ppc64el: librust-roxmltree-0.7+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk-0+default-dev (>= 0.5.0-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on s390x: librust-jpeg-decoder-0.1-dev (>= 0.1.15-~~)
    • resvg unsatisfiable Build-Depends(-Arch) on s390x: librust-pico-args-0.3+default-dev
    • resvg unsatisfiable Build-Depends(-Arch) on s390x: librust-roxmltree-0.7+default-dev
    • Impossible Depends: resvg -> libqt5core5a/5.15.10+dfsg-7/armhf
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/resvg.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1350 days old (needed 5 days)
• w3-dtd-mathml (- to 2.0.0.0-5.1)
  • Migration status for w3-dtd-mathml (- to 2.0.0.0-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating w3-dtd-mathml would introduce bugs in testing: #994795
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/w3-dtd-mathml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1350 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
    • Reproducible on armhf - info ♻
    • 1351 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 ♻
    • 1351 days old (needed 5 days)
• vlogger (- to 1.3-4.1)
  • Migration status for vlogger (- to 1.3-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vlogger would introduce bugs in testing: #965867
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vlogger.html
    • 1351 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 ♻
    • 1357 days old (needed 5 days)
• asterisk-prompt-de (- to 2.0-1.2)
  • Migration status for asterisk-prompt-de (- to 2.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: asterisk-prompt-de asterisk (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk-prompt-de.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1358 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
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/broker.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
    • 1358 days old (needed 5 days)
• node-node-localstorage (- to 2.1.5-1)
  • Migration status for node-node-localstorage (- to 2.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-node-localstorage would introduce bugs in testing: #1013621
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-node-localstorage.html
    • autopkgtest for node-node-localstorage/2.1.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1358 days old (needed 2 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 ♻
    • 1361 days old (needed 5 days)
• jskeus (- to 1.2.4+dfsg-3)
  • Migration status for jskeus (- to 1.2.4+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • jskeus/armel has unsatisfiable dependency
    • jskeus/armhf has unsatisfiable dependency
    • Updating jskeus would introduce bugs in testing: #1069313
    • autopkgtest for jskeus/1.2.4+dfsg-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): jskeus euslisp (not considered)
    • Depends: jskeus euslisp (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jskeus.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1363 days old (needed 5 days)
• adabrowse (- to 4.0.3-14)
  • Migration status for adabrowse (- to 4.0.3-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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 ♻
    • 1364 days old (needed 5 days)
• dfwinreg (- to 20201006-1.1)
  • Migration status for dfwinreg (- to 20201006-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dfwinreg would introduce bugs in testing: #1074700
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dfwinreg.html
    • 1364 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
    • 1364 days old (needed 5 days)
• spyder-reports (- to 0.1.1-4)
  • Migration status for spyder-reports (- to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spyder-reports would introduce bugs in testing: #982647
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/spyder-reports.html
    • autopkgtest for spyder-reports/0.1.1-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • 1366 days old (needed 5 days)
• adacontrol (- to 1.21r6b-7)
  • Migration status for adacontrol (- to 1.21r6b-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • adacontrol/amd64 has unsatisfiable dependency
    • adacontrol/arm64 has unsatisfiable dependency
    • adacontrol/armel has unsatisfiable dependency
    • adacontrol/armhf has unsatisfiable dependency
    • adacontrol/i386 has unsatisfiable dependency
    • adacontrol/mips64el has unsatisfiable dependency
    • adacontrol/ppc64el has unsatisfiable dependency
    • adacontrol/s390x has unsatisfiable dependency
    • Updating adacontrol would introduce bugs in testing: #1008982, #1080507
    • adacontrol unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on armel: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on armhf: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on i386: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll19-dev (>= 21.0.0-2)
    • Build-Depends(-Arch): adacontrol asis (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adacontrol.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1370 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 ♻
    • 1370 days old (needed 5 days)
• libaws (- to 20.2-2)
  • Migration status for libaws (- to 20.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libaws-bin/amd64 has unsatisfiable dependency
    • libaws20-dev/amd64 has unsatisfiable dependency
    • libaws6/amd64 has unsatisfiable dependency
    • libaws-bin/arm64 has unsatisfiable dependency
    • libaws20-dev/arm64 has unsatisfiable dependency
    • libaws6/arm64 has unsatisfiable dependency
    • libaws-bin/armel has unsatisfiable dependency
    • libaws20-dev/armel has unsatisfiable dependency
    • libaws6/armel has unsatisfiable dependency
    • libaws-bin/armhf has unsatisfiable dependency
    • libaws20-dev/armhf has unsatisfiable dependency
    • libaws6/armhf has unsatisfiable dependency
    • libaws-bin/i386 has unsatisfiable dependency
    • libaws20-dev/i386 has unsatisfiable dependency
    • libaws6/i386 has unsatisfiable dependency
    • libaws-bin/mips64el has unsatisfiable dependency
    • libaws20-dev/mips64el has unsatisfiable dependency
    • libaws6/mips64el has unsatisfiable dependency
    • libaws-bin/ppc64el has unsatisfiable dependency
    • libaws20-dev/ppc64el has unsatisfiable dependency
    • libaws6/ppc64el has unsatisfiable dependency
    • libaws-bin/s390x has unsatisfiable dependency
    • libaws20-dev/s390x has unsatisfiable dependency
    • libaws6/s390x has unsatisfiable dependency
    • Updating libaws would introduce bugs in testing: #1008981, #1023114, #997457
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: gnat-10
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: gnat-10
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: gnat-10
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: gnat-10
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: gnat-10
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: gnat-10
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: gnat-10
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: gnat-10
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-unicode10-dev (>= 21)
    • Build-Depends(-Arch): libaws asis (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/liba/libaws.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1370 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
    • 1376 days old (needed 2 days)
• py-lz4framed (- to 0.14.0-1)
  • Migration status for py-lz4framed (- to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating py-lz4framed would introduce bugs in testing: #978287
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/py-lz4framed.html
    • autopkgtest for py-lz4framed/0.14.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 1379 days old (needed 5 days)
• leaflet-image (- to 0.4.0~dfsg-3)
  • Migration status for leaflet-image (- to 0.4.0~dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating leaflet-image would introduce bugs in testing: #1003260
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/leaflet-image.html
    • autopkgtest for leaflet-image/0.4.0~dfsg-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1380 days old (needed 5 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
    • Reproducible on armhf - info ♻
    • 1381 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: Pass, 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 ♻
    • Reproducible on i386 - info ♻
    • 1382 days old (needed 5 days)
• ruby-behance (- to 0.6.1-4)
  • Migration status for ruby-behance (- to 0.6.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-behance would introduce bugs in testing: #1025094
    • autopkgtest for ruby-behance/0.6.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): ruby-behance ruby-faraday-middleware (not considered)
    • Depends: ruby-behance ruby-faraday-middleware (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-behance.html
    • 1382 days old (needed 5 days)
• shoogle (- to 0.1.4-10)
  • Migration status for shoogle (- to 0.1.4-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: shoogle python-oauth2client (not considered)
    • Invalidated by dependency
  • 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
    • 1383 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 ♻
    • 1386 days old (needed 5 days)
• prelude-manager (- to 5.2.0-2)
  • Migration status for prelude-manager (- to 5.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prelude-manager would introduce bugs in testing: #1077422
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prelude-manager.html
    • Reproducible on armhf - info ♻
    • 1387 days old (needed 5 days)
• read-edid (- to 3.0.2-1.1)
  • Migration status for read-edid (- to 3.0.2-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): read-edid libx86 (not considered)
    • Depends: read-edid libx86 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/read-edid.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1387 days old (needed 5 days)
• rust-rust-code-analysis (- to 0.0.18-2)
  • Migration status for rust-rust-code-analysis (- to 0.0.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-rust-code-analysis-dev/amd64 has unsatisfiable dependency
    • librust-rust-code-analysis-dev/arm64 has unsatisfiable dependency
    • librust-rust-code-analysis-dev/armel has unsatisfiable dependency
    • librust-rust-code-analysis-dev/armhf has unsatisfiable dependency
    • librust-rust-code-analysis-dev/i386 has unsatisfiable dependency
    • librust-rust-code-analysis-dev/mips64el has unsatisfiable dependency
    • librust-rust-code-analysis-dev/ppc64el has unsatisfiable dependency
    • librust-rust-code-analysis-dev/s390x has unsatisfiable dependency
    • Updating rust-rust-code-analysis would introduce bugs in testing: #1031013, #1071891
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-enum-iterator-0.6+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-enum-iterator-0.6+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-enum-iterator-0.6+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-enum-iterator-0.6+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-enum-iterator-0.6+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-enum-iterator-0.6+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-enum-iterator-0.6+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-enum-iterator-0.6+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-tree-sitter-0.17+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-rust-code-analysis.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1387 days old (needed 5 days)
• chibi-scheme (- to 0.9.1-3)
  • Migration status for chibi-scheme (- to 0.9.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chibi-scheme would introduce bugs in testing: #1079846, #981762
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/chibi-scheme.html
  • Additional info:
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for chibi-scheme/0.9.1-3: amd64: Pass, arm64: Pass, ppc64el: Pass, 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
    • 1388 days old (needed 2 days)
• dahdi-tools (- to 1:3.1.0-2)
  • Migration status for dahdi-tools (- to 1:3.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): dahdi-tools dahdi-linux (not considered)
    • Depends: dahdi-tools dahdi-linux (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dahdi-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1392 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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
    • Reproducible on armhf - info ♻
    • 1394 days old (needed 5 days)
• ssm (- to 1.4.0-2)
  • Migration status for ssm (- to 1.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ssm libccp4 (not considered)
    • Depends: ssm libccp4 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/ssm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1396 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 (not considered)
    • 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
    • Reproducible on armhf - info ♻
    • 1398 days old (needed 5 days)
• directvnc (- to 0.7.8-1)
  • Migration status for directvnc (- to 0.7.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating directvnc would introduce bugs in testing: #1074914
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/directvnc.html
    • Reproducible on armhf - info ♻
    • 1399 days old (needed 5 days)
• hts-nim-tools (- to 0.2.1-1)
  • Migration status for hts-nim-tools (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hts-nim-tools would introduce bugs in testing: #1075071
    • Build-Depends(-Arch): hts-nim-tools nim (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-docopt (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-hts (not considered)
    • 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 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hts-nim-tools.html
    • autopkgtest for hts-nim-tools/0.2.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1400 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)
    • Depends: nim-d3 nim (not considered)
    • Invalidated by build-dependency
    • Invalidated by 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 ♻
    • Reproducible on i386 - info ♻
    • 1400 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 ♻
    • 1402 days old (needed 5 days)
• ruby-ldap (- to 0.9.20-2)
  • Migration status for ruby-ldap (- to 0.9.20-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-ldap would introduce bugs in testing: #1075465
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ldap.html
    • Reproducible on armhf - info ♻
    • 1404 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 ♻
    • 1404 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
    • 1405 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 ♻
    • 1412 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)
    • Depends: nim-regex nim (not considered)
    • Invalidated by build-dependency
    • Invalidated by 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 ♻
    • Reproducible on i386 - info ♻
    • 1413 days old (needed 5 days)
• libzorpll (- to 7.0.4.0-2)
  • Migration status for libzorpll (- to 7.0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libzorpll-7.0-4/amd64 has unsatisfiable dependency
    • libzorpll-7.0-4/arm64 has unsatisfiable dependency
    • libzorpll-7.0-4/armel has unsatisfiable dependency
    • libzorpll-7.0-4/armhf has unsatisfiable dependency
    • libzorpll-7.0-4/i386 has unsatisfiable dependency
    • libzorpll-7.0-4/mips64el has unsatisfiable dependency
    • libzorpll-7.0-4/ppc64el has unsatisfiable dependency
    • libzorpll-7.0-4/s390x has unsatisfiable dependency
    • Updating libzorpll would introduce bugs in testing: #1006506
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libz/libzorpll.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1418 days old (needed 5 days)
• gtetrinet (- to 0.7.11+git20200916.46e7ade-2)
  • Migration status for gtetrinet (- to 0.7.11+git20200916.46e7ade-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtetrinet would introduce bugs in testing: #1075048
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtetrinet.html
    • Reproducible on armhf - info ♻
    • 1421 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-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 ♻
    • 1423 days old (needed 5 days)
• php-horde-mnemo (- to 4.2.14-10)
  • Migration status for php-horde-mnemo (- to 4.2.14-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-mnemo php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mnemo.html
    • autopkgtest for php-horde-mnemo/4.2.14-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1423 days old (needed 2 days)
• php-net-dns2 (- to 1.5.0-1)
  • Migration status for php-net-dns2 (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-dns2 would introduce bugs in testing: #1042457
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-dns2.html
    • autopkgtest for php-net-dns2/1.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1425 days old (needed 2 days)
• rust-mdl (- to 1.0.4-1)
  • Migration status for rust-mdl (- to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-mdl would introduce bugs in testing: #1052952
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • Build-Depends(-Arch): rust-mdl rust-failure (not considered)
    • Depends: rust-mdl rust-failure (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-mdl.html
    • autopkgtest for rust-mdl/1.0.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1425 days old (needed 5 days)
• iitii (- to 0.0+git20191030.85209e0-2)
  • Migration status for iitii (- to 0.0+git20191030.85209e0-2): 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1426 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 ♻
    • 1428 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
    • 1432 days old (needed 5 days)
• libxaw3dxft (- to 1.6.2h-1)
  • Migration status for libxaw3dxft (- to 1.6.2h-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libxaw3dxft would introduce bugs in testing: #1075217
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxaw3dxft.html
    • autopkgtest for libxaw3dxft/1.6.2h-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
    • 1433 days old (needed 2 days)
• rust-rspotify (- to 0.7.0-3)
  • Migration status for rust-rspotify (- to 0.7.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-rspotify-dev/amd64 has unsatisfiable dependency
    • librust-rspotify-dev/arm64 has unsatisfiable dependency
    • librust-rspotify-dev/armel has unsatisfiable dependency
    • librust-rspotify-dev/armhf has unsatisfiable dependency
    • librust-rspotify-dev/i386 has unsatisfiable dependency
    • librust-rspotify-dev/mips64el has unsatisfiable dependency
    • librust-rspotify-dev/ppc64el has unsatisfiable dependency
    • librust-rspotify-dev/s390x has unsatisfiable dependency
    • Updating rust-rspotify would introduce bugs in testing: #1031072, #1071890
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-chrono-0.4+rustc-serialize-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on amd64: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-chrono-0.4+rustc-serialize-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on arm64: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-chrono-0.4+rustc-serialize-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armel: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-chrono-0.4+rustc-serialize-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on armhf: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-chrono-0.4+rustc-serialize-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on i386: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-chrono-0.4+rustc-serialize-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on mips64el: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-chrono-0.4+rustc-serialize-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on ppc64el: librust-webbrowser-0.5+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-base64-0.12+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-chrono-0.4+rustc-serialize-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-derive-builder-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-itertools-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-rand-0.7+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-reqwest-0.9+default-dev
    • rust-rspotify unsatisfiable Build-Depends(-Arch) on s390x: librust-webbrowser-0.5+default-dev
    • Build-Depends(-Arch): rust-rspotify rust-dotenv (not considered)
    • Build-Depends(-Arch): rust-rspotify rust-env-logger-0.7 (not considered)
    • Build-Depends(-Arch): rust-rspotify rust-failure (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-rspotify.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1440 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
    • Depends: php-horde-nag php-horde
    • Depends: php-horde-nag php-horde-dav
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-nag.html
    • autopkgtest for php-horde-nag/4.2.19-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1441 days old (needed 2 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 ♻
    • 1446 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 ♻
    • 1457 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
    • 1470 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 ♻
    • 1481 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
    • 1485 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
    • 1487 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
    • 1489 days old (needed 2 days)
• fortunes-es (- to 1.36)
  • Migration status for fortunes-es (- to 1.36): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fortunes-es would introduce bugs in testing: #1077423
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fortunes-es.html
    • Reproducible on armhf - info ♻
    • 1491 days old (needed 5 days)
• ruby-rails-assets-highlightjs (- to 9.12.0-3)
  • Migration status for ruby-rails-assets-highlightjs (- to 9.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-highlightjs would introduce bugs in testing: #946846
    • autopkgtest for ruby-rails-assets-highlightjs/9.12.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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-highlightjs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1491 days old (needed 5 days)
• fonts-pecita (- to 5.4-2)
  • Migration status for fonts-pecita (- to 5.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-pecita would introduce bugs in testing: #975810
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-pecita.html
    • 1492 days old (needed 5 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
    • Reproducible on armhf - info ♻
    • 1492 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1493 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 ♻
    • Reproducible on i386 - info ♻
    • 1493 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
    • 1494 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, #1073516
    • 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 ♻
    • 1497 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)
    • 1499 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)
    • 1499 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 ♻
    • 1500 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)
    • 1503 days old (needed 5 days)
• opensm (- to 3.3.23-2)
  • Migration status for opensm (- to 3.3.23-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensm would introduce bugs in testing: #1052380
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1506 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:
    • Updating gnucap-python would introduce bugs in testing: #1067335
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnucap-python.html
    • 1507 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
    • 1512 days old (needed 5 days)
• crazydiskinfo (- to 1.1.0-2)
  • Migration status for crazydiskinfo (- to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crazydiskinfo would introduce bugs in testing: #1080504, #997156
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crazydiskinfo.html
    • 1513 days old (needed 5 days)
• kwin-effect-xrdesktop (- to 0.15.1-1)
  • Migration status for kwin-effect-xrdesktop (- to 0.15.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kwin-effect-xrdesktop/amd64 has unsatisfiable dependency
    • kwin-effect-xrdesktop/arm64 has unsatisfiable dependency
    • kwin-effect-xrdesktop/armel has unsatisfiable dependency
    • kwin-effect-xrdesktop/armhf has unsatisfiable dependency
    • kwin-effect-xrdesktop/i386 has unsatisfiable dependency
    • kwin-effect-xrdesktop/mips64el has unsatisfiable dependency
    • kwin-effect-xrdesktop/ppc64el has unsatisfiable dependency
    • kwin-effect-xrdesktop/s390x has unsatisfiable dependency
    • Updating kwin-effect-xrdesktop would introduce bugs in testing: #1037382, #993015
    • Build-Depends(-Arch): kwin-effect-xrdesktop gxr (not considered)
    • Build-Depends(-Arch): kwin-effect-xrdesktop xrdesktop (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/kwin-effect-xrdesktop.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1513 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
    • Reproducible on armhf - info ♻
    • 1518 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 ♻
    • 1519 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 ♻
    • 1520 days old (needed 5 days)
• dune-pdelab (- to 2.7~20200605-2)
  • Migration status for dune-pdelab (- to 2.7~20200605-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libdune-pdelab-dev/amd64 has unsatisfiable dependency
    • libdune-pdelab-dev/arm64 has unsatisfiable dependency
    • libdune-pdelab-dev/armel has unsatisfiable dependency
    • libdune-pdelab-dev/armhf has unsatisfiable dependency
    • libdune-pdelab-dev/i386 has unsatisfiable dependency
    • libdune-pdelab-dev/mips64el has unsatisfiable dependency
    • libdune-pdelab-dev/ppc64el has unsatisfiable dependency
    • libdune-pdelab-dev/s390x has unsatisfiable dependency
    • Updating dune-pdelab would introduce bugs in testing: #1023356, #1080409, #976499
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/dune-pdelab.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1522 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• uci2wb (- to 4.1+git200714-1)
  • Migration status for uci2wb (- to 4.1+git200714-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating uci2wb would introduce bugs in testing: #1071727
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uci2wb.html
    • 1522 days old (needed 5 days)
• php-horde-whups (- to 3.0.12-7)
  • Migration status for php-horde-whups (- to 3.0.12-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-whups php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-whups.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1532 days old (needed 5 days)
• php-horde-gollem (- to 3.0.13-5)
  • Migration status for php-horde-gollem (- to 3.0.13-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-gollem php-horde (not considered)
    • Invalidated by dependency
    • Depends: php-horde-gollem php-horde-editor (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 ♻
    • 1533 days old (needed 5 days)
• php-horde-trean (- to 1.1.10-3)
  • Migration status for php-horde-trean (- to 1.1.10-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-trean php-horde (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-trean.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1533 days old (needed 5 days)
• php-horde-dav (- to 1.1.4-6)
  • Migration status for php-horde-dav (- to 1.1.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-dav php-sabredav (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-dav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1536 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 ♻
    • 1536 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-gollem
    • Depends: php-horde-groupware php-horde-kronolith (not considered)
    • Depends: php-horde-groupware php-horde-mnemo
    • Depends: php-horde-groupware php-horde-nag (not considered)
    • 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 ♻
    • 1536 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-gollem
    • Depends: php-horde-webmail php-horde-imp (not considered)
    • Depends: php-horde-webmail php-horde-ingo
    • Depends: php-horde-webmail php-horde-kronolith (not considered)
    • Depends: php-horde-webmail php-horde-mnemo
    • Depends: php-horde-webmail php-horde-nag (not considered)
    • 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 ♻
    • 1536 days old (needed 5 days)
• simutrans-pak64 (- to 121.0-1)
  • Migration status for simutrans-pak64 (- to 121.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: simutrans-pak64 simutrans (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simutrans-pak64.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1539 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 ♻
    • 1544 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
    • Reproducible on armhf - info ♻
    • 1544 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
    • Reproducible on armhf - info ♻
    • 1554 days old (needed 5 days)
• audtty (- to 0.1.12-5.1)
  • Migration status for audtty (- to 0.1.12-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating audtty would introduce bugs in testing: #1066318
    • Impossible Depends: audtty -> libglib2.0-0/2.78.4-1/armel
    • Impossible Depends: audtty -> libglib2.0-0/2.78.4-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/audtty.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1555 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 ♻
    • 1560 days old (needed 5 days)
• breezy-loom (- to 3.0.0+bzr167-1)
  • Migration status for breezy-loom (- to 3.0.0+bzr167-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating breezy-loom would introduce bugs in testing: #1080502, #988156
    • autopkgtest for breezy-loom/3.0.0+bzr167-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/breezy-loom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1567 days old (needed 5 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
    • 1572 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 ♻
    • 1572 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
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1573 days old (needed 2 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
    • 1578 days old (needed 2 days)
• telegram-purple (- to 1.4.3-3)
  • Migration status for telegram-purple (- to 1.4.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • telegram-purple/armel has unsatisfiable dependency
    • telegram-purple/armhf has unsatisfiable dependency
    • Updating telegram-purple would introduce bugs in testing: #1011846, #1040074
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telegram-purple.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1580 days old (needed 5 days)
• gearhead2 (- to 0.701-2)
  • Migration status for gearhead2 (- to 0.701-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: gearhead2 openimageio (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gearhead2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1585 days old (needed 5 days)
• vbetool (- to 1.1-5)
  • Migration status for vbetool (- to 1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vbetool would introduce bugs in testing: #1075615
    • Build-Depends(-Arch): vbetool libx86 (not considered)
    • Depends: vbetool libx86 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vbetool.html
    • 1594 days old (needed 5 days)
• sipxtapi (- to 3.3.0~test18+dfsg.1-0.1)
  • Migration status for sipxtapi (- to 3.3.0~test18+dfsg.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsipxtapi/amd64 has unsatisfiable dependency
    • libsipxtapi/arm64 has unsatisfiable dependency
    • libsipxtapi/armel has unsatisfiable dependency
    • libsipxtapi/armhf has unsatisfiable dependency
    • libsipxtapi/i386 has unsatisfiable dependency
    • libsipxtapi/mips64el has unsatisfiable dependency
    • libsipxtapi/ppc64el has unsatisfiable dependency
    • libsipxtapi/s390x has unsatisfiable dependency
    • Updating sipxtapi would introduce bugs in testing: #1058941, #984331, #986494, #999960
    • Build-Depends(-Arch): sipxtapi pcre3 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sipxtapi.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1595 days old (needed 5 days)
• libx86 (- to 1.1+ds1-12)
  • Migration status for libx86 (- to 1.1+ds1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libx86 would introduce bugs in testing: #1075218
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libx86.html
    • Reproducible on i386 - info ♻
    • 1599 days old (needed 5 days)
• lordsawar (- to 0.3.2+frogknows-1)
  • Migration status for lordsawar (- to 0.3.2+frogknows-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lordsawar would introduce bugs in testing: #1075234
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lordsawar.html
    • Reproducible on armhf - info ♻
    • 1602 days old (needed 5 days)
• rust-dotenv (- to 0.15.0-2)
  • Migration status for rust-dotenv (- to 0.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-dotenv would introduce bugs in testing: #1076369
    • 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 i386 binaries not found
    • Not built on buildd: upload info for arch ppc64el binaries not found
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-dotenv.html
    • autopkgtest for rust-dotenv/0.15.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
    • 1605 days old (needed 2 days)
• rust-librespot-protocol (- to 0.1.0-2)
  • Migration status for rust-librespot-protocol (- to 0.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-librespot-protocol would introduce bugs in testing: #1002238
    • autopkgtest for rust-librespot-protocol/0.1.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-librespot-protocol.html
    • 1606 days old (needed 5 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 armhf - info ♻
    • 1607 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/armel has unsatisfiable dependency
    • code-saturne-bin/armhf has unsatisfiable dependency
    • Updating code-saturne would introduce bugs in testing: #1066231
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/code-saturne.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1608 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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)
    • 1616 days old (needed 5 days)
• genwqe-user (- to 4.0.18-3.1)
  • Migration status for genwqe-user (- to 4.0.18-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating genwqe-user would introduce bugs in testing: #1069483
  • 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 ♻
    • 1616 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 ♻
    • 1616 days old (needed 5 days)
• rust-failure-derive (- to 0.1.7-2)
  • Migration status for rust-failure-derive (- to 0.1.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-failure-derive-dev/amd64 has unsatisfiable dependency
    • librust-failure-derive-dev/arm64 has unsatisfiable dependency
    • librust-failure-derive-dev/armel has unsatisfiable dependency
    • librust-failure-derive-dev/armhf has unsatisfiable dependency
    • librust-failure-derive-dev/i386 has unsatisfiable dependency
    • librust-failure-derive-dev/mips64el has unsatisfiable dependency
    • librust-failure-derive-dev/ppc64el has unsatisfiable dependency
    • librust-failure-derive-dev/s390x has unsatisfiable dependency
    • Updating rust-failure-derive would introduce bugs in testing: #1069798
    • autopkgtest for rust-failure-derive/blocked-on-ci-infra: riscv64: Regression or new test ♻
    • rust-failure-derive unsatisfiable Build-Depends(-Arch) on amd64: librust-synstructure-0.12+default-dev
    • rust-failure-derive unsatisfiable Build-Depends(-Arch) on arm64: librust-synstructure-0.12+default-dev
    • rust-failure-derive unsatisfiable Build-Depends(-Arch) on armel: librust-synstructure-0.12+default-dev
    • rust-failure-derive unsatisfiable Build-Depends(-Arch) on armhf: librust-synstructure-0.12+default-dev
    • rust-failure-derive unsatisfiable Build-Depends(-Arch) on i386: librust-synstructure-0.12+default-dev
    • rust-failure-derive unsatisfiable Build-Depends(-Arch) on mips64el: librust-synstructure-0.12+default-dev
    • rust-failure-derive unsatisfiable Build-Depends(-Arch) on ppc64el: librust-synstructure-0.12+default-dev
    • rust-failure-derive unsatisfiable Build-Depends(-Arch) on riscv64: librust-synstructure-0.12+default-dev
    • rust-failure-derive unsatisfiable Build-Depends(-Arch) on s390x: librust-synstructure-0.12+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-failure-derive.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 ♻
    • 1616 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/s390x has unsatisfiable dependency
    • Updating sdaps would introduce bugs in testing: #1001643, #1061159
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/sdaps.html
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • autopkgtest for sdaps/1.9.8-0.1: riscv64: No tests, superficial or marked flaky ♻
  • 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
    • 1616 days old (needed 5 days)
• ecb (- to 2.50+git20170628-1)
  • Migration status for ecb (- to 2.50+git20170628-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ecb would introduce bugs in testing: #1020168
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecb.html
    • 1619 days old (needed 5 days)
• libdmx (- to 1:1.1.4-2)
  • Migration status for libdmx (- to 1:1.1.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libdmx would introduce bugs in testing: #1035474
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdmx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1622 days old (needed 5 days)
• openexr-viewers (- to 2.3.0-1)
  • Migration status for openexr-viewers (- to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openexr-viewers/amd64 has unsatisfiable dependency
    • openexr-viewers/arm64 has unsatisfiable dependency
    • openexr-viewers/armel has unsatisfiable dependency
    • openexr-viewers/armhf has unsatisfiable dependency
    • openexr-viewers/i386 has unsatisfiable dependency
    • openexr-viewers/mips64el has unsatisfiable dependency
    • openexr-viewers/ppc64el has unsatisfiable dependency
    • openexr-viewers/s390x has unsatisfiable dependency
    • Updating openexr-viewers would introduce bugs in testing: #1017547
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/openexr-viewers.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1623 days old (needed 5 days)
• rust-failure (- to 0.1.7-1)
  • Migration status for rust-failure (- to 0.1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-failure/0.1.7-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for rust-failure/blocked-on-ci-infra: riscv64: Regression or new test ♻
    • Build-Depends(-Arch): rust-failure rust-failure-derive (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-failure.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 ♻
    • 1624 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 ♻
    • 1628 days old (needed 5 days)
• airport-utils (- to 2-8)
  • Migration status for airport-utils (- to 2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating airport-utils would introduce bugs in testing: #1080501, #414092
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/airport-utils.html
    • autopkgtest for airport-utils/2-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1629 days old (needed 2 days)
• telepathy-logger-qt (- to 17.09.0-1)
  • Migration status for telepathy-logger-qt (- to 17.09.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): telepathy-logger-qt telepathy-logger (not considered)
    • Depends: telepathy-logger-qt telepathy-logger (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telepathy-logger-qt.html
    • autopkgtest for telepathy-logger-qt/17.09.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
    • 1645 days old (needed 2 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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 ♻
    • 1650 days old (needed 5 days)
• aboot (- to 1.0~pre20200212-1)
  • Migration status for aboot (- to 1.0~pre20200212-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aboot-cross/amd64 has unsatisfiable dependency
    • aboot-cross/arm64 has unsatisfiable dependency
    • aboot-cross/armel has unsatisfiable dependency
    • aboot-cross/armhf has unsatisfiable dependency
    • aboot-cross/i386 has unsatisfiable dependency
    • aboot-cross/mips64el has unsatisfiable dependency
    • aboot-cross/ppc64el has unsatisfiable dependency
    • aboot-cross/s390x has unsatisfiable dependency
    • Updating aboot would introduce bugs in testing: #805988
    • 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 ♻
    • 1652 days old (needed 5 days)
• ruby-jekyll-mentions (- to 1.6.0-1)
  • Migration status for ruby-jekyll-mentions (- to 1.6.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-jekyll-mentions ruby-html-pipeline (not considered)
    • Depends: ruby-jekyll-mentions ruby-html-pipeline (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-mentions.html
    • autopkgtest for ruby-jekyll-mentions/1.6.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1653 days old (needed 2 days)
• win-iconv (- to 0.0.8-4)
  • Migration status for win-iconv (- to 0.0.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating win-iconv would introduce bugs in testing: #921904
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/win-iconv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1653 days old (needed 5 days)
• porg (- to 2:0.10-1.2)
  • Migration status for porg (- to 2:0.10-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • grop/armel has unsatisfiable dependency
    • grop/armhf has unsatisfiable dependency
    • Updating porg would introduce bugs in testing: #1068149
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/porg.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 ♻
    • 1655 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uml-utilities.html
    • Reproducible on armhf - info ♻
    • 1656 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
    • Reproducible on armhf - info ♻
    • 1659 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 ♻
    • 1660 days old (needed 5 days)
• gnat-gps (- to 19.2-3)
  • Migration status for gnat-gps (- to 19.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnat-gps/amd64 has unsatisfiable dependency
    • gnat-gps/arm64 has unsatisfiable dependency
    • gnat-gps/mips64el has unsatisfiable dependency
    • gnat-gps/ppc64el has unsatisfiable dependency
    • gnat-gps/s390x has unsatisfiable dependency
    • Updating gnat-gps would introduce bugs in testing: #936624, #979146
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-unicode9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-python18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-sqlite-bin
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-sqlite18-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll-xref19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgnatprj7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libgtkada19-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libpython2.7-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libtemplates-parser13-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax9-dev
    • gnat-gps unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-unicode9-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnat-gps.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1662 days old (needed 5 days)
• mod-gnutls (- to 0.9.0-1.1)
  • Migration status for mod-gnutls (- to 0.9.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mod-gnutls would introduce bugs in testing: #1050670, #942737
    • Impossible Depends: mod-gnutls -> libgnutls30/3.8.3-1/armel
    • Impossible Depends: mod-gnutls -> libgnutls30/3.8.3-1/armhf
    • Build-Depends(-Arch): mod-gnutls monkeysphere (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mod-gnutls.html
    • 1664 days old (needed 5 days)
• ruby-google-cloud-translate (- to 1.3.0-2)
  • Migration status for ruby-google-cloud-translate (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-google-cloud-translate/amd64 has unsatisfiable dependency
    • ruby-google-cloud-translate/arm64 has unsatisfiable dependency
    • Updating ruby-google-cloud-translate would introduce bugs in testing: #964607
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/ruby-google-cloud-translate.html
    • autopkgtest for ruby-google-cloud-translate/1.3.0-2: riscv64: Regression or new test ♻
    • ruby-google-cloud-translate unsatisfiable Build-Depends(-Arch) on amd64: ruby-googleauth (<< 0.10.0)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1678 days old (needed 5 days)
• kcov (- to 38+dfsg-1)
  • Migration status for kcov (- to 38+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kcov would introduce bugs in testing: #964654
    • Impossible Depends: kcov -> libdw1/0.190-1+b1/armel
    • Impossible Depends: kcov -> libdw1/0.190-1+b1/armhf
    • Impossible Depends: kcov -> libelf1/0.190-1+b1/armel
    • Impossible Depends: kcov -> libelf1/0.190-1+b1/armhf
    • Depends: kcov curl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcov.html
    • 1679 days old (needed 5 days)
• rust-include-dir-impl (- to 0.5.0-1)
  • Migration status for rust-include-dir-impl (- to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-include-dir-impl/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 ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for rust-include-dir-impl/blocked-on-ci-infra: riscv64: Regression or new test ♻
    • Build-Depends(-Arch): rust-include-dir-impl rust-failure (not considered)
    • Depends: rust-include-dir-impl rust-failure (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-include-dir-impl.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 ♻
    • 1684 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 ♻
    • 1686 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:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • 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 ♻
    • 1692 days old (needed 5 days)
    • Remove hint for (transitive) dependency: acpi-override
• 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
    • Build-Depends(-Arch): ghemical gtkglext (not considered)
    • Build-Depends(-Arch): ghemical libghemical
    • Build-Depends(-Arch): ghemical libglade2 (not considered)
    • Build-Depends(-Arch): ghemical mopac7
    • Build-Depends(-Arch): ghemical mpqc (not considered)
    • Depends: ghemical gtkglext (not considered)
    • Depends: ghemical libghemical
    • 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
    • 1696 days old (needed 5 days)
• mergelog (- to 4.5.1-10)
  • Migration status for mergelog (- to 4.5.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mergelog would introduce bugs in testing: #1075264
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mergelog.html
    • Reproducible on armhf - info ♻
    • 1700 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 ♻
    • 1717 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
    • Reproducible on armhf - info ♻
    • 1718 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
    • Reproducible on armhf - info ♻
    • 1718 days old (needed 5 days)
• dirspec (- to 13.10-1.1)
  • Migration status for dirspec (- to 13.10-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dirspec would introduce bugs in testing: #949937
    • dirspec unsatisfiable Build-Depends(-Arch) on amd64: pep8
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dirspec.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1727 days old (needed 5 days)
• opensta (- to 0~20191111gitc018cb2+dfsg-1)
  • Migration status for opensta (- to 0~20191111gitc018cb2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensta would introduce bugs in testing: #1037806
    • Impossible Depends: opensta -> libreadline8/8.2-3+b1/armel
    • Impossible Depends: opensta -> libreadline8/8.2-3+b1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensta.html
    • 1728 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1730 days old (needed 2 days)
• brickos (- to 0.9.0.dfsg-12.2)
  • Migration status for brickos (- to 0.9.0.dfsg-12.2): 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 ♻
    • 1733 days old (needed 5 days)
• check-all-the-things (- to 2017.05.20+nmu1)
  • Migration status for check-all-the-things (- to 2017.05.20+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating check-all-the-things would introduce bugs in testing: #1071792, #862378
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/check-all-the-things.html
    • 1735 days old (needed 5 days)
• golang-github-ulule-limiter (- to 3.3.3-1)
  • Migration status for golang-github-ulule-limiter (- to 3.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-ulule-limiter/3.3.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • 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)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ulule-limiter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1748 days old (needed 5 days)
• thawab (- to 4.1-2)
  • Migration status for thawab (- to 4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • thawab/amd64 has unsatisfiable dependency
    • thawab/arm64 has unsatisfiable dependency
    • Updating thawab would introduce bugs in testing: #1071083, #990746
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 1762 days old (needed 5 days)
• golang-github-getlantern-errors (- to 0.0~git20190325.abdb3e3-2)
  • Migration status for golang-github-getlantern-errors (- to 0.0~git20190325.abdb3e3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-getlantern-errors/0.0~git20190325.abdb3e3-2: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-getlantern-errors golang-github-getlantern-ops (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getlantern-errors.html
    • Reproducible on amd64 - info ♻
    • 1766 days old (needed 5 days)
• vtun (- to 3.0.4-2)
  • Migration status for vtun (- to 3.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vtun would introduce bugs in testing: #1064613
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vtun.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1767 days old (needed 5 days)
• ruby-coffee-script (- to 2.4.1-2)
  • Migration status for ruby-coffee-script (- to 2.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-coffee-script would introduce bugs in testing: #1019927
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-coffee-script.html
    • autopkgtest for ruby-coffee-script/2.4.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 1769 days old (needed 5 days)
• telepathy-logger (- to 0.8.2-4)
  • Migration status for telepathy-logger (- to 0.8.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telepathy-logger would introduce bugs in testing: #1075559
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telepathy-logger.html
    • Reproducible on armhf - info ♻
    • 1771 days old (needed 5 days)
• jsunit (- to 0.2.2-2)
  • Migration status for jsunit (- to 0.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jsunit would introduce bugs in testing: #1079849, #974083
    • autopkgtest for jsunit/blocked-on-ci-infra: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsunit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1774 days old (needed 5 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
    • Reproducible on armhf - info ♻
    • 1783 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 ♻
    • 1784 days old (needed 5 days)
• pymia (- to 0.1.9-2.1)
  • Migration status for pymia (- to 0.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): pymia mia (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymia.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 ♻
    • 1787 days old (needed 5 days)
• irsim (- to 9.7.104-1)
  • Migration status for irsim (- to 9.7.104-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating irsim would introduce bugs in testing: #997299
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/irsim.html
    • 1791 days old (needed 5 days)
• socket-activate (- to 0.1-2)
  • Migration status for socket-activate (- to 0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating socket-activate would introduce bugs in testing: #1079771, #922504
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socket-activate.html
    • 1806 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
    • 1814 days old (needed 5 days)
• python-pyramid-multiauth (- to 0.8.0-1.1)
  • Migration status for python-pyramid-multiauth (- to 0.8.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pyramid-multiauth would introduce bugs in testing: #997297
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyramid-multiauth.html
    • 1817 days old (needed 5 days)
• gigedit (- to 1.1.1-1)
  • Migration status for gigedit (- to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gigedit/amd64 has unsatisfiable dependency
    • gigedit/arm64 has unsatisfiable dependency
    • gigedit/armel has unsatisfiable dependency
    • gigedit/armhf has unsatisfiable dependency
    • gigedit/i386 has unsatisfiable dependency
    • gigedit/mips64el has unsatisfiable dependency
    • gigedit/ppc64el has unsatisfiable dependency
    • gigedit/s390x has unsatisfiable dependency
    • Updating gigedit would introduce bugs in testing: #1079966, #997203
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gigedit.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1829 days old (needed 5 days)
• ruby-jekyll-gist (- to 1.5.0-2)
  • Migration status for ruby-jekyll-gist (- to 1.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-gist would introduce bugs in testing: #1059707
    • autopkgtest for ruby-jekyll-gist/1.5.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-jekyll-gist.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1830 days old (needed 5 days)
• umlet (- to 13.3-1.3)
  • Migration status for umlet (- to 13.3-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umlet would introduce bugs in testing: #965851
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umlet.html
    • 1831 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
    • 1832 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
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1836 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 ♻
    • 1838 days old (needed 5 days)
• golang-github-jesseduffield-gocui (- to 0.3.0+git20190803.ad0cd60-1)
  • Migration status for golang-github-jesseduffield-gocui (- to 0.3.0+git20190803.ad0cd60-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-gocui would introduce bugs in testing: #1032109
    • Build-Depends(-Arch): golang-github-jesseduffield-gocui golang-github-jesseduffield-termbox-go (not considered)
    • Depends: golang-github-jesseduffield-gocui golang-github-jesseduffield-termbox-go (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-gocui.html
    • autopkgtest for golang-github-jesseduffield-gocui/0.3.0+git20190803.ad0cd60-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1841 days old (needed 2 days)
• matanza (- to 0.13+ds2-1)
  • Migration status for matanza (- to 0.13+ds2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating matanza would introduce bugs in testing: #1075255
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matanza.html
    • Reproducible on armhf - info ♻
    • 1844 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
    • 1845 days old (needed 5 days)
• libss7 (- to 2.0.0-3)
  • Migration status for libss7 (- to 2.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libss7 would introduce bugs in testing: #1069523
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libss7.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1856 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
    • 1859 days old (needed 5 days)
• rust-pbr (- to 1.0.1-1)
  • Migration status for rust-pbr (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-pbr would introduce bugs in testing: #1053638
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pbr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1863 days old (needed 5 days)
• profitbricks-sdk-python (- to 4.1.3-3)
  • Migration status for profitbricks-sdk-python (- to 4.1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating profitbricks-sdk-python would introduce bugs in testing: #1020092
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/profitbricks-sdk-python.html
    • 1880 days old (needed 5 days)
• nbibtex (- to 0.9.18-13)
  • Migration status for nbibtex (- to 0.9.18-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nbibtex would introduce bugs in testing: #1030454
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nbibtex.html
    • 1883 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 ♻
    • Reproducible on armhf - info ♻
    • 1893 days old (needed 5 days)
• pluginhook (- to 0~20150216.0~a320158-2.1)
  • Migration status for pluginhook (- to 0~20150216.0~a320158-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pluginhook would introduce bugs in testing: #1079844, #972915
    • pluginhook/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • pluginhook/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pluginhook.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1905 days old (needed 5 days)
• averell (- to 1.2.5-1.1)
  • Migration status for averell (- to 1.2.5-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): averell erlang-cowboy (not considered)
    • Depends: averell erlang-cowboy (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/averell.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1941 days old (needed 5 days)
• libapache2-mod-defensible (- to 1.4-3.2)
  • Migration status for libapache2-mod-defensible (- to 1.4-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-defensible would introduce bugs in testing: #965622, #998981
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-defensible.html
    • 1942 days old (needed 5 days)
• golang-github-getlantern-ops (- to 0.0~git20190325.d70cb0d-1)
  • Migration status for golang-github-getlantern-ops (- to 0.0~git20190325.d70cb0d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by micah, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-getlantern-ops.html
    • autopkgtest for golang-github-getlantern-ops/0.0~git20190325.d70cb0d-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 1977 days old (needed 2 days)
• pyfr (- to 1.5.0-3)
  • Migration status for pyfr (- to 1.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyfr would introduce bugs in testing: #997427
    • autopkgtest for pyfr/1.5.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfr.html
    • 2019 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 ♻
    • 2022 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 ♻
    • 2022 days old (needed 5 days)
• dnssecjava (- to 1.1.3-3)
  • Migration status for dnssecjava (- to 1.1.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
    • Build-Depends(-Arch): dnssecjava dnsjava (not considered)
    • Depends: dnssecjava dnsjava (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnssecjava.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2023 days old (needed 5 days)
    • Remove hint for (transitive) dependency: dnsjava, dnssecjava
• ffproxy (- to 1.6-12)
  • Migration status for ffproxy (- to 1.6-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ffproxy would introduce bugs in testing: #1074954
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/ffproxy.html
    • Reproducible on armhf - info ♻
    • 2034 days old (needed 5 days)
• libapache2-mod-auth-cas (- to 1.2-1)
  • Migration status for libapache2-mod-auth-cas (- to 1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-auth-cas would introduce bugs in testing: #1000068
    • Build-Depends(-Arch): libapache2-mod-auth-cas pcre3 (not considered)
    • Depends: libapache2-mod-auth-cas pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-auth-cas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2037 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
    • 2040 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
    • 2042 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
    • 2046 days old (needed 5 days)
• sqwebmail-de (- to 6.0.0-1)
  • Migration status for sqwebmail-de (- to 6.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sqwebmail-de courier (not considered)
    • Built-Using: sqwebmail-de courier (not considered)
    • Depends: sqwebmail-de courier (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqwebmail-de.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2056 days old (needed 5 days)
• yorick-full (- to 2.2.04+dfsg1+full)
  • Migration status for yorick-full (- to 2.2.04+dfsg1+full): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: yorick-full yorick-ynfft (not considered)
    • Invalidated by dependency
    • Depends: yorick-full yorick-mira
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-full.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2066 days old (needed 5 days)
• gozer (- to 0.7.nofont.1-7)
  • Migration status for gozer (- to 0.7.nofont.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gozer/armel has unsatisfiable dependency
    • gozer/armhf has unsatisfiable dependency
    • Build-Depends(-Arch): gozer giblib (not considered)
    • Depends: gozer giblib (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gozer.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 ♻
    • Reproducible on i386 - info ♻
    • 2071 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)
    • 2071 days old (needed 5 days)
• vibe.d (- to 0.8.4-2)
  • Migration status for vibe.d (- to 0.8.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libvibe-core0/amd64 has unsatisfiable dependency
    • libvibe-crypto0/amd64 has unsatisfiable dependency
    • libvibe-data0/amd64 has unsatisfiable dependency
    • libvibe-http0/amd64 has unsatisfiable dependency
    • libvibe-inet0/amd64 has unsatisfiable dependency
    • libvibe-mail0/amd64 has unsatisfiable dependency
    • libvibe-mongodb0/amd64 has unsatisfiable dependency
    • libvibe-redis0/amd64 has unsatisfiable dependency
    • libvibe-stream0/amd64 has unsatisfiable dependency
    • libvibe-textfilter0/amd64 has unsatisfiable dependency
    • libvibe-tls0/amd64 has unsatisfiable dependency
    • libvibe-utils0/amd64 has unsatisfiable dependency
    • libvibe-web0/amd64 has unsatisfiable dependency
    • libvibe-core0/arm64 has unsatisfiable dependency
    • libvibe-crypto0/arm64 has unsatisfiable dependency
    • libvibe-data0/arm64 has unsatisfiable dependency
    • libvibe-http0/arm64 has unsatisfiable dependency
    • libvibe-inet0/arm64 has unsatisfiable dependency
    • libvibe-mail0/arm64 has unsatisfiable dependency
    • libvibe-mongodb0/arm64 has unsatisfiable dependency
    • libvibe-redis0/arm64 has unsatisfiable dependency
    • libvibe-stream0/arm64 has unsatisfiable dependency
    • libvibe-textfilter0/arm64 has unsatisfiable dependency
    • libvibe-tls0/arm64 has unsatisfiable dependency
    • libvibe-utils0/arm64 has unsatisfiable dependency
    • libvibe-web0/arm64 has unsatisfiable dependency
    • libvibe-core0/armhf has unsatisfiable dependency
    • libvibe-crypto0/armhf has unsatisfiable dependency
    • libvibe-data0/armhf has unsatisfiable dependency
    • libvibe-http0/armhf has unsatisfiable dependency
    • libvibe-inet0/armhf has unsatisfiable dependency
    • libvibe-mail0/armhf has unsatisfiable dependency
    • libvibe-mongodb0/armhf has unsatisfiable dependency
    • libvibe-redis0/armhf has unsatisfiable dependency
    • libvibe-stream0/armhf has unsatisfiable dependency
    • libvibe-textfilter0/armhf has unsatisfiable dependency
    • libvibe-tls0/armhf has unsatisfiable dependency
    • libvibe-utils0/armhf has unsatisfiable dependency
    • libvibe-web0/armhf has unsatisfiable dependency
    • libvibe-core0/i386 has unsatisfiable dependency
    • libvibe-crypto0/i386 has unsatisfiable dependency
    • libvibe-data0/i386 has unsatisfiable dependency
    • libvibe-http0/i386 has unsatisfiable dependency
    • libvibe-inet0/i386 has unsatisfiable dependency
    • libvibe-mail0/i386 has unsatisfiable dependency
    • libvibe-mongodb0/i386 has unsatisfiable dependency
    • libvibe-redis0/i386 has unsatisfiable dependency
    • libvibe-stream0/i386 has unsatisfiable dependency
    • libvibe-textfilter0/i386 has unsatisfiable dependency
    • libvibe-tls0/i386 has unsatisfiable dependency
    • libvibe-utils0/i386 has unsatisfiable dependency
    • libvibe-web0/i386 has unsatisfiable dependency
    • Updating vibe.d would introduce bugs in testing: #941453
    • vibe.d unsatisfiable Build-Depends(-Arch) on amd64: libstdx-allocator-dev (>= 2.77.2)
    • vibe.d unsatisfiable Build-Depends(-Arch) on arm64: libstdx-allocator-dev (>= 2.77.2)
    • vibe.d unsatisfiable Build-Depends(-Arch) on armhf: libstdx-allocator-dev (>= 2.77.2)
    • vibe.d unsatisfiable Build-Depends(-Arch) on i386: libstdx-allocator-dev (>= 2.77.2)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vibe.d.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2072 days old (needed 5 days)
• openr2 (- to 1.3.3-2)
  • Migration status for openr2 (- to 1.3.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): openr2 dahdi-linux (not considered)
    • Depends: openr2 dahdi-tools (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openr2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2075 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• 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 ♻
    • 2077 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
    • 2080 days old (needed 2 days)
• resteasy (- to 3.6.2-2)
  • Migration status for resteasy (- to 3.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating resteasy would introduce bugs in testing: #1057677, #879469
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resteasy.html
    • 2082 days old (needed 5 days)
• mpqc3 (- to 0.0~git20170114-4.1)
  • Migration status for mpqc3 (- to 0.0~git20170114-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mpqc3/amd64 has unsatisfiable dependency
    • mpqc3/arm64 has unsatisfiable dependency
    • mpqc3/armel has unsatisfiable dependency
    • mpqc3/armhf has unsatisfiable dependency
    • mpqc3/i386 has unsatisfiable dependency
    • mpqc3/mips64el has unsatisfiable dependency
    • mpqc3/ppc64el has unsatisfiable dependency
    • Updating mpqc3 would introduce bugs in testing: #946452
    • Build-Depends(-Arch): mpqc3 psicode (not considered)
    • Build-Depends(-Arch): mpqc3 tiledarray (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mpqc3.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 2098 days old (needed 5 days)
• clamz (- to 0.5-2.1)
  • Migration status for clamz (- to 0.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating clamz would introduce bugs in testing: #1071838
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clamz.html
    • 2134 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
    • 2135 days old (needed 5 days)
• flightgear-phi (- to 2018.1.1+dfsg1-1.1)
  • Migration status for flightgear-phi (- to 2018.1.1+dfsg1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flightgear-phi would introduce bugs in testing: #979902
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flightgear-phi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2137 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:
    • Updating amp would introduce bugs in testing: #1067375
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amp.html
    • 2147 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
    • Reproducible on armhf - info ♻
    • 2147 days old (needed 5 days)
• gauche-gl (- to 0.6-4)
  • Migration status for gauche-gl (- to 0.6-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gauche-gl gauche (not considered)
    • Depends: gauche-gl gauche (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gauche-gl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2154 days old (needed 5 days)
• swfmill (- to 0.3.6-1)
  • Migration status for swfmill (- to 0.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating swfmill would introduce bugs in testing: #1019600
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swfmill.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2163 days old (needed 5 days)
• libmoe (- to 1.5.8-5)
  • Migration status for libmoe (- to 1.5.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libmoe would introduce bugs in testing: #1075187
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmoe.html
    • Reproducible on armhf - info ♻
    • 2172 days old (needed 5 days)
• darcs-monitor (- to 0.4.2-14)
  • Migration status for darcs-monitor (- to 0.4.2-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating darcs-monitor would introduce bugs in testing: #1057792
    • Depends: darcs-monitor darcs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/darcs-monitor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2174 days old (needed 5 days)
• newmat (- to 1.10.4-8)
  • Migration status for newmat (- to 1.10.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating newmat would introduce bugs in testing: #1052790
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/newmat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2183 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2191 days old (needed 5 days)
• yad (- to 0.40.0-1)
  • Migration status for yad (- to 0.40.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yad would introduce bugs in testing: #1075695, #1077429
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yad.html
    • Reproducible on armhf - info ♻
    • 2196 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
    • Reproducible on armhf - info ♻
    • 2200 days old (needed 5 days)
• smarty-validate (- to 3.0.3-4)
  • Migration status for smarty-validate (- to 3.0.3-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: smarty-validate smarty3 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smarty-validate.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2213 days old (needed 5 days)
• ruby-yaml-db (- to 0.7.0-1)
  • Migration status for ruby-yaml-db (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-yaml-db would introduce bugs in testing: #1019679
    • autopkgtest for ruby-yaml-db/0.7.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-yaml-db.html
    • 2220 days old (needed 5 days)
• xtrs (- to 4.9d-2)
  • Migration status for xtrs (- to 4.9d-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xtrs would introduce bugs in testing: #1066954
    • Impossible Depends: xtrs -> libreadline8/8.2-3+b1/armel
    • Impossible Depends: xtrs -> libreadline8/8.2-3+b1/armhf
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2221 days old (needed 5 days)
• lphdisk (- to 0.9.1.ds1-3)
  • Migration status for lphdisk (- to 0.9.1.ds1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lphdisk libx86 (not considered)
    • Depends: lphdisk libx86 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on i386 - info ♻
    • 2227 days old (needed 5 days)
• lief (- to 0.9.0-1)
  • Migration status for lief (- to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liblief0/armel has unsatisfiable dependency
    • liblief0/armhf has unsatisfiable dependency
    • Updating lief would introduce bugs in testing: #1037752
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lief.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 2235 days old (needed 5 days)
• sus (- to 7.20180621)
  • Migration status for sus (- to 7.20180621): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sus would introduce bugs in testing: #968415
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2276 days old (needed 5 days)
• soundmanager2 (- to 2.97a.20150601+dfsg2-2)
  • Migration status for soundmanager2 (- to 2.97a.20150601+dfsg2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating soundmanager2 would introduce bugs in testing: #1031482
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/soundmanager2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2279 days old (needed 5 days)
• xqilla (- to 2.3.4-1)
  • Migration status for xqilla (- to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libxqilla6v5/armel has unsatisfiable dependency
    • xqilla/armel has unsatisfiable dependency
    • libxqilla6v5/armhf has unsatisfiable dependency
    • xqilla/armhf has unsatisfiable dependency
    • Updating xqilla would introduce bugs in testing: #1040163, #984418
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xqilla.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 2281 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 ♻
    • 2291 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
    • 2321 days old (needed 5 days)
• liboggplay (- to 0.2.1~git20091227-5)
  • Migration status for liboggplay (- to 0.2.1~git20091227-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating liboggplay would introduce bugs in testing: #1075195
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/liboggplay.html
    • autopkgtest for liboggplay/0.2.1~git20091227-5: 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
    • 2334 days old (needed 2 days)
• ctioga2 (- to 0.14.1-2)
  • Migration status for ctioga2 (- to 0.14.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ctioga2 ruby-tioga (not considered)
    • Depends: ctioga2 ruby-tioga (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ctioga2.html
    • autopkgtest for ctioga2/0.14.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 2343 days old (needed 5 days)
• golang-github-coreos-go-tspi (- to 0.1.1-2)
  • Migration status for golang-github-coreos-go-tspi (- to 0.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-coreos-go-tspi would introduce bugs in testing: #1079965, #849665
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-coreos-go-tspi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2343 days old (needed 5 days)
• mldemos (- to 0.5.1+git.1.ee5d11f-4)
  • Migration status for mldemos (- to 0.5.1+git.1.ee5d11f-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mldemos would introduce bugs in testing: #915711, #922585
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mldemos.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 2344 days old (needed 5 days)
• debbugs (- to 2.6.0)
  • Migration status for debbugs (- to 2.6.0): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debbugs would introduce bugs in testing: #903413
    • autopkgtest for debbugs/2.6.0: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by don, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debbugs.html
    • 2363 days old (needed 5 days)
• dnsjava (- to 2.1.8-2)
  • Migration status for dnsjava (- to 2.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Updating dnsjava would introduce bugs in testing: #1077368, #1077750, #1077751
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnsjava.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2377 days old (needed 5 days)
    • Remove hint for (transitive) dependency: dnsjava
• 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)
    • 2423 days old (needed 5 days)
• pagetools (- to 0.1-3)
  • Migration status for pagetools (- to 0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pagetools/amd64 has unsatisfiable dependency
    • pagetools/arm64 has unsatisfiable dependency
    • pagetools/armel has unsatisfiable dependency
    • pagetools/armhf has unsatisfiable dependency
    • pagetools/i386 has unsatisfiable dependency
    • pagetools/mips64el has unsatisfiable dependency
    • pagetools/ppc64el has unsatisfiable dependency
    • pagetools/s390x has unsatisfiable dependency
    • Updating pagetools would introduce bugs in testing: #1012690
    • pagetools unsatisfiable Build-Depends(-Arch) on amd64: libnetpbm10-dev
    • pagetools unsatisfiable Build-Depends(-Arch) on arm64: libnetpbm10-dev
    • pagetools unsatisfiable Build-Depends(-Arch) on armel: libnetpbm10-dev
    • pagetools unsatisfiable Build-Depends(-Arch) on armhf: libnetpbm10-dev
    • pagetools unsatisfiable Build-Depends(-Arch) on i386: libnetpbm10-dev
    • pagetools unsatisfiable Build-Depends(-Arch) on mips64el: libnetpbm10-dev
    • pagetools unsatisfiable Build-Depends(-Arch) on ppc64el: libnetpbm10-dev
    • pagetools unsatisfiable Build-Depends(-Arch) on s390x: libnetpbm10-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pagetools.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2443 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
    • 2443 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
    • 2445 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debtags.html
    • 2445 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 ♻
    • 2465 days old (needed 5 days)
• sift (- to 4.0.3b-6)
  • Migration status for sift (- to 4.0.3b-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sift would introduce bugs in testing: #1066998
    • Build-Depends(-Arch): sift blimps (not considered)
    • Depends: sift blimps (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2475 days old (needed 5 days)
• sdcv (- to 0.5.2-2)
  • Migration status for sdcv (- to 0.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sdcv would introduce bugs in testing: #1078404
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdcv.html
    • 2492 days old (needed 5 days)
• octicons (- to 4.4.0-2)
  • Migration status for octicons (- to 4.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octicons would introduce bugs in testing: #883107
    • Not built on buildd: arch all binaries uploaded by henrich, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octicons.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2515 days old (needed 5 days)
• urweb (- to 20170720+dfsg-2)
  • Migration status for urweb (- to 20170720+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liburweb0/ppc64el has unsatisfiable dependency
    • Updating urweb would introduce bugs in testing: #1060107
    • Impossible Depends: urweb -> libssl3/3.1.5-1/armel
    • Impossible Depends: urweb -> libssl3/3.1.5-1/armhf
    • Build-Depends(-Arch): urweb mlton (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urweb.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 2553 days old (needed 5 days)
    • Remove hint for (transitive) dependency: llvm-toolchain-19
• opengrm-ngram (- to 1.3.2-3)
  • Migration status for opengrm-ngram (- to 1.3.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libngram-tools/amd64 has unsatisfiable dependency
    • libngram2/amd64 has unsatisfiable dependency
    • libngram-tools/arm64 has unsatisfiable dependency
    • libngram2/arm64 has unsatisfiable dependency
    • libngram-tools/armel has unsatisfiable dependency
    • libngram2/armel has unsatisfiable dependency
    • libngram-tools/armhf has unsatisfiable dependency
    • libngram2/armhf has unsatisfiable dependency
    • libngram-tools/i386 has unsatisfiable dependency
    • libngram2/i386 has unsatisfiable dependency
    • libngram-tools/mips64el has unsatisfiable dependency
    • libngram2/mips64el has unsatisfiable dependency
    • libngram-tools/ppc64el has unsatisfiable dependency
    • libngram2/ppc64el has unsatisfiable dependency
    • libngram-tools/s390x has unsatisfiable dependency
    • libngram2/s390x has unsatisfiable dependency
    • Updating opengrm-ngram would introduce bugs in testing: #1019172
    • Build-Depends(-Arch): opengrm-ngram openfst (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/opengrm-ngram.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2565 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 ♻
    • 2583 days old (needed 5 days)
• golang-github-minio-cli (- to 1.3.0+git20170313.0.8683fa7-1)
  • Migration status for golang-github-minio-cli (- to 1.3.0+git20170313.0.8683fa7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-minio-cli would introduce bugs in testing: #1079774, #869190
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-minio-cli.html
    • 2620 days old (needed 5 days)
• golang-gopkg-mcuadros-go-syslog.v2 (- to 2.2.1-1)
  • Migration status for golang-gopkg-mcuadros-go-syslog.v2 (- to 2.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-gopkg-mcuadros-go-syslog.v2 would introduce bugs in testing: #954514
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-gopkg-mcuadros-go-syslog.v2.html
    • 2625 days old (needed 5 days)
• yorick-mira (- to 1.1.0+git20170124.3bd1c3~dfsg1-2)
  • Migration status for yorick-mira (- to 1.1.0+git20170124.3bd1c3~dfsg1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: yorick-mira yorick-ynfft (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-mira.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2749 days old (needed 5 days)
• irssi-plugin-robustirc (- to 0.6-4)
  • Migration status for irssi-plugin-robustirc (- to 0.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating irssi-plugin-robustirc would introduce bugs in testing: #1015080
    • Impossible Depends: irssi-plugin-robustirc -> libglib2.0-0/2.78.4-1/armel
    • Impossible Depends: irssi-plugin-robustirc -> libglib2.0-0/2.78.4-1/armhf
    • Depends: irssi-plugin-robustirc curl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/irssi-plugin-robustirc.html
    • 2762 days old (needed 5 days)
• xjump (- to 2.7.5-6.2)
  • Migration status for xjump (- to 2.7.5-6.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xjump would introduce bugs in testing: #1075666
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xjump.html
    • Reproducible on armhf - info ♻
    • 2798 days old (needed 5 days)
• verilog-mode (- to 20161124.fd230e6-2)
  • Migration status for verilog-mode (- to 20161124.fd230e6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating verilog-mode would introduce bugs in testing: #934977
    • verilog-mode unsatisfiable Build-Depends(-Arch) on amd64: emacs25
    • Not built on buildd: arch all binaries uploaded by spwhitton@spwhitton.name, a new source-only upload is needed to allow migration
    • 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 ♻
    • 2810 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:
    • 2820 days old (needed 5 days)
• golang-github-tsenart-tb (- to 0.0~git20151208.0.19f4c3d-2)
  • Migration status for golang-github-tsenart-tb (- to 0.0~git20151208.0.19f4c3d-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-tsenart-tb would introduce bugs in testing: #964048
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-tsenart-tb.html
    • Reproducible on amd64 - info ♻
    • 2844 days old (needed 5 days)
• fairymax (- to 5.0b-1)
  • Migration status for fairymax (- to 5.0b-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fairymax would introduce bugs in testing: #1074943
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fairymax.html
    • Reproducible on armhf - info ♻
    • 2863 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
    • Reproducible on armhf - info ♻
    • 2863 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
    • 2901 days old (needed 5 days)
• kryo-serializers (- to 0.22-3)
  • Migration status for kryo-serializers (- to 0.22-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kryo-serializers would introduce bugs in testing: #1053047, #875594
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kryo-serializers.html
    • 2908 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
    • Reproducible on armhf - info ♻
    • 2915 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)
    • 2937 days old (needed 5 days)
• ecere-sdk (- to 0.44.15-1)
  • Migration status for ecere-sdk (- to 0.44.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libedasqlite0/amd64 has unsatisfiable dependency
    • libedasqlite0/arm64 has unsatisfiable dependency
    • libedasqlite0/armel has unsatisfiable dependency
    • libedasqlite0/armhf has unsatisfiable dependency
    • libecere0/i386 has unsatisfiable dependency
    • libedasqlite0/i386 has unsatisfiable dependency
    • libedasqlite0/mips64el has unsatisfiable dependency
    • libedasqlite0/ppc64el has unsatisfiable dependency
    • libedasqlite0/s390x has unsatisfiable dependency
    • Updating ecere-sdk would introduce bugs in testing: #898832, #995050
    • 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
    • Impossible Depends: ecere-sdk -> libasound2/1.2.10-3/armel
    • Impossible Depends: ecere-sdk -> libasound2/1.2.10-3/armhf
    • Impossible Depends: ecere-sdk -> libpng16-16/1.6.43-1/armel
    • Impossible Depends: ecere-sdk -> libpng16-16/1.6.43-1/armhf
  • 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 ♻
    • 2961 days old (needed 5 days)
• libretro-mupen64plus (- to 2.0+git20160207+dfsg2-1)
  • Migration status for libretro-mupen64plus (- to 2.0+git20160207+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libretro-mupen64plus would introduce bugs in testing: #935282, #976078
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libretro-mupen64plus.html
    • 3014 days old (needed 5 days)
• glosstex (- to 0.4.dfsg.1-4)
  • Migration status for glosstex (- to 0.4.dfsg.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glosstex would introduce bugs in testing: #1052914
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glosstex.html
    • 3018 days old (needed 5 days)
• elektra (- to 0.8.14-5.1)
  • Migration status for elektra (- to 0.8.14-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • elektra-tests/amd64 has unsatisfiable dependency
    • libelektra4-python/amd64 has unsatisfiable dependency
    • python3-elektra/amd64 has unsatisfiable dependency
    • elektra-tests/arm64 has unsatisfiable dependency
    • libelektra4-python/arm64 has unsatisfiable dependency
    • python3-elektra/arm64 has unsatisfiable dependency
    • elektra-tests/armel has unsatisfiable dependency
    • libelektra4-python/armel has unsatisfiable dependency
    • python3-elektra/armel has unsatisfiable dependency
    • elektra-tests/armhf has unsatisfiable dependency
    • libelektra4-python/armhf has unsatisfiable dependency
    • python3-elektra/armhf has unsatisfiable dependency
    • elektra-tests/i386 has unsatisfiable dependency
    • libelektra4-python/i386 has unsatisfiable dependency
    • python3-elektra/i386 has unsatisfiable dependency
    • elektra-tests/mips64el has unsatisfiable dependency
    • libelektra4-python/mips64el has unsatisfiable dependency
    • python3-elektra/mips64el has unsatisfiable dependency
    • elektra-tests/ppc64el has unsatisfiable dependency
    • libelektra4-python/ppc64el has unsatisfiable dependency
    • python3-elektra/ppc64el has unsatisfiable dependency
    • elektra-tests/s390x has unsatisfiable dependency
    • libelektra4-python/s390x has unsatisfiable dependency
    • python3-elektra/s390x has unsatisfiable dependency
    • Updating elektra would introduce bugs in testing: #1079779, #844145, #846200, #851592, #881676, #956949
    • elektra unsatisfiable Build-Depends(-Arch) on amd64: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on arm64: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on armel: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on armhf: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on i386: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on mips64el: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on ppc64el: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on s390x: swig3.0
    • Not built on buildd: arch amd64 binaries uploaded by aeb
    • Not built on buildd: arch all binaries uploaded by aeb, a new source-only upload is needed to allow migration
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
    • Impossible Depends: elektra -> libqt5core5a/5.15.10+dfsg-7/armel
    • Impossible Depends: elektra -> libqt5core5a/5.15.10+dfsg-7/armhf
    • Impossible Depends: elektra -> libqt5gui5/5.15.10+dfsg-7/armel
    • Impossible Depends: elektra -> libqt5gui5/5.15.10+dfsg-7/armhf
    • Impossible Depends: elektra -> libqt5widgets5/5.15.10+dfsg-7/armel
    • Impossible Depends: elektra -> libqt5widgets5/5.15.10+dfsg-7/armhf
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/elektra.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 3024 days old (needed 5 days)
• php-sabre-xml (- to 1.4.2-1)
  • Migration status for php-sabre-xml (- to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-xml would introduce bugs in testing: #882949
    • autopkgtest for php-sabre-xml/1.4.2-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-sabre-xml php-sabre-uri (not considered)
    • Depends: php-sabre-xml php-sabre-uri (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-xml.html
    • 3038 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
    • 3063 days old (needed 5 days)
• mp3wrap (- to 0.5-4)
  • Migration status for mp3wrap (- to 0.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mp3wrap would introduce bugs in testing: #1066643
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mp3wrap.html
    • 3071 days old (needed 5 days)
• ruby-uconv (- to 0.6.1-3)
  • Migration status for ruby-uconv (- to 0.6.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-uconv would introduce bugs in testing: #1075480
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-uconv.html
    • autopkgtest for ruby-uconv/0.6.1-3: 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
    • 3095 days old (needed 2 days)
• rep-gtk (- to 1:0.90.8.2-3)
  • Migration status for rep-gtk (- to 1:0.90.8.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rep-gtk would introduce bugs in testing: #1075443
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rep-gtk.html
    • Reproducible on armhf - info ♻
    • 3097 days old (needed 5 days)
• php-sabre-uri (- to 1.1.0-1)
  • Migration status for php-sabre-uri (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-uri would introduce bugs in testing: #882923
    • autopkgtest for php-sabre-uri/1.1.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-uri.html
    • 3101 days old (needed 5 days)
• php-sabre-http (- to 4.2.1-3)
  • Migration status for php-sabre-http (- to 4.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-http would introduce bugs in testing: #882935
    • autopkgtest for php-sabre-http/4.2.1-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): php-sabre-http php-sabre-event (not considered)
    • Build-Depends(-Arch): php-sabre-http php-sabre-uri (not considered)
    • Depends: php-sabre-http php-sabre-event (not considered)
    • Depends: php-sabre-http php-sabre-uri (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-http.html
    • 3107 days old (needed 5 days)
• php-sabre-event (- to 3.0.0~as2.0.2-2)
  • Migration status for php-sabre-event (- to 3.0.0~as2.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabre-event would introduce bugs in testing: #882915
    • autopkgtest for php-sabre-event/3.0.0~as2.0.2-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-event.html
    • 3115 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
    • Reproducible on armhf - info ♻
    • 3116 days old (needed 5 days)
• nield (- to 0.6.1-2)
  • Migration status for nield (- to 0.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nield would introduce bugs in testing: #1066535
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nield.html
    • 3121 days old (needed 5 days)
• libr3 (- to 1.3.4-1)
  • Migration status for libr3 (- to 1.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libr3 would introduce bugs in testing: #1000058
    • Build-Depends(-Arch): libr3 pcre3 (not considered)
    • Depends: libr3 pcre3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libr3.html
    • autopkgtest for libr3/1.3.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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
    • 3141 days old (needed 2 days)
• treil (- to 1.8-2.2)
  • Migration status for treil (- to 1.8-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating treil would introduce bugs in testing: #1075585
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/treil.html
    • Reproducible on armhf - info ♻
    • 3232 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
    • 3251 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
    • 3286 days old (needed 5 days)
• yap (- to 6.2.2-6)
  • Migration status for yap (- to 6.2.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • yap/i386 has unsatisfiable dependency
    • Updating yap would introduce bugs in testing: #877034, #965915
    • Impossible Depends: yap -> libreadline8/8.2-3+b1/armel
    • Impossible Depends: yap -> libreadline8/8.2-3+b1/armhf
    • autopkgtest for yap/6.2.2-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yap.html
    • uninstallable on arch i386, not running autopkgtest there
    • 3349 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)
    • 3368 days old (needed 5 days)
• vncterm (- to 0.9.10-2)
  • Migration status for vncterm (- to 0.9.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vncterm would introduce bugs in testing: #1079778, #898453
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vncterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3383 days old (needed 5 days)
• qmenu (- to 5.0.2-2)
  • Migration status for qmenu (- to 5.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qmenu would introduce bugs in testing: #997191
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qmenu.html
    • 3424 days old (needed 5 days)
• molds (- to 0.3.1-1)
  • Migration status for molds (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating molds would introduce bugs in testing: #1075979
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/molds.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 3610 days old (needed 5 days)
• libmonitoring-availability-perl (- to 0.46-1)
  • Migration status for libmonitoring-availability-perl (- to 0.46-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libmonitoring-availability-perl would introduce bugs in testing: #839432
    • Not built on buildd: arch all binaries uploaded by formorer, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmonitoring-availability-perl.html
    • 3611 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
    • Reproducible on armhf - info ♻
    • 3613 days old (needed 5 days)
• input-utils (- to 1.0-1.1)
  • Migration status for input-utils (- to 1.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating input-utils would introduce bugs in testing: #1069502
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/input-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 3658 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
    • 3670 days old (needed 5 days)
• pacman4console (- to 1.3-1)
  • Migration status for pacman4console (- to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pacman4console would introduce bugs in testing: #1066196
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pacman4console.html
    • 3684 days old (needed 5 days)
• crashme (- to 2.8.5-1)
  • Migration status for crashme (- to 2.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crashme would introduce bugs in testing: #1066596
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crashme.html
    • 3690 days old (needed 5 days)
• pgdbf (- to 0.6.2-1.1)
  • Migration status for pgdbf (- to 0.6.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pgdbf would introduce bugs in testing: #1066700
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pgdbf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3727 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
    • 3730 days old (needed 5 days)
• xzip (- to 1:1.8.2-4)
  • Migration status for xzip (- to 1:1.8.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xzip would introduce bugs in testing: #1066696
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xzip.html
    • 3737 days old (needed 5 days)
• netstat-nat (- to 1.4.10-3)
  • Migration status for netstat-nat (- to 1.4.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netstat-nat would introduce bugs in testing: #1066719
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netstat-nat.html
    • 3751 days old (needed 5 days)
• jikespg (- to 1.3-3)
  • Migration status for jikespg (- to 1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jikespg would introduce bugs in testing: #1075100
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jikespg.html
    • Reproducible on armhf - info ♻
    • 3757 days old (needed 5 days)
• scheme2c (- to 2012.10.14-1)
  • Migration status for scheme2c (- to 2012.10.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scheme2c would introduce bugs in testing: #778111
    • Not built on buildd: arch amd64 binaries uploaded by bap
    • Not built on buildd: arch all binaries uploaded by bap, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scheme2c.html
    • 3790 days old (needed 5 days)
• libpthread-workqueue (- to 0.9.1-1)
  • Migration status for libpthread-workqueue (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpthread-workqueue would introduce bugs in testing: #1079775, #835107
    • Not built on buildd: arch amd64 binaries uploaded by rbalint
    • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpthread-workqueue.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3842 days old (needed 5 days)
• ttf2ufm (- to 3.4.4~r2+gbp-1)
  • Migration status for ttf2ufm (- to 3.4.4~r2+gbp-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ttf2ufm would introduce bugs in testing: #1075588
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/ttf2ufm.html
    • Reproducible on armhf - info ♻
    • 3881 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 ♻
    • 3892 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)
    • 3980 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)
    • 4008 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)
    • 4041 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
    • Reproducible on armhf - info ♻
    • 4042 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
    • Reproducible on armhf - info ♻
    • 4108 days old (needed 5 days)
• xjobs (- to 20120412-1)
  • Migration status for xjobs (- to 20120412-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xjobs would introduce bugs in testing: #1066652
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xjobs.html
    • Reproducible on arm64 - info ♻
    • 4115 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
    • Reproducible on i386 - info ♻
    • 4144 days old (needed 5 days)
• mutextrace (- to 0.1.4-1)
  • Migration status for mutextrace (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mutextrace would introduce bugs in testing: #743062
    • Not built on buildd: arch amd64 binaries uploaded by sjr
    • Not built on buildd: arch ppc64el binaries uploaded by aurel32
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mutextrace.html
    • 4148 days old (needed 5 days)
• espctag (- to 0.4-1)
  • Migration status for espctag (- to 0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating espctag would introduce bugs in testing: #1066640
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/espctag.html
    • 4381 days old (needed 5 days)
• uniutils (- to 2.27-2)
  • Migration status for uniutils (- to 2.27-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating uniutils would introduce bugs in testing: #1066323
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uniutils.html
    • 4421 days old (needed 5 days)
• ruby-fast-xs (- to 0.8.0-3)
  • Migration status for ruby-fast-xs (- to 0.8.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-fast-xs would introduce bugs in testing: #1075459
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-fast-xs.html
    • Reproducible on armhf - info ♻
    • 4452 days old (needed 5 days)
• mumudvb (- to 1.7.1-1)
  • Migration status for mumudvb (- to 1.7.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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 ♻
    • 4458 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
    • Reproducible on armhf - info ♻
    • 4519 days old (needed 5 days)
• mppenc (- to 1.16-1.1)
  • Migration status for mppenc (- to 1.16-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mppenc would introduce bugs in testing: #965730, #999076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mppenc.html
    • 4531 days old (needed 5 days)
• nttcp (- to 1.47-13)
  • Migration status for nttcp (- to 1.47-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nttcp would introduce bugs in testing: #1002847
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4549 days old (needed 5 days)
• cdcd (- to 0.6.6-13.1)
  • Migration status for cdcd (- to 0.6.6-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cdcd would introduce bugs in testing: #1074870
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cdcd.html
    • Reproducible on armhf - info ♻
    • 4670 days old (needed 5 days)
• nullidentd (- to 1.0-5)
  • Migration status for nullidentd (- to 1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nullidentd would introduce bugs in testing: #1075325
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nullidentd.html
    • Reproducible on armhf - info ♻
    • 4795 days old (needed 5 days)
• rovclock (- to 0.6e-7)
  • Migration status for rovclock (- to 0.6e-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rovclock would introduce bugs in testing: #1069556
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rovclock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 4925 days old (needed 5 days)
• puf (- to 1.0.0-7)
  • Migration status for puf (- to 1.0.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating puf would introduce bugs in testing: #1075401
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puf.html
    • Reproducible on armhf - info ♻
    • 4942 days old (needed 5 days)