Generated: 2024.07.15 12:04:48 +0000

• -biobambam2 (2.0.185+ds-1 to -)
  • Migration status for -biobambam2 (2.0.185+ds-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
• -hts-nim-tools (0.2.1-1 to -)
  • Migration status for -hts-nim-tools (0.2.1-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -libmaus2 (2.0.813+ds-1 to -)
  • Migration status for -libmaus2 (2.0.813+ds-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
• -mosdepth (0.3.6+ds-1 to -)
  • Migration status for -mosdepth (0.3.6+ds-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
• -nim (1.6.14-3 to -)
  • Migration status for -nim (1.6.14-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
• -nim-d3 (0.1.3-2 to -)
  • Migration status for -nim-d3 (0.1.3-2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -nim-docopt (0.6.8-3 to -)
  • Migration status for -nim-docopt (0.6.8-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
• -nim-hts (0.3.19+ds-1 to -)
  • Migration status for -nim-hts (0.3.19+ds-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
• -nim-kexpr (0.0.2-3 to -)
  • Migration status for -nim-kexpr (0.0.2-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
• -nim-lapper (0.1.7-5 to -)
  • Migration status for -nim-lapper (0.1.7-5 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -nim-regex (0.17.0+ds-2 to -)
  • Migration status for -nim-regex (0.17.0+ds-2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -nim-unicodedb (0.9.0-2 to -)
  • Migration status for -nim-unicodedb (0.9.0-2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -nim-unicodeplus (0.5.1-2 to -)
  • Migration status for -nim-unicodeplus (0.5.1-2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -openstack-trove (1:21.0.1-2 to -)
  • Migration status for -openstack-trove (1:21.0.1-2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -rstcheck (6.1.2+~1.0.3-2 to -)
  • Migration status for -rstcheck (6.1.2+~1.0.3-2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• 1oom/riscv64 (1.8.1-1 to 1.8.1-1)
  • Migration status for 1oom/riscv64 (1.8.1-1 to 1.8.1-1): Will attempt migration (Any information below is purely informational)
• 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)
• 4ti2/riscv64 (1.6.10+ds-1.1 to 1.6.10+ds-1.1)
  • Migration status for 4ti2/riscv64 (1.6.10+ds-1.1 to 1.6.10+ds-1.1): Will attempt migration (Any information below is purely informational)
• 7kaa/riscv64 (2.15.6+ds-1 to 2.15.6+ds-1)
  • Migration status for 7kaa/riscv64 (2.15.6+ds-1 to 2.15.6+ds-1): Will attempt migration (Any information below is purely informational)
• a2ps/riscv64 (1:4.15.5-2 to 1:4.15.5-2)
  • Migration status for a2ps/riscv64 (1:4.15.5-2 to 1:4.15.5-2): Will attempt migration (Any information below is purely informational)
• a7xpg/riscv64 (0.11.dfsg1-11 to 0.11.dfsg1-11)
  • Migration status for a7xpg/riscv64 (0.11.dfsg1-11 to 0.11.dfsg1-11): Will attempt migration (Any information below is purely informational)
• aaphoto/riscv64 (0.45-1 to 0.45-1)
  • Migration status for aaphoto/riscv64 (0.45-1 to 0.45-1): Will attempt migration (Any information below is purely informational)
• abe/riscv64 (1.1+dfsg-5 to 1.1+dfsg-5)
  • Migration status for abe/riscv64 (1.1+dfsg-5 to 1.1+dfsg-5): 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)
• ableton-link/riscv64 (3.1.1+dfsg-1 to 3.1.1+dfsg-1)
  • Migration status for ableton-link/riscv64 (3.1.1+dfsg-1 to 3.1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• abseil/riscv64 (20230802.1-4 to 20230802.1-4)
  • Migration status for abseil/riscv64 (20230802.1-4 to 20230802.1-4): 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)
• abyss/riscv64 (2.3.7-3 to 2.3.7-3)
  • Migration status for abyss/riscv64 (2.3.7-3 to 2.3.7-3): Will attempt migration (Any information below is purely informational)
• accounts-qml-module/riscv64 (0.7+git20231028.05e79eb-1 to 0.7+git20231028.05e79eb-1)
  • Migration status for accounts-qml-module/riscv64 (0.7+git20231028.05e79eb-1 to 0.7+git20231028.05e79eb-1): Will attempt migration (Any information below is purely informational)
• acepack/riscv64 (1.4.2-1 to 1.4.2-1)
  • Migration status for acepack/riscv64 (1.4.2-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
• aces3/riscv64 (3.0.8-9 to 3.0.8-9)
  • Migration status for aces3/riscv64 (3.0.8-9 to 3.0.8-9): 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)
• acl2/riscv64 (8.5dfsg-5 to 8.5dfsg-5)
  • Migration status for acl2/riscv64 (8.5dfsg-5 to 8.5dfsg-5): 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)
• aconnectgui/riscv64 (0.9.0rc2-1-10.3 to 0.9.0rc2-1-10.3)
  • Migration status for aconnectgui/riscv64 (0.9.0rc2-1-10.3 to 0.9.0rc2-1-10.3): Will attempt migration (Any information below is purely informational)
• acpitool/riscv64 (0.5.1-7 to 0.5.1-7)
  • Migration status for acpitool/riscv64 (0.5.1-7 to 0.5.1-7): Will attempt migration (Any information below is purely informational)
• 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)
• actor-framework/riscv64 (0.17.6-3.1 to 0.17.6-3.1)
  • Migration status for actor-framework/riscv64 (0.17.6-3.1 to 0.17.6-3.1): Will attempt migration (Any information below is purely informational)
• adacgi/riscv64 (1.6-34 to 1.6-34)
  • Migration status for adacgi/riscv64 (1.6-34 to 1.6-34): Will attempt migration (Any information below is purely informational)
• adasockets/riscv64 (1.14-1 to 1.14-1)
  • Migration status for adasockets/riscv64 (1.14-1 to 1.14-1): Will attempt migration (Any information below is purely informational)
• addresses-for-gnustep/riscv64 (0.4.8-3 to 0.4.8-3)
  • Migration status for addresses-for-gnustep/riscv64 (0.4.8-3 to 0.4.8-3): Will attempt migration (Any information below is purely informational)
• 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)
• adolc/riscv64 (2.7.2-6.1 to 2.7.2-6.1)
  • Migration status for adolc/riscv64 (2.7.2-6.1 to 2.7.2-6.1): Will attempt migration (Any information below is purely informational)
• adonthell/riscv64 (0.3.8-3 to 0.3.8-3)
  • Migration status for adonthell/riscv64 (0.3.8-3 to 0.3.8-3): Will attempt migration (Any information below is purely informational)
• adplay/riscv64 (1.8.1-3 to 1.8.1-3)
  • Migration status for adplay/riscv64 (1.8.1-3 to 1.8.1-3): Will attempt migration (Any information below is purely informational)
• adplug/riscv64 (2.3.3+dfsg-2 to 2.3.3+dfsg-2)
  • Migration status for adplug/riscv64 (2.3.3+dfsg-2 to 2.3.3+dfsg-2): Will attempt migration (Any information below is purely informational)
• adun.app/amd64 (0.81-14 to 0.81-14)
  • Migration status for adun.app/amd64 (0.81-14 to 0.81-14): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: adun.app/amd64 steptalk (not considered)
    • Invalidated by dependency
• adun.app/arm64 (0.81-14 to 0.81-14)
  • Migration status for adun.app/arm64 (0.81-14 to 0.81-14): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: adun.app/arm64 steptalk (not considered)
    • Invalidated by dependency
• adun.app/armel (0.81-14 to 0.81-14)
  • Migration status for adun.app/armel (0.81-14 to 0.81-14): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: adun.app/armel steptalk (not considered)
    • Invalidated by dependency
• adun.app/armhf (0.81-14 to 0.81-14)
  • Migration status for adun.app/armhf (0.81-14 to 0.81-14): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: adun.app/armhf steptalk (not considered)
    • Invalidated by dependency
• adun.app/i386 (0.81-14 to 0.81-14)
  • Migration status for adun.app/i386 (0.81-14 to 0.81-14): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: adun.app/i386 steptalk (not considered)
    • Invalidated by dependency
• adun.app/mips64el (0.81-14 to 0.81-14)
  • Migration status for adun.app/mips64el (0.81-14 to 0.81-14): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: adun.app/mips64el steptalk (not considered)
    • Invalidated by dependency
• adun.app/ppc64el (0.81-14 to 0.81-14)
  • Migration status for adun.app/ppc64el (0.81-14 to 0.81-14): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: adun.app/ppc64el steptalk (not considered)
    • Invalidated by dependency
• 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)
• adun.app/s390x (0.81-14 to 0.81-14)
  • Migration status for adun.app/s390x (0.81-14 to 0.81-14): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: adun.app/s390x steptalk (not considered)
    • Invalidated by dependency
• advancecomp/riscv64 (2.5-1 to 2.5-1)
  • Migration status for advancecomp/riscv64 (2.5-1 to 2.5-1): Will attempt migration (Any information below is purely informational)
• advi/riscv64 (1.10.2-10 to 1.10.2-10)
  • Migration status for advi/riscv64 (1.10.2-10 to 1.10.2-10): 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)
• aeolus/riscv64 (0.10.4-1 to 0.10.4-1)
  • Migration status for aeolus/riscv64 (0.10.4-1 to 0.10.4-1): Will attempt migration (Any information below is purely informational)
• aesfix/riscv64 (1.0.1-8 to 1.0.1-8)
  • Migration status for aesfix/riscv64 (1.0.1-8 to 1.0.1-8): Will attempt migration (Any information below is purely informational)
• aevol/riscv64 (5.0+ds-3 to 5.0+ds-3)
  • Migration status for aevol/riscv64 (5.0+ds-3 to 5.0+ds-3): Will attempt migration (Any information below is purely informational)
• aewm++-goodies/riscv64 (1.0-10.1 to 1.0-10.1)
  • Migration status for aewm++-goodies/riscv64 (1.0-10.1 to 1.0-10.1): Will attempt migration (Any information below is purely informational)
• aewm++/riscv64 (1.1.2-5.3 to 1.1.2-5.3)
  • Migration status for aewm++/riscv64 (1.1.2-5.3 to 1.1.2-5.3): Will attempt migration (Any information below is purely informational)
• 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)
• agda/riscv64 (2.6.3-1 to 2.6.3-1)
  • Migration status for agda/riscv64 (2.6.3-1 to 2.6.3-1): Will attempt migration (Any information below is purely informational)
• 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)
• agg/riscv64 (1:2.6.1-r134+dfsg1-2.1 to 1:2.6.1-r134+dfsg1-2.1)
  • Migration status for agg/riscv64 (1:2.6.1-r134+dfsg1-2.1 to 1:2.6.1-r134+dfsg1-2.1): Will attempt migration (Any information below is purely informational)
• aggdraw/riscv64 (1.3.18-1 to 1.3.18-1)
  • Migration status for aggdraw/riscv64 (1.3.18-1 to 1.3.18-1): 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)
• ahven/riscv64 (2.8-9 to 2.8-9)
  • Migration status for ahven/riscv64 (2.8-9 to 2.8-9): Will attempt migration (Any information below is purely informational)
• aiksaurus/riscv64 (1.2.1+dev-0.12-7.2 to 1.2.1+dev-0.12-7.2)
  • Migration status for aiksaurus/riscv64 (1.2.1+dev-0.12-7.2 to 1.2.1+dev-0.12-7.2): Will attempt migration (Any information below is purely informational)
• airstrike/riscv64 (0.99+1.0pre6a-11 to 0.99+1.0pre6a-11)
  • Migration status for airstrike/riscv64 (0.99+1.0pre6a-11 to 0.99+1.0pre6a-11): Will attempt migration (Any information below is purely informational)
• akira/riscv64 (0.0.16-2 to 0.0.16-2)
  • Migration status for akira/riscv64 (0.0.16-2 to 0.0.16-2): 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)
• aldo/riscv64 (0.7.8-2 to 0.7.8-2)
  • Migration status for aldo/riscv64 (0.7.8-2 to 0.7.8-2): Will attempt migration (Any information below is purely informational)
• ale/riscv64 (0.9.0.3-6 to 0.9.0.3-6)
  • Migration status for ale/riscv64 (0.9.0.3-6 to 0.9.0.3-6): Will attempt migration (Any information below is purely informational)
• alfa/riscv64 (2.2-1 to 2.2-1)
  • Migration status for alfa/riscv64 (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
• alienblaster/riscv64 (1.1.0-11 to 1.1.0-11)
  • Migration status for alienblaster/riscv64 (1.1.0-11 to 1.1.0-11): Will attempt migration (Any information below is purely informational)
• aliki/riscv64 (0.3.0-6 to 0.3.0-6)
  • Migration status for aliki/riscv64 (0.3.0-6 to 0.3.0-6): Will attempt migration (Any information below is purely informational)
• alire/riscv64 (1.2.1-2 to 1.2.1-2)
  • Migration status for alire/riscv64 (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
• 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)
• allure/riscv64 (0.11.0.0-1 to 0.11.0.0-1)
  • Migration status for allure/riscv64 (0.11.0.0-1 to 0.11.0.0-1): Will attempt migration (Any information below is purely informational)
• almanah/riscv64 (0.12.3-2 to 0.12.3-2)
  • Migration status for almanah/riscv64 (0.12.3-2 to 0.12.3-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)
• alsaequal/riscv64 (0.6-8 to 0.6-8)
  • Migration status for alsaequal/riscv64 (0.6-8 to 0.6-8): Will attempt migration (Any information below is purely informational)
• alsamixergui/riscv64 (0.9.0rc2-1-10.2 to 0.9.0rc2-1-10.2)
  • Migration status for alsamixergui/riscv64 (0.9.0rc2-1-10.2 to 0.9.0rc2-1-10.2): Will attempt migration (Any information below is purely informational)
• alsaplayer/riscv64 (0.99.81-2 to 0.99.81-2)
  • Migration status for alsaplayer/riscv64 (0.99.81-2 to 0.99.81-2): Will attempt migration (Any information below is purely informational)
• altos/riscv64 (1.9.18-1 to 1.9.18-1)
  • Migration status for altos/riscv64 (1.9.18-1 to 1.9.18-1): Will attempt migration (Any information below is purely informational)
• altree/riscv64 (1.3.2-2 to 1.3.2-2)
  • Migration status for altree/riscv64 (1.3.2-2 to 1.3.2-2): Will attempt migration (Any information below is purely informational)
• alure/riscv64 (1.2-9 to 1.2-9)
  • Migration status for alure/riscv64 (1.2-9 to 1.2-9): Will attempt migration (Any information below is purely informational)
• amap-align/riscv64 (2.2+git20080214.600fc29+dfsg-2 to 2.2+git20080214.600fc29+dfsg-2)
  • Migration status for amap-align/riscv64 (2.2+git20080214.600fc29+dfsg-2 to 2.2+git20080214.600fc29+dfsg-2): Will attempt migration (Any information below is purely informational)
• amb-plugins/riscv64 (0.8.1-8 to 0.8.1-8)
  • Migration status for amb-plugins/riscv64 (0.8.1-8 to 0.8.1-8): Will attempt migration (Any information below is purely informational)
• ambdec/riscv64 (0.7.1-1 to 0.7.1-1)
  • Migration status for ambdec/riscv64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• amide/riscv64 (1.0.6-5 to 1.0.6-5)
  • Migration status for amide/riscv64 (1.0.6-5 to 1.0.6-5): Will attempt migration (Any information below is purely informational)
• 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)
• amoebax/riscv64 (0.2.1+dfsg-6 to 0.2.1+dfsg-6)
  • Migration status for amoebax/riscv64 (0.2.1+dfsg-6 to 0.2.1+dfsg-6): Will attempt migration (Any information below is purely informational)
• amphetamine/riscv64 (0.8.10-21 to 0.8.10-21)
  • Migration status for amphetamine/riscv64 (0.8.10-21 to 0.8.10-21): 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-emc/riscv64 (0.5.2-4 to 0.5.2-4)
  • Migration status for amule-emc/riscv64 (0.5.2-4 to 0.5.2-4): 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)
• an/riscv64 (1.2-7 to 1.2-7)
  • Migration status for an/riscv64 (1.2-7 to 1.2-7): 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)
• analog/riscv64 (2:6.0.17-3 to 2:6.0.17-3)
  • Migration status for analog/riscv64 (2:6.0.17-3 to 2:6.0.17-3): Will attempt migration (Any information below is purely informational)
• andi/riscv64 (0.14-3 to 0.14-3)
  • Migration status for andi/riscv64 (0.14-3 to 0.14-3): 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/riscv64 (10.0.0+r32+git20220314.09dfa26c4e59-7 to 10.0.0+r32+git20220314.09dfa26c4e59-7)
  • Migration status for android-platform-build-kati/riscv64 (10.0.0+r32+git20220314.09dfa26c4e59-7 to 10.0.0+r32+git20220314.09dfa26c4e59-7): Will attempt migration (Any information below is purely informational)
• anet/riscv64 (0.5.0-3 to 0.5.0-3)
  • Migration status for anet/riscv64 (0.5.0-3 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
• angband/riscv64 (1:4.2.5+dfsg1-1 to 1:4.2.5+dfsg1-1)
  • Migration status for angband/riscv64 (1:4.2.5+dfsg1-1 to 1:4.2.5+dfsg1-1): Will attempt migration (Any information below is purely informational)
• angelscript/riscv64 (2.35.1+ds-3.1 to 2.35.1+ds-3.1)
  • Migration status for angelscript/riscv64 (2.35.1+ds-3.1 to 2.35.1+ds-3.1): Will attempt migration (Any information below is purely informational)
• animals/riscv64 (201207131226-2.2 to 201207131226-2.2)
  • Migration status for animals/riscv64 (201207131226-2.2 to 201207131226-2.2): Will attempt migration (Any information below is purely informational)
• ann/riscv64 (1.1.2+doc-9 to 1.1.2+doc-9)
  • Migration status for ann/riscv64 (1.1.2+doc-9 to 1.1.2+doc-9): Will attempt migration (Any information below is purely informational)
• anomaly/riscv64 (1.1.0-3 to 1.1.0-3)
  • Migration status for anomaly/riscv64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• anope/riscv64 (2.0.15-1 to 2.0.15-1)
  • Migration status for anope/riscv64 (2.0.15-1 to 2.0.15-1): Will attempt migration (Any information below is purely informational)
• 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)
• antennavis/riscv64 (0.3.1-4 to 0.3.1-4)
  • Migration status for antennavis/riscv64 (0.3.1-4 to 0.3.1-4): 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)
• antlr4-cpp-runtime/riscv64 (4.9+dfsg-3 to 4.9+dfsg-3)
  • Migration status for antlr4-cpp-runtime/riscv64 (4.9+dfsg-3 to 4.9+dfsg-3): 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)
• anymeal/riscv64 (1.27-1 to 1.27-1)
  • Migration status for anymeal/riscv64 (1.27-1 to 1.27-1): Will attempt migration (Any information below is purely informational)
• anyremote/riscv64 (6.7.3-5 to 6.7.3-5)
  • Migration status for anyremote/riscv64 (6.7.3-5 to 6.7.3-5): 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)
• apache2_pu (2.4.61-1 to 2.4.61-1~deb12u1)
  • Migration status for apache2_pu (2.4.61-1 to 2.4.61-1~deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: apache2 is newer in the target suite (2.4.61-1 2.4.61-1~deb12u1)
• apachetop/riscv64 (0.23.2-2 to 0.23.2-2)
  • Migration status for apachetop/riscv64 (0.23.2-2 to 0.23.2-2): Will attempt migration (Any information below is purely informational)
• apcupsd/riscv64 (3.14.14-3.1 to 3.14.14-3.1)
  • Migration status for apcupsd/riscv64 (3.14.14-3.1 to 3.14.14-3.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)
• apng2gif/riscv64 (1.8-5 to 1.8-5)
  • Migration status for apng2gif/riscv64 (1.8-5 to 1.8-5): Will attempt migration (Any information below is purely informational)
• apngasm/riscv64 (2.91-5 to 2.91-5)
  • Migration status for apngasm/riscv64 (2.91-5 to 2.91-5): Will attempt migration (Any information below is purely informational)
• apngdis/riscv64 (2.9-6 to 2.9-6)
  • Migration status for apngdis/riscv64 (2.9-6 to 2.9-6): Will attempt migration (Any information below is purely informational)
• apngopt/riscv64 (1.4-3 to 1.4-3)
  • Migration status for apngopt/riscv64 (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
• apophenia/riscv64 (1.0+ds-8.1 to 1.0+ds-8.1)
  • Migration status for apophenia/riscv64 (1.0+ds-8.1 to 1.0+ds-8.1): 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)
• apriltag/riscv64 (3.3.0-3 to 3.3.0-3)
  • Migration status for apriltag/riscv64 (3.3.0-3 to 3.3.0-3): 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)
• aptitude/riscv64 (0.8.13-6 to 0.8.13-6)
  • Migration status for aptitude/riscv64 (0.8.13-6 to 0.8.13-6): Will attempt migration (Any information below is purely informational)
• 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)
• arachne-pnr/riscv64 (0.1+20190728gitc40fb22-3 to 0.1+20190728gitc40fb22-3)
  • Migration status for arachne-pnr/riscv64 (0.1+20190728gitc40fb22-3 to 0.1+20190728gitc40fb22-3): Will attempt migration (Any information below is purely informational)
• aranym/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for aranym/riscv64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• aravis/riscv64 (0.8.30-1 to 0.8.30-1)
  • Migration status for aravis/riscv64 (0.8.30-1 to 0.8.30-1): 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)
• archivemount/riscv64 (0.8.7-1 to 0.8.7-1)
  • Migration status for archivemount/riscv64 (0.8.7-1 to 0.8.7-1): Will attempt migration (Any information below is purely informational)
• argyll/riscv64 (3.1.0+repack-1 to 3.1.0+repack-1)
  • Migration status for argyll/riscv64 (3.1.0+repack-1 to 3.1.0+repack-1): Will attempt migration (Any information below is purely informational)
• 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)
• armadillo/riscv64 (1:12.8.2+dfsg-1 to 1:12.8.2+dfsg-1)
  • Migration status for armadillo/riscv64 (1:12.8.2+dfsg-1 to 1:12.8.2+dfsg-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)
• armnn/amd64 (23.08-4.1 to 23.08-4.1)
  • Migration status for armnn/amd64 (23.08-4.1 to 23.08-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: armnn/amd64 flatbuffers (not considered)
    • Invalidated by dependency
• armnn/arm64 (23.08-4.1 to 23.08-4.1)
  • Migration status for armnn/arm64 (23.08-4.1 to 23.08-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: armnn/arm64 flatbuffers (not considered)
    • Invalidated by dependency
• armnn/armhf (23.08-4.1 to 23.08-4.1)
  • Migration status for armnn/armhf (23.08-4.1 to 23.08-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: armnn/armhf flatbuffers (not considered)
    • Invalidated by dependency
• armnn/i386 (23.08-4.1 to 23.08-4.1)
  • Migration status for armnn/i386 (23.08-4.1 to 23.08-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: armnn/i386 flatbuffers (not considered)
    • Invalidated by dependency
• armnn/mips64el (23.08-4.1 to 23.08-4.1)
  • Migration status for armnn/mips64el (23.08-4.1 to 23.08-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: armnn/mips64el flatbuffers (not considered)
    • Invalidated by dependency
• armnn/ppc64el (23.08-4.1 to 23.08-4.1)
  • Migration status for armnn/ppc64el (23.08-4.1 to 23.08-4.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: armnn/ppc64el flatbuffers (not considered)
    • Invalidated by dependency
• arpack++/riscv64 (2.3-10 to 2.3-10)
  • Migration status for arpack++/riscv64 (2.3-10 to 2.3-10): Will attempt migration (Any information below is purely informational)
• arpack/riscv64 (3.9.1-1.1 to 3.9.1-1.1)
  • Migration status for arpack/riscv64 (3.9.1-1.1 to 3.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)
• art-nextgen-simulation-tools/riscv64 (20160605+dfsg-5 to 20160605+dfsg-5)
  • Migration status for art-nextgen-simulation-tools/riscv64 (20160605+dfsg-5 to 20160605+dfsg-5): 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)
• ascd/riscv64 (0.13.2-7.1 to 0.13.2-7.1)
  • Migration status for ascd/riscv64 (0.13.2-7.1 to 0.13.2-7.1): Will attempt migration (Any information below is purely informational)
• ascii-patrol/riscv64 (1.7+dfsg-1 to 1.7+dfsg-1)
  • Migration status for ascii-patrol/riscv64 (1.7+dfsg-1 to 1.7+dfsg-1): Will attempt migration (Any information below is purely informational)
• aseba/riscv64 (1.6.99+dfsg-9 to 1.6.99+dfsg-9)
  • Migration status for aseba/riscv64 (1.6.99+dfsg-9 to 1.6.99+dfsg-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)
• aspcud/riscv64 (1:1.9.6-2 to 1:1.9.6-2)
  • Migration status for aspcud/riscv64 (1:1.9.6-2 to 1:1.9.6-2): Will attempt migration (Any information below is purely informational)
• aspell/riscv64 (0.60.8.1-1 to 0.60.8.1-1)
  • Migration status for aspell/riscv64 (0.60.8.1-1 to 0.60.8.1-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)
• assembly-stats/riscv64 (1.0.1+ds-6 to 1.0.1+ds-6)
  • Migration status for assembly-stats/riscv64 (1.0.1+ds-6 to 1.0.1+ds-6): Will attempt migration (Any information below is purely informational)
• astlib/riscv64 (0.11.10-2 to 0.11.10-2)
  • Migration status for astlib/riscv64 (0.11.10-2 to 0.11.10-2): Will attempt migration (Any information below is purely informational)
• 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)
• astropy-healpix/riscv64 (1.0.0-2 to 1.0.0-2)
  • Migration status for astropy-healpix/riscv64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• astropy-regions/riscv64 (0.9-1 to 0.9-1)
  • Migration status for astropy-regions/riscv64 (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
• astroscrappy/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for astroscrappy/riscv64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• astyle/riscv64 (3.1-3 to 3.1-3)
  • Migration status for astyle/riscv64 (3.1-3 to 3.1-3): 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)
• asymptote/riscv64 (2.89+ds-1 to 2.89+ds-1)
  • Migration status for asymptote/riscv64 (2.89+ds-1 to 2.89+ds-1): 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)
• atanks/riscv64 (6.6~dfsg-1 to 6.6~dfsg-1)
  • Migration status for atanks/riscv64 (6.6~dfsg-1 to 6.6~dfsg-1): Will attempt migration (Any information below is purely informational)
• ataqv/riscv64 (1.3.1+ds-2 to 1.3.1+ds-2)
  • Migration status for ataqv/riscv64 (1.3.1+ds-2 to 1.3.1+ds-2): Will attempt migration (Any information below is purely informational)
• atf/riscv64 (0.21+git20240225+0c62cf9d569d-1 to 0.21+git20240225+0c62cf9d569d-1)
  • Migration status for atf/riscv64 (0.21+git20240225+0c62cf9d569d-1 to 0.21+git20240225+0c62cf9d569d-1): Will attempt migration (Any information below is purely informational)
• atkmm1.6/riscv64 (2.28.4-1 to 2.28.4-1)
  • Migration status for atkmm1.6/riscv64 (2.28.4-1 to 2.28.4-1): Will attempt migration (Any information below is purely informational)
• atom4/riscv64 (4.1-9 to 4.1-9)
  • Migration status for atom4/riscv64 (4.1-9 to 4.1-9): 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)
• atomicparsley/riscv64 (20210715.151551.e7ad03a-1 to 20210715.151551.e7ad03a-1)
  • Migration status for atomicparsley/riscv64 (20210715.151551.e7ad03a-1 to 20210715.151551.e7ad03a-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)
• atril/riscv64 (1.26.2-3 to 1.26.2-3)
  • Migration status for atril/riscv64 (1.26.2-3 to 1.26.2-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)
• aubio/riscv64 (0.4.9-4.4 to 0.4.9-4.4)
  • Migration status for aubio/riscv64 (0.4.9-4.4 to 0.4.9-4.4): 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)
• audacity/riscv64 (3.5.1+dfsg-1 to 3.5.1+dfsg-1)
  • Migration status for audacity/riscv64 (3.5.1+dfsg-1 to 3.5.1+dfsg-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)
• audiofile/riscv64 (0.3.6-6 to 0.3.6-6)
  • Migration status for audiofile/riscv64 (0.3.6-6 to 0.3.6-6): 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)
• augustus/riscv64 (3.5.0+dfsg-4 to 3.5.0+dfsg-4)
  • Migration status for augustus/riscv64 (3.5.0+dfsg-4 to 3.5.0+dfsg-4): 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)
• autodock-vina/riscv64 (1.2.5-2 to 1.2.5-2)
  • Migration status for autodock-vina/riscv64 (1.2.5-2 to 1.2.5-2): Will attempt migration (Any information below is purely informational)
• autodocksuite/riscv64 (4.2.6-9 to 4.2.6-9)
  • Migration status for autodocksuite/riscv64 (4.2.6-9 to 4.2.6-9): Will attempt migration (Any information below is purely informational)
• autofdo/riscv64 (0.19-3 to 0.19-3)
  • Migration status for autofdo/riscv64 (0.19-3 to 0.19-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)
• avarice/riscv64 (2.14+svn427-1 to 2.14+svn427-1)
  • Migration status for avarice/riscv64 (2.14+svn427-1 to 2.14+svn427-1): Will attempt migration (Any information below is purely informational)
• avifile/riscv64 (1:0.7.48~20090503.ds-26 to 1:0.7.48~20090503.ds-26)
  • Migration status for avifile/riscv64 (1:0.7.48~20090503.ds-26 to 1:0.7.48~20090503.ds-26): Will attempt migration (Any information below is purely informational)
• avldrums.lv2/riscv64 (0.7.2-1 to 0.7.2-1)
  • Migration status for avldrums.lv2/riscv64 (0.7.2-1 to 0.7.2-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)
• avro-c/riscv64 (1.11.1-1 to 1.11.1-1)
  • Migration status for avro-c/riscv64 (1.11.1-1 to 1.11.1-1): 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)
• awffull/riscv64 (3.10.2-9 to 3.10.2-9)
  • Migration status for awffull/riscv64 (3.10.2-9 to 3.10.2-9): Will attempt migration (Any information below is purely informational)
• ax25mail-utils/riscv64 (0.15-1 to 0.15-1)
  • Migration status for ax25mail-utils/riscv64 (0.15-1 to 0.15-1): Will attempt migration (Any information below is purely informational)
• 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)
• babeld/riscv64 (1.12.1-1 to 1.12.1-1)
  • Migration status for babeld/riscv64 (1.12.1-1 to 1.12.1-1): Will attempt migration (Any information below is purely informational)
• baconqrcode/riscv64 (2.0.8-3 to 2.0.8-3)
  • Migration status for baconqrcode/riscv64 (2.0.8-3 to 2.0.8-3): Will attempt migration (Any information below is purely informational)
• bagel/riscv64 (1.2.2-7 to 1.2.2-7)
  • Migration status for bagel/riscv64 (1.2.2-7 to 1.2.2-7): Will attempt migration (Any information below is purely informational)
• baitfisher/riscv64 (1.2.7+git20211020.de26d5c+dfsg-1 to 1.2.7+git20211020.de26d5c+dfsg-1)
  • Migration status for baitfisher/riscv64 (1.2.7+git20211020.de26d5c+dfsg-1 to 1.2.7+git20211020.de26d5c+dfsg-1): Will attempt migration (Any information below is purely informational)
• balboa/riscv64 (2.0.0+ds-6 to 2.0.0+ds-6)
  • Migration status for balboa/riscv64 (2.0.0+ds-6 to 2.0.0+ds-6): Will attempt migration (Any information below is purely informational)
• bali-phy/riscv64 (3.6.1+dfsg-2 to 3.6.1+dfsg-2)
  • Migration status for bali-phy/riscv64 (3.6.1+dfsg-2 to 3.6.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• 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-kf5/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for baloo-kf5/riscv64 (5.115.0-2 to 5.115.0-2): 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)
• balsa/riscv64 (2.6.4-2 to 2.6.4-2)
  • Migration status for balsa/riscv64 (2.6.4-2 to 2.6.4-2): 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)
• 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)
• barada-pam/riscv64 (0.5-3.3 to 0.5-3.3)
  • Migration status for barada-pam/riscv64 (0.5-3.3 to 0.5-3.3): 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)
• barrage/riscv64 (1.0.5-1 to 1.0.5-1)
  • Migration status for barrage/riscv64 (1.0.5-1 to 1.0.5-1): 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)
• bart/riscv64 (0.9.00-2 to 0.9.00-2)
  • Migration status for bart/riscv64 (0.9.00-2 to 0.9.00-2): Will attempt migration (Any information below is purely informational)
• basemap/riscv64 (1.2.2+dfsg-5 to 1.2.2+dfsg-5)
  • Migration status for basemap/riscv64 (1.2.2+dfsg-5 to 1.2.2+dfsg-5): 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)
• bastet/riscv64 (0.43-7 to 0.43-7)
  • Migration status for bastet/riscv64 (0.43-7 to 0.43-7): 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)
• bb/riscv64 (1.3rc1-13 to 1.3rc1-13)
  • Migration status for bb/riscv64 (1.3rc1-13 to 1.3rc1-13): Will attempt migration (Any information below is purely informational)
• bbmail/riscv64 (0.9.3-5 to 0.9.3-5)
  • Migration status for bbmail/riscv64 (0.9.3-5 to 0.9.3-5): Will attempt migration (Any information below is purely informational)
• bbpager/riscv64 (0.4.7-10 to 0.4.7-10)
  • Migration status for bbpager/riscv64 (0.4.7-10 to 0.4.7-10): Will attempt migration (Any information below is purely informational)
• bcalm/riscv64 (2.2.3-5 to 2.2.3-5)
  • Migration status for bcalm/riscv64 (2.2.3-5 to 2.2.3-5): Will attempt migration (Any information below is purely informational)
• bcmatroska2/riscv64 (5.2.0-2 to 5.2.0-2)
  • Migration status for bcmatroska2/riscv64 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bcpp/riscv64 (0.0.20210108-1 to 0.0.20210108-1)
  • Migration status for bcpp/riscv64 (0.0.20210108-1 to 0.0.20210108-1): Will attempt migration (Any information below is purely informational)
• bctoolbox/riscv64 (5.2.0-2.1 to 5.2.0-2.1)
  • Migration status for bctoolbox/riscv64 (5.2.0-2.1 to 5.2.0-2.1): 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)
• beancount/riscv64 (2.3.6-1 to 2.3.6-1)
  • Migration status for beancount/riscv64 (2.3.6-1 to 2.3.6-1): Will attempt migration (Any information below is purely informational)
• bedops/riscv64 (2.4.41+dfsg-2 to 2.4.41+dfsg-2)
  • Migration status for bedops/riscv64 (2.4.41+dfsg-2 to 2.4.41+dfsg-2): Will attempt migration (Any information below is purely informational)
• bedtools/riscv64 (2.31.1+dfsg-2 to 2.31.1+dfsg-2)
  • Migration status for bedtools/riscv64 (2.31.1+dfsg-2 to 2.31.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• belcard/riscv64 (5.2.0-2 to 5.2.0-2)
  • Migration status for belcard/riscv64 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• belle-sip/riscv64 (5.2.0+dfsg-3.1 to 5.2.0+dfsg-3.1)
  • Migration status for belle-sip/riscv64 (5.2.0+dfsg-3.1 to 5.2.0+dfsg-3.1): Will attempt migration (Any information below is purely informational)
• belr/riscv64 (5.2.0-2 to 5.2.0-2)
  • Migration status for belr/riscv64 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• bemenu/riscv64 (0.6.15+dfsg-1 to 0.6.15+dfsg-1)
  • Migration status for bemenu/riscv64 (0.6.15+dfsg-1 to 0.6.15+dfsg-1): Will attempt migration (Any information below is purely informational)
• benchmark/riscv64 (1.8.3-3 to 1.8.3-3)
  • Migration status for benchmark/riscv64 (1.8.3-3 to 1.8.3-3): Will attempt migration (Any information below is purely informational)
• berkeley-express/riscv64 (1.5.3+dfsg-3 to 1.5.3+dfsg-3)
  • Migration status for berkeley-express/riscv64 (1.5.3+dfsg-3 to 1.5.3+dfsg-3): Will attempt migration (Any information below is purely informational)
• 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)
• 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)
• bgw-replstatus/riscv64 (1.0.7-2 to 1.0.7-2)
  • Migration status for bgw-replstatus/riscv64 (1.0.7-2 to 1.0.7-2): Will attempt migration (Any information below is purely informational)
• biblesync/riscv64 (2.1.0-2 to 2.1.0-2)
  • Migration status for biblesync/riscv64 (2.1.0-2 to 2.1.0-2): 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)
• biboumi/riscv64 (9.0-5 to 9.0-5)
  • Migration status for biboumi/riscv64 (9.0-5 to 9.0-5): Will attempt migration (Any information below is purely informational)
• bibtex2html/riscv64 (1.99-4 to 1.99-4)
  • Migration status for bibtex2html/riscv64 (1.99-4 to 1.99-4): Will attempt migration (Any information below is purely informational)
• bibtexconv/riscv64 (1.3.6-1 to 1.3.6-1)
  • Migration status for bibtexconv/riscv64 (1.3.6-1 to 1.3.6-1): Will attempt migration (Any information below is purely informational)
• bifcl/riscv64 (1.6.2-1 to 1.6.2-1)
  • Migration status for bifcl/riscv64 (1.6.2-1 to 1.6.2-1): Will attempt migration (Any information below is purely informational)
• bifrost/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for bifrost/riscv64 (1.3.1-1 to 1.3.1-1): 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)
• biloba/riscv64 (0.9.3-11 to 0.9.3-11)
  • Migration status for biloba/riscv64 (0.9.3-11 to 0.9.3-11): Will attempt migration (Any information below is purely informational)
• bin-prot/riscv64 (1:0.16.0-1 to 1:0.16.0-1)
  • Migration status for bin-prot/riscv64 (1:0.16.0-1 to 1:0.16.0-1): Will attempt migration (Any information below is purely informational)
• binaryen/riscv64 (108-1 to 108-1)
  • Migration status for binaryen/riscv64 (108-1 to 108-1): Will attempt migration (Any information below is purely informational)
• binfmtc/riscv64 (0.17-2.3 to 0.17-2.3)
  • Migration status for binfmtc/riscv64 (0.17-2.3 to 0.17-2.3): Will attempt migration (Any information below is purely informational)
• biniax2/riscv64 (1.30-7 to 1.30-7)
  • Migration status for biniax2/riscv64 (1.30-7 to 1.30-7): 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)
• binpac/riscv64 (0.59.0-1 to 0.59.0-1)
  • Migration status for binpac/riscv64 (0.59.0-1 to 0.59.0-1): Will attempt migration (Any information below is purely informational)
• biosig/riscv64 (2.6.0-1 to 2.6.0-1)
  • Migration status for biosig/riscv64 (2.6.0-1 to 2.6.0-1): Will attempt migration (Any information below is purely informational)
• 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)
• bisect-ppx/riscv64 (2.8.3+dfsg-1 to 2.8.3+dfsg-1)
  • Migration status for bisect-ppx/riscv64 (2.8.3+dfsg-1 to 2.8.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• bitlbee-facebook/riscv64 (1.2.2-3 to 1.2.2-3)
  • Migration status for bitlbee-facebook/riscv64 (1.2.2-3 to 1.2.2-3): Will attempt migration (Any information below is purely informational)
• bitlbee-mastodon/riscv64 (1.4.5-1 to 1.4.5-1)
  • Migration status for bitlbee-mastodon/riscv64 (1.4.5-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
• bitlbee/riscv64 (3.6-1.4 to 3.6-1.4)
  • Migration status for bitlbee/riscv64 (3.6-1.4 to 3.6-1.4): Will attempt migration (Any information below is purely informational)
• bitseq/riscv64 (0.7.5+dfsg-6 to 0.7.5+dfsg-6)
  • Migration status for bitseq/riscv64 (0.7.5+dfsg-6 to 0.7.5+dfsg-6): Will attempt migration (Any information below is purely informational)
• bitshuffle/riscv64 (0.5.1-1.2 to 0.5.1-1.2)
  • Migration status for bitshuffle/riscv64 (0.5.1-1.2 to 0.5.1-1.2): Will attempt migration (Any information below is purely informational)
• black-box/riscv64 (1.4.8-4 to 1.4.8-4)
  • Migration status for black-box/riscv64 (1.4.8-4 to 1.4.8-4): Will attempt migration (Any information below is purely informational)
• blackbox/riscv64 (0.70.1-39 to 0.70.1-39)
  • Migration status for blackbox/riscv64 (0.70.1-39 to 0.70.1-39): Will attempt migration (Any information below is purely informational)
• blahtexml/riscv64 (0.9-1.1 to 0.9-1.1)
  • Migration status for blahtexml/riscv64 (0.9-1.1 to 0.9-1.1): Will attempt migration (Any information below is purely informational)
• blepvco/riscv64 (0.1.0-4 to 0.1.0-4)
  • Migration status for blepvco/riscv64 (0.1.0-4 to 0.1.0-4): 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)
• bliss/riscv64 (0.77-3 to 0.77-3)
  • Migration status for bliss/riscv64 (0.77-3 to 0.77-3): Will attempt migration (Any information below is purely informational)
• blitz++/riscv64 (1:1.0.2+ds-4.1 to 1:1.0.2+ds-4.1)
  • Migration status for blitz++/riscv64 (1:1.0.2+ds-4.1 to 1:1.0.2+ds-4.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)
• blockattack/riscv64 (2.8.0-1 to 2.8.0-1)
  • Migration status for blockattack/riscv64 (2.8.0-1 to 2.8.0-1): 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)
• blueman/riscv64 (2.4.1-1 to 2.4.1-1)
  • Migration status for blueman/riscv64 (2.4.1-1 to 2.4.1-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)
• blupimania/riscv64 (1.6.3-1 to 1.6.3-1)
  • Migration status for blupimania/riscv64 (1.6.3-1 to 1.6.3-1): 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)
• blurhash-python/riscv64 (1.1.4-3 to 1.1.4-3)
  • Migration status for blurhash-python/riscv64 (1.1.4-3 to 1.1.4-3): Will attempt migration (Any information below is purely informational)
• bmusb/riscv64 (0.7.8-1 to 0.7.8-1)
  • Migration status for bmusb/riscv64 (0.7.8-1 to 0.7.8-1): 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)
• bogl/riscv64 (0.1.18-22 to 0.1.18-22)
  • Migration status for bogl/riscv64 (0.1.18-22 to 0.1.18-22): Will attempt migration (Any information below is purely informational)
• boinctui/riscv64 (2.7.1-1 to 2.7.1-1)
  • Migration status for boinctui/riscv64 (2.7.1-1 to 2.7.1-1): Will attempt migration (Any information below is purely informational)
• 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)
• bomberclone/riscv64 (0.11.9-7.1 to 0.11.9-7.1)
  • Migration status for bomberclone/riscv64 (0.11.9-7.1 to 0.11.9-7.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)
• boolstuff/riscv64 (0.1.16-2 to 0.1.16-2)
  • Migration status for boolstuff/riscv64 (0.1.16-2 to 0.1.16-2): 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)
• boost-defaults/riscv64 (1.83.0.2 to 1.83.0.2)
  • Migration status for boost-defaults/riscv64 (1.83.0.2 to 1.83.0.2): Will attempt migration (Any information below is purely informational)
• boost1.83/amd64 (1.83.0-3 to 1.83.0-3)
  • Migration status for boost1.83/amd64 (1.83.0-3 to 1.83.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libboost-python1.83.0/1.83.0-3+b2/amd64 to testing makes coot/1.1.09+dfsg-1/amd64 uninstallable
    • migrating libboost-python1.83.0/1.83.0-3+b2/amd64 to testing makes python3-pycuda/2024.1~dfsg-1/amd64 uninstallable
• boost1.83/arm64 (1.83.0-3 to 1.83.0-3)
  • Migration status for boost1.83/arm64 (1.83.0-3 to 1.83.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libboost-python1.83.0/1.83.0-3+b2/arm64 to testing makes coot/1.1.09+dfsg-1/arm64 uninstallable
    • migrating libboost-python1.83.0/1.83.0-3+b2/arm64 to testing makes python3-pycuda/2024.1~dfsg-1/arm64 uninstallable
• boost1.83/armhf (1.83.0-3 to 1.83.0-3)
  • Migration status for boost1.83/armhf (1.83.0-3 to 1.83.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libboost-python1.83.0/1.83.0-3+b2/armhf to testing makes coot/1.1.09+dfsg-1/armhf uninstallable
• boost1.83/ppc64el (1.83.0-3 to 1.83.0-3)
  • Migration status for boost1.83/ppc64el (1.83.0-3 to 1.83.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libboost-python1.83.0/1.83.0-3+b2/ppc64el to testing makes coot/1.1.09+dfsg-1/ppc64el uninstallable
    • migrating libboost-python1.83.0/1.83.0-3+b2/ppc64el to testing makes python3-pycuda/2024.1~dfsg-1/ppc64el uninstallable
• borgbackup2/riscv64 (2.0.0b8-2 to 2.0.0b8-2)
  • Migration status for borgbackup2/riscv64 (2.0.0b8-2 to 2.0.0b8-2): 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)
• botch/amd64 (0.24-4 to 0.24-4)
  • Migration status for botch/amd64 (0.24-4 to 0.24-4): Will attempt migration (Any information below is purely informational)
• botch/arm64 (0.24-4 to 0.24-4)
  • Migration status for botch/arm64 (0.24-4 to 0.24-4): Will attempt migration (Any information below is purely informational)
• botch/armhf (0.24-4 to 0.24-4)
  • Migration status for botch/armhf (0.24-4 to 0.24-4): Will attempt migration (Any information below is purely informational)
• botch/i386 (0.24-4 to 0.24-4)
  • Migration status for botch/i386 (0.24-4 to 0.24-4): Will attempt migration (Any information below is purely informational)
• botch/ppc64el (0.24-4 to 0.24-4)
  • Migration status for botch/ppc64el (0.24-4 to 0.24-4): Will attempt migration (Any information below is purely informational)
• botch/s390x (0.24-4 to 0.24-4)
  • Migration status for botch/s390x (0.24-4 to 0.24-4): 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)
• bowtie/riscv64 (1.3.1-3 to 1.3.1-3)
  • Migration status for bowtie/riscv64 (1.3.1-3 to 1.3.1-3): Will attempt migration (Any information below is purely informational)
• bowtie2/riscv64 (2.5.3-1 to 2.5.3-1)
  • Migration status for bowtie2/riscv64 (2.5.3-1 to 2.5.3-1): Will attempt migration (Any information below is purely informational)
• box2d/riscv64 (2.4.1-3 to 2.4.1-3)
  • Migration status for box2d/riscv64 (2.4.1-3 to 2.4.1-3): Will attempt migration (Any information below is purely informational)
• bpm-tools/riscv64 (0.3-4 to 0.3-4)
  • Migration status for bpm-tools/riscv64 (0.3-4 to 0.3-4): 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)
• bppsuite/riscv64 (2.4.1-7 to 2.4.1-7)
  • Migration status for bppsuite/riscv64 (2.4.1-7 to 2.4.1-7): 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)
• breezy/riscv64 (3.3.6-1 to 3.3.6-1)
  • Migration status for breezy/riscv64 (3.3.6-1 to 3.3.6-1): 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)
• brian/riscv64 (2.5.4-4 to 2.5.4-4)
  • Migration status for brian/riscv64 (2.5.4-4 to 2.5.4-4): 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)
• brlaser/riscv64 (6-3 to 6-3)
  • Migration status for brlaser/riscv64 (6-3 to 6-3): Will attempt migration (Any information below is purely informational)
• 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)
• brutefir/riscv64 (1.0o-2 to 1.0o-2)
  • Migration status for brutefir/riscv64 (1.0o-2 to 1.0o-2): Will attempt migration (Any information below is purely informational)
• bs2b-ladspa/riscv64 (0.9.1-3 to 0.9.1-3)
  • Migration status for bs2b-ladspa/riscv64 (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• bsdgames/riscv64 (2.17-34 to 2.17-34)
  • Migration status for bsdgames/riscv64 (2.17-34 to 2.17-34): Will attempt migration (Any information below is purely informational)
• bsdmainutils/riscv64 (12.1.8 to 12.1.8)
  • Migration status for bsdmainutils/riscv64 (12.1.8 to 12.1.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)
• btag/riscv64 (1.4.1-0.1 to 1.4.1-0.1)
  • Migration status for btag/riscv64 (1.4.1-0.1 to 1.4.1-0.1): 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)
• bterm-unifont/riscv64 (1.7 to 1.7)
  • Migration status for bterm-unifont/riscv64 (1.7 to 1.7): Will attempt migration (Any information below is purely informational)
• btfs/riscv64 (2.24-1 to 2.24-1)
  • Migration status for btfs/riscv64 (2.24-1 to 2.24-1): 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)
• btllib/riscv64 (1.4.10+dfsg-1 to 1.4.10+dfsg-1)
  • Migration status for btllib/riscv64 (1.4.10+dfsg-1 to 1.4.10+dfsg-1): Will attempt migration (Any information below is purely informational)
• btop/riscv64 (1.3.0-1 to 1.3.0-1)
  • Migration status for btop/riscv64 (1.3.0-1 to 1.3.0-1): 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)
• bucklespring/riscv64 (1.4.0-2 to 1.4.0-2)
  • Migration status for bucklespring/riscv64 (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• buddy/riscv64 (2.4+dfsg-2 to 2.4+dfsg-2)
  • Migration status for buddy/riscv64 (2.4+dfsg-2 to 2.4+dfsg-2): 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)
• budgie-desktop/riscv64 (10.8.2-3 to 10.8.2-3)
  • Migration status for budgie-desktop/riscv64 (10.8.2-3 to 10.8.2-3): Will attempt migration (Any information below is purely informational)
• budgie-extras/riscv64 (1.8.0-1 to 1.8.0-1)
  • Migration status for budgie-extras/riscv64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• bugsquish/riscv64 (0.0.6-10 to 0.0.6-10)
  • Migration status for bugsquish/riscv64 (0.0.6-10 to 0.0.6-10): Will attempt migration (Any information below is purely informational)
• buici-clock/riscv64 (0.4.9.4+nmu2 to 0.4.9.4+nmu2)
  • Migration status for buici-clock/riscv64 (0.4.9.4+nmu2 to 0.4.9.4+nmu2): Will attempt migration (Any information below is purely informational)
• build-essential/riscv64 (12.10 to 12.10)
  • Migration status for build-essential/riscv64 (12.10 to 12.10): Will attempt migration (Any information below is purely informational)
• bullet/riscv64 (3.24+dfsg-2.1 to 3.24+dfsg-2.1)
  • Migration status for bullet/riscv64 (3.24+dfsg-2.1 to 3.24+dfsg-2.1): Will attempt migration (Any information below is purely informational)
• bulletml/riscv64 (0.0.6-8 to 0.0.6-8)
  • Migration status for bulletml/riscv64 (0.0.6-8 to 0.0.6-8): 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)
• bumprace/riscv64 (1.5.8-1 to 1.5.8-1)
  • Migration status for bumprace/riscv64 (1.5.8-1 to 1.5.8-1): Will attempt migration (Any information below is purely informational)
• bup/riscv64 (0.33.3-1 to 0.33.3-1)
  • Migration status for bup/riscv64 (0.33.3-1 to 0.33.3-1): Will attempt migration (Any information below is purely informational)
• burgerspace/riscv64 (1.9.5-1 to 1.9.5-1)
  • Migration status for burgerspace/riscv64 (1.9.5-1 to 1.9.5-1): Will attempt migration (Any information below is purely informational)
• burp/riscv64 (3.1.4-3.1 to 3.1.4-3.1)
  • Migration status for burp/riscv64 (3.1.4-3.1 to 3.1.4-3.1): Will attempt migration (Any information below is purely informational)
• 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)
• bustools/riscv64 (0.43.2+dfsg-1 to 0.43.2+dfsg-1)
  • Migration status for bustools/riscv64 (0.43.2+dfsg-1 to 0.43.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• butt/riscv64 (0.1.37-2 to 0.1.37-2)
  • Migration status for butt/riscv64 (0.1.37-2 to 0.1.37-2): Will attempt migration (Any information below is purely informational)
• butteraugli/riscv64 (0~20170116-3 to 0~20170116-3)
  • Migration status for butteraugli/riscv64 (0~20170116-3 to 0~20170116-3): 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-blosc/riscv64 (1.21.5+ds-1 to 1.21.5+ds-1)
  • Migration status for c-blosc/riscv64 (1.21.5+ds-1 to 1.21.5+ds-1): 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)
• c2050/riscv64 (0.3b-10 to 0.3b-10)
  • Migration status for c2050/riscv64 (0.3b-10 to 0.3b-10): Will attempt migration (Any information below is purely informational)
• c2esp/riscv64 (27-11 to 27-11)
  • Migration status for c2esp/riscv64 (27-11 to 27-11): Will attempt migration (Any information below is purely informational)
• 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): Will attempt migration (Any information below is purely informational)
• c2x/riscv64 (2.41.b+ds-2 to 2.41.b+ds-2)
  • Migration status for c2x/riscv64 (2.41.b+ds-2 to 2.41.b+ds-2): Will attempt migration (Any information below is purely informational)
• cacti-spine/riscv64 (1.2.25-1 to 1.2.25-1)
  • Migration status for cacti-spine/riscv64 (1.2.25-1 to 1.2.25-1): Will attempt migration (Any information below is purely informational)
• cadical/riscv64 (1.7.4-1 to 1.7.4-1)
  • Migration status for cadical/riscv64 (1.7.4-1 to 1.7.4-1): Will attempt migration (Any information below is purely informational)
• 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)
• cairo-ocaml/riscv64 (1:1.2.0-9 to 1:1.2.0-9)
  • Migration status for cairo-ocaml/riscv64 (1:1.2.0-9 to 1:1.2.0-9): Will attempt migration (Any information below is purely informational)
• cairomm1.16/riscv64 (1.18.0-1 to 1.18.0-1)
  • Migration status for cairomm1.16/riscv64 (1.18.0-1 to 1.18.0-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-seahorse/riscv64 (1.18.5-3 to 1.18.5-3)
  • Migration status for caja-seahorse/riscv64 (1.18.5-3 to 1.18.5-3): 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)
• cal3d/riscv64 (0.11.0-8.1 to 0.11.0-8.1)
  • Migration status for cal3d/riscv64 (0.11.0-8.1 to 0.11.0-8.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)
• calculix-ccx/riscv64 (2.21-1 to 2.21-1)
  • Migration status for calculix-ccx/riscv64 (2.21-1 to 2.21-1): Will attempt migration (Any information below is purely informational)
• calculix-cgx/riscv64 (2.21+dfsg-1 to 2.21+dfsg-1)
  • Migration status for calculix-cgx/riscv64 (2.21+dfsg-1 to 2.21+dfsg-1): Will attempt migration (Any information below is purely informational)
• 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)
• 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)
• calligra/riscv64 (1:3.2.1+dfsg-8 to 1:3.2.1+dfsg-8)
  • Migration status for calligra/riscv64 (1:3.2.1+dfsg-8 to 1:3.2.1+dfsg-8): 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)
• caml2html/riscv64 (1.4.4-3 to 1.4.4-3)
  • Migration status for caml2html/riscv64 (1.4.4-3 to 1.4.4-3): Will attempt migration (Any information below is purely informational)
• camlbz2/riscv64 (0.8.0-1 to 0.8.0-1)
  • Migration status for camlbz2/riscv64 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• camlidl/riscv64 (1.12-1 to 1.12-1)
  • Migration status for camlidl/riscv64 (1.12-1 to 1.12-1): Will attempt migration (Any information below is purely informational)
• camlimages/riscv64 (1:5.0.4-4 to 1:5.0.4-4)
  • Migration status for camlimages/riscv64 (1:5.0.4-4 to 1:5.0.4-4): Will attempt migration (Any information below is purely informational)
• camljava/riscv64 (0.3-5 to 0.3-5)
  • Migration status for camljava/riscv64 (0.3-5 to 0.3-5): Will attempt migration (Any information below is purely informational)
• camlp4/riscv64 (4.14+1-1 to 4.14+1-1)
  • Migration status for camlp4/riscv64 (4.14+1-1 to 4.14+1-1): Will attempt migration (Any information below is purely informational)
• camlp5-buildscripts/riscv64 (0.03-1 to 0.03-1)
  • Migration status for camlp5-buildscripts/riscv64 (0.03-1 to 0.03-1): Will attempt migration (Any information below is purely informational)
• camltemplate/riscv64 (1.0.2-4 to 1.0.2-4)
  • Migration status for camltemplate/riscv64 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• camomile/amd64 (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/amd64 (2.0.0-2 to 2.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: camomile/amd64 ocaml-dune (not considered)
    • Invalidated by dependency
• camomile/arm64 (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/arm64 (2.0.0-2 to 2.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: camomile/arm64 ocaml-dune (not considered)
    • Invalidated by dependency
• camomile/armel (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/armel (2.0.0-2 to 2.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: camomile/armel ocaml-dune (not considered)
    • Invalidated by dependency
• camomile/armhf (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/armhf (2.0.0-2 to 2.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: camomile/armhf ocaml-dune (not considered)
    • Invalidated by dependency
• camomile/i386 (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/i386 (2.0.0-2 to 2.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: camomile/i386 ocaml-dune (not considered)
    • Invalidated by dependency
• camomile/mips64el (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/mips64el (2.0.0-2 to 2.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: camomile/mips64el ocaml-dune (not considered)
    • Invalidated by dependency
• camomile/ppc64el (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/ppc64el (2.0.0-2 to 2.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: camomile/ppc64el ocaml-dune (not considered)
    • Invalidated by dependency
• camomile/riscv64 (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/riscv64 (2.0.0-2 to 2.0.0-2): Will attempt migration (Any information below is purely informational)
• camomile/s390x (2.0.0-2 to 2.0.0-2)
  • Migration status for camomile/s390x (2.0.0-2 to 2.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: camomile/s390x ocaml-dune (not considered)
    • Invalidated by dependency
• camp/riscv64 (0.8.4-4.1 to 0.8.4-4.1)
  • Migration status for camp/riscv64 (0.8.4-4.1 to 0.8.4-4.1): Will attempt migration (Any information below is purely informational)
• 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)
• capnproto/riscv64 (1.0.1-4 to 1.0.1-4)
  • Migration status for capnproto/riscv64 (1.0.1-4 to 1.0.1-4): Will attempt migration (Any information below is purely informational)
• caps/riscv64 (0.9.26-1 to 0.9.26-1)
  • Migration status for caps/riscv64 (0.9.26-1 to 0.9.26-1): Will attempt migration (Any information below is purely informational)
• capstats/riscv64 (0.31-1 to 0.31-1)
  • Migration status for capstats/riscv64 (0.31-1 to 0.31-1): Will attempt migration (Any information below is purely informational)
• 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)
• casa-formats-io/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for casa-formats-io/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• casacore/riscv64 (3.5.0-4.1 to 3.5.0-4.1)
  • Migration status for casacore/riscv64 (3.5.0-4.1 to 3.5.0-4.1): 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)
• cassiopee/riscv64 (1.0.9-4 to 1.0.9-4)
  • Migration status for cassiopee/riscv64 (1.0.9-4 to 1.0.9-4): Will attempt migration (Any information below is purely informational)
• cat-bat/riscv64 (5.3-2 to 5.3-2)
  • Migration status for cat-bat/riscv64 (5.3-2 to 5.3-2): Will attempt migration (Any information below is purely informational)
• cataclysm-dda/riscv64 (0.G-4 to 0.G-4)
  • Migration status for cataclysm-dda/riscv64 (0.G-4 to 0.G-4): Will attempt migration (Any information below is purely informational)
• catcodec/riscv64 (1.0.5-4 to 1.0.5-4)
  • Migration status for catcodec/riscv64 (1.0.5-4 to 1.0.5-4): Will attempt migration (Any information below is purely informational)
• caveexpress/riscv64 (2.5.2-2 to 2.5.2-2)
  • Migration status for caveexpress/riscv64 (2.5.2-2 to 2.5.2-2): 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)
• cbflib/riscv64 (0.9.7+dfsg1-3.1 to 0.9.7+dfsg1-3.1)
  • Migration status for cbflib/riscv64 (0.9.7+dfsg1-3.1 to 0.9.7+dfsg1-3.1): Will attempt migration (Any information below is purely informational)
• cbm/riscv64 (0.3.2-2 to 0.3.2-2)
  • Migration status for cbm/riscv64 (0.3.2-2 to 0.3.2-2): 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)
• cbp2make/riscv64 (147+dfsg-4 to 147+dfsg-4)
  • Migration status for cbp2make/riscv64 (147+dfsg-4 to 147+dfsg-4): Will attempt migration (Any information below is purely informational)
• cc-tool/riscv64 (0.27-1 to 0.27-1)
  • Migration status for cc-tool/riscv64 (0.27-1 to 0.27-1): Will attempt migration (Any information below is purely informational)
• ccbuild/riscv64 (2.0.9-1 to 2.0.9-1)
  • Migration status for ccbuild/riscv64 (2.0.9-1 to 2.0.9-1): Will attempt migration (Any information below is purely informational)
• cccc/riscv64 (1:3.2.0+dfsg1-1 to 1:3.2.0+dfsg1-1)
  • Migration status for cccc/riscv64 (1:3.2.0+dfsg1-1 to 1:3.2.0+dfsg1-1): Will attempt migration (Any information below is purely informational)
• ccfits/riscv64 (2.6+dfsg-1 to 2.6+dfsg-1)
  • Migration status for ccfits/riscv64 (2.6+dfsg-1 to 2.6+dfsg-1): 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)
• ccsm/riscv64 (2:0.8.18-4 to 2:0.8.18-4)
  • Migration status for ccsm/riscv64 (2:0.8.18-4 to 2:0.8.18-4): 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)
• cctz/riscv64 (2.3+dfsg1-5 to 2.3+dfsg1-5)
  • Migration status for cctz/riscv64 (2.3+dfsg1-5 to 2.3+dfsg1-5): Will attempt migration (Any information below is purely informational)
• cd-hit/riscv64 (4.8.1-4 to 4.8.1-4)
  • Migration status for cd-hit/riscv64 (4.8.1-4 to 4.8.1-4): Will attempt migration (Any information below is purely informational)
• cdargs/riscv64 (1.35-12 to 1.35-12)
  • Migration status for cdargs/riscv64 (1.35-12 to 1.35-12): Will attempt migration (Any information below is purely informational)
• cdbfasta/riscv64 (1.00+git20230710.da8f5ba+dfsg-1 to 1.00+git20230710.da8f5ba+dfsg-1)
  • Migration status for cdbfasta/riscv64 (1.00+git20230710.da8f5ba+dfsg-1 to 1.00+git20230710.da8f5ba+dfsg-1): Will attempt migration (Any information below is purely informational)
• cdck/riscv64 (0.7.0+dfsg-3 to 0.7.0+dfsg-3)
  • Migration status for cdck/riscv64 (0.7.0+dfsg-3 to 0.7.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• cdcover/riscv64 (0.9.1-14 to 0.9.1-14)
  • Migration status for cdcover/riscv64 (0.9.1-14 to 0.9.1-14): Will attempt migration (Any information below is purely informational)
• cddlib/riscv64 (094m-1.1 to 094m-1.1)
  • Migration status for cddlib/riscv64 (094m-1.1 to 094m-1.1): Will attempt migration (Any information below is purely informational)
• cdebconf-entropy/riscv64 (0.54 to 0.54)
  • Migration status for cdebconf-entropy/riscv64 (0.54 to 0.54): 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)
• 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)
• cdrdao/riscv64 (1:1.2.4-3 to 1:1.2.4-3)
  • Migration status for cdrdao/riscv64 (1:1.2.4-3 to 1:1.2.4-3): Will attempt migration (Any information below is purely informational)
• ceferino/riscv64 (0.97.8+svn37-3 to 0.97.8+svn37-3)
  • Migration status for ceferino/riscv64 (0.97.8+svn37-3 to 0.97.8+svn37-3): Will attempt migration (Any information below is purely informational)
• centrifuge/riscv64 (1.0.3-12 to 1.0.3-12)
  • Migration status for centrifuge/riscv64 (1.0.3-12 to 1.0.3-12): Will attempt migration (Any information below is purely informational)
• ceres-solver/riscv64 (2.2.0+dfsg-4.1 to 2.2.0+dfsg-4.1)
  • Migration status for ceres-solver/riscv64 (2.2.0+dfsg-4.1 to 2.2.0+dfsg-4.1): Will attempt migration (Any information below is purely informational)
• 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)
• cg3/riscv64 (1.4.6-1 to 1.4.6-1)
  • Migration status for cg3/riscv64 (1.4.6-1 to 1.4.6-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)
• cgit/riscv64 (1.2.3+git20221219.50.91f2590+git2.39.1-1 to 1.2.3+git20221219.50.91f2590+git2.39.1-1)
  • Migration status for cgit/riscv64 (1.2.3+git20221219.50.91f2590+git2.39.1-1 to 1.2.3+git20221219.50.91f2590+git2.39.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)
• cgsi-gsoap/riscv64 (1.3.11-5 to 1.3.11-5)
  • Migration status for cgsi-gsoap/riscv64 (1.3.11-5 to 1.3.11-5): Will attempt migration (Any information below is purely informational)
• charls/riscv64 (2.4.2-2 to 2.4.2-2)
  • Migration status for charls/riscv64 (2.4.2-2 to 2.4.2-2): 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)
• chasen/riscv64 (2.4.5-44 to 2.4.5-44)
  • Migration status for chasen/riscv64 (2.4.5-44 to 2.4.5-44): Will attempt migration (Any information below is purely informational)
• check/riscv64 (0.15.2-2 to 0.15.2-2)
  • Migration status for check/riscv64 (0.15.2-2 to 0.15.2-2): Will attempt migration (Any information below is purely informational)
• cheese/riscv64 (44.1-1 to 44.1-1)
  • Migration status for cheese/riscv64 (44.1-1 to 44.1-1): Will attempt migration (Any information below is purely informational)
• cheesecutter/riscv64 (2.9+git20211011-2 to 2.9+git20211011-2)
  • Migration status for cheesecutter/riscv64 (2.9+git20211011-2 to 2.9+git20211011-2): Will attempt migration (Any information below is purely informational)
• chemeq/riscv64 (3.6-1 to 3.6-1)
  • Migration status for chemeq/riscv64 (3.6-1 to 3.6-1): Will attempt migration (Any information below is purely informational)
• 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)
• chessx/riscv64 (1.4.6-2 to 1.4.6-2)
  • Migration status for chessx/riscv64 (1.4.6-2 to 1.4.6-2): 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)
• chocolate-doom/riscv64 (3.0.1+really3.0.0+git1548-1 to 3.0.1+really3.0.0+git1548-1)
  • Migration status for chocolate-doom/riscv64 (3.0.1+really3.0.0+git1548-1 to 3.0.1+really3.0.0+git1548-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)
• chroma/riscv64 (1.19-2 to 1.19-2)
  • Migration status for chroma/riscv64 (1.19-2 to 1.19-2): Will attempt migration (Any information below is purely informational)
• chromaprint/riscv64 (1.5.1-5 to 1.5.1-5)
  • Migration status for chromaprint/riscv64 (1.5.1-5 to 1.5.1-5): 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 (125.0.6422.60-1 to 126.0.6478.126-1~deb12u1)
  • Migration status for chromium_pu (125.0.6422.60-1 to 126.0.6478.126-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-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
    • chromium unsatisfiable Build-Depends(-Arch) on arm64: rustc-web
    • chromium unsatisfiable Build-Depends(-Arch) on armhf: rustc-web
    • chromium unsatisfiable Build-Depends(-Arch) on i386: rustc-web
    • chromium unsatisfiable Build-Depends(-Arch) on ppc64el: rustc-web
    • 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)
• chron/riscv64 (2.3-61-2 to 2.3-61-2)
  • Migration status for chron/riscv64 (2.3-61-2 to 2.3-61-2): Will attempt migration (Any information below is purely informational)
• chuck/riscv64 (1.5.2.4-1 to 1.5.2.4-1)
  • Migration status for chuck/riscv64 (1.5.2.4-1 to 1.5.2.4-1): Will attempt migration (Any information below is purely informational)
• chuffed/riscv64 (0.13.1-1 to 0.13.1-1)
  • Migration status for chuffed/riscv64 (0.13.1-1 to 0.13.1-1): Will attempt migration (Any information below is purely informational)
• cif-api/riscv64 (0.4.2-5 to 0.4.2-5)
  • Migration status for cif-api/riscv64 (0.4.2-5 to 0.4.2-5): Will attempt migration (Any information below is purely informational)
• cif-tools/riscv64 (1.0.7-1 to 1.0.7-1)
  • Migration status for cif-tools/riscv64 (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
• cif2hkl/riscv64 (1.4.3+ds1-1 to 1.4.3+ds1-1)
  • Migration status for cif2hkl/riscv64 (1.4.3+ds1-1 to 1.4.3+ds1-1): Will attempt migration (Any information below is purely informational)
• 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-control-center/riscv64 (6.0.1-3 to 6.0.1-3)
  • Migration status for cinnamon-control-center/riscv64 (6.0.1-3 to 6.0.1-3): Will attempt migration (Any information below is purely informational)
• cinnamon-desktop-environment/riscv64 (5.8.0 to 5.8.0)
  • Migration status for cinnamon-desktop-environment/riscv64 (5.8.0 to 5.8.0): 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-screensaver/riscv64 (6.0.3-2 to 6.0.3-2)
  • Migration status for cinnamon-screensaver/riscv64 (6.0.3-2 to 6.0.3-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)
• circuslinux/riscv64 (1.0.3-35 to 1.0.3-35)
  • Migration status for circuslinux/riscv64 (1.0.3-35 to 1.0.3-35): 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)
• civetweb/riscv64 (1.16+dfsg-1 to 1.16+dfsg-1)
  • Migration status for civetweb/riscv64 (1.16+dfsg-1 to 1.16+dfsg-1): Will attempt migration (Any information below is purely informational)
• cjk/riscv64 (4.8.5-1 to 4.8.5-1)
  • Migration status for cjk/riscv64 (4.8.5-1 to 4.8.5-1): Will attempt migration (Any information below is purely informational)
• cjs/riscv64 (6.0.0-2 to 6.0.0-2)
  • Migration status for cjs/riscv64 (6.0.0-2 to 6.0.0-2): 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)
• ckon/riscv64 (0.7.1-5 to 0.7.1-5)
  • Migration status for ckon/riscv64 (0.7.1-5 to 0.7.1-5): Will attempt migration (Any information below is purely informational)
• cl-sql/riscv64 (6.7.2-1.1 to 6.7.2-1.1)
  • Migration status for cl-sql/riscv64 (6.7.2-1.1 to 6.7.2-1.1): Will attempt migration (Any information below is purely informational)
• clalsadrv/riscv64 (2.0.0-4.1 to 2.0.0-4.1)
  • Migration status for clalsadrv/riscv64 (2.0.0-4.1 to 2.0.0-4.1): Will attempt migration (Any information below is purely informational)
• clamfs/riscv64 (1.3.0-1 to 1.3.0-1)
  • Migration status for clamfs/riscv64 (1.3.0-1 to 1.3.0-1): 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)
• clasp/riscv64 (3.3.5-4.2 to 3.3.5-4.2)
  • Migration status for clasp/riscv64 (3.3.5-4.2 to 3.3.5-4.2): Will attempt migration (Any information below is purely informational)
• cld2/riscv64 (0.0.0-git20150806-9 to 0.0.0-git20150806-9)
  • Migration status for cld2/riscv64 (0.0.0-git20150806-9 to 0.0.0-git20150806-9): 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)
• clfft/riscv64 (2.12.2-5 to 2.12.2-5)
  • Migration status for clfft/riscv64 (2.12.2-5 to 2.12.2-5): Will attempt migration (Any information below is purely informational)
• clhep/riscv64 (2.1.4.1+dfsg-1.2 to 2.1.4.1+dfsg-1.2)
  • Migration status for clhep/riscv64 (2.1.4.1+dfsg-1.2 to 2.1.4.1+dfsg-1.2): Will attempt migration (Any information below is purely informational)
• clipit/riscv64 (1.4.5+git20210313-2 to 1.4.5+git20210313-2)
  • Migration status for clipit/riscv64 (1.4.5+git20210313-2 to 1.4.5+git20210313-2): Will attempt migration (Any information below is purely informational)
• clisp/riscv64 (1:2.49.20210628.gitde01f0f-3.1 to 1:2.49.20210628.gitde01f0f-3.1)
  • Migration status for clisp/riscv64 (1:2.49.20210628.gitde01f0f-3.1 to 1:2.49.20210628.gitde01f0f-3.1): Will attempt migration (Any information below is purely informational)
• cln/riscv64 (1.3.7-1 to 1.3.7-1)
  • Migration status for cln/riscv64 (1.3.7-1 to 1.3.7-1): Will attempt migration (Any information below is purely informational)
• clog/riscv64 (1.3.0-1.1 to 1.3.0-1.1)
  • Migration status for clog/riscv64 (1.3.0-1.1 to 1.3.0-1.1): Will attempt migration (Any information below is purely informational)
• clonalframe/riscv64 (1.2-11 to 1.2-11)
  • Migration status for clonalframe/riscv64 (1.2-11 to 1.2-11): Will attempt migration (Any information below is purely informational)
• clonalframeml/riscv64 (1.13-1 to 1.13-1)
  • Migration status for clonalframeml/riscv64 (1.13-1 to 1.13-1): Will attempt migration (Any information below is purely informational)
• clonalorigin/riscv64 (1.0-8 to 1.0-8)
  • Migration status for clonalorigin/riscv64 (1.0-8 to 1.0-8): Will attempt migration (Any information below is purely informational)
• cloop/riscv64 (3.14.1.3+nmu1 to 3.14.1.3+nmu1)
  • Migration status for cloop/riscv64 (3.14.1.3+nmu1 to 3.14.1.3+nmu1): Will attempt migration (Any information below is purely informational)
• cloudcompare/riscv64 (2.11.3-7.1 to 2.11.3-7.1)
  • Migration status for cloudcompare/riscv64 (2.11.3-7.1 to 2.11.3-7.1): Will attempt migration (Any information below is purely informational)
• cloudflare-ddns/riscv64 (2.1.0-1 to 2.1.0-1)
  • Migration status for cloudflare-ddns/riscv64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• clpeak/riscv64 (1.1.2-1 to 1.1.2-1)
  • Migration status for clpeak/riscv64 (1.1.2-1 to 1.1.2-1): Will attempt migration (Any information below is purely informational)
• clthreads/riscv64 (2.4.2-1.1 to 2.4.2-1.1)
  • Migration status for clthreads/riscv64 (2.4.2-1.1 to 2.4.2-1.1): Will attempt migration (Any information below is purely informational)
• clucene-core/riscv64 (2.3.3.4+dfsg-1.2 to 2.3.3.4+dfsg-1.2)
  • Migration status for clucene-core/riscv64 (2.3.3.4+dfsg-1.2 to 2.3.3.4+dfsg-1.2): Will attempt migration (Any information below is purely informational)
• clustalo/riscv64 (1.2.4-8 to 1.2.4-8)
  • Migration status for clustalo/riscv64 (1.2.4-8 to 1.2.4-8): Will attempt migration (Any information below is purely informational)
• clustalw/riscv64 (2.1+lgpl-7 to 2.1+lgpl-7)
  • Migration status for clustalw/riscv64 (2.1+lgpl-7 to 2.1+lgpl-7): Will attempt migration (Any information below is purely informational)
• 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)
• cluster/riscv64 (2.1.6-1 to 2.1.6-1)
  • Migration status for cluster/riscv64 (2.1.6-1 to 2.1.6-1): 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)
• clxclient/riscv64 (3.9.2-2.1 to 3.9.2-2.1)
  • Migration status for clxclient/riscv64 (3.9.2-2.1 to 3.9.2-2.1): Will attempt migration (Any information below is purely informational)
• cmor/riscv64 (3.8.0-1 to 3.8.0-1)
  • Migration status for cmor/riscv64 (3.8.0-1 to 3.8.0-1): Will attempt migration (Any information below is purely informational)
• cmt/riscv64 (1.18-1 to 1.18-1)
  • Migration status for cmt/riscv64 (1.18-1 to 1.18-1): Will attempt migration (Any information below is purely informational)
• cmtk/riscv64 (3.3.1p2+dfsg-2 to 3.3.1p2+dfsg-2)
  • Migration status for cmtk/riscv64 (3.3.1p2+dfsg-2 to 3.3.1p2+dfsg-2): Will attempt migration (Any information below is purely informational)
• coco-cpp/riscv64 (20120102-3 to 20120102-3)
  • Migration status for coco-cpp/riscv64 (20120102-3 to 20120102-3): Will attempt migration (Any information below is purely informational)
• coda/riscv64 (2.25.2-1.1 to 2.25.2-1.1)
  • Migration status for coda/riscv64 (2.25.2-1.1 to 2.25.2-1.1): Will attempt migration (Any information below is purely informational)
• 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)
• codecrypt/riscv64 (1.8-1 to 1.8-1)
  • Migration status for codecrypt/riscv64 (1.8-1 to 1.8-1): 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)
• codetiming/riscv64 (1.4.0-2 to 1.4.0-2)
  • Migration status for codetiming/riscv64 (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• codfis/riscv64 (0.4.7-2 to 0.4.7-2)
  • Migration status for codfis/riscv64 (0.4.7-2 to 0.4.7-2): Will attempt migration (Any information below is purely informational)
• 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)
• cohomcalg/riscv64 (0.32+ds-6 to 0.32+ds-6)
  • Migration status for cohomcalg/riscv64 (0.32+ds-6 to 0.32+ds-6): Will attempt migration (Any information below is purely informational)
• coinmp/riscv64 (1.8.3-3 to 1.8.3-3)
  • Migration status for coinmp/riscv64 (1.8.3-3 to 1.8.3-3): 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-csdp/riscv64 (6.2.0-5 to 6.2.0-5)
  • Migration status for coinor-csdp/riscv64 (6.2.0-5 to 6.2.0-5): 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)
• coinor-osi/riscv64 (0.108.10+ds-1 to 0.108.10+ds-1)
  • Migration status for coinor-osi/riscv64 (0.108.10+ds-1 to 0.108.10+ds-1): Will attempt migration (Any information below is purely informational)
• coinor-symphony/riscv64 (5.6.17+dfsg-1 to 5.6.17+dfsg-1)
  • Migration status for coinor-symphony/riscv64 (5.6.17+dfsg-1 to 5.6.17+dfsg-1): Will attempt migration (Any information below is purely informational)
• coinor-vol/riscv64 (1.5.4-4 to 1.5.4-4)
  • Migration status for coinor-vol/riscv64 (1.5.4-4 to 1.5.4-4): Will attempt migration (Any information below is purely informational)
• coinutils/riscv64 (2.11.4+repack1-4 to 2.11.4+repack1-4)
  • Migration status for coinutils/riscv64 (2.11.4+repack1-4 to 2.11.4+repack1-4): 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)
• colmap/riscv64 (3.9.1-2 to 3.9.1-2)
  • Migration status for colmap/riscv64 (3.9.1-2 to 3.9.1-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)
• colortail/riscv64 (0.3.3-1 to 0.3.3-1)
  • Migration status for colortail/riscv64 (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• colpack/riscv64 (1.0.10-8 to 1.0.10-8)
  • Migration status for colpack/riscv64 (1.0.10-8 to 1.0.10-8): 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)
• comedilib/riscv64 (0.11.0+5-1.1 to 0.11.0+5-1.1)
  • Migration status for comedilib/riscv64 (0.11.0+5-1.1 to 0.11.0+5-1.1): Will attempt migration (Any information below is purely informational)
• comet-ms/riscv64 (2019015+cleaned1-4.1 to 2019015+cleaned1-4.1)
  • Migration status for comet-ms/riscv64 (2019015+cleaned1-4.1 to 2019015+cleaned1-4.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)
• comptext/riscv64 (1.0.1-6 to 1.0.1-6)
  • Migration status for comptext/riscv64 (1.0.1-6 to 1.0.1-6): Will attempt migration (Any information below is purely informational)
• compton-conf/riscv64 (0.16.0-3 to 0.16.0-3)
  • Migration status for compton-conf/riscv64 (0.16.0-3 to 0.16.0-3): 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)
• comptty/riscv64 (1.0.1-5 to 1.0.1-5)
  • Migration status for comptty/riscv64 (1.0.1-5 to 1.0.1-5): Will attempt migration (Any information below is purely informational)
• comskip/riscv64 (0.82.009+git20230112.d0cc422+ds.1-2.1 to 0.82.009+git20230112.d0cc422+ds.1-2.1)
  • Migration status for comskip/riscv64 (0.82.009+git20230112.d0cc422+ds.1-2.1 to 0.82.009+git20230112.d0cc422+ds.1-2.1): Will attempt migration (Any information below is purely informational)
• concalc/riscv64 (0.9.2-2.1 to 0.9.2-2.1)
  • Migration status for concalc/riscv64 (0.9.2-2.1 to 0.9.2-2.1): Will attempt migration (Any information below is purely informational)
• concavity/riscv64 (0.1+dfsg.1-5 to 0.1+dfsg.1-5)
  • Migration status for concavity/riscv64 (0.1+dfsg.1-5 to 0.1+dfsg.1-5): 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)
• consensuscore/riscv64 (1.1.1+dfsg-7 to 1.1.1+dfsg-7)
  • Migration status for consensuscore/riscv64 (1.1.1+dfsg-7 to 1.1.1+dfsg-7): Will attempt migration (Any information below is purely informational)
• console-bridge/riscv64 (1.0.1+dfsg2-3 to 1.0.1+dfsg2-3)
  • Migration status for console-bridge/riscv64 (1.0.1+dfsg2-3 to 1.0.1+dfsg2-3): Will attempt migration (Any information below is purely informational)
• contourpy/riscv64 (1.0.7-3 to 1.0.7-3)
  • Migration status for contourpy/riscv64 (1.0.7-3 to 1.0.7-3): Will attempt migration (Any information below is purely informational)
• 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)
• cool-retro-term/riscv64 (1.2.0+ds2-2 to 1.2.0+ds2-2)
  • Migration status for cool-retro-term/riscv64 (1.2.0+ds2-2 to 1.2.0+ds2-2): Will attempt migration (Any information below is purely informational)
• coolkey/riscv64 (1.1.0-16.1 to 1.1.0-16.1)
  • Migration status for coolkey/riscv64 (1.1.0-16.1 to 1.1.0-16.1): Will attempt migration (Any information below is purely informational)
• 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)
• cothreads/riscv64 (0.10-6 to 0.10-6)
  • Migration status for cothreads/riscv64 (0.10-6 to 0.10-6): Will attempt migration (Any information below is purely informational)
• courier-unicode/riscv64 (2.1.2-2 to 2.1.2-2)
  • Migration status for courier-unicode/riscv64 (2.1.2-2 to 2.1.2-2): Will attempt migration (Any information below is purely informational)
• covtobed/riscv64 (1.3.5+dfsg-2 to 1.3.5+dfsg-2)
  • Migration status for covtobed/riscv64 (1.3.5+dfsg-2 to 1.3.5+dfsg-2): Will attempt migration (Any information below is purely informational)
• cpl-plugin-giraf/riscv64 (2.16.10+dfsg-1 to 2.16.10+dfsg-1)
  • Migration status for cpl-plugin-giraf/riscv64 (2.16.10+dfsg-1 to 2.16.10+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-hawki/riscv64 (2.4.11+dfsg-1 to 2.4.11+dfsg-1)
  • Migration status for cpl-plugin-hawki/riscv64 (2.4.11+dfsg-1 to 2.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl-plugin-naco/riscv64 (4.4.11+dfsg-1 to 4.4.11+dfsg-1)
  • Migration status for cpl-plugin-naco/riscv64 (4.4.11+dfsg-1 to 4.4.11+dfsg-1): Will attempt migration (Any information below is purely informational)
• cpl/riscv64 (7.3.2+ds-1 to 7.3.2+ds-1)
  • Migration status for cpl/riscv64 (7.3.2+ds-1 to 7.3.2+ds-1): Will attempt migration (Any information below is purely informational)
• cpluff/riscv64 (0.2.0+ds1-2 to 0.2.0+ds1-2)
  • Migration status for cpluff/riscv64 (0.2.0+ds1-2 to 0.2.0+ds1-2): Will attempt migration (Any information below is purely informational)
• cpp-hocon/riscv64 (0.3.0-1.1 to 0.3.0-1.1)
  • Migration status for cpp-hocon/riscv64 (0.3.0-1.1 to 0.3.0-1.1): Will attempt migration (Any information below is purely informational)
• cppcheck/riscv64 (2.14.0-1 to 2.14.0-1)
  • Migration status for cppcheck/riscv64 (2.14.0-1 to 2.14.0-1): Will attempt migration (Any information below is purely informational)
• cppdap/riscv64 (1.58.0a-4 to 1.58.0a-4)
  • Migration status for cppdap/riscv64 (1.58.0a-4 to 1.58.0a-4): Will attempt migration (Any information below is purely informational)
• cppdb/riscv64 (0.3.1+dfsg-9.1 to 0.3.1+dfsg-9.1)
  • Migration status for cppdb/riscv64 (0.3.1+dfsg-9.1 to 0.3.1+dfsg-9.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)
• cpprest/riscv64 (2.10.19-2 to 2.10.19-2)
  • Migration status for cpprest/riscv64 (2.10.19-2 to 2.10.19-2): Will attempt migration (Any information below is purely informational)
• cpptest/riscv64 (2.0.0-3 to 2.0.0-3)
  • Migration status for cpptest/riscv64 (2.0.0-3 to 2.0.0-3): Will attempt migration (Any information below is purely informational)
• cppunit/riscv64 (1.15.1-4 to 1.15.1-4)
  • Migration status for cppunit/riscv64 (1.15.1-4 to 1.15.1-4): 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)
• crac/riscv64 (2.5.2+dfsg-6 to 2.5.2+dfsg-6)
  • Migration status for crac/riscv64 (2.5.2+dfsg-6 to 2.5.2+dfsg-6): 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)
• crash/riscv64 (8.0.5-1 to 8.0.5-1)
  • Migration status for crash/riscv64 (8.0.5-1 to 8.0.5-1): 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)
• credcheck/riscv64 (2.7-1 to 2.7-1)
  • Migration status for credcheck/riscv64 (2.7-1 to 2.7-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)
• crispy-doom/riscv64 (6.0-2 to 6.0-2)
  • Migration status for crispy-doom/riscv64 (6.0-2 to 6.0-2): Will attempt migration (Any information below is purely informational)
• critcl/riscv64 (3.1.18.1+dfsg-3 to 3.1.18.1+dfsg-3)
  • Migration status for critcl/riscv64 (3.1.18.1+dfsg-3 to 3.1.18.1+dfsg-3): 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)
• critterding/riscv64 (1.0-beta12.1-1.3 to 1.0-beta12.1-1.3)
  • Migration status for critterding/riscv64 (1.0-beta12.1-1.3 to 1.0-beta12.1-1.3): 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)
• crossguid/riscv64 (0.0+git200150803-6 to 0.0+git200150803-6)
  • Migration status for crossguid/riscv64 (0.0+git200150803-6 to 0.0+git200150803-6): Will attempt migration (Any information below is purely informational)
• crow-translate/riscv64 (2.11.1+git20240108+ds-1 to 2.11.1+git20240108+ds-1)
  • Migration status for crow-translate/riscv64 (2.11.1+git20240108+ds-1 to 2.11.1+git20240108+ds-1): Will attempt migration (Any information below is purely informational)
• 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)
• cryfs/riscv64 (0.11.4-1 to 0.11.4-1)
  • Migration status for cryfs/riscv64 (0.11.4-1 to 0.11.4-1): Will attempt migration (Any information below is purely informational)
• cryptgps/riscv64 (0.2.1-12 to 0.2.1-12)
  • Migration status for cryptgps/riscv64 (0.2.1-12 to 0.2.1-12): Will attempt migration (Any information below is purely informational)
• cryptominisat/riscv64 (5.11.21+dfsg1-1 to 5.11.21+dfsg1-1)
  • Migration status for cryptominisat/riscv64 (5.11.21+dfsg1-1 to 5.11.21+dfsg1-1): Will attempt migration (Any information below is purely informational)
• csladspa/riscv64 (1:6.11.1-1 to 1:6.11.1-1)
  • Migration status for csladspa/riscv64 (1:6.11.1-1 to 1:6.11.1-1): Will attempt migration (Any information below is purely informational)
• csmith/riscv64 (2.3.0-7.1 to 2.3.0-7.1)
  • Migration status for csmith/riscv64 (2.3.0-7.1 to 2.3.0-7.1): 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)
• csoundqt/riscv64 (1.1.1+dfsg0-1 to 1.1.1+dfsg0-1)
  • Migration status for csoundqt/riscv64 (1.1.1+dfsg0-1 to 1.1.1+dfsg0-1): Will attempt migration (Any information below is purely informational)
• cssc/riscv64 (1.4.1-1 to 1.4.1-1)
  • Migration status for cssc/riscv64 (1.4.1-1 to 1.4.1-1): Will attempt migration (Any information below is purely informational)
• csync2/riscv64 (2.0-42-g83b3644-2 to 2.0-42-g83b3644-2)
  • Migration status for csync2/riscv64 (2.0-42-g83b3644-2 to 2.0-42-g83b3644-2): Will attempt migration (Any information below is purely informational)
• ctemplate/riscv64 (2.4-3.1 to 2.4-3.1)
  • Migration status for ctemplate/riscv64 (2.4-3.1 to 2.4-3.1): Will attempt migration (Any information below is purely informational)
• ctffind/riscv64 (4.1.14-2 to 4.1.14-2)
  • Migration status for ctffind/riscv64 (4.1.14-2 to 4.1.14-2): Will attempt migration (Any information below is purely informational)
• ctorrent/riscv64 (1.3.4.dnh3.3.2-6 to 1.3.4.dnh3.3.2-6)
  • Migration status for ctorrent/riscv64 (1.3.4.dnh3.3.2-6 to 1.3.4.dnh3.3.2-6): 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)
• cubemap/riscv64 (1.5.1-2 to 1.5.1-2)
  • Migration status for cubemap/riscv64 (1.5.1-2 to 1.5.1-2): Will attempt migration (Any information below is purely informational)
• cufflinks/riscv64 (2.2.1+dfsg.1-9 to 2.2.1+dfsg.1-9)
  • Migration status for cufflinks/riscv64 (2.2.1+dfsg.1-9 to 2.2.1+dfsg.1-9): Will attempt migration (Any information below is purely informational)
• cultivation/riscv64 (9+dfsg1-2 to 9+dfsg1-2)
  • Migration status for cultivation/riscv64 (9+dfsg1-2 to 9+dfsg1-2): Will attempt migration (Any information below is purely informational)
• cups-filters/riscv64 (1.28.17-4 to 1.28.17-4)
  • Migration status for cups-filters/riscv64 (1.28.17-4 to 1.28.17-4): Will attempt migration (Any information below is purely informational)
• cups_pu (2.4.10-1 to 2.4.2-3+deb12u7)
  • Migration status for cups_pu (2.4.10-1 to 2.4.2-3+deb12u7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: cups is newer in the target suite (2.4.10-1 2.4.2-3+deb12u7)
• cupt/riscv64 (2.10.4+nmu2 to 2.10.4+nmu2)
  • Migration status for cupt/riscv64 (2.10.4+nmu2 to 2.10.4+nmu2): Will attempt migration (Any information below is purely informational)
• cura-engine/riscv64 (1:5.0.0-4 to 1:5.0.0-4)
  • Migration status for cura-engine/riscv64 (1:5.0.0-4 to 1:5.0.0-4): Will attempt migration (Any information below is purely informational)
• curlpp/riscv64 (0.8.1-5.3 to 0.8.1-5.3)
  • Migration status for curlpp/riscv64 (0.8.1-5.3 to 0.8.1-5.3): 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)
• cuyo/riscv64 (2.1.0-1 to 2.1.0-1)
  • Migration status for cuyo/riscv64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• cvc4/riscv64 (1.8-3 to 1.8-3)
  • Migration status for cvc4/riscv64 (1.8-3 to 1.8-3): Will attempt migration (Any information below is purely informational)
• cvc5/riscv64 (1.1.2-2 to 1.1.2-2)
  • Migration status for cvc5/riscv64 (1.1.2-2 to 1.1.2-2): Will attempt migration (Any information below is purely informational)
• cvsgraph/riscv64 (1.7.0-6 to 1.7.0-6)
  • Migration status for cvsgraph/riscv64 (1.7.0-6 to 1.7.0-6): Will attempt migration (Any information below is purely informational)
• cvxopt/riscv64 (1.3.0+dfsg-1 to 1.3.0+dfsg-1)
  • Migration status for cvxopt/riscv64 (1.3.0+dfsg-1 to 1.3.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• cwidget/riscv64 (0.5.18-6 to 0.5.18-6)
  • Migration status for cwidget/riscv64 (0.5.18-6 to 0.5.18-6): Will attempt migration (Any information below is purely informational)
• cwiid/riscv64 (0.6.91-7.1 to 0.6.91-7.1)
  • Migration status for cwiid/riscv64 (0.6.91-7.1 to 0.6.91-7.1): Will attempt migration (Any information below is purely informational)
• cxxtools/riscv64 (3.0.0-3 to 3.0.0-3)
  • Migration status for cxxtools/riscv64 (3.0.0-3 to 3.0.0-3): Will attempt migration (Any information below is purely informational)
• cyarray/riscv64 (1.1-7 to 1.1-7)
  • Migration status for cyarray/riscv64 (1.1-7 to 1.1-7): 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)
• d-itg/riscv64 (2.8.1-r1023-6 to 2.8.1-r1023-6)
  • Migration status for d-itg/riscv64 (2.8.1-r1023-6 to 2.8.1-r1023-6): Will attempt migration (Any information below is purely informational)
• d-spy/riscv64 (1.10.0-1 to 1.10.0-1)
  • Migration status for d-spy/riscv64 (1.10.0-1 to 1.10.0-1): 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)
• dangen/riscv64 (0.5-7 to 0.5-7)
  • Migration status for dangen/riscv64 (0.5-7 to 0.5-7): 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/riscv64 (2.7.14-1 to 2.7.14-1)
  • Migration status for dar/riscv64 (2.7.14-1 to 2.7.14-1): Will attempt migration (Any information below is purely informational)
• darkice/riscv64 (1.3-0.3 to 1.3-0.3)
  • Migration status for darkice/riscv64 (1.3-0.3 to 1.3-0.3): Will attempt migration (Any information below is purely informational)
• 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)
• darnwdl/riscv64 (0.8-1 to 0.8-1)
  • Migration status for darnwdl/riscv64 (0.8-1 to 0.8-1): Will attempt migration (Any information below is purely informational)
• dart/riscv64 (6.12.1+dfsg4-13.1 to 6.12.1+dfsg4-13.1)
  • Migration status for dart/riscv64 (6.12.1+dfsg4-13.1 to 6.12.1+dfsg4-13.1): Will attempt migration (Any information below is purely informational)
• darts/riscv64 (0.32-20 to 0.32-20)
  • Migration status for darts/riscv64 (0.32-20 to 0.32-20): Will attempt migration (Any information below is purely informational)
• 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)
• dashel/riscv64 (1.3.3-6 to 1.3.3-6)
  • Migration status for dashel/riscv64 (1.3.3-6 to 1.3.3-6): 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)
• date/riscv64 (1.2.42-1 to 1.2.42-1)
  • Migration status for date/riscv64 (1.2.42-1 to 1.2.42-1): Will attempt migration (Any information below is purely informational)
• davegnukem/riscv64 (1.0.3-4 to 1.0.3-4)
  • Migration status for davegnukem/riscv64 (1.0.3-4 to 1.0.3-4): 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)
• dawg/riscv64 (1.2-4 to 1.2-4)
  • Migration status for dawg/riscv64 (1.2-4 to 1.2-4): Will attempt migration (Any information below is purely informational)
• dawgdic/riscv64 (0.4.5-3 to 0.4.5-3)
  • Migration status for dawgdic/riscv64 (0.4.5-3 to 0.4.5-3): Will attempt migration (Any information below is purely informational)
• dbeacon/riscv64 (0.4.0-2 to 0.4.0-2)
  • Migration status for dbeacon/riscv64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• dbus-c++/riscv64 (0.9.0-12 to 0.9.0-12)
  • Migration status for dbus-c++/riscv64 (0.9.0-12 to 0.9.0-12): Will attempt migration (Any information below is purely informational)
• dbus-deviation/riscv64 (0.6.0-2 to 0.6.0-2)
  • Migration status for dbus-deviation/riscv64 (0.6.0-2 to 0.6.0-2): Will attempt migration (Any information below is purely informational)
• dbusada/riscv64 (0.6.2-6 to 0.6.2-6)
  • Migration status for dbusada/riscv64 (0.6.2-6 to 0.6.2-6): Will attempt migration (Any information below is purely informational)
• dbuskit/riscv64 (0.1.1-3 to 0.1.1-3)
  • Migration status for dbuskit/riscv64 (0.1.1-3 to 0.1.1-3): 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)
• dcm2niix/riscv64 (1.0.20220720-1 to 1.0.20220720-1)
  • Migration status for dcm2niix/riscv64 (1.0.20220720-1 to 1.0.20220720-1): 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)
• dd-opentracing-cpp/riscv64 (1.3.7-1 to 1.3.7-1)
  • Migration status for dd-opentracing-cpp/riscv64 (1.3.7-1 to 1.3.7-1): Will attempt migration (Any information below is purely informational)
• dd2/riscv64 (0.2.2-4 to 0.2.2-4)
  • Migration status for dd2/riscv64 (0.2.2-4 to 0.2.2-4): Will attempt migration (Any information below is purely informational)
• ddcui/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for ddcui/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• ddd/riscv64 (1:3.3.12-5.4 to 1:3.3.12-5.4)
  • Migration status for ddd/riscv64 (1:3.3.12-5.4 to 1:3.3.12-5.4): 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)
• ddnet/riscv64 (16.4-1.2 to 16.4-1.2)
  • Migration status for ddnet/riscv64 (16.4-1.2 to 16.4-1.2): Will attempt migration (Any information below is purely informational)
• ddpt/riscv64 (0.97-1 to 0.97-1)
  • Migration status for ddpt/riscv64 (0.97-1 to 0.97-1): Will attempt migration (Any information below is purely informational)
• ddrutility/riscv64 (2.8-4 to 2.8-4)
  • Migration status for ddrutility/riscv64 (2.8-4 to 2.8-4): Will attempt migration (Any information below is purely informational)
• dds/riscv64 (2.9.0-10 to 2.9.0-10)
  • Migration status for dds/riscv64 (2.9.0-10 to 2.9.0-10): Will attempt migration (Any information below is purely informational)
• deal/riscv64 (3.1.9-13 to 3.1.9-13)
  • Migration status for deal/riscv64 (3.1.9-13 to 3.1.9-13): 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)
• debfoster/riscv64 (2.7-2.2 to 2.7-2.2)
  • Migration status for debfoster/riscv64 (2.7-2.2 to 2.7-2.2): Will attempt migration (Any information below is purely informational)
• debian-edu/riscv64 (2.12.15 to 2.12.15)
  • Migration status for debian-edu/riscv64 (2.12.15 to 2.12.15): Will attempt migration (Any information below is purely informational)
• dee/riscv64 (1.2.7+17.10.20170616-7 to 1.2.7+17.10.20170616-7)
  • Migration status for dee/riscv64 (1.2.7+17.10.20170616-7 to 1.2.7+17.10.20170616-7): Will attempt migration (Any information below is purely informational)
• deepin-album/riscv64 (5.9.1+dfsg-1 to 5.9.1+dfsg-1)
  • Migration status for deepin-album/riscv64 (5.9.1+dfsg-1 to 5.9.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• 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-movie-reborn/riscv64 (5.10.8-2.1 to 5.10.8-2.1)
  • Migration status for deepin-movie-reborn/riscv64 (5.10.8-2.1 to 5.10.8-2.1): Will attempt migration (Any information below is purely informational)
• deepin-music/riscv64 (6.2.18-1 to 6.2.18-1)
  • Migration status for deepin-music/riscv64 (6.2.18-1 to 6.2.18-1): 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)
• deepin-terminal/riscv64 (5.9.40+dfsg-2 to 5.9.40+dfsg-2)
  • Migration status for deepin-terminal/riscv64 (5.9.40+dfsg-2 to 5.9.40+dfsg-2): 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)
• delly/riscv64 (1.1.8-1 to 1.1.8-1)
  • Migration status for delly/riscv64 (1.1.8-1 to 1.1.8-1): Will attempt migration (Any information below is purely informational)
• denemo/riscv64 (2.6.18-1 to 2.6.18-1)
  • Migration status for denemo/riscv64 (2.6.18-1 to 2.6.18-1): Will attempt migration (Any information below is purely informational)
• desktopfolder/riscv64 (1.1.3-3 to 1.1.3-3)
  • Migration status for desktopfolder/riscv64 (1.1.3-3 to 1.1.3-3): 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)
• devtodo/riscv64 (0.1.20+git20200830.0ad52b0-3 to 0.1.20+git20200830.0ad52b0-3)
  • Migration status for devtodo/riscv64 (0.1.20+git20200830.0ad52b0-3 to 0.1.20+git20200830.0ad52b0-3): 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)
• dextractor/riscv64 (1.0-6 to 1.0-6)
  • Migration status for dextractor/riscv64 (1.0-6 to 1.0-6): 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)
• dhewm3/riscv64 (1.5.2+dfsg-1 to 1.5.2+dfsg-1)
  • Migration status for dhewm3/riscv64 (1.5.2+dfsg-1 to 1.5.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• diagnostics/riscv64 (0.3.3-12.4 to 0.3.3-12.4)
  • Migration status for diagnostics/riscv64 (0.3.3-12.4 to 0.3.3-12.4): Will attempt migration (Any information below is purely informational)
• diamond-aligner/riscv64 (2.1.9-1 to 2.1.9-1)
  • Migration status for diamond-aligner/riscv64 (2.1.9-1 to 2.1.9-1): 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)
• dibbler/riscv64 (1.0.1-1.1 to 1.0.1-1.1)
  • Migration status for dibbler/riscv64 (1.0.1-1.1 to 1.0.1-1.1): Will attempt migration (Any information below is purely informational)
• dicom3tools/riscv64 (1.00~20240118131615-1 to 1.00~20240118131615-1)
  • Migration status for dicom3tools/riscv64 (1.00~20240118131615-1 to 1.00~20240118131615-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)
• diet-ng/riscv64 (1.8.1-3 to 1.8.1-3)
  • Migration status for diet-ng/riscv64 (1.8.1-3 to 1.8.1-3): 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)
• 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/riscv64 (4:8.3.0-2 to 4:8.3.0-2)
  • Migration status for digikam/riscv64 (4:8.3.0-2 to 4:8.3.0-2): Will attempt migration (Any information below is purely informational)
• 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)
• dillo/riscv64 (3.0.5-7 to 3.0.5-7)
  • Migration status for dillo/riscv64 (3.0.5-7 to 3.0.5-7): Will attempt migration (Any information below is purely informational)
• dime/riscv64 (0.20111205-2.2 to 0.20111205-2.2)
  • Migration status for dime/riscv64 (0.20111205-2.2 to 0.20111205-2.2): 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)
• diod/riscv64 (1.0.24-5.1 to 1.0.24-5.1)
  • Migration status for diod/riscv64 (1.0.24-5.1 to 1.0.24-5.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)
• directvnc/riscv64 (0.7.8-1 to 0.7.8-1)
  • Migration status for directvnc/riscv64 (0.7.8-1 to 0.7.8-1): Will attempt migration (Any information below is purely informational)
• direwolf/riscv64 (1.7+dfsg-2 to 1.7+dfsg-2)
  • Migration status for direwolf/riscv64 (1.7+dfsg-2 to 1.7+dfsg-2): Will attempt migration (Any information below is purely informational)
• discord-rpc/riscv64 (3.4.0-1 to 3.4.0-1)
  • Migration status for discord-rpc/riscv64 (3.4.0-1 to 3.4.0-1): Will attempt migration (Any information below is purely informational)
• discosnp/riscv64 (1:2.6.2-3 to 1:2.6.2-3)
  • Migration status for discosnp/riscv64 (1:2.6.2-3 to 1:2.6.2-3): Will attempt migration (Any information below is purely informational)
• dislocker/riscv64 (0.7.3-3.1 to 0.7.3-3.1)
  • Migration status for dislocker/riscv64 (0.7.3-3.1 to 0.7.3-3.1): Will attempt migration (Any information below is purely informational)
• disorderfs/riscv64 (0.5.11-3 to 0.5.11-3)
  • Migration status for disorderfs/riscv64 (0.5.11-3 to 0.5.11-3): Will attempt migration (Any information below is purely informational)
• distcc/riscv64 (3.4+really3.4-4 to 3.4+really3.4-4)
  • Migration status for distcc/riscv64 (3.4+really3.4-4 to 3.4+really3.4-4): Will attempt migration (Any information below is purely informational)
• disulfinder/riscv64 (1.2.11-12 to 1.2.11-12)
  • Migration status for disulfinder/riscv64 (1.2.11-12 to 1.2.11-12): Will attempt migration (Any information below is purely informational)
• 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)
• djvulibre/riscv64 (3.5.28-2 to 3.5.28-2)
  • Migration status for djvulibre/riscv64 (3.5.28-2 to 3.5.28-2): Will attempt migration (Any information below is purely informational)
• dleyna/riscv64 (0.8.3-1 to 0.8.3-1)
  • Migration status for dleyna/riscv64 (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• dlt-viewer/riscv64 (2.25.0+dfsg-2 to 2.25.0+dfsg-2)
  • Migration status for dlt-viewer/riscv64 (2.25.0+dfsg-2 to 2.25.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• dm-tree/riscv64 (0.1.8-3 to 0.1.8-3)
  • Migration status for dm-tree/riscv64 (0.1.8-3 to 0.1.8-3): Will attempt migration (Any information below is purely informational)
• dmlc-core/riscv64 (0.5-1.1 to 0.5-1.1)
  • Migration status for dmlc-core/riscv64 (0.5-1.1 to 0.5-1.1): Will attempt migration (Any information below is purely informational)
• dmrgpp/riscv64 (6.06-2 to 6.06-2)
  • Migration status for dmrgpp/riscv64 (6.06-2 to 6.06-2): Will attempt migration (Any information below is purely informational)
• 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)
• dmucs/riscv64 (0.6.1+dfsg-1 to 0.6.1+dfsg-1)
  • Migration status for dmucs/riscv64 (0.6.1+dfsg-1 to 0.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• dnaclust/riscv64 (3-7 to 3-7)
  • Migration status for dnaclust/riscv64 (3-7 to 3-7): Will attempt migration (Any information below is purely informational)
• 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)
• docopt.cpp/riscv64 (0.6.3-4 to 0.6.3-4)
  • Migration status for docopt.cpp/riscv64 (0.6.3-4 to 0.6.3-4): Will attempt migration (Any information below is purely informational)
• 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)
• dose3/amd64 (7.0.0-5 to 7.0.0-5)
  • Migration status for dose3/amd64 (7.0.0-5 to 7.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dose3/amd64 camlzip (not considered)
    • Invalidated by dependency
• dose3/arm64 (7.0.0-5 to 7.0.0-5)
  • Migration status for dose3/arm64 (7.0.0-5 to 7.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dose3/arm64 camlzip (not considered)
    • Invalidated by dependency
• dose3/armel (7.0.0-5 to 7.0.0-5)
  • Migration status for dose3/armel (7.0.0-5 to 7.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dose3/armel camlzip (not considered)
    • Invalidated by dependency
• dose3/armhf (7.0.0-5 to 7.0.0-5)
  • Migration status for dose3/armhf (7.0.0-5 to 7.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dose3/armhf camlzip (not considered)
    • Invalidated by dependency
• dose3/i386 (7.0.0-5 to 7.0.0-5)
  • Migration status for dose3/i386 (7.0.0-5 to 7.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dose3/i386 camlzip (not considered)
    • Invalidated by dependency
• dose3/mips64el (7.0.0-5 to 7.0.0-5)
  • Migration status for dose3/mips64el (7.0.0-5 to 7.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dose3/mips64el camlzip (not considered)
    • Invalidated by dependency
• dose3/ppc64el (7.0.0-5 to 7.0.0-5)
  • Migration status for dose3/ppc64el (7.0.0-5 to 7.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dose3/ppc64el camlzip (not considered)
    • Invalidated by dependency
• dose3/riscv64 (7.0.0-5 to 7.0.0-5)
  • Migration status for dose3/riscv64 (7.0.0-5 to 7.0.0-5): Will attempt migration (Any information below is purely informational)
• dose3/s390x (7.0.0-5 to 7.0.0-5)
  • Migration status for dose3/s390x (7.0.0-5 to 7.0.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: dose3/s390x camlzip (not considered)
    • Invalidated by dependency
• dossizola/riscv64 (1.0-12 to 1.0-12)
  • Migration status for dossizola/riscv64 (1.0-12 to 1.0-12): Will attempt migration (Any information below is purely informational)
• double-conversion/riscv64 (3.3.0-1 to 3.3.0-1)
  • Migration status for double-conversion/riscv64 (3.3.0-1 to 3.3.0-1): Will attempt migration (Any information below is purely informational)
• dovecot/riscv64 (1:2.3.21+dfsg1-3 to 1:2.3.21+dfsg1-3)
  • Migration status for dovecot/riscv64 (1:2.3.21+dfsg1-3 to 1:2.3.21+dfsg1-3): 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)
• dpaste/riscv64 (0.4.0-1 to 0.4.0-1)
  • Migration status for dpaste/riscv64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• dpf-plugins/riscv64 (1.7+ds-2 to 1.7+ds-2)
  • Migration status for dpf-plugins/riscv64 (1.7+ds-2 to 1.7+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)
• draco/riscv64 (1.5.6+dfsg-3 to 1.5.6+dfsg-3)
  • Migration status for draco/riscv64 (1.5.6+dfsg-3 to 1.5.6+dfsg-3): 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)
• drc/riscv64 (3.2.3~dfsg0-1 to 3.2.3~dfsg0-1)
  • Migration status for drc/riscv64 (3.2.3~dfsg0-1 to 3.2.3~dfsg0-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)
• drs4eb/riscv64 (5.0.6+git20211217+ds-3 to 5.0.6+git20211217+ds-3)
  • Migration status for drs4eb/riscv64 (5.0.6+git20211217+ds-3 to 5.0.6+git20211217+ds-3): Will attempt migration (Any information below is purely informational)
• drumgizmo/riscv64 (0.9.20-3 to 0.9.20-3)
  • Migration status for drumgizmo/riscv64 (0.9.20-3 to 0.9.20-3): Will attempt migration (Any information below is purely informational)
• drumkv1/riscv64 (0.9.90-1 to 0.9.90-1)
  • Migration status for drumkv1/riscv64 (0.9.90-1 to 0.9.90-1): Will attempt migration (Any information below is purely informational)
• dsda-doom/riscv64 (0.27.5+dfsg-1 to 0.27.5+dfsg-1)
  • Migration status for dsda-doom/riscv64 (0.27.5+dfsg-1 to 0.27.5+dfsg-1): Will attempt migration (Any information below is purely informational)
• dsdcc/riscv64 (1.9.3-2.1 to 1.9.3-2.1)
  • Migration status for dsdcc/riscv64 (1.9.3-2.1 to 1.9.3-2.1): Will attempt migration (Any information below is purely informational)
• dsdp/riscv64 (5.8-10.1 to 5.8-10.1)
  • Migration status for dsdp/riscv64 (5.8-10.1 to 5.8-10.1): 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)
• dssi/riscv64 (1.1.1~dfsg0-5 to 1.1.1~dfsg0-5)
  • Migration status for dssi/riscv64 (1.1.1~dfsg0-5 to 1.1.1~dfsg0-5): Will attempt migration (Any information below is purely informational)
• dssp/riscv64 (4.2.2-2 to 4.2.2-2)
  • Migration status for dssp/riscv64 (4.2.2-2 to 4.2.2-2): 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)
• dublin-traceroute/riscv64 (0.4.2-3 to 0.4.2-3)
  • Migration status for dublin-traceroute/riscv64 (0.4.2-3 to 0.4.2-3): Will attempt migration (Any information below is purely informational)
• duc/riscv64 (1.4.5-1 to 1.4.5-1)
  • Migration status for duc/riscv64 (1.4.5-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
• duma/riscv64 (2.5.21-8 to 2.5.21-8)
  • Migration status for duma/riscv64 (2.5.21-8 to 2.5.21-8): Will attempt migration (Any information below is purely informational)
• 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)
• duplicity/riscv64 (2.1.4-3 to 2.1.4-3)
  • Migration status for duplicity/riscv64 (2.1.4-3 to 2.1.4-3): Will attempt migration (Any information below is purely informational)
• dustmite/riscv64 (0.0.430-2.1 to 0.0.430-2.1)
  • Migration status for dustmite/riscv64 (0.0.430-2.1 to 0.0.430-2.1): 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)
• dvbcut/riscv64 (0.7.4-1 to 0.7.4-1)
  • Migration status for dvbcut/riscv64 (0.7.4-1 to 0.7.4-1): 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)
• dvd+rw-tools/riscv64 (7.1-14 to 7.1-14)
  • Migration status for dvd+rw-tools/riscv64 (7.1-14 to 7.1-14): 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)
• dvipng/riscv64 (1.15-1.1 to 1.15-1.1)
  • Migration status for dvipng/riscv64 (1.15-1.1 to 1.15-1.1): Will attempt migration (Any information below is purely informational)
• dvisvgm/riscv64 (3.3+ds-1 to 3.3+ds-1)
  • Migration status for dvisvgm/riscv64 (3.3+ds-1 to 3.3+ds-1): Will attempt migration (Any information below is purely informational)
• dwarf2sources/riscv64 (0.2.4-1 to 0.2.4-1)
  • Migration status for dwarf2sources/riscv64 (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
• dwdiff/riscv64 (2.1.4-2 to 2.1.4-2)
  • Migration status for dwdiff/riscv64 (2.1.4-2 to 2.1.4-2): Will attempt migration (Any information below is purely informational)
• dwww/riscv64 (1.16 to 1.16)
  • Migration status for dwww/riscv64 (1.16 to 1.16): Will attempt migration (Any information below is purely informational)
• dx/riscv64 (1:4.4.4-16 to 1:4.4.4-16)
  • Migration status for dx/riscv64 (1:4.4.4-16 to 1:4.4.4-16): Will attempt migration (Any information below is purely informational)
• dxflib/riscv64 (3.26.4-1 to 3.26.4-1)
  • Migration status for dxflib/riscv64 (3.26.4-1 to 3.26.4-1): Will attempt migration (Any information below is purely informational)
• dymo-cups-drivers/riscv64 (1.4.0-12 to 1.4.0-12)
  • Migration status for dymo-cups-drivers/riscv64 (1.4.0-12 to 1.4.0-12): 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)
• e-antic/riscv64 (2.0.2+ds-2 to 2.0.2+ds-2)
  • Migration status for e-antic/riscv64 (2.0.2+ds-2 to 2.0.2+ds-2): Will attempt migration (Any information below is purely informational)
• e-mem/riscv64 (1.0.1-5 to 1.0.1-5)
  • Migration status for e-mem/riscv64 (1.0.1-5 to 1.0.1-5): 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)
• eancheck/riscv64 (1.0-3 to 1.0-3)
  • Migration status for eancheck/riscv64 (1.0-3 to 1.0-3): 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)
• 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)
• ebumeter/riscv64 (0.5.1-1 to 0.5.1-1)
  • Migration status for ebumeter/riscv64 (0.5.1-1 to 0.5.1-1): Will attempt migration (Any information below is purely informational)
• ecasound/riscv64 (2.9.3-4 to 2.9.3-4)
  • Migration status for ecasound/riscv64 (2.9.3-4 to 2.9.3-4): 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)
• ecl/riscv64 (21.2.1+ds-4.1 to 21.2.1+ds-4.1)
  • Migration status for ecl/riscv64 (21.2.1+ds-4.1 to 21.2.1+ds-4.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)
• ectrans/riscv64 (1.3.2-1 to 1.3.2-1)
  • Migration status for ectrans/riscv64 (1.3.2-1 to 1.3.2-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)
• edgar/riscv64 (1.37-1 to 1.37-1)
  • Migration status for edgar/riscv64 (1.37-1 to 1.37-1): Will attempt migration (Any information below is purely informational)
• edid-decode/riscv64 (0.1~git20220315.cb74358c2896-1.1 to 0.1~git20220315.cb74358c2896-1.1)
  • Migration status for edid-decode/riscv64 (0.1~git20220315.cb74358c2896-1.1 to 0.1~git20220315.cb74358c2896-1.1): Will attempt migration (Any information below is purely informational)
• edtsurf/riscv64 (0.2009-10 to 0.2009-10)
  • Migration status for edtsurf/riscv64 (0.2009-10 to 0.2009-10): Will attempt migration (Any information below is purely informational)
• efte/riscv64 (1.1-4 to 1.1-4)
  • Migration status for efte/riscv64 (1.1-4 to 1.1-4): Will attempt migration (Any information below is purely informational)
• eg25-manager/riscv64 (0.4.6-3 to 0.4.6-3)
  • Migration status for eg25-manager/riscv64 (0.4.6-3 to 0.4.6-3): Will attempt migration (Any information below is purely informational)
• eiciel/riscv64 (0.10.0-1 to 0.10.0-1)
  • Migration status for eiciel/riscv64 (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• eigensoft/riscv64 (8.0.0+dfsg-2 to 8.0.0+dfsg-2)
  • Migration status for eigensoft/riscv64 (8.0.0+dfsg-2 to 8.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• 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)
• ekeyd/riscv64 (1.1.5-6.3 to 1.1.5-6.3)
  • Migration status for ekeyd/riscv64 (1.1.5-6.3 to 1.1.5-6.3): 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)
• eliom/amd64 (10.4.1-1 to 10.4.1-1)
  • Migration status for eliom/amd64 (10.4.1-1 to 10.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/amd64 ocamlbuild (not considered)
    • Invalidated by dependency
    • Depends: eliom/amd64 js-of-ocaml-ocamlbuild/amd64
• eliom/arm64 (10.4.1-1 to 10.4.1-1)
  • Migration status for eliom/arm64 (10.4.1-1 to 10.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/arm64 ocamlbuild (not considered)
    • Invalidated by dependency
    • Depends: eliom/arm64 js-of-ocaml-ocamlbuild/arm64
• eliom/armel (10.4.1-1 to 10.4.1-1)
  • Migration status for eliom/armel (10.4.1-1 to 10.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/armel ocamlbuild (not considered)
    • Invalidated by dependency
• eliom/armhf (10.4.1-1 to 10.4.1-1)
  • Migration status for eliom/armhf (10.4.1-1 to 10.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/armhf ocamlbuild (not considered)
    • Invalidated by dependency
    • Depends: eliom/armhf js-of-ocaml-ocamlbuild/armhf
• eliom/i386 (10.4.1-1 to 10.4.1-1)
  • Migration status for eliom/i386 (10.4.1-1 to 10.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/i386 ocamlbuild (not considered)
    • Invalidated by dependency
    • Depends: eliom/i386 js-of-ocaml-ocamlbuild/i386
• eliom/mips64el (10.4.1-1 to 10.4.1-1)
  • Migration status for eliom/mips64el (10.4.1-1 to 10.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/mips64el ocamlbuild (not considered)
    • Invalidated by dependency
• eliom/ppc64el (10.4.1-1 to 10.4.1-1)
  • Migration status for eliom/ppc64el (10.4.1-1 to 10.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/ppc64el ocamlbuild (not considered)
    • Invalidated by dependency
    • Depends: eliom/ppc64el js-of-ocaml-ocamlbuild/ppc64el
• eliom/riscv64 (10.4.1-1 to 10.4.1-1)
  • Migration status for eliom/riscv64 (10.4.1-1 to 10.4.1-1): Will attempt migration (Any information below is purely informational)
• eliom/s390x (10.4.1-1 to 10.4.1-1)
  • Migration status for eliom/s390x (10.4.1-1 to 10.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: eliom/s390x ocamlbuild (not considered)
    • Invalidated by dependency
    • Depends: eliom/s390x js-of-ocaml-ocamlbuild/s390x
• elixir-lang/riscv64 (1.14.0.dfsg-2 to 1.14.0.dfsg-2)
  • Migration status for elixir-lang/riscv64 (1.14.0.dfsg-2 to 1.14.0.dfsg-2): Will attempt migration (Any information below is purely informational)
• elixir-makeup-c/riscv64 (0.1.1-3 to 0.1.1-3)
  • Migration status for elixir-makeup-c/riscv64 (0.1.1-3 to 0.1.1-3): Will attempt migration (Any information below is purely informational)
• elixir-makeup-elixir/riscv64 (0.16.2-1 to 0.16.2-1)
  • Migration status for elixir-makeup-elixir/riscv64 (0.16.2-1 to 0.16.2-1): Will attempt migration (Any information below is purely informational)
• elixir-nimble-parsec/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for elixir-nimble-parsec/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• elph/riscv64 (1.0.1-5 to 1.0.1-5)
  • Migration status for elph/riscv64 (1.0.1-5 to 1.0.1-5): Will attempt migration (Any information below is purely informational)
• emacs-pdf-tools/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for emacs-pdf-tools/riscv64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• emacs_pu (1:29.4+1-3 to 1:28.2+1-15+deb12u3)
  • Migration status for emacs_pu (1:29.4+1-3 to 1:28.2+1-15+deb12u3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: emacs is newer in the target suite (1:29.4+1-3 1:28.2+1-15+deb12u3)
• 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)
• emacspeak/riscv64 (53.0+dfsg-3 to 53.0+dfsg-3)
  • Migration status for emacspeak/riscv64 (53.0+dfsg-3 to 53.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• embassy-domainatrix/riscv64 (0.1.660-5 to 0.1.660-5)
  • Migration status for embassy-domainatrix/riscv64 (0.1.660-5 to 0.1.660-5): Will attempt migration (Any information below is purely informational)
• embassy-domalign/riscv64 (0.1.660-5 to 0.1.660-5)
  • Migration status for embassy-domalign/riscv64 (0.1.660-5 to 0.1.660-5): Will attempt migration (Any information below is purely informational)
• embassy-domsearch/riscv64 (1:0.1.660-4 to 1:0.1.660-4)
  • Migration status for embassy-domsearch/riscv64 (1:0.1.660-4 to 1:0.1.660-4): Will attempt migration (Any information below is purely informational)
• emboss/riscv64 (6.6.0+dfsg-15 to 6.6.0+dfsg-15)
  • Migration status for emboss/riscv64 (6.6.0+dfsg-15 to 6.6.0+dfsg-15): Will attempt migration (Any information below is purely informational)
• 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)
• emmax/riscv64 (0~beta.20100307-5 to 0~beta.20100307-5)
  • Migration status for emmax/riscv64 (0~beta.20100307-5 to 0~beta.20100307-5): Will attempt migration (Any information below is purely informational)
• emms/riscv64 (5.1-1 to 5.1-1)
  • Migration status for emms/riscv64 (5.1-1 to 5.1-1): 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)
• enblend-enfuse/riscv64 (4.2-10 to 4.2-10)
  • Migration status for enblend-enfuse/riscv64 (4.2-10 to 4.2-10): Will attempt migration (Any information below is purely informational)
• encfs/riscv64 (1.9.5-2 to 1.9.5-2)
  • Migration status for encfs/riscv64 (1.9.5-2 to 1.9.5-2): Will attempt migration (Any information below is purely informational)
• enchant-2/riscv64 (2.3.3-2 to 2.3.3-2)
  • Migration status for enchant-2/riscv64 (2.3.3-2 to 2.3.3-2): Will attempt migration (Any information below is purely informational)
• 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)
• enigma/riscv64 (1.30+dfsg-1 to 1.30+dfsg-1)
  • Migration status for enigma/riscv64 (1.30+dfsg-1 to 1.30+dfsg-1): 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)
• enscribe/riscv64 (0.1.0-5 to 0.1.0-5)
  • Migration status for enscribe/riscv64 (0.1.0-5 to 0.1.0-5): Will attempt migration (Any information below is purely informational)
• ensmallen/riscv64 (2.21.1-1 to 2.21.1-1)
  • Migration status for ensmallen/riscv64 (2.21.1-1 to 2.21.1-1): 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)
• eog/riscv64 (45.3-1 to 45.3-1)
  • Migration status for eog/riscv64 (45.3-1 to 45.3-1): 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)
• epcr/riscv64 (2.3.12-1-9 to 2.3.12-1-9)
  • Migration status for epcr/riscv64 (2.3.12-1-9 to 2.3.12-1-9): 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)
• epiphany/riscv64 (0.7.0+0-7 to 0.7.0+0-7)
  • Migration status for epiphany/riscv64 (0.7.0+0-7 to 0.7.0+0-7): 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)
• epm/riscv64 (4.2-12 to 4.2-12)
  • Migration status for epm/riscv64 (4.2-12 to 4.2-12): Will attempt migration (Any information below is purely informational)
• epstool/riscv64 (3.09-4 to 3.09-4)
  • Migration status for epstool/riscv64 (3.09-4 to 3.09-4): Will attempt migration (Any information below is purely informational)
• eq10q/riscv64 (2.2~repack0-5 to 2.2~repack0-5)
  • Migration status for eq10q/riscv64 (2.2~repack0-5 to 2.2~repack0-5): Will attempt migration (Any information below is purely informational)
• equalx/riscv64 (0.7.1-4.1 to 0.7.1-4.1)
  • Migration status for equalx/riscv64 (0.7.1-4.1 to 0.7.1-4.1): Will attempt migration (Any information below is purely informational)
• erlang-asciideck/riscv64 (0.0+git20170714.48cbfe8b-4 to 0.0+git20170714.48cbfe8b-4)
  • Migration status for erlang-asciideck/riscv64 (0.0+git20170714.48cbfe8b-4 to 0.0+git20170714.48cbfe8b-4): Will attempt migration (Any information below is purely informational)
• erlang-base64url/riscv64 (1.0.1-8 to 1.0.1-8)
  • Migration status for erlang-base64url/riscv64 (1.0.1-8 to 1.0.1-8): Will attempt migration (Any information below is purely informational)
• erlang-bbmustache/riscv64 (1.6.1+dfsg-1 to 1.6.1+dfsg-1)
  • Migration status for erlang-bbmustache/riscv64 (1.6.1+dfsg-1 to 1.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• erlang-bitcask/riscv64 (2.1.0-2 to 2.1.0-2)
  • Migration status for erlang-bitcask/riscv64 (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
• erlang-cf/riscv64 (0.3.1-1 to 0.3.1-1)
  • Migration status for erlang-cf/riscv64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• erlang-cl/riscv64 (1.2.4-1 to 1.2.4-1)
  • Migration status for erlang-cl/riscv64 (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
• erlang-cowlib/riscv64 (1.3.0-3 to 1.3.0-3)
  • Migration status for erlang-cowlib/riscv64 (1.3.0-3 to 1.3.0-3): Will attempt migration (Any information below is purely informational)
• erlang-erlware-commons/riscv64 (1.6.0+dfsg-1 to 1.6.0+dfsg-1)
  • Migration status for erlang-erlware-commons/riscv64 (1.6.0+dfsg-1 to 1.6.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• erlang-getopt/riscv64 (1.0.2-1 to 1.0.2-1)
  • Migration status for erlang-getopt/riscv64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• erlang-goldrush/riscv64 (0.2.0-9 to 0.2.0-9)
  • Migration status for erlang-goldrush/riscv64 (0.2.0-9 to 0.2.0-9): Will attempt migration (Any information below is purely informational)
• erlang-horse/riscv64 (0+git20161117.0.4dc81d4-1 to 0+git20161117.0.4dc81d4-1)
  • Migration status for erlang-horse/riscv64 (0+git20161117.0.4dc81d4-1 to 0+git20161117.0.4dc81d4-1): Will attempt migration (Any information below is purely informational)
• erlang-idna/riscv64 (6.1.1-5 to 6.1.1-5)
  • Migration status for erlang-idna/riscv64 (6.1.1-5 to 6.1.1-5): Will attempt migration (Any information below is purely informational)
• erlang-jiffy/riscv64 (1.1.1-2 to 1.1.1-2)
  • Migration status for erlang-jiffy/riscv64 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• erlang-jose/riscv64 (1.11.6-1 to 1.11.6-1)
  • Migration status for erlang-jose/riscv64 (1.11.6-1 to 1.11.6-1): Will attempt migration (Any information below is purely informational)
• erlang-lager/riscv64 (3.9.2-3 to 3.9.2-3)
  • Migration status for erlang-lager/riscv64 (3.9.2-3 to 3.9.2-3): Will attempt migration (Any information below is purely informational)
• erlang-luerl/riscv64 (1:1.1-1 to 1:1.1-1)
  • Migration status for erlang-luerl/riscv64 (1:1.1-1 to 1:1.1-1): Will attempt migration (Any information below is purely informational)
• erlang-metrics/riscv64 (2.5.0-2 to 2.5.0-2)
  • Migration status for erlang-metrics/riscv64 (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• erlang-p1-acme/riscv64 (1.0.22-2 to 1.0.22-2)
  • Migration status for erlang-p1-acme/riscv64 (1.0.22-2 to 1.0.22-2): Will attempt migration (Any information below is purely informational)
• erlang-p1-cache-tab/riscv64 (1.0.30-3 to 1.0.30-3)
  • Migration status for erlang-p1-cache-tab/riscv64 (1.0.30-3 to 1.0.30-3): Will attempt migration (Any information below is purely informational)
• erlang-p1-eimp/riscv64 (1.0.22-3 to 1.0.22-3)
  • Migration status for erlang-p1-eimp/riscv64 (1.0.22-3 to 1.0.22-3): Will attempt migration (Any information below is purely informational)
• erlang-p1-iconv/riscv64 (1.0.13-4 to 1.0.13-4)
  • Migration status for erlang-p1-iconv/riscv64 (1.0.13-4 to 1.0.13-4): Will attempt migration (Any information below is purely informational)
• erlang-p1-mqtree/riscv64 (1.0.15-3 to 1.0.15-3)
  • Migration status for erlang-p1-mqtree/riscv64 (1.0.15-3 to 1.0.15-3): Will attempt migration (Any information below is purely informational)
• erlang-p1-mysql/riscv64 (1.0.22-1 to 1.0.22-1)
  • Migration status for erlang-p1-mysql/riscv64 (1.0.22-1 to 1.0.22-1): Will attempt migration (Any information below is purely informational)
• erlang-p1-oauth2/riscv64 (0.6.11-3 to 0.6.11-3)
  • Migration status for erlang-p1-oauth2/riscv64 (0.6.11-3 to 0.6.11-3): Will attempt migration (Any information below is purely informational)
• erlang-p1-pam/riscv64 (1.0.14-2 to 1.0.14-2)
  • Migration status for erlang-p1-pam/riscv64 (1.0.14-2 to 1.0.14-2): Will attempt migration (Any information below is purely informational)
• erlang-p1-pkix/riscv64 (1.0.9-3 to 1.0.9-3)
  • Migration status for erlang-p1-pkix/riscv64 (1.0.9-3 to 1.0.9-3): Will attempt migration (Any information below is purely informational)
• erlang-p1-sip/riscv64 (1.0.50-1 to 1.0.50-1)
  • Migration status for erlang-p1-sip/riscv64 (1.0.50-1 to 1.0.50-1): Will attempt migration (Any information below is purely informational)
• erlang-p1-sqlite3/riscv64 (1.1.14-2 to 1.1.14-2)
  • Migration status for erlang-p1-sqlite3/riscv64 (1.1.14-2 to 1.1.14-2): Will attempt migration (Any information below is purely informational)
• erlang-p1-stringprep/riscv64 (1.0.29-3 to 1.0.29-3)
  • Migration status for erlang-p1-stringprep/riscv64 (1.0.29-3 to 1.0.29-3): Will attempt migration (Any information below is purely informational)
• erlang-p1-stun/riscv64 (1.2.10-1 to 1.2.10-1)
  • Migration status for erlang-p1-stun/riscv64 (1.2.10-1 to 1.2.10-1): Will attempt migration (Any information below is purely informational)
• erlang-p1-tls/riscv64 (1.1.16-3 to 1.1.16-3)
  • Migration status for erlang-p1-tls/riscv64 (1.1.16-3 to 1.1.16-3): Will attempt migration (Any information below is purely informational)
• erlang-p1-utils/riscv64 (1.0.25-3 to 1.0.25-3)
  • Migration status for erlang-p1-utils/riscv64 (1.0.25-3 to 1.0.25-3): Will attempt migration (Any information below is purely informational)
• erlang-p1-yaml/riscv64 (1.0.36-2 to 1.0.36-2)
  • Migration status for erlang-p1-yaml/riscv64 (1.0.36-2 to 1.0.36-2): Will attempt migration (Any information below is purely informational)
• erlang-p1-yconf/riscv64 (1.0.15-2 to 1.0.15-2)
  • Migration status for erlang-p1-yconf/riscv64 (1.0.15-2 to 1.0.15-2): Will attempt migration (Any information below is purely informational)
• erlang-p1-zlib/riscv64 (1.0.12-3 to 1.0.12-3)
  • Migration status for erlang-p1-zlib/riscv64 (1.0.12-3 to 1.0.12-3): Will attempt migration (Any information below is purely informational)
• erlang-proper/riscv64 (1.2+git988ea0ed9f+dfsg-2.1 to 1.2+git988ea0ed9f+dfsg-2.1)
  • Migration status for erlang-proper/riscv64 (1.2+git988ea0ed9f+dfsg-2.1 to 1.2+git988ea0ed9f+dfsg-2.1): Will attempt migration (Any information below is purely informational)
• erlang-redis-client/riscv64 (1.2.0-7 to 1.2.0-7)
  • Migration status for erlang-redis-client/riscv64 (1.2.0-7 to 1.2.0-7): Will attempt migration (Any information below is purely informational)
• erlang-unicode-util-compat/riscv64 (0.7.0-5 to 0.7.0-5)
  • Migration status for erlang-unicode-util-compat/riscv64 (0.7.0-5 to 0.7.0-5): Will attempt migration (Any information below is purely informational)
• erlang-uuid/riscv64 (0.4.6-2 to 0.4.6-2)
  • Migration status for erlang-uuid/riscv64 (0.4.6-2 to 0.4.6-2): Will attempt migration (Any information below is purely informational)
• erlang/riscv64 (1:25.3.2.12+dfsg-1 to 1:25.3.2.12+dfsg-1)
  • Migration status for erlang/riscv64 (1:25.3.2.12+dfsg-1 to 1:25.3.2.12+dfsg-1): Will attempt migration (Any information below is purely informational)
• esnacc/riscv64 (1.8.1-4 to 1.8.1-4)
  • Migration status for esnacc/riscv64 (1.8.1-4 to 1.8.1-4): Will attempt migration (Any information below is purely informational)
• eso-midas/riscv64 (23.02pl1.0-2 to 23.02pl1.0-2)
  • Migration status for eso-midas/riscv64 (23.02pl1.0-2 to 23.02pl1.0-2): Will attempt migration (Any information below is purely informational)
• esorex/riscv64 (3.13.7+ds-1 to 3.13.7+ds-1)
  • Migration status for esorex/riscv64 (3.13.7+ds-1 to 3.13.7+ds-1): 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)
• espresso/riscv64 (6.7-2 to 6.7-2)
  • Migration status for espresso/riscv64 (6.7-2 to 6.7-2): Will attempt migration (Any information below is purely informational)
• estscan/riscv64 (3.0.3-6 to 3.0.3-6)
  • Migration status for estscan/riscv64 (3.0.3-6 to 3.0.3-6): 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)
• etherape/riscv64 (0.9.20-2 to 0.9.20-2)
  • Migration status for etherape/riscv64 (0.9.20-2 to 0.9.20-2): Will attempt migration (Any information below is purely informational)
• 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)
• eureka/riscv64 (1.27b-2 to 1.27b-2)
  • Migration status for eureka/riscv64 (1.27b-2 to 1.27b-2): 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)
• exactimage/riscv64 (1.0.2-11 to 1.0.2-11)
  • Migration status for exactimage/riscv64 (1.0.2-11 to 1.0.2-11): 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)
• exempi/riscv64 (2.6.5-1 to 2.6.5-1)
  • Migration status for exempi/riscv64 (2.6.5-1 to 2.6.5-1): Will attempt migration (Any information below is purely informational)
• exim4_pu (4.98-1 to 4.96-15+deb12u5)
  • Migration status for exim4_pu (4.98-1 to 4.96-15+deb12u5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: exim4 is newer in the target suite (4.98-1 4.96-15+deb12u5)
• exiv2/riscv64 (0.27.6-1 to 0.27.6-1)
  • Migration status for exiv2/riscv64 (0.27.6-1 to 0.27.6-1): 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)
• ext3grep/riscv64 (0.10.2-5 to 0.10.2-5)
  • Migration status for ext3grep/riscv64 (0.10.2-5 to 0.10.2-5): Will attempt migration (Any information below is purely informational)
• extinction/riscv64 (0.4.6-3 to 0.4.6-3)
  • Migration status for extinction/riscv64 (0.4.6-3 to 0.4.6-3): Will attempt migration (Any information below is purely informational)
• extra-window-functions/riscv64 (1.0-5 to 1.0-5)
  • Migration status for extra-window-functions/riscv64 (1.0-5 to 1.0-5): Will attempt migration (Any information below is purely informational)
• extractpdfmark/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for extractpdfmark/riscv64 (1.1.1-1 to 1.1.1-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)
• extundelete/riscv64 (0.2.4-3 to 0.2.4-3)
  • Migration status for extundelete/riscv64 (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
• exult/riscv64 (1.8-2 to 1.8-2)
  • Migration status for exult/riscv64 (1.8-2 to 1.8-2): 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)
• f3d/riscv64 (2.4.0+dfsg-2 to 2.4.0+dfsg-2)
  • Migration status for f3d/riscv64 (2.4.0+dfsg-2 to 2.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• fabulous/riscv64 (0.4.0+dfsg1-1 to 0.4.0+dfsg1-1)
  • Migration status for fabulous/riscv64 (0.4.0+dfsg1-1 to 0.4.0+dfsg1-1): 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)
• fact++/riscv64 (1.6.5~dfsg-3 to 1.6.5~dfsg-3)
  • Migration status for fact++/riscv64 (1.6.5~dfsg-3 to 1.6.5~dfsg-3): Will attempt migration (Any information below is purely informational)
• fairy-stockfish/riscv64 (11.1-1 to 11.1-1)
  • Migration status for fairy-stockfish/riscv64 (11.1-1 to 11.1-1): Will attempt migration (Any information below is purely informational)
• faiss/riscv64 (1.8.0-5 to 1.8.0-5)
  • Migration status for faiss/riscv64 (1.8.0-5 to 1.8.0-5): Will attempt migration (Any information below is purely informational)
• far2l/riscv64 (2.6.1~beta+ds-1 to 2.6.1~beta+ds-1)
  • Migration status for far2l/riscv64 (2.6.1~beta+ds-1 to 2.6.1~beta+ds-1): 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)
• fast-histogram/riscv64 (0.11-2 to 0.11-2)
  • Migration status for fast-histogram/riscv64 (0.11-2 to 0.11-2): Will attempt migration (Any information below is purely informational)
• fast5/riscv64 (0.6.5-7 to 0.6.5-7)
  • Migration status for fast5/riscv64 (0.6.5-7 to 0.6.5-7): Will attempt migration (Any information below is purely informational)
• fastani/riscv64 (1.33-3 to 1.33-3)
  • Migration status for fastani/riscv64 (1.33-3 to 1.33-3): Will attempt migration (Any information below is purely informational)
• fastchunking/riscv64 (0.0.3-4 to 0.0.3-4)
  • Migration status for fastchunking/riscv64 (0.0.3-4 to 0.0.3-4): Will attempt migration (Any information below is purely informational)
• fastdtw/riscv64 (0.3.4-3 to 0.3.4-3)
  • Migration status for fastdtw/riscv64 (0.3.4-3 to 0.3.4-3): Will attempt migration (Any information below is purely informational)
• fastjet/riscv64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/riscv64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• fastml/riscv64 (3.11-4 to 3.11-4)
  • Migration status for fastml/riscv64 (3.11-4 to 3.11-4): Will attempt migration (Any information below is purely informational)
• fastp/riscv64 (0.23.4+dfsg-1 to 0.23.4+dfsg-1)
  • Migration status for fastp/riscv64 (0.23.4+dfsg-1 to 0.23.4+dfsg-1): Will attempt migration (Any information below is purely informational)
• fastqtl/riscv64 (2.184+v7+dfsg-4 to 2.184+v7+dfsg-4)
  • Migration status for fastqtl/riscv64 (2.184+v7+dfsg-4 to 2.184+v7+dfsg-4): Will attempt migration (Any information below is purely informational)
• fasttext/riscv64 (0.9.2+ds-7 to 0.9.2+ds-7)
  • Migration status for fasttext/riscv64 (0.9.2+ds-7 to 0.9.2+ds-7): Will attempt migration (Any information below is purely informational)
• fasttree/riscv64 (2.1.11-2 to 2.1.11-2)
  • Migration status for fasttree/riscv64 (2.1.11-2 to 2.1.11-2): Will attempt migration (Any information below is purely informational)
• fatcat/riscv64 (1.1.1-3 to 1.1.1-3)
  • Migration status for fatcat/riscv64 (1.1.1-3 to 1.1.1-3): Will attempt migration (Any information below is purely informational)
• faucc/riscv64 (20180503-1.1 to 20180503-1.1)
  • Migration status for faucc/riscv64 (20180503-1.1 to 20180503-1.1): Will attempt migration (Any information below is purely informational)
• fauhdlc/riscv64 (20180504-3.1 to 20180504-3.1)
  • Migration status for fauhdlc/riscv64 (20180504-3.1 to 20180504-3.1): Will attempt migration (Any information below is purely informational)
• faust/riscv64 (2.72.14+ds-1 to 2.72.14+ds-1)
  • Migration status for faust/riscv64 (2.72.14+ds-1 to 2.72.14+ds-1): 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)
• fbasics/riscv64 (4032.96-1 to 4032.96-1)
  • Migration status for fbasics/riscv64 (4032.96-1 to 4032.96-1): Will attempt migration (Any information below is purely informational)
• fbautostart/riscv64 (2.718281828-1 to 2.718281828-1)
  • Migration status for fbautostart/riscv64 (2.718281828-1 to 2.718281828-1): Will attempt migration (Any information below is purely informational)
• fbpager/riscv64 (0.1.5~git20090221.1.8e0927e6-3 to 0.1.5~git20090221.1.8e0927e6-3)
  • Migration status for fbpager/riscv64 (0.1.5~git20090221.1.8e0927e6-3 to 0.1.5~git20090221.1.8e0927e6-3): Will attempt migration (Any information below is purely informational)
• fbterm/riscv64 (1.7-5 to 1.7-5)
  • Migration status for fbterm/riscv64 (1.7-5 to 1.7-5): Will attempt migration (Any information below is purely informational)
• fbzx/riscv64 (4.8.0-2 to 4.8.0-2)
  • Migration status for fbzx/riscv64 (4.8.0-2 to 4.8.0-2): 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)
• fcft/riscv64 (3.1.8-1.1 to 3.1.8-1.1)
  • Migration status for fcft/riscv64 (3.1.8-1.1 to 3.1.8-1.1): Will attempt migration (Any information below is purely informational)
• 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-fbterm/riscv64 (0.2.0-5 to 0.2.0-5)
  • Migration status for fcitx-fbterm/riscv64 (0.2.0-5 to 0.2.0-5): 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-libpinyin/riscv64 (0.5.4-5 to 0.5.4-5)
  • Migration status for fcitx-libpinyin/riscv64 (0.5.4-5 to 0.5.4-5): 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-qt5/riscv64 (1.2.7-2 to 1.2.7-2)
  • Migration status for fcitx-qt5/riscv64 (1.2.7-2 to 1.2.7-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-sunpinyin/riscv64 (0.4.2-3 to 0.4.2-3)
  • Migration status for fcitx-sunpinyin/riscv64 (0.4.2-3 to 0.4.2-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-fbterm/riscv64 (0.0~git20220315.620980b-2 to 0.0~git20220315.620980b-2)
  • Migration status for fcitx5-fbterm/riscv64 (0.0~git20220315.620980b-2 to 0.0~git20220315.620980b-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-quwei/riscv64 (0.0~git20220225.aa4cf7c-1 to 0.0~git20220225.aa4cf7c-1)
  • Migration status for fcitx5-quwei/riscv64 (0.0~git20220225.aa4cf7c-1 to 0.0~git20220225.aa4cf7c-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)
• fcl/riscv64 (0.7.0-3 to 0.7.0-3)
  • Migration status for fcl/riscv64 (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
• fclib/riscv64 (3.1.0+dfsg-3 to 3.1.0+dfsg-3)
  • Migration status for fclib/riscv64 (3.1.0+dfsg-3 to 3.1.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• fcopulae/riscv64 (4022.85-1 to 4022.85-1)
  • Migration status for fcopulae/riscv64 (4022.85-1 to 4022.85-1): Will attempt migration (Any information below is purely informational)
• fdb/riscv64 (5.12.1-1 to 5.12.1-1)
  • Migration status for fdb/riscv64 (5.12.1-1 to 5.12.1-1): Will attempt migration (Any information below is purely informational)
• 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)
• feff85exafs/riscv64 (0.2+dfsg-2 to 0.2+dfsg-2)
  • Migration status for feff85exafs/riscv64 (0.2+dfsg-2 to 0.2+dfsg-2): 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)
• ferret-vis/riscv64 (7.6.0-7 to 7.6.0-7)
  • Migration status for ferret-vis/riscv64 (7.6.0-7 to 7.6.0-7): Will attempt migration (Any information below is purely informational)
• festival/riscv64 (1:2.5.0-10 to 1:2.5.0-10)
  • Migration status for festival/riscv64 (1:2.5.0-10 to 1:2.5.0-10): 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)
• 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)
• fflas-ffpack/riscv64 (2.5.0-3 to 2.5.0-3)
  • Migration status for fflas-ffpack/riscv64 (2.5.0-3 to 2.5.0-3): 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)
• fftw/riscv64 (2.1.5-6 to 2.1.5-6)
  • Migration status for fftw/riscv64 (2.1.5-6 to 2.1.5-6): Will attempt migration (Any information below is purely informational)
• fftw3/riscv64 (3.3.10-1 to 3.3.10-1)
  • Migration status for fftw3/riscv64 (3.3.10-1 to 3.3.10-1): Will attempt migration (Any information below is purely informational)
• fgarch/riscv64 (4033.92-1 to 4033.92-1)
  • Migration status for fgarch/riscv64 (4033.92-1 to 4033.92-1): Will attempt migration (Any information below is purely informational)
• 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)
• field3d/riscv64 (1.7.3-4.1 to 1.7.3-4.1)
  • Migration status for field3d/riscv64 (1.7.3-4.1 to 1.7.3-4.1): Will attempt migration (Any information below is purely informational)
• fieldslib/riscv64 (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for fieldslib/riscv64 (1:0.16.0-2 to 1:0.16.0-2): 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)
• fig2sxd/riscv64 (0.23-1 to 0.23-1)
  • Migration status for fig2sxd/riscv64 (0.23-1 to 0.23-1): Will attempt migration (Any information below is purely informational)
• fil-plugins/riscv64 (0.3.0-7 to 0.3.0-7)
  • Migration status for fil-plugins/riscv64 (0.3.0-7 to 0.3.0-7): 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)
• filtermail/riscv64 (1.05.00-1 to 1.05.00-1)
  • Migration status for filtermail/riscv64 (1.05.00-1 to 1.05.00-1): Will attempt migration (Any information below is purely informational)
• filtlong/riscv64 (0.2.1-4 to 0.2.1-4)
  • Migration status for filtlong/riscv64 (0.2.1-4 to 0.2.1-4): Will attempt migration (Any information below is purely informational)
• finalcut/riscv64 (0.9.0-2 to 0.9.0-2)
  • Migration status for finalcut/riscv64 (0.9.0-2 to 0.9.0-2): Will attempt migration (Any information below is purely informational)
• findent/riscv64 (4.3.2-1 to 4.3.2-1)
  • Migration status for findent/riscv64 (4.3.2-1 to 4.3.2-1): 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)
• fiona/riscv64 (1.9.6-1 to 1.9.6-1)
  • Migration status for fiona/riscv64 (1.9.6-1 to 1.9.6-1): Will attempt migration (Any information below is purely informational)
• firebuild/riscv64 (0.8.2-1 to 0.8.2-1)
  • Migration status for firebuild/riscv64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
• first-last-agg/riscv64 (0.1.4-4-gd63ea3b-7 to 0.1.4-4-gd63ea3b-7)
  • Migration status for first-last-agg/riscv64 (0.1.4-4-gd63ea3b-7 to 0.1.4-4-gd63ea3b-7): Will attempt migration (Any information below is purely informational)
• fische/riscv64 (3.2.2-7 to 3.2.2-7)
  • Migration status for fische/riscv64 (3.2.2-7 to 3.2.2-7): Will attempt migration (Any information below is purely informational)
• fish/riscv64 (3.7.1-1 to 3.7.1-1)
  • Migration status for fish/riscv64 (3.7.1-1 to 3.7.1-1): Will attempt migration (Any information below is purely informational)
• 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)
• flare-engine/riscv64 (1.14-3 to 1.14-3)
  • Migration status for flare-engine/riscv64 (1.14-3 to 1.14-3): Will attempt migration (Any information below is purely informational)
• flatpak-builder/riscv64 (1.4.2-1 to 1.4.2-1)
  • Migration status for flatpak-builder/riscv64 (1.4.2-1 to 1.4.2-1): Will attempt migration (Any information below is purely informational)
• flatpak/riscv64 (1.14.8-1 to 1.14.8-1)
  • Migration status for flatpak/riscv64 (1.14.8-1 to 1.14.8-1): Will attempt migration (Any information below is purely informational)
• flatzebra/riscv64 (0.1.7-2.1 to 0.1.7-2.1)
  • Migration status for flatzebra/riscv64 (0.1.7-2.1 to 0.1.7-2.1): Will attempt migration (Any information below is purely informational)
• fldiff/riscv64 (1.1+0-7 to 1.1+0-7)
  • Migration status for fldiff/riscv64 (1.1+0-7 to 1.1+0-7): Will attempt migration (Any information below is purely informational)
• fldigi/riscv64 (4.2.05-1 to 4.2.05-1)
  • Migration status for fldigi/riscv64 (4.2.05-1 to 4.2.05-1): Will attempt migration (Any information below is purely informational)
• flexbar/riscv64 (1:3.5.0-5 to 1:3.5.0-5)
  • Migration status for flexbar/riscv64 (1:3.5.0-5 to 1:3.5.0-5): Will attempt migration (Any information below is purely informational)
• flextra/riscv64 (5.0-17 to 5.0-17)
  • Migration status for flextra/riscv64 (5.0-17 to 5.0-17): 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)
• flintqs/riscv64 (1:1.0-4 to 1:1.0-4)
  • Migration status for flintqs/riscv64 (1:1.0-4 to 1:1.0-4): Will attempt migration (Any information below is purely informational)
• flmsg/riscv64 (4.0.23-1 to 4.0.23-1)
  • Migration status for flmsg/riscv64 (4.0.23-1 to 4.0.23-1): Will attempt migration (Any information below is purely informational)
• flobopuyo/riscv64 (0.20-5.1 to 0.20-5.1)
  • Migration status for flobopuyo/riscv64 (0.20-5.1 to 0.20-5.1): Will attempt migration (Any information below is purely informational)
• flpsed/riscv64 (0.7.3-9 to 0.7.3-9)
  • Migration status for flpsed/riscv64 (0.7.3-9 to 0.7.3-9): Will attempt migration (Any information below is purely informational)
• fltk1.3/riscv64 (1.3.8-6.1 to 1.3.8-6.1)
  • Migration status for fltk1.3/riscv64 (1.3.8-6.1 to 1.3.8-6.1): Will attempt migration (Any information below is purely informational)
• fluidsynth-dssi/riscv64 (1.0.0-9 to 1.0.0-9)
  • Migration status for fluidsynth-dssi/riscv64 (1.0.0-9 to 1.0.0-9): Will attempt migration (Any information below is purely informational)
• fluidsynth/riscv64 (2.3.5-1 to 2.3.5-1)
  • Migration status for fluidsynth/riscv64 (2.3.5-1 to 2.3.5-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)
• flwm/riscv64 (1.02+git2015.10.03+7dbb30-7 to 1.02+git2015.10.03+7dbb30-7)
  • Migration status for flwm/riscv64 (1.02+git2015.10.03+7dbb30-7 to 1.02+git2015.10.03+7dbb30-7): Will attempt migration (Any information below is purely informational)
• flwrap/riscv64 (1.3.6-1 to 1.3.6-1)
  • Migration status for flwrap/riscv64 (1.3.6-1 to 1.3.6-1): Will attempt migration (Any information below is purely informational)
• flxmlrpc/riscv64 (0.1.4-6 to 0.1.4-6)
  • Migration status for flxmlrpc/riscv64 (0.1.4-6 to 0.1.4-6): 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)
• fmtlib/riscv64 (9.1.0+ds1-2 to 9.1.0+ds1-2)
  • Migration status for fmtlib/riscv64 (9.1.0+ds1-2 to 9.1.0+ds1-2): Will attempt migration (Any information below is purely informational)
• fnonlinear/riscv64 (4021.81-1 to 4021.81-1)
  • Migration status for fnonlinear/riscv64 (4021.81-1 to 4021.81-1): Will attempt migration (Any information below is purely informational)
• fntsample/riscv64 (5.4-3 to 5.4-3)
  • Migration status for fntsample/riscv64 (5.4-3 to 5.4-3): Will attempt migration (Any information below is purely informational)
• folks/riscv64 (0.15.9-2 to 0.15.9-2)
  • Migration status for folks/riscv64 (0.15.9-2 to 0.15.9-2): Will attempt migration (Any information below is purely informational)
• fomp/riscv64 (1.2.4-1 to 1.2.4-1)
  • Migration status for fomp/riscv64 (1.2.4-1 to 1.2.4-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)
• foo2zjs/riscv64 (20200505dfsg0-3 to 20200505dfsg0-3)
  • Migration status for foo2zjs/riscv64 (20200505dfsg0-3 to 20200505dfsg0-3): 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)
• foonathan-memory/riscv64 (0.7.3-2.1 to 0.7.3-2.1)
  • Migration status for foonathan-memory/riscv64 (0.7.3-2.1 to 0.7.3-2.1): Will attempt migration (Any information below is purely informational)
• foot/riscv64 (1.17.2-2 to 1.17.2-2)
  • Migration status for foot/riscv64 (1.17.2-2 to 1.17.2-2): 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)
• form/riscv64 (4.3.1+git20240409+ds-2 to 4.3.1+git20240409+ds-2)
  • Migration status for form/riscv64 (4.3.1+git20240409+ds-2 to 4.3.1+git20240409+ds-2): Will attempt migration (Any information below is purely informational)
• fort-validator/riscv64 (1.6.1-1 to 1.6.1-1)
  • Migration status for fort-validator/riscv64 (1.6.1-1 to 1.6.1-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)
• foxeye/riscv64 (0.12.1-5 to 0.12.1-5)
  • Migration status for foxeye/riscv64 (0.12.1-5 to 0.12.1-5): Will attempt migration (Any information below is purely informational)
• fparserc++/riscv64 (4.5.2-2 to 4.5.2-2)
  • Migration status for fparserc++/riscv64 (4.5.2-2 to 4.5.2-2): Will attempt migration (Any information below is purely informational)
• fplll/riscv64 (5.4.5-1.1 to 5.4.5-1.1)
  • Migration status for fplll/riscv64 (5.4.5-1.1 to 5.4.5-1.1): Will attempt migration (Any information below is purely informational)
• fpylll/riscv64 (0.6.1-1 to 0.6.1-1)
  • Migration status for fpylll/riscv64 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• fpzip/riscv64 (1.3.0-4 to 1.3.0-4)
  • Migration status for fpzip/riscv64 (1.3.0-4 to 1.3.0-4): 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)
• frama-c/riscv64 (20220511-manganese-5 to 20220511-manganese-5)
  • Migration status for frama-c/riscv64 (20220511-manganese-5 to 20220511-manganese-5): 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)
• freealut/riscv64 (1.1.0-6 to 1.1.0-6)
  • Migration status for freealut/riscv64 (1.1.0-6 to 1.1.0-6): Will attempt migration (Any information below is purely informational)
• freeciv/riscv64 (3.1.1+ds-1 to 3.1.1+ds-1)
  • Migration status for freeciv/riscv64 (3.1.1+ds-1 to 3.1.1+ds-1): Will attempt migration (Any information below is purely informational)
• freediameter/riscv64 (1.2.1-8.1 to 1.2.1-8.1)
  • Migration status for freediameter/riscv64 (1.2.1-8.1 to 1.2.1-8.1): Will attempt migration (Any information below is purely informational)
• freedink/riscv64 (109.6-6 to 109.6-6)
  • Migration status for freedink/riscv64 (109.6-6 to 109.6-6): Will attempt migration (Any information below is purely informational)
• freedroidrpg/riscv64 (1.0-1 to 1.0-1)
  • Migration status for freedroidrpg/riscv64 (1.0-1 to 1.0-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)
• freefem/riscv64 (3.5.8-7 to 3.5.8-7)
  • Migration status for freefem/riscv64 (3.5.8-7 to 3.5.8-7): 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)
• freeimage/riscv64 (3.18.0+ds2-10 to 3.18.0+ds2-10)
  • Migration status for freeimage/riscv64 (3.18.0+ds2-10 to 3.18.0+ds2-10): Will attempt migration (Any information below is purely informational)
• freeorion/riscv64 (0.5+git20230820-4 to 0.5+git20230820-4)
  • Migration status for freeorion/riscv64 (0.5+git20230820-4 to 0.5+git20230820-4): Will attempt migration (Any information below is purely informational)
• freerdp2/riscv64 (2.11.5+dfsg1-1 to 2.11.5+dfsg1-1)
  • Migration status for freerdp2/riscv64 (2.11.5+dfsg1-1 to 2.11.5+dfsg1-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)
• fregression/riscv64 (4021.83-1 to 4021.83-1)
  • Migration status for fregression/riscv64 (4021.83-1 to 4021.83-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)
• frobby/riscv64 (0.9.5-4 to 0.9.5-4)
  • Migration status for frobby/riscv64 (0.9.5-4 to 0.9.5-4): 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)
• frozen-bubble/riscv64 (2.212-12 to 2.212-12)
  • Migration status for frozen-bubble/riscv64 (2.212-12 to 2.212-12): Will attempt migration (Any information below is purely informational)
• fs-uae/riscv64 (3.1.66-2 to 3.1.66-2)
  • Migration status for fs-uae/riscv64 (3.1.66-2 to 3.1.66-2): Will attempt migration (Any information below is purely informational)
• fsa/riscv64 (1.15.9+dfsg-6 to 1.15.9+dfsg-6)
  • Migration status for fsa/riscv64 (1.15.9+dfsg-6 to 1.15.9+dfsg-6): Will attempt migration (Any information below is purely informational)
• fsm-lite/riscv64 (1.0-8 to 1.0-8)
  • Migration status for fsm-lite/riscv64 (1.0-8 to 1.0-8): Will attempt migration (Any information below is purely informational)
• 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)
• fstransform/riscv64 (0.9.4-1 to 0.9.4-1)
  • Migration status for fstransform/riscv64 (0.9.4-1 to 0.9.4-1): Will attempt migration (Any information below is purely informational)
• fswatch/riscv64 (1.14.0+repack-13.1 to 1.14.0+repack-13.1)
  • Migration status for fswatch/riscv64 (1.14.0+repack-13.1 to 1.14.0+repack-13.1): Will attempt migration (Any information below is purely informational)
• fswebcam/riscv64 (20140113-2 to 20140113-2)
  • Migration status for fswebcam/riscv64 (20140113-2 to 20140113-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)
• ftpgrab/riscv64 (0.1.5-7 to 0.1.5-7)
  • Migration status for ftpgrab/riscv64 (0.1.5-7 to 0.1.5-7): Will attempt migration (Any information below is purely informational)
• fullquottel/riscv64 (0.1.5-2 to 0.1.5-2)
  • Migration status for fullquottel/riscv64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• funtools/riscv64 (1.4.8-1.1 to 1.4.8-1.1)
  • Migration status for funtools/riscv64 (1.4.8-1.1 to 1.4.8-1.1): Will attempt migration (Any information below is purely informational)
• fuse-convmvfs/riscv64 (0.2.6-2 to 0.2.6-2)
  • Migration status for fuse-convmvfs/riscv64 (0.2.6-2 to 0.2.6-2): Will attempt migration (Any information below is purely informational)
• fuse-emulator-utils/riscv64 (1.4.3-2 to 1.4.3-2)
  • Migration status for fuse-emulator-utils/riscv64 (1.4.3-2 to 1.4.3-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)
• fuse-zip/riscv64 (0.5.0-1 to 0.5.0-1)
  • Migration status for fuse-zip/riscv64 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• fuzzel/riscv64 (1.9.2-1 to 1.9.2-1)
  • Migration status for fuzzel/riscv64 (1.9.2-1 to 1.9.2-1): Will attempt migration (Any information below is purely informational)
• fuzzylite/riscv64 (6.0+dfsg-7 to 6.0+dfsg-7)
  • Migration status for fuzzylite/riscv64 (6.0+dfsg-7 to 6.0+dfsg-7): Will attempt migration (Any information below is purely informational)
• fvwm/riscv64 (1:2.7.0-2 to 1:2.7.0-2)
  • Migration status for fvwm/riscv64 (1:2.7.0-2 to 1:2.7.0-2): Will attempt migration (Any information below is purely informational)
• fvwm3/riscv64 (1.0.6a+ds-1 to 1.0.6a+ds-1)
  • Migration status for fvwm3/riscv64 (1.0.6a+ds-1 to 1.0.6a+ds-1): 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)
• fyba/riscv64 (4.1.1-11 to 4.1.1-11)
  • Migration status for fyba/riscv64 (4.1.1-11 to 4.1.1-11): Will attempt migration (Any information below is purely informational)
• g10k/riscv64 (0.9.9-1 to 0.9.9-1)
  • Migration status for g10k/riscv64 (0.9.9-1 to 0.9.9-1): Will attempt migration (Any information below is purely informational)
• g2/riscv64 (0.72-12 to 0.72-12)
  • Migration status for g2/riscv64 (0.72-12 to 0.72-12): Will attempt migration (Any information below is purely informational)
• g2clib/riscv64 (1.9.0-1 to 1.9.0-1)
  • Migration status for g2clib/riscv64 (1.9.0-1 to 1.9.0-1): Will attempt migration (Any information below is purely informational)
• g2o/riscv64 (0~20230806-4.1 to 0~20230806-4.1)
  • Migration status for g2o/riscv64 (0~20230806-4.1 to 0~20230806-4.1): Will attempt migration (Any information below is purely informational)
• g810-led/riscv64 (0.4.3-2 to 0.4.3-2)
  • Migration status for g810-led/riscv64 (0.4.3-2 to 0.4.3-2): Will attempt migration (Any information below is purely informational)
• gaffitter/riscv64 (0.6.0-4 to 0.6.0-4)
  • Migration status for gaffitter/riscv64 (0.6.0-4 to 0.6.0-4): Will attempt migration (Any information below is purely informational)
• 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)
• galera-4/riscv64 (26.4.18-1 to 26.4.18-1)
  • Migration status for galera-4/riscv64 (26.4.18-1 to 26.4.18-1): Will attempt migration (Any information below is purely informational)
• galib/riscv64 (1:2.4.7-6 to 1:2.4.7-6)
  • Migration status for galib/riscv64 (1:2.4.7-6 to 1:2.4.7-6): 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)
• gamazons/riscv64 (0.83-12 to 0.83-12)
  • Migration status for gamazons/riscv64 (0.83-12 to 0.83-12): Will attempt migration (Any information below is purely informational)
• gambas3/riscv64 (3.19.1-1 to 3.19.1-1)
  • Migration status for gambas3/riscv64 (3.19.1-1 to 3.19.1-1): Will attempt migration (Any information below is purely informational)
• game-music-emu/riscv64 (0.6.3-7 to 0.6.3-7)
  • Migration status for game-music-emu/riscv64 (0.6.3-7 to 0.6.3-7): 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)
• ganglia-modules-linux/riscv64 (1.3.6-5 to 1.3.6-5)
  • Migration status for ganglia-modules-linux/riscv64 (1.3.6-5 to 1.3.6-5): Will attempt migration (Any information below is purely informational)
• ganglia/riscv64 (3.7.2-7 to 3.7.2-7)
  • Migration status for ganglia/riscv64 (3.7.2-7 to 3.7.2-7): Will attempt migration (Any information below is purely informational)
• gap-float/riscv64 (1.0.4+ds-2 to 1.0.4+ds-2)
  • Migration status for gap-float/riscv64 (1.0.4+ds-2 to 1.0.4+ds-2): Will attempt migration (Any information below is purely informational)
• 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)
• garli/riscv64 (2.1-7 to 2.1-7)
  • Migration status for garli/riscv64 (2.1-7 to 2.1-7): Will attempt migration (Any information below is purely informational)
• gatb-core/riscv64 (1.4.2+dfsg-13 to 1.4.2+dfsg-13)
  • Migration status for gatb-core/riscv64 (1.4.2+dfsg-13 to 1.4.2+dfsg-13): Will attempt migration (Any information below is purely informational)
• gau2grid/riscv64 (2.0.7-2 to 2.0.7-2)
  • Migration status for gau2grid/riscv64 (2.0.7-2 to 2.0.7-2): Will attempt migration (Any information below is purely informational)
• gav/riscv64 (0.9.0-3.2 to 0.9.0-3.2)
  • Migration status for gav/riscv64 (0.9.0-3.2 to 0.9.0-3.2): 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)
• gbatnav/riscv64 (1.0.4cvs20051004-7 to 1.0.4cvs20051004-7)
  • Migration status for gbatnav/riscv64 (1.0.4cvs20051004-7 to 1.0.4cvs20051004-7): 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)
• gcc-arm-none-eabi/riscv64 (15:13.2.rel1-2 to 15:13.2.rel1-2)
  • Migration status for gcc-arm-none-eabi/riscv64 (15:13.2.rel1-2 to 15:13.2.rel1-2): Will attempt migration (Any information below is purely informational)
• gcc-defaults/riscv64 (1.214 to 1.214)
  • Migration status for gcc-defaults/riscv64 (1.214 to 1.214): Will attempt migration (Any information below is purely informational)
• gcc-mingw-w64/riscv64 (26.3 to 26.3)
  • Migration status for gcc-mingw-w64/riscv64 (26.3 to 26.3): Will attempt migration (Any information below is purely informational)
• gcc-riscv64-unknown-elf/riscv64 (12 to 12)
  • Migration status for gcc-riscv64-unknown-elf/riscv64 (12 to 12): Will attempt migration (Any information below is purely informational)
• gcc-xtensa/riscv64 (14 to 14)
  • Migration status for gcc-xtensa/riscv64 (14 to 14): Will attempt migration (Any information below is purely informational)
• gcin/riscv64 (2.9.0+dfsg1-3 to 2.9.0+dfsg1-3)
  • Migration status for gcin/riscv64 (2.9.0+dfsg1-3 to 2.9.0+dfsg1-3): 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)
• gd4o/riscv64 (1.0~alpha5.git20220521.bb52fb2-1 to 1.0~alpha5.git20220521.bb52fb2-1)
  • Migration status for gd4o/riscv64 (1.0~alpha5.git20220521.bb52fb2-1 to 1.0~alpha5.git20220521.bb52fb2-1): Will attempt migration (Any information below is purely informational)
• gdb-avr/riscv64 (13.2-4 to 13.2-4)
  • Migration status for gdb-avr/riscv64 (13.2-4 to 13.2-4): Will attempt migration (Any information below is purely informational)
• gdb-bpf/riscv64 (6 to 6)
  • Migration status for gdb-bpf/riscv64 (6 to 6): Will attempt migration (Any information below is purely informational)
• gdb-mingw-w64/riscv64 (13.1 to 13.1)
  • Migration status for gdb-mingw-w64/riscv64 (13.1 to 13.1): Will attempt migration (Any information below is purely informational)
• gdb/riscv64 (13.2-1 to 13.2-1)
  • Migration status for gdb/riscv64 (13.2-1 to 13.2-1): Will attempt migration (Any information below is purely informational)
• gddrescue/riscv64 (1.27-1 to 1.27-1)
  • Migration status for gddrescue/riscv64 (1.27-1 to 1.27-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)
• gdisk/riscv64 (1.0.10-1 to 1.0.10-1)
  • Migration status for gdisk/riscv64 (1.0.10-1 to 1.0.10-1): 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)
• gdspy/riscv64 (1.4.2-2 to 1.4.2-2)
  • Migration status for gdspy/riscv64 (1.4.2-2 to 1.4.2-2): Will attempt migration (Any information below is purely informational)
• gearmand/riscv64 (1.1.20+ds-1.2 to 1.1.20+ds-1.2)
  • Migration status for gearmand/riscv64 (1.1.20+ds-1.2 to 1.1.20+ds-1.2): Will attempt migration (Any information below is purely informational)
• gecode/riscv64 (6.2.0-5.1 to 6.2.0-5.1)
  • Migration status for gecode/riscv64 (6.2.0-5.1 to 6.2.0-5.1): Will attempt migration (Any information below is purely informational)
• 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/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)
• 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)
• gemdropx/riscv64 (0.9-9 to 0.9-9)
  • Migration status for gemdropx/riscv64 (0.9-9 to 0.9-9): Will attempt migration (Any information below is purely informational)
• gemma/riscv64 (0.98.5+dfsg-2 to 0.98.5+dfsg-2)
  • Migration status for gemma/riscv64 (0.98.5+dfsg-2 to 0.98.5+dfsg-2): Will attempt migration (Any information below is purely informational)
• gemrb/riscv64 (0.9.2+dfsg-1 to 0.9.2+dfsg-1)
  • Migration status for gemrb/riscv64 (0.9.2+dfsg-1 to 0.9.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• generate-ninja/riscv64 (0.0~git20240328.93ee9b9-1 to 0.0~git20240328.93ee9b9-1)
  • Migration status for generate-ninja/riscv64 (0.0~git20240328.93ee9b9-1 to 0.0~git20240328.93ee9b9-1): Will attempt migration (Any information below is purely informational)
• geners/riscv64 (0.0~svn60+ds-3 to 0.0~svn60+ds-3)
  • Migration status for geners/riscv64 (0.0~svn60+ds-3 to 0.0~svn60+ds-3): 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)
• gengetopt/riscv64 (2.23+dfsg1-1 to 2.23+dfsg1-1)
  • Migration status for gengetopt/riscv64 (2.23+dfsg1-1 to 2.23+dfsg1-1): 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)
• genomethreader/riscv64 (1.7.3+dfsg-10 to 1.7.3+dfsg-10)
  • Migration status for genomethreader/riscv64 (1.7.3+dfsg-10 to 1.7.3+dfsg-10): Will attempt migration (Any information below is purely informational)
• genometools/riscv64 (1.6.5+ds-2.2 to 1.6.5+ds-2.2)
  • Migration status for genometools/riscv64 (1.6.5+ds-2.2 to 1.6.5+ds-2.2): Will attempt migration (Any information below is purely informational)
• genparse/riscv64 (0.9.3-2 to 0.9.3-2)
  • Migration status for genparse/riscv64 (0.9.3-2 to 0.9.3-2): Will attempt migration (Any information below is purely informational)
• gensim/riscv64 (4.3.2+dfsg-1 to 4.3.2+dfsg-1)
  • Migration status for gensim/riscv64 (4.3.2+dfsg-1 to 4.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• gensio/riscv64 (2.8.2-6.1 to 2.8.2-6.1)
  • Migration status for gensio/riscv64 (2.8.2-6.1 to 2.8.2-6.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)
• geotranz/riscv64 (3.7-3 to 3.7-3)
  • Migration status for geotranz/riscv64 (3.7-3 to 3.7-3): Will attempt migration (Any information below is purely informational)
• gerbera/riscv64 (2.0.0+dfsg-1 to 2.0.0+dfsg-1)
  • Migration status for gerbera/riscv64 (2.0.0+dfsg-1 to 2.0.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• 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)
• gerris/riscv64 (20131206+dfsg-19.1 to 20131206+dfsg-19.1)
  • Migration status for gerris/riscv64 (20131206+dfsg-19.1 to 20131206+dfsg-19.1): Will attempt migration (Any information below is purely informational)
• getdp/riscv64 (3.5.0+dfsg1-2 to 3.5.0+dfsg1-2)
  • Migration status for getdp/riscv64 (3.5.0+dfsg1-2 to 3.5.0+dfsg1-2): Will attempt migration (Any information below is purely informational)
• geventhttpclient/riscv64 (2.0.11-2 to 2.0.11-2)
  • Migration status for geventhttpclient/riscv64 (2.0.11-2 to 2.0.11-2): Will attempt migration (Any information below is purely informational)
• 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)
• gfal2-bindings/riscv64 (1.12.2-2 to 1.12.2-2)
  • Migration status for gfal2-bindings/riscv64 (1.12.2-2 to 1.12.2-2): Will attempt migration (Any information below is purely informational)
• gfal2/riscv64 (2.22.2-2 to 2.22.2-2)
  • Migration status for gfal2/riscv64 (2.22.2-2 to 2.22.2-2): Will attempt migration (Any information below is purely informational)
• gfan/riscv64 (0.6.2-7 to 0.6.2-7)
  • Migration status for gfan/riscv64 (0.6.2-7 to 0.6.2-7): Will attempt migration (Any information below is purely informational)
• gfarm/riscv64 (2.7.20+dfsg-1.2 to 2.7.20+dfsg-1.2)
  • Migration status for gfarm/riscv64 (2.7.20+dfsg-1.2 to 2.7.20+dfsg-1.2): Will attempt migration (Any information below is purely informational)
• gfarm2fs/riscv64 (1.2.16-1 to 1.2.16-1)
  • Migration status for gfarm2fs/riscv64 (1.2.16-1 to 1.2.16-1): Will attempt migration (Any information below is purely informational)
• gflags/riscv64 (2.2.2-2 to 2.2.2-2)
  • Migration status for gflags/riscv64 (2.2.2-2 to 2.2.2-2): Will attempt migration (Any information below is purely informational)
• gfsview/riscv64 (20121130+dfsg-8.1 to 20121130+dfsg-8.1)
  • Migration status for gfsview/riscv64 (20121130+dfsg-8.1 to 20121130+dfsg-8.1): Will attempt migration (Any information below is purely informational)
• gftp/riscv64 (2.9.1~beta-2 to 2.9.1~beta-2)
  • Migration status for gftp/riscv64 (2.9.1~beta-2 to 2.9.1~beta-2): Will attempt migration (Any information below is purely informational)
• ggobi/riscv64 (2.1.11-2 to 2.1.11-2)
  • Migration status for ggobi/riscv64 (2.1.11-2 to 2.1.11-2): Will attempt migration (Any information below is purely informational)
• ghc/riscv64 (9.4.7-5 to 9.4.7-5)
  • Migration status for ghc/riscv64 (9.4.7-5 to 9.4.7-5): Will attempt migration (Any information below is purely informational)
• 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)
• ghostess/riscv64 (20210101-1 to 20210101-1)
  • Migration status for ghostess/riscv64 (20210101-1 to 20210101-1): Will attempt migration (Any information below is purely informational)
• 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)
• gigalomania/riscv64 (1.0+ds1-1.1 to 1.0+ds1-1.1)
  • Migration status for gigalomania/riscv64 (1.0+ds1-1.1 to 1.0+ds1-1.1): Will attempt migration (Any information below is purely informational)
• giggle/riscv64 (0.7-6 to 0.7-6)
  • Migration status for giggle/riscv64 (0.7-6 to 0.7-6): Will attempt migration (Any information below is purely informational)
• 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-gap/riscv64 (2.6.0+dfsg-8 to 2.6.0+dfsg-8)
  • Migration status for gimp-gap/riscv64 (2.6.0+dfsg-8 to 2.6.0+dfsg-8): Will attempt migration (Any information below is purely informational)
• gimp-plugin-registry/riscv64 (9.20240404 to 9.20240404)
  • Migration status for gimp-plugin-registry/riscv64 (9.20240404 to 9.20240404): 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): Will attempt migration (Any information below is purely informational)
• ginac/riscv64 (1.8.7-1 to 1.8.7-1)
  • Migration status for ginac/riscv64 (1.8.7-1 to 1.8.7-1): Will attempt migration (Any information below is purely informational)
• gir-to-d/riscv64 (0.23.2-1 to 0.23.2-1)
  • Migration status for gir-to-d/riscv64 (0.23.2-1 to 0.23.2-1): Will attempt migration (Any information below is purely informational)
• 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-crypt/riscv64 (0.7.0-0.1 to 0.7.0-0.1)
  • Migration status for git-crypt/riscv64 (0.7.0-0.1 to 0.7.0-0.1): Will attempt migration (Any information below is purely informational)
• git-evtag/riscv64 (2022.1-1 to 2022.1-1)
  • Migration status for git-evtag/riscv64 (2022.1-1 to 2022.1-1): Will attempt migration (Any information below is purely informational)
• git-lfs/riscv64 (3.5.0-1 to 3.5.0-1)
  • Migration status for git-lfs/riscv64 (3.5.0-1 to 3.5.0-1): Will attempt migration (Any information below is purely informational)
• git-repair/riscv64 (1.20230814-1 to 1.20230814-1)
  • Migration status for git-repair/riscv64 (1.20230814-1 to 1.20230814-1): Will attempt migration (Any information below is purely informational)
• gitbrute/riscv64 (0~15-2 to 0~15-2)
  • Migration status for gitbrute/riscv64 (0~15-2 to 0~15-2): Will attempt migration (Any information below is purely informational)
• 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)
• giza/riscv64 (1.4.1-1 to 1.4.1-1)
  • Migration status for giza/riscv64 (1.4.1-1 to 1.4.1-1): Will attempt migration (Any information below is purely informational)
• 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)
• gjh-asl-json/riscv64 (0.0+git20210628.867c5da-1 to 0.0+git20210628.867c5da-1)
  • Migration status for gjh-asl-json/riscv64 (0.0+git20210628.867c5da-1 to 0.0+git20210628.867c5da-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-mailwatch/riscv64 (2.4.3-2 to 2.4.3-2)
  • Migration status for gkrellm-mailwatch/riscv64 (2.4.3-2 to 2.4.3-2): Will attempt migration (Any information below is purely informational)
• gkrellm-radio/riscv64 (2.0.4-3 to 2.0.4-3)
  • Migration status for gkrellm-radio/riscv64 (2.0.4-3 to 2.0.4-3): Will attempt migration (Any information below is purely informational)
• gkrellm-thinkbat/riscv64 (0.2.2-1.2 to 0.2.2-1.2)
  • Migration status for gkrellm-thinkbat/riscv64 (0.2.2-1.2 to 0.2.2-1.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-xkb/riscv64 (1.05-5.2 to 1.05-5.2)
  • Migration status for gkrellm-xkb/riscv64 (1.05-5.2 to 1.05-5.2): 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)
• gkrellshoot/riscv64 (0.4.4-3 to 0.4.4-3)
  • Migration status for gkrellshoot/riscv64 (0.4.4-3 to 0.4.4-3): 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)
• gl-image-display/riscv64 (0.18-1 to 0.18-1)
  • Migration status for gl-image-display/riscv64 (0.18-1 to 0.18-1): 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)
• glabels/riscv64 (3.4.1-4 to 3.4.1-4)
  • Migration status for glabels/riscv64 (3.4.1-4 to 3.4.1-4): Will attempt migration (Any information below is purely informational)
• glade/riscv64 (3.40.0-5 to 3.40.0-5)
  • Migration status for glade/riscv64 (3.40.0-5 to 3.40.0-5): Will attempt migration (Any information below is purely informational)
• glam2/riscv64 (1064-9 to 1064-9)
  • Migration status for glam2/riscv64 (1064-9 to 1064-9): 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)
• glibmm2.4/riscv64 (2.66.7-1 to 2.66.7-1)
  • Migration status for glibmm2.4/riscv64 (2.66.7-1 to 2.66.7-1): Will attempt migration (Any information below is purely informational)
• glmark2/riscv64 (2023.01+dfsg-1 to 2023.01+dfsg-1)
  • Migration status for glmark2/riscv64 (2023.01+dfsg-1 to 2023.01+dfsg-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)
• glogg/riscv64 (1.1.4-1.2 to 1.1.4-1.2)
  • Migration status for glogg/riscv64 (1.1.4-1.2 to 1.1.4-1.2): 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)
• gloox/riscv64 (1.0.28-1 to 1.0.28-1)
  • Migration status for gloox/riscv64 (1.0.28-1 to 1.0.28-1): 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)
• glpk-java/riscv64 (1.12.0-2 to 1.12.0-2)
  • Migration status for glpk-java/riscv64 (1.12.0-2 to 1.12.0-2): Will attempt migration (Any information below is purely informational)
• glpk/riscv64 (5.0-1 to 5.0-1)
  • Migration status for glpk/riscv64 (5.0-1 to 5.0-1): 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)
• glycin-loaders/riscv64 (0.1.2+dfsg-2 to 0.1.2+dfsg-2)
  • Migration status for glycin-loaders/riscv64 (0.1.2+dfsg-2 to 0.1.2+dfsg-2): 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)
• gmanedit/riscv64 (0.4.2-8 to 0.4.2-8)
  • Migration status for gmanedit/riscv64 (0.4.2-8 to 0.4.2-8): 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)
• gmpc-plugins/riscv64 (11.8.16-7 to 11.8.16-7)
  • Migration status for gmpc-plugins/riscv64 (11.8.16-7 to 11.8.16-7): Will attempt migration (Any information below is purely informational)
• gmpc/riscv64 (11.8.16-21 to 11.8.16-21)
  • Migration status for gmpc/riscv64 (11.8.16-21 to 11.8.16-21): Will attempt migration (Any information below is purely informational)
• gmrender-resurrect/riscv64 (0.1-1 to 0.1-1)
  • Migration status for gmrender-resurrect/riscv64 (0.1-1 to 0.1-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)
• gnomad2/riscv64 (2.9.6-9 to 2.9.6-9)
  • Migration status for gnomad2/riscv64 (2.9.6-9 to 2.9.6-9): 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-autoar/riscv64 (0.4.4-2 to 0.4.4-2)
  • Migration status for gnome-autoar/riscv64 (0.4.4-2 to 0.4.4-2): 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-breakout/riscv64 (0.5.3-8 to 0.5.3-8)
  • Migration status for gnome-breakout/riscv64 (0.5.3-8 to 0.5.3-8): 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-characters/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-characters/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• gnome-chess/riscv64 (1:46.0-1 to 1:46.0-1)
  • Migration status for gnome-chess/riscv64 (1:46.0-1 to 1:46.0-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-connections/riscv64 (46.0-2 to 46.0-2)
  • Migration status for gnome-connections/riscv64 (46.0-2 to 46.0-2): Will attempt migration (Any information below is purely informational)
• gnome-console/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-console/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• gnome-contacts/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-contacts/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• 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-disk-utility/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-disk-utility/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• gnome-dvb-daemon/riscv64 (1:0.2.91~git20170110-5 to 1:0.2.91~git20170110-5)
  • Migration status for gnome-dvb-daemon/riscv64 (1:0.2.91~git20170110-5 to 1:0.2.91~git20170110-5): 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-font-viewer/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-font-viewer/riscv64 (46.0-1 to 46.0-1): 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-keyring/riscv64 (46.1-2 to 46.1-2)
  • Migration status for gnome-keyring/riscv64 (46.1-2 to 46.1-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-mahjongg/riscv64 (1:3.40.1-1 to 1:3.40.1-1)
  • Migration status for gnome-mahjongg/riscv64 (1:3.40.1-1 to 1:3.40.1-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-model-thumbnailer/riscv64 (0+git20240108+ds-2 to 0+git20240108+ds-2)
  • Migration status for gnome-model-thumbnailer/riscv64 (0+git20240108+ds-2 to 0+git20240108+ds-2): 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-music/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnome-music/riscv64 (46.0-1 to 46.0-1): 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-nibbles/riscv64 (1:4.0.4-1 to 1:4.0.4-1)
  • Migration status for gnome-nibbles/riscv64 (1:4.0.4-1 to 1:4.0.4-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-packagekit/riscv64 (43.0-2 to 43.0-2)
  • Migration status for gnome-packagekit/riscv64 (43.0-2 to 43.0-2): Will attempt migration (Any information below is purely informational)
• gnome-paint/riscv64 (0.4.0-10 to 0.4.0-10)
  • Migration status for gnome-paint/riscv64 (0.4.0-10 to 0.4.0-10): 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-shell-extension-panel-osd/riscv64 (1.0.50.gc032923-4 to 1.0.50.gc032923-4)
  • Migration status for gnome-shell-extension-panel-osd/riscv64 (1.0.50.gc032923-4 to 1.0.50.gc032923-4): 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-system-tools/riscv64 (3.0.0-10 to 3.0.0-10)
  • Migration status for gnome-system-tools/riscv64 (3.0.0-10 to 3.0.0-10): 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-themes-extra/riscv64 (3.28-2 to 3.28-2)
  • Migration status for gnome-themes-extra/riscv64 (3.28-2 to 3.28-2): 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)
• gnomekiss/riscv64 (2.0-6.1 to 2.0-6.1)
  • Migration status for gnomekiss/riscv64 (2.0-6.1 to 2.0-6.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)
• gnote/riscv64 (46.0-1 to 46.0-1)
  • Migration status for gnote/riscv64 (46.0-1 to 46.0-1): 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)
• gnuastro/riscv64 (0.22-3.1 to 0.22-3.1)
  • Migration status for gnuastro/riscv64 (0.22-3.1 to 0.22-3.1): Will attempt migration (Any information below is purely informational)
• gnubg/riscv64 (1.07.001-3 to 1.07.001-3)
  • Migration status for gnubg/riscv64 (1.07.001-3 to 1.07.001-3): Will attempt migration (Any information below is purely informational)
• gnucap/riscv64 (1:0.36~20171003-1.1 to 1:0.36~20171003-1.1)
  • Migration status for gnucap/riscv64 (1:0.36~20171003-1.1 to 1:0.36~20171003-1.1): Will attempt migration (Any information below is purely informational)
• gnucash/riscv64 (1:5.6-1 to 1:5.6-1)
  • Migration status for gnucash/riscv64 (1:5.6-1 to 1:5.6-1): Will attempt migration (Any information below is purely informational)
• gnucobol/riscv64 (5 to 5)
  • Migration status for gnucobol/riscv64 (5 to 5): Will attempt migration (Any information below is purely informational)
• gnucobol3/riscv64 (3.1.2-5.1 to 3.1.2-5.1)
  • Migration status for gnucobol3/riscv64 (3.1.2-5.1 to 3.1.2-5.1): Will attempt migration (Any information below is purely informational)
• gnucobol4/riscv64 (4.0~early~20200606-6.1 to 4.0~early~20200606-6.1)
  • Migration status for gnucobol4/riscv64 (4.0~early~20200606-6.1 to 4.0~early~20200606-6.1): Will attempt migration (Any information below is purely informational)
• gnudatalanguage/riscv64 (1.0.4-1 to 1.0.4-1)
  • Migration status for gnudatalanguage/riscv64 (1.0.4-1 to 1.0.4-1): Will attempt migration (Any information below is purely informational)
• gnujump/riscv64 (1.0.8-3.1 to 1.0.8-3.1)
  • Migration status for gnujump/riscv64 (1.0.8-3.1 to 1.0.8-3.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)
• gnunet-fuse/riscv64 (0.20.0-3 to 0.20.0-3)
  • Migration status for gnunet-fuse/riscv64 (0.20.0-3 to 0.20.0-3): Will attempt migration (Any information below is purely informational)
• gnunet-gtk/riscv64 (0.20.0-4 to 0.20.0-4)
  • Migration status for gnunet-gtk/riscv64 (0.20.0-4 to 0.20.0-4): Will attempt migration (Any information below is purely informational)
• gnuplot/riscv64 (6.0.0+dfsg1-3 to 6.0.0+dfsg1-3)
  • Migration status for gnuplot/riscv64 (6.0.0+dfsg1-3 to 6.0.0+dfsg1-3): Will attempt migration (Any information below is purely informational)
• gnuradio/riscv64 (3.10.10.0-1 to 3.10.10.0-1)
  • Migration status for gnuradio/riscv64 (3.10.10.0-1 to 3.10.10.0-1): 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)
• gnuserv/riscv64 (3.12.8-12 to 3.12.8-12)
  • Migration status for gnuserv/riscv64 (3.12.8-12 to 3.12.8-12): 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-netclasses/riscv64 (1.06.dfsg-7 to 1.06.dfsg-7)
  • Migration status for gnustep-netclasses/riscv64 (1.06.dfsg-7 to 1.06.dfsg-7): 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-containerregistry/riscv64 (0.14.0+ds1-2 to 0.14.0+ds1-2)
  • Migration status for go-containerregistry/riscv64 (0.14.0+ds1-2 to 0.14.0+ds1-2): 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)
• gobby/riscv64 (0.6.0-2 to 0.6.0-2)
  • Migration status for gobby/riscv64 (0.6.0-2 to 0.6.0-2): Will attempt migration (Any information below is purely informational)
• 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)
• golang-connectrpc-connect/riscv64 (1.13.0-1 to 1.13.0-1)
  • Migration status for golang-connectrpc-connect/riscv64 (1.13.0-1 to 1.13.0-1): Will attempt migration (Any information below is purely informational)
• golang-defaults/riscv64 (2:1.22~3 to 2:1.22~3)
  • Migration status for golang-defaults/riscv64 (2:1.22~3 to 2:1.22~3): Will attempt migration (Any information below is purely informational)
• 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-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-golang-protobuf-1-3/riscv64 (1.3.5-4 to 1.3.5-4)
  • Migration status for golang-github-golang-protobuf-1-3/riscv64 (1.3.5-4 to 1.3.5-4): Will attempt migration (Any information below is purely informational)
• golang-github-golang-protobuf-1-5/riscv64 (1.5.4-1 to 1.5.4-1)
  • Migration status for golang-github-golang-protobuf-1-5/riscv64 (1.5.4-1 to 1.5.4-1): Will attempt migration (Any information below is purely informational)
• golang-gogoprotobuf/riscv64 (1.3.2-3 to 1.3.2-3)
  • Migration status for golang-gogoprotobuf/riscv64 (1.3.2-3 to 1.3.2-3): Will attempt migration (Any information below is purely informational)
• golang-google-grpc/riscv64 (1.38.0+really1.33.3-1 to 1.38.0+really1.33.3-1)
  • Migration status for golang-google-grpc/riscv64 (1.38.0+really1.33.3-1 to 1.38.0+really1.33.3-1): Will attempt migration (Any information below is purely informational)
• golang-google-protobuf/riscv64 (1.33.0-1 to 1.33.0-1)
  • Migration status for golang-google-protobuf/riscv64 (1.33.0-1 to 1.33.0-1): Will attempt migration (Any information below is purely informational)
• goldendict/riscv64 (1.5.0-1 to 1.5.0-1)
  • Migration status for goldendict/riscv64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
• 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)
• gomoku.app/riscv64 (1.2.9-5 to 1.2.9-5)
  • Migration status for gomoku.app/riscv64 (1.2.9-5 to 1.2.9-5): Will attempt migration (Any information below is purely informational)
• gomuks/riscv64 (0.3.0-3 to 0.3.0-3)
  • Migration status for gomuks/riscv64 (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
• goo/riscv64 (0.155+ds-4 to 0.155+ds-4)
  • Migration status for goo/riscv64 (0.155+ds-4 to 0.155+ds-4): Will attempt migration (Any information below is purely informational)
• goocanvas-2.0/riscv64 (2.0.4-1 to 2.0.4-1)
  • Migration status for goocanvas-2.0/riscv64 (2.0.4-1 to 2.0.4-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)
• google-compute-engine-oslogin/riscv64 (20240415.00-1 to 20240415.00-1)
  • Migration status for google-compute-engine-oslogin/riscv64 (20240415.00-1 to 20240415.00-1): Will attempt migration (Any information below is purely informational)
• google-glog/riscv64 (0.6.0-2.1 to 0.6.0-2.1)
  • Migration status for google-glog/riscv64 (0.6.0-2.1 to 0.6.0-2.1): Will attempt migration (Any information below is purely informational)
• google-perftools/riscv64 (2.15-3 to 2.15-3)
  • Migration status for google-perftools/riscv64 (2.15-3 to 2.15-3): 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)
• gp2c/riscv64 (0.0.13-1 to 0.0.13-1)
  • Migration status for gp2c/riscv64 (0.0.13-1 to 0.0.13-1): Will attempt migration (Any information below is purely informational)
• gpa/riscv64 (0.10.0-6 to 0.10.0-6)
  • Migration status for gpa/riscv64 (0.10.0-6 to 0.10.0-6): 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)
• gpaste/riscv64 (44.1-2.1 to 44.1-2.1)
  • Migration status for gpaste/riscv64 (44.1-2.1 to 44.1-2.1): Will attempt migration (Any information below is purely informational)
• gperf/riscv64 (3.1-1 to 3.1-1)
  • Migration status for gperf/riscv64 (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
• gperiodic/riscv64 (3.0.3-1 to 3.0.3-1)
  • Migration status for gperiodic/riscv64 (3.0.3-1 to 3.0.3-1): Will attempt migration (Any information below is purely informational)
• gpg-remailer/riscv64 (3.04.07-1 to 3.04.07-1)
  • Migration status for gpg-remailer/riscv64 (3.04.07-1 to 3.04.07-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)
• gphoto2/riscv64 (2.5.28-2 to 2.5.28-2)
  • Migration status for gphoto2/riscv64 (2.5.28-2 to 2.5.28-2): 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)
• gpicview/riscv64 (0.2.5-5 to 0.2.5-5)
  • Migration status for gpicview/riscv64 (0.2.5-5 to 0.2.5-5): 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)
• gprbuild/riscv64 (2024.1.20231009-5 to 2024.1.20231009-5)
  • Migration status for gprbuild/riscv64 (2024.1.20231009-5 to 2024.1.20231009-5): Will attempt migration (Any information below is purely informational)
• gpredict/riscv64 (2.3-115-g0f3beb6-3 to 2.3-115-g0f3beb6-3)
  • Migration status for gpredict/riscv64 (2.3-115-g0f3beb6-3 to 2.3-115-g0f3beb6-3): Will attempt migration (Any information below is purely informational)
• gpsim/riscv64 (0.32.1-2 to 0.32.1-2)
  • Migration status for gpsim/riscv64 (0.32.1-2 to 0.32.1-2): Will attempt migration (Any information below is purely informational)
• gpsmanshp/riscv64 (1.2.3-7 to 1.2.3-7)
  • Migration status for gpsmanshp/riscv64 (1.2.3-7 to 1.2.3-7): Will attempt migration (Any information below is purely informational)
• gpt/riscv64 (1.1-8 to 1.1-8)
  • Migration status for gpt/riscv64 (1.1-8 to 1.1-8): 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-gsm/riscv64 (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/riscv64 (1.0.0~20220727-1 to 1.0.0~20220727-1): 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)
• grabix/riscv64 (0.1.7-4 to 0.1.7-4)
  • Migration status for grabix/riscv64 (0.1.7-4 to 0.1.7-4): Will attempt migration (Any information below is purely informational)
• grads/riscv64 (3:2.2.1-6 to 3:2.2.1-6)
  • Migration status for grads/riscv64 (3:2.2.1-6 to 3:2.2.1-6): Will attempt migration (Any information below is purely informational)
• grafx2/riscv64 (2.8+ds-3 to 2.8+ds-3)
  • Migration status for grafx2/riscv64 (2.8+ds-3 to 2.8+ds-3): Will attempt migration (Any information below is purely informational)
• grail/riscv64 (3.1.1-4 to 3.1.1-4)
  • Migration status for grail/riscv64 (3.1.1-4 to 3.1.1-4): 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)
• graphicsmagick/riscv64 (1.4+really1.3.43-1 to 1.4+really1.3.43-1)
  • Migration status for graphicsmagick/riscv64 (1.4+really1.3.43-1 to 1.4+really1.3.43-1): Will attempt migration (Any information below is purely informational)
• graphite2/riscv64 (1.3.14-2 to 1.3.14-2)
  • Migration status for graphite2/riscv64 (1.3.14-2 to 1.3.14-2): Will attempt migration (Any information below is purely informational)
• grass/riscv64 (8.3.2-1 to 8.3.2-1)
  • Migration status for grass/riscv64 (8.3.2-1 to 8.3.2-1): 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)
• gravitation/riscv64 (3+dfsg1-6 to 3+dfsg1-6)
  • Migration status for gravitation/riscv64 (3+dfsg1-6 to 3+dfsg1-6): Will attempt migration (Any information below is purely informational)
• grcompiler/riscv64 (5.2.1-1 to 5.2.1-1)
  • Migration status for grcompiler/riscv64 (5.2.1-1 to 5.2.1-1): 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)
• grhino/riscv64 (0.16.1-5 to 0.16.1-5)
  • Migration status for grhino/riscv64 (0.16.1-5 to 0.16.1-5): 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)
• gringotts/riscv64 (1.2.10-4 to 1.2.10-4)
  • Migration status for gringotts/riscv64 (1.2.10-4 to 1.2.10-4): Will attempt migration (Any information below is purely informational)
• gromit-mpx/riscv64 (1.6.0-1 to 1.6.0-1)
  • Migration status for gromit-mpx/riscv64 (1.6.0-1 to 1.6.0-1): 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)
• groonga-normalizer-mysql/riscv64 (1.2.3-4 to 1.2.3-4)
  • Migration status for groonga-normalizer-mysql/riscv64 (1.2.3-4 to 1.2.3-4): 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)
• grpc/riscv64 (1.51.1-4.1 to 1.51.1-4.1)
  • Migration status for grpc/riscv64 (1.51.1-4.1 to 1.51.1-4.1): Will attempt migration (Any information below is purely informational)
• grpn/riscv64 (1.4.1-1.1 to 1.4.1-1.1)
  • Migration status for grpn/riscv64 (1.4.1-1.1 to 1.4.1-1.1): Will attempt migration (Any information below is purely informational)
• grr.app/riscv64 (1.0-1 to 1.0-1)
  • Migration status for grr.app/riscv64 (1.0-1 to 1.0-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)
• gsmlib/riscv64 (1.10+20120414.gita5e5ae9a-3 to 1.10+20120414.gita5e5ae9a-3)
  • Migration status for gsmlib/riscv64 (1.10+20120414.gita5e5ae9a-3 to 1.10+20120414.gita5e5ae9a-3): Will attempt migration (Any information below is purely informational)
• gsoap/riscv64 (2.8.132-2.1 to 2.8.132-2.1)
  • Migration status for gsoap/riscv64 (2.8.132-2.1 to 2.8.132-2.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)
• gss/riscv64 (1.0.4-3 to 1.0.4-3)
  • Migration status for gss/riscv64 (1.0.4-3 to 1.0.4-3): Will attempt migration (Any information below is purely informational)
• gst-plugins-espeak/riscv64 (0.5.0-1 to 0.5.0-1)
  • Migration status for gst-plugins-espeak/riscv64 (0.5.0-1 to 0.5.0-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)
• gtans/riscv64 (1.99.0-2.1 to 1.99.0-2.1)
  • Migration status for gtans/riscv64 (1.99.0-2.1 to 1.99.0-2.1): Will attempt migration (Any information below is purely informational)
• gtetrinet/riscv64 (0.7.11+git20200916.46e7ade-2 to 0.7.11+git20200916.46e7ade-2)
  • Migration status for gtetrinet/riscv64 (0.7.11+git20200916.46e7ade-2 to 0.7.11+git20200916.46e7ade-2): 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)
• gthumb/riscv64 (3:3.12.6-1 to 3:3.12.6-1)
  • Migration status for gthumb/riscv64 (3:3.12.6-1 to 3:3.12.6-1): 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-vector-screenshot/riscv64 (0.3.3-2 to 0.3.3-2)
  • Migration status for gtk-vector-screenshot/riscv64 (0.3.3-2 to 0.3.3-2): 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)
• gtk4/riscv64 (4.12.5+ds-6 to 4.12.5+ds-6)
  • Migration status for gtk4/riscv64 (4.12.5+ds-6 to 4.12.5+ds-6): Will attempt migration (Any information below is purely informational)
• gtkam/riscv64 (1.0-5 to 1.0-5)
  • Migration status for gtkam/riscv64 (1.0-5 to 1.0-5): 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)
• gtksheet/riscv64 (4.3.13+dfsg-1 to 4.3.13+dfsg-1)
  • Migration status for gtksheet/riscv64 (4.3.13+dfsg-1 to 4.3.13+dfsg-1): Will attempt migration (Any information below is purely informational)
• gtksourceview3/riscv64 (3.24.11-2 to 3.24.11-2)
  • Migration status for gtksourceview3/riscv64 (3.24.11-2 to 3.24.11-2): 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)
• gtkwave/riscv64 (3.3.118-0.1 to 3.3.118-0.1)
  • Migration status for gtkwave/riscv64 (3.3.118-0.1 to 3.3.118-0.1): Will attempt migration (Any information below is purely informational)
• gtools/riscv64 (3.9.5-1 to 3.9.5-1)
  • Migration status for gtools/riscv64 (3.9.5-1 to 3.9.5-1): Will attempt migration (Any information below is purely informational)
• gtranslator/riscv64 (46.1-1 to 46.1-1)
  • Migration status for gtranslator/riscv64 (46.1-1 to 46.1-1): Will attempt migration (Any information below is purely informational)
• gtsam/riscv64 (4.2.0+dfsg-1 to 4.2.0+dfsg-1)
  • Migration status for gtsam/riscv64 (4.2.0+dfsg-1 to 4.2.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• guetzli/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for guetzli/riscv64 (1.0.1-1 to 1.0.1-1): 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)
• guile-2.2/riscv64 (2.2.7+1-9 to 2.2.7+1-9)
  • Migration status for guile-2.2/riscv64 (2.2.7+1-9 to 2.2.7+1-9): Will attempt migration (Any information below is purely informational)
• guile-avahi/riscv64 (0.4.1-2 to 0.4.1-2)
  • Migration status for guile-avahi/riscv64 (0.4.1-2 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
• guile-cairo/riscv64 (1.12.0~pre1-2 to 1.12.0~pre1-2)
  • Migration status for guile-cairo/riscv64 (1.12.0~pre1-2 to 1.12.0~pre1-2): Will attempt migration (Any information below is purely informational)
• guile-gcrypt/riscv64 (0.4.0-2 to 0.4.0-2)
  • Migration status for guile-gcrypt/riscv64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• guile-git/riscv64 (0.7.0-1 to 0.7.0-1)
  • Migration status for guile-git/riscv64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• guile-json/riscv64 (4.7.3-2 to 4.7.3-2)
  • Migration status for guile-json/riscv64 (4.7.3-2 to 4.7.3-2): Will attempt migration (Any information below is purely informational)
• guile-lib/riscv64 (0.2.8.1-1 to 0.2.8.1-1)
  • Migration status for guile-lib/riscv64 (0.2.8.1-1 to 0.2.8.1-1): Will attempt migration (Any information below is purely informational)
• guile-lzlib/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for guile-lzlib/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• guile-semver/riscv64 (0.1.1-3 to 0.1.1-3)
  • Migration status for guile-semver/riscv64 (0.1.1-3 to 0.1.1-3): Will attempt migration (Any information below is purely informational)
• guile-sqlite3/riscv64 (0.1.3-3 to 0.1.3-3)
  • Migration status for guile-sqlite3/riscv64 (0.1.3-3 to 0.1.3-3): Will attempt migration (Any information below is purely informational)
• guile-zlib/riscv64 (0.1.0-4 to 0.1.0-4)
  • Migration status for guile-zlib/riscv64 (0.1.0-4 to 0.1.0-4): Will attempt migration (Any information below is purely informational)
• guile-zstd/riscv64 (0.1.1-4 to 0.1.1-4)
  • Migration status for guile-zstd/riscv64 (0.1.1-4 to 0.1.1-4): 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)
• gummi/riscv64 (0.8.3+really0.8.3-2 to 0.8.3+really0.8.3-2)
  • Migration status for gummi/riscv64 (0.8.3+really0.8.3-2 to 0.8.3+really0.8.3-2): Will attempt migration (Any information below is purely informational)
• guncat/riscv64 (2.01.00-1 to 2.01.00-1)
  • Migration status for guncat/riscv64 (2.01.00-1 to 2.01.00-1): 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)
• gutenprint/riscv64 (5.3.4.20220624T01008808d602-2 to 5.3.4.20220624T01008808d602-2)
  • Migration status for gutenprint/riscv64 (5.3.4.20220624T01008808d602-2 to 5.3.4.20220624T01008808d602-2): Will attempt migration (Any information below is purely informational)
• guvcview/riscv64 (2.0.8-2.1 to 2.0.8-2.1)
  • Migration status for guvcview/riscv64 (2.0.8-2.1 to 2.0.8-2.1): Will attempt migration (Any information below is purely informational)
• gv/riscv64 (1:3.7.4-2 to 1:3.7.4-2)
  • Migration status for gv/riscv64 (1:3.7.4-2 to 1:3.7.4-2): Will attempt migration (Any information below is purely informational)
• gvars3/riscv64 (0.0~git20220105194034.62f5a78-4.1 to 0.0~git20220105194034.62f5a78-4.1)
  • Migration status for gvars3/riscv64 (0.0~git20220105194034.62f5a78-4.1 to 0.0~git20220105194034.62f5a78-4.1): Will attempt migration (Any information below is purely informational)
• gvfs/amd64 (1.54.2-1 to 1.54.2-1)
  • Migration status for gvfs/amd64 (1.54.2-1 to 1.54.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gvfs/amd64 libplist (not considered)
    • Invalidated by dependency
    • Depends: gvfs/amd64 libgcrypt20
    • Depends: gvfs/amd64 libimobiledevice
• gvfs/arm64 (1.54.2-1 to 1.54.2-1)
  • Migration status for gvfs/arm64 (1.54.2-1 to 1.54.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gvfs/arm64 libplist (not considered)
    • Invalidated by dependency
    • Depends: gvfs/arm64 libgcrypt20
    • Depends: gvfs/arm64 libimobiledevice
• gvfs/armel (1.54.2-1 to 1.54.2-1)
  • Migration status for gvfs/armel (1.54.2-1 to 1.54.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gvfs/armel libplist (not considered)
    • Invalidated by dependency
    • Depends: gvfs/armel libgcrypt20
    • Depends: gvfs/armel libimobiledevice
• gvfs/armhf (1.54.2-1 to 1.54.2-1)
  • Migration status for gvfs/armhf (1.54.2-1 to 1.54.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gvfs/armhf libplist (not considered)
    • Invalidated by dependency
    • Depends: gvfs/armhf libgcrypt20
    • Depends: gvfs/armhf libimobiledevice
• gvfs/i386 (1.54.2-1 to 1.54.2-1)
  • Migration status for gvfs/i386 (1.54.2-1 to 1.54.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gvfs/i386 libplist (not considered)
    • Invalidated by dependency
    • Depends: gvfs/i386 libgcrypt20
    • Depends: gvfs/i386 libimobiledevice
• gvfs/mips64el (1.54.2-1 to 1.54.2-1)
  • Migration status for gvfs/mips64el (1.54.2-1 to 1.54.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gvfs/mips64el libplist (not considered)
    • Invalidated by dependency
    • Depends: gvfs/mips64el libgcrypt20
    • Depends: gvfs/mips64el libimobiledevice
• gvfs/ppc64el (1.54.2-1 to 1.54.2-1)
  • Migration status for gvfs/ppc64el (1.54.2-1 to 1.54.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gvfs/ppc64el libplist (not considered)
    • Invalidated by dependency
    • Depends: gvfs/ppc64el libgcrypt20
    • Depends: gvfs/ppc64el libimobiledevice
• gvfs/s390x (1.54.2-1 to 1.54.2-1)
  • Migration status for gvfs/s390x (1.54.2-1 to 1.54.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: gvfs/s390x libplist (not considered)
    • Invalidated by dependency
    • Depends: gvfs/s390x libgcrypt20
    • Depends: gvfs/s390x libimobiledevice
• 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)
• gvpe/riscv64 (3.1-2 to 3.1-2)
  • Migration status for gvpe/riscv64 (3.1-2 to 3.1-2): 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)
• gwama/riscv64 (2.2.2+dfsg-5 to 2.2.2+dfsg-5)
  • Migration status for gwama/riscv64 (2.2.2+dfsg-5 to 2.2.2+dfsg-5): 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)
• gworkspace/riscv64 (1.0.0-1 to 1.0.0-1)
  • Migration status for gworkspace/riscv64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• 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)
• gwyddion/riscv64 (2.64-1.1 to 2.64-1.1)
  • Migration status for gwyddion/riscv64 (2.64-1.1 to 2.64-1.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)
• gxr/riscv64 (0.15.1-4.1 to 0.15.1-4.1)
  • Migration status for gxr/riscv64 (0.15.1-4.1 to 0.15.1-4.1): 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)
• h2o/riscv64 (2.2.5+dfsg2-8.1 to 2.2.5+dfsg2-8.1)
  • Migration status for h2o/riscv64 (2.2.5+dfsg2-8.1 to 2.2.5+dfsg2-8.1): Will attempt migration (Any information below is purely informational)
• h3-pg/riscv64 (4.1.3-3 to 4.1.3-3)
  • Migration status for h3-pg/riscv64 (4.1.3-3 to 4.1.3-3): Will attempt migration (Any information below is purely informational)
• h5utils/riscv64 (1.13.2-1 to 1.13.2-1)
  • Migration status for h5utils/riscv64 (1.13.2-1 to 1.13.2-1): Will attempt migration (Any information below is purely informational)
• h5z-zfp/riscv64 (1.1.1-2 to 1.1.1-2)
  • Migration status for h5z-zfp/riscv64 (1.1.1-2 to 1.1.1-2): Will attempt migration (Any information below is purely informational)
• hackrf/riscv64 (2024.02.1-2 to 2024.02.1-2)
  • Migration status for hackrf/riscv64 (2024.02.1-2 to 2024.02.1-2): Will attempt migration (Any information below is purely informational)
• hacktv/riscv64 (0+git20230104+ds-2 to 0+git20230104+ds-2)
  • Migration status for hacktv/riscv64 (0+git20230104+ds-2 to 0+git20230104+ds-2): Will attempt migration (Any information below is purely informational)
• hadori/riscv64 (1.1-1 to 1.1-1)
  • Migration status for hadori/riscv64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
• hamlib/riscv64 (4.5.5-4 to 4.5.5-4)
  • Migration status for hamlib/riscv64 (4.5.5-4 to 4.5.5-4): Will attempt migration (Any information below is purely informational)
• handbrake/riscv64 (1.7.2+ds1-1 to 1.7.2+ds1-1)
  • Migration status for handbrake/riscv64 (1.7.2+ds1-1 to 1.7.2+ds1-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)
• hannah/riscv64 (2.0.1+ds1-0.3 to 2.0.1+ds1-0.3)
  • Migration status for hannah/riscv64 (2.0.1+ds1-0.3 to 2.0.1+ds1-0.3): Will attempt migration (Any information below is purely informational)
• harfbuzz/riscv64 (8.3.0-2 to 8.3.0-2)
  • Migration status for harfbuzz/riscv64 (8.3.0-2 to 8.3.0-2): Will attempt migration (Any information below is purely informational)
• harminv/riscv64 (1.4.2-1 to 1.4.2-1)
  • Migration status for harminv/riscv64 (1.4.2-1 to 1.4.2-1): 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)
• harvest-tools/riscv64 (1.3-8 to 1.3-8)
  • Migration status for harvest-tools/riscv64 (1.3-8 to 1.3-8): 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)
• haserl/riscv64 (0.9.36-2 to 0.9.36-2)
  • Migration status for haserl/riscv64 (0.9.36-2 to 0.9.36-2): 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-cracknum/riscv64 (3.4-1 to 3.4-1)
  • Migration status for haskell-cracknum/riscv64 (3.4-1 to 3.4-1): 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-hdf5/riscv64 (1.8.11-1 to 1.8.11-1)
  • Migration status for haskell-hdf5/riscv64 (1.8.11-1 to 1.8.11-1): 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-hsopenssl/riscv64 (0.11.7.6-1 to 0.11.7.6-1)
  • Migration status for haskell-hsopenssl/riscv64 (0.11.7.6-1 to 0.11.7.6-1): 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-intern/riscv64 (0.9.5-1 to 0.9.5-1)
  • Migration status for haskell-intern/riscv64 (0.9.5-1 to 0.9.5-1): 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-libxml-sax/riscv64 (0.7.5-13 to 0.7.5-13)
  • Migration status for haskell-libxml-sax/riscv64 (0.7.5-13 to 0.7.5-13): 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-pandoc/riscv64 (3.1.3-2 to 3.1.3-2)
  • Migration status for haskell-pandoc/riscv64 (3.1.3-2 to 3.1.3-2): 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-stack/riscv64 (2.9.3.1-1 to 2.9.3.1-1)
  • Migration status for haskell-stack/riscv64 (2.9.3.1-1 to 2.9.3.1-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)
• hdf-eos4/riscv64 (2.20v1.00-1.1 to 2.20v1.00-1.1)
  • Migration status for hdf-eos4/riscv64 (2.20v1.00-1.1 to 2.20v1.00-1.1): Will attempt migration (Any information below is purely informational)
• hdf-eos5/riscv64 (2:2.0-3 to 2:2.0-3)
  • Migration status for hdf-eos5/riscv64 (2:2.0-3 to 2:2.0-3): Will attempt migration (Any information below is purely informational)
• hdf5-blosc/riscv64 (0.0~git20220616.9683f7d-5 to 0.0~git20220616.9683f7d-5)
  • Migration status for hdf5-blosc/riscv64 (0.0~git20220616.9683f7d-5 to 0.0~git20220616.9683f7d-5): Will attempt migration (Any information below is purely informational)
• hdf5-filter-plugin/riscv64 (0.0~git20221111.49e3b65-4 to 0.0~git20221111.49e3b65-4)
  • Migration status for hdf5-filter-plugin/riscv64 (0.0~git20221111.49e3b65-4 to 0.0~git20221111.49e3b65-4): Will attempt migration (Any information below is purely informational)
• hdf5/riscv64 (1.10.10+repack-3.3 to 1.10.10+repack-3.3)
  • Migration status for hdf5/riscv64 (1.10.10+repack-3.3 to 1.10.10+repack-3.3): Will attempt migration (Any information below is purely informational)
• healpix-cxx/riscv64 (3.80.0-5 to 3.80.0-5)
  • Migration status for healpix-cxx/riscv64 (3.80.0-5 to 3.80.0-5): Will attempt migration (Any information below is purely informational)
• healpix-fortran/riscv64 (3.60+ds-1 to 3.60+ds-1)
  • Migration status for healpix-fortran/riscv64 (3.60+ds-1 to 3.60+ds-1): 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)
• heaptrack/riscv64 (1.5.0+dfsg1-2 to 1.5.0+dfsg1-2)
  • Migration status for heaptrack/riscv64 (1.5.0+dfsg1-2 to 1.5.0+dfsg1-2): Will attempt migration (Any information below is purely informational)
• heimdall-flash/riscv64 (2.0.2-2 to 2.0.2-2)
  • Migration status for heimdall-flash/riscv64 (2.0.2-2 to 2.0.2-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)
• hera/riscv64 (2.0.0+git20221115.8bfdd4b+dfsg-1 to 2.0.0+git20221115.8bfdd4b+dfsg-1)
  • Migration status for hera/riscv64 (2.0.0+git20221115.8bfdd4b+dfsg-1 to 2.0.0+git20221115.8bfdd4b+dfsg-1): Will attempt migration (Any information below is purely informational)
• herbstluftwm/riscv64 (0.9.5-3 to 0.9.5-3)
  • Migration status for herbstluftwm/riscv64 (0.9.5-3 to 0.9.5-3): 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)
• heroes/riscv64 (0.21-19 to 0.21-19)
  • Migration status for heroes/riscv64 (0.21-19 to 0.21-19): 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)
• hexter/riscv64 (1.1.1-2 to 1.1.1-2)
  • Migration status for hexter/riscv64 (1.1.1-2 to 1.1.1-2): 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)
• hfst/riscv64 (3.16.0-5 to 3.16.0-5)
  • Migration status for hfst/riscv64 (3.16.0-5 to 3.16.0-5): Will attempt migration (Any information below is purely informational)
• hhsuite/riscv64 (3.3.0+ds-8 to 3.3.0+ds-8)
  • Migration status for hhsuite/riscv64 (3.3.0+ds-8 to 3.3.0+ds-8): Will attempt migration (Any information below is purely informational)
• highlight/riscv64 (4.10-1 to 4.10-1)
  • Migration status for highlight/riscv64 (4.10-1 to 4.10-1): Will attempt migration (Any information below is purely informational)
• highwayhash/riscv64 (0~git20200803.9490b14-4.1 to 0~git20200803.9490b14-4.1)
  • Migration status for highwayhash/riscv64 (0~git20200803.9490b14-4.1 to 0~git20200803.9490b14-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)
• hipercontracer/riscv64 (1.6.10-1 to 1.6.10-1)
  • Migration status for hipercontracer/riscv64 (1.6.10-1 to 1.6.10-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)
• hippotat/riscv64 (1.1.11 to 1.1.11)
  • Migration status for hippotat/riscv64 (1.1.11 to 1.1.11): 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)
• hivelytracker/riscv64 (1.9+git20221114+ds-2 to 1.9+git20221114+ds-2)
  • Migration status for hivelytracker/riscv64 (1.9+git20221114+ds-2 to 1.9+git20221114+ds-2): Will attempt migration (Any information below is purely informational)
• hivex/riscv64 (1.3.23-1 to 1.3.23-1)
  • Migration status for hivex/riscv64 (1.3.23-1 to 1.3.23-1): 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)
• hnswlib/riscv64 (0.8.0-1 to 0.8.0-1)
  • Migration status for hnswlib/riscv64 (0.8.0-1 to 0.8.0-1): Will attempt migration (Any information below is purely informational)
• hoel/riscv64 (1.4.29-1.1 to 1.4.29-1.1)
  • Migration status for hoel/riscv64 (1.4.29-1.1 to 1.4.29-1.1): Will attempt migration (Any information below is purely informational)
• hoichess/riscv64 (0.22.0-3 to 0.22.0-3)
  • Migration status for hoichess/riscv64 (0.22.0-3 to 0.22.0-3): 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)
• horgand/riscv64 (1.14-8 to 1.14-8)
  • Migration status for horgand/riscv64 (1.14-8 to 1.14-8): Will attempt migration (Any information below is purely informational)
• howardhinnant-date/riscv64 (3.0.1+ds-5 to 3.0.1+ds-5)
  • Migration status for howardhinnant-date/riscv64 (3.0.1+ds-5 to 3.0.1+ds-5): Will attempt migration (Any information below is purely informational)
• hp2xx/riscv64 (3.4.4-12 to 3.4.4-12)
  • Migration status for hp2xx/riscv64 (3.4.4-12 to 3.4.4-12): Will attempt migration (Any information below is purely informational)
• hplip/riscv64 (3.22.10+dfsg0-5 to 3.22.10+dfsg0-5)
  • Migration status for hplip/riscv64 (3.22.10+dfsg0-5 to 3.22.10+dfsg0-5): Will attempt migration (Any information below is purely informational)
• hsail-tools/riscv64 (0~20180830-1 to 0~20180830-1)
  • Migration status for hsail-tools/riscv64 (0~20180830-1 to 0~20180830-1): Will attempt migration (Any information below is purely informational)
• 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)
• ht/riscv64 (2.1.0+repack1-5 to 2.1.0+repack1-5)
  • Migration status for ht/riscv64 (2.1.0+repack1-5 to 2.1.0+repack1-5): Will attempt migration (Any information below is purely informational)
• htdig/riscv64 (1:3.2.0b6-20 to 1:3.2.0b6-20)
  • Migration status for htdig/riscv64 (1:3.2.0b6-20 to 1:3.2.0b6-20): Will attempt migration (Any information below is purely informational)
• html2text/riscv64 (2.2.3-2 to 2.2.3-2)
  • Migration status for html2text/riscv64 (2.2.3-2 to 2.2.3-2): 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)
• htmlcxx/riscv64 (0.87-4 to 0.87-4)
  • Migration status for htmlcxx/riscv64 (0.87-4 to 0.87-4): Will attempt migration (Any information below is purely informational)
• htmldoc/riscv64 (1.9.18-1 to 1.9.18-1)
  • Migration status for htmldoc/riscv64 (1.9.18-1 to 1.9.18-1): Will attempt migration (Any information below is purely informational)
• hts-nim-tools/amd64 (0.2.1-1 to 0.2.1-1)
  • Migration status for hts-nim-tools/amd64 (0.2.1-1 to 0.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
• hts-nim-tools/arm64 (0.2.1-1 to 0.2.1-1)
  • Migration status for hts-nim-tools/arm64 (0.2.1-1 to 0.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
• hts-nim-tools/armel (0.2.1-1 to 0.2.1-1)
  • Migration status for hts-nim-tools/armel (0.2.1-1 to 0.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
• hts-nim-tools/armhf (0.2.1-1 to 0.2.1-1)
  • Migration status for hts-nim-tools/armhf (0.2.1-1 to 0.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
• hts-nim-tools/i386 (0.2.1-1 to 0.2.1-1)
  • Migration status for hts-nim-tools/i386 (0.2.1-1 to 0.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
• hts-nim-tools/mips64el (0.2.1-1 to 0.2.1-1)
  • Migration status for hts-nim-tools/mips64el (0.2.1-1 to 0.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
• hts-nim-tools/ppc64el (0.2.1-1 to 0.2.1-1)
  • Migration status for hts-nim-tools/ppc64el (0.2.1-1 to 0.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
• hts-nim-tools/riscv64 (0.2.1-1 to 0.2.1-1)
  • Migration status for hts-nim-tools/riscv64 (0.2.1-1 to 0.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
• hts-nim-tools/s390x (0.2.1-1 to 0.2.1-1)
  • Migration status for hts-nim-tools/s390x (0.2.1-1 to 0.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
• httping/riscv64 (2.5-5.2 to 2.5-5.2)
  • Migration status for httping/riscv64 (2.5-5.2 to 2.5-5.2): 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)
• hub/riscv64 (2.14.2~ds1-1 to 2.14.2~ds1-1)
  • Migration status for hub/riscv64 (2.14.2~ds1-1 to 2.14.2~ds1-1): Will attempt migration (Any information below is purely informational)
• hugin/riscv64 (2023.0.0+dfsg-1 to 2023.0.0+dfsg-1)
  • Migration status for hugin/riscv64 (2023.0.0+dfsg-1 to 2023.0.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• hugs98/riscv64 (98.200609.21-7 to 98.200609.21-7)
  • Migration status for hugs98/riscv64 (98.200609.21-7 to 98.200609.21-7): Will attempt migration (Any information below is purely informational)
• hunspell/riscv64 (1.7.2+really1.7.2-10 to 1.7.2+really1.7.2-10)
  • Migration status for hunspell/riscv64 (1.7.2+really1.7.2-10 to 1.7.2+really1.7.2-10): Will attempt migration (Any information below is purely informational)
• hxtools/riscv64 (20231224-2 to 20231224-2)
  • Migration status for hxtools/riscv64 (20231224-2 to 20231224-2): 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)
• hydrogen/riscv64 (1.2.0~beta1+dfsg-1 to 1.2.0~beta1+dfsg-1)
  • Migration status for hydrogen/riscv64 (1.2.0~beta1+dfsg-1 to 1.2.0~beta1+dfsg-1): Will attempt migration (Any information below is purely informational)
• hylafax/riscv64 (3:6.0.7-9 to 3:6.0.7-9)
  • Migration status for hylafax/riscv64 (3:6.0.7-9 to 3:6.0.7-9): 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)
• hypopg/riscv64 (1.4.1-1 to 1.4.1-1)
  • Migration status for hypopg/riscv64 (1.4.1-1 to 1.4.1-1): Will attempt migration (Any information below is purely informational)
• i2pd/riscv64 (2.51.0-1 to 2.51.0-1)
  • Migration status for i2pd/riscv64 (2.51.0-1 to 2.51.0-1): Will attempt migration (Any information below is purely informational)
• i3-wm/riscv64 (4.23-1 to 4.23-1)
  • Migration status for i3-wm/riscv64 (4.23-1 to 4.23-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-chewing/riscv64 (2.0.0-1 to 2.0.0-1)
  • Migration status for ibus-chewing/riscv64 (2.0.0-1 to 2.0.0-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-libpinyin/riscv64 (1.15.7-1 to 1.15.7-1)
  • Migration status for ibus-libpinyin/riscv64 (1.15.7-1 to 1.15.7-1): 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-libzhuyin/riscv64 (1.10.3-1 to 1.10.3-1)
  • Migration status for ibus-libzhuyin/riscv64 (1.10.3-1 to 1.10.3-1): Will attempt migration (Any information below is purely informational)
• ibus-m17n/riscv64 (1.4.29-1 to 1.4.29-1)
  • Migration status for ibus-m17n/riscv64 (1.4.29-1 to 1.4.29-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)
• ical2html/riscv64 (3.0-2 to 3.0-2)
  • Migration status for ical2html/riscv64 (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
• icebreaker/riscv64 (2.2.0-1 to 2.2.0-1)
  • Migration status for icebreaker/riscv64 (2.2.0-1 to 2.2.0-1): 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)
• icecream-sundae/riscv64 (1.0.0-3 to 1.0.0-3)
  • Migration status for icecream-sundae/riscv64 (1.0.0-3 to 1.0.0-3): Will attempt migration (Any information below is purely informational)
• iceoryx/riscv64 (2.0.6+dfsg-1 to 2.0.6+dfsg-1)
  • Migration status for iceoryx/riscv64 (2.0.6+dfsg-1 to 2.0.6+dfsg-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)
• icinga2/riscv64 (2.14.2-1 to 2.14.2-1)
  • Migration status for icinga2/riscv64 (2.14.2-1 to 2.14.2-1): Will attempt migration (Any information below is purely informational)
• icmake/riscv64 (12.01.00-1 to 12.01.00-1)
  • Migration status for icmake/riscv64 (12.01.00-1 to 12.01.00-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)
• id3lib3.8.3/riscv64 (3.8.3-18 to 3.8.3-18)
  • Migration status for id3lib3.8.3/riscv64 (3.8.3-18 to 3.8.3-18): Will attempt migration (Any information below is purely informational)
• id3v2/riscv64 (0.1.12+dfsg-7 to 0.1.12+dfsg-7)
  • Migration status for id3v2/riscv64 (0.1.12+dfsg-7 to 0.1.12+dfsg-7): Will attempt migration (Any information below is purely informational)
• idba/riscv64 (1.1.3-8 to 1.1.3-8)
  • Migration status for idba/riscv64 (1.1.3-8 to 1.1.3-8): Will attempt migration (Any information below is purely informational)
• iddawc/riscv64 (1.1.9+ds-2 to 1.1.9+ds-2)
  • Migration status for iddawc/riscv64 (1.1.9+ds-2 to 1.1.9+ds-2): 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)
• ifeffit/riscv64 (2:1.2.11d-12.5 to 2:1.2.11d-12.5)
  • Migration status for ifeffit/riscv64 (2:1.2.11d-12.5 to 2:1.2.11d-12.5): Will attempt migration (Any information below is purely informational)
• ifhp/riscv64 (3.5.20-20 to 3.5.20-20)
  • Migration status for ifhp/riscv64 (3.5.20-20 to 3.5.20-20): 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-math/riscv64 (6.15.0+ds-1 to 6.15.0+ds-1)
  • Migration status for ignition-math/riscv64 (6.15.0+ds-1 to 6.15.0+ds-1): Will attempt migration (Any information below is purely informational)
• ignition-msgs/riscv64 (8.2.0+ds-1 to 8.2.0+ds-1)
  • Migration status for ignition-msgs/riscv64 (8.2.0+ds-1 to 8.2.0+ds-1): Will attempt migration (Any information below is purely informational)
• ignition-plugin/riscv64 (1.4.0+ds-1 to 1.4.0+ds-1)
  • Migration status for ignition-plugin/riscv64 (1.4.0+ds-1 to 1.4.0+ds-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)
• igor/riscv64 (1.4.0+dfsg-5 to 1.4.0+dfsg-5)
  • Migration status for igor/riscv64 (1.4.0+dfsg-5 to 1.4.0+dfsg-5): 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)
• iipimage/riscv64 (1.1-3 to 1.1-3)
  • Migration status for iipimage/riscv64 (1.1-3 to 1.1-3): Will attempt migration (Any information below is purely informational)
• ikiwiki-hosting/riscv64 (0.20220716-2 to 0.20220716-2)
  • Migration status for ikiwiki-hosting/riscv64 (0.20220716-2 to 0.20220716-2): Will attempt migration (Any information below is purely informational)
• illustrate/riscv64 (0.0+git20200923.217db48-2 to 0.0+git20200923.217db48-2)
  • Migration status for illustrate/riscv64 (0.0+git20200923.217db48-2 to 0.0+git20200923.217db48-2): Will attempt migration (Any information below is purely informational)
• 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)
• imapfilter/riscv64 (1:2.8.2+1-0.2 to 1:2.8.2+1-0.2)
  • Migration status for imapfilter/riscv64 (1:2.8.2+1-0.2 to 1:2.8.2+1-0.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)
• iminuit/riscv64 (2.24.0-3 to 2.24.0-3)
  • Migration status for iminuit/riscv64 (2.24.0-3 to 2.24.0-3): 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)
• immer/riscv64 (0.8.1+dfsg-2 to 0.8.1+dfsg-2)
  • Migration status for immer/riscv64 (0.8.1+dfsg-2 to 0.8.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• imview/riscv64 (1.1.9h-4 to 1.1.9h-4)
  • Migration status for imview/riscv64 (1.1.9h-4 to 1.1.9h-4): Will attempt migration (Any information below is purely informational)
• imx-code-signing-tool/riscv64 (3.4.0+dfsg-2 to 3.4.0+dfsg-2)
  • Migration status for imx-code-signing-tool/riscv64 (3.4.0+dfsg-2 to 3.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• incron/riscv64 (0.5.12-4 to 0.5.12-4)
  • Migration status for incron/riscv64 (0.5.12-4 to 0.5.12-4): Will attempt migration (Any information below is purely informational)
• indelible/riscv64 (1.03-6 to 1.03-6)
  • Migration status for indelible/riscv64 (1.03-6 to 1.03-6): Will attempt migration (Any information below is purely informational)
• indi-aagcloudwatcher-ng/riscv64 (1.7+20230106180155-1 to 1.7+20230106180155-1)
  • Migration status for indi-aagcloudwatcher-ng/riscv64 (1.7+20230106180155-1 to 1.7+20230106180155-1): Will attempt migration (Any information below is purely informational)
• indi-aok/riscv64 (2.0+20221222093242-1 to 2.0+20221222093242-1)
  • Migration status for indi-aok/riscv64 (2.0+20221222093242-1 to 2.0+20221222093242-1): Will attempt migration (Any information below is purely informational)
• indi-apogee/riscv64 (1.9+20221223184417-2 to 1.9+20221223184417-2)
  • Migration status for indi-apogee/riscv64 (1.9+20221223184417-2 to 1.9+20221223184417-2): Will attempt migration (Any information below is purely informational)
• indi-armadillo-platypus/riscv64 (1.0+20221226082641-2 to 1.0+20221226082641-2)
  • Migration status for indi-armadillo-platypus/riscv64 (1.0+20221226082641-2 to 1.0+20221226082641-2): Will attempt migration (Any information below is purely informational)
• indi-astrolink4/riscv64 (0.1+20221223182627-1 to 0.1+20221223182627-1)
  • Migration status for indi-astrolink4/riscv64 (0.1+20221223182627-1 to 0.1+20221223182627-1): Will attempt migration (Any information below is purely informational)
• indi-astromechfoc/riscv64 (0.2+20221223181816-1 to 0.2+20221223181816-1)
  • Migration status for indi-astromechfoc/riscv64 (0.2+20221223181816-1 to 0.2+20221223181816-1): Will attempt migration (Any information below is purely informational)
• indi-avalon/riscv64 (1.12+20221223132122-1 to 1.12+20221223132122-1)
  • Migration status for indi-avalon/riscv64 (1.12+20221223132122-1 to 1.12+20221223132122-1): Will attempt migration (Any information below is purely informational)
• indi-beefocus/riscv64 (0.1+20221222010828-1 to 0.1+20221222010828-1)
  • Migration status for indi-beefocus/riscv64 (0.1+20221222010828-1 to 0.1+20221222010828-1): Will attempt migration (Any information below is purely informational)
• indi-bresserexos2/riscv64 (1.0+20221223130124-1 to 1.0+20221223130124-1)
  • Migration status for indi-bresserexos2/riscv64 (1.0+20221223130124-1 to 1.0+20221223130124-1): Will attempt migration (Any information below is purely informational)
• indi-dreamfocuser/riscv64 (2.1+20221223125100-1 to 2.1+20221223125100-1)
  • Migration status for indi-dreamfocuser/riscv64 (2.1+20221223125100-1 to 2.1+20221223125100-1): Will attempt migration (Any information below is purely informational)
• indi-eqmod/riscv64 (1.0+20230126190232-1 to 1.0+20230126190232-1)
  • Migration status for indi-eqmod/riscv64 (1.0+20230126190232-1 to 1.0+20230126190232-1): Will attempt migration (Any information below is purely informational)
• indi-ffmv/riscv64 (0.3+20221223120905-2 to 0.3+20221223120905-2)
  • Migration status for indi-ffmv/riscv64 (0.3+20221223120905-2 to 0.3+20221223120905-2): Will attempt migration (Any information below is purely informational)
• indi-fli/riscv64 (1.5+20221225141318-1 to 1.5+20221225141318-1)
  • Migration status for indi-fli/riscv64 (1.5+20221225141318-1 to 1.5+20221225141318-1): Will attempt migration (Any information below is purely informational)
• indi-gige/riscv64 (0.1+20221223115700-2 to 0.1+20221223115700-2)
  • Migration status for indi-gige/riscv64 (0.1+20221223115700-2 to 0.1+20221223115700-2): 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-gpsd/riscv64 (0.5+20221222000619-1 to 0.5+20221222000619-1)
  • Migration status for indi-gpsd/riscv64 (0.5+20221222000619-1 to 0.5+20221222000619-1): Will attempt migration (Any information below is purely informational)
• indi-gpsnmea/riscv64 (0.2+20221223114018-1 to 0.2+20221223114018-1)
  • Migration status for indi-gpsnmea/riscv64 (0.2+20221223114018-1 to 0.2+20221223114018-1): Will attempt migration (Any information below is purely informational)
• indi-limesdr/riscv64 (1.4+20221223110308-1 to 1.4+20221223110308-1)
  • Migration status for indi-limesdr/riscv64 (1.4+20221223110308-1 to 1.4+20221223110308-1): Will attempt migration (Any information below is purely informational)
• indi-maxdomeii/riscv64 (1.3+20221223105522-1 to 1.3+20221223105522-1)
  • Migration status for indi-maxdomeii/riscv64 (1.3+20221223105522-1 to 1.3+20221223105522-1): Will attempt migration (Any information below is purely informational)
• indi-mgen/riscv64 (0.1+20221222184336-1 to 0.1+20221222184336-1)
  • Migration status for indi-mgen/riscv64 (0.1+20221222184336-1 to 0.1+20221222184336-1): Will attempt migration (Any information below is purely informational)
• indi-nexdome/riscv64 (1.5+20221222183051-1 to 1.5+20221222183051-1)
  • Migration status for indi-nexdome/riscv64 (1.5+20221222183051-1 to 1.5+20221222183051-1): Will attempt migration (Any information below is purely informational)
• indi-nightscape/riscv64 (1.0.6+20221222181314-2 to 1.0.6+20221222181314-2)
  • Migration status for indi-nightscape/riscv64 (1.0.6+20221222181314-2 to 1.0.6+20221222181314-2): Will attempt migration (Any information below is purely informational)
• indi-orion-ssg3/riscv64 (0.1+20221222180647-2 to 0.1+20221222180647-2)
  • Migration status for indi-orion-ssg3/riscv64 (0.1+20221222180647-2 to 0.1+20221222180647-2): Will attempt migration (Any information below is purely informational)
• indi-rtklib/riscv64 (1.0+20221222172722-1 to 1.0+20221222172722-1)
  • Migration status for indi-rtklib/riscv64 (1.0+20221222172722-1 to 1.0+20221222172722-1): Will attempt migration (Any information below is purely informational)
• indi-shelyak/riscv64 (1.0+20221222171819-1 to 1.0+20221222171819-1)
  • Migration status for indi-shelyak/riscv64 (1.0+20221222171819-1 to 1.0+20221222171819-1): Will attempt migration (Any information below is purely informational)
• indi-spectracyber/riscv64 (1.3+20221222164952-1 to 1.3+20221222164952-1)
  • Migration status for indi-spectracyber/riscv64 (1.3+20221222164952-1 to 1.3+20221222164952-1): Will attempt migration (Any information below is purely informational)
• indi-starbook-ten/riscv64 (0.1-2 to 0.1-2)
  • Migration status for indi-starbook-ten/riscv64 (0.1-2 to 0.1-2): Will attempt migration (Any information below is purely informational)
• indi-starbook/riscv64 (0.8+20221222163625-1 to 0.8+20221222163625-1)
  • Migration status for indi-starbook/riscv64 (0.8+20221222163625-1 to 0.8+20221222163625-1): Will attempt migration (Any information below is purely informational)
• indi-sx/riscv64 (1.16+20221222162728-2 to 1.16+20221222162728-2)
  • Migration status for indi-sx/riscv64 (1.16+20221222162728-2 to 1.16+20221222162728-2): Will attempt migration (Any information below is purely informational)
• indi-talon6/riscv64 (2.0+20221222160901-1 to 2.0+20221222160901-1)
  • Migration status for indi-talon6/riscv64 (2.0+20221222160901-1 to 2.0+20221222160901-1): 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)
• indi-weewx-json/riscv64 (1.0-1 to 1.0-1)
  • Migration status for indi-weewx-json/riscv64 (1.0-1 to 1.0-1): Will attempt migration (Any information below is purely informational)
• indi/riscv64 (1.9.9+dfsg-3 to 1.9.9+dfsg-3)
  • Migration status for indi/riscv64 (1.9.9+dfsg-3 to 1.9.9+dfsg-3): 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)
• indigo/riscv64 (1.2.3-3.1 to 1.2.3-3.1)
  • Migration status for indigo/riscv64 (1.2.3-3.1 to 1.2.3-3.1): Will attempt migration (Any information below is purely informational)
• inhomog/riscv64 (0.1.9.2-1 to 0.1.9.2-1)
  • Migration status for inhomog/riscv64 (0.1.9.2-1 to 0.1.9.2-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)
• inkscape/riscv64 (1.2.2-3 to 1.2.2-3)
  • Migration status for inkscape/riscv64 (1.2.2-3 to 1.2.2-3): Will attempt migration (Any information below is purely informational)
• innoextract/riscv64 (1.9-0.1 to 1.9-0.1)
  • Migration status for innoextract/riscv64 (1.9-0.1 to 1.9-0.1): 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)
• inputplug/riscv64 (0.4.0-4 to 0.4.0-4)
  • Migration status for inputplug/riscv64 (0.4.0-4 to 0.4.0-4): 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)
• inspircd/riscv64 (3.17.0-1 to 3.17.0-1)
  • Migration status for inspircd/riscv64 (3.17.0-1 to 3.17.0-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)
• intel2gas/riscv64 (1.3.3-19 to 1.3.3-19)
  • Migration status for intel2gas/riscv64 (1.3.3-19 to 1.3.3-19): Will attempt migration (Any information below is purely informational)
• interception-tools/riscv64 (0.6.8-3 to 0.6.8-3)
  • Migration status for interception-tools/riscv64 (0.6.8-3 to 0.6.8-3): Will attempt migration (Any information below is purely informational)
• invada-studio-plugins-lv2/riscv64 (1.2.0+repack0-9 to 1.2.0+repack0-9)
  • Migration status for invada-studio-plugins-lv2/riscv64 (1.2.0+repack0-9 to 1.2.0+repack0-9): Will attempt migration (Any information below is purely informational)
• inventor/riscv64 (2.1.5-10+dfsg-2.1 to 2.1.5-10+dfsg-2.1)
  • Migration status for inventor/riscv64 (2.1.5-10+dfsg-2.1 to 2.1.5-10+dfsg-2.1): Will attempt migration (Any information below is purely informational)
• ioquake3/riscv64 (1.36+u20240217.7d711f8+dfsg-1 to 1.36+u20240217.7d711f8+dfsg-1)
  • Migration status for ioquake3/riscv64 (1.36+u20240217.7d711f8+dfsg-1 to 1.36+u20240217.7d711f8+dfsg-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)
• ip4r/riscv64 (2.4.2-2 to 2.4.2-2)
  • Migration status for ip4r/riscv64 (2.4.2-2 to 2.4.2-2): Will attempt migration (Any information below is purely informational)
• ipe-tools/riscv64 (1:7.2.24.1-3.1 to 1:7.2.24.1-3.1)
  • Migration status for ipe-tools/riscv64 (1:7.2.24.1-3.1 to 1:7.2.24.1-3.1): 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)
• iptstate/riscv64 (2.2.7-0.1 to 2.2.7-0.1)
  • Migration status for iptstate/riscv64 (2.2.7-0.1 to 2.2.7-0.1): 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)
• iraf-mscred/riscv64 (5.05+2018.07.09-3 to 5.05+2018.07.09-3)
  • Migration status for iraf-mscred/riscv64 (5.05+2018.07.09-3 to 5.05+2018.07.09-3): Will attempt migration (Any information below is purely informational)
• iraf-rvsao/riscv64 (2.8.5-2 to 2.8.5-2)
  • Migration status for iraf-rvsao/riscv64 (2.8.5-2 to 2.8.5-2): Will attempt migration (Any information below is purely informational)
• iraf-sptable/riscv64 (1.0~pre20180612-3 to 1.0~pre20180612-3)
  • Migration status for iraf-sptable/riscv64 (1.0~pre20180612-3 to 1.0~pre20180612-3): Will attempt migration (Any information below is purely informational)
• iraf-st4gem/riscv64 (1.0+ds-3 to 1.0+ds-3)
  • Migration status for iraf-st4gem/riscv64 (1.0+ds-3 to 1.0+ds-3): Will attempt migration (Any information below is purely informational)
• iraf-xdimsum/riscv64 (2003.01.24-2 to 2003.01.24-2)
  • Migration status for iraf-xdimsum/riscv64 (2003.01.24-2 to 2003.01.24-2): Will attempt migration (Any information below is purely informational)
• iraf/riscv64 (2.18-1 to 2.18-1)
  • Migration status for iraf/riscv64 (2.18-1 to 2.18-1): Will attempt migration (Any information below is purely informational)
• ircmarkers/riscv64 (0.16-1 to 0.16-1)
  • Migration status for ircmarkers/riscv64 (0.16-1 to 0.16-1): Will attempt migration (Any information below is purely informational)
• irony-mode/riscv64 (1.6.0-2 to 1.6.0-2)
  • Migration status for irony-mode/riscv64 (1.6.0-2 to 1.6.0-2): 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)
• irssi-plugin-xmpp/riscv64 (0.54+git20191101+c13fa5-2 to 0.54+git20191101+c13fa5-2)
  • Migration status for irssi-plugin-xmpp/riscv64 (0.54+git20191101+c13fa5-2 to 0.54+git20191101+c13fa5-2): Will attempt migration (Any information below is purely informational)
• irstlm/riscv64 (6.00.05-4.1 to 6.00.05-4.1)
  • Migration status for irstlm/riscv64 (6.00.05-4.1 to 6.00.05-4.1): Will attempt migration (Any information below is purely informational)
• isc-kea/riscv64 (2.4.1-3 to 2.4.1-3)
  • Migration status for isc-kea/riscv64 (2.4.1-3 to 2.4.1-3): Will attempt migration (Any information below is purely informational)
• ismrmrd/riscv64 (1.8.0-2 to 1.8.0-2)
  • Migration status for ismrmrd/riscv64 (1.8.0-2 to 1.8.0-2): 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)
• iva/riscv64 (1.0.11+ds-5 to 1.0.11+ds-5)
  • Migration status for iva/riscv64 (1.0.11+ds-5 to 1.0.11+ds-5): Will attempt migration (Any information below is purely informational)
• iverilog/riscv64 (12.0-2 to 12.0-2)
  • Migration status for iverilog/riscv64 (12.0-2 to 12.0-2): Will attempt migration (Any information below is purely informational)
• ivtools/riscv64 (2.0.11d.a1-3 to 2.0.11d.a1-3)
  • Migration status for ivtools/riscv64 (2.0.11d.a1-3 to 2.0.11d.a1-3): 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)
• j4-dmenu-desktop/riscv64 (2.16-1.1 to 2.16-1.1)
  • Migration status for j4-dmenu-desktop/riscv64 (2.16-1.1 to 2.16-1.1): Will attempt migration (Any information below is purely informational)
• jaaa/riscv64 (0.9.2-1 to 0.9.2-1)
  • Migration status for jaaa/riscv64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• jack-delay/riscv64 (0.4.2-1 to 0.4.2-1)
  • Migration status for jack-delay/riscv64 (0.4.2-1 to 0.4.2-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)
• jags/riscv64 (4.3.2-1 to 4.3.2-1)
  • Migration status for jags/riscv64 (4.3.2-1 to 4.3.2-1): 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)
• jamin/riscv64 (0.98.9~git20170111~199091~repack1-2 to 0.98.9~git20170111~199091~repack1-2)
  • Migration status for jamin/riscv64 (0.98.9~git20170111~199091~repack1-2 to 0.98.9~git20170111~199091~repack1-2): Will attempt migration (Any information below is purely informational)
• janest-ocaml-compiler-libs/riscv64 (0.12.4-4 to 0.12.4-4)
  • Migration status for janest-ocaml-compiler-libs/riscv64 (0.12.4-4 to 0.12.4-4): Will attempt migration (Any information below is purely informational)
• janus/riscv64 (1.1.2-1 to 1.1.2-1)
  • Migration status for janus/riscv64 (1.1.2-1 to 1.1.2-1): Will attempt migration (Any information below is purely informational)
• japa/riscv64 (0.9.4-1 to 0.9.4-1)
  • Migration status for japa/riscv64 (0.9.4-1 to 0.9.4-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)
• java-common/riscv64 (0.75 to 0.75)
  • Migration status for java-common/riscv64 (0.75 to 0.75): Will attempt migration (Any information below is purely informational)
• java-gnome/riscv64 (4.1.3-10 to 4.1.3-10)
  • Migration status for java-gnome/riscv64 (4.1.3-10 to 4.1.3-10): 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)
• jbig2enc/riscv64 (0.29-2.1 to 0.29-2.1)
  • Migration status for jbig2enc/riscv64 (0.29-2.1 to 0.29-2.1): Will attempt migration (Any information below is purely informational)
• jblas/riscv64 (1.2.5+dfsg-1 to 1.2.5+dfsg-1)
  • Migration status for jblas/riscv64 (1.2.5+dfsg-1 to 1.2.5+dfsg-1): Will attempt migration (Any information below is purely informational)
• jconvolver/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for jconvolver/riscv64 (1.1.0-2 to 1.1.0-2): 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)
• jeex/riscv64 (12.0.4-1.1 to 12.0.4-1.1)
  • Migration status for jeex/riscv64 (12.0.4-1.1 to 12.0.4-1.1): Will attempt migration (Any information below is purely informational)
• jellyfish/riscv64 (2.3.1-3 to 2.3.1-3)
  • Migration status for jellyfish/riscv64 (2.3.1-3 to 2.3.1-3): Will attempt migration (Any information below is purely informational)
• jellyfish1/riscv64 (1.1.11-9 to 1.1.11-9)
  • Migration status for jellyfish1/riscv64 (1.1.11-9 to 1.1.11-9): Will attempt migration (Any information below is purely informational)
• jemalloc/riscv64 (5.3.0-2 to 5.3.0-2)
  • Migration status for jemalloc/riscv64 (5.3.0-2 to 5.3.0-2): 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)
• jigdo/riscv64 (0.8.2-1 to 0.8.2-1)
  • Migration status for jigdo/riscv64 (0.8.2-1 to 0.8.2-1): 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)
• jkmeter/riscv64 (0.9.0-1 to 0.9.0-1)
  • Migration status for jkmeter/riscv64 (0.9.0-1 to 0.9.0-1): 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)
• jmeters/riscv64 (0.4.5-1 to 0.4.5-1)
  • Migration status for jmeters/riscv64 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
• jmtpfs/riscv64 (0.5-4 to 0.5-4)
  • Migration status for jmtpfs/riscv64 (0.5-4 to 0.5-4): Will attempt migration (Any information below is purely informational)
• jnoisemeter/riscv64 (0.4.1-1 to 0.4.1-1)
  • Migration status for jnoisemeter/riscv64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• john/riscv64 (1.9.0-2 to 1.9.0-2)
  • Migration status for john/riscv64 (1.9.0-2 to 1.9.0-2): Will attempt migration (Any information below is purely informational)
• jpathwatch/riscv64 (0.95-5 to 0.95-5)
  • Migration status for jpathwatch/riscv64 (0.95-5 to 0.95-5): Will attempt migration (Any information below is purely informational)
• jpegqs/riscv64 (1.20210408-3 to 1.20210408-3)
  • Migration status for jpegqs/riscv64 (1.20210408-3 to 1.20210408-3): Will attempt migration (Any information below is purely informational)
• jpy/riscv64 (0.13.0-1 to 0.13.0-1)
  • Migration status for jpy/riscv64 (0.13.0-1 to 0.13.0-1): 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-ocamlbuild/amd64 (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/amd64 (5.0-2 to 5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml-ocamlbuild/amd64 ocamlbuild (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml-ocamlbuild/amd64 eliom/amd64
• js-of-ocaml-ocamlbuild/arm64 (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/arm64 (5.0-2 to 5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml-ocamlbuild/arm64 ocamlbuild (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml-ocamlbuild/arm64 eliom/arm64
• js-of-ocaml-ocamlbuild/armel (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/armel (5.0-2 to 5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml-ocamlbuild/armel ocamlbuild (not considered)
    • Invalidated by dependency
• js-of-ocaml-ocamlbuild/armhf (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/armhf (5.0-2 to 5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml-ocamlbuild/armhf ocamlbuild (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml-ocamlbuild/armhf eliom/armhf
• js-of-ocaml-ocamlbuild/i386 (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/i386 (5.0-2 to 5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml-ocamlbuild/i386 ocamlbuild (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml-ocamlbuild/i386 eliom/i386
• js-of-ocaml-ocamlbuild/mips64el (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/mips64el (5.0-2 to 5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml-ocamlbuild/mips64el ocamlbuild (not considered)
    • Invalidated by dependency
• js-of-ocaml-ocamlbuild/ppc64el (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/ppc64el (5.0-2 to 5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml-ocamlbuild/ppc64el ocamlbuild (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml-ocamlbuild/ppc64el eliom/ppc64el
• js-of-ocaml-ocamlbuild/riscv64 (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/riscv64 (5.0-2 to 5.0-2): Will attempt migration (Any information below is purely informational)
• js-of-ocaml-ocamlbuild/s390x (5.0-2 to 5.0-2)
  • Migration status for js-of-ocaml-ocamlbuild/s390x (5.0-2 to 5.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: js-of-ocaml-ocamlbuild/s390x ocamlbuild (not considered)
    • Invalidated by dependency
    • Implicit dependency: js-of-ocaml-ocamlbuild/s390x eliom/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)
• jsonm/riscv64 (1.0.2-2 to 1.0.2-2)
  • Migration status for jsonm/riscv64 (1.0.2-2 to 1.0.2-2): Will attempt migration (Any information below is purely informational)
• jsonnet/riscv64 (0.20.0+ds-1 to 0.20.0+ds-1)
  • Migration status for jsonnet/riscv64 (0.20.0+ds-1 to 0.20.0+ds-1): Will attempt migration (Any information below is purely informational)
• jsquery/riscv64 (1.2-1 to 1.2-1)
  • Migration status for jsquery/riscv64 (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• jss/riscv64 (5.5.0-1 to 5.5.0-1)
  • Migration status for jss/riscv64 (5.5.0-1 to 5.5.0-1): Will attempt migration (Any information below is purely informational)
• jssc/riscv64 (2.8.0-4 to 2.8.0-4)
  • Migration status for jssc/riscv64 (2.8.0-4 to 2.8.0-4): Will attempt migration (Any information below is purely informational)
• jst-config/riscv64 (0.16.0-3 to 0.16.0-3)
  • Migration status for jst-config/riscv64 (0.16.0-3 to 0.16.0-3): 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)
• jsusfx/riscv64 (0.4.0-5 to 0.4.0-5)
  • Migration status for jsusfx/riscv64 (0.4.0-5 to 0.4.0-5): 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)
• jxgrabkey/riscv64 (0.3.2-10 to 0.3.2-10)
  • Migration status for jxgrabkey/riscv64 (0.3.2-10 to 0.3.2-10): Will attempt migration (Any information below is purely informational)
• jzmq/riscv64 (3.1.0-16 to 3.1.0-16)
  • Migration status for jzmq/riscv64 (3.1.0-16 to 3.1.0-16): Will attempt migration (Any information below is purely informational)
• k3b/riscv64 (23.08.3-1 to 23.08.3-1)
  • Migration status for k3b/riscv64 (23.08.3-1 to 23.08.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)
• kaidan/riscv64 (0.9.1-3 to 0.9.1-3)
  • Migration status for kaidan/riscv64 (0.9.1-3 to 0.9.1-3): Will attempt migration (Any information below is purely informational)
• kakoune/riscv64 (2022.10.31-2 to 2022.10.31-2)
  • Migration status for kakoune/riscv64 (2022.10.31-2 to 2022.10.31-2): 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)
• kalign/riscv64 (1:3.4.0-1 to 1:3.4.0-1)
  • Migration status for kalign/riscv64 (1:3.4.0-1 to 1:3.4.0-1): 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)
• kallisto/riscv64 (0.48.0+dfsg-4 to 0.48.0+dfsg-4)
  • Migration status for kallisto/riscv64 (0.48.0+dfsg-4 to 0.48.0+dfsg-4): 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)
• kasts/riscv64 (23.08.4-1 to 23.08.4-1)
  • Migration status for kasts/riscv64 (23.08.4-1 to 23.08.4-1): Will attempt migration (Any information below is purely informational)
• kasumi/riscv64 (2.5+debian1-1 to 2.5+debian1-1)
  • Migration status for kasumi/riscv64 (2.5+debian1-1 to 2.5+debian1-1): 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)
• kawari8/riscv64 (8.2.8-11 to 8.2.8-11)
  • Migration status for kawari8/riscv64 (8.2.8-11 to 8.2.8-11): 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)
• kball/riscv64 (0.0.20041216-11 to 0.0.20041216-11)
  • Migration status for kball/riscv64 (0.0.20041216-11 to 0.0.20041216-11): 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)
• kcemu/riscv64 (0.5.2+dfsg-2 to 0.5.2+dfsg-2)
  • Migration status for kcemu/riscv64 (0.5.2+dfsg-2 to 0.5.2+dfsg-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)
• kdc2tiff/riscv64 (0.35-10.2 to 0.35-10.2)
  • Migration status for kdc2tiff/riscv64 (0.35-10.2 to 0.35-10.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)
• kdiskmark/riscv64 (3.1.3+ds-4 to 3.1.3+ds-4)
  • Migration status for kdiskmark/riscv64 (3.1.3+ds-4 to 3.1.3+ds-4): 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)
• 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)
• 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)
• kget/riscv64 (4:23.08.3-1 to 4:23.08.3-1)
  • Migration status for kget/riscv64 (4:23.08.3-1 to 4:23.08.3-1): Will attempt migration (Any information below is purely informational)
• kglobalaccel/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kglobalaccel/riscv64 (5.115.0-2 to 5.115.0-2): 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)
• kgpg/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kgpg/riscv64 (4:22.12.3-1 to 4:22.12.3-1): Will attempt migration (Any information below is purely informational)
• kguiaddons/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kguiaddons/riscv64 (5.115.0-2 to 5.115.0-2): 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)
• kim-api/riscv64 (2.3.0-1 to 2.3.0-1)
  • Migration status for kim-api/riscv64 (2.3.0-1 to 2.3.0-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)
• kineticstools/riscv64 (0.6.1+git20220223.1326a4d+dfsg-2 to 0.6.1+git20220223.1326a4d+dfsg-2)
  • Migration status for kineticstools/riscv64 (0.6.1+git20220223.1326a4d+dfsg-2 to 0.6.1+git20220223.1326a4d+dfsg-2): 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)
• kissplice/riscv64 (2.6.2-3 to 2.6.2-3)
  • Migration status for kissplice/riscv64 (2.6.2-3 to 2.6.2-3): 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)
• kivy/riscv64 (2.2.1-3 to 2.2.1-3)
  • Migration status for kivy/riscv64 (2.2.1-3 to 2.2.1-3): Will attempt migration (Any information below is purely informational)
• kiwisolver/riscv64 (1.4.5-1 to 1.4.5-1)
  • Migration status for kiwisolver/riscv64 (1.4.5-1 to 1.4.5-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)
• kleborate/riscv64 (2.4.1-3 to 2.4.1-3)
  • Migration status for kleborate/riscv64 (2.4.1-3 to 2.4.1-3): Will attempt migration (Any information below is purely informational)
• kleopatra/riscv64 (4:22.12.3-2 to 4:22.12.3-2)
  • Migration status for kleopatra/riscv64 (4:22.12.3-2 to 4:22.12.3-2): 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)
• klick/riscv64 (0.12.2-5 to 0.12.2-5)
  • Migration status for klick/riscv64 (0.12.2-5 to 0.12.2-5): 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)
• klustakwik/riscv64 (3.0.2+ds-2 to 3.0.2+ds-2)
  • Migration status for klustakwik/riscv64 (3.0.2+ds-2 to 3.0.2+ds-2): 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)
• kmail-account-wizard/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kmail-account-wizard/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)
• kmc/riscv64 (3.2.4+dfsg-1 to 3.2.4+dfsg-1)
  • Migration status for kmc/riscv64 (3.2.4+dfsg-1 to 3.2.4+dfsg-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)
• kmer/riscv64 (0~20150903+r2013-8 to 0~20150903+r2013-8)
  • Migration status for kmer/riscv64 (0~20150903+r2013-8 to 0~20150903+r2013-8): 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)
• kmscube/riscv64 (0.0.0~git20210103-1 to 0.0.0~git20210103-1)
  • Migration status for kmscube/riscv64 (0.0.0~git20210103-1 to 0.0.0~git20210103-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)
• knxd/riscv64 (0.14.54.1 to 0.14.54.1)
  • Migration status for knxd/riscv64 (0.14.54.1 to 0.14.54.1): Will attempt migration (Any information below is purely informational)
• kobodeluxe/riscv64 (0.5.1-10 to 0.5.1-10)
  • Migration status for kobodeluxe/riscv64 (0.5.1-10 to 0.5.1-10): Will attempt migration (Any information below is purely informational)
• kodi-audiodecoder-fluidsynth/riscv64 (20.2.1+ds1-2 to 20.2.1+ds1-2)
  • Migration status for kodi-audiodecoder-fluidsynth/riscv64 (20.2.1+ds1-2 to 20.2.1+ds1-2): Will attempt migration (Any information below is purely informational)
• kodi-audiodecoder-openmpt/riscv64 (20.2.0+ds1-2 to 20.2.0+ds1-2)
  • Migration status for kodi-audiodecoder-openmpt/riscv64 (20.2.0+ds1-2 to 20.2.0+ds1-2): Will attempt migration (Any information below is purely informational)
• kodi-audiodecoder-sidplay/riscv64 (20.2.0+ds1-2 to 20.2.0+ds1-2)
  • Migration status for kodi-audiodecoder-sidplay/riscv64 (20.2.0+ds1-2 to 20.2.0+ds1-2): Will attempt migration (Any information below is purely informational)
• kodi-audioencoder-flac/riscv64 (20.2.0+ds1-2 to 20.2.0+ds1-2)
  • Migration status for kodi-audioencoder-flac/riscv64 (20.2.0+ds1-2 to 20.2.0+ds1-2): Will attempt migration (Any information below is purely informational)
• kodi-audioencoder-lame/riscv64 (20.3.0+ds1-2 to 20.3.0+ds1-2)
  • Migration status for kodi-audioencoder-lame/riscv64 (20.3.0+ds1-2 to 20.3.0+ds1-2): Will attempt migration (Any information below is purely informational)
• kodi-audioencoder-vorbis/riscv64 (20.2.0+ds1-2 to 20.2.0+ds1-2)
  • Migration status for kodi-audioencoder-vorbis/riscv64 (20.2.0+ds1-2 to 20.2.0+ds1-2): Will attempt migration (Any information below is purely informational)
• kodi-audioencoder-wav/riscv64 (20.2.0-2 to 20.2.0-2)
  • Migration status for kodi-audioencoder-wav/riscv64 (20.2.0-2 to 20.2.0-2): Will attempt migration (Any information below is purely informational)
• kodi-game-libretro/riscv64 (20.2.4-2 to 20.2.4-2)
  • Migration status for kodi-game-libretro/riscv64 (20.2.4-2 to 20.2.4-2): Will attempt migration (Any information below is purely informational)
• kodi-imagedecoder-heif/riscv64 (20.1.0+ds1-3 to 20.1.0+ds1-3)
  • Migration status for kodi-imagedecoder-heif/riscv64 (20.1.0+ds1-3 to 20.1.0+ds1-3): Will attempt migration (Any information below is purely informational)
• kodi-imagedecoder-raw/riscv64 (20.1.0+ds1-2 to 20.1.0+ds1-2)
  • Migration status for kodi-imagedecoder-raw/riscv64 (20.1.0+ds1-2 to 20.1.0+ds1-2): Will attempt migration (Any information below is purely informational)
• kodi-inputstream-adaptive/riscv64 (20.3.18+ds-1 to 20.3.18+ds-1)
  • Migration status for kodi-inputstream-adaptive/riscv64 (20.3.18+ds-1 to 20.3.18+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-inputstream-rtmp/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1)
  • Migration status for kodi-inputstream-rtmp/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-peripheral-xarcade/riscv64 (20.1.3-1 to 20.1.3-1)
  • Migration status for kodi-peripheral-xarcade/riscv64 (20.1.3-1 to 20.1.3-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-argustv/riscv64 (20.5.0+ds1-1 to 20.5.0+ds1-1)
  • Migration status for kodi-pvr-argustv/riscv64 (20.5.0+ds1-1 to 20.5.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-dvblink/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-dvblink/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-dvbviewer/riscv64 (20.4.0+ds1-1 to 20.4.0+ds1-1)
  • Migration status for kodi-pvr-dvbviewer/riscv64 (20.4.0+ds1-1 to 20.4.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-filmon/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-filmon/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-hdhomerun/riscv64 (20.4.0+ds1-1 to 20.4.0+ds1-1)
  • Migration status for kodi-pvr-hdhomerun/riscv64 (20.4.0+ds1-1 to 20.4.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-hts/riscv64 (20.7.2+ds-1 to 20.7.2+ds-1)
  • Migration status for kodi-pvr-hts/riscv64 (20.7.2+ds-1 to 20.7.2+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-iptvsimple/riscv64 (20.13.0+ds-1 to 20.13.0+ds-1)
  • Migration status for kodi-pvr-iptvsimple/riscv64 (20.13.0+ds-1 to 20.13.0+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-mediaportal-tvserver/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-mediaportal-tvserver/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-mythtv/riscv64 (20.6.9+ds-1 to 20.6.9+ds-1)
  • Migration status for kodi-pvr-mythtv/riscv64 (20.6.9+ds-1 to 20.6.9+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-nextpvr/riscv64 (20.4.3+ds-1 to 20.4.3+ds-1)
  • Migration status for kodi-pvr-nextpvr/riscv64 (20.4.3+ds-1 to 20.4.3+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-njoy/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-njoy/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-octonet/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1)
  • Migration status for kodi-pvr-octonet/riscv64 (20.3.0+ds1-1 to 20.3.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-pctv/riscv64 (20.4.0+ds1-1 to 20.4.0+ds1-1)
  • Migration status for kodi-pvr-pctv/riscv64 (20.4.0+ds1-1 to 20.4.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-sledovanitv-cz/riscv64 (20.7.0+ds-1 to 20.7.0+ds-1)
  • Migration status for kodi-pvr-sledovanitv-cz/riscv64 (20.7.0+ds-1 to 20.7.0+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-teleboy/riscv64 (20.3.4+ds-1 to 20.3.4+ds-1)
  • Migration status for kodi-pvr-teleboy/riscv64 (20.3.4+ds-1 to 20.3.4+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-vbox/riscv64 (20.4.2-1 to 20.4.2-1)
  • Migration status for kodi-pvr-vbox/riscv64 (20.4.2-1 to 20.4.2-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-vdr-vnsi/riscv64 (20.4.1+ds-1 to 20.4.1+ds-1)
  • Migration status for kodi-pvr-vdr-vnsi/riscv64 (20.4.1+ds-1 to 20.4.1+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-vuplus/riscv64 (20.5.1+ds-1 to 20.5.1+ds-1)
  • Migration status for kodi-pvr-vuplus/riscv64 (20.5.1+ds-1 to 20.5.1+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-wmc/riscv64 (20.3.0-1 to 20.3.0-1)
  • Migration status for kodi-pvr-wmc/riscv64 (20.3.0-1 to 20.3.0-1): Will attempt migration (Any information below is purely informational)
• kodi-pvr-zattoo/riscv64 (20.3.14+ds-1 to 20.3.14+ds-1)
  • Migration status for kodi-pvr-zattoo/riscv64 (20.3.14+ds-1 to 20.3.14+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-screensaver-asteroids/riscv64 (20.2.0+ds-1 to 20.2.0+ds-1)
  • Migration status for kodi-screensaver-asteroids/riscv64 (20.2.0+ds-1 to 20.2.0+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-screensaver-biogenesis/riscv64 (20.1.0-2 to 20.1.0-2)
  • Migration status for kodi-screensaver-biogenesis/riscv64 (20.1.0-2 to 20.1.0-2): Will attempt migration (Any information below is purely informational)
• kodi-screensaver-greynetic/riscv64 (20.2.0+ds-1 to 20.2.0+ds-1)
  • Migration status for kodi-screensaver-greynetic/riscv64 (20.2.0+ds-1 to 20.2.0+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-screensaver-pingpong/riscv64 (20.2.0+ds-1 to 20.2.0+ds-1)
  • Migration status for kodi-screensaver-pingpong/riscv64 (20.2.0+ds-1 to 20.2.0+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-screensaver-pyro/riscv64 (20.1.0-2 to 20.1.0-2)
  • Migration status for kodi-screensaver-pyro/riscv64 (20.1.0-2 to 20.1.0-2): Will attempt migration (Any information below is purely informational)
• kodi-screensaver-shadertoy/riscv64 (20.2.0+ds-1 to 20.2.0+ds-1)
  • Migration status for kodi-screensaver-shadertoy/riscv64 (20.2.0+ds-1 to 20.2.0+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-vfs-libarchive/riscv64 (20.3.0+ds-1 to 20.3.0+ds-1)
  • Migration status for kodi-vfs-libarchive/riscv64 (20.3.0+ds-1 to 20.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-vfs-sftp/riscv64 (20.2.0+ds-1 to 20.2.0+ds-1)
  • Migration status for kodi-vfs-sftp/riscv64 (20.2.0+ds-1 to 20.2.0+ds-1): Will attempt migration (Any information below is purely informational)
• kodi-visualization-fishbmc/riscv64 (20.2.0+ds1-1 to 20.2.0+ds1-1)
  • Migration status for kodi-visualization-fishbmc/riscv64 (20.2.0+ds1-1 to 20.2.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-visualization-pictureit/riscv64 (20.2.0+ds1-1 to 20.2.0+ds1-1)
  • Migration status for kodi-visualization-pictureit/riscv64 (20.2.0+ds1-1 to 20.2.0+ds1-1): Will attempt migration (Any information below is purely informational)
• kodi-visualization-spectrum/riscv64 (20.2.0+ds1-1 to 20.2.0+ds1-1)
  • Migration status for kodi-visualization-spectrum/riscv64 (20.2.0+ds1-1 to 20.2.0+ds1-1): Will attempt migration (Any information below is purely informational)
• 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)
• 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)
• komi/riscv64 (1.04-5.1 to 1.04-5.1)
  • Migration status for komi/riscv64 (1.04-5.1 to 1.04-5.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)
• komposter/riscv64 (0+git20201216+ds-3 to 0+git20201216+ds-3)
  • Migration status for komposter/riscv64 (0+git20201216+ds-3 to 0+git20201216+ds-3): 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)
• konwert/riscv64 (1.8-13.2 to 1.8-13.2)
  • Migration status for konwert/riscv64 (1.8-13.2 to 1.8-13.2): 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)
• 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/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)
• 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)
• kraken/riscv64 (1.1.1-4 to 1.1.1-4)
  • Migration status for kraken/riscv64 (1.1.1-4 to 1.1.1-4): Will attempt migration (Any information below is purely informational)
• kraken2/riscv64 (2.1.3-1 to 2.1.3-1)
  • Migration status for kraken2/riscv64 (2.1.3-1 to 2.1.3-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)
• krb5-sync/riscv64 (3.1-3 to 3.1-3)
  • Migration status for krb5-sync/riscv64 (3.1-3 to 3.1-3): Will attempt migration (Any information below is purely informational)
• krb5_pu (1.21.2-1 to 1.20.1-2+deb12u2)
  • Migration status for krb5_pu (1.21.2-1 to 1.20.1-2+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: krb5 is newer in the target suite (1.21.2-1 1.20.1-2+deb12u2)
• 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/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)
• 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)
• kreversi/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for kreversi/riscv64 (4:22.12.3-1 to 4:22.12.3-1): 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)
• 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)
• krunner/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for krunner/riscv64 (5.115.0-2 to 5.115.0-2): 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)
• kseexpr/riscv64 (4.0.4.0-6 to 4.0.4.0-6)
  • Migration status for kseexpr/riscv64 (4.0.4.0-6 to 4.0.4.0-6): 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)
• ktp-accounts-kcm/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ktp-accounts-kcm/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktp-approver/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ktp-approver/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktp-auth-handler/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ktp-auth-handler/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktp-call-ui/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ktp-call-ui/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktp-common-internals/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ktp-common-internals/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktp-contact-list/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ktp-contact-list/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktp-contact-runner/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ktp-contact-runner/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktp-desktop-applets/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ktp-desktop-applets/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktp-filetransfer-handler/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ktp-filetransfer-handler/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktp-kded-integration-module/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ktp-kded-integration-module/riscv64 (22.12.3-1 to 22.12.3-1): Will attempt migration (Any information below is purely informational)
• ktp-send-file/riscv64 (22.12.3-1 to 22.12.3-1)
  • Migration status for ktp-send-file/riscv64 (22.12.3-1 to 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)
• kwallet-kf5/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for kwallet-kf5/riscv64 (5.115.0-2 to 5.115.0-2): 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)
• kwayland/riscv64 (4:5.115.0-2 to 4:5.115.0-2)
  • Migration status for kwayland/riscv64 (4:5.115.0-2 to 4:5.115.0-2): 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)
• kwstyle/riscv64 (1.1.0~git20200506.b253a2b-1 to 1.1.0~git20200506.b253a2b-1)
  • Migration status for kwstyle/riscv64 (1.1.0~git20200506.b253a2b-1 to 1.1.0~git20200506.b253a2b-1): 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-burner/riscv64 (3.0.10-1.2 to 3.0.10-1.2)
  • Migration status for kylin-burner/riscv64 (3.0.10-1.2 to 3.0.10-1.2): 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)
• kyotocabinet/riscv64 (1.2.80-2 to 1.2.80-2)
  • Migration status for kyotocabinet/riscv64 (1.2.80-2 to 1.2.80-2): Will attempt migration (Any information below is purely informational)
• kyua/riscv64 (0.13+git20240311+0a43bb8d89e3-2 to 0.13+git20240311+0a43bb8d89e3-2)
  • Migration status for kyua/riscv64 (0.13+git20240311+0a43bb8d89e3-2 to 0.13+git20240311+0a43bb8d89e3-2): 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)
• lablgl/riscv64 (1:1.07-1 to 1:1.07-1)
  • Migration status for lablgl/riscv64 (1:1.07-1 to 1:1.07-1): 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)
• ladspa-sdk/riscv64 (1.17-1 to 1.17-1)
  • Migration status for ladspa-sdk/riscv64 (1.17-1 to 1.17-1): Will attempt migration (Any information below is purely informational)
• lagan/riscv64 (2.0-10 to 2.0-10)
  • Migration status for lagan/riscv64 (2.0-10 to 2.0-10): Will attempt migration (Any information below is purely informational)
• lager/riscv64 (0.1.1-1 to 0.1.1-1)
  • Migration status for lager/riscv64 (0.1.1-1 to 0.1.1-1): 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)
• lambda-align/riscv64 (1.0.3-6 to 1.0.3-6)
  • Migration status for lambda-align/riscv64 (1.0.3-6 to 1.0.3-6): Will attempt migration (Any information below is purely informational)
• lambda-term/riscv64 (3.3.2-1 to 3.3.2-1)
  • Migration status for lambda-term/riscv64 (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
• lammps/riscv64 (20240207+dfsg-1.1 to 20240207+dfsg-1.1)
  • Migration status for lammps/riscv64 (20240207+dfsg-1.1 to 20240207+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• langford/riscv64 (0.0.20130228-6.3 to 0.0.20130228-6.3)
  • Migration status for langford/riscv64 (0.0.20130228-6.3 to 0.0.20130228-6.3): Will attempt migration (Any information below is purely informational)
• lapack/riscv64 (3.12.0-3 to 3.12.0-3)
  • Migration status for lapack/riscv64 (3.12.0-3 to 3.12.0-3): Will attempt migration (Any information below is purely informational)
• largetifftools/riscv64 (1.4.1-1 to 1.4.1-1)
  • Migration status for largetifftools/riscv64 (1.4.1-1 to 1.4.1-1): Will attempt migration (Any information below is purely informational)
• laserboy/riscv64 (2016.03.15-1.3 to 2016.03.15-1.3)
  • Migration status for laserboy/riscv64 (2016.03.15-1.3 to 2016.03.15-1.3): Will attempt migration (Any information below is purely informational)
• lasi/riscv64 (1.1.3-2.1 to 1.1.3-2.1)
  • Migration status for lasi/riscv64 (1.1.3-2.1 to 1.1.3-2.1): Will attempt migration (Any information below is purely informational)
• last-align/riscv64 (1542-1 to 1542-1)
  • Migration status for last-align/riscv64 (1542-1 to 1542-1): Will attempt migration (Any information below is purely informational)
• laszip/riscv64 (3.5.0-2 to 3.5.0-2)
  • Migration status for laszip/riscv64 (3.5.0-2 to 3.5.0-2): Will attempt migration (Any information below is purely informational)
• late/riscv64 (0.1.0-14 to 0.1.0-14)
  • Migration status for late/riscv64 (0.1.0-14 to 0.1.0-14): 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)
• latexila/riscv64 (3.22.0-1.1 to 3.22.0-1.1)
  • Migration status for latexila/riscv64 (3.22.0-1.1 to 3.22.0-1.1): 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)
• latte-int/riscv64 (1.7.6+ds-3 to 1.7.6+ds-3)
  • Migration status for latte-int/riscv64 (1.7.6+ds-3 to 1.7.6+ds-3): Will attempt migration (Any information below is purely informational)
• lbfgsb/riscv64 (3.0+dfsg.4-1 to 3.0+dfsg.4-1)
  • Migration status for lbfgsb/riscv64 (3.0+dfsg.4-1 to 3.0+dfsg.4-1): Will attempt migration (Any information below is purely informational)
• lbreakouthd/riscv64 (1.1.8-1 to 1.1.8-1)
  • Migration status for lbreakouthd/riscv64 (1.1.8-1 to 1.1.8-1): Will attempt migration (Any information below is purely informational)
• lbt/riscv64 (1.2.2-7 to 1.2.2-7)
  • Migration status for lbt/riscv64 (1.2.2-7 to 1.2.2-7): Will attempt migration (Any information below is purely informational)
• lcalc/riscv64 (2.0.5-1.1 to 2.0.5-1.1)
  • Migration status for lcalc/riscv64 (2.0.5-1.1 to 2.0.5-1.1): Will attempt migration (Any information below is purely informational)
• lcd4linux/riscv64 (0.11.0~svn1203-3 to 0.11.0~svn1203-3)
  • Migration status for lcd4linux/riscv64 (0.11.0~svn1203-3 to 0.11.0~svn1203-3): Will attempt migration (Any information below is purely informational)
• lcdf-typetools/riscv64 (2.110-1 to 2.110-1)
  • Migration status for lcdf-typetools/riscv64 (2.110-1 to 2.110-1): Will attempt migration (Any information below is purely informational)
• lcmaps-plugins-basic/riscv64 (1.7.1-2 to 1.7.1-2)
  • Migration status for lcmaps-plugins-basic/riscv64 (1.7.1-2 to 1.7.1-2): Will attempt migration (Any information below is purely informational)
• lcmaps-plugins-jobrep/riscv64 (1.5.7-1 to 1.5.7-1)
  • Migration status for lcmaps-plugins-jobrep/riscv64 (1.5.7-1 to 1.5.7-1): Will attempt migration (Any information below is purely informational)
• lcmaps-plugins-verify-proxy/riscv64 (1.5.10-3 to 1.5.10-3)
  • Migration status for lcmaps-plugins-verify-proxy/riscv64 (1.5.10-3 to 1.5.10-3): Will attempt migration (Any information below is purely informational)
• lcmaps-plugins-voms/riscv64 (1.7.1-2 to 1.7.1-2)
  • Migration status for lcmaps-plugins-voms/riscv64 (1.7.1-2 to 1.7.1-2): Will attempt migration (Any information below is purely informational)
• lcmaps/riscv64 (1.6.6-3.1 to 1.6.6-3.1)
  • Migration status for lcmaps/riscv64 (1.6.6-3.1 to 1.6.6-3.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)
• ldc/riscv64 (1:1.36.0-2 to 1:1.36.0-2)
  • Migration status for ldc/riscv64 (1:1.36.0-2 to 1:1.36.0-2): Will attempt migration (Any information below is purely informational)
• le/riscv64 (1.16.8-0.1 to 1.16.8-0.1)
  • Migration status for le/riscv64 (1.16.8-0.1 to 1.16.8-0.1): Will attempt migration (Any information below is purely informational)
• leaktracer/riscv64 (2.4-6.3 to 2.4-6.3)
  • Migration status for leaktracer/riscv64 (2.4-6.3 to 2.4-6.3): Will attempt migration (Any information below is purely informational)
• leatherman/riscv64 (1.12.1+dfsg-1.3 to 1.12.1+dfsg-1.3)
  • Migration status for leatherman/riscv64 (1.12.1+dfsg-1.3 to 1.12.1+dfsg-1.3): Will attempt migration (Any information below is purely informational)
• lebiniou/riscv64 (3.66.0-2 to 3.66.0-2)
  • Migration status for lebiniou/riscv64 (3.66.0-2 to 3.66.0-2): Will attempt migration (Any information below is purely informational)
• ledger/riscv64 (3.3.2-1 to 3.3.2-1)
  • Migration status for ledger/riscv64 (3.3.2-1 to 3.3.2-1): Will attempt migration (Any information below is purely informational)
• ledit/riscv64 (2.04-7 to 2.04-7)
  • Migration status for ledit/riscv64 (2.04-7 to 2.04-7): 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)
• lensfun/riscv64 (0.3.4-1 to 0.3.4-1)
  • Migration status for lensfun/riscv64 (0.3.4-1 to 0.3.4-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)
• leptonlib/riscv64 (1.82.0-3 to 1.82.0-3)
  • Migration status for leptonlib/riscv64 (1.82.0-3 to 1.82.0-3): Will attempt migration (Any information below is purely informational)
• lerc/riscv64 (4.0.0+ds-4 to 4.0.0+ds-4)
  • Migration status for lerc/riscv64 (4.0.0+ds-4 to 4.0.0+ds-4): Will attempt migration (Any information below is purely informational)
• leveldb/riscv64 (1.23-5 to 1.23-5)
  • Migration status for leveldb/riscv64 (1.23-5 to 1.23-5): Will attempt migration (Any information below is purely informational)
• lexd/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for lexd/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• lftp/riscv64 (4.9.2-2.1 to 4.9.2-2.1)
  • Migration status for lftp/riscv64 (4.9.2-2.1 to 4.9.2-2.1): Will attempt migration (Any information below is purely informational)
• lhs2tex/riscv64 (1.24-1 to 1.24-1)
  • Migration status for lhs2tex/riscv64 (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• lib2geom/riscv64 (1.2.2-4 to 1.2.2-4)
  • Migration status for lib2geom/riscv64 (1.2.2-4 to 1.2.2-4): Will attempt migration (Any information below is purely informational)
• lib3mf/riscv64 (1.8.1+ds-4.1 to 1.8.1+ds-4.1)
  • Migration status for lib3mf/riscv64 (1.8.1+ds-4.1 to 1.8.1+ds-4.1): 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)
• libai-decisiontree-perl/riscv64 (0.11-2 to 0.11-2)
  • Migration status for libai-decisiontree-perl/riscv64 (0.11-2 to 0.11-2): Will attempt migration (Any information below is purely informational)
• libalgorithm-svm-perl/riscv64 (0.13-4 to 0.13-4)
  • Migration status for libalgorithm-svm-perl/riscv64 (0.13-4 to 0.13-4): Will attempt migration (Any information below is purely informational)
• libalien-gnuplot-perl/riscv64 (1.043-1 to 1.043-1)
  • Migration status for libalien-gnuplot-perl/riscv64 (1.043-1 to 1.043-1): 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)
• libalog/riscv64 (0.6.2-5 to 0.6.2-5)
  • Migration status for libalog/riscv64 (0.6.2-5 to 0.6.2-5): 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)
• libansilove/riscv64 (1.4.1-1 to 1.4.1-1)
  • Migration status for libansilove/riscv64 (1.4.1-1 to 1.4.1-1): Will attempt migration (Any information below is purely informational)
• libantlr3c/riscv64 (3.4+dfsg-4 to 3.4+dfsg-4)
  • Migration status for libantlr3c/riscv64 (3.4+dfsg-4 to 3.4+dfsg-4): Will attempt migration (Any information below is purely informational)
• libaosd/riscv64 (0.2.7-1.1 to 0.2.7-1.1)
  • Migration status for libaosd/riscv64 (0.2.7-1.1 to 0.2.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-auth-radius/riscv64 (1.5.8-2 to 1.5.8-2)
  • Migration status for libapache-mod-auth-radius/riscv64 (1.5.8-2 to 1.5.8-2): 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-log-sql/riscv64 (1.100-16.3 to 1.100-16.3)
  • Migration status for libapache-mod-log-sql/riscv64 (1.100-16.3 to 1.100-16.3): 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-mellon/riscv64 (0.19.0-1 to 0.19.0-1)
  • Migration status for libapache2-mod-auth-mellon/riscv64 (0.19.0-1 to 0.19.0-1): 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-sasl/riscv64 (1.2-2 to 1.2-2)
  • Migration status for libapache2-mod-authn-sasl/riscv64 (1.2-2 to 1.2-2): 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-encoding/riscv64 (20040616-8 to 20040616-8)
  • Migration status for libapache2-mod-encoding/riscv64 (20040616-8 to 20040616-8): 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-log-slow/riscv64 (1.0.8-3 to 1.0.8-3)
  • Migration status for libapache2-mod-log-slow/riscv64 (1.0.8-3 to 1.0.8-3): 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-qos/riscv64 (11.74-1 to 11.74-1)
  • Migration status for libapache2-mod-qos/riscv64 (11.74-1 to 11.74-1): 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)
• libapache2-mod-watchcat/riscv64 (1.1.2-2 to 1.1.2-2)
  • Migration status for libapache2-mod-watchcat/riscv64 (1.1.2-2 to 1.1.2-2): Will attempt migration (Any information below is purely informational)
• libapache2-mod-xsendfile/riscv64 (0.12-2 to 0.12-2)
  • Migration status for libapache2-mod-xsendfile/riscv64 (0.12-2 to 0.12-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)
• libapp-stacktrace-perl/riscv64 (0.09-5 to 0.09-5)
  • Migration status for libapp-stacktrace-perl/riscv64 (0.09-5 to 0.09-5): Will attempt migration (Any information below is purely informational)
• libappimage/riscv64 (1.0.4-5-3.1 to 1.0.4-5-3.1)
  • Migration status for libappimage/riscv64 (1.0.4-5-3.1 to 1.0.4-5-3.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)
• libapt-pkg-perl/riscv64 (0.1.40 to 0.1.40)
  • Migration status for libapt-pkg-perl/riscv64 (0.1.40 to 0.1.40): Will attempt migration (Any information below is purely informational)
• libarcus/riscv64 (5.0.0-5 to 5.0.0-5)
  • Migration status for libarcus/riscv64 (5.0.0-5 to 5.0.0-5): Will attempt migration (Any information below is purely informational)
• libassa/riscv64 (3.5.1-8.1 to 3.5.1-8.1)
  • Migration status for libassa/riscv64 (3.5.1-8.1 to 3.5.1-8.1): 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)
• libaudio-ecasound-perl/riscv64 (1.01-5 to 1.01-5)
  • Migration status for libaudio-ecasound-perl/riscv64 (1.01-5 to 1.01-5): Will attempt migration (Any information below is purely informational)
• libaudiomask/riscv64 (1.0-3.1 to 1.0-3.1)
  • Migration status for libaudiomask/riscv64 (1.0-3.1 to 1.0-3.1): Will attempt migration (Any information below is purely informational)
• libaunit/riscv64 (24.0.0-2 to 24.0.0-2)
  • Migration status for libaunit/riscv64 (24.0.0-2 to 24.0.0-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)
• libb2/riscv64 (0.98.1-1.1 to 0.98.1-1.1)
  • Migration status for libb2/riscv64 (0.98.1-1.1 to 0.98.1-1.1): Will attempt migration (Any information below is purely informational)
• libbacktrace/riscv64 (0.1-2 to 0.1-2)
  • Migration status for libbacktrace/riscv64 (0.1-2 to 0.1-2): Will attempt migration (Any information below is purely informational)
• libbgcode/riscv64 (0.0~git20240328.8ae75bd-1 to 0.0~git20240328.8ae75bd-1)
  • Migration status for libbgcode/riscv64 (0.0~git20240328.8ae75bd-1 to 0.0~git20240328.8ae75bd-1): Will attempt migration (Any information below is purely informational)
• libbinio/riscv64 (1.5+dfsg-0.1 to 1.5+dfsg-0.1)
  • Migration status for libbinio/riscv64 (1.5+dfsg-0.1 to 1.5+dfsg-0.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)
• libboost-geometry-utils-perl/riscv64 (0.15-3 to 0.15-3)
  • Migration status for libboost-geometry-utils-perl/riscv64 (0.15-3 to 0.15-3): Will attempt migration (Any information below is purely informational)
• libbpp-raa/riscv64 (2.4.1-8 to 2.4.1-8)
  • Migration status for libbpp-raa/riscv64 (2.4.1-8 to 2.4.1-8): Will attempt migration (Any information below is purely informational)
• libbpp-seq-omics/riscv64 (2.4.1-11 to 2.4.1-11)
  • Migration status for libbpp-seq-omics/riscv64 (2.4.1-11 to 2.4.1-11): Will attempt migration (Any information below is purely informational)
• libbpp-seq/riscv64 (2.4.1-12 to 2.4.1-12)
  • Migration status for libbpp-seq/riscv64 (2.4.1-12 to 2.4.1-12): Will attempt migration (Any information below is purely informational)
• libbraiding/riscv64 (1.1-1.1 to 1.1-1.1)
  • Migration status for libbraiding/riscv64 (1.1-1.1 to 1.1-1.1): Will attempt migration (Any information below is purely informational)
• libbs2b/riscv64 (3.1.0+dfsg-8 to 3.1.0+dfsg-8)
  • Migration status for libbs2b/riscv64 (3.1.0+dfsg-8 to 3.1.0+dfsg-8): Will attempt migration (Any information below is purely informational)
• libbssolv-perl/riscv64 (0.17-4 to 0.17-4)
  • Migration status for libbssolv-perl/riscv64 (0.17-4 to 0.17-4): Will attempt migration (Any information below is purely informational)
• libcaca/riscv64 (0.99.beta20-4 to 0.99.beta20-4)
  • Migration status for libcaca/riscv64 (0.99.beta20-4 to 0.99.beta20-4): Will attempt migration (Any information below is purely informational)
• libcache-fastmmap-perl/riscv64 (1.57-2 to 1.57-2)
  • Migration status for libcache-fastmmap-perl/riscv64 (1.57-2 to 1.57-2): 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)
• libcdr/riscv64 (0.1.7-1 to 0.1.7-1)
  • Migration status for libcdr/riscv64 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• libcds/riscv64 (2.3.3-4.1 to 2.3.3-4.1)
  • Migration status for libcds/riscv64 (2.3.3-4.1 to 2.3.3-4.1): Will attempt migration (Any information below is purely informational)
• libcec/riscv64 (6.0.2-5 to 6.0.2-5)
  • Migration status for libcec/riscv64 (6.0.2-5 to 6.0.2-5): Will attempt migration (Any information below is purely informational)
• libcgicc/riscv64 (3.2.19-1 to 3.2.19-1)
  • Migration status for libcgicc/riscv64 (3.2.19-1 to 3.2.19-1): Will attempt migration (Any information below is purely informational)
• libcgns/riscv64 (3.4.0-4 to 3.4.0-4)
  • Migration status for libcgns/riscv64 (3.4.0-4 to 3.4.0-4): 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)
• libchardet/riscv64 (1.0.4-1.1 to 1.0.4-1.1)
  • Migration status for libchardet/riscv64 (1.0.4-1.1 to 1.0.4-1.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)
• libcifpp/riscv64 (5.0.7.1-3 to 5.0.7.1-3)
  • Migration status for libcifpp/riscv64 (5.0.7.1-3 to 5.0.7.1-3): 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)
• libclaw/riscv64 (1.7.4-2.1 to 1.7.4-2.1)
  • Migration status for libclaw/riscv64 (1.7.4-2.1 to 1.7.4-2.1): 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)
• libcompiler-lexer-perl/riscv64 (0.23-3 to 0.23-3)
  • Migration status for libcompiler-lexer-perl/riscv64 (0.23-3 to 0.23-3): 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)
• libcrypto++/riscv64 (8.9.0-1.1 to 8.9.0-1.1)
  • Migration status for libcrypto++/riscv64 (8.9.0-1.1 to 8.9.0-1.1): Will attempt migration (Any information below is purely informational)
• libcryptui/riscv64 (3.12.2-8 to 3.12.2-8)
  • Migration status for libcryptui/riscv64 (3.12.2-8 to 3.12.2-8): Will attempt migration (Any information below is purely informational)
• libcsfml/riscv64 (2.6.0-3 to 2.6.0-3)
  • Migration status for libcsfml/riscv64 (2.6.0-3 to 2.6.0-3): Will attempt migration (Any information below is purely informational)
• libctl/riscv64 (4.5.1-2.1 to 4.5.1-2.1)
  • Migration status for libctl/riscv64 (4.5.1-2.1 to 4.5.1-2.1): Will attempt migration (Any information below is purely informational)
• libcutl/riscv64 (1.10.0+ds1-5 to 1.10.0+ds1-5)
  • Migration status for libcutl/riscv64 (1.10.0+ds1-5 to 1.10.0+ds1-5): 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)
• libdap/riscv64 (3.21.0-1.1 to 3.21.0-1.1)
  • Migration status for libdap/riscv64 (3.21.0-1.1 to 3.21.0-1.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)
• libde265/riscv64 (1.0.15-1 to 1.0.15-1)
  • Migration status for libde265/riscv64 (1.0.15-1 to 1.0.15-1): Will attempt migration (Any information below is purely informational)
• libdevice-usb-pcsensor-hidtemper-perl/riscv64 (2:0.04-2 to 2:0.04-2)
  • Migration status for libdevice-usb-pcsensor-hidtemper-perl/riscv64 (2:0.04-2 to 2:0.04-2): Will attempt migration (Any information below is purely informational)
• libdevice-usb-perl/riscv64 (0.38-3 to 0.38-3)
  • Migration status for libdevice-usb-perl/riscv64 (0.38-3 to 0.38-3): Will attempt migration (Any information below is purely informational)
• libdigidoc/riscv64 (3.10.5-5 to 3.10.5-5)
  • Migration status for libdigidoc/riscv64 (3.10.5-5 to 3.10.5-5): Will attempt migration (Any information below is purely informational)
• libdkim/riscv64 (1:1.0.21-4 to 1:1.0.21-4)
  • Migration status for libdkim/riscv64 (1:1.0.21-4 to 1:1.0.21-4): 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)
• libdogleg/riscv64 (0.16-4 to 0.16-4)
  • Migration status for libdogleg/riscv64 (0.16-4 to 0.16-4): 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)
• libdrpm/riscv64 (0.5.2-1 to 0.5.2-1)
  • Migration status for libdrpm/riscv64 (0.5.2-1 to 0.5.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)
• libebml/riscv64 (1.4.5-1 to 1.4.5-1)
  • Migration status for libebml/riscv64 (1.4.5-1 to 1.4.5-1): 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)
• libecap/riscv64 (1.0.1-3.4 to 1.0.1-3.4)
  • Migration status for libecap/riscv64 (1.0.1-3.4 to 1.0.1-3.4): Will attempt migration (Any information below is purely informational)
• libecpint/riscv64 (1.0.7-4 to 1.0.7-4)
  • Migration status for libecpint/riscv64 (1.0.7-4 to 1.0.7-4): Will attempt migration (Any information below is purely informational)
• libemf2svg/riscv64 (1.1.0+ds-3 to 1.1.0+ds-3)
  • Migration status for libemf2svg/riscv64 (1.1.0+ds-3 to 1.1.0+ds-3): Will attempt migration (Any information below is purely informational)
• libencode-detect-perl/riscv64 (1.01-6 to 1.01-6)
  • Migration status for libencode-detect-perl/riscv64 (1.01-6 to 1.01-6): Will attempt migration (Any information below is purely informational)
• libepoxy/riscv64 (1.5.10-1 to 1.5.10-1)
  • Migration status for libepoxy/riscv64 (1.5.10-1 to 1.5.10-1): Will attempt migration (Any information below is purely informational)
• libept/riscv64 (1.2.1+nmu1 to 1.2.1+nmu1)
  • Migration status for libept/riscv64 (1.2.1+nmu1 to 1.2.1+nmu1): Will attempt migration (Any information below is purely informational)
• libepubgen/riscv64 (0.1.1-1 to 0.1.1-1)
  • Migration status for libepubgen/riscv64 (0.1.1-1 to 0.1.1-1): Will attempt migration (Any information below is purely informational)
• libequihash/riscv64 (1.0.9-1 to 1.0.9-1)
  • Migration status for libequihash/riscv64 (1.0.9-1 to 1.0.9-1): 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)
• libetpan/riscv64 (1.9.4-3.2 to 1.9.4-3.2)
  • Migration status for libetpan/riscv64 (1.9.4-3.2 to 1.9.4-3.2): Will attempt migration (Any information below is purely informational)
• libexadrums/riscv64 (0.7.0-1.1 to 0.7.0-1.1)
  • Migration status for libexadrums/riscv64 (0.7.0-1.1 to 0.7.0-1.1): 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)
• libfabric/riscv64 (1.17.0-3 to 1.17.0-3)
  • Migration status for libfabric/riscv64 (1.17.0-3 to 1.17.0-3): Will attempt migration (Any information below is purely informational)
• libfastahack/riscv64 (1.0.0+dfsg-11 to 1.0.0+dfsg-11)
  • Migration status for libfastahack/riscv64 (1.0.0+dfsg-11 to 1.0.0+dfsg-11): Will attempt migration (Any information below is purely informational)
• libfcgi-perl/riscv64 (0.82+ds-3 to 0.82+ds-3)
  • Migration status for libfcgi-perl/riscv64 (0.82+ds-3 to 0.82+ds-3): Will attempt migration (Any information below is purely informational)
• libfcgi/riscv64 (2.4.2-2.1 to 2.4.2-2.1)
  • Migration status for libfcgi/riscv64 (2.4.2-2.1 to 2.4.2-2.1): Will attempt migration (Any information below is purely informational)
• libfilesys-smbclient-perl/riscv64 (3.2-4 to 3.2-4)
  • Migration status for libfilesys-smbclient-perl/riscv64 (3.2-4 to 3.2-4): Will attempt migration (Any information below is purely informational)
• 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)
• libflame/riscv64 (5.2.0-5.1 to 5.2.0-5.1)
  • Migration status for libflame/riscv64 (5.2.0-5.1 to 5.2.0-5.1): Will attempt migration (Any information below is purely informational)
• libflorist/riscv64 (2022.0.1~20220616-6 to 2022.0.1~20220616-6)
  • Migration status for libflorist/riscv64 (2022.0.1~20220616-6 to 2022.0.1~20220616-6): 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)
• libformfactor/riscv64 (0.3.1-1 to 0.3.1-1)
  • Migration status for libformfactor/riscv64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• libforms/riscv64 (1.2.3-1.7 to 1.2.3-1.7)
  • Migration status for libforms/riscv64 (1.2.3-1.7 to 1.2.3-1.7): Will attempt migration (Any information below is purely informational)
• libfreehand/riscv64 (0.1.2-3 to 0.1.2-3)
  • Migration status for libfreehand/riscv64 (0.1.2-3 to 0.1.2-3): 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)
• libfreesrp/riscv64 (0.3.0-5 to 0.3.0-5)
  • Migration status for libfreesrp/riscv64 (0.3.0-5 to 0.3.0-5): 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)
• libgadu/riscv64 (1:1.12.2-6.1 to 1:1.12.2-6.1)
  • Migration status for libgadu/riscv64 (1:1.12.2-6.1 to 1:1.12.2-6.1): Will attempt migration (Any information below is purely informational)
• libgav1/riscv64 (0.19.0-2 to 0.19.0-2)
  • Migration status for libgav1/riscv64 (0.19.0-2 to 0.19.0-2): Will attempt migration (Any information below is purely informational)
• libgc/riscv64 (1:8.2.6-1 to 1:8.2.6-1)
  • Migration status for libgc/riscv64 (1:8.2.6-1 to 1:8.2.6-1): Will attempt migration (Any information below is purely informational)
• libgclib/riscv64 (0.12.7+ds-5 to 0.12.7+ds-5)
  • Migration status for libgclib/riscv64 (0.12.7+ds-5 to 0.12.7+ds-5): Will attempt migration (Any information below is purely informational)
• libgd-perl/riscv64 (2.78-1 to 2.78-1)
  • Migration status for libgd-perl/riscv64 (2.78-1 to 2.78-1): Will attempt migration (Any information below is purely informational)
• libgda5/riscv64 (5.2.10-4.1 to 5.2.10-4.1)
  • Migration status for libgda5/riscv64 (5.2.10-4.1 to 5.2.10-4.1): Will attempt migration (Any information below is purely informational)
• libgdal-grass/riscv64 (1:1.0.2-7 to 1:1.0.2-7)
  • Migration status for libgdal-grass/riscv64 (1:1.0.2-7 to 1:1.0.2-7): 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)
• libgdchart-gd2/riscv64 (0.11.5-12 to 0.11.5-12)
  • Migration status for libgdchart-gd2/riscv64 (0.11.5-12 to 0.11.5-12): 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)
• libgdsii/riscv64 (0.2+ds.1-1 to 0.2+ds.1-1)
  • Migration status for libgdsii/riscv64 (0.2+ds.1-1 to 0.2+ds.1-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)
• libgenome/riscv64 (1.3.11+svn20110227.4616-6 to 1.3.11+svn20110227.4616-6)
  • Migration status for libgenome/riscv64 (1.3.11+svn20110227.4616-6 to 1.3.11+svn20110227.4616-6): Will attempt migration (Any information below is purely informational)
• libgeo-shapelib-perl/riscv64 (0.22-6 to 0.22-6)
  • Migration status for libgeo-shapelib-perl/riscv64 (0.22-6 to 0.22-6): 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)
• libgetdata/riscv64 (0.11.0-13 to 0.11.0-13)
  • Migration status for libgetdata/riscv64 (0.11.0-13 to 0.11.0-13): Will attempt migration (Any information below is purely informational)
• libghemical/riscv64 (3.0.0-4.4 to 3.0.0-4.4)
  • Migration status for libghemical/riscv64 (3.0.0-4.4 to 3.0.0-4.4): Will attempt migration (Any information below is purely informational)
• libgig/riscv64 (4.3.0~ds1-2.1 to 4.3.0~ds1-2.1)
  • Migration status for libgig/riscv64 (4.3.0~ds1-2.1 to 4.3.0~ds1-2.1): Will attempt migration (Any information below is purely informational)
• libgkarrays/riscv64 (2.1.0+dfsg-4.2 to 2.1.0+dfsg-4.2)
  • Migration status for libgkarrays/riscv64 (2.1.0+dfsg-4.2 to 2.1.0+dfsg-4.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)
• libglu/riscv64 (9.0.2-1.1 to 9.0.2-1.1)
  • Migration status for libglu/riscv64 (9.0.2-1.1 to 9.0.2-1.1): Will attempt migration (Any information below is purely informational)
• libglvnd/riscv64 (1.7.0-1 to 1.7.0-1)
  • Migration status for libglvnd/riscv64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• libgmpada/riscv64 (1.6-2 to 1.6-2)
  • Migration status for libgmpada/riscv64 (1.6-2 to 1.6-2): Will attempt migration (Any information below is purely informational)
• libgnatcoll-bindings/riscv64 (24.0.0-2 to 24.0.0-2)
  • Migration status for libgnatcoll-bindings/riscv64 (24.0.0-2 to 24.0.0-2): Will attempt migration (Any information below is purely informational)
• libgnatcoll-db/riscv64 (23.0.0-6 to 23.0.0-6)
  • Migration status for libgnatcoll-db/riscv64 (23.0.0-6 to 23.0.0-6): Will attempt migration (Any information below is purely informational)
• libgnatcoll/riscv64 (24.1.20230921-4 to 24.1.20230921-4)
  • Migration status for libgnatcoll/riscv64 (24.1.20230921-4 to 24.1.20230921-4): 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)
• libgoocanvas2-cairotypes-perl/riscv64 (0.001-2 to 0.001-2)
  • Migration status for libgoocanvas2-cairotypes-perl/riscv64 (0.001-2 to 0.001-2): Will attempt migration (Any information below is purely informational)
• libgooglepinyin/riscv64 (0.1.2-8 to 0.1.2-8)
  • Migration status for libgooglepinyin/riscv64 (0.1.2-8 to 0.1.2-8): Will attempt migration (Any information below is purely informational)
• libgpiod/riscv64 (1.6.3-1.1 to 1.6.3-1.1)
  • Migration status for libgpiod/riscv64 (1.6.3-1.1 to 1.6.3-1.1): Will attempt migration (Any information below is purely informational)
• libgraphics-libplot-perl/riscv64 (2.2.3-1 to 2.2.3-1)
  • Migration status for libgraphics-libplot-perl/riscv64 (2.2.3-1 to 2.2.3-1): Will attempt migration (Any information below is purely informational)
• libgrokj2k/riscv64 (10.0.5-1 to 10.0.5-1)
  • Migration status for libgrokj2k/riscv64 (10.0.5-1 to 10.0.5-1): Will attempt migration (Any information below is purely informational)
• 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)
• libgtextutils/riscv64 (0.7-9 to 0.7-9)
  • Migration status for libgtextutils/riscv64 (0.7-9 to 0.7-9): 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)
• libgwenhywfar/riscv64 (5.11.2beta-1 to 5.11.2beta-1)
  • Migration status for libgwenhywfar/riscv64 (5.11.2beta-1 to 5.11.2beta-1): 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)
• libgzstream/riscv64 (1.5+git20171107.9a20658-2 to 1.5+git20171107.9a20658-2)
  • Migration status for libgzstream/riscv64 (1.5+git20171107.9a20658-2 to 1.5+git20171107.9a20658-2): 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)
• libhdate/riscv64 (1.6.02-2.1 to 1.6.02-2.1)
  • Migration status for libhdate/riscv64 (1.6.02-2.1 to 1.6.02-2.1): Will attempt migration (Any information below is purely informational)
• libhdf4/riscv64 (4.3.0-1 to 4.3.0-1)
  • Migration status for libhdf4/riscv64 (4.3.0-1 to 4.3.0-1): Will attempt migration (Any information below is purely informational)
• libhinawa/riscv64 (4.0.2-1 to 4.0.2-1)
  • Migration status for libhinawa/riscv64 (4.0.2-1 to 4.0.2-1): Will attempt migration (Any information below is purely informational)
• libhinoko/riscv64 (1.0.2-1 to 1.0.2-1)
  • Migration status for libhinoko/riscv64 (1.0.2-1 to 1.0.2-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)
• libhitaki/riscv64 (0.2.1-2 to 0.2.1-2)
  • Migration status for libhitaki/riscv64 (0.2.1-2 to 0.2.1-2): 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)
• libhomfly/riscv64 (1.02r6-1 to 1.02r6-1)
  • Migration status for libhomfly/riscv64 (1.02r6-1 to 1.02r6-1): Will attempt migration (Any information below is purely informational)
• libibtk/riscv64 (0.0.14-13.1 to 0.0.14-13.1)
  • Migration status for libibtk/riscv64 (0.0.14-13.1 to 0.0.14-13.1): Will attempt migration (Any information below is purely informational)
• libical3/riscv64 (3.0.18-1 to 3.0.18-1)
  • Migration status for libical3/riscv64 (3.0.18-1 to 3.0.18-1): Will attempt migration (Any information below is purely informational)
• libicns/riscv64 (0.8.1.83.g921f972-0.1 to 0.8.1.83.g921f972-0.1)
  • Migration status for libicns/riscv64 (0.8.1.83.g921f972-0.1 to 0.8.1.83.g921f972-0.1): Will attempt migration (Any information below is purely informational)
• libidl/riscv64 (0.8.14-4 to 0.8.14-4)
  • Migration status for libidl/riscv64 (0.8.14-4 to 0.8.14-4): Will attempt migration (Any information below is purely informational)
• libiio/riscv64 (0.25-4 to 0.25-4)
  • Migration status for libiio/riscv64 (0.25-4 to 0.25-4): 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-librsvg-perl/riscv64 (0.07-9 to 0.07-9)
  • Migration status for libimage-librsvg-perl/riscv64 (0.07-9 to 0.07-9): 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)
• libimage-seek-perl/riscv64 (0.06-3 to 0.06-3)
  • Migration status for libimage-seek-perl/riscv64 (0.06-3 to 0.06-3): Will attempt migration (Any information below is purely informational)
• libimagequant/riscv64 (2.18.0-1 to 2.18.0-1)
  • Migration status for libimagequant/riscv64 (2.18.0-1 to 2.18.0-1): Will attempt migration (Any information below is purely informational)
• libimager-perl/riscv64 (1.024+dfsg-1 to 1.024+dfsg-1)
  • Migration status for libimager-perl/riscv64 (1.024+dfsg-1 to 1.024+dfsg-1): Will attempt migration (Any information below is purely informational)
• libimager-qrcode-perl/riscv64 (0.033-1.2 to 0.033-1.2)
  • Migration status for libimager-qrcode-perl/riscv64 (0.033-1.2 to 0.033-1.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)
• libinsane/riscv64 (1.0.10-1 to 1.0.10-1)
  • Migration status for libinsane/riscv64 (1.0.10-1 to 1.0.10-1): Will attempt migration (Any information below is purely informational)
• libinstpatch/riscv64 (1.1.6-1 to 1.1.6-1)
  • Migration status for libinstpatch/riscv64 (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• libint2/riscv64 (2.7.2-1.1 to 2.7.2-1.1)
  • Migration status for libint2/riscv64 (2.7.2-1.1 to 2.7.2-1.1): Will attempt migration (Any information below is purely informational)
• libitpp/riscv64 (4.3.1-10 to 4.3.1-10)
  • Migration status for libitpp/riscv64 (4.3.1-10 to 4.3.1-10): Will attempt migration (Any information below is purely informational)
• libixion/riscv64 (0.19.0-4 to 0.19.0-4)
  • Migration status for libixion/riscv64 (0.19.0-4 to 0.19.0-4): 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)
• libjpeg/riscv64 (0.0~git20220805.54ec643-1 to 0.0~git20220805.54ec643-1)
  • Migration status for libjpeg/riscv64 (0.0~git20220805.54ec643-1 to 0.0~git20220805.54ec643-1): Will attempt migration (Any information below is purely informational)
• libjson-rpc-cpp/riscv64 (0.7.0-2.2 to 0.7.0-2.2)
  • Migration status for libjson-rpc-cpp/riscv64 (0.7.0-2.2 to 0.7.0-2.2): Will attempt migration (Any information below is purely informational)
• libjsoncpp/riscv64 (1.9.5-6 to 1.9.5-6)
  • Migration status for libjsoncpp/riscv64 (1.9.5-6 to 1.9.5-6): Will attempt migration (Any information below is purely informational)
• libkarma/riscv64 (0.1.2-9 to 0.1.2-9)
  • Migration status for libkarma/riscv64 (0.1.2-9 to 0.1.2-9): 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)
• libkdtree++/riscv64 (0.7.1+git20101123-6 to 0.7.1+git20101123-6)
  • Migration status for libkdtree++/riscv64 (0.7.1+git20101123-6 to 0.7.1+git20101123-6): 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)
• 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/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)
• 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)
• libkf5libkleo/riscv64 (4:22.12.3-1 to 4:22.12.3-1)
  • Migration status for libkf5libkleo/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)
• libkml/riscv64 (1.3.0-12 to 1.3.0-12)
  • Migration status for libkml/riscv64 (1.3.0-12 to 1.3.0-12): Will attempt migration (Any information below is purely informational)
• libkolabxml/riscv64 (1.2.1-5 to 1.2.1-5)
  • Migration status for libkolabxml/riscv64 (1.2.1-5 to 1.2.1-5): 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)
• libktoblzcheck/riscv64 (1.53-3.1 to 1.53-3.1)
  • Migration status for libktoblzcheck/riscv64 (1.53-3.1 to 1.53-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)
• libkysdk-base/riscv64 (2.2.0.1-1.1 to 2.2.0.1-1.1)
  • Migration status for libkysdk-base/riscv64 (2.2.0.1-1.1 to 2.2.0.1-1.1): 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)
• liblemon/riscv64 (1.3.1+dfsg-6 to 1.3.1+dfsg-6)
  • Migration status for liblemon/riscv64 (1.3.1+dfsg-6 to 1.3.1+dfsg-6): Will attempt migration (Any information below is purely informational)
• liblinear/riscv64 (2.3.0+dfsg-5 to 2.3.0+dfsg-5)
  • Migration status for liblinear/riscv64 (2.3.0+dfsg-5 to 2.3.0+dfsg-5): Will attempt migration (Any information below is purely informational)
• liblog4ada/riscv64 (1.3.1.b6dafb49-13 to 1.3.1.b6dafb49-13)
  • Migration status for liblog4ada/riscv64 (1.3.1.b6dafb49-13 to 1.3.1.b6dafb49-13): Will attempt migration (Any information below is purely informational)
• libloki/riscv64 (0.1.7-5.1 to 0.1.7-5.1)
  • Migration status for libloki/riscv64 (0.1.7-5.1 to 0.1.7-5.1): 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)
• liblxqt/riscv64 (1.4.0-2 to 1.4.0-2)
  • Migration status for liblxqt/riscv64 (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• libmatchbox/riscv64 (1.12+git20170224-2 to 1.12+git20170224-2)
  • Migration status for libmatchbox/riscv64 (1.12+git20170224-2 to 1.12+git20170224-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)
• libmath-clipper-perl/riscv64 (1.29-2 to 1.29-2)
  • Migration status for libmath-clipper-perl/riscv64 (1.29-2 to 1.29-2): Will attempt migration (Any information below is purely informational)
• libmath-tamuanova-perl/riscv64 (1.0.2-4 to 1.0.2-4)
  • Migration status for libmath-tamuanova-perl/riscv64 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• libmatroska/riscv64 (1.7.1-1 to 1.7.1-1)
  • Migration status for libmatroska/riscv64 (1.7.1-1 to 1.7.1-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)
• libmediascan/riscv64 (0~20220401.git.34fc2d-5 to 0~20220401.git.34fc2d-5)
  • Migration status for libmediascan/riscv64 (0~20220401.git.34fc2d-5 to 0~20220401.git.34fc2d-5): 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)
• libmemcached-libmemcached-perl/riscv64 (1.001801+dfsg-4 to 1.001801+dfsg-4)
  • Migration status for libmemcached-libmemcached-perl/riscv64 (1.001801+dfsg-4 to 1.001801+dfsg-4): Will attempt migration (Any information below is purely informational)
• libmemcached/riscv64 (1.1.4-1.1 to 1.1.4-1.1)
  • Migration status for libmemcached/riscv64 (1.1.4-1.1 to 1.1.4-1.1): Will attempt migration (Any information below is purely informational)
• libmems/riscv64 (1.6.0+4725-10 to 1.6.0+4725-10)
  • Migration status for libmems/riscv64 (1.6.0+4725-10 to 1.6.0+4725-10): 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)
• libmikmod/riscv64 (3.3.11.1-7 to 3.3.11.1-7)
  • Migration status for libmikmod/riscv64 (3.3.11.1-7 to 3.3.11.1-7): 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)
• libminini/riscv64 (1.4+ds-1.1 to 1.4+ds-1.1)
  • Migration status for libminini/riscv64 (1.4+ds-1.1 to 1.4+ds-1.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)
• libmobi/riscv64 (0.11+dfsg-1.1 to 0.11+dfsg-1.1)
  • Migration status for libmobi/riscv64 (0.11+dfsg-1.1 to 0.11+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• libmodplug/riscv64 (1:0.8.9.0-3 to 1:0.8.9.0-3)
  • Migration status for libmodplug/riscv64 (1:0.8.9.0-3 to 1:0.8.9.0-3): 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)
• libmsnumpress/riscv64 (1.0.0-7 to 1.0.0-7)
  • Migration status for libmsnumpress/riscv64 (1.0.0-7 to 1.0.0-7): Will attempt migration (Any information below is purely informational)
• libmspub/riscv64 (0.1.4-3 to 0.1.4-3)
  • Migration status for libmspub/riscv64 (0.1.4-3 to 0.1.4-3): Will attempt migration (Any information below is purely informational)
• libmstoolkit/riscv64 (82-7.2 to 82-7.2)
  • Migration status for libmstoolkit/riscv64 (82-7.2 to 82-7.2): Will attempt migration (Any information below is purely informational)
• libmwaw/riscv64 (0.3.22-1 to 0.3.22-1)
  • Migration status for libmwaw/riscv64 (0.3.22-1 to 0.3.22-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)
• libmypaint/riscv64 (1.6.0-2 to 1.6.0-2)
  • Migration status for libmypaint/riscv64 (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
• libncl/riscv64 (2.1.21+git20210811.b1213a7-5 to 2.1.21+git20210811.b1213a7-5)
  • Migration status for libncl/riscv64 (2.1.21+git20210811.b1213a7-5 to 2.1.21+git20210811.b1213a7-5): Will attempt migration (Any information below is purely informational)
• libncursesada/riscv64 (6.3.20211021-11 to 6.3.20211021-11)
  • Migration status for libncursesada/riscv64 (6.3.20211021-11 to 6.3.20211021-11): Will attempt migration (Any information below is purely informational)
• libnet-bluetooth-perl/riscv64 (0.41-4 to 0.41-4)
  • Migration status for libnet-bluetooth-perl/riscv64 (0.41-4 to 0.41-4): Will attempt migration (Any information below is purely informational)
• libnet-jabber-loudmouth-perl/riscv64 (0.07-4 to 0.07-4)
  • Migration status for libnet-jabber-loudmouth-perl/riscv64 (0.07-4 to 0.07-4): Will attempt migration (Any information below is purely informational)
• libnet-z3950-simpleserver-perl/riscv64 (1.21-3 to 1.21-3)
  • Migration status for libnet-z3950-simpleserver-perl/riscv64 (1.21-3 to 1.21-3): Will attempt migration (Any information below is purely informational)
• libnet-z3950-zoom-perl/riscv64 (1.30-4 to 1.30-4)
  • Migration status for libnet-z3950-zoom-perl/riscv64 (1.30-4 to 1.30-4): 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)
• libnma/riscv64 (1.10.6-3 to 1.10.6-3)
  • Migration status for libnma/riscv64 (1.10.6-3 to 1.10.6-3): Will attempt migration (Any information below is purely informational)
• libnoise/riscv64 (1.0.0+repack-3 to 1.0.0+repack-3)
  • Migration status for libnoise/riscv64 (1.0.0+repack-3 to 1.0.0+repack-3): 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)
• libnumbertext/riscv64 (1.0.11-4 to 1.0.11-4)
  • Migration status for libnumbertext/riscv64 (1.0.11-4 to 1.0.11-4): Will attempt migration (Any information below is purely informational)
• libodb-boost/riscv64 (2.4.0-1.1 to 2.4.0-1.1)
  • Migration status for libodb-boost/riscv64 (2.4.0-1.1 to 2.4.0-1.1): Will attempt migration (Any information below is purely informational)
• libodb-mysql/riscv64 (2.4.0-5.1 to 2.4.0-5.1)
  • Migration status for libodb-mysql/riscv64 (2.4.0-5.1 to 2.4.0-5.1): Will attempt migration (Any information below is purely informational)
• libodb-pgsql/riscv64 (2.4.0-1 to 2.4.0-1)
  • Migration status for libodb-pgsql/riscv64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
• libodb-qt/riscv64 (2.4.0-3.1 to 2.4.0-3.1)
  • Migration status for libodb-qt/riscv64 (2.4.0-3.1 to 2.4.0-3.1): Will attempt migration (Any information below is purely informational)
• libodb-sqlite/riscv64 (2.4.0-1 to 2.4.0-1)
  • Migration status for libodb-sqlite/riscv64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
• libodb/riscv64 (2.4.0-2 to 2.4.0-2)
  • Migration status for libodb/riscv64 (2.4.0-2 to 2.4.0-2): 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)
• libofa/riscv64 (0.9.3-21 to 0.9.3-21)
  • Migration status for libofa/riscv64 (0.9.3-21 to 0.9.3-21): 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)
• liboglappth/riscv64 (1.0.0-2 to 1.0.0-2)
  • Migration status for liboglappth/riscv64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• libois-perl/riscv64 (0.10-2 to 0.10-2)
  • Migration status for libois-perl/riscv64 (0.10-2 to 0.10-2): Will attempt migration (Any information below is purely informational)
• libonvif/riscv64 (1.4.4-1.1 to 1.4.4-1.1)
  • Migration status for libonvif/riscv64 (1.4.4-1.1 to 1.4.4-1.1): Will attempt migration (Any information below is purely informational)
• libopencsd/riscv64 (1.5.2-1 to 1.5.2-1)
  • Migration status for libopencsd/riscv64 (1.5.2-1 to 1.5.2-1): Will attempt migration (Any information below is purely informational)
• libopendbx/riscv64 (1.4.6-17 to 1.4.6-17)
  • Migration status for libopendbx/riscv64 (1.4.6-17 to 1.4.6-17): 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)
• libopenmpt-modplug/riscv64 (0.8.9.0-openmpt1-2 to 0.8.9.0-openmpt1-2)
  • Migration status for libopenmpt-modplug/riscv64 (0.8.9.0-openmpt1-2 to 0.8.9.0-openmpt1-2): Will attempt migration (Any information below is purely informational)
• libopenobex/riscv64 (1.7.2-2.2 to 1.7.2-2.2)
  • Migration status for libopenobex/riscv64 (1.7.2-2.2 to 1.7.2-2.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)
• libopenshot-audio/riscv64 (0.3.2+dfsg1-2.1 to 0.3.2+dfsg1-2.1)
  • Migration status for libopenshot-audio/riscv64 (0.3.2+dfsg1-2.1 to 0.3.2+dfsg1-2.1): Will attempt migration (Any information below is purely informational)
• libopenshot/riscv64 (0.3.2+dfsg1-2.1 to 0.3.2+dfsg1-2.1)
  • Migration status for libopenshot/riscv64 (0.3.2+dfsg1-2.1 to 0.3.2+dfsg1-2.1): Will attempt migration (Any information below is purely informational)
• liborcus/riscv64 (0.19.2-3 to 0.19.2-3)
  • Migration status for liborcus/riscv64 (0.19.2-3 to 0.19.2-3): Will attempt migration (Any information below is purely informational)
• liborigin2/riscv64 (2:20110117-6 to 2:20110117-6)
  • Migration status for liborigin2/riscv64 (2:20110117-6 to 2:20110117-6): 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)
• libosmium/riscv64 (2.20.0-1 to 2.20.0-1)
  • Migration status for libosmium/riscv64 (2.20.0-1 to 2.20.0-1): Will attempt migration (Any information below is purely informational)
• libosmo-abis/riscv64 (1.3.0-2.1 to 1.3.0-2.1)
  • Migration status for libosmo-abis/riscv64 (1.3.0-2.1 to 1.3.0-2.1): Will attempt migration (Any information below is purely informational)
• libpagemaker/riscv64 (0.0.4-1 to 0.0.4-1)
  • Migration status for libpagemaker/riscv64 (0.0.4-1 to 0.0.4-1): Will attempt migration (Any information below is purely informational)
• libpam-encfs/riscv64 (0.1.4.4-16 to 0.1.4.4-16)
  • Migration status for libpam-encfs/riscv64 (0.1.4.4-16 to 0.1.4.4-16): 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)
• libpango-perl/riscv64 (1.227-4 to 1.227-4)
  • Migration status for libpango-perl/riscv64 (1.227-4 to 1.227-4): Will attempt migration (Any information below is purely informational)
• libpano13/riscv64 (2.9.22+dfsg-1.1 to 2.9.22+dfsg-1.1)
  • Migration status for libpano13/riscv64 (2.9.22+dfsg-1.1 to 2.9.22+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• libpdl-io-hdf5-perl/riscv64 (1:0.75-5 to 1:0.75-5)
  • Migration status for libpdl-io-hdf5-perl/riscv64 (1:0.75-5 to 1:0.75-5): Will attempt migration (Any information below is purely informational)
• libpdl-io-matlab-perl/riscv64 (0.006-5 to 0.006-5)
  • Migration status for libpdl-io-matlab-perl/riscv64 (0.006-5 to 0.006-5): Will attempt migration (Any information below is purely informational)
• libpdl-linearalgebra-perl/riscv64 (0.38-1 to 0.38-1)
  • Migration status for libpdl-linearalgebra-perl/riscv64 (0.38-1 to 0.38-1): 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)
• libpeas2/riscv64 (2.0.2-1 to 2.0.2-1)
  • Migration status for libpeas2/riscv64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• libpgf/riscv64 (7.21.7+ds-2 to 7.21.7+ds-2)
  • Migration status for libpgf/riscv64 (7.21.7+ds-2 to 7.21.7+ds-2): Will attempt migration (Any information below is purely informational)
• libphonenumber/riscv64 (8.12.57+ds-4.2 to 8.12.57+ds-4.2)
  • Migration status for libphonenumber/riscv64 (8.12.57+ds-4.2 to 8.12.57+ds-4.2): Will attempt migration (Any information below is purely informational)
• libpillowfight/riscv64 (0.3.0-5 to 0.3.0-5)
  • Migration status for libpillowfight/riscv64 (0.3.0-5 to 0.3.0-5): Will attempt migration (Any information below is purely informational)
• libpinyin/riscv64 (2.8.1-1 to 2.8.1-1)
  • Migration status for libpinyin/riscv64 (2.8.1-1 to 2.8.1-1): 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)
• libplacebo/riscv64 (6.338.2-2 to 6.338.2-2)
  • Migration status for libplacebo/riscv64 (6.338.2-2 to 6.338.2-2): Will attempt migration (Any information below is purely informational)
• libpodofo/riscv64 (0.9.8+dfsg-3.1 to 0.9.8+dfsg-3.1)
  • Migration status for libpodofo/riscv64 (0.9.8+dfsg-3.1 to 0.9.8+dfsg-3.1): Will attempt migration (Any information below is purely informational)
• libportal/riscv64 (0.7.1-5 to 0.7.1-5)
  • Migration status for libportal/riscv64 (0.7.1-5 to 0.7.1-5): Will attempt migration (Any information below is purely informational)
• libprelude/riscv64 (5.2.0-5.5 to 5.2.0-5.5)
  • Migration status for libprelude/riscv64 (5.2.0-5.5 to 5.2.0-5.5): Will attempt migration (Any information below is purely informational)
• libpsortb/riscv64 (1.0+dfsg-6 to 1.0+dfsg-6)
  • Migration status for libpsortb/riscv64 (1.0+dfsg-6 to 1.0+dfsg-6): 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)
• libptytty/riscv64 (2.0-1 to 2.0-1)
  • Migration status for libptytty/riscv64 (2.0-1 to 2.0-1): Will attempt migration (Any information below is purely informational)
• libpuzzle/riscv64 (0.11-3 to 0.11-3)
  • Migration status for libpuzzle/riscv64 (0.11-3 to 0.11-3): Will attempt migration (Any information below is purely informational)
• libpwiz/riscv64 (3.0.18342-4.1 to 3.0.18342-4.1)
  • Migration status for libpwiz/riscv64 (3.0.18342-4.1 to 3.0.18342-4.1): Will attempt migration (Any information below is purely informational)
• libpyzy/riscv64 (1.0.1-8 to 1.0.1-8)
  • Migration status for libpyzy/riscv64 (1.0.1-8 to 1.0.1-8): Will attempt migration (Any information below is purely informational)
• libqaccessibilityclient/riscv64 (0.6.0-1 to 0.6.0-1)
  • Migration status for libqaccessibilityclient/riscv64 (0.6.0-1 to 0.6.0-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)
• libquvi/riscv64 (0.9.4-3 to 0.9.4-3)
  • Migration status for libquvi/riscv64 (0.9.4-3 to 0.9.4-3): Will attempt migration (Any information below is purely informational)
• libqxp/riscv64 (0.0.2-1 to 0.0.2-1)
  • Migration status for libqxp/riscv64 (0.0.2-1 to 0.0.2-1): Will attempt migration (Any information below is purely informational)
• librandomx/riscv64 (1.1.10-3 to 1.1.10-3)
  • Migration status for librandomx/riscv64 (1.1.10-3 to 1.1.10-3): 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)
• libraw/riscv64 (0.21.2-2.1 to 0.21.2-2.1)
  • Migration status for libraw/riscv64 (0.21.2-2.1 to 0.21.2-2.1): 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)
• librcsb-core-wrapper/riscv64 (1.005-11.1 to 1.005-11.1)
  • Migration status for librcsb-core-wrapper/riscv64 (1.005-11.1 to 1.005-11.1): Will attempt migration (Any information below is purely informational)
• libre-engine-re2-perl/riscv64 (0.18+ds-1 to 0.18+ds-1)
  • Migration status for libre-engine-re2-perl/riscv64 (0.18+ds-1 to 0.18+ds-1): 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)
• librep/riscv64 (0.92.5-3.2 to 0.92.5-3.2)
  • Migration status for librep/riscv64 (0.92.5-3.2 to 0.92.5-3.2): Will attempt migration (Any information below is purely informational)
• librepfunc/riscv64 (1.10.0-1 to 1.10.0-1)
  • Migration status for librepfunc/riscv64 (1.10.0-1 to 1.10.0-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)
• libreswan/riscv64 (4.14-1 to 4.14-1)
  • Migration status for libreswan/riscv64 (4.14-1 to 4.14-1): 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)
• librevenge/riscv64 (0.0.5-3 to 0.0.5-3)
  • Migration status for librevenge/riscv64 (0.0.5-3 to 0.0.5-3): Will attempt migration (Any information below is purely informational)
• librevisa/riscv64 (0.0.20130812-6 to 0.0.20130812-6)
  • Migration status for librevisa/riscv64 (0.0.20130812-6 to 0.0.20130812-6): Will attempt migration (Any information below is purely informational)
• librg-blast-parser-perl/riscv64 (0.03-9 to 0.03-9)
  • Migration status for librg-blast-parser-perl/riscv64 (0.03-9 to 0.03-9): Will attempt migration (Any information below is purely informational)
• librostlab-blast/riscv64 (1.0.1-14 to 1.0.1-14)
  • Migration status for librostlab-blast/riscv64 (1.0.1-14 to 1.0.1-14): Will attempt migration (Any information below is purely informational)
• librsb/riscv64 (1.3.0.2+dfsg-6.1 to 1.3.0.2+dfsg-6.1)
  • Migration status for librsb/riscv64 (1.3.0.2+dfsg-6.1 to 1.3.0.2+dfsg-6.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)
• librsync/riscv64 (2.3.4-1.1 to 2.3.4-1.1)
  • Migration status for librsync/riscv64 (2.3.4-1.1 to 2.3.4-1.1): Will attempt migration (Any information below is purely informational)
• librttopo/riscv64 (1.1.0-3 to 1.1.0-3)
  • Migration status for librttopo/riscv64 (1.1.0-3 to 1.1.0-3): 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)
• libsass-python/riscv64 (0.22.0-1 to 0.22.0-1)
  • Migration status for libsass-python/riscv64 (0.22.0-1 to 0.22.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
• libsass/riscv64 (3.6.5+20231221-3 to 3.6.5+20231221-3)
  • Migration status for libsass/riscv64 (3.6.5+20231221-3 to 3.6.5+20231221-3): 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)
• libsbsms/riscv64 (2.3.0-1 to 2.3.0-1)
  • Migration status for libsbsms/riscv64 (2.3.0-1 to 2.3.0-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)
• libsdl2-gfx/riscv64 (1.0.4+dfsg-5 to 1.0.4+dfsg-5)
  • Migration status for libsdl2-gfx/riscv64 (1.0.4+dfsg-5 to 1.0.4+dfsg-5): Will attempt migration (Any information below is purely informational)
• libsdl2-image/riscv64 (2.8.2+dfsg-1 to 2.8.2+dfsg-1)
  • Migration status for libsdl2-image/riscv64 (2.8.2+dfsg-1 to 2.8.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• libsdl2-mixer/riscv64 (2.8.0+dfsg-1 to 2.8.0+dfsg-1)
  • Migration status for libsdl2-mixer/riscv64 (2.8.0+dfsg-1 to 2.8.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• libsdl2-net/riscv64 (2.2.0+dfsg-2 to 2.2.0+dfsg-2)
  • Migration status for libsdl2-net/riscv64 (2.2.0+dfsg-2 to 2.2.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• libsdl2-ttf/riscv64 (2.22.0+dfsg-1 to 2.22.0+dfsg-1)
  • Migration status for libsdl2-ttf/riscv64 (2.22.0+dfsg-1 to 2.22.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• libsdsl/riscv64 (2.1.1+dfsg-4 to 2.1.1+dfsg-4)
  • Migration status for libsdsl/riscv64 (2.1.1+dfsg-4 to 2.1.1+dfsg-4): Will attempt migration (Any information below is purely informational)
• libsearch-xapian-perl/riscv64 (1.2.25.5-3 to 1.2.25.5-3)
  • Migration status for libsearch-xapian-perl/riscv64 (1.2.25.5-3 to 1.2.25.5-3): Will attempt migration (Any information below is purely informational)
• libsecrecy/riscv64 (0.0.5+ds-4 to 0.0.5+ds-4)
  • Migration status for libsecrecy/riscv64 (0.0.5+ds-4 to 0.0.5+ds-4): Will attempt migration (Any information below is purely informational)
• libseqlib/riscv64 (1.2.0+dfsg-11 to 1.2.0+dfsg-11)
  • Migration status for libseqlib/riscv64 (1.2.0+dfsg-11 to 1.2.0+dfsg-11): Will attempt migration (Any information below is purely informational)
• libserial/riscv64 (1.0.0-9 to 1.0.0-9)
  • Migration status for libserial/riscv64 (1.0.0-9 to 1.0.0-9): Will attempt migration (Any information below is purely informational)
• libset-intervaltree-perl/riscv64 (0.12-2 to 0.12-2)
  • Migration status for libset-intervaltree-perl/riscv64 (0.12-2 to 0.12-2): Will attempt migration (Any information below is purely informational)
• libsgml-parser-opensp-perl/riscv64 (0.994-7 to 0.994-7)
  • Migration status for libsgml-parser-opensp-perl/riscv64 (0.994-7 to 0.994-7): Will attempt migration (Any information below is purely informational)
• libsharp/riscv64 (1.0.0-2 to 1.0.0-2)
  • Migration status for libsharp/riscv64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• libsidplay/riscv64 (1.36.60-1 to 1.36.60-1)
  • Migration status for libsidplay/riscv64 (1.36.60-1 to 1.36.60-1): Will attempt migration (Any information below is purely informational)
• libsigc++-2.0/riscv64 (2.12.1-2 to 2.12.1-2)
  • Migration status for libsigc++-2.0/riscv64 (2.12.1-2 to 2.12.1-2): Will attempt migration (Any information below is purely informational)
• libsigc++-3.0/riscv64 (3.6.0-2 to 3.6.0-2)
  • Migration status for libsigc++-3.0/riscv64 (3.6.0-2 to 3.6.0-2): Will attempt migration (Any information below is purely informational)
• libsigrok/riscv64 (0.5.2-5.1 to 0.5.2-5.1)
  • Migration status for libsigrok/riscv64 (0.5.2-5.1 to 0.5.2-5.1): Will attempt migration (Any information below is purely informational)
• libslow5lib/riscv64 (0.7.0+dfsg-2.1 to 0.7.0+dfsg-2.1)
  • Migration status for libslow5lib/riscv64 (0.7.0+dfsg-2.1 to 0.7.0+dfsg-2.1): Will attempt migration (Any information below is purely informational)
• libsmithwaterman/riscv64 (0.0+git20160702.2610e25-12 to 0.0+git20160702.2610e25-12)
  • Migration status for libsmithwaterman/riscv64 (0.0+git20160702.2610e25-12 to 0.0+git20160702.2610e25-12): 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)
• libsnl/riscv64 (0.2.1.svn.18-1.2 to 0.2.1.svn.18-1.2)
  • Migration status for libsnl/riscv64 (0.2.1.svn.18-1.2 to 0.2.1.svn.18-1.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)
• libsoxr/riscv64 (0.1.3-4 to 0.1.3-4)
  • Migration status for libsoxr/riscv64 (0.1.3-4 to 0.1.3-4): Will attempt migration (Any information below is purely informational)
• libspatialaudio/riscv64 (0.3.0+git20180730+dfsg1-2.1 to 0.3.0+git20180730+dfsg1-2.1)
  • Migration status for libspatialaudio/riscv64 (0.3.0+git20180730+dfsg1-2.1 to 0.3.0+git20180730+dfsg1-2.1): Will attempt migration (Any information below is purely informational)
• libspectre/riscv64 (0.2.12-1 to 0.2.12-1)
  • Migration status for libspectre/riscv64 (0.2.12-1 to 0.2.12-1): Will attempt migration (Any information below is purely informational)
• libspectrum/riscv64 (1.5.0-4 to 1.5.0-4)
  • Migration status for libspectrum/riscv64 (1.5.0-4 to 1.5.0-4): Will attempt migration (Any information below is purely informational)
• libsquish/riscv64 (1.15-3 to 1.15-3)
  • Migration status for libsquish/riscv64 (1.15-3 to 1.15-3): Will attempt migration (Any information below is purely informational)
• libssw/riscv64 (1.1-14 to 1.1-14)
  • Migration status for libssw/riscv64 (1.1-14 to 1.1-14): Will attempt migration (Any information below is purely informational)
• libstaroffice/riscv64 (0.0.7-1 to 0.0.7-1)
  • Migration status for libstaroffice/riscv64 (0.0.7-1 to 0.0.7-1): Will attempt migration (Any information below is purely informational)
• libstorj/riscv64 (1.0.3-1.3 to 1.0.3-1.3)
  • Migration status for libstorj/riscv64 (1.0.3-1.3 to 1.0.3-1.3): Will attempt migration (Any information below is purely informational)
• libstxxl/riscv64 (1.4.1-4.1 to 1.4.1-4.1)
  • Migration status for libstxxl/riscv64 (1.4.1-4.1 to 1.4.1-4.1): Will attempt migration (Any information below is purely informational)
• libsvm/riscv64 (3.24+ds-6 to 3.24+ds-6)
  • Migration status for libsvm/riscv64 (3.24+ds-6 to 3.24+ds-6): Will attempt migration (Any information below is purely informational)
• libsys-virt-perl/riscv64 (10.2.0-1 to 10.2.0-1)
  • Migration status for libsys-virt-perl/riscv64 (10.2.0-1 to 10.2.0-1): Will attempt migration (Any information below is purely informational)
• libsysstat/riscv64 (0.4.6-3 to 0.4.6-3)
  • Migration status for libsysstat/riscv64 (0.4.6-3 to 0.4.6-3): Will attempt migration (Any information below is purely informational)
• libt3widget/riscv64 (1.2.0-1.1 to 1.2.0-1.1)
  • Migration status for libt3widget/riscv64 (1.2.0-1.1 to 1.2.0-1.1): Will attempt migration (Any information below is purely informational)
• libtabixpp/riscv64 (1.1.2-2.1 to 1.1.2-2.1)
  • Migration status for libtabixpp/riscv64 (1.1.2-2.1 to 1.1.2-2.1): Will attempt migration (Any information below is purely informational)
• libtcod/riscv64 (1.18.1+dfsg-1.1 to 1.18.1+dfsg-1.1)
  • Migration status for libtcod/riscv64 (1.18.1+dfsg-1.1 to 1.18.1+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• libtemplates-parser/riscv64 (24.0.0-2 to 24.0.0-2)
  • Migration status for libtemplates-parser/riscv64 (24.0.0-2 to 24.0.0-2): Will attempt migration (Any information below is purely informational)
• libterralib/riscv64 (4.3.0+dfsg.2-12.2 to 4.3.0+dfsg.2-12.2)
  • Migration status for libterralib/riscv64 (4.3.0+dfsg.2-12.2 to 4.3.0+dfsg.2-12.2): Will attempt migration (Any information below is purely informational)
• libtext-aspell-perl/riscv64 (0.09-3 to 0.09-3)
  • Migration status for libtext-aspell-perl/riscv64 (0.09-3 to 0.09-3): Will attempt migration (Any information below is purely informational)
• libtext-hunspell-perl/riscv64 (2.16-1 to 2.16-1)
  • Migration status for libtext-hunspell-perl/riscv64 (2.16-1 to 2.16-1): Will attempt migration (Any information below is purely informational)
• libtext-mecab-perl/riscv64 (0.20016-5 to 0.20016-5)
  • Migration status for libtext-mecab-perl/riscv64 (0.20016-5 to 0.20016-5): Will attempt migration (Any information below is purely informational)
• libtexttools/riscv64 (2.1.0-28 to 2.1.0-28)
  • Migration status for libtexttools/riscv64 (2.1.0-28 to 2.1.0-28): Will attempt migration (Any information below is purely informational)
• libtgowt/riscv64 (0~git20230615.a45d8b8+dfsg-2 to 0~git20230615.a45d8b8+dfsg-2)
  • Migration status for libtgowt/riscv64 (0~git20230615.a45d8b8+dfsg-2 to 0~git20230615.a45d8b8+dfsg-2): Will attempt migration (Any information below is purely informational)
• libthreadar/riscv64 (1.4.0-2 to 1.4.0-2)
  • Migration status for libthreadar/riscv64 (1.4.0-2 to 1.4.0-2): 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)
• libtins/riscv64 (4.5-1 to 4.5-1)
  • Migration status for libtins/riscv64 (4.5-1 to 4.5-1): Will attempt migration (Any information below is purely informational)
• libtorrent-rasterbar/riscv64 (2.0.10-1.1 to 2.0.10-1.1)
  • Migration status for libtorrent-rasterbar/riscv64 (2.0.10-1.1 to 2.0.10-1.1): Will attempt migration (Any information below is purely informational)
• libtorrent/riscv64 (0.13.8-2.1 to 0.13.8-2.1)
  • Migration status for libtorrent/riscv64 (0.13.8-2.1 to 0.13.8-2.1): Will attempt migration (Any information below is purely informational)
• libtrace3/riscv64 (3.0.22-0.2 to 3.0.22-0.2)
  • Migration status for libtrace3/riscv64 (3.0.22-0.2 to 3.0.22-0.2): Will attempt migration (Any information below is purely informational)
• libtrexio/riscv64 (2.2.3-3 to 2.2.3-3)
  • Migration status for libtrexio/riscv64 (2.2.3-3 to 2.2.3-3): Will attempt migration (Any information below is purely informational)
• libtritonus-java/riscv64 (20070428-14.2 to 20070428-14.2)
  • Migration status for libtritonus-java/riscv64 (20070428-14.2 to 20070428-14.2): Will attempt migration (Any information below is purely informational)
• libucimf/riscv64 (2.3.8-14 to 2.3.8-14)
  • Migration status for libucimf/riscv64 (2.3.8-14 to 2.3.8-14): 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)
• libusermetrics/riscv64 (1.3.2-1 to 1.3.2-1)
  • Migration status for libusermetrics/riscv64 (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
• libvbz-hdf-plugin/riscv64 (1.0.2-3.1 to 1.0.2-3.1)
  • Migration status for libvbz-hdf-plugin/riscv64 (1.0.2-3.1 to 1.0.2-3.1): Will attempt migration (Any information below is purely informational)
• libvcflib/riscv64 (1.0.9+dfsg1-3 to 1.0.9+dfsg1-3)
  • Migration status for libvcflib/riscv64 (1.0.9+dfsg1-3 to 1.0.9+dfsg1-3): Will attempt migration (Any information below is purely informational)
• libvdpau-va-gl/riscv64 (0.4.2-1 to 0.4.2-1)
  • Migration status for libvdpau-va-gl/riscv64 (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• libverilog-perl/riscv64 (3.482-1 to 3.482-1)
  • Migration status for libverilog-perl/riscv64 (3.482-1 to 3.482-1): Will attempt migration (Any information below is purely informational)
• libvideo-capture-v4l-perl/riscv64 (0.902-5 to 0.902-5)
  • Migration status for libvideo-capture-v4l-perl/riscv64 (0.902-5 to 0.902-5): Will attempt migration (Any information below is purely informational)
• libvidstab/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for libvidstab/riscv64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• libvigraimpex/riscv64 (1.11.2+dfsg-3 to 1.11.2+dfsg-3)
  • Migration status for libvigraimpex/riscv64 (1.11.2+dfsg-3 to 1.11.2+dfsg-3): 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)
• libvisual/riscv64 (0.4.2-2 to 0.4.2-2)
  • Migration status for libvisual/riscv64 (0.4.2-2 to 0.4.2-2): Will attempt migration (Any information below is purely informational)
• libvmime/riscv64 (0.9.2-8.2 to 0.9.2-8.2)
  • Migration status for libvmime/riscv64 (0.9.2-8.2 to 0.9.2-8.2): Will attempt migration (Any information below is purely informational)
• libvncserver/riscv64 (0.9.14+dfsg-1 to 0.9.14+dfsg-1)
  • Migration status for libvncserver/riscv64 (0.9.14+dfsg-1 to 0.9.14+dfsg-1): 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)
• libvpx_pu (1.14.1-1 to 1.12.0-1+deb12u3)
  • Migration status for libvpx_pu (1.14.1-1 to 1.12.0-1+deb12u3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libvpx is newer in the target suite (1.14.1-1 1.12.0-1+deb12u3)
• libvsqlitepp/riscv64 (0.3.13-4.1 to 0.3.13-4.1)
  • Migration status for libvsqlitepp/riscv64 (0.3.13-4.1 to 0.3.13-4.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)
• libwebm/riscv64 (1.0.0.31-1 to 1.0.0.31-1)
  • Migration status for libwebm/riscv64 (1.0.0.31-1 to 1.0.0.31-1): Will attempt migration (Any information below is purely informational)
• libwfa2/riscv64 (2.3.3-4 to 2.3.3-4)
  • Migration status for libwfa2/riscv64 (2.3.3-4 to 2.3.3-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)
• libwpd/riscv64 (0.10.3-2 to 0.10.3-2)
  • Migration status for libwpd/riscv64 (0.10.3-2 to 0.10.3-2): 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)
• libwpg/riscv64 (0.3.4-3 to 0.3.4-3)
  • Migration status for libwpg/riscv64 (0.3.4-3 to 0.3.4-3): Will attempt migration (Any information below is purely informational)
• libwps/riscv64 (0.4.14-2 to 0.4.14-2)
  • Migration status for libwps/riscv64 (0.4.14-2 to 0.4.14-2): 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)
• libxc/riscv64 (5.2.3-1 to 5.2.3-1)
  • Migration status for libxc/riscv64 (5.2.3-1 to 5.2.3-1): Will attempt migration (Any information below is purely informational)
• libxdf/riscv64 (0.99.8+dfsg-3 to 0.99.8+dfsg-3)
  • Migration status for libxdf/riscv64 (0.99.8+dfsg-3 to 0.99.8+dfsg-3): Will attempt migration (Any information below is purely informational)
• libxfce4ui/riscv64 (4.18.4-1 to 4.18.4-1)
  • Migration status for libxfce4ui/riscv64 (4.18.4-1 to 4.18.4-1): Will attempt migration (Any information below is purely informational)
• libxisf/riscv64 (0.2.8-1 to 0.2.8-1)
  • Migration status for libxisf/riscv64 (0.2.8-1 to 0.2.8-1): 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)
• libxmlada/riscv64 (24.0.0-2 to 24.0.0-2)
  • Migration status for libxmlada/riscv64 (24.0.0-2 to 24.0.0-2): Will attempt migration (Any information below is purely informational)
• libxmlb/riscv64 (0.3.18-1 to 0.3.18-1)
  • Migration status for libxmlb/riscv64 (0.3.18-1 to 0.3.18-1): Will attempt migration (Any information below is purely informational)
• libxmlezout/riscv64 (1.06.2-14 to 1.06.2-14)
  • Migration status for libxmlezout/riscv64 (1.06.2-14 to 1.06.2-14): 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)
• libzeep/riscv64 (5.1.8-1 to 5.1.8-1)
  • Migration status for libzeep/riscv64 (5.1.8-1 to 5.1.8-1): Will attempt migration (Any information below is purely informational)
• libzen/riscv64 (0.4.41-2.1 to 0.4.41-2.1)
  • Migration status for libzen/riscv64 (0.4.41-2.1 to 0.4.41-2.1): Will attempt migration (Any information below is purely informational)
• libzim/riscv64 (8.2.1-2 to 8.2.1-2)
  • Migration status for libzim/riscv64 (8.2.1-2 to 8.2.1-2): Will attempt migration (Any information below is purely informational)
• libzmf/riscv64 (0.0.2-1 to 0.0.2-1)
  • Migration status for libzmf/riscv64 (0.0.2-1 to 0.0.2-1): Will attempt migration (Any information below is purely informational)
• licenseutils/riscv64 (0.0.9-7 to 0.0.9-7)
  • Migration status for licenseutils/riscv64 (0.0.9-7 to 0.0.9-7): Will attempt migration (Any information below is purely informational)
• liece/riscv64 (2.0+0.20030527cvs-14 to 2.0+0.20030527cvs-14)
  • Migration status for liece/riscv64 (2.0+0.20030527cvs-14 to 2.0+0.20030527cvs-14): Will attempt migration (Any information below is purely informational)
• lierolibre/riscv64 (0.5-3 to 0.5-3)
  • Migration status for lierolibre/riscv64 (0.5-3 to 0.5-3): 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)
• lighter/riscv64 (1.1.2-7 to 1.1.2-7)
  • Migration status for lighter/riscv64 (1.1.2-7 to 1.1.2-7): 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)
• lilypond/riscv64 (2.24.3-1 to 2.24.3-1)
  • Migration status for lilypond/riscv64 (2.24.3-1 to 2.24.3-1): Will attempt migration (Any information below is purely informational)
• limesuite/riscv64 (23.11.0+dfsg-3 to 23.11.0+dfsg-3)
  • Migration status for limesuite/riscv64 (23.11.0+dfsg-3 to 23.11.0+dfsg-3): 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)
• linpac/riscv64 (0.28-3 to 0.28-3)
  • Migration status for linpac/riscv64 (0.28-3 to 0.28-3): Will attempt migration (Any information below is purely informational)
• liquid-dsp/riscv64 (1.6.0-3 to 1.6.0-3)
  • Migration status for liquid-dsp/riscv64 (1.6.0-3 to 1.6.0-3): Will attempt migration (Any information below is purely informational)
• litehtml/riscv64 (0.6-1.2 to 0.6-1.2)
  • Migration status for litehtml/riscv64 (0.6-1.2 to 0.6-1.2): 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)
• littler/riscv64 (0.3.20-1 to 0.3.20-1)
  • Migration status for littler/riscv64 (0.3.20-1 to 0.3.20-1): 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)
• llvm-toolchain-17/riscv64 (1:17.0.6-12 to 1:17.0.6-12)
  • Migration status for llvm-toolchain-17/riscv64 (1:17.0.6-12 to 1:17.0.6-12): Will attempt migration (Any information below is purely informational)
• lmarbles/riscv64 (1.0.8-0.2 to 1.0.8-0.2)
  • Migration status for lmarbles/riscv64 (1.0.8-0.2 to 1.0.8-0.2): Will attempt migration (Any information below is purely informational)
• lmbench/riscv64 (3.0-a9+debian.1-7 to 3.0-a9+debian.1-7)
  • Migration status for lmbench/riscv64 (3.0-a9+debian.1-7 to 3.0-a9+debian.1-7): Will attempt migration (Any information below is purely informational)
• lmemory/riscv64 (0.6c-12 to 0.6c-12)
  • Migration status for lmemory/riscv64 (0.6c-12 to 0.6c-12): 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)
• lmtest/riscv64 (0.9.40-1 to 0.9.40-1)
  • Migration status for lmtest/riscv64 (0.9.40-1 to 0.9.40-1): Will attempt migration (Any information below is purely informational)
• log4cplus/riscv64 (2.0.8-1.1 to 2.0.8-1.1)
  • Migration status for log4cplus/riscv64 (2.0.8-1.1 to 2.0.8-1.1): Will attempt migration (Any information below is purely informational)
• log4cpp/riscv64 (1.1.3-3.1 to 1.1.3-3.1)
  • Migration status for log4cpp/riscv64 (1.1.3-3.1 to 1.1.3-3.1): Will attempt migration (Any information below is purely informational)
• log4shib/riscv64 (2.0.1-1 to 2.0.1-1)
  • Migration status for log4shib/riscv64 (2.0.1-1 to 2.0.1-1): 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)
• logtools/riscv64 (0.13e+nmu3 to 0.13e+nmu3)
  • Migration status for logtools/riscv64 (0.13e+nmu3 to 0.13e+nmu3): 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-api/riscv64 (0.2.1-1 to 0.2.1-1)
  • Migration status for lomiri-api/riscv64 (0.2.1-1 to 0.2.1-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-filemanager-app/riscv64 (1.0.4+dfsg-3 to 1.0.4+dfsg-3)
  • Migration status for lomiri-filemanager-app/riscv64 (1.0.4+dfsg-3 to 1.0.4+dfsg-3): Will attempt migration (Any information below is purely informational)
• lomiri-gallery-app/riscv64 (3.0.2-1 to 3.0.2-1)
  • Migration status for lomiri-gallery-app/riscv64 (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
• lomiri-mediaplayer-app/riscv64 (1.0.4+dfsg-1 to 1.0.4+dfsg-1)
  • Migration status for lomiri-mediaplayer-app/riscv64 (1.0.4+dfsg-1 to 1.0.4+dfsg-1): Will attempt migration (Any information below is purely informational)
• 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-polkit-agent/riscv64 (0.1-1 to 0.1-1)
  • Migration status for lomiri-polkit-agent/riscv64 (0.1-1 to 0.1-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/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-toolkit/riscv64 (1.3.5100+dfsg-1 to 1.3.5100+dfsg-1)
  • Migration status for lomiri-ui-toolkit/riscv64 (1.3.5100+dfsg-1 to 1.3.5100+dfsg-1): Will attempt migration (Any information below is purely informational)
• 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)
• looptools/riscv64 (2.16-1 to 2.16-1)
  • Migration status for looptools/riscv64 (2.16-1 to 2.16-1): Will attempt migration (Any information below is purely informational)
• loqui/riscv64 (0.7.0-2.1 to 0.7.0-2.1)
  • Migration status for loqui/riscv64 (0.7.0-2.1 to 0.7.0-2.1): Will attempt migration (Any information below is purely informational)
• lordsawar/riscv64 (0.3.2+frogknows-1 to 0.3.2+frogknows-1)
  • Migration status for lordsawar/riscv64 (0.3.2+frogknows-1 to 0.3.2+frogknows-1): Will attempt migration (Any information below is purely informational)
• lorene/riscv64 (0.0.0~cvs20161116+dfsg-1.3 to 0.0.0~cvs20161116+dfsg-1.3)
  • Migration status for lorene/riscv64 (0.0.0~cvs20161116+dfsg-1.3 to 0.0.0~cvs20161116+dfsg-1.3): Will attempt migration (Any information below is purely informational)
• loudgain/riscv64 (0.6.8+ds-3 to 0.6.8+ds-3)
  • Migration status for loudgain/riscv64 (0.6.8+ds-3 to 0.6.8+ds-3): Will attempt migration (Any information below is purely informational)
• loudmouth/riscv64 (1.5.4-2 to 1.5.4-2)
  • Migration status for loudmouth/riscv64 (1.5.4-2 to 1.5.4-2): Will attempt migration (Any information below is purely informational)
• lp-solve/riscv64 (5.5.2.5-2 to 5.5.2.5-2)
  • Migration status for lp-solve/riscv64 (5.5.2.5-2 to 5.5.2.5-2): Will attempt migration (Any information below is purely informational)
• lrzip/riscv64 (0.651-3 to 0.651-3)
  • Migration status for lrzip/riscv64 (0.651-3 to 0.651-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)
• lsyncd/riscv64 (2.2.3-1 to 2.2.3-1)
  • Migration status for lsyncd/riscv64 (2.2.3-1 to 2.2.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)
• lua-lxc/riscv64 (1:3.0.2-3 to 1:3.0.2-3)
  • Migration status for lua-lxc/riscv64 (1:3.0.2-3 to 1:3.0.2-3): Will attempt migration (Any information below is purely informational)
• lua-wsapi/riscv64 (1.6.1-2 to 1.6.1-2)
  • Migration status for lua-wsapi/riscv64 (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
• lua5.1/riscv64 (5.1.5-9 to 5.1.5-9)
  • Migration status for lua5.1/riscv64 (5.1.5-9 to 5.1.5-9): Will attempt migration (Any information below is purely informational)
• lua5.2/riscv64 (5.2.4-3 to 5.2.4-3)
  • Migration status for lua5.2/riscv64 (5.2.4-3 to 5.2.4-3): Will attempt migration (Any information below is purely informational)
• lua5.3/riscv64 (5.3.6-2 to 5.3.6-2)
  • Migration status for lua5.3/riscv64 (5.3.6-2 to 5.3.6-2): Will attempt migration (Any information below is purely informational)
• lua5.4/riscv64 (5.4.6-3 to 5.4.6-3)
  • Migration status for lua5.4/riscv64 (5.4.6-3 to 5.4.6-3): Will attempt migration (Any information below is purely informational)
• luabind/riscv64 (0.9.1+git20150823+dfsg-3.1 to 0.9.1+git20150823+dfsg-3.1)
  • Migration status for luabind/riscv64 (0.9.1+git20150823+dfsg-3.1 to 0.9.1+git20150823+dfsg-3.1): Will attempt migration (Any information below is purely informational)
• lucene++/riscv64 (3.0.9-3.2 to 3.0.9-3.2)
  • Migration status for lucene++/riscv64 (3.0.9-3.2 to 3.0.9-3.2): 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)
• luma.emulator/riscv64 (1.4.0-3 to 1.4.0-3)
  • Migration status for luma.emulator/riscv64 (1.4.0-3 to 1.4.0-3): Will attempt migration (Any information below is purely informational)
• luma.lcd/riscv64 (2.10.0-1 to 2.10.0-1)
  • Migration status for luma.lcd/riscv64 (2.10.0-1 to 2.10.0-1): Will attempt migration (Any information below is purely informational)
• luma.led-matrix/riscv64 (1.7.0-1 to 1.7.0-1)
  • Migration status for luma.led-matrix/riscv64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• luma.oled/riscv64 (3.10.0-1 to 3.10.0-1)
  • Migration status for luma.oled/riscv64 (3.10.0-1 to 3.10.0-1): Will attempt migration (Any information below is purely informational)
• 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)
• lumpy-sv/riscv64 (0.3.1+dfsg-7 to 0.3.1+dfsg-7)
  • Migration status for lumpy-sv/riscv64 (0.3.1+dfsg-7 to 0.3.1+dfsg-7): Will attempt migration (Any information below is purely informational)
• 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)
• lutok/riscv64 (0.4+dfsg-4.1 to 0.4+dfsg-4.1)
  • Migration status for lutok/riscv64 (0.4+dfsg-4.1 to 0.4+dfsg-4.1): Will attempt migration (Any information below is purely informational)
• lwt-log/riscv64 (1.1.2-4 to 1.1.2-4)
  • Migration status for lwt-log/riscv64 (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
• lwt-ssl/riscv64 (1:1.2.0-2 to 1:1.2.0-2)
  • Migration status for lwt-ssl/riscv64 (1:1.2.0-2 to 1:1.2.0-2): Will attempt migration (Any information below is purely informational)
• lwt/riscv64 (5.7.0-1 to 5.7.0-1)
  • Migration status for lwt/riscv64 (5.7.0-1 to 5.7.0-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)
• lxc-templates/riscv64 (3.0.4.79.g84b0597-1 to 3.0.4.79.g84b0597-1)
  • Migration status for lxc-templates/riscv64 (3.0.4.79.g84b0597-1 to 3.0.4.79.g84b0597-1): 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)
• lxmusic/riscv64 (0.4.7-2 to 0.4.7-2)
  • Migration status for lxmusic/riscv64 (0.4.7-2 to 0.4.7-2): 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-about/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for lxqt-about/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• lxqt-admin/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for lxqt-admin/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• lxqt-config/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for lxqt-config/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• lxqt-globalkeys/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for lxqt-globalkeys/riscv64 (1.4.0-1 to 1.4.0-1): 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)
• lxqt-notificationd/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for lxqt-notificationd/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• lxqt-openssh-askpass/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for lxqt-openssh-askpass/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• lxqt-policykit/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for lxqt-policykit/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• lxqt-powermanagement/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for lxqt-powermanagement/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• lxqt-runner/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for lxqt-runner/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• lxqt-session/riscv64 (1.3.0-1 to 1.3.0-1)
  • Migration status for lxqt-session/riscv64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• lxqt-sudo/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for lxqt-sudo/riscv64 (1.4.0-1 to 1.4.0-1): 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)
• lzd/riscv64 (1.4-1 to 1.4-1)
  • Migration status for lzd/riscv64 (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• lzip/riscv64 (1.24.1-1 to 1.24.1-1)
  • Migration status for lzip/riscv64 (1.24.1-1 to 1.24.1-1): Will attempt migration (Any information below is purely informational)
• lziprecover/riscv64 (1.24-1 to 1.24-1)
  • Migration status for lziprecover/riscv64 (1.24-1 to 1.24-1): Will attempt migration (Any information below is purely informational)
• lzma/riscv64 (9.22-2.2 to 9.22-2.2)
  • Migration status for lzma/riscv64 (9.22-2.2 to 9.22-2.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)
• macs/riscv64 (3.0.1-2 to 3.0.1-2)
  • Migration status for macs/riscv64 (3.0.1-2 to 3.0.1-2): Will attempt migration (Any information below is purely informational)
• madbomber/riscv64 (0.2.5-9 to 0.2.5-9)
  • Migration status for madbomber/riscv64 (0.2.5-9 to 0.2.5-9): Will attempt migration (Any information below is purely informational)
• maelstrom/riscv64 (3.0.7-4 to 3.0.7-4)
  • Migration status for maelstrom/riscv64 (3.0.7-4 to 3.0.7-4): Will attempt migration (Any information below is purely informational)
• maffilter/riscv64 (1.3.1+dfsg-6 to 1.3.1+dfsg-6)
  • Migration status for maffilter/riscv64 (1.3.1+dfsg-6 to 1.3.1+dfsg-6): 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)
• magic/riscv64 (8.3.105+ds.1-1.1 to 8.3.105+ds.1-1.1)
  • Migration status for magic/riscv64 (8.3.105+ds.1-1.1 to 8.3.105+ds.1-1.1): 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)
• mailfilter/riscv64 (0.8.9-1 to 0.8.9-1)
  • Migration status for mailfilter/riscv64 (0.8.9-1 to 0.8.9-1): Will attempt migration (Any information below is purely informational)
• mailfromd/riscv64 (9.0-1 to 9.0-1)
  • Migration status for mailfromd/riscv64 (9.0-1 to 9.0-1): Will attempt migration (Any information below is purely informational)
• mailio/riscv64 (0.23.0-1 to 0.23.0-1)
  • Migration status for mailio/riscv64 (0.23.0-1 to 0.23.0-1): Will attempt migration (Any information below is purely informational)
• mailsync/riscv64 (5.2.7-3.2 to 5.2.7-3.2)
  • Migration status for mailsync/riscv64 (5.2.7-3.2 to 5.2.7-3.2): Will attempt migration (Any information below is purely informational)
• mailtextbody/riscv64 (0.1.5-1 to 0.1.5-1)
  • Migration status for mailtextbody/riscv64 (0.1.5-1 to 0.1.5-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)
• man2html/riscv64 (1.6g-16 to 1.6g-16)
  • Migration status for man2html/riscv64 (1.6g-16 to 1.6g-16): Will attempt migration (Any information below is purely informational)
• mancala/riscv64 (1.0.3-1 to 1.0.3-1)
  • Migration status for mancala/riscv64 (1.0.3-1 to 1.0.3-1): 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)
• mangohud/riscv64 (0.7.1.1-1 to 0.7.1.1-1)
  • Migration status for mangohud/riscv64 (0.7.1.1-1 to 0.7.1.1-1): Will attempt migration (Any information below is purely informational)
• manimpango/riscv64 (0.5.0-1 to 0.5.0-1)
  • Migration status for manimpango/riscv64 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• mapcache/riscv64 (1.14.0-4 to 1.14.0-4)
  • Migration status for mapcache/riscv64 (1.14.0-4 to 1.14.0-4): Will attempt migration (Any information below is purely informational)
• maq/riscv64 (0.7.1-9 to 0.7.1-9)
  • Migration status for maq/riscv64 (0.7.1-9 to 0.7.1-9): Will attempt migration (Any information below is purely informational)
• maqview/riscv64 (0.2.5-11 to 0.2.5-11)
  • Migration status for maqview/riscv64 (0.2.5-11 to 0.2.5-11): 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)
• maria/riscv64 (1.3.5-4.2 to 1.3.5-4.2)
  • Migration status for maria/riscv64 (1.3.5-4.2 to 1.3.5-4.2): Will attempt migration (Any information below is purely informational)
• marisa/riscv64 (0.2.6-17 to 0.2.6-17)
  • Migration status for marisa/riscv64 (0.2.6-17 to 0.2.6-17): 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)
• mash/riscv64 (2.3+dfsg-6 to 2.3+dfsg-6)
  • Migration status for mash/riscv64 (2.3+dfsg-6 to 2.3+dfsg-6): 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-desktop/riscv64 (2.2+git20200512-1 to 2.2+git20200512-1)
  • Migration status for matchbox-desktop/riscv64 (2.2+git20200512-1 to 2.2+git20200512-1): 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)
• matchbox-window-manager/riscv64 (1.2.2+git20200512-1 to 1.2.2+git20200512-1)
  • Migration status for matchbox-window-manager/riscv64 (1.2.2+git20200512-1 to 1.2.2+git20200512-1): Will attempt migration (Any information below is purely informational)
• mate-applets/riscv64 (1.26.1-3 to 1.26.1-3)
  • Migration status for mate-applets/riscv64 (1.26.1-3 to 1.26.1-3): 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-power-manager/riscv64 (1.26.1-1 to 1.26.1-1)
  • Migration status for mate-power-manager/riscv64 (1.26.1-1 to 1.26.1-1): 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)
• mathic/riscv64 (1.0~git20230916-1 to 1.0~git20230916-1)
  • Migration status for mathic/riscv64 (1.0~git20230916-1 to 1.0~git20230916-1): Will attempt migration (Any information below is purely informational)
• mathicgb/riscv64 (1.0~git20240206-1.1 to 1.0~git20240206-1.1)
  • Migration status for mathicgb/riscv64 (1.0~git20240206-1.1 to 1.0~git20240206-1.1): Will attempt migration (Any information below is purely informational)
• mathtex/riscv64 (1.03-3 to 1.03-3)
  • Migration status for mathtex/riscv64 (1.03-3 to 1.03-3): Will attempt migration (Any information below is purely informational)
• matplotlib/riscv64 (3.6.3-2 to 3.6.3-2)
  • Migration status for matplotlib/riscv64 (3.6.3-2 to 3.6.3-2): Will attempt migration (Any information below is purely informational)
• maude/riscv64 (3.4-1 to 3.4-1)
  • Migration status for maude/riscv64 (3.4-1 to 3.4-1): Will attempt migration (Any information below is purely informational)
• maxflow/riscv64 (3.0.5-3 to 3.0.5-3)
  • Migration status for maxflow/riscv64 (3.0.5-3 to 3.0.5-3): Will attempt migration (Any information below is purely informational)
• maxima-sage/riscv64 (5.45.1-2 to 5.45.1-2)
  • Migration status for maxima-sage/riscv64 (5.45.1-2 to 5.45.1-2): 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)
• mcabber/riscv64 (1.1.2-2 to 1.1.2-2)
  • Migration status for mcabber/riscv64 (1.1.2-2 to 1.1.2-2): Will attempt migration (Any information below is purely informational)
• mccs/riscv64 (1:1.1-10 to 1:1.1-10)
  • Migration status for mccs/riscv64 (1:1.1-10 to 1:1.1-10): Will attempt migration (Any information below is purely informational)
• mcp-plugins/riscv64 (0.4.0-7 to 0.4.0-7)
  • Migration status for mcp-plugins/riscv64 (0.4.0-7 to 0.4.0-7): Will attempt migration (Any information below is purely informational)
• mcron/riscv64 (1.0.8-1.1 to 1.0.8-1.1)
  • Migration status for mcron/riscv64 (1.0.8-1.1 to 1.0.8-1.1): Will attempt migration (Any information below is purely informational)
• mctc-lib/riscv64 (0.3.1-3 to 0.3.1-3)
  • Migration status for mctc-lib/riscv64 (0.3.1-3 to 0.3.1-3): Will attempt migration (Any information below is purely informational)
• mda-lv2/riscv64 (1.2.10-2 to 1.2.10-2)
  • Migration status for mda-lv2/riscv64 (1.2.10-2 to 1.2.10-2): Will attempt migration (Any information below is purely informational)
• mdk/riscv64 (1.3.0+dfsg-3 to 1.3.0+dfsg-3)
  • Migration status for mdk/riscv64 (1.3.0+dfsg-3 to 1.3.0+dfsg-3): Will attempt migration (Any information below is purely informational)
• mecab/riscv64 (0.996-14 to 0.996-14)
  • Migration status for mecab/riscv64 (0.996-14 to 0.996-14): Will attempt migration (Any information below is purely informational)
• med-fichier/riscv64 (4.1.0+repack-4.1 to 4.1.0+repack-4.1)
  • Migration status for med-fichier/riscv64 (4.1.0+repack-4.1 to 4.1.0+repack-4.1): Will attempt migration (Any information below is purely informational)
• mediastreamer2/riscv64 (1:5.2.0+dfsg-4 to 1:5.2.0+dfsg-4)
  • Migration status for mediastreamer2/riscv64 (1:5.2.0+dfsg-4 to 1:5.2.0+dfsg-4): Will attempt migration (Any information below is purely informational)
• mednafen/riscv64 (1.32.1+dfsg-1 to 1.32.1+dfsg-1)
  • Migration status for mednafen/riscv64 (1.32.1+dfsg-1 to 1.32.1+dfsg-1): 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)
• megadepth/riscv64 (1.2.0-4 to 1.2.0-4)
  • Migration status for megadepth/riscv64 (1.2.0-4 to 1.2.0-4): 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)
• members/riscv64 (20080128.1+nmu2 to 20080128.1+nmu2)
  • Migration status for members/riscv64 (20080128.1+nmu2 to 20080128.1+nmu2): Will attempt migration (Any information below is purely informational)
• memtailor/riscv64 (1.0~git20230916-1 to 1.0~git20230916-1)
  • Migration status for memtailor/riscv64 (1.0~git20230916-1 to 1.0~git20230916-1): Will attempt migration (Any information below is purely informational)
• menhir/riscv64 (20231231+ds-1 to 20231231+ds-1)
  • Migration status for menhir/riscv64 (20231231+ds-1 to 20231231+ds-1): 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)
• menu/riscv64 (2.1.50 to 2.1.50)
  • Migration status for menu/riscv64 (2.1.50 to 2.1.50): Will attempt migration (Any information below is purely informational)
• meritous/riscv64 (1.5-1.1 to 1.5-1.1)
  • Migration status for meritous/riscv64 (1.5-1.1 to 1.5-1.1): Will attempt migration (Any information below is purely informational)
• merkaartor/riscv64 (0.19.0+ds-5 to 0.19.0+ds-5)
  • Migration status for merkaartor/riscv64 (0.19.0+ds-5 to 0.19.0+ds-5): 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)
• meshlab/riscv64 (2020.09+dfsg1-2 to 2020.09+dfsg1-2)
  • Migration status for meshlab/riscv64 (2020.09+dfsg1-2 to 2020.09+dfsg1-2): Will attempt migration (Any information below is purely informational)
• metacam/riscv64 (1.2-14 to 1.2-14)
  • Migration status for metacam/riscv64 (1.2-14 to 1.2-14): 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)
• metaeuk/riscv64 (6-a5d39d9+ds-5 to 6-a5d39d9+ds-5)
  • Migration status for metaeuk/riscv64 (6-a5d39d9+ds-5 to 6-a5d39d9+ds-5): 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)
• meterbridge/riscv64 (0.9.2-14 to 0.9.2-14)
  • Migration status for meterbridge/riscv64 (0.9.2-14 to 0.9.2-14): Will attempt migration (Any information below is purely informational)
• mffm-fftw/riscv64 (1.7-4.1 to 1.7-4.1)
  • Migration status for mffm-fftw/riscv64 (1.7-4.1 to 1.7-4.1): Will attempt migration (Any information below is purely informational)
• mfgtools/riscv64 (1.5.141-1 to 1.5.141-1)
  • Migration status for mfgtools/riscv64 (1.5.141-1 to 1.5.141-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)
• mgcv/riscv64 (1.9-1-1 to 1.9-1-1)
  • Migration status for mgcv/riscv64 (1.9-1-1 to 1.9-1-1): Will attempt migration (Any information below is purely informational)
• mgen/riscv64 (5.02.b+dfsg1-2.2 to 5.02.b+dfsg1-2.2)
  • Migration status for mgen/riscv64 (5.02.b+dfsg1-2.2 to 5.02.b+dfsg1-2.2): 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)
• microbiomeutil/riscv64 (20101212+dfsg1-6 to 20101212+dfsg1-6)
  • Migration status for microbiomeutil/riscv64 (20101212+dfsg1-6 to 20101212+dfsg1-6): Will attempt migration (Any information below is purely informational)
• microdc2/riscv64 (0.15.6-6 to 0.15.6-6)
  • Migration status for microdc2/riscv64 (0.15.6-6 to 0.15.6-6): Will attempt migration (Any information below is purely informational)
• microprofile/riscv64 (4.0+dfsg-4 to 4.0+dfsg-4)
  • Migration status for microprofile/riscv64 (4.0+dfsg-4 to 4.0+dfsg-4): 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)
• mikmod/riscv64 (3.2.8-3 to 3.2.8-3)
  • Migration status for mikmod/riscv64 (3.2.8-3 to 3.2.8-3): Will attempt migration (Any information below is purely informational)
• milkytracker/riscv64 (1.04.00.20230830+dfsg-1 to 1.04.00.20230830+dfsg-1)
  • Migration status for milkytracker/riscv64 (1.04.00.20230830+dfsg-1 to 1.04.00.20230830+dfsg-1): Will attempt migration (Any information below is purely informational)
• milter-greylist/riscv64 (4.6.4-3 to 4.6.4-3)
  • Migration status for milter-greylist/riscv64 (4.6.4-3 to 4.6.4-3): Will attempt migration (Any information below is purely informational)
• mimedefang/riscv64 (3.4.1-1 to 3.4.1-1)
  • Migration status for mimedefang/riscv64 (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
• mimetic/riscv64 (0.9.8-12 to 0.9.8-12)
  • Migration status for mimetic/riscv64 (0.9.8-12 to 0.9.8-12): 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)
• minder/riscv64 (1.16.2-1 to 1.16.2-1)
  • Migration status for minder/riscv64 (1.16.2-1 to 1.16.2-1): Will attempt migration (Any information below is purely informational)
• mindthegap/riscv64 (2.3.0-3 to 2.3.0-3)
  • Migration status for mindthegap/riscv64 (2.3.0-3 to 2.3.0-3): Will attempt migration (Any information below is purely informational)
• minetestmapper/riscv64 (20220221-2 to 20220221-2)
  • Migration status for minetestmapper/riscv64 (20220221-2 to 20220221-2): Will attempt migration (Any information below is purely informational)
• minia/riscv64 (3.2.6-4 to 3.2.6-4)
  • Migration status for minia/riscv64 (3.2.6-4 to 3.2.6-4): Will attempt migration (Any information below is purely informational)
• minidjvu/riscv64 (0.8.svn.2010.05.06+dfsg-7 to 0.8.svn.2010.05.06+dfsg-7)
  • Migration status for minidjvu/riscv64 (0.8.svn.2010.05.06+dfsg-7 to 0.8.svn.2010.05.06+dfsg-7): Will attempt migration (Any information below is purely informational)
• minidlna/riscv64 (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for minidlna/riscv64 (1.3.3+dfsg-1 to 1.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• minieigen/riscv64 (0.50.3+dfsg1-13 to 0.50.3+dfsg1-13)
  • Migration status for minieigen/riscv64 (0.50.3+dfsg1-13 to 0.50.3+dfsg1-13): Will attempt migration (Any information below is purely informational)
• minimodem/riscv64 (0.24-1 to 0.24-1)
  • Migration status for minimodem/riscv64 (0.24-1 to 0.24-1): Will attempt migration (Any information below is purely informational)
• mininet/riscv64 (2.3.0-1.1 to 2.3.0-1.1)
  • Migration status for mininet/riscv64 (2.3.0-1.1 to 2.3.0-1.1): Will attempt migration (Any information below is purely informational)
• minisat+/riscv64 (1.0-4 to 1.0-4)
  • Migration status for minisat+/riscv64 (1.0-4 to 1.0-4): Will attempt migration (Any information below is purely informational)
• minisat2/riscv64 (1:2.2.1-8 to 1:2.2.1-8)
  • Migration status for minisat2/riscv64 (1:2.2.1-8 to 1:2.2.1-8): 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)
• minizinc/riscv64 (2.8.3+dfsg1-1 to 2.8.3+dfsg1-1)
  • Migration status for minizinc/riscv64 (2.8.3+dfsg1-1 to 2.8.3+dfsg1-1): 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)
• mir-core/riscv64 (1.7.0-1 to 1.7.0-1)
  • Migration status for mir-core/riscv64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• mir/riscv64 (2.14.1-6 to 2.14.1-6)
  • Migration status for mir/riscv64 (2.14.1-6 to 2.14.1-6): Will attempt migration (Any information below is purely informational)
• mira/riscv64 (4.9.6-11 to 4.9.6-11)
  • Migration status for mira/riscv64 (4.9.6-11 to 4.9.6-11): 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)
• mirrorbits/riscv64 (0.5.1+git20240203.4e34d9b+ds1-2 to 0.5.1+git20240203.4e34d9b+ds1-2)
  • Migration status for mirrorbits/riscv64 (0.5.1+git20240203.4e34d9b+ds1-2 to 0.5.1+git20240203.4e34d9b+ds1-2): Will attempt migration (Any information below is purely informational)
• mirrormagic/riscv64 (3.3.0+dfsg1-1 to 3.3.0+dfsg1-1)
  • Migration status for mirrormagic/riscv64 (3.3.0+dfsg1-1 to 3.3.0+dfsg1-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)
• miwm/riscv64 (1.1-9 to 1.1-9)
  • Migration status for miwm/riscv64 (1.1-9 to 1.1-9): Will attempt migration (Any information below is purely informational)
• mjpegtools/riscv64 (1:2.1.0+debian-8.1 to 1:2.1.0+debian-8.1)
  • Migration status for mjpegtools/riscv64 (1:2.1.0+debian-8.1 to 1:2.1.0+debian-8.1): Will attempt migration (Any information below is purely informational)
• mklibs/riscv64 (0.1.45 to 0.1.45)
  • Migration status for mklibs/riscv64 (0.1.45 to 0.1.45): Will attempt migration (Any information below is purely informational)
• mle/riscv64 (1.7.2-1 to 1.7.2-1)
  • Migration status for mle/riscv64 (1.7.2-1 to 1.7.2-1): Will attempt migration (Any information below is purely informational)
• mlpost/riscv64 (0.9-5 to 0.9-5)
  • Migration status for mlpost/riscv64 (0.9-5 to 0.9-5): Will attempt migration (Any information below is purely informational)
• mlpy/riscv64 (3.5.0+ds-3 to 3.5.0+ds-3)
  • Migration status for mlpy/riscv64 (3.5.0+ds-3 to 3.5.0+ds-3): Will attempt migration (Any information below is purely informational)
• mlt/riscv64 (7.24.0-1 to 7.24.0-1)
  • Migration status for mlt/riscv64 (7.24.0-1 to 7.24.0-1): Will attempt migration (Any information below is purely informational)
• mlterm/riscv64 (3.9.3-1 to 3.9.3-1)
  • Migration status for mlterm/riscv64 (3.9.3-1 to 3.9.3-1): Will attempt migration (Any information below is purely informational)
• mm3d/riscv64 (1.3.14+git20240503+ds-1 to 1.3.14+git20240503+ds-1)
  • Migration status for mm3d/riscv64 (1.3.14+git20240503+ds-1 to 1.3.14+git20240503+ds-1): Will attempt migration (Any information below is purely informational)
• mmdb/riscv64 (2.0.22-1 to 2.0.22-1)
  • Migration status for mmdb/riscv64 (2.0.22-1 to 2.0.22-1): Will attempt migration (Any information below is purely informational)
• mmsd-tng/riscv64 (2.6.0-3 to 2.6.0-3)
  • Migration status for mmsd-tng/riscv64 (2.6.0-3 to 2.6.0-3): Will attempt migration (Any information below is purely informational)
• mmseqs2/riscv64 (15-6f452+ds-2 to 15-6f452+ds-2)
  • Migration status for mmseqs2/riscv64 (15-6f452+ds-2 to 15-6f452+ds-2): Will attempt migration (Any information below is purely informational)
• mmv/riscv64 (2.5.1-1 to 2.5.1-1)
  • Migration status for mmv/riscv64 (2.5.1-1 to 2.5.1-1): Will attempt migration (Any information below is purely informational)
• mnormt/riscv64 (2.1.1-2 to 2.1.1-2)
  • Migration status for mnormt/riscv64 (2.1.1-2 to 2.1.1-2): Will attempt migration (Any information below is purely informational)
• moc/riscv64 (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1)
  • Migration status for moc/riscv64 (1:2.6.0~svn-r3005-3.1 to 1:2.6.0~svn-r3005-3.1): Will attempt migration (Any information below is purely informational)
• mocassin/riscv64 (2.02.73.2-1 to 2.02.73.2-1)
  • Migration status for mocassin/riscv64 (2.02.73.2-1 to 2.02.73.2-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)
• modem-manager-gui/riscv64 (0.0.20-6 to 0.0.20-6)
  • Migration status for modem-manager-gui/riscv64 (0.0.20-6 to 0.0.20-6): 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)
• modplugtools/riscv64 (0.5.6-2 to 0.5.6-2)
  • Migration status for modplugtools/riscv64 (0.5.6-2 to 0.5.6-2): Will attempt migration (Any information below is purely informational)
• modsecurity-apache/riscv64 (2.9.7-1 to 2.9.7-1)
  • Migration status for modsecurity-apache/riscv64 (2.9.7-1 to 2.9.7-1): Will attempt migration (Any information below is purely informational)
• modsecurity/riscv64 (3.0.12-1.1 to 3.0.12-1.1)
  • Migration status for modsecurity/riscv64 (3.0.12-1.1 to 3.0.12-1.1): 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)
• molds/riscv64 (0.3.1-1 to 0.3.1-1)
  • Migration status for molds/riscv64 (0.3.1-1 to 0.3.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)
• mona/riscv64 (1.4-18-1 to 1.4-18-1)
  • Migration status for mona/riscv64 (1.4-18-1 to 1.4-18-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)
• monero/riscv64 (0.18.3.1+~0+20200826-1 to 0.18.3.1+~0+20200826-1)
  • Migration status for monero/riscv64 (0.18.3.1+~0+20200826-1 to 0.18.3.1+~0+20200826-1): Will attempt migration (Any information below is purely informational)
• mongo-cxx-driver-legacy/riscv64 (1.1.3-3.3 to 1.1.3-3.3)
  • Migration status for mongo-cxx-driver-legacy/riscv64 (1.1.3-3.3 to 1.1.3-3.3): 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)
• monopd/riscv64 (0.10.3-1 to 0.10.3-1)
  • Migration status for monopd/riscv64 (0.10.3-1 to 0.10.3-1): Will attempt migration (Any information below is purely informational)
• monsterz/riscv64 (0.7.1-12 to 0.7.1-12)
  • Migration status for monsterz/riscv64 (0.7.1-12 to 0.7.1-12): Will attempt migration (Any information below is purely informational)
• mopac/riscv64 (22.1.1-2 to 22.1.1-2)
  • Migration status for mopac/riscv64 (22.1.1-2 to 22.1.1-2): Will attempt migration (Any information below is purely informational)
• mopac7/riscv64 (1.15-6 to 1.15-6)
  • Migration status for mopac7/riscv64 (1.15-6 to 1.15-6): Will attempt migration (Any information below is purely informational)
• morbig/riscv64 (0.11.0-1 to 0.11.0-1)
  • Migration status for morbig/riscv64 (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
• moria/riscv64 (5.7.13-1 to 5.7.13-1)
  • Migration status for moria/riscv64 (5.7.13-1 to 5.7.13-1): Will attempt migration (Any information below is purely informational)
• morla/riscv64 (0.16.1-2 to 0.16.1-2)
  • Migration status for morla/riscv64 (0.16.1-2 to 0.16.1-2): 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)
• morsmall/riscv64 (0.3.0-7 to 0.3.0-7)
  • Migration status for morsmall/riscv64 (0.3.0-7 to 0.3.0-7): Will attempt migration (Any information below is purely informational)
• mosdepth/amd64 (0.3.6+ds-1 to 0.3.6+ds-1)
  • Migration status for mosdepth/amd64 (0.3.6+ds-1 to 0.3.6+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
• mosdepth/arm64 (0.3.6+ds-1 to 0.3.6+ds-1)
  • Migration status for mosdepth/arm64 (0.3.6+ds-1 to 0.3.6+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
• mosdepth/armel (0.3.6+ds-1 to 0.3.6+ds-1)
  • Migration status for mosdepth/armel (0.3.6+ds-1 to 0.3.6+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
• mosdepth/armhf (0.3.6+ds-1 to 0.3.6+ds-1)
  • Migration status for mosdepth/armhf (0.3.6+ds-1 to 0.3.6+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
• mosdepth/i386 (0.3.6+ds-1 to 0.3.6+ds-1)
  • Migration status for mosdepth/i386 (0.3.6+ds-1 to 0.3.6+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
• mosdepth/mips64el (0.3.6+ds-1 to 0.3.6+ds-1)
  • Migration status for mosdepth/mips64el (0.3.6+ds-1 to 0.3.6+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
• mosdepth/ppc64el (0.3.6+ds-1 to 0.3.6+ds-1)
  • Migration status for mosdepth/ppc64el (0.3.6+ds-1 to 0.3.6+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
• mosdepth/riscv64 (0.3.6+ds-1 to 0.3.6+ds-1)
  • Migration status for mosdepth/riscv64 (0.3.6+ds-1 to 0.3.6+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
• mosdepth/s390x (0.3.6+ds-1 to 0.3.6+ds-1)
  • Migration status for mosdepth/s390x (0.3.6+ds-1 to 0.3.6+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
• 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)
• mosquitto/riscv64 (2.0.18-1 to 2.0.18-1)
  • Migration status for mosquitto/riscv64 (2.0.18-1 to 2.0.18-1): Will attempt migration (Any information below is purely informational)
• motion/riscv64 (4.6.0-1 to 4.6.0-1)
  • Migration status for motion/riscv64 (4.6.0-1 to 4.6.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)
• mozjs102/riscv64 (102.15.1-5 to 102.15.1-5)
  • Migration status for mozjs102/riscv64 (102.15.1-5 to 102.15.1-5): Will attempt migration (Any information below is purely informational)
• mp3blaster/riscv64 (1:3.2.6-3 to 1:3.2.6-3)
  • Migration status for mp3blaster/riscv64 (1:3.2.6-3 to 1:3.2.6-3): Will attempt migration (Any information below is purely informational)
• mp3check/riscv64 (0.8.7-5 to 0.8.7-5)
  • Migration status for mp3check/riscv64 (0.8.7-5 to 0.8.7-5): 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)
• mp3fs/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for mp3fs/riscv64 (1.1.1-1 to 1.1.1-1): 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)
• mp3val/riscv64 (0.1.8-5 to 0.1.8-5)
  • Migration status for mp3val/riscv64 (0.1.8-5 to 0.1.8-5): Will attempt migration (Any information below is purely informational)
• mpb/riscv64 (1.11.1-5.1 to 1.11.1-5.1)
  • Migration status for mpb/riscv64 (1.11.1-5.1 to 1.11.1-5.1): Will attempt migration (Any information below is purely informational)
• mpdas/riscv64 (0.4.5-1 to 0.4.5-1)
  • Migration status for mpdas/riscv64 (0.4.5-1 to 0.4.5-1): 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)
• mpdscribble/riscv64 (0.25-2 to 0.25-2)
  • Migration status for mpdscribble/riscv64 (0.25-2 to 0.25-2): Will attempt migration (Any information below is purely informational)
• mpgtx/riscv64 (1.3.1-6 to 1.3.1-6)
  • Migration status for mpgtx/riscv64 (1.3.1-6 to 1.3.1-6): Will attempt migration (Any information below is purely informational)
• mpi4py-fft/riscv64 (2.0.5-2 to 2.0.5-2)
  • Migration status for mpi4py-fft/riscv64 (2.0.5-2 to 2.0.5-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)
• mpqc/riscv64 (2.3.1-22 to 2.3.1-22)
  • Migration status for mpqc/riscv64 (2.3.1-22 to 2.3.1-22): 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)
• mrc/riscv64 (1.3.10-1 to 1.3.10-1)
  • Migration status for mrc/riscv64 (1.3.10-1 to 1.3.10-1): Will attempt migration (Any information below is purely informational)
• mrgingham/riscv64 (1.24-1 to 1.24-1)
  • Migration status for mrgingham/riscv64 (1.24-1 to 1.24-1): 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)
• mrpt/riscv64 (1:2.12.0+ds-1.1 to 1:2.12.0+ds-1.1)
  • Migration status for mrpt/riscv64 (1:2.12.0+ds-1.1 to 1:2.12.0+ds-1.1): Will attempt migration (Any information below is purely informational)
• mrtg/riscv64 (2.17.10-12 to 2.17.10-12)
  • Migration status for mrtg/riscv64 (2.17.10-12 to 2.17.10-12): Will attempt migration (Any information below is purely informational)
• msc-generator/riscv64 (8.5-1 to 8.5-1)
  • Migration status for msc-generator/riscv64 (8.5-1 to 8.5-1): Will attempt migration (Any information below is purely informational)
• mscgen/riscv64 (0.20-15 to 0.20-15)
  • Migration status for mscgen/riscv64 (0.20-15 to 0.20-15): Will attempt migration (Any information below is purely informational)
• msgpack-cxx/riscv64 (6.1.1-1 to 6.1.1-1)
  • Migration status for msgpack-cxx/riscv64 (6.1.1-1 to 6.1.1-1): 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)
• msktutil/riscv64 (1.2.1-2 to 1.2.1-2)
  • Migration status for msktutil/riscv64 (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
• msopenh264/riscv64 (5.2.0-2 to 5.2.0-2)
  • Migration status for msopenh264/riscv64 (5.2.0-2 to 5.2.0-2): Will attempt migration (Any information below is purely informational)
• msort/riscv64 (8.53-2.3 to 8.53-2.3)
  • Migration status for msort/riscv64 (8.53-2.3 to 8.53-2.3): 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)
• mstch/riscv64 (1.0.2-4 to 1.0.2-4)
  • Migration status for mstch/riscv64 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• mstflint/riscv64 (4.26.0+1-2 to 4.26.0+1-2)
  • Migration status for mstflint/riscv64 (4.26.0+1-2 to 4.26.0+1-2): Will attempt migration (Any information below is purely informational)
• mtbl/riscv64 (1.6.1-1 to 1.6.1-1)
  • Migration status for mtbl/riscv64 (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• mtpaint/riscv64 (3.50-0.1 to 3.50-0.1)
  • Migration status for mtpaint/riscv64 (3.50-0.1 to 3.50-0.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)
• muchsync/riscv64 (7-1 to 7-1)
  • Migration status for muchsync/riscv64 (7-1 to 7-1): 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)
• multimon/riscv64 (1.0-8 to 1.0-8)
  • Migration status for multimon/riscv64 (1.0-8 to 1.0-8): Will attempt migration (Any information below is purely informational)
• mummer/riscv64 (3.23+dfsg-8 to 3.23+dfsg-8)
  • Migration status for mummer/riscv64 (3.23+dfsg-8 to 3.23+dfsg-8): 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)
• muparser/riscv64 (2.3.4-1 to 2.3.4-1)
  • Migration status for muparser/riscv64 (2.3.4-1 to 2.3.4-1): Will attempt migration (Any information below is purely informational)
• muparserx/riscv64 (4.0.11-2 to 4.0.11-2)
  • Migration status for muparserx/riscv64 (4.0.11-2 to 4.0.11-2): 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)
• muscle/riscv64 (1:5.1.0-1 to 1:5.1.0-1)
  • Migration status for muscle/riscv64 (1:5.1.0-1 to 1:5.1.0-1): Will attempt migration (Any information below is purely informational)
• muscle3/riscv64 (3.8.1551-3 to 3.8.1551-3)
  • Migration status for muscle3/riscv64 (3.8.1551-3 to 3.8.1551-3): 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)
• music/riscv64 (1.2.1-0.3 to 1.2.1-0.3)
  • Migration status for music/riscv64 (1.2.1-0.3 to 1.2.1-0.3): Will attempt migration (Any information below is purely informational)
• musl/riscv64 (1.2.5-1 to 1.2.5-1)
  • Migration status for musl/riscv64 (1.2.5-1 to 1.2.5-1): Will attempt migration (Any information below is purely informational)
• mustache-d/riscv64 (0.1.4-1 to 0.1.4-1)
  • Migration status for mustache-d/riscv64 (0.1.4-1 to 0.1.4-1): 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)
• mustang/riscv64 (3.2.4-1 to 3.2.4-1)
  • Migration status for mustang/riscv64 (3.2.4-1 to 3.2.4-1): 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)
• mymake/riscv64 (2.3.5-1 to 2.3.5-1)
  • Migration status for mymake/riscv64 (2.3.5-1 to 2.3.5-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)
• myproxy/riscv64 (6.2.16-2 to 6.2.16-2)
  • Migration status for myproxy/riscv64 (6.2.16-2 to 6.2.16-2): 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)
• mysql++/riscv64 (3.2.5-2.3 to 3.2.5-2.3)
  • Migration status for mysql++/riscv64 (3.2.5-2.3 to 3.2.5-2.3): Will attempt migration (Any information below is purely informational)
• mysql-connector-c++/riscv64 (1.1.12-4.1 to 1.1.12-4.1)
  • Migration status for mysql-connector-c++/riscv64 (1.1.12-4.1 to 1.1.12-4.1): Will attempt migration (Any information below is purely informational)
• mysql-defaults/riscv64 (1.1.0 to 1.1.0)
  • Migration status for mysql-defaults/riscv64 (1.1.0 to 1.1.0): Will attempt migration (Any information below is purely informational)
• mysql-ocaml/riscv64 (1.2.4-2 to 1.2.4-2)
  • Migration status for mysql-ocaml/riscv64 (1.2.4-2 to 1.2.4-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)
• mythes/riscv64 (2:1.2.5-1 to 2:1.2.5-1)
  • Migration status for mythes/riscv64 (2:1.2.5-1 to 2:1.2.5-1): 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)
• nanolyse/riscv64 (1.2.0-4 to 1.2.0-4)
  • Migration status for nanolyse/riscv64 (1.2.0-4 to 1.2.0-4): Will attempt migration (Any information below is purely informational)
• nanopolish/riscv64 (0.14.0-1 to 0.14.0-1)
  • Migration status for nanopolish/riscv64 (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• natlog/riscv64 (3.00.01-1 to 3.00.01-1)
  • Migration status for natlog/riscv64 (3.00.01-1 to 3.00.01-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-image-converter/riscv64 (0.4.0-2 to 0.4.0-2)
  • Migration status for nautilus-image-converter/riscv64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• nautilus-python/riscv64 (4.0.1-1 to 4.0.1-1)
  • Migration status for nautilus-python/riscv64 (4.0.1-1 to 4.0.1-1): 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)
• nautilus-wipe/riscv64 (0.4.alpha2-0.2 to 0.4.alpha2-0.2)
  • Migration status for nautilus-wipe/riscv64 (0.4.alpha2-0.2 to 0.4.alpha2-0.2): Will attempt migration (Any information below is purely informational)
• navit/riscv64 (0.5.6+dfsg.1-2 to 0.5.6+dfsg.1-2)
  • Migration status for navit/riscv64 (0.5.6+dfsg.1-2 to 0.5.6+dfsg.1-2): Will attempt migration (Any information below is purely informational)
• ncbi-blast+/riscv64 (2.12.0+ds-4 to 2.12.0+ds-4)
  • Migration status for ncbi-blast+/riscv64 (2.12.0+ds-4 to 2.12.0+ds-4): Will attempt migration (Any information below is purely informational)
• ncbi-igblast/riscv64 (1.19.0-1 to 1.19.0-1)
  • Migration status for ncbi-igblast/riscv64 (1.19.0-1 to 1.19.0-1): Will attempt migration (Any information below is purely informational)
• ncbi-tools6/riscv64 (6.1.20170106+dfsg2-2 to 6.1.20170106+dfsg2-2)
  • Migration status for ncbi-tools6/riscv64 (6.1.20170106+dfsg2-2 to 6.1.20170106+dfsg2-2): Will attempt migration (Any information below is purely informational)
• ncl/riscv64 (6.6.2.dfsg.1-7 to 6.6.2.dfsg.1-7)
  • Migration status for ncl/riscv64 (6.6.2.dfsg.1-7 to 6.6.2.dfsg.1-7): Will attempt migration (Any information below is purely informational)
• ncmpc/riscv64 (0.49-1 to 0.49-1)
  • Migration status for ncmpc/riscv64 (0.49-1 to 0.49-1): Will attempt migration (Any information below is purely informational)
• ncmpcpp/riscv64 (0.9.2-2 to 0.9.2-2)
  • Migration status for ncmpcpp/riscv64 (0.9.2-2 to 0.9.2-2): Will attempt migration (Any information below is purely informational)
• ncrack/riscv64 (0.7+debian-6 to 0.7+debian-6)
  • Migration status for ncrack/riscv64 (0.7+debian-6 to 0.7+debian-6): Will attempt migration (Any information below is purely informational)
• ncrystal/riscv64 (3.4.1+ds1-1.1 to 3.4.1+ds1-1.1)
  • Migration status for ncrystal/riscv64 (3.4.1+ds1-1.1 to 3.4.1+ds1-1.1): 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)
• ndppd/riscv64 (0.2.5-6 to 0.2.5-6)
  • Migration status for ndppd/riscv64 (0.2.5-6 to 0.2.5-6): Will attempt migration (Any information below is purely informational)
• neat/riscv64 (2.3.2-2 to 2.3.2-2)
  • Migration status for neat/riscv64 (2.3.2-2 to 2.3.2-2): Will attempt migration (Any information below is purely informational)
• neatvnc/riscv64 (0.8.0+dfsg-1 to 0.8.0+dfsg-1)
  • Migration status for neatvnc/riscv64 (0.8.0+dfsg-1 to 0.8.0+dfsg-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)
• neo-cli/riscv64 (0.6.1-1 to 0.6.1-1)
  • Migration status for neo-cli/riscv64 (0.6.1-1 to 0.6.1-1): 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)
• neovim/riscv64 (0.9.5-7 to 0.9.5-7)
  • Migration status for neovim/riscv64 (0.9.5-7 to 0.9.5-7): 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)
• net-cpp/riscv64 (3.1.1+dfsg-1 to 3.1.1+dfsg-1)
  • Migration status for net-cpp/riscv64 (3.1.1+dfsg-1 to 3.1.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)
• nethogs/riscv64 (0.8.7-2 to 0.8.7-2)
  • Migration status for nethogs/riscv64 (0.8.7-2 to 0.8.7-2): 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)
• netpanzer/riscv64 (0.8.7+ds-5 to 0.8.7+ds-5)
  • Migration status for netpanzer/riscv64 (0.8.7+ds-5 to 0.8.7+ds-5): Will attempt migration (Any information below is purely informational)
• netperfmeter/riscv64 (1.9.6-1 to 1.9.6-1)
  • Migration status for netperfmeter/riscv64 (1.9.6-1 to 1.9.6-1): 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)
• netsurf/riscv64 (3.11-1 to 3.11-1)
  • Migration status for netsurf/riscv64 (3.11-1 to 3.11-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-pptp/riscv64 (1.2.12-3 to 1.2.12-3)
  • Migration status for network-manager-pptp/riscv64 (1.2.12-3 to 1.2.12-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)
• network-manager-vpnc/riscv64 (1.2.8-7 to 1.2.8-7)
  • Migration status for network-manager-vpnc/riscv64 (1.2.8-7 to 1.2.8-7): 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)
• neuron/riscv64 (8.2.2-6 to 8.2.2-6)
  • Migration status for neuron/riscv64 (8.2.2-6 to 8.2.2-6): 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)
• nextepc/riscv64 (0.3.10+nods-4.2 to 0.3.10+nods-4.2)
  • Migration status for nextepc/riscv64 (0.3.10+nods-4.2 to 0.3.10+nods-4.2): 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)
• nfstrace/riscv64 (0.4.3.2+git20200805+b220d04-4 to 0.4.3.2+git20200805+b220d04-4)
  • Migration status for nfstrace/riscv64 (0.4.3.2+git20200805+b220d04-4 to 0.4.3.2+git20200805+b220d04-4): Will attempt migration (Any information below is purely informational)
• ngmlr/riscv64 (0.2.7+git20210816.a2a31fb+dfsg-2 to 0.2.7+git20210816.a2a31fb+dfsg-2)
  • Migration status for ngmlr/riscv64 (0.2.7+git20210816.a2a31fb+dfsg-2 to 0.2.7+git20210816.a2a31fb+dfsg-2): Will attempt migration (Any information below is purely informational)
• ngraph-gtk/riscv64 (6.09.07-1 to 6.09.07-1)
  • Migration status for ngraph-gtk/riscv64 (6.09.07-1 to 6.09.07-1): Will attempt migration (Any information below is purely informational)
• ngspice/riscv64 (42+ds-3 to 42+ds-3)
  • Migration status for ngspice/riscv64 (42+ds-3 to 42+ds-3): Will attempt migration (Any information below is purely informational)
• nihstro/riscv64 (0.0~git20211107.e924e21-2 to 0.0~git20211107.e924e21-2)
  • Migration status for nihstro/riscv64 (0.0~git20211107.e924e21-2 to 0.0~git20211107.e924e21-2): Will attempt migration (Any information below is purely informational)
• nikwi/riscv64 (0.0.20120213-6 to 0.0.20120213-6)
  • Migration status for nikwi/riscv64 (0.0.20120213-6 to 0.0.20120213-6): Will attempt migration (Any information below is purely informational)
• nim-d3/amd64 (0.1.3-2 to 0.1.3-2)
  • Migration status for nim-d3/amd64 (0.1.3-2 to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-d3/arm64 (0.1.3-2 to 0.1.3-2)
  • Migration status for nim-d3/arm64 (0.1.3-2 to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-d3/armel (0.1.3-2 to 0.1.3-2)
  • Migration status for nim-d3/armel (0.1.3-2 to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-d3/armhf (0.1.3-2 to 0.1.3-2)
  • Migration status for nim-d3/armhf (0.1.3-2 to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-d3/i386 (0.1.3-2 to 0.1.3-2)
  • Migration status for nim-d3/i386 (0.1.3-2 to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-d3/mips64el (0.1.3-2 to 0.1.3-2)
  • Migration status for nim-d3/mips64el (0.1.3-2 to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-d3/ppc64el (0.1.3-2 to 0.1.3-2)
  • Migration status for nim-d3/ppc64el (0.1.3-2 to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-d3/riscv64 (0.1.3-2 to 0.1.3-2)
  • Migration status for nim-d3/riscv64 (0.1.3-2 to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-d3/s390x (0.1.3-2 to 0.1.3-2)
  • Migration status for nim-d3/s390x (0.1.3-2 to 0.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-docopt/amd64 (0.6.8-3 to 0.6.8-3)
  • Migration status for nim-docopt/amd64 (0.6.8-3 to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-docopt/arm64 (0.6.8-3 to 0.6.8-3)
  • Migration status for nim-docopt/arm64 (0.6.8-3 to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-docopt/armel (0.6.8-3 to 0.6.8-3)
  • Migration status for nim-docopt/armel (0.6.8-3 to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-docopt/armhf (0.6.8-3 to 0.6.8-3)
  • Migration status for nim-docopt/armhf (0.6.8-3 to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-docopt/i386 (0.6.8-3 to 0.6.8-3)
  • Migration status for nim-docopt/i386 (0.6.8-3 to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-docopt/mips64el (0.6.8-3 to 0.6.8-3)
  • Migration status for nim-docopt/mips64el (0.6.8-3 to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-docopt/ppc64el (0.6.8-3 to 0.6.8-3)
  • Migration status for nim-docopt/ppc64el (0.6.8-3 to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-docopt/riscv64 (0.6.8-3 to 0.6.8-3)
  • Migration status for nim-docopt/riscv64 (0.6.8-3 to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-docopt/s390x (0.6.8-3 to 0.6.8-3)
  • Migration status for nim-docopt/s390x (0.6.8-3 to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-hts/amd64 (0.3.19+ds-1 to 0.3.19+ds-1)
  • Migration status for nim-hts/amd64 (0.3.19+ds-1 to 0.3.19+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
• nim-hts/arm64 (0.3.19+ds-1 to 0.3.19+ds-1)
  • Migration status for nim-hts/arm64 (0.3.19+ds-1 to 0.3.19+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
• nim-hts/armel (0.3.19+ds-1 to 0.3.19+ds-1)
  • Migration status for nim-hts/armel (0.3.19+ds-1 to 0.3.19+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
• nim-hts/armhf (0.3.19+ds-1 to 0.3.19+ds-1)
  • Migration status for nim-hts/armhf (0.3.19+ds-1 to 0.3.19+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
• nim-hts/i386 (0.3.19+ds-1 to 0.3.19+ds-1)
  • Migration status for nim-hts/i386 (0.3.19+ds-1 to 0.3.19+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
• nim-hts/mips64el (0.3.19+ds-1 to 0.3.19+ds-1)
  • Migration status for nim-hts/mips64el (0.3.19+ds-1 to 0.3.19+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
• nim-hts/ppc64el (0.3.19+ds-1 to 0.3.19+ds-1)
  • Migration status for nim-hts/ppc64el (0.3.19+ds-1 to 0.3.19+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
• nim-hts/riscv64 (0.3.19+ds-1 to 0.3.19+ds-1)
  • Migration status for nim-hts/riscv64 (0.3.19+ds-1 to 0.3.19+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
• nim-hts/s390x (0.3.19+ds-1 to 0.3.19+ds-1)
  • Migration status for nim-hts/s390x (0.3.19+ds-1 to 0.3.19+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
• nim-kexpr/amd64 (0.0.2-3 to 0.0.2-3)
  • Migration status for nim-kexpr/amd64 (0.0.2-3 to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-kexpr/arm64 (0.0.2-3 to 0.0.2-3)
  • Migration status for nim-kexpr/arm64 (0.0.2-3 to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-kexpr/armel (0.0.2-3 to 0.0.2-3)
  • Migration status for nim-kexpr/armel (0.0.2-3 to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-kexpr/armhf (0.0.2-3 to 0.0.2-3)
  • Migration status for nim-kexpr/armhf (0.0.2-3 to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-kexpr/i386 (0.0.2-3 to 0.0.2-3)
  • Migration status for nim-kexpr/i386 (0.0.2-3 to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-kexpr/mips64el (0.0.2-3 to 0.0.2-3)
  • Migration status for nim-kexpr/mips64el (0.0.2-3 to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-kexpr/ppc64el (0.0.2-3 to 0.0.2-3)
  • Migration status for nim-kexpr/ppc64el (0.0.2-3 to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-kexpr/riscv64 (0.0.2-3 to 0.0.2-3)
  • Migration status for nim-kexpr/riscv64 (0.0.2-3 to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-kexpr/s390x (0.0.2-3 to 0.0.2-3)
  • Migration status for nim-kexpr/s390x (0.0.2-3 to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-lapper/amd64 (0.1.7-5 to 0.1.7-5)
  • Migration status for nim-lapper/amd64 (0.1.7-5 to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-lapper/arm64 (0.1.7-5 to 0.1.7-5)
  • Migration status for nim-lapper/arm64 (0.1.7-5 to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-lapper/armel (0.1.7-5 to 0.1.7-5)
  • Migration status for nim-lapper/armel (0.1.7-5 to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-lapper/armhf (0.1.7-5 to 0.1.7-5)
  • Migration status for nim-lapper/armhf (0.1.7-5 to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-lapper/i386 (0.1.7-5 to 0.1.7-5)
  • Migration status for nim-lapper/i386 (0.1.7-5 to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-lapper/mips64el (0.1.7-5 to 0.1.7-5)
  • Migration status for nim-lapper/mips64el (0.1.7-5 to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-lapper/ppc64el (0.1.7-5 to 0.1.7-5)
  • Migration status for nim-lapper/ppc64el (0.1.7-5 to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-lapper/riscv64 (0.1.7-5 to 0.1.7-5)
  • Migration status for nim-lapper/riscv64 (0.1.7-5 to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-lapper/s390x (0.1.7-5 to 0.1.7-5)
  • Migration status for nim-lapper/s390x (0.1.7-5 to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-regex/amd64 (0.17.0+ds-2 to 0.17.0+ds-2)
  • Migration status for nim-regex/amd64 (0.17.0+ds-2 to 0.17.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
• nim-regex/arm64 (0.17.0+ds-2 to 0.17.0+ds-2)
  • Migration status for nim-regex/arm64 (0.17.0+ds-2 to 0.17.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
• nim-regex/armel (0.17.0+ds-2 to 0.17.0+ds-2)
  • Migration status for nim-regex/armel (0.17.0+ds-2 to 0.17.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
• nim-regex/armhf (0.17.0+ds-2 to 0.17.0+ds-2)
  • Migration status for nim-regex/armhf (0.17.0+ds-2 to 0.17.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
• nim-regex/i386 (0.17.0+ds-2 to 0.17.0+ds-2)
  • Migration status for nim-regex/i386 (0.17.0+ds-2 to 0.17.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
• nim-regex/mips64el (0.17.0+ds-2 to 0.17.0+ds-2)
  • Migration status for nim-regex/mips64el (0.17.0+ds-2 to 0.17.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
• nim-regex/ppc64el (0.17.0+ds-2 to 0.17.0+ds-2)
  • Migration status for nim-regex/ppc64el (0.17.0+ds-2 to 0.17.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
• nim-regex/riscv64 (0.17.0+ds-2 to 0.17.0+ds-2)
  • Migration status for nim-regex/riscv64 (0.17.0+ds-2 to 0.17.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
• nim-regex/s390x (0.17.0+ds-2 to 0.17.0+ds-2)
  • Migration status for nim-regex/s390x (0.17.0+ds-2 to 0.17.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
• nim-unicodedb/amd64 (0.9.0-2 to 0.9.0-2)
  • Migration status for nim-unicodedb/amd64 (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-unicodedb/arm64 (0.9.0-2 to 0.9.0-2)
  • Migration status for nim-unicodedb/arm64 (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-unicodedb/armel (0.9.0-2 to 0.9.0-2)
  • Migration status for nim-unicodedb/armel (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-unicodedb/armhf (0.9.0-2 to 0.9.0-2)
  • Migration status for nim-unicodedb/armhf (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-unicodedb/i386 (0.9.0-2 to 0.9.0-2)
  • Migration status for nim-unicodedb/i386 (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-unicodedb/mips64el (0.9.0-2 to 0.9.0-2)
  • Migration status for nim-unicodedb/mips64el (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-unicodedb/ppc64el (0.9.0-2 to 0.9.0-2)
  • Migration status for nim-unicodedb/ppc64el (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-unicodedb/riscv64 (0.9.0-2 to 0.9.0-2)
  • Migration status for nim-unicodedb/riscv64 (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-unicodedb/s390x (0.9.0-2 to 0.9.0-2)
  • Migration status for nim-unicodedb/s390x (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim-unicodeplus/amd64 (0.5.1-2 to 0.5.1-2)
  • Migration status for nim-unicodeplus/amd64 (0.5.1-2 to 0.5.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
• nim-unicodeplus/arm64 (0.5.1-2 to 0.5.1-2)
  • Migration status for nim-unicodeplus/arm64 (0.5.1-2 to 0.5.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
• nim-unicodeplus/armel (0.5.1-2 to 0.5.1-2)
  • Migration status for nim-unicodeplus/armel (0.5.1-2 to 0.5.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
• nim-unicodeplus/armhf (0.5.1-2 to 0.5.1-2)
  • Migration status for nim-unicodeplus/armhf (0.5.1-2 to 0.5.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
• nim-unicodeplus/i386 (0.5.1-2 to 0.5.1-2)
  • Migration status for nim-unicodeplus/i386 (0.5.1-2 to 0.5.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
• nim-unicodeplus/mips64el (0.5.1-2 to 0.5.1-2)
  • Migration status for nim-unicodeplus/mips64el (0.5.1-2 to 0.5.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
• nim-unicodeplus/ppc64el (0.5.1-2 to 0.5.1-2)
  • Migration status for nim-unicodeplus/ppc64el (0.5.1-2 to 0.5.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
• nim-unicodeplus/riscv64 (0.5.1-2 to 0.5.1-2)
  • Migration status for nim-unicodeplus/riscv64 (0.5.1-2 to 0.5.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
• nim-unicodeplus/s390x (0.5.1-2 to 0.5.1-2)
  • Migration status for nim-unicodeplus/s390x (0.5.1-2 to 0.5.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
• nim/amd64 (1.6.14-3 to 1.6.14-3)
  • Migration status for nim/amd64 (1.6.14-3 to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim/arm64 (1.6.14-3 to 1.6.14-3)
  • Migration status for nim/arm64 (1.6.14-3 to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim/armel (1.6.14-3 to 1.6.14-3)
  • Migration status for nim/armel (1.6.14-3 to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim/armhf (1.6.14-3 to 1.6.14-3)
  • Migration status for nim/armhf (1.6.14-3 to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim/i386 (1.6.14-3 to 1.6.14-3)
  • Migration status for nim/i386 (1.6.14-3 to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim/mips64el (1.6.14-3 to 1.6.14-3)
  • Migration status for nim/mips64el (1.6.14-3 to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim/ppc64el (1.6.14-3 to 1.6.14-3)
  • Migration status for nim/ppc64el (1.6.14-3 to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim/riscv64 (1.6.14-3 to 1.6.14-3)
  • Migration status for nim/riscv64 (1.6.14-3 to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nim/s390x (1.6.14-3 to 1.6.14-3)
  • Migration status for nim/s390x (1.6.14-3 to 1.6.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ninix-aya/riscv64 (5.0.9-1 to 5.0.9-1)
  • Migration status for ninix-aya/riscv64 (5.0.9-1 to 5.0.9-1): 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)
• nipy/riscv64 (0.6.0-1 to 0.6.0-1)
  • Migration status for nipy/riscv64 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• nitpic/riscv64 (0.1-19 to 0.1-19)
  • Migration status for nitpic/riscv64 (0.1-19 to 0.1-19): 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)
• njam/riscv64 (1.25-12 to 1.25-12)
  • Migration status for njam/riscv64 (1.25-12 to 1.25-12): 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)
• nload/riscv64 (0.7.4-2 to 0.7.4-2)
  • Migration status for nload/riscv64 (0.7.4-2 to 0.7.4-2): Will attempt migration (Any information below is purely informational)
• nlopt/riscv64 (2.7.1-5 to 2.7.1-5)
  • Migration status for nlopt/riscv64 (2.7.1-5 to 2.7.1-5): 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)
• nml/riscv64 (0.7.5-1 to 0.7.5-1)
  • Migration status for nml/riscv64 (0.7.5-1 to 0.7.5-1): Will attempt migration (Any information below is purely informational)
• nmodl/riscv64 (0.6-2 to 0.6-2)
  • Migration status for nmodl/riscv64 (0.6-2 to 0.6-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-iconv/riscv64 (3.0.1+~3.0.0-1 to 3.0.1+~3.0.0-1)
  • Migration status for node-iconv/riscv64 (3.0.1+~3.0.0-1 to 3.0.1+~3.0.0-1): Will attempt migration (Any information below is purely informational)
• node-libpq/riscv64 (1.8.12+~1.8.10-2 to 1.8.12+~1.8.10-2)
  • Migration status for node-libpq/riscv64 (1.8.12+~1.8.10-2 to 1.8.12+~1.8.10-2): Will attempt migration (Any information below is purely informational)
• node-modern-syslog/riscv64 (1.2.0-4 to 1.2.0-4)
  • Migration status for node-modern-syslog/riscv64 (1.2.0-4 to 1.2.0-4): Will attempt migration (Any information below is purely informational)
• node-node-pty/riscv64 (1.0.0+ds1+~6.3.0-1 to 1.0.0+ds1+~6.3.0-1)
  • Migration status for node-node-pty/riscv64 (1.0.0+ds1+~6.3.0-1 to 1.0.0+ds1+~6.3.0-1): Will attempt migration (Any information below is purely informational)
• node-node-sass/riscv64 (9.0.0+git20240131.6081731+dfsg-1 to 9.0.0+git20240131.6081731+dfsg-1)
  • Migration status for node-node-sass/riscv64 (9.0.0+git20240131.6081731+dfsg-1 to 9.0.0+git20240131.6081731+dfsg-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-sqlite3/riscv64 (5.1.5+ds1-1 to 5.1.5+ds1-1)
  • Migration status for node-sqlite3/riscv64 (5.1.5+ds1-1 to 5.1.5+ds1-1): Will attempt migration (Any information below is purely informational)
• noiz2sa/riscv64 (0.51a-13 to 0.51a-13)
  • Migration status for noiz2sa/riscv64 (0.51a-13 to 0.51a-13): Will attempt migration (Any information below is purely informational)
• 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)
• normalize-audio/riscv64 (0.7.7-18 to 0.7.7-18)
  • Migration status for normalize-audio/riscv64 (0.7.7-18 to 0.7.7-18): 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)
• notify-osd/riscv64 (0.9.35+15.04.20150126-3 to 0.9.35+15.04.20150126-3)
  • Migration status for notify-osd/riscv64 (0.9.35+15.04.20150126-3 to 0.9.35+15.04.20150126-3): Will attempt migration (Any information below is purely informational)
• notion/riscv64 (4.0.2+dfsg-7 to 4.0.2+dfsg-7)
  • Migration status for notion/riscv64 (4.0.2+dfsg-7 to 4.0.2+dfsg-7): Will attempt migration (Any information below is purely informational)
• notmuch-addrlookup/riscv64 (10-1 to 10-1)
  • Migration status for notmuch-addrlookup/riscv64 (10-1 to 10-1): Will attempt migration (Any information below is purely informational)
• notmuch/riscv64 (0.38.3-1 to 0.38.3-1)
  • Migration status for notmuch/riscv64 (0.38.3-1 to 0.38.3-1): Will attempt migration (Any information below is purely informational)
• nproc/riscv64 (0.5.1-4 to 0.5.1-4)
  • Migration status for nproc/riscv64 (0.5.1-4 to 0.5.1-4): Will attempt migration (Any information below is purely informational)
• nqc/riscv64 (3.1.r6-11 to 3.1.r6-11)
  • Migration status for nqc/riscv64 (3.1.r6-11 to 3.1.r6-11): Will attempt migration (Any information below is purely informational)
• ns2/riscv64 (2.35+dfsg-5 to 2.35+dfsg-5)
  • Migration status for ns2/riscv64 (2.35+dfsg-5 to 2.35+dfsg-5): Will attempt migration (Any information below is purely informational)
• nsis/riscv64 (3.10-2 to 3.10-2)
  • Migration status for nsis/riscv64 (3.10-2 to 3.10-2): Will attempt migration (Any information below is purely informational)
• nsnake/riscv64 (3.0.1-2.1 to 3.0.1-2.1)
  • Migration status for nsnake/riscv64 (3.0.1-2.1 to 3.0.1-2.1): 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)
• ntcard/riscv64 (1.2.2+dfsg-8 to 1.2.2+dfsg-8)
  • Migration status for ntcard/riscv64 (1.2.2+dfsg-8 to 1.2.2+dfsg-8): 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)
• ntfs2btrfs/riscv64 (20240115-1 to 20240115-1)
  • Migration status for ntfs2btrfs/riscv64 (20240115-1 to 20240115-1): Will attempt migration (Any information below is purely informational)
• nthash/riscv64 (2.3.0+dfsg-1 to 2.3.0+dfsg-1)
  • Migration status for nthash/riscv64 (2.3.0+dfsg-1 to 2.3.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• ntl/riscv64 (11.5.1-1 to 11.5.1-1)
  • Migration status for ntl/riscv64 (11.5.1-1 to 11.5.1-1): Will attempt migration (Any information below is purely informational)
• numcodecs/riscv64 (0.12.1+ds-1 to 0.12.1+ds-1)
  • Migration status for numcodecs/riscv64 (0.12.1+ds-1 to 0.12.1+ds-1): Will attempt migration (Any information below is purely informational)
• 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)
• numpy-stl/riscv64 (2.9.0-2 to 2.9.0-2)
  • Migration status for numpy-stl/riscv64 (2.9.0-2 to 2.9.0-2): Will attempt migration (Any information below is purely informational)
• numpy/riscv64 (1:1.26.4+ds-10 to 1:1.26.4+ds-10)
  • Migration status for numpy/riscv64 (1:1.26.4+ds-10 to 1:1.26.4+ds-10): Will attempt migration (Any information below is purely informational)
• numpy_pu (1:1.26.4+ds-10 to 1:1.24.2-1+deb12u1)
  • Migration status for numpy_pu (1:1.26.4+ds-10 to 1:1.24.2-1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: numpy is newer in the target suite (1:1.26.4+ds-10 1:1.24.2-1+deb12u1)
• 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)
• nurpawiki/amd64 (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/amd64 (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
• nurpawiki/arm64 (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/arm64 (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
• nurpawiki/armel (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/armel (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
• nurpawiki/armhf (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/armhf (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
• nurpawiki/i386 (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/i386 (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
• nurpawiki/mips64el (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/mips64el (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
• nurpawiki/ppc64el (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/ppc64el (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
• nurpawiki/s390x (1.2.4-4 to 1.2.4-4)
  • Migration status for nurpawiki/s390x (1.2.4-4 to 1.2.4-4): Will attempt migration (Any information below is purely informational)
• nuspell/riscv64 (5.1.4-1 to 5.1.4-1)
  • Migration status for nuspell/riscv64 (5.1.4-1 to 5.1.4-1): Will attempt migration (Any information below is purely informational)
• nvidia-cuda-toolkit/amd64 (12.1.1-1 to 12.1.1-1)
  • Migration status for nvidia-cuda-toolkit/amd64 (12.1.1-1 to 12.1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-cuda-toolkit/amd64 ucx (not considered)
    • Invalidated by dependency
• nvidia-cuda-toolkit/arm64 (12.1.1-1 to 12.1.1-1)
  • Migration status for nvidia-cuda-toolkit/arm64 (12.1.1-1 to 12.1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-cuda-toolkit/arm64 ucx (not considered)
    • Invalidated by dependency
• nvidia-vaapi-driver/riscv64 (0.0.8-1 to 0.0.8-1)
  • Migration status for nvidia-vaapi-driver/riscv64 (0.0.8-1 to 0.0.8-1): 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)
• nxtrim/riscv64 (0.4.3+dfsg-3 to 0.4.3+dfsg-3)
  • Migration status for nxtrim/riscv64 (0.4.3+dfsg-3 to 0.4.3+dfsg-3): Will attempt migration (Any information below is purely informational)
• nyquist/riscv64 (3.22+ds-2 to 3.22+ds-2)
  • Migration status for nyquist/riscv64 (3.22+ds-2 to 3.22+ds-2): 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)
• oakleaf/riscv64 (0.0.1-3 to 0.0.1-3)
  • Migration status for oakleaf/riscv64 (0.0.1-3 to 0.0.1-3): 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)
• oasis/amd64 (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/amd64 (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/amd64 ocamlbuild (not considered)
    • Invalidated by dependency
• oasis/arm64 (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/arm64 (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/arm64 ocamlbuild (not considered)
    • Invalidated by dependency
• oasis/armel (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/armel (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/armel ocamlbuild (not considered)
    • Invalidated by dependency
• oasis/armhf (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/armhf (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/armhf ocamlbuild (not considered)
    • Invalidated by dependency
• oasis/i386 (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/i386 (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/i386 ocamlbuild (not considered)
    • Invalidated by dependency
• oasis/mips64el (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/mips64el (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/mips64el ocamlbuild (not considered)
    • Invalidated by dependency
• oasis/ppc64el (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/ppc64el (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/ppc64el ocamlbuild (not considered)
    • Invalidated by dependency
• oasis/s390x (0.4.11-5 to 0.4.11-5)
  • Migration status for oasis/s390x (0.4.11-5 to 0.4.11-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: oasis/s390x ocamlbuild (not considered)
    • Invalidated by dependency
• 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)
• oath-toolkit/riscv64 (2.6.11-3 to 2.6.11-3)
  • Migration status for oath-toolkit/riscv64 (2.6.11-3 to 2.6.11-3): 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)
• obexfs/riscv64 (0.11-3 to 0.11-3)
  • Migration status for obexfs/riscv64 (0.11-3 to 0.11-3): Will attempt migration (Any information below is purely informational)
• obexftp/riscv64 (0.24-10 to 0.24-10)
  • Migration status for obexftp/riscv64 (0.24-10 to 0.24-10): 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-alsa/riscv64 (0.3.0-4 to 0.3.0-4)
  • Migration status for ocaml-alsa/riscv64 (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• ocaml-angstrom/riscv64 (0.16.0-1 to 0.16.0-1)
  • Migration status for ocaml-angstrom/riscv64 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-ao/riscv64 (0.2.4-3 to 0.2.4-3)
  • Migration status for ocaml-ao/riscv64 (0.2.4-3 to 0.2.4-3): Will attempt migration (Any information below is purely informational)
• ocaml-asn1-combinators/riscv64 (0.2.6-4 to 0.2.6-4)
  • Migration status for ocaml-asn1-combinators/riscv64 (0.2.6-4 to 0.2.6-4): Will attempt migration (Any information below is purely informational)
• ocaml-atd/riscv64 (2.15.0-1 to 2.15.0-1)
  • Migration status for ocaml-atd/riscv64 (2.15.0-1 to 2.15.0-1): Will attempt migration (Any information below is purely informational)
• 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-base64/riscv64 (3.5.1-2 to 3.5.1-2)
  • Migration status for ocaml-base64/riscv64 (3.5.1-2 to 3.5.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-benchmark/riscv64 (1.6-4 to 1.6-4)
  • Migration status for ocaml-benchmark/riscv64 (1.6-4 to 1.6-4): Will attempt migration (Any information below is purely informational)
• ocaml-bigarray-compat/riscv64 (1.1.0-3 to 1.1.0-3)
  • Migration status for ocaml-bigarray-compat/riscv64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-bigstringaf/riscv64 (0.9.1-1 to 0.9.1-1)
  • Migration status for ocaml-bigstringaf/riscv64 (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-bitstring/riscv64 (4.1.1-2 to 4.1.1-2)
  • Migration status for ocaml-bitstring/riscv64 (4.1.1-2 to 4.1.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-bjack/riscv64 (0.1.6-3 to 0.1.6-3)
  • Migration status for ocaml-bjack/riscv64 (0.1.6-3 to 0.1.6-3): Will attempt migration (Any information below is purely informational)
• ocaml-bos/riscv64 (0.2.1-2 to 0.2.1-2)
  • Migration status for ocaml-bos/riscv64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-cairo2/riscv64 (0.6.4+dfsg-2 to 0.6.4+dfsg-2)
  • Migration status for ocaml-cairo2/riscv64 (0.6.4+dfsg-2 to 0.6.4+dfsg-2): Will attempt migration (Any information below is purely informational)
• ocaml-charinfo-width/riscv64 (2.0.0-1 to 2.0.0-1)
  • Migration status for ocaml-charinfo-width/riscv64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-cpu/riscv64 (2.0.0-5 to 2.0.0-5)
  • Migration status for ocaml-cpu/riscv64 (2.0.0-5 to 2.0.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-crunch/riscv64 (3.3.1-1 to 3.3.1-1)
  • Migration status for ocaml-crunch/riscv64 (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-cry/riscv64 (1.0.3-1 to 1.0.3-1)
  • Migration status for ocaml-cry/riscv64 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• ocaml-csexp/riscv64 (1.5.2-4 to 1.5.2-4)
  • Migration status for ocaml-csexp/riscv64 (1.5.2-4 to 1.5.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-csv/riscv64 (2.4-3 to 2.4-3)
  • Migration status for ocaml-csv/riscv64 (2.4-3 to 2.4-3): Will attempt migration (Any information below is purely informational)
• ocaml-curses/riscv64 (1.0.11-4 to 1.0.11-4)
  • Migration status for ocaml-curses/riscv64 (1.0.11-4 to 1.0.11-4): Will attempt migration (Any information below is purely informational)
• ocaml-dbus/riscv64 (0.29-7 to 0.29-7)
  • Migration status for ocaml-dbus/riscv64 (0.29-7 to 0.29-7): Will attempt migration (Any information below is purely informational)
• ocaml-domain-name/riscv64 (0.4.0-3 to 0.4.0-3)
  • Migration status for ocaml-domain-name/riscv64 (0.4.0-3 to 0.4.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-dssi/riscv64 (0.1.5-3 to 0.1.5-3)
  • Migration status for ocaml-dssi/riscv64 (0.1.5-3 to 0.1.5-3): Will attempt migration (Any information below is purely informational)
• ocaml-dtools/riscv64 (0.4.5-1 to 0.4.5-1)
  • Migration status for ocaml-dtools/riscv64 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
• 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-duration/riscv64 (0.2.1-4 to 0.2.1-4)
  • Migration status for ocaml-duration/riscv64 (0.2.1-4 to 0.2.1-4): Will attempt migration (Any information below is purely informational)
• ocaml-expat/riscv64 (1.3.0-1 to 1.3.0-1)
  • Migration status for ocaml-expat/riscv64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-faad/riscv64 (0.5.1-5 to 0.5.1-5)
  • Migration status for ocaml-faad/riscv64 (0.5.1-5 to 0.5.1-5): Will attempt migration (Any information below is purely informational)
• ocaml-ffmpeg/riscv64 (1.1.11-1 to 1.1.11-1)
  • Migration status for ocaml-ffmpeg/riscv64 (1.1.11-1 to 1.1.11-1): Will attempt migration (Any information below is purely informational)
• ocaml-fileutils/riscv64 (0.6.4-4 to 0.6.4-4)
  • Migration status for ocaml-fileutils/riscv64 (0.6.4-4 to 0.6.4-4): Will attempt migration (Any information below is purely informational)
• ocaml-flac/riscv64 (0.5.0-1 to 0.5.0-1)
  • Migration status for ocaml-flac/riscv64 (0.5.0-1 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-fmt/riscv64 (0.9.0-3 to 0.9.0-3)
  • Migration status for ocaml-fmt/riscv64 (0.9.0-3 to 0.9.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-fpath/riscv64 (0.7.3-3 to 0.7.3-3)
  • Migration status for ocaml-fpath/riscv64 (0.7.3-3 to 0.7.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-frei0r/riscv64 (0.1.2-3 to 0.1.2-3)
  • Migration status for ocaml-frei0r/riscv64 (0.1.2-3 to 0.1.2-3): Will attempt migration (Any information below is purely informational)
• 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-gen/riscv64 (1.1-1 to 1.1-1)
  • Migration status for ocaml-gen/riscv64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-getopt/riscv64 (0.0.20230213-1 to 0.0.20230213-1)
  • Migration status for ocaml-getopt/riscv64 (0.0.20230213-1 to 0.0.20230213-1): Will attempt migration (Any information below is purely informational)
• ocaml-gmap/riscv64 (0.3.0-4 to 0.3.0-4)
  • Migration status for ocaml-gmap/riscv64 (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• ocaml-gnuplot/riscv64 (0.8.3-5 to 0.8.3-5)
  • Migration status for ocaml-gnuplot/riscv64 (0.8.3-5 to 0.8.3-5): Will attempt migration (Any information below is purely informational)
• ocaml-graphics/riscv64 (5.1.2-3 to 5.1.2-3)
  • Migration status for ocaml-graphics/riscv64 (5.1.2-3 to 5.1.2-3): 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-hex/riscv64 (1.5.0-3 to 1.5.0-3)
  • Migration status for ocaml-hex/riscv64 (1.5.0-3 to 1.5.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-hmap/riscv64 (0.8.1-2 to 0.8.1-2)
  • Migration status for ocaml-hmap/riscv64 (0.8.1-2 to 0.8.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-inifiles/riscv64 (1.2-6 to 1.2-6)
  • Migration status for ocaml-inifiles/riscv64 (1.2-6 to 1.2-6): Will attempt migration (Any information below is purely informational)
• ocaml-inotify/riscv64 (2.5-1 to 2.5-1)
  • Migration status for ocaml-inotify/riscv64 (2.5-1 to 2.5-1): Will attempt migration (Any information below is purely informational)
• ocaml-integers/riscv64 (0.7.0-3 to 0.7.0-3)
  • Migration status for ocaml-integers/riscv64 (0.7.0-3 to 0.7.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-ladspa/riscv64 (0.2.2-3 to 0.2.2-3)
  • Migration status for ocaml-ladspa/riscv64 (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• ocaml-lame/riscv64 (0.3.7-3 to 0.3.7-3)
  • Migration status for ocaml-lame/riscv64 (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
• 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-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-lo/riscv64 (0.2.0-4 to 0.2.0-4)
  • Migration status for ocaml-lo/riscv64 (0.2.0-4 to 0.2.0-4): Will attempt migration (Any information below is purely informational)
• 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-luv/riscv64 (0.5.12-2 to 0.5.12-2)
  • Migration status for ocaml-luv/riscv64 (0.5.12-2 to 0.5.12-2): Will attempt migration (Any information below is purely informational)
• ocaml-magic-mime/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for ocaml-magic-mime/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-magic/riscv64 (0.7.3-6 to 0.7.3-6)
  • Migration status for ocaml-magic/riscv64 (0.7.3-6 to 0.7.3-6): Will attempt migration (Any information below is purely informational)
• ocaml-mccs/riscv64 (1.1+17-1 to 1.1+17-1)
  • Migration status for ocaml-mccs/riscv64 (1.1+17-1 to 1.1+17-1): Will attempt migration (Any information below is purely informational)
• ocaml-merlin/riscv64 (4.13-414+ds-1 to 4.13-414+ds-1)
  • Migration status for ocaml-merlin/riscv64 (4.13-414+ds-1 to 4.13-414+ds-1): Will attempt migration (Any information below is purely informational)
• ocaml-metadata/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for ocaml-metadata/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-mew-vi/riscv64 (0.5.0-3 to 0.5.0-3)
  • Migration status for ocaml-mew-vi/riscv64 (0.5.0-3 to 0.5.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-mew/riscv64 (0.1.0-4 to 0.1.0-4)
  • Migration status for ocaml-mew/riscv64 (0.1.0-4 to 0.1.0-4): Will attempt migration (Any information below is purely informational)
• ocaml-mm/riscv64 (0.8.5-4 to 0.8.5-4)
  • Migration status for ocaml-mm/riscv64 (0.8.5-4 to 0.8.5-4): Will attempt migration (Any information below is purely informational)
• ocaml-mmap/riscv64 (1.2.0-3 to 1.2.0-3)
  • Migration status for ocaml-mmap/riscv64 (1.2.0-3 to 1.2.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-mtime/riscv64 (2.0.0-1 to 2.0.0-1)
  • Migration status for ocaml-mtime/riscv64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-num/riscv64 (1.5-1 to 1.5-1)
  • Migration status for ocaml-num/riscv64 (1.5-1 to 1.5-1): Will attempt migration (Any information below is purely informational)
• ocaml-ogg/riscv64 (0.7.4-3 to 0.7.4-3)
  • Migration status for ocaml-ogg/riscv64 (0.7.4-3 to 0.7.4-3): Will attempt migration (Any information below is purely informational)
• ocaml-opus/riscv64 (0.2.2-6 to 0.2.2-6)
  • Migration status for ocaml-opus/riscv64 (0.2.2-6 to 0.2.2-6): Will attempt migration (Any information below is purely informational)
• ocaml-parany/riscv64 (14.0.1-1 to 14.0.1-1)
  • Migration status for ocaml-parany/riscv64 (14.0.1-1 to 14.0.1-1): Will attempt migration (Any information below is purely informational)
• ocaml-parsexp/riscv64 (0.16.0-3 to 0.16.0-3)
  • Migration status for ocaml-parsexp/riscv64 (0.16.0-3 to 0.16.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-portaudio/riscv64 (0.2.3-3 to 0.2.3-3)
  • Migration status for ocaml-portaudio/riscv64 (0.2.3-3 to 0.2.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-pp/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for ocaml-pp/riscv64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-pprint/riscv64 (20230830-1 to 20230830-1)
  • Migration status for ocaml-pprint/riscv64 (20230830-1 to 20230830-1): Will attempt migration (Any information below is purely informational)
• ocaml-ptime/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for ocaml-ptime/riscv64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-ptmap/riscv64 (2.0.5-4 to 2.0.5-4)
  • Migration status for ocaml-ptmap/riscv64 (2.0.5-4 to 2.0.5-4): Will attempt migration (Any information below is purely informational)
• ocaml-pulseaudio/riscv64 (0.1.5-3 to 0.1.5-3)
  • Migration status for ocaml-pulseaudio/riscv64 (0.1.5-3 to 0.1.5-3): Will attempt migration (Any information below is purely informational)
• ocaml-qtest/riscv64 (2.11.2-4 to 2.11.2-4)
  • Migration status for ocaml-qtest/riscv64 (2.11.2-4 to 2.11.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-re/riscv64 (1.11.0-1 to 1.11.0-1)
  • Migration status for ocaml-re/riscv64 (1.11.0-1 to 1.11.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-reins/riscv64 (0.1a-11 to 0.1a-11)
  • Migration status for ocaml-reins/riscv64 (0.1a-11 to 0.1a-11): Will attempt migration (Any information below is purely informational)
• ocaml-res/riscv64 (5.0.1-3 to 5.0.1-3)
  • Migration status for ocaml-res/riscv64 (5.0.1-3 to 5.0.1-3): Will attempt migration (Any information below is purely informational)
• ocaml-result/riscv64 (1.5-4 to 1.5-4)
  • Migration status for ocaml-result/riscv64 (1.5-4 to 1.5-4): Will attempt migration (Any information below is purely informational)
• ocaml-rope/riscv64 (0.6.2-4 to 0.6.2-4)
  • Migration status for ocaml-rope/riscv64 (0.6.2-4 to 0.6.2-4): Will attempt migration (Any information below is purely informational)
• ocaml-rresult/riscv64 (0.7.0-2 to 0.7.0-2)
  • Migration status for ocaml-rresult/riscv64 (0.7.0-2 to 0.7.0-2): Will attempt migration (Any information below is purely informational)
• ocaml-samplerate/riscv64 (0.1.6-3 to 0.1.6-3)
  • Migration status for ocaml-samplerate/riscv64 (0.1.6-3 to 0.1.6-3): Will attempt migration (Any information below is purely informational)
• ocaml-sedlex/riscv64 (3.2-1 to 3.2-1)
  • Migration status for ocaml-sedlex/riscv64 (3.2-1 to 3.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-sha/riscv64 (1.15.4-3 to 1.15.4-3)
  • Migration status for ocaml-sha/riscv64 (1.15.4-3 to 1.15.4-3): Will attempt migration (Any information below is purely informational)
• ocaml-shine/riscv64 (0.2.3-3 to 0.2.3-3)
  • Migration status for ocaml-shine/riscv64 (0.2.3-3 to 0.2.3-3): Will attempt migration (Any information below is purely informational)
• ocaml-shout/riscv64 (0.2.7-2 to 0.2.7-2)
  • Migration status for ocaml-shout/riscv64 (0.2.7-2 to 0.2.7-2): Will attempt migration (Any information below is purely informational)
• ocaml-soundtouch/riscv64 (0.1.9-4 to 0.1.9-4)
  • Migration status for ocaml-soundtouch/riscv64 (0.1.9-4 to 0.1.9-4): Will attempt migration (Any information below is purely informational)
• ocaml-speex/riscv64 (0.4.1-4 to 0.4.1-4)
  • Migration status for ocaml-speex/riscv64 (0.4.1-4 to 0.4.1-4): Will attempt migration (Any information below is purely informational)
• ocaml-sqlite3/riscv64 (5.1.0-3 to 5.1.0-3)
  • Migration status for ocaml-sqlite3/riscv64 (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-ssl/riscv64 (0.7.0-1 to 0.7.0-1)
  • Migration status for ocaml-ssl/riscv64 (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-stringext/riscv64 (1.6.0-3 to 1.6.0-3)
  • Migration status for ocaml-stringext/riscv64 (1.6.0-3 to 1.6.0-3): Will attempt migration (Any information below is purely informational)
• ocaml-taglib/riscv64 (0.3.10-3 to 0.3.10-3)
  • Migration status for ocaml-taglib/riscv64 (0.3.10-3 to 0.3.10-3): Will attempt migration (Any information below is purely informational)
• ocaml-theora/riscv64 (0.4.0-5 to 0.4.0-5)
  • Migration status for ocaml-theora/riscv64 (0.4.0-5 to 0.4.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-topkg/riscv64 (1.0.7-1 to 1.0.7-1)
  • Migration status for ocaml-topkg/riscv64 (1.0.7-1 to 1.0.7-1): Will attempt migration (Any information below is purely informational)
• ocaml-trie/riscv64 (1.0.0-4 to 1.0.0-4)
  • Migration status for ocaml-trie/riscv64 (1.0.0-4 to 1.0.0-4): Will attempt migration (Any information below is purely informational)
• ocaml-unix-errno/riscv64 (0.6.2-1 to 0.6.2-1)
  • Migration status for ocaml-unix-errno/riscv64 (0.6.2-1 to 0.6.2-1): Will attempt migration (Any information below is purely informational)
• ocaml-uri/riscv64 (4.4.0-1 to 4.4.0-1)
  • Migration status for ocaml-uri/riscv64 (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-uucd/riscv64 (15.1.0-1 to 15.1.0-1)
  • Migration status for ocaml-uucd/riscv64 (15.1.0-1 to 15.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-uucp/riscv64 (15.1.0-1 to 15.1.0-1)
  • Migration status for ocaml-uucp/riscv64 (15.1.0-1 to 15.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-uunf/riscv64 (15.1.0-1 to 15.1.0-1)
  • Migration status for ocaml-uunf/riscv64 (15.1.0-1 to 15.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-uuseg/riscv64 (15.1.0-1 to 15.1.0-1)
  • Migration status for ocaml-uuseg/riscv64 (15.1.0-1 to 15.1.0-1): Will attempt migration (Any information below is purely informational)
• ocaml-voaacenc/riscv64 (0.1.1-2 to 0.1.1-2)
  • Migration status for ocaml-voaacenc/riscv64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• ocaml-vorbis/riscv64 (0.8.0-5 to 0.8.0-5)
  • Migration status for ocaml-vorbis/riscv64 (0.8.0-5 to 0.8.0-5): Will attempt migration (Any information below is purely informational)
• ocaml-xmlplaylist/riscv64 (0.1.5-4 to 0.1.5-4)
  • Migration status for ocaml-xmlplaylist/riscv64 (0.1.5-4 to 0.1.5-4): Will attempt migration (Any information below is purely informational)
• ocamlagrep/riscv64 (1.0-15 to 1.0-15)
  • Migration status for ocamlagrep/riscv64 (1.0-15 to 1.0-15): Will attempt migration (Any information below is purely informational)
• ocamlcreal/riscv64 (0.7-7 to 0.7-7)
  • Migration status for ocamlcreal/riscv64 (0.7-7 to 0.7-7): Will attempt migration (Any information below is purely informational)
• ocamlgraph/riscv64 (2.1.0-1 to 2.1.0-1)
  • Migration status for ocamlgraph/riscv64 (2.1.0-1 to 2.1.0-1): Will attempt migration (Any information below is purely informational)
• ocamlgsl/riscv64 (1.25.0-1 to 1.25.0-1)
  • Migration status for ocamlgsl/riscv64 (1.25.0-1 to 1.25.0-1): Will attempt migration (Any information below is purely informational)
• ocamlnet/amd64 (4.1.9-5 to 4.1.9-5)
  • Migration status for ocamlnet/amd64 (4.1.9-5 to 4.1.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlnet/amd64 camlzip (not considered)
    • Invalidated by dependency
• ocamlnet/arm64 (4.1.9-5 to 4.1.9-5)
  • Migration status for ocamlnet/arm64 (4.1.9-5 to 4.1.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlnet/arm64 camlzip (not considered)
    • Invalidated by dependency
• ocamlnet/armel (4.1.9-5 to 4.1.9-5)
  • Migration status for ocamlnet/armel (4.1.9-5 to 4.1.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlnet/armel camlzip (not considered)
    • Invalidated by dependency
• ocamlnet/armhf (4.1.9-5 to 4.1.9-5)
  • Migration status for ocamlnet/armhf (4.1.9-5 to 4.1.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlnet/armhf camlzip (not considered)
    • Invalidated by dependency
• ocamlnet/i386 (4.1.9-5 to 4.1.9-5)
  • Migration status for ocamlnet/i386 (4.1.9-5 to 4.1.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlnet/i386 camlzip (not considered)
    • Invalidated by dependency
• ocamlnet/mips64el (4.1.9-5 to 4.1.9-5)
  • Migration status for ocamlnet/mips64el (4.1.9-5 to 4.1.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlnet/mips64el camlzip (not considered)
    • Invalidated by dependency
• ocamlnet/ppc64el (4.1.9-5 to 4.1.9-5)
  • Migration status for ocamlnet/ppc64el (4.1.9-5 to 4.1.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlnet/ppc64el camlzip (not considered)
    • Invalidated by dependency
• ocamlnet/riscv64 (4.1.9-5 to 4.1.9-5)
  • Migration status for ocamlnet/riscv64 (4.1.9-5 to 4.1.9-5): Will attempt migration (Any information below is purely informational)
• ocamlnet/s390x (4.1.9-5 to 4.1.9-5)
  • Migration status for ocamlnet/s390x (4.1.9-5 to 4.1.9-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocamlnet/s390x camlzip (not considered)
    • Invalidated by dependency
• ocamlpam/riscv64 (1.1-6 to 1.1-6)
  • Migration status for ocamlpam/riscv64 (1.1-6 to 1.1-6): Will attempt migration (Any information below is purely informational)
• ocamlrss/riscv64 (2.2.2-2 to 2.2.2-2)
  • Migration status for ocamlrss/riscv64 (2.2.2-2 to 2.2.2-2): Will attempt migration (Any information below is purely informational)
• ocamlviz/riscv64 (1.01-8 to 1.01-8)
  • Migration status for ocamlviz/riscv64 (1.01-8 to 1.01-8): Will attempt migration (Any information below is purely informational)
• ocp-indent/riscv64 (1.8.2-5 to 1.8.2-5)
  • Migration status for ocp-indent/riscv64 (1.8.2-5 to 1.8.2-5): Will attempt migration (Any information below is purely informational)
• ocp/riscv64 (1:0.2.109+ds-1 to 1:0.2.109+ds-1)
  • Migration status for ocp/riscv64 (1:0.2.109+ds-1 to 1:0.2.109+ds-1): Will attempt migration (Any information below is purely informational)
• ocrad/riscv64 (0.28-4 to 0.28-4)
  • Migration status for ocrad/riscv64 (0.28-4 to 0.28-4): Will attempt migration (Any information below is purely informational)
• ocsigenserver/amd64 (5.1.2-2 to 5.1.2-2)
  • Migration status for ocsigenserver/amd64 (5.1.2-2 to 5.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocsigenserver/amd64 camlzip (not considered)
    • Invalidated by dependency
• ocsigenserver/arm64 (5.1.2-2 to 5.1.2-2)
  • Migration status for ocsigenserver/arm64 (5.1.2-2 to 5.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocsigenserver/arm64 camlzip (not considered)
    • Invalidated by dependency
• ocsigenserver/armel (5.1.2-2 to 5.1.2-2)
  • Migration status for ocsigenserver/armel (5.1.2-2 to 5.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocsigenserver/armel camlzip (not considered)
    • Invalidated by dependency
• ocsigenserver/armhf (5.1.2-2 to 5.1.2-2)
  • Migration status for ocsigenserver/armhf (5.1.2-2 to 5.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocsigenserver/armhf camlzip (not considered)
    • Invalidated by dependency
• ocsigenserver/i386 (5.1.2-2 to 5.1.2-2)
  • Migration status for ocsigenserver/i386 (5.1.2-2 to 5.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocsigenserver/i386 camlzip (not considered)
    • Invalidated by dependency
• ocsigenserver/mips64el (5.1.2-2 to 5.1.2-2)
  • Migration status for ocsigenserver/mips64el (5.1.2-2 to 5.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocsigenserver/mips64el camlzip (not considered)
    • Invalidated by dependency
• ocsigenserver/ppc64el (5.1.2-2 to 5.1.2-2)
  • Migration status for ocsigenserver/ppc64el (5.1.2-2 to 5.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocsigenserver/ppc64el camlzip (not considered)
    • Invalidated by dependency
• ocsigenserver/riscv64 (5.1.2-2 to 5.1.2-2)
  • Migration status for ocsigenserver/riscv64 (5.1.2-2 to 5.1.2-2): Will attempt migration (Any information below is purely informational)
• ocsigenserver/s390x (5.1.2-2 to 5.1.2-2)
  • Migration status for ocsigenserver/s390x (5.1.2-2 to 5.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ocsigenserver/s390x camlzip (not considered)
    • Invalidated by dependency
• ocsipersist/amd64 (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/amd64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• ocsipersist/arm64 (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/arm64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• ocsipersist/armel (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/armel (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• ocsipersist/armhf (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/armhf (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• ocsipersist/i386 (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/i386 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• ocsipersist/mips64el (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/mips64el (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• ocsipersist/ppc64el (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/ppc64el (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• ocsipersist/riscv64 (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/riscv64 (1.1.0-3 to 1.1.0-3): Will attempt migration (Any information below is purely informational)
• ocsipersist/s390x (1.1.0-3 to 1.1.0-3)
  • Migration status for ocsipersist/s390x (1.1.0-3 to 1.1.0-3): 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-miscellaneous/riscv64 (1.3.0-5 to 1.3.0-5)
  • Migration status for octave-miscellaneous/riscv64 (1.3.0-5 to 1.3.0-5): 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)
• octomap/riscv64 (1.9.7+dfsg-3.1 to 1.9.7+dfsg-3.1)
  • Migration status for octomap/riscv64 (1.9.7+dfsg-3.1 to 1.9.7+dfsg-3.1): Will attempt migration (Any information below is purely informational)
• ocurl/riscv64 (0.9.2-3 to 0.9.2-3)
  • Migration status for ocurl/riscv64 (0.9.2-3 to 0.9.2-3): Will attempt migration (Any information below is purely informational)
• odb/riscv64 (2.4.0-16 to 2.4.0-16)
  • Migration status for odb/riscv64 (2.4.0-16 to 2.4.0-16): 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)
• ode/riscv64 (2:0.16.2-1.1 to 2:0.16.2-1.1)
  • Migration status for ode/riscv64 (2:0.16.2-1.1 to 2:0.16.2-1.1): Will attempt migration (Any information below is purely informational)
• odil/riscv64 (0.12.2-4.1 to 0.12.2-4.1)
  • Migration status for odil/riscv64 (0.12.2-4.1 to 0.12.2-4.1): Will attempt migration (Any information below is purely informational)
• odr-dabmod/riscv64 (2.6.0+ds-1 to 2.6.0+ds-1)
  • Migration status for odr-dabmod/riscv64 (2.6.0+ds-1 to 2.6.0+ds-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)
• oggvideotools/riscv64 (0.9.1-7 to 0.9.1-7)
  • Migration status for oggvideotools/riscv64 (0.9.1-7 to 0.9.1-7): Will attempt migration (Any information below is purely informational)
• ogmtools/riscv64 (1:1.5-4.1 to 1:1.5-4.1)
  • Migration status for ogmtools/riscv64 (1:1.5-4.1 to 1:1.5-4.1): 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)
• oidc-agent/riscv64 (4.2.6-1.1 to 4.2.6-1.1)
  • Migration status for oidc-agent/riscv64 (4.2.6-1.1 to 4.2.6-1.1): Will attempt migration (Any information below is purely informational)
• ois/riscv64 (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7)
  • Migration status for ois/riscv64 (1.3.0+dfsg0-7 to 1.3.0+dfsg0-7): Will attempt migration (Any information below is purely informational)
• okteta/riscv64 (5:0.26.15-1 to 5:0.26.15-1)
  • Migration status for okteta/riscv64 (5:0.26.15-1 to 5:0.26.15-1): 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)
• olm/riscv64 (3.2.16+dfsg-2 to 3.2.16+dfsg-2)
  • Migration status for olm/riscv64 (3.2.16+dfsg-2 to 3.2.16+dfsg-2): Will attempt migration (Any information below is purely informational)
• omemo-dr/riscv64 (1.0.1-2 to 1.0.1-2)
  • Migration status for omemo-dr/riscv64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• omnidb-plpgsql-debugger/riscv64 (3.0.0.20201026-5 to 3.0.0.20201026-5)
  • Migration status for omnidb-plpgsql-debugger/riscv64 (3.0.0.20201026-5 to 3.0.0.20201026-5): Will attempt migration (Any information below is purely informational)
• omniorb-dfsg/riscv64 (4.3.2+ds1-1.1 to 4.3.2+ds1-1.1)
  • Migration status for omniorb-dfsg/riscv64 (4.3.2+ds1-1.1 to 4.3.2+ds1-1.1): Will attempt migration (Any information below is purely informational)
• ompl/riscv64 (1.5.2+ds1-1.1 to 1.5.2+ds1-1.1)
  • Migration status for ompl/riscv64 (1.5.2+ds1-1.1 to 1.5.2+ds1-1.1): Will attempt migration (Any information below is purely informational)
• onnx/riscv64 (1.14.1-2.1 to 1.14.1-2.1)
  • Migration status for onnx/riscv64 (1.14.1-2.1 to 1.14.1-2.1): 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)
• ont-fast5-api/riscv64 (4.1.1+dfsg-3 to 4.1.1+dfsg-3)
  • Migration status for ont-fast5-api/riscv64 (4.1.1+dfsg-3 to 4.1.1+dfsg-3): Will attempt migration (Any information below is purely informational)
• oomd/riscv64 (0.5.0-1.2 to 0.5.0-1.2)
  • Migration status for oomd/riscv64 (0.5.0-1.2 to 0.5.0-1.2): Will attempt migration (Any information below is purely informational)
• opam-file-format/riscv64 (2.1.6-1 to 2.1.6-1)
  • Migration status for opam-file-format/riscv64 (2.1.6-1 to 2.1.6-1): Will attempt migration (Any information below is purely informational)
• opari/riscv64 (1.1+dfsg-9 to 1.1+dfsg-9)
  • Migration status for opari/riscv64 (1.1+dfsg-9 to 1.1+dfsg-9): Will attempt migration (Any information below is purely informational)
• opari2/riscv64 (2.0.7-2 to 2.0.7-2)
  • Migration status for opari2/riscv64 (2.0.7-2 to 2.0.7-2): 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)
• open-invaders/riscv64 (0.3-9 to 0.3-9)
  • Migration status for open-invaders/riscv64 (0.3-9 to 0.3-9): Will attempt migration (Any information below is purely informational)
• open-jtalk/riscv64 (1.11-5 to 1.11-5)
  • Migration status for open-jtalk/riscv64 (1.11-5 to 1.11-5): Will attempt migration (Any information below is purely informational)
• openal-soft/riscv64 (1:1.23.1-4 to 1:1.23.1-4)
  • Migration status for openal-soft/riscv64 (1:1.23.1-4 to 1:1.23.1-4): 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)
• openblas/riscv64 (0.3.27+ds-2 to 0.3.27+ds-2)
  • Migration status for openblas/riscv64 (0.3.27+ds-2 to 0.3.27+ds-2): Will attempt migration (Any information below is purely informational)
• openboard/riscv64 (1.6.4+dfsg-1 to 1.6.4+dfsg-1)
  • Migration status for openboard/riscv64 (1.6.4+dfsg-1 to 1.6.4+dfsg-1): 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)
• opencamlib/riscv64 (2023.01.11-5 to 2023.01.11-5)
  • Migration status for opencamlib/riscv64 (2023.01.11-5 to 2023.01.11-5): Will attempt migration (Any information below is purely informational)
• opencc/riscv64 (1.1.7+ds1-1 to 1.1.7+ds1-1)
  • Migration status for opencc/riscv64 (1.1.7+ds1-1 to 1.1.7+ds1-1): 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-15/riscv64 (15.0.0-3 to 15.0.0-3)
  • Migration status for opencl-clang-15/riscv64 (15.0.0-3 to 15.0.0-3): Will attempt migration (Any information below is purely informational)
• opencl-clang-16/riscv64 (16.0.0-3.1 to 16.0.0-3.1)
  • Migration status for opencl-clang-16/riscv64 (16.0.0-3.1 to 16.0.0-3.1): 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)
• openctm/riscv64 (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3)
  • Migration status for openctm/riscv64 (1.0.3+dfsg1-3 to 1.0.3+dfsg1-3): Will attempt migration (Any information below is purely informational)
• opencv/riscv64 (4.6.0+dfsg-13.1 to 4.6.0+dfsg-13.1)
  • Migration status for opencv/riscv64 (4.6.0+dfsg-13.1 to 4.6.0+dfsg-13.1): Will attempt migration (Any information below is purely informational)
• opendht/riscv64 (3.0.1-1.1 to 3.0.1-1.1)
  • Migration status for opendht/riscv64 (3.0.1-1.1 to 3.0.1-1.1): Will attempt migration (Any information below is purely informational)
• opendkim/riscv64 (2.11.0~beta2-9 to 2.11.0~beta2-9)
  • Migration status for opendkim/riscv64 (2.11.0~beta2-9 to 2.11.0~beta2-9): Will attempt migration (Any information below is purely informational)
• opendnssec/riscv64 (1:2.1.13-1.1 to 1:2.1.13-1.1)
  • Migration status for opendnssec/riscv64 (1:2.1.13-1.1 to 1:2.1.13-1.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)
• openexr/riscv64 (3.1.5-5.1 to 3.1.5-5.1)
  • Migration status for openexr/riscv64 (3.1.5-5.1 to 3.1.5-5.1): Will attempt migration (Any information below is purely informational)
• openfoam/riscv64 (1912.200626-2 to 1912.200626-2)
  • Migration status for openfoam/riscv64 (1912.200626-2 to 1912.200626-2): Will attempt migration (Any information below is purely informational)
• openfpgaloader/riscv64 (0.12.0-1 to 0.12.0-1)
  • Migration status for openfpgaloader/riscv64 (0.12.0-1 to 0.12.0-1): Will attempt migration (Any information below is purely informational)
• openfst/riscv64 (1.7.9-5 to 1.7.9-5)
  • Migration status for openfst/riscv64 (1.7.9-5 to 1.7.9-5): Will attempt migration (Any information below is purely informational)
• opengv/riscv64 (1.0+1git91f4b1-7.1 to 1.0+1git91f4b1-7.1)
  • Migration status for opengv/riscv64 (1.0+1git91f4b1-7.1 to 1.0+1git91f4b1-7.1): Will attempt migration (Any information below is purely informational)
• openh264/riscv64 (2.4.1+dfsg-1 to 2.4.1+dfsg-1)
  • Migration status for openh264/riscv64 (2.4.1+dfsg-1 to 2.4.1+dfsg-1): 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)
• openigtlink/riscv64 (1.11.0-4 to 1.11.0-4)
  • Migration status for openigtlink/riscv64 (1.11.0-4 to 1.11.0-4): Will attempt migration (Any information below is purely informational)
• openjade/riscv64 (1.4devel1-23.1 to 1.4devel1-23.1)
  • Migration status for openjade/riscv64 (1.4devel1-23.1 to 1.4devel1-23.1): Will attempt migration (Any information below is purely informational)
• openjazz/riscv64 (20231028-2 to 20231028-2)
  • Migration status for openjazz/riscv64 (20231028-2 to 20231028-2): Will attempt migration (Any information below is purely informational)
• openjpeg2/riscv64 (2.5.0-2 to 2.5.0-2)
  • Migration status for openjpeg2/riscv64 (2.5.0-2 to 2.5.0-2): Will attempt migration (Any information below is purely informational)
• openjph/riscv64 (0.9.0-3 to 0.9.0-3)
  • Migration status for openjph/riscv64 (0.9.0-3 to 0.9.0-3): Will attempt migration (Any information below is purely informational)
• openkim-models/riscv64 (1:2021.01.28-2 to 1:2021.01.28-2)
  • Migration status for openkim-models/riscv64 (1:2021.01.28-2 to 1:2021.01.28-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)
• openocd/riscv64 (0.12.0-1 to 0.12.0-1)
  • Migration status for openocd/riscv64 (0.12.0-1 to 0.12.0-1): 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)
• opensaml/riscv64 (3.2.1-4.1 to 3.2.1-4.1)
  • Migration status for opensaml/riscv64 (3.2.1-4.1 to 3.2.1-4.1): Will attempt migration (Any information below is purely informational)
• openscap/amd64 (1.3.10+dfsg-3 to 1.3.10+dfsg-3)
  • Migration status for openscap/amd64 (1.3.10+dfsg-3 to 1.3.10+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: openscap/amd64 libgcrypt20 (not considered)
    • Invalidated by dependency
• openscap/arm64 (1.3.10+dfsg-3 to 1.3.10+dfsg-3)
  • Migration status for openscap/arm64 (1.3.10+dfsg-3 to 1.3.10+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: openscap/arm64 libgcrypt20 (not considered)
    • Invalidated by dependency
• openscap/armel (1.3.10+dfsg-3 to 1.3.10+dfsg-3)
  • Migration status for openscap/armel (1.3.10+dfsg-3 to 1.3.10+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: openscap/armel libgcrypt20 (not considered)
    • Invalidated by dependency
• openscap/armhf (1.3.10+dfsg-3 to 1.3.10+dfsg-3)
  • Migration status for openscap/armhf (1.3.10+dfsg-3 to 1.3.10+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: openscap/armhf libgcrypt20 (not considered)
    • Invalidated by dependency
• openscap/i386 (1.3.10+dfsg-3 to 1.3.10+dfsg-3)
  • Migration status for openscap/i386 (1.3.10+dfsg-3 to 1.3.10+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: openscap/i386 libgcrypt20 (not considered)
    • Invalidated by dependency
• openscap/mips64el (1.3.10+dfsg-3 to 1.3.10+dfsg-3)
  • Migration status for openscap/mips64el (1.3.10+dfsg-3 to 1.3.10+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: openscap/mips64el libgcrypt20 (not considered)
    • Invalidated by dependency
• openscap/ppc64el (1.3.10+dfsg-3 to 1.3.10+dfsg-3)
  • Migration status for openscap/ppc64el (1.3.10+dfsg-3 to 1.3.10+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: openscap/ppc64el libgcrypt20 (not considered)
    • Invalidated by dependency
• openscap/s390x (1.3.10+dfsg-3 to 1.3.10+dfsg-3)
  • Migration status for openscap/s390x (1.3.10+dfsg-3 to 1.3.10+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: openscap/s390x libgcrypt20 (not considered)
    • Invalidated by dependency
• 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)
• opensp/riscv64 (1.5.2-15 to 1.5.2-15)
  • Migration status for opensp/riscv64 (1.5.2-15 to 1.5.2-15): Will attempt migration (Any information below is purely informational)
• openssh_pu (1:9.7p1-7 to 1:9.2p1-2+deb12u3)
  • Migration status for openssh_pu (1:9.7p1-7 to 1:9.2p1-2+deb12u3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: openssh is newer in the target suite (1:9.7p1-7 1:9.2p1-2+deb12u3)
• 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)
• openstack-trove/amd64 (1:21.0.1-2 to 1:21.0.1-2)
  • Migration status for openstack-trove/amd64 (1:21.0.1-2 to 1:21.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
• openstack-trove/arm64 (1:21.0.1-2 to 1:21.0.1-2)
  • Migration status for openstack-trove/arm64 (1:21.0.1-2 to 1:21.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
• openstack-trove/armel (1:21.0.1-2 to 1:21.0.1-2)
  • Migration status for openstack-trove/armel (1:21.0.1-2 to 1:21.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
• openstack-trove/armhf (1:21.0.1-2 to 1:21.0.1-2)
  • Migration status for openstack-trove/armhf (1:21.0.1-2 to 1:21.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
• openstack-trove/i386 (1:21.0.1-2 to 1:21.0.1-2)
  • Migration status for openstack-trove/i386 (1:21.0.1-2 to 1:21.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
• openstack-trove/mips64el (1:21.0.1-2 to 1:21.0.1-2)
  • Migration status for openstack-trove/mips64el (1:21.0.1-2 to 1:21.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
• openstack-trove/ppc64el (1:21.0.1-2 to 1:21.0.1-2)
  • Migration status for openstack-trove/ppc64el (1:21.0.1-2 to 1:21.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
• openstack-trove/riscv64 (1:21.0.1-2 to 1:21.0.1-2)
  • Migration status for openstack-trove/riscv64 (1:21.0.1-2 to 1:21.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
• openstack-trove/s390x (1:21.0.1-2 to 1:21.0.1-2)
  • Migration status for openstack-trove/s390x (1:21.0.1-2 to 1:21.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
• opentracing-c-wrapper/riscv64 (1.1.3-3.1 to 1.1.3-3.1)
  • Migration status for opentracing-c-wrapper/riscv64 (1.1.3-3.1 to 1.1.3-3.1): Will attempt migration (Any information below is purely informational)
• opentracing-cpp/riscv64 (1.6.0-4 to 1.6.0-4)
  • Migration status for opentracing-cpp/riscv64 (1.6.0-4 to 1.6.0-4): Will attempt migration (Any information below is purely informational)
• opentype-sanitizer/riscv64 (8.2.1+dfsg-2 to 8.2.1+dfsg-2)
  • Migration status for opentype-sanitizer/riscv64 (8.2.1+dfsg-2 to 8.2.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• opentyrian/riscv64 (2.1.20221123-1 to 2.1.20221123-1)
  • Migration status for opentyrian/riscv64 (2.1.20221123-1 to 2.1.20221123-1): 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)
• openvanilla-modules/riscv64 (0.9.0a1.3+dfsg1-3 to 0.9.0a1.3+dfsg1-3)
  • Migration status for openvanilla-modules/riscv64 (0.9.0a1.3+dfsg1-3 to 0.9.0a1.3+dfsg1-3): Will attempt migration (Any information below is purely informational)
• openvlbi/riscv64 (3.0.2-2.1 to 3.0.2-2.1)
  • Migration status for openvlbi/riscv64 (3.0.2-2.1 to 3.0.2-2.1): Will attempt migration (Any information below is purely informational)
• openvpn-auth-ldap/riscv64 (2.0.4-3 to 2.0.4-3)
  • Migration status for openvpn-auth-ldap/riscv64 (2.0.4-3 to 2.0.4-3): Will attempt migration (Any information below is purely informational)
• openvpn-auth-radius/riscv64 (2.1-8 to 2.1-8)
  • Migration status for openvpn-auth-radius/riscv64 (2.1-8 to 2.1-8): 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)
• orbital-eunuchs-sniper/riscv64 (1.30+svn20070601-4.1 to 1.30+svn20070601-4.1)
  • Migration status for orbital-eunuchs-sniper/riscv64 (1.30+svn20070601-4.1 to 1.30+svn20070601-4.1): Will attempt migration (Any information below is purely informational)
• orocos-bfl/riscv64 (0.8.0-6 to 0.8.0-6)
  • Migration status for orocos-bfl/riscv64 (0.8.0-6 to 0.8.0-6): Will attempt migration (Any information below is purely informational)
• orocos-kdl/riscv64 (1.5.1-4 to 1.5.1-4)
  • Migration status for orocos-kdl/riscv64 (1.5.1-4 to 1.5.1-4): 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)
• ortp/riscv64 (1:5.2.0-2 to 1:5.2.0-2)
  • Migration status for ortp/riscv64 (1:5.2.0-2 to 1:5.2.0-2): 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)
• oscpack/riscv64 (1.1.0-3 to 1.1.0-3)
  • Migration status for oscpack/riscv64 (1.1.0-3 to 1.1.0-3): 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)
• osm2pgrouting/riscv64 (2.3.8-2 to 2.3.8-2)
  • Migration status for osm2pgrouting/riscv64 (2.3.8-2 to 2.3.8-2): Will attempt migration (Any information below is purely informational)
• osm2pgsql/riscv64 (1.11.0+ds-1 to 1.11.0+ds-1)
  • Migration status for osm2pgsql/riscv64 (1.11.0+ds-1 to 1.11.0+ds-1): 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)
• osmid/riscv64 (0.8.0~repack-3 to 0.8.0~repack-3)
  • Migration status for osmid/riscv64 (0.8.0~repack-3 to 0.8.0~repack-3): Will attempt migration (Any information below is purely informational)
• osmium-tool/riscv64 (1.16.0-1 to 1.16.0-1)
  • Migration status for osmium-tool/riscv64 (1.16.0-1 to 1.16.0-1): Will attempt migration (Any information below is purely informational)
• osmo-bsc/riscv64 (1.9.0-3 to 1.9.0-3)
  • Migration status for osmo-bsc/riscv64 (1.9.0-3 to 1.9.0-3): Will attempt migration (Any information below is purely informational)
• osmo-bts/riscv64 (1.5.0+dfsg1-3 to 1.5.0+dfsg1-3)
  • Migration status for osmo-bts/riscv64 (1.5.0+dfsg1-3 to 1.5.0+dfsg1-3): Will attempt migration (Any information below is purely informational)
• osmo-hlr/riscv64 (1.5.0+dfsg1-4 to 1.5.0+dfsg1-4)
  • Migration status for osmo-hlr/riscv64 (1.5.0+dfsg1-4 to 1.5.0+dfsg1-4): Will attempt migration (Any information below is purely informational)
• osmo-mgw/riscv64 (1.10.0+dfsg1-3 to 1.10.0+dfsg1-3)
  • Migration status for osmo-mgw/riscv64 (1.10.0+dfsg1-3 to 1.10.0+dfsg1-3): Will attempt migration (Any information below is purely informational)
• osmo-msc/riscv64 (1.9.0+dfsg1-2 to 1.9.0+dfsg1-2)
  • Migration status for osmo-msc/riscv64 (1.9.0+dfsg1-2 to 1.9.0+dfsg1-2): Will attempt migration (Any information below is purely informational)
• osmo-pcu/riscv64 (1.1.0-4 to 1.1.0-4)
  • Migration status for osmo-pcu/riscv64 (1.1.0-4 to 1.1.0-4): Will attempt migration (Any information below is purely informational)
• osmo-sgsn/riscv64 (1.9.0+dfsg1-3 to 1.9.0+dfsg1-3)
  • Migration status for osmo-sgsn/riscv64 (1.9.0+dfsg1-3 to 1.9.0+dfsg1-3): Will attempt migration (Any information below is purely informational)
• osmo-trx/riscv64 (1.4.1-2 to 1.4.1-2)
  • Migration status for osmo-trx/riscv64 (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
• osmo/riscv64 (0.4.4-2.1 to 0.4.4-2.1)
  • Migration status for osmo/riscv64 (0.4.4-2.1 to 0.4.4-2.1): 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)
• osmpbf/riscv64 (1.5.1-1 to 1.5.1-1)
  • Migration status for osmpbf/riscv64 (1.5.1-1 to 1.5.1-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)
• ossp-uuid/riscv64 (1.6.2-1.5 to 1.6.2-1.5)
  • Migration status for ossp-uuid/riscv64 (1.6.2-1.5 to 1.6.2-1.5): 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)
• otf2/riscv64 (3.0.3-3.1 to 3.0.3-3.1)
  • Migration status for otf2/riscv64 (3.0.3-3.1 to 3.0.3-3.1): 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)
• ounit/riscv64 (2.2.7-2 to 2.2.7-2)
  • Migration status for ounit/riscv64 (2.2.7-2 to 2.2.7-2): 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)
• p8-platform/riscv64 (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4)
  • Migration status for p8-platform/riscv64 (2.1.0.1+dfsg1-4 to 2.1.0.1+dfsg1-4): Will attempt migration (Any information below is purely informational)
• pa-ounit/riscv64 (113.00.00-5 to 113.00.00-5)
  • Migration status for pa-ounit/riscv64 (113.00.00-5 to 113.00.00-5): Will attempt migration (Any information below is purely informational)
• pachi/riscv64 (1:1.0-11 to 1:1.0-11)
  • Migration status for pachi/riscv64 (1:1.0-11 to 1:1.0-11): Will attempt migration (Any information below is purely informational)
• packmol/riscv64 (1:20.14.3-1 to 1:20.14.3-1)
  • Migration status for packmol/riscv64 (1:20.14.3-1 to 1:20.14.3-1): Will attempt migration (Any information below is purely informational)
• packup/riscv64 (0.6-3.1 to 0.6-3.1)
  • Migration status for packup/riscv64 (0.6-3.1 to 0.6-3.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)
• pacman/riscv64 (10-20 to 10-20)
  • Migration status for pacman/riscv64 (10-20 to 10-20): Will attempt migration (Any information below is purely informational)
• pacvim/riscv64 (1.1.1-1.1 to 1.1.1-1.1)
  • Migration status for pacvim/riscv64 (1.1.1-1.1 to 1.1.1-1.1): Will attempt migration (Any information below is purely informational)
• padthv1/riscv64 (0.9.90-1 to 0.9.90-1)
  • Migration status for padthv1/riscv64 (0.9.90-1 to 0.9.90-1): Will attempt migration (Any information below is purely informational)
• pagmo/riscv64 (2.19.0-3.1 to 2.19.0-3.1)
  • Migration status for pagmo/riscv64 (2.19.0-3.1 to 2.19.0-3.1): Will attempt migration (Any information below is purely informational)
• pagodacf/riscv64 (0.10-7 to 0.10-7)
  • Migration status for pagodacf/riscv64 (0.10-7 to 0.10-7): Will attempt migration (Any information below is purely informational)
• paho.mqtt.cpp/riscv64 (1.2.0-2 to 1.2.0-2)
  • Migration status for paho.mqtt.cpp/riscv64 (1.2.0-2 to 1.2.0-2): 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)
• paje.app/riscv64 (1.98-1.1 to 1.98-1.1)
  • Migration status for paje.app/riscv64 (1.98-1.1 to 1.98-1.1): Will attempt migration (Any information below is purely informational)
• pajeng/riscv64 (1.3.6-4 to 1.3.6-4)
  • Migration status for pajeng/riscv64 (1.3.6-4 to 1.3.6-4): 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)
• pamix/riscv64 (1.6~git20180112.ea4ab3b-4 to 1.6~git20180112.ea4ab3b-4)
  • Migration status for pamix/riscv64 (1.6~git20180112.ea4ab3b-4 to 1.6~git20180112.ea4ab3b-4): Will attempt migration (Any information below is purely informational)
• pamixer/riscv64 (1.6-1 to 1.6-1)
  • Migration status for pamixer/riscv64 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
• pandoc/riscv64 (3.1.3+ds-3 to 3.1.3+ds-3)
  • Migration status for pandoc/riscv64 (3.1.3+ds-3 to 3.1.3+ds-3): Will attempt migration (Any information below is purely informational)
• pangomm/riscv64 (2.46.4-1 to 2.46.4-1)
  • Migration status for pangomm/riscv64 (2.46.4-1 to 2.46.4-1): Will attempt migration (Any information below is purely informational)
• pangomm2.48/riscv64 (2.52.0-1 to 2.52.0-1)
  • Migration status for pangomm2.48/riscv64 (2.52.0-1 to 2.52.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)
• paps/riscv64 (0.6.8-7.2 to 0.6.8-7.2)
  • Migration status for paps/riscv64 (0.6.8-7.2 to 0.6.8-7.2): Will attempt migration (Any information below is purely informational)
• paq/riscv64 (0.1.1+git20170722.9c5d493-6 to 0.1.1+git20170722.9c5d493-6)
  • Migration status for paq/riscv64 (0.1.1+git20170722.9c5d493-6 to 0.1.1+git20170722.9c5d493-6): Will attempt migration (Any information below is purely informational)
• par2cmdline/riscv64 (0.8.1-3 to 0.8.1-3)
  • Migration status for par2cmdline/riscv64 (0.8.1-3 to 0.8.1-3): Will attempt migration (Any information below is purely informational)
• paraclu/riscv64 (10-1 to 10-1)
  • Migration status for paraclu/riscv64 (10-1 to 10-1): Will attempt migration (Any information below is purely informational)
• parafly/riscv64 (0.1.0-4 to 0.1.0-4)
  • Migration status for parafly/riscv64 (0.1.0-4 to 0.1.0-4): Will attempt migration (Any information below is purely informational)
• parasail/riscv64 (2.6.2+dfsg-1 to 2.6.2+dfsg-1)
  • Migration status for parasail/riscv64 (2.6.2+dfsg-1 to 2.6.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• parcellite/riscv64 (1.2.1-8 to 1.2.1-8)
  • Migration status for parcellite/riscv64 (1.2.1-8 to 1.2.1-8): Will attempt migration (Any information below is purely informational)
• parlatype/riscv64 (3.1-3.1 to 3.1-3.1)
  • Migration status for parlatype/riscv64 (3.1-3.1 to 3.1-3.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)
• parser-mysql/riscv64 (10.8-3 to 10.8-3)
  • Migration status for parser-mysql/riscv64 (10.8-3 to 10.8-3): Will attempt migration (Any information below is purely informational)
• parsnp/riscv64 (2.0.5+dfsg-1 to 2.0.5+dfsg-1)
  • Migration status for parsnp/riscv64 (2.0.5+dfsg-1 to 2.0.5+dfsg-1): Will attempt migration (Any information below is purely informational)
• partimage/riscv64 (0.6.9-11 to 0.6.9-11)
  • Migration status for partimage/riscv64 (0.6.9-11 to 0.6.9-11): 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)
• passage/riscv64 (4+dfsg1-3 to 4+dfsg1-3)
  • Migration status for passage/riscv64 (4+dfsg1-3 to 4+dfsg1-3): 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)
• passwordmaker-cli/riscv64 (1.5+dfsg-6 to 1.5+dfsg-6)
  • Migration status for passwordmaker-cli/riscv64 (1.5+dfsg-6 to 1.5+dfsg-6): 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)
• patchelf/riscv64 (0.18.0-1.1 to 0.18.0-1.1)
  • Migration status for patchelf/riscv64 (0.18.0-1.1 to 0.18.0-1.1): Will attempt migration (Any information below is purely informational)
• pathogen/riscv64 (1.1.1-5 to 1.1.1-5)
  • Migration status for pathogen/riscv64 (1.1.1-5 to 1.1.1-5): Will attempt migration (Any information below is purely informational)
• patman/riscv64 (1.2.2+dfsg-8 to 1.2.2+dfsg-8)
  • Migration status for patman/riscv64 (1.2.2+dfsg-8 to 1.2.2+dfsg-8): Will attempt migration (Any information below is purely informational)
• pavucontrol-qt/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for pavucontrol-qt/riscv64 (1.4.0-1 to 1.4.0-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)
• pbbam/riscv64 (2.4.0+dfsg-1 to 2.4.0+dfsg-1)
  • Migration status for pbbam/riscv64 (2.4.0+dfsg-1 to 2.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• pbcopper/riscv64 (2.3.0+dfsg-2 to 2.3.0+dfsg-2)
  • Migration status for pbcopper/riscv64 (2.3.0+dfsg-2 to 2.3.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• pbdagcon/riscv64 (0.3+git20180411.c14c422+dfsg-8 to 0.3+git20180411.c14c422+dfsg-8)
  • Migration status for pbdagcon/riscv64 (0.3+git20180411.c14c422+dfsg-8 to 0.3+git20180411.c14c422+dfsg-8): Will attempt migration (Any information below is purely informational)
• pbseqlib/riscv64 (5.3.5+dfsg-6 to 5.3.5+dfsg-6)
  • Migration status for pbseqlib/riscv64 (5.3.5+dfsg-6 to 5.3.5+dfsg-6): Will attempt migration (Any information below is purely informational)
• pbzip2/riscv64 (1.1.13-1 to 1.1.13-1)
  • Migration status for pbzip2/riscv64 (1.1.13-1 to 1.1.13-1): Will attempt migration (Any information below is purely informational)
• pcapy/riscv64 (0.11.5-3 to 0.11.5-3)
  • Migration status for pcapy/riscv64 (0.11.5-3 to 0.11.5-3): Will attempt migration (Any information below is purely informational)
• pcf2bdf/riscv64 (1.07-1 to 1.07-1)
  • Migration status for pcf2bdf/riscv64 (1.07-1 to 1.07-1): Will attempt migration (Any information below is purely informational)
• pchar/riscv64 (1.5-6 to 1.5-6)
  • Migration status for pchar/riscv64 (1.5-6 to 1.5-6): 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)
• pcre2-ocaml/riscv64 (7.5.2-1 to 7.5.2-1)
  • Migration status for pcre2-ocaml/riscv64 (7.5.2-1 to 7.5.2-1): Will attempt migration (Any information below is purely informational)
• pcre3/riscv64 (2:8.39-15 to 2:8.39-15)
  • Migration status for pcre3/riscv64 (2:8.39-15 to 2:8.39-15): Will attempt migration (Any information below is purely informational)
• pcsc-cyberjack/riscv64 (3.99.5final.sp14-2 to 3.99.5final.sp14-2)
  • Migration status for pcsc-cyberjack/riscv64 (3.99.5final.sp14-2 to 3.99.5final.sp14-2): Will attempt migration (Any information below is purely informational)
• pcscada/riscv64 (0.7.7-6 to 0.7.7-6)
  • Migration status for pcscada/riscv64 (0.7.7-6 to 0.7.7-6): Will attempt migration (Any information below is purely informational)
• pcsxr/riscv64 (1.9.94-6 to 1.9.94-6)
  • Migration status for pcsxr/riscv64 (1.9.94-6 to 1.9.94-6): Will attempt migration (Any information below is purely informational)
• pd-ableton-link/riscv64 (0.6~ds0-7 to 0.6~ds0-7)
  • Migration status for pd-ableton-link/riscv64 (0.6~ds0-7 to 0.6~ds0-7): Will attempt migration (Any information below is purely informational)
• pd-bsaylor/riscv64 (0.1.5-3 to 0.1.5-3)
  • Migration status for pd-bsaylor/riscv64 (0.1.5-3 to 0.1.5-3): Will attempt migration (Any information below is purely informational)
• pd-creb/riscv64 (0.10.0-2 to 0.10.0-2)
  • Migration status for pd-creb/riscv64 (0.10.0-2 to 0.10.0-2): Will attempt migration (Any information below is purely informational)
• pd-csound/riscv64 (2:1.01.0-6 to 2:1.01.0-6)
  • Migration status for pd-csound/riscv64 (2:1.01.0-6 to 2:1.01.0-6): Will attempt migration (Any information below is purely informational)
• pd-lua/riscv64 (0.11.6+ds1-1 to 0.11.6+ds1-1)
  • Migration status for pd-lua/riscv64 (0.11.6+ds1-1 to 0.11.6+ds1-1): Will attempt migration (Any information below is purely informational)
• pd-pool/riscv64 (0.2.2+git20210923.1.40cb82e-3 to 0.2.2+git20210923.1.40cb82e-3)
  • Migration status for pd-pool/riscv64 (0.2.2+git20210923.1.40cb82e-3 to 0.2.2+git20210923.1.40cb82e-3): 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)
• pd-wiimote/riscv64 (0.3.2-9 to 0.3.2-9)
  • Migration status for pd-wiimote/riscv64 (0.3.2-9 to 0.3.2-9): Will attempt migration (Any information below is purely informational)
• pd-xsample/riscv64 (0.3.2+git20170905.1.4441ae5-7 to 0.3.2+git20170905.1.4441ae5-7)
  • Migration status for pd-xsample/riscv64 (0.3.2+git20170905.1.4441ae5-7 to 0.3.2+git20170905.1.4441ae5-7): 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/riscv64 (0.9.18.2-2 to 0.9.18.2-2)
  • Migration status for pdf2djvu/riscv64 (0.9.18.2-2 to 0.9.18.2-2): Will attempt migration (Any information below is purely informational)
• pdf2svg/riscv64 (0.2.3-5 to 0.2.3-5)
  • Migration status for pdf2svg/riscv64 (0.2.3-5 to 0.2.3-5): Will attempt migration (Any information below is purely informational)
• 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)
• pdfgrep/riscv64 (2.2.0-0.1 to 2.2.0-0.1)
  • Migration status for pdfgrep/riscv64 (2.2.0-0.1 to 2.2.0-0.1): 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)
• pekka-kana-2/riscv64 (1.2.7-1 to 1.2.7-1)
  • Migration status for pekka-kana-2/riscv64 (1.2.7-1 to 1.2.7-1): 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)
• perceptualdiff/riscv64 (2.1-7 to 2.1-7)
  • Migration status for perceptualdiff/riscv64 (2.1-7 to 2.1-7): Will attempt migration (Any information below is purely informational)
• performous/riscv64 (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for performous/riscv64 (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• perl4caml/riscv64 (0.9.5-7 to 0.9.5-7)
  • Migration status for perl4caml/riscv64 (0.9.5-7 to 0.9.5-7): Will attempt migration (Any information below is purely informational)
• perm/riscv64 (0.4.0-8 to 0.4.0-8)
  • Migration status for perm/riscv64 (0.4.0-8 to 0.4.0-8): Will attempt migration (Any information below is purely informational)
• persistent-cache-cpp/riscv64 (1.0.7-1 to 1.0.7-1)
  • Migration status for persistent-cache-cpp/riscv64 (1.0.7-1 to 1.0.7-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)
• pfstools/riscv64 (2.2.0-7 to 2.2.0-7)
  • Migration status for pfstools/riscv64 (2.2.0-7 to 2.2.0-7): Will attempt migration (Any information below is purely informational)
• pg-auto-failover/riscv64 (2.1-2 to 2.1-2)
  • Migration status for pg-auto-failover/riscv64 (2.1-2 to 2.1-2): Will attempt migration (Any information below is purely informational)
• pg-catcheck/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for pg-catcheck/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• pg-checksums/riscv64 (1.1-6 to 1.1-6)
  • Migration status for pg-checksums/riscv64 (1.1-6 to 1.1-6): Will attempt migration (Any information below is purely informational)
• pg-cron/riscv64 (1.6.2-1 to 1.6.2-1)
  • Migration status for pg-cron/riscv64 (1.6.2-1 to 1.6.2-1): 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-failover-slots/riscv64 (1.0.1-2 to 1.0.1-2)
  • Migration status for pg-failover-slots/riscv64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• pg-hint-plan-16/riscv64 (1.6.0-1 to 1.6.0-1)
  • Migration status for pg-hint-plan-16/riscv64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
• pg-partman/riscv64 (5.1.0-1 to 5.1.0-1)
  • Migration status for pg-partman/riscv64 (5.1.0-1 to 5.1.0-1): 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-squeeze/riscv64 (1.6.2-1 to 1.6.2-1)
  • Migration status for pg-squeeze/riscv64 (1.6.2-1 to 1.6.2-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)
• pg-wait-sampling/riscv64 (1.1.5-1 to 1.1.5-1)
  • Migration status for pg-wait-sampling/riscv64 (1.1.5-1 to 1.1.5-1): Will attempt migration (Any information below is purely informational)
• pgagent/riscv64 (4.2.2-3 to 4.2.2-3)
  • Migration status for pgagent/riscv64 (4.2.2-3 to 4.2.2-3): 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)
• pgauditlogtofile/riscv64 (1.5.12-2 to 1.5.12-2)
  • Migration status for pgauditlogtofile/riscv64 (1.5.12-2 to 1.5.12-2): 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/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)
• 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)
• pgplot5/riscv64 (5.2.2-19.5 to 5.2.2-19.5)
  • Migration status for pgplot5/riscv64 (5.2.2-19.5 to 5.2.2-19.5): 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)
• pgq/riscv64 (3.5-3 to 3.5-3)
  • Migration status for pgq/riscv64 (3.5-3 to 3.5-3): Will attempt migration (Any information below is purely informational)
• pgrouting/riscv64 (3.6.2-1 to 3.6.2-1)
  • Migration status for pgrouting/riscv64 (3.6.2-1 to 3.6.2-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)
• phasex/riscv64 (0.14.97-3 to 0.14.97-3)
  • Migration status for phasex/riscv64 (0.14.97-3 to 0.14.97-3): Will attempt migration (Any information below is purely informational)
• phast/riscv64 (1.6+dfsg-5 to 1.6+dfsg-5)
  • Migration status for phast/riscv64 (1.6+dfsg-5 to 1.6+dfsg-5): Will attempt migration (Any information below is purely informational)
• phcpack/riscv64 (2.4.90+dfsg-1 to 2.4.90+dfsg-1)
  • Migration status for phcpack/riscv64 (2.4.90+dfsg-1 to 2.4.90+dfsg-1): Will attempt migration (Any information below is purely informational)
• phipack/riscv64 (0.0.20160614-5 to 0.0.20160614-5)
  • Migration status for phipack/riscv64 (0.0.20160614-5 to 0.0.20160614-5): 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)
• phosh-osk-stub/riscv64 (0.38.0-1 to 0.38.0-1)
  • Migration status for phosh-osk-stub/riscv64 (0.38.0-1 to 0.38.0-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)
• php-excimer/riscv64 (1.2.1-1 to 1.2.1-1)
  • Migration status for php-excimer/riscv64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• 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-pinba/riscv64 (1.1.2-16 to 1.1.2-16)
  • Migration status for php-pinba/riscv64 (1.1.2-16 to 1.1.2-16): 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)
• phylonium/riscv64 (1.7-3 to 1.7-3)
  • Migration status for phylonium/riscv64 (1.7-3 to 1.7-3): 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)
• physamp/riscv64 (1.1.0-5 to 1.1.0-5)
  • Migration status for physamp/riscv64 (1.1.0-5 to 1.1.0-5): Will attempt migration (Any information below is purely informational)
• phyx/riscv64 (1.3.1+ds-2 to 1.3.1+ds-2)
  • Migration status for phyx/riscv64 (1.3.1+ds-2 to 1.3.1+ds-2): Will attempt migration (Any information below is purely informational)
• pianobar/riscv64 (2022.04.01-1.1 to 2022.04.01-1.1)
  • Migration status for pianobar/riscv64 (2022.04.01-1.1 to 2022.04.01-1.1): 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-blinklight/riscv64 (0.11.1-5 to 0.11.1-5)
  • Migration status for pidgin-blinklight/riscv64 (0.11.1-5 to 0.11.1-5): 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-nateon/riscv64 (0.0.0.svn147-2 to 0.0.0.svn147-2)
  • Migration status for pidgin-nateon/riscv64 (0.0.0.svn147-2 to 0.0.0.svn147-2): 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-skype/riscv64 (20240122+gitab786a3+dfsg-2 to 20240122+gitab786a3+dfsg-2)
  • Migration status for pidgin-skype/riscv64 (20240122+gitab786a3+dfsg-2 to 20240122+gitab786a3+dfsg-2): 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)
• piglit/riscv64 (0~git20231002-24207f5be-1 to 0~git20231002-24207f5be-1)
  • Migration status for piglit/riscv64 (0~git20231002-24207f5be-1 to 0~git20231002-24207f5be-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)
• pikepdf/riscv64 (8.15.1+dfsg-1 to 8.15.1+dfsg-1)
  • Migration status for pikepdf/riscv64 (8.15.1+dfsg-1 to 8.15.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• pikopixel.app/riscv64 (1.0-b10b-1 to 1.0-b10b-1)
  • Migration status for pikopixel.app/riscv64 (1.0-b10b-1 to 1.0-b10b-1): Will attempt migration (Any information below is purely informational)
• piler/riscv64 (0~20140707-4 to 0~20140707-4)
  • Migration status for piler/riscv64 (0~20140707-4 to 0~20140707-4): Will attempt migration (Any information below is purely informational)
• pilercr/riscv64 (1.06+dfsg-5 to 1.06+dfsg-5)
  • Migration status for pilercr/riscv64 (1.06+dfsg-5 to 1.06+dfsg-5): 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)
• 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)
• pinentry/riscv64 (1.2.1-3 to 1.2.1-3)
  • Migration status for pinentry/riscv64 (1.2.1-3 to 1.2.1-3): Will attempt migration (Any information below is purely informational)
• pinfish/riscv64 (0.1.0+ds-4 to 0.1.0+ds-4)
  • Migration status for pinfish/riscv64 (0.1.0+ds-4 to 0.1.0+ds-4): 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/riscv64 (1.21-1 to 1.21-1)
  • Migration status for pinot/riscv64 (1.21-1 to 1.21-1): Will attempt migration (Any information below is purely informational)
• 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)
• pipenightdreams/riscv64 (0.10.0-15 to 0.10.0-15)
  • Migration status for pipenightdreams/riscv64 (0.10.0-15 to 0.10.0-15): Will attempt migration (Any information below is purely informational)
• pipewire-module-xrdp/riscv64 (0.2-2 to 0.2-2)
  • Migration status for pipewire-module-xrdp/riscv64 (0.2-2 to 0.2-2): Will attempt migration (Any information below is purely informational)
• pirs/riscv64 (2.0.2+dfsg-12 to 2.0.2+dfsg-12)
  • Migration status for pirs/riscv64 (2.0.2+dfsg-12 to 2.0.2+dfsg-12): Will attempt migration (Any information below is purely informational)
• pistache/riscv64 (0.0.5+ds-5.1 to 0.0.5+ds-5.1)
  • Migration status for pistache/riscv64 (0.0.5+ds-5.1 to 0.0.5+ds-5.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)
• pizzly/riscv64 (0.37.3+ds-9 to 0.37.3+ds-9)
  • Migration status for pizzly/riscv64 (0.37.3+ds-9 to 0.37.3+ds-9): Will attempt migration (Any information below is purely informational)
• pkcs11-dump/riscv64 (0.3.4-1.1 to 0.3.4-1.1)
  • Migration status for pkcs11-dump/riscv64 (0.3.4-1.1 to 0.3.4-1.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)
• pktanon/riscv64 (2~git20160407.0.2bde4f2+dfsg-12 to 2~git20160407.0.2bde4f2+dfsg-12)
  • Migration status for pktanon/riscv64 (2~git20160407.0.2bde4f2+dfsg-12 to 2~git20160407.0.2bde4f2+dfsg-12): 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)
• planner/riscv64 (0.14.92-1 to 0.14.92-1)
  • Migration status for planner/riscv64 (0.14.92-1 to 0.14.92-1): 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-framework/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for plasma-framework/riscv64 (5.115.0-2 to 5.115.0-2): 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-pass/riscv64 (1.2.2-1 to 1.2.2-1)
  • Migration status for plasma-pass/riscv64 (1.2.2-1 to 1.2.2-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)
• plasma-workspace_pu (4:5.27.11.1-1 to 4:5.27.5-2+deb12u2)
  • Migration status for plasma-workspace_pu (4:5.27.11.1-1 to 4:5.27.5-2+deb12u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: plasma-workspace is newer in the target suite (4:5.27.11.1-1 4:5.27.5-2+deb12u2)
• plast/riscv64 (2.3.2+dfsg-10 to 2.3.2+dfsg-10)
  • Migration status for plast/riscv64 (2.3.2+dfsg-10 to 2.3.2+dfsg-10): Will attempt migration (Any information below is purely informational)
• pldebugger/riscv64 (1:1.5-2 to 1:1.5-2)
  • Migration status for pldebugger/riscv64 (1:1.5-2 to 1:1.5-2): 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)
• plink/riscv64 (1.07+dfsg-4 to 1.07+dfsg-4)
  • Migration status for plink/riscv64 (1.07+dfsg-4 to 1.07+dfsg-4): Will attempt migration (Any information below is purely informational)
• plink2/riscv64 (2.00~a5.8-231123+dfsg-1 to 2.00~a5.8-231123+dfsg-1)
  • Migration status for plink2/riscv64 (2.00~a5.8-231123+dfsg-1 to 2.00~a5.8-231123+dfsg-1): Will attempt migration (Any information below is purely informational)
• plocate/riscv64 (1.1.22-3 to 1.1.22-3)
  • Migration status for plocate/riscv64 (1.1.22-3 to 1.1.22-3): 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)
• plotutils/riscv64 (2.6-14 to 2.6-14)
  • Migration status for plotutils/riscv64 (2.6-14 to 2.6-14): 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)
• plprofiler/riscv64 (4.2.4-1 to 4.2.4-1)
  • Migration status for plprofiler/riscv64 (4.2.4-1 to 4.2.4-1): Will attempt migration (Any information below is purely informational)
• plptools/riscv64 (1.0.13-3 to 1.0.13-3)
  • Migration status for plptools/riscv64 (1.0.13-3 to 1.0.13-3): Will attempt migration (Any information below is purely informational)
• plr/riscv64 (1:8.4.6-2 to 1:8.4.6-2)
  • Migration status for plr/riscv64 (1:8.4.6-2 to 1:8.4.6-2): Will attempt migration (Any information below is purely informational)
• pluma-plugins/riscv64 (1.27.0-3 to 1.27.0-3)
  • Migration status for pluma-plugins/riscv64 (1.27.0-3 to 1.27.0-3): Will attempt migration (Any information below is purely informational)
• pluma/riscv64 (1.26.1-2 to 1.26.1-2)
  • Migration status for pluma/riscv64 (1.26.1-2 to 1.26.1-2): 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)
• plymouth/riscv64 (24.004.60-1 to 24.004.60-1)
  • Migration status for plymouth/riscv64 (24.004.60-1 to 24.004.60-1): Will attempt migration (Any information below is purely informational)
• plyvel/riscv64 (1.5.1-1 to 1.5.1-1)
  • Migration status for plyvel/riscv64 (1.5.1-1 to 1.5.1-1): Will attempt migration (Any information below is purely informational)
• plzip/riscv64 (1.11-1 to 1.11-1)
  • Migration status for plzip/riscv64 (1.11-1 to 1.11-1): Will attempt migration (Any information below is purely informational)
• pmacct/riscv64 (1.7.8-2 to 1.7.8-2)
  • Migration status for pmacct/riscv64 (1.7.8-2 to 1.7.8-2): Will attempt migration (Any information below is purely informational)
• pms/riscv64 (0.42-1.1 to 0.42-1.1)
  • Migration status for pms/riscv64 (0.42-1.1 to 0.42-1.1): Will attempt migration (Any information below is purely informational)
• pnc/riscv64 (0.9.4-3 to 0.9.4-3)
  • Migration status for pnc/riscv64 (0.9.4-3 to 0.9.4-3): Will attempt migration (Any information below is purely informational)
• png2html/riscv64 (1.1-9 to 1.1-9)
  • Migration status for png2html/riscv64 (1.1-9 to 1.1-9): Will attempt migration (Any information below is purely informational)
• pngquant/riscv64 (2.18.0-1 to 2.18.0-1)
  • Migration status for pngquant/riscv64 (2.18.0-1 to 2.18.0-1): Will attempt migration (Any information below is purely informational)
• pnm2ppa/riscv64 (1.13-13 to 1.13-13)
  • Migration status for pnm2ppa/riscv64 (1.13-13 to 1.13-13): 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)
• pocketsphinx-python/riscv64 (1:0.1.15-3 to 1:0.1.15-3)
  • Migration status for pocketsphinx-python/riscv64 (1:0.1.15-3 to 1:0.1.15-3): Will attempt migration (Any information below is purely informational)
• pocketsphinx/riscv64 (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15)
  • Migration status for pocketsphinx/riscv64 (0.8+5prealpha+1-15 to 0.8+5prealpha+1-15): Will attempt migration (Any information below is purely informational)
• poco/riscv64 (1.13.0-6 to 1.13.0-6)
  • Migration status for poco/riscv64 (1.13.0-6 to 1.13.0-6): Will attempt migration (Any information below is purely informational)
• poe.app/riscv64 (0.5.1-6.1 to 0.5.1-6.1)
  • Migration status for poe.app/riscv64 (0.5.1-6.1 to 0.5.1-6.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)
• polybar/riscv64 (3.7.1-1 to 3.7.1-1)
  • Migration status for polybar/riscv64 (3.7.1-1 to 3.7.1-1): 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)
• pong2/riscv64 (0.1.3-3 to 0.1.3-3)
  • Migration status for pong2/riscv64 (0.1.3-3 to 0.1.3-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)
• portsmf/riscv64 (0.1~svn20101010-7 to 0.1~svn20101010-7)
  • Migration status for portsmf/riscv64 (0.1~svn20101010-7 to 0.1~svn20101010-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)
• posterazor/riscv64 (1.5.1-10 to 1.5.1-10)
  • Migration status for posterazor/riscv64 (1.5.1-10 to 1.5.1-10): Will attempt migration (Any information below is purely informational)
• postfix/riscv64 (3.9.0-2 to 3.9.0-2)
  • Migration status for postfix/riscv64 (3.9.0-2 to 3.9.0-2): Will attempt migration (Any information below is purely informational)
• postgres-decoderbufs/riscv64 (2.6.1-1 to 2.6.1-1)
  • Migration status for postgres-decoderbufs/riscv64 (2.6.1-1 to 2.6.1-1): 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-debversion/riscv64 (1.1.2-3 to 1.1.2-3)
  • Migration status for postgresql-debversion/riscv64 (1.1.2-3 to 1.1.2-3): 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-mysql-fdw/riscv64 (2.9.1-2 to 2.9.1-2)
  • Migration status for postgresql-mysql-fdw/riscv64 (2.9.1-2 to 2.9.1-2): 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-q3c/riscv64 (2.0.1-1 to 2.0.1-1)
  • Migration status for postgresql-q3c/riscv64 (2.0.1-1 to 2.0.1-1): 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-semver/riscv64 (0.32.1-2 to 0.32.1-2)
  • Migration status for postgresql-semver/riscv64 (0.32.1-2 to 0.32.1-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)
• povray/riscv64 (1:3.7.0.10-3 to 1:3.7.0.10-3)
  • Migration status for povray/riscv64 (1:3.7.0.10-3 to 1:3.7.0.10-3): 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)
• powermanga/riscv64 (0.93.1-6 to 0.93.1-6)
  • Migration status for powermanga/riscv64 (0.93.1-6 to 0.93.1-6): Will attempt migration (Any information below is purely informational)
• powertop/riscv64 (2.15-3 to 2.15-3)
  • Migration status for powertop/riscv64 (2.15-3 to 2.15-3): 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)
• ppl/riscv64 (1:1.2-8.1 to 1:1.2-8.1)
  • Migration status for ppl/riscv64 (1:1.2-8.1 to 1:1.2-8.1): Will attempt migration (Any information below is purely informational)
• ppx-derivers/riscv64 (1.2.1-4 to 1.2.1-4)
  • Migration status for ppx-derivers/riscv64 (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
• ppx-stable-witness/riscv64 (0.16.0-1 to 0.16.0-1)
  • Migration status for ppx-stable-witness/riscv64 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
• ppx-tools/riscv64 (6.6-4 to 6.6-4)
  • Migration status for ppx-tools/riscv64 (6.6-4 to 6.6-4): 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)
• prank/riscv64 (0.0.170427+dfsg-3 to 0.0.170427+dfsg-3)
  • Migration status for prank/riscv64 (0.0.170427+dfsg-3 to 0.0.170427+dfsg-3): 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)
• premake4/riscv64 (4.3+repack1-2 to 4.3+repack1-2)
  • Migration status for premake4/riscv64 (4.3+repack1-2 to 4.3+repack1-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)
• prerex/riscv64 (6.8.0-1 to 6.8.0-1)
  • Migration status for prerex/riscv64 (6.8.0-1 to 6.8.0-1): Will attempt migration (Any information below is purely informational)
• presage/riscv64 (0.9.1-2.6 to 0.9.1-2.6)
  • Migration status for presage/riscv64 (0.9.1-2.6 to 0.9.1-2.6): Will attempt migration (Any information below is purely informational)
• presto/riscv64 (0.7.2-1 to 0.7.2-1)
  • Migration status for presto/riscv64 (0.7.2-1 to 0.7.2-1): 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)
• prime-phylo/riscv64 (1.0.11-11 to 1.0.11-11)
  • Migration status for prime-phylo/riscv64 (1.0.11-11 to 1.0.11-11): Will attempt migration (Any information below is purely informational)
• primecount/riscv64 (7.13+ds-1 to 7.13+ds-1)
  • Migration status for primecount/riscv64 (7.13+ds-1 to 7.13+ds-1): Will attempt migration (Any information below is purely informational)
• primecountpy/riscv64 (0.1.0-3 to 0.1.0-3)
  • Migration status for primecountpy/riscv64 (0.1.0-3 to 0.1.0-3): Will attempt migration (Any information below is purely informational)
• primer3/riscv64 (2.6.1-4 to 2.6.1-4)
  • Migration status for primer3/riscv64 (2.6.1-4 to 2.6.1-4): Will attempt migration (Any information below is purely informational)
• primesieve/riscv64 (12.3+ds-1 to 12.3+ds-1)
  • Migration status for primesieve/riscv64 (12.3+ds-1 to 12.3+ds-1): Will attempt migration (Any information below is purely informational)
• primrose/riscv64 (6+dfsg1-4 to 6+dfsg1-4)
  • Migration status for primrose/riscv64 (6+dfsg1-4 to 6+dfsg1-4): Will attempt migration (Any information below is purely informational)
• primus-vk/riscv64 (1.6.4-2 to 1.6.4-2)
  • Migration status for primus-vk/riscv64 (1.6.4-2 to 1.6.4-2): 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-lfs/riscv64 (20210404.1-2 to 20210404.1-2)
  • Migration status for pristine-lfs/riscv64 (20210404.1-2 to 20210404.1-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)
• prjtrellis/riscv64 (1.4-2 to 1.4-2)
  • Migration status for prjtrellis/riscv64 (1.4-2 to 1.4-2): 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)
• probalign/riscv64 (1.4-10 to 1.4-10)
  • Migration status for probalign/riscv64 (1.4-10 to 1.4-10): Will attempt migration (Any information below is purely informational)
• probcons/riscv64 (1.12-14 to 1.12-14)
  • Migration status for probcons/riscv64 (1.12-14 to 1.12-14): Will attempt migration (Any information below is purely informational)
• process-cpp/riscv64 (3.0.1-9 to 3.0.1-9)
  • Migration status for process-cpp/riscv64 (3.0.1-9 to 3.0.1-9): Will attempt migration (Any information below is purely informational)
• procinfo/riscv64 (1:2.0.304-7 to 1:2.0.304-7)
  • Migration status for procinfo/riscv64 (1:2.0.304-7 to 1:2.0.304-7): 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)
• procserv/riscv64 (2.7.0-1 to 2.7.0-1)
  • Migration status for procserv/riscv64 (2.7.0-1 to 2.7.0-1): Will attempt migration (Any information below is purely informational)
• proda/riscv64 (1.0-14 to 1.0-14)
  • Migration status for proda/riscv64 (1.0-14 to 1.0-14): Will attempt migration (Any information below is purely informational)
• profanity/riscv64 (0.14.0-1 to 0.14.0-1)
  • Migration status for profanity/riscv64 (0.14.0-1 to 0.14.0-1): Will attempt migration (Any information below is purely informational)
• profnet/riscv64 (1.0.22-8 to 1.0.22-8)
  • Migration status for profnet/riscv64 (1.0.22-8 to 1.0.22-8): Will attempt migration (Any information below is purely informational)
• profphd-utils/riscv64 (1.0.10-7 to 1.0.10-7)
  • Migration status for profphd-utils/riscv64 (1.0.10-7 to 1.0.10-7): Will attempt migration (Any information below is purely informational)
• proftmb/riscv64 (1.1.12-11 to 1.1.12-11)
  • Migration status for proftmb/riscv64 (1.1.12-11 to 1.1.12-11): Will attempt migration (Any information below is purely informational)
• proftpd-dfsg/riscv64 (1.3.8.b+dfsg-2 to 1.3.8.b+dfsg-2)
  • Migration status for proftpd-dfsg/riscv64 (1.3.8.b+dfsg-2 to 1.3.8.b+dfsg-2): Will attempt migration (Any information below is purely informational)
• proftpd-mod-autohost/riscv64 (0.6-2 to 0.6-2)
  • Migration status for proftpd-mod-autohost/riscv64 (0.6-2 to 0.6-2): Will attempt migration (Any information below is purely informational)
• proftpd-mod-case/riscv64 (0.9-1 to 0.9-1)
  • Migration status for proftpd-mod-case/riscv64 (0.9-1 to 0.9-1): Will attempt migration (Any information below is purely informational)
• proftpd-mod-clamav/riscv64 (0.14~rc2-4 to 0.14~rc2-4)
  • Migration status for proftpd-mod-clamav/riscv64 (0.14~rc2-4 to 0.14~rc2-4): Will attempt migration (Any information below is purely informational)
• proftpd-mod-counter/riscv64 (0.6.2-2 to 0.6.2-2)
  • Migration status for proftpd-mod-counter/riscv64 (0.6.2-2 to 0.6.2-2): Will attempt migration (Any information below is purely informational)
• proftpd-mod-fsync/riscv64 (0.3-4 to 0.3-4)
  • Migration status for proftpd-mod-fsync/riscv64 (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
• proftpd-mod-geoip2/riscv64 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-geoip2/riscv64 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
• proftpd-mod-kafka/riscv64 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-kafka/riscv64 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
• proftpd-mod-msg/riscv64 (0.5-3 to 0.5-3)
  • Migration status for proftpd-mod-msg/riscv64 (0.5-3 to 0.5-3): Will attempt migration (Any information below is purely informational)
• proftpd-mod-proxy/riscv64 (0.9.4-1 to 0.9.4-1)
  • Migration status for proftpd-mod-proxy/riscv64 (0.9.4-1 to 0.9.4-1): Will attempt migration (Any information below is purely informational)
• proftpd-mod-sftp-ldap/riscv64 (0.2-1 to 0.2-1)
  • Migration status for proftpd-mod-sftp-ldap/riscv64 (0.2-1 to 0.2-1): Will attempt migration (Any information below is purely informational)
• proftpd-mod-statsd/riscv64 (0.1-1 to 0.1-1)
  • Migration status for proftpd-mod-statsd/riscv64 (0.1-1 to 0.1-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)
• progressivemauve/riscv64 (1.2.0+4713+dfsg-5 to 1.2.0+4713+dfsg-5)
  • Migration status for progressivemauve/riscv64 (1.2.0+4713+dfsg-5 to 1.2.0+4713+dfsg-5): Will attempt migration (Any information below is purely informational)
• projectcenter.app/riscv64 (0.7.0-1 to 0.7.0-1)
  • Migration status for projectcenter.app/riscv64 (0.7.0-1 to 0.7.0-1): 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-cpp/riscv64 (1.0.2-2 to 1.0.2-2)
  • Migration status for prometheus-cpp/riscv64 (1.0.2-2 to 1.0.2-2): 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)
• prometheus-postfix-exporter/riscv64 (0.3.0-4 to 0.3.0-4)
  • Migration status for prometheus-postfix-exporter/riscv64 (0.3.0-4 to 0.3.0-4): Will attempt migration (Any information below is purely informational)
• prometheus-varnish-exporter/riscv64 (1.6.1-2 to 1.6.1-2)
  • Migration status for prometheus-varnish-exporter/riscv64 (1.6.1-2 to 1.6.1-2): 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)
• prosody/riscv64 (0.12.4-1 to 0.12.4-1)
  • Migration status for prosody/riscv64 (0.12.4-1 to 0.12.4-1): Will attempt migration (Any information below is purely informational)
• proteinortho/riscv64 (6.3.1+dfsg-1 to 6.3.1+dfsg-1)
  • Migration status for proteinortho/riscv64 (6.3.1+dfsg-1 to 6.3.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• protobuf/riscv64 (3.21.12-8.2 to 3.21.12-8.2)
  • Migration status for protobuf/riscv64 (3.21.12-8.2 to 3.21.12-8.2): Will attempt migration (Any information below is purely informational)
• ps2eps/riscv64 (1.70-1 to 1.70-1)
  • Migration status for ps2eps/riscv64 (1.70-1 to 1.70-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)
• pscan-chip/riscv64 (1.1-3 to 1.1-3)
  • Migration status for pscan-chip/riscv64 (1.1-3 to 1.1-3): Will attempt migration (Any information below is purely informational)
• pscan-tfbs/riscv64 (1.2.2-4 to 1.2.2-4)
  • Migration status for pscan-tfbs/riscv64 (1.2.2-4 to 1.2.2-4): 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)
• psk31lx/riscv64 (2.2-1 to 2.2-1)
  • Migration status for psk31lx/riscv64 (2.2-1 to 2.2-1): Will attempt migration (Any information below is purely informational)
• psmt2-frontend/riscv64 (0.4.0-3 to 0.4.0-3)
  • Migration status for psmt2-frontend/riscv64 (0.4.0-3 to 0.4.0-3): 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)
• pspresent/riscv64 (1.3-6 to 1.3-6)
  • Migration status for pspresent/riscv64 (1.3-6 to 1.3-6): 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)
• psurface/riscv64 (2.0.0-2.1 to 2.0.0-2.1)
  • Migration status for psurface/riscv64 (2.0.0-2.1 to 2.0.0-2.1): Will attempt migration (Any information below is purely informational)
• psychtoolbox-3/riscv64 (3.0.19.9.dfsg1-1 to 3.0.19.9.dfsg1-1)
  • Migration status for psychtoolbox-3/riscv64 (3.0.19.9.dfsg1-1 to 3.0.19.9.dfsg1-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)
• ptl/riscv64 (2.3.3-2.1 to 2.3.3-2.1)
  • Migration status for ptl/riscv64 (2.3.3-2.1 to 2.3.3-2.1): Will attempt migration (Any information below is purely informational)
• ptouch-driver/riscv64 (1.7-1 to 1.7-1)
  • Migration status for ptouch-driver/riscv64 (1.7-1 to 1.7-1): Will attempt migration (Any information below is purely informational)
• pugixml/riscv64 (1.14-0.1 to 1.14-0.1)
  • Migration status for pugixml/riscv64 (1.14-0.1 to 1.14-0.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)
• puma/riscv64 (6.4.2-4 to 6.4.2-4)
  • Migration status for puma/riscv64 (6.4.2-4 to 6.4.2-4): 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)
• 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)
• purpose/riscv64 (5.115.0-2 to 5.115.0-2)
  • Migration status for purpose/riscv64 (5.115.0-2 to 5.115.0-2): Will attempt migration (Any information below is purely informational)
• pushover/riscv64 (1.1-3 to 1.1-3)
  • Migration status for pushover/riscv64 (1.1-3 to 1.1-3): Will attempt migration (Any information below is purely informational)
• pushpin/riscv64 (1.39.1-1 to 1.39.1-1)
  • Migration status for pushpin/riscv64 (1.39.1-1 to 1.39.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)
• pxlib/riscv64 (0.6.8-1 to 0.6.8-1)
  • Migration status for pxlib/riscv64 (0.6.8-1 to 0.6.8-1): Will attempt migration (Any information below is purely informational)
• pxp/riscv64 (1.2.9-3 to 1.2.9-3)
  • Migration status for pxp/riscv64 (1.2.9-3 to 1.2.9-3): Will attempt migration (Any information below is purely informational)
• py-stringmatching/riscv64 (0.4.5-1 to 0.4.5-1)
  • Migration status for py-stringmatching/riscv64 (0.4.5-1 to 0.4.5-1): Will attempt migration (Any information below is purely informational)
• py3exiv2/riscv64 (0.7.2-1.1 to 0.7.2-1.1)
  • Migration status for py3exiv2/riscv64 (0.7.2-1.1 to 0.7.2-1.1): Will attempt migration (Any information below is purely informational)
• pybigwig/riscv64 (0.3.22+dfsg-1 to 0.3.22+dfsg-1)
  • Migration status for pybigwig/riscv64 (0.3.22+dfsg-1 to 0.3.22+dfsg-1): Will attempt migration (Any information below is purely informational)
• 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)
• pybj/riscv64 (0.2.6-2 to 0.2.6-2)
  • Migration status for pybj/riscv64 (0.2.6-2 to 0.2.6-2): Will attempt migration (Any information below is purely informational)
• pybluez/riscv64 (0.23-5.1 to 0.23-5.1)
  • Migration status for pybluez/riscv64 (0.23-5.1 to 0.23-5.1): Will attempt migration (Any information below is purely informational)
• pyclipper/riscv64 (1.3.0.post5-3 to 1.3.0.post5-3)
  • Migration status for pyclipper/riscv64 (1.3.0.post5-3 to 1.3.0.post5-3): Will attempt migration (Any information below is purely informational)
• pydantic-core/riscv64 (2.11.0-1 to 2.11.0-1)
  • Migration status for pydantic-core/riscv64 (2.11.0-1 to 2.11.0-1): Will attempt migration (Any information below is purely informational)
• pyemd/riscv64 (0.5.1.54.g802fa86-2 to 0.5.1.54.g802fa86-2)
  • Migration status for pyemd/riscv64 (0.5.1.54.g802fa86-2 to 0.5.1.54.g802fa86-2): Will attempt migration (Any information below is purely informational)
• pyepr/riscv64 (1.1.5-2 to 1.1.5-2)
  • Migration status for pyepr/riscv64 (1.1.5-2 to 1.1.5-2): Will attempt migration (Any information below is purely informational)
• pyerfa/riscv64 (2.0.1.4+ds-1 to 2.0.1.4+ds-1)
  • Migration status for pyerfa/riscv64 (2.0.1.4+ds-1 to 2.0.1.4+ds-1): 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)
• pygac/riscv64 (1.7.3-1 to 1.7.3-1)
  • Migration status for pygac/riscv64 (1.7.3-1 to 1.7.3-1): 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)
• pygame/riscv64 (2.5.2-2 to 2.5.2-2)
  • Migration status for pygame/riscv64 (2.5.2-2 to 2.5.2-2): Will attempt migration (Any information below is purely informational)
• pygattlib/riscv64 (0~20210616-1 to 0~20210616-1)
  • Migration status for pygattlib/riscv64 (0~20210616-1 to 0~20210616-1): Will attempt migration (Any information below is purely informational)
• pygccjit/riscv64 (0.4-13 to 0.4-13)
  • Migration status for pygccjit/riscv64 (0.4-13 to 0.4-13): Will attempt migration (Any information below is purely informational)
• pygrib/riscv64 (2.1.5-4 to 2.1.5-4)
  • Migration status for pygrib/riscv64 (2.1.5-4 to 2.1.5-4): Will attempt migration (Any information below is purely informational)
• pyhunspell/riscv64 (0.5.5-2 to 0.5.5-2)
  • Migration status for pyhunspell/riscv64 (0.5.5-2 to 0.5.5-2): Will attempt migration (Any information below is purely informational)
• pyicu/riscv64 (2.13.1-1 to 2.13.1-1)
  • Migration status for pyicu/riscv64 (2.13.1-1 to 2.13.1-1): Will attempt migration (Any information below is purely informational)
• pyjdata/riscv64 (0.3.6-1 to 0.3.6-1)
  • Migration status for pyjdata/riscv64 (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
• pykdtree/riscv64 (1.3.12+ds-1 to 1.3.12+ds-1)
  • Migration status for pykdtree/riscv64 (1.3.12+ds-1 to 1.3.12+ds-1): Will attempt migration (Any information below is purely informational)
• pylibmc/riscv64 (1.6.3-1 to 1.6.3-1)
  • Migration status for pylibmc/riscv64 (1.6.3-1 to 1.6.3-1): Will attempt migration (Any information below is purely informational)
• pylibtiff/riscv64 (0.6.1-1 to 0.6.1-1)
  • Migration status for pylibtiff/riscv64 (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
• pymatgen/riscv64 (2024.1.27+dfsg1-7 to 2024.1.27+dfsg1-7)
  • Migration status for pymatgen/riscv64 (2024.1.27+dfsg1-7 to 2024.1.27+dfsg1-7): Will attempt migration (Any information below is purely informational)
• pymbolic/riscv64 (2022.2-2 to 2022.2-2)
  • Migration status for pymbolic/riscv64 (2022.2-2 to 2022.2-2): Will attempt migration (Any information below is purely informational)
• pymca/riscv64 (5.9.2+dfsg-2 to 5.9.2+dfsg-2)
  • Migration status for pymca/riscv64 (5.9.2+dfsg-2 to 5.9.2+dfsg-2): Will attempt migration (Any information below is purely informational)
• pyml/riscv64 (20231101-1 to 20231101-1)
  • Migration status for pyml/riscv64 (20231101-1 to 20231101-1): Will attempt migration (Any information below is purely informational)
• pymol/riscv64 (2.5.0+dfsg-1 to 2.5.0+dfsg-1)
  • Migration status for pymol/riscv64 (2.5.0+dfsg-1 to 2.5.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• 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)
• pyodbc/riscv64 (5.1.0-1 to 5.1.0-1)
  • Migration status for pyodbc/riscv64 (5.1.0-1 to 5.1.0-1): Will attempt migration (Any information below is purely informational)
• pyode/riscv64 (1.2.0.dev15-5 to 1.2.0.dev15-5)
  • Migration status for pyode/riscv64 (1.2.0.dev15-5 to 1.2.0.dev15-5): Will attempt migration (Any information below is purely informational)
• pyosmium/riscv64 (3.7.0-1 to 3.7.0-1)
  • Migration status for pyosmium/riscv64 (3.7.0-1 to 3.7.0-1): 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)
• pyqt5/riscv64 (5.15.10+dfsg-1 to 5.15.10+dfsg-1)
  • Migration status for pyqt5/riscv64 (5.15.10+dfsg-1 to 5.15.10+dfsg-1): Will attempt migration (Any information below is purely informational)
• pyqt5chart/riscv64 (5.15.6+dfsg-1 to 5.15.6+dfsg-1)
  • Migration status for pyqt5chart/riscv64 (5.15.6+dfsg-1 to 5.15.6+dfsg-1): Will attempt migration (Any information below is purely informational)
• pyqt6/riscv64 (6.7.0-1 to 6.7.0-1)
  • Migration status for pyqt6/riscv64 (6.7.0-1 to 6.7.0-1): Will attempt migration (Any information below is purely informational)
• pyreadstat/riscv64 (1.2.6-1 to 1.2.6-1)
  • Migration status for pyreadstat/riscv64 (1.2.6-1 to 1.2.6-1): Will attempt migration (Any information below is purely informational)
• pyregion/riscv64 (2.2.0-3 to 2.2.0-3)
  • Migration status for pyregion/riscv64 (2.2.0-3 to 2.2.0-3): Will attempt migration (Any information below is purely informational)
• pyrle/riscv64 (0.0.33-4.1 to 0.0.33-4.1)
  • Migration status for pyrle/riscv64 (0.0.33-4.1 to 0.0.33-4.1): 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)
• pysmbc/riscv64 (1.0.25.1-1 to 1.0.25.1-1)
  • Migration status for pysmbc/riscv64 (1.0.25.1-1 to 1.0.25.1-1): 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)
• pystring/riscv64 (1.1.4-1 to 1.1.4-1)
  • Migration status for pystring/riscv64 (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
• pysubnettree/riscv64 (0.36-1 to 0.36-1)
  • Migration status for pysubnettree/riscv64 (0.36-1 to 0.36-1): Will attempt migration (Any information below is purely informational)
• pysvn/riscv64 (1.9.22-1 to 1.9.22-1)
  • Migration status for pysvn/riscv64 (1.9.22-1 to 1.9.22-1): Will attempt migration (Any information below is purely informational)
• pysynphot/riscv64 (2.0.0+dfsg-1 to 2.0.0+dfsg-1)
  • Migration status for pysynphot/riscv64 (2.0.0+dfsg-1 to 2.0.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• pytables/amd64 (3.9.2-2 to 3.9.2-2)
  • Migration status for pytables/amd64 (3.9.2-2 to 3.9.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: pytables/amd64 c-blosc2 (not considered)
    • Invalidated by dependency
• pytables/arm64 (3.9.2-2 to 3.9.2-2)
  • Migration status for pytables/arm64 (3.9.2-2 to 3.9.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: pytables/arm64 c-blosc2 (not considered)
    • Invalidated by dependency
• pytables/armhf (3.9.2-2 to 3.9.2-2)
  • Migration status for pytables/armhf (3.9.2-2 to 3.9.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: pytables/armhf c-blosc2 (not considered)
    • Invalidated by dependency
• pytables/i386 (3.9.2-2 to 3.9.2-2)
  • Migration status for pytables/i386 (3.9.2-2 to 3.9.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: pytables/i386 c-blosc2 (not considered)
    • Invalidated by dependency
• pytables/ppc64el (3.9.2-2 to 3.9.2-2)
  • Migration status for pytables/ppc64el (3.9.2-2 to 3.9.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: pytables/ppc64el c-blosc2 (not considered)
    • Invalidated by dependency
• pytables/riscv64 (3.9.2-2 to 3.9.2-2)
  • Migration status for pytables/riscv64 (3.9.2-2 to 3.9.2-2): Will attempt migration (Any information below is purely informational)
• pytaglib/riscv64 (2.1.0-2 to 2.1.0-2)
  • Migration status for pytaglib/riscv64 (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
• python-apt/riscv64 (2.9.0 to 2.9.0)
  • Migration status for python-apt/riscv64 (2.9.0 to 2.9.0): Will attempt migration (Any information below is purely informational)
• python-blosc/riscv64 (1.11.1+ds1-2 to 1.11.1+ds1-2)
  • Migration status for python-blosc/riscv64 (1.11.1+ds1-2 to 1.11.1+ds1-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-casacore/riscv64 (3.5.2-1 to 3.5.2-1)
  • Migration status for python-casacore/riscv64 (3.5.2-1 to 3.5.2-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-cffi/riscv64 (1.16.0-2 to 1.16.0-2)
  • Migration status for python-cffi/riscv64 (1.16.0-2 to 1.16.0-2): Will attempt migration (Any information below is purely informational)
• python-clevercsv/riscv64 (0.8.2+ds-1 to 0.8.2+ds-1)
  • Migration status for python-clevercsv/riscv64 (0.8.2+ds-1 to 0.8.2+ds-1): Will attempt migration (Any information below is purely informational)
• python-cpl/riscv64 (0.7.4-2 to 0.7.4-2)
  • Migration status for python-cpl/riscv64 (0.7.4-2 to 0.7.4-2): Will attempt migration (Any information below is purely informational)
• python-cryptography/riscv64 (42.0.5-2 to 42.0.5-2)
  • Migration status for python-cryptography/riscv64 (42.0.5-2 to 42.0.5-2): Will attempt migration (Any information below is purely informational)
• python-csa/riscv64 (0.1.12-1.1 to 0.1.12-1.1)
  • Migration status for python-csa/riscv64 (0.1.12-1.1 to 0.1.12-1.1): Will attempt migration (Any information below is purely informational)
• python-demgengeo/riscv64 (1.4-4.1 to 1.4-4.1)
  • Migration status for python-demgengeo/riscv64 (1.4-4.1 to 1.4-4.1): 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-falcon/riscv64 (3.1.1-4 to 3.1.1-4)
  • Migration status for python-falcon/riscv64 (3.1.1-4 to 3.1.1-4): Will attempt migration (Any information below is purely informational)
• python-fann2/riscv64 (1:1.2.0+ds-4 to 1:1.2.0+ds-4)
  • Migration status for python-fann2/riscv64 (1:1.2.0+ds-4 to 1:1.2.0+ds-4): Will attempt migration (Any information below is purely informational)
• python-feather-format/riscv64 (0.3.1+dfsg1-8 to 0.3.1+dfsg1-8)
  • Migration status for python-feather-format/riscv64 (0.3.1+dfsg1-8 to 0.3.1+dfsg1-8): Will attempt migration (Any information below is purely informational)
• python-fisx/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for python-fisx/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• 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-gammu/riscv64 (3.2.4-1 to 3.2.4-1)
  • Migration status for python-gammu/riscv64 (3.2.4-1 to 3.2.4-1): 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-greenlet/riscv64 (3.0.1-3 to 3.0.1-3)
  • Migration status for python-greenlet/riscv64 (3.0.1-3 to 3.0.1-3): Will attempt migration (Any information below is purely informational)
• python-grpc-tools/riscv64 (1.14.1-7 to 1.14.1-7)
  • Migration status for python-grpc-tools/riscv64 (1.14.1-7 to 1.14.1-7): Will attempt migration (Any information below is purely informational)
• python-hdf4/riscv64 (0.11.4-2 to 0.11.4-2)
  • Migration status for python-hdf4/riscv64 (0.11.4-2 to 0.11.4-2): Will attempt migration (Any information below is purely informational)
• python-hdmedians/riscv64 (0.14.2-5.1 to 0.14.2-5.1)
  • Migration status for python-hdmedians/riscv64 (0.14.2-5.1 to 0.14.2-5.1): Will attempt migration (Any information below is purely informational)
• python-hmmlearn/riscv64 (0.3.0-5 to 0.3.0-5)
  • Migration status for python-hmmlearn/riscv64 (0.3.0-5 to 0.3.0-5): Will attempt migration (Any information below is purely informational)
• python-hug/riscv64 (2.6.0-4 to 2.6.0-4)
  • Migration status for python-hug/riscv64 (2.6.0-4 to 2.6.0-4): Will attempt migration (Any information below is purely informational)
• python-iow/riscv64 (1.0.6-5 to 1.0.6-5)
  • Migration status for python-iow/riscv64 (1.0.6-5 to 1.0.6-5): Will attempt migration (Any information below is purely informational)
• python-jpype/riscv64 (1.5.0-1 to 1.5.0-1)
  • Migration status for python-jpype/riscv64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
• python-kyotocabinet/riscv64 (1.23-3 to 1.23-3)
  • Migration status for python-kyotocabinet/riscv64 (1.23-3 to 1.23-3): Will attempt migration (Any information below is purely informational)
• python-laszip/riscv64 (0.2.3-1 to 0.2.3-1)
  • Migration status for python-laszip/riscv64 (0.2.3-1 to 0.2.3-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-levenshtein/riscv64 (0.25.1-3 to 0.25.1-3)
  • Migration status for python-levenshtein/riscv64 (0.25.1-3 to 0.25.1-3): Will attempt migration (Any information below is purely informational)
• python-libais/riscv64 (0.17+git.20190917.master.e464cf8-4 to 0.17+git.20190917.master.e464cf8-4)
  • Migration status for python-libais/riscv64 (0.17+git.20190917.master.e464cf8-4 to 0.17+git.20190917.master.e464cf8-4): Will attempt migration (Any information below is purely informational)
• python-libcst/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for python-libcst/riscv64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• python-libtrace/riscv64 (1.6+git20180219-1.1 to 1.6+git20180219-1.1)
  • Migration status for python-libtrace/riscv64 (1.6+git20180219-1.1 to 1.6+git20180219-1.1): Will attempt migration (Any information below is purely informational)
• python-libzim/riscv64 (3.1.0-2 to 3.1.0-2)
  • Migration status for python-libzim/riscv64 (3.1.0-2 to 3.1.0-2): Will attempt migration (Any information below is purely informational)
• python-line-profiler/riscv64 (4.1.2-1 to 4.1.2-1)
  • Migration status for python-line-profiler/riscv64 (4.1.2-1 to 4.1.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-mapbox-earcut/riscv64 (1.0.1-3 to 1.0.1-3)
  • Migration status for python-mapbox-earcut/riscv64 (1.0.1-3 to 1.0.1-3): 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-moderngl/riscv64 (5.10.0-1 to 5.10.0-1)
  • Migration status for python-moderngl/riscv64 (5.10.0-1 to 5.10.0-1): Will attempt migration (Any information below is purely informational)
• python-msgpack/riscv64 (1.0.3-3 to 1.0.3-3)
  • Migration status for python-msgpack/riscv64 (1.0.3-3 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
• python-ncls/riscv64 (0.0.63-hotfix+ds-1 to 0.0.63-hotfix+ds-1)
  • Migration status for python-ncls/riscv64 (0.0.63-hotfix+ds-1 to 0.0.63-hotfix+ds-1): Will attempt migration (Any information below is purely informational)
• python-openstep-plist/riscv64 (0.3.1-1 to 0.3.1-1)
  • Migration status for python-openstep-plist/riscv64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• python-oracledb/riscv64 (1.2.1-3 to 1.2.1-3)
  • Migration status for python-oracledb/riscv64 (1.2.1-3 to 1.2.1-3): 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-pomegranate/riscv64 (0.14.8-6 to 0.14.8-6)
  • Migration status for python-pomegranate/riscv64 (0.14.8-6 to 0.14.8-6): 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-pot/riscv64 (0.9.3+dfsg-2 to 0.9.3+dfsg-2)
  • Migration status for python-pot/riscv64 (0.9.3+dfsg-2 to 0.9.3+dfsg-2): 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-pybedtools/riscv64 (0.10.0-1 to 0.10.0-1)
  • Migration status for python-pybedtools/riscv64 (0.10.0-1 to 0.10.0-1): Will attempt migration (Any information below is purely informational)
• python-pyspike/riscv64 (0.8.0+dfsg-2 to 0.8.0+dfsg-2)
  • Migration status for python-pyspike/riscv64 (0.8.0+dfsg-2 to 0.8.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• python-pyspoa/riscv64 (0.0.10-1 to 0.0.10-1)
  • Migration status for python-pyspoa/riscv64 (0.0.10-1 to 0.0.10-1): Will attempt migration (Any information below is purely informational)
• python-qrencode/riscv64 (1.2-7 to 1.2-7)
  • Migration status for python-qrencode/riscv64 (1.2-7 to 1.2-7): Will attempt migration (Any information below is purely informational)
• python-questplus/riscv64 (2019.4-6 to 2019.4-6)
  • Migration status for python-questplus/riscv64 (2019.4-6 to 2019.4-6): Will attempt migration (Any information below is purely informational)
• python-rtmidi/riscv64 (1.5.8-3 to 1.5.8-3)
  • Migration status for python-rtmidi/riscv64 (1.5.8-3 to 1.5.8-3): Will attempt migration (Any information below is purely informational)
• python-schema-salad/riscv64 (8.5.20240410123758-1 to 8.5.20240410123758-1)
  • Migration status for python-schema-salad/riscv64 (8.5.20240410123758-1 to 8.5.20240410123758-1): Will attempt migration (Any information below is purely informational)
• python-sfml/riscv64 (2.3.2.dev1+dfsg-1 to 2.3.2.dev1+dfsg-1)
  • Migration status for python-sfml/riscv64 (2.3.2.dev1+dfsg-1 to 2.3.2.dev1+dfsg-1): Will attempt migration (Any information below is purely informational)
• python-snappy/riscv64 (0.5.3-1.2 to 0.5.3-1.2)
  • Migration status for python-snappy/riscv64 (0.5.3-1.2 to 0.5.3-1.2): 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-ssdeep/riscv64 (3.4.1-1 to 3.4.1-1)
  • Migration status for python-ssdeep/riscv64 (3.4.1-1 to 3.4.1-1): Will attempt migration (Any information below is purely informational)
• python-suitesparse-graphblas/riscv64 (7.4.0.0-2 to 7.4.0.0-2)
  • Migration status for python-suitesparse-graphblas/riscv64 (7.4.0.0-2 to 7.4.0.0-2): Will attempt migration (Any information below is purely informational)
• python-tesserocr/riscv64 (2.6.0-1 to 2.6.0-1)
  • Migration status for python-tesserocr/riscv64 (2.6.0-1 to 2.6.0-1): 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)
• python-xmlsec/riscv64 (1.3.14-1 to 1.3.14-1)
  • Migration status for python-xmlsec/riscv64 (1.3.14-1 to 1.3.14-1): Will attempt migration (Any information below is purely informational)
• python-yappi/riscv64 (1.4.0-3 to 1.4.0-3)
  • Migration status for python-yappi/riscv64 (1.4.0-3 to 1.4.0-3): Will attempt migration (Any information below is purely informational)
• python3-lxc/riscv64 (1:5.0.0-2 to 1:5.0.0-2)
  • Migration status for python3-lxc/riscv64 (1:5.0.0-2 to 1:5.0.0-2): Will attempt migration (Any information below is purely informational)
• 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)
• pytsk/riscv64 (20200117-3.1 to 20200117-3.1)
  • Migration status for pytsk/riscv64 (20200117-3.1 to 20200117-3.1): Will attempt migration (Any information below is purely informational)
• pyvkfft/mips64el (2024.1.2+ds1-2 to 2024.1.2+ds1-2)
  • Migration status for pyvkfft/mips64el (2024.1.2+ds1-2 to 2024.1.2+ds1-2): Will attempt migration (Any information below is purely informational)
• pyvkfft/riscv64 (2024.1.2+ds1-2 to 2024.1.2+ds1-2)
  • Migration status for pyvkfft/riscv64 (2024.1.2+ds1-2 to 2024.1.2+ds1-2): 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)
• qbootctl/riscv64 (0.1.2-1 to 0.1.2-1)
  • Migration status for qbootctl/riscv64 (0.1.2-1 to 0.1.2-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)
• qd/riscv64 (2.3.23+dfsg.1-1.1 to 2.3.23+dfsg.1-1.1)
  • Migration status for qd/riscv64 (2.3.23+dfsg.1-1.1 to 2.3.23+dfsg.1-1.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)
• qdbm/riscv64 (1.8.78-12.1 to 1.8.78-12.1)
  • Migration status for qdbm/riscv64 (1.8.78-12.1 to 1.8.78-12.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)
• qdmr/riscv64 (0.11.2-1 to 0.11.2-1)
  • Migration status for qdmr/riscv64 (0.11.2-1 to 0.11.2-1): 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)
• qepcad/riscv64 (1.74+ds-4 to 1.74+ds-4)
  • Migration status for qepcad/riscv64 (1.74+ds-4 to 1.74+ds-4): 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)
• 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)
• qhull/riscv64 (2020.2-6 to 2020.2-6)
  • Migration status for qhull/riscv64 (2020.2-6 to 2020.2-6): Will attempt migration (Any information below is purely informational)
• 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)
• 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)
• qlogo/riscv64 (0.92+git.1.29a5ca2-2 to 0.92+git.1.29a5ca2-2)
  • Migration status for qlogo/riscv64 (0.92+git.1.29a5ca2-2 to 0.92+git.1.29a5ca2-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)
• qmc/riscv64 (0.94-4.1 to 0.94-4.1)
  • Migration status for qmc/riscv64 (0.94-4.1 to 0.94-4.1): Will attempt migration (Any information below is purely informational)
• qmidiarp/riscv64 (0.7.0+ds-1 to 0.7.0+ds-1)
  • Migration status for qmidiarp/riscv64 (0.7.0+ds-1 to 0.7.0+ds-1): Will attempt migration (Any information below is purely informational)
• qmidinet/riscv64 (0.9.90-1 to 0.9.90-1)
  • Migration status for qmidinet/riscv64 (0.9.90-1 to 0.9.90-1): 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)
• qmltermwidget/riscv64 (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3)
  • Migration status for qmltermwidget/riscv64 (0.2+git20220109.6322802-3 to 0.2+git20220109.6322802-3): 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)
• qpid-proton/riscv64 (0.37.0-2 to 0.37.0-2)
  • Migration status for qpid-proton/riscv64 (0.37.0-2 to 0.37.0-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)
• qqwing/riscv64 (1.3.4-1.1 to 1.3.4-1.1)
  • Migration status for qqwing/riscv64 (1.3.4-1.1 to 1.3.4-1.1): Will attempt migration (Any information below is purely informational)
• qr-code-generator/riscv64 (1.8.0-1.2 to 1.8.0-1.2)
  • Migration status for qr-code-generator/riscv64 (1.8.0-1.2 to 1.8.0-1.2): Will attempt migration (Any information below is purely informational)
• qrupdate/riscv64 (1.1.2-4 to 1.1.2-4)
  • Migration status for qrupdate/riscv64 (1.1.2-4 to 1.1.2-4): Will attempt migration (Any information below is purely informational)
• qsampler/riscv64 (0.9.90-1 to 0.9.90-1)
  • Migration status for qsampler/riscv64 (0.9.90-1 to 0.9.90-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)
• qstardict/riscv64 (1.4.1-2 to 1.4.1-2)
  • Migration status for qstardict/riscv64 (1.4.1-2 to 1.4.1-2): 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)
• qt5ct/riscv64 (1.8-1 to 1.8-1)
  • Migration status for qt5ct/riscv64 (1.8-1 to 1.8-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)
• qtchooser/riscv64 (66-2 to 66-2)
  • Migration status for qtchooser/riscv64 (66-2 to 66-2): 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)
• qterminal/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for qterminal/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• qtermwidget/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for qtermwidget/riscv64 (1.4.0-1 to 1.4.0-1): 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)
• qtltools/riscv64 (1.3.1+dfsg-4 to 1.3.1+dfsg-4)
  • Migration status for qtltools/riscv64 (1.3.1+dfsg-4 to 1.3.1+dfsg-4): Will attempt migration (Any information below is purely informational)
• qtmir/riscv64 (0.8.0~git20240306.de639c3-1 to 0.8.0~git20240306.de639c3-1)
  • Migration status for qtmir/riscv64 (0.8.0~git20240306.de639c3-1 to 0.8.0~git20240306.de639c3-1): 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)
• qtsystems-opensource-src/riscv64 (5.0~git20230712.81e08ee+dfsg-1 to 5.0~git20230712.81e08ee+dfsg-1)
  • Migration status for qtsystems-opensource-src/riscv64 (5.0~git20230712.81e08ee+dfsg-1 to 5.0~git20230712.81e08ee+dfsg-1): 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)
• quadprog/riscv64 (1.5-8-1 to 1.5-8-1)
  • Migration status for quadprog/riscv64 (1.5-8-1 to 1.5-8-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)
• quantlib/riscv64 (1.34-1 to 1.34-1)
  • Migration status for quantlib/riscv64 (1.34-1 to 1.34-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)
• quelcom/riscv64 (0.4.0-18 to 0.4.0-18)
  • Migration status for quelcom/riscv64 (0.4.0-18 to 0.4.0-18): Will attempt migration (Any information below is purely informational)
• quesoglc/riscv64 (0.7.2-7 to 0.7.2-7)
  • Migration status for quesoglc/riscv64 (0.7.2-7 to 0.7.2-7): 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)
• quickplot/riscv64 (1.0.1~rc-1 to 1.0.1~rc-1)
  • Migration status for quickplot/riscv64 (1.0.1~rc-1 to 1.0.1~rc-1): 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)
• quorum/riscv64 (1.1.2-2 to 1.1.2-2)
  • Migration status for quorum/riscv64 (1.1.2-2 to 1.1.2-2): 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)
• qvge/riscv64 (0.6.3-4 to 0.6.3-4)
  • Migration status for qvge/riscv64 (0.6.3-4 to 0.6.3-4): 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)
• qwinff/riscv64 (0.2.1+git20201215-2 to 0.2.1+git20201215-2)
  • Migration status for qwinff/riscv64 (0.2.1+git20201215-2 to 0.2.1+git20201215-2): 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)
• qxgedit/riscv64 (0.9.90-1 to 0.9.90-1)
  • Migration status for qxgedit/riscv64 (0.9.90-1 to 0.9.90-1): 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)
• qzxing/riscv64 (3.3.0+dfsg-5 to 3.3.0+dfsg-5)
  • Migration status for qzxing/riscv64 (3.3.0+dfsg-5 to 3.3.0+dfsg-5): Will attempt migration (Any information below is purely informational)
• r-bioc-affy/riscv64 (1.80.0-1 to 1.80.0-1)
  • Migration status for r-bioc-affy/riscv64 (1.80.0-1 to 1.80.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-affyio/riscv64 (1.72.0-1 to 1.72.0-1)
  • Migration status for r-bioc-affyio/riscv64 (1.72.0-1 to 1.72.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-biobase/riscv64 (2.62.0-1 to 2.62.0-1)
  • Migration status for r-bioc-biobase/riscv64 (2.62.0-1 to 2.62.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-biocparallel/riscv64 (1.36.0-1 to 1.36.0-1)
  • Migration status for r-bioc-biocparallel/riscv64 (1.36.0-1 to 1.36.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-chemminer/riscv64 (3.54.0+dfsg-1 to 3.54.0+dfsg-1)
  • Migration status for r-bioc-chemminer/riscv64 (3.54.0+dfsg-1 to 3.54.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-bioc-dnacopy/riscv64 (1.76.0-1 to 1.76.0-1)
  • Migration status for r-bioc-dnacopy/riscv64 (1.76.0-1 to 1.76.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-ebseq/riscv64 (2.0.0-1 to 2.0.0-1)
  • Migration status for r-bioc-ebseq/riscv64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-edger/riscv64 (4.0.16+dfsg-1 to 4.0.16+dfsg-1)
  • Migration status for r-bioc-edger/riscv64 (4.0.16+dfsg-1 to 4.0.16+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-bioc-fmcsr/riscv64 (1.44.0+dfsg-1 to 1.44.0+dfsg-1)
  • Migration status for r-bioc-fmcsr/riscv64 (1.44.0+dfsg-1 to 1.44.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-bioc-graph/riscv64 (1.80.0-1 to 1.80.0-1)
  • Migration status for r-bioc-graph/riscv64 (1.80.0-1 to 1.80.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-impute/riscv64 (1.76.0-1 to 1.76.0-1)
  • Migration status for r-bioc-impute/riscv64 (1.76.0-1 to 1.76.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-limma/riscv64 (3.58.1+dfsg-1 to 3.58.1+dfsg-1)
  • Migration status for r-bioc-limma/riscv64 (3.58.1+dfsg-1 to 3.58.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-bioc-lpsymphony/riscv64 (1.30.0+dfsg-1 to 1.30.0+dfsg-1)
  • Migration status for r-bioc-lpsymphony/riscv64 (1.30.0+dfsg-1 to 1.30.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-bioc-makecdfenv/riscv64 (1.78.0-1 to 1.78.0-1)
  • Migration status for r-bioc-makecdfenv/riscv64 (1.78.0-1 to 1.78.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-metapod/riscv64 (1.10.1+dfsg-1 to 1.10.1+dfsg-1)
  • Migration status for r-bioc-metapod/riscv64 (1.10.1+dfsg-1 to 1.10.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-bioc-monocle/riscv64 (2.30.0-1 to 2.30.0-1)
  • Migration status for r-bioc-monocle/riscv64 (2.30.0-1 to 2.30.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-multtest/riscv64 (2.58.0-1 to 2.58.0-1)
  • Migration status for r-bioc-multtest/riscv64 (2.58.0-1 to 2.58.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-pcamethods/riscv64 (1.94.0-1 to 1.94.0-1)
  • Migration status for r-bioc-pcamethods/riscv64 (1.94.0-1 to 1.94.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-preprocesscore/riscv64 (1.64.0+ds-1 to 1.64.0+ds-1)
  • Migration status for r-bioc-preprocesscore/riscv64 (1.64.0+ds-1 to 1.64.0+ds-1): Will attempt migration (Any information below is purely informational)
• r-bioc-rbgl/riscv64 (1.78.0+dfsg-1 to 1.78.0+dfsg-1)
  • Migration status for r-bioc-rbgl/riscv64 (1.78.0+dfsg-1 to 1.78.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-bioc-rhdf5filters/riscv64 (1.14.1+dfsg-3 to 1.14.1+dfsg-3)
  • Migration status for r-bioc-rhdf5filters/riscv64 (1.14.1+dfsg-3 to 1.14.1+dfsg-3): Will attempt migration (Any information below is purely informational)
• r-bioc-rhdf5lib/riscv64 (1.24.2+dfsg-1 to 1.24.2+dfsg-1)
  • Migration status for r-bioc-rhdf5lib/riscv64 (1.24.2+dfsg-1 to 1.24.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-bioc-rhtslib/riscv64 (2.4.1+dfsg-3 to 2.4.1+dfsg-3)
  • Migration status for r-bioc-rhtslib/riscv64 (2.4.1+dfsg-3 to 2.4.1+dfsg-3): Will attempt migration (Any information below is purely informational)
• r-bioc-rots/riscv64 (1.30.0-1 to 1.30.0-1)
  • Migration status for r-bioc-rots/riscv64 (1.30.0-1 to 1.30.0-1): Will attempt migration (Any information below is purely informational)
• r-bioc-rsubread/riscv64 (2.16.1-1 to 2.16.1-1)
  • Migration status for r-bioc-rsubread/riscv64 (2.16.1-1 to 2.16.1-1): Will attempt migration (Any information below is purely informational)
• r-bioc-snpstats/riscv64 (1.52.0+dfsg-1 to 1.52.0+dfsg-1)
  • Migration status for r-bioc-snpstats/riscv64 (1.52.0+dfsg-1 to 1.52.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-bioc-sparsematrixstats/riscv64 (1.14.0+dfsg-1 to 1.14.0+dfsg-1)
  • Migration status for r-bioc-sparsematrixstats/riscv64 (1.14.0+dfsg-1 to 1.14.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-actuar/riscv64 (3.3-4-1 to 3.3-4-1)
  • Migration status for r-cran-actuar/riscv64 (3.3-4-1 to 3.3-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-ade4/riscv64 (1.7-22-1 to 1.7-22-1)
  • Migration status for r-cran-ade4/riscv64 (1.7-22-1 to 1.7-22-1): 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-admisc/riscv64 (0.35-1 to 0.35-1)
  • Migration status for r-cran-admisc/riscv64 (0.35-1 to 0.35-1): Will attempt migration (Any information below is purely informational)
• r-cran-amap/riscv64 (0.8-19-1 to 0.8-19-1)
  • Migration status for r-cran-amap/riscv64 (0.8-19-1 to 0.8-19-1): Will attempt migration (Any information below is purely informational)
• r-cran-amore/riscv64 (0.2-16-2 to 0.2-16-2)
  • Migration status for r-cran-amore/riscv64 (0.2-16-2 to 0.2-16-2): Will attempt migration (Any information below is purely informational)
• r-cran-apcluster/riscv64 (1.4.11-1 to 1.4.11-1)
  • Migration status for r-cran-apcluster/riscv64 (1.4.11-1 to 1.4.11-1): Will attempt migration (Any information below is purely informational)
• r-cran-askpass/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for r-cran-askpass/riscv64 (1.2.0-1 to 1.2.0-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-base64enc/riscv64 (0.1-3-3 to 0.1-3-3)
  • Migration status for r-cran-base64enc/riscv64 (0.1-3-3 to 0.1-3-3): 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-bayesfactor/riscv64 (0.9.12-4.7+dfsg-1 to 0.9.12-4.7+dfsg-1)
  • Migration status for r-cran-bayesfactor/riscv64 (0.9.12-4.7+dfsg-1 to 0.9.12-4.7+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-bayesm/riscv64 (3.1-6+dfsg-1 to 3.1-6+dfsg-1)
  • Migration status for r-cran-bayesm/riscv64 (3.1-6+dfsg-1 to 3.1-6+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-bdgraph/riscv64 (2.72+dfsg-2 to 2.72+dfsg-2)
  • Migration status for r-cran-bdgraph/riscv64 (2.72+dfsg-2 to 2.72+dfsg-2): Will attempt migration (Any information below is purely informational)
• r-cran-bdsmatrix/riscv64 (1.3-7-1 to 1.3-7-1)
  • Migration status for r-cran-bdsmatrix/riscv64 (1.3-7-1 to 1.3-7-1): Will attempt migration (Any information below is purely informational)
• r-cran-beeswarm/riscv64 (0.4.0-1 to 0.4.0-1)
  • Migration status for r-cran-beeswarm/riscv64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-bench/riscv64 (1.1.3-1 to 1.1.3-1)
  • Migration status for r-cran-bench/riscv64 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-biasedurn/riscv64 (2.0.11-1 to 2.0.11-1)
  • Migration status for r-cran-biasedurn/riscv64 (2.0.11-1 to 2.0.11-1): Will attempt migration (Any information below is purely informational)
• r-cran-bindrcpp/riscv64 (0.2.3-1 to 0.2.3-1)
  • Migration status for r-cran-bindrcpp/riscv64 (0.2.3-1 to 0.2.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-bio3d/riscv64 (2.4-4-1 to 2.4-4-1)
  • Migration status for r-cran-bio3d/riscv64 (2.4-4-1 to 2.4-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-bit/riscv64 (4.0.5-1 to 4.0.5-1)
  • Migration status for r-cran-bit/riscv64 (4.0.5-1 to 4.0.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-bit64/riscv64 (4.0.5-1 to 4.0.5-1)
  • Migration status for r-cran-bit64/riscv64 (4.0.5-1 to 4.0.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-bitops/riscv64 (1.0-7-1 to 1.0-7-1)
  • Migration status for r-cran-bitops/riscv64 (1.0-7-1 to 1.0-7-1): Will attempt migration (Any information below is purely informational)
• r-cran-biwt/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-biwt/riscv64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-blockmodeling/riscv64 (1.1.5-1 to 1.1.5-1)
  • Migration status for r-cran-blockmodeling/riscv64 (1.1.5-1 to 1.1.5-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-brglm/riscv64 (0.7.2-1 to 0.7.2-1)
  • Migration status for r-cran-brglm/riscv64 (0.7.2-1 to 0.7.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-brglm2/riscv64 (0.9.2+dfsg-1 to 0.9.2+dfsg-1)
  • Migration status for r-cran-brglm2/riscv64 (0.9.2+dfsg-1 to 0.9.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-brio/riscv64 (1.1.5-1 to 1.1.5-1)
  • Migration status for r-cran-brio/riscv64 (1.1.5-1 to 1.1.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-cachem/riscv64 (1.0.8-1 to 1.0.8-1)
  • Migration status for r-cran-cachem/riscv64 (1.0.8-1 to 1.0.8-1): Will attempt migration (Any information below is purely informational)
• r-cran-cairo/riscv64 (1.6-2-1 to 1.6-2-1)
  • Migration status for r-cran-cairo/riscv64 (1.6-2-1 to 1.6-2-1): Will attempt migration (Any information below is purely informational)
• r-cran-caret/riscv64 (6.0-94+dfsg-1 to 6.0-94+dfsg-1)
  • Migration status for r-cran-caret/riscv64 (6.0-94+dfsg-1 to 6.0-94+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-catools/riscv64 (1.18.2-1 to 1.18.2-1)
  • Migration status for r-cran-catools/riscv64 (1.18.2-1 to 1.18.2-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-circular/riscv64 (0.5-0-1 to 0.5-0-1)
  • Migration status for r-cran-circular/riscv64 (0.5-0-1 to 0.5-0-1): Will attempt migration (Any information below is purely informational)
• r-cran-class/riscv64 (7.3-22-2 to 7.3-22-2)
  • Migration status for r-cran-class/riscv64 (7.3-22-2 to 7.3-22-2): Will attempt migration (Any information below is purely informational)
• r-cran-classint/riscv64 (0.4-10+dfsg-1 to 0.4-10+dfsg-1)
  • Migration status for r-cran-classint/riscv64 (0.4-10+dfsg-1 to 0.4-10+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-cli/riscv64 (3.6.2-1 to 3.6.2-1)
  • Migration status for r-cran-cli/riscv64 (3.6.2-1 to 3.6.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-clock/riscv64 (0.7.0-1.1 to 0.7.0-1.1)
  • Migration status for r-cran-clock/riscv64 (0.7.0-1.1 to 0.7.0-1.1): Will attempt migration (Any information below is purely informational)
• r-cran-clue/riscv64 (0.3-65-1 to 0.3-65-1)
  • Migration status for r-cran-clue/riscv64 (0.3-65-1 to 0.3-65-1): Will attempt migration (Any information below is purely informational)
• r-cran-cmprsk/riscv64 (2.2-11-1 to 2.2-11-1)
  • Migration status for r-cran-cmprsk/riscv64 (2.2-11-1 to 2.2-11-1): Will attempt migration (Any information below is purely informational)
• r-cran-coin/riscv64 (1.4-3-1 to 1.4-3-1)
  • Migration status for r-cran-coin/riscv64 (1.4-3-1 to 1.4-3-1): Will attempt migration (Any information below is purely informational)
• r-cran-colorspace/riscv64 (2.1-0+dfsg-1 to 2.1-0+dfsg-1)
  • Migration status for r-cran-colorspace/riscv64 (2.1-0+dfsg-1 to 2.1-0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-commonmark/riscv64 (1.9.1-1 to 1.9.1-1)
  • Migration status for r-cran-commonmark/riscv64 (1.9.1-1 to 1.9.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-conquer/riscv64 (1.3.3-1 to 1.3.3-1)
  • Migration status for r-cran-conquer/riscv64 (1.3.3-1 to 1.3.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-contfrac/riscv64 (1.1-12-2 to 1.1-12-2)
  • Migration status for r-cran-contfrac/riscv64 (1.1-12-2 to 1.1-12-2): Will attempt migration (Any information below is purely informational)
• r-cran-covr/riscv64 (3.6.4+dfsg-1 to 3.6.4+dfsg-1)
  • Migration status for r-cran-covr/riscv64 (3.6.4+dfsg-1 to 3.6.4+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-ctmcd/riscv64 (1.4.4+dfsg-1 to 1.4.4+dfsg-1)
  • Migration status for r-cran-ctmcd/riscv64 (1.4.4+dfsg-1 to 1.4.4+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-cutpointr/riscv64 (1.1.2-1 to 1.1.2-1)
  • Migration status for r-cran-cutpointr/riscv64 (1.1.2-1 to 1.1.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-dbscan/riscv64 (1.1-12+ds-1 to 1.1-12+ds-1)
  • Migration status for r-cran-dbscan/riscv64 (1.1-12+ds-1 to 1.1-12+ds-1): Will attempt migration (Any information below is purely informational)
• r-cran-ddalpha/riscv64 (1.3.15-1 to 1.3.15-1)
  • Migration status for r-cran-ddalpha/riscv64 (1.3.15-1 to 1.3.15-1): Will attempt migration (Any information below is purely informational)
• r-cran-ddrtree/riscv64 (0.1.5-2 to 0.1.5-2)
  • Migration status for r-cran-ddrtree/riscv64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• r-cran-deal/riscv64 (1:1.2-42-1 to 1:1.2-42-1)
  • Migration status for r-cran-deal/riscv64 (1:1.2-42-1 to 1:1.2-42-1): Will attempt migration (Any information below is purely informational)
• r-cran-decor/riscv64 (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-decor/riscv64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-deldir/riscv64 (2.0-4-1 to 2.0-4-1)
  • Migration status for r-cran-deldir/riscv64 (2.0-4-1 to 2.0-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-densityclust/riscv64 (0.3.3-1 to 0.3.3-1)
  • Migration status for r-cran-densityclust/riscv64 (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-deoptim/riscv64 (2.2-8-1 to 2.2-8-1)
  • Migration status for r-cran-deoptim/riscv64 (2.2-8-1 to 2.2-8-1): Will attempt migration (Any information below is purely informational)
• r-cran-desolve/riscv64 (1.40-1 to 1.40-1)
  • Migration status for r-cran-desolve/riscv64 (1.40-1 to 1.40-1): Will attempt migration (Any information below is purely informational)
• r-cran-dicedesign/riscv64 (1.10-1 to 1.10-1)
  • Migration status for r-cran-dicedesign/riscv64 (1.10-1 to 1.10-1): Will attempt migration (Any information below is purely informational)
• r-cran-diffobj/riscv64 (0.3.5-1 to 0.3.5-1)
  • Migration status for r-cran-diffobj/riscv64 (0.3.5-1 to 0.3.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-diptest/riscv64 (0.77-0-1 to 0.77-0-1)
  • Migration status for r-cran-diptest/riscv64 (0.77-0-1 to 0.77-0-1): Will attempt migration (Any information below is purely informational)
• r-cran-distory/riscv64 (1.4.4-1 to 1.4.4-1)
  • Migration status for r-cran-distory/riscv64 (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
• r-cran-distr/riscv64 (2.9.3+dfsg-1 to 2.9.3+dfsg-1)
  • Migration status for r-cran-distr/riscv64 (2.9.3+dfsg-1 to 2.9.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-dosefinding/riscv64 (1.1-1-1 to 1.1-1-1)
  • Migration status for r-cran-dosefinding/riscv64 (1.1-1-1 to 1.1-1-1): Will attempt migration (Any information below is purely informational)
• r-cran-dotcall64/riscv64 (1.1-1-1 to 1.1-1-1)
  • Migration status for r-cran-dotcall64/riscv64 (1.1-1-1 to 1.1-1-1): Will attempt migration (Any information below is purely informational)
• r-cran-dplyr/riscv64 (1.1.4-1 to 1.1.4-1)
  • Migration status for r-cran-dplyr/riscv64 (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
• r-cran-dqrng/riscv64 (0.3.2+dfsg-1 to 0.3.2+dfsg-1)
  • Migration status for r-cran-dqrng/riscv64 (0.3.2+dfsg-1 to 0.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-e1071/riscv64 (1.7-14-1 to 1.7-14-1)
  • Migration status for r-cran-e1071/riscv64 (1.7-14-1 to 1.7-14-1): Will attempt migration (Any information below is purely informational)
• r-cran-eaf/riscv64 (2.5-1 to 2.5-1)
  • Migration status for r-cran-eaf/riscv64 (2.5-1 to 2.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-earth/riscv64 (5.3.3-1 to 5.3.3-1)
  • Migration status for r-cran-earth/riscv64 (5.3.3-1 to 5.3.3-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-ecosolver/riscv64 (0.5.5-1 to 0.5.5-1)
  • Migration status for r-cran-ecosolver/riscv64 (0.5.5-1 to 0.5.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-eipack/riscv64 (0.2-2-1 to 0.2-2-1)
  • Migration status for r-cran-eipack/riscv64 (0.2-2-1 to 0.2-2-1): Will attempt migration (Any information below is purely informational)
• r-cran-ellipsis/riscv64 (0.3.2-2 to 0.3.2-2)
  • Migration status for r-cran-ellipsis/riscv64 (0.3.2-2 to 0.3.2-2): Will attempt migration (Any information below is purely informational)
• r-cran-emoa/riscv64 (0.5-2-1 to 0.5-2-1)
  • Migration status for r-cran-emoa/riscv64 (0.5-2-1 to 0.5-2-1): Will attempt migration (Any information below is purely informational)
• r-cran-energy/riscv64 (1.7-11-1 to 1.7-11-1)
  • Migration status for r-cran-energy/riscv64 (1.7-11-1 to 1.7-11-1): Will attempt migration (Any information below is purely informational)
• r-cran-epi/riscv64 (2.47.1-2 to 2.47.1-2)
  • Migration status for r-cran-epi/riscv64 (2.47.1-2 to 2.47.1-2): Will attempt migration (Any information below is purely informational)
• r-cran-erm/riscv64 (1.0-6-1 to 1.0-6-1)
  • Migration status for r-cran-erm/riscv64 (1.0-6-1 to 1.0-6-1): Will attempt migration (Any information below is purely informational)
• r-cran-etm/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for r-cran-etm/riscv64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-evd/riscv64 (2.3-6.1-1 to 2.3-6.1-1)
  • Migration status for r-cran-evd/riscv64 (2.3-6.1-1 to 2.3-6.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-exactranktests/riscv64 (0.8-35-1 to 0.8-35-1)
  • Migration status for r-cran-exactranktests/riscv64 (0.8-35-1 to 0.8-35-1): Will attempt migration (Any information below is purely informational)
• r-cran-expint/riscv64 (0.1-8-1 to 0.1-8-1)
  • Migration status for r-cran-expint/riscv64 (0.1-8-1 to 0.1-8-1): Will attempt migration (Any information below is purely informational)
• r-cran-expm/riscv64 (0.999-9-1 to 0.999-9-1)
  • Migration status for r-cran-expm/riscv64 (0.999-9-1 to 0.999-9-1): Will attempt migration (Any information below is purely informational)
• r-cran-extradistr/riscv64 (1.10.0-1 to 1.10.0-1)
  • Migration status for r-cran-extradistr/riscv64 (1.10.0-1 to 1.10.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-fansi/riscv64 (1.0.5-1 to 1.0.5-1)
  • Migration status for r-cran-fansi/riscv64 (1.0.5-1 to 1.0.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-fastcluster/riscv64 (1.2.6-1 to 1.2.6-1)
  • Migration status for r-cran-fastcluster/riscv64 (1.2.6-1 to 1.2.6-1): Will attempt migration (Any information below is purely informational)
• r-cran-fastica/riscv64 (1.2-4-1 to 1.2-4-1)
  • Migration status for r-cran-fastica/riscv64 (1.2-4-1 to 1.2-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-fastmap/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for r-cran-fastmap/riscv64 (1.1.1-1 to 1.1.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-fastmatch/riscv64 (1.1-4-1 to 1.1-4-1)
  • Migration status for r-cran-fastmatch/riscv64 (1.1-4-1 to 1.1-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-fdrtool/riscv64 (1.2.17-2 to 1.2.17-2)
  • Migration status for r-cran-fdrtool/riscv64 (1.2.17-2 to 1.2.17-2): Will attempt migration (Any information below is purely informational)
• r-cran-fftw/riscv64 (1.0-8-1 to 1.0-8-1)
  • Migration status for r-cran-fftw/riscv64 (1.0-8-1 to 1.0-8-1): Will attempt migration (Any information below is purely informational)
• r-cran-filehash/riscv64 (2.4-5-1 to 2.4-5-1)
  • Migration status for r-cran-filehash/riscv64 (2.4-5-1 to 2.4-5-1): Will attempt migration (Any information below is purely informational)
• r-cran-filelock/riscv64 (1.0.3-1 to 1.0.3-1)
  • Migration status for r-cran-filelock/riscv64 (1.0.3-1 to 1.0.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-fingerprint/riscv64 (3.5.7-2 to 3.5.7-2)
  • Migration status for r-cran-fingerprint/riscv64 (3.5.7-2 to 3.5.7-2): Will attempt migration (Any information below is purely informational)
• r-cran-flashclust/riscv64 (1.01-2-3 to 1.01-2-3)
  • Migration status for r-cran-flashclust/riscv64 (1.01-2-3 to 1.01-2-3): Will attempt migration (Any information below is purely informational)
• r-cran-fnn/riscv64 (1.1.4-1 to 1.1.4-1)
  • Migration status for r-cran-fnn/riscv64 (1.1.4-1 to 1.1.4-1): Will attempt migration (Any information below is purely informational)
• r-cran-fracdiff/riscv64 (1.5-3-1 to 1.5-3-1)
  • Migration status for r-cran-fracdiff/riscv64 (1.5-3-1 to 1.5-3-1): Will attempt migration (Any information below is purely informational)
• r-cran-freetypeharfbuzz/riscv64 (0.2.6+dfsg-3 to 0.2.6+dfsg-3)
  • Migration status for r-cran-freetypeharfbuzz/riscv64 (0.2.6+dfsg-3 to 0.2.6+dfsg-3): Will attempt migration (Any information below is purely informational)
• r-cran-fts/riscv64 (0.9.9.2-2 to 0.9.9.2-2)
  • Migration status for r-cran-fts/riscv64 (0.9.9.2-2 to 0.9.9.2-2): Will attempt migration (Any information below is purely informational)
• r-cran-gam/riscv64 (1.22-3-1 to 1.22-3-1)
  • Migration status for r-cran-gam/riscv64 (1.22-3-1 to 1.22-3-1): Will attempt migration (Any information below is purely informational)
• r-cran-geepack/riscv64 (1.3.10-1 to 1.3.10-1)
  • Migration status for r-cran-geepack/riscv64 (1.3.10-1 to 1.3.10-1): Will attempt migration (Any information below is purely informational)
• r-cran-genabel/riscv64 (1.8-0-7 to 1.8-0-7)
  • Migration status for r-cran-genabel/riscv64 (1.8-0-7 to 1.8-0-7): Will attempt migration (Any information below is purely informational)
• r-cran-genie/riscv64 (1.0.5-2 to 1.0.5-2)
  • Migration status for r-cran-genie/riscv64 (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• r-cran-genieclust/riscv64 (1.1.5-2-1 to 1.1.5-2-1)
  • Migration status for r-cran-genieclust/riscv64 (1.1.5-2-1 to 1.1.5-2-1): Will attempt migration (Any information below is purely informational)
• r-cran-geometry/riscv64 (0.4.7-1 to 0.4.7-1)
  • Migration status for r-cran-geometry/riscv64 (0.4.7-1 to 0.4.7-1): Will attempt migration (Any information below is purely informational)
• r-cran-geosphere/riscv64 (1.5-18-1 to 1.5-18-1)
  • Migration status for r-cran-geosphere/riscv64 (1.5-18-1 to 1.5-18-1): Will attempt migration (Any information below is purely informational)
• r-cran-gert/riscv64 (2.0.1+dfsg-1 to 2.0.1+dfsg-1)
  • Migration status for r-cran-gert/riscv64 (2.0.1+dfsg-1 to 2.0.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-ggforce/riscv64 (0.4.2-1 to 0.4.2-1)
  • Migration status for r-cran-ggforce/riscv64 (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-ggraph/riscv64 (2.1.0+dfsg-1 to 2.1.0+dfsg-1)
  • Migration status for r-cran-ggraph/riscv64 (2.1.0+dfsg-1 to 2.1.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-ggrepel/riscv64 (0.9.5-2 to 0.9.5-2)
  • Migration status for r-cran-ggrepel/riscv64 (0.9.5-2 to 0.9.5-2): Will attempt migration (Any information below is purely informational)
• r-cran-git2r/riscv64 (0.33.0+dfsg-1 to 0.33.0+dfsg-1)
  • Migration status for r-cran-git2r/riscv64 (0.33.0+dfsg-1 to 0.33.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-glasso/riscv64 (1.11-2 to 1.11-2)
  • Migration status for r-cran-glasso/riscv64 (1.11-2 to 1.11-2): Will attempt migration (Any information below is purely informational)
• r-cran-glmmtmb/riscv64 (1.1.8+dfsg-3 to 1.1.8+dfsg-3)
  • Migration status for r-cran-glmmtmb/riscv64 (1.1.8+dfsg-3 to 1.1.8+dfsg-3): Will attempt migration (Any information below is purely informational)
• r-cran-glmnet/riscv64 (4.1-8-1 to 4.1-8-1)
  • Migration status for r-cran-glmnet/riscv64 (4.1-8-1 to 4.1-8-1): Will attempt migration (Any information below is purely informational)
• r-cran-glue/riscv64 (1.7.0-1 to 1.7.0-1)
  • Migration status for r-cran-glue/riscv64 (1.7.0-1 to 1.7.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-gmm/riscv64 (1.8-1 to 1.8-1)
  • Migration status for r-cran-gmm/riscv64 (1.8-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
• r-cran-gmp/riscv64 (0.7-4-1 to 0.7-4-1)
  • Migration status for r-cran-gmp/riscv64 (0.7-4-1 to 0.7-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-gnm/riscv64 (1.1-5-1 to 1.1-5-1)
  • Migration status for r-cran-gnm/riscv64 (1.1-5-1 to 1.1-5-1): Will attempt migration (Any information below is purely informational)
• r-cran-goftest/riscv64 (1.2-3-1 to 1.2-3-1)
  • Migration status for r-cran-goftest/riscv64 (1.2-3-1 to 1.2-3-1): Will attempt migration (Any information below is purely informational)
• r-cran-gower/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-gower/riscv64 (1.0.1-1 to 1.0.1-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-gsl/riscv64 (2.1-8-1 to 2.1-8-1)
  • Migration status for r-cran-gsl/riscv64 (2.1-8-1 to 2.1-8-1): Will attempt migration (Any information below is purely informational)
• r-cran-gss/riscv64 (2.2-7-1 to 2.2-7-1)
  • Migration status for r-cran-gss/riscv64 (2.2-7-1 to 2.2-7-1): Will attempt migration (Any information below is purely informational)
• r-cran-gunifrac/riscv64 (1.8+dfsg-1 to 1.8+dfsg-1)
  • Migration status for r-cran-gunifrac/riscv64 (1.8+dfsg-1 to 1.8+dfsg-1): 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-haven/riscv64 (2.5.4-1 to 2.5.4-1)
  • Migration status for r-cran-haven/riscv64 (2.5.4-1 to 2.5.4-1): Will attempt migration (Any information below is purely informational)
• r-cran-hdf5r/riscv64 (1.3.9+dfsg-1 to 1.3.9+dfsg-1)
  • Migration status for r-cran-hdf5r/riscv64 (1.3.9+dfsg-1 to 1.3.9+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-hexbin/riscv64 (1.28.3-1 to 1.28.3-1)
  • Migration status for r-cran-hexbin/riscv64 (1.28.3-1 to 1.28.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-httpuv/riscv64 (1.6.15+dfsg-1 to 1.6.15+dfsg-1)
  • Migration status for r-cran-httpuv/riscv64 (1.6.15+dfsg-1 to 1.6.15+dfsg-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-hunspell/riscv64 (3.0.3+dfsg2-2 to 3.0.3+dfsg2-2)
  • Migration status for r-cran-hunspell/riscv64 (3.0.3+dfsg2-2 to 3.0.3+dfsg2-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-interp/riscv64 (1.1-6-1 to 1.1-6-1)
  • Migration status for r-cran-interp/riscv64 (1.1-6-1 to 1.1-6-1): Will attempt migration (Any information below is purely informational)
• r-cran-intervals/riscv64 (0.15.4-1 to 0.15.4-1)
  • Migration status for r-cran-intervals/riscv64 (0.15.4-1 to 0.15.4-1): Will attempt migration (Any information below is purely informational)
• r-cran-ipred/riscv64 (0.9-14-1 to 0.9-14-1)
  • Migration status for r-cran-ipred/riscv64 (0.9-14-1 to 0.9-14-1): Will attempt migration (Any information below is purely informational)
• r-cran-irace/riscv64 (3.5-2 to 3.5-2)
  • Migration status for r-cran-irace/riscv64 (3.5-2 to 3.5-2): Will attempt migration (Any information below is purely informational)
• r-cran-iso/riscv64 (0.0-21-1 to 0.0-21-1)
  • Migration status for r-cran-iso/riscv64 (0.0-21-1 to 0.0-21-1): Will attempt migration (Any information below is purely informational)
• r-cran-isoband/riscv64 (0.2.7-1 to 0.2.7-1)
  • Migration status for r-cran-isoband/riscv64 (0.2.7-1 to 0.2.7-1): Will attempt migration (Any information below is purely informational)
• r-cran-isospecr/riscv64 (2.1.3-1 to 2.1.3-1)
  • Migration status for r-cran-isospecr/riscv64 (2.1.3-1 to 2.1.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-jinjar/riscv64 (0.3.1+dfsg-1 to 0.3.1+dfsg-1)
  • Migration status for r-cran-jinjar/riscv64 (0.3.1+dfsg-1 to 0.3.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-jomo/riscv64 (2.7-6-1 to 2.7-6-1)
  • Migration status for r-cran-jomo/riscv64 (2.7-6-1 to 2.7-6-1): Will attempt migration (Any information below is purely informational)
• r-cran-jpeg/riscv64 (0.1-10-1 to 0.1-10-1)
  • Migration status for r-cran-jpeg/riscv64 (0.1-10-1 to 0.1-10-1): Will attempt migration (Any information below is purely informational)
• r-cran-jsonlite/riscv64 (1.8.8+dfsg-1 to 1.8.8+dfsg-1)
  • Migration status for r-cran-jsonlite/riscv64 (1.8.8+dfsg-1 to 1.8.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-kernlab/riscv64 (0.9-32-1 to 0.9-32-1)
  • Migration status for r-cran-kernlab/riscv64 (0.9-32-1 to 0.9-32-1): Will attempt migration (Any information below is purely informational)
• r-cran-keyring/riscv64 (1.3.2-1 to 1.3.2-1)
  • Migration status for r-cran-keyring/riscv64 (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-kmsurv/riscv64 (0.1-5-2 to 0.1-5-2)
  • Migration status for r-cran-kmsurv/riscv64 (0.1-5-2 to 0.1-5-2): Will attempt migration (Any information below is purely informational)
• r-cran-knn.covertree/riscv64 (1.0-2 to 1.0-2)
  • Migration status for r-cran-knn.covertree/riscv64 (1.0-2 to 1.0-2): Will attempt migration (Any information below is purely informational)
• r-cran-kohonen/riscv64 (3.0.12+dfsg-1 to 3.0.12+dfsg-1)
  • Migration status for r-cran-kohonen/riscv64 (3.0.12+dfsg-1 to 3.0.12+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-ks/riscv64 (1.14.2-1 to 1.14.2-1)
  • Migration status for r-cran-ks/riscv64 (1.14.2-1 to 1.14.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-ksamples/riscv64 (1.2-10-1 to 1.2-10-1)
  • Migration status for r-cran-ksamples/riscv64 (1.2-10-1 to 1.2-10-1): Will attempt migration (Any information below is purely informational)
• r-cran-labdsv/riscv64 (2.1-0-1 to 2.1-0-1)
  • Migration status for r-cran-labdsv/riscv64 (2.1-0-1 to 2.1-0-1): Will attempt migration (Any information below is purely informational)
• r-cran-lamw/riscv64 (2.2.3-1 to 2.2.3-1)
  • Migration status for r-cran-lamw/riscv64 (2.2.3-1 to 2.2.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-later/riscv64 (1.3.2+dfsg-1 to 1.3.2+dfsg-1)
  • Migration status for r-cran-later/riscv64 (1.3.2+dfsg-1 to 1.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-lazyeval/riscv64 (0.2.2-1 to 0.2.2-1)
  • Migration status for r-cran-lazyeval/riscv64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-lbfgsb3c/riscv64 (2020-3.3-1 to 2020-3.3-1)
  • Migration status for r-cran-lbfgsb3c/riscv64 (2020-3.3-1 to 2020-3.3-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-lhs/riscv64 (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-lhs/riscv64 (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• r-cran-libcoin/riscv64 (1.0-10-1 to 1.0-10-1)
  • Migration status for r-cran-libcoin/riscv64 (1.0-10-1 to 1.0-10-1): Will attempt migration (Any information below is purely informational)
• r-cran-lobstr/riscv64 (1.1.2-1 to 1.1.2-1)
  • Migration status for r-cran-lobstr/riscv64 (1.1.2-1 to 1.1.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-lpsolve/riscv64 (5.6.20-1 to 5.6.20-1)
  • Migration status for r-cran-lpsolve/riscv64 (5.6.20-1 to 5.6.20-1): Will attempt migration (Any information below is purely informational)
• r-cran-lsei/riscv64 (1.3-0-1 to 1.3-0-1)
  • Migration status for r-cran-lsei/riscv64 (1.3-0-1 to 1.3-0-1): Will attempt migration (Any information below is purely informational)
• r-cran-lubridate/riscv64 (1.9.3+dfsg-1 to 1.9.3+dfsg-1)
  • Migration status for r-cran-lubridate/riscv64 (1.9.3+dfsg-1 to 1.9.3+dfsg-1): 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-magrittr/riscv64 (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-magrittr/riscv64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-maldiquant/riscv64 (1.22.2-1 to 1.22.2-1)
  • Migration status for r-cran-maldiquant/riscv64 (1.22.2-1 to 1.22.2-1): 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-mapdata/riscv64 (2.3.1-1 to 2.3.1-1)
  • Migration status for r-cran-mapdata/riscv64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-mapproj/riscv64 (1.2.11-1 to 1.2.11-1)
  • Migration status for r-cran-mapproj/riscv64 (1.2.11-1 to 1.2.11-1): Will attempt migration (Any information below is purely informational)
• r-cran-maps/riscv64 (3.4.2-1 to 3.4.2-1)
  • Migration status for r-cran-maps/riscv64 (3.4.2-1 to 3.4.2-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-matching/riscv64 (4.10-14-1 to 4.10-14-1)
  • Migration status for r-cran-matching/riscv64 (4.10-14-1 to 4.10-14-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-maxstat/riscv64 (0.7-25-2 to 0.7-25-2)
  • Migration status for r-cran-maxstat/riscv64 (0.7-25-2 to 0.7-25-2): Will attempt migration (Any information below is purely informational)
• r-cran-mclust/riscv64 (6.0.1-1 to 6.0.1-1)
  • Migration status for r-cran-mclust/riscv64 (6.0.1-1 to 6.0.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-mclustcomp/riscv64 (0.3.3-2 to 0.3.3-2)
  • Migration status for r-cran-mclustcomp/riscv64 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• r-cran-mcmc/riscv64 (0.9-8-1 to 0.9-8-1)
  • Migration status for r-cran-mcmc/riscv64 (0.9-8-1 to 0.9-8-1): Will attempt migration (Any information below is purely informational)
• r-cran-mcmcpack/riscv64 (1.7-0-1 to 1.7-0-1)
  • Migration status for r-cran-mcmcpack/riscv64 (1.7-0-1 to 1.7-0-1): Will attempt migration (Any information below is purely informational)
• r-cran-mda/riscv64 (0.5-4-1 to 0.5-4-1)
  • Migration status for r-cran-mda/riscv64 (0.5-4-1 to 0.5-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-medadherence/riscv64 (1.03-6 to 1.03-6)
  • Migration status for r-cran-medadherence/riscv64 (1.03-6 to 1.03-6): Will attempt migration (Any information below is purely informational)
• r-cran-memisc/riscv64 (0.99.31.7+dfsg-1 to 0.99.31.7+dfsg-1)
  • Migration status for r-cran-memisc/riscv64 (0.99.31.7+dfsg-1 to 0.99.31.7+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-mets/riscv64 (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for r-cran-mets/riscv64 (1.3.3+dfsg-1 to 1.3.3+dfsg-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-mime/riscv64 (0.12-2 to 0.12-2)
  • Migration status for r-cran-mime/riscv64 (0.12-2 to 0.12-2): Will attempt migration (Any information below is purely informational)
• r-cran-minerva/riscv64 (1.5.10-1 to 1.5.10-1)
  • Migration status for r-cran-minerva/riscv64 (1.5.10-1 to 1.5.10-1): Will attempt migration (Any information below is purely informational)
• r-cran-minpack.lm/riscv64 (1.2-4-1 to 1.2-4-1)
  • Migration status for r-cran-minpack.lm/riscv64 (1.2-4-1 to 1.2-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-mixsqp/riscv64 (0.3-54-1 to 0.3-54-1)
  • Migration status for r-cran-mixsqp/riscv64 (0.3-54-1 to 0.3-54-1): Will attempt migration (Any information below is purely informational)
• r-cran-mixtools/riscv64 (2.0.0-1 to 2.0.0-1)
  • Migration status for r-cran-mixtools/riscv64 (2.0.0-1 to 2.0.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-mnp/riscv64 (3.1-4-1 to 3.1-4-1)
  • Migration status for r-cran-mnp/riscv64 (3.1-4-1 to 3.1-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-modelmetrics/riscv64 (1.2.2.2-1 to 1.2.2.2-1)
  • Migration status for r-cran-modelmetrics/riscv64 (1.2.2.2-1 to 1.2.2.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-msm/riscv64 (1.7.1-1 to 1.7.1-1)
  • Migration status for r-cran-msm/riscv64 (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-multicool/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for r-cran-multicool/riscv64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-mvnfast/riscv64 (0.2.8+dfsg-1 to 0.2.8+dfsg-1)
  • Migration status for r-cran-mvnfast/riscv64 (0.2.8+dfsg-1 to 0.2.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-nanoarrow/riscv64 (0.4.0-1 to 0.4.0-1)
  • Migration status for r-cran-nanoarrow/riscv64 (0.4.0-1 to 0.4.0-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-network/riscv64 (1.18.2-1 to 1.18.2-1)
  • Migration status for r-cran-network/riscv64 (1.18.2-1 to 1.18.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-nleqslv/riscv64 (3.3.5-1 to 3.3.5-1)
  • Migration status for r-cran-nleqslv/riscv64 (3.3.5-1 to 3.3.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-nmf/riscv64 (0.27-1 to 0.27-1)
  • Migration status for r-cran-nmf/riscv64 (0.27-1 to 0.27-1): Will attempt migration (Any information below is purely informational)
• r-cran-nnet/riscv64 (7.3-19-2 to 7.3-19-2)
  • Migration status for r-cran-nnet/riscv64 (7.3-19-2 to 7.3-19-2): Will attempt migration (Any information below is purely informational)
• r-cran-nnls/riscv64 (1.5-1 to 1.5-1)
  • Migration status for r-cran-nnls/riscv64 (1.5-1 to 1.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-oaqc/riscv64 (1.0-2 to 1.0-2)
  • Migration status for r-cran-oaqc/riscv64 (1.0-2 to 1.0-2): Will attempt migration (Any information below is purely informational)
• r-cran-openssl/riscv64 (2.1.1+dfsg-2 to 2.1.1+dfsg-2)
  • Migration status for r-cran-openssl/riscv64 (2.1.1+dfsg-2 to 2.1.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• r-cran-openxlsx/riscv64 (4.2.5.2-1 to 4.2.5.2-1)
  • Migration status for r-cran-openxlsx/riscv64 (4.2.5.2-1 to 4.2.5.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-ordinal/riscv64 (2023.12-4-1 to 2023.12-4-1)
  • Migration status for r-cran-ordinal/riscv64 (2023.12-4-1 to 2023.12-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-pan/riscv64 (1.9-1 to 1.9-1)
  • Migration status for r-cran-pan/riscv64 (1.9-1 to 1.9-1): Will attempt migration (Any information below is purely informational)
• r-cran-pander/riscv64 (0.6.5+dfsg-3+deb12u1 to 0.6.5+dfsg-3+deb12u1)
  • Migration status for r-cran-pander/riscv64 (0.6.5+dfsg-3+deb12u1 to 0.6.5+dfsg-3+deb12u1): Will attempt migration (Any information below is purely informational)
• r-cran-parallelly/riscv64 (1.37.1-1 to 1.37.1-1)
  • Migration status for r-cran-parallelly/riscv64 (1.37.1-1 to 1.37.1-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-parmigene/riscv64 (1.1.0-1 to 1.1.0-1)
  • Migration status for r-cran-parmigene/riscv64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-partitions/riscv64 (1.10-7+ds-1 to 1.10-7+ds-1)
  • Migration status for r-cran-partitions/riscv64 (1.10-7+ds-1 to 1.10-7+ds-1): Will attempt migration (Any information below is purely informational)
• r-cran-party/riscv64 (1.3-14-1 to 1.3-14-1)
  • Migration status for r-cran-party/riscv64 (1.3-14-1 to 1.3-14-1): Will attempt migration (Any information below is purely informational)
• r-cran-partykit/riscv64 (1.2-20-1 to 1.2-20-1)
  • Migration status for r-cran-partykit/riscv64 (1.2-20-1 to 1.2-20-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-pbivnorm/riscv64 (0.6.0-4 to 0.6.0-4)
  • Migration status for r-cran-pbivnorm/riscv64 (0.6.0-4 to 0.6.0-4): Will attempt migration (Any information below is purely informational)
• r-cran-pbmcapply/riscv64 (1.5.1-1 to 1.5.1-1)
  • Migration status for r-cran-pbmcapply/riscv64 (1.5.1-1 to 1.5.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-pcapp/riscv64 (2.0-4-1 to 2.0-4-1)
  • Migration status for r-cran-pcapp/riscv64 (2.0-4-1 to 2.0-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-pcict/riscv64 (0.5-4.4-1 to 0.5-4.4-1)
  • Migration status for r-cran-pcict/riscv64 (0.5-4.4-1 to 0.5-4.4-1): Will attempt migration (Any information below is purely informational)
• r-cran-pdftools/riscv64 (3.4.0-1 to 3.4.0-1)
  • Migration status for r-cran-pdftools/riscv64 (3.4.0-1 to 3.4.0-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-pingr/riscv64 (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-pingr/riscv64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-pki/riscv64 (0.1-12-2 to 0.1-12-2)
  • Migration status for r-cran-pki/riscv64 (0.1-12-2 to 0.1-12-2): Will attempt migration (Any information below is purely informational)
• r-cran-plyr/riscv64 (1.8.9-1 to 1.8.9-1)
  • Migration status for r-cran-plyr/riscv64 (1.8.9-1 to 1.8.9-1): Will attempt migration (Any information below is purely informational)
• r-cran-png/riscv64 (0.1-8-1 to 0.1-8-1)
  • Migration status for r-cran-png/riscv64 (0.1-8-1 to 0.1-8-1): Will attempt migration (Any information below is purely informational)
• r-cran-poissonbinomial/riscv64 (1.2.6-1 to 1.2.6-1)
  • Migration status for r-cran-poissonbinomial/riscv64 (1.2.6-1 to 1.2.6-1): Will attempt migration (Any information below is purely informational)
• r-cran-polyclip/riscv64 (1.10-6-1 to 1.10-6-1)
  • Migration status for r-cran-polyclip/riscv64 (1.10-6-1 to 1.10-6-1): Will attempt migration (Any information below is purely informational)
• r-cran-princurve/riscv64 (2.1.6-1 to 2.1.6-1)
  • Migration status for r-cran-princurve/riscv64 (2.1.6-1 to 2.1.6-1): Will attempt migration (Any information below is purely informational)
• r-cran-proc/riscv64 (1.18.5-1 to 1.18.5-1)
  • Migration status for r-cran-proc/riscv64 (1.18.5-1 to 1.18.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-prodlim/riscv64 (2023.08.28-1 to 2023.08.28-1)
  • Migration status for r-cran-prodlim/riscv64 (2023.08.28-1 to 2023.08.28-1): Will attempt migration (Any information below is purely informational)
• r-cran-profvis/riscv64 (0.3.8+dfsg-1 to 0.3.8+dfsg-1)
  • Migration status for r-cran-profvis/riscv64 (0.3.8+dfsg-1 to 0.3.8+dfsg-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-propclust/riscv64 (1.4-7-1 to 1.4-7-1)
  • Migration status for r-cran-propclust/riscv64 (1.4-7-1 to 1.4-7-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-proxy/riscv64 (0.4-27-1 to 0.4-27-1)
  • Migration status for r-cran-proxy/riscv64 (0.4-27-1 to 0.4-27-1): Will attempt migration (Any information below is purely informational)
• r-cran-ps/riscv64 (1.7.6-1 to 1.7.6-1)
  • Migration status for r-cran-ps/riscv64 (1.7.6-1 to 1.7.6-1): Will attempt migration (Any information below is purely informational)
• r-cran-pscl/riscv64 (1.5.9-1 to 1.5.9-1)
  • Migration status for r-cran-pscl/riscv64 (1.5.9-1 to 1.5.9-1): Will attempt migration (Any information below is purely informational)
• r-cran-psychotools/riscv64 (0.7-3-1 to 0.7-3-1)
  • Migration status for r-cran-psychotools/riscv64 (0.7-3-1 to 0.7-3-1): Will attempt migration (Any information below is purely informational)
• r-cran-purrr/riscv64 (1.0.2-1 to 1.0.2-1)
  • Migration status for r-cran-purrr/riscv64 (1.0.2-1 to 1.0.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-purrrlyr/riscv64 (0.0.8-1 to 0.0.8-1)
  • Migration status for r-cran-purrrlyr/riscv64 (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
• r-cran-qap/riscv64 (0.1-2-1 to 0.1-2-1)
  • Migration status for r-cran-qap/riscv64 (0.1-2-1 to 0.1-2-1): 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-qqconf/riscv64 (1.3.2+dfsg-1 to 1.3.2+dfsg-1)
  • Migration status for r-cran-qqconf/riscv64 (1.3.2+dfsg-1 to 1.3.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-qtl/riscv64 (1.66-1 to 1.66-1)
  • Migration status for r-cran-qtl/riscv64 (1.66-1 to 1.66-1): Will attempt migration (Any information below is purely informational)
• r-cran-quickjsr/riscv64 (1.1.3-1 to 1.1.3-1)
  • Migration status for r-cran-quickjsr/riscv64 (1.1.3-1 to 1.1.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-randomforest/riscv64 (4.7-1.1-1 to 4.7-1.1-1)
  • Migration status for r-cran-randomforest/riscv64 (4.7-1.1-1 to 4.7-1.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-ranger/riscv64 (0.16.0-1 to 0.16.0-1)
  • Migration status for r-cran-ranger/riscv64 (0.16.0-1 to 0.16.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-rann/riscv64 (2.6.1-1 to 2.6.1-1)
  • Migration status for r-cran-rann/riscv64 (2.6.1-1 to 2.6.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-rappdirs/riscv64 (0.3.3-1 to 0.3.3-1)
  • Migration status for r-cran-rappdirs/riscv64 (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-raschsampler/riscv64 (0.8-10-1 to 0.8-10-1)
  • Migration status for r-cran-raschsampler/riscv64 (0.8-10-1 to 0.8-10-1): 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-rbibutils/riscv64 (2.2.16-1 to 2.2.16-1)
  • Migration status for r-cran-rbibutils/riscv64 (2.2.16-1 to 2.2.16-1): Will attempt migration (Any information below is purely informational)
• r-cran-rcppannoy/riscv64 (0.0.22-1 to 0.0.22-1)
  • Migration status for r-cran-rcppannoy/riscv64 (0.0.22-1 to 0.0.22-1): Will attempt migration (Any information below is purely informational)
• r-cran-rcppcctz/riscv64 (0.2.12-1 to 0.2.12-1)
  • Migration status for r-cran-rcppcctz/riscv64 (0.2.12-1 to 0.2.12-1): Will attempt migration (Any information below is purely informational)
• r-cran-rcppdist/riscv64 (0.1.1-2 to 0.1.1-2)
  • Migration status for r-cran-rcppdist/riscv64 (0.1.1-2 to 0.1.1-2): Will attempt migration (Any information below is purely informational)
• r-cran-rcppeigen/riscv64 (0.3.4.0.0-1 to 0.3.4.0.0-1)
  • Migration status for r-cran-rcppeigen/riscv64 (0.3.4.0.0-1 to 0.3.4.0.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-rcppgsl/riscv64 (0.3.13-1 to 0.3.13-1)
  • Migration status for r-cran-rcppgsl/riscv64 (0.3.13-1 to 0.3.13-1): Will attempt migration (Any information below is purely informational)
• r-cran-rcpphnsw/riscv64 (0.5.0+ds-1 to 0.5.0+ds-1)
  • Migration status for r-cran-rcpphnsw/riscv64 (0.5.0+ds-1 to 0.5.0+ds-1): Will attempt migration (Any information below is purely informational)
• r-cran-rcppml/riscv64 (0.3.7-2 to 0.3.7-2)
  • Migration status for r-cran-rcppml/riscv64 (0.3.7-2 to 0.3.7-2): Will attempt migration (Any information below is purely informational)
• r-cran-rcppmlpack/riscv64 (1.0.10-7-2 to 1.0.10-7-2)
  • Migration status for r-cran-rcppmlpack/riscv64 (1.0.10-7-2 to 1.0.10-7-2): Will attempt migration (Any information below is purely informational)
• r-cran-rcppparallel/amd64 (5.1.7+dfsg-5 to 5.1.7+dfsg-5)
  • Migration status for r-cran-rcppparallel/amd64 (5.1.7+dfsg-5 to 5.1.7+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: r-cran-rcppparallel/amd64 onetbb (not considered)
    • Invalidated by dependency
• r-cran-rcppparallel/arm64 (5.1.7+dfsg-5 to 5.1.7+dfsg-5)
  • Migration status for r-cran-rcppparallel/arm64 (5.1.7+dfsg-5 to 5.1.7+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: r-cran-rcppparallel/arm64 onetbb (not considered)
    • Invalidated by dependency
• r-cran-rcppparallel/armel (5.1.7+dfsg-5 to 5.1.7+dfsg-5)
  • Migration status for r-cran-rcppparallel/armel (5.1.7+dfsg-5 to 5.1.7+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: r-cran-rcppparallel/armel onetbb (not considered)
    • Invalidated by dependency
• r-cran-rcppparallel/armhf (5.1.7+dfsg-5 to 5.1.7+dfsg-5)
  • Migration status for r-cran-rcppparallel/armhf (5.1.7+dfsg-5 to 5.1.7+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: r-cran-rcppparallel/armhf onetbb (not considered)
    • Invalidated by dependency
• r-cran-rcppparallel/i386 (5.1.7+dfsg-5 to 5.1.7+dfsg-5)
  • Migration status for r-cran-rcppparallel/i386 (5.1.7+dfsg-5 to 5.1.7+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: r-cran-rcppparallel/i386 onetbb (not considered)
    • Invalidated by dependency
• r-cran-rcppparallel/mips64el (5.1.7+dfsg-5 to 5.1.7+dfsg-5)
  • Migration status for r-cran-rcppparallel/mips64el (5.1.7+dfsg-5 to 5.1.7+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: r-cran-rcppparallel/mips64el onetbb (not considered)
    • Invalidated by dependency
• r-cran-rcppparallel/ppc64el (5.1.7+dfsg-5 to 5.1.7+dfsg-5)
  • Migration status for r-cran-rcppparallel/ppc64el (5.1.7+dfsg-5 to 5.1.7+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: r-cran-rcppparallel/ppc64el onetbb (not considered)
    • Invalidated by dependency
• r-cran-rcppparallel/s390x (5.1.7+dfsg-5 to 5.1.7+dfsg-5)
  • Migration status for r-cran-rcppparallel/s390x (5.1.7+dfsg-5 to 5.1.7+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: r-cran-rcppparallel/s390x onetbb (not considered)
    • Invalidated by dependency
• r-cran-rcpproll/riscv64 (0.3.0-2 to 0.3.0-2)
  • Migration status for r-cran-rcpproll/riscv64 (0.3.0-2 to 0.3.0-2): Will attempt migration (Any information below is purely informational)
• r-cran-rcppspdlog/riscv64 (0.0.17-1 to 0.0.17-1)
  • Migration status for r-cran-rcppspdlog/riscv64 (0.0.17-1 to 0.0.17-1): Will attempt migration (Any information below is purely informational)
• r-cran-rcpptoml/riscv64 (0.2.2+dfsg-1 to 0.2.2+dfsg-1)
  • Migration status for r-cran-rcpptoml/riscv64 (0.2.2+dfsg-1 to 0.2.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-rcsdp/riscv64 (0.1.57.5-1 to 0.1.57.5-1)
  • Migration status for r-cran-rcsdp/riscv64 (0.1.57.5-1 to 0.1.57.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-rcurl/riscv64 (1.98-1.14+dfsg-1 to 1.98-1.14+dfsg-1)
  • Migration status for r-cran-rcurl/riscv64 (1.98-1.14+dfsg-1 to 1.98-1.14+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-readr/riscv64 (2.1.5-1 to 2.1.5-1)
  • Migration status for r-cran-readr/riscv64 (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-readstata13/riscv64 (0.10.1-1 to 0.10.1-1)
  • Migration status for r-cran-readstata13/riscv64 (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-readxl/riscv64 (1.4.3-1 to 1.4.3-1)
  • Migration status for r-cran-readxl/riscv64 (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-regsem/riscv64 (1.9.5+dfsg-1 to 1.9.5+dfsg-1)
  • Migration status for r-cran-regsem/riscv64 (1.9.5+dfsg-1 to 1.9.5+dfsg-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-reshape2/riscv64 (1.4.4-2 to 1.4.4-2)
  • Migration status for r-cran-reshape2/riscv64 (1.4.4-2 to 1.4.4-2): Will attempt migration (Any information below is purely informational)
• r-cran-reticulate/riscv64 (1.35.0+dfsg-1 to 1.35.0+dfsg-1)
  • Migration status for r-cran-reticulate/riscv64 (1.35.0+dfsg-1 to 1.35.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-rgenoud/riscv64 (5.9-0.10-1 to 5.9-0.10-1)
  • Migration status for r-cran-rgenoud/riscv64 (5.9-0.10-1 to 5.9-0.10-1): Will attempt migration (Any information below is purely informational)
• r-cran-rhpcblasctl/riscv64 (0.23-42-1 to 0.23-42-1)
  • Migration status for r-cran-rhpcblasctl/riscv64 (0.23-42-1 to 0.23-42-1): Will attempt migration (Any information below is purely informational)
• r-cran-rinside/riscv64 (0.2.18-1 to 0.2.18-1)
  • Migration status for r-cran-rinside/riscv64 (0.2.18-1 to 0.2.18-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-rjags/riscv64 (1:4-15-1 to 1:4-15-1)
  • Migration status for r-cran-rjags/riscv64 (1:4-15-1 to 1:4-15-1): Will attempt migration (Any information below is purely informational)
• r-cran-rjson/riscv64 (0.2.21-1 to 0.2.21-1)
  • Migration status for r-cran-rjson/riscv64 (0.2.21-1 to 0.2.21-1): Will attempt migration (Any information below is purely informational)
• r-cran-rle/riscv64 (0.9.2-2 to 0.9.2-2)
  • Migration status for r-cran-rle/riscv64 (0.9.2-2 to 0.9.2-2): Will attempt migration (Any information below is purely informational)
• r-cran-rlinsolve/riscv64 (0.3.2-1 to 0.3.2-1)
  • Migration status for r-cran-rlinsolve/riscv64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-rlrsim/riscv64 (3.1-8-1 to 3.1-8-1)
  • Migration status for r-cran-rlrsim/riscv64 (3.1-8-1 to 3.1-8-1): Will attempt migration (Any information below is purely informational)
• r-cran-rmpfr/riscv64 (0.9-5-1 to 0.9-5-1)
  • Migration status for r-cran-rmpfr/riscv64 (0.9-5-1 to 0.9-5-1): Will attempt migration (Any information below is purely informational)
• r-cran-rmutil/riscv64 (1.1.10-1 to 1.1.10-1)
  • Migration status for r-cran-rmutil/riscv64 (1.1.10-1 to 1.1.10-1): Will attempt migration (Any information below is purely informational)
• r-cran-rncl/riscv64 (0.8.7-1 to 0.8.7-1)
  • Migration status for r-cran-rncl/riscv64 (0.8.7-1 to 0.8.7-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-rook/riscv64 (1.2+dfsg-1 to 1.2+dfsg-1)
  • Migration status for r-cran-rook/riscv64 (1.2+dfsg-1 to 1.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-roxygen2/riscv64 (7.3.1-1 to 7.3.1-1)
  • Migration status for r-cran-roxygen2/riscv64 (7.3.1-1 to 7.3.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-rpf/riscv64 (1.0.14+dfsg-1 to 1.0.14+dfsg-1)
  • Migration status for r-cran-rpf/riscv64 (1.0.14+dfsg-1 to 1.0.14+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-rpostgresql/riscv64 (0.7-6+dfsg-1 to 0.7-6+dfsg-1)
  • Migration status for r-cran-rpostgresql/riscv64 (0.7-6+dfsg-1 to 0.7-6+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-rprotobuf/riscv64 (0.4.22-1 to 0.4.22-1)
  • Migration status for r-cran-rprotobuf/riscv64 (0.4.22-1 to 0.4.22-1): Will attempt migration (Any information below is purely informational)
• r-cran-rrcov/riscv64 (1.7-5-1 to 1.7-5-1)
  • Migration status for r-cran-rrcov/riscv64 (1.7-5-1 to 1.7-5-1): Will attempt migration (Any information below is purely informational)
• r-cran-rsclient/riscv64 (0.7-10-1 to 0.7-10-1)
  • Migration status for r-cran-rsclient/riscv64 (0.7-10-1 to 0.7-10-1): Will attempt migration (Any information below is purely informational)
• r-cran-rspectra/riscv64 (0.16-1-1 to 0.16-1-1)
  • Migration status for r-cran-rspectra/riscv64 (0.16-1-1 to 0.16-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-rtdists/riscv64 (0.11-5-1 to 0.11-5-1)
  • Migration status for r-cran-rtdists/riscv64 (0.11-5-1 to 0.11-5-1): Will attempt migration (Any information below is purely informational)
• r-cran-rtsne/riscv64 (0.17-1 to 0.17-1)
  • Migration status for r-cran-rtsne/riscv64 (0.17-1 to 0.17-1): Will attempt migration (Any information below is purely informational)
• r-cran-rwave/riscv64 (2.6-5-1 to 2.6-5-1)
  • Migration status for r-cran-rwave/riscv64 (2.6-5-1 to 2.6-5-1): Will attempt migration (Any information below is purely informational)
• r-cran-rwiener/riscv64 (1.3-3-1 to 1.3-3-1)
  • Migration status for r-cran-rwiener/riscv64 (1.3-3-1 to 1.3-3-1): Will attempt migration (Any information below is purely informational)
• r-cran-s2/riscv64 (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-s2/riscv64 (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• r-cran-sampling/riscv64 (2.10-1 to 2.10-1)
  • Migration status for r-cran-sampling/riscv64 (2.10-1 to 2.10-1): Will attempt migration (Any information below is purely informational)
• r-cran-samr/riscv64 (3.0-2 to 3.0-2)
  • Migration status for r-cran-samr/riscv64 (3.0-2 to 3.0-2): Will attempt migration (Any information below is purely informational)
• r-cran-scattermore/riscv64 (1.2-1 to 1.2-1)
  • Migration status for r-cran-scattermore/riscv64 (1.2-1 to 1.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-sctransform/riscv64 (0.4.1-1 to 0.4.1-1)
  • Migration status for r-cran-sctransform/riscv64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-sdmtools/riscv64 (1.1-221.2-1 to 1.1-221.2-1)
  • Migration status for r-cran-sdmtools/riscv64 (1.1-221.2-1 to 1.1-221.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-sem/riscv64 (3.1.15-2 to 3.1.15-2)
  • Migration status for r-cran-sem/riscv64 (3.1.15-2 to 3.1.15-2): Will attempt migration (Any information below is purely informational)
• r-cran-seqinr/riscv64 (4.2-36-1 to 4.2-36-1)
  • Migration status for r-cran-seqinr/riscv64 (4.2-36-1 to 4.2-36-1): Will attempt migration (Any information below is purely informational)
• r-cran-sets/riscv64 (1.0.25+ds-1 to 1.0.25+ds-1)
  • Migration status for r-cran-sets/riscv64 (1.0.25+ds-1 to 1.0.25+ds-1): Will attempt migration (Any information below is purely informational)
• r-cran-seuratobject/riscv64 (5.0.1-2 to 5.0.1-2)
  • Migration status for r-cran-seuratobject/riscv64 (5.0.1-2 to 5.0.1-2): Will attempt migration (Any information below is purely informational)
• r-cran-sitmo/riscv64 (2.0.2-1 to 2.0.2-1)
  • Migration status for r-cran-sitmo/riscv64 (2.0.2-1 to 2.0.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-slam/riscv64 (0.1-50-1 to 0.1-50-1)
  • Migration status for r-cran-slam/riscv64 (0.1-50-1 to 0.1-50-1): Will attempt migration (Any information below is purely informational)
• r-cran-slider/riscv64 (0.3.1-1 to 0.3.1-1)
  • Migration status for r-cran-slider/riscv64 (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-sna/riscv64 (2.7-2-1 to 2.7-2-1)
  • Migration status for r-cran-sna/riscv64 (2.7-2-1 to 2.7-2-1): Will attempt migration (Any information below is purely informational)
• r-cran-snowballc/riscv64 (0.7.1-1 to 0.7.1-1)
  • Migration status for r-cran-snowballc/riscv64 (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-sodium/riscv64 (1.3.1+dfsg-1 to 1.3.1+dfsg-1)
  • Migration status for r-cran-sodium/riscv64 (1.3.1+dfsg-1 to 1.3.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-sourcetools/riscv64 (0.1.7-1-1 to 0.1.7-1-1)
  • Migration status for r-cran-sourcetools/riscv64 (0.1.7-1-1 to 0.1.7-1-1): Will attempt migration (Any information below is purely informational)
• r-cran-sp/riscv64 (1:2.1-2+dfsg-1 to 1:2.1-2+dfsg-1)
  • Migration status for r-cran-sp/riscv64 (1:2.1-2+dfsg-1 to 1:2.1-2+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-spam/riscv64 (2.10-0-1 to 2.10-0-1)
  • Migration status for r-cran-spam/riscv64 (2.10-0-1 to 2.10-0-1): Will attempt migration (Any information below is purely informational)
• r-cran-sparsesvd/riscv64 (0.2-2-1 to 0.2-2-1)
  • Migration status for r-cran-sparsesvd/riscv64 (0.2-2-1 to 0.2-2-1): Will attempt migration (Any information below is purely informational)
• r-cran-spatial/riscv64 (7.3-17-1 to 7.3-17-1)
  • Migration status for r-cran-spatial/riscv64 (7.3-17-1 to 7.3-17-1): Will attempt migration (Any information below is purely informational)
• r-cran-spatstat.sparse/riscv64 (3.0-3-1 to 3.0-3-1)
  • Migration status for r-cran-spatstat.sparse/riscv64 (3.0-3-1 to 3.0-3-1): Will attempt migration (Any information below is purely informational)
• r-cran-spatstat.utils/riscv64 (3.0-4-1 to 3.0-4-1)
  • Migration status for r-cran-spatstat.utils/riscv64 (3.0-4-1 to 3.0-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-spc/riscv64 (1:0.6.7-1 to 1:0.6.7-1)
  • Migration status for r-cran-spc/riscv64 (1:0.6.7-1 to 1:0.6.7-1): Will attempt migration (Any information below is purely informational)
• r-cran-stable/riscv64 (1.1.6-1 to 1.1.6-1)
  • Migration status for r-cran-stable/riscv64 (1.1.6-1 to 1.1.6-1): Will attempt migration (Any information below is purely informational)
• r-cran-stanheaders/riscv64 (2.32.5-1 to 2.32.5-1)
  • Migration status for r-cran-stanheaders/riscv64 (2.32.5-1 to 2.32.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-statip/riscv64 (0.2.3-2 to 0.2.3-2)
  • Migration status for r-cran-statip/riscv64 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• r-cran-statmod/riscv64 (1.5.0-1 to 1.5.0-1)
  • Migration status for r-cran-statmod/riscv64 (1.5.0-1 to 1.5.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-statnet.common/riscv64 (4.9.0-1 to 4.9.0-1)
  • Migration status for r-cran-statnet.common/riscv64 (4.9.0-1 to 4.9.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-stringdist/riscv64 (0.9.12-1 to 0.9.12-1)
  • Migration status for r-cran-stringdist/riscv64 (0.9.12-1 to 0.9.12-1): Will attempt migration (Any information below is purely informational)
• r-cran-stringi/riscv64 (1.8.3-1 to 1.8.3-1)
  • Migration status for r-cran-stringi/riscv64 (1.8.3-1 to 1.8.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-suppdists/riscv64 (1.1-9.7-1 to 1.1-9.7-1)
  • Migration status for r-cran-suppdists/riscv64 (1.1-9.7-1 to 1.1-9.7-1): Will attempt migration (Any information below is purely informational)
• r-cran-svglite/riscv64 (2.1.3-1 to 2.1.3-1)
  • Migration status for r-cran-svglite/riscv64 (2.1.3-1 to 2.1.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-sys/riscv64 (3.4.2-1 to 3.4.2-1)
  • Migration status for r-cran-sys/riscv64 (3.4.2-1 to 3.4.2-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-tensora/riscv64 (0.36.2.1-1 to 0.36.2.1-1)
  • Migration status for r-cran-tensora/riscv64 (0.36.2.1-1 to 0.36.2.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-textshaping/riscv64 (0.3.7-2 to 0.3.7-2)
  • Migration status for r-cran-textshaping/riscv64 (0.3.7-2 to 0.3.7-2): Will attempt migration (Any information below is purely informational)
• r-cran-tfmpvalue/riscv64 (0.0.9-1 to 0.0.9-1)
  • Migration status for r-cran-tfmpvalue/riscv64 (0.0.9-1 to 0.0.9-1): Will attempt migration (Any information below is purely informational)
• r-cran-tgp/riscv64 (2.4-22-1 to 2.4-22-1)
  • Migration status for r-cran-tgp/riscv64 (2.4-22-1 to 2.4-22-1): Will attempt migration (Any information below is purely informational)
• r-cran-tibble/riscv64 (3.2.1+dfsg-2 to 3.2.1+dfsg-2)
  • Migration status for r-cran-tibble/riscv64 (3.2.1+dfsg-2 to 3.2.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• r-cran-tidygraph/riscv64 (1.3.0-1 to 1.3.0-1)
  • Migration status for r-cran-tidygraph/riscv64 (1.3.0-1 to 1.3.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-tidyr/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for r-cran-tidyr/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-tiff/riscv64 (0.1-12-1 to 0.1-12-1)
  • Migration status for r-cran-tiff/riscv64 (0.1-12-1 to 0.1-12-1): Will attempt migration (Any information below is purely informational)
• r-cran-tikzdevice/riscv64 (0.12.6-1 to 0.12.6-1)
  • Migration status for r-cran-tikzdevice/riscv64 (0.12.6-1 to 0.12.6-1): Will attempt migration (Any information below is purely informational)
• r-cran-timechange/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for r-cran-timechange/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-timedate/riscv64 (4032.109-1 to 4032.109-1)
  • Migration status for r-cran-timedate/riscv64 (4032.109-1 to 4032.109-1): Will attempt migration (Any information below is purely informational)
• r-cran-timereg/riscv64 (2.0.5-1 to 2.0.5-1)
  • Migration status for r-cran-timereg/riscv64 (2.0.5-1 to 2.0.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-tmvnsim/riscv64 (1.0-2-1 to 1.0-2-1)
  • Migration status for r-cran-tmvnsim/riscv64 (1.0-2-1 to 1.0-2-1): Will attempt migration (Any information below is purely informational)
• r-cran-tmvtnorm/riscv64 (1.6-1 to 1.6-1)
  • Migration status for r-cran-tmvtnorm/riscv64 (1.6-1 to 1.6-1): Will attempt migration (Any information below is purely informational)
• r-cran-tokenizers/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for r-cran-tokenizers/riscv64 (0.3.0-1 to 0.3.0-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-triebeard/riscv64 (0.4.1-1 to 0.4.1-1)
  • Migration status for r-cran-triebeard/riscv64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-truncnorm/riscv64 (1.0-9-2 to 1.0-9-2)
  • Migration status for r-cran-truncnorm/riscv64 (1.0-9-2 to 1.0-9-2): Will attempt migration (Any information below is purely informational)
• r-cran-tsp/riscv64 (1.2-4-1 to 1.2-4-1)
  • Migration status for r-cran-tsp/riscv64 (1.2-4-1 to 1.2-4-1): Will attempt migration (Any information below is purely informational)
• r-cran-ttr/riscv64 (0.24.4-1 to 0.24.4-1)
  • Migration status for r-cran-ttr/riscv64 (0.24.4-1 to 0.24.4-1): Will attempt migration (Any information below is purely informational)
• r-cran-tweenr/riscv64 (2.0.3-1 to 2.0.3-1)
  • Migration status for r-cran-tweenr/riscv64 (2.0.3-1 to 2.0.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-tzdb/riscv64 (0.4.0-2 to 0.4.0-2)
  • Migration status for r-cran-tzdb/riscv64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• r-cran-ucminf/riscv64 (1.2.1-1 to 1.2.1-1)
  • Migration status for r-cran-ucminf/riscv64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-udunits2/riscv64 (0.13.2.1-2 to 0.13.2.1-2)
  • Migration status for r-cran-udunits2/riscv64 (0.13.2.1-2 to 0.13.2.1-2): Will attempt migration (Any information below is purely informational)
• r-cran-units/riscv64 (0.8-5+dfsg-1 to 0.8-5+dfsg-1)
  • Migration status for r-cran-units/riscv64 (0.8-5+dfsg-1 to 0.8-5+dfsg-1): Will attempt migration (Any information below is purely informational)
• r-cran-urltools/riscv64 (1.7.3+dfsg-2 to 1.7.3+dfsg-2)
  • Migration status for r-cran-urltools/riscv64 (1.7.3+dfsg-2 to 1.7.3+dfsg-2): Will attempt migration (Any information below is purely informational)
• r-cran-utf8/riscv64 (1.2.4-1 to 1.2.4-1)
  • Migration status for r-cran-utf8/riscv64 (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
• r-cran-uuid/riscv64 (1.2-0-1 to 1.2-0-1)
  • Migration status for r-cran-uuid/riscv64 (1.2-0-1 to 1.2-0-1): Will attempt migration (Any information below is purely informational)
• r-cran-uwot/riscv64 (0.1.16-2 to 0.1.16-2)
  • Migration status for r-cran-uwot/riscv64 (0.1.16-2 to 0.1.16-2): Will attempt migration (Any information below is purely informational)
• r-cran-vctrs/riscv64 (0.6.5-1 to 0.6.5-1)
  • Migration status for r-cran-vctrs/riscv64 (0.6.5-1 to 0.6.5-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-vgam/riscv64 (1.1-9-1 to 1.1-9-1)
  • Migration status for r-cran-vgam/riscv64 (1.1-9-1 to 1.1-9-1): Will attempt migration (Any information below is purely informational)
• r-cran-vroom/riscv64 (1.6.5-1 to 1.6.5-1)
  • Migration status for r-cran-vroom/riscv64 (1.6.5-1 to 1.6.5-1): Will attempt migration (Any information below is purely informational)
• r-cran-warp/riscv64 (0.2.1-1 to 0.2.1-1)
  • Migration status for r-cran-warp/riscv64 (0.2.1-1 to 0.2.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-waveslim/riscv64 (1.8.4-1 to 1.8.4-1)
  • Migration status for r-cran-waveslim/riscv64 (1.8.4-1 to 1.8.4-1): Will attempt migration (Any information below is purely informational)
• r-cran-wavethresh/riscv64 (4.7.2-1 to 4.7.2-1)
  • Migration status for r-cran-wavethresh/riscv64 (4.7.2-1 to 4.7.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-webfakes/riscv64 (1.3.0-1 to 1.3.0-1)
  • Migration status for r-cran-webfakes/riscv64 (1.3.0-1 to 1.3.0-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-webutils/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for r-cran-webutils/riscv64 (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
• r-cran-wk/riscv64 (0.9.1-1 to 0.9.1-1)
  • Migration status for r-cran-wk/riscv64 (0.9.1-1 to 0.9.1-1): Will attempt migration (Any information below is purely informational)
• r-cran-wkutils/riscv64 (0.1.3-1 to 0.1.3-1)
  • Migration status for r-cran-wkutils/riscv64 (0.1.3-1 to 0.1.3-1): Will attempt migration (Any information below is purely informational)
• r-cran-wordcloud/riscv64 (2.6-2 to 2.6-2)
  • Migration status for r-cran-wordcloud/riscv64 (2.6-2 to 2.6-2): Will attempt migration (Any information below is purely informational)
• r-cran-writexl/riscv64 (1.5.0-1 to 1.5.0-1)
  • Migration status for r-cran-writexl/riscv64 (1.5.0-1 to 1.5.0-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)
• r-cran-xts/riscv64 (0.13.2-1 to 0.13.2-1)
  • Migration status for r-cran-xts/riscv64 (0.13.2-1 to 0.13.2-1): Will attempt migration (Any information below is purely informational)
• r-cran-yaml/riscv64 (2.3.8-2 to 2.3.8-2)
  • Migration status for r-cran-yaml/riscv64 (2.3.8-2 to 2.3.8-2): Will attempt migration (Any information below is purely informational)
• r-cran-zip/riscv64 (2.3.1-1 to 2.3.1-1)
  • Migration status for r-cran-zip/riscv64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• r-other-amsmercury/riscv64 (1.3.0-4 to 1.3.0-4)
  • Migration status for r-other-amsmercury/riscv64 (1.3.0-4 to 1.3.0-4): Will attempt migration (Any information below is purely informational)
• r-other-chbutils/riscv64 (0.1+git20171026.a226cee-2 to 0.1+git20171026.a226cee-2)
  • Migration status for r-other-chbutils/riscv64 (0.1+git20171026.a226cee-2 to 0.1+git20171026.a226cee-2): Will attempt migration (Any information below is purely informational)
• r-other-iwrlars/riscv64 (0.9-5-4 to 0.9-5-4)
  • Migration status for r-other-iwrlars/riscv64 (0.9-5-4 to 0.9-5-4): Will attempt migration (Any information below is purely informational)
• r-other-kcha-psiplot/riscv64 (2.3.0-2 to 2.3.0-2)
  • Migration status for r-other-kcha-psiplot/riscv64 (2.3.0-2 to 2.3.0-2): Will attempt migration (Any information below is purely informational)
• r-other-mott-happy/riscv64 (2.4-5 to 2.4-5)
  • Migration status for r-other-mott-happy/riscv64 (2.4-5 to 2.4-5): Will attempt migration (Any information below is purely informational)
• r-other-x4r/riscv64 (1.0.1+git20150806.c6bd9bd-3 to 1.0.1+git20150806.c6bd9bd-3)
  • Migration status for r-other-x4r/riscv64 (1.0.1+git20150806.c6bd9bd-3 to 1.0.1+git20150806.c6bd9bd-3): Will attempt migration (Any information below is purely informational)
• r-zoo/riscv64 (1.8-12-2 to 1.8-12-2)
  • Migration status for r-zoo/riscv64 (1.8-12-2 to 1.8-12-2): Will attempt migration (Any information below is purely informational)
• racon/riscv64 (1.5.0-3 to 1.5.0-3)
  • Migration status for racon/riscv64 (1.5.0-3 to 1.5.0-3): 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)
• rafkill/riscv64 (1.2.2-8 to 1.2.2-8)
  • Migration status for rafkill/riscv64 (1.2.2-8 to 1.2.2-8): Will attempt migration (Any information below is purely informational)
• ragel/riscv64 (6.10-4 to 6.10-4)
  • Migration status for ragel/riscv64 (6.10-4 to 6.10-4): Will attempt migration (Any information below is purely informational)
• ragout/riscv64 (2.3-5 to 2.3-5)
  • Migration status for ragout/riscv64 (2.3-5 to 2.3-5): 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)
• rakarrack/riscv64 (0.6.1-9 to 0.6.1-9)
  • Migration status for rakarrack/riscv64 (0.6.1-9 to 0.6.1-9): Will attempt migration (Any information below is purely informational)
• rampler/riscv64 (2.1.1-1 to 2.1.1-1)
  • Migration status for rampler/riscv64 (2.1.1-1 to 2.1.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)
• raqm/riscv64 (0.10.1-1 to 0.10.1-1)
  • Migration status for raqm/riscv64 (0.10.1-1 to 0.10.1-1): 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)
• raspell/riscv64 (1.3-2 to 1.3-2)
  • Migration status for raspell/riscv64 (1.3-2 to 1.3-2): 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)
• rasterview/riscv64 (1.8-1 to 1.8-1)
  • Migration status for rasterview/riscv64 (1.8-1 to 1.8-1): Will attempt migration (Any information below is purely informational)
• rate4site/riscv64 (3.0.0-8 to 3.0.0-8)
  • Migration status for rate4site/riscv64 (3.0.0-8 to 3.0.0-8): Will attempt migration (Any information below is purely informational)
• ratt/riscv64 (0.0~git20190123.9e77a6d-1 to 0.0~git20190123.9e77a6d-1)
  • Migration status for ratt/riscv64 (0.0~git20190123.9e77a6d-1 to 0.0~git20190123.9e77a6d-1): Will attempt migration (Any information below is purely informational)
• 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)
• 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)
• rbdoom3bfg/riscv64 (1.4.0+dfsg-2 to 1.4.0+dfsg-2)
  • Migration status for rbdoom3bfg/riscv64 (1.4.0+dfsg-2 to 1.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• rclone-browser/riscv64 (1.8.0-4 to 1.8.0-4)
  • Migration status for rclone-browser/riscv64 (1.8.0-4 to 1.8.0-4): Will attempt migration (Any information below is purely informational)
• rcpp/riscv64 (1.0.12-1 to 1.0.12-1)
  • Migration status for rcpp/riscv64 (1.0.12-1 to 1.0.12-1): Will attempt migration (Any information below is purely informational)
• rdfind/riscv64 (1.6.0-1 to 1.6.0-1)
  • Migration status for rdfind/riscv64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
• rdiff-backup/riscv64 (2.2.6-1 to 2.2.6-1)
  • Migration status for rdiff-backup/riscv64 (2.2.6-1 to 2.2.6-1): Will attempt migration (Any information below is purely informational)
• re2c/riscv64 (3.1-1 to 3.1-1)
  • Migration status for re2c/riscv64 (3.1-1 to 3.1-1): Will attempt migration (Any information below is purely informational)
• react/riscv64 (1.2.2-1 to 1.2.2-1)
  • Migration status for react/riscv64 (1.2.2-1 to 1.2.2-1): Will attempt migration (Any information below is purely informational)
• reactivedata/riscv64 (0.3-4 to 0.3-4)
  • Migration status for reactivedata/riscv64 (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
• readseq/riscv64 (1-15 to 1-15)
  • Migration status for readseq/riscv64 (1-15 to 1-15): Will attempt migration (Any information below is purely informational)
• reapr/riscv64 (1.0.18+dfsg-6 to 1.0.18+dfsg-6)
  • Migration status for reapr/riscv64 (1.0.18+dfsg-6 to 1.0.18+dfsg-6): 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)
• recastnavigation/riscv64 (1.5.1+git20210215.e75adf8-1 to 1.5.1+git20210215.e75adf8-1)
  • Migration status for recastnavigation/riscv64 (1.5.1+git20210215.e75adf8-1 to 1.5.1+git20210215.e75adf8-1): 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)
• redis/riscv64 (5:7.0.15-1 to 5:7.0.15-1)
  • Migration status for redis/riscv64 (5:7.0.15-1 to 5:7.0.15-1): Will attempt migration (Any information below is purely informational)
• redisearch/riscv64 (1:1.2.2-4 to 1:1.2.2-4)
  • Migration status for redisearch/riscv64 (1:1.2.2-4 to 1:1.2.2-4): 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)
• regina-rexx/riscv64 (3.9.5+dfsg1-0.1 to 3.9.5+dfsg1-0.1)
  • Migration status for regina-rexx/riscv64 (3.9.5+dfsg1-0.1 to 3.9.5+dfsg1-0.1): 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)
• remake/riscv64 (4.3+dbg-1.6+dfsg-1 to 4.3+dbg-1.6+dfsg-1)
  • Migration status for remake/riscv64 (4.3+dbg-1.6+dfsg-1 to 4.3+dbg-1.6+dfsg-1): Will attempt migration (Any information below is purely informational)
• remctl/riscv64 (3.18-1.1 to 3.18-1.1)
  • Migration status for remctl/riscv64 (3.18-1.1 to 3.18-1.1): 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)
• rep-gtk/riscv64 (1:0.90.8.2-3 to 1:0.90.8.2-3)
  • Migration status for rep-gtk/riscv64 (1:0.90.8.2-3 to 1:0.90.8.2-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)
• repowerd/riscv64 (2023.07-4 to 2023.07-4)
  • Migration status for repowerd/riscv64 (2023.07-4 to 2023.07-4): 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)
• restinio/riscv64 (0.6.19+ds-1 to 0.6.19+ds-1)
  • Migration status for restinio/riscv64 (0.6.19+ds-1 to 0.6.19+ds-1): Will attempt migration (Any information below is purely informational)
• rev-plugins/riscv64 (0.8.1-1 to 0.8.1-1)
  • Migration status for rev-plugins/riscv64 (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• 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)
• rglpk/riscv64 (0.6-5.1-1 to 0.6-5.1-1)
  • Migration status for rglpk/riscv64 (0.6-5.1-1 to 0.6-5.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)
• rhonabwy/riscv64 (1.1.13-2.1 to 1.1.13-2.1)
  • Migration status for rhonabwy/riscv64 (1.1.13-2.1 to 1.1.13-2.1): Will attempt migration (Any information below is purely informational)
• rhvoice/riscv64 (1.8.0+dfsg-3 to 1.8.0+dfsg-3)
  • Migration status for rhvoice/riscv64 (1.8.0+dfsg-3 to 1.8.0+dfsg-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)
• ri-li/riscv64 (3.1.4-1 to 3.1.4-1)
  • Migration status for ri-li/riscv64 (3.1.4-1 to 3.1.4-1): Will attempt migration (Any information below is purely informational)
• riemann-c-client_pu (1.10.4-4 to 1.10.4-2+deb12u1)
  • Migration status for riemann-c-client_pu (1.10.4-4 to 1.10.4-2+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: riemann-c-client is newer in the target suite (1.10.4-4 1.10.4-2+deb12u1)
• rig/riscv64 (1.11-1.1 to 1.11-1.1)
  • Migration status for rig/riscv64 (1.11-1.1 to 1.11-1.1): Will attempt migration (Any information below is purely informational)
• ring/riscv64 (20231201.0~ds1-1 to 20231201.0~ds1-1)
  • Migration status for ring/riscv64 (20231201.0~ds1-1 to 20231201.0~ds1-1): Will attempt migration (Any information below is purely informational)
• ripser/riscv64 (1.2.1-3 to 1.2.1-3)
  • Migration status for ripser/riscv64 (1.2.1-3 to 1.2.1-3): 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)
• rlottie-qml/riscv64 (0.1~git20210503.f950688-1 to 0.1~git20210503.f950688-1)
  • Migration status for rlottie-qml/riscv64 (0.1~git20210503.f950688-1 to 0.1~git20210503.f950688-1): Will attempt migration (Any information below is purely informational)
• rlottie/riscv64 (0.1+dfsg-4 to 0.1+dfsg-4)
  • Migration status for rlottie/riscv64 (0.1+dfsg-4 to 0.1+dfsg-4): 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)
• rmysql/riscv64 (0.10.27-1 to 0.10.27-1)
  • Migration status for rmysql/riscv64 (0.10.27-1 to 0.10.27-1): Will attempt migration (Any information below is purely informational)
• rnahybrid/riscv64 (2.1.2-8 to 2.1.2-8)
  • Migration status for rnahybrid/riscv64 (2.1.2-8 to 2.1.2-8): 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)
• robot-testing-framework/riscv64 (2.0.1+ds1-3 to 2.0.1+ds1-3)
  • Migration status for robot-testing-framework/riscv64 (2.0.1+ds1-3 to 2.0.1+ds1-3): Will attempt migration (Any information below is purely informational)
• rockdodger/riscv64 (1.1.4-3 to 1.1.4-3)
  • Migration status for rockdodger/riscv64 (1.1.4-3 to 1.1.4-3): Will attempt migration (Any information below is purely informational)
• rocketcea/riscv64 (1.1.34+dfsg-2 to 1.1.34+dfsg-2)
  • Migration status for rocketcea/riscv64 (1.1.34+dfsg-2 to 1.1.34+dfsg-2): Will attempt migration (Any information below is purely informational)
• rocksndiamonds/riscv64 (4.3.8.2+dfsg-1 to 4.3.8.2+dfsg-1)
  • Migration status for rocksndiamonds/riscv64 (4.3.8.2+dfsg-1 to 4.3.8.2+dfsg-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)
• rocm-smi-lib/riscv64 (5.7.0-1 to 5.7.0-1)
  • Migration status for rocm-smi-lib/riscv64 (5.7.0-1 to 5.7.0-1): Will attempt migration (Any information below is purely informational)
• rocminfo/riscv64 (5.7.1-3 to 5.7.1-3)
  • Migration status for rocminfo/riscv64 (5.7.1-3 to 5.7.1-3): Will attempt migration (Any information below is purely informational)
• rocr-runtime/riscv64 (5.7.1-2 to 5.7.1-2)
  • Migration status for rocr-runtime/riscv64 (5.7.1-2 to 5.7.1-2): 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)
• rodbc/riscv64 (1.3-23-1 to 1.3-23-1)
  • Migration status for rodbc/riscv64 (1.3-23-1 to 1.3-23-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-actionlib/riscv64 (1.14.0-7 to 1.14.0-7)
  • Migration status for ros-actionlib/riscv64 (1.14.0-7 to 1.14.0-7): Will attempt migration (Any information below is purely informational)
• ros-bond-core/riscv64 (1.8.6-10 to 1.8.6-10)
  • Migration status for ros-bond-core/riscv64 (1.8.6-10 to 1.8.6-10): Will attempt migration (Any information below is purely informational)
• ros-class-loader/riscv64 (2.8.0-1 to 2.8.0-1)
  • Migration status for ros-class-loader/riscv64 (2.8.0-1 to 2.8.0-1): Will attempt migration (Any information below is purely informational)
• ros-collada-urdf/riscv64 (1.12.13-8 to 1.12.13-8)
  • Migration status for ros-collada-urdf/riscv64 (1.12.13-8 to 1.12.13-8): Will attempt migration (Any information below is purely informational)
• ros-common-msgs/riscv64 (1.13.1-2 to 1.13.1-2)
  • Migration status for ros-common-msgs/riscv64 (1.13.1-2 to 1.13.1-2): 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-dynamic-reconfigure/riscv64 (1.7.3-1 to 1.7.3-1)
  • Migration status for ros-dynamic-reconfigure/riscv64 (1.7.3-1 to 1.7.3-1): Will attempt migration (Any information below is purely informational)
• ros-geometry/riscv64 (1.13.2-10 to 1.13.2-10)
  • Migration status for ros-geometry/riscv64 (1.13.2-10 to 1.13.2-10): Will attempt migration (Any information below is purely informational)
• ros-geometry2/riscv64 (0.7.7-1 to 0.7.7-1)
  • Migration status for ros-geometry2/riscv64 (0.7.7-1 to 0.7.7-1): 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-interactive-markers/riscv64 (1.12.0-9 to 1.12.0-9)
  • Migration status for ros-interactive-markers/riscv64 (1.12.0-9 to 1.12.0-9): 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-message-runtime/riscv64 (0.4.13-5 to 0.4.13-5)
  • Migration status for ros-message-runtime/riscv64 (0.4.13-5 to 0.4.13-5): Will attempt migration (Any information below is purely informational)
• ros-navigation-msgs/riscv64 (1.14.1-3 to 1.14.1-3)
  • Migration status for ros-navigation-msgs/riscv64 (1.14.1-3 to 1.14.1-3): 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-pcl-msgs/riscv64 (0.3.0-3 to 0.3.0-3)
  • Migration status for ros-pcl-msgs/riscv64 (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
• ros-random-numbers/riscv64 (0.3.2-5 to 0.3.2-5)
  • Migration status for ros-random-numbers/riscv64 (0.3.2-5 to 0.3.2-5): Will attempt migration (Any information below is purely informational)
• ros-resource-retriever/riscv64 (1.12.7-4 to 1.12.7-4)
  • Migration status for ros-resource-retriever/riscv64 (1.12.7-4 to 1.12.7-4): 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-ros-comm-msgs/riscv64 (1.11.3-3 to 1.11.3-3)
  • Migration status for ros-ros-comm-msgs/riscv64 (1.11.3-3 to 1.11.3-3): Will attempt migration (Any information below is purely informational)
• ros-ros/riscv64 (1.15.8-5 to 1.15.8-5)
  • Migration status for ros-ros/riscv64 (1.15.8-5 to 1.15.8-5): Will attempt migration (Any information below is purely informational)
• ros-rosconsole-bridge/riscv64 (0.5.4-4 to 0.5.4-4)
  • Migration status for ros-rosconsole-bridge/riscv64 (0.5.4-4 to 0.5.4-4): Will attempt migration (Any information below is purely informational)
• ros-rosconsole/riscv64 (1.14.3-12 to 1.14.3-12)
  • Migration status for ros-rosconsole/riscv64 (1.14.3-12 to 1.14.3-12): Will attempt migration (Any information below is purely informational)
• ros-roscpp-core/riscv64 (0.7.3-1 to 0.7.3-1)
  • Migration status for ros-roscpp-core/riscv64 (0.7.3-1 to 0.7.3-1): Will attempt migration (Any information below is purely informational)
• ros-rospack/riscv64 (2.6.2-8 to 2.6.2-8)
  • Migration status for ros-rospack/riscv64 (2.6.2-8 to 2.6.2-8): Will attempt migration (Any information below is purely informational)
• ros-std-msgs/riscv64 (0.5.13-3 to 0.5.13-3)
  • Migration status for ros-std-msgs/riscv64 (0.5.13-3 to 0.5.13-3): 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)
• ros2-ament-index/riscv64 (1.9.0-1 to 1.9.0-1)
  • Migration status for ros2-ament-index/riscv64 (1.9.0-1 to 1.9.0-1): Will attempt migration (Any information below is purely informational)
• ros2-rcpputils/riscv64 (2.12.0-1 to 2.12.0-1)
  • Migration status for ros2-rcpputils/riscv64 (2.12.0-1 to 2.12.0-1): Will attempt migration (Any information below is purely informational)
• rott/riscv64 (20230810-1 to 20230810-1)
  • Migration status for rott/riscv64 (20230810-1 to 20230810-1): Will attempt migration (Any information below is purely informational)
• rpart/riscv64 (4.1.23-1 to 4.1.23-1)
  • Migration status for rpart/riscv64 (4.1.23-1 to 4.1.23-1): Will attempt migration (Any information below is purely informational)
• rpds-py/riscv64 (0.12.0-3 to 0.12.0-3)
  • Migration status for rpds-py/riscv64 (0.12.0-3 to 0.12.0-3): Will attempt migration (Any information below is purely informational)
• rpm/riscv64 (4.19.1.1+dfsg-1 to 4.19.1.1+dfsg-1)
  • Migration status for rpm/riscv64 (4.19.1.1+dfsg-1 to 4.19.1.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• rquantlib/riscv64 (0.4.22-1 to 0.4.22-1)
  • Migration status for rquantlib/riscv64 (0.4.22-1 to 0.4.22-1): 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)
• rsakeyfind/riscv64 (1:1.0-8 to 1:1.0-8)
  • Migration status for rsakeyfind/riscv64 (1:1.0-8 to 1:1.0-8): Will attempt migration (Any information below is purely informational)
• rsbackup/riscv64 (8.0-1 to 8.0-1)
  • Migration status for rsbackup/riscv64 (8.0-1 to 8.0-1): Will attempt migration (Any information below is purely informational)
• rsem/riscv64 (1.3.3+dfsg-3 to 1.3.3+dfsg-3)
  • Migration status for rsem/riscv64 (1.3.3+dfsg-3 to 1.3.3+dfsg-3): Will attempt migration (Any information below is purely informational)
• rserve/riscv64 (1.8-13-2 to 1.8-13-2)
  • Migration status for rserve/riscv64 (1.8-13-2 to 1.8-13-2): 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)
• rsskit/riscv64 (0.4-1 to 0.4-1)
  • Migration status for rsskit/riscv64 (0.4-1 to 0.4-1): Will attempt migration (Any information below is purely informational)
• rstcheck/amd64 (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2)
  • Migration status for rstcheck/amd64 (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstcheck/arm64 (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2)
  • Migration status for rstcheck/arm64 (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstcheck/armel (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2)
  • Migration status for rstcheck/armel (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstcheck/armhf (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2)
  • Migration status for rstcheck/armhf (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstcheck/i386 (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2)
  • Migration status for rstcheck/i386 (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstcheck/mips64el (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2)
  • Migration status for rstcheck/mips64el (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstcheck/ppc64el (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2)
  • Migration status for rstcheck/ppc64el (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstcheck/riscv64 (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2)
  • Migration status for rstcheck/riscv64 (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstcheck/s390x (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2)
  • Migration status for rstcheck/s390x (6.1.2+~1.0.3-2 to 6.1.2+~1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rsymphony/riscv64 (0.1-33-1 to 0.1-33-1)
  • Migration status for rsymphony/riscv64 (0.1-33-1 to 0.1-33-1): Will attempt migration (Any information below is purely informational)
• rsyncrypto/riscv64 (1.14-1.2 to 1.14-1.2)
  • Migration status for rsyncrypto/riscv64 (1.14-1.2 to 1.14-1.2): 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)
• rtl-433/riscv64 (23.11-1 to 23.11-1)
  • Migration status for rtl-433/riscv64 (23.11-1 to 23.11-1): Will attempt migration (Any information below is purely informational)
• rttr/riscv64 (0.9.6+dfsg1-6.1 to 0.9.6+dfsg1-6.1)
  • Migration status for rttr/riscv64 (0.9.6+dfsg1-6.1 to 0.9.6+dfsg1-6.1): Will attempt migration (Any information below is purely informational)
• rubberband/riscv64 (3.3.0+dfsg-2 to 3.3.0+dfsg-2)
  • Migration status for rubberband/riscv64 (3.3.0+dfsg-2 to 3.3.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• ruby-aliyun-sdk/riscv64 (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-aliyun-sdk/riscv64 (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-atomic/riscv64 (1.1.16-3 to 1.1.16-3)
  • Migration status for ruby-atomic/riscv64 (1.1.16-3 to 1.1.16-3): Will attempt migration (Any information below is purely informational)
• ruby-augeas/riscv64 (1:0.5.0+gem-1 to 1:0.5.0+gem-1)
  • Migration status for ruby-augeas/riscv64 (1:0.5.0+gem-1 to 1:0.5.0+gem-1): Will attempt migration (Any information below is purely informational)
• ruby-bcrypt/riscv64 (3.1.18-1 to 3.1.18-1)
  • Migration status for ruby-bcrypt/riscv64 (3.1.18-1 to 3.1.18-1): Will attempt migration (Any information below is purely informational)
• ruby-bert/riscv64 (1.1.6-3 to 1.1.6-3)
  • Migration status for ruby-bert/riscv64 (1.1.6-3 to 1.1.6-3): Will attempt migration (Any information below is purely informational)
• ruby-bindex/riscv64 (0.8.1+ds-1 to 0.8.1+ds-1)
  • Migration status for ruby-bindex/riscv64 (0.8.1+ds-1 to 0.8.1+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-binding-ninja/riscv64 (0.2.3-2 to 0.2.3-2)
  • Migration status for ruby-binding-ninja/riscv64 (0.2.3-2 to 0.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-bson/riscv64 (4.15.0-1 to 4.15.0-1)
  • Migration status for ruby-bson/riscv64 (4.15.0-1 to 4.15.0-1): Will attempt migration (Any information below is purely informational)
• ruby-byebug/riscv64 (11.1.3-4 to 11.1.3-4)
  • Migration status for ruby-byebug/riscv64 (11.1.3-4 to 11.1.3-4): Will attempt migration (Any information below is purely informational)
• ruby-cairo/riscv64 (1.17.12-1 to 1.17.12-1)
  • Migration status for ruby-cairo/riscv64 (1.17.12-1 to 1.17.12-1): Will attempt migration (Any information below is purely informational)
• ruby-cbor/riscv64 (0.5.9.6-2 to 0.5.9.6-2)
  • Migration status for ruby-cbor/riscv64 (0.5.9.6-2 to 0.5.9.6-2): Will attempt migration (Any information below is purely informational)
• ruby-character-set/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for ruby-character-set/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• ruby-charlock-holmes/riscv64 (0.7.7-3 to 0.7.7-3)
  • Migration status for ruby-charlock-holmes/riscv64 (0.7.7-3 to 0.7.7-3): Will attempt migration (Any information below is purely informational)
• ruby-commonmarker/riscv64 (0.23.10-1 to 0.23.10-1)
  • Migration status for ruby-commonmarker/riscv64 (0.23.10-1 to 0.23.10-1): Will attempt migration (Any information below is purely informational)
• ruby-concurrent/riscv64 (1.2.3-2 to 1.2.3-2)
  • Migration status for ruby-concurrent/riscv64 (1.2.3-2 to 1.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-cool.io/riscv64 (1.7.1-1 to 1.7.1-1)
  • Migration status for ruby-cool.io/riscv64 (1.7.1-1 to 1.7.1-1): Will attempt migration (Any information below is purely informational)
• ruby-curb/riscv64 (1.0.5-1 to 1.0.5-1)
  • Migration status for ruby-curb/riscv64 (1.0.5-1 to 1.0.5-1): Will attempt migration (Any information below is purely informational)
• ruby-curses/riscv64 (1.4.4-1 to 1.4.4-1)
  • Migration status for ruby-curses/riscv64 (1.4.4-1 to 1.4.4-1): Will attempt migration (Any information below is purely informational)
• ruby-damerau-levenshtein/riscv64 (1.3.3+dfsg-1 to 1.3.3+dfsg-1)
  • Migration status for ruby-damerau-levenshtein/riscv64 (1.3.3+dfsg-1 to 1.3.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-dataobjects-mysql/riscv64 (0.10.17-4 to 0.10.17-4)
  • Migration status for ruby-dataobjects-mysql/riscv64 (0.10.17-4 to 0.10.17-4): Will attempt migration (Any information below is purely informational)
• ruby-dataobjects-postgres/riscv64 (0.10.17-1 to 0.10.17-1)
  • Migration status for ruby-dataobjects-postgres/riscv64 (0.10.17-1 to 0.10.17-1): Will attempt migration (Any information below is purely informational)
• ruby-dataobjects-sqlite3/riscv64 (0.10.17-1 to 0.10.17-1)
  • Migration status for ruby-dataobjects-sqlite3/riscv64 (0.10.17-1 to 0.10.17-1): Will attempt migration (Any information below is purely informational)
• ruby-dbm/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-dbm/riscv64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-debian/riscv64 (0.3.10 to 0.3.10)
  • Migration status for ruby-debian/riscv64 (0.3.10 to 0.3.10): Will attempt migration (Any information below is purely informational)
• ruby-debug-inspector/riscv64 (1.1.0+gh-1 to 1.1.0+gh-1)
  • Migration status for ruby-debug-inspector/riscv64 (1.1.0+gh-1 to 1.1.0+gh-1): Will attempt migration (Any information below is purely informational)
• ruby-defaults/riscv64 (1:3.1+nmu1 to 1:3.1+nmu1)
  • Migration status for ruby-defaults/riscv64 (1:3.1+nmu1 to 1:3.1+nmu1): Will attempt migration (Any information below is purely informational)
• ruby-eb/riscv64 (2.6-4 to 2.6-4)
  • Migration status for ruby-eb/riscv64 (2.6-4 to 2.6-4): Will attempt migration (Any information below is purely informational)
• ruby-ed25519/riscv64 (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for ruby-ed25519/riscv64 (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-enumerable-statistics/riscv64 (2.0.7+dfsg-3 to 2.0.7+dfsg-3)
  • Migration status for ruby-enumerable-statistics/riscv64 (2.0.7+dfsg-3 to 2.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• ruby-escape-utils/riscv64 (1.2.1-4 to 1.2.1-4)
  • Migration status for ruby-escape-utils/riscv64 (1.2.1-4 to 1.2.1-4): Will attempt migration (Any information below is purely informational)
• ruby-eventmachine/riscv64 (1.3~pre20220315-df4ab006-3 to 1.3~pre20220315-df4ab006-3)
  • Migration status for ruby-eventmachine/riscv64 (1.3~pre20220315-df4ab006-3 to 1.3~pre20220315-df4ab006-3): Will attempt migration (Any information below is purely informational)
• ruby-exif/riscv64 (0.1.2-22 to 0.1.2-22)
  • Migration status for ruby-exif/riscv64 (0.1.2-22 to 0.1.2-22): Will attempt migration (Any information below is purely informational)
• ruby-fast-blank/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for ruby-fast-blank/riscv64 (1.0.1-1 to 1.0.1-1): Will attempt migration (Any information below is purely informational)
• ruby-fast-stemmer/riscv64 (1.0.2-4 to 1.0.2-4)
  • Migration status for ruby-fast-stemmer/riscv64 (1.0.2-4 to 1.0.2-4): Will attempt migration (Any information below is purely informational)
• ruby-fast-xs/riscv64 (0.8.0-3 to 0.8.0-3)
  • Migration status for ruby-fast-xs/riscv64 (0.8.0-3 to 0.8.0-3): Will attempt migration (Any information below is purely informational)
• ruby-ffi-yajl/riscv64 (2.3.1-3 to 2.3.1-3)
  • Migration status for ruby-ffi-yajl/riscv64 (2.3.1-3 to 2.3.1-3): Will attempt migration (Any information below is purely informational)
• ruby-fftw3/riscv64 (1.0.2-3 to 1.0.2-3)
  • Migration status for ruby-fftw3/riscv64 (1.0.2-3 to 1.0.2-3): Will attempt migration (Any information below is purely informational)
• ruby-fusefs/riscv64 (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/riscv64 (0.7.0-6 to 0.7.0-6): Will attempt migration (Any information below is purely informational)
• ruby-gd/riscv64 (0.8.0-8 to 0.8.0-8)
  • Migration status for ruby-gd/riscv64 (0.8.0-8 to 0.8.0-8): Will attempt migration (Any information below is purely informational)
• ruby-github-linguist/riscv64 (7.27.0-1 to 7.27.0-1)
  • Migration status for ruby-github-linguist/riscv64 (7.27.0-1 to 7.27.0-1): Will attempt migration (Any information below is purely informational)
• ruby-github-markdown/riscv64 (0.6.9-5 to 0.6.9-5)
  • Migration status for ruby-github-markdown/riscv64 (0.6.9-5 to 0.6.9-5): Will attempt migration (Any information below is purely informational)
• ruby-gnome/riscv64 (3.5.1-1 to 3.5.1-1)
  • Migration status for ruby-gnome/riscv64 (3.5.1-1 to 3.5.1-1): Will attempt migration (Any information below is purely informational)
• ruby-gpgme/riscv64 (2.0.23-1 to 2.0.23-1)
  • Migration status for ruby-gpgme/riscv64 (2.0.23-1 to 2.0.23-1): Will attempt migration (Any information below is purely informational)
• ruby-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-gsl/riscv64 (2.1.0.3+dfsg1-5 to 2.1.0.3+dfsg1-5)
  • Migration status for ruby-gsl/riscv64 (2.1.0.3+dfsg1-5 to 2.1.0.3+dfsg1-5): Will attempt migration (Any information below is purely informational)
• ruby-haml/riscv64 (6.1.2-1 to 6.1.2-1)
  • Migration status for ruby-haml/riscv64 (6.1.2-1 to 6.1.2-1): Will attempt migration (Any information below is purely informational)
• ruby-hamlit/riscv64 (2.15.1-3 to 2.15.1-3)
  • Migration status for ruby-hamlit/riscv64 (2.15.1-3 to 2.15.1-3): Will attempt migration (Any information below is purely informational)
• ruby-hdfeos5/riscv64 (1.2-12 to 1.2-12)
  • Migration status for ruby-hdfeos5/riscv64 (1.2-12 to 1.2-12): Will attempt migration (Any information below is purely informational)
• ruby-hiredis/riscv64 (0.6.3-3 to 0.6.3-3)
  • Migration status for ruby-hiredis/riscv64 (0.6.3-3 to 0.6.3-3): Will attempt migration (Any information below is purely informational)
• ruby-hitimes/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for ruby-hitimes/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-http-parser.rb/riscv64 (0.6.0-6 to 0.6.0-6)
  • Migration status for ruby-http-parser.rb/riscv64 (0.6.0-6 to 0.6.0-6): Will attempt migration (Any information below is purely informational)
• ruby-http-parser/riscv64 (1.2.3-1 to 1.2.3-1)
  • Migration status for ruby-http-parser/riscv64 (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
• ruby-jaro-winkler/riscv64 (1.5.6-1 to 1.5.6-1)
  • Migration status for ruby-jaro-winkler/riscv64 (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
• ruby-json/riscv64 (2.7.2+dfsg-1 to 2.7.2+dfsg-1)
  • Migration status for ruby-json/riscv64 (2.7.2+dfsg-1 to 2.7.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• ruby-kgio/riscv64 (2.11.2-2 to 2.11.2-2)
  • Migration status for ruby-kgio/riscv64 (2.11.2-2 to 2.11.2-2): Will attempt migration (Any information below is purely informational)
• ruby-kyotocabinet/riscv64 (1.34-2 to 1.34-2)
  • Migration status for ruby-kyotocabinet/riscv64 (1.34-2 to 1.34-2): Will attempt migration (Any information below is purely informational)
• ruby-lapack/riscv64 (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/riscv64 (1.8.2-1 to 1.8.2-1): Will attempt migration (Any information below is purely informational)
• ruby-ldap/riscv64 (0.9.20-2 to 0.9.20-2)
  • Migration status for ruby-ldap/riscv64 (0.9.20-2 to 0.9.20-2): Will attempt migration (Any information below is purely informational)
• ruby-levenshtein/riscv64 (0.2.2-3 to 0.2.2-3)
  • Migration status for ruby-levenshtein/riscv64 (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
• ruby-libxml/riscv64 (3.2.4-2 to 3.2.4-2)
  • Migration status for ruby-libxml/riscv64 (3.2.4-2 to 3.2.4-2): Will attempt migration (Any information below is purely informational)
• ruby-liquid-c/riscv64 (4.1.0-2 to 4.1.0-2)
  • Migration status for ruby-liquid-c/riscv64 (4.1.0-2 to 4.1.0-2): 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-mmap2/riscv64 (2.2.9-1 to 2.2.9-1)
  • Migration status for ruby-mmap2/riscv64 (2.2.9-1 to 2.2.9-1): Will attempt migration (Any information below is purely informational)
• ruby-msgpack/riscv64 (1.4.2-2 to 1.4.2-2)
  • Migration status for ruby-msgpack/riscv64 (1.4.2-2 to 1.4.2-2): Will attempt migration (Any information below is purely informational)
• ruby-multibitnums/riscv64 (0.1.4-4 to 0.1.4-4)
  • Migration status for ruby-multibitnums/riscv64 (0.1.4-4 to 0.1.4-4): Will attempt migration (Any information below is purely informational)
• ruby-murmurhash3/riscv64 (0.1.6-2 to 0.1.6-2)
  • Migration status for ruby-murmurhash3/riscv64 (0.1.6-2 to 0.1.6-2): Will attempt migration (Any information below is purely informational)
• ruby-narray/riscv64 (0.6.1.2-4 to 0.6.1.2-4)
  • Migration status for ruby-narray/riscv64 (0.6.1.2-4 to 0.6.1.2-4): Will attempt migration (Any information below is purely informational)
• ruby-ncurses/riscv64 (1.4.9-1 to 1.4.9-1)
  • Migration status for ruby-ncurses/riscv64 (1.4.9-1 to 1.4.9-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-nfc/riscv64 (3.1.2-2 to 3.1.2-2)
  • Migration status for ruby-nfc/riscv64 (3.1.2-2 to 3.1.2-2): Will attempt migration (Any information below is purely informational)
• ruby-nio4r/riscv64 (2.5.8-4 to 2.5.8-4)
  • Migration status for ruby-nio4r/riscv64 (2.5.8-4 to 2.5.8-4): 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-odbc/riscv64 (0.99998-2 to 0.99998-2)
  • Migration status for ruby-odbc/riscv64 (0.99998-2 to 0.99998-2): Will attempt migration (Any information below is purely informational)
• ruby-oily-png/riscv64 (1.2.1~dfsg-3 to 1.2.1~dfsg-3)
  • Migration status for ruby-oily-png/riscv64 (1.2.1~dfsg-3 to 1.2.1~dfsg-3): Will attempt migration (Any information below is purely informational)
• ruby-oj-introspect/riscv64 (0.7.1-3 to 0.7.1-3)
  • Migration status for ruby-oj-introspect/riscv64 (0.7.1-3 to 0.7.1-3): Will attempt migration (Any information below is purely informational)
• ruby-oj/riscv64 (3.16.3-1 to 3.16.3-1)
  • Migration status for ruby-oj/riscv64 (3.16.3-1 to 3.16.3-1): Will attempt migration (Any information below is purely informational)
• ruby-ox/riscv64 (2.14.17-1 to 2.14.17-1)
  • Migration status for ruby-ox/riscv64 (2.14.17-1 to 2.14.17-1): Will attempt migration (Any information below is purely informational)
• ruby-password/riscv64 (0.5.3-5 to 0.5.3-5)
  • Migration status for ruby-password/riscv64 (0.5.3-5 to 0.5.3-5): Will attempt migration (Any information below is purely informational)
• ruby-pcaprub/riscv64 (0.12.4-2 to 0.12.4-2)
  • Migration status for ruby-pcaprub/riscv64 (0.12.4-2 to 0.12.4-2): Will attempt migration (Any information below is purely informational)
• ruby-pg-query/riscv64 (4.2.3-2 to 4.2.3-2)
  • Migration status for ruby-pg-query/riscv64 (4.2.3-2 to 4.2.3-2): Will attempt migration (Any information below is purely informational)
• ruby-pgplot/riscv64 (0.2.0-4 to 0.2.0-4)
  • Migration status for ruby-pgplot/riscv64 (0.2.0-4 to 0.2.0-4): Will attempt migration (Any information below is purely informational)
• ruby-posix-spawn/riscv64 (0.3.15-1 to 0.3.15-1)
  • Migration status for ruby-posix-spawn/riscv64 (0.3.15-1 to 0.3.15-1): Will attempt migration (Any information below is purely informational)
• ruby-prof/riscv64 (1.4.5-2 to 1.4.5-2)
  • Migration status for ruby-prof/riscv64 (1.4.5-2 to 1.4.5-2): Will attempt migration (Any information below is purely informational)
• ruby-prometheus-client-mmap/riscv64 (0.23.1-3 to 0.23.1-3)
  • Migration status for ruby-prometheus-client-mmap/riscv64 (0.23.1-3 to 0.23.1-3): Will attempt migration (Any information below is purely informational)
• ruby-psych/riscv64 (5.0.2-2 to 5.0.2-2)
  • Migration status for ruby-psych/riscv64 (5.0.2-2 to 5.0.2-2): Will attempt migration (Any information below is purely informational)
• ruby-raindrops/riscv64 (0.20.0-1 to 0.20.0-1)
  • Migration status for ruby-raindrops/riscv64 (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
• ruby-rblineprof/riscv64 (0.3.7-2 to 0.3.7-2)
  • Migration status for ruby-rblineprof/riscv64 (0.3.7-2 to 0.3.7-2): Will attempt migration (Any information below is purely informational)
• ruby-rbtrace/riscv64 (0.4.14-1 to 0.4.14-1)
  • Migration status for ruby-rbtrace/riscv64 (0.4.14-1 to 0.4.14-1): Will attempt migration (Any information below is purely informational)
• ruby-rbtree/riscv64 (0.4.6-1 to 0.4.6-1)
  • Migration status for ruby-rbtree/riscv64 (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
• ruby-rdiscount/riscv64 (2.1.8-3 to 2.1.8-3)
  • Migration status for ruby-rdiscount/riscv64 (2.1.8-3 to 2.1.8-3): Will attempt migration (Any information below is purely informational)
• ruby-re2/riscv64 (2.7.0-2 to 2.7.0-2)
  • Migration status for ruby-re2/riscv64 (2.7.0-2 to 2.7.0-2): Will attempt migration (Any information below is purely informational)
• ruby-redcarpet/riscv64 (3.6.0-1 to 3.6.0-1)
  • Migration status for ruby-redcarpet/riscv64 (3.6.0-1 to 3.6.0-1): Will attempt migration (Any information below is purely informational)
• ruby-regexp-property-values/riscv64 (1.0.0-2 to 1.0.0-2)
  • Migration status for ruby-regexp-property-values/riscv64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• ruby-rinku/riscv64 (1.7.3-2.1 to 1.7.3-2.1)
  • Migration status for ruby-rinku/riscv64 (1.7.3-2.1 to 1.7.3-2.1): Will attempt migration (Any information below is purely informational)
• ruby-rmagick/riscv64 (5.3.0-2 to 5.3.0-2)
  • Migration status for ruby-rmagick/riscv64 (5.3.0-2 to 5.3.0-2): Will attempt migration (Any information below is purely informational)
• ruby-rpam-ruby19/riscv64 (1.2.1-1 to 1.2.1-1)
  • Migration status for ruby-rpam-ruby19/riscv64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• ruby-rpatricia/riscv64 (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/riscv64 (1.0.1-2 to 1.0.1-2): Will attempt migration (Any information below is purely informational)
• ruby-rugged/riscv64 (1.7.1+ds-1 to 1.7.1+ds-1)
  • Migration status for ruby-rugged/riscv64 (1.7.1+ds-1 to 1.7.1+ds-1): Will attempt migration (Any information below is purely informational)
• ruby-sdbm/riscv64 (1.0.0-5 to 1.0.0-5)
  • Migration status for ruby-sdbm/riscv64 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• ruby-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-sequel-pg/riscv64 (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/riscv64 (1.14.0-1 to 1.14.0-1): Will attempt migration (Any information below is purely informational)
• ruby-serialport/riscv64 (1.3.2-1 to 1.3.2-1)
  • Migration status for ruby-serialport/riscv64 (1.3.2-1 to 1.3.2-1): Will attempt migration (Any information below is purely informational)
• ruby-shadow/riscv64 (2.5.1-1 to 2.5.1-1)
  • Migration status for ruby-shadow/riscv64 (2.5.1-1 to 2.5.1-1): Will attempt migration (Any information below is purely informational)
• ruby-sqlite3/riscv64 (1.4.2-4 to 1.4.2-4)
  • Migration status for ruby-sqlite3/riscv64 (1.4.2-4 to 1.4.2-4): Will attempt migration (Any information below is purely informational)
• ruby-stackprof/riscv64 (0.2.25-2 to 0.2.25-2)
  • Migration status for ruby-stackprof/riscv64 (0.2.25-2 to 0.2.25-2): Will attempt migration (Any information below is purely informational)
• ruby-standalone/riscv64 (3.0~1 to 3.0~1)
  • Migration status for ruby-standalone/riscv64 (3.0~1 to 3.0~1): Will attempt migration (Any information below is purely informational)
• ruby-strptime/riscv64 (0.2.5-1 to 0.2.5-1)
  • Migration status for ruby-strptime/riscv64 (0.2.5-1 to 0.2.5-1): Will attempt migration (Any information below is purely informational)
• ruby-termios/riscv64 (1.1.0-2 to 1.1.0-2)
  • Migration status for ruby-termios/riscv64 (1.1.0-2 to 1.1.0-2): Will attempt migration (Any information below is purely informational)
• ruby-thrift/riscv64 (0.16.0-2 to 0.16.0-2)
  • Migration status for ruby-thrift/riscv64 (0.16.0-2 to 0.16.0-2): Will attempt migration (Any information below is purely informational)
• ruby-timfel-krb5-auth/riscv64 (0.8.3-3 to 0.8.3-3)
  • Migration status for ruby-timfel-krb5-auth/riscv64 (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
• ruby-tioga/riscv64 (1.19.1-5 to 1.19.1-5)
  • Migration status for ruby-tioga/riscv64 (1.19.1-5 to 1.19.1-5): Will attempt migration (Any information below is purely informational)
• ruby-tokyocabinet/riscv64 (1.31-6 to 1.31-6)
  • Migration status for ruby-tokyocabinet/riscv64 (1.31-6 to 1.31-6): Will attempt migration (Any information below is purely informational)
• ruby-uconv/riscv64 (0.6.1-3 to 0.6.1-3)
  • Migration status for ruby-uconv/riscv64 (0.6.1-3 to 0.6.1-3): Will attempt migration (Any information below is purely informational)
• ruby-unf-ext/riscv64 (0.0.7.7-1 to 0.0.7.7-1)
  • Migration status for ruby-unf-ext/riscv64 (0.0.7.7-1 to 0.0.7.7-1): Will attempt migration (Any information below is purely informational)
• ruby-unicode/riscv64 (0.4.4.4-1 to 0.4.4.4-1)
  • Migration status for ruby-unicode/riscv64 (0.4.4.4-1 to 0.4.4.4-1): Will attempt migration (Any information below is purely informational)
• ruby-version-sorter/riscv64 (2.3.0-1 to 2.3.0-1)
  • Migration status for ruby-version-sorter/riscv64 (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
• ruby-vmstat/riscv64 (2.3.1-1 to 2.3.1-1)
  • Migration status for ruby-vmstat/riscv64 (2.3.1-1 to 2.3.1-1): Will attempt migration (Any information below is purely informational)
• ruby-websocket-driver/riscv64 (0.6.3-3 to 0.6.3-3)
  • Migration status for ruby-websocket-driver/riscv64 (0.6.3-3 to 0.6.3-3): Will attempt migration (Any information below is purely informational)
• ruby-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-xmlparser/riscv64 (0.7.3-4 to 0.7.3-4)
  • Migration status for ruby-xmlparser/riscv64 (0.7.3-4 to 0.7.3-4): Will attempt migration (Any information below is purely informational)
• ruby-yajl/riscv64 (1.4.3-1 to 1.4.3-1)
  • Migration status for ruby-yajl/riscv64 (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
• ruby-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)
• ruby3.1/riscv64 (3.1.2-8.3 to 3.1.2-8.3)
  • Migration status for ruby3.1/riscv64 (3.1.2-8.3 to 3.1.2-8.3): Will attempt migration (Any information below is purely informational)
• rudecgi/riscv64 (5.0.0-1.1 to 5.0.0-1.1)
  • Migration status for rudecgi/riscv64 (5.0.0-1.1 to 5.0.0-1.1): 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-aom-sys/riscv64 (0.3.3-1 to 0.3.3-1)
  • Migration status for rust-aom-sys/riscv64 (0.3.3-1 to 0.3.3-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-async-zip/riscv64 (0.0.16-1 to 0.0.16-1)
  • Migration status for rust-async-zip/riscv64 (0.0.16-1 to 0.0.16-1): Will attempt migration (Any information below is purely informational)
• rust-auditable-serde/riscv64 (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-auditable-serde/riscv64 (0.6.0-1 to 0.6.0-1): Will attempt migration (Any information below is purely informational)
• rust-b3sum/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for rust-b3sum/riscv64 (1.2.0-1 to 1.2.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-bkt/riscv64 (0.6.1-2 to 0.6.1-2)
  • Migration status for rust-bkt/riscv64 (0.6.1-2 to 0.6.1-2): Will attempt migration (Any information below is purely informational)
• rust-botan-sys/riscv64 (0.10.5-1 to 0.10.5-1)
  • Migration status for rust-botan-sys/riscv64 (0.10.5-1 to 0.10.5-1): Will attempt migration (Any information below is purely informational)
• rust-botan/riscv64 (0.10.7-1 to 0.10.7-1)
  • Migration status for rust-botan/riscv64 (0.10.7-1 to 0.10.7-1): Will attempt migration (Any information below is purely informational)
• rust-cairo-sys-rs/riscv64 (0.19.2-2 to 0.19.2-2)
  • Migration status for rust-cairo-sys-rs/riscv64 (0.19.2-2 to 0.19.2-2): Will attempt migration (Any information below is purely informational)
• rust-capnpc/riscv64 (0.19.0-1 to 0.19.0-1)
  • Migration status for rust-capnpc/riscv64 (0.19.0-1 to 0.19.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-cargo-auditable/riscv64 (0.6.1-3 to 0.6.1-3)
  • Migration status for rust-cargo-auditable/riscv64 (0.6.1-3 to 0.6.1-3): Will attempt migration (Any information below is purely informational)
• rust-cargo-binutils/riscv64 (0.3.6-1 to 0.3.6-1)
  • Migration status for rust-cargo-binutils/riscv64 (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
• rust-cargo-lichking/riscv64 (0.9.0-3 to 0.9.0-3)
  • Migration status for rust-cargo-lichking/riscv64 (0.9.0-3 to 0.9.0-3): Will attempt migration (Any information below is purely informational)
• rust-cargo-lock/riscv64 (9.0.0-1 to 9.0.0-1)
  • Migration status for rust-cargo-lock/riscv64 (9.0.0-1 to 9.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-cbindgen/riscv64 (0.26.0-3 to 0.26.0-3)
  • Migration status for rust-cbindgen/riscv64 (0.26.0-3 to 0.26.0-3): Will attempt migration (Any information below is purely informational)
• rust-chrono-tz-build/riscv64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-chrono-tz-build/riscv64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• rust-chrono-tz/riscv64 (0.8.3-1 to 0.8.3-1)
  • Migration status for rust-chrono-tz/riscv64 (0.8.3-1 to 0.8.3-1): Will attempt migration (Any information below is purely informational)
• rust-cid-npm/riscv64 (0.0~git20200813.59cf068-2 to 0.0~git20200813.59cf068-2)
  • Migration status for rust-cid-npm/riscv64 (0.0~git20200813.59cf068-2 to 0.0~git20200813.59cf068-2): Will attempt migration (Any information below is purely informational)
• rust-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-color-print/riscv64 (0.3.5-2 to 0.3.5-2)
  • Migration status for rust-color-print/riscv64 (0.3.5-2 to 0.3.5-2): Will attempt migration (Any information below is purely informational)
• rust-comrak/riscv64 (0.20.0-2 to 0.20.0-2)
  • Migration status for rust-comrak/riscv64 (0.20.0-2 to 0.20.0-2): Will attempt migration (Any information below is purely informational)
• rust-condure/riscv64 (1.10.0-4 to 1.10.0-4)
  • Migration status for rust-condure/riscv64 (1.10.0-4 to 1.10.0-4): 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-cryptoki-sys/riscv64 (0.1.7-1 to 0.1.7-1)
  • Migration status for rust-cryptoki-sys/riscv64 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• rust-cryptoki/riscv64 (0.6.1-2 to 0.6.1-2)
  • Migration status for rust-cryptoki/riscv64 (0.6.1-2 to 0.6.1-2): 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-cursive-core/riscv64 (0.3.5-1 to 0.3.5-1)
  • Migration status for rust-cursive-core/riscv64 (0.3.5-1 to 0.3.5-1): Will attempt migration (Any information below is purely informational)
• rust-cursive/riscv64 (0.20.0-2 to 0.20.0-2)
  • Migration status for rust-cursive/riscv64 (0.20.0-2 to 0.20.0-2): 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-dhcproto/riscv64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-dhcproto/riscv64 (0.9.0-1 to 0.9.0-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-difference/riscv64 (2.0.0-1 to 2.0.0-1)
  • Migration status for rust-difference/riscv64 (2.0.0-1 to 2.0.0-1): Will attempt migration (Any information below is purely informational)
• rust-diffr/riscv64 (0.1.5-2 to 0.1.5-2)
  • Migration status for rust-diffr/riscv64 (0.1.5-2 to 0.1.5-2): Will attempt migration (Any information below is purely informational)
• rust-diffutils/riscv64 (0.4.1-1 to 0.4.1-1)
  • Migration status for rust-diffutils/riscv64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• rust-dotenv/riscv64 (0.15.0-2 to 0.15.0-2)
  • Migration status for rust-dotenv/riscv64 (0.15.0-2 to 0.15.0-2): 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-droid-juicer/riscv64 (0.2.1-2 to 0.2.1-2)
  • Migration status for rust-droid-juicer/riscv64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-elfx86exts/riscv64 (0.6.2-1 to 0.6.2-1)
  • Migration status for rust-elfx86exts/riscv64 (0.6.2-1 to 0.6.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-erbium/riscv64 (1.0.5-2 to 1.0.5-2)
  • Migration status for rust-erbium/riscv64 (1.0.5-2 to 1.0.5-2): Will attempt migration (Any information below is purely informational)
• rust-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-fd-find/riscv64 (9.0.0-1 to 9.0.0-1)
  • Migration status for rust-fd-find/riscv64 (9.0.0-1 to 9.0.0-1): 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-filespooler/riscv64 (1.2.3-1 to 1.2.3-1)
  • Migration status for rust-filespooler/riscv64 (1.2.3-1 to 1.2.3-1): 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-gdk-pixbuf-sys/riscv64 (0.19.5-1 to 0.19.5-1)
  • Migration status for rust-gdk-pixbuf-sys/riscv64 (0.19.5-1 to 0.19.5-1): Will attempt migration (Any information below is purely informational)
• rust-gdk-pixbuf/riscv64 (0.19.2-2 to 0.19.2-2)
  • Migration status for rust-gdk-pixbuf/riscv64 (0.19.2-2 to 0.19.2-2): Will attempt migration (Any information below is purely informational)
• rust-gdk4-wayland-sys/riscv64 (0.8.2-2 to 0.8.2-2)
  • Migration status for rust-gdk4-wayland-sys/riscv64 (0.8.2-2 to 0.8.2-2): 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-git2/riscv64 (0.18.1-1 to 0.18.1-1)
  • Migration status for rust-git2/riscv64 (0.18.1-1 to 0.18.1-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-gsk4-sys/riscv64 (0.8.2-1 to 0.8.2-1)
  • Migration status for rust-gsk4-sys/riscv64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-audio-sys/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-audio-sys/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-audio/riscv64 (0.22.4-2 to 0.22.4-2)
  • Migration status for rust-gstreamer-audio/riscv64 (0.22.4-2 to 0.22.4-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-base-sys/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-base-sys/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-base/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-base/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-gl-egl-sys/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-gl-egl-sys/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-gl-egl/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-gl-egl/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-gl-sys/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-gl-sys/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-gl-wayland-sys/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-gl-wayland-sys/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-gl-wayland/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-gl-wayland/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-gl-x11-sys/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-gl-x11-sys/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-gl-x11/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-gl-x11/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-gl/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-gl/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-pbutils-sys/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-pbutils-sys/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-pbutils/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-pbutils/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-play-sys/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-play-sys/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-play/riscv64 (0.22.0-2 to 0.22.0-2)
  • Migration status for rust-gstreamer-play/riscv64 (0.22.0-2 to 0.22.0-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-video-sys/riscv64 (0.22.1-2 to 0.22.1-2)
  • Migration status for rust-gstreamer-video-sys/riscv64 (0.22.1-2 to 0.22.1-2): Will attempt migration (Any information below is purely informational)
• rust-gstreamer-video/riscv64 (0.22.4-3 to 0.22.4-3)
  • Migration status for rust-gstreamer-video/riscv64 (0.22.4-3 to 0.22.4-3): Will attempt migration (Any information below is purely informational)
• rust-gtk-rs-lgpl-docs/riscv64 (0.1.12-2 to 0.1.12-2)
  • Migration status for rust-gtk-rs-lgpl-docs/riscv64 (0.1.12-2 to 0.1.12-2): Will attempt migration (Any information below is purely informational)
• rust-gtk4-sys/riscv64 (0.8.2-1 to 0.8.2-1)
  • Migration status for rust-gtk4-sys/riscv64 (0.8.2-1 to 0.8.2-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-hexyl/riscv64 (0.8.0-2 to 0.8.0-2)
  • Migration status for rust-hexyl/riscv64 (0.8.0-2 to 0.8.0-2): 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-hyperfine/riscv64 (1.18.0-2 to 1.18.0-2)
  • Migration status for rust-hyperfine/riscv64 (1.18.0-2 to 1.18.0-2): 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-kmon/riscv64 (1.6.0-2 to 1.6.0-2)
  • Migration status for rust-kmon/riscv64 (1.6.0-2 to 1.6.0-2): Will attempt migration (Any information below is purely informational)
• rust-lalrpop/riscv64 (0.20.2-1 to 0.20.2-1)
  • Migration status for rust-lalrpop/riscv64 (0.20.2-1 to 0.20.2-1): Will attempt migration (Any information below is purely informational)
• rust-libadwaita-sys/riscv64 (0.6.0-2 to 0.6.0-2)
  • Migration status for rust-libadwaita-sys/riscv64 (0.6.0-2 to 0.6.0-2): 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-libgit2-sys/riscv64 (0.16.1-1 to 0.16.1-1)
  • Migration status for rust-libgit2-sys/riscv64 (0.16.1-1 to 0.16.1-1): Will attempt migration (Any information below is purely informational)
• rust-libheif-rs/riscv64 (0.20.0-5 to 0.20.0-5)
  • Migration status for rust-libheif-rs/riscv64 (0.20.0-5 to 0.20.0-5): Will attempt migration (Any information below is purely informational)
• rust-libheif-sys/riscv64 (1.16.2-5 to 1.16.2-5)
  • Migration status for rust-libheif-sys/riscv64 (1.16.2-5 to 1.16.2-5): 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-libshumate-sys/riscv64 (0.5.0-2 to 0.5.0-2)
  • Migration status for rust-libshumate-sys/riscv64 (0.5.0-2 to 0.5.0-2): 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-lscolors/riscv64 (0.16.0-3 to 0.16.0-3)
  • Migration status for rust-lscolors/riscv64 (0.16.0-3 to 0.16.0-3): Will attempt migration (Any information below is purely informational)
• rust-lsd/riscv64 (1.0.0-2 to 1.0.0-2)
  • Migration status for rust-lsd/riscv64 (1.0.0-2 to 1.0.0-2): Will attempt migration (Any information below is purely informational)
• rust-markdown/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-markdown/riscv64 (0.3.0-1 to 0.3.0-1): 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-mysqlclient-sys/riscv64 (0.2.5-2 to 0.2.5-2)
  • Migration status for rust-mysqlclient-sys/riscv64 (0.2.5-2 to 0.2.5-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-netr/riscv64 (0.1.6-1 to 0.1.6-1)
  • Migration status for rust-netr/riscv64 (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
• rust-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-nitrocli/riscv64 (0.2.4-2 to 0.2.4-2)
  • Migration status for rust-nitrocli/riscv64 (0.2.4-2 to 0.2.4-2): Will attempt migration (Any information below is purely informational)
• rust-nitrokey-sys/riscv64 (3.4.3-2 to 3.4.3-2)
  • Migration status for rust-nitrokey-sys/riscv64 (3.4.3-2 to 3.4.3-2): Will attempt migration (Any information below is purely informational)
• rust-nitrokey/riscv64 (0.3.4-3 to 0.3.4-3)
  • Migration status for rust-nitrokey/riscv64 (0.3.4-3 to 0.3.4-3): Will attempt migration (Any information below is purely informational)
• rust-numbat-exchange-rates/riscv64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-numbat-exchange-rates/riscv64 (0.4.0-1 to 0.4.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-opam-file-rs/riscv64 (0.1.5-2 to 0.1.5-2)
  • Migration status for rust-opam-file-rs/riscv64 (0.1.5-2 to 0.1.5-2): 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-pango/riscv64 (0.19.5-1 to 0.19.5-1)
  • Migration status for rust-pango/riscv64 (0.19.5-1 to 0.19.5-1): Will attempt migration (Any information below is purely informational)
• rust-pangocairo-sys/riscv64 (0.19.5-1 to 0.19.5-1)
  • Migration status for rust-pangocairo-sys/riscv64 (0.19.5-1 to 0.19.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-pep440-rs/riscv64 (0.3.12-2 to 0.3.12-2)
  • Migration status for rust-pep440-rs/riscv64 (0.3.12-2 to 0.3.12-2): Will attempt migration (Any information below is purely informational)
• rust-pep508-rs/riscv64 (0.2.3-1 to 0.2.3-1)
  • Migration status for rust-pep508-rs/riscv64 (0.2.3-1 to 0.2.3-1): 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-plotters/riscv64 (0.3.5-2 to 0.3.5-2)
  • Migration status for rust-plotters/riscv64 (0.3.5-2 to 0.3.5-2): 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-protobuf-codegen-pure/riscv64 (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protobuf-codegen-pure/riscv64 (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-protobuf-codegen/riscv64 (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protobuf-codegen/riscv64 (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-protoc-rust/riscv64 (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protoc-rust/riscv64 (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-protoc/riscv64 (2.27.1-1 to 2.27.1-1)
  • Migration status for rust-protoc/riscv64 (2.27.1-1 to 2.27.1-1): Will attempt migration (Any information below is purely informational)
• rust-proton-call/riscv64 (3.1.2-1 to 3.1.2-1)
  • Migration status for rust-proton-call/riscv64 (3.1.2-1 to 3.1.2-1): 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-pulldown-cmark/riscv64 (0.9.2-1 to 0.9.2-1)
  • Migration status for rust-pulldown-cmark/riscv64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• rust-pyo3-build-config/riscv64 (0.20.2-1 to 0.20.2-1)
  • Migration status for rust-pyo3-build-config/riscv64 (0.20.2-1 to 0.20.2-1): Will attempt migration (Any information below is purely informational)
• rust-pyo3-ffi/riscv64 (0.20.2-2 to 0.20.2-2)
  • Migration status for rust-pyo3-ffi/riscv64 (0.20.2-2 to 0.20.2-2): Will attempt migration (Any information below is purely informational)
• rust-pyo3-log/riscv64 (0.9.0-1 to 0.9.0-1)
  • Migration status for rust-pyo3-log/riscv64 (0.9.0-1 to 0.9.0-1): 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-python3-dll-a/riscv64 (0.2.6-1 to 0.2.6-1)
  • Migration status for rust-python3-dll-a/riscv64 (0.2.6-1 to 0.2.6-1): Will attempt migration (Any information below is purely informational)
• rust-pythonize/riscv64 (0.20.0-1 to 0.20.0-1)
  • Migration status for rust-pythonize/riscv64 (0.20.0-1 to 0.20.0-1): Will attempt migration (Any information below is purely informational)
• rust-rav1e/riscv64 (0.7.1-2 to 0.7.1-2)
  • Migration status for rust-rav1e/riscv64 (0.7.1-2 to 0.7.1-2): 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-repro-env/riscv64 (0.4.0-1 to 0.4.0-1)
  • Migration status for rust-repro-env/riscv64 (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
• rust-ripgrep/riscv64 (14.1.0-1 to 14.1.0-1)
  • Migration status for rust-ripgrep/riscv64 (14.1.0-1 to 14.1.0-1): Will attempt migration (Any information below is purely informational)
• rust-ruma-push-gateway-api/riscv64 (0.6.0-1 to 0.6.0-1)
  • Migration status for rust-ruma-push-gateway-api/riscv64 (0.6.0-1 to 0.6.0-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-rustdoc-stripper/riscv64 (0.1.12-1 to 0.1.12-1)
  • Migration status for rust-rustdoc-stripper/riscv64 (0.1.12-1 to 0.1.12-1): Will attempt migration (Any information below is purely informational)
• rust-rustfilt/riscv64 (0.2.1-2 to 0.2.1-2)
  • Migration status for rust-rustfilt/riscv64 (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
• rust-rusty-tags/riscv64 (3.10.0-1 to 3.10.0-1)
  • Migration status for rust-rusty-tags/riscv64 (3.10.0-1 to 3.10.0-1): Will attempt migration (Any information below is purely informational)
• 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-selinux/riscv64 (0.4.3-1 to 0.4.3-1)
  • Migration status for rust-selinux/riscv64 (0.4.3-1 to 0.4.3-1): 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-keystore/riscv64 (0.2.0-1 to 0.2.0-1)
  • Migration status for rust-sequoia-keystore/riscv64 (0.2.0-1 to 0.2.0-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-sequoia-sq/riscv64 (0.33.0-3 to 0.33.0-3)
  • Migration status for rust-sequoia-sq/riscv64 (0.33.0-3 to 0.33.0-3): Will attempt migration (Any information below is purely informational)
• rust-sequoia-sqv/riscv64 (1.1.0-1 to 1.1.0-1)
  • Migration status for rust-sequoia-sqv/riscv64 (1.1.0-1 to 1.1.0-1): 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-shadow-rs/riscv64 (0.24.1-2 to 0.24.1-2)
  • Migration status for rust-shadow-rs/riscv64 (0.24.1-2 to 0.24.1-2): 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-skeptic/riscv64 (0.13.7-3 to 0.13.7-3)
  • Migration status for rust-skeptic/riscv64 (0.13.7-3 to 0.13.7-3): Will attempt migration (Any information below is purely informational)
• rust-sniffglue/riscv64 (0.16.0-3 to 0.16.0-3)
  • Migration status for rust-sniffglue/riscv64 (0.16.0-3 to 0.16.0-3): Will attempt migration (Any information below is purely informational)
• 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-sudo-rs/riscv64 (0.2.2-1 to 0.2.2-1)
  • Migration status for rust-sudo-rs/riscv64 (0.2.2-1 to 0.2.2-1): Will attempt migration (Any information below is purely informational)
• rust-svg-metadata/riscv64 (0.5.0-1 to 0.5.0-1)
  • Migration status for rust-svg-metadata/riscv64 (0.5.0-1 to 0.5.0-1): 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-tcmalloc-sys/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-tcmalloc-sys/riscv64 (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
• rust-tealdeer/riscv64 (1.6.1-4 to 1.6.1-4)
  • Migration status for rust-tealdeer/riscv64 (1.6.1-4 to 1.6.1-4): 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-tls-parser/riscv64 (0.11.0-3 to 0.11.0-3)
  • Migration status for rust-tls-parser/riscv64 (0.11.0-3 to 0.11.0-3): 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-tui-react/riscv64 (0.20.0-2 to 0.20.0-2)
  • Migration status for rust-tui-react/riscv64 (0.20.0-2 to 0.20.0-2): 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-ucd-generate/riscv64 (0.3.0-1 to 0.3.0-1)
  • Migration status for rust-ucd-generate/riscv64 (0.3.0-1 to 0.3.0-1): 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-usb-ids/riscv64 (1.2024.2-1 to 1.2024.2-1)
  • Migration status for rust-usb-ids/riscv64 (1.2024.2-1 to 1.2024.2-1): Will attempt migration (Any information below is purely informational)
• rust-vivid/riscv64 (0.9.0-2 to 0.9.0-2)
  • Migration status for rust-vivid/riscv64 (0.9.0-2 to 0.9.0-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-z-base-32/riscv64 (0.1.2-1 to 0.1.2-1)
  • Migration status for rust-z-base-32/riscv64 (0.1.2-1 to 0.1.2-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)
• safe-rm/riscv64 (1.1.0-5 to 1.1.0-5)
  • Migration status for safe-rm/riscv64 (1.1.0-5 to 1.1.0-5): Will attempt migration (Any information below is purely informational)
• safe-vdash/riscv64 (0.16.4-1 to 0.16.4-1)
  • Migration status for safe-vdash/riscv64 (0.16.4-1 to 0.16.4-1): 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)
• sakura/riscv64 (3.8.7-1 to 3.8.7-1)
  • Migration status for sakura/riscv64 (3.8.7-1 to 3.8.7-1): Will attempt migration (Any information below is purely informational)
• sambamba/riscv64 (1.0.1+dfsg-2 to 1.0.1+dfsg-2)
  • Migration status for sambamba/riscv64 (1.0.1+dfsg-2 to 1.0.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• samblaster/riscv64 (0.1.26-4 to 0.1.26-4)
  • Migration status for samblaster/riscv64 (0.1.26-4 to 0.1.26-4): Will attempt migration (Any information below is purely informational)
• samplv1/riscv64 (0.9.90-1 to 0.9.90-1)
  • Migration status for samplv1/riscv64 (0.9.90-1 to 0.9.90-1): Will attempt migration (Any information below is purely informational)
• sane-airscan/riscv64 (0.99.27-1 to 0.99.27-1)
  • Migration status for sane-airscan/riscv64 (0.99.27-1 to 0.99.27-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)
• saods9/riscv64 (8.5+repack-1 to 8.5+repack-1)
  • Migration status for saods9/riscv64 (8.5+repack-1 to 8.5+repack-1): Will attempt migration (Any information below is purely informational)
• sarg/riscv64 (2.4.0-3 to 2.4.0-3)
  • Migration status for sarg/riscv64 (2.4.0-3 to 2.4.0-3): 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)
• sassc/riscv64 (3.6.1+20201027-2 to 3.6.1+20201027-2)
  • Migration status for sassc/riscv64 (3.6.1+20201027-2 to 3.6.1+20201027-2): Will attempt migration (Any information below is purely informational)
• savvy/riscv64 (2.1.0-2 to 2.1.0-2)
  • Migration status for savvy/riscv64 (2.1.0-2 to 2.1.0-2): Will attempt migration (Any information below is purely informational)
• sawfish/riscv64 (1:1.11.90-1.2 to 1:1.11.90-1.2)
  • Migration status for sawfish/riscv64 (1:1.11.90-1.2 to 1:1.11.90-1.2): Will attempt migration (Any information below is purely informational)
• sayonara/riscv64 (1.8.0-beta1-1 to 1.8.0-beta1-1)
  • Migration status for sayonara/riscv64 (1.8.0-beta1-1 to 1.8.0-beta1-1): Will attempt migration (Any information below is purely informational)
• saytime/riscv64 (1.0-35 to 1.0-35)
  • Migration status for saytime/riscv64 (1.0-35 to 1.0-35): 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)
• sblim-wbemcli/riscv64 (1.6.3-3 to 1.6.3-3)
  • Migration status for sblim-wbemcli/riscv64 (1.6.3-3 to 1.6.3-3): Will attempt migration (Any information below is purely informational)
• sc-im/riscv64 (0.8.3+ds-3 to 0.8.3+ds-3)
  • Migration status for sc-im/riscv64 (0.8.3+ds-3 to 0.8.3+ds-3): 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)
• scheme-bytestructures/riscv64 (1.0.10-3 to 1.0.10-3)
  • Migration status for scheme-bytestructures/riscv64 (1.0.10-3 to 1.0.10-3): Will attempt migration (Any information below is purely informational)
• schroedinger-coordgenlibs/riscv64 (3.0.2-1 to 3.0.2-1)
  • Migration status for schroedinger-coordgenlibs/riscv64 (3.0.2-1 to 3.0.2-1): Will attempt migration (Any information below is purely informational)
• schroedinger-maeparser/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for schroedinger-maeparser/riscv64 (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
• schroot/riscv64 (1.6.13-3 to 1.6.13-3)
  • Migration status for schroot/riscv64 (1.6.13-3 to 1.6.13-3): Will attempt migration (Any information below is purely informational)
• scid/riscv64 (1:4.7.4+dfsg1-2 to 1:4.7.4+dfsg1-2)
  • Migration status for scid/riscv64 (1:4.7.4+dfsg1-2 to 1:4.7.4+dfsg1-2): Will attempt migration (Any information below is purely informational)
• scikit-misc/riscv64 (0.3.1+dfsg-3 to 0.3.1+dfsg-3)
  • Migration status for scikit-misc/riscv64 (0.3.1+dfsg-3 to 0.3.1+dfsg-3): 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)
• scite/riscv64 (5.5.0-1 to 5.5.0-1)
  • Migration status for scite/riscv64 (5.5.0-1 to 5.5.0-1): 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)
• scitokens-cpp/riscv64 (1.1.1-1 to 1.1.1-1)
  • Migration status for scitokens-cpp/riscv64 (1.1.1-1 to 1.1.1-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)
• scotch/riscv64 (7.0.4-2 to 7.0.4-2)
  • Migration status for scotch/riscv64 (7.0.4-2 to 7.0.4-2): Will attempt migration (Any information below is purely informational)
• scram/riscv64 (0.16.2-3 to 0.16.2-3)
  • Migration status for scram/riscv64 (0.16.2-3 to 0.16.2-3): Will attempt migration (Any information below is purely informational)
• scrappie/riscv64 (1.4.2-8 to 1.4.2-8)
  • Migration status for scrappie/riscv64 (1.4.2-8 to 1.4.2-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)
• screengrab/riscv64 (2.7.0-1 to 2.7.0-1)
  • Migration status for screengrab/riscv64 (2.7.0-1 to 2.7.0-1): Will attempt migration (Any information below is purely informational)
• scrm/riscv64 (1.7.4-1 to 1.7.4-1)
  • Migration status for scrm/riscv64 (1.7.4-1 to 1.7.4-1): 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)
• sdbus-cpp/riscv64 (1.4.0-2 to 1.4.0-2)
  • Migration status for sdbus-cpp/riscv64 (1.4.0-2 to 1.4.0-2): Will attempt migration (Any information below is purely informational)
• sdcc/riscv64 (4.4.0+dfsg-2 to 4.4.0+dfsg-2)
  • Migration status for sdcc/riscv64 (4.4.0+dfsg-2 to 4.4.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• sdcv/riscv64 (0.5.2-2 to 0.5.2-2)
  • Migration status for sdcv/riscv64 (0.5.2-2 to 0.5.2-2): Will attempt migration (Any information below is purely informational)
• sdformat/riscv64 (12.3.0+ds-2 to 12.3.0+ds-2)
  • Migration status for sdformat/riscv64 (12.3.0+ds-2 to 12.3.0+ds-2): 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-image1.2/riscv64 (1.2.12-13 to 1.2.12-13)
  • Migration status for sdl-image1.2/riscv64 (1.2.12-13 to 1.2.12-13): 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-mixer1.2/riscv64 (1.2.12-18 to 1.2.12-18)
  • Migration status for sdl-mixer1.2/riscv64 (1.2.12-18 to 1.2.12-18): Will attempt migration (Any information below is purely informational)
• sdl-net1.2/riscv64 (1.2.8-6 to 1.2.8-6)
  • Migration status for sdl-net1.2/riscv64 (1.2.8-6 to 1.2.8-6): 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)
• sdpb/riscv64 (1.0-4 to 1.0-4)
  • Migration status for sdpb/riscv64 (1.0-4 to 1.0-4): Will attempt migration (Any information below is purely informational)
• seahorse-nautilus/riscv64 (3.11.92+git20230129.d59dc92f-1 to 3.11.92+git20230129.d59dc92f-1)
  • Migration status for seahorse-nautilus/riscv64 (3.11.92+git20230129.d59dc92f-1 to 3.11.92+git20230129.d59dc92f-1): Will attempt migration (Any information below is purely informational)
• seahorse/riscv64 (43.0-3 to 43.0-3)
  • Migration status for seahorse/riscv64 (43.0-3 to 43.0-3): 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)
• seaview/riscv64 (1:5.0.5-2 to 1:5.0.5-2)
  • Migration status for seaview/riscv64 (1:5.0.5-2 to 1:5.0.5-2): Will attempt migration (Any information below is purely informational)
• securefs/riscv64 (0.13.1+ds-1 to 0.13.1+ds-1)
  • Migration status for securefs/riscv64 (0.13.1+ds-1 to 0.13.1+ds-1): Will attempt migration (Any information below is purely informational)
• sedutil/riscv64 (1.20.0-2 to 1.20.0-2)
  • Migration status for sedutil/riscv64 (1.20.0-2 to 1.20.0-2): Will attempt migration (Any information below is purely informational)
• seer/riscv64 (1.1.4-7 to 1.1.4-7)
  • Migration status for seer/riscv64 (1.1.4-7 to 1.1.4-7): Will attempt migration (Any information below is purely informational)
• seergdb/riscv64 (2.4+git20240321+ds-1 to 2.4+git20240321+ds-1)
  • Migration status for seergdb/riscv64 (2.4+git20240321+ds-1 to 2.4+git20240321+ds-1): Will attempt migration (Any information below is purely informational)
• selinux-python/riscv64 (3.5-1 to 3.5-1)
  • Migration status for selinux-python/riscv64 (3.5-1 to 3.5-1): 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)
• sentencepiece/riscv64 (0.2.0-1 to 0.2.0-1)
  • Migration status for sentencepiece/riscv64 (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
• sep/riscv64 (1.2.1-6 to 1.2.1-6)
  • Migration status for sep/riscv64 (1.2.1-6 to 1.2.1-6): Will attempt migration (Any information below is purely informational)
• seqan-needle/riscv64 (1.0.2+ds-2 to 1.0.2+ds-2)
  • Migration status for seqan-needle/riscv64 (1.0.2+ds-2 to 1.0.2+ds-2): Will attempt migration (Any information below is purely informational)
• seqan-raptor/riscv64 (3.0.1+ds-5 to 3.0.1+ds-5)
  • Migration status for seqan-raptor/riscv64 (3.0.1+ds-5 to 3.0.1+ds-5): Will attempt migration (Any information below is purely informational)
• seqan2/riscv64 (2.4.0+dfsg-16 to 2.4.0+dfsg-16)
  • Migration status for seqan2/riscv64 (2.4.0+dfsg-16 to 2.4.0+dfsg-16): Will attempt migration (Any information below is purely informational)
• 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)
• sequeler/riscv64 (0.8.2-1 to 0.8.2-1)
  • Migration status for sequeler/riscv64 (0.8.2-1 to 0.8.2-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)
• ser2net/riscv64 (4.6.0-1 to 4.6.0-1)
  • Migration status for ser2net/riscv64 (4.6.0-1 to 4.6.0-1): Will attempt migration (Any information below is purely informational)
• serialdv/riscv64 (1.1.4-2 to 1.1.4-2)
  • Migration status for serialdv/riscv64 (1.1.4-2 to 1.1.4-2): Will attempt migration (Any information below is purely informational)
• service-wrapper-java/riscv64 (3.5.51-2 to 3.5.51-2)
  • Migration status for service-wrapper-java/riscv64 (3.5.51-2 to 3.5.51-2): Will attempt migration (Any information below is purely informational)
• setbfree/riscv64 (0.8.12+ds-2 to 0.8.12+ds-2)
  • Migration status for setbfree/riscv64 (0.8.12+ds-2 to 0.8.12+ds-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)
• setop/riscv64 (0.1-1 to 0.1-1)
  • Migration status for setop/riscv64 (0.1-1 to 0.1-1): Will attempt migration (Any information below is purely informational)
• settle/riscv64 (0.40.1-4 to 0.40.1-4)
  • Migration status for settle/riscv64 (0.40.1-4 to 0.40.1-4): Will attempt migration (Any information below is purely informational)
• sexplib310/riscv64 (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for sexplib310/riscv64 (1:0.16.0-2 to 1:0.16.0-2): Will attempt migration (Any information below is purely informational)
• sexpp/riscv64 (0.8.7-4 to 0.8.7-4)
  • Migration status for sexpp/riscv64 (0.8.7-4 to 0.8.7-4): Will attempt migration (Any information below is purely informational)
• sfcgal/riscv64 (1.5.1-3 to 1.5.1-3)
  • Migration status for sfcgal/riscv64 (1.5.1-3 to 1.5.1-3): Will attempt migration (Any information below is purely informational)
• sfftobmp/riscv64 (3.1.3-9 to 3.1.3-9)
  • Migration status for sfftobmp/riscv64 (3.1.3-9 to 3.1.3-9): 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)
• sfst/riscv64 (1.4.7b-1 to 1.4.7b-1)
  • Migration status for sfst/riscv64 (1.4.7b-1 to 1.4.7b-1): 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)
• sga/riscv64 (0.10.15-7 to 0.10.15-7)
  • Migration status for sga/riscv64 (0.10.15-7 to 0.10.15-7): 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)
• shairport-sync/riscv64 (3.3.8-1 to 3.3.8-1)
  • Migration status for shairport-sync/riscv64 (3.3.8-1 to 3.3.8-1): Will attempt migration (Any information below is purely informational)
• shapeit4/riscv64 (4.2.2+dfsg-1 to 4.2.2+dfsg-1)
  • Migration status for shapeit4/riscv64 (4.2.2+dfsg-1 to 4.2.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• shapelib/riscv64 (1.6.0-1 to 1.6.0-1)
  • Migration status for shapelib/riscv64 (1.6.0-1 to 1.6.0-1): 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)
• shim-helpers-amd64-signed_pu (1+15.7+1 to 1+15.8+1~deb12u1)
  • Migration status for shim-helpers-amd64-signed_pu (1+15.7+1 to 1+15.8+1~deb12u1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • NEEDS APPROVAL BY RM
    • Build-Depends(-Arch): shim-helpers-amd64-signed_pu shim_pu (not considered)
    • Built-Using: shim-helpers-amd64-signed_pu shim_pu (not considered)
    • Depends: shim-helpers-amd64-signed_pu shim (not considered)
• shim-helpers-arm64-signed_pu (1+15.7+1 to 1+15.8+1~deb12u1)
  • Migration status for shim-helpers-arm64-signed_pu (1+15.7+1 to 1+15.8+1~deb12u1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • NEEDS APPROVAL BY RM
    • Build-Depends(-Arch): shim-helpers-arm64-signed_pu shim_pu (not considered)
    • Built-Using: shim-helpers-arm64-signed_pu shim_pu (not considered)
    • Depends: shim-helpers-arm64-signed_pu shim (not considered)
• shim-helpers-i386-signed_pu (1+15.7+1 to 1+15.8+1~deb12u1)
  • Migration status for shim-helpers-i386-signed_pu (1+15.7+1 to 1+15.8+1~deb12u1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • NEEDS APPROVAL BY RM
    • Build-Depends(-Arch): shim-helpers-i386-signed_pu shim_pu (not considered)
    • Built-Using: shim-helpers-i386-signed_pu shim_pu (not considered)
    • Depends: shim-helpers-i386-signed_pu shim_pu (not considered)
• shim_pu (15.7-1 to 15.8-1~deb12u1)
  • Migration status for shim_pu (15.7-1 to 15.8-1~deb12u1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • NEEDS APPROVAL BY RM
• 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)
• shotcut/riscv64 (24.04.28+ds-1 to 24.04.28+ds-1)
  • Migration status for shotcut/riscv64 (24.04.28+ds-1 to 24.04.28+ds-1): 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)
• sibelia/riscv64 (3.0.7+dfsg-3 to 3.0.7+dfsg-3)
  • Migration status for sibelia/riscv64 (3.0.7+dfsg-3 to 3.0.7+dfsg-3): Will attempt migration (Any information below is purely informational)
• sidplay-base/riscv64 (1.0.9-8 to 1.0.9-8)
  • Migration status for sidplay-base/riscv64 (1.0.9-8 to 1.0.9-8): Will attempt migration (Any information below is purely informational)
• sidplay-libs/riscv64 (2.1.1-15 to 2.1.1-15)
  • Migration status for sidplay-libs/riscv64 (2.1.1-15 to 2.1.1-15): Will attempt migration (Any information below is purely informational)
• sidplay/riscv64 (2.0.9-7 to 2.0.9-7)
  • Migration status for sidplay/riscv64 (2.0.9-7 to 2.0.9-7): 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)
• sigrok-cli/riscv64 (0.7.2-1 to 0.7.2-1)
  • Migration status for sigrok-cli/riscv64 (0.7.2-1 to 0.7.2-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)
• silly/riscv64 (0.1.0-8.1 to 0.1.0-8.1)
  • Migration status for silly/riscv64 (0.1.0-8.1 to 0.1.0-8.1): Will attempt migration (Any information below is purely informational)
• silo-llnl/riscv64 (4.11-5 to 4.11-5)
  • Migration status for silo-llnl/riscv64 (4.11-5 to 4.11-5): 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)
• simage/riscv64 (1.8.3+ds-2 to 1.8.3+ds-2)
  • Migration status for simage/riscv64 (1.8.3+ds-2 to 1.8.3+ds-2): 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)
• simdjson/riscv64 (3.6.4-1 to 3.6.4-1)
  • Migration status for simdjson/riscv64 (3.6.4-1 to 3.6.4-1): 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)
• simka/riscv64 (1.5.3-8 to 1.5.3-8)
  • Migration status for simka/riscv64 (1.5.3-8 to 1.5.3-8): 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)
• simple-tpm-pk11/riscv64 (0.06-5 to 0.06-5)
  • Migration status for simple-tpm-pk11/riscv64 (0.06-5 to 0.06-5): Will attempt migration (Any information below is purely informational)
• simstring/riscv64 (1.0-3 to 1.0-3)
  • Migration status for simstring/riscv64 (1.0-3 to 1.0-3): Will attempt migration (Any information below is purely informational)
• simulavr/riscv64 (1.0.0+git20160221.e53413b-3 to 1.0.0+git20160221.e53413b-3)
  • Migration status for simulavr/riscv64 (1.0.0+git20160221.e53413b-3 to 1.0.0+git20160221.e53413b-3): Will attempt migration (Any information below is purely informational)
• simutrans/riscv64 (123.0.1-3 to 123.0.1-3)
  • Migration status for simutrans/riscv64 (123.0.1-3 to 123.0.1-3): Will attempt migration (Any information below is purely informational)
• sinfo/riscv64 (0.0.48-2.1 to 0.0.48-2.1)
  • Migration status for sinfo/riscv64 (0.0.48-2.1 to 0.0.48-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)
• sip-tester/riscv64 (1:3.7.2-1 to 1:3.7.2-1)
  • Migration status for sip-tester/riscv64 (1:3.7.2-1 to 1:3.7.2-1): Will attempt migration (Any information below is purely informational)
• siril/riscv64 (1.2.1-1 to 1.2.1-1)
  • Migration status for siril/riscv64 (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
• siscone/riscv64 (3.0.5-2 to 3.0.5-2)
  • Migration status for siscone/riscv64 (3.0.5-2 to 3.0.5-2): Will attempt migration (Any information below is purely informational)
• sjaakii/riscv64 (1.4.1-2 to 1.4.1-2)
  • Migration status for sjaakii/riscv64 (1.4.1-2 to 1.4.1-2): Will attempt migration (Any information below is purely informational)
• ska/riscv64 (1.0+dfsg-4 to 1.0+dfsg-4)
  • Migration status for ska/riscv64 (1.0+dfsg-4 to 1.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)
• skewer/riscv64 (0.2.2-6 to 0.2.2-6)
  • Migration status for skewer/riscv64 (0.2.2-6 to 0.2.2-6): 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)
• skycat/riscv64 (3.1.2+starlink1~b+dfsg-7 to 3.1.2+starlink1~b+dfsg-7)
  • Migration status for skycat/riscv64 (3.1.2+starlink1~b+dfsg-7 to 3.1.2+starlink1~b+dfsg-7): Will attempt migration (Any information below is purely informational)
• sleuthkit/riscv64 (4.12.1+dfsg-2 to 4.12.1+dfsg-2)
  • Migration status for sleuthkit/riscv64 (4.12.1+dfsg-2 to 4.12.1+dfsg-2): Will attempt migration (Any information below is purely informational)
• slicot/riscv64 (5.9-1 to 5.9-1)
  • Migration status for slicot/riscv64 (5.9-1 to 5.9-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)
• slony1-2/riscv64 (2.2.11-3 to 2.2.11-3)
  • Migration status for slony1-2/riscv64 (2.2.11-3 to 2.2.11-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)
• slowhttptest/riscv64 (1.9.0-1 to 1.9.0-1)
  • Migration status for slowhttptest/riscv64 (1.9.0-1 to 1.9.0-1): 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)
• sm/riscv64 (2.2-6.0-1 to 2.2-6.0-1)
  • Migration status for sm/riscv64 (2.2-6.0-1 to 2.2-6.0-1): Will attempt migration (Any information below is purely informational)
• smartmontools/riscv64 (7.4-2 to 7.4-2)
  • Migration status for smartmontools/riscv64 (7.4-2 to 7.4-2): 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)
• smbnetfs/riscv64 (0.6.3-1 to 0.6.3-1)
  • Migration status for smbnetfs/riscv64 (0.6.3-1 to 0.6.3-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)
• smpq/riscv64 (1.6-2 to 1.6-2)
  • Migration status for smpq/riscv64 (1.6-2 to 1.6-2): Will attempt migration (Any information below is purely informational)
• smtpping/riscv64 (1.1.4-1 to 1.1.4-1)
  • Migration status for smtpping/riscv64 (1.1.4-1 to 1.1.4-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)
• snacc/riscv64 (1.3.1-10 to 1.3.1-10)
  • Migration status for snacc/riscv64 (1.3.1-10 to 1.3.1-10): Will attempt migration (Any information below is purely informational)
• snap-aligner/riscv64 (2.0.3+dfsg-2 to 2.0.3+dfsg-2)
  • Migration status for snap-aligner/riscv64 (2.0.3+dfsg-2 to 2.0.3+dfsg-2): 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)
• snapper/riscv64 (0.10.6-1.1 to 0.10.6-1.1)
  • Migration status for snapper/riscv64 (0.10.6-1.1 to 0.10.6-1.1): Will attempt migration (Any information below is purely informational)
• snappy-java/riscv64 (1.1.10.5-2 to 1.1.10.5-2)
  • Migration status for snappy-java/riscv64 (1.1.10.5-2 to 1.1.10.5-2): Will attempt migration (Any information below is purely informational)
• snappy-tools/riscv64 (1-1 to 1-1)
  • Migration status for snappy-tools/riscv64 (1-1 to 1-1): Will attempt migration (Any information below is purely informational)
• sndfile-tools/riscv64 (1.5-3 to 1.5-3)
  • Migration status for sndfile-tools/riscv64 (1.5-3 to 1.5-3): Will attempt migration (Any information below is purely informational)
• sndobj/riscv64 (2.6.7+ds1-4 to 2.6.7+ds1-4)
  • Migration status for sndobj/riscv64 (2.6.7+ds1-4 to 2.6.7+ds1-4): Will attempt migration (Any information below is purely informational)
• snimpy/riscv64 (1.0.0-1 to 1.0.0-1)
  • Migration status for snimpy/riscv64 (1.0.0-1 to 1.0.0-1): Will attempt migration (Any information below is purely informational)
• snpomatic/riscv64 (1.0-7 to 1.0-7)
  • Migration status for snpomatic/riscv64 (1.0-7 to 1.0-7): Will attempt migration (Any information below is purely informational)
• soapsnp/riscv64 (1.03-5 to 1.03-5)
  • Migration status for soapsnp/riscv64 (1.03-5 to 1.03-5): Will attempt migration (Any information below is purely informational)
• soapyairspy/riscv64 (0.2.0-4 to 0.2.0-4)
  • Migration status for soapyairspy/riscv64 (0.2.0-4 to 0.2.0-4): Will attempt migration (Any information below is purely informational)
• soapybladerf/riscv64 (0.4.1-5 to 0.4.1-5)
  • Migration status for soapybladerf/riscv64 (0.4.1-5 to 0.4.1-5): Will attempt migration (Any information below is purely informational)
• soapyhackrf/riscv64 (0.3.4-1 to 0.3.4-1)
  • Migration status for soapyhackrf/riscv64 (0.3.4-1 to 0.3.4-1): Will attempt migration (Any information below is purely informational)
• soapyosmo/riscv64 (0.2.5-8 to 0.2.5-8)
  • Migration status for soapyosmo/riscv64 (0.2.5-8 to 0.2.5-8): Will attempt migration (Any information below is purely informational)
• soapyredpitaya/riscv64 (0.1.1-5 to 0.1.1-5)
  • Migration status for soapyredpitaya/riscv64 (0.1.1-5 to 0.1.1-5): Will attempt migration (Any information below is purely informational)
• soapyremote/riscv64 (0.5.2-4 to 0.5.2-4)
  • Migration status for soapyremote/riscv64 (0.5.2-4 to 0.5.2-4): Will attempt migration (Any information below is purely informational)
• soapyrtlsdr/riscv64 (0.3.3-1 to 0.3.3-1)
  • Migration status for soapyrtlsdr/riscv64 (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• soapyuhd/riscv64 (0.4.1-4 to 0.4.1-4)
  • Migration status for soapyuhd/riscv64 (0.4.1-4 to 0.4.1-4): Will attempt migration (Any information below is purely informational)
• soci/riscv64 (4.0.3-1 to 4.0.3-1)
  • Migration status for soci/riscv64 (4.0.3-1 to 4.0.3-1): Will attempt migration (Any information below is purely informational)
• socket++/riscv64 (1.12.13+git20131030.5d039ba-1 to 1.12.13+git20131030.5d039ba-1)
  • Migration status for socket++/riscv64 (1.12.13+git20131030.5d039ba-1 to 1.12.13+git20131030.5d039ba-1): Will attempt migration (Any information below is purely informational)
• sockperf/riscv64 (3.7-1 to 3.7-1)
  • Migration status for sockperf/riscv64 (3.7-1 to 3.7-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)
• softhsm2/riscv64 (2.6.1-2.2 to 2.6.1-2.2)
  • Migration status for softhsm2/riscv64 (2.6.1-2.2 to 2.6.1-2.2): Will attempt migration (Any information below is purely informational)
• solarpowerlog/riscv64 (0.25-2 to 0.25-2)
  • Migration status for solarpowerlog/riscv64 (0.25-2 to 0.25-2): 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)
• sope/riscv64 (5.10.0-1 to 5.10.0-1)
  • Migration status for sope/riscv64 (5.10.0-1 to 5.10.0-1): Will attempt migration (Any information below is purely informational)
• sopt/riscv64 (3.0.1+dfsg-3.1 to 3.0.1+dfsg-3.1)
  • Migration status for sopt/riscv64 (3.0.1+dfsg-3.1 to 3.0.1+dfsg-3.1): 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)
• sorted-nearest/riscv64 (0.0.39+dfsg-2 to 0.0.39+dfsg-2)
  • Migration status for sorted-nearest/riscv64 (0.0.39+dfsg-2 to 0.0.39+dfsg-2): 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)
• soundkonverter/riscv64 (3.0.1-3 to 3.0.1-3)
  • Migration status for soundkonverter/riscv64 (3.0.1-3 to 3.0.1-3): 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)
• soundscaperenderer/riscv64 (0.6.1+dfsg-1 to 0.6.1+dfsg-1)
  • Migration status for soundscaperenderer/riscv64 (0.6.1+dfsg-1 to 0.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• soundtouch/riscv64 (2.3.3+ds-1 to 2.3.3+ds-1)
  • Migration status for soundtouch/riscv64 (2.3.3+ds-1 to 2.3.3+ds-1): Will attempt migration (Any information below is purely informational)
• source-highlight/riscv64 (3.1.9-4.3 to 3.1.9-4.3)
  • Migration status for source-highlight/riscv64 (3.1.9-4.3 to 3.1.9-4.3): Will attempt migration (Any information below is purely informational)
• sox/riscv64 (14.4.2+git20190427-4 to 14.4.2+git20190427-4)
  • Migration status for sox/riscv64 (14.4.2+git20190427-4 to 14.4.2+git20190427-4): Will attempt migration (Any information below is purely informational)
• sp800-90b-entropy-assessment/riscv64 (1.1.5-4 to 1.1.5-4)
  • Migration status for sp800-90b-entropy-assessment/riscv64 (1.1.5-4 to 1.1.5-4): 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)
• spaced/riscv64 (1.2.0-201605+dfsg-4 to 1.2.0-201605+dfsg-4)
  • Migration status for spaced/riscv64 (1.2.0-201605+dfsg-4 to 1.2.0-201605+dfsg-4): Will attempt migration (Any information below is purely informational)
• spacefm/riscv64 (1.0.6-7 to 1.0.6-7)
  • Migration status for spacefm/riscv64 (1.0.6-7 to 1.0.6-7): Will attempt migration (Any information below is purely informational)
• spaln/riscv64 (3.0.2+dfsg-2 to 3.0.2+dfsg-2)
  • Migration status for spaln/riscv64 (3.0.2+dfsg-2 to 3.0.2+dfsg-2): Will attempt migration (Any information below is purely informational)
• spamass-milter/riscv64 (0.4.0-2 to 0.4.0-2)
  • Migration status for spamass-milter/riscv64 (0.4.0-2 to 0.4.0-2): Will attempt migration (Any information below is purely informational)
• spamprobe/riscv64 (1.4d-17 to 1.4d-17)
  • Migration status for spamprobe/riscv64 (1.4d-17 to 1.4d-17): Will attempt migration (Any information below is purely informational)
• spandsp/riscv64 (0.0.6+dfsg-2.1 to 0.0.6+dfsg-2.1)
  • Migration status for spandsp/riscv64 (0.0.6+dfsg-2.1 to 0.0.6+dfsg-2.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)
• sparskit/riscv64 (2.0.0-5 to 2.0.0-5)
  • Migration status for sparskit/riscv64 (2.0.0-5 to 2.0.0-5): 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)
• spd/riscv64 (1.3.0-1.1 to 1.3.0-1.1)
  • Migration status for spd/riscv64 (1.3.0-1.1 to 1.3.0-1.1): Will attempt migration (Any information below is purely informational)
• spdlog/riscv64 (1:1.12.0+ds-2 to 1:1.12.0+ds-2)
  • Migration status for spdlog/riscv64 (1:1.12.0+ds-2 to 1:1.12.0+ds-2): Will attempt migration (Any information below is purely informational)
• speech-dispatcher/riscv64 (0.11.5-4 to 0.11.5-4)
  • Migration status for speech-dispatcher/riscv64 (0.11.5-4 to 0.11.5-4): Will attempt migration (Any information below is purely informational)
• speech-tools/riscv64 (1:2.5.0-13 to 1:2.5.0-13)
  • Migration status for speech-tools/riscv64 (1:2.5.0-13 to 1:2.5.0-13): Will attempt migration (Any information below is purely informational)
• speechd-up/riscv64 (0.5~20110719-15 to 0.5~20110719-15)
  • Migration status for speechd-up/riscv64 (0.5~20110719-15 to 0.5~20110719-15): Will attempt migration (Any information below is purely informational)
• spew/riscv64 (1.0.8-1.2 to 1.0.8-1.2)
  • Migration status for spew/riscv64 (1.0.8-1.2 to 1.0.8-1.2): Will attempt migration (Any information below is purely informational)
• spglib/riscv64 (2.4.0-1 to 2.4.0-1)
  • Migration status for spglib/riscv64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
• spherepack/riscv64 (3.3~a1-5.1 to 3.3~a1-5.1)
  • Migration status for spherepack/riscv64 (3.3~a1-5.1 to 3.3~a1-5.1): Will attempt migration (Any information below is purely informational)
• sphinxbase/riscv64 (0.8+5prealpha+1-17 to 0.8+5prealpha+1-17)
  • Migration status for sphinxbase/riscv64 (0.8+5prealpha+1-17 to 0.8+5prealpha+1-17): Will attempt migration (Any information below is purely informational)
• sphinxsearch/riscv64 (2.2.11-8 to 2.2.11-8)
  • Migration status for sphinxsearch/riscv64 (2.2.11-8 to 2.2.11-8): Will attempt migration (Any information below is purely informational)
• sphinxtrain/riscv64 (1.0.8+5prealpha+1-6 to 1.0.8+5prealpha+1-6)
  • Migration status for sphinxtrain/riscv64 (1.0.8+5prealpha+1-6 to 1.0.8+5prealpha+1-6): 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)
• spigot/riscv64 (0.2017-01-15.gdad1bbc6-1 to 0.2017-01-15.gdad1bbc6-1)
  • Migration status for spigot/riscv64 (0.2017-01-15.gdad1bbc6-1 to 0.2017-01-15.gdad1bbc6-1): Will attempt migration (Any information below is purely informational)
• spirv-cross/riscv64 (2021.01.15+1.3.239.0-1 to 2021.01.15+1.3.239.0-1)
  • Migration status for spirv-cross/riscv64 (2021.01.15+1.3.239.0-1 to 2021.01.15+1.3.239.0-1): Will attempt migration (Any information below is purely informational)
• splash/riscv64 (3.10.1-2 to 3.10.1-2)
  • Migration status for splash/riscv64 (3.10.1-2 to 3.10.1-2): Will attempt migration (Any information below is purely informational)
• splat/riscv64 (1.4.2-3 to 1.4.2-3)
  • Migration status for splat/riscv64 (1.4.2-3 to 1.4.2-3): Will attempt migration (Any information below is purely informational)
• splay/riscv64 (0.9.5.2-14 to 0.9.5.2-14)
  • Migration status for splay/riscv64 (0.9.5.2-14 to 0.9.5.2-14): Will attempt migration (Any information below is purely informational)
• splix/riscv64 (2.0.0+svn315-7 to 2.0.0+svn315-7)
  • Migration status for splix/riscv64 (2.0.0+svn315-7 to 2.0.0+svn315-7): Will attempt migration (Any information below is purely informational)
• spoa/riscv64 (4.1.4-1 to 4.1.4-1)
  • Migration status for spoa/riscv64 (4.1.4-1 to 4.1.4-1): Will attempt migration (Any information below is purely informational)
• spooles/riscv64 (2.2-14.1 to 2.2-14.1)
  • Migration status for spooles/riscv64 (2.2-14.1 to 2.2-14.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)
• sprai/riscv64 (0.9.9.23+dfsg1-2 to 0.9.9.23+dfsg1-2)
  • Migration status for sprai/riscv64 (0.9.9.23+dfsg1-2 to 0.9.9.23+dfsg1-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)
• sprng/riscv64 (2.0a-13 to 2.0a-13)
  • Migration status for sprng/riscv64 (2.0a-13 to 2.0a-13): Will attempt migration (Any information below is purely informational)
• sqlitebrowser/riscv64 (3.12.2-3 to 3.12.2-3)
  • Migration status for sqlitebrowser/riscv64 (3.12.2-3 to 3.12.2-3): 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)
• sqlsmith/riscv64 (1.4-1 to 1.4-1)
  • Migration status for sqlsmith/riscv64 (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• squidview/riscv64 (0.86-1 to 0.86-1)
  • Migration status for squidview/riscv64 (0.86-1 to 0.86-1): Will attempt migration (Any information below is purely informational)
• srain/riscv64 (1.5.1-1 to 1.5.1-1)
  • Migration status for srain/riscv64 (1.5.1-1 to 1.5.1-1): Will attempt migration (Any information below is purely informational)
• srecord/riscv64 (1.64-4.1 to 1.64-4.1)
  • Migration status for srecord/riscv64 (1.64-4.1 to 1.64-4.1): Will attempt migration (Any information below is purely informational)
• srg/riscv64 (1.3.6-2.1 to 1.3.6-2.1)
  • Migration status for srg/riscv64 (1.3.6-2.1 to 1.3.6-2.1): Will attempt migration (Any information below is purely informational)
• srm-ifce/riscv64 (1.24.6-2 to 1.24.6-2)
  • Migration status for srm-ifce/riscv64 (1.24.6-2 to 1.24.6-2): Will attempt migration (Any information below is purely informational)
• srt/riscv64 (1.5.3-1 to 1.5.3-1)
  • Migration status for srt/riscv64 (1.5.3-1 to 1.5.3-1): Will attempt migration (Any information below is purely informational)
• ssdeep/riscv64 (2.14.1+git20180629.57fcfff-3 to 2.14.1+git20180629.57fcfff-3)
  • Migration status for ssdeep/riscv64 (2.14.1+git20180629.57fcfff-3 to 2.14.1+git20180629.57fcfff-3): 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)
• sslsniff/riscv64 (0.8-9 to 0.8-9)
  • Migration status for sslsniff/riscv64 (0.8-9 to 0.8-9): Will attempt migration (Any information below is purely informational)
• ssvnc/riscv64 (1.0.29-6 to 1.0.29-6)
  • Migration status for ssvnc/riscv64 (1.0.29-6 to 1.0.29-6): Will attempt migration (Any information below is purely informational)
• stacer/riscv64 (1.1.0+ds-2 to 1.1.0+ds-2)
  • Migration status for stacer/riscv64 (1.1.0+ds-2 to 1.1.0+ds-2): Will attempt migration (Any information below is purely informational)
• stacks/riscv64 (2.66+dfsg-1 to 2.66+dfsg-1)
  • Migration status for stacks/riscv64 (2.66+dfsg-1 to 2.66+dfsg-1): Will attempt migration (Any information below is purely informational)
• staden/riscv64 (2.0.0+b11-5 to 2.0.0+b11-5)
  • Migration status for staden/riscv64 (2.0.0+b11-5 to 2.0.0+b11-5): Will attempt migration (Any information below is purely informational)
• starfighter/riscv64 (2.4-1 to 2.4-1)
  • Migration status for starfighter/riscv64 (2.4-1 to 2.4-1): Will attempt migration (Any information below is purely informational)
• statsmodels/riscv64 (0.14.2+dfsg-1 to 0.14.2+dfsg-1)
  • Migration status for statsmodels/riscv64 (0.14.2+dfsg-1 to 0.14.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• stax/riscv64 (1.37-2 to 1.37-2)
  • Migration status for stax/riscv64 (1.37-2 to 1.37-2): Will attempt migration (Any information below is purely informational)
• stdgpu/riscv64 (1.3.0+git20220507.32e0517-6 to 1.3.0+git20220507.32e0517-6)
  • Migration status for stdgpu/riscv64 (1.3.0+git20220507.32e0517-6 to 1.3.0+git20220507.32e0517-6): Will attempt migration (Any information below is purely informational)
• ste-plugins/riscv64 (0.0.2-7 to 0.0.2-7)
  • Migration status for ste-plugins/riscv64 (0.0.2-7 to 0.0.2-7): Will attempt migration (Any information below is purely informational)
• stealth/riscv64 (4.03.03-1 to 4.03.03-1)
  • Migration status for stealth/riscv64 (4.03.03-1 to 4.03.03-1): Will attempt migration (Any information below is purely informational)
• steghide/riscv64 (0.5.1-15 to 0.5.1-15)
  • Migration status for steghide/riscv64 (0.5.1-15 to 0.5.1-15): Will attempt migration (Any information below is purely informational)
• stegseek/riscv64 (0.6+git20210910.ff677b9-1 to 0.6+git20210910.ff677b9-1)
  • Migration status for stegseek/riscv64 (0.6+git20210910.ff677b9-1 to 0.6+git20210910.ff677b9-1): Will attempt migration (Any information below is purely informational)
• stella/riscv64 (6.7.1+dfsg-1 to 6.7.1+dfsg-1)
  • Migration status for stella/riscv64 (6.7.1+dfsg-1 to 6.7.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• stellarsolver/riscv64 (2.5-2 to 2.5-2)
  • Migration status for stellarsolver/riscv64 (2.5-2 to 2.5-2): Will attempt migration (Any information below is purely informational)
• stenc/riscv64 (1.0.7-2 to 1.0.7-2)
  • Migration status for stenc/riscv64 (1.0.7-2 to 1.0.7-2): Will attempt migration (Any information below is purely informational)
• 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)
• stfl/riscv64 (0.22-3 to 0.22-3)
  • Migration status for stfl/riscv64 (0.22-3 to 0.22-3): Will attempt migration (Any information below is purely informational)
• stiff/riscv64 (2.4.0-7 to 2.4.0-7)
  • Migration status for stiff/riscv64 (2.4.0-7 to 2.4.0-7): Will attempt migration (Any information below is purely informational)
• stlcmd/riscv64 (1.1-1 to 1.1-1)
  • Migration status for stlcmd/riscv64 (1.1-1 to 1.1-1): Will attempt migration (Any information below is purely informational)
• stlink/riscv64 (1.8.0-1 to 1.8.0-1)
  • Migration status for stlink/riscv64 (1.8.0-1 to 1.8.0-1): Will attempt migration (Any information below is purely informational)
• stockfish/riscv64 (16-1 to 16-1)
  • Migration status for stockfish/riscv64 (16-1 to 16-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)
• stopt/riscv64 (5.8+dfsg-1.1 to 5.8+dfsg-1.1)
  • Migration status for stopt/riscv64 (5.8+dfsg-1.1 to 5.8+dfsg-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)
• stormlib/riscv64 (9.22-1 to 9.22-1)
  • Migration status for stormlib/riscv64 (9.22-1 to 9.22-1): Will attempt migration (Any information below is purely informational)
• strawberry/riscv64 (1.0.23-1 to 1.0.23-1)
  • Migration status for strawberry/riscv64 (1.0.23-1 to 1.0.23-1): Will attempt migration (Any information below is purely informational)
• stressapptest/riscv64 (1.0.11-2 to 1.0.11-2)
  • Migration status for stressapptest/riscv64 (1.0.11-2 to 1.0.11-2): 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)
• stringtie/riscv64 (2.2.1+ds-3 to 2.2.1+ds-3)
  • Migration status for stringtie/riscv64 (2.2.1+ds-3 to 2.2.1+ds-3): Will attempt migration (Any information below is purely informational)
• strucchange/riscv64 (1.5-3-1 to 1.5-3-1)
  • Migration status for strucchange/riscv64 (1.5-3-1 to 1.5-3-1): 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)
• stun/riscv64 (0.97~dfsg-3 to 0.97~dfsg-3)
  • Migration status for stun/riscv64 (0.97~dfsg-3 to 0.97~dfsg-3): Will attempt migration (Any information below is purely informational)
• stymulator/riscv64 (0.21a~dfsg-4 to 0.21a~dfsg-4)
  • Migration status for stymulator/riscv64 (0.21a~dfsg-4 to 0.21a~dfsg-4): Will attempt migration (Any information below is purely informational)
• subnetcalc/riscv64 (2.4.23-1 to 2.4.23-1)
  • Migration status for subnetcalc/riscv64 (2.4.23-1 to 2.4.23-1): 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)
• subtle/riscv64 (0.11.3224-xi-2.2 to 0.11.3224-xi-2.2)
  • Migration status for subtle/riscv64 (0.11.3224-xi-2.2 to 0.11.3224-xi-2.2): Will attempt migration (Any information below is purely informational)
• subunit/riscv64 (1.4.2-3 to 1.4.2-3)
  • Migration status for subunit/riscv64 (1.4.2-3 to 1.4.2-3): 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)
• suitesparse-graphblas/riscv64 (7.4.0+dfsg-1 to 7.4.0+dfsg-1)
  • Migration status for suitesparse-graphblas/riscv64 (7.4.0+dfsg-1 to 7.4.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• sumaclust/riscv64 (1.0.36+ds-2 to 1.0.36+ds-2)
  • Migration status for sumaclust/riscv64 (1.0.36+ds-2 to 1.0.36+ds-2): 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)
• sunpinyin/riscv64 (3.0.0~rc2+ds1-5 to 3.0.0~rc2+ds1-5)
  • Migration status for sunpinyin/riscv64 (3.0.0~rc2+ds1-5 to 3.0.0~rc2+ds1-5): Will attempt migration (Any information below is purely informational)
• sup-mail/riscv64 (1.1-1 to 1.1-1)
  • Migration status for sup-mail/riscv64 (1.1-1 to 1.1-1): 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)
• superlu/riscv64 (6.0.1+dfsg1-1 to 6.0.1+dfsg1-1)
  • Migration status for superlu/riscv64 (6.0.1+dfsg1-1 to 6.0.1+dfsg1-1): Will attempt migration (Any information below is purely informational)
• supermin/riscv64 (5.2.2-4 to 5.2.2-4)
  • Migration status for supermin/riscv64 (5.2.2-4 to 5.2.2-4): 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)
• supertuxkart/riscv64 (1.4+dfsg-4 to 1.4+dfsg-4)
  • Migration status for supertuxkart/riscv64 (1.4+dfsg-4 to 1.4+dfsg-4): Will attempt migration (Any information below is purely informational)
• surf-alggeo/riscv64 (1.0.6+ds-7 to 1.0.6+ds-7)
  • Migration status for surf-alggeo/riscv64 (1.0.6+ds-7 to 1.0.6+ds-7): 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)
• survivor/riscv64 (1.0.7-4 to 1.0.7-4)
  • Migration status for survivor/riscv64 (1.0.7-4 to 1.0.7-4): 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)
• swath/riscv64 (0.6.1-3 to 0.6.1-3)
  • Migration status for swath/riscv64 (0.6.1-3 to 0.6.1-3): Will attempt migration (Any information below is purely informational)
• sway/riscv64 (1.9-1 to 1.9-1)
  • Migration status for sway/riscv64 (1.9-1 to 1.9-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)
• swaylock/riscv64 (1.7.2-1 to 1.7.2-1)
  • Migration status for swaylock/riscv64 (1.7.2-1 to 1.7.2-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)
• swh-plugins/riscv64 (0.4.17-3 to 0.4.17-3)
  • Migration status for swh-plugins/riscv64 (0.4.17-3 to 0.4.17-3): 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)
• swig/riscv64 (4.2.1-1 to 4.2.1-1)
  • Migration status for swig/riscv64 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• swiglpk/riscv64 (5.0.10-1 to 5.0.10-1)
  • Migration status for swiglpk/riscv64 (5.0.10-1 to 5.0.10-1): Will attempt migration (Any information below is purely informational)
• swish++/riscv64 (6.1.5-6 to 6.1.5-6)
  • Migration status for swish++/riscv64 (6.1.5-6 to 6.1.5-6): 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)
• sword/riscv64 (1.9.0+dfsg-6 to 1.9.0+dfsg-6)
  • Migration status for sword/riscv64 (1.9.0+dfsg-6 to 1.9.0+dfsg-6): Will attempt migration (Any information below is purely informational)
• swt4-gtk/riscv64 (4.26.0-2 to 4.26.0-2)
  • Migration status for swt4-gtk/riscv64 (4.26.0-2 to 4.26.0-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)
• sylfilter/riscv64 (0.8-7 to 0.8-7)
  • Migration status for sylfilter/riscv64 (0.8-7 to 0.8-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)
• sylpheed/riscv64 (3.8.0~beta1-1 to 3.8.0~beta1-1)
  • Migration status for sylpheed/riscv64 (3.8.0~beta1-1 to 3.8.0~beta1-1): Will attempt migration (Any information below is purely informational)
• sympa/riscv64 (6.2.70~dfsg-2 to 6.2.70~dfsg-2)
  • Migration status for sympa/riscv64 (6.2.70~dfsg-2 to 6.2.70~dfsg-2): 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)
• synphot/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for synphot/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• synthv1/riscv64 (0.9.90-1 to 0.9.90-1)
  • Migration status for synthv1/riscv64 (0.9.90-1 to 0.9.90-1): Will attempt migration (Any information below is purely informational)
• syslog-ng/riscv64 (4.4.0-1 to 4.4.0-1)
  • Migration status for syslog-ng/riscv64 (4.4.0-1 to 4.4.0-1): Will attempt migration (Any information below is purely informational)
• syslog-ocaml/riscv64 (2.0.2-4 to 2.0.2-4)
  • Migration status for syslog-ocaml/riscv64 (2.0.2-4 to 2.0.2-4): Will attempt migration (Any information below is purely informational)
• systempreferences.app/riscv64 (1.2.0-2 to 1.2.0-2)
  • Migration status for systempreferences.app/riscv64 (1.2.0-2 to 1.2.0-2): Will attempt migration (Any information below is purely informational)
• t-coffee/riscv64 (13.45.0.4846264+really13.41.0.28bdc39+dfsg-1 to 13.45.0.4846264+really13.41.0.28bdc39+dfsg-1)
  • Migration status for t-coffee/riscv64 (13.45.0.4846264+really13.41.0.28bdc39+dfsg-1 to 13.45.0.4846264+really13.41.0.28bdc39+dfsg-1): Will attempt migration (Any information below is purely informational)
• t2n/riscv64 (0.7-1 to 0.7-1)
  • Migration status for t2n/riscv64 (0.7-1 to 0.7-1): Will attempt migration (Any information below is purely informational)
• t4kcommon/riscv64 (0.1.1-11.2 to 0.1.1-11.2)
  • Migration status for t4kcommon/riscv64 (0.1.1-11.2 to 0.1.1-11.2): 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)
• taglib/riscv64 (1.13.1-1 to 1.13.1-1)
  • Migration status for taglib/riscv64 (1.13.1-1 to 1.13.1-1): Will attempt migration (Any information below is purely informational)
• tagpy/riscv64 (2022.1-1 to 2022.1-1)
  • Migration status for tagpy/riscv64 (2022.1-1 to 2022.1-1): 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)
• tandem-mass/riscv64 (1:201702011-1 to 1:201702011-1)
  • Migration status for tandem-mass/riscv64 (1:201702011-1 to 1:201702011-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)
• tantan/riscv64 (49-2 to 49-2)
  • Migration status for tantan/riscv64 (49-2 to 49-2): 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)
• taptempo/riscv64 (1.4.5-1 to 1.4.5-1)
  • Migration status for taptempo/riscv64 (1.4.5-1 to 1.4.5-1): Will attempt migration (Any information below is purely informational)
• tardy/riscv64 (1.25-3 to 1.25-3)
  • Migration status for tardy/riscv64 (1.25-3 to 1.25-3): Will attempt migration (Any information below is purely informational)
• target-factory/riscv64 (2.5-11.1 to 2.5-11.1)
  • Migration status for target-factory/riscv64 (2.5-11.1 to 2.5-11.1): Will attempt migration (Any information below is purely informational)
• tarlz/riscv64 (0.25-1 to 0.25-1)
  • Migration status for tarlz/riscv64 (0.25-1 to 0.25-1): Will attempt migration (Any information below is purely informational)
• task/riscv64 (2.6.2+dfsg-1 to 2.6.2+dfsg-1)
  • Migration status for task/riscv64 (2.6.2+dfsg-1 to 2.6.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• tasksh/riscv64 (1.2.0-1 to 1.2.0-1)
  • Migration status for tasksh/riscv64 (1.2.0-1 to 1.2.0-1): 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)
• tclcl/riscv64 (1.20-10 to 1.20-10)
  • Migration status for tclcl/riscv64 (1.20-10 to 1.20-10): Will attempt migration (Any information below is purely informational)
• tclodbc/riscv64 (2.5.1-2 to 2.5.1-2)
  • Migration status for tclodbc/riscv64 (2.5.1-2 to 2.5.1-2): Will attempt migration (Any information below is purely informational)
• tclxml/riscv64 (1:3.2.7-7 to 1:3.2.7-7)
  • Migration status for tclxml/riscv64 (1:3.2.7-7 to 1:3.2.7-7): Will attempt migration (Any information below is purely informational)
• tcm/riscv64 (2.20+TSQD-7 to 2.20+TSQD-7)
  • Migration status for tcm/riscv64 (2.20+TSQD-7 to 2.20+TSQD-7): Will attempt migration (Any information below is purely informational)
• tcmu/riscv64 (1.5.4-9 to 1.5.4-9)
  • Migration status for tcmu/riscv64 (1.5.4-9 to 1.5.4-9): Will attempt migration (Any information below is purely informational)
• tcpflow/riscv64 (1.6.1-3 to 1.6.1-3)
  • Migration status for tcpflow/riscv64 (1.6.1-3 to 1.6.1-3): Will attempt migration (Any information below is purely informational)
• tcpreen/riscv64 (1.4.4-2.1 to 1.4.4-2.1)
  • Migration status for tcpreen/riscv64 (1.4.4-2.1 to 1.4.4-2.1): Will attempt migration (Any information below is purely informational)
• tcptrack/riscv64 (1.4.3-2 to 1.4.3-2)
  • Migration status for tcptrack/riscv64 (1.4.3-2 to 1.4.3-2): 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)
• tea/riscv64 (62.0.2-1 to 62.0.2-1)
  • Migration status for tea/riscv64 (62.0.2-1 to 62.0.2-1): Will attempt migration (Any information below is purely informational)
• teckit/riscv64 (2.5.12+ds1-1 to 2.5.12+ds1-1)
  • Migration status for teckit/riscv64 (2.5.12+ds1-1 to 2.5.12+ds1-1): Will attempt migration (Any information below is purely informational)
• tecla/riscv64 (46.0-1 to 46.0-1)
  • Migration status for tecla/riscv64 (46.0-1 to 46.0-1): Will attempt migration (Any information below is purely informational)
• tecnoballz/riscv64 (0.93.1-10 to 0.93.1-10)
  • Migration status for tecnoballz/riscv64 (0.93.1-10 to 0.93.1-10): 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)
• teg/riscv64 (0.12.0-2 to 0.12.0-2)
  • Migration status for teg/riscv64 (0.12.0-2 to 0.12.0-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-haze/riscv64 (0.8.1-0.1 to 0.8.1-0.1)
  • Migration status for telepathy-haze/riscv64 (0.8.1-0.1 to 0.8.1-0.1): Will attempt migration (Any information below is purely informational)
• telepathy-logger-qt/riscv64 (17.09.0-1 to 17.09.0-1)
  • Migration status for telepathy-logger-qt/riscv64 (17.09.0-1 to 17.09.0-1): Will attempt migration (Any information below is purely informational)
• telepathy-logger/riscv64 (0.8.2-4 to 0.8.2-4)
  • Migration status for telepathy-logger/riscv64 (0.8.2-4 to 0.8.2-4): 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)
• tenmado/riscv64 (0.10-5 to 0.10-5)
  • Migration status for tenmado/riscv64 (0.10-5 to 0.10-5): Will attempt migration (Any information below is purely informational)
• tennix/riscv64 (1.3.4-0.1 to 1.3.4-0.1)
  • Migration status for tennix/riscv64 (1.3.4-0.1 to 1.3.4-0.1): Will attempt migration (Any information below is purely informational)
• tensorpipe/riscv64 (0.0~git20220513.bb1473a-5 to 0.0~git20220513.bb1473a-5)
  • Migration status for tensorpipe/riscv64 (0.0~git20220513.bb1473a-5 to 0.0~git20220513.bb1473a-5): 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)
• termdebug/riscv64 (2.2+dfsg-1 to 2.2+dfsg-1)
  • Migration status for termdebug/riscv64 (2.2+dfsg-1 to 2.2+dfsg-1): 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)
• terminus/riscv64 (2.3.1-1 to 2.3.1-1)
  • Migration status for terminus/riscv64 (2.3.1-1 to 2.3.1-1): 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)
• termpaint/riscv64 (0.3.0-3 to 0.3.0-3)
  • Migration status for termpaint/riscv64 (0.3.0-3 to 0.3.0-3): Will attempt migration (Any information below is purely informational)
• termshark/riscv64 (2.4.0-1 to 2.4.0-1)
  • Migration status for termshark/riscv64 (2.4.0-1 to 2.4.0-1): Will attempt migration (Any information below is purely informational)
• terraphast/riscv64 (0.0+git20200413.8af2e4c+dfsg-3 to 0.0+git20200413.8af2e4c+dfsg-3)
  • Migration status for terraphast/riscv64 (0.0+git20200413.8af2e4c+dfsg-3 to 0.0+git20200413.8af2e4c+dfsg-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)
• tetgen/riscv64 (1.5.0-5 to 1.5.0-5)
  • Migration status for tetgen/riscv64 (1.5.0-5 to 1.5.0-5): Will attempt migration (Any information below is purely informational)
• tetraproc/riscv64 (0.9.2-1 to 0.9.2-1)
  • Migration status for tetraproc/riscv64 (0.9.2-1 to 0.9.2-1): Will attempt migration (Any information below is purely informational)
• tetzle/riscv64 (2.2.3-1.1 to 2.2.3-1.1)
  • Migration status for tetzle/riscv64 (2.2.3-1.1 to 2.2.3-1.1): Will attempt migration (Any information below is purely informational)
• texmaker/riscv64 (5.1.3+dfsg-1 to 5.1.3+dfsg-1)
  • Migration status for texmaker/riscv64 (5.1.3+dfsg-1 to 5.1.3+dfsg-1): Will attempt migration (Any information below is purely informational)
• text-engine/riscv64 (0.1.1-4 to 0.1.1-4)
  • Migration status for text-engine/riscv64 (0.1.1-4 to 0.1.1-4): Will attempt migration (Any information below is purely informational)
• textedit.app/riscv64 (5.0-3 to 5.0-3)
  • Migration status for textedit.app/riscv64 (5.0-3 to 5.0-3): Will attempt migration (Any information below is purely informational)
• tgif/riscv64 (1:4.2.5-1.3 to 1:4.2.5-1.3)
  • Migration status for tgif/riscv64 (1:4.2.5-1.3 to 1:4.2.5-1.3): Will attempt migration (Any information below is purely informational)
• tgt/riscv64 (1:1.0.85-1.2 to 1:1.0.85-1.2)
  • Migration status for tgt/riscv64 (1:1.0.85-1.2 to 1:1.0.85-1.2): Will attempt migration (Any information below is purely informational)
• the/riscv64 (3.3~rc1-3.2 to 3.3~rc1-3.2)
  • Migration status for the/riscv64 (3.3~rc1-3.2 to 3.3~rc1-3.2): Will attempt migration (Any information below is purely informational)
• theme-d/riscv64 (5.1.2-1 to 5.1.2-1)
  • Migration status for theme-d/riscv64 (5.1.2-1 to 5.1.2-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)
• thesias/riscv64 (3.1.1-2 to 3.1.1-2)
  • Migration status for thesias/riscv64 (3.1.1-2 to 3.1.1-2): Will attempt migration (Any information below is purely informational)
• thin/riscv64 (1.8.1-2 to 1.8.1-2)
  • Migration status for thin/riscv64 (1.8.1-2 to 1.8.1-2): 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)
• thunar/riscv64 (4.18.8-1 to 4.18.8-1)
  • Migration status for thunar/riscv64 (4.18.8-1 to 4.18.8-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)
• thunderbolt-tools/riscv64 (0.9.3-7 to 0.9.3-7)
  • Migration status for thunderbolt-tools/riscv64 (0.9.3-7 to 0.9.3-7): Will attempt migration (Any information below is purely informational)
• 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)
• tiddit/riscv64 (3.6.1+dfsg-1 to 3.6.1+dfsg-1)
  • Migration status for tiddit/riscv64 (3.6.1+dfsg-1 to 3.6.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• tideways/riscv64 (5.0.4-16 to 5.0.4-16)
  • Migration status for tideways/riscv64 (5.0.4-16 to 5.0.4-16): Will attempt migration (Any information below is purely informational)
• tiff/riscv64 (4.5.1+git230720-4 to 4.5.1+git230720-4)
  • Migration status for tiff/riscv64 (4.5.1+git230720-4 to 4.5.1+git230720-4): Will attempt migration (Any information below is purely informational)
• tig/riscv64 (2.5.8-1 to 2.5.8-1)
  • Migration status for tig/riscv64 (2.5.8-1 to 2.5.8-1): Will attempt migration (Any information below is purely informational)
• tigr-glimmer/riscv64 (3.02b-6 to 3.02b-6)
  • Migration status for tigr-glimmer/riscv64 (3.02b-6 to 3.02b-6): 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)
• tilde/riscv64 (1.1.2-1 to 1.1.2-1)
  • Migration status for tilde/riscv64 (1.1.2-1 to 1.1.2-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)
• tilem/riscv64 (2.0-5 to 2.0-5)
  • Migration status for tilem/riscv64 (2.0-5 to 2.0-5): Will attempt migration (Any information below is purely informational)
• tilemaker/riscv64 (3.0.0-1 to 3.0.0-1)
  • Migration status for tilemaker/riscv64 (3.0.0-1 to 3.0.0-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)
• timekpr-next/riscv64 (0.5.4-2 to 0.5.4-2)
  • Migration status for timekpr-next/riscv64 (0.5.4-2 to 0.5.4-2): 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)
• timescaledb/riscv64 (2.15.2+dfsg-1 to 2.15.2+dfsg-1)
  • Migration status for timescaledb/riscv64 (2.15.2+dfsg-1 to 2.15.2+dfsg-1): Will attempt migration (Any information below is purely informational)
• timew/riscv64 (1.7.1+ds.1-2 to 1.7.1+ds.1-2)
  • Migration status for timew/riscv64 (1.7.1+ds.1-2 to 1.7.1+ds.1-2): 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)
• tinyexr/riscv64 (1.0.8+dfsg-1 to 1.0.8+dfsg-1)
  • Migration status for tinyexr/riscv64 (1.0.8+dfsg-1 to 1.0.8+dfsg-1): Will attempt migration (Any information below is purely informational)
• tinygltf/riscv64 (2.8.20+dfsg-1 to 2.8.20+dfsg-1)
  • Migration status for tinygltf/riscv64 (2.8.20+dfsg-1 to 2.8.20+dfsg-1): Will attempt migration (Any information below is purely informational)
• tinymux/riscv64 (2.12.0.10-1 to 2.12.0.10-1)
  • Migration status for tinymux/riscv64 (2.12.0.10-1 to 2.12.0.10-1): Will attempt migration (Any information below is purely informational)
• tinyobjloader/riscv64 (2.0.0~rc10+dfsg-3 to 2.0.0~rc10+dfsg-3)
  • Migration status for tinyobjloader/riscv64 (2.0.0~rc10+dfsg-3 to 2.0.0~rc10+dfsg-3): Will attempt migration (Any information below is purely informational)
• tinyxml/riscv64 (2.6.2-6.1 to 2.6.2-6.1)
  • Migration status for tinyxml/riscv64 (2.6.2-6.1 to 2.6.2-6.1): Will attempt migration (Any information below is purely informational)
• tinyxml2/riscv64 (10.0.0+dfsg-2 to 10.0.0+dfsg-2)
  • Migration status for tinyxml2/riscv64 (10.0.0+dfsg-2 to 10.0.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• tipp10/riscv64 (3.3.1-1 to 3.3.1-1)
  • Migration status for tipp10/riscv64 (3.3.1-1 to 3.3.1-1): Will attempt migration (Any information below is purely informational)
• tippecanoe/riscv64 (2.53.0-1 to 2.53.0-1)
  • Migration status for tippecanoe/riscv64 (2.53.0-1 to 2.53.0-1): 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)
• tiv/riscv64 (1.2.1+dfsg-1 to 1.2.1+dfsg-1)
  • Migration status for tiv/riscv64 (1.2.1+dfsg-1 to 1.2.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• tkagif/riscv64 (1.0.5-1 to 1.0.5-1)
  • Migration status for tkagif/riscv64 (1.0.5-1 to 1.0.5-1): Will attempt migration (Any information below is purely informational)
• tkblt/riscv64 (3.2.23-1 to 3.2.23-1)
  • Migration status for tkblt/riscv64 (3.2.23-1 to 3.2.23-1): Will attempt migration (Any information below is purely informational)
• tkmpeg/riscv64 (1.0.10-1 to 1.0.10-1)
  • Migration status for tkmpeg/riscv64 (1.0.10-1 to 1.0.10-1): Will attempt migration (Any information below is purely informational)
• tkrplot/riscv64 (0.0.27-2 to 0.0.27-2)
  • Migration status for tkrplot/riscv64 (0.0.27-2 to 0.0.27-2): Will attempt migration (Any information below is purely informational)
• tlf/riscv64 (1.4.1-327-g7b714df-4 to 1.4.1-327-g7b714df-4)
  • Migration status for tlf/riscv64 (1.4.1-327-g7b714df-4 to 1.4.1-327-g7b714df-4): Will attempt migration (Any information below is purely informational)
• tlsh/riscv64 (3.4.4+20151206-1.4 to 3.4.4+20151206-1.4)
  • Migration status for tlsh/riscv64 (3.4.4+20151206-1.4 to 3.4.4+20151206-1.4): Will attempt migration (Any information below is purely informational)
• tm-align/riscv64 (20190822+dfsg-2 to 20190822+dfsg-2)
  • Migration status for tm-align/riscv64 (20190822+dfsg-2 to 20190822+dfsg-2): Will attempt migration (Any information below is purely informational)
• tmfs/riscv64 (3-2 to 3-2)
  • Migration status for tmfs/riscv64 (3-2 to 3-2): 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)
• tntdb/riscv64 (1.4-1 to 1.4-1)
  • Migration status for tntdb/riscv64 (1.4-1 to 1.4-1): Will attempt migration (Any information below is purely informational)
• tntnet/riscv64 (3.0-3.1 to 3.0-3.1)
  • Migration status for tntnet/riscv64 (3.0-3.1 to 3.0-3.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)
• tofi/riscv64 (0.9.1-2 to 0.9.1-2)
  • Migration status for tofi/riscv64 (0.9.1-2 to 0.9.1-2): Will attempt migration (Any information below is purely informational)
• toilet/riscv64 (0.3-1.4 to 0.3-1.4)
  • Migration status for toilet/riscv64 (0.3-1.4 to 0.3-1.4): Will attempt migration (Any information below is purely informational)
• tokodon/riscv64 (23.04.2-1 to 23.04.2-1)
  • Migration status for tokodon/riscv64 (23.04.2-1 to 23.04.2-1): Will attempt migration (Any information below is purely informational)
• tolua++/riscv64 (1.0.93-5 to 1.0.93-5)
  • Migration status for tolua++/riscv64 (1.0.93-5 to 1.0.93-5): Will attempt migration (Any information below is purely informational)
• tolua/riscv64 (5.2.4-0.1 to 5.2.4-0.1)
  • Migration status for tolua/riscv64 (5.2.4-0.1 to 5.2.4-0.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)
• tombo/riscv64 (1.5.1-6 to 1.5.1-6)
  • Migration status for tombo/riscv64 (1.5.1-6 to 1.5.1-6): Will attempt migration (Any information below is purely informational)
• tome/riscv64 (2.41-ah~0.git.20200131-1.3 to 2.41-ah~0.git.20200131-1.3)
  • Migration status for tome/riscv64 (2.41-ah~0.git.20200131-1.3 to 2.41-ah~0.git.20200131-1.3): Will attempt migration (Any information below is purely informational)
• tomlplusplus/riscv64 (3.4.0+ds-0.2 to 3.4.0+ds-0.2)
  • Migration status for tomlplusplus/riscv64 (3.4.0+ds-0.2 to 3.4.0+ds-0.2): 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)
• toontag/riscv64 (0.0~git20220105193632.41237ef-2.1 to 0.0~git20220105193632.41237ef-2.1)
  • Migration status for toontag/riscv64 (0.0~git20220105193632.41237ef-2.1 to 0.0~git20220105193632.41237ef-2.1): Will attempt migration (Any information below is purely informational)
• topcom/riscv64 (1.1.2+ds-1.1 to 1.1.2+ds-1.1)
  • Migration status for topcom/riscv64 (1.1.2+ds-1.1 to 1.1.2+ds-1.1): Will attempt migration (Any information below is purely informational)
• tophide/riscv64 (1.0.4-5 to 1.0.4-5)
  • Migration status for tophide/riscv64 (1.0.4-5 to 1.0.4-5): 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)
• toppler/riscv64 (1.3-2 to 1.3-2)
  • Migration status for toppler/riscv64 (1.3-2 to 1.3-2): Will attempt migration (Any information below is purely informational)
• toppred/riscv64 (1.10-10 to 1.10-10)
  • Migration status for toppred/riscv64 (1.10-10 to 1.10-10): 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)
• tortoize/riscv64 (2.0.11-1 to 2.0.11-1)
  • Migration status for tortoize/riscv64 (2.0.11-1 to 2.0.11-1): 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)
• toulbar2/riscv64 (1.2.1+dfsg-0.1 to 1.2.1+dfsg-0.1)
  • Migration status for toulbar2/riscv64 (1.2.1+dfsg-0.1 to 1.2.1+dfsg-0.1): Will attempt migration (Any information below is purely informational)
• tpm2-abrmd/riscv64 (3.0.0-1.1 to 3.0.0-1.1)
  • Migration status for tpm2-abrmd/riscv64 (3.0.0-1.1 to 3.0.0-1.1): 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)
• tpm2-pkcs11/riscv64 (1.9.0-0.2 to 1.9.0-0.2)
  • Migration status for tpm2-pkcs11/riscv64 (1.9.0-0.2 to 1.9.0-0.2): Will attempt migration (Any information below is purely informational)
• tpm2-tss-engine/riscv64 (1.2.0-2 to 1.2.0-2)
  • Migration status for tpm2-tss-engine/riscv64 (1.2.0-2 to 1.2.0-2): 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)
• tralics/riscv64 (2.14.4-2.1 to 2.14.4-2.1)
  • Migration status for tralics/riscv64 (2.14.4-2.1 to 2.14.4-2.1): Will attempt migration (Any information below is purely informational)
• 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)
• transcriber/riscv64 (1.5.1.1-10 to 1.5.1.1-10)
  • Migration status for transcriber/riscv64 (1.5.1.1-10 to 1.5.1.1-10): 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)
• transrate-tools/riscv64 (1.0.0-5 to 1.0.0-5)
  • Migration status for transrate-tools/riscv64 (1.0.0-5 to 1.0.0-5): Will attempt migration (Any information below is purely informational)
• transtermhp/riscv64 (2.09-5 to 2.09-5)
  • Migration status for transtermhp/riscv64 (2.09-5 to 2.09-5): 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)
• travis/riscv64 (220729-1 to 220729-1)
  • Migration status for travis/riscv64 (220729-1 to 220729-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)
• tree-puzzle/riscv64 (5.3~rc16+dfsg-9 to 5.3~rc16+dfsg-9)
  • Migration status for tree-puzzle/riscv64 (5.3~rc16+dfsg-9 to 5.3~rc16+dfsg-9): 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)
• treil/riscv64 (1.8-2.2 to 1.8-2.2)
  • Migration status for treil/riscv64 (1.8-2.2 to 1.8-2.2): 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)
• trinculo/riscv64 (0.96+dfsg-4 to 0.96+dfsg-4)
  • Migration status for trinculo/riscv64 (0.96+dfsg-4 to 0.96+dfsg-4): Will attempt migration (Any information below is purely informational)
• trinityrnaseq/riscv64 (2.15.1+dfsg-5 to 2.15.1+dfsg-5)
  • Migration status for trinityrnaseq/riscv64 (2.15.1+dfsg-5 to 2.15.1+dfsg-5): Will attempt migration (Any information below is purely informational)
• triplane/riscv64 (1.0.8-3 to 1.0.8-3)
  • Migration status for triplane/riscv64 (1.0.8-3 to 1.0.8-3): Will attempt migration (Any information below is purely informational)
• tripwire/amd64 (2.4.3.7-5 to 2.4.3.7-5)
  • Migration status for tripwire/amd64 (2.4.3.7-5 to 2.4.3.7-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: tripwire/amd64 gcc-14 (not considered)
    • Invalidated by built-using
• tripwire/arm64 (2.4.3.7-5 to 2.4.3.7-5)
  • Migration status for tripwire/arm64 (2.4.3.7-5 to 2.4.3.7-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: tripwire/arm64 gcc-14 (not considered)
    • Invalidated by built-using
• tripwire/i386 (2.4.3.7-5 to 2.4.3.7-5)
  • Migration status for tripwire/i386 (2.4.3.7-5 to 2.4.3.7-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: tripwire/i386 gcc-14 (not considered)
    • Invalidated by built-using
• tripwire/mips64el (2.4.3.7-5 to 2.4.3.7-5)
  • Migration status for tripwire/mips64el (2.4.3.7-5 to 2.4.3.7-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: tripwire/mips64el gcc-14 (not considered)
    • Invalidated by built-using
• tripwire/ppc64el (2.4.3.7-5 to 2.4.3.7-5)
  • Migration status for tripwire/ppc64el (2.4.3.7-5 to 2.4.3.7-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: tripwire/ppc64el gcc-14 (not considered)
    • Invalidated by built-using
• tripwire/riscv64 (2.4.3.7-5 to 2.4.3.7-5)
  • Migration status for tripwire/riscv64 (2.4.3.7-5 to 2.4.3.7-5): Will attempt migration (Any information below is purely informational)
• tripwire/s390x (2.4.3.7-5 to 2.4.3.7-5)
  • Migration status for tripwire/s390x (2.4.3.7-5 to 2.4.3.7-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: tripwire/s390x gcc-14 (not considered)
    • Invalidated by built-using
• trustedqsl/riscv64 (2.7.3-1 to 2.7.3-1)
  • Migration status for trustedqsl/riscv64 (2.7.3-1 to 2.7.3-1): Will attempt migration (Any information below is purely informational)
• tse3/riscv64 (0.3.1-7 to 0.3.1-7)
  • Migration status for tse3/riscv64 (0.3.1-7 to 0.3.1-7): 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)
• tuba/riscv64 (0.6.3-1 to 0.6.3-1)
  • Migration status for tuba/riscv64 (0.6.3-1 to 0.6.3-1): Will attempt migration (Any information below is purely informational)
• tucnak/riscv64 (4.59-1 to 4.59-1)
  • Migration status for tucnak/riscv64 (4.59-1 to 4.59-1): Will attempt migration (Any information below is purely informational)
• tudu/riscv64 (0.10.4-2 to 0.10.4-2)
  • Migration status for tudu/riscv64 (0.10.4-2 to 0.10.4-2): 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)
• tuxfootball/riscv64 (0.3.1-7 to 0.3.1-7)
  • Migration status for tuxfootball/riscv64 (0.3.1-7 to 0.3.1-7): Will attempt migration (Any information below is purely informational)
• tuxguitar/riscv64 (1.5.6+dfsg1-8 to 1.5.6+dfsg1-8)
  • Migration status for tuxguitar/riscv64 (1.5.6+dfsg1-8 to 1.5.6+dfsg1-8): Will attempt migration (Any information below is purely informational)
• tuxmath/riscv64 (2.0.3-9 to 2.0.3-9)
  • Migration status for tuxmath/riscv64 (2.0.3-9 to 2.0.3-9): Will attempt migration (Any information below is purely informational)
• tuxpaint-config/riscv64 (0.17rc1-1 to 0.17rc1-1)
  • Migration status for tuxpaint-config/riscv64 (0.17rc1-1 to 0.17rc1-1): Will attempt migration (Any information below is purely informational)
• tuxpaint/riscv64 (1:0.9.28-sdl2-1 to 1:0.9.28-sdl2-1)
  • Migration status for tuxpaint/riscv64 (1:0.9.28-sdl2-1 to 1:0.9.28-sdl2-1): Will attempt migration (Any information below is purely informational)
• tuxtype/riscv64 (1.8.3-5.1 to 1.8.3-5.1)
  • Migration status for tuxtype/riscv64 (1.8.3-5.1 to 1.8.3-5.1): Will attempt migration (Any information below is purely informational)
• tvc/riscv64 (5.0.3+git20151221.80e144e+dfsg-5 to 5.0.3+git20151221.80e144e+dfsg-5)
  • Migration status for tvc/riscv64 (5.0.3+git20151221.80e144e+dfsg-5 to 5.0.3+git20151221.80e144e+dfsg-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)
• twm/riscv64 (1:1.0.10-1 to 1:1.0.10-1)
  • Migration status for twm/riscv64 (1:1.0.10-1 to 1:1.0.10-1): Will attempt migration (Any information below is purely informational)
• twopaco/riscv64 (1.0.0+dfsg-1 to 1.0.0+dfsg-1)
  • Migration status for twopaco/riscv64 (1.0.0+dfsg-1 to 1.0.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• twpsk/riscv64 (4.3-1 to 4.3-1)
  • Migration status for twpsk/riscv64 (4.3-1 to 4.3-1): 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)
• typerep/riscv64 (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for typerep/riscv64 (1:0.16.0-2 to 1:0.16.0-2): Will attempt migration (Any information below is purely informational)
• 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)
• u1db-qt/riscv64 (0.1.7-1 to 0.1.7-1)
  • Migration status for u1db-qt/riscv64 (0.1.7-1 to 0.1.7-1): Will attempt migration (Any information below is purely informational)
• ucblogo/riscv64 (6.2.4-1 to 6.2.4-1)
  • Migration status for ucblogo/riscv64 (6.2.4-1 to 6.2.4-1): Will attempt migration (Any information below is purely informational)
• uchardet/riscv64 (0.0.8-1 to 0.0.8-1)
  • Migration status for uchardet/riscv64 (0.0.8-1 to 0.0.8-1): Will attempt migration (Any information below is purely informational)
• ucimf-chewing/riscv64 (0.3-4 to 0.3-4)
  • Migration status for ucimf-chewing/riscv64 (0.3-4 to 0.3-4): Will attempt migration (Any information below is purely informational)
• ucimf-openvanilla/riscv64 (2.10.11-4 to 2.10.11-4)
  • Migration status for ucimf-openvanilla/riscv64 (2.10.11-4 to 2.10.11-4): Will attempt migration (Any information below is purely informational)
• ucimf-sunpinyin/riscv64 (0.5-3 to 0.5-3)
  • Migration status for ucimf-sunpinyin/riscv64 (0.5-3 to 0.5-3): 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)
• ueberzug/riscv64 (18.2.2-1 to 18.2.2-1)
  • Migration status for ueberzug/riscv64 (18.2.2-1 to 18.2.2-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)
• uftrace/riscv64 (0.16-1 to 0.16-1)
  • Migration status for uftrace/riscv64 (0.16-1 to 0.16-1): 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)
• uisp/riscv64 (20050207-4.5 to 20050207-4.5)
  • Migration status for uisp/riscv64 (20050207-4.5 to 20050207-4.5): 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-media/riscv64 (3.1.1.2-1 to 3.1.1.2-1)
  • Migration status for ukui-media/riscv64 (3.1.1.2-1 to 3.1.1.2-1): 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-settings-daemon/riscv64 (3.22.0.1-1 to 3.22.0.1-1)
  • Migration status for ukui-settings-daemon/riscv64 (3.22.0.1-1 to 3.22.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)
• ukwm/riscv64 (1.2.2-1 to 1.2.2-1)
  • Migration status for ukwm/riscv64 (1.2.2-1 to 1.2.2-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)
• ulfius/riscv64 (2.7.15-2.2 to 2.7.15-2.2)
  • Migration status for ulfius/riscv64 (2.7.15-2.2 to 2.7.15-2.2): 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)
• umis/riscv64 (1.0.9-1 to 1.0.9-1)
  • Migration status for umis/riscv64 (1.0.9-1 to 1.0.9-1): Will attempt migration (Any information below is purely informational)
• ums2net/riscv64 (0.1.3-3 to 0.1.3-3)
  • Migration status for ums2net/riscv64 (0.1.3-3 to 0.1.3-3): Will attempt migration (Any information below is purely informational)
• unalz/riscv64 (0.65-9 to 0.65-9)
  • Migration status for unalz/riscv64 (0.65-9 to 0.65-9): Will attempt migration (Any information below is purely informational)
• uncalled/riscv64 (2.3+ds-1 to 2.3+ds-1)
  • Migration status for uncalled/riscv64 (2.3+ds-1 to 2.3+ds-1): Will attempt migration (Any information below is purely informational)
• uncrustify/riscv64 (0.78.1+dfsg1-1 to 0.78.1+dfsg1-1)
  • Migration status for uncrustify/riscv64 (0.78.1+dfsg1-1 to 0.78.1+dfsg1-1): Will attempt migration (Any information below is purely informational)
• unicap/riscv64 (0.9.12+repack20150328.0.git2c600ae-3 to 0.9.12+repack20150328.0.git2c600ae-3)
  • Migration status for unicap/riscv64 (0.9.12+repack20150328.0.git2c600ae-3 to 0.9.12+repack20150328.0.git2c600ae-3): Will attempt migration (Any information below is purely informational)
• unicon/riscv64 (3.0.4+dfsg1-5 to 3.0.4+dfsg1-5)
  • Migration status for unicon/riscv64 (3.0.4+dfsg1-5 to 3.0.4+dfsg1-5): Will attempt migration (Any information below is purely informational)
• unicorn-engine/riscv64 (2.0.1.post1-4.1 to 2.0.1.post1-4.1)
  • Migration status for unicorn-engine/riscv64 (2.0.1.post1-4.1 to 2.0.1.post1-4.1): Will attempt migration (Any information below is purely informational)
• unicorn/riscv64 (6.1.0-2 to 6.1.0-2)
  • Migration status for unicorn/riscv64 (6.1.0-2 to 6.1.0-2): Will attempt migration (Any information below is purely informational)
• unifdef/riscv64 (2.12-1 to 2.12-1)
  • Migration status for unifdef/riscv64 (2.12-1 to 2.12-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)
• unifrac-tools/riscv64 (1.4-3 to 1.4-3)
  • Migration status for unifrac-tools/riscv64 (1.4-3 to 1.4-3): Will attempt migration (Any information below is purely informational)
• unilog/riscv64 (2.5-2 to 2.5-2)
  • Migration status for unilog/riscv64 (2.5-2 to 2.5-2): Will attempt migration (Any information below is purely informational)
• unison-2.53/riscv64 (2.53.3-2 to 2.53.3-2)
  • Migration status for unison-2.53/riscv64 (2.53.3-2 to 2.53.3-2): Will attempt migration (Any information below is purely informational)
• units-filter/riscv64 (4.2.1-1 to 4.2.1-1)
  • Migration status for units-filter/riscv64 (4.2.1-1 to 4.2.1-1): Will attempt migration (Any information below is purely informational)
• unittest++/riscv64 (2.0.0-3 to 2.0.0-3)
  • Migration status for unittest++/riscv64 (2.0.0-3 to 2.0.0-3): 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)
• upower/amd64 (1.90.3-1 to 1.90.3-1)
  • Migration status for upower/amd64 (1.90.3-1 to 1.90.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: upower/amd64 libplist (not considered)
    • Invalidated by dependency
    • Depends: upower/amd64 libimobiledevice
• upower/arm64 (1.90.3-1 to 1.90.3-1)
  • Migration status for upower/arm64 (1.90.3-1 to 1.90.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: upower/arm64 libplist (not considered)
    • Invalidated by dependency
    • Depends: upower/arm64 libimobiledevice
• upower/armel (1.90.3-1 to 1.90.3-1)
  • Migration status for upower/armel (1.90.3-1 to 1.90.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: upower/armel libplist (not considered)
    • Invalidated by dependency
    • Depends: upower/armel libimobiledevice
• upower/armhf (1.90.3-1 to 1.90.3-1)
  • Migration status for upower/armhf (1.90.3-1 to 1.90.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: upower/armhf libplist (not considered)
    • Invalidated by dependency
    • Depends: upower/armhf libimobiledevice
• upower/i386 (1.90.3-1 to 1.90.3-1)
  • Migration status for upower/i386 (1.90.3-1 to 1.90.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: upower/i386 libplist (not considered)
    • Invalidated by dependency
    • Depends: upower/i386 libimobiledevice
• upower/mips64el (1.90.3-1 to 1.90.3-1)
  • Migration status for upower/mips64el (1.90.3-1 to 1.90.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: upower/mips64el libplist (not considered)
    • Invalidated by dependency
    • Depends: upower/mips64el libimobiledevice
• upower/ppc64el (1.90.3-1 to 1.90.3-1)
  • Migration status for upower/ppc64el (1.90.3-1 to 1.90.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: upower/ppc64el libplist (not considered)
    • Invalidated by dependency
    • Depends: upower/ppc64el libimobiledevice
• upower/riscv64 (1.90.3-1 to 1.90.3-1)
  • Migration status for upower/riscv64 (1.90.3-1 to 1.90.3-1): Will attempt migration (Any information below is purely informational)
• upower/s390x (1.90.3-1 to 1.90.3-1)
  • Migration status for upower/s390x (1.90.3-1 to 1.90.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: upower/s390x libplist (not considered)
    • Invalidated by dependency
    • Depends: upower/s390x libimobiledevice
• 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)
• upx-ucl/riscv64 (4.2.2-3 to 4.2.2-3)
  • Migration status for upx-ucl/riscv64 (4.2.2-3 to 4.2.2-3): Will attempt migration (Any information below is purely informational)
• uqm/riscv64 (0.8.0+dfsg-2 to 0.8.0+dfsg-2)
  • Migration status for uqm/riscv64 (0.8.0+dfsg-2 to 0.8.0+dfsg-2): Will attempt migration (Any information below is purely informational)
• urdfdom/riscv64 (3.0.1-1 to 3.0.1-1)
  • Migration status for urdfdom/riscv64 (3.0.1-1 to 3.0.1-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)
• usbtop/riscv64 (1.0+dfsg-1 to 1.0+dfsg-1)
  • Migration status for usbtop/riscv64 (1.0+dfsg-1 to 1.0+dfsg-1): 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)
• ussp-push/riscv64 (0.11-4 to 0.11-4)
  • Migration status for ussp-push/riscv64 (0.11-4 to 0.11-4): 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)
• utop/amd64 (2.14.0-1 to 2.14.0-1)
  • Migration status for utop/amd64 (2.14.0-1 to 2.14.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: utop/amd64 ocaml-dune (not considered)
    • Invalidated by dependency
• utop/arm64 (2.14.0-1 to 2.14.0-1)
  • Migration status for utop/arm64 (2.14.0-1 to 2.14.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: utop/arm64 ocaml-dune (not considered)
    • Invalidated by dependency
• utop/armel (2.14.0-1 to 2.14.0-1)
  • Migration status for utop/armel (2.14.0-1 to 2.14.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: utop/armel ocaml-dune (not considered)
    • Invalidated by dependency
• utop/armhf (2.14.0-1 to 2.14.0-1)
  • Migration status for utop/armhf (2.14.0-1 to 2.14.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: utop/armhf ocaml-dune (not considered)
    • Invalidated by dependency
• utop/i386 (2.14.0-1 to 2.14.0-1)
  • Migration status for utop/i386 (2.14.0-1 to 2.14.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: utop/i386 ocaml-dune (not considered)
    • Invalidated by dependency
• utop/mips64el (2.14.0-1 to 2.14.0-1)
  • Migration status for utop/mips64el (2.14.0-1 to 2.14.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: utop/mips64el ocaml-dune (not considered)
    • Invalidated by dependency
• utop/ppc64el (2.14.0-1 to 2.14.0-1)
  • Migration status for utop/ppc64el (2.14.0-1 to 2.14.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: utop/ppc64el ocaml-dune (not considered)
    • Invalidated by dependency
• utop/riscv64 (2.14.0-1 to 2.14.0-1)
  • Migration status for utop/riscv64 (2.14.0-1 to 2.14.0-1): Will attempt migration (Any information below is purely informational)
• utop/s390x (2.14.0-1 to 2.14.0-1)
  • Migration status for utop/s390x (2.14.0-1 to 2.14.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: utop/s390x ocaml-dune (not considered)
    • Invalidated by dependency
• uuidm/riscv64 (0.9.8-2 to 0.9.8-2)
  • Migration status for uuidm/riscv64 (0.9.8-2 to 0.9.8-2): Will attempt migration (Any information below is purely informational)
• uwsgi/riscv64 (2.0.25.1-1 to 2.0.25.1-1)
  • Migration status for uwsgi/riscv64 (2.0.25.1-1 to 2.0.25.1-1): Will attempt migration (Any information below is purely informational)
• uxplay/amd64 (1.68.3-1 to 1.68.3-1)
  • Migration status for uxplay/amd64 (1.68.3-1 to 1.68.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: uxplay/amd64 libplist (not considered)
    • Invalidated by dependency
• uxplay/arm64 (1.68.3-1 to 1.68.3-1)
  • Migration status for uxplay/arm64 (1.68.3-1 to 1.68.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: uxplay/arm64 libplist (not considered)
    • Invalidated by dependency
• uxplay/armel (1.68.3-1 to 1.68.3-1)
  • Migration status for uxplay/armel (1.68.3-1 to 1.68.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: uxplay/armel libplist (not considered)
    • Invalidated by dependency
• uxplay/armhf (1.68.3-1 to 1.68.3-1)
  • Migration status for uxplay/armhf (1.68.3-1 to 1.68.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: uxplay/armhf libplist (not considered)
    • Invalidated by dependency
• uxplay/i386 (1.68.3-1 to 1.68.3-1)
  • Migration status for uxplay/i386 (1.68.3-1 to 1.68.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: uxplay/i386 libplist (not considered)
    • Invalidated by dependency
• uxplay/mips64el (1.68.3-1 to 1.68.3-1)
  • Migration status for uxplay/mips64el (1.68.3-1 to 1.68.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: uxplay/mips64el libplist (not considered)
    • Invalidated by dependency
• uxplay/ppc64el (1.68.3-1 to 1.68.3-1)
  • Migration status for uxplay/ppc64el (1.68.3-1 to 1.68.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: uxplay/ppc64el libplist (not considered)
    • Invalidated by dependency
• uxplay/s390x (1.68.3-1 to 1.68.3-1)
  • Migration status for uxplay/s390x (1.68.3-1 to 1.68.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: uxplay/s390x libplist (not considered)
    • Invalidated by dependency
• v-sim/riscv64 (3.7.2-9 to 3.7.2-9)
  • Migration status for v-sim/riscv64 (3.7.2-9 to 3.7.2-9): Will attempt migration (Any information below is purely informational)
• v4l-utils/riscv64 (1.26.1-4 to 1.26.1-4)
  • Migration status for v4l-utils/riscv64 (1.26.1-4 to 1.26.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)
• variantslib/riscv64 (1:0.16.0-2 to 1:0.16.0-2)
  • Migration status for variantslib/riscv64 (1:0.16.0-2 to 1:0.16.0-2): Will attempt migration (Any information below is purely informational)
• vbindiff/riscv64 (3.0-beta5-2 to 3.0-beta5-2)
  • Migration status for vbindiff/riscv64 (3.0-beta5-2 to 3.0-beta5-2): Will attempt migration (Any information below is purely informational)
• vbrfix/riscv64 (0.24+dfsg-2 to 0.24+dfsg-2)
  • Migration status for vbrfix/riscv64 (0.24+dfsg-2 to 0.24+dfsg-2): 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)
• vcftools/riscv64 (0.1.16-3 to 0.1.16-3)
  • Migration status for vcftools/riscv64 (0.1.16-3 to 0.1.16-3): Will attempt migration (Any information below is purely informational)
• vco-plugins/riscv64 (0.3.0-6 to 0.3.0-6)
  • Migration status for vco-plugins/riscv64 (0.3.0-6 to 0.3.0-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-markad/riscv64 (3.4.12-1 to 3.4.12-1)
  • Migration status for vdr-plugin-markad/riscv64 (3.4.12-1 to 3.4.12-1): Will attempt migration (Any information below is purely informational)
• vdr-plugin-mp3/riscv64 (0.10.4-2 to 0.10.4-2)
  • Migration status for vdr-plugin-mp3/riscv64 (0.10.4-2 to 0.10.4-2): 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)
• vectoroids/riscv64 (1.1.0-16 to 1.1.0-16)
  • Migration status for vectoroids/riscv64 (1.1.0-16 to 1.1.0-16): Will attempt migration (Any information below is purely informational)
• velvet/riscv64 (1.2.10+dfsg1-8 to 1.2.10+dfsg1-8)
  • Migration status for velvet/riscv64 (1.2.10+dfsg1-8 to 1.2.10+dfsg1-8): Will attempt migration (Any information below is purely informational)
• vera++/riscv64 (1.2.1-2 to 1.2.1-2)
  • Migration status for vera++/riscv64 (1.2.1-2 to 1.2.1-2): Will attempt migration (Any information below is purely informational)
• verbiste/riscv64 (0.1.48-1 to 0.1.48-1)
  • Migration status for verbiste/riscv64 (0.1.48-1 to 0.1.48-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)
• veryfasttree/riscv64 (4.0.3+dfsg-1 to 4.0.3+dfsg-1)
  • Migration status for veryfasttree/riscv64 (4.0.3+dfsg-1 to 4.0.3+dfsg-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)
• vfu/riscv64 (5.09-2 to 5.09-2)
  • Migration status for vfu/riscv64 (5.09-2 to 5.09-2): Will attempt migration (Any information below is purely informational)
• vgrabbj/riscv64 (0.9.9-3 to 0.9.9-3)
  • Migration status for vgrabbj/riscv64 (0.9.9-3 to 0.9.9-3): 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)
• videotrans/riscv64 (1.6.1-9 to 1.6.1-9)
  • Migration status for videotrans/riscv64 (1.6.1-9 to 1.6.1-9): Will attempt migration (Any information below is purely informational)
• vienna-rna/riscv64 (2.5.1+dfsg-1 to 2.5.1+dfsg-1)
  • Migration status for vienna-rna/riscv64 (2.5.1+dfsg-1 to 2.5.1+dfsg-1): Will attempt migration (Any information below is purely informational)
• viking/riscv64 (1.10-3 to 1.10-3)
  • Migration status for viking/riscv64 (1.10-3 to 1.10-3): Will attempt migration (Any information below is purely informational)
• vim-command-t/riscv64 (5.0.5-1 to 5.0.5-1)
  • Migration status for vim-command-t/riscv64 (5.0.5-1 to 5.0.5-1): Will attempt migration (Any information below is purely informational)
• vimix/riscv64 (0.7.2+git20221123+ds-2 to 0.7.2+git20221123+ds-2)
  • Migration status for vimix/riscv64 (0.7.2+git20221123+ds-2 to 0.7.2+git20221123+ds-2): Will attempt migration (Any information below is purely informational)
• vinagre/riscv64 (3.22.0-8.1 to 3.22.0-8.1)
  • Migration status for vinagre/riscv64 (3.22.0-8.1 to 3.22.0-8.1): Will attempt migration (Any information below is purely informational)
• 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)
• vips/riscv64 (8.15.2-1 to 8.15.2-1)
  • Migration status for vips/riscv64 (8.15.2-1 to 8.15.2-1): Will attempt migration (Any information below is purely informational)
• virglrenderer/riscv64 (1.0.0-1 to 1.0.0-1)
  • Migration status for virglrenderer/riscv64 (1.0.0-1 to 1.0.0-1): 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)
• virtuoso-opensource/riscv64 (7.2.12+dfsg-0.2 to 7.2.12+dfsg-0.2)
  • Migration status for virtuoso-opensource/riscv64 (7.2.12+dfsg-0.2 to 7.2.12+dfsg-0.2): 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)
• vish/riscv64 (0.0.20130812-1 to 0.0.20130812-1)
  • Migration status for vish/riscv64 (0.0.20130812-1 to 0.0.20130812-1): 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)
• vite/riscv64 (1.2+svn+git4.c6c0ce7-8 to 1.2+svn+git4.c6c0ce7-8)
  • Migration status for vite/riscv64 (1.2+svn+git4.c6c0ce7-8 to 1.2+svn+git4.c6c0ce7-8): Will attempt migration (Any information below is purely informational)
• vixl/riscv64 (5.1.0-3 to 5.1.0-3)
  • Migration status for vixl/riscv64 (5.1.0-3 to 5.1.0-3): Will attempt migration (Any information below is purely informational)
• vkbasalt/riscv64 (0.3.2.10-1 to 0.3.2.10-1)
  • Migration status for vkbasalt/riscv64 (0.3.2.10-1 to 0.3.2.10-1): Will attempt migration (Any information below is purely informational)
• vkmark/riscv64 (2017.08+git20220909-1 to 2017.08+git20220909-1)
  • Migration status for vkmark/riscv64 (2017.08+git20220909-1 to 2017.08+git20220909-1): Will attempt migration (Any information below is purely informational)
• vlc-plugin-bittorrent/riscv64 (2.15-1 to 2.15-1)
  • Migration status for vlc-plugin-bittorrent/riscv64 (2.15-1 to 2.15-1): Will attempt migration (Any information below is purely informational)
• vlc-plugin-pipewire/riscv64 (3-3 to 3-3)
  • Migration status for vlc-plugin-pipewire/riscv64 (3-3 to 3-3): Will attempt migration (Any information below is purely informational)
• vlevel/riscv64 (0.5.1-4 to 0.5.1-4)
  • Migration status for vlevel/riscv64 (0.5.1-4 to 0.5.1-4): 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)
• 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)
• vncsnapshot/riscv64 (1.2a-5.2 to 1.2a-5.2)
  • Migration status for vncsnapshot/riscv64 (1.2a-5.2 to 1.2a-5.2): Will attempt migration (Any information below is purely informational)
• vnstat/riscv64 (2.12-1 to 2.12-1)
  • Migration status for vnstat/riscv64 (2.12-1 to 2.12-1): Will attempt migration (Any information below is purely informational)
• vodovod/riscv64 (1.10-5 to 1.10-5)
  • Migration status for vodovod/riscv64 (1.10-5 to 1.10-5): 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)
• volk/riscv64 (3.1.2-1.1 to 3.1.2-1.1)
  • Migration status for volk/riscv64 (3.1.2-1.1 to 3.1.2-1.1): Will attempt migration (Any information below is purely informational)
• volpack/riscv64 (1.0b3-9.1 to 1.0b3-9.1)
  • Migration status for volpack/riscv64 (1.0b3-9.1 to 1.0b3-9.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)
• voms-mysql-plugin/riscv64 (3.1.7-3 to 3.1.7-3)
  • Migration status for voms-mysql-plugin/riscv64 (3.1.7-3 to 3.1.7-3): Will attempt migration (Any information below is purely informational)
• vonsh/riscv64 (1.0+ds-0.1 to 1.0+ds-0.1)
  • Migration status for vonsh/riscv64 (1.0+ds-0.1 to 1.0+ds-0.1): Will attempt migration (Any information below is purely informational)
• vor/riscv64 (0.5.8-1 to 0.5.8-1)
  • Migration status for vor/riscv64 (0.5.8-1 to 0.5.8-1): Will attempt migration (Any information below is purely informational)
• voro++/riscv64 (0.5+revert-to-0.4.6+dfsg1-1 to 0.5+revert-to-0.4.6+dfsg1-1)
  • Migration status for voro++/riscv64 (0.5+revert-to-0.4.6+dfsg1-1 to 0.5+revert-to-0.4.6+dfsg1-1): Will attempt migration (Any information below is purely informational)
• voronota/riscv64 (1.22.3149-2 to 1.22.3149-2)
  • Migration status for voronota/riscv64 (1.22.3149-2 to 1.22.3149-2): Will attempt migration (Any information below is purely informational)
• vpb-driver/riscv64 (4.2.61-1.4 to 4.2.61-1.4)
  • Migration status for vpb-driver/riscv64 (4.2.61-1.4 to 4.2.61-1.4): 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)
• vramsteg/riscv64 (1.1.0-1 to 1.1.0-1)
  • Migration status for vramsteg/riscv64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• vt/riscv64 (0.57721+ds-3 to 0.57721+ds-3)
  • Migration status for vt/riscv64 (0.57721+ds-3 to 0.57721+ds-3): Will attempt migration (Any information below is purely informational)
• vtable-dumper/riscv64 (1.2-1 to 1.2-1)
  • Migration status for vtable-dumper/riscv64 (1.2-1 to 1.2-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)
• vte2.91/riscv64 (0.75.92-1 to 0.75.92-1)
  • Migration status for vte2.91/riscv64 (0.75.92-1 to 0.75.92-1): Will attempt migration (Any information below is purely informational)
• vtk9/mips64el (9.3.0+dfsg1-1 to 9.3.0+dfsg1-1)
  • Migration status for vtk9/mips64el (9.3.0+dfsg1-1 to 9.3.0+dfsg1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: vtk9/mips64el onetbb (not considered)
    • Invalidated by dependency
• vvmd/riscv64 (0.18-1 to 0.18-1)
  • Migration status for vvmd/riscv64 (0.18-1 to 0.18-1): Will attempt migration (Any information below is purely informational)
• w-scan-cpp/riscv64 (20231015+dfsg-3 to 20231015+dfsg-3)
  • Migration status for w-scan-cpp/riscv64 (20231015+dfsg-3 to 20231015+dfsg-3): Will attempt migration (Any information below is purely informational)
• w1retap/riscv64 (1.4.6-1.1 to 1.4.6-1.1)
  • Migration status for w1retap/riscv64 (1.4.6-1.1 to 1.4.6-1.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)
• wabt/riscv64 (1.0.34+dsfg2+~cs1.0.32-1 to 1.0.34+dsfg2+~cs1.0.32-1)
  • Migration status for wabt/riscv64 (1.0.34+dsfg2+~cs1.0.32-1 to 1.0.34+dsfg2+~cs1.0.32-1): Will attempt migration (Any information below is purely informational)
• waffle/riscv64 (1.8.0-2 to 1.8.0-2)
  • Migration status for waffle/riscv64 (1.8.0-2 to 1.8.0-2): Will attempt migration (Any information below is purely informational)
• wah-plugins/riscv64 (0.1.0-5 to 0.1.0-5)
  • Migration status for wah-plugins/riscv64 (0.1.0-5 to 0.1.0-5): Will attempt migration (Any information below is purely informational)
• waili/riscv64 (19990723-22.3 to 19990723-22.3)
  • Migration status for waili/riscv64 (19990723-22.3 to 19990723-22.3): 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)
• wannier90/riscv64 (3.1.0+ds-8 to 3.1.0+ds-8)
  • Migration status for wannier90/riscv64 (3.1.0+ds-8 to 3.1.0+ds-8): 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)
• warzone2100/riscv64 (4.4.2-1 to 4.4.2-1)
  • Migration status for warzone2100/riscv64 (4.4.2-1 to 4.4.2-1): 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)
• wayfire/riscv64 (0.8.1-1 to 0.8.1-1)
  • Migration status for wayfire/riscv64 (0.8.1-1 to 0.8.1-1): Will attempt migration (Any information below is purely informational)
• waylandpp/riscv64 (1.0.0-6 to 1.0.0-6)
  • Migration status for waylandpp/riscv64 (1.0.0-6 to 1.0.0-6): Will attempt migration (Any information below is purely informational)
• wayout/riscv64 (0.1.4-1 to 0.1.4-1)
  • Migration status for wayout/riscv64 (0.1.4-1 to 0.1.4-1): 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)
• wcm/riscv64 (0.8.0+git20231201-1 to 0.8.0+git20231201-1)
  • Migration status for wcm/riscv64 (0.8.0+git20231201-1 to 0.8.0+git20231201-1): 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)
• wdq2wav/riscv64 (1.0.0-1.1 to 1.0.0-1.1)
  • Migration status for wdq2wav/riscv64 (1.0.0-1.1 to 1.0.0-1.1): Will attempt migration (Any information below is purely informational)
• webalizer/riscv64 (2.23.08-3.3 to 2.23.08-3.3)
  • Migration status for webalizer/riscv64 (2.23.08-3.3 to 2.23.08-3.3): Will attempt migration (Any information below is purely informational)
• webdruid/riscv64 (0.5.4-16 to 0.5.4-16)
  • Migration status for webdruid/riscv64 (0.5.4-16 to 0.5.4-16): 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)
• webrtc-audio-processing/riscv64 (0.3-1 to 0.3-1)
  • Migration status for webrtc-audio-processing/riscv64 (0.3-1 to 0.3-1): Will attempt migration (Any information below is purely informational)
• wf-config/riscv64 (0.8.0+git20240312-1 to 0.8.0+git20240312-1)
  • Migration status for wf-config/riscv64 (0.8.0+git20240312-1 to 0.8.0+git20240312-1): Will attempt migration (Any information below is purely informational)
• wf-recorder/riscv64 (0.4.1-1 to 0.4.1-1)
  • Migration status for wf-recorder/riscv64 (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
• wf-shell/riscv64 (0.8.1+ds-1 to 0.8.1+ds-1)
  • Migration status for wf-shell/riscv64 (0.8.1+ds-1 to 0.8.1+ds-1): 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)
• wham-align/riscv64 (0.1.5-8 to 0.1.5-8)
  • Migration status for wham-align/riscv64 (0.1.5-8 to 0.1.5-8): Will attempt migration (Any information below is purely informational)
• why3/riscv64 (1.6.0-1 to 1.6.0-1)
  • Migration status for why3/riscv64 (1.6.0-1 to 1.6.0-1): Will attempt migration (Any information below is purely informational)
• whysynth/riscv64 (20170701-3 to 20170701-3)
  • Migration status for whysynth/riscv64 (20170701-3 to 20170701-3): Will attempt migration (Any information below is purely informational)
• wiipdf/riscv64 (1.4-6 to 1.4-6)
  • Migration status for wiipdf/riscv64 (1.4-6 to 1.4-6): Will attempt migration (Any information below is purely informational)
• wing/riscv64 (0.7-32 to 0.7-32)
  • Migration status for wing/riscv64 (0.7-32 to 0.7-32): 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)
• wlcs/riscv64 (1.6.1-1 to 1.6.1-1)
  • Migration status for wlcs/riscv64 (1.6.1-1 to 1.6.1-1): Will attempt migration (Any information below is purely informational)
• wm2/riscv64 (4+svn20090216-4 to 4+svn20090216-4)
  • Migration status for wm2/riscv64 (4+svn20090216-4 to 4+svn20090216-4): 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)
• wmanager/riscv64 (0.3.1-2 to 0.3.1-2)
  • Migration status for wmanager/riscv64 (0.3.1-2 to 0.3.1-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)
• wmbattery/riscv64 (2.56-1 to 2.56-1)
  • Migration status for wmbattery/riscv64 (2.56-1 to 2.56-1): Will attempt migration (Any information below is purely informational)
• wmcdplay/riscv64 (1.1-3 to 1.1-3)
  • Migration status for wmcdplay/riscv64 (1.1-3 to 1.1-3): 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)
• wmmixer/riscv64 (1.9-2 to 1.9-2)
  • Migration status for wmmixer/riscv64 (1.9-2 to 1.9-2): 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)
• wmtv/riscv64 (0.6.7-2 to 0.6.7-2)
  • Migration status for wmtv/riscv64 (0.6.7-2 to 0.6.7-2): Will attempt migration (Any information below is purely informational)
• wmweather+/riscv64 (2.19~alpha+ds-1.1 to 2.19~alpha+ds-1.1)
  • Migration status for wmweather+/riscv64 (2.19~alpha+ds-1.1 to 2.19~alpha+ds-1.1): Will attempt migration (Any information below is purely informational)
• woff2/riscv64 (1.0.2-2 to 1.0.2-2)
  • Migration status for woff2/riscv64 (1.0.2-2 to 1.0.2-2): 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)
• wolf4sdl/riscv64 (20230117-1 to 20230117-1)
  • Migration status for wolf4sdl/riscv64 (20230117-1 to 20230117-1): Will attempt migration (Any information below is purely informational)
• woof-doom/riscv64 (14.3.0+dfsg-1 to 14.3.0+dfsg-1)
  • Migration status for woof-doom/riscv64 (14.3.0+dfsg-1 to 14.3.0+dfsg-1): Will attempt migration (Any information below is purely informational)
• wordgrinder/riscv64 (0.8-1 to 0.8-1)
  • Migration status for wordgrinder/riscv64 (0.8-1 to 0.8-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)
• wreport/riscv64 (3.36-1.1 to 3.36-1.1)
  • Migration status for wreport/riscv64 (3.36-1.1 to 3.36-1.1): 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)
• wsjtx/riscv64 (2.7.0~rc4+repack-1 to 2.7.0~rc4+repack-1)
  • Migration status for wsjtx/riscv64 (2.7.0~rc4+repack-1 to 2.7.0~rc4+repack-1): 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)
• wvkbd/riscv64 (0.14.3-1 to 0.14.3-1)
  • Migration status for wvkbd/riscv64 (0.14.3-1 to 0.14.3-1): Will attempt migration (Any information below is purely informational)
• wvstreams/riscv64 (4.6.1-17.1 to 4.6.1-17.1)
  • Migration status for wvstreams/riscv64 (4.6.1-17.1 to 4.6.1-17.1): 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)
• x11-apps/riscv64 (7.7+11 to 7.7+11)
  • Migration status for x11-apps/riscv64 (7.7+11 to 7.7+11): Will attempt migration (Any information below is purely informational)
• x11-utils/riscv64 (7.7+6 to 7.7+6)
  • Migration status for x11-utils/riscv64 (7.7+6 to 7.7+6): Will attempt migration (Any information below is purely informational)
• x11-xserver-utils/riscv64 (7.7+10 to 7.7+10)
  • Migration status for x11-xserver-utils/riscv64 (7.7+10 to 7.7+10): Will attempt migration (Any information below is purely informational)
• x11vnc/riscv64 (0.9.16-10 to 0.9.16-10)
  • Migration status for x11vnc/riscv64 (0.9.16-10 to 0.9.16-10): Will attempt migration (Any information below is purely informational)
• x264/riscv64 (2:0.164.3108+git31e19f9-1 to 2:0.164.3108+git31e19f9-1)
  • Migration status for x264/riscv64 (2:0.164.3108+git31e19f9-1 to 2:0.164.3108+git31e19f9-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)
• x42-plugins/riscv64 (20230915+ds-1 to 20230915+ds-1)
  • Migration status for x42-plugins/riscv64 (20230915+ds-1 to 20230915+ds-1): Will attempt migration (Any information below is purely informational)
• xalan/riscv64 (1.12-7.1 to 1.12-7.1)
  • Migration status for xalan/riscv64 (1.12-7.1 to 1.12-7.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)
• xapian-bindings/riscv64 (1.4.25-1 to 1.4.25-1)
  • Migration status for xapian-bindings/riscv64 (1.4.25-1 to 1.4.25-1): Will attempt migration (Any information below is purely informational)
• xapian-core/riscv64 (1.4.25-1 to 1.4.25-1)
  • Migration status for xapian-core/riscv64 (1.4.25-1 to 1.4.25-1): Will attempt migration (Any information below is purely informational)
• xapian-omega/riscv64 (1.4.25-2 to 1.4.25-2)
  • Migration status for xapian-omega/riscv64 (1.4.25-2 to 1.4.25-2): 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)
• xawtv/riscv64 (3.107-2 to 3.107-2)
  • Migration status for xawtv/riscv64 (3.107-2 to 3.107-2): Will attempt migration (Any information below is purely informational)
• xbindkeys/riscv64 (1.8.7-2 to 1.8.7-2)
  • Migration status for xbindkeys/riscv64 (1.8.7-2 to 1.8.7-2): 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)
• xboxdrv/riscv64 (0.8.8-4 to 0.8.8-4)
  • Migration status for xboxdrv/riscv64 (0.8.8-4 to 0.8.8-4): Will attempt migration (Any information below is purely informational)
• xbrzscale/riscv64 (1.8-2 to 1.8-2)
  • Migration status for xbrzscale/riscv64 (1.8-2 to 1.8-2): Will attempt migration (Any information below is purely informational)
• xc3sprog/riscv64 (0+svn795+dfsg-4 to 0+svn795+dfsg-4)
  • Migration status for xc3sprog/riscv64 (0+svn795+dfsg-4 to 0+svn795+dfsg-4): 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)
• xcrysden/riscv64 (1.6.2-4 to 1.6.2-4)
  • Migration status for xcrysden/riscv64 (1.6.2-4 to 1.6.2-4): Will attempt migration (Any information below is purely informational)
• xd/riscv64 (5.00.01-1 to 5.00.01-1)
  • Migration status for xd/riscv64 (5.00.01-1 to 5.00.01-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)
• xdg-utils-cxx/riscv64 (1.0.1-3.1 to 1.0.1-3.1)
  • Migration status for xdg-utils-cxx/riscv64 (1.0.1-3.1 to 1.0.1-3.1): Will attempt migration (Any information below is purely informational)
• xdiskusage/riscv64 (1.60-4 to 1.60-4)
  • Migration status for xdiskusage/riscv64 (1.60-4 to 1.60-4): 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)
• xdvik-ja/riscv64 (22.87.06+j1.42-3 to 22.87.06+j1.42-3)
  • Migration status for xdvik-ja/riscv64 (22.87.06+j1.42-3 to 22.87.06+j1.42-3): 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)
• xemacs21/riscv64 (21.4.24-12 to 21.4.24-12)
  • Migration status for xemacs21/riscv64 (21.4.24-12 to 21.4.24-12): Will attempt migration (Any information below is purely informational)
• xerces-c/riscv64 (3.2.4+debian-1.3 to 3.2.4+debian-1.3)
  • Migration status for xerces-c/riscv64 (3.2.4+debian-1.3 to 3.2.4+debian-1.3): 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)
• xeus/riscv64 (3.1.3-2 to 3.1.3-2)
  • Migration status for xeus/riscv64 (3.1.3-2 to 3.1.3-2): Will attempt migration (Any information below is purely informational)
• xevil/riscv64 (2.02r2-10.2 to 2.02r2-10.2)
  • Migration status for xevil/riscv64 (2.02r2-10.2 to 2.02r2-10.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)
• xfburn/riscv64 (0.7.0-1 to 0.7.0-1)
  • Migration status for xfburn/riscv64 (0.7.0-1 to 0.7.0-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-notes-plugin/riscv64 (1.11.0-1 to 1.11.0-1)
  • Migration status for xfce4-notes-plugin/riscv64 (1.11.0-1 to 1.11.0-1): Will attempt migration (Any information below is purely informational)
• xfce4-notifyd/riscv64 (0.9.4-1 to 0.9.4-1)
  • Migration status for xfce4-notifyd/riscv64 (0.9.4-1 to 0.9.4-1): Will attempt migration (Any information below is purely informational)
• xfce4-panel/riscv64 (4.18.4-1 to 4.18.4-1)
  • Migration status for xfce4-panel/riscv64 (4.18.4-1 to 4.18.4-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-power-manager/riscv64 (4.18.3-2 to 4.18.3-2)
  • Migration status for xfce4-power-manager/riscv64 (4.18.3-2 to 4.18.3-2): 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-screenshooter/riscv64 (1.10.5-1 to 1.10.5-1)
  • Migration status for xfce4-screenshooter/riscv64 (1.10.5-1 to 1.10.5-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-session/riscv64 (4.18.3-1 to 4.18.3-1)
  • Migration status for xfce4-session/riscv64 (4.18.3-1 to 4.18.3-1): Will attempt migration (Any information below is purely informational)
• xfce4-settings/riscv64 (4.18.3-1 to 4.18.3-1)
  • Migration status for xfce4-settings/riscv64 (4.18.3-1 to 4.18.3-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)
• xfishtank/riscv64 (2.5-1 to 2.5-1)
  • Migration status for xfishtank/riscv64 (2.5-1 to 2.5-1): Will attempt migration (Any information below is purely informational)
• xfoil/riscv64 (6.99.dfsg+1-3 to 6.99.dfsg+1-3)
  • Migration status for xfoil/riscv64 (6.99.dfsg+1-3 to 6.99.dfsg+1-3): 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)
• xgalaga++/riscv64 (0.9-2 to 0.9-2)
  • Migration status for xgalaga++/riscv64 (0.9-2 to 0.9-2): Will attempt migration (Any information below is purely informational)
• xgks/riscv64 (2.6.1+dfsg.2-15 to 2.6.1+dfsg.2-15)
  • Migration status for xgks/riscv64 (2.6.1+dfsg.2-15 to 2.6.1+dfsg.2-15): 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)
• xilinx-bootgen/riscv64 (2022.2-2 to 2022.2-2)
  • Migration status for xilinx-bootgen/riscv64 (2022.2-2 to 2022.2-2): Will attempt migration (Any information below is purely informational)
• xindy/riscv64 (2.5.1.20160104-11 to 2.5.1.20160104-11)
  • Migration status for xindy/riscv64 (2.5.1.20160104-11 to 2.5.1.20160104-11): 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)
• xinput-calibrator/riscv64 (0.7.5+git20140201-1 to 0.7.5+git20140201-1)
  • Migration status for xinput-calibrator/riscv64 (0.7.5+git20140201-1 to 0.7.5+git20140201-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)
• xloadimage/riscv64 (4.1-25 to 4.1-25)
  • Migration status for xloadimage/riscv64 (4.1-25 to 4.1-25): 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)
• xmahjongg/riscv64 (3.7-5 to 3.7-5)
  • Migration status for xmahjongg/riscv64 (3.7-5 to 3.7-5): Will attempt migration (Any information below is purely informational)
• xmakemol/riscv64 (5.16-10 to 5.16-10)
  • Migration status for xmakemol/riscv64 (5.16-10 to 5.16-10): Will attempt migration (Any information below is purely informational)
• xmedcon/riscv64 (0.23.0-gtk3+dfsg-1.1 to 0.23.0-gtk3+dfsg-1.1)
  • Migration status for xmedcon/riscv64 (0.23.0-gtk3+dfsg-1.1 to 0.23.0-gtk3+dfsg-1.1): Will attempt migration (Any information below is purely informational)
• xml-light/riscv64 (2.5-2 to 2.5-2)
  • Migration status for xml-light/riscv64 (2.5-2 to 2.5-2): Will attempt migration (Any information below is purely informational)
• xml-security-c/riscv64 (2.0.4-2 to 2.0.4-2)
  • Migration status for xml-security-c/riscv64 (2.0.4-2 to 2.0.4-2): Will attempt migration (Any information below is purely informational)
• xmlcopyeditor/riscv64 (1.3.0.0-1.1 to 1.3.0.0-1.1)
  • Migration status for xmlcopyeditor/riscv64 (1.3.0.0-1.1 to 1.3.0.0-1.1): Will attempt migration (Any information below is purely informational)
• xmlm/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for xmlm/riscv64 (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
• xmlsec1/riscv64 (1.2.39-5 to 1.2.39-5)
  • Migration status for xmlsec1/riscv64 (1.2.39-5 to 1.2.39-5): 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)
• xmlto/riscv64 (0.0.28-2.1 to 0.0.28-2.1)
  • Migration status for xmlto/riscv64 (0.0.28-2.1 to 0.0.28-2.1): Will attempt migration (Any information below is purely informational)
• xmltooling/riscv64 (3.2.4-2.1 to 3.2.4-2.1)
  • Migration status for xmltooling/riscv64 (3.2.4-2.1 to 3.2.4-2.1): Will attempt migration (Any information below is purely informational)
• xmobar/riscv64 (0.46-3 to 0.46-3)
  • Migration status for xmobar/riscv64 (0.46-3 to 0.46-3): 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)
• xmount/riscv64 (0.7.6-3 to 0.7.6-3)
  • Migration status for xmount/riscv64 (0.7.6-3 to 0.7.6-3): 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)
• xnec2c/riscv64 (1:4.4.14-1 to 1:4.4.14-1)
  • Migration status for xnec2c/riscv64 (1:4.4.14-1 to 1:4.4.14-1): Will attempt migration (Any information below is purely informational)
• xnnpack/riscv64 (0.0~git20221221.51a9875-1 to 0.0~git20221221.51a9875-1)
  • Migration status for xnnpack/riscv64 (0.0~git20221221.51a9875-1 to 0.0~git20221221.51a9875-1): Will attempt migration (Any information below is purely informational)
• xorg-server/riscv64 (2:21.1.12-1 to 2:21.1.12-1)
  • Migration status for xorg-server/riscv64 (2:21.1.12-1 to 2:21.1.12-1): Will attempt migration (Any information below is purely informational)
• xorg/riscv64 (1:7.7+23 to 1:7.7+23)
  • Migration status for xorg/riscv64 (1:7.7+23 to 1:7.7+23): Will attempt migration (Any information below is purely informational)
• xorgxrdp/riscv64 (1:0.9.19-1 to 1:0.9.19-1)
  • Migration status for xorgxrdp/riscv64 (1:0.9.19-1 to 1:0.9.19-1): Will attempt migration (Any information below is purely informational)
• xoscope/riscv64 (2.3-1 to 2.3-1)
  • Migration status for xoscope/riscv64 (2.3-1 to 2.3-1): Will attempt migration (Any information below is purely informational)
• xosview/riscv64 (1.24-1 to 1.24-1)
  • Migration status for xosview/riscv64 (1.24-1 to 1.24-1): 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)
• xpaint/riscv64 (2.9.1.4-4.1 to 2.9.1.4-4.1)
  • Migration status for xpaint/riscv64 (2.9.1.4-4.1 to 2.9.1.4-4.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)
• xplanet/riscv64 (1.3.1-3 to 1.3.1-3)
  • Migration status for xplanet/riscv64 (1.3.1-3 to 1.3.1-3): Will attempt migration (Any information below is purely informational)
• xplc/riscv64 (0.3.13-12.1 to 0.3.13-12.1)
  • Migration status for xplc/riscv64 (0.3.13-12.1 to 0.3.13-12.1): Will attempt migration (Any information below is purely informational)
• xplot/riscv64 (1.19-9.1 to 1.19-9.1)
  • Migration status for xplot/riscv64 (1.19-9.1 to 1.19-9.1): 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)
• xraylib/riscv64 (4.0.0+dfsg1-3 to 4.0.0+dfsg1-3)
  • Migration status for xraylib/riscv64 (4.0.0+dfsg1-3 to 4.0.0+dfsg1-3): Will attempt migration (Any information below is purely informational)
• xrdesktop/riscv64 (0.15.1-5.1 to 0.15.1-5.1)
  • Migration status for xrdesktop/riscv64 (0.15.1-5.1 to 0.15.1-5.1): 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)
• xsd/riscv64 (4.0.0-9 to 4.0.0-9)
  • Migration status for xsd/riscv64 (4.0.0-9 to 4.0.0-9): Will attempt migration (Any information below is purely informational)
• xsecurelock/riscv64 (1.9.0-1 to 1.9.0-1)
  • Migration status for xsecurelock/riscv64 (1.9.0-1 to 1.9.0-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-aiptek/riscv64 (1:1.4.1-4 to 1:1.4.1-4)
  • Migration status for xserver-xorg-input-aiptek/riscv64 (1:1.4.1-4 to 1:1.4.1-4): 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-joystick/riscv64 (1:1.6.3-1.1 to 1:1.6.3-1.1)
  • Migration status for xserver-xorg-input-joystick/riscv64 (1:1.6.3-1.1 to 1:1.6.3-1.1): 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-mutouch/riscv64 (1:1.3.0-3 to 1:1.3.0-3)
  • Migration status for xserver-xorg-input-mutouch/riscv64 (1:1.3.0-3 to 1:1.3.0-3): 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-cirrus/riscv64 (1:1.5.3-1 to 1:1.5.3-1)
  • Migration status for xserver-xorg-video-cirrus/riscv64 (1:1.5.3-1 to 1:1.5.3-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)
• xsettingsd/riscv64 (1.0.2-1 to 1.0.2-1)
  • Migration status for xsettingsd/riscv64 (1.0.2-1 to 1.0.2-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)
• xsoldier/riscv64 (1:1.8-6 to 1:1.8-6)
  • Migration status for xsoldier/riscv64 (1:1.8-6 to 1:1.8-6): Will attempt migration (Any information below is purely informational)
• xstow/riscv64 (1.1.0-1 to 1.1.0-1)
  • Migration status for xstow/riscv64 (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
• xstr/riscv64 (0.2.1-24 to 0.2.1-24)
  • Migration status for xstr/riscv64 (0.2.1-24 to 0.2.1-24): Will attempt migration (Any information below is purely informational)
• xstrp4/riscv64 (1.8.2-7 to 1.8.2-7)
  • Migration status for xstrp4/riscv64 (1.8.2-7 to 1.8.2-7): 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)
• xsystem35/riscv64 (1.7.3-pre5-11 to 1.7.3-pre5-11)
  • Migration status for xsystem35/riscv64 (1.7.3-pre5-11 to 1.7.3-pre5-11): Will attempt migration (Any information below is purely informational)
• xtb/riscv64 (6.7.0-1 to 6.7.0-1)
  • Migration status for xtb/riscv64 (6.7.0-1 to 6.7.0-1): 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)
• xtrkcad/riscv64 (1:5.2.0Beta2.1-2 to 1:5.2.0Beta2.1-2)
  • Migration status for xtrkcad/riscv64 (1:5.2.0Beta2.1-2 to 1:5.2.0Beta2.1-2): Will attempt migration (Any information below is purely informational)
• xutils-dev/riscv64 (1:7.7+6.2 to 1:7.7+6.2)
  • Migration status for xutils-dev/riscv64 (1:7.7+6.2 to 1:7.7+6.2): Will attempt migration (Any information below is purely informational)
• xva-img/riscv64 (1.5-1 to 1.5-1)
  • Migration status for xva-img/riscv64 (1.5-1 to 1.5-1): Will attempt migration (Any information below is purely informational)
• xwatch/riscv64 (2.11-16.1 to 2.11-16.1)
  • Migration status for xwatch/riscv64 (2.11-16.1 to 2.11-16.1): 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)
• xwelltris/riscv64 (1.0.1-18 to 1.0.1-18)
  • Migration status for xwelltris/riscv64 (1.0.1-18 to 1.0.1-18): 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)
• yabar/riscv64 (0.4.0-1.1 to 0.4.0-1.1)
  • Migration status for yabar/riscv64 (0.4.0-1.1 to 0.4.0-1.1): 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)
• yacas/riscv64 (1.3.6-2.3 to 1.3.6-2.3)
  • Migration status for yacas/riscv64 (1.3.6-2.3 to 1.3.6-2.3): Will attempt migration (Any information below is purely informational)
• yad/riscv64 (0.40.0-1 to 0.40.0-1)
  • Migration status for yad/riscv64 (0.40.0-1 to 0.40.0-1): 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)
• yambar/riscv64 (1.11.0-1 to 1.11.0-1)
  • Migration status for yambar/riscv64 (1.11.0-1 to 1.11.0-1): Will attempt migration (Any information below is purely informational)
• yaml-cpp/riscv64 (0.8.0+dfsg-6 to 0.8.0+dfsg-6)
  • Migration status for yaml-cpp/riscv64 (0.8.0+dfsg-6 to 0.8.0+dfsg-6): Will attempt migration (Any information below is purely informational)
• yanosim/riscv64 (0.1-5 to 0.1-5)
  • Migration status for yanosim/riscv64 (0.1-5 to 0.1-5): Will attempt migration (Any information below is purely informational)
• yapet/riscv64 (2.6-2 to 2.6-2)
  • Migration status for yapet/riscv64 (2.6-2 to 2.6-2): Will attempt migration (Any information below is purely informational)
• yaskkserv/riscv64 (1.1.1-3 to 1.1.1-3)
  • Migration status for yaskkserv/riscv64 (1.1.1-3 to 1.1.1-3): 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)
• yatm/riscv64 (0.9-5 to 0.9-5)
  • Migration status for yatm/riscv64 (0.9-5 to 0.9-5): Will attempt migration (Any information below is purely informational)
• yc-el/riscv64 (5.0.0-9 to 5.0.0-9)
  • Migration status for yc-el/riscv64 (5.0.0-9 to 5.0.0-9): 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)
• ygl/riscv64 (4.2e-6.1 to 4.2e-6.1)
  • Migration status for ygl/riscv64 (4.2e-6.1 to 4.2e-6.1): Will attempt migration (Any information below is purely informational)
• ykush-control/riscv64 (1.3.0+ds-1 to 1.3.0+ds-1)
  • Migration status for ykush-control/riscv64 (1.3.0+ds-1 to 1.3.0+ds-1): Will attempt migration (Any information below is purely informational)
• ylva/riscv64 (1.7-2 to 1.7-2)
  • Migration status for ylva/riscv64 (1.7-2 to 1.7-2): 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)
• yodl/riscv64 (4.03.03-1 to 4.03.03-1)
  • Migration status for yodl/riscv64 (4.03.03-1 to 4.03.03-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)
• yorick-hdf5/riscv64 (0.8.0-8 to 0.8.0-8)
  • Migration status for yorick-hdf5/riscv64 (0.8.0-8 to 0.8.0-8): Will attempt migration (Any information below is purely informational)
• yorick-yeti/riscv64 (6.4.0-1.1 to 6.4.0-1.1)
  • Migration status for yorick-yeti/riscv64 (6.4.0-1.1 to 6.4.0-1.1): Will attempt migration (Any information below is purely informational)
• yoshimi/riscv64 (2.3.2-1 to 2.3.2-1)
  • Migration status for yoshimi/riscv64 (2.3.2-1 to 2.3.2-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)
• yquake2/riscv64 (8.30+dfsg-1 to 8.30+dfsg-1)
  • Migration status for yquake2/riscv64 (8.30+dfsg-1 to 8.30+dfsg-1): 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)
• yudit/riscv64 (3.1.0-1 to 3.1.0-1)
  • Migration status for yudit/riscv64 (3.1.0-1 to 3.1.0-1): 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)
• z3/riscv64 (4.8.12-3.1 to 4.8.12-3.1)
  • Migration status for z3/riscv64 (4.8.12-3.1 to 4.8.12-3.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)
• zarchive/riscv64 (0.1.2-2 to 0.1.2-2)
  • Migration status for zarchive/riscv64 (0.1.2-2 to 0.1.2-2): 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)
• zathura-cb/riscv64 (0.1.10-1 to 0.1.10-1)
  • Migration status for zathura-cb/riscv64 (0.1.10-1 to 0.1.10-1): Will attempt migration (Any information below is purely informational)
• zathura-djvu/riscv64 (0.2.9-1 to 0.2.9-1)
  • Migration status for zathura-djvu/riscv64 (0.2.9-1 to 0.2.9-1): Will attempt migration (Any information below is purely informational)
• zathura-pdf-poppler/riscv64 (0.3.2-1 to 0.3.2-1)
  • Migration status for zathura-pdf-poppler/riscv64 (0.3.2-1 to 0.3.2-1): Will attempt migration (Any information below is purely informational)
• zathura-ps/riscv64 (0.2.7-2 to 0.2.7-2)
  • Migration status for zathura-ps/riscv64 (0.2.7-2 to 0.2.7-2): Will attempt migration (Any information below is purely informational)
• zathura/riscv64 (0.5.6-1 to 0.5.6-1)
  • Migration status for zathura/riscv64 (0.5.6-1 to 0.5.6-1): 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)
• zbackup/riscv64 (1.5-2 to 1.5-2)
  • Migration status for zbackup/riscv64 (1.5-2 to 1.5-2): Will attempt migration (Any information below is purely informational)
• zbar/riscv64 (0.23.93-4 to 0.23.93-4)
  • Migration status for zbar/riscv64 (0.23.93-4 to 0.23.93-4): Will attempt migration (Any information below is purely informational)
• zdbsp/riscv64 (1.19+20181027+dfsg.1-4 to 1.19+20181027+dfsg.1-4)
  • Migration status for zdbsp/riscv64 (1.19+20181027+dfsg.1-4 to 1.19+20181027+dfsg.1-4): Will attempt migration (Any information below is purely informational)
• zed/riscv64 (3.2.3-1 to 3.2.3-1)
  • Migration status for zed/riscv64 (3.2.3-1 to 3.2.3-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)
• zeroinstall-injector/riscv64 (2.18-2.1 to 2.18-2.1)
  • Migration status for zeroinstall-injector/riscv64 (2.18-2.1 to 2.18-2.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)
• zim-tools/riscv64 (3.2.0-1 to 3.2.0-1)
  • Migration status for zim-tools/riscv64 (3.2.0-1 to 3.2.0-1): Will attempt migration (Any information below is purely informational)
• zimg/riscv64 (3.0.5+ds1-1 to 3.0.5+ds1-1)
  • Migration status for zimg/riscv64 (3.0.5+ds1-1 to 3.0.5+ds1-1): Will attempt migration (Any information below is purely informational)
• zinnia/riscv64 (0.06-8 to 0.06-8)
  • Migration status for zinnia/riscv64 (0.06-8 to 0.06-8): 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)
• zipios++/riscv64 (0.1.5.9+cvs.2007.04.28-11 to 0.1.5.9+cvs.2007.04.28-11)
  • Migration status for zipios++/riscv64 (0.1.5.9+cvs.2007.04.28-11 to 0.1.5.9+cvs.2007.04.28-11): 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)
• zita-ajbridge/riscv64 (0.8.4-1 to 0.8.4-1)
  • Migration status for zita-ajbridge/riscv64 (0.8.4-1 to 0.8.4-1): Will attempt migration (Any information below is purely informational)
• zita-alsa-pcmi/riscv64 (0.6.1-1.1 to 0.6.1-1.1)
  • Migration status for zita-alsa-pcmi/riscv64 (0.6.1-1.1 to 0.6.1-1.1): Will attempt migration (Any information below is purely informational)
• zita-at1/riscv64 (0.8.2-1 to 0.8.2-1)
  • Migration status for zita-at1/riscv64 (0.8.2-1 to 0.8.2-1): Will attempt migration (Any information below is purely informational)
• zita-bls1/riscv64 (0.3.3-3 to 0.3.3-3)
  • Migration status for zita-bls1/riscv64 (0.3.3-3 to 0.3.3-3): Will attempt migration (Any information below is purely informational)
• zita-convolver/riscv64 (4.0.3-2 to 4.0.3-2)
  • Migration status for zita-convolver/riscv64 (4.0.3-2 to 4.0.3-2): Will attempt migration (Any information below is purely informational)
• zita-dc1/riscv64 (0.3.3-2 to 0.3.3-2)
  • Migration status for zita-dc1/riscv64 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• zita-dpl1/riscv64 (0.3.3-1 to 0.3.3-1)
  • Migration status for zita-dpl1/riscv64 (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
• zita-lrx/riscv64 (0.1.2-1 to 0.1.2-1)
  • Migration status for zita-lrx/riscv64 (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
• zita-mu1/riscv64 (0.3.3-2 to 0.3.3-2)
  • Migration status for zita-mu1/riscv64 (0.3.3-2 to 0.3.3-2): Will attempt migration (Any information below is purely informational)
• zita-njbridge/riscv64 (0.4.8-1 to 0.4.8-1)
  • Migration status for zita-njbridge/riscv64 (0.4.8-1 to 0.4.8-1): Will attempt migration (Any information below is purely informational)
• zita-resampler/riscv64 (1.11.2-1 to 1.11.2-1)
  • Migration status for zita-resampler/riscv64 (1.11.2-1 to 1.11.2-1): Will attempt migration (Any information below is purely informational)
• zita-rev1/riscv64 (0.2.2-2 to 0.2.2-2)
  • Migration status for zita-rev1/riscv64 (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
• znc_pu (1.9.1-1 to 1.8.2-3.1+deb12u1)
  • Migration status for znc_pu (1.9.1-1 to 1.8.2-3.1+deb12u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: znc is newer in the target suite (1.9.1-1 1.8.2-3.1+deb12u1)
• 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)
• zopfli/riscv64 (1.0.3-2 to 1.0.3-2)
  • Migration status for zopfli/riscv64 (1.0.3-2 to 1.0.3-2): Will attempt migration (Any information below is purely informational)
• zpaq/riscv64 (7.15+repack-1 to 7.15+repack-1)
  • Migration status for zpaq/riscv64 (7.15+repack-1 to 7.15+repack-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)
• zthreads/riscv64 (2.3.2-11.1 to 2.3.2-11.1)
  • Migration status for zthreads/riscv64 (2.3.2-11.1 to 2.3.2-11.1): Will attempt migration (Any information below is purely informational)
• zug/riscv64 (0.1.1-1 to 0.1.1-1)
  • Migration status for zug/riscv64 (0.1.1-1 to 0.1.1-1): 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)
• zutils/riscv64 (1.13-2 to 1.13-2)
  • Migration status for zutils/riscv64 (1.13-2 to 1.13-2): Will attempt migration (Any information below is purely informational)
• zxing-cpp/riscv64 (2.2.1-3 to 2.2.1-3)
  • Migration status for zxing-cpp/riscv64 (2.2.1-3 to 2.2.1-3): Will attempt migration (Any information below is purely informational)
• zynaddsubfx/riscv64 (3.0.6-6 to 3.0.6-6)
  • Migration status for zynaddsubfx/riscv64 (3.0.6-6 to 3.0.6-6): Will attempt migration (Any information below is purely informational)
• aardvark-dns (1.4.0-6 to 1.6.0-3)
  • Migration status for aardvark-dns (1.4.0-6 to 1.6.0-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/a/aardvark-dns.html
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
    • Depends: aardvark-dns netavark (not considered)
  • 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 ♻
• apfsprogs (0+git20231203+ds-1 to 0+git20231203+ds-2)
  • Migration status for apfsprogs (0+git20231203+ds-1 to 0+git20231203+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apfsprogs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• backuppc (4.4.0-8 to 4.4.0-8.1)
  • Migration status for backuppc (4.4.0-8 to 4.4.0-8.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 backuppc/4.4.0-8.1: 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/b/backuppc.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 ♻
• biometric-authentication (0.9.71-1 to 0.9.71-1.1)
  • Migration status for biometric-authentication (0.9.71-1 to 0.9.71-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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biometric-authentication.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 ♻
• booth (- to 1.1-2)
  • Migration status for booth (- to 1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for booth/1.1-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
    • Depends: booth libgcrypt20
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/booth.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 ♻
• bosixnet (2.0-2.1 to 2.0-2.2)
  • Migration status for bosixnet (2.0-2.1 to 2.0-2.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/b/bosixnet.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 ♻
• c-blosc2 (2.14.4+ds-2 to 2.15.0+ds-1)
  • Migration status for c-blosc2 (2.14.4+ds-2 to 2.15.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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/c-blosc2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• coccinelle (1.1.1.deb-6 to 1.2.deb-1)
  • Migration status for coccinelle (1.1.1.deb-6 to 1.2.deb-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/c/coccinelle.html
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for coccinelle/1.2.deb-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • 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 ♻
• corkscrew (2.0-14 to 2.0-15)
  • Migration status for corkscrew (2.0-14 to 2.0-15): 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/c/corkscrew.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 ♻
• corosync-qdevice (3.0.3-1 to 3.0.3-2)
  • Migration status for corosync-qdevice (3.0.3-1 to 3.0.3-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for corosync-qdevice/3.0.3-2: 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/corosync-qdevice.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 ♻
• csh (20230828-1 to 20230828-1.1)
  • Migration status for csh (20230828-1 to 20230828-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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/csh.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 ♻
• dh-virtualenv (1.2.2-1.5 to 1.2.2-1.6)
  • Migration status for dh-virtualenv (1.2.2-1.5 to 1.2.2-1.6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-virtualenv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• docknot (8.0.0-1 to 8.0.1-1)
  • Migration status for docknot (8.0.0-1 to 8.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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/docknot.html
    • autopkgtest for docknot/8.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
• doxygen-awesome-css (2.3.1-1 to 2.3.3-1)
  • Migration status for doxygen-awesome-css (2.3.1-1 to 2.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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/doxygen-awesome-css.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• dump (0.4b47-4 to 0.4b47-4.1)
  • Migration status for dump (0.4b47-4 to 0.4b47-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
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dump.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 ♻
• ecflow (5.13.0-1 to 5.13.2-1)
  • Migration status for ecflow (5.13.0-1 to 5.13.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecflow.html
    • autopkgtest for ecflow/5.13.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • 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
• efibootmgr (18-1 to 18-2)
  • Migration status for efibootmgr (18-1 to 18-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/e/efibootmgr.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 ♻
• fake-hwclock (0.13 to 0.14)
  • Migration status for fake-hwclock (0.13 to 0.14): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fake-hwclock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• firmware-ast (20140808-7 to 20140808-8)
  • Migration status for firmware-ast (20140808-7 to 20140808-8): 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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gcl (2.6.14-9 to 2.6.14-10)
  • Migration status for gcl (2.6.14-9 to 2.6.14-10): 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/g/gcl.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 ♻
• geographiclib (2.3-1 to 2.4-1)
  • Migration status for geographiclib (2.3-1 to 2.4-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/g/geographiclib.html
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • 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 ♻
• gnome-shell-extension-flypie (22-1 to 26-1)
  • Migration status for gnome-shell-extension-flypie (22-1 to 26-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnome-shell-extension-flypie/amd64 has unsatisfiable dependency
    • gnome-shell-extension-flypie/arm64 has unsatisfiable dependency
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-flypie.html
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating gnome-shell-extension-flypie will fix bugs in testing: #1052096
    • 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 ♻
• gnumach (2:1.8+git20240406-5 to 2:1.8+git20240714-1)
  • Migration status for gnumach (2:1.8+git20240406-5 to 2:1.8+git20240714-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:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnumach.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gobgp (3.27.0-1 to 3.28.0-1)
  • Migration status for gobgp (3.27.0-1 to 3.28.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
    • autopkgtest for gobgp/3.28.0-1: 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/g/gobgp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• golang-github-casbin-govaluate (1.1.1-2 to 1.2.0-1)
  • Migration status for golang-github-casbin-govaluate (1.1.1-2 to 1.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-casbin-govaluate.html
    • autopkgtest for golang-github-casbin-govaluate/1.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-github-containerd-imgcrypt (- to 1.1.11-3)
  • Migration status for golang-github-containerd-imgcrypt (- to 1.1.11-3): 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/g/golang-github-containerd-imgcrypt.html
    • autopkgtest for golang-github-containerd-imgcrypt/1.1.11-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • 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 ♻
• golang-github-ovn-org-libovsdb (0.6.0+git20240125.03f787b-1 to 0.7.0-1)
  • Migration status for golang-github-ovn-org-libovsdb (0.6.0+git20240125.03f787b-1 to 0.7.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ovn-org-libovsdb.html
    • autopkgtest for golang-github-ovn-org-libovsdb/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
• golang-k8s-utils (0.0~git20240502.fe8a2dd-1 to 0.0~git20240711.18e509b-1)
  • Migration status for golang-k8s-utils (0.0~git20240502.fe8a2dd-1 to 0.0~git20240711.18e509b-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-k8s-apimachinery/0.29.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for golang-k8s-utils/0.0~git20240711.18e509b-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-utils.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 ♻
• gophernicus (3.1.1-3 to 3.1.1-3.1)
  • Migration status for gophernicus (3.1.1-3 to 3.1.1-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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gophernicus.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 ♻
• h5py (3.11.0-2 to 3.11.0-5)
  • Migration status for h5py (3.11.0-2 to 3.11.0-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 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 h5py will fix bugs in testing: #1076028
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/h5py.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• hddemux (- to 0.5-1.1)
  • Migration status for hddemux (- to 0.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hddemux would introduce bugs in testing: #1060597
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hddemux.html
    • autopkgtest for hddemux/0.5-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, 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 ♻
    • Reproducible on i386 - info ♻
• hfsprogs (540.1.linux3-5 to 540.1.linux3-6)
  • Migration status for hfsprogs (540.1.linux3-5 to 540.1.linux3-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• hugo (0.127.0-1 to 0.128.2-2)
  • Migration status for hugo (0.127.0-1 to 0.128.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for hugo/0.128.2-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • missing build on mips64el
    • missing build on riscv64
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/h/hugo.html
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): hugo golang-github-alecthomas-chroma-v2
    • Build-Depends(-Arch): hugo golang-github-evanw-esbuild
    • Build-Depends(-Arch): hugo golang-github-yuin-goldmark
    • Build-Depends(-Arch): hugo golang-github-yuin-goldmark-emoji
  • 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 ♻
• hurd (- to 1:0.9.git20240714-1)
  • Migration status for hurd (- to 1:0.9.git20240714-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hurd would introduce bugs in testing: #650080, #838244, #943307
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libc0.3-dev (>= 2.33-2~1)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-disk-dev (>= 0~20211031-2)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-usb-dev
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libacpica-dev
    • Not built on buildd: arch all binaries uploaded by sthibault, a new source-only upload is needed to allow migration
    • Not touching package due to block request by freeze (please contact debian-release if update is needed)
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): hurd libgcrypt20
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hurd.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 ♻
• ibus-pinyin (1.5.0-11 to 1.5.1-1)
  • Migration status for ibus-pinyin (1.5.0-11 to 1.5.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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibus-pinyin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ifupdown2 (3.0.0-1.1 to 3.0.0-1.2)
  • Migration status for ifupdown2 (3.0.0-1.1 to 3.0.0-1.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ifupdown2.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 ♻
• junit5 (5.10.1-1 to 5.10.3-1)
  • Migration status for junit5 (5.10.1-1 to 5.10.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/junit5.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ksmtuned (4.20150326 to 4.20150326+nmu1)
  • Migration status for ksmtuned (4.20150326 to 4.20150326+nmu1): 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/k/ksmtuned.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 ♻
• lcrq (0.1.2-1 to 0.2.1-2)
  • Migration status for lcrq (0.1.2-1 to 0.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for librecast/0.8.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Test in progress
    • missing build on riscv64
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/l/lcrq.html
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • 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 ♻
• libervia-backend (0.9.0~hg4260-2 to 0.9.0~hg4285-1)
  • Migration status for libervia-backend (0.9.0~hg4260-2 to 0.9.0~hg4285-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libervia-backend/0.9.0~hg4285-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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libervia-backend.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 ♻
• libmuscle (3.7+4565-7 to 3.7+4565-8)
  • Migration status for libmuscle (3.7+4565-7 to 3.7+4565-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/libm/libmuscle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libsigmf (1.0.2-2 to 1.0.2-3)
  • Migration status for libsigmf (1.0.2-2 to 1.0.2-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/libs/libsigmf.html
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • 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 ♻
• lxc-ci (0.0~git20240430.ebf4128-1 to 0.0~git20240711.228d36a-1)
  • Migration status for lxc-ci (0.0~git20240430.ebf4128-1 to 0.0~git20240711.228d36a-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/l/lxc-ci.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• magics-python (2:1.5.8-1 to 2:1.5.8-3)
  • Migration status for magics-python (2:1.5.8-1 to 2:1.5.8-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magics-python.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 magics-python/2:1.5.8-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• magnum (- to 18.0.0-2)
  • Migration status for magnum (- to 18.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magnum.html
    • autopkgtest for magnum/18.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
• metakernel (- to 0.30.2-2)
  • Migration status for metakernel (- to 0.30.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for metakernel/0.30.2-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Test in progress
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/m/metakernel.html
    • Too young, only 0 of 5 days old
  • 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 ♻
• mig (1.8+git20231217-2 to 1.8+git20231217-3)
  • Migration status for mig (1.8+git20231217-2 to 1.8+git20231217-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mig.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mm-common (1.0.6-2 to 1.0.6-2.1)
  • Migration status for mm-common (1.0.6-2 to 1.0.6-2.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating mm-common will fix bugs in testing: #1065903
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mm-common.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• netavark (1.4.0-4.1 to 1.6.0-2.1)
  • Migration status for netavark (1.4.0-4.1 to 1.6.0-2.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 netavark/1.6.0-2.1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): netavark rust-tonic
    • Build-Depends(-Arch): netavark rust-zbus (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netavark.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• netcfg (1.189 to 1.190)
  • Migration status for netcfg (1.189 to 1.190): 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:
    • 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 ♻
    • Reproducible on i386 - info ♻
• nodm (0.13-6 to 0.13-6.1)
  • Migration status for nodm (0.13-6 to 0.13-6.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/nodm.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 ♻
• openldap (2.5.18+dfsg-1 to 2.5.18+dfsg-2)
  • Migration status for openldap (2.5.18+dfsg-1 to 2.5.18+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for apache2/2.4.61-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for balsa/2.6.4-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for curl/8.8.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for openldap/2.5.18+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 ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for php-net-ldap2/2.3.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for php8.2/8.2.21-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for phpldapadmin/1.2.6.7-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for postfix/3.9.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for postgresql-16/16.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for proftpd-dfsg/1.3.8.b+dfsg-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for python-ldap/3.4.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for samba/2:4.20.2+dfsg-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for squid/6.10-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for strongswan/5.9.13-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • 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/o/openldap.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 ♻
• osspd (1.3.2-13.2 to 1.3.2-14)
  • Migration status for osspd (1.3.2-13.2 to 1.3.2-14): 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/o/osspd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pesign (116-7 to 116-8)
  • Migration status for pesign (116-7 to 116-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/p/pesign.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 ♻
• php-amqplib (3.6.2-1 to 3.7.0-1)
  • Migration status for php-amqplib (3.6.2-1 to 3.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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-amqplib.html
    • autopkgtest for php-amqplib/3.7.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-composer-ca-bundle (1.5.0-1 to 1.5.1-1)
  • Migration status for php-composer-ca-bundle (1.5.0-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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-composer-ca-bundle.html
    • autopkgtest for php-composer-ca-bundle/1.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-composer-class-map-generator (1.3.4-1 to 1.3.4-2)
  • Migration status for php-composer-class-map-generator (1.3.4-1 to 1.3.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-composer-class-map-generator.html
    • autopkgtest for php-composer-class-map-generator/1.3.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
• php-composer-pcre (3.1.4-1 to 3.1.4-2)
  • Migration status for php-composer-pcre (3.1.4-1 to 3.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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-composer-pcre.html
    • autopkgtest for php-composer-pcre/3.1.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
• php-composer-xdebug-handler (3.0.5-1 to 3.0.5-2)
  • Migration status for php-composer-xdebug-handler (3.0.5-1 to 3.0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-composer-xdebug-handler/3.0.5-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for phpmd/2.15.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-composer-xdebug-handler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• php-constant-time (2.7.0-1 to 3.0.0-2)
  • Migration status for php-constant-time (2.7.0-1 to 3.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-constant-time.html
    • autopkgtest for php-constant-time/3.0.0-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
• php-doctrine-annotations (2.0.1-3 to 2.0.1-4)
  • Migration status for php-doctrine-annotations (2.0.1-3 to 2.0.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-doctrine-annotations.html
    • autopkgtest for php-doctrine-annotations/2.0.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-doctrine-cache (2.2.0-3 to 2.2.0-4)
  • Migration status for php-doctrine-cache (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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-doctrine-cache.html
    • autopkgtest for php-doctrine-cache/2.2.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
• php-doctrine-deprecations (1.1.3-2 to 1.1.3-3)
  • Migration status for php-doctrine-deprecations (1.1.3-2 to 1.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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-doctrine-deprecations.html
    • autopkgtest for php-doctrine-deprecations/1.1.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-doctrine-event-manager (2.0.1-1 to 2.0.1-2)
  • Migration status for php-doctrine-event-manager (2.0.1-1 to 2.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-doctrine-event-manager/2.0.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for symfony/6.4.7+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: 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/p/php-doctrine-event-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• php-doctrine-inflector (2.0.10-2 to 2.0.10-3)
  • Migration status for php-doctrine-inflector (2.0.10-2 to 2.0.10-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-doctrine-inflector.html
    • autopkgtest for php-doctrine-inflector/2.0.10-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
• php-guzzlehttp-promises (1.5.3-3 to 1.5.3-4)
  • Migration status for php-guzzlehttp-promises (1.5.3-3 to 1.5.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-guzzlehttp-promises/1.5.3-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for symfony/6.4.7+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-guzzlehttp-promises.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• php-hamcrest (2.0.1-4 to 2.0.1-5)
  • Migration status for php-hamcrest (2.0.1-4 to 2.0.1-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-hamcrest.html
    • autopkgtest for php-hamcrest/2.0.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-json-schema (5.2.13-1 to 5.3.0-1)
  • Migration status for php-json-schema (5.2.13-1 to 5.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-json-schema.html
    • autopkgtest for php-json-schema/5.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-masterminds-html5 (2.9.0+dfsg-2 to 2.9.0+dfsg-3)
  • Migration status for php-masterminds-html5 (2.9.0+dfsg-2 to 2.9.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-dompdf/2.0.7+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for php-masterminds-html5/2.9.0+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for roundcube/1.6.7+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for symfony/6.4.7+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-masterminds-html5.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• php-phpspec-prophecy (1.19.0-1 to 1.19.0-2)
  • Migration status for php-phpspec-prophecy (1.19.0-1 to 1.19.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-phpspec-prophecy.html
    • autopkgtest for php-phpspec-prophecy/1.19.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
• powermgmt-base (1.37 to 1.37+nmu1)
  • Migration status for powermgmt-base (1.37 to 1.37+nmu1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/powermgmt-base.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 ♻
• pydoctor (23.9.1-1 to 23.9.1-2)
  • Migration status for pydoctor (23.9.1-1 to 23.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 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydoctor.html
    • autopkgtest for pydoctor/23.9.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
• python-pecan (1.5.1-3 to 1.5.1-4)
  • Migration status for python-pecan (1.5.1-3 to 1.5.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for aodh/18.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for barbican/1:18.0.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for ceph/18.2.3+ds-3: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for cloudkitty/20.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for designate/1:18.0.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for ironic/1:24.1.1-3: 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: Pass, s390x: Test in progress
    • autopkgtest for mistral/18.0.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Test in progress (will not be considered a regression)
    • autopkgtest for networking-bagpipe/20.0.1-5: 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: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test in progress
    • autopkgtest for octavia/14.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for python-neutron-lib/3.11.0-3: 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: Pass, s390x: Test in progress
    • autopkgtest for python-pecan/1.5.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pecan.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-pyaarlo (0.8.0.2-3 to 0.8.0.3-1)
  • Migration status for python-pyaarlo (0.8.0.2-3 to 0.8.0.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for python-pyaarlo/0.8.0.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for simplemonitor/1.12.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyaarlo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-zstandard (0.22.0+git20240526-1 to 0.23.0-1)
  • Migration status for python-zstandard (0.22.0+git20240526-1 to 0.23.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/p/python-zstandard.html
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for augur/24.4.0-1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test in progress
    • autopkgtest for conda-package-streaming/0.10.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for django-compression-middleware/0.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for pandas/2.2.2+dfsg-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for python-zstandard/0.23.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: Test in progress
    • autopkgtest for rpmlint/2.5.0+ds1-0.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • 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 ♻
• qemu-web-desktop (- to 24.07.12+ds1-1)
  • Migration status for qemu-web-desktop (- to 24.07.12+ds1-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
    • Depends: qemu-web-desktop novnc
    • Depends: qemu-web-desktop websockify (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qemu-web-desktop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• qtbase-opensource-src (5.15.13+dfsg-2 to 5.15.13+dfsg-3)
  • Migration status for qtbase-opensource-src (5.15.13+dfsg-2 to 5.15.13+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cmake/3.29.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, s390x: Test in progress
    • autopkgtest for mediaconch/24.06-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pyside2/5.15.14-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: Test in progress
    • 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/q/qtbase-opensource-src.html
    • 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 ♻
• r-cran-cubature (2.1.0-1 to 2.1.1-1)
  • Migration status for r-cran-cubature (2.1.0-1 to 2.1.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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-cubature.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• razercfg (0.43-2 to 0.43-3)
  • Migration status for razercfg (0.43-2 to 0.43-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating razercfg will fix bugs in testing: #1074755
    • 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 ♻
• recode (3.6-26 to 3.6-28)
  • Migration status for recode (3.6-26 to 3.6-28): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating recode would introduce bugs in testing: #1076355, #1076370
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for ipolish/20240101-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/recode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-anyhow (1.0.85-1 to 1.0.86-1)
  • Migration status for rust-anyhow (1.0.85-1 to 1.0.86-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 rust-anyhow/1.0.86-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-av1-grain/0.2.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-bkt/0.6.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-bmap-parser/0.1.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-cargo/0.70.1-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test in progress
    • autopkgtest for rust-cargo-binutils/0.3.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-cargo-c/0.9.19-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-cargo-util/0.2.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-crates-io/0.36.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-csv2svg/0.2.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-dateparser/0.2.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test in progress
    • autopkgtest for rust-debcargo/2.6.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-distro-info/0.4.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-ethtool/0.2.5-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-filespooler/1.2.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-git-absorb/0.6.11-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-glycin-utils/0.1.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-gping/1.16.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-hafas-rs/0.2.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 ♻), s390x: Test in progress
    • autopkgtest for rust-html2pango/0.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-laurel/0.6.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-log4rs/1.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-mptcp-pm/0.1.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 ♻), s390x: Test in progress
    • autopkgtest for rust-netlink-packet-core/0.7.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: Test in progress
    • autopkgtest for rust-netlink-packet-route/0.17.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-netlink-packet-utils/0.5.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-openpgp-cert-d/0.3.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-openpgp-keylist/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-parsec-service/1.3.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-pathsearch/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-pep508-rs/0.2.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), s390x: Test in progress
    • autopkgtest for rust-pinger/1.1.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-pipewire/0.8.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-prost-derive/0.11.9-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-pyo3/0.20.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-regex-test/0.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-repro-env/0.4.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-roadmap/0.6.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-rockusb/0.1.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-rustfix/0.6.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: Test in progress
    • autopkgtest for rust-rustpython-parser/0.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-cert-store/0.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-directories/0.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-gpg-agent/0.3.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-ipc/0.34.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-keystore/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-keystore-backend/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-keystore-softkeys/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-net/0.28.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-openpgp/1.21.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-openpgp-mt/0.1.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-sop/0.35.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sequoia-wot/0.11.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sniffglue/0.16.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-sop/0.7.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-tree-sitter-cli/0.20.8-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-tree-sitter-config/0.19.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-tree-sitter-loader/0.20.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-vergen/8.2.6-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-wasmtime/19.0.0+dfsg-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test in progress
    • autopkgtest for rust-zram-generator/1.1.2-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rustup/1.26.0-7: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-anyhow.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 ♻
• rust-ashpd (- to 0.8.1-2)
  • Migration status for rust-ashpd (- to 0.8.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for rust-ashpd/0.8.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-ashpd rust-zbus (not considered)
    • Depends: rust-ashpd rust-zbus (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ashpd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-async-channel (1.9.0-2 to 2.3.1-4)
  • Migration status for rust-async-channel (1.9.0-2 to 2.3.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-async-channel-dev/2.3.1-4/amd64 to testing makes librust-sluice-dev/0.5.5-1+b1/amd64 uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/amd64 to testing makes librust-swtchr-dev/0.1.2-2/amd64 uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/arm64 to testing makes librust-sluice-dev/0.5.5-1+b1/arm64 uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/arm64 to testing makes librust-swtchr-dev/0.1.2-2/arm64 uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/armel to testing makes librust-sluice-dev/0.5.5-1+b1/armel uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/armel to testing makes librust-swtchr-dev/0.1.2-2/armel uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/armhf to testing makes librust-sluice-dev/0.5.5-1+b1/armhf uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/armhf to testing makes librust-swtchr-dev/0.1.2-2/armhf uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/i386 to testing makes librust-sluice-dev/0.5.5-1+b1/i386 uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/i386 to testing makes librust-swtchr-dev/0.1.2-2/i386 uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/mips64el to testing makes librust-sluice-dev/0.5.5-1+b1/mips64el uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/mips64el to testing makes librust-swtchr-dev/0.1.2-2/mips64el uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/ppc64el to testing makes librust-sluice-dev/0.5.5-1+b1/ppc64el uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/ppc64el to testing makes librust-swtchr-dev/0.1.2-2/ppc64el uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/s390x to testing makes librust-sluice-dev/0.5.5-1+b1/s390x uninstallable
    • migrating librust-async-channel-dev/2.3.1-4/s390x to testing makes librust-swtchr-dev/0.1.2-2/s390x uninstallable
    • autopkgtest for rust-async-channel/2.3.1-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-async-channel dh-rust
    • Build-Depends(-Arch): rust-async-channel rust-event-listener-strategy (not considered)
    • Depends: rust-async-channel rust-event-listener-strategy (not considered)
    • Implicit dependency: rust-async-channel rust-gst-plugin-gtk4 (not considered)
    • Implicit dependency: rust-async-channel rust-smol (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-channel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-async-lock (2.8.0-2 to 3.4.0-3)
  • Migration status for rust-async-lock (2.8.0-2 to 3.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-async-lock/3.4.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-zbus/4.3.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-async-lock dh-rust
    • Build-Depends(-Arch): rust-async-lock rust-event-listener (not considered)
    • Build-Depends(-Arch): rust-async-lock rust-event-listener-strategy (not considered)
    • Depends: rust-async-lock rust-event-listener (not considered)
    • Depends: rust-async-lock rust-event-listener-strategy (not considered)
    • Implicit dependency: rust-async-lock rust-async-global-executor
    • Implicit dependency: rust-async-lock rust-async-io (not considered)
    • Implicit dependency: rust-async-lock rust-async-process
    • Implicit dependency: rust-async-lock rust-smol (not considered)
    • Implicit dependency: rust-async-lock rust-zbus (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-lock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-async-process (1.7.0-4 to 2.2.3-3)
  • Migration status for rust-async-process (1.7.0-4 to 2.2.3-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 2 days old
    • Build-Depends(-Arch): rust-async-process dh-rust
    • Build-Depends(-Arch): rust-async-process rust-async-channel (not considered)
    • Build-Depends(-Arch): rust-async-process rust-async-lock (not considered)
    • Build-Depends(-Arch): rust-async-process rust-event-listener (not considered)
    • Depends: rust-async-process rust-async-channel (not considered)
    • Depends: rust-async-process rust-async-lock (not considered)
    • Depends: rust-async-process rust-event-listener (not considered)
    • Implicit dependency: rust-async-process rust-smol (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-process.html
    • autopkgtest for rust-async-process/2.2.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-bitstream-io (2.2.0-1 to 2.5.0-1)
  • Migration status for rust-bitstream-io (2.2.0-1 to 2.5.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
    • autopkgtest for rust-bitstream-io/2.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-ivf/0.1.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-rav1e/0.7.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bitstream-io.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 ♻
• rust-event-listener (2.5.3-4 to 5.3.1-4)
  • Migration status for rust-event-listener (2.5.3-4 to 5.3.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-async-broadcast/0.5.1-2: riscv64: Regression or new test ♻ (reference ♻), s390x: Test in progress
    • autopkgtest for rust-async-lock/2.8.0-2: 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: Test in progress
    • autopkgtest for rust-async-mutex/1.4.0-1: riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test in progress
    • autopkgtest for rust-async-process/1.7.0-4: 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: Test in progress
    • autopkgtest for rust-event-listener/5.3.1-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Test in progress
    • autopkgtest for rust-sqlx-core: s390x: Test in progress
    • autopkgtest for rust-zbus/3.14.1-8: riscv64: Regression or new test ♻ (reference ♻), s390x: Test in progress
    • autopkgtest for rust-zbus/4.3.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻)
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-event-listener.html
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-event-listener dh-rust
    • Implicit dependency: rust-event-listener rust-async-broadcast (not considered)
    • Implicit dependency: rust-event-listener rust-async-channel (not considered)
    • Implicit dependency: rust-event-listener rust-async-lock (not considered)
    • Implicit dependency: rust-event-listener rust-async-mutex (not considered)
    • Implicit dependency: rust-event-listener rust-async-process
    • Implicit dependency: rust-event-listener rust-sqlx-core (not considered)
    • Implicit dependency: rust-event-listener rust-zbus (not considered)
  • 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 ♻
• rust-hyper-timeout (- to 0.4.1-2)
  • Migration status for rust-hyper-timeout (- to 0.4.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on mips64el
    • missing build on riscv64
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/r/rust-hyper-timeout.html
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for rust-hyper-timeout/0.4.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • 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 ♻
• rust-librsvg (- to 2.58.0-3)
  • Migration status for rust-librsvg (- to 2.58.0-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
    • autopkgtest for rust-librsvg/2.58.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 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-librsvg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-libseccomp (- to 0.3.0-6)
  • Migration status for rust-libseccomp (- to 0.3.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-libseccomp/0.3.0-6: amd64: Regression or new test ♻, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libseccomp.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-oo7 (0.2.1-1 to 0.3.3-2)
  • Migration status for rust-oo7 (0.2.1-1 to 0.3.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-oo7/0.3.3-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-oo7 rust-async-lock (not considered)
    • Build-Depends(-Arch): rust-oo7 rust-zbus (not considered)
    • Build-Depends(-Arch): rust-oo7 rust-zvariant (not considered)
    • Depends: rust-oo7 rust-async-lock (not considered)
    • Depends: rust-oo7 rust-zbus (not considered)
    • Depends: rust-oo7 rust-zvariant (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-oo7.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-search-provider (- to 0.8.1-2)
  • Migration status for rust-search-provider (- to 0.8.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for rust-search-provider/0.8.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-search-provider rust-zbus (not considered)
    • Depends: rust-search-provider rust-zbus (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-search-provider.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-smol (1.3.0-7 to 2.0.0-5)
  • Migration status for rust-smol (1.3.0-7 to 2.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-criterion-0.3/0.3.6-10: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-fs4/0.8.4-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-if-watch/3.2.0-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: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-smol/2.0.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-smol dh-rust
    • Build-Depends(-Arch): rust-smol rust-async-channel (not considered)
    • Build-Depends(-Arch): rust-smol rust-async-lock (not considered)
    • Build-Depends(-Arch): rust-smol rust-async-process
    • Depends: rust-smol rust-async-channel (not considered)
    • Depends: rust-smol rust-async-lock (not considered)
    • Depends: rust-smol rust-async-process
    • Implicit dependency: rust-smol rust-fs4 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-smol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-sqlx-core (0.7.3-1 to 0.7.3-3)
  • Migration status for rust-sqlx-core (0.7.3-1 to 0.7.3-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
    • autopkgtest for rust-sqlx-core/0.7.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-sqlx-core rust-event-listener (not considered)
    • Depends: rust-sqlx-core rust-event-listener (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-core.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-zbus (3.14.1-8 to 4.3.1-2)
  • Migration status for rust-zbus (3.14.1-8 to 4.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-zbus/4.3.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-zbus rust-async-broadcast (not considered)
    • Build-Depends(-Arch): rust-zbus rust-async-lock (not considered)
    • Build-Depends(-Arch): rust-zbus rust-event-listener (not considered)
    • Build-Depends(-Arch): rust-zbus rust-zbus-macros (not considered)
    • Build-Depends(-Arch): rust-zbus rust-zbus-names (not considered)
    • Build-Depends(-Arch): rust-zbus rust-zvariant (not considered)
    • Depends: rust-zbus rust-async-broadcast (not considered)
    • Depends: rust-zbus rust-async-lock (not considered)
    • Depends: rust-zbus rust-event-listener (not considered)
    • Depends: rust-zbus rust-zbus-macros (not considered)
    • Depends: rust-zbus rust-zbus-names (not considered)
    • Depends: rust-zbus rust-zvariant (not considered)
    • Implicit dependency: rust-zbus rust-glycin-utils
    • Implicit dependency: rust-zbus rust-mpris-server (not considered)
    • Implicit dependency: rust-zbus rust-oo7 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zbus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-zbus-macros (3.14.1-1 to 4.3.1-3)
  • Migration status for rust-zbus-macros (3.14.1-1 to 4.3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-zbus/4.3.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-zbus-macros/4.3.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-zbus-macros rust-zvariant-utils
    • Depends: rust-zbus-macros rust-zvariant-utils
    • Implicit dependency: rust-zbus-macros rust-zbus (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zbus-macros.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-zvariant (3.15.0-1 to 4.1.2-5)
  • Migration status for rust-zvariant (3.15.0-1 to 4.1.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-zbus/4.3.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-zvariant/4.1.2-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 0 of 5 days old
    • Build-Depends(-Arch): rust-zvariant rust-zvariant-derive
    • Depends: rust-zvariant rust-zvariant-derive
    • Implicit dependency: rust-zvariant rust-zbus (not considered)
    • Implicit dependency: rust-zvariant rust-zbus-names (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zvariant.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-zvariant-derive (3.15.0-1 to 4.1.2-2)
  • Migration status for rust-zvariant-derive (3.15.0-1 to 4.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 0 of 5 days old
    • Build-Depends(-Arch): rust-zvariant-derive rust-zvariant-utils
    • Depends: rust-zvariant-derive rust-zvariant-utils
    • Implicit dependency: rust-zvariant-derive rust-zvariant (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zvariant-derive.html
    • autopkgtest for rust-zvariant-derive/4.1.2-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 ♻
• samba (2:4.20.2+dfsg-6 to 2:4.20.2+dfsg-7)
  • Migration status for samba (2:4.20.2+dfsg-6 to 2:4.20.2+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for samba/2:4.20.2+dfsg-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for scapy/2.5.0+git20240324.2b58b51+dfsg-2: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • 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/samba.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• sks (1.1.6+git20210302.c3ba6d5a-4 to 1.1.6+git20210302.c3ba6d5a-4.1)
  • Migration status for sks (1.1.6+git20210302.c3ba6d5a-4 to 1.1.6+git20210302.c3ba6d5a-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
    • autopkgtest for sks/1.1.6+git20210302.c3ba6d5a-4.1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sks.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 ♻
• tftp-hpa (5.2+20150808-1.4 to 5.2+20240610-1)
  • Migration status for tftp-hpa (5.2+20150808-1.4 to 5.2+20240610-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for debian-edu/2.12.15: amd64: Pass, arm64: Pass, armel: Pass, armhf: Test in progress, i386: Pass, s390x: Test in progress
    • autopkgtest for debian-edu-config/2.12.44: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for fai/6.2.3: 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: Test in progress
    • autopkgtest for ironic/1:24.1.1-3: 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: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tftp-hpa.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 ♻
• titantools (4.0.11+notdfsg1-7 to 4.0.11+notdfsg1-7.1)
  • Migration status for titantools (4.0.11+notdfsg1-7 to 4.0.11+notdfsg1-7.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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• toybox (0.8.9+dfsg-1 to 0.8.9+dfsg-1.1)
  • Migration status for toybox (0.8.9+dfsg-1 to 0.8.9+dfsg-1.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for toybox/0.8.9+dfsg-1.1: amd64: Failed (not a regression), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/toybox.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 ♻
• udevil (0.4.4-3 to 0.4.4-3.1)
  • Migration status for udevil (0.4.4-3 to 0.4.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 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/udevil.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 ♻
• uhd (4.6.0.0+ds1-6 to 4.7.0.0+ds1-2)
  • Migration status for uhd (4.6.0.0+ds1-6 to 4.7.0.0+ds1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for gnss-sdr/0.0.19-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 ♻), s390x: Test in progress
    • autopkgtest for gr-osmosdr/0.2.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uhd.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 ♻
    • Reproducibility regression on i386 - info ♻
• unearth (0.16.0+ds-1 to 0.16.1-1)
  • Migration status for unearth (0.16.0+ds-1 to 0.16.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unearth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• usbrelay (1.0-2.1 to 1.0-2.2)
  • Migration status for usbrelay (1.0-2.1 to 1.0-2.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/u/usbrelay.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 ♻
• websockify (- to 0.12.0+dfsg1-1)
  • Migration status for websockify (- to 0.12.0+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating websockify would introduce bugs in testing: #1075849
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for websockify/0.12.0+dfsg1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/websockify.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 ♻
• welle.io (2.4+ds-3 to 2.4+ds-4)
  • Migration status for welle.io (2.4+ds-3 to 2.4+ds-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/welle.io.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 ♻
• wtmpdb (0.12.0-2 to 0.12.0-3)
  • Migration status for wtmpdb (0.12.0-2 to 0.12.0-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
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wtmpdb.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 ♻
• xgboost (2.0.3-1 to 2.1.0-1)
  • Migration status for xgboost (2.0.3-1 to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xgboost unsatisfiable Build-Depends(-Arch) on amd64: libdmlc-dev (>= 0.5+git20240614.1334185~)
    • xgboost unsatisfiable Build-Depends(-Arch) on arm64: libdmlc-dev (>= 0.5+git20240614.1334185~)
    • xgboost unsatisfiable Build-Depends(-Arch) on armel: libdmlc-dev (>= 0.5+git20240614.1334185~)
    • xgboost unsatisfiable Build-Depends(-Arch) on armhf: libdmlc-dev (>= 0.5+git20240614.1334185~)
    • xgboost unsatisfiable Build-Depends(-Arch) on i386: libdmlc-dev (>= 0.5+git20240614.1334185~)
    • xgboost unsatisfiable Build-Depends(-Arch) on mips64el: libdmlc-dev (>= 0.5+git20240614.1334185~)
    • xgboost unsatisfiable Build-Depends(-Arch) on ppc64el: libdmlc-dev (>= 0.5+git20240614.1334185~)
    • xgboost unsatisfiable Build-Depends(-Arch) on riscv64: libdmlc-dev (>= 0.5+git20240614.1334185~)
    • xgboost unsatisfiable Build-Depends(-Arch) on s390x: libdmlc-dev (>= 0.5+git20240614.1334185~)
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xgboost.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 ♻
• xterm (392-1 to 393-1)
  • Migration status for xterm (392-1 to 393-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for spyder-unittest/0.6.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Failed (not a regression), s390x: Failed (not a regression)
    • autopkgtest for xterm/393-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 ♻)
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• yaru-theme (23.04.4-1 to 24.04.3-1)
  • Migration status for yaru-theme (23.04.4-1 to 24.04.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/y/yaru-theme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• aerc (0.17.0-1 to 0.18.0-1)
  • Migration status for aerc (0.17.0-1 to 0.18.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): aerc golang-github-emersion-go-smtp
    • Build-Depends(-Arch): aerc golang-sourcehut-rockorager-vaxis (not considered)
    • Built-Using: aerc golang-github-emersion-go-smtp
    • Built-Using: aerc golang-github-soniakeys-quant
    • Built-Using: aerc golang-sourcehut-rockorager-vaxis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aerc.html
    • autopkgtest for aerc/0.18.0-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 ♻
    • Reproducibility regression 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
• autoconf-dickey (2.52+20231210-1 to 2.52+20240618-1)
  • Migration status for autoconf-dickey (2.52+20231210-1 to 2.52+20240618-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/autoconf-dickey.html
    • autopkgtest for autoconf-dickey/2.52+20240618-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
• biglybt (3.4.0.0-1.1 to 3.6.0.0-1)
  • Migration status for biglybt (3.4.0.0-1.1 to 3.6.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biglybt.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 ♻
• blis (0.9.0-1 to 1.0-1)
  • Migration status for blis (0.9.0-1 to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for blis/1.0-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, s390x: Pass
    • autopkgtest for hypre/2.29.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, s390x: Pass
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cappuccino (0.5.1-10.2 to 0.5.1-10.3)
  • Migration status for cappuccino (0.5.1-10.2 to 0.5.1-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:
    • Updating cappuccino will fix bugs in testing: #1065837
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cappuccino.html
    • Reproducibility regression on amd64 - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
• cgdb (0.8.0-2 to 0.8.0-3)
  • Migration status for cgdb (0.8.0-2 to 0.8.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cgdb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• colorize (0.65-1 to 0.66-1)
  • Migration status for colorize (0.65-1 to 0.66-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/colorize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• crowdsec (1.4.6-7 to 1.4.6-8)
  • Migration status for crowdsec (1.4.6-7 to 1.4.6-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for crowdsec/1.4.6-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crowdsec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• crowdsec-custom-bouncer (0.0.15-3 to 0.0.15-4)
  • Migration status for crowdsec-custom-bouncer (0.0.15-3 to 0.0.15-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
    • Built-Using: crowdsec-custom-bouncer crowdsec (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crowdsec-custom-bouncer.html
    • autopkgtest for crowdsec-custom-bouncer/0.0.15-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• crowdsec-firewall-bouncer (0.0.25-4 to 0.0.25-5)
  • Migration status for crowdsec-firewall-bouncer (0.0.25-4 to 0.0.25-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
    • Built-Using: crowdsec-firewall-bouncer crowdsec (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crowdsec-firewall-bouncer.html
    • autopkgtest for crowdsec-firewall-bouncer/0.0.25-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• darkradiant (3.8.0-2 to 3.9.0-1)
  • Migration status for darkradiant (3.8.0-2 to 3.9.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/darkradiant.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 ♻
• dnsdiag (2.1.0-1 to 2.5.0-2)
  • Migration status for dnsdiag (2.1.0-1 to 2.5.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/d/dnsdiag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• docker-pycreds (- to 0.3.0-1.2)
  • Migration status for docker-pycreds (- to 0.3.0-1.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/docker-pycreds.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• dolfin (2019.2.0~legacy20240219.1c52e83-9 to 2019.2.0~legacy20240219.1c52e83-10)
  • Migration status for dolfin (2019.2.0~legacy20240219.1c52e83-9 to 2019.2.0~legacy20240219.1c52e83-10): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on 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/d/dolfin.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• ecopcr (1.0.1+dfsg-4 to 1.0.1+dfsg-5)
  • Migration status for ecopcr (1.0.1+dfsg-4 to 1.0.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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecopcr.html
    • autopkgtest for ecopcr/1.0.1+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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• fpc (3.2.2+dfsg-33 to 3.2.2+dfsg-34)
  • Migration status for fpc (3.2.2+dfsg-33 to 3.2.2+dfsg-34): 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 fpc will fix bugs in testing: #1074706
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fpc.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for fpc/3.2.2+dfsg-34: 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
• glide (2002.04.10ds1-22 to 2002.04.10ds1-23)
  • Migration status for glide (2002.04.10ds1-22 to 2002.04.10ds1-23): Waiting for test 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/glide.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gmap (2024-05-20+ds-1 to 2024-06-24+ds-1)
  • Migration status for gmap (2024-05-20+ds-1 to 2024-06-24+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gmap.html
    • autopkgtest for gmap/2024-06-24+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • 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
• gnome-shell-extension-blur-my-shell (47-2 to 62-2)
  • Migration status for gnome-shell-extension-blur-my-shell (47-2 to 62-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: gnome-shell-extension-blur-my-shell gnome-shell (not considered)
  • Additional info:
    • Updating gnome-shell-extension-blur-my-shell will fix bugs in testing: #1076261
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-blur-my-shell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-easyscreencast (1.7.1-2 to 1.9.0-1)
  • Migration status for gnome-shell-extension-easyscreencast (1.7.1-2 to 1.9.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Depends: gnome-shell-extension-easyscreencast gnome-shell (not considered)
  • 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 ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• golang-github-alecthomas-assert (2.6.0-1 to 2.7.0-1)
  • Migration status for golang-github-alecthomas-assert (2.6.0-1 to 2.7.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-alecthomas-assert.html
    • autopkgtest for golang-github-alecthomas-assert/2.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
• golang-github-alecthomas-chroma-v2 (2.13.0-1 to 2.14.0-1)
  • Migration status for golang-github-alecthomas-chroma-v2 (2.13.0-1 to 2.14.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): golang-github-alecthomas-chroma-v2 golang-github-alecthomas-assert
    • Depends: golang-github-alecthomas-chroma-v2 golang-github-alecthomas-assert
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-alecthomas-chroma-v2.html
    • autopkgtest for golang-github-alecthomas-chroma-v2/2.14.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
• golang-github-emersion-go-smtp (0.12.1-1 to 0.21.2-1)
  • Migration status for golang-github-emersion-go-smtp (0.12.1-1 to 0.21.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-emersion-go-smtp.html
    • autopkgtest for golang-github-emersion-go-smtp/0.21.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
• golang-github-evanw-esbuild (0.20.2-1 to 0.21.4-1)
  • Migration status for golang-github-evanw-esbuild (0.20.2-1 to 0.21.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-evanw-esbuild.html
    • autopkgtest for golang-github-evanw-esbuild/0.21.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
• golang-github-soniakeys-quant (- to 1.0.0-2)
  • Migration status for golang-github-soniakeys-quant (- to 1.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-soniakeys-quant.html
    • autopkgtest for golang-github-soniakeys-quant/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
• golang-github-yuin-goldmark (1.7.1-1 to 1.7.4-1)
  • Migration status for golang-github-yuin-goldmark (1.7.1-1 to 1.7.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-yuin-goldmark.html
    • autopkgtest for golang-github-yuin-goldmark/1.7.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
• golang-github-yuin-goldmark-emoji (1.0.2-1 to 1.0.3-1)
  • Migration status for golang-github-yuin-goldmark-emoji (1.0.2-1 to 1.0.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-yuin-goldmark-emoji.html
    • autopkgtest for golang-github-yuin-goldmark-emoji/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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• golang-sourcehut-rockorager-vaxis (- to 0.9.2-2)
  • Migration status for golang-sourcehut-rockorager-vaxis (- to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-sourcehut-rockorager-vaxis/0.9.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): golang-sourcehut-rockorager-vaxis golang-github-soniakeys-quant
    • Depends: golang-sourcehut-rockorager-vaxis golang-github-soniakeys-quant
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-sourcehut-rockorager-vaxis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• goobox (3.6.0-13 to 3.6.0-14)
  • Migration status for goobox (3.6.0-13 to 3.6.0-14): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goobox.html
    • autopkgtest for goobox/3.6.0-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
• idevicerestore (1.0.0-3 to 1.0.0-4)
  • Migration status for idevicerestore (1.0.0-3 to 1.0.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Depends: idevicerestore libimobiledevice
    • Depends: idevicerestore libplist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/idevicerestore.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• intel-gmmlib (22.3.19+ds1-1 to 22.4.1+ds1-1)
  • Migration status for intel-gmmlib (22.3.19+ds1-1 to 22.4.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-gmmlib.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• intel-media-driver (24.2.2+dfsg1-1 to 24.2.5+dfsg1-1)
  • Migration status for intel-media-driver (24.2.2+dfsg1-1 to 24.2.5+dfsg1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): intel-media-driver intel-gmmlib
    • Depends: intel-media-driver intel-gmmlib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-media-driver.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• intel-media-driver-non-free (24.2.2+ds1-1 to 24.2.5+ds1-1)
  • Migration status for intel-media-driver-non-free (24.2.2+ds1-1 to 24.2.5+ds1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): intel-media-driver-non-free intel-gmmlib
    • Depends: intel-media-driver-non-free intel-gmmlib
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• ipheth (1.0-5.1 to 1.0-5.2)
  • Migration status for ipheth (1.0-5.1 to 1.0-5.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): ipheth libimobiledevice
    • Depends: ipheth libimobiledevice
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ipheth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ivar (1.4.2+dfsg-3 to 1.4.3+dfsg-2)
  • Migration status for ivar (1.4.2+dfsg-3 to 1.4.3+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ivar.html
    • autopkgtest for ivar/1.4.3+dfsg-2: amd64: Pass, arm64: Pass, i386: Pass, riscv64: 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
• jgit (6.7.0-1 to 6.7.0-2)
  • Migration status for jgit (6.7.0-1 to 6.7.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jgit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kio-extras (4:23.08.4-1 to 4:23.08.4-2)
  • Migration status for kio-extras (4:23.08.4-1 to 4:23.08.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Depends: kio-extras libimobiledevice
    • Depends: kio-extras libplist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kio-extras.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• kodi (2:20.5+dfsg-4 to 2:20.5+dfsg-5)
  • Migration status for kodi (2:20.5+dfsg-4 to 2:20.5+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 2 days old
    • Depends: kodi libgcrypt20
    • Depends: kodi libplist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi.html
    • autopkgtest for kodi/2:20.5+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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• labplot (2.10.1-3 to 2.11.0-1)
  • Migration status for labplot (2.10.1-3 to 2.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/labplot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libedlib (1.2.7-5 to 1.2.7-6)
  • Migration status for libedlib (1.2.7-5 to 1.2.7-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libedlib.html
    • autopkgtest for libedlib/1.2.7-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
• libgpod (0.8.3-19.1 to 0.8.3-21)
  • Migration status for libgpod (0.8.3-19.1 to 0.8.3-21): Waiting for test 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: libgpod libimobiledevice
    • Depends: libgpod libplist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgpod.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libirclib-java (- to 2.0.0~alpha3-1)
  • Migration status for libirclib-java (- to 2.0.0~alpha3-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/libi/libirclib-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libplayerone (3.1.0+20221218103507-1 to 3.1.0+20221218103507-2)
  • Migration status for libplayerone (3.1.0+20221218103507-1 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
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• libsolv (0.7.29-1 to 0.7.30-1)
  • Migration status for libsolv (0.7.29-1 to 0.7.30-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsolv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• linux (6.9.8-1 to 6.9.9-1)
  • Migration status for linux (6.9.8-1 to 6.9.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for debvm/0.3.1: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for linux/6.9.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 ♻)
    • Too young, only 1 of 5 days old
    • Implicit dependency: linux linux-signed-amd64
    • Implicit dependency: linux linux-signed-arm64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• linux-signed-amd64 (6.9.8+1 to 6.9.9+1)
  • Migration status for linux-signed-amd64 (6.9.8+1 to 6.9.9+1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): linux-signed-amd64 linux (not considered)
    • Built-Using: linux-signed-amd64 linux (not considered)
    • Depends: linux-signed-amd64 linux (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-signed-amd64.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• linux-signed-arm64 (6.9.8+1 to 6.9.9+1)
  • Migration status for linux-signed-arm64 (6.9.8+1 to 6.9.9+1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): linux-signed-arm64 linux (not considered)
    • Built-Using: linux-signed-arm64 linux (not considered)
    • Depends: linux-signed-arm64 linux (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• lombok-patcher (0.42-3 to 0.50-1)
  • Migration status for lombok-patcher (0.42-3 to 0.50-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/lombok-patcher.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• matrix-synapse (1.103.0-4 to 1.103.0-5)
  • Migration status for matrix-synapse (1.103.0-4 to 1.103.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:
    • Updating matrix-synapse will fix bugs in testing: #1065900
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matrix-synapse.html
    • autopkgtest for matrix-synapse/1.103.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
• mdtraj (1.10.0-2 to 1.10.0-3)
  • Migration status for mdtraj (1.10.0-2 to 1.10.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 2 days old
  • Additional info:
    • Updating mdtraj will fix bugs in testing: #1076166
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdtraj.html
    • autopkgtest for mdtraj/1.10.0-3: amd64: Pass, arm64: Pass, i386: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• mkvtoolnix (85.0-1 to 86.0-1)
  • Migration status for mkvtoolnix (85.0-1 to 86.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkvtoolnix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mpi4py (3.1.6-1 to 3.1.6-6)
  • Migration status for mpi4py (3.1.6-1 to 3.1.6-6): 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 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:
    • Updating mpi4py will fix bugs in testing: #1075980
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpi4py.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• muon-meson (0.2.0-2 to 0.2.0-3)
  • Migration status for muon-meson (0.2.0-2 to 0.2.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/muon-meson.html
    • autopkgtest for muon-meson/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 ♻
    • Required age reduced by 3 days because of autopkgtest
• nautilus (45.2.1-4 to 46.2-1)
  • Migration status for nautilus (45.2.1-4 to 46.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducibility regression on i386 - info ♻
• neochat (23.08.5-2 to 23.08.5-3)
  • Migration status for neochat (23.08.5-2 to 23.08.5-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neochat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• 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
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• oscar (1.5.1-1 to 1.5.3-1)
  • Migration status for oscar (1.5.1-1 to 1.5.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oscar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pcb-rnd (3.1.4-3 to 3.1.5-2)
  • Migration status for pcb-rnd (3.1.4-3 to 3.1.5-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 1 of 5 days old
    • Build-Depends(-Arch): pcb-rnd libgd2
    • Depends: pcb-rnd libgd2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcb-rnd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• peewee (3.17.5+dfsg-1 to 3.17.6+dfsg-1)
  • Migration status for peewee (3.17.5+dfsg-1 to 3.17.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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/peewee.html
    • autopkgtest for peewee/3.17.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pencil2d (0.6.6-3 to 0.7.0-1)
  • Migration status for pencil2d (0.6.6-3 to 0.7.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pencil2d.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• poetry (1.8.3+dfsg-2 to 1.8.3+dfsg-3)
  • Migration status for poetry (1.8.3+dfsg-2 to 1.8.3+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating poetry will fix bugs in testing: #1074725
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poetry.html
    • autopkgtest for poetry/1.8.3+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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• precious (0.6.0-6 to 0.7.3-1)
  • Migration status for precious (0.6.0-6 to 0.7.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 1 of 5 days old
    • Build-Depends(-Arch): precious dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/precious.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 ♻
• pvrg-jpeg (1.2.1+dfsg1-7 to 1.2.1+dfsg1-8)
  • Migration status for pvrg-jpeg (1.2.1+dfsg1-7 to 1.2.1+dfsg1-8): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pvrg-jpeg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pyqt-builder (1.16.3+dfsg-1 to 1.16.4+dfsg-1)
  • Migration status for pyqt-builder (1.16.3+dfsg-1 to 1.16.4+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyqt-builder.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-asyncclick (8.1.7.0+async-3 to 8.1.7.2-1)
  • Migration status for python-asyncclick (8.1.7.0+async-3 to 8.1.7.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-asyncclick.html
    • autopkgtest for python-asyncclick/8.1.7.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
• python-av (11.0.0-4 to 12.2.0-2)
  • Migration status for python-av (11.0.0-4 to 12.2.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-av.html
    • autopkgtest for python-av/12.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-dbusmock (0.31.1-1 to 0.32.1-1)
  • Migration status for python-dbusmock (0.31.1-1 to 0.32.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-dbusmock/0.32.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for upower/1.90.3-1: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dbusmock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-marathon (0.13.0-5 to 0.13.0-6)
  • Migration status for python-marathon (0.13.0-5 to 0.13.0-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:
    • Updating python-marathon will fix bugs in testing: #1074710
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-marathon.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 ♻
• python-openai (1.12.0-1 to 1.35.12-1)
  • Migration status for python-openai (1.12.0-1 to 1.35.12-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-openai.html
    • autopkgtest for python-openai/1.35.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-parse (1.19.0-0.2 to 1.20.2-1)
  • Migration status for python-parse (1.19.0-0.2 to 1.20.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-parse.html
    • autopkgtest for python-parse/1.20.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
• python-shapely (2.0.4-1 to 2.0.5-1)
  • Migration status for python-shapely (2.0.4-1 to 2.0.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-shapely.html
    • autopkgtest for antimeridian/0.3.7-1: s390x: Pass
    • autopkgtest for python-shapely/2.0.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-tenacity (8.4.1-1 to 8.4.2+really8.4.1-1)
  • Migration status for python-tenacity (8.4.1-1 to 8.4.2+really8.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-tenacity.html
    • autopkgtest for python-tenacity/8.4.2+really8.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
• rapidfuzz (3.6.2+ds-3 to 3.9.4+ds-1)
  • Migration status for rapidfuzz (3.6.2+ds-3 to 3.9.4+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rapidfuzz rapidfuzz-cpp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rapidfuzz.html
    • autopkgtest for rapidfuzz/3.9.4+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 ♻
• rapidfuzz-cpp (3.0.2-5 to 3.0.5-1)
  • Migration status for rapidfuzz-cpp (3.0.2-5 to 3.0.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rapidfuzz-cpp.html
    • autopkgtest for rapidfuzz-cpp/3.0.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
• ruby-web-console (4.2.0-1 to 4.2.1-1)
  • Migration status for ruby-web-console (4.2.0-1 to 4.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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-web-console.html
    • autopkgtest for ruby-web-console/4.2.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 ♻
• rumur (2023.11.27-1 to 2024.05.07-1)
  • Migration status for rumur (2023.11.27-1 to 2024.05.07-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 rumur/2024.05.07-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rumur.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-async-broadcast (0.5.1-2 to 0.7.1-1)
  • Migration status for rust-async-broadcast (0.5.1-2 to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-async-broadcast/0.7.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-zbus/4.3.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-async-broadcast rust-event-listener (not considered)
    • Build-Depends(-Arch): rust-async-broadcast rust-event-listener-strategy (not considered)
    • Depends: rust-async-broadcast rust-event-listener (not considered)
    • Depends: rust-async-broadcast rust-event-listener-strategy (not considered)
    • Implicit dependency: rust-async-broadcast rust-zbus (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-broadcast.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 ♻
• rust-async-generic (- to 1.1.0-1)
  • Migration status for rust-async-generic (- to 1.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-generic.html
    • autopkgtest for rust-async-generic/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
• rust-async-global-executor (2.4.1-1 to 2.4.1-4)
  • Migration status for rust-async-global-executor (2.4.1-1 to 2.4.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-async-global-executor rust-async-channel (not considered)
    • Build-Depends(-Arch): rust-async-global-executor rust-async-lock (not considered)
    • Depends: rust-async-global-executor rust-async-channel (not considered)
    • Depends: rust-async-global-executor rust-async-lock (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-global-executor.html
    • autopkgtest for rust-async-global-executor/2.4.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-async-io (2.3.1-2 to 2.3.3-3)
  • Migration status for rust-async-io (2.3.1-2 to 2.3.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-async-io/2.3.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-async-process/1.7.0-4: 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 rust-if-watch/3.2.0-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: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-prodash/28.0.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-smol/1.3.0-7: 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 rust-zbus/3.14.1-8: riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-zbus/4.3.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-async-io rust-async-lock (not considered)
    • Depends: rust-async-io rust-async-lock (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-io.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 ♻
• rust-async-mutex (1.4.0-1 to 1.4.0-3)
  • Migration status for rust-async-mutex (1.4.0-1 to 1.4.0-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
    • autopkgtest for rust-async-mutex/1.4.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 ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-async-mutex rust-event-listener (not considered)
    • Depends: rust-async-mutex rust-event-listener (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-mutex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-cargo (0.70.1-3 to 0.76.0-2)
  • Migration status for rust-cargo (0.70.1-3 to 0.76.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for rust-cargo/0.76.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 ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-cargo rust-cargo-credential
    • Build-Depends(-Arch): rust-cargo rust-cargo-credential-libsecret
    • Build-Depends(-Arch): rust-cargo rust-crates-io
    • Build-Depends(-Arch): rust-cargo rust-gix
    • Depends: rust-cargo rust-cargo-credential
    • Depends: rust-cargo rust-cargo-credential-libsecret
    • Depends: rust-cargo rust-crates-io
    • Depends: rust-cargo rust-gix
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-cargo-credential (- to 0.4.1-2)
  • Migration status for rust-cargo-credential (- to 0.4.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-credential.html
    • autopkgtest for rust-cargo-credential/0.4.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-event-listener-strategy (- to 0.5.2-2)
  • Migration status for rust-event-listener-strategy (- to 0.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-async-channel/1.9.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-event-listener-strategy/0.5.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 ♻
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-event-listener-strategy rust-event-listener (not considered)
    • Depends: rust-event-listener-strategy rust-event-listener (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-event-listener-strategy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-fs4 (0.7.0-1 to 0.8.4-3)
  • Migration status for rust-fs4 (0.7.0-1 to 0.8.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-fs4/0.8.4-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 1 of 5 days old
    • Depends: rust-fs4 rust-smol (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fs4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-glycin (- to 1.0.1-2)
  • Migration status for rust-glycin (- to 1.0.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for rust-glycin/1.0.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-glycin rust-async-lock (not considered)
    • Build-Depends(-Arch): rust-glycin rust-glycin-utils
    • Build-Depends(-Arch): rust-glycin rust-libseccomp (not considered)
    • Build-Depends(-Arch): rust-glycin rust-zbus (not considered)
    • Depends: rust-glycin rust-async-lock (not considered)
    • Depends: rust-glycin rust-glycin-utils
    • Depends: rust-glycin rust-libseccomp (not considered)
    • Depends: rust-glycin rust-zbus (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-glycin.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 ♻
• rust-glycin-utils (0.1.0-3 to 1.0.1-2)
  • Migration status for rust-glycin-utils (0.1.0-3 to 1.0.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-glycin-utils rust-libseccomp (not considered)
    • Build-Depends(-Arch): rust-glycin-utils rust-zbus (not considered)
    • Depends: rust-glycin-utils rust-libseccomp (not considered)
    • Depends: rust-glycin-utils rust-zbus (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-glycin-utils.html
    • autopkgtest for rust-glycin-utils/1.0.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-gst-plugin-gtk4 (0.12.6-1 to 0.12.7-2)
  • Migration status for rust-gst-plugin-gtk4 (0.12.6-1 to 0.12.7-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for rust-gst-plugin-gtk4/0.12.7-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-gst-plugin-gtk4 rust-async-channel (not considered)
    • Depends: rust-gst-plugin-gtk4 rust-async-channel (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gst-plugin-gtk4.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 ♻
• rust-hickory-server (- to 0.24.1-2)
  • Migration status for rust-hickory-server (- to 0.24.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for rust-hickory-server/0.24.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hickory-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-libbpf-sys (- to 1.4.2-2)
  • Migration status for rust-libbpf-sys (- to 1.4.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/rust-libbpf-sys.html
    • autopkgtest for rust-libbpf-sys/1.4.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-mpris-server (0.7.0-1 to 0.8.0-2)
  • Migration status for rust-mpris-server (0.7.0-1 to 0.8.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for rust-mpris-server/0.8.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-mpris-server rust-async-channel (not considered)
    • Build-Depends(-Arch): rust-mpris-server rust-zbus (not considered)
    • Depends: rust-mpris-server rust-async-channel (not considered)
    • Depends: rust-mpris-server rust-zbus (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-mpris-server.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 ♻
• rust-p521 (0.13.3-1 to 0.13.3-2)
  • Migration status for rust-p521 (0.13.3-1 to 0.13.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-p521/0.13.3-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-p521.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-proptest (1.0.0-3 to 1.5.0-1)
  • Migration status for rust-proptest (1.0.0-3 to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-proptest/1.5.0-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proptest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-pyo3 (0.20.2-3 to 0.20.2-4)
  • Migration status for rust-pyo3 (0.20.2-3 to 0.20.2-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/r/rust-pyo3.html
    • autopkgtest for rust-pyo3/0.20.2-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-version-sync (0.9.5-3 to 0.9.5-4)
  • Migration status for rust-version-sync (0.9.5-3 to 0.9.5-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): rust-version-sync dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-version-sync.html
    • autopkgtest for rust-version-sync/0.9.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-zbus-names (2.6.0-1 to 3.0.0-3)
  • Migration status for rust-zbus-names (2.6.0-1 to 3.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-zbus/4.3.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-zbus-names/3.0.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): rust-zbus-names rust-zvariant (not considered)
    • Depends: rust-zbus-names rust-zvariant (not considered)
    • Implicit dependency: rust-zbus-names rust-zbus (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zbus-names.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 ♻
• rust-zvariant-utils (1.0.1-2 to 2.0.0-2)
  • Migration status for rust-zvariant-utils (1.0.1-2 to 2.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Implicit dependency: rust-zvariant-utils rust-zbus-macros (not considered)
    • Implicit dependency: rust-zvariant-utils rust-zvariant-derive
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zvariant-utils.html
    • autopkgtest for rust-zvariant-utils/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
• scikit-rf (1.0.0-1.1 to 1.1.0-1)
  • Migration status for scikit-rf (1.0.0-1.1 to 1.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scikit-rf.html
    • autopkgtest for scikit-rf/1.1.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• solid (5.115.0-2 to 5.115.0-3)
  • Migration status for solid (5.115.0-2 to 5.115.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 2 days old
    • Depends: solid libimobiledevice
    • Depends: solid libplist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/solid.html
    • autopkgtest for solid/5.115.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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• swayimg (2.3-1 to 2.4-1)
  • Migration status for swayimg (2.3-1 to 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swayimg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• systemd-boot-installer (0.3 to 0.4)
  • Migration status for systemd-boot-installer (0.3 to 0.4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • 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 ♻
• texttable (1.6.7-1 to 1.7.0-1)
  • Migration status for texttable (1.6.7-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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/texttable.html
    • autopkgtest for texttable/1.7.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 ♻
• tigervnc (1.13.1+dfsg-2 to 1.13.1+dfsg-3)
  • Migration status for tigervnc (1.13.1+dfsg-2 to 1.13.1+dfsg-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
    • Too young, only 1 of 5 days old
    • Depends: tigervnc libgcrypt20
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tigervnc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• txdbus (1.1.0-3 to 1.1.0-4)
  • Migration status for txdbus (1.1.0-3 to 1.1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for txdbus/1.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 ♻
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating txdbus will fix bugs in testing: #1074642
    • 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 ♻
• varna (3-93+ds-5 to 3-93+ds-6)
  • Migration status for varna (3-93+ds-5 to 3-93+ds-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating varna will fix bugs in testing: #1073230
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/varna.html
    • autopkgtest for varna/3-93+ds-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
• vsftpd (3.0.3-13 to 3.0.3-13.1)
  • Migration status for vsftpd (3.0.3-13 to 3.0.3-13.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 vsftpd will fix bugs in testing: #1042969
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vsftpd.html
    • autopkgtest for vsftpd/3.0.3-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
• workrave (1.10.52-2 to 1.10.52-3)
  • Migration status for workrave (1.10.52-2 to 1.10.52-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Depends: workrave gnome-shell (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/workrave.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• zope.deferredimport (- to 5.0-2)
  • Migration status for zope.deferredimport (- to 5.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zope.deferredimport.html
    • autopkgtest for zope.deferredimport/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
• accessible-pygments (- to 0.0.5-1)
  • Migration status for accessible-pygments (- to 0.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by eamanu@yaerobi.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/accessible-pygments.html
    • autopkgtest for accessible-pygments/0.0.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
    • 2 days old (needed 2 days)
• arping (2.24-2 to 2.25-1)
  • Migration status for arping (2.24-2 to 2.25-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arping.html
    • autopkgtest for arping/2.25-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 ♻
• ayatana-indicator-keyboard (24.5.0-1 to 24.7.0-2)
  • Migration status for ayatana-indicator-keyboard (24.5.0-1 to 24.7.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-keyboard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• buteo-sync-plugins (- to 0.8.35-2)
  • Migration status for buteo-sync-plugins (- to 0.8.35-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): buteo-sync-plugins nemo-qml-plugin-contacts (not considered)
    • Depends: buteo-sync-plugins nemo-qml-plugin-contacts (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/buteo-sync-plugins.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• clapper (0.5.2-8 to 0.6.1-3)
  • Migration status for clapper (0.5.2-8 to 0.6.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/clapper.html
    • autopkgtest for clapper/0.6.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 amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• contactsd (- to 1.4.14-2)
  • Migration status for contactsd (- to 1.4.14-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): contactsd nemo-qml-plugin-contacts (not considered)
    • Depends: contactsd nemo-qml-plugin-contacts (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/contactsd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• cryptokit (1.19-1 to 1.20.1-1)
  • Migration status for cryptokit (1.19-1 to 1.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cryptokit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ddclient (3.10.0-2.1 to 3.11.2-1)
  • Migration status for ddclient (3.10.0-2.1 to 3.11.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/ddclient.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• dmitry (1.3a-4 to 1.3a-6)
  • Migration status for dmitry (1.3a-4 to 1.3a-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dmitry.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• dotenv-cli (3.3.0-1 to 3.3.1-1)
  • Migration status for dotenv-cli (3.3.0-1 to 3.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by venthur, a new source-only upload is needed to allow migration
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dotenv-cli.html
    • autopkgtest for dotenv-cli/3.3.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 ♻
• e2tools (0.1.0-3 to 0.1.0-4)
  • Migration status for e2tools (0.1.0-3 to 0.1.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/e2tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• elfutils (0.191-1 to 0.191-2)
  • Migration status for elfutils (0.191-1 to 0.191-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/elfutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• fl-cow (0.6-7 to 0.6-9)
  • Migration status for fl-cow (0.6-7 to 0.6-9): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fl-cow.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• flatbuffers (2.0.8+dfsg1-6 to 23.5.26+dfsg-1)
  • Migration status for flatbuffers (2.0.8+dfsg1-6 to 23.5.26+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flatbuffers would introduce bugs in testing: #1043102
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flatbuffers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• fonts-cantarell (0.303.1-1 to 0.303.1-2)
  • Migration status for fonts-cantarell (0.303.1-1 to 0.303.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 fonts-cantarell will fix bugs in testing: #1065860
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-cantarell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gammu (1.42.0-8.1 to 1.42.0-9)
  • Migration status for gammu (1.42.0-8.1 to 1.42.0-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/gammu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gcc-13 (13.3.0-1 to 13.3.0-3)
  • Migration status for gcc-13 (13.3.0-1 to 13.3.0-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
    • autopkgtest for gcc-13/13.3.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating gcc-13 will fix bugs in testing: #1074577
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-13.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 ♻
• git-delta (0.17.0-2 to 0.17.0-3)
  • Migration status for git-delta (0.17.0-2 to 0.17.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
    • Build-Depends(-Arch): git-delta dh-rust
    • Build-Depends(-Arch): git-delta rust-sysinfo (not considered)
    • Built-Using: git-delta rust-fast-srgb8
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-delta.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-control-center (1:46.1-2 to 1:46.3-1)
  • Migration status for gnome-control-center (1:46.1-2 to 1:46.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
    • Depends: gnome-control-center gnome-remote-desktop
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-control-center.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-kiosk (- to 46.0-3)
  • Migration status for gnome-kiosk (- to 46.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
    • Build-Depends(-Arch): gnome-kiosk mutter (not considered)
    • Depends: gnome-kiosk mutter (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-kiosk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-remote-desktop (- to 46.3-3)
  • Migration status for gnome-remote-desktop (- to 46.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
    • Build-Depends(-Arch): gnome-remote-desktop mutter (not considered)
    • Depends: gnome-remote-desktop mutter (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-remote-desktop.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-3 to 46.0-5)
  • Migration status for gnome-session (46.0-3 to 46.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-session.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell (44.9-2 to 46.3.1-2)
  • Migration status for gnome-shell (44.9-2 to 46.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating gnome-shell/46.3.1-2/amd64 to testing makes gnome-shell-extension-gamemode/8-3/amd64 uninstallable
    • migrating gnome-shell/46.3.1-2/amd64 to testing makes gnome-shell-extension-gpaste/44.1-2.1/amd64 uninstallable
    • migrating gnome-shell/46.3.1-2/amd64 to testing makes gnome-shell-extension-hamster/0.10.0+git20230901-1/amd64 uninstallable
    • migrating gnome-shell/46.3.1-2/amd64 to testing makes gnome-shell-extension-hide-activities/44-1/amd64 uninstallable
    • migrating gnome-shell/46.3.1-2/amd64 to testing makes gnome-shell-extension-impatience/0.4.8-3/amd64 uninstallable
    • migrating gnome-shell/46.3.1-2/amd64 to testing makes gnome-shell-extension-no-annoyance/0+20220925-c6804a4-3.1/amd64 uninstallable
    • migrating gnome-shell/46.3.1-2/amd64 to testing makes gnome-shell-extension-panel-osd/1.0.50.gc032923-4/amd64 uninstallable
    • migrating gnome-shell/46.3.1-2/amd64 to testing makes gnome-shell-extension-shortcuts/1.3.7-1/amd64 uninstallable
    • migrating gnome-shell/46.3.1-2/amd64 to testing makes gnome-shell-extension-system-monitor/40-6/amd64 uninstallable
    • migrating gnome-shell/46.3.1-2/amd64 to testing makes gnome-shell-extension-vertical-overview/10-2/amd64 uninstallable
    • migrating gnome-shell/46.3.1-2/arm64 to testing makes gnome-shell-extension-gamemode/8-3/arm64 uninstallable
    • migrating gnome-shell/46.3.1-2/arm64 to testing makes gnome-shell-extension-gpaste/44.1-2.1/arm64 uninstallable
    • migrating gnome-shell/46.3.1-2/arm64 to testing makes gnome-shell-extension-hamster/0.10.0+git20230901-1/arm64 uninstallable
    • migrating gnome-shell/46.3.1-2/arm64 to testing makes gnome-shell-extension-hide-activities/44-1/arm64 uninstallable
    • migrating gnome-shell/46.3.1-2/arm64 to testing makes gnome-shell-extension-impatience/0.4.8-3/arm64 uninstallable
    • migrating gnome-shell/46.3.1-2/arm64 to testing makes gnome-shell-extension-no-annoyance/0+20220925-c6804a4-3.1/arm64 uninstallable
    • migrating gnome-shell/46.3.1-2/arm64 to testing makes gnome-shell-extension-panel-osd/1.0.50.gc032923-4/arm64 uninstallable
    • migrating gnome-shell/46.3.1-2/arm64 to testing makes gnome-shell-extension-shortcuts/1.3.7-1/arm64 uninstallable
    • migrating gnome-shell/46.3.1-2/arm64 to testing makes gnome-shell-extension-system-monitor/40-6/arm64 uninstallable
    • migrating gnome-shell/46.3.1-2/arm64 to testing makes gnome-shell-extension-vertical-overview/10-2/arm64 uninstallable
    • migrating gnome-shell/46.3.1-2/armel to testing makes gnome-shell-extension-panel-osd/1.0.50.gc032923-4/armel uninstallable
    • migrating gnome-shell/46.3.1-2/armhf to testing makes gnome-shell-extension-panel-osd/1.0.50.gc032923-4/armhf uninstallable
    • migrating gnome-shell/46.3.1-2/i386 to testing makes gnome-shell-extension-panel-osd/1.0.50.gc032923-4/i386 uninstallable
    • migrating gnome-shell/46.3.1-2/mips64el to testing makes gnome-shell-extension-panel-osd/1.0.50.gc032923-4/mips64el uninstallable
    • migrating gnome-shell/46.3.1-2/ppc64el to testing makes gnome-shell-extension-panel-osd/1.0.50.gc032923-4/ppc64el uninstallable
    • migrating gnome-shell/46.3.1-2/s390x to testing makes gnome-shell-extension-panel-osd/1.0.50.gc032923-4/s390x uninstallable
    • Build-Depends(-Arch): gnome-shell mutter (not considered)
    • Depends: gnome-shell mutter (not considered)
    • Implicit dependency: gnome-shell gnome-shell-extension-autohidetopbar
    • Implicit dependency: gnome-shell gnome-shell-extension-blur-my-shell
    • Implicit dependency: gnome-shell gnome-shell-extension-caffeine
    • Implicit dependency: gnome-shell gnome-shell-extension-dashtodock
    • Implicit dependency: gnome-shell gnome-shell-extension-desktop-icons-ng
    • Implicit dependency: gnome-shell gnome-shell-extension-easyscreencast
    • Implicit dependency: gnome-shell gnome-shell-extension-espresso
    • Implicit dependency: gnome-shell gnome-shell-extension-flypie (not considered)
    • Implicit dependency: gnome-shell gnome-shell-extension-freon
    • Implicit dependency: gnome-shell gnome-shell-extension-gsconnect
    • Implicit dependency: gnome-shell gnome-shell-extension-kimpanel
    • Implicit dependency: gnome-shell gnome-shell-extension-runcat
    • Implicit dependency: gnome-shell gnome-shell-extension-tiling-assistant
    • Implicit dependency: gnome-shell gnome-shell-extensions
    • Implicit dependency: gnome-shell gnome-shell-extensions-extra
    • Implicit dependency: gnome-shell gnome-shell-pomodoro
    • Implicit dependency: gnome-shell workrave
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2 days old (needed 2 days)
• gnome-shell-extension-autohidetopbar (1:114-1 to 1:117-1)
  • Migration status for gnome-shell-extension-autohidetopbar (1:114-1 to 1:117-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: gnome-shell-extension-autohidetopbar gnome-shell (not considered)
  • Additional info:
    • Updating gnome-shell-extension-autohidetopbar will fix bugs in testing: #1052089
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-autohidetopbar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-caffeine (49-1 to 53-1)
  • Migration status for gnome-shell-extension-caffeine (49-1 to 53-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): gnome-shell-extension-caffeine gnome-shell (not considered)
    • Depends: gnome-shell-extension-caffeine gnome-shell (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-caffeine.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-dashtodock (87+really84-1 to 92-1)
  • Migration status for gnome-shell-extension-dashtodock (87+really84-1 to 92-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: gnome-shell-extension-dashtodock gnome-shell (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-dashtodock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-desktop-icons-ng (46+really47.0.4-2 to 47.0.11-2)
  • Migration status for gnome-shell-extension-desktop-icons-ng (46+really47.0.4-2 to 47.0.11-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: gnome-shell-extension-desktop-icons-ng gnome-shell (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-desktop-icons-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-espresso (8-2 to 10-2)
  • Migration status for gnome-shell-extension-espresso (8-2 to 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
    • Depends: gnome-shell-extension-espresso gnome-shell (not considered)
  • 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 (52+dfsg-2 to 56+dfsg-2)
  • Migration status for gnome-shell-extension-freon (52+dfsg-2 to 56+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: gnome-shell-extension-freon gnome-shell (not considered)
  • 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-gsconnect (55-3 to 57-2)
  • Migration status for gnome-shell-extension-gsconnect (55-3 to 57-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: gnome-shell-extension-gsconnect gnome-shell (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-gsconnect.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-kimpanel (0.0~git20240317.really.20230412-1 to 0.0~git20240513.9a7c460-1)
  • Migration status for gnome-shell-extension-kimpanel (0.0~git20240317.really.20230412-1 to 0.0~git20240513.9a7c460-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: gnome-shell-extension-kimpanel gnome-shell (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-kimpanel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extension-runcat (23-1 to 27-2)
  • Migration status for gnome-shell-extension-runcat (23-1 to 27-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: gnome-shell-extension-runcat gnome-shell (not considered)
  • 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 ♻
• gnome-shell-extension-tiling-assistant (41-3 to 47-1)
  • Migration status for gnome-shell-extension-tiling-assistant (41-3 to 47-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: gnome-shell-extension-tiling-assistant gnome-shell (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-tiling-assistant.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extensions (44.0-2 to 46.2-2)
  • Migration status for gnome-shell-extensions (44.0-2 to 46.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
    • Depends: gnome-shell-extensions gnome-shell (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extensions.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-extensions-extra (20231210-1 to 20240414-2)
  • Migration status for gnome-shell-extensions-extra (20231210-1 to 20240414-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: gnome-shell-extensions-extra gnome-shell (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extensions-extra.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-shell-pomodoro (0.23.1-1 to 0.25.2-1)
  • Migration status for gnome-shell-pomodoro (0.23.1-1 to 0.25.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnome-shell-pomodoro gnome-shell (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-pomodoro.html
    • autopkgtest for gnome-shell-pomodoro/0.25.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)
• gtkman (- to 2.3.3-1)
  • Migration status for gtkman (- to 2.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtkman.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• identify (2.5.36-1 to 2.6.0-1)
  • Migration status for identify (2.5.36-1 to 2.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/identify.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ideviceinstaller (1.1.1-1 to 1.1.1+git20240518-1)
  • Migration status for ideviceinstaller (1.1.1-1 to 1.1.1+git20240518-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): ideviceinstaller libimobiledevice
    • Build-Depends(-Arch): ideviceinstaller libplist
    • Depends: ideviceinstaller libimobiledevice
    • Depends: ideviceinstaller libplist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ideviceinstaller.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 ♻
• ifuse (1.1.4~git20181007.3b00243-1 to 1.1.4-2)
  • Migration status for ifuse (1.1.4~git20181007.3b00243-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 2 of 5 days old
    • Build-Depends(-Arch): ifuse libimobiledevice
    • Build-Depends(-Arch): ifuse libplist
    • Depends: ifuse libimobiledevice
    • Depends: ifuse libplist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ifuse.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 ♻
• imsprog (1.3.9-1 to 1.4.2-1)
  • Migration status for imsprog (1.3.9-1 to 1.4.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/imsprog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• inotify-info (0.0.2-1 to 0.0.3-1)
  • Migration status for inotify-info (0.0.2-1 to 0.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/i/inotify-info.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• labwc (0.7.2-2 to 0.7.3-1)
  • Migration status for labwc (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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/labwc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libbpp-popgen (2.4.1-10 to 2.4.1-11)
  • Migration status for libbpp-popgen (2.4.1-10 to 2.4.1-11): 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/libb/libbpp-popgen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libcdk5 (5.0.20240331-1 to 5.0.20240619-1)
  • Migration status for libcdk5 (5.0.20240331-1 to 5.0.20240619-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/libc/libcdk5.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libdjinterop (- to 0.21.0+ds-2)
  • Migration status for libdjinterop (- to 0.21.0+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): libdjinterop sqlite-modern-cpp
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdjinterop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libfli (2.0+20221221182632-1 to 2.0+20221221182632-2)
  • Migration status for libfli (2.0+20221221182632-1 to 2.0+20221221182632-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/libf/libfli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• 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
    • Too young, only 2 of 10 days old
  • 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libheif (1.17.6-3 to 1.17.6-4)
  • Migration status for libheif (1.17.6-3 to 1.17.6-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libheif.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libimobiledevice (1.3.0-7.1 to 1.3.0+git20240701-2)
  • Migration status for libimobiledevice (1.3.0-7.1 to 1.3.0+git20240701-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): libimobiledevice libimobiledevice-glue
    • Build-Depends(-Arch): libimobiledevice libplist
    • Build-Depends(-Arch): libimobiledevice libtatsu
    • Build-Depends(-Arch): libimobiledevice libusbmuxd
    • Depends: libimobiledevice libimobiledevice-glue
    • Depends: libimobiledevice libplist
    • Depends: libimobiledevice libtatsu
    • Depends: libimobiledevice libusbmuxd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libimobiledevice.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 ♻
• libimobiledevice-glue (- to 1.3.0-1)
  • Migration status for libimobiledevice-glue (- to 1.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): libimobiledevice-glue libplist
    • Depends: libimobiledevice-glue libplist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libi/libimobiledevice-glue.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libmicam (1.0+20221224111636-1 to 1.0+20221224111636-3)
  • Migration status for libmicam (1.0+20221224111636-1 to 1.0+20221224111636-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:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• libplist (2.2.0-7 to 2.6.0-1)
  • Migration status for libplist (2.2.0-7 to 2.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libplist.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libtatsu (- to 1.0.3-1)
  • Migration status for libtatsu (- 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
    • Build-Depends(-Arch): libtatsu libplist
    • Depends: libtatsu libplist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtatsu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• libusbmuxd (2.0.2-4 to 2.1.0-1)
  • Migration status for libusbmuxd (2.0.2-4 to 2.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): libusbmuxd libimobiledevice-glue
    • Build-Depends(-Arch): libusbmuxd libplist
    • Depends: libusbmuxd libimobiledevice-glue
    • Depends: libusbmuxd libplist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libu/libusbmuxd.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 ♻
• litecli (1.11.0-1 to 1.11.1-1)
  • Migration status for litecli (1.11.0-1 to 1.11.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/l/litecli.html
    • autopkgtest for litecli/1.11.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 ♻
• lyx (2.4.1-1 to 2.4.1-2)
  • Migration status for lyx (2.4.1-1 to 2.4.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lyx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• meep (1.25.0-2 to 1.25.0-3)
  • Migration status for meep (1.25.0-2 to 1.25.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for meep/1.25.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on mips64el
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating meep will fix bugs in testing: #1074728
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• meep-mpi-default (1.25.0-2 to 1.25.0-3)
  • Migration status for meep-mpi-default (1.25.0-2 to 1.25.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for meep-mpi-default/1.25.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on mips64el
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating meep-mpi-default will fix bugs in testing: #1074740
    • 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 ♻
• meep-openmpi (1.25.0-2 to 1.25.0-3)
  • Migration status for meep-openmpi (1.25.0-2 to 1.25.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for meep-openmpi/1.25.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating meep-openmpi will fix bugs in testing: #1074748
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meep-openmpi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• 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
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mes.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mintstick (1.6.1-2 to 1.6.2-1)
  • Migration status for mintstick (1.6.1-2 to 1.6.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mintstick.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mixxx (- to 2.4.0+dfsg-3)
  • Migration status for mixxx (- to 2.4.0+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): mixxx libdjinterop
    • Depends: mixxx libdjinterop
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mixxx.html
    • Reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
• mrbuild (1.10-2 to 1.11-1)
  • Migration status for mrbuild (1.10-2 to 1.11-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/mrbuild.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• 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
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/multispeech.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• mutter (44.8-3.1 to 46.3.1-2)
  • Migration status for mutter (44.8-3.1 to 46.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for budgie-desktop/10.8.2-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for mutter/46.3.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
    • Implicit dependency: mutter gnome-shell (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mutter.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• netperf (2.7.0-0.3 to 2.7.0+git20210121.3bc455b+ds-0.1)
  • Migration status for netperf (2.7.0-0.3 to 2.7.0+git20210121.3bc455b+ds-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/n/netperf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• nfdump (1.7.3-1 to 1.7.4-1)
  • Migration status for nfdump (1.7.3-1 to 1.7.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nfdump.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• nocache (- to 1.2-0.1)
  • Migration status for nocache (- to 1.2-0.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nocache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• nwg-look (- to 0.2.7-1)
  • Migration status for nwg-look (- to 0.2.7-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: nwg-look xcur2png (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nwg-look.html
    • autopkgtest for nwg-look/0.2.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• ocaml-conduit (6.2.2-1 to 6.2.3-1)
  • Migration status for ocaml-conduit (6.2.2-1 to 6.2.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/o/ocaml-conduit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ocaml-qcheck (0.21.3-1 to 0.22-1)
  • Migration status for ocaml-qcheck (0.21.3-1 to 0.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ocaml-qcheck/0.22-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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-qcheck.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ocamlformat (- to 0.26.2-1)
  • Migration status for ocamlformat (- to 0.26.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): ocamlformat ocaml-version
    • Depends: ocamlformat ocaml-dune
    • Depends: ocamlformat ocaml-version
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamlformat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• open-vm-tools (2:12.4.0-1 to 2:12.4.5-1)
  • Migration status for open-vm-tools (2:12.4.0-1 to 2:12.4.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open-vm-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• opm-common (2024.04+ds-1 to 2024.04+ds-2)
  • Migration status for opm-common (2024.04+ds-1 to 2024.04+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for opm-common/2024.04+ds-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for opm-models/2024.04+ds-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for opm-simulators/2024.04+ds-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for opm-upscaling/2024.04+ds-2: amd64: Pass, arm64: Pass, ppc64el: Pass, 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/o/opm-common.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• oxigraph (- to 0.4.0~alpha7-10)
  • Migration status for oxigraph (- to 0.4.0~alpha7-10): 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 oxigraph/0.4.0~alpha7-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): oxigraph dh-rust
    • Built-Using: oxigraph rust-json-event-parser
    • Built-Using: oxigraph rust-oxhttp
    • Built-Using: oxigraph rust-oxilangtag
    • Built-Using: oxigraph rust-oxiri
    • Built-Using: oxigraph rust-peg
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oxigraph.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• package-notes (0.14 to 0.15)
  • Migration status for package-notes (0.14 to 0.15): 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/package-notes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pipectl (0.4.2-1 to 0.5.0-1)
  • Migration status for pipectl (0.4.2-1 to 0.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pipectl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• porechop (0.2.4+dfsg-5 to 0.2.4+dfsg-6)
  • Migration status for porechop (0.2.4+dfsg-5 to 0.2.4+dfsg-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating porechop will fix bugs in testing: #1074677
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/porechop.html
    • autopkgtest for porechop/0.2.4+dfsg-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 ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• postfix-gld (1.7-9 to 1.7-10)
  • Migration status for postfix-gld (1.7-9 to 1.7-10): 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/postfix-gld.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pydantic-extra-types (2.8.2-1 to 2.9.0-1)
  • Migration status for pydantic-extra-types (2.8.2-1 to 2.9.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydantic-extra-types.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• pymupdf (1.23.7+ds1-1 to 1.24.2+ds1-3)
  • Migration status for pymupdf (1.23.7+ds1-1 to 1.24.2+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for plakativ/0.5.2-1: armel: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression)
    • autopkgtest for plakativ/0.5.2-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pymupdf/1.24.2+ds1-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 ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating pymupdf will fix bugs in testing: #1064772
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymupdf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• qtorganizer-eds (- to 0.2.0-2)
  • Migration status for qtorganizer-eds (- 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/q/qtorganizer-eds.html
    • Waiting for reproducibility test results on armhf - info ♻
• 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
    • Too young, only 2 of 5 days old
  • 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• radsecproxy (1.10.0-2 to 1.10.1-1)
  • Migration status for radsecproxy (1.10.0-2 to 1.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/radsecproxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ros2-osrf-testing-tools-cpp (2.1.0+ds-1 to 2.2.0+ds-1)
  • Migration status for ros2-osrf-testing-tools-cpp (2.1.0+ds-1 to 2.2.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros2-osrf-testing-tools-cpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ros2-performance-test-fixture (0.3.0-1 to 0.3.1-1)
  • Migration status for ros2-performance-test-fixture (0.3.0-1 to 0.3.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros2-performance-test-fixture.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• ros2-rcutils (6.8.0-1 to 6.9.0-1)
  • Migration status for ros2-rcutils (6.8.0-1 to 6.9.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros2-rcutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rpavlik-cmake-modules (- to 0.0~git20231201.03239c6-1)
  • Migration status for rpavlik-cmake-modules (- to 0.0~git20231201.03239c6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rpavlik-cmake-modules.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rsass (0.28.10-3 to 0.28.10-5)
  • Migration status for rsass (0.28.10-3 to 0.28.10-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rsass dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsass.html
    • autopkgtest for rsass/0.28.10-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
    • 2 days old (needed 2 days)
• rust-ahash (0.8.11-5 to 0.8.11-7)
  • Migration status for rust-ahash (0.8.11-5 to 0.8.11-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ahash/0.8.11-7: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), 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
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): rust-ahash dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ahash.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-cargo-c (0.9.19-2 to 0.9.29-1)
  • Migration status for rust-cargo-c (0.9.19-2 to 0.9.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-cargo-c/0.9.29-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): rust-cargo-c rust-cargo (not considered)
    • Built-Using: rust-cargo-c rust-ahash (not considered)
    • Built-Using: rust-cargo-c rust-signature
    • Depends: rust-cargo-c rust-cargo (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-c.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-crates-io (0.36.0-1 to 0.39.2-1)
  • Migration status for rust-crates-io (0.36.0-1 to 0.39.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-crates-io rust-cargo (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-crates-io.html
    • autopkgtest for rust-crates-io/0.39.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)
• rust-debcargo (2.6.1-5 to 2.6.1-6)
  • Migration status for rust-debcargo (2.6.1-5 to 2.6.1-6): 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 rust-debcargo/2.6.1-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): rust-debcargo rust-cargo (not considered)
    • Built-Using: rust-debcargo rust-ahash (not considered)
    • Built-Using: rust-debcargo rust-signature
    • Depends: rust-debcargo rust-cargo (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-debcargo.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-flume (0.11.0-1 to 0.11.0-3)
  • Migration status for rust-flume (0.11.0-1 to 0.11.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-flume dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-flume.html
    • autopkgtest for rust-flume/0.11.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
    • 2 days old (needed 2 days)
• rust-gix-dir (- to 0.4.1-2)
  • Migration status for rust-gix-dir (- to 0.4.1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for rust-gix-dir/0.4.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): rust-gix-dir rust-gix-discover
    • Depends: rust-gix-dir rust-gix-discover
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gix-dir.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-gix-status (- to 0.9.0-3)
  • Migration status for rust-gix-status (- to 0.9.0-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
    • autopkgtest for rust-gix-status/0.9.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
    • Depends: rust-gix-status rust-gix-dir (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gix-status.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-id-arena (2.2.1-2 to 2.2.1-4)
  • Migration status for rust-id-arena (2.2.1-2 to 2.2.1-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-id-arena dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-id-arena.html
    • autopkgtest for rust-id-arena/2.2.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 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-libbpf-rs (- to 0.23.3-1)
  • Migration status for rust-libbpf-rs (- to 0.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 2 of 5 days old
    • Build-Depends(-Arch): rust-libbpf-rs rust-libbpf-sys
    • Depends: rust-libbpf-rs rust-libbpf-sys
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libbpf-rs.html
    • autopkgtest for rust-libbpf-rs/0.23.3-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-libp2p-identity (- to 0.2.9+ds-5)
  • Migration status for rust-libp2p-identity (- to 0.2.9+ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-libp2p-identity/0.2.9+ds-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 ♻
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): rust-libp2p-identity dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-libp2p-identity.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-magic-wormhole (- to 0.6.1-1)
  • Migration status for rust-magic-wormhole (- to 0.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-magic-wormhole/0.6.1-1: amd64: Regression or new test ♻, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-magic-wormhole.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-multiaddr (- to 0.18.1-5)
  • Migration status for rust-multiaddr (- to 0.18.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-multiaddr rust-libp2p-identity (not considered)
    • Depends: rust-multiaddr rust-libp2p-identity (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-multiaddr dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-multiaddr.html
    • autopkgtest for rust-multiaddr/0.18.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-oxhttp (0.2.0-2 to 0.2.0-4)
  • Migration status for rust-oxhttp (0.2.0-2 to 0.2.0-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-oxhttp dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-oxhttp.html
    • autopkgtest for rust-oxhttp/0.2.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
    • 2 days old (needed 2 days)
• rust-prr (- to 0.18.0-1)
  • Migration status for rust-prr (- to 0.18.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): rust-prr rust-octocrab
    • Built-Using: rust-prr rust-hyper-rustls (not considered)
    • Built-Using: rust-prr rust-rustls (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-prr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-rusty-pool (0.7.0-6 to 0.7.0-8)
  • Migration status for rust-rusty-pool (0.7.0-6 to 0.7.0-8): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-rusty-pool dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rusty-pool.html
    • autopkgtest for rust-rusty-pool/0.7.0-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-safe-arch (0.7.2-1 to 0.7.2-2)
  • Migration status for rust-safe-arch (0.7.2-1 to 0.7.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-safe-arch dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-safe-arch.html
    • autopkgtest for rust-safe-arch/0.7.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-sequoia-keystore-gpg-agent (- to 0.3.0-1)
  • Migration status for rust-sequoia-keystore-gpg-agent (- to 0.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): rust-sequoia-keystore-gpg-agent rust-sequoia-keystore-backend (not considered)
    • Depends: rust-sequoia-keystore-gpg-agent rust-sequoia-keystore-backend (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-sequoia-keystore-gpg-agent rust-sequoia-gpg-agent (not considered)
    • Build-Depends(-Arch): rust-sequoia-keystore-gpg-agent rust-sequoia-ipc (not considered)
    • Depends: rust-sequoia-keystore-gpg-agent rust-sequoia-gpg-agent (not considered)
    • Depends: rust-sequoia-keystore-gpg-agent rust-sequoia-ipc (not considered)
  • 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.3.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 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-serde-fmt (1.0.3-2 to 1.0.3-3)
  • Migration status for rust-serde-fmt (1.0.3-2 to 1.0.3-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-serde-fmt dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-serde-fmt.html
    • autopkgtest for rust-serde-fmt/1.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 ♻
    • 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-signature (2.2.0+ds-2 to 2.2.0+ds-3)
  • Migration status for rust-signature (2.2.0+ds-2 to 2.2.0+ds-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-signature dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-signature.html
    • autopkgtest for rust-signature/2.2.0+ds-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 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-slice-group-by (0.3.1-3 to 0.3.1-4)
  • Migration status for rust-slice-group-by (0.3.1-3 to 0.3.1-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-slice-group-by dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-slice-group-by.html
    • autopkgtest for rust-slice-group-by/0.3.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 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-snow (0.9.6-1 to 0.9.6-5)
  • Migration status for rust-snow (0.9.6-1 to 0.9.6-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-snow dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Updating rust-snow will fix bugs in testing: #1073499
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-snow.html
    • autopkgtest for rust-snow/0.9.6-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)
• rust-socks (0.3.4-4 to 0.3.4-5)
  • Migration status for rust-socks (0.3.4-4 to 0.3.4-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
    • Build-Depends(-Arch): rust-socks dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-socks.html
    • autopkgtest for rust-socks/0.3.4-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: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-souper-ir (2.1.0-2 to 2.1.0-3)
  • Migration status for rust-souper-ir (2.1.0-2 to 2.1.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-souper-ir dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-souper-ir.html
    • autopkgtest for rust-souper-ir/2.1.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 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-strfmt (0.2.4-2 to 0.2.4-3)
  • Migration status for rust-strfmt (0.2.4-2 to 0.2.4-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-strfmt dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-strfmt.html
    • autopkgtest for rust-strfmt/0.2.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 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-subtile (0.1.8-4 to 0.1.9-1)
  • Migration status for rust-subtile (0.1.8-4 to 0.1.9-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-subtile dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-subtile.html
    • autopkgtest for rust-subtile/0.1.9-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-tesseract-plumbing (0.11.0-3 to 0.11.0-4)
  • Migration status for rust-tesseract-plumbing (0.11.0-3 to 0.11.0-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-tesseract-plumbing dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tesseract-plumbing.html
    • autopkgtest for rust-tesseract-plumbing/0.11.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-tesseract-sys (0.6.1-1 to 0.6.1-2)
  • Migration status for rust-tesseract-sys (0.6.1-1 to 0.6.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-tesseract-sys dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tesseract-sys.html
    • autopkgtest for rust-tesseract-sys/0.6.1-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-test-case (3.3.1-2 to 3.3.1-3)
  • Migration status for rust-test-case (3.3.1-2 to 3.3.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-test-case dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-test-case.html
    • autopkgtest for rust-test-case/3.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)
• rust-threadfin (0.1.2-2 to 0.1.2-3)
  • Migration status for rust-threadfin (0.1.2-2 to 0.1.2-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-threadfin dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-threadfin.html
    • autopkgtest for rust-threadfin/0.1.2-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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-tonic (- to 0.10.2+dfsg-9)
  • Migration status for rust-tonic (- to 0.10.2+dfsg-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-tonic rust-hyper-timeout (not considered)
    • Depends: rust-tonic rust-hyper-timeout (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-tonic dh-rust
    • Build-Depends(-Arch): rust-tonic rust-axum (not considered)
    • Build-Depends(-Arch): rust-tonic rust-prost
    • Build-Depends(-Arch): rust-tonic rust-prost-build
    • Depends: rust-tonic rust-axum (not considered)
    • Depends: rust-tonic rust-prost
    • Depends: rust-tonic rust-prost-build
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tonic.html
    • autopkgtest for rust-tonic/0.10.2+dfsg-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
    • 2 days old (needed 2 days)
• rust-ureq (2.10.0-2 to 2.10.0-3)
  • Migration status for rust-ureq (2.10.0-2 to 2.10.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-ureq dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ureq.html
    • autopkgtest for rust-ureq/2.10.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
    • 2 days old (needed 2 days)
• rust-wasmtime (19.0.0+dfsg-2 to 19.0.0+dfsg-3)
  • Migration status for rust-wasmtime (19.0.0+dfsg-2 to 19.0.0+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): rust-wasmtime dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-wasmtime.html
    • autopkgtest for rust-wasmtime/19.0.0+dfsg-3: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
• rust-wide (0.7.25-1 to 0.7.25-2)
  • Migration status for rust-wide (0.7.25-1 to 0.7.25-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-wide dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-wide.html
    • autopkgtest for rust-wide/0.7.25-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 ♻
    • Required age reduced by 3 days because of autopkgtest
    • 2 days old (needed 2 days)
• rust-xor-name (5.0.0-6 to 5.0.0-7)
  • Migration status for rust-xor-name (5.0.0-6 to 5.0.0-7): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-xor-name dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xor-name.html
    • autopkgtest for rust-xor-name/5.0.0-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)
• sasdata (0.8.1-3 to 0.8.1-4)
  • Migration status for sasdata (0.8.1-3 to 0.8.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sasdata/0.8.1-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating sasdata will fix bugs in testing: #1073418
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sasdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• sasview (5.0.6-2 to 5.0.6-3)
  • Migration status for sasview (5.0.6-2 to 5.0.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sasview/5.0.6-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating sasview will fix bugs in testing: #1073429
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sasview.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 ♻
• sccache (0.8.1-4 to 0.8.1-6)
  • Migration status for sccache (0.8.1-4 to 0.8.1-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): sccache dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sccache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• setuptools (68.1.2-4 to 70.3.0-2)
  • Migration status for setuptools (68.1.2-4 to 70.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pandas/2.1.4+dfsg-8: riscv64: Failed (not a regression), s390x: Pass
    • autopkgtest for python-pyproject-hooks/1.1.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python3.13/3.13.0~b2-1: riscv64: Failed (not a regression), s390x: Pass
    • autopkgtest for q2-alignment/2024.5.0-1: amd64: Failed (not a regression), arm64: Failed (not a regression), 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: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for q2cli/2024.5.0-2: amd64: Failed (not a regression), arm64: Failed (not a regression), 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: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for scikit-build/0.17.6-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for sip6/6.8.3+dfsg-1: 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/s/setuptools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sosreport (4.0-2.1 to 4.7.2-0.1)
  • Migration status for sosreport (4.0-2.1 to 4.7.2-0.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating sosreport will fix bugs in testing: #1074339, #1075909
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sosreport.html
    • autopkgtest for sosreport/4.7.2-0.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• sqlglot (25.1.0-1 to 25.5.1-1)
  • Migration status for sqlglot (25.1.0-1 to 25.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 2 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 ♻
• sqlite-modern-cpp (- to 3.2+git20231203-2)
  • Migration status for sqlite-modern-cpp (- to 3.2+git20231203-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/sqlite-modern-cpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• stenographer (1.0.1-4 to 1.0.1-6)
  • Migration status for stenographer (1.0.1-4 to 1.0.1-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stenographer.html
    • autopkgtest for stenographer/1.0.1-6: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• storm-lang (0.6.22-1 to 0.6.23-1)
  • Migration status for storm-lang (0.6.22-1 to 0.6.23-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/storm-lang.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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
• suitesparse (1:7.7.0+dfsg-2 to 1:7.7.0+dfsg-5)
  • Migration status for suitesparse (1:7.7.0+dfsg-2 to 1:7.7.0+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for opm-simulators/2024.04+ds-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for opm-upscaling/2024.04+ds-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for suitesparse/1:7.7.0+dfsg-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 ♻
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/suitesparse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• svxlink (24.02-2 to 24.02-3)
  • Migration status for svxlink (24.02-2 to 24.02-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
    • Depends: svxlink libgcrypt20
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/svxlink.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• texlive-extra (2024.20240401-2 to 2024.20240706-2)
  • Migration status for texlive-extra (2024.20240401-2 to 2024.20240706-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/t/texlive-extra.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• typedload (2.33-1 to 2.34-1)
  • Migration status for typedload (2.33-1 to 2.34-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/t/typedload.html
    • autopkgtest for typedload/2.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
• usbmuxd (1.1.1-3 to 1.1.1-5)
  • Migration status for usbmuxd (1.1.1-3 to 1.1.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
    • Build-Depends(-Arch): usbmuxd libimobiledevice
    • Build-Depends(-Arch): usbmuxd libplist
    • Depends: usbmuxd libimobiledevice
    • Depends: usbmuxd libplist
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/usbmuxd.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 ♻
• vim-link-vim (- to 1.0.3+git20240521-2)
  • Migration status for vim-link-vim (- to 1.0.3+git20240521-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/v/vim-link-vim.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• x13as (1.1-b60-1 to 1.1-b61-1)
  • Migration status for x13as (1.1-b60-1 to 1.1-b61-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• xcur2png (- to 0.7.1-1)
  • Migration status for xcur2png (- to 0.7.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcur2png.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• xdg-desktop-portal-gnome (44.2-4 to 46.2-3)
  • Migration status for xdg-desktop-portal-gnome (44.2-4 to 46.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdg-desktop-portal-gnome.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• yiyantang (0.7.0-9 to 0.7.0-10)
  • Migration status for yiyantang (0.7.0-9 to 0.7.0-10): 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/yiyantang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• zd1211-firmware (1:1.5-10 to 1:1.5-11)
  • Migration status for zd1211-firmware (1:1.5-10 to 1:1.5-11): 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)
• bibcursed (- to 2.0.1-0.1)
  • Migration status for bibcursed (- to 2.0.1-0.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bibcursed.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• bootcd (6.8 to 6.8.1)
  • Migration status for bootcd (6.8 to 6.8.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating bootcd will fix bugs in testing: #1074720
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bootcd.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• btm (0.9.6-7 to 0.9.6-8)
  • Migration status for btm (0.9.6-7 to 0.9.6-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 3 of 5 days old
    • Build-Depends(-Arch): btm dh-rust
    • Build-Depends(-Arch): btm rust-sysinfo (not considered)
    • Built-Using: btm rust-ahash (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
• camlzip (1.11-3 to 1.12-1)
  • Migration status for camlzip (1.11-3 to 1.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libzip-ocaml-dev/1.12-1/amd64 to testing makes libwhy3-ocaml-dev/1.6.0-1+b5/amd64 uninstallable
    • migrating libzip-ocaml-dev/1.12-1/arm64 to testing makes libwhy3-ocaml-dev/1.6.0-1+b5/arm64 uninstallable
    • migrating libzip-ocaml/1.12-1/armel to testing makes botch/0.24-4+b1/armel uninstallable
    • migrating libzip-ocaml/1.12-1/armel to testing makes why3/1.6.0-1+b5/armel uninstallable
    • migrating libzip-ocaml-dev/1.12-1/armel to testing makes libwhy3-ocaml-dev/1.6.0-1+b5/armel uninstallable
    • migrating libzip-ocaml-dev/1.12-1/armhf to testing makes libwhy3-ocaml-dev/1.6.0-1+b5/armhf uninstallable
    • migrating libzip-ocaml-dev/1.12-1/i386 to testing makes libwhy3-ocaml-dev/1.6.0-1+b5/i386 uninstallable
    • migrating libzip-ocaml/1.12-1/mips64el to testing makes botch/0.24-4+b1/mips64el uninstallable
    • migrating libzip-ocaml/1.12-1/mips64el to testing makes why3/1.6.0-1+b5/mips64el uninstallable
    • migrating libzip-ocaml-dev/1.12-1/mips64el to testing makes libwhy3-ocaml-dev/1.6.0-1+b5/mips64el uninstallable
    • migrating libzip-ocaml-dev/1.12-1/ppc64el to testing makes libwhy3-ocaml-dev/1.6.0-1+b5/ppc64el uninstallable
    • migrating libzip-ocaml-dev/1.12-1/s390x to testing makes libwhy3-ocaml-dev/1.6.0-1+b5/s390x uninstallable
    • Implicit dependency: camlzip dose3/amd64
    • Implicit dependency: camlzip dose3/arm64
    • Implicit dependency: camlzip dose3/armel
    • Implicit dependency: camlzip dose3/armhf
    • Implicit dependency: camlzip dose3/i386
    • Implicit dependency: camlzip dose3/mips64el
    • Implicit dependency: camlzip dose3/ppc64el
    • Implicit dependency: camlzip dose3/s390x
    • Implicit dependency: camlzip ocamlnet/amd64
    • Implicit dependency: camlzip ocamlnet/arm64
    • Implicit dependency: camlzip ocamlnet/armel
    • Implicit dependency: camlzip ocamlnet/armhf
    • Implicit dependency: camlzip ocamlnet/i386
    • Implicit dependency: camlzip ocamlnet/mips64el
    • Implicit dependency: camlzip ocamlnet/ppc64el
    • Implicit dependency: camlzip ocamlnet/s390x
    • Implicit dependency: camlzip ocsigenserver/amd64
    • Implicit dependency: camlzip ocsigenserver/arm64
    • Implicit dependency: camlzip ocsigenserver/armel
    • Implicit dependency: camlzip ocsigenserver/armhf
    • Implicit dependency: camlzip ocsigenserver/i386
    • Implicit dependency: camlzip ocsigenserver/mips64el
    • Implicit dependency: camlzip ocsigenserver/ppc64el
    • Implicit dependency: camlzip ocsigenserver/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camlzip.html
    • autopkgtest for camlzip/1.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
    • 3 days old (needed 2 days)
• cenon.app (4.0.6+ds1-2 to 4.0.6+ds1-4)
  • Migration status for cenon.app (4.0.6+ds1-2 to 4.0.6+ds1-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/c/cenon.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• console-setup (1.229 to 1.230)
  • Migration status for console-setup (1.229 to 1.230): Waiting for test 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/console-setup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• debugpy (1.8.0+ds-4 to 1.8.2+ds-5)
  • Migration status for debugpy (1.8.0+ds-4 to 1.8.2+ds-5): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating debugpy will fix bugs in testing: #1075603
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debugpy.html
    • autopkgtest for debugpy/1.8.2+ds-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
    • 3 days old (needed 2 days)
• dh-rust (- to 0.0.5)
  • Migration status for dh-rust (- to 0.0.5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• docker-compose (1.29.2-6 to 1.29.2-6.1)
  • Migration status for docker-compose (1.29.2-6 to 1.29.2-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating docker-compose would introduce bugs in testing: #1076201
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating docker-compose will fix bugs in testing: #1065848
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/docker-compose.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• dxvk (- to 2.4-1)
  • Migration status for dxvk (- to 2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dxvk/arm64 has unsatisfiable dependency
    • Updating dxvk would introduce bugs in testing: #1073188, #982159
    • autopkgtest for dxvk/2.4-1: amd64: Regression or new test ♻, i386: Regression or new test ♻
    • Too young, only 3 of 5 days old
    • 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 arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• elinks (0.16.1.1-4.1 to 0.17.0-1)
  • Migration status for elinks (0.16.1.1-4.1 to 0.17.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: elinks libgcrypt20 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elinks.html
    • autopkgtest for elinks/0.17.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
    • 3 days old (needed 2 days)
• emacs-git-modes (1.4.2-1 to 1.4.3-1)
  • Migration status for emacs-git-modes (1.4.2-1 to 1.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-git-modes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• filezilla (3.67.1~rc1-1 to 3.67.1-1)
  • Migration status for filezilla (3.67.1~rc1-1 to 3.67.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): filezilla libfilezilla
    • Depends: filezilla libfilezilla
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/filezilla.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• g-golf (0.8.0~rc3-1 to 0.8.0~rc4-1)
  • Migration status for g-golf (0.8.0~rc3-1 to 0.8.0~rc4-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/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 ♻
• galvani (0.35-2 to 0.36-1)
  • Migration status for galvani (0.35-2 to 0.36-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/galvani.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• gcc-12 (12.4.0-1 to 12.4.0-2)
  • Migration status for gcc-12 (12.4.0-1 to 12.4.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 gcc-12/12.4.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-12.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility reference results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• golang-1.23 (- to 1.23~rc1-1)
  • Migration status for golang-1.23 (- to 1.23~rc1-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
    • Not built on buildd: arch amd64 binaries uploaded by i@zhsj.me
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-1.23.html
    • autopkgtest for golang-1.23/1.23~rc1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• heat (1:22.0.0-2 to 1:22.0.0-3)
  • Migration status for heat (1:22.0.0-2 to 1:22.0.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating heat will fix bugs in testing: #1074656
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/heat.html
    • autopkgtest for heat/1:22.0.0-3: 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: Pass, s390x: Pass
    • Reproducibility regression on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• helvum (0.5.1+20240328-2 to 0.5.1+20240328-3)
  • Migration status for helvum (0.5.1+20240328-2 to 0.5.1+20240328-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
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): helvum dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/helvum.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• hl-todo-el (3.6.0-1 to 3.8.0-1)
  • Migration status for hl-todo-el (3.6.0-1 to 3.8.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hl-todo-el.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• hyprlang (0.5.1-1 to 0.5.2-1)
  • Migration status for hyprlang (0.5.1-1 to 0.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/h/hyprlang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• icedtea-web (1.8.8-2 to 1.8.8-3)
  • Migration status for icedtea-web (1.8.8-2 to 1.8.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/i/icedtea-web.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• icingaweb2-module-idoreports (0.10.1-3 to 0.10.1-4)
  • Migration status for icingaweb2-module-idoreports (0.10.1-3 to 0.10.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-idoreports.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• icingaweb2-module-map (1.1.0-4 to 2.0.0-1)
  • Migration status for icingaweb2-module-map (1.1.0-4 to 2.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-map.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• icingaweb2-module-pdfexport (0.10.2+dfsg1-4 to 0.11.0+dfsg-1)
  • Migration status for icingaweb2-module-pdfexport (0.10.2+dfsg1-4 to 0.11.0+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/icingaweb2-module-pdfexport.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• intellij-community-idea (183.5153.4-4 to 183.5153.4-5)
  • Migration status for intellij-community-idea (183.5153.4-4 to 183.5153.4-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/i/intellij-community-idea.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• jack-mixer (- to 18+git20240504-1)
  • Migration status for jack-mixer (- to 18+git20240504-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jack-mixer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• jboss-logging-tools (2.2.1-3 to 2.2.1-4)
  • Migration status for jboss-logging-tools (2.2.1-3 to 2.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jboss-logging-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Reproducible on i386 - info ♻
• labltk (8.06.13-2 to 8.06.14-1)
  • Migration status for labltk (8.06.13-2 to 8.06.14-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/labltk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libfilezilla (0.48.0-2 to 0.48.1-2)
  • Migration status for libfilezilla (0.48.0-2 to 0.48.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/libf/libfilezilla.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libgd2 (2.3.3-9 to 2.3.3-12)
  • Migration status for libgd2 (2.3.3-9 to 2.3.3-12): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgd2.html
    • autopkgtest for libgd2/2.3.3-12: 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libguestfs (1:1.52.0-6.1 to 1:1.52.2-1)
  • Migration status for libguestfs (1:1.52.0-6.1 to 1:1.52.2-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
    • autopkgtest for libguestfs/1:1.52.2-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libguestfs.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 ♻
• libmail-dmarc-perl (1.20230215-1 to 1.20240314-1)
  • Migration status for libmail-dmarc-perl (1.20230215-1 to 1.20240314-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmail-dmarc-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libphp-adodb (5.21.4-1 to 5.22.7-0.1)
  • Migration status for libphp-adodb (5.21.4-1 to 5.22.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/libp/libphp-adodb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libreoffice (4:24.2.4-1 to 4:24.2.5-1)
  • Migration status for libreoffice (4:24.2.4-1 to 4:24.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/libr/libreoffice.html
    • autopkgtest for libreoffice/4:24.2.5-1: amd64: Pass, 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)
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• lomiri-session (0.2-12 to 0.3-1)
  • Migration status for lomiri-session (0.2-12 to 0.3-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-session.html
• magics++ (4.15.4-1 to 4.15.4-2)
  • Migration status for magics++ (4.15.4-1 to 4.15.4-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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magics++.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 ♻
• metview (5.22.0-1 to 5.22.0-2)
  • Migration status for metview (5.22.0-1 to 5.22.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating metview will fix bugs in testing: #1073325
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/metview.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• no-littering-el (1.5.0-1 to 1.7.0-1)
  • Migration status for no-littering-el (1.5.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/n/no-littering-el.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• nordugrid-arc-nagios-plugins (2.0.1-1 to 2.0.1-2)
  • Migration status for nordugrid-arc-nagios-plugins (2.0.1-1 to 2.0.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating nordugrid-arc-nagios-plugins will fix bugs in testing: #1074697
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nordugrid-arc-nagios-plugins.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ocaml-dune (3.15.3-2 to 3.16.0-1)
  • Migration status for ocaml-dune (3.15.3-2 to 3.16.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Implicit dependency: ocaml-dune camomile/amd64
    • Implicit dependency: ocaml-dune camomile/arm64
    • Implicit dependency: ocaml-dune camomile/armel
    • Implicit dependency: ocaml-dune camomile/armhf
    • Implicit dependency: ocaml-dune camomile/i386
    • Implicit dependency: ocaml-dune camomile/mips64el
    • Implicit dependency: ocaml-dune camomile/ppc64el
    • Implicit dependency: ocaml-dune camomile/s390x
    • Implicit dependency: ocaml-dune utop/amd64
    • Implicit dependency: ocaml-dune utop/arm64
    • Implicit dependency: ocaml-dune utop/armel
    • Implicit dependency: ocaml-dune utop/armhf
    • Implicit dependency: ocaml-dune utop/i386
    • Implicit dependency: ocaml-dune utop/mips64el
    • Implicit dependency: ocaml-dune utop/ppc64el
    • Implicit dependency: ocaml-dune utop/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-dune.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• ocaml-version (- to 3.6.7-1)
  • Migration status for ocaml-version (- to 3.6.7-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-version.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ocamlbuild (0.14.3-2 to 0.15.0-1)
  • Migration status for ocamlbuild (0.14.3-2 to 0.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for js-of-ocaml-ocamlbuild/5.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • Too young, only 3 of 5 days old
    • Implicit dependency: ocamlbuild eliom/amd64
    • Implicit dependency: ocamlbuild eliom/arm64
    • Implicit dependency: ocamlbuild eliom/armel
    • Implicit dependency: ocamlbuild eliom/armhf
    • Implicit dependency: ocamlbuild eliom/i386
    • Implicit dependency: ocamlbuild eliom/mips64el
    • Implicit dependency: ocamlbuild eliom/ppc64el
    • Implicit dependency: ocamlbuild eliom/s390x
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/amd64
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/arm64
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/armel
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/armhf
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/i386
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/mips64el
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/ppc64el
    • Implicit dependency: ocamlbuild js-of-ocaml-ocamlbuild/s390x
    • Implicit dependency: ocamlbuild oasis/amd64
    • Implicit dependency: ocamlbuild oasis/arm64
    • Implicit dependency: ocamlbuild oasis/armel
    • Implicit dependency: ocamlbuild oasis/armhf
    • Implicit dependency: ocamlbuild oasis/i386
    • Implicit dependency: ocamlbuild oasis/mips64el
    • Implicit dependency: ocamlbuild oasis/ppc64el
    • Implicit dependency: ocamlbuild oasis/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamlbuild.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• onetbb (2021.11.0-2 to 2021.12.0-1)
  • Migration status for onetbb (2021.11.0-2 to 2021.12.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Implicit dependency: onetbb r-cran-rcppparallel/amd64
    • Implicit dependency: onetbb r-cran-rcppparallel/arm64
    • Implicit dependency: onetbb r-cran-rcppparallel/armel
    • Implicit dependency: onetbb r-cran-rcppparallel/armhf
    • Implicit dependency: onetbb r-cran-rcppparallel/i386
    • Implicit dependency: onetbb r-cran-rcppparallel/mips64el
    • Implicit dependency: onetbb r-cran-rcppparallel/ppc64el
    • Implicit dependency: onetbb r-cran-rcppparallel/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onetbb.html
    • autopkgtest for onetbb/2021.12.0-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Reproducible on i386 - info ♻
• pompem (0.2.0-6 to 0.2.0-7)
  • Migration status for pompem (0.2.0-6 to 0.2.0-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating pompem will fix bugs in testing: #1074500
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pompem.html
    • autopkgtest for pompem/0.2.0-7: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
• powerline (2.8.3-5 to 2.8.3-6)
  • Migration status for powerline (2.8.3-5 to 2.8.3-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/p/powerline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-asyncio-mqtt (- to 2.2.0-1)
  • Migration status for python-asyncio-mqtt (- 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 debacle, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-asyncio-mqtt.html
    • autopkgtest for python-asyncio-mqtt/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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• python-colored-traceback (0.3.0-4 to 0.4.1-1)
  • Migration status for python-colored-traceback (0.3.0-4 to 0.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-colored-traceback.html
    • autopkgtest for python-colored-traceback/0.4.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-gevent (24.2.1-0.1 to 24.2.1-1)
  • Migration status for python-gevent (24.2.1-0.1 to 24.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/p/python-gevent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-recipe-scrapers (14.57.0-2 to 14.57.1-1)
  • Migration status for python-recipe-scrapers (14.57.0-2 to 14.57.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/p/python-recipe-scrapers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• qt6-declarative (6.6.2+dfsg-3 to 6.6.2+dfsg-4)
  • Migration status for qt6-declarative (6.6.2+dfsg-3 to 6.6.2+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qt6-declarative.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Reproducibility regression on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• r-cran-dimred (- to 0.2.6-2)
  • Migration status for r-cran-dimred (- to 0.2.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-dimred/0.2.6-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • r-cran-dimred unsatisfiable Build-Depends(-Arch) on armel: architecture-is-64-bit
    • r-cran-dimred unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • r-cran-dimred 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
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-dimred.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 ♻
• ruby-redis-client (0.19.1-2 to 0.22.2-1.1)
  • Migration status for ruby-redis-client (0.19.1-2 to 0.22.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:
    • Updating ruby-redis-client will fix bugs in testing: #1074362
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-redis-client.html
    • autopkgtest for ruby-redis-client/0.22.2-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 ♻
• rust-abnf-core (0.6.0-2 to 0.6.0-3)
  • Migration status for rust-abnf-core (0.6.0-2 to 0.6.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-abnf-core dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-abnf-core.html
    • autopkgtest for rust-abnf-core/0.6.0-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
    • 3 days old (needed 2 days)
• rust-assert-json-diff (2.0.2-5 to 2.0.2-6)
  • Migration status for rust-assert-json-diff (2.0.2-5 to 2.0.2-6): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-assert-json-diff dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-assert-json-diff.html
    • autopkgtest for rust-assert-json-diff/2.0.2-6: 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
    • 3 days old (needed 2 days)
• rust-async-attributes (1.1.2-5 to 1.1.2-6)
  • Migration status for rust-async-attributes (1.1.2-5 to 1.1.2-6): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-async-attributes dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-attributes.html
    • autopkgtest for rust-async-attributes/1.1.2-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-async-executor (1.12.0-2 to 1.12.0-3)
  • Migration status for rust-async-executor (1.12.0-2 to 1.12.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-async-executor dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-executor.html
    • autopkgtest for rust-async-executor/1.12.0-3: 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
    • 3 days old (needed 2 days)
• rust-async-fs (2.1.2-2 to 2.1.2-3)
  • Migration status for rust-async-fs (2.1.2-2 to 2.1.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-async-fs/2.1.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-oo7/0.2.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 ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test in progress
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): rust-async-fs dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-fs.html
    • Reproducible on armhf - info ♻
• rust-async-net (2.0.0-2 to 2.0.0-3)
  • Migration status for rust-async-net (2.0.0-2 to 2.0.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-async-net dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-net.html
    • autopkgtest for rust-async-net/2.0.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 ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-async-std (1.12.0-20 to 1.12.0-21)
  • Migration status for rust-async-std (1.12.0-20 to 1.12.0-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-async-std/1.12.0-21: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-async-tungstenite/0.23.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): rust-async-std dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-std.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-async-task (4.7.1-1 to 4.7.1-2)
  • Migration status for rust-async-task (4.7.1-1 to 4.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
    • Build-Depends(-Arch): rust-async-task dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-async-task.html
    • autopkgtest for rust-async-task/4.7.1-2: 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-blocking (1.6.1-2 to 1.6.1-3)
  • Migration status for rust-blocking (1.6.1-2 to 1.6.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-blocking dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-blocking.html
    • autopkgtest for rust-blocking/1.6.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 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-bounded-static (0.8.0-2 to 0.8.0-3)
  • Migration status for rust-bounded-static (0.8.0-2 to 0.8.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-bounded-static dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bounded-static.html
    • autopkgtest for rust-bounded-static/0.8.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 ♻
    • 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-crdts (7.3.2+dfsg-3 to 7.3.2+dfsg-4)
  • Migration status for rust-crdts (7.3.2+dfsg-3 to 7.3.2+dfsg-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-crdts dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-crdts.html
    • autopkgtest for rust-crdts/7.3.2+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
    • 3 days old (needed 2 days)
• rust-criterion (0.5.1-4 to 0.5.1-5)
  • Migration status for rust-criterion (0.5.1-4 to 0.5.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-criterion dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-criterion.html
    • autopkgtest for rust-criterion/0.5.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
    • 3 days old (needed 2 days)
• rust-curve25519-dalek (4.1.3+20240618+dfsg-1 to 4.1.3+20240618+dfsg-3)
  • Migration status for rust-curve25519-dalek (4.1.3+20240618+dfsg-1 to 4.1.3+20240618+dfsg-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): rust-curve25519-dalek dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-curve25519-dalek.html
    • autopkgtest for rust-curve25519-dalek/4.1.3+20240618+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-easy-parallel (3.3.1-1 to 3.3.1-2)
  • Migration status for rust-easy-parallel (3.3.1-1 to 3.3.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-easy-parallel dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-easy-parallel.html
    • autopkgtest for rust-easy-parallel/3.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
    • 3 days old (needed 2 days)
• rust-ed25519 (2.2.3+ds-3 to 2.2.3+ds-4)
  • Migration status for rust-ed25519 (2.2.3+ds-3 to 2.2.3+ds-4): 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 3 of 5 days old
    • Build-Depends(-Arch): rust-ed25519 dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ed25519.html
    • Waiting for reproducibility test results on armhf - info ♻
• rust-fast-srgb8 (1.0.0-5 to 1.0.0-6)
  • Migration status for rust-fast-srgb8 (1.0.0-5 to 1.0.0-6): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-fast-srgb8 dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-fast-srgb8.html
    • autopkgtest for rust-fast-srgb8/1.0.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
    • 3 days old (needed 2 days)
• rust-femme (2.2.1~dfsg-5 to 2.2.1~dfsg-6)
  • Migration status for rust-femme (2.2.1~dfsg-5 to 2.2.1~dfsg-6): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-femme dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-femme.html
    • autopkgtest for rust-femme/2.2.1~dfsg-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
    • 3 days old (needed 2 days)
• rust-futures-timer (3.0.3-1 to 3.0.3-2)
  • Migration status for rust-futures-timer (3.0.3-1 to 3.0.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-futures-timer dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-futures-timer.html
    • autopkgtest for rust-futures-timer/3.0.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-hyper-rustls (0.24.2-2 to 0.24.2-3)
  • Migration status for rust-hyper-rustls (0.24.2-2 to 0.24.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-hyper-rustls/0.24.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-reqwest/0.11.27-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): rust-hyper-rustls dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hyper-rustls.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-hypothesis (- to 0.11.5-3)
  • Migration status for rust-hypothesis (- to 0.11.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-hypothesis would introduce bugs in testing: #1076306
    • autopkgtest for rust-hypothesis/0.11.5-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on mips64el
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): rust-hypothesis dh-rust
    • Built-Using: rust-hypothesis rust-rustls (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hypothesis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-if-watch (3.2.0-8 to 3.2.0-9)
  • Migration status for rust-if-watch (3.2.0-8 to 3.2.0-9): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-if-watch dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-if-watch.html
    • autopkgtest for rust-if-watch/3.2.0-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-imap-codec (1.0.0-5 to 1.0.0-6)
  • Migration status for rust-imap-codec (1.0.0-5 to 1.0.0-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): rust-imap-codec dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-imap-codec.html
    • autopkgtest for rust-imap-codec/1.0.0-6: 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-json-event-parser (0.2.0-3 to 0.2.0-4)
  • Migration status for rust-json-event-parser (0.2.0-3 to 0.2.0-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-json-event-parser dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-json-event-parser.html
    • autopkgtest for rust-json-event-parser/0.2.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
    • 3 days old (needed 2 days)
• rust-kv-log-macro (1.0.8-3 to 1.0.8-4)
  • Migration status for rust-kv-log-macro (1.0.8-3 to 1.0.8-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-kv-log-macro dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-kv-log-macro.html
    • autopkgtest for rust-kv-log-macro/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
    • 3 days old (needed 2 days)
• rust-leptess (- to 0.14.0-3)
  • Migration status for rust-leptess (- to 0.14.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-leptess/0.14.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 ♻
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): rust-leptess dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-leptess.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-leptonica-plumbing (1.4.0-1 to 1.4.0-2)
  • Migration status for rust-leptonica-plumbing (1.4.0-1 to 1.4.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-leptonica-plumbing dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-leptonica-plumbing.html
    • autopkgtest for rust-leptonica-plumbing/1.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-leptonica-sys (0.4.8-1 to 0.4.8-2)
  • Migration status for rust-leptonica-sys (0.4.8-1 to 0.4.8-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-leptonica-sys dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-leptonica-sys.html
    • autopkgtest for rust-leptonica-sys/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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-linemux (0.3.0-6 to 0.3.0-7)
  • Migration status for rust-linemux (0.3.0-6 to 0.3.0-7): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-linemux dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-linemux.html
    • autopkgtest for rust-linemux/0.3.0-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
    • 3 days old (needed 2 days)
• rust-nanorand (0.7.0-9 to 0.7.0-10)
  • Migration status for rust-nanorand (0.7.0-9 to 0.7.0-10): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-nanorand dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-nanorand.html
    • autopkgtest for rust-nanorand/0.7.0-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
    • 3 days old (needed 2 days)
• rust-nom-locate (4.2.0-1 to 4.2.0-2)
  • Migration status for rust-nom-locate (4.2.0-1 to 4.2.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-nom-locate dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-nom-locate.html
    • autopkgtest for rust-nom-locate/4.2.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-oxilangtag (0.1.5-1 to 0.1.5-2)
  • Migration status for rust-oxilangtag (0.1.5-1 to 0.1.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-oxilangtag dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-oxilangtag.html
    • autopkgtest for rust-oxilangtag/0.1.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
    • 3 days old (needed 2 days)
• rust-oxiri (0.2.3-1 to 0.2.3-2)
  • Migration status for rust-oxiri (0.2.3-1 to 0.2.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-oxiri dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-oxiri.html
    • autopkgtest for rust-oxiri/0.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
    • 3 days old (needed 2 days)
• rust-pandoc-ast (0.8.6-4 to 0.8.6-5)
  • Migration status for rust-pandoc-ast (0.8.6-4 to 0.8.6-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-pandoc-ast dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pandoc-ast.html
    • autopkgtest for rust-pandoc-ast/0.8.6-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
    • 3 days old (needed 2 days)
• rust-parsec-interface (0.29.1-1 to 0.29.1-2)
  • Migration status for rust-parsec-interface (0.29.1-1 to 0.29.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-parsec-interface rust-prost (not considered)
    • Depends: rust-parsec-interface rust-prost (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: rust-parsec-interface rust-prost-build
  • Additional info:
    • Updating rust-parsec-interface will fix bugs in testing: #1075860
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-parsec-interface.html
    • autopkgtest for rust-parsec-interface/0.29.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
    • 3 days old (needed 2 days)
• rust-parsec-service (1.3.0-5 to 1.3.0-6)
  • Migration status for rust-parsec-service (1.3.0-5 to 1.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-parsec-service rust-ahash (not considered)
    • Invalidated by built-using
    • Depends: rust-parsec-service rust-prost
    • Depends: rust-parsec-service rust-prost-build
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-parsec-service.html
    • autopkgtest for rust-parsec-service/1.3.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
    • 3 days old (needed 2 days)
• rust-peg (0.8.3-1 to 0.8.3-2)
  • Migration status for rust-peg (0.8.3-1 to 0.8.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-peg dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-peg.html
    • autopkgtest for rust-peg/0.8.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
    • 3 days old (needed 2 days)
• rust-pikchr (0.1.3-4 to 0.1.3-5)
  • Migration status for rust-pikchr (0.1.3-4 to 0.1.3-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-pikchr dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pikchr.html
    • autopkgtest for rust-pikchr/0.1.3-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-pkcs8 (0.10.2+ds-8 to 0.10.2+ds-9)
  • Migration status for rust-pkcs8 (0.10.2+ds-8 to 0.10.2+ds-9): 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 3 of 5 days old
    • Build-Depends(-Arch): rust-pkcs8 dh-rust
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pkcs8.html
    • Waiting for reproducibility test results on armhf - info ♻
• rust-regalloc2 (0.9.3-2 to 0.9.3-3)
  • Migration status for rust-regalloc2 (0.9.3-2 to 0.9.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-regalloc2 rust-ahash (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): rust-regalloc2 dh-rust
    • Built-Using: rust-regalloc2 rust-slice-group-by
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-regalloc2.html
    • autopkgtest for rust-regalloc2/0.9.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-reqwest (0.11.27-1 to 0.11.27-3)
  • Migration status for rust-reqwest (0.11.27-1 to 0.11.27-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-reqwest/0.11.27-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-reqwest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-resource-proof (1.0.39-7 to 1.0.39-8)
  • Migration status for rust-resource-proof (1.0.39-7 to 1.0.39-8): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-resource-proof dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-resource-proof.html
    • autopkgtest for rust-resource-proof/1.0.39-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
    • 3 days old (needed 2 days)
• rust-retry (2.0.0-4 to 2.0.0-5)
  • Migration status for rust-retry (2.0.0-4 to 2.0.0-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-retry dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-retry.html
    • autopkgtest for rust-retry/2.0.0-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-rio (0.8.4-2 to 0.8.4-3)
  • Migration status for rust-rio (0.8.4-2 to 0.8.4-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-rio dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rio.html
    • autopkgtest for rust-rio/0.8.4-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• rust-roadmap (0.6.0-3 to 0.6.0-4)
  • Migration status for rust-roadmap (0.6.0-3 to 0.6.0-4): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-roadmap dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-roadmap.html
    • autopkgtest for rust-roadmap/0.6.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
    • 3 days old (needed 2 days)
• rust-rustls-pki-types (1.7.0-1 to 1.7.0-2)
  • Migration status for rust-rustls-pki-types (1.7.0-1 to 1.7.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-rustls-pki-types dh-rust (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustls-pki-types.html
    • autopkgtest for rust-rustls-pki-types/1.7.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
    • 3 days old (needed 2 days)
• rust-scriptisto (- to 2.2.0-1)
  • Migration status for rust-scriptisto (- 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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-scriptisto.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• rust-sequoia-keystore-softkeys (0.2.0-1 to 0.5.0-1)
  • Migration status for rust-sequoia-keystore-softkeys (0.2.0-1 to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-sequoia-keystore-softkeys-dev/0.5.0-1/amd64 to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/amd64 uninstallable
    • migrating librust-sequoia-keystore-softkeys-dev/0.5.0-1/arm64 to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/arm64 uninstallable
    • migrating librust-sequoia-keystore-softkeys-dev/0.5.0-1/armel to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/armel uninstallable
    • migrating librust-sequoia-keystore-softkeys-dev/0.5.0-1/armhf to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/armhf uninstallable
    • migrating librust-sequoia-keystore-softkeys-dev/0.5.0-1/i386 to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/i386 uninstallable
    • migrating librust-sequoia-keystore-softkeys-dev/0.5.0-1/mips64el to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/mips64el uninstallable
    • migrating librust-sequoia-keystore-softkeys-dev/0.5.0-1/ppc64el to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/ppc64el uninstallable
    • migrating librust-sequoia-keystore-softkeys-dev/0.5.0-1/s390x to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/s390x uninstallable
    • Build-Depends(-Arch): rust-sequoia-keystore-softkeys rust-sequoia-keystore-backend (not considered)
    • Depends: rust-sequoia-keystore-softkeys rust-sequoia-keystore-backend (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-keystore-softkeys.html
    • autopkgtest for rust-sequoia-keystore-softkeys/0.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
    • 3 days old (needed 2 days)
• scilab (2024.1.0+dfsg-1 to 2024.1.0+dfsg-2)
  • Migration status for scilab (2024.1.0+dfsg-1 to 2024.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 3 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-2: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • No reference result, but not reproducibility on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• sdop (1.10-2 to 1.10-3)
  • Migration status for sdop (1.10-2 to 1.10-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• simple-scan (44.0-1 to 46.0-1)
  • Migration status for simple-scan (44.0-1 to 46.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simple-scan.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• storm (0.26-2 to 0.26-3)
  • Migration status for storm (0.26-2 to 0.26-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for storm/0.26-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 ♻
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/storm.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• swift (2.33.0-5 to 2.33.0-6)
  • Migration status for swift (2.33.0-5 to 2.33.0-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating swift will fix bugs in testing: #1074021
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swift.html
    • autopkgtest for swift/2.33.0-6: 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)
    • autopkgtest for swift/blocked-on-ci-infra: s390x: Failed (not a regression)
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• tayga (0.9.2-8 to 0.9.2-9)
  • Migration status for tayga (0.9.2-8 to 0.9.2-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/t/tayga.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• texlive-base (2024.20240401-3 to 2024.20240706-1)
  • Migration status for texlive-base (2024.20240401-3 to 2024.20240706-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/t/texlive-base.html
    • Too young, only 3 of 5 days old
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• texlive-lang (2024.20240401-3 to 2024.20240706-1)
  • Migration status for texlive-lang (2024.20240401-3 to 2024.20240706-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/texlive-lang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• unrardll (0.1.7+ds-1 to 0.1.7+ds-2)
  • Migration status for unrardll (0.1.7+ds-1 to 0.1.7+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for unrardll/0.1.7+ds-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻)
• uriparser (0.9.7+dfsg-2 to 0.9.8+dfsg-1)
  • Migration status for uriparser (0.9.7+dfsg-2 to 0.9.8+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uriparser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ust (2.13.8-1 to 2.13.8-2)
  • Migration status for ust (2.13.8-1 to 2.13.8-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for libcamera/0.3.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating ust will fix bugs in testing: #1065994
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ust.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• weex (2.8.4.2 to 2.8.4.3)
  • Migration status for weex (2.8.4.2 to 2.8.4.3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/weex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• wireshark (4.2.5-2 to 4.2.6-1)
  • Migration status for wireshark (4.2.5-2 to 4.2.6-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 wireshark/4.2.6-1: amd64: Failed (not a regression), arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Failed (not a regression), s390x: Failed (not a regression)
    • Too young, only 3 of 5 days old
    • Depends: wireshark libgcrypt20
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wireshark.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• appmenu-registrar (0.7.6-2 to 24.05-1)
  • Migration status for appmenu-registrar (0.7.6-2 to 24.05-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appmenu-registrar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• chatty (0.8.3-1 to 0.8.4-1)
  • Migration status for chatty (0.8.3-1 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
    • Depends: chatty libgcrypt20
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chatty.html
    • autopkgtest for chatty/0.8.4-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
• classmate (1.3.4-2 to 1.3.4-3)
  • Migration status for classmate (1.3.4-2 to 1.3.4-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/classmate.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Reproducible on i386 - info ♻
• cramfsswap (1.4.2 to 1.4.4)
  • Migration status for cramfsswap (1.4.2 to 1.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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cramfsswap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• curl (8.8.0-1 to 8.8.0-4)
  • Migration status for curl (8.8.0-1 to 8.8.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for curl/8.8.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • autopkgtest for munin/2.0.76-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • autopkgtest for stenographer/1.0.1-4: amd64: No tests, superficial or marked flaky ♻ (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: No tests, superficial or marked flaky ♻ (reference ♻), 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/c/curl.html
• damo (2.4.0-1 to 2.4.2-1)
  • Migration status for damo (2.4.0-1 to 2.4.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/damo.html
    • autopkgtest for damo/2.4.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• debugedit (1:5.0-5 to 1:5.0-6)
  • Migration status for debugedit (1:5.0-5 to 1:5.0-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debugedit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• doxyqml (0.3.0-1.1 to 0.3.0-1.2)
  • Migration status for doxyqml (0.3.0-1.1 to 0.3.0-1.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating doxyqml will fix bugs in testing: #1065851
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/doxyqml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• eximdoc4 (4.97~RC2-1 to 4.98-1)
  • Migration status for eximdoc4 (4.97~RC2-1 to 4.98-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/eximdoc4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• firefox (- to 128.0-1)
  • Migration status for firefox (- to 128.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating firefox would introduce bugs in testing: #1017919, #1073074, #817954, #992263, #993659
    • missing build on armhf
    • missing build on mips64el
    • arch:armhf not built yet, autopkgtest delayed there
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/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 ♻
• fontmanager.app (0.1-3 to 0.1-4)
  • Migration status for fontmanager.app (0.1-3 to 0.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fontmanager.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• fonts-lxgw-wenkai (1.315+repack-1 to 1.330+repack-1)
  • Migration status for fonts-lxgw-wenkai (1.315+repack-1 to 1.330+repack-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-lxgw-wenkai.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• freecad (- to 0.21.2+dfsg1-5)
  • Migration status for freecad (- to 0.21.2+dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for freecad/0.21.2+dfsg1-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 ♻
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freecad.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 ♻
• gcc-11 (11.4.0-9 to 11.4.0-10)
  • Migration status for gcc-11 (11.4.0-9 to 11.4.0-10): 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 gcc-11/11.4.0-10: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility reference results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
• gio-qt (0.0.12-1 to 0.0.14-2)
  • Migration status for gio-qt (0.0.12-1 to 0.0.14-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gio-qt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• globus-gridftp-server-control (9.3-5 to 9.3-6)
  • Migration status for globus-gridftp-server-control (9.3-5 to 9.3-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globus-gridftp-server-control.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-settings-daemon (46.0-1 to 46.0-5)
  • Migration status for gnome-settings-daemon (46.0-1 to 46.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-settings-daemon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• gnome-software (46.2-1 to 46.3-1)
  • Migration status for gnome-software (46.2-1 to 46.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/g/gnome-software.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnome-user-share (43.0-1 to 47~alpha-1)
  • Migration status for gnome-user-share (43.0-1 to 47~alpha-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-user-share.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• gnustep-examples (1:1.4.0-3 to 1:1.4.0-4)
  • Migration status for gnustep-examples (1:1.4.0-3 to 1:1.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnustep-examples.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• gorm.app (1.3.1-1 to 1.4.0-5)
  • Migration status for gorm.app (1.3.1-1 to 1.4.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gorm.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• gtk+3.0 (3.24.42-1 to 3.24.43-1)
  • Migration status for gtk+3.0 (3.24.42-1 to 3.24.43-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for gtk+3.0/3.24.43-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for openjdk-21/21.0.4~6ea-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk+3.0.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 4 days old (needed 2 days)
• hypercorn (0.14.4-1 to 0.17.3-1)
  • Migration status for hypercorn (0.14.4-1 to 0.17.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 7 days old
    • Build-Depends(-Arch): hypercorn node-mermaid (not considered)
  • 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
• ibus-typing-booster (2.25.11-1 to 2.25.12-1)
  • Migration status for ibus-typing-booster (2.25.11-1 to 2.25.12-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibus-typing-booster.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
• iio-sensor-proxy (- to 3.5-2)
  • Migration status for iio-sensor-proxy (- to 3.5-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iio-sensor-proxy.html
    • autopkgtest for iio-sensor-proxy/3.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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• iotas (0.2.14+ds-1 to 0.8.0+ds-1)
  • Migration status for iotas (0.2.14+ds-1 to 0.8.0+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iotas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• jline3 (3.3.1-3 to 3.3.1-4)
  • Migration status for jline3 (3.3.1-3 to 3.3.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/j/jline3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Reproducible on i386 - info ♻
• jtreg7 (7.3.1+1+ds1-2 to 7.4+1+ds1-1)
  • Migration status for jtreg7 (7.3.1+1+ds1-2 to 7.4+1+ds1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for jtreg7/7.4+1+ds1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for openjdk-23/23~28ea-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jtreg7.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
• ktls-utils (0.10-1 to 0.11-1)
  • Migration status for ktls-utils (0.10-1 to 0.11-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktls-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• kwartz-client (3.0-11 to 3.0-12)
  • Migration status for kwartz-client (3.0-11 to 3.0-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/k/kwartz-client.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libproxy (0.5.6-1 to 0.5.7-1)
  • Migration status for libproxy (0.5.6-1 to 0.5.7-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libproxy.html
    • autopkgtest for libproxy/0.5.7-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (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 ♻
• libsis-base-java (18.09~pre1+git20180928.45fbd31+dfsg-3 to 18.09~pre1+git20180928.45fbd31+dfsg-4)
  • Migration status for libsis-base-java (18.09~pre1+git20180928.45fbd31+dfsg-3 to 18.09~pre1+git20180928.45fbd31+dfsg-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsis-base-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• libyuv (0.0.1888.20240509-4 to 0.0.1888.20240710-2)
  • Migration status for libyuv (0.0.1888.20240509-4 to 0.0.1888.20240710-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/liby/libyuv.html
    • autopkgtest for libyuv/0.0.1888.20240710-2: amd64: Pass, arm64: Pass, armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
• libzypp (17.35.0-2 to 17.35.2-1)
  • Migration status for libzypp (17.35.0-2 to 17.35.2-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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libz/libzypp.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
• meshtastic (- to 2.3.14-1)
  • Migration status for meshtastic (- to 2.3.14-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meshtastic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• meson (1.4.1-1 to 1.5.0-1)
  • Migration status for meson (1.4.1-1 to 1.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meson.html
    • autopkgtest for meson/1.5.0-1: amd64: Pass, arm64: Failed (not a regression), armel: Failed (not a regression), armhf: Pass, i386: Failed (not a regression), ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Reproducible on amd64 - info ♻
• meta-gnome3 (1:46+1 to 1:46+2)
  • Migration status for meta-gnome3 (1:46+1 to 1:46+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/m/meta-gnome3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• metro-policy (2.7.2-3 to 2.7.2-4)
  • Migration status for metro-policy (2.7.2-3 to 2.7.2-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/metro-policy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Reproducible on i386 - info ♻
• mina (1.1.7.dfsg-13 to 1.1.7.dfsg-14)
  • Migration status for mina (1.1.7.dfsg-13 to 1.1.7.dfsg-14): Waiting for test results or 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/mina.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• mobile-tweaks (6 to 7)
  • Migration status for mobile-tweaks (6 to 7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mobile-tweaks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• msgraph (0.2.2-1 to 0.2.3-1)
  • Migration status for msgraph (0.2.2-1 to 0.2.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): msgraph uhttpmock (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/msgraph.html
    • autopkgtest for msgraph/0.2.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
    • 4 days old (needed 2 days)
• owncloud-client (- to 5.2.1.13040+dfsg-3.0.1)
  • Migration status for owncloud-client (- to 5.2.1.13040+dfsg-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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/owncloud-client.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• pass-tomb (1.3-3 to 1.3-4)
  • Migration status for pass-tomb (1.3-3 to 1.3-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pass-tomb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• passes-gtk (0.9-1 to 0.10-1)
  • Migration status for passes-gtk (0.9-1 to 0.10-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/passes-gtk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• pmix (5.0.2-3 to 5.0.3-1)
  • Migration status for pmix (5.0.2-3 to 5.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pmix would introduce bugs in testing: #1076148
    • autopkgtest for mpi4py/3.1.6-1: 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 ♻)
    • autopkgtest for openmpi/4.1.6-13.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 slurm-wlm/23.11.4-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • missing build on mips64el
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pmix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• port-for (0.7.2-1 to 0.7.2-2)
  • Migration status for port-for (0.7.2-1 to 0.7.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/port-for.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• price.app (1.3.0-5 to 1.3.0-6)
  • Migration status for price.app (1.3.0-5 to 1.3.0-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/price.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• procps (2:4.0.4-4 to 2:4.0.4-5)
  • Migration status for procps (2:4.0.4-4 to 2:4.0.4-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/procps.html
    • autopkgtest for glance/2:28.0.1-3+deb12u1: s390x: Pass
    • autopkgtest for mariadb/1:10.11.8-1: s390x: Pass
    • autopkgtest for procps/2:4.0.4-5: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Ignored failure
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• pyqi (0.3.2+dfsg-9 to 0.3.2+dfsg-10)
  • Migration status for pyqi (0.3.2+dfsg-9 to 0.3.2+dfsg-10): Waiting for test results or 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 pyqi will fix bugs in testing: #1074741
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyqi.html
    • autopkgtest for pyqi/0.3.2+dfsg-10: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), armel: No tests, superficial or marked flaky ♻ (reference ♻), armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-enigma (0.1-3 to 0.1-4)
  • Migration status for python-enigma (0.1-3 to 0.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating python-enigma will fix bugs in testing: #1065928
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-enigma.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• python-igraph (0.11.5+ds-2 to 0.11.6+ds-1)
  • Migration status for python-igraph (0.11.5+ds-2 to 0.11.6+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-igraph.html
    • autopkgtest for python-igraph/0.11.6+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), 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 ♻
• python-rioxarray (0.15.7-1 to 0.16.0-1)
  • Migration status for python-rioxarray (0.15.7-1 to 0.16.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-rioxarray.html
    • autopkgtest for python-rioxarray/0.16.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 ♻
• python-skbio (0.6.1-2 to 0.6.1-3)
  • Migration status for python-skbio (0.6.1-2 to 0.6.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-skbio/0.6.1-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Failed (not a regression)
    • autopkgtest for q2-alignment/2024.5.0-1: amd64: Failed (not a regression), arm64: Failed (not a regression), ppc64el: Failed (not a regression), riscv64: Regression or new test ♻ (reference ♻)
    • autopkgtest for q2-diversity-lib/2024.5.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Failed (not a regression), riscv64: Failed (not a regression)
    • autopkgtest for q2-feature-table/2024.5.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression)
    • autopkgtest for q2-fragment-insertion/2024.5.0-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating python-skbio will fix bugs in testing: #1074745
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-skbio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-srp (1.0.20-1 to 1.0.21-1)
  • Migration status for python-srp (1.0.20-1 to 1.0.21-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-srp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• randomplay (0.60+pristine-2 to 0.60+pristine-3)
  • Migration status for randomplay (0.60+pristine-2 to 0.60+pristine-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/randomplay.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• secrets (- to 9.5-1)
  • Migration status for secrets (- to 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
    • Build-Depends(-Arch): secrets python-zxcvbn (not considered)
    • Depends: secrets python-zxcvbn (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/secrets.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• sherlock (0.14.4+git20240531.e5ad3c4-2 to 0.15.0-1)
  • Migration status for sherlock (0.14.4+git20240531.e5ad3c4-2 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 4 of 5 days old
  • Additional info:
    • Updating sherlock will fix bugs in testing: #1071007, #1072733
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sherlock.html
    • autopkgtest for sherlock/0.15.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 ♻
• sngrep (1.8.1-1 to 1.8.2-1)
  • Migration status for sngrep (1.8.1-1 to 1.8.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
    • Depends: sngrep libgcrypt20
  • Additional info:
    • Updating sngrep will fix bugs in testing: #1071954
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sngrep.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• steptalk (0.10.0-6 to 0.10.0+git20200629-2)
  • Migration status for steptalk (0.10.0-6 to 0.10.0+git20200629-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): steptalk gnustep-dl2 (not considered)
    • Depends: steptalk gnustep-dl2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/steptalk.html
    • autopkgtest for steptalk/0.10.0+git20200629-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 4 days old (needed 2 days)
• superlu-dist (8.2.1+dfsg1-1 to 8.2.1+dfsg1-2)
  • Migration status for superlu-dist (8.2.1+dfsg1-1 to 8.2.1+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for hypre/2.29.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • autopkgtest for superlu-dist/8.2.1+dfsg1-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating superlu-dist will fix bugs in testing: #1076030
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/superlu-dist.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• tkcvs (8.2.3-3 to 8.2.3-4)
  • Migration status for tkcvs (8.2.3-3 to 8.2.3-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tkcvs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• ttf-ancient-fonts (2.60-1.1 to 2.60-2)
  • Migration status for ttf-ancient-fonts (2.60-1.1 to 2.60-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/t/ttf-ancient-fonts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• uhttpmock (0.10.0-3 to 0.11.0-1)
  • Migration status for uhttpmock (0.10.0-3 to 0.11.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uhttpmock.html
• urwid (2.6.14-1 to 2.6.15-1)
  • Migration status for urwid (2.6.14-1 to 2.6.15-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/urwid.html
    • autopkgtest for urwid/2.6.15-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 armhf - info ♻
    • Reproducible on i386 - info ♻
• vala-panel-appmenu (0.7.6+dfsg1-4 to 0.7.6+dfsg1-5)
  • Migration status for vala-panel-appmenu (0.7.6+dfsg1-4 to 0.7.6+dfsg1-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vala-panel-appmenu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• vttest (2.7+20230201-1 to 2.7+20240708-1)
  • Migration status for vttest (2.7+20230201-1 to 2.7+20240708-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vttest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• wikitrans (- to 1.4-1)
  • Migration status for wikitrans (- to 1.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wikitrans.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• xfce4-sntray-plugin (0.4.13.1-2 to 0.4.13.1-3)
  • Migration status for xfce4-sntray-plugin (0.4.13.1-2 to 0.4.13.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/x/xfce4-sntray-plugin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• xmacro (0.3pre-20000911-9 to 0.3pre-20000911-10)
  • Migration status for xmacro (0.3pre-20000911-9 to 0.3pre-20000911-10): Waiting for test results or 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/xmacro.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• zutty (0.15.7.20240421+dfsg1-1 to 0.16.0.20240607+dfsg1-1)
  • Migration status for zutty (0.15.7.20240421+dfsg1-1 to 0.16.0.20240607+dfsg1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zutty.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• cmake (3.29.6-1 to 3.30.0-1)
  • Migration status for cmake (3.29.6-1 to 3.30.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for boost1.83/1.83.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Failed (not a regression), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for cmake/3.30.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, riscv64: Failed (not a regression), s390x: Pass
    • autopkgtest for cmake/blocked-on-ci-infra: ppc64el: Failed (not a regression)
    • autopkgtest for dart/6.12.1+dfsg4-13.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: Failed (not a regression)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cmake.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• csaps (1.1.0-2 to 1.2.0-1)
  • Migration status for csaps (1.1.0-2 to 1.2.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/csaps.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 5 days old (needed 5 days)
• firefox-esr (115.12.0esr-1 to 115.13.0esr-1)
  • Migration status for firefox-esr (115.12.0esr-1 to 115.13.0esr-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firefox-esr.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 ♻
    • 5 days old (needed 5 days)
• gcc-14 (14-20240330-1 to 14.1.0-4)
  • Migration status for gcc-14 (14-20240330-1 to 14.1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cctbx/2023.12+ds2+~3.17.0+ds1-4: amd64: Failed (not a regression), arm64: Pass, ppc64el: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for dune-grid/2.9.0-4: 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 gcc-14/14.1.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • autopkgtest for pandas/2.1.4+dfsg-8: s390x: Pass
    • autopkgtest for pytango/9.5.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression)
    • autopkgtest for python-cryptography/42.0.5-2: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Pass, ppc64el: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python3.13/3.13.0~b2-1: s390x: Pass
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): gcc-14 amdgcn-tools-18
    • Depends: gcc-14 amdgcn-tools-18
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-14.html
    • No reference result, but not reproducibility on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • No reference result, but not reproducibility on i386 - info ♻
    • 5 days old (needed 5 days)
• gnustep-dl2 (0.12.0-16 to 0.12.0+git20171224-3)
  • Migration status for gnustep-dl2 (0.12.0-16 to 0.12.0+git20171224-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): gnustep-dl2 gorm.app (not considered)
    • Depends: gnustep-dl2 gorm.app (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnustep-dl2.html
    • autopkgtest for gnustep-dl2/0.12.0+git20171224-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
    • 5 days old (needed 2 days)
• grub-efi-amd64-signed (1+2.12+2 to 1+2.12+4)
  • Migration status for grub-efi-amd64-signed (1+2.12+2 to 1+2.12+4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): grub-efi-amd64-signed grub2 (not considered)
    • Built-Using: grub-efi-amd64-signed grub2 (not considered)
    • Depends: grub-efi-amd64-signed grub2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grub-efi-amd64-signed.html
    • Reproducible on amd64 - info ♻
    • 5 days old (needed 5 days)
• grub-efi-arm64-signed (1+2.12+2 to 1+2.12+4)
  • Migration status for grub-efi-arm64-signed (1+2.12+2 to 1+2.12+4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): grub-efi-arm64-signed grub2 (not considered)
    • Built-Using: grub-efi-arm64-signed grub2 (not considered)
    • Depends: grub-efi-arm64-signed grub2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
• grub-efi-ia32-signed (1+2.12+2 to 1+2.12+4)
  • Migration status for grub-efi-ia32-signed (1+2.12+2 to 1+2.12+4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): grub-efi-ia32-signed grub2 (not considered)
    • Built-Using: grub-efi-ia32-signed grub2 (not considered)
    • Depends: grub-efi-ia32-signed grub2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• grub2 (2.12-2 to 2.12-4)
  • Migration status for grub2 (2.12-2 to 2.12-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating grub2 would introduce bugs in testing: #1076235
    • Implicit dependency: grub2 grub-efi-amd64-signed
    • Implicit dependency: grub2 grub-efi-arm64-signed
    • Implicit dependency: grub2 grub-efi-ia32-signed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grub2.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 5 days old (needed 5 days)
• libgcrypt20 (1.10.3-3 to 1.11.0-2)
  • Migration status for libgcrypt20 (1.10.3-3 to 1.11.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 5 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgcrypt20.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
• mpich (4.2.0-6 to 4.2.0-9)
  • Migration status for mpich (4.2.0-6 to 4.2.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dune-grid/2.9.0-4: 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 hypre/2.29.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
    • autopkgtest for mpich/4.2.0-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Depends: mpich ucx (not considered)
  • Additional info:
    • Updating mpich will fix bugs in testing: #1028172
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpich.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 5 days old (needed 5 days)
• nodejs (20.15.0+dfsg-1 to 20.15.1+dfsg-1)
  • Migration status for nodejs (20.15.0+dfsg-1 to 20.15.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nodejs/20.15.1+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nodejs.html
    • 5 days old (needed 5 days)
• nss (2:3.101-1 to 2:3.102-1)
  • Migration status for nss (2:3.101-1 to 2:3.102-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for openjdk-23/23~28ea-1: amd64: Pass, arm64: Pass, armel: Failed (not a regression), armhf: Failed (not a regression), i386: Pass, ppc64el: Pass, riscv64: Test in progress, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nss.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 5 days old (needed 5 days)
• onboard (- to 1.4.1-7)
  • Migration status for onboard (- to 1.4.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating onboard would introduce bugs in testing: #1076120
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onboard.html
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• opm-grid (2024.04+ds-2 to 2024.04+ds-3)
  • Migration status for opm-grid (2024.04+ds-2 to 2024.04+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for opm-grid/2024.04+ds-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • autopkgtest for opm-models/2024.04+ds-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opm-grid.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
• pillow (10.3.0-2 to 10.4.0-1)
  • Migration status for pillow (10.3.0-2 to 10.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cctbx/2023.12+ds2+~3.17.0+ds1-4: amd64: Failed (not a regression), arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for pillow/10.4.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/p/pillow.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• python-packaging (24.0-1 to 24.1-1)
  • Migration status for python-packaging (24.0-1 to 24.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for azure-cli/2.61.0-1: s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for pytango/9.5.0-3: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Failed (not a regression), riscv64: Pass
    • autopkgtest for python-asdf/3.2.0-1: s390x: Pass
    • autopkgtest for python-geopandas/0.14.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for sip6/6.8.3+dfsg-1: s390x: No tests, superficial or marked flaky
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-packaging.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• rmpi (0.7-2-1 to 0.7-2-2)
  • Migration status for rmpi (0.7-2-1 to 0.7-2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-metamix/0.3-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating rmpi will fix bugs in testing: #1075978
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rmpi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 5 days old (needed 5 days)
• rust-axum (- to 0.6.20-21)
  • Migration status for rust-axum (- to 0.6.20-21): 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): rust-axum rust-prost
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-axum.html
    • 5 days old (needed 5 days)
• rust-wayland-sys-0.29 (0.29.5-2 to 0.29.5-3)
  • Migration status for rust-wayland-sys-0.29 (0.29.5-2 to 0.29.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-wayland-sys-0.29 rust-memoffset (not considered)
    • Invalidated by dependency
  • Additional info:
    • Updating rust-wayland-sys-0.29 will fix bugs in testing: #1076058
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-wayland-sys-0.29.html
    • autopkgtest for rust-wayland-sys-0.29/0.29.5-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
    • 5 days old (needed 2 days)
• weborf (1.2-1 to 1.3-1)
  • Migration status for weborf (1.2-1 to 1.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 5 of 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/weborf.html
    • autopkgtest for weborf/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
• ffmpeg (7:6.1.1-4 to 7:6.1.1-5)
  • Migration status for ffmpeg (7:6.1.1-4 to 7:6.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for avifile/1:0.7.48~20090503.ds-26: amd64: Pass, arm64: Pass, armel: Pass, armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for ffmpeg/7:6.1.1-5: 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/f/ffmpeg.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Reproducible on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 6 days old (needed 5 days)
• gffread (0.12.7-4 to 0.12.7-6)
  • Migration status for gffread (0.12.7-4 to 0.12.7-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gffread/0.12.7-6: 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/g/gffread.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 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 ♻
    • 6 days old (needed 5 days)
• libvmod-re2 (- to 2.0.0-4)
  • Migration status for libvmod-re2 (- to 2.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for libvmod-re2/2.0.0-4: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Too young, only 6 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvmod-re2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• 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:
    • 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
    • autopkgtest for symfony/6.4.7+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: Pass
    • 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-doctrine-persistence.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• purple-lurch (- to 0.7.0-2.1)
  • Migration status for purple-lurch (- to 0.7.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • purple-lurch/armel has unsatisfiable dependency
    • purple-lurch/armhf has unsatisfiable dependency
    • autopkgtest for purple-lurch/0.7.0-2.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/purple-lurch.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 6 days old (needed 5 days)
• python3-stdlib-extensions (3.12.3-3.1 to 3.12.4-1)
  • Migration status for python3-stdlib-extensions (3.12.3-3.1 to 3.12.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • removing python3-distutils/3.12.3-3.1/amd64 from testing makes grass-core/8.3.2-1+b2/amd64 uninstallable
    • removing python3-distutils/3.12.3-3.1/amd64 from testing makes hamster-time-tracker/3.0.3-1/amd64 uninstallable
    • removing python3-distutils/3.12.3-3.1/amd64 from testing makes python3-azure-cli-core/2.62.0-1/amd64 uninstallable
    • removing python3-distutils/3.12.3-3.1/amd64 from testing makes python3.11-full/3.11.9-1/amd64 uninstallable
    • removing python3-distutils/3.12.3-3.1/amd64 from testing makes python3.11-venv/3.11.9-1/amd64 uninstallable
    • removing python3-distutils/3.12.3-3.1/amd64 from testing makes wfuzz/3.1.0-4/amd64 uninstallable
    • migrating python3-gdbm/3.12.4-1/amd64 to testing makes python3.11-full/3.11.9-1/amd64 uninstallable
    • migrating python3-lib2to3/3.12.4-1/amd64 to testing makes python3.11-full/3.11.9-1/amd64 uninstallable
    • migrating python3-tk/3.12.4-1/amd64 to testing makes idle-python3.11/3.11.9-1/amd64 uninstallable
    • migrating python3-tk/3.12.4-1/amd64 to testing makes python3.11-full/3.11.9-1/amd64 uninstallable
    • removing python3-distutils/3.12.3-3.1/arm64 from testing makes grass-core/8.3.2-1+b2/arm64 uninstallable
    • removing python3-distutils/3.12.3-3.1/arm64 from testing makes hamster-time-tracker/3.0.3-1/arm64 uninstallable
    • removing python3-distutils/3.12.3-3.1/arm64 from testing makes python3-azure-cli-core/2.62.0-1/arm64 uninstallable
    • removing python3-distutils/3.12.3-3.1/arm64 from testing makes python3.11-full/3.11.9-1/arm64 uninstallable
    • removing python3-distutils/3.12.3-3.1/arm64 from testing makes python3.11-venv/3.11.9-1/arm64 uninstallable
    • removing python3-distutils/3.12.3-3.1/arm64 from testing makes wfuzz/3.1.0-4/arm64 uninstallable
    • migrating python3-gdbm/3.12.4-1/arm64 to testing makes python3.11-full/3.11.9-1/arm64 uninstallable
    • migrating python3-lib2to3/3.12.4-1/arm64 to testing makes python3.11-full/3.11.9-1/arm64 uninstallable
    • migrating python3-tk/3.12.4-1/arm64 to testing makes idle-python3.11/3.11.9-1/arm64 uninstallable
    • migrating python3-tk/3.12.4-1/arm64 to testing makes python3.11-full/3.11.9-1/arm64 uninstallable
    • removing python3-distutils/3.12.3-3.1/armel from testing makes grass-core/8.3.2-1+b1/armel uninstallable
    • removing python3-distutils/3.12.3-3.1/armel from testing makes python3.11-full/3.11.9-1/armel uninstallable
    • removing python3-distutils/3.12.3-3.1/armel from testing makes python3.11-venv/3.11.9-1/armel uninstallable
    • migrating python3-gdbm/3.12.4-1/armel to testing makes python3.11-full/3.11.9-1/armel uninstallable
    • migrating python3-lib2to3/3.12.4-1/armel to testing makes python3.11-full/3.11.9-1/armel uninstallable
    • migrating python3-tk/3.12.4-1/armel to testing makes python3.11-full/3.11.9-1/armel uninstallable
    • removing python3-distutils/3.12.3-3.1/armhf from testing makes grass-core/8.3.2-1+b1/armhf uninstallable
    • removing python3-distutils/3.12.3-3.1/armhf from testing makes python3.11-full/3.11.9-1/armhf uninstallable
    • removing python3-distutils/3.12.3-3.1/armhf from testing makes python3.11-venv/3.11.9-1/armhf uninstallable
    • migrating python3-gdbm/3.12.4-1/armhf to testing makes python3.11-full/3.11.9-1/armhf uninstallable
    • migrating python3-lib2to3/3.12.4-1/armhf to testing makes python3.11-full/3.11.9-1/armhf uninstallable
    • migrating python3-tk/3.12.4-1/armhf to testing makes python3.11-full/3.11.9-1/armhf uninstallable
    • removing python3-distutils/3.12.3-3.1/i386 from testing makes grass-core/8.3.2-1+b2/i386 uninstallable
    • removing python3-distutils/3.12.3-3.1/i386 from testing makes python3.11-full/3.11.9-1/i386 uninstallable
    • removing python3-distutils/3.12.3-3.1/i386 from testing makes python3.11-venv/3.11.9-1/i386 uninstallable
    • migrating python3-gdbm/3.12.4-1/i386 to testing makes python3.11-full/3.11.9-1/i386 uninstallable
    • migrating python3-lib2to3/3.12.4-1/i386 to testing makes python3.11-full/3.11.9-1/i386 uninstallable
    • migrating python3-tk/3.12.4-1/i386 to testing makes python3.11-full/3.11.9-1/i386 uninstallable
    • removing python3-distutils/3.12.3-3.1/mips64el from testing makes grass-core/8.3.2-1+b2/mips64el uninstallable
    • removing python3-distutils/3.12.3-3.1/mips64el from testing makes python3.11-full/3.11.9-1/mips64el uninstallable
    • removing python3-distutils/3.12.3-3.1/mips64el from testing makes python3.11-venv/3.11.9-1/mips64el uninstallable
    • migrating python3-gdbm/3.12.4-1/mips64el to testing makes python3.11-full/3.11.9-1/mips64el uninstallable
    • migrating python3-lib2to3/3.12.4-1/mips64el to testing makes python3.11-full/3.11.9-1/mips64el uninstallable
    • migrating python3-tk/3.12.4-1/mips64el to testing makes python3.11-full/3.11.9-1/mips64el uninstallable
    • removing python3-distutils/3.12.3-3.1/ppc64el from testing makes grass-core/8.3.2-1+b2/ppc64el uninstallable
    • removing python3-distutils/3.12.3-3.1/ppc64el from testing makes python3.11-full/3.11.9-1/ppc64el uninstallable
    • removing python3-distutils/3.12.3-3.1/ppc64el from testing makes python3.11-venv/3.11.9-1/ppc64el uninstallable
    • migrating python3-gdbm/3.12.4-1/ppc64el to testing makes python3.11-full/3.11.9-1/ppc64el uninstallable
    • migrating python3-lib2to3/3.12.4-1/ppc64el to testing makes python3.11-full/3.11.9-1/ppc64el uninstallable
    • migrating python3-tk/3.12.4-1/ppc64el to testing makes python3.11-full/3.11.9-1/ppc64el uninstallable
    • removing python3-distutils/3.12.3-3.1/s390x from testing makes grass-core/8.3.2-1+b2/s390x uninstallable
    • removing python3-distutils/3.12.3-3.1/s390x from testing makes python3.11-full/3.11.9-1/s390x uninstallable
    • removing python3-distutils/3.12.3-3.1/s390x from testing makes python3.11-venv/3.11.9-1/s390x uninstallable
    • migrating python3-gdbm/3.12.4-1/s390x to testing makes python3.11-full/3.11.9-1/s390x uninstallable
    • migrating python3-lib2to3/3.12.4-1/s390x to testing makes python3.11-full/3.11.9-1/s390x uninstallable
    • migrating python3-tk/3.12.4-1/s390x to testing makes python3.11-full/3.11.9-1/s390x uninstallable
    • autopkgtest for pandas/2.1.4+dfsg-8: s390x: Pass
    • autopkgtest for python3.11/3.11.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: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python3.12/3.12.4-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python3.13/3.13.0~b2-1: riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • Implicit dependency: python3-stdlib-extensions docker-compose (not considered)
    • Implicit dependency: python3-stdlib-extensions matrix-synapse
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3-stdlib-extensions.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• spopt (- to 0.6.1-2)
  • Migration status for spopt (- to 0.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for spopt/0.6.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spopt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• ucx (1.16.0+ds-5 to 1.17.0+ds-2)
  • Migration status for ucx (1.16.0+ds-5 to 1.17.0+ds-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ucx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
• wxpython4.0 (4.2.1+dfsg-3 to 4.2.1+dfsg-4)
  • Migration status for wxpython4.0 (4.2.1+dfsg-3 to 4.2.1+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cctbx/2023.12+ds2+~3.17.0+ds1-4: amd64: Failed (not a regression), arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
  • Additional info:
    • Updating wxpython4.0 will fix bugs in testing: #1074751
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wxpython4.0.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 6 days old (needed 5 days)
• 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:
    • autopkgtest for collectd/5.12.0-18.1: amd64: Regression or new test ♻, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): collectd nut (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/collectd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 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
    • 7 days old (needed 2 days)
• llvm-toolchain-18 (- to 1:18.1.8-2)
  • Migration status for llvm-toolchain-18 (- to 1:18.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating llvm-toolchain-18 would introduce bugs in testing: #1068961, #1076131
    • Not touching package due to block request by sramacher (please contact debian-release if update is needed)
    • autopkgtest for llvm-toolchain-18/1:18.1.8-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Test in progress, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvm-toolchain-18.html
    • New but not reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• mpi-defaults (1.15 to 1.17)
  • Migration status for mpi-defaults (1.15 to 1.17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for abinit/9.10.4-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, riscv64: Pass, s390x: Pass
    • autopkgtest for armci-mpi/0.4-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for dijitso/2019.2.0~git20190418.c92dcb0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for esys-particle/2.3.5+dfsg2-6: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for h5py/3.11.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for hypre/2.29.0-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Failed (not a regression), i386: Failed (not a regression), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for lammps/20240207+dfsg-1.1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, s390x: Pass
    • autopkgtest for liggghts/3.8.0+repack1-10: 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
    • autopkgtest for mpi4py/3.1.6-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for netgen/6.2.2401+dfsg1-2: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for pytest-mpi/0.6-5: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Failed (not a regression), ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpi-defaults.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• numba (- to 0.59.1+dfsg-2)
  • Migration status for numba (- to 0.59.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating numba would introduce bugs in testing: #1033907
    • autopkgtest for numba/0.59.1+dfsg-2: amd64: Regression or new test ♻
    • 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 ♻
    • 7 days old (needed 5 days)
• r-bioc-rcwl (- to 1.18.0+ds-3)
  • Migration status for r-bioc-rcwl (- to 1.18.0+ds-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-rcwl r-bioc-s4vectors (not considered)
    • Depends: r-bioc-rcwl r-bioc-s4vectors (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rcwl.html
    • autopkgtest for r-bioc-rcwl/1.18.0+ds-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 7 days old (needed 2 days)
• rust-field-offset (0.3.4-1 to 0.3.6-1)
  • Migration status for rust-field-offset (0.3.4-1 to 0.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): rust-field-offset rust-memoffset (not considered)
    • Depends: rust-field-offset rust-memoffset (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-field-offset.html
    • autopkgtest for rust-field-offset/0.3.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
    • 7 days old (needed 2 days)
• rust-intrusive-collections (0.9.4-1 to 0.9.6-1)
  • Migration status for rust-intrusive-collections (0.9.4-1 to 0.9.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-intrusive-collections rust-memoffset (not considered)
    • Depends: rust-intrusive-collections rust-memoffset (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-intrusive-collections.html
    • autopkgtest for rust-intrusive-collections/0.9.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
    • 7 days old (needed 2 days)
• rust-memoffset (0.6.5-1 to 0.8.0-1)
  • Migration status for rust-memoffset (0.6.5-1 to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-memoffset/0.8.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-pyo3/0.20.2-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Implicit dependency: rust-memoffset rust-field-offset
    • Implicit dependency: rust-memoffset rust-intrusive-collections
    • Implicit dependency: rust-memoffset rust-wayland-sys-0.29
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-memoffset.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• rust-process-viewer (0.5.9-2 to 0.5.9-3)
  • Migration status for rust-process-viewer (0.5.9-2 to 0.5.9-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-process-viewer rust-sysinfo (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-process-viewer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• rust-sysinfo (0.28.4-4 to 0.29.11-1)
  • Migration status for rust-sysinfo (0.28.4-4 to 0.29.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-sysinfo/0.29.11-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-vergen/8.2.6-2: arm64: Pass, armel: Pass, s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sysinfo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• rust-vergen (8.2.6-2 to 8.2.6-3)
  • Migration status for rust-vergen (8.2.6-2 to 8.2.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-vergen/8.2.6-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Depends: rust-vergen rust-sysinfo (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-vergen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 days old (needed 5 days)
• zypper (1.14.74-1 to 1.14.76-1)
  • Migration status for zypper (1.14.74-1 to 1.14.76-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: zypper libzypp (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zypper.html
    • autopkgtest for zypper/1.14.76-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 7 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
    • 8 days old (needed 5 days)
• pyroma (- to 4.2-1)
  • Migration status for pyroma (- to 4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyroma.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• python-aioitertools (- to 0.11.0-1)
  • Migration status for python-aioitertools (- to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jdg, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioitertools.html
    • autopkgtest for python-aioitertools/0.11.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• python-google-api-core (- to 2.19.0-1)
  • Migration status for python-google-api-core (- to 2.19.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jak, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-google-api-core.html
    • autopkgtest for python-google-api-core/2.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
    • 8 days old (needed 7 days)
• python-jsonschema-path (- to 0.3.2-1)
  • Migration status for python-jsonschema-path (- to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jdg, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): python-jsonschema-path python-pathable (not considered)
    • Depends: python-jsonschema-path python-pathable (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jsonschema-path.html
    • autopkgtest for python-jsonschema-path/0.3.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• python-pathable (- to 0.4.3-1)
  • Migration status for python-pathable (- to 0.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jdg, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pathable.html
    • autopkgtest for python-pathable/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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• rust-pprof (0.13.0-2 to 0.13.0-4)
  • Migration status for rust-pprof (0.13.0-2 to 0.13.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-pprof rust-prost (not considered)
    • Invalidated by dependency
    • Depends: rust-pprof rust-prost-build
    • Depends: rust-pprof rust-prost-derive
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-pprof.html
    • autopkgtest for rust-pprof/0.13.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 8 days old (needed 5 days)
• rust-prometheus-client (0.21.2-1 to 0.22.2-1)
  • Migration status for rust-prometheus-client (0.21.2-1 to 0.22.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-prometheus-client rust-prost (not considered)
    • Invalidated by dependency
    • Depends: rust-prometheus-client rust-prost-build
    • Depends: rust-prometheus-client rust-prost-types
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-prometheus-client.html
    • autopkgtest for rust-prometheus-client/0.22.2-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 ♻), 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 ♻
    • 8 days old (needed 5 days)
• krb5 (1.21.2-1 to 1.21.3-3)
  • Migration status for krb5 (1.21.2-1 to 1.21.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating krb5 would introduce bugs in testing: #1063648
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/krb5.html
    • autopkgtest for krb5/1.21.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
    • Required age is not allowed to drop below 2 days
    • 9 days old (needed 2 days)
• orthanc-wsi (2.0+dfsg-2 to 2.0+dfsg-3)
  • Migration status for orthanc-wsi (2.0+dfsg-2 to 2.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orthanc-wsi/2.0+dfsg-3: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression), s390x: Pass
  • Additional info:
    • Updating orthanc-wsi will fix bugs in testing: #1075794
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-wsi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 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 ♻
    • 9 days old (needed 5 days)
• qemu (1:8.2.4+ds-1 to 1:9.0.1+ds-1)
  • Migration status for qemu (1:8.2.4+ds-1 to 1:9.0.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qemu would introduce bugs in testing: #1076008
    • Built-Using: qemu gcc-14 (not considered)
  • Additional info:
    • Updating qemu will fix bugs in testing: #1075824
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qemu.html
    • autopkgtest for glance/2:28.0.1-3+deb12u1: s390x: Pass
    • autopkgtest for qemu/1:9.0.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: 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 ♻
    • 9 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 ♻
    • slic3r-prusa unsatisfiable Build-Depends(-Arch) on s390x: libbgcode-dev
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • 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 arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 9 days old (needed 5 days)
• 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
    • Build-Depends(-Arch): ruby-redis-cluster-client ruby-redis-client
    • Depends: ruby-redis-cluster-client ruby-redis-client
  • 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 ♻
    • 10 days old (needed 5 days)
• rust-cntr (- to 1.5.3-2)
  • Migration status for rust-cntr (- to 1.5.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-cntr rust-cntr-fuse (not considered)
    • Depends: rust-cntr rust-cntr-fuse (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • 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
    • 10 days old (needed 2 days)
• rust-prost (0.11.9-1 to 0.12.6-1)
  • Migration status for rust-prost (0.11.9-1 to 0.12.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-prost rust-parsec-service (not considered)
    • Invalidated by implicit-dependency
    • Build-Depends(-Arch): rust-prost rust-prost-derive
    • Depends: rust-prost rust-prost-derive
    • Implicit dependency: rust-prost rust-parsec-interface
    • Implicit dependency: rust-prost rust-pprof
    • Implicit dependency: rust-prost rust-prometheus-client
    • Implicit dependency: rust-prost rust-prost-build
    • Implicit dependency: rust-prost rust-prost-types
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-prost.html
    • autopkgtest for rust-prost/0.12.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• rust-prost-build (0.11.9-3 to 0.12.6-1)
  • Migration status for rust-prost-build (0.11.9-3 to 0.12.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-prost-build rust-parsec-service (not considered)
    • Invalidated by implicit-dependency
    • Build-Depends(-Arch): rust-prost-build rust-prost
    • Build-Depends(-Arch): rust-prost-build rust-prost-types
    • Depends: rust-prost-build rust-prost
    • Depends: rust-prost-build rust-prost-types
    • Implicit dependency: rust-prost-build rust-parsec-interface
    • Implicit dependency: rust-prost-build rust-pprof
    • Implicit dependency: rust-prost-build rust-prometheus-client
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-prost-build.html
    • autopkgtest for rust-prost-build/0.12.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• rust-prost-derive (0.11.9-3 to 0.12.6-1)
  • Migration status for rust-prost-derive (0.11.9-3 to 0.12.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-prost-derive rust-prost (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: rust-prost-derive rust-pprof
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-prost-derive.html
    • autopkgtest for rust-prost-derive/0.12.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• rust-prost-types (0.11.9-1 to 0.12.6-1)
  • Migration status for rust-prost-types (0.11.9-1 to 0.12.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-prost-types rust-prost (not considered)
    • Depends: rust-prost-types rust-prost (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Implicit dependency: rust-prost-types rust-prometheus-client
    • Implicit dependency: rust-prost-types rust-prost-build
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-prost-types.html
    • autopkgtest for rust-prost-types/0.12.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 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: No tests, superficial or 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 ♻
    • 10 days old (needed 5 days)
• rust-sequoia-gpg-agent (0.3.1-2 to 0.4.2-1)
  • Migration status for rust-sequoia-gpg-agent (0.3.1-2 to 0.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-sequoia-gpg-agent/0.4.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 ♻)
    • Build-Depends(-Arch): rust-sequoia-gpg-agent rust-sequoia-ipc (not considered)
    • Depends: rust-sequoia-gpg-agent rust-sequoia-ipc (not considered)
  • Additional info:
    • Updating rust-sequoia-gpg-agent will fix bugs in testing: #1074688
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-gpg-agent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 10 days old (needed 5 days)
• rust-sequoia-keystore-backend (0.2.0-1 to 0.5.0-1)
  • Migration status for rust-sequoia-keystore-backend (0.2.0-1 to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-sequoia-keystore-backend-dev/0.5.0-1/amd64 to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/amd64 uninstallable
    • migrating librust-sequoia-keystore-backend-dev/0.5.0-1/arm64 to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/arm64 uninstallable
    • migrating librust-sequoia-keystore-backend-dev/0.5.0-1/armel to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/armel uninstallable
    • migrating librust-sequoia-keystore-backend-dev/0.5.0-1/armhf to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/armhf uninstallable
    • migrating librust-sequoia-keystore-backend-dev/0.5.0-1/i386 to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/i386 uninstallable
    • migrating librust-sequoia-keystore-backend-dev/0.5.0-1/mips64el to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/mips64el uninstallable
    • migrating librust-sequoia-keystore-backend-dev/0.5.0-1/ppc64el to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/ppc64el uninstallable
    • migrating librust-sequoia-keystore-backend-dev/0.5.0-1/s390x to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/s390x uninstallable
    • Implicit dependency: rust-sequoia-keystore-backend rust-sequoia-keystore-softkeys (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-keystore-backend.html
    • autopkgtest for rust-sequoia-keystore-backend/0.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
    • 10 days old (needed 2 days)
• skimage (0.22.0-3 to 0.24.0-2)
  • Migration status for skimage (0.22.0-3 to 0.24.0-2): 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-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 ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 10 days old (needed 2 days)
• tpm2-pytss (2.2.1-1 to 2.3.0-1)
  • Migration status for tpm2-pytss (2.2.1-1 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:
    • Updating tpm2-pytss will fix bugs in testing: #1073384
    • 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
    • 10 days old (needed 2 days)
• chafa (1.14.0-1.1 to 1.14.1-1)
  • Migration status for chafa (1.14.0-1.1 to 1.14.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 chafa/1.14.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 ♻), 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/c/chafa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 11 days old (needed 5 days)
• chiark-utils (7.0.0 to 7.0.1)
  • Migration status for chiark-utils (7.0.0 to 7.0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chiark-utils would introduce bugs in testing: #1075799, #1075821
    • missing build on amd64
    • missing build on arm64
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chiark-utils.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 11 days old (needed 5 days)
• datalab (- to 0.16.3-1)
  • Migration status for datalab (- to 0.16.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-datalab/arm64 has unsatisfiable dependency
    • autopkgtest for datalab/0.16.3-1: amd64: Pass, armhf: Pass, i386: Pass, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): datalab plotpy (not considered)
    • Depends: datalab plotpy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/datalab.html
    • uninstallable on arch arm64, not running autopkgtest there
    • 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 ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 11 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:
    • 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 amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 11 days old (needed 5 days)
• flask-babel (4.0.0-1 to 4.1.0-1)
  • Migration status for flask-babel (4.0.0-1 to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for flask-babel/4.1.0-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/f/flask-babel.html
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 11 days old (needed 5 days)
• 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
    • Updating genx would introduce bugs in testing: #1058473
    • 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 11 days old (needed 5 days)
• python-mpv (1.0.6-1 to 1.0.7-1)
  • Migration status for python-mpv (1.0.6-1 to 1.0.7-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-mpv.html
    • 11 days old (needed 5 days)
• python-thinc (- to 9.0.0-1)
  • Migration status for python-thinc (- to 9.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-thinc/9.0.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 ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): python-thinc python-srsly (not considered)
    • Depends: python-thinc python-catalogue
    • Depends: python-thinc python-confection
    • Depends: python-thinc python-srsly (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-thinc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 11 days old (needed 5 days)
• ruby-roadie (5.1.0-1 to 5.2.1-1)
  • Migration status for ruby-roadie (5.1.0-1 to 5.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-roadie/5.2.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating ruby-roadie will fix bugs in testing: #1073372
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-roadie.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 11 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: Regression or new test ♻, 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 ♻
    • New but not reproducible on i386 - info ♻
    • 11 days old (needed 5 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:
    • 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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• python-csb43 (0.9.2+dfsg-1 to 0.10.0+dfsg-1)
  • Migration status for python-csb43 (0.9.2+dfsg-1 to 0.10.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-csb43/0.10.0+dfsg-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-csb43.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• python-npe2 (0.7.2-2 to 0.7.6-1)
  • Migration status for python-npe2 (0.7.2-2 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 ♻ (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 python-npe2 will fix bugs in testing: #1073375
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-npe2.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)
• python-pyepics (- to 3.5.6+ds-1)
  • Migration status for python-pyepics (- to 3.5.6+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-pyepics epics-base (not considered)
    • Depends: python-pyepics epics-base (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyepics.html
    • autopkgtest for python-pyepics/3.5.6+ds-1: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 12 days old (needed 2 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:
    • 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 ♻
    • 12 days old (needed 5 days)
• rust-numbat-cli (- to 1.9.0-2)
  • Migration status for rust-numbat-cli (- to 1.9.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rust-numbat-cli rust-rustls (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-numbat-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-proc-macro2 (1.0.85-1 to 1.0.86-1)
  • Migration status for rust-proc-macro2 (1.0.85-1 to 1.0.86-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-impl-trait-for-tuples/0.2.2-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: Regression or new test ♻ (reference ♻), s390x: Failed (not a regression)
    • autopkgtest for rust-mockall-derive/0.12.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
    • autopkgtest for rust-mockall-double/0.3.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test in progress
    • autopkgtest for rust-proc-macro2/1.0.86-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-proc-macro2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 days old (needed 5 days)
• rust-sequoia-cert-store (0.5.0-1 to 0.6.0-2)
  • Migration status for rust-sequoia-cert-store (0.5.0-1 to 0.6.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: rust-sequoia-cert-store rust-sequoia-gpg-agent (not considered)
    • Invalidated by implicit-dependency
    • Implicit dependency: rust-sequoia-cert-store rust-sequoia-wot
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-cert-store.html
    • autopkgtest for rust-sequoia-cert-store/0.6.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
    • 12 days old (needed 2 days)
• rust-sequoia-wot (0.11.0-1 to 0.12.0-1)
  • Migration status for rust-sequoia-wot (0.11.0-1 to 0.12.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-sequoia-wot rust-sequoia-cert-store (not considered)
    • Built-Using: rust-sequoia-wot rust-sequoia-cert-store (not considered)
    • Depends: rust-sequoia-wot rust-sequoia-cert-store (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Updating rust-sequoia-wot will fix bugs in testing: #1074637
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-wot.html
    • autopkgtest for rust-sequoia-wot/0.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
    • 12 days old (needed 2 days)
• shim-signed (1.40 to 1.44)
  • Migration status for shim-signed (1.40 to 1.44): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • shim-signed unsatisfiable Build-Depends(-Arch) on i386: shim-unsigned (= 15.8-1)
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): shim-signed shim (not considered)
    • Built-Using: shim-signed shim (not considered)
    • Depends: shim-signed shim-helpers-amd64-signed
    • Depends: shim-signed shim-helpers-arm64-signed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shim-signed.html
    • 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 ♻
    • 12 days old (needed 5 days)
• tifffile (20240618-1 to 20240702-1)
  • Migration status for tifffile (20240618-1 to 20240702-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tifffile would introduce bugs in testing: #1075798
    • autopkgtest for tifffile/20240702-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻ (reference ♻)
    • Not built on buildd: arch all binaries uploaded by debian@liska.ath.cx, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tifffile.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)
• z88 (- to 13.0.0+dfsg2-7)
  • Migration status for z88 (- to 13.0.0+dfsg2-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): z88 gtkglext (not considered)
    • Depends: z88 gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/z88.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 12 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
    • 13 days old (needed 7 days)
• node-postcss (8.4.31+~cs8.0.26-1 to 8.4.39+~cs9.2.29-1)
  • Migration status for node-postcss (8.4.31+~cs8.0.26-1 to 8.4.39+~cs9.2.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating node-postcss/8.4.39+~cs9.2.29-1/amd64 to testing makes perlnavigator/0.6.0~dfsg-2/amd64 uninstallable
    • migrating node-postcss/8.4.39+~cs9.2.29-1/arm64 to testing makes perlnavigator/0.6.0~dfsg-2/arm64 uninstallable
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-postcss.html
    • autopkgtest for node-postcss/8.4.39+~cs9.2.29-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
    • 13 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 ♻
    • 13 days old (needed 5 days)
• pydevd (2.10.0+ds-10 to 3.1.0+ds-2)
  • Migration status for pydevd (2.10.0+ds-10 to 3.1.0+ds-2): Will attempt migration (Any information below is purely informational)
    • Implicit dependency: pydevd debugpy
  • Additional info:
    • Updating pydevd will fix bugs in testing: #1069412
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydevd.html
    • autopkgtest for pydevd/3.1.0+ds-2: 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
    • 13 days old (needed 2 days)
• r-cran-tmb (1.9.11-2 to 1.9.13-1)
  • Migration status for r-cran-tmb (1.9.11-2 to 1.9.13-1): 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 ♻), 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-tmb/1.9.13-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tmb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 13 days old (needed 5 days)
• ruby-ffaker (2.20.0-1 to 2.23.0-1)
  • Migration status for ruby-ffaker (2.20.0-1 to 2.23.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-ffaker.html
    • 13 days old (needed 5 days)
• ccache (4.9.1-1 to 4.10.1-1)
  • Migration status for ccache (4.9.1-1 to 4.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ccache/4.10.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ccache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dogecoin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 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 ♻
    • 14 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 ♻
    • 14 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
    • 14 days old (needed 2 days)
• mayavi2 (- to 4.8.1-5)
  • Migration status for mayavi2 (- to 4.8.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mayavi2 would introduce bugs in testing: #1074586, #1075851
    • missing build on ppc64el
    • missing build on riscv64
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mayavi2.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 ♻
    • 14 days old (needed 5 days)
• openafs (- to 1.8.12~pre1-1)
  • Migration status for openafs (- to 1.8.12~pre1-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~pre1-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 ♻
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• plotpy (- to 2.4.0-1)
  • Migration status for plotpy (- to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating plotpy would introduce bugs in testing: #1075814, #1075815
    • autopkgtest for plotpy/2.4.0-1: amd64: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plotpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 14 days old (needed 5 days)
• psygnal (0.9.1-2 to 0.11.1-1)
  • Migration status for psygnal (0.9.1-2 to 0.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for magicgui/0.7.2-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for psygnal/0.11.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating psygnal will fix bugs in testing: #1073369
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psygnal.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-openapi-schema-validator (- to 0.6.2-1)
  • Migration status for python-openapi-schema-validator (- to 0.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jdg, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-openapi-schema-validator.html
    • autopkgtest for python-openapi-schema-validator/0.6.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 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-openapi-spec-validator (- to 0.7.1-1)
  • Migration status for python-openapi-spec-validator (- 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 jdg, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): python-openapi-spec-validator python-jsonschema-path (not considered)
    • Build-Depends(-Arch): python-openapi-spec-validator python-openapi-schema-validator (not considered)
    • Depends: python-openapi-spec-validator python-jsonschema-path (not considered)
    • Depends: python-openapi-spec-validator python-openapi-schema-validator (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-openapi-spec-validator.html
    • autopkgtest for python-openapi-spec-validator/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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 14 days old (needed 2 days)
• 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
    • 14 days old (needed 2 days)
• anytree (- to 2.12.1-1)
  • Migration status for anytree (- to 2.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by lool, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/anytree.html
    • autopkgtest for anytree/2.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 ♻, 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 ♻
    • 15 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 ♻
    • 15 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 ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/colorcet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for git-remote-hg/1.0.4~ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): git-remote-hg hg-git (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-remote-hg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 15 days old (needed 5 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 ♻
    • 15 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
    • Build-Depends(-Arch): golang-github-protonmail-gluon golang-github-protonmail-go-mbox (not considered)
  • 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 ♻
    • 15 days old (needed 5 days)
• golang-github-protonmail-go-mbox (- to 1.1.0-1)
  • Migration status for golang-github-protonmail-go-mbox (- 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 nilesh, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-protonmail-go-mbox.html
    • autopkgtest for golang-github-protonmail-go-mbox/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
    • 15 days old (needed 2 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
    • 15 days old (needed 2 days)
• gscan2pdf (2.13.2-1 to 2.13.3-1)
  • Migration status for gscan2pdf (2.13.2-1 to 2.13.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gscan2pdf/2.13.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻ (reference ♻), s390x: Pass
    • Not built on buildd: arch all binaries uploaded by jjr, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating gscan2pdf will fix bugs in testing: #1073489
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gscan2pdf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• guile-3.0 (3.0.9-1 to 3.0.10-1)
  • Migration status for guile-3.0 (3.0.9-1 to 3.0.10-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
    • missing build on mips64el
    • missing build on ppc64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guile-3.0.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 15 days old (needed 5 days)
• lomiri-abook2cal-syncd (- to 1.0.0-2)
  • Migration status for lomiri-abook2cal-syncd (- to 1.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lomiri-abook2cal-syncd/mips64el has unsatisfiable dependency
    • Depends: lomiri-abook2cal-syncd qtorganizer-eds
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-abook2cal-syncd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• lomiri-online-accounts (- to 0.13-1)
  • Migration status for lomiri-online-accounts (- to 0.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lomiri-online-accounts would introduce bugs in testing: #1074537
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-online-accounts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• m2crypto (0.40.1-4 to 0.41.0-1)
  • Migration status for m2crypto (0.40.1-4 to 0.41.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for m2crypto/0.41.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/m2crypto.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 ♻
    • 15 days old (needed 5 days)
• python-persistent (5.2-1 to 6.0-1)
  • Migration status for python-persistent (5.2-1 to 6.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-persistent zope.deferredimport (not considered)
    • Depends: python-persistent zope.deferredimport (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-persistent.html
    • autopkgtest for python-persistent/6.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 15 days old (needed 5 days)
• gcc-snapshot (- to 1:20240629-1)
  • Migration status for gcc-snapshot (- to 1:20240629-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 amd64
    • missing build on arm64
    • missing build on armel
    • 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:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for gcc-snapshot/1:20240629-1: armhf: Pass, i386: Pass
    • Build-Depends(-Arch): gcc-snapshot amdgcn-tools-18
  • 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)
• halide (- to 17.0.2-1)
  • Migration status for halide (- to 17.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
    • Not built on buildd: arch amd64 binaries uploaded by costamagnagianfranco@yahoo.it
    • Build-Depends(-Arch): halide llvm-toolchain-18 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/halide.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • 16 days old (needed 5 days)
• openjdk-11 (- to 11.0.24~7ea-1)
  • Migration status for openjdk-11 (- to 11.0.24~7ea-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-11 would introduce bugs in testing: #1023237, #1071118
    • autopkgtest for openjdk-11/blocked-on-ci-infra: 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/o/openjdk-11.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 16 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: Pass, 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 ♻
    • 16 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 ♻
    • Build-Depends(-Arch): rust-ntpd rust-ntp-udp (not considered)
    • Built-Using: rust-ntpd rust-rustls (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 ♻
    • 16 days old (needed 5 days)
• debusine (- to 0.4.1)
  • Migration status for debusine (- to 0.4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for debusine/0.4.1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debusine.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 17 days old (needed 5 days)
• gpscorrelate (2.0-4 to 2.1-2)
  • Migration status for gpscorrelate (2.0-4 to 2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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 ♻
  • Additional info:
    • Updating gpscorrelate will fix bugs in testing: #1074151
    • 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 ♻
    • 17 days old (needed 5 days)
• plakativ (0.5.2-1 to 0.5.2-3)
  • Migration status for plakativ (0.5.2-1 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 ♻ (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): plakativ pymupdf (not considered)
    • Depends: plakativ pymupdf (not considered)
  • Additional info:
    • Updating plakativ will fix bugs in testing: #1071861
    • 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 ♻
    • 17 days old (needed 5 days)
• recoll (1.36.1-1 to 1.39.0-1)
  • Migration status for recoll (1.36.1-1 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:
    • Updating recoll will fix bugs in testing: #1073334
    • 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 ♻
    • 17 days old (needed 10 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 ♻
    • 17 days old (needed 5 days)
• blender (- to 4.1.1+dfsg-3)
  • Migration status for blender (- to 4.1.1+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): blender openvdb (not considered)
    • Depends: blender openvdb (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): blender embree
    • Build-Depends(-Arch): blender opencolorio
    • Build-Depends(-Arch): blender openimageio
    • Depends: blender embree
    • Depends: blender opencolorio
    • Depends: blender openimageio
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/blender.html
    • Reproducible on amd64 - info ♻
    • 18 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 ♻
    • 18 days old (needed 5 days)
• intel-compute-runtime (- to 24.22.29735.21-1)
  • Migration status for intel-compute-runtime (- to 24.22.29735.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for intel-compute-runtime/24.22.29735.21-1: amd64: Regression or new test ♻
    • 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 ♻
    • 18 days old (needed 5 days)
• intel-graphics-compiler (- to 1.0.17193.2-1)
  • Migration status for intel-graphics-compiler (- to 1.0.17193.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-graphics-compiler would introduce bugs in testing: #1061213
    • Build-Depends(-Arch): intel-graphics-compiler intel-vc-intrinsics (not considered)
    • Build-Depends(-Arch): intel-graphics-compiler llvm-toolchain-14 (not considered)
    • Build-Depends(-Arch): intel-graphics-compiler opencl-clang-14
    • Build-Depends(-Arch): intel-graphics-compiler spirv-llvm-translator-14
    • Depends: intel-graphics-compiler llvm-toolchain-14 (not considered)
    • Depends: intel-graphics-compiler opencl-clang-14
    • Depends: intel-graphics-compiler spirv-llvm-translator-14
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-graphics-compiler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• mold (- to 2.32.1+dfsg-1)
  • Migration status for mold (- to 2.32.1+dfsg-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/mold.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 18 days old (needed 5 days)
• nabu (- to 2024.1.6-4)
  • Migration status for nabu (- to 2024.1.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nabu/2024.1.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 ♻
    • Build-Depends(-Arch): nabu tomoscan (not considered)
    • Depends: nabu tomoscan (not considered)
  • 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 ♻
    • 18 days old (needed 5 days)
• q2-dada2 (- to 2024.5.0-1)
  • Migration status for q2-dada2 (- to 2024.5.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): q2-dada2 r-bioc-dada2 (not considered)
    • Depends: q2-dada2 r-bioc-dada2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-dada2.html
    • autopkgtest for q2-dada2/2024.5.0-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
    • 18 days old (needed 2 days)
• slapi-nis (- to 0.60.0-1.1)
  • Migration status for slapi-nis (- to 0.60.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): slapi-nis sssd (not considered)
    • Depends: slapi-nis sssd (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slapi-nis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• translate-toolkit (3.13.0-2 to 3.13.1-1)
  • Migration status for translate-toolkit (3.13.0-2 to 3.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for translate-toolkit/3.13.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 ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/translate-toolkit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 18 days old (needed 5 days)
• chromium (125.0.6422.60-1 to 126.0.6478.126-1)
  • Migration status for chromium (125.0.6422.60-1 to 126.0.6478.126-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:
    • Updating chromium will fix bugs in testing: #1074153
    • 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
    • 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 ♻
    • 19 days old (needed 2 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 ♻
    • 19 days old (needed 5 days)
• r-cran-xslt (1.4.4-1 to 1.4.5-1)
  • Migration status for r-cran-xslt (1.4.4-1 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 ♻ (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 r-cran-xslt will fix bugs in testing: #1073338
    • 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 ♻
    • 19 days old (needed 5 days)
• fakeroot (1.33-1 to 1.35.1-1)
  • Migration status for fakeroot (1.33-1 to 1.35.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fakeroot would introduce bugs in testing: #1065552
    • 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 fakeroot/1.35.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating fakeroot will fix bugs in testing: #1071409
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fakeroot.html
    • Reproducible on i386 - info ♻
    • 20 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 ♻
    • 20 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 tomoscan (not considered)
    • Depends: pynx tomoscan (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): pynx nabu (not considered)
    • Build-Depends(-Arch): pynx numba (not considered)
    • Build-Depends(-Arch): pynx pyvkfft/mips64el
    • Depends: pynx pyvkfft/mips64el
  • 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
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 20 days old (needed 5 days)
• r-cran-collapse (2.0.13-1 to 2.0.14-1)
  • Migration status for r-cran-collapse (2.0.13-1 to 2.0.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-collapse/2.0.14-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-collapse.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 20 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 ♻
    • 20 days old (needed 10 days)
• spirv-llvm-translator-18 (- to 18.1.1-1)
  • Migration status for spirv-llvm-translator-18 (- to 18.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for spirv-llvm-translator-18/18.1.1-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): spirv-llvm-translator-18 llvm-toolchain-18 (not considered)
    • Depends: spirv-llvm-translator-18 llvm-toolchain-18 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spirv-llvm-translator-18.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 21 days old (needed 5 days)
• libhdr-histogram (0.11.8-1 to 0.11.8-4)
  • Migration status for libhdr-histogram (0.11.8-1 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 ♻
    • 22 days old (needed 5 days)
• bpftrace (0.20.2-1 to 0.21.0-1)
  • Migration status for bpftrace (0.20.2-1 to 0.21.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bpftrace.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 23 days old (needed 5 days)
• golang-github-cloudflare-backoff (- to 0.0~git20161212.647f3cd-1)
  • Migration status for golang-github-cloudflare-backoff (- to 0.0~git20161212.647f3cd-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by siretart, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-cloudflare-backoff.html
    • autopkgtest for golang-github-cloudflare-backoff/0.0~git20161212.647f3cd-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
    • 23 days old (needed 2 days)
• golang-github-containerd-log (- to 0.1.0-1)
  • Migration status for golang-github-containerd-log (- to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by siretart, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-containerd-log.html
    • autopkgtest for golang-github-containerd-log/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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• openvas-scanner (- to 23.4.1-1)
  • Migration status for openvas-scanner (- to 23.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): openvas-scanner gvm-libs (not considered)
    • Depends: openvas-scanner gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openvas-scanner.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 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
    • 23 days old (needed 2 days)
• python-qwt (0.12.1-1 to 0.12.5-1)
  • Migration status for python-qwt (0.12.1-1 to 0.12.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-qwt/0.12.5-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-qwt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 23 days old (needed 5 days)
• rust-gix (- to 0.62.0-1)
  • Migration status for rust-gix (- to 0.62.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-gix rust-gix-status (not considered)
    • Depends: rust-gix rust-gix-status (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-gix rust-gix-archive (not considered)
    • Build-Depends(-Arch): rust-gix rust-gix-config (not considered)
    • Build-Depends(-Arch): rust-gix rust-gix-dir (not considered)
    • Build-Depends(-Arch): rust-gix rust-gix-discover
    • Build-Depends(-Arch): rust-gix rust-gix-odb
    • Build-Depends(-Arch): rust-gix rust-gix-pack (not considered)
    • Build-Depends(-Arch): rust-gix rust-gix-ref (not considered)
    • Build-Depends(-Arch): rust-gix rust-gix-submodule
    • Depends: rust-gix rust-gix-archive (not considered)
    • Depends: rust-gix rust-gix-config (not considered)
    • Depends: rust-gix rust-gix-dir (not considered)
    • Depends: rust-gix rust-gix-discover
    • Depends: rust-gix rust-gix-odb
    • Depends: rust-gix rust-gix-pack (not considered)
    • Depends: rust-gix rust-gix-protocol (not considered)
    • Depends: rust-gix rust-gix-ref (not considered)
    • Depends: rust-gix rust-gix-submodule
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gix.html
    • autopkgtest for rust-gix/0.62.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
    • 23 days old (needed 2 days)
• sight (- to 23.1.0-3)
  • Migration status for sight (- to 23.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sight would introduce bugs in testing: #1075792
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sight.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 ♻
    • 23 days old (needed 5 days)
• bcachefs-tools (- to 1:1.9.1-1)
  • Migration status for bcachefs-tools (- to 1:1.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bcachefs-tools would introduce bugs in testing: #1074797
    • 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/b/bcachefs-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 24 days old (needed 5 days)
• dask.distributed (2023.12.1+ds-4 to 2024.5.2+ds.1-2)
  • Migration status for dask.distributed (2023.12.1+ds-4 to 2024.5.2+ds.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dask.distributed/2024.5.2+ds.1-2: amd64: Regression or new test ♻ (reference ♻), arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Pass, riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating dask.distributed will fix bugs in testing: #1066799
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dask.distributed.html
    • 24 days old (needed 5 days)
• gaupol (1.14.1-1 to 1.15-1)
  • Migration status for gaupol (1.14.1-1 to 1.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for translate-toolkit/3.13.0-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gaupol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 days)
• gsad (- to 22.9.1-2)
  • Migration status for gsad (- to 22.9.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gsad gvm-libs (not considered)
    • Depends: gsad gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: gsad gvmd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsad.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 24 days old (needed 5 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 ♻
    • 24 days old (needed 5 days)
• nova (- to 2:29.0.2-2)
  • Migration status for nova (- to 2:29.0.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: nova websockify (not considered)
    • Depends: nova websockify (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Depends: nova novnc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nova.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 nova/2:29.0.2-2: amd64: Pass, arm64: Pass, ppc64el: Pass, 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 ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 24 days old (needed 5 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
    • 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 ♻
    • 25 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
    • 25 days old (needed 7 days)
• neutron (2:24.0.0-2 to 2:24.0.0-3)
  • Migration status for neutron (2:24.0.0-2 to 2:24.0.0-3): 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/n/neutron.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 ♻
    • 25 days old (needed 5 days)
• opencryptoki (3.8.1+dfsg-3.2 to 3.23.0+dfsg-0.2)
  • Migration status for opencryptoki (3.8.1+dfsg-3.2 to 3.23.0+dfsg-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/opencryptoki.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• safeeyes (2.1.5-0.1 to 2.1.9-1)
  • Migration status for safeeyes (2.1.5-0.1 to 2.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/safeeyes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 25 days old (needed 5 days)
• gvm-libs (- to 22.10.0-1)
  • Migration status for gvm-libs (- to 22.10.0-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 ♻
    • 26 days old (needed 5 days)
• gvmd (- to 23.6.2-1)
  • Migration status for gvmd (- to 23.6.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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.6.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 26 days old (needed 2 days)
• ispc (1.23.0-1 to 1.24.0-1)
  • Migration status for ispc (1.23.0-1 to 1.24.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libispcrt-dev/armhf has unsatisfiable dependency
    • autopkgtest for ispc/1.24.0-1: amd64: Pass, arm64: Pass, i386: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ispc.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 ♻
    • 26 days old (needed 5 days)
• rust-cargo-credential-libsecret (- to 0.4.1-1)
  • Migration status for rust-cargo-credential-libsecret (- to 0.4.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-cargo-credential-libsecret rust-cargo-credential (not considered)
    • Depends: rust-cargo-credential-libsecret rust-cargo-credential (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-credential-libsecret.html
    • autopkgtest for rust-cargo-credential-libsecret/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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 26 days old (needed 2 days)
• importlib-resources (6.0.1-1 to 6.4.0-1)
  • Migration status for importlib-resources (6.0.1-1 to 6.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for importlib-resources/6.4.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/i/importlib-resources.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 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 ♻
    • 27 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: #1058640, #1074330, #1076245
    • lintian-brush unsatisfiable Build-Depends(-Arch) on amd64: librust-breezyshim-dev (>= 0.1.101)
    • lintian-brush unsatisfiable Build-Depends(-Arch) on arm64: librust-breezyshim-dev (>= 0.1.101)
    • lintian-brush unsatisfiable Build-Depends(-Arch) on armel: librust-breezyshim-dev (>= 0.1.101)
    • lintian-brush unsatisfiable Build-Depends(-Arch) on armhf: librust-breezyshim-dev (>= 0.1.101)
    • lintian-brush unsatisfiable Build-Depends(-Arch) on i386: librust-breezyshim-dev (>= 0.1.101)
    • lintian-brush unsatisfiable Build-Depends(-Arch) on mips64el: librust-breezyshim-dev (>= 0.1.101)
    • lintian-brush unsatisfiable Build-Depends(-Arch) on ppc64el: librust-breezyshim-dev (>= 0.1.101)
    • lintian-brush unsatisfiable Build-Depends(-Arch) on riscv64: librust-breezyshim-dev (>= 0.1.101)
    • lintian-brush unsatisfiable Build-Depends(-Arch) on s390x: librust-breezyshim-dev (>= 0.1.101)
    • 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lintian-brush.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 ♻
    • 27 days old (needed 5 days)
• obs-time-source (- to 0.2-5)
  • Migration status for obs-time-source (- to 0.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • obs-time-source unsatisfiable Build-Depends(-Arch) on ppc64el: libobs-dev
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for obs-time-source/0.2-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-time-source.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 days old (needed 5 days)
• openimageio (- to 2.5.12.0+dfsg-2)
  • Migration status for openimageio (- to 2.5.12.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): 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 ♻
    • 27 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
    • 27 days old (needed 2 days)
• snapd (2.62-5 to 2.63-3)
  • Migration status for snapd (2.62-5 to 2.63-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for snapd/2.63-3: 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: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snapd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 days old (needed 5 days)
• spirv-llvm-translator-14 (- to 14.0.1-2)
  • Migration status for spirv-llvm-translator-14 (- to 14.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): spirv-llvm-translator-14 llvm-toolchain-14 (not considered)
    • Depends: spirv-llvm-translator-14 llvm-toolchain-14 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spirv-llvm-translator-14.html
    • autopkgtest for spirv-llvm-translator-14/14.0.1-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 27 days old (needed 5 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 ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 28 days old (needed 10 days)
• developers-reference (13.6 to 13.7)
  • Migration status for developers-reference (13.6 to 13.7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for developers-reference/13.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: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/developers-reference.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• dput (1.1.3 to 1.2.1)
  • Migration status for dput (1.1.3 to 1.2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ben@benfinney.id.au, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating dput will fix bugs in testing: #1076298
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dput.html
    • autopkgtest for dput/1.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• git (1:2.43.0-1 to 1:2.45.2-1)
  • Migration status for git (1:2.43.0-1 to 1:2.45.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ikiwiki-hosting/0.20220716-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating git will fix bugs in testing: #1071160, #1074064
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 10 days)
• node-websocket (1.0.34+~cs10.0.25-2 to 1.0.35+~cs11.0.28-1)
  • Migration status for node-websocket (1.0.34+~cs10.0.25-2 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 ♻
    • 28 days old (needed 5 days)
• php-deepcopy (1.11.1-2 to 1.12.0-1)
  • Migration status for php-deepcopy (1.11.1-2 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-deepcopy.html
    • autopkgtest for php-deepcopy/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
    • 28 days old (needed 2 days)
• r-cran-effectsize (- to 0.8.8+dfsg-1)
  • Migration status for r-cran-effectsize (- to 0.8.8+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.8+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
    • 28 days old (needed 2 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
    • 28 days old (needed 2 days)
• rust-sequoia-ipc (0.34.1-1 to 0.35.0-1)
  • Migration status for rust-sequoia-ipc (0.34.1-1 to 0.35.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-sequoia-ipc-dev/0.35.0-1/amd64 to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/amd64 uninstallable
    • migrating librust-sequoia-ipc-dev/0.35.0-1/arm64 to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/arm64 uninstallable
    • migrating librust-sequoia-ipc-dev/0.35.0-1/armel to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/armel uninstallable
    • migrating librust-sequoia-ipc-dev/0.35.0-1/armhf to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/armhf uninstallable
    • migrating librust-sequoia-ipc-dev/0.35.0-1/i386 to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/i386 uninstallable
    • migrating librust-sequoia-ipc-dev/0.35.0-1/mips64el to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/mips64el uninstallable
    • migrating librust-sequoia-ipc-dev/0.35.0-1/ppc64el to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/ppc64el uninstallable
    • migrating librust-sequoia-ipc-dev/0.35.0-1/s390x to testing makes librust-sequoia-keystore-dev/0.2.0-1+b1/s390x uninstallable
    • autopkgtest for rust-sequoia-gpg-agent/0.4.2-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for rust-sequoia-ipc/0.35.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Implicit dependency: rust-sequoia-ipc rust-sequoia-gpg-agent (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-ipc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 28 days old (needed 5 days)
• libpam-ssh (- to 2.3+ds-6.1)
  • Migration status for libpam-ssh (- to 2.3+ds-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpam-ssh would introduce bugs in testing: #994992
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpam-ssh.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 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-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: 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:
    • 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 ♻
    • 29 days old (needed 5 days)
• obs-advanced-scene-switcher (- to 1.26.4-1)
  • Migration status for obs-advanced-scene-switcher (- to 1.26.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating obs-advanced-scene-switcher would introduce bugs in testing: #1068414
    • obs-advanced-scene-switcher unsatisfiable Build-Depends(-Arch) on ppc64el: libobs-dev (>= 26.1.2)
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for obs-advanced-scene-switcher/1.26.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 ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-advanced-scene-switcher.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• soundcraft-utils (- to 0.4.0-2)
  • Migration status for soundcraft-utils (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tiago, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/soundcraft-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 29 days old (needed 5 days)
• datalad (- to 1.1.0-1)
  • Migration status for datalad (- to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating datalad would introduce bugs in testing: #1067782
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/datalad.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 ♻
    • 30 days old (needed 5 days)
• kamailio (- to 5.8.2-2)
  • Migration status for kamailio (- to 5.8.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kamailio would introduce bugs in testing: #1075961
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kamailio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• python-django-structlog (- to 8.1.0-1)
  • Migration status for python-django-structlog (- to 8.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-structlog.html
    • autopkgtest for python-django-structlog/8.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
    • 30 days old (needed 7 days)
• rust-gix-archive (- to 0.12.0-1)
  • Migration status for rust-gix-archive (- to 0.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gix-archive/0.12.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: 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-gix-archive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• rust-gix-config (- to 0.36.1-1)
  • Migration status for rust-gix-config (- to 0.36.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gix-config/0.36.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: 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-gix-config rust-gix-ref (not considered)
    • Depends: rust-gix-config rust-gix-ref (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gix-config.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• rust-gix-discover (- to 0.31.0-1)
  • Migration status for rust-gix-discover (- to 0.31.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-gix-discover rust-gix-ref (not considered)
    • Depends: rust-gix-discover rust-gix-ref (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gix-discover.html
    • autopkgtest for rust-gix-discover/0.31.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 ♻
    • 30 days old (needed 5 days)
• rust-gix-odb (- to 0.60.0-1)
  • Migration status for rust-gix-odb (- to 0.60.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-gix-odb rust-gix-pack (not considered)
    • Depends: rust-gix-odb rust-gix-pack (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gix-odb.html
    • autopkgtest for rust-gix-odb/0.60.0-1: amd64: No tests, superficial or marked flaky ♻, 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 ♻
    • 30 days old (needed 5 days)
• rust-gix-pack (- to 0.50.0-1)
  • Migration status for rust-gix-pack (- to 0.50.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gix-pack/0.50.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: 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-gix-pack.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 ♻
    • 30 days old (needed 5 days)
• rust-gix-protocol (- to 0.45.1-1)
  • Migration status for rust-gix-protocol (- to 0.45.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gix-protocol/0.45.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-gix-protocol.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• rust-gix-ref (- to 0.43.0-1)
  • Migration status for rust-gix-ref (- to 0.43.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gix-ref/0.43.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: 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-gix-ref.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• rust-gix-submodule (- to 0.10.0-1)
  • Migration status for rust-gix-submodule (- 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): rust-gix-submodule rust-gix-config (not considered)
    • Depends: rust-gix-submodule rust-gix-config (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gix-submodule.html
    • autopkgtest for rust-gix-submodule/0.10.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 30 days old (needed 5 days)
• silver-platter (- to 0.5.23-1)
  • Migration status for silver-platter (- to 0.5.23-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): silver-platter lintian-brush (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/silver-platter.html
    • autopkgtest for silver-platter/0.5.23-1: amd64: Pass, i386: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 30 days old (needed 2 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: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hilive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 31 days old (needed 5 days)
• grub-customizer (- to 5.2.5-1)
  • Migration status for grub-customizer (- to 5.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: grub-customizer hwinfo (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grub-customizer.html
    • autopkgtest for grub-customizer/5.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 ♻
    • 32 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
    • 32 days old (needed 2 days)
• pagure (- to 5.11.3+dfsg-3)
  • Migration status for pagure (- to 5.11.3+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pagure trololio (not considered)
    • Invalidated by dependency
  • 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 ♻
    • 32 days old (needed 5 days)
• python-urllib3 (1.26.18-2 to 2.0.7-2)
  • Migration status for python-urllib3 (1.26.18-2 to 2.0.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-urllib3 would introduce bugs in testing: #1073396
    • autopkgtest for azure-cli/2.61.0-1: s390x: Pass
    • autopkgtest for python-requests-cache/0.9.8-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-urllib3/2.0.7-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/p/python-urllib3.html
    • Reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• r-cran-performance (- to 0.12.0-1)
  • Migration status for r-cran-performance (- to 0.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-performance would introduce bugs in testing: #1071104
    • autopkgtest for r-cran-performance/0.12.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• requests (2.31.0+dfsg-2 to 2.32.3+dfsg-1)
  • Migration status for requests (2.31.0+dfsg-2 to 2.32.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for azure-cli/2.61.0-1: s390x: Pass
    • autopkgtest for glance/2:28.0.1-3+deb12u1: s390x: Pass
    • autopkgtest for python-azure/20240522+git-2: s390x: No tests, superficial or marked flaky
    • autopkgtest for python-requests-cache/0.9.8-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-requests-unixsocket/0.3.0-4: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for python-truststore/0.9.1-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for requests/2.32.3+dfsg-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/requests.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 32 days old (needed 5 days)
• dahdi-linux (- to 1:3.1.0+git20230717~dfsg-5.1)
  • Migration status for dahdi-linux (- to 1:3.1.0+git20230717~dfsg-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dahdi-linux would introduce bugs in testing: #1071575
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/dahdi-linux.html
    • autopkgtest for dahdi-linux/1:3.1.0+git20230717~dfsg-5.1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 33 days old (needed 5 days)
• oddjob (- to 0.34.7-2.1)
  • Migration status for oddjob (- to 0.34.7-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oddjob would introduce bugs in testing: #1060605
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oddjob.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 33 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 ♻
    • 33 days old (needed 5 days)
• rust-ripasso-cursive (- to 0.6.5-3)
  • Migration status for rust-ripasso-cursive (- to 0.6.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-ripasso-cursive rust-ripasso (not considered)
    • Built-Using: rust-ripasso-cursive rust-ripasso (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ripasso-cursive.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 ♻
    • 33 days old (needed 5 days)
• flake8-pytest (- to 1.4-1)
  • Migration status for flake8-pytest (- to 1.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/f/flake8-pytest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 34 days old (needed 5 days)
• freezegun (1.2.1+actually1.2.1-1 to 1.5.1-1)
  • Migration status for freezegun (1.2.1+actually1.2.1-1 to 1.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by federico.ceratto@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating freezegun will fix bugs in testing: #1076301
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freezegun.html
    • autopkgtest for freezegun/1.5.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 34 days old (needed 2 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:
    • 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 ♻
    • 34 days old (needed 10 days)
• mako (1.3.2-1 to 1.3.5-1)
  • Migration status for mako (1.3.2-1 to 1.3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by piotr, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating mako will fix bugs in testing: #1076304
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mako.html
    • autopkgtest for mako/1.3.5-1: 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
    • 34 days old (needed 2 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 ♻
    • 34 days old (needed 5 days)
• rust-rustls (0.21.10-1 to 0.21.12-1)
  • Migration status for rust-rustls (0.21.10-1 to 0.21.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-rustls/0.21.12-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating rust-rustls will fix bugs in testing: #1069677, #1076302
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustls.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 34 days old (needed 5 days)
• rust-sequoia-chameleon-gnupg (0.8.0-5 to 0.9.0-1)
  • Migration status for rust-sequoia-chameleon-gnupg (0.8.0-5 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-sequoia-chameleon-gnupg would introduce bugs in testing: #1073272, #1074652
    • rust-sequoia-chameleon-gnupg unsatisfiable Build-Depends(-Arch) on riscv64: librust-sequoia-cert-store-0.5+default-dev
    • rust-sequoia-chameleon-gnupg unsatisfiable Build-Depends(-Arch) on riscv64: librust-sequoia-gpg-agent-0.3+default-dev
    • rust-sequoia-chameleon-gnupg unsatisfiable Build-Depends(-Arch) on riscv64: librust-sequoia-ipc-0.34+default-dev
    • rust-sequoia-chameleon-gnupg unsatisfiable Build-Depends(-Arch) on riscv64: librust-sequoia-wot-0.11+default-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-chameleon-gnupg.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 34 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: 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): 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 ♻
    • 34 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: 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/w/web-cache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 34 days old (needed 5 days)
• gcc-defaults-mipsen (1.203 to 1.213)
  • Migration status for gcc-defaults-mipsen (1.203 to 1.213): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gcc-defaults-mipsen gcc-13-cross-mipsen (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-defaults-mipsen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 35 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gmemusage.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 35 days old (needed 5 days)
• jupyterhub (- to 5.0.0+ds1-1)
  • Migration status for jupyterhub (- to 5.0.0+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jupyterhub would introduce bugs in testing: #1071982, #1072938
    • jupyterhub unsatisfiable Build-Depends(-Arch) on amd64: python3-pydantic (>= 2)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyterhub.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 ♻
    • 35 days old (needed 5 days)
• obs-source-copy (- to 0.2.4-1)
  • Migration status for obs-source-copy (- to 0.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating obs-source-copy would introduce bugs in testing: #1071017
    • obs-source-copy unsatisfiable Build-Depends(-Arch) on ppc64el: libobs-dev (>= 29)
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for obs-source-copy/0.2.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 ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-source-copy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 35 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:
    • 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 ♻
    • 35 days old (needed 5 days)
• python-anyio (4.3.0-1 to 4.4.0-1)
  • Migration status for python-anyio (4.3.0-1 to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-anyio/4.4.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for starlette/0.37.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:
    • Updating python-anyio will fix bugs in testing: #1076297
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-anyio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 36 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-frameworks-base (not considered)
    • Invalidated by dependency
    • Depends: android-sdk-meta android-platform-art (not considered)
    • Depends: android-sdk-meta android-platform-build (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
    • 37 days old (needed 2 days)
• ognibuild (- to 0.0.20-1)
  • Migration status for ognibuild (- to 0.0.20-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ognibuild rust-axum (not considered)
    • Invalidated by build-dependency
    • 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 amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• rust-minijinja (- to 1.0.3-1)
  • Migration status for rust-minijinja (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-minijinja/1.0.3-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/rust-minijinja.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 37 days old (needed 5 days)
• tailspin (- to 3.0.1+dfsg-1)
  • Migration status for tailspin (- to 3.0.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tailspin would introduce bugs in testing: #1075912
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tailspin.html
    • 37 days old (needed 5 days)
• virtualbox (- to 7.0.18-dfsg-2)
  • Migration status for virtualbox (- to 7.0.18-dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtualbox would introduce bugs in testing: #794466
    • autopkgtest for virtualbox/7.0.18-dfsg-2: amd64: No tests, superficial or marked flaky ♻, i386: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 37 days old (needed 5 days)
• asterisk (- to 1:20.8.1~dfsg+~cs6.14.40431414-1)
  • Migration status for asterisk (- to 1:20.8.1~dfsg+~cs6.14.40431414-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
    • Build-Depends(-Arch): asterisk libss7 (not considered)
    • Build-Depends(-Arch): asterisk openr2
    • Depends: asterisk dahdi-tools
    • Depends: asterisk libss7 (not considered)
    • Depends: asterisk openr2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk.html
    • autopkgtest for asterisk/1:20.8.1~dfsg+~cs6.14.40431414-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 ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 38 days old (needed 2 days)
• gcc-13-cross-mipsen (2+c1 to 3+c1)
  • Migration status for gcc-13-cross-mipsen (2+c1 to 3+c1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by wzssyqa@gmail.com
    • Not built on buildd: arch all binaries uploaded by wzssyqa@gmail.com, a new source-only upload is needed to allow migration
    • Depends: gcc-13-cross-mipsen gcc-14-cross-mipsen (not considered)
  • Additional info:
    • Updating gcc-13-cross-mipsen will fix bugs in testing: #1075974
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-13-cross-mipsen.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 38 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 ♻
    • Built-Using: gcc-sh-elf gcc-13 (not considered)
  • 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 ♻
    • 38 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 ♻
    • 38 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
    • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 38 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 ♻
    • 39 days old (needed 5 days)
• ipywidgets (8.1.1-2 to 8.1.3-1)
  • Migration status for ipywidgets (8.1.1-2 to 8.1.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Updating ipywidgets will fix bugs in testing: #1063908
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/i/ipywidgets.html
    • autopkgtest for ipywidgets/8.1.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 39 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 ♻
    • 39 days old (needed 5 days)
• slime (2:2.28+dfsg-1 to 2:2.30+dfsg-1)
  • Migration status for slime (2:2.28+dfsg-1 to 2:2.30+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for slime/2:2.30+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 slime will fix bugs in testing: #1076296
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slime.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • Ignoring non-reproducibility on armhf (not a regression) - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 39 days old (needed 5 days)
• strace (6.5-0.1 to 6.8-2)
  • Migration status for strace (6.5-0.1 to 6.8-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Updating strace will fix bugs in testing: #1060789, #1068758, #1073223
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/strace.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 39 days old (needed 5 days)
• cyrus-imapd (- to 3.8.3-1)
  • Migration status for cyrus-imapd (- to 3.8.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cyrus-imapd would introduce bugs in testing: #1068223, #1075853
    • autopkgtest for cyrus-imapd/3.8.3-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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cyrus-imapd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 40 days old (needed 5 days)
• libfishcamp (1.2+20220607003151-1 to 1.2+20220607003151-2)
  • Migration status for libfishcamp (1.2+20220607003151-1 to 1.2+20220607003151-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libfishcamp would introduce bugs in testing: #1072730, #1072731
  • Additional info:
    • Updating libfishcamp will fix bugs in testing: #1076295
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 40 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 ♻
    • 40 days old (needed 5 days)
• sssd (- to 2.9.5-3)
  • Migration status for sssd (- to 2.9.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sssd uid-wrapper (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sssd.html
    • autopkgtest for sssd/2.9.5-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
    • 40 days old (needed 2 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 ♻
    • 41 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 ♻
    • 41 days old (needed 5 days)
• r-cran-stars (- to 0.6-5-1)
  • Migration status for r-cran-stars (- to 0.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): 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-5-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 ♻
    • 41 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
    • autopkgtest for libxml2/2.12.7+dfsg-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for mariadb/1:11.4.2-4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for ruby-libxml/3.2.4-2: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
    • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 42 days old (needed 5 days)
• powder (118+dfsg1-3 to 118+dfsg1-4)
  • Migration status for powder (118+dfsg1-3 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:
    • Updating powder will fix bugs in testing: #1075774
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 42 days old (needed 5 days)
• display-mail-user-agent (- to 2.9.13+dfsg-1)
  • Migration status for display-mail-user-agent (- to 2.9.13+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ooo@mechtilde.de, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/display-mail-user-agent.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 43 days old (needed 5 days)
• gcc-14-cross-mipsen (- to 1+c1)
  • Migration status for gcc-14-cross-mipsen (- to 1+c1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch amd64 binaries uploaded by wzssyqa@gmail.com
    • Not built on buildd: arch all binaries uploaded by wzssyqa@gmail.com, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): gcc-14-cross-mipsen gcc-14 (not considered)
    • Built-Using: gcc-14-cross-mipsen gcc-14 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-14-cross-mipsen.html
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 43 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 ♻
    • 43 days old (needed 5 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
    • 44 days old (needed 2 days)
• sbcl (2:2.3.7-2 to 2:2.4.5-1)
  • Migration status for sbcl (2:2.3.7-2 to 2:2.4.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cl-portable-aserve/20190720.gitcac1d69+dfsg-4: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for cl-postmodern/20211113.git9d4332f-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for sbcl/2:2.4.5-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed (not a regression)
    • 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 sbcl will fix bugs in testing: #1075754
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbcl.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 44 days old (needed 5 days)
• slurm-wlm-contrib (- to 23.11.7-2)
  • Migration status for slurm-wlm-contrib (- to 23.11.7-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 45 days old (needed 5 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 ♻
    • 45 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:
    • Piuparts tested OK - 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 ♻
    • 46 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 ♻
    • 47 days old (needed 5 days)
• libmodule-faker-perl (0.025-1 to 0.027-1)
  • Migration status for libmodule-faker-perl (0.025-1 to 0.027-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: libmodule-faker-perl libdata-fake-perl (not considered)
    • Depends: libmodule-faker-perl libdata-fake-perl (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Updating libmodule-faker-perl will fix bugs in testing: #1073225
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmodule-faker-perl.html
    • autopkgtest for libmodule-faker-perl/0.027-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
    • 47 days old (needed 2 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
    • 47 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 ♻
    • 48 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
    • Depends: meta-plasma-mobile iio-sensor-proxy
  • 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 ♻
    • 48 days old (needed 5 days)
• reform-setup-wizard (- to 1.0-7)
  • Migration status for reform-setup-wizard (- to 1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for reform-setup-wizard/1.0-7: 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/r/reform-setup-wizard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 48 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:
    • autopkgtest for mu-editor/1.0.3+dfsg-6.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: mu-editor python-guizero (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mu-editor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 49 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 ♻
    • 49 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
    • 50 days old (needed 2 days)
• packagesearch (- to 2.8.2)
  • Migration status for packagesearch (- to 2.8.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • packagesearch/amd64 has unsatisfiable dependency
    • packagesearch/arm64 has unsatisfiable dependency
    • packagesearch/armel has unsatisfiable dependency
    • packagesearch/armhf has unsatisfiable dependency
    • packagesearch/i386 has unsatisfiable dependency
    • packagesearch/mips64el has unsatisfiable dependency
    • packagesearch/ppc64el has unsatisfiable dependency
    • packagesearch/s390x has unsatisfiable dependency
    • Updating packagesearch would introduce bugs in testing: #1072806
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/packagesearch.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 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 ♻
    • 50 days old (needed 5 days)
• ripe-atlas-tools (- to 2.3.0-3)
  • Migration status for ripe-atlas-tools (- to 2.3.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ripe-atlas-tools ripe-atlas-sagan (not considered)
    • Depends: ripe-atlas-tools ripe-atlas-sagan (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ripe-atlas-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 50 days old (needed 5 days)
• sepp (- to 4.5.1+really4.5.1+dfsg-6)
  • Migration status for sepp (- to 4.5.1+really4.5.1+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sepp pplacer (not considered)
    • Depends: sepp pplacer (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sepp.html
    • autopkgtest for sepp/4.5.1+really4.5.1+dfsg-6: 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
    • 50 days old (needed 2 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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 50 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
    • 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
    • autopkgtest for falcosecurity-libs/0.15.1-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/falcosecurity-libs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 51 days old (needed 5 days)
• obs-transition-table (- to 0.2.7-2)
  • Migration status for obs-transition-table (- to 0.2.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • obs-transition-table unsatisfiable Build-Depends(-Arch) on ppc64el: libobs-dev (>= 29)
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for obs-transition-table/0.2.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 ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-transition-table.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 52 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:
    • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 52 days old (needed 5 days)
• resampy (- to 0.4.3+ds-3)
  • Migration status for resampy (- to 0.4.3+ds-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): resampy numba (not considered)
    • Depends: resampy numba (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • 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
    • Reproducible on arm64 - info ♻
    • 52 days old (needed 5 days)
• ktextaddons (1.5.2-2.1 to 1.5.4-2)
  • Migration status for ktextaddons (1.5.2-2.1 to 1.5.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ktextaddons has no binaries on any arch
    • Updating ktextaddons would introduce bugs in testing: #1073394
    • ktextaddons unsatisfiable Build-Depends(-Arch) on amd64: libkf6archive-dev (>= 6.0.0~)
    • ktextaddons unsatisfiable Build-Depends(-Arch) on amd64: libkf6configwidgets-dev (>= 6.0.0~)
    • ktextaddons unsatisfiable Build-Depends(-Arch) on amd64: libkf6coreaddons-dev (>= 6.0.0~)
    • ktextaddons unsatisfiable Build-Depends(-Arch) on amd64: libkf6i18n-dev (>= 6.0.0~)
    • ktextaddons unsatisfiable Build-Depends(-Arch) on amd64: libkf6kio-dev (>= 6.0.0~)
    • ktextaddons unsatisfiable Build-Depends(-Arch) on amd64: libkf6sonnet-dev (>= 6.0.0~)
    • ktextaddons unsatisfiable Build-Depends(-Arch) on amd64: libkf6syntaxhighlighting-dev (>= 6.0.0~)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Updating ktextaddons will fix bugs in testing: #1074155
    • 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 ♻
    • 53 days old (needed 5 days)
• slurm-wlm (23.11.4-2 to 23.11.7-1)
  • Migration status for slurm-wlm (23.11.4-2 to 23.11.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • slurm-wlm-basic-plugins/armel has unsatisfiable dependency
    • slurm-wlm-basic-plugins/armhf has unsatisfiable dependency
    • slurm-wlm-basic-plugins/i386 has unsatisfiable dependency
    • Updating slurm-wlm would introduce bugs in testing: #1074384
    • autopkgtest for slurm-wlm/23.11.7-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating slurm-wlm will fix bugs in testing: #1070898, #1073224
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slurm-wlm.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 amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 53 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 ♻
    • Build-Depends(-Arch): datalad-next datalad (not considered)
    • Depends: datalad-next datalad (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/datalad-next.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 54 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-460 (- to 460.106.00-15)
  • Migration status for nvidia-graphics-drivers-tesla-460 (- to 460.106.00-15): 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-15: 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 ♻
    • 54 days old (needed 5 days)
• quickml (0.8-1 to 0.8-2)
  • Migration status for quickml (0.8-1 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:
    • Updating quickml will fix bugs in testing: #1074152
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quickml.html
    • 54 days old (needed 5 days)
• rust-octocrab (- to 0.31.2-2)
  • Migration status for rust-octocrab (- to 0.31.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-octocrab rust-hyper-timeout (not considered)
    • Depends: rust-octocrab rust-hyper-timeout (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-octocrab.html
    • autopkgtest for rust-octocrab/0.31.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 ♻
    • 54 days old (needed 5 days)
• node-nock (13.3.3-1 to 13.5.4-1)
  • Migration status for node-nock (13.3.3-1 to 13.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-nock/13.5.4-1: amd64: Regression or new test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻), armel: Regression or new test ♻ (reference ♻), armhf: Regression or new test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻), ppc64el: Regression or new test ♻ (reference ♻), riscv64: Failed (not a regression), s390x: Regression or new test ♻ (reference ♻)
  • Additional info:
    • Updating node-nock will fix bugs in testing: #1074062
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-nock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 55 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-418 (- to 418.226.00-14)
  • Migration status for nvidia-graphics-drivers-tesla-418 (- to 418.226.00-14): 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
    • autopkgtest for nvidia-graphics-drivers-tesla-418/418.226.00-14: i386: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 55 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-450 (- to 450.248.02-5)
  • Migration status for nvidia-graphics-drivers-tesla-450 (- to 450.248.02-5): 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-5: 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 ♻
    • 55 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.random (not considered)
    • Depends: r-cran-spatstat r-cran-spatstat.random (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-spatstat r-cran-spatstat.explore (not considered)
    • Build-Depends(-Arch): r-cran-spatstat r-cran-spatstat.linnet (not considered)
    • Build-Depends(-Arch): r-cran-spatstat r-cran-spatstat.model (not considered)
    • Depends: r-cran-spatstat r-cran-spatstat.explore (not considered)
    • Depends: r-cran-spatstat r-cran-spatstat.linnet (not considered)
    • Depends: r-cran-spatstat r-cran-spatstat.model (not considered)
  • 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
    • 55 days old (needed 2 days)
• nvidia-graphics-drivers-legacy-390xx (- to 390.157-7)
  • Migration status for nvidia-graphics-drivers-legacy-390xx (- to 390.157-7): 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-7: amd64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • 56 days old (needed 5 days)
• r-cran-spatstat.explore (- to 3.2-7-1)
  • Migration status for r-cran-spatstat.explore (- to 3.2-7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-spatstat.explore/3.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: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): r-cran-spatstat.explore r-cran-spatstat.random (not considered)
    • Depends: r-cran-spatstat.explore r-cran-spatstat.random (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.explore.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 56 days old (needed 5 days)
• r-cran-spatstat.linnet (- to 3.1-5-1)
  • Migration status for r-cran-spatstat.linnet (- to 3.1-5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-spatstat.linnet/3.1-5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): r-cran-spatstat.linnet r-cran-spatstat.explore (not considered)
    • Build-Depends(-Arch): r-cran-spatstat.linnet r-cran-spatstat.model (not considered)
    • Build-Depends(-Arch): r-cran-spatstat.linnet r-cran-spatstat.random (not considered)
    • Depends: r-cran-spatstat.linnet r-cran-spatstat.explore (not considered)
    • Depends: r-cran-spatstat.linnet r-cran-spatstat.model (not considered)
    • Depends: r-cran-spatstat.linnet r-cran-spatstat.random (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.linnet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 56 days old (needed 5 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
    • autopkgtest for r-cran-spatstat.model/3.2-11-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): r-cran-spatstat.model r-cran-spatstat.explore (not considered)
    • Build-Depends(-Arch): r-cran-spatstat.model r-cran-spatstat.random (not considered)
    • Depends: r-cran-spatstat.model r-cran-spatstat.explore (not considered)
    • Depends: r-cran-spatstat.model r-cran-spatstat.random (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.model.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 56 days old (needed 5 days)
• r-cran-spatstat.random (- to 3.2-3-1)
  • Migration status for r-cran-spatstat.random (- to 3.2-3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-spatstat.random/3.2-3-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spatstat.random.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 56 days old (needed 5 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 ♻
    • 57 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
    • Build-Depends(-Arch): olive-editor opencolorio
    • Build-Depends(-Arch): olive-editor openimageio
  • Additional info:
    • Piuparts tested OK - 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
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 59 days old (needed 5 days)
• gcc-bpf (14 to 15)
  • Migration status for gcc-bpf (14 to 15): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-bpf gcc-14 (not considered)
    • Built-Using: gcc-bpf gcc-14 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
  • Additional info:
    • Updating gcc-bpf will fix bugs in testing: #1073517
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-bpf.html
    • autopkgtest for gcc-bpf/15: 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
    • 60 days old (needed 2 days)
• nbd (1:3.25-1 to 1:3.26.1-2)
  • Migration status for nbd (1:3.25-1 to 1:3.26.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nbd would introduce bugs in testing: #1066831
    • autopkgtest for nbd/1:3.26.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating nbd will fix bugs in testing: #1071070
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nbd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 61 days old (needed 5 days)
• pcp (- to 6.2.2-1)
  • Migration status for pcp (- to 6.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pcp/ppc64el has unsatisfiable dependency
    • Updating pcp would introduce bugs in testing: #1071103
    • pcp unsatisfiable Build-Depends(-Arch) on ppc64el: bpftrace (>= 0.9.2) [amd64 arm64 ppc64el]
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcp.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 61 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: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Pass
    • 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 ♻
    • 61 days old (needed 5 days)
• makedumpfile (- to 1:1.7.5-2)
  • Migration status for makedumpfile (- to 1:1.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for makedumpfile/1:1.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/m/makedumpfile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 62 days old (needed 5 days)
• mysql-8.0 (- to 8.0.37-1)
  • Migration status for mysql-8.0 (- to 8.0.37-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.37-1: amd64: Regression or new test ♻, arm64: Pass, 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
    • New but not reproducible on arm64 - info ♻
    • 62 days old (needed 5 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
    • 62 days old (needed 2 days)
• python-rosettasciio (- to 0.4-2)
  • Migration status for python-rosettasciio (- to 0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-rosettasciio/amd64 has unsatisfiable dependency
    • python3-rosettasciio/armhf has unsatisfiable dependency
    • python3-rosettasciio/mips64el has unsatisfiable dependency
    • python3-rosettasciio/ppc64el has unsatisfiable dependency
    • Updating python-rosettasciio would introduce bugs in testing: #1071880
    • Build-Depends(-Arch): python-rosettasciio python-sparse (not considered)
    • Build-Depends(-Arch): python-rosettasciio pyusid (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-rosettasciio.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • 62 days old (needed 5 days)
• amdgcn-tools-18 (- to 18.1)
  • Migration status for amdgcn-tools-18 (- to 18.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): amdgcn-tools-18 llvm-toolchain-18 (not considered)
    • Depends: amdgcn-tools-18 llvm-toolchain-18 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amdgcn-tools-18.html
    • Reproducible on amd64 - info ♻
    • 64 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 ♻
    • 64 days old (needed 5 days)
• cdlclient (- to 0.10.0-3)
  • Migration status for cdlclient (- to 0.10.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cdlclient/0.10.0-3: 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 ♻
    • 64 days old (needed 5 days)
• libdata-fake-perl (- to 0.006-2)
  • Migration status for libdata-fake-perl (- to 0.006-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libdata-fake-perl would introduce bugs in testing: #1071967
    • autopkgtest for libdata-fake-perl/0.006-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/libd/libdata-fake-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 64 days old (needed 5 days)
• python-calendra (- to 7.9.0-1)
  • Migration status for python-calendra (- to 7.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-calendra.html
    • Reproducible on armhf - info ♻
    • 64 days old (needed 5 days)
• pyusid (- to 0.0.12-2)
  • Migration status for pyusid (- to 0.0.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyusid would introduce bugs in testing: #1071881
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyusid.html
    • autopkgtest for pyusid/0.0.12-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 64 days old (needed 2 days)
• tomoscan (- to 2.0.5-1)
  • Migration status for tomoscan (- to 2.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for tomoscan/2.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomoscan.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 64 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
  • 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 ♻
    • 65 days old (needed 5 days)
• cinder (- to 2:24.0.0-3)
  • Migration status for cinder (- to 2:24.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cinder would introduce bugs in testing: #1074763
    • autopkgtest for cinder/2:24.0.0-3: 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 ♻
    • 66 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 ♻
    • 67 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 ♻
    • 68 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 ♻
    • 68 days old (needed 5 days)
• dico (- to 2.11-4.2)
  • Migration status for dico (- to 2.11-4.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): dico wordnet (not considered)
    • Depends: dico wordnet (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: dico wikitrans
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dico.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 69 days old (needed 5 days)
• jupyter-server-terminals (- to 0.5.3-2)
  • Migration status for jupyter-server-terminals (- to 0.5.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jupyter-server-terminals would introduce bugs in testing: #1071875
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Build-Depends(-Arch): jupyter-server-terminals pytest-jupyter (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyter-server-terminals.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 ♻
    • 69 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
    • autopkgtest for r-cran-sf/1.0-16+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 69 days old (needed 5 days)
• shim-helpers-amd64-signed (1+15.7+1 to 1+15.8+1)
  • Migration status for shim-helpers-amd64-signed (1+15.7+1 to 1+15.8+1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): shim-helpers-amd64-signed shim (not considered)
    • Built-Using: shim-helpers-amd64-signed shim (not considered)
    • Depends: shim-helpers-amd64-signed shim (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/shim-helpers-amd64-signed.html
    • Reproducible on amd64 - info ♻
    • 69 days old (needed 5 days)
• shim-helpers-arm64-signed (1+15.7+1 to 1+15.8+1)
  • Migration status for shim-helpers-arm64-signed (1+15.7+1 to 1+15.8+1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): shim-helpers-arm64-signed shim (not considered)
    • Built-Using: shim-helpers-arm64-signed shim (not considered)
    • Depends: shim-helpers-arm64-signed shim (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on arm64 - info ♻
    • 69 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 ♻
    • 70 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 ♻
    • 70 days old (needed 5 days)
• shim (15.7-1 to 15.8-1)
  • Migration status for shim (15.7-1 to 15.8-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • Not touching package due to block request by ivodd (please contact debian-release if update is needed)
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for shim/15.8-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻
  • Additional info:
    • Updating shim will fix bugs in testing: #1057606, #1061519
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shim.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 70 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 ♻
    • Reproducible on i386 - info ♻
    • 71 days old (needed 5 days)
• rust-gvdb (- to 0.6.1-2)
  • Migration status for rust-gvdb (- to 0.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-gvdb-dev/amd64 has unsatisfiable dependency
    • librust-gvdb-dev/arm64 has unsatisfiable dependency
    • librust-gvdb-dev/armel has unsatisfiable dependency
    • librust-gvdb-dev/armhf has unsatisfiable dependency
    • librust-gvdb-dev/i386 has unsatisfiable dependency
    • librust-gvdb-dev/mips64el has unsatisfiable dependency
    • librust-gvdb-dev/ppc64el has unsatisfiable dependency
    • librust-gvdb-dev/s390x has unsatisfiable dependency
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): rust-gvdb rust-zvariant (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gvdb.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 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 ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 71 days old (needed 5 days)
• rust-gvdb-macros (- to 0.1.12-2)
  • Migration status for rust-gvdb-macros (- to 0.1.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-gvdb-macros would introduce bugs in testing: #1071888
    • rust-gvdb-macros unsatisfiable Build-Depends(-Arch) on riscv64: librust-gvdb-0.6+gresource-dev
    • missing build on amd64
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): rust-gvdb-macros rust-gvdb (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-gvdb-macros.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 ♻
    • 71 days old (needed 5 days)
• rust-num-modular (- to 0.6.1-1)
  • Migration status for rust-num-modular (- to 0.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-num-modular/0.6.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-num-modular.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 71 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 ♻
    • 71 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 ♻
    • 71 days old (needed 5 days)
• scm (- to 5f3-6)
  • Migration status for scm (- to 5f3-6): 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
    • 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 amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 71 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:
    • Updating llvm-toolchain-14 would introduce bugs in testing: #1036596, #1058822, #1068840
    • autopkgtest for llvm-toolchain-14/1:14.0.6-20: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 72 days old (needed 5 days)
• ayatana-indicator-a11y (- to 24.4.1-1)
  • Migration status for ayatana-indicator-a11y (- to 24.4.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ayatana-indicator-a11y onboard (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ayatana-indicator-a11y.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 73 days old (needed 5 days)
• virtualbox-ext-pack (- to 7.0.18-1)
  • Migration status for virtualbox-ext-pack (- to 7.0.18-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
    • 73 days old (needed 5 days)
• python-docx (1.1.0+dfsg-2 to 1.1.2+dfsg-1)
  • Migration status for python-docx (1.1.0+dfsg-2 to 1.1.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-docx/1.1.2+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-docxcompose/1.4.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-docx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 74 days old (needed 5 days)
• 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 ♻
    • 75 days old (needed 5 days)
• dioptas (- to 0.6.0-2)
  • Migration status for dioptas (- to 0.6.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): dioptas python-pyepics (not considered)
    • Depends: dioptas python-pyepics (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dioptas.html
    • autopkgtest for dioptas/0.6.0-2: amd64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 76 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 ♻
    • 76 days old (needed 5 days)
• ifscheme (- to 1.7-9)
  • Migration status for ifscheme (- to 1.7-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ifscheme would introduce bugs in testing: #981637
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ifscheme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 76 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 ♻
    • 77 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gxr-openvr openvr (not considered)
    • Depends: gxr-openvr openvr (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 77 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 ♻
    • 77 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 ♻
    • 77 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
  • 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 ♻
    • 77 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 ♻
    • 78 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 ♻
    • 78 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
    • 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 amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 78 days old (needed 5 days)
• clblas (- to 2.12-5)
  • Migration status for clblas (- to 2.12-5): 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-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
    • 79 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
    • 79 days old (needed 5 days)
• gramofile (- to 1.6-13)
  • Migration status for gramofile (- to 1.6-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gramofile/1.6-13: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: 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/gramofile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 79 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
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 79 days old (needed 5 days)
• libest (- to 3.2.0+ds-1)
  • Migration status for libest (- to 3.2.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by debian.axhn@manchmal.in-ulm.de, a new source-only upload is needed to allow migration
    • Not built on buildd: arch armel binaries uploaded by debian.axhn@manchmal.in-ulm.de
    • Impossible Depends: libest -> libssl3/3.1.5-1/armel
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 79 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 ♻
    • 79 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 ♻
    • 79 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 ♻
    • 79 days old (needed 5 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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 80 days old (needed 5 days)
• 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 ♻
    • 81 days old (needed 5 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)
    • 81 days old (needed 5 days)
• libmaus2 (2.0.813+ds-1 to 2.0.813+ds-3)
  • Migration status for libmaus2 (2.0.813+ds-1 to 2.0.813+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • Updating libmaus2 would introduce bugs in testing: #1069691
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
  • Additional info:
    • Updating libmaus2 will fix bugs in testing: #1072303
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmaus2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 81 days old (needed 5 days)
    • Remove hint for (transitive) dependency: libmaus2
• 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
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pytorch.html
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on arm64 - info ♻
    • 81 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
    • 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 ♻
    • 82 days old (needed 5 days)
• gvm-tools (- to 24.3.0-1)
  • Migration status for gvm-tools (- to 24.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): 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.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 82 days old (needed 5 days)
• iwyu (- to 8.22-1)
  • Migration status for iwyu (- to 8.22-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): iwyu llvm-toolchain-18 (not considered)
    • Depends: iwyu llvm-toolchain-18 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • 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 ♻
    • 82 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
    • 82 days old (needed 2 days)
• python-gvm (- to 24.3.0-1)
  • Migration status for python-gvm (- to 24.3.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.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 ♻
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 82 days old (needed 5 days)
• trantor (- to 1.5.12+ds-1.2)
  • Migration status for trantor (- to 1.5.12+ds-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating trantor would introduce bugs in testing: #1071725
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trantor.html
    • 82 days old (needed 5 days)
• ui-gxmlcpp (- to 1.4.6-2)
  • Migration status for ui-gxmlcpp (- to 1.4.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ui-gxmlcpp ui-utilcpp (not considered)
    • Depends: ui-gxmlcpp ui-utilcpp (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • 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 ♻
    • 82 days old (needed 5 days)
• ui-utilcpp (- to 1.10.3-2)
  • Migration status for ui-utilcpp (- to 1.10.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ui-utilcpp ucommon (not considered)
    • Depends: ui-utilcpp ucommon (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ui-utilcpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 82 days old (needed 5 days)
• 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 ♻
    • 83 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 ♻
    • 83 days old (needed 5 days)
• nvptx-tools (0.20230904-1 to 0.20240423-1)
  • Migration status for nvptx-tools (0.20230904-1 to 0.20240423-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nvptx-tools llvm-toolchain-18 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Updating nvptx-tools will fix bugs in testing: #1072307
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nvptx-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 83 days old (needed 5 days)
• openjdk-8 (- to 8u412-ga-1)
  • Migration status for openjdk-8 (- to 8u412-ga-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 ♻
    • 83 days old (needed 5 days)
• rust-sequoia-octopus-librnp (- to 1.8.1-4)
  • Migration status for rust-sequoia-octopus-librnp (- to 1.8.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-sequoia-octopus-librnp/1.8.1-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Regression or new test ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • rust-sequoia-octopus-librnp unsatisfiable Build-Depends(-Arch) on riscv64: librust-sequoia-ipc-dev (<< 0.35-~~)
    • rust-sequoia-octopus-librnp unsatisfiable Build-Depends(-Arch) on riscv64: librust-sequoia-wot-dev (<< 0.12-~~)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-octopus-librnp.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 83 days old (needed 5 days)
• trafficserver (- to 9.2.4+ds-2)
  • Migration status for trafficserver (- to 9.2.4+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating trafficserver would introduce bugs in testing: #999938
    • trafficserver unsatisfiable Build-Depends(-Arch) on amd64: libluajit2-5.1-dev [!x32] | lua [x32]
    • trafficserver unsatisfiable Build-Depends(-Arch) on arm64: libluajit2-5.1-dev [!x32] | lua [x32]
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trafficserver.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 83 days old (needed 5 days)
• uid-wrapper (- to 1.3.0-5)
  • Migration status for uid-wrapper (- to 1.3.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating uid-wrapper would introduce bugs in testing: #1069425
    • 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 uid-wrapper/1.3.0-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uid-wrapper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 83 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 ♻
    • 84 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 ♻
    • 84 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 ♻
    • 84 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 ♻
    • 84 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 ♻
    • 84 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 ♻
    • 84 days old (needed 5 days)
• mdk4 (- to 4.2-4)
  • Migration status for mdk4 (- to 4.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mdk4 aircrack-ng (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdk4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 84 days old (needed 5 days)
• controku (- to 1.1.0-1)
  • Migration status for controku (- 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 eamanu@yaerobi.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/controku.html
    • autopkgtest for controku/1.1.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, 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 ♻
    • 85 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 amd64 binaries uploaded by alteholz
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcupsfilters.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 85 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 ♻
    • 85 days old (needed 5 days)
• opencl-clang-18 (- to 18.1.0-1)
  • Migration status for opencl-clang-18 (- to 18.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): opencl-clang-18 spirv-llvm-translator-18 (not considered)
    • Depends: opencl-clang-18 spirv-llvm-translator-18 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): opencl-clang-18 llvm-toolchain-18 (not considered)
    • Depends: opencl-clang-18 llvm-toolchain-18 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencl-clang-18.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 85 days old (needed 5 days)
• ruby-base64 (- to 0.2.0-1)
  • Migration status for ruby-base64 (- 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 boutil, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-base64.html
    • autopkgtest for ruby-base64/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
    • 85 days old (needed 2 days)
• biobambam2 (2.0.185+ds-1 to 2.0.185+ds-2)
  • Migration status for biobambam2 (2.0.185+ds-1 to 2.0.185+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
    • Build-Depends(-Arch): biobambam2 libmaus2 (not considered)
    • Depends: biobambam2 libmaus2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/biobambam2.html
    • autopkgtest for biobambam2/2.0.185+ds-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 86 days old (needed 2 days)
    • Remove hint for (transitive) dependency: biobambam2, libmaus2
• 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
    • 86 days old (needed 5 days)
• dh-puppet (- to 1.0)
  • Migration status for dh-puppet (- to 1.0): 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/d/dh-puppet.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 86 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:
    • autopkgtest for exiflooter/1.0.0+git20231228.22e4700-1: 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/e/exiflooter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 86 days old (needed 5 days)
• lenovolegionlinux (- to 0.0.10+ds-2)
  • Migration status for lenovolegionlinux (- to 0.0.10+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lenovolegionlinux would introduce bugs in testing: #1070824
    • autopkgtest for lenovolegionlinux/0.0.10+ds-2: amd64: Regression or new test ♻
    • Not built on buildd: arch amd64 binaries uploaded by zigo
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/lenovolegionlinux.html
    • Reproducible on amd64 - info ♻
    • 86 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
  • 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 ♻
    • 86 days old (needed 5 days)
• raven (- to 1.0.1-1)
  • Migration status for raven (- 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 samueloph, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raven.html
    • autopkgtest for raven/1.0.1-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 86 days old (needed 2 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 armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 86 days old (needed 5 days)
• waymore (- to 3.7-1)
  • Migration status for waymore (- to 3.7-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/w/waymore.html
    • autopkgtest for waymore/3.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 ♻, 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 ♻
    • 86 days old (needed 5 days)
• amberol (- to 0.10.3-3)
  • Migration status for amberol (- to 0.10.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating amberol would introduce bugs in testing: #1071871
    • amberol unsatisfiable Build-Depends(-Arch) on amd64: librust-ashpd-0.6+gtk4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-audio-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-play-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on amd64: librust-gdk-pixbuf-0.18+v2-42-dev
    • amberol unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk4-0.7+v4-10-dev
    • amberol unsatisfiable Build-Depends(-Arch) on amd64: librust-libadwaita-0.5+v1-4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on arm64: librust-ashpd-0.6+gtk4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-audio-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-play-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on arm64: librust-gdk-pixbuf-0.18+v2-42-dev
    • amberol unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk4-0.7+v4-10-dev
    • amberol unsatisfiable Build-Depends(-Arch) on arm64: librust-libadwaita-0.5+v1-4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armel: librust-ashpd-0.6+gtk4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-audio-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-play-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armel: librust-gdk-pixbuf-0.18+v2-42-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armel: librust-gtk4-0.7+v4-10-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armel: librust-libadwaita-0.5+v1-4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armhf: librust-ashpd-0.6+gtk4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-audio-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-play-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armhf: librust-gdk-pixbuf-0.18+v2-42-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk4-0.7+v4-10-dev
    • amberol unsatisfiable Build-Depends(-Arch) on armhf: librust-libadwaita-0.5+v1-4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on i386: librust-ashpd-0.6+gtk4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-audio-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-play-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on i386: librust-gdk-pixbuf-0.18+v2-42-dev
    • amberol unsatisfiable Build-Depends(-Arch) on i386: librust-gtk4-0.7+v4-10-dev
    • amberol unsatisfiable Build-Depends(-Arch) on i386: librust-libadwaita-0.5+v1-4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on mips64el: librust-ashpd-0.6+gtk4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-audio-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-play-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on mips64el: librust-gdk-pixbuf-0.18+v2-42-dev
    • amberol unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk4-0.7+v4-10-dev
    • amberol unsatisfiable Build-Depends(-Arch) on mips64el: librust-libadwaita-0.5+v1-4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on ppc64el: librust-ashpd-0.6+gtk4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-audio-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-play-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gdk-pixbuf-0.18+v2-42-dev
    • amberol unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk4-0.7+v4-10-dev
    • amberol unsatisfiable Build-Depends(-Arch) on ppc64el: librust-libadwaita-0.5+v1-4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on riscv64: librust-gstreamer-audio-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on riscv64: librust-gstreamer-play-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on riscv64: librust-gdk-pixbuf-0.18+v2-42-dev
    • amberol unsatisfiable Build-Depends(-Arch) on riscv64: librust-gtk4-0.7+v4-10-dev
    • amberol unsatisfiable Build-Depends(-Arch) on riscv64: librust-libadwaita-0.5+v1-4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on s390x: librust-ashpd-0.6+gtk4-dev
    • amberol unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-audio-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-play-0.21-dev
    • amberol unsatisfiable Build-Depends(-Arch) on s390x: librust-gdk-pixbuf-0.18+v2-42-dev
    • amberol unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk4-0.7+v4-10-dev
    • amberol unsatisfiable Build-Depends(-Arch) on s390x: librust-libadwaita-0.5+v1-4-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amberol.html
    • autopkgtest for amberol/0.10.3-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 ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 87 days old (needed 5 days)
• gnome-shell-extension-appindicator (- to 58-1)
  • Migration status for gnome-shell-extension-appindicator (- to 58-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnome-shell-extension-appindicator gnome-shell (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-appindicator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 87 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 ♻
    • 87 days old (needed 5 days)
• magnum-cluster-api (- to 0.16.0-1)
  • Migration status for magnum-cluster-api (- to 0.16.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends-Indep: magnum-cluster-api magnum (not considered)
    • Depends: magnum-cluster-api magnum (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magnum-cluster-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 88 days old (needed 5 days)
• coremltools (- to 7.1-1)
  • Migration status for coremltools (- to 7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coremltools.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 89 days old (needed 5 days)
• gnome-shell-mailnag (- to 40.0-7)
  • Migration status for gnome-shell-mailnag (- to 40.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gnome-shell-mailnag gnome-shell (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnome-shell-mailnag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 89 days old (needed 5 days)
• openstack-cluster-installer (- to 42.3.9)
  • Migration status for openstack-cluster-installer (- to 42.3.9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: openstack-cluster-installer openstack-meta-packages (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openstack-cluster-installer.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
    • 89 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 ♻
    • 90 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 ♻
    • 91 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 ♻
    • 91 days old (needed 5 days)
• cpupower-gui (- to 0.7.2-2.2)
  • Migration status for cpupower-gui (- to 0.7.2-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpupower-gui would introduce bugs in testing: #1025555
    • Impossible Depends: cpupower-gui -> policykit-1/124-2/amd64
    • Impossible Depends: cpupower-gui -> policykit-1/124-2/arm64
    • Impossible Depends: cpupower-gui -> policykit-1/124-2/armel
    • Impossible Depends: cpupower-gui -> policykit-1/124-2/armhf
    • Impossible Depends: cpupower-gui -> policykit-1/124-2/i386
    • Impossible Depends: cpupower-gui -> policykit-1/124-2/mips64el
    • Impossible Depends: cpupower-gui -> policykit-1/124-2/ppc64el
    • Impossible Depends: cpupower-gui -> policykit-1/124-2/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpupower-gui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 92 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:
    • 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 ♻
    • 93 days old (needed 5 days)
• freeipa (- to 4.11.1-2)
  • Migration status for freeipa (- to 4.11.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-ipalib/amd64 has unsatisfiable dependency
    • python3-ipalib/arm64 has unsatisfiable dependency
    • Updating freeipa would introduce bugs in testing: #1060492
    • Build-Depends(-Arch): freeipa sssd
    • Depends: freeipa certmonger (not considered)
    • Depends: freeipa oddjob (not considered)
    • Depends: freeipa sssd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freeipa.html
    • autopkgtest for freeipa/4.11.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 ♻
    • 94 days old (needed 5 days)
• gnome-snapshot (- to 46.2-1)
  • Migration status for gnome-snapshot (- to 46.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-snapshot would introduce bugs in testing: #1070419
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on amd64: librust-gst-plugin-gtk4-0.11-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-0.21+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-0.21+v1-20-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on amd64: librust-gstreamer-pbutils-0.21-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk4-0.7+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk4-0.7+gnome-45-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on amd64: librust-libadwaita-0.5+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on amd64: librust-libadwaita-0.5+v1-4-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on arm64: librust-gst-plugin-gtk4-0.11-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-0.21+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-0.21+v1-20-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on arm64: librust-gstreamer-pbutils-0.21-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk4-0.7+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk4-0.7+gnome-45-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on arm64: librust-libadwaita-0.5+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on arm64: librust-libadwaita-0.5+v1-4-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armel: librust-gst-plugin-gtk4-0.11-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-0.21+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-0.21+v1-20-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armel: librust-gstreamer-pbutils-0.21-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armel: librust-gtk4-0.7+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armel: librust-gtk4-0.7+gnome-45-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armel: librust-libadwaita-0.5+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armel: librust-libadwaita-0.5+v1-4-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armhf: librust-gst-plugin-gtk4-0.11-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-0.21+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-0.21+v1-20-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armhf: librust-gstreamer-pbutils-0.21-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk4-0.7+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk4-0.7+gnome-45-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armhf: librust-libadwaita-0.5+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on armhf: librust-libadwaita-0.5+v1-4-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on i386: librust-gst-plugin-gtk4-0.11-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-0.21+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-0.21+v1-20-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on i386: librust-gstreamer-pbutils-0.21-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on i386: librust-gtk4-0.7+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on i386: librust-gtk4-0.7+gnome-45-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on i386: librust-libadwaita-0.5+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on i386: librust-libadwaita-0.5+v1-4-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on mips64el: librust-gst-plugin-gtk4-0.11-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-0.21+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-0.21+v1-20-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on mips64el: librust-gstreamer-pbutils-0.21-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk4-0.7+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk4-0.7+gnome-45-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on mips64el: librust-libadwaita-0.5+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on mips64el: librust-libadwaita-0.5+v1-4-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gst-plugin-gtk4-0.11-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-0.21+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-0.21+v1-20-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gstreamer-pbutils-0.21-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk4-0.7+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk4-0.7+gnome-45-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on ppc64el: librust-libadwaita-0.5+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on ppc64el: librust-libadwaita-0.5+v1-4-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on riscv64: librust-gst-plugin-gtk4-0.11-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on riscv64: librust-gstreamer-0.21+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on riscv64: librust-gstreamer-0.21+v1-20-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on riscv64: librust-gstreamer-pbutils-0.21-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on riscv64: librust-gtk4-0.7+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on riscv64: librust-gtk4-0.7+gnome-45-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on riscv64: librust-libadwaita-0.5+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on riscv64: librust-libadwaita-0.5+v1-4-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on s390x: librust-gst-plugin-gtk4-0.11-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-0.21+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-0.21+v1-20-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on s390x: librust-gstreamer-pbutils-0.21-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk4-0.7+default-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk4-0.7+gnome-45-dev
    • gnome-snapshot unsatisfiable Build-Depends(-Arch) on s390x: librust-libadwaita-0.5+default-dev
    • gnome-snapshot 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-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 ♻
    • 94 days old (needed 5 days)
• ampliconnoise (- to 1.29-11)
  • Migration status for ampliconnoise (- to 1.29-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ampliconnoise/1.29-11: 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 ♻
    • 95 days old (needed 5 days)
• bluez (5.71-1 to 5.73-1)
  • Migration status for bluez (5.71-1 to 5.73-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bluez would introduce bugs in testing: #1071147
    • autopkgtest for bluez/5.73-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:
    • Updating bluez will fix bugs in testing: #1060795, #1072270
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bluez.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Ignoring non-reproducibility on i386 (not a regression) - info ♻
    • 95 days old (needed 5 days)
• pytest-jupyter (- to 0.9.1-2)
  • Migration status for pytest-jupyter (- to 0.9.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytest-jupyter would introduce bugs in testing: #1071879
    • pytest-jupyter unsatisfiable Build-Depends(-Arch) on amd64: python3-jupyter-core (>= 5.7)
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pytest-jupyter.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 ♻
    • 95 days old (needed 5 days)
• tiktoken (- to 0.6.0-3)
  • Migration status for tiktoken (- to 0.6.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for tiktoken/0.6.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/tiktoken.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 95 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 ♻
    • 96 days old (needed 5 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
    • 96 days old (needed 2 days)
• intel-vc-intrinsics (- to 0.18.0-1)
  • Migration status for intel-vc-intrinsics (- to 0.18.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 ♻
    • 97 days old (needed 5 days)
• paperwork (- to 2.2.2-2)
  • Migration status for paperwork (- to 2.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for paperwork/2.2.2-2: 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/p/paperwork.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 98 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 ♻
    • 98 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 ♻
    • 98 days old (needed 5 days)
• rg-el (- to 2.3.0-2)
  • Migration status for rg-el (- to 2.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rg-el/2.3.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/rg-el.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 99 days old (needed 5 days)
• ruby-gitlab-sdk (- to 0.3.1-1)
  • Migration status for ruby-gitlab-sdk (- 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 praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-sdk.html
    • autopkgtest for ruby-gitlab-sdk/0.3.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 99 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
    • 99 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 ♻
    • 99 days old (needed 5 days)
• singularity-container (- to 4.1.2+ds1-1)
  • Migration status for singularity-container (- to 4.1.2+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating singularity-container would introduce bugs in testing: #1029669
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/singularity-container.html
    • Reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 99 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 ♻
    • 99 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
  • 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 ♻
    • 100 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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 102 days old (needed 5 days)
• libwww-telegram-botapi-perl (- to 0.12-1)
  • Migration status for libwww-telegram-botapi-perl (- to 0.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by happyaron.xu@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libw/libwww-telegram-botapi-perl.html
    • autopkgtest for libwww-telegram-botapi-perl/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
    • 102 days old (needed 2 days)
• ruby-moneta (- to 1.6.0-1)
  • Migration status for ruby-moneta (- to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-moneta/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/r/ruby-moneta.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 102 days old (needed 5 days)
• adios (- to 1.13.1-36)
  • Migration status for adios (- to 1.13.1-36): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): adios netcdf-parallel (not considered)
    • Depends: adios netcdf-parallel (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/adios.html
    • autopkgtest for adios/1.13.1-36: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible 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)
• 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)
    • 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 ♻
    • 103 days old (needed 5 days)
• zmat (- to 0.9.9+ds.1-2)
  • Migration status for zmat (- to 0.9.9+ds.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • matlab-zmat/arm64 has unsatisfiable dependency
    • Updating zmat would introduce bugs in testing: #1068683, #1069384
    • 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:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zmat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 103 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 ♻
    • 105 days old (needed 5 days)
• octave-iso2mesh (- to 1.9.6+ds-10)
  • Migration status for octave-iso2mesh (- to 1.9.6+ds-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: octave-iso2mesh zmat (not considered)
    • Invalidated by dependency
    • Depends: octave-iso2mesh octave-jnifti
    • Depends: octave-iso2mesh octave-jsonlab
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-iso2mesh.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 ♻
    • 105 days old (needed 5 days)
• magit-forge-el (- to 0.3.2+git20231227.1.299bbaa-1)
  • Migration status for magit-forge-el (- to 0.3.2+git20231227.1.299bbaa-1): 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-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
    • 106 days old (needed 2 days)
• octave-jsonlab (- to 2.9.8-1)
  • Migration status for octave-jsonlab (- to 2.9.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: octave-jsonlab zmat (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-jsonlab.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 107 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 ♻
    • 108 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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 108 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
  • 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 ♻
    • 109 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 109 days old (needed 5 days)
• gcc-10 (- to 10.5.0-4)
  • Migration status for gcc-10 (- to 10.5.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-10 would introduce bugs in testing: #1023666
    • Not touching package due to block request by sramacher (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10.html
    • autopkgtest for gcc-10/10.5.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 109 days old (needed 2 days)
• gcc-9 (- to 9.5.0-6)
  • Migration status for gcc-9 (- to 9.5.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9 would introduce bugs in testing: #994108
    • missing build on mips64el
    • Build-Depends(-Arch): gcc-9 gcc-10 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9.html
    • autopkgtest for gcc-9/9.5.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 109 days old (needed 2 days)
• osslsigncode (- to 2.8-2)
  • Migration status for osslsigncode (- to 2.8-2): 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/o/osslsigncode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 109 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 ♻
    • 109 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
    • 110 days old (needed 5 days)
• r-bioc-biostrings (- to 2.70.3+dfsg-1)
  • Migration status for r-bioc-biostrings (- to 2.70.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-biostrings/2.70.3+dfsg-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
    • Build-Depends(-Arch): r-bioc-biostrings r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-biostrings r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-biostrings r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-biostrings r-bioc-xvector (not considered)
    • Depends: r-bioc-biostrings r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-biostrings r-bioc-iranges (not considered)
    • Depends: r-bioc-biostrings r-bioc-s4vectors (not considered)
    • Depends: r-bioc-biostrings r-bioc-xvector (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biostrings.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 110 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
    • 111 days old (needed 2 days)
• baler (- to 1.4.0-1)
  • Migration status for baler (- to 1.4.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): baler pytorch (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - 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 ♻
    • 112 days old (needed 5 days)
• gbrainy (- to 1:2.4.6-2)
  • Migration status for gbrainy (- to 1:2.4.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gbrainy would introduce bugs in testing: #1067609
    • 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): gbrainy gtk-sharp3 (not considered)
    • Depends: gbrainy gtk-sharp3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gbrainy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 112 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 ♻
    • 112 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 ♻
    • 114 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:
    • Updating liquidsoap would introduce bugs in testing: #1064128
    • Build-Depends(-Arch): liquidsoap pcre-ocaml (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/liquidsoap.html
    • autopkgtest for liquidsoap/2.2.4-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
    • 115 days old (needed 2 days)
• lomiri-system-settings-online-accounts (- to 0.10-3)
  • Migration status for lomiri-system-settings-online-accounts (- to 0.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lomiri-system-settings-online-accounts/amd64 has unsatisfiable dependency
    • lomiri-system-settings-online-accounts/arm64 has unsatisfiable dependency
    • lomiri-system-settings-online-accounts/armel has unsatisfiable dependency
    • lomiri-system-settings-online-accounts/armhf has unsatisfiable dependency
    • lomiri-system-settings-online-accounts/i386 has unsatisfiable dependency
    • lomiri-system-settings-online-accounts/mips64el has unsatisfiable dependency
    • lomiri-system-settings-online-accounts/ppc64el has unsatisfiable dependency
    • lomiri-system-settings-online-accounts/s390x has unsatisfiable dependency
    • Updating lomiri-system-settings-online-accounts would introduce bugs in testing: #1067751, #1074537
    • 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/l/lomiri-system-settings-online-accounts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 115 days old (needed 5 days)
• rust-ripasso (- to 0.6.5-2)
  • Migration status for rust-ripasso (- to 0.6.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ripasso/0.6.5-2: 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
    • rust-ripasso unsatisfiable Build-Depends(-Arch) on riscv64: librust-sequoia-ipc-0.34+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-ripasso.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 ♻
    • 115 days old (needed 5 days)
• jupyterlab (- to 4.0.11+ds1-2)
  • Migration status for jupyterlab (- to 4.0.11+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jupyterlab would introduce bugs in testing: #1060772
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyterlab.html
    • autopkgtest for jupyterlab/4.0.11+ds1-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
    • 117 days old (needed 2 days)
• postsrsd (- to 1.10-2.1)
  • Migration status for postsrsd (- to 1.10-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating postsrsd would introduce bugs in testing: #1068053
    • 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 postsrsd/1.10-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/postsrsd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 117 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
    • 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
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • 118 days old (needed 5 days)
• dante (- to 1.4.3+dfsg-1)
  • Migration status for dante (- to 1.4.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dante would introduce bugs in testing: #1067709
    • 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 dante/1.4.3+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dante.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 119 days old (needed 5 days)
• guix (- to 1.4.0-6)
  • Migration status for guix (- to 1.4.0-6): 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 121 days old (needed 5 days)
• cvise (- to 2.10.0-1)
  • Migration status for cvise (- to 2.10.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): cvise llvm-toolchain-18 (not considered)
    • Depends: cvise llvm-toolchain-18 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cvise.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 123 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 ♻
    • 123 days old (needed 5 days)
• python-dmidecode (- to 3.12.3-3)
  • Migration status for python-dmidecode (- to 3.12.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-dmidecode/3.12.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dmidecode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 123 days old (needed 5 days)
• creduce (- to 2.11.0~20240312-1)
  • Migration status for creduce (- to 2.11.0~20240312-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): creduce llvm-toolchain-18 (not considered)
    • Depends: creduce llvm-toolchain-18 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/creduce.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 124 days old (needed 5 days)
• libfiu (- to 1.2-2)
  • Migration status for libfiu (- to 1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libfiu would introduce bugs in testing: #1066938
    • 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 libfiu/1.2-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libfiu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 125 days old (needed 5 days)
• r-bioc-deseq2 (- to 1.42.1+dfsg-1)
  • Migration status for r-bioc-deseq2 (- to 1.42.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-deseq2/1.42.1+dfsg-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
    • Build-Depends(-Arch): r-bioc-deseq2 r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-deseq2 r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-deseq2 r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-deseq2 r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-deseq2 r-bioc-genomicranges (not considered)
    • Depends: r-bioc-deseq2 r-bioc-iranges (not considered)
    • Depends: r-bioc-deseq2 r-bioc-s4vectors (not considered)
    • Depends: r-bioc-deseq2 r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-deseq2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 125 days old (needed 5 days)
• ruby-semver-dialects (- to 1.6.2-1)
  • Migration status for ruby-semver-dialects (- to 1.6.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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/1.6.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 ♻
    • 125 days old (needed 5 days)
• autofs (- to 5.1.9-1.1)
  • Migration status for autofs (- to 5.1.9-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): autofs sssd (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autofs.html
    • autopkgtest for autofs/5.1.9-1.1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 127 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:
    • gitlab/amd64 has unsatisfiable dependency
    • gitlab/arm64 has unsatisfiable dependency
    • Updating gitlab would introduce bugs in testing: #1009942, #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
    • Build-Depends(-Arch): gitlab gitaly
    • Built-Using: gitlab gitaly
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab.html
    • Reproducible on armhf - info ♻
    • 127 days old (needed 5 days)
• netdata (- to 1.44.3-2)
  • Migration status for netdata (- to 1.44.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netdata would introduce bugs in testing: #1042533, #1045145
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 127 days old (needed 5 days)
• openstack-meta-packages (- to 0.35)
  • Migration status for openstack-meta-packages (- to 0.35): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: openstack-meta-packages novnc (not considered)
    • Invalidated by dependency
    • Depends: openstack-meta-packages nova
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openstack-meta-packages.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 127 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 arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 128 days old (needed 5 days)
• owncloud-client-desktop-shell-integration-dolphin (- to 5.0.0-2)
  • Migration status for owncloud-client-desktop-shell-integration-dolphin (- to 5.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: owncloud-client-desktop-shell-integration-dolphin owncloud-client (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/owncloud-client-desktop-shell-integration-dolphin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 128 days old (needed 5 days)
• owncloud-client-desktop-shell-integration-nautilus (- to 5.0.0-2)
  • Migration status for owncloud-client-desktop-shell-integration-nautilus (- to 5.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: owncloud-client-desktop-shell-integration-nautilus owncloud-client (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/owncloud-client-desktop-shell-integration-nautilus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 128 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 ♻
    • 129 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 armhf - info ♻
    • Reproducible on i386 - info ♻
    • 130 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
    • 130 days old (needed 2 days)
• epics-base (- to 7.0.8+dfsg1-1)
  • Migration status for epics-base (- to 7.0.8+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating epics-base would introduce bugs in testing: #1065724
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epics-base.html
    • 131 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:
    • Updating anki would introduce bugs in testing: #1053541, #1065822, #1067702, #958853
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/anki.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 132 days old (needed 5 days)
• gnome-shell-extension-arc-menu (- to 55-1)
  • Migration status for gnome-shell-extension-arc-menu (- to 55-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnome-shell-extension-arc-menu/amd64 has unsatisfiable dependency
    • gnome-shell-extension-arc-menu/arm64 has unsatisfiable dependency
    • Updating gnome-shell-extension-arc-menu would introduce bugs in testing: #1052088
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-arc-menu.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 ♻
    • 132 days old (needed 5 days)
• qwertone (- to 0.4.0-1)
  • Migration status for qwertone (- to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qwertone would introduce bugs in testing: #1019042
    • qwertone unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on amd64: librust-gdk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on arm64: librust-gdk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on armhf: librust-gdk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on i386: librust-gtk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on i386: librust-gdk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on mips64el: librust-gdk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gdk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on riscv64: librust-gtk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on riscv64: librust-gdk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk-0+default-dev (>= 0.14-~~)
    • qwertone unsatisfiable Build-Depends(-Arch) on s390x: librust-gdk-0+default-dev (>= 0.14-~~)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qwertone.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 ♻
    • 133 days old (needed 5 days)
• r-cran-afex (- to 1.3-1-1)
  • Migration status for r-cran-afex (- to 1.3-1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-afex/1.3-1-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-afex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 133 days old (needed 5 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, #1065145
  • 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 ♻
    • 134 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, #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 ♻
    • 135 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 135 days old (needed 5 days)
• hwinfo (- to 21.82-1.1)
  • Migration status for hwinfo (- to 21.82-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): hwinfo libx86emu (not considered)
    • Depends: hwinfo libx86emu (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hwinfo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 136 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)
    • 136 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 ♻
    • 136 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
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Build-Depends(-Arch): pytorch-cuda gloo-cuda (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
    • 136 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
    • Waiting for reproducibility test results on i386 - info ♻
    • 136 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 ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 136 days old (needed 5 days)
• sysrepo (- to 2.0.53-6.1)
  • Migration status for sysrepo (- to 2.0.53-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sysrepo would introduce bugs in testing: #1037068, #996847
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sysrepo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 136 days old (needed 5 days)
• termrec (- to 0.19-2.1)
  • Migration status for termrec (- to 0.19-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating termrec would introduce bugs in testing: #1065906
    • missing build on armel
    • missing build on armhf
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/termrec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 136 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 ♻
    • 136 days old (needed 5 days)
• vagrant-librarian-puppet (- to 0.9.2-3)
  • Migration status for vagrant-librarian-puppet (- to 0.9.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vagrant-librarian-puppet would introduce bugs in testing: #1064686
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vagrant-librarian-puppet.html
    • autopkgtest for vagrant-librarian-puppet/0.9.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 ♻
    • 136 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 ♻
    • 137 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 ♻
    • 137 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 ♻
    • 137 days old (needed 5 days)
• freecontact (- to 1.0.21-13.1)
  • Migration status for freecontact (- to 1.0.21-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freecontact would introduce bugs in testing: #1069552
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freecontact.html
    • autopkgtest for freecontact/1.0.21-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 137 days old (needed 2 days)
• gpac (- to 2.2.1+dfsg1-3.1)
  • Migration status for gpac (- to 2.2.1+dfsg1-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpac would introduce bugs in testing: #1034732, #1051740, #1051866, #1051955, #1056282, #1059056, #1060409, #1068462
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpac.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 137 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grok.html
    • 137 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 ♻
    • 137 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 ♻
    • 137 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
  • 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 ♻
    • 137 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 ♻
    • 137 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
    • 137 days old (needed 2 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
    • 137 days old (needed 5 days)
• nut (- to 2.8.1-3.1)
  • Migration status for nut (- to 2.8.1-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nut would introduce bugs in testing: #1064670, #1067790
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nut.html
    • autopkgtest for nut/2.8.1-3.1: amd64: Pass, arm64: Pass, armel: Ignored failure, armhf: Pass, i386: Ignored failure, ppc64el: Ignored failure, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 137 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 ♻
    • 137 days old (needed 5 days)
• open3d (- to 0.18.0+ds-3.1)
  • Migration status for open3d (- to 0.18.0+ds-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-open3d/amd64 has unsatisfiable dependency
    • python3-open3d/arm64 has unsatisfiable dependency
    • libopen3d0.18t64/ppc64el has unsatisfiable dependency
    • python3-open3d/ppc64el has unsatisfiable dependency
    • libopen3d0.18t64/s390x has unsatisfiable dependency
    • python3-open3d/s390x has unsatisfiable dependency
    • open3d unsatisfiable Build-Depends(-Arch) on s390x: libfilament-dev
    • open3d unsatisfiable Build-Depends(-Arch) on s390x: libfilament-tools
    • autopkgtest for open3d/0.18.0+ds-3.1: armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): open3d pytorch (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open3d.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 ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 137 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 ♻
    • 137 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 ♻
    • 137 days old (needed 5 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
    • 138 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
    • 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 amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 138 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
    • 138 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/boost1.74.html
    • autopkgtest for boost1.74/1.74.0+ds1-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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 138 days old (needed 2 days)
• brial (- to 1.2.12-1.1)
  • Migration status for brial (- to 1.2.12-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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 ♻
    • 138 days old (needed 5 days)
• drogon (- to 1.8.7+ds-1.1)
  • Migration status for drogon (- to 1.8.7+ds-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating drogon would introduce bugs in testing: #1071304
    • Build-Depends(-Arch): drogon trantor (not considered)
    • Depends: drogon trantor (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drogon.html
    • 138 days old (needed 5 days)
• 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eiskaltdcpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 138 days old (needed 5 days)
• gyoto (- to 2.0.2-1.1)
  • Migration status for gyoto (- to 2.0.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libgyoto9t64/amd64 has unsatisfiable dependency
    • libgyoto9t64/arm64 has unsatisfiable dependency
    • gyoto-bin/armel has unsatisfiable dependency
    • libgyoto9t64/armel has unsatisfiable dependency
    • python3-gyoto/armel has unsatisfiable dependency
    • yorick-gyoto/armel has unsatisfiable dependency
    • gyoto-bin/armhf has unsatisfiable dependency
    • libgyoto9t64/armhf has unsatisfiable dependency
    • python3-gyoto/armhf has unsatisfiable dependency
    • yorick-gyoto/armhf has unsatisfiable dependency
    • libgyoto9t64/i386 has unsatisfiable dependency
    • libgyoto9t64/mips64el has unsatisfiable dependency
    • libgyoto9t64/ppc64el has unsatisfiable dependency
    • libgyoto9t64/s390x has unsatisfiable dependency
    • Updating gyoto would introduce bugs in testing: #1066788
    • autopkgtest for gyoto/2.0.2-1.1: riscv64: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gyoto.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 138 days old (needed 5 days)
• hepmc3 (- to 3.1.2-2.1)
  • Migration status for hepmc3 (- to 3.1.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hepmc3 would introduce bugs in testing: #1064556
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hepmc3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • 138 days old (needed 5 days)
• ledmon (- to 0.97-1)
  • Migration status for ledmon (- to 0.97-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ledmon would introduce bugs in testing: #1060587
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ledmon.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 138 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 ♻
    • 138 days old (needed 5 days)
• progress-linux-metapackages (- to 20221002-13)
  • Migration status for progress-linux-metapackages (- to 20221002-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • progress-linux-container-server/amd64 has unsatisfiable dependency
    • progress-linux-gnome-desktop/amd64 has unsatisfiable dependency
    • progress-linux-container-server/arm64 has unsatisfiable dependency
    • progress-linux-gnome-desktop/arm64 has unsatisfiable dependency
    • Updating progress-linux-metapackages would introduce bugs in testing: #1076259
    • Depends: progress-linux-metapackages fq (not considered)
    • 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 ♻
    • 139 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
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 139 days old (needed 5 days)
• tox-delay (- to 0.1.4-1)
  • Migration status for tox-delay (- 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): tox-delay feature-check (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tox-delay.html
    • autopkgtest for tox-delay/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
    • 139 days old (needed 2 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 ♻
    • 142 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
    • 142 days old (needed 2 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 ♻
    • 143 days old (needed 5 days)
• rust-isahc (- to 1.7.2+ds-26)
  • Migration status for rust-isahc (- to 1.7.2+ds-26): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-isahc would introduce bugs in testing: #1060848, #1067251
    • 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/r/rust-isahc.html
    • 143 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)
    • 145 days old (needed 5 days)
• qpid-proton-j-extensions (- to 1.2.4-2)
  • Migration status for qpid-proton-j-extensions (- to 1.2.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: qpid-proton-j-extensions qpid-proton-j (not considered)
    • Depends: qpid-proton-j-extensions qpid-proton-j (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpid-proton-j-extensions.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 days old (needed 5 days)
• r-bioc-beachmat (- to 2.18.1+ds-1)
  • Migration status for r-bioc-beachmat (- to 2.18.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-beachmat r-bioc-sparsearray (not considered)
    • Depends: r-bioc-beachmat r-bioc-sparsearray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-beachmat r-bioc-delayedarray
    • Depends: r-bioc-beachmat r-bioc-delayedarray
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-beachmat.html
    • autopkgtest for r-bioc-beachmat/2.18.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 145 days old (needed 2 days)
• r-bioc-hdf5array (- to 1.30.1-1)
  • Migration status for r-bioc-hdf5array (- to 1.30.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-hdf5array would introduce bugs in testing: #1071342
    • autopkgtest for r-bioc-hdf5array/1.30.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
    • Build-Depends(-Arch): r-bioc-hdf5array r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-hdf5array r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-hdf5array r-bioc-rhdf5 (not considered)
    • Build-Depends(-Arch): r-bioc-hdf5array r-bioc-s4arrays (not considered)
    • Build-Depends(-Arch): r-bioc-hdf5array r-bioc-s4vectors (not considered)
    • Depends: r-bioc-hdf5array r-bioc-delayedarray
    • Depends: r-bioc-hdf5array r-bioc-iranges (not considered)
    • Depends: r-bioc-hdf5array r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-hdf5array r-bioc-s4arrays (not considered)
    • Depends: r-bioc-hdf5array r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-hdf5array.html
    • 145 days old (needed 5 days)
• scribus (- to 1.5.8+dfsg-5)
  • Migration status for scribus (- to 1.5.8+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scribus would introduce bugs in testing: #1074220
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scribus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 145 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: Pass
  • 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
    • 145 days old (needed 5 days)
• r-bioc-sparsearray (- to 1.2.4+dfsg-1)
  • Migration status for r-bioc-sparsearray (- to 1.2.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-sparsearray would introduce bugs in testing: #1071351
    • autopkgtest for r-bioc-sparsearray/1.2.4+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): r-bioc-sparsearray r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-sparsearray r-bioc-s4arrays (not considered)
    • Build-Depends(-Arch): r-bioc-sparsearray r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-sparsearray r-bioc-xvector (not considered)
    • Depends: r-bioc-sparsearray r-bioc-iranges (not considered)
    • Depends: r-bioc-sparsearray r-bioc-s4arrays (not considered)
    • Depends: r-bioc-sparsearray r-bioc-s4vectors (not considered)
    • Depends: r-bioc-sparsearray r-bioc-xvector (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-sparsearray.html
    • 146 days old (needed 5 days)
• gitaly (- to 16.8.2+ds3-2)
  • Migration status for gitaly (- to 16.8.2+ds3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gitaly golang-github-go-enry-go-license-detector (not considered)
    • Depends: gitaly golang-github-go-enry-go-license-detector (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): gitaly gitlab-shell
    • Depends: gitaly gitlab-shell
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitaly.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 147 days old (needed 5 days)
• gitlab-shell (- to 14.33.0-2)
  • Migration status for gitlab-shell (- to 14.33.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gitlab-shell gitaly (not considered)
    • Built-Using: gitlab-shell gitaly (not considered)
    • Depends: gitlab-shell gitaly (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-shell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 147 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:
    • Updating nipype would introduce bugs in testing: #1064732
    • autopkgtest for nipype/1.8.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): nipype nitime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nipype.html
    • 147 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: No tests, superficial or marked flaky ♻
  • 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
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 147 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
    • 148 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
    • 148 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
    • 148 days old (needed 2 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 ♻
    • 150 days old (needed 5 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 ♻
    • 150 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: #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 ♻
    • 152 days old (needed 5 days)
• transmissionrpc (- to 7.0.3-2)
  • Migration status for transmissionrpc (- to 7.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating transmissionrpc would introduce bugs in testing: #1071724
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/transmissionrpc.html
    • autopkgtest for transmissionrpc/7.0.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 152 days old (needed 2 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 ♻
    • 153 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
    • 153 days old (needed 5 days)
• r-bioc-bsgenome (- to 1.70.2-1)
  • Migration status for r-bioc-bsgenome (- to 1.70.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-bsgenome r-bioc-xvector (not considered)
    • Depends: r-bioc-bsgenome r-bioc-xvector (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-bsgenome r-bioc-biocio
    • Build-Depends(-Arch): r-bioc-bsgenome r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-bsgenome r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-bsgenome r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-bsgenome r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-bsgenome r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-bsgenome r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-bsgenome r-bioc-s4vectors (not considered)
    • Depends: r-bioc-bsgenome r-bioc-biocio
    • Depends: r-bioc-bsgenome r-bioc-biostrings (not considered)
    • Depends: r-bioc-bsgenome r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-bsgenome r-bioc-genomicranges (not considered)
    • Depends: r-bioc-bsgenome r-bioc-iranges (not considered)
    • Depends: r-bioc-bsgenome r-bioc-rsamtools (not considered)
    • Depends: r-bioc-bsgenome r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-bsgenome r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-bsgenome.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-bsgenome/1.70.2-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
    • 153 days old (needed 2 days)
• r-bioc-genomeinfodb (- to 1.38.6+dfsg-1)
  • Migration status for r-bioc-genomeinfodb (- to 1.38.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-genomeinfodb/1.38.6+dfsg-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
    • Build-Depends(-Arch): r-bioc-genomeinfodb r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-genomeinfodb r-bioc-s4vectors (not considered)
    • Depends: r-bioc-genomeinfodb r-bioc-iranges (not considered)
    • Depends: r-bioc-genomeinfodb r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genomeinfodb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 153 days old (needed 5 days)
• r-bioc-glmgampoi (- to 1.14.3+dfsg-1)
  • Migration status for r-bioc-glmgampoi (- to 1.14.3+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-glmgampoi r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-glmgampoi r-bioc-summarizedexperiment (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-glmgampoi r-bioc-beachmat
    • Build-Depends(-Arch): r-bioc-glmgampoi r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-glmgampoi r-bioc-delayedmatrixstats
    • Build-Depends(-Arch): r-bioc-glmgampoi r-bioc-hdf5array (not considered)
    • Build-Depends(-Arch): r-bioc-glmgampoi r-bioc-singlecellexperiment (not considered)
    • Depends: r-bioc-glmgampoi r-bioc-beachmat
    • Depends: r-bioc-glmgampoi r-bioc-delayedarray
    • Depends: r-bioc-glmgampoi r-bioc-delayedmatrixstats
    • Depends: r-bioc-glmgampoi r-bioc-hdf5array (not considered)
    • Depends: r-bioc-glmgampoi r-bioc-singlecellexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-glmgampoi.html
    • autopkgtest for r-bioc-glmgampoi/1.14.3+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 153 days old (needed 2 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 ♻
    • 154 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
  • 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
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 154 days old (needed 2 days)
• routine-update (- to 0.2)
  • Migration status for routine-update (- to 0.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: routine-update lintian-brush (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/routine-update.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 154 days old (needed 5 days)
• 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:
    • Piuparts tested OK - 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 ♻
    • 154 days old (needed 5 days)
• feature-check (- to 2.1.0-2)
  • Migration status for feature-check (- to 2.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating feature-check would introduce bugs in testing: #1071683
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/feature-check.html
    • autopkgtest for feature-check/2.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 155 days old (needed 2 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 ♻
    • 155 days old (needed 5 days)
• yade (- to 2024.02a-1)
  • Migration status for yade (- to 2024.02a-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yade would introduce bugs in testing: #1074435
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yade.html
    • autopkgtest for yade/2024.02a-1: amd64: Pass, arm64: 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
    • 155 days old (needed 2 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
    • Depends: bookletimposer pypdf2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bookletimposer.html
    • autopkgtest for bookletimposer/0.3.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 156 days old (needed 2 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
    • 156 days old (needed 5 days)
• rust-sqlx (- to 0.7.3-3)
  • Migration status for rust-sqlx (- to 0.7.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-sqlx/0.7.3-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): rust-sqlx rust-sqlx-macros
    • Build-Depends(-Arch): rust-sqlx rust-sqlx-mysql
    • Depends: rust-sqlx rust-sqlx-macros
    • Depends: rust-sqlx rust-sqlx-mysql
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 157 days old (needed 5 days)
• beaker (- to 1.12.1-3)
  • Migration status for beaker (- to 1.12.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: beaker pycryptodome (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/beaker.html
    • autopkgtest for beaker/1.12.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 158 days old (needed 2 days)
• loupe (- to 45.3-2)
  • Migration status for loupe (- to 45.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating loupe would introduce bugs in testing: #1071876
    • loupe unsatisfiable Build-Depends(-Arch) on amd64: librust-ashpd-0.6+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on amd64: librust-ashpd-0.6+gtk4-dev
    • loupe unsatisfiable Build-Depends(-Arch) on amd64: librust-gio-0.18+default-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on amd64: librust-gio-0.18+v2-74-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on amd64: librust-glycin-0.1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk4-0.7+default-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk4-0.7+v4-12-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on amd64: librust-gtk4-0.7+xml-validation-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on amd64: librust-indexmap-1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on amd64: librust-libadwaita-0.5+default-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on amd64: librust-libadwaita-0.5+v1-4-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on arm64: librust-ashpd-0.6+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on arm64: librust-ashpd-0.6+gtk4-dev
    • loupe unsatisfiable Build-Depends(-Arch) on arm64: librust-gio-0.18+default-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on arm64: librust-gio-0.18+v2-74-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on arm64: librust-glycin-0.1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk4-0.7+default-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk4-0.7+v4-12-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on arm64: librust-gtk4-0.7+xml-validation-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on arm64: librust-indexmap-1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on arm64: librust-libadwaita-0.5+default-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on arm64: librust-libadwaita-0.5+v1-4-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armel: librust-ashpd-0.6+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on armel: librust-ashpd-0.6+gtk4-dev
    • loupe unsatisfiable Build-Depends(-Arch) on armel: librust-gio-0.18+default-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armel: librust-gio-0.18+v2-74-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armel: librust-glycin-0.1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on armel: librust-gtk4-0.7+default-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armel: librust-gtk4-0.7+v4-12-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armel: librust-gtk4-0.7+xml-validation-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armel: librust-indexmap-1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on armel: librust-libadwaita-0.5+default-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armel: librust-libadwaita-0.5+v1-4-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armhf: librust-ashpd-0.6+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on armhf: librust-ashpd-0.6+gtk4-dev
    • loupe unsatisfiable Build-Depends(-Arch) on armhf: librust-gio-0.18+default-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armhf: librust-gio-0.18+v2-74-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armhf: librust-glycin-0.1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk4-0.7+default-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk4-0.7+v4-12-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armhf: librust-gtk4-0.7+xml-validation-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armhf: librust-indexmap-1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on armhf: librust-libadwaita-0.5+default-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on armhf: librust-libadwaita-0.5+v1-4-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on i386: librust-ashpd-0.6+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on i386: librust-ashpd-0.6+gtk4-dev
    • loupe unsatisfiable Build-Depends(-Arch) on i386: librust-gio-0.18+default-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on i386: librust-gio-0.18+v2-74-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on i386: librust-glycin-0.1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on i386: librust-gtk4-0.7+default-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on i386: librust-gtk4-0.7+v4-12-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on i386: librust-gtk4-0.7+xml-validation-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on i386: librust-indexmap-1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on i386: librust-libadwaita-0.5+default-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on i386: librust-libadwaita-0.5+v1-4-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on mips64el: librust-ashpd-0.6+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on mips64el: librust-ashpd-0.6+gtk4-dev
    • loupe unsatisfiable Build-Depends(-Arch) on mips64el: librust-gio-0.18+default-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on mips64el: librust-gio-0.18+v2-74-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on mips64el: librust-glycin-0.1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk4-0.7+default-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk4-0.7+v4-12-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on mips64el: librust-gtk4-0.7+xml-validation-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on mips64el: librust-indexmap-1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on mips64el: librust-libadwaita-0.5+default-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on mips64el: librust-libadwaita-0.5+v1-4-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on ppc64el: librust-ashpd-0.6+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on ppc64el: librust-ashpd-0.6+gtk4-dev
    • loupe unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gio-0.18+default-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gio-0.18+v2-74-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on ppc64el: librust-glycin-0.1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk4-0.7+default-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk4-0.7+v4-12-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on ppc64el: librust-gtk4-0.7+xml-validation-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on ppc64el: librust-indexmap-1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on ppc64el: librust-libadwaita-0.5+default-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on ppc64el: librust-libadwaita-0.5+v1-4-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on riscv64: librust-gio-0.18+default-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on riscv64: librust-gio-0.18+v2-74-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on riscv64: librust-gtk4-0.7+default-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on riscv64: librust-gtk4-0.7+v4-12-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on riscv64: librust-gtk4-0.7+xml-validation-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on riscv64: librust-indexmap-1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on riscv64: librust-libadwaita-0.5+default-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on riscv64: librust-libadwaita-0.5+v1-4-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on s390x: librust-ashpd-0.6+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on s390x: librust-ashpd-0.6+gtk4-dev
    • loupe unsatisfiable Build-Depends(-Arch) on s390x: librust-gio-0.18+default-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on s390x: librust-gio-0.18+v2-74-dev (>= 0.18.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on s390x: librust-glycin-0.1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk4-0.7+default-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk4-0.7+v4-12-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on s390x: librust-gtk4-0.7+xml-validation-dev (>= 0.7.1-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on s390x: librust-indexmap-1+default-dev
    • loupe unsatisfiable Build-Depends(-Arch) on s390x: librust-libadwaita-0.5+default-dev (>= 0.5.2-~~)
    • loupe unsatisfiable Build-Depends(-Arch) on s390x: librust-libadwaita-0.5+v1-4-dev (>= 0.5.2-~~)
    • Build-Depends(-Arch): loupe rust-gvdb-macros (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/loupe.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 ♻
    • 158 days old (needed 5 days)
• r-bioc-gosemsim (- to 2.28.1-1)
  • Migration status for r-bioc-gosemsim (- to 2.28.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-gosemsim r-bioc-annotationdbi (not considered)
    • Depends: r-bioc-gosemsim r-bioc-annotationdbi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-gosemsim r-bioc-go.db
    • Depends: r-bioc-gosemsim r-bioc-go.db
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-gosemsim.html
    • autopkgtest for r-bioc-gosemsim/2.28.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
    • 159 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 ♻
    • 160 days old (needed 5 days)
• pynpoint (- to 0.11.0-2)
  • Migration status for pynpoint (- to 0.11.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pynpoint/amd64 has unsatisfiable dependency
    • python3-pynpoint/arm64 has unsatisfiable dependency
    • Updating pynpoint would introduce bugs in testing: #1071053
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pynpoint.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 ♻
    • 160 days old (needed 5 days)
• rust-sqlx-macros (- to 0.7.3-1)
  • Migration status for rust-sqlx-macros (- 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-macros rust-sqlx-macros-core (not considered)
    • Depends: rust-sqlx-macros rust-sqlx-macros-core (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-macros.html
    • autopkgtest for rust-sqlx-macros/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
    • 160 days old (needed 2 days)
• rust-sqlx-macros-core (- to 0.7.3-1)
  • Migration status for rust-sqlx-macros-core (- to 0.7.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-sqlx-macros-core rust-sqlx-mysql (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sqlx-macros-core.html
    • autopkgtest for rust-sqlx-macros-core/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
    • 160 days old (needed 2 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
    • 160 days old (needed 2 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:
    • Updating giada would introduce bugs in testing: #1073997
    • Impossible Depends: giada -> librtaudio6/5.2.0~ds1-2+b2/amd64
    • Impossible Depends: giada -> librtaudio6/5.2.0~ds1-2+b2/arm64
    • Impossible Depends: giada -> librtaudio6/5.2.0~ds1-2+b2/armhf
    • Impossible Depends: giada -> librtaudio6/5.2.0~ds1-2+b2/i386
    • Impossible Depends: giada -> librtaudio6/5.2.0~ds1-2+b2/mips64el
    • Impossible Depends: giada -> librtaudio6/5.2.0~ds1-2+b2/ppc64el
    • Impossible Depends: giada -> librtaudio6/5.2.0~ds1-2+b2/s390x
    • Impossible Depends: giada -> librtmidi6/5.0.0-3+b2/amd64
    • Impossible Depends: giada -> librtmidi6/5.0.0-3+b2/arm64
    • Impossible Depends: giada -> librtmidi6/5.0.0-3+b2/armhf
    • Impossible Depends: giada -> librtmidi6/5.0.0-3+b2/i386
    • Impossible Depends: giada -> librtmidi6/5.0.0-3+b2/mips64el
    • Impossible Depends: giada -> librtmidi6/5.0.0-3+b2/ppc64el
    • Impossible Depends: giada -> librtmidi6/5.0.0-3+b2/s390x
    • 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
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 161 days old (needed 5 days)
• python-altair (- to 5.0.1-1)
  • Migration status for python-altair (- to 5.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-altair would introduce bugs in testing: #1064701
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-altair.html
    • autopkgtest for python-altair/5.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 ♻
    • 161 days old (needed 5 days)
• python-cooler (- to 0.9.3-1)
  • Migration status for python-cooler (- to 0.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-cooler would introduce bugs in testing: #1069359
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cooler.html
    • autopkgtest for python-cooler/0.9.3-1: amd64: Pass, arm64: Pass, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 161 days old (needed 5 days)
• r-bioc-biomart (- to 2.58.2+dfsg-1)
  • Migration status for r-bioc-biomart (- to 2.58.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): r-bioc-biomart r-bioc-annotationdbi (not considered)
    • Depends: r-bioc-biomart r-bioc-annotationdbi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biomart.html
    • autopkgtest for r-bioc-biomart/2.58.2+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
    • 161 days old (needed 2 days)
• r-bioc-genomicfeatures (- to 1.54.3+dfsg-1)
  • Migration status for r-bioc-genomicfeatures (- to 1.54.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gffread/0.12.7-6: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-bioc-genomicfeatures/1.54.3+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): r-bioc-genomicfeatures r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-genomicfeatures r-bioc-biocio
    • Build-Depends(-Arch): r-bioc-genomicfeatures r-bioc-biomart
    • Build-Depends(-Arch): r-bioc-genomicfeatures r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfeatures r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfeatures r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfeatures r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfeatures r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfeatures r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfeatures r-bioc-xvector (not considered)
    • Depends: r-bioc-genomicfeatures r-bioc-annotationdbi
    • Depends: r-bioc-genomicfeatures r-bioc-biocio
    • Depends: r-bioc-genomicfeatures r-bioc-biomart
    • Depends: r-bioc-genomicfeatures r-bioc-biostrings (not considered)
    • Depends: r-bioc-genomicfeatures r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-genomicfeatures r-bioc-genomicranges (not considered)
    • Depends: r-bioc-genomicfeatures r-bioc-iranges (not considered)
    • Depends: r-bioc-genomicfeatures r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-genomicfeatures r-bioc-s4vectors (not considered)
    • Depends: r-bioc-genomicfeatures r-bioc-xvector (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genomicfeatures.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
    • 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 ♻
    • 161 days old (needed 5 days)
• r-bioc-tximeta (- to 1.20.3+dfsg-1)
  • Migration status for r-bioc-tximeta (- to 1.20.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-tximeta/1.20.3+dfsg-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
    • Build-Depends(-Arch): r-bioc-tximeta r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-tximeta r-bioc-annotationhub (not considered)
    • Build-Depends(-Arch): r-bioc-tximeta r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-tximeta r-bioc-ensembldb
    • Build-Depends(-Arch): r-bioc-tximeta r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-tximeta r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-tximeta r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-tximeta r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-tximeta r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-tximeta r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-tximeta r-bioc-annotationdbi
    • Depends: r-bioc-tximeta r-bioc-annotationhub (not considered)
    • Depends: r-bioc-tximeta r-bioc-biostrings (not considered)
    • Depends: r-bioc-tximeta r-bioc-ensembldb
    • Depends: r-bioc-tximeta r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-tximeta r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-tximeta r-bioc-genomicranges (not considered)
    • Depends: r-bioc-tximeta r-bioc-iranges (not considered)
    • Depends: r-bioc-tximeta r-bioc-s4vectors (not considered)
    • Depends: r-bioc-tximeta r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-tximeta.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 ♻
    • 161 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
  • Additional info:
    • Piuparts tested OK - 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 ♻
    • 162 days old (needed 5 days)
• python-django-adminplus (- to 0.6-1)
  • Migration status for python-django-adminplus (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-adminplus.html
    • autopkgtest for python-django-adminplus/0.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 162 days old (needed 2 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 ♻
    • 162 days old (needed 5 days)
• ffcv (- to 1.0.0+git20240202+ds-1)
  • Migration status for ffcv (- to 1.0.0+git20240202+ds-1): 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 ♻
    • 164 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 ♻
    • 164 days old (needed 5 days)
• r-cran-rpact (- to 3.5.0-1)
  • Migration status for r-cran-rpact (- to 3.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-rpact/3.5.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 ♻
    • 164 days old (needed 5 days)
• sbws (- to 1.9.0-1)
  • Migration status for sbws (- to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sbws would introduce bugs in testing: #1071057
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbws.html
    • autopkgtest for sbws/1.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 164 days old (needed 2 days)
• ocserv (- to 1.2.4-1)
  • Migration status for ocserv (- to 1.2.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ocserv uid-wrapper (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): ocserv socket-wrapper (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocserv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 165 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
    • autopkgtest for r-cran-lavasearch2/2.0.3+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test in progress
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/atlas.html
    • 166 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
    • 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.1.5-1/armel
    • Impossible Depends: ruby3.2 -> libssl3/3.1.5-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby3.2.html
    • 166 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 ♻
    • 168 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 ♻
    • 170 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 ♻
    • 170 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
    • 170 days old (needed 5 days)
• r-bioc-genomicalignments (- to 1.38.2-1)
  • Migration status for r-bioc-genomicalignments (- to 1.38.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-genomicalignments r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-genomicalignments r-bioc-summarizedexperiment (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-genomicalignments r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-genomicalignments r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-genomicalignments r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-genomicalignments r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-genomicalignments r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-genomicalignments r-bioc-s4vectors (not considered)
    • Depends: r-bioc-genomicalignments r-bioc-biostrings (not considered)
    • Depends: r-bioc-genomicalignments r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-genomicalignments r-bioc-genomicranges (not considered)
    • Depends: r-bioc-genomicalignments r-bioc-iranges (not considered)
    • Depends: r-bioc-genomicalignments r-bioc-rsamtools (not considered)
    • Depends: r-bioc-genomicalignments r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genomicalignments.html
    • autopkgtest for r-bioc-genomicalignments/1.38.2-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
    • 171 days old (needed 2 days)
• r-bioc-scran (- to 1.30.2+dfsg-1)
  • Migration status for r-bioc-scran (- to 1.30.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-scran/1.30.2+dfsg-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
    • Build-Depends(-Arch): r-bioc-scran r-bioc-beachmat
    • Build-Depends(-Arch): r-bioc-scran r-bioc-biocsingular
    • Build-Depends(-Arch): r-bioc-scran r-bioc-bluster (not considered)
    • Build-Depends(-Arch): r-bioc-scran r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-scran r-bioc-delayedmatrixstats
    • Build-Depends(-Arch): r-bioc-scran r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-scran r-bioc-scuttle (not considered)
    • Build-Depends(-Arch): r-bioc-scran r-bioc-singlecellexperiment (not considered)
    • Build-Depends(-Arch): r-bioc-scran r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-scran r-bioc-beachmat
    • Depends: r-bioc-scran r-bioc-biocsingular
    • Depends: r-bioc-scran r-bioc-bluster (not considered)
    • Depends: r-bioc-scran r-bioc-delayedarray
    • Depends: r-bioc-scran r-bioc-delayedmatrixstats
    • Depends: r-bioc-scran r-bioc-s4vectors (not considered)
    • Depends: r-bioc-scran r-bioc-scuttle (not considered)
    • Depends: r-bioc-scran r-bioc-singlecellexperiment (not considered)
    • Depends: r-bioc-scran r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-scran.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 171 days old (needed 5 days)
• rlinetd (- to 0.9.3-2)
  • Migration status for rlinetd (- to 0.9.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rlinetd would introduce bugs in testing: #1066466
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rlinetd.html
    • 171 days old (needed 5 days)
• rust-microformats (- to 0.6.1-2)
  • Migration status for rust-microformats (- to 0.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-microformats would introduce bugs in testing: #1050087
    • autopkgtest for rust-microformats/0.6.1-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-microformats.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 171 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 ♻
    • 172 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 ♻
    • 172 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 ♻
    • 172 days old (needed 5 days)
• gnome-shell-extension-dash-to-panel (- to 60-1~exp1)
  • Migration status for gnome-shell-extension-dash-to-panel (- to 60-1~exp1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gnome-shell-extension-dash-to-panel/amd64 has unsatisfiable dependency
    • gnome-shell-extension-dash-to-panel/arm64 has unsatisfiable dependency
    • Updating gnome-shell-extension-dash-to-panel would introduce bugs in testing: #1069113
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-dash-to-panel.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 ♻
    • 173 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 dfvfs (not considered)
    • Depends: plaso dfvfs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plaso.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 174 days old (needed 5 days)
• golang-github-prometheus-community-pgbouncer-exporter (- to 0.7.0-1)
  • Migration status for golang-github-prometheus-community-pgbouncer-exporter (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-prometheus-community-pgbouncer-exporter would introduce bugs in testing: #1067277
    • autopkgtest for golang-github-prometheus-community-pgbouncer-exporter/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/g/golang-github-prometheus-community-pgbouncer-exporter.html
    • 175 days old (needed 5 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
    • 175 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
    • 175 days old (needed 2 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
    • 175 days old (needed 5 days)
• pynfft (- to 1.3.2-8)
  • Migration status for pynfft (- to 1.3.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pynfft/amd64 has unsatisfiable dependency
    • python3-pynfft/arm64 has unsatisfiable dependency
    • python3-pynfft/armel has unsatisfiable dependency
    • python3-pynfft/armhf has unsatisfiable dependency
    • python3-pynfft/i386 has unsatisfiable dependency
    • python3-pynfft/mips64el has unsatisfiable dependency
    • python3-pynfft/ppc64el has unsatisfiable dependency
    • python3-pynfft/s390x has unsatisfiable dependency
    • autopkgtest for pynfft/1.3.2-8: riscv64: Regression or new test ♻
    • Build-Depends(-Arch): pynfft nfft (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pynfft.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 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 ♻
    • 175 days old (needed 5 days)
• astra-toolbox (- to 2.1.0-4)
  • Migration status for astra-toolbox (- to 2.1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-astra-toolbox/amd64 has unsatisfiable dependency
    • Updating astra-toolbox would introduce bugs in testing: #1074375
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • 177 days old (needed 5 days)
• endless-sky (- to 0.10.4-1)
  • Migration status for endless-sky (- to 0.10.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating endless-sky would introduce bugs in testing: #1061241
    • missing build on i386
    • missing build on ppc64el
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/endless-sky.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 177 days old (needed 5 days)
• py-libzfs (- to 0.0+git20240117.143b624-1)
  • Migration status for py-libzfs (- to 0.0+git20240117.143b624-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating py-libzfs would introduce bugs in testing: #1072137
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for py-libzfs/0.0+git20240117.143b624-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 ♻
    • 177 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
    • 177 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 ♻
    • 177 days old (needed 5 days)
• datalad-container (- to 1.2.5-1)
  • Migration status for datalad-container (- to 1.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): datalad-container datalad (not considered)
    • Depends: datalad-container datalad (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/datalad-container.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 178 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: Regression or new test ♻
  • 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 ♻
    • 178 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
    • 180 days old (needed 2 days)
• r-bioc-biocneighbors (- to 1.20.2+ds-1)
  • Migration status for r-bioc-biocneighbors (- to 1.20.2+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-biocneighbors r-bioc-s4vectors (not considered)
    • Depends: r-bioc-biocneighbors r-bioc-s4vectors (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biocneighbors.html
    • autopkgtest for r-bioc-biocneighbors/1.20.2+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
    • 180 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 ♻
    • 180 days old (needed 5 days)
• r-cran-epir (- to 2.0.67+dfsg-1)
  • Migration status for r-cran-epir (- to 2.0.67+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-epir/2.0.67+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): r-cran-epir r-cran-sf (not considered)
    • Depends: r-cran-epir r-cran-sf (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-epir.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 180 days old (needed 5 days)
• buildbot (- to 3.10.1-2)
  • Migration status for buildbot (- to 3.10.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • buildbot/amd64 has unsatisfiable dependency
    • buildbot/arm64 has unsatisfiable dependency
    • Updating buildbot would introduce bugs in testing: #1073001
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/b/buildbot.html
    • buildbot unsatisfiable Build-Depends(-Arch) on amd64: python3-sqlalchemy (<< 1.5)
    • autopkgtest for buildbot/3.10.1-2: riscv64: Pass
  • 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 ♻
    • 181 days old (needed 5 days)
• datefudge (- to 1.26)
  • Migration status for datefudge (- to 1.26): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating datefudge would introduce bugs in testing: #1069478
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/datefudge.html
    • autopkgtest for datefudge/1.26: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 182 days old (needed 2 days)
• python-django-test-migrations (- to 1.3.0-2)
  • Migration status for python-django-test-migrations (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-test-migrations would introduce bugs in testing: #1072607
    • autopkgtest for python-django-test-migrations/1.3.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-test-migrations.html
    • 182 days old (needed 5 days)
• r-bioc-demixt (- to 1.18.0+dfsg-1)
  • Migration status for r-bioc-demixt (- to 1.18.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
    • Build-Depends(-Arch): r-bioc-demixt r-bioc-summarizedexperiment (not considered)
    • Build-Depends(-Arch): r-bioc-demixt r-bioc-sva
    • Depends: r-bioc-demixt r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-demixt r-bioc-sva
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-demixt.html
    • autopkgtest for r-bioc-demixt/1.18.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
    • 182 days old (needed 2 days)
• r-bioc-dss (- to 2.50.1+dfsg-1)
  • Migration status for r-bioc-dss (- to 2.50.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-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.50.1+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
    • 182 days old (needed 2 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 ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 183 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
    • 183 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
    • 183 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
    • 183 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:
    • autopkgtest for python-aiortc/1.6.0-1: amd64: Regression or new test ♻, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
    • python-aiortc unsatisfiable Build-Depends(-Arch) on riscv64: 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 ♻
    • 184 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
    • 185 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:
    • Updating rust-transmission-client would introduce bugs in testing: #1071892
    • Build-Depends(-Arch): rust-transmission-client rust-isahc (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-transmission-client.html
    • autopkgtest for rust-transmission-client/0.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 ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 185 days old (needed 5 days)
• apktool (- to 2.7.0+dfsg-7)
  • Migration status for apktool (- to 2.7.0+dfsg-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: apktool android-platform-frameworks-base (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apktool.html
    • autopkgtest for apktool/2.7.0+dfsg-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
    • 186 days old (needed 2 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
    • 186 days old (needed 5 days)
• pycryptodome (3.11.0+dfsg1-4 to 3.20.0+dfsg-1)
  • Migration status for pycryptodome (3.11.0+dfsg1-4 to 3.20.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pycryptodome would introduce bugs in testing: #1069534
    • missing build on armel
    • missing build on mips64el
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for pycryptodome/3.20.0+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating pycryptodome will fix bugs in testing: #1052336
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pycryptodome.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 186 days old (needed 5 days)
• r-bioc-singler (- to 2.4.1+ds-1)
  • Migration status for r-bioc-singler (- to 2.4.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-singler/2.4.1+ds-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
    • Build-Depends(-Arch): r-bioc-singler r-bioc-beachmat
    • Build-Depends(-Arch): r-bioc-singler r-bioc-biocneighbors
    • Build-Depends(-Arch): r-bioc-singler r-bioc-biocsingular
    • Build-Depends(-Arch): r-bioc-singler r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-singler r-bioc-delayedmatrixstats
    • Build-Depends(-Arch): r-bioc-singler r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-singler r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-singler r-bioc-beachmat
    • Depends: r-bioc-singler r-bioc-biocneighbors
    • Depends: r-bioc-singler r-bioc-biocsingular
    • Depends: r-bioc-singler r-bioc-delayedarray
    • Depends: r-bioc-singler r-bioc-delayedmatrixstats
    • Depends: r-bioc-singler r-bioc-s4vectors (not considered)
    • Depends: r-bioc-singler r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-singler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 186 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
    • 187 days old (needed 2 days)
• python-stdlib-list (- to 0.10.0-1)
  • Migration status for python-stdlib-list (- to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-stdlib-list would introduce bugs in testing: #1067325
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-stdlib-list.html
    • autopkgtest for python-stdlib-list/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 ♻
    • 187 days old (needed 5 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
    • 187 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 beaker (not considered)
    • Depends: pysph beaker (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): pysph compyle (not considered)
    • Build-Depends(-Arch): pysph mayavi2 (not considered)
    • Depends: pysph compyle (not considered)
  • 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 ♻
    • 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
    • 189 days old (needed 2 days)
• octave-brain2mesh (- to 0.7.9-3)
  • Migration status for octave-brain2mesh (- 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: octave-brain2mesh zmat (not considered)
    • Invalidated by dependency
    • Depends: octave-brain2mesh octave-iso2mesh
    • Depends: octave-brain2mesh octave-jnifti
    • Depends: octave-brain2mesh octave-jsonlab
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-brain2mesh.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 190 days old (needed 5 days)
• octave-jnifti (- to 0.6-3)
  • Migration status for octave-jnifti (- to 0.6-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: octave-jnifti octave-jsonlab (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-jnifti.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 190 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
    • 190 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
    • Not built on buildd: arch all binaries uploaded by jas, a new source-only upload is needed to allow migration
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/apt-verify.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 191 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)
  • 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 ♻
    • 191 days old (needed 5 days)
• picom-conf (- to 0.17.0-1)
  • Migration status for picom-conf (- to 0.17.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): picom-conf qtilitools (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picom-conf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 191 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
    • 192 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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intake.html
    • 192 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 ♻
    • 193 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 ♻
    • 194 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
    • 195 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
    • 197 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)
    • Depends: courier courier-authlib (not considered)
    • Depends: courier maildrop (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
    • 197 days old (needed 5 days)
• devicexlib (- to 0.8.2-1)
  • Migration status for devicexlib (- to 0.8.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/devicexlib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 198 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 ♻
    • 198 days old (needed 5 days)
• yt (- to 4.3.0-1)
  • Migration status for yt (- to 4.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yt would introduce bugs in testing: #1069397
    • autopkgtest for yt/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/y/yt.html
    • 201 days old (needed 5 days)
• rust-secret-service (- to 3.0.1-1)
  • Migration status for rust-secret-service (- to 3.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-secret-service-dev/amd64 has unsatisfiable dependency
    • librust-secret-service-dev/arm64 has unsatisfiable dependency
    • librust-secret-service-dev/armel has unsatisfiable dependency
    • librust-secret-service-dev/armhf has unsatisfiable dependency
    • librust-secret-service-dev/i386 has unsatisfiable dependency
    • librust-secret-service-dev/mips64el has unsatisfiable dependency
    • librust-secret-service-dev/ppc64el has unsatisfiable dependency
    • librust-secret-service-dev/s390x has unsatisfiable dependency
    • Updating rust-secret-service would introduce bugs in testing: #1060321
    • autopkgtest for rust-secret-service/3.0.1-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-secret-service.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 202 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
    • 204 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
    • 204 days old (needed 2 days)
• swiftlang (- to 5.6.3-3)
  • Migration status for swiftlang (- to 5.6.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating swiftlang would introduce bugs in testing: #1072131
  • 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
    • 204 days old (needed 5 days)
• bfh-metapackages (- to 20211009-24)
  • Migration status for bfh-metapackages (- to 20211009-24): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bfh-container-server/amd64 has unsatisfiable dependency
    • bfh-gnome-desktop/amd64 has unsatisfiable dependency
    • bfh-container-server/arm64 has unsatisfiable dependency
    • bfh-gnome-desktop/arm64 has unsatisfiable dependency
    • Updating bfh-metapackages would introduce bugs in testing: #1052556
    • Depends: bfh-metapackages lnav (not considered)
    • Depends: bfh-metapackages sssd
  • 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 ♻
    • 205 days old (needed 5 days)
• golang-github-henrybear327-go-proton-api (- to 1.0.0-3)
  • Migration status for golang-github-henrybear327-go-proton-api (- to 1.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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
    • 205 days old (needed 5 days)
• golang-github-henrybear327-proton-api-bridge (- to 1.0.0-2)
  • Migration status for golang-github-henrybear327-proton-api-bridge (- to 1.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-henrybear327-proton-api-bridge/1.0.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): golang-github-henrybear327-proton-api-bridge golang-github-henrybear327-go-proton-api (not considered)
    • Build-Depends(-Arch): golang-github-henrybear327-proton-api-bridge golang-github-protonmail-gluon (not considered)
    • Depends: golang-github-henrybear327-proton-api-bridge golang-github-henrybear327-go-proton-api (not considered)
    • Depends: golang-github-henrybear327-proton-api-bridge golang-github-protonmail-gluon (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-henrybear327-proton-api-bridge.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 205 days old (needed 5 days)
• golang-github-protonmail-go-srp (- to 0.0.7+ds-2)
  • Migration status for golang-github-protonmail-go-srp (- to 0.0.7+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-protonmail-go-srp/0.0.7+ds-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, 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 ♻
    • 205 days old (needed 5 days)
• qtilitools (- to 0.1.2-1)
  • Migration status for qtilitools (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtilitools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 205 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ohcount.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 206 days old (needed 5 days)
• fq (- to 0.9.0-2)
  • Migration status for fq (- to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fq would introduce bugs in testing: #1005961
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fq.html
    • autopkgtest for fq/0.9.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
    • 207 days old (needed 2 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 ♻
    • 207 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 ♻
    • 208 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)
    • 209 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 ♻
    • 209 days old (needed 5 days)
• r-bioc-megadepth (- to 1.12.0+ds-2)
  • Migration status for r-bioc-megadepth (- to 1.12.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-megadepth/1.12.0+ds-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: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): r-bioc-megadepth r-bioc-genomicranges (not considered)
    • Depends: r-bioc-megadepth r-bioc-genomicranges (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-megadepth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 209 days old (needed 5 days)
• r-bioc-scater (- to 1.30.1+ds-2)
  • Migration status for r-bioc-scater (- to 1.30.1+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-scater r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-scater r-bioc-summarizedexperiment (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-scater r-bioc-beachmat
    • Build-Depends(-Arch): r-bioc-scater r-bioc-biocneighbors
    • Build-Depends(-Arch): r-bioc-scater r-bioc-biocsingular
    • Build-Depends(-Arch): r-bioc-scater r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-scater r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-scater r-bioc-scuttle (not considered)
    • Build-Depends(-Arch): r-bioc-scater r-bioc-singlecellexperiment (not considered)
    • Depends: r-bioc-scater r-bioc-beachmat
    • Depends: r-bioc-scater r-bioc-biocneighbors
    • Depends: r-bioc-scater r-bioc-biocsingular
    • Depends: r-bioc-scater r-bioc-delayedarray
    • Depends: r-bioc-scater r-bioc-s4vectors (not considered)
    • Depends: r-bioc-scater r-bioc-scuttle (not considered)
    • Depends: r-bioc-scater r-bioc-singlecellexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-scater.html
    • autopkgtest for r-bioc-scater/1.30.1+ds-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: 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 ♻
    • 209 days old (needed 5 days)
• r-cran-wgcna (- to 1.72-5-1)
  • Migration status for r-cran-wgcna (- to 1.72-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-wgcna r-bioc-annotationdbi (not considered)
    • Depends: r-cran-wgcna r-bioc-annotationdbi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-wgcna r-bioc-go.db
    • Depends: r-cran-wgcna r-bioc-go.db
  • 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 ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 209 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 ♻
    • 209 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
    • 209 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-pyepics
    • Depends: xraylarch python-pyepics
  • 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
    • 209 days old (needed 2 days)
• r-bioc-cner (- to 1.38.0+dfsg-2)
  • Migration status for r-bioc-cner (- to 1.38.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): r-bioc-cner r-bioc-xvector (not considered)
    • Depends: r-bioc-cner r-bioc-xvector (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-cner r-bioc-annotate
    • Build-Depends(-Arch): r-bioc-cner r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-cner r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-cner r-bioc-genomicalignments
    • Build-Depends(-Arch): r-bioc-cner r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-cner r-bioc-go.db
    • Build-Depends(-Arch): r-bioc-cner r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-cner r-bioc-keggrest
    • Build-Depends(-Arch): r-bioc-cner r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-cner r-bioc-s4vectors (not considered)
    • Depends: r-bioc-cner r-bioc-annotate
    • Depends: r-bioc-cner r-bioc-biostrings (not considered)
    • Depends: r-bioc-cner r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-cner r-bioc-genomicalignments
    • Depends: r-bioc-cner r-bioc-genomicranges (not considered)
    • Depends: r-bioc-cner r-bioc-go.db
    • Depends: r-bioc-cner r-bioc-iranges (not considered)
    • Depends: r-bioc-cner r-bioc-keggrest
    • Depends: r-bioc-cner r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-cner r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-cner.html
    • autopkgtest for r-bioc-cner/1.38.0+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
    • 210 days old (needed 2 days)
• r-bioc-degreport (- to 1.38.5+dfsg-1)
  • Migration status for r-bioc-degreport (- to 1.38.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-bioc-degreport r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-degreport r-bioc-summarizedexperiment (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-degreport r-bioc-complexheatmap
    • Build-Depends(-Arch): r-bioc-degreport r-bioc-deseq2 (not considered)
    • Build-Depends(-Arch): r-bioc-degreport r-bioc-s4vectors (not considered)
    • Depends: r-bioc-degreport r-bioc-complexheatmap
    • Depends: r-bioc-degreport r-bioc-deseq2 (not considered)
    • Depends: r-bioc-degreport r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-degreport.html
    • autopkgtest for r-bioc-degreport/1.38.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
    • 210 days old (needed 2 days)
• r-bioc-rhdf5 (- to 2.46.1+dfsg-1)
  • Migration status for r-bioc-rhdf5 (- to 2.46.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-rhdf5 would introduce bugs in testing: #1071345
    • autopkgtest for r-bioc-rhdf5/2.46.1+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): r-bioc-rhdf5 r-bioc-s4vectors (not considered)
    • Depends: r-bioc-rhdf5 r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rhdf5.html
    • 210 days old (needed 5 days)
• r-bioc-shortread (- to 1.60.0-2)
  • Migration status for r-bioc-shortread (- to 1.60.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-shortread would introduce bugs in testing: #1071350
    • autopkgtest for r-bioc-shortread/1.60.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): r-bioc-shortread r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-shortread r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-shortread r-bioc-genomicalignments
    • Build-Depends(-Arch): r-bioc-shortread r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-shortread r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-shortread r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-shortread r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-shortread r-bioc-xvector (not considered)
    • Depends: r-bioc-shortread r-bioc-biostrings (not considered)
    • Depends: r-bioc-shortread r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-shortread r-bioc-genomicalignments
    • Depends: r-bioc-shortread r-bioc-genomicranges (not considered)
    • Depends: r-bioc-shortread r-bioc-iranges (not considered)
    • Depends: r-bioc-shortread r-bioc-rsamtools (not considered)
    • Depends: r-bioc-shortread r-bioc-s4vectors (not considered)
    • Depends: r-bioc-shortread r-bioc-xvector (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-shortread.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 210 days old (needed 5 days)
• appstream-generator (- to 0.9.1-1)
  • Migration status for appstream-generator (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating appstream-generator would introduce bugs in testing: #966249
    • missing build on armhf
    • missing build on s390x
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appstream-generator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 211 days old (needed 5 days)
• pysurfer (- to 0.11.2-1)
  • Migration status for pysurfer (- to 0.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pysurfer/0.11.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): pysurfer mayavi2 (not considered)
    • Depends: pysurfer mayavi2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysurfer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 212 days old (needed 5 days)
• pyferret (- to 7.6.5-5)
  • Migration status for pyferret (- to 7.6.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-ferret/amd64 has unsatisfiable dependency
    • python3-ferret/arm64 has unsatisfiable dependency
    • python3-ferret/i386 has unsatisfiable dependency
    • python3-ferret/s390x has unsatisfiable dependency
    • Updating pyferret would introduce bugs in testing: #1058888
    • autopkgtest for pyferret/7.6.5-5: riscv64: Regression or new test ♻
    • pyferret unsatisfiable Build-Depends(-Arch) on amd64: python3-future
    • pyferret unsatisfiable Build-Depends(-Arch) on arm64: python3-future
    • pyferret unsatisfiable Build-Depends(-Arch) on armel: python3-future
    • pyferret unsatisfiable Build-Depends(-Arch) on armhf: python3-future
    • pyferret unsatisfiable Build-Depends(-Arch) on i386: python3-future
    • pyferret unsatisfiable Build-Depends(-Arch) on mips64el: python3-future
    • pyferret unsatisfiable Build-Depends(-Arch) on ppc64el: python3-future
    • pyferret unsatisfiable Build-Depends(-Arch) on riscv64: python3-future
    • pyferret unsatisfiable Build-Depends(-Arch) on s390x: python3-future
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyferret.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 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 ♻
    • 213 days old (needed 5 days)
• pynn (- to 0.10.1-3)
  • Migration status for pynn (- to 0.10.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pynn would introduce bugs in testing: #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 ♻
    • 213 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
    • Build-Depends(-Arch): pytorch-sparse pytorch (not considered)
    • Build-Depends(-Arch): pytorch-sparse pytorch-scatter (not considered)
  • Additional info:
    • Piuparts tested OK - 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 ♻
    • 214 days old (needed 5 days)
• fapolicyd (- to 1.3.2+20231212+git973a86d1b4-1)
  • Migration status for fapolicyd (- to 1.3.2+20231212+git973a86d1b4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fapolicyd would introduce bugs in testing: #1037547
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fapolicyd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 215 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
    • Build-Depends(-Arch): pytorch-scatter pytorch (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-scatter.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 ♻
    • 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)
• 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: 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/h/hg-git.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 216 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 ♻
    • 216 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
    • Build-Depends(-Arch): pytorch-cluster pytorch (not considered)
  • Additional info:
    • Piuparts tested OK - 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 216 days old (needed 5 days)
• sstp-client (- to 1.0.19-1)
  • Migration status for sstp-client (- to 1.0.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sstp-client would introduce bugs in testing: #1010992
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sstp-client.html
    • 216 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 ♻
    • 217 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 ♻
    • 218 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
    • 218 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 ♻
    • 218 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 ♻
    • 218 days old (needed 5 days)
• r-bioc-cummerbund (- to 2.44.0-1)
  • Migration status for r-bioc-cummerbund (- to 2.44.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-bioc-cummerbund r-bioc-s4vectors (not considered)
    • Depends: r-bioc-cummerbund r-bioc-s4vectors (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-cummerbund r-bioc-gviz (not considered)
    • Build-Depends(-Arch): r-bioc-cummerbund r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-cummerbund r-bioc-gviz (not considered)
    • Depends: r-bioc-cummerbund r-bioc-rtracklayer (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-cummerbund.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for r-bioc-cummerbund/2.44.0-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
    • 219 days old (needed 2 days)
• r-bioc-ggbio (- to 1.50.0-1)
  • Migration status for r-bioc-ggbio (- to 1.50.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-bioc-ggbio r-bioc-bsgenome (not considered)
    • Depends: r-bioc-ggbio r-bioc-bsgenome (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-annotationfilter
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-biovizbase
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-ensembldb
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-genomicalignments
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-organismdbi (not considered)
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-summarizedexperiment (not considered)
    • Build-Depends(-Arch): r-bioc-ggbio r-bioc-variantannotation (not considered)
    • Depends: r-bioc-ggbio r-bioc-annotationdbi
    • Depends: r-bioc-ggbio r-bioc-annotationfilter
    • Depends: r-bioc-ggbio r-bioc-biostrings (not considered)
    • Depends: r-bioc-ggbio r-bioc-biovizbase
    • Depends: r-bioc-ggbio r-bioc-ensembldb
    • Depends: r-bioc-ggbio r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-ggbio r-bioc-genomicalignments
    • Depends: r-bioc-ggbio r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-ggbio r-bioc-genomicranges (not considered)
    • Depends: r-bioc-ggbio r-bioc-iranges (not considered)
    • Depends: r-bioc-ggbio r-bioc-organismdbi (not considered)
    • Depends: r-bioc-ggbio r-bioc-rsamtools (not considered)
    • Depends: r-bioc-ggbio r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-ggbio r-bioc-s4vectors (not considered)
    • Depends: r-bioc-ggbio r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-ggbio r-bioc-variantannotation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-ggbio.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-ggbio/1.50.0-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
    • 219 days old (needed 2 days)
• r-bioc-gviz (- to 1.46.1+dfsg-1)
  • Migration status for r-bioc-gviz (- to 1.46.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gffread/0.12.7-6: amd64: Pass, arm64: Pass, ppc64el: Pass, s390x: Regression or new test ♻ (reference ♻)
    • autopkgtest for r-bioc-gviz/1.46.1+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-biomart
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-biovizbase
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-bsgenome
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-ensembldb
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-genomicalignments
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-gviz r-bioc-xvector (not considered)
    • Depends: r-bioc-gviz r-bioc-annotationdbi
    • Depends: r-bioc-gviz r-bioc-biomart
    • Depends: r-bioc-gviz r-bioc-biostrings (not considered)
    • Depends: r-bioc-gviz r-bioc-biovizbase
    • Depends: r-bioc-gviz r-bioc-bsgenome
    • Depends: r-bioc-gviz r-bioc-ensembldb
    • Depends: r-bioc-gviz r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-gviz r-bioc-genomicalignments
    • Depends: r-bioc-gviz r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-gviz r-bioc-genomicranges (not considered)
    • Depends: r-bioc-gviz r-bioc-iranges (not considered)
    • Depends: r-bioc-gviz r-bioc-rsamtools (not considered)
    • Depends: r-bioc-gviz r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-gviz r-bioc-s4vectors (not considered)
    • Depends: r-bioc-gviz r-bioc-xvector (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-gviz.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 ♻
    • 219 days old (needed 5 days)
• r-bioc-isoformswitchanalyzer (- to 2.2.0+ds-1)
  • Migration status for r-bioc-isoformswitchanalyzer (- to 2.2.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-isoformswitchanalyzer r-bioc-xvector (not considered)
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-xvector (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-bsgenome
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-dexseq
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-saturn (not considered)
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-summarizedexperiment (not considered)
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-sva
    • Build-Depends(-Arch): r-bioc-isoformswitchanalyzer r-bioc-tximeta (not considered)
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-biostrings (not considered)
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-bsgenome
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-dexseq
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-genomicranges (not considered)
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-iranges (not considered)
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-s4vectors (not considered)
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-saturn (not considered)
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-sva
    • Depends: r-bioc-isoformswitchanalyzer r-bioc-tximeta (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-isoformswitchanalyzer.html
    • autopkgtest for r-bioc-isoformswitchanalyzer/2.2.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
    • 219 days old (needed 2 days)
• r-bioc-rgsepd (- to 1.34.0-1)
  • Migration status for r-bioc-rgsepd (- to 1.34.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-rgsepd/1.34.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
    • Build-Depends(-Arch): r-bioc-rgsepd r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-rgsepd r-bioc-biomart
    • Build-Depends(-Arch): r-bioc-rgsepd r-bioc-deseq2 (not considered)
    • Build-Depends(-Arch): r-bioc-rgsepd r-bioc-go.db
    • Build-Depends(-Arch): r-bioc-rgsepd r-bioc-goseq (not considered)
    • Build-Depends(-Arch): r-bioc-rgsepd r-bioc-org.hs.eg.db
    • Build-Depends(-Arch): r-bioc-rgsepd r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-rgsepd r-bioc-annotationdbi
    • Depends: r-bioc-rgsepd r-bioc-biomart
    • Depends: r-bioc-rgsepd r-bioc-deseq2 (not considered)
    • Depends: r-bioc-rgsepd r-bioc-go.db
    • Depends: r-bioc-rgsepd r-bioc-goseq (not considered)
    • Depends: r-bioc-rgsepd r-bioc-org.hs.eg.db
    • Depends: r-bioc-rgsepd r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rgsepd.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 ♻
    • 219 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 ♻
    • 221 days old (needed 5 days)
• pychopper (- to 2.7.9-1)
  • Migration status for pychopper (- to 2.7.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pychopper/2.7.9-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 i386 - info ♻
    • 222 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 ♻
    • 223 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 ♻
    • 223 days old (needed 5 days)
• r-bioc-netsam (- to 1.42.0-1)
  • Migration status for r-bioc-netsam (- to 1.42.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-bioc-netsam r-bioc-annotationdbi (not considered)
    • Depends: r-bioc-netsam r-bioc-annotationdbi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-netsam r-bioc-biomart
    • Build-Depends(-Arch): r-bioc-netsam r-bioc-go.db
    • Build-Depends(-Arch): r-bioc-netsam r-cran-wgcna
    • Depends: r-bioc-netsam r-bioc-biomart
    • Depends: r-bioc-netsam r-bioc-go.db
    • 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.42.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 223 days old (needed 2 days)
• r-bioc-org.hs.eg.db (- to 3.18.0-1)
  • Migration status for r-bioc-org.hs.eg.db (- 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): r-bioc-org.hs.eg.db r-bioc-annotationdbi (not considered)
    • Depends: r-bioc-org.hs.eg.db r-bioc-annotationdbi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-org.hs.eg.db.html
    • autopkgtest for r-bioc-org.hs.eg.db/3.18.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
    • 223 days old (needed 2 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
    • 225 days old (needed 2 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 ♻
    • 225 days old (needed 5 days)
• r-bioc-degnorm (- to 1.12.0+ds-1)
  • Migration status for r-bioc-degnorm (- to 1.12.0+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-degnorm r-bioc-genomicalignments (not considered)
    • Depends: r-bioc-degnorm r-bioc-genomicalignments (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-degnorm r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-degnorm r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-degnorm r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-degnorm r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-degnorm r-bioc-s4vectors (not considered)
    • Depends: r-bioc-degnorm r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-degnorm r-bioc-genomicranges (not considered)
    • Depends: r-bioc-degnorm r-bioc-iranges (not considered)
    • Depends: r-bioc-degnorm r-bioc-rsamtools (not considered)
    • Depends: r-bioc-degnorm r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-degnorm.html
    • autopkgtest for r-bioc-degnorm/1.12.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
    • 226 days old (needed 2 days)
• r-bioc-scrnaseq (- to 2.16.0+ds-1)
  • Migration status for r-bioc-scrnaseq (- to 2.16.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-scrnaseq/2.16.0+ds-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
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-annotationhub (not considered)
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-ensembldb
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-experimenthub (not considered)
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-singlecellexperiment (not considered)
    • Build-Depends(-Arch): r-bioc-scrnaseq r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-scrnaseq r-bioc-annotationdbi
    • Depends: r-bioc-scrnaseq r-bioc-annotationhub (not considered)
    • Depends: r-bioc-scrnaseq r-bioc-ensembldb
    • Depends: r-bioc-scrnaseq r-bioc-experimenthub (not considered)
    • Depends: r-bioc-scrnaseq r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-scrnaseq r-bioc-genomicranges (not considered)
    • Depends: r-bioc-scrnaseq r-bioc-s4vectors (not considered)
    • Depends: r-bioc-scrnaseq r-bioc-singlecellexperiment (not considered)
    • Depends: r-bioc-scrnaseq r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-scrnaseq.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 ♻
    • 226 days old (needed 5 days)
• r-bioc-structuralvariantannotation (- to 1.18.0+ds-1)
  • Migration status for r-bioc-structuralvariantannotation (- to 1.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-structuralvariantannotation r-bioc-variantannotation (not considered)
    • Depends: r-bioc-structuralvariantannotation r-bioc-variantannotation (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-structuralvariantannotation r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-structuralvariantannotation r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-structuralvariantannotation r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-structuralvariantannotation r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-structuralvariantannotation r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-structuralvariantannotation r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-structuralvariantannotation r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-structuralvariantannotation r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-structuralvariantannotation r-bioc-biostrings (not considered)
    • Depends: r-bioc-structuralvariantannotation r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-structuralvariantannotation r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-structuralvariantannotation r-bioc-genomicranges (not considered)
    • Depends: r-bioc-structuralvariantannotation r-bioc-iranges (not considered)
    • Depends: r-bioc-structuralvariantannotation r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-structuralvariantannotation r-bioc-s4vectors (not considered)
    • Depends: r-bioc-structuralvariantannotation r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-structuralvariantannotation.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-structuralvariantannotation/1.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
    • 226 days old (needed 2 days)
• r-bioc-titancna (- to 1.40.0-1)
  • Migration status for r-bioc-titancna (- to 1.40.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-bioc-titancna r-bioc-variantannotation (not considered)
    • Depends: r-bioc-titancna r-bioc-variantannotation (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-titancna r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-titancna r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-titancna r-bioc-iranges (not considered)
    • Depends: r-bioc-titancna r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-titancna r-bioc-genomicranges (not considered)
    • Depends: r-bioc-titancna r-bioc-iranges (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-titancna.html
    • autopkgtest for r-bioc-titancna/1.40.0-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
    • 226 days old (needed 2 days)
• r-bioc-arrayexpress (- to 1.62.0-1)
  • Migration status for r-bioc-arrayexpress (- to 1.62.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-bioc-arrayexpress r-bioc-oligo (not considered)
    • Depends: r-bioc-arrayexpress r-bioc-oligo (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-arrayexpress.html
    • autopkgtest for r-bioc-arrayexpress/1.62.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
    • 227 days old (needed 2 days)
• r-bioc-ballgown (- to 2.34.0+dfsg-1)
  • Migration status for r-bioc-ballgown (- to 2.34.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-ballgown r-bioc-s4vectors (not considered)
    • Depends: r-bioc-ballgown r-bioc-s4vectors (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-ballgown r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-ballgown r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-ballgown r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-ballgown r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-ballgown r-bioc-sva
    • Depends: r-bioc-ballgown r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-ballgown r-bioc-genomicranges (not considered)
    • Depends: r-bioc-ballgown r-bioc-iranges (not considered)
    • Depends: r-bioc-ballgown r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-ballgown r-bioc-sva
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-ballgown.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-ballgown/2.34.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
    • 227 days old (needed 2 days)
• r-bioc-biovizbase (- to 1.50.0-1)
  • Migration status for r-bioc-biovizbase (- to 1.50.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-bioc-biovizbase r-bioc-variantannotation (not considered)
    • Depends: r-bioc-biovizbase r-bioc-variantannotation (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-annotationfilter
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-ensembldb
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-genomicalignments
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-biovizbase r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-biovizbase r-bioc-annotationdbi
    • Depends: r-bioc-biovizbase r-bioc-annotationfilter
    • Depends: r-bioc-biovizbase r-bioc-biostrings (not considered)
    • Depends: r-bioc-biovizbase r-bioc-ensembldb
    • Depends: r-bioc-biovizbase r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-biovizbase r-bioc-genomicalignments
    • Depends: r-bioc-biovizbase r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-biovizbase r-bioc-genomicranges (not considered)
    • Depends: r-bioc-biovizbase r-bioc-iranges (not considered)
    • Depends: r-bioc-biovizbase r-bioc-rsamtools (not considered)
    • Depends: r-bioc-biovizbase r-bioc-s4vectors (not considered)
    • Depends: r-bioc-biovizbase r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biovizbase.html
    • autopkgtest for r-bioc-biovizbase/1.50.0-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
    • 227 days old (needed 2 days)
• r-bioc-bsseq (- to 1.38.0+dfsg-1)
  • Migration status for r-bioc-bsseq (- to 1.38.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-bsgenome (not considered)
    • Depends: r-bioc-bsseq r-bioc-bsgenome (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-beachmat
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-delayedmatrixstats
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-hdf5array (not considered)
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-rhdf5 (not considered)
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-bsseq r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-bsseq r-bioc-beachmat
    • Depends: r-bioc-bsseq r-bioc-biostrings (not considered)
    • Depends: r-bioc-bsseq r-bioc-delayedarray
    • Depends: r-bioc-bsseq r-bioc-delayedmatrixstats
    • Depends: r-bioc-bsseq r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-bsseq r-bioc-genomicranges (not considered)
    • Depends: r-bioc-bsseq r-bioc-hdf5array (not considered)
    • Depends: r-bioc-bsseq r-bioc-iranges (not considered)
    • Depends: r-bioc-bsseq r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-bsseq r-bioc-s4vectors (not considered)
    • Depends: r-bioc-bsseq r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-bsseq.html
    • autopkgtest for r-bioc-bsseq/1.38.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
    • 227 days old (needed 2 days)
• r-bioc-dada2 (- to 1.30.0+dfsg-1)
  • Migration status for r-bioc-dada2 (- to 1.30.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-dada2 r-bioc-xvector (not considered)
    • Depends: r-bioc-dada2 r-bioc-xvector (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-dada2 r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-dada2 r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-dada2 r-bioc-shortread (not considered)
    • Depends: r-bioc-dada2 r-bioc-biostrings (not considered)
    • Depends: r-bioc-dada2 r-bioc-iranges (not considered)
    • Depends: r-bioc-dada2 r-bioc-shortread (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-dada2.html
    • autopkgtest for r-bioc-dada2/1.30.0+dfsg-1: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 227 days old (needed 2 days)
• r-bioc-deseq (- to 1.39.0-13)
  • Migration status for r-bioc-deseq (- to 1.39.0-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-deseq r-bioc-geneplotter (not considered)
    • Depends: r-bioc-deseq r-bioc-geneplotter (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-deseq r-bioc-genefilter (not considered)
    • Depends: r-bioc-deseq r-bioc-genefilter (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-deseq.html
    • autopkgtest for r-bioc-deseq/1.39.0-13: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 227 days old (needed 2 days)
• r-bioc-destiny (- to 3.16.0-1)
  • Migration status for r-bioc-destiny (- to 3.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-destiny/3.16.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
    • Build-Depends(-Arch): r-bioc-destiny r-bioc-singlecellexperiment (not considered)
    • Build-Depends(-Arch): r-bioc-destiny r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-destiny r-bioc-singlecellexperiment (not considered)
    • Depends: r-bioc-destiny r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-destiny.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 227 days old (needed 5 days)
• r-bioc-dexseq (- to 1.48.0+dfsg-1)
  • Migration status for r-bioc-dexseq (- 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-dexseq r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-dexseq r-bioc-summarizedexperiment (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-dexseq r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-dexseq r-bioc-biomart
    • Build-Depends(-Arch): r-bioc-dexseq r-bioc-deseq2 (not considered)
    • Build-Depends(-Arch): r-bioc-dexseq r-bioc-genefilter (not considered)
    • Build-Depends(-Arch): r-bioc-dexseq r-bioc-geneplotter
    • Build-Depends(-Arch): r-bioc-dexseq r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-dexseq r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-dexseq r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-dexseq r-bioc-s4vectors (not considered)
    • Depends: r-bioc-dexseq r-bioc-annotationdbi
    • Depends: r-bioc-dexseq r-bioc-biomart
    • Depends: r-bioc-dexseq r-bioc-deseq2 (not considered)
    • Depends: r-bioc-dexseq r-bioc-genefilter (not considered)
    • Depends: r-bioc-dexseq r-bioc-geneplotter
    • Depends: r-bioc-dexseq r-bioc-genomicranges (not considered)
    • Depends: r-bioc-dexseq r-bioc-iranges (not considered)
    • Depends: r-bioc-dexseq r-bioc-rsamtools (not considered)
    • Depends: r-bioc-dexseq r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-dexseq.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-dexseq/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
    • 227 days old (needed 2 days)
• r-bioc-dropletutils (- to 1.22.0+ds-1)
  • Migration status for r-bioc-dropletutils (- to 1.22.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-dropletutils/1.22.0+ds-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-beachmat
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-delayedmatrixstats
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-hdf5array (not considered)
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-rhdf5 (not considered)
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-scuttle (not considered)
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-singlecellexperiment (not considered)
    • Build-Depends(-Arch): r-bioc-dropletutils r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-dropletutils r-bioc-beachmat
    • Depends: r-bioc-dropletutils r-bioc-delayedarray
    • Depends: r-bioc-dropletutils r-bioc-delayedmatrixstats
    • Depends: r-bioc-dropletutils r-bioc-genomicranges (not considered)
    • Depends: r-bioc-dropletutils r-bioc-hdf5array (not considered)
    • Depends: r-bioc-dropletutils r-bioc-iranges (not considered)
    • Depends: r-bioc-dropletutils r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-dropletutils r-bioc-s4vectors (not considered)
    • Depends: r-bioc-dropletutils r-bioc-scuttle (not considered)
    • Depends: r-bioc-dropletutils r-bioc-singlecellexperiment (not considered)
    • Depends: r-bioc-dropletutils r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-dropletutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 227 days old (needed 5 days)
• r-bioc-edaseq (- to 2.36.0+dfsg-1)
  • Migration status for r-bioc-edaseq (- to 2.36.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-edaseq r-bioc-shortread (not considered)
    • Depends: r-bioc-edaseq r-bioc-shortread (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-edaseq r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-edaseq r-bioc-biomart
    • Build-Depends(-Arch): r-bioc-edaseq r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-edaseq r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-edaseq r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-edaseq r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-edaseq r-bioc-rsamtools (not considered)
    • Depends: r-bioc-edaseq r-bioc-annotationdbi
    • Depends: r-bioc-edaseq r-bioc-biomart
    • Depends: r-bioc-edaseq r-bioc-biostrings (not considered)
    • Depends: r-bioc-edaseq r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-edaseq r-bioc-genomicranges (not considered)
    • Depends: r-bioc-edaseq r-bioc-iranges (not considered)
    • Depends: r-bioc-edaseq r-bioc-rsamtools (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-edaseq.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-edaseq/2.36.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
    • 227 days old (needed 2 days)
• r-bioc-ensembldb (- to 2.26.0+dfsg-1)
  • Migration status for r-bioc-ensembldb (- to 2.26.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-ensembldb r-bioc-s4vectors (not considered)
    • Depends: r-bioc-ensembldb r-bioc-s4vectors (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-ensembldb r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-ensembldb r-bioc-annotationfilter
    • Build-Depends(-Arch): r-bioc-ensembldb r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-ensembldb r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-ensembldb r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-ensembldb r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-ensembldb r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-ensembldb r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-ensembldb r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-ensembldb r-bioc-annotationdbi
    • Depends: r-bioc-ensembldb r-bioc-annotationfilter
    • Depends: r-bioc-ensembldb r-bioc-biostrings (not considered)
    • Depends: r-bioc-ensembldb r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-ensembldb r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-ensembldb r-bioc-genomicranges (not considered)
    • Depends: r-bioc-ensembldb r-bioc-iranges (not considered)
    • Depends: r-bioc-ensembldb r-bioc-rsamtools (not considered)
    • Depends: r-bioc-ensembldb r-bioc-rtracklayer (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-ensembldb.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-ensembldb/2.26.0+dfsg-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 ♻, 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 ♻
    • 227 days old (needed 5 days)
• r-bioc-experimenthub (- to 2.10.0+ds-1)
  • Migration status for r-bioc-experimenthub (- to 2.10.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-experimenthub/2.10.0+ds-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
    • Build-Depends(-Arch): r-bioc-experimenthub r-bioc-annotationhub (not considered)
    • Build-Depends(-Arch): r-bioc-experimenthub r-bioc-s4vectors (not considered)
    • Depends: r-bioc-experimenthub r-bioc-annotationhub (not considered)
    • Depends: r-bioc-experimenthub r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-experimenthub.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 227 days old (needed 5 days)
• r-bioc-fishpond (- to 2.8.0+ds-1)
  • Migration status for r-bioc-fishpond (- to 2.8.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-fishpond/2.8.0+ds-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
    • Build-Depends(-Arch): r-bioc-fishpond r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-fishpond r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-fishpond r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-fishpond r-bioc-singlecellexperiment (not considered)
    • Build-Depends(-Arch): r-bioc-fishpond r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-fishpond r-bioc-genomicranges (not considered)
    • Depends: r-bioc-fishpond r-bioc-iranges (not considered)
    • Depends: r-bioc-fishpond r-bioc-s4vectors (not considered)
    • Depends: r-bioc-fishpond r-bioc-singlecellexperiment (not considered)
    • Depends: r-bioc-fishpond r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-fishpond.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 227 days old (needed 5 days)
• r-bioc-genefilter (- to 1.84.0-1)
  • Migration status for r-bioc-genefilter (- to 1.84.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-genefilter would introduce bugs in testing: #1071341
    • Build-Depends(-Arch): r-bioc-genefilter r-bioc-annotate
    • Build-Depends(-Arch): r-bioc-genefilter r-bioc-annotationdbi
    • Depends: r-bioc-genefilter r-bioc-annotate
    • Depends: r-bioc-genefilter r-bioc-annotationdbi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genefilter.html
    • autopkgtest for r-bioc-genefilter/1.84.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 227 days old (needed 2 days)
• r-bioc-genelendatabase (- to 1.38.0-1)
  • Migration status for r-bioc-genelendatabase (- to 1.38.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-bioc-genelendatabase r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-genelendatabase r-bioc-rtracklayer (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-genelendatabase r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-genelendatabase r-bioc-genomicfeatures (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genelendatabase.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-genelendatabase/1.38.0-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
    • 227 days old (needed 2 days)
• r-bioc-geneplotter (- to 1.80.0+dfsg-1)
  • Migration status for r-bioc-geneplotter (- to 1.80.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-geneplotter r-bioc-annotationdbi (not considered)
    • Depends: r-bioc-geneplotter r-bioc-annotationdbi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-geneplotter r-bioc-annotate
    • Depends: r-bioc-geneplotter r-bioc-annotate
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-geneplotter.html
    • autopkgtest for r-bioc-geneplotter/1.80.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
    • 227 days old (needed 2 days)
• r-bioc-genomicfiles (- to 1.38.0+dfsg-1)
  • Migration status for r-bioc-genomicfiles (- to 1.38.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-genomicfiles r-bioc-variantannotation (not considered)
    • Depends: r-bioc-genomicfiles r-bioc-variantannotation (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-genomicfiles r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfiles r-bioc-genomicalignments
    • Build-Depends(-Arch): r-bioc-genomicfiles r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfiles r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfiles r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfiles r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfiles r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-genomicfiles r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-genomicfiles r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-genomicfiles r-bioc-genomicalignments
    • Depends: r-bioc-genomicfiles r-bioc-genomicranges (not considered)
    • Depends: r-bioc-genomicfiles r-bioc-iranges (not considered)
    • Depends: r-bioc-genomicfiles r-bioc-rsamtools (not considered)
    • Depends: r-bioc-genomicfiles r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-genomicfiles r-bioc-s4vectors (not considered)
    • Depends: r-bioc-genomicfiles r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genomicfiles.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-genomicfiles/1.38.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
    • 227 days old (needed 2 days)
• r-bioc-go.db (- to 3.18.0-1)
  • Migration status for r-bioc-go.db (- 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): r-bioc-go.db r-bioc-annotationdbi (not considered)
    • Depends: r-bioc-go.db r-bioc-annotationdbi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-go.db.html
    • autopkgtest for r-bioc-go.db/3.18.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
    • 227 days old (needed 2 days)
• r-bioc-goseq (- to 1.54.0-1)
  • Migration status for r-bioc-goseq (- to 1.54.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-goseq/1.54.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
    • Build-Depends(-Arch): r-bioc-goseq r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-goseq r-bioc-genelendatabase
    • Build-Depends(-Arch): r-bioc-goseq r-bioc-go.db
    • Depends: r-bioc-goseq r-bioc-annotationdbi
    • Depends: r-bioc-goseq r-bioc-genelendatabase
    • Depends: r-bioc-goseq r-bioc-go.db
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-goseq.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 ♻
    • 227 days old (needed 5 days)
• r-bioc-grohmm (- to 1.36.0-1)
  • Migration status for r-bioc-grohmm (- to 1.36.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-bioc-grohmm r-bioc-genomicalignments (not considered)
    • Depends: r-bioc-grohmm r-bioc-genomicalignments (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-grohmm r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-grohmm r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-grohmm r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-grohmm r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-grohmm r-bioc-s4vectors (not considered)
    • Depends: r-bioc-grohmm r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-grohmm r-bioc-genomicranges (not considered)
    • Depends: r-bioc-grohmm r-bioc-iranges (not considered)
    • Depends: r-bioc-grohmm r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-grohmm r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-grohmm.html
    • autopkgtest for r-bioc-grohmm/1.36.0-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
    • 227 days old (needed 2 days)
• r-bioc-gseabase (- to 1.64.0+ds-1)
  • Migration status for r-bioc-gseabase (- to 1.64.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-gseabase r-bioc-annotationdbi (not considered)
    • Depends: r-bioc-gseabase r-bioc-annotationdbi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-gseabase r-bioc-annotate
    • Depends: r-bioc-gseabase r-bioc-annotate
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-gseabase.html
    • autopkgtest for r-bioc-gseabase/1.64.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 227 days old (needed 2 days)
• r-bioc-gsva (- to 1.50.0+ds-1)
  • Migration status for r-bioc-gsva (- to 1.50.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-gsva r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-gsva r-bioc-summarizedexperiment (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-gsva r-bioc-biocsingular
    • Build-Depends(-Arch): r-bioc-gsva r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-gsva r-bioc-delayedmatrixstats
    • Build-Depends(-Arch): r-bioc-gsva r-bioc-gseabase
    • Build-Depends(-Arch): r-bioc-gsva r-bioc-hdf5array (not considered)
    • Build-Depends(-Arch): r-bioc-gsva r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-gsva r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-gsva r-bioc-singlecellexperiment (not considered)
    • Depends: r-bioc-gsva r-bioc-biocsingular
    • Depends: r-bioc-gsva r-bioc-delayedarray
    • Depends: r-bioc-gsva r-bioc-delayedmatrixstats
    • Depends: r-bioc-gsva r-bioc-gseabase
    • Depends: r-bioc-gsva r-bioc-hdf5array (not considered)
    • Depends: r-bioc-gsva r-bioc-iranges (not considered)
    • Depends: r-bioc-gsva r-bioc-s4vectors (not considered)
    • Depends: r-bioc-gsva r-bioc-singlecellexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-gsva.html
    • autopkgtest for r-bioc-gsva/1.50.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 227 days old (needed 2 days)
• r-bioc-htsfilter (- to 1.42.0+dfsg-1)
  • Migration status for r-bioc-htsfilter (- to 1.42.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-htsfilter/1.42.0+dfsg-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
    • Build-Depends(-Arch): r-bioc-htsfilter r-bioc-deseq2 (not considered)
    • Depends: r-bioc-htsfilter r-bioc-deseq2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-htsfilter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 227 days old (needed 5 days)
• r-bioc-ioniser (- to 2.26.0+dfsg-1)
  • Migration status for r-bioc-ioniser (- to 2.26.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-xvector (not considered)
    • Depends: r-bioc-ioniser r-bioc-xvector (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-ioniser r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-ioniser r-bioc-rhdf5 (not considered)
    • Build-Depends(-Arch): r-bioc-ioniser r-bioc-shortread (not considered)
    • Depends: r-bioc-ioniser r-bioc-biostrings (not considered)
    • Depends: r-bioc-ioniser r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-ioniser r-bioc-shortread (not considered)
  • 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.26.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
    • 227 days old (needed 2 days)
• r-bioc-mofa (- to 1.6.1+dfsg-12)
  • Migration status for r-bioc-mofa (- to 1.6.1+dfsg-12): 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-multiassayexperiment (not considered)
    • Depends: r-bioc-mofa r-bioc-multiassayexperiment (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-mofa r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-mofa r-bioc-rhdf5 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-mofa.html
    • autopkgtest for r-bioc-mofa/1.6.1+dfsg-12: amd64: No tests, superficial or 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 ♻
    • 227 days old (needed 5 days)
• r-bioc-multiassayexperiment (- to 1.28.0+dfsg-1)
  • Migration status for r-bioc-multiassayexperiment (- to 1.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-multiassayexperiment r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-multiassayexperiment r-bioc-summarizedexperiment (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-multiassayexperiment r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-multiassayexperiment r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-multiassayexperiment r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-multiassayexperiment r-bioc-s4vectors (not considered)
    • Depends: r-bioc-multiassayexperiment r-bioc-delayedarray
    • Depends: r-bioc-multiassayexperiment r-bioc-genomicranges (not considered)
    • Depends: r-bioc-multiassayexperiment r-bioc-iranges (not considered)
    • Depends: r-bioc-multiassayexperiment r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-multiassayexperiment.html
    • autopkgtest for r-bioc-multiassayexperiment/1.28.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
    • 227 days old (needed 2 days)
• r-bioc-mutationalpatterns (- to 3.12.0+dfsg-1)
  • Migration status for r-bioc-mutationalpatterns (- to 3.12.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-mutationalpatterns would introduce bugs in testing: #1070842
    • autopkgtest for r-bioc-mutationalpatterns/3.12.0+dfsg-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): r-bioc-mutationalpatterns r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-mutationalpatterns r-bioc-bsgenome
    • Build-Depends(-Arch): r-bioc-mutationalpatterns r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-mutationalpatterns r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-mutationalpatterns r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-mutationalpatterns r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-mutationalpatterns r-bioc-variantannotation (not considered)
    • Depends: r-bioc-mutationalpatterns r-bioc-biostrings (not considered)
    • Depends: r-bioc-mutationalpatterns r-bioc-bsgenome
    • Depends: r-bioc-mutationalpatterns r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-mutationalpatterns r-bioc-genomicranges (not considered)
    • Depends: r-bioc-mutationalpatterns r-bioc-iranges (not considered)
    • Depends: r-bioc-mutationalpatterns r-bioc-s4vectors (not considered)
    • Depends: r-bioc-mutationalpatterns r-bioc-variantannotation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-mutationalpatterns.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 ♻
    • 227 days old (needed 5 days)
• r-bioc-oligo (- to 1.66.0+ds-1)
  • Migration status for r-bioc-oligo (- to 1.66.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-oligo would introduce bugs in testing: #1071344
    • Build-Depends(-Arch): r-bioc-oligo r-bioc-affxparser (not considered)
    • Build-Depends(-Arch): r-bioc-oligo r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-oligo r-bioc-oligoclasses
    • Depends: r-bioc-oligo r-bioc-affxparser (not considered)
    • Depends: r-bioc-oligo r-bioc-biostrings (not considered)
    • Depends: r-bioc-oligo r-bioc-oligoclasses
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-oligo.html
    • autopkgtest for r-bioc-oligo/1.66.0+ds-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
    • 227 days old (needed 2 days)
• r-bioc-oligoclasses (- to 1.64.0-1)
  • Migration status for r-bioc-oligoclasses (- to 1.64.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-bioc-oligoclasses r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-oligoclasses r-bioc-summarizedexperiment (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-oligoclasses r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-oligoclasses r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-oligoclasses r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-oligoclasses r-bioc-s4vectors (not considered)
    • Depends: r-bioc-oligoclasses r-bioc-biostrings (not considered)
    • Depends: r-bioc-oligoclasses r-bioc-genomicranges (not considered)
    • Depends: r-bioc-oligoclasses r-bioc-iranges (not considered)
    • Depends: r-bioc-oligoclasses r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-oligoclasses.html
    • autopkgtest for r-bioc-oligoclasses/1.64.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
    • 227 days old (needed 2 days)
• r-bioc-organismdbi (- to 1.44.0+dfsg-1)
  • Migration status for r-bioc-organismdbi (- to 1.44.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-organismdbi/1.44.0+dfsg-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
    • Build-Depends(-Arch): r-bioc-organismdbi r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-organismdbi r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-organismdbi r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-organismdbi r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-organismdbi r-bioc-s4vectors (not considered)
    • Depends: r-bioc-organismdbi r-bioc-annotationdbi
    • Depends: r-bioc-organismdbi r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-organismdbi r-bioc-genomicranges (not considered)
    • Depends: r-bioc-organismdbi r-bioc-iranges (not considered)
    • Depends: r-bioc-organismdbi r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-organismdbi.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 ♻
    • 227 days old (needed 5 days)
• r-bioc-purecn (- to 2.8.1+dfsg-1)
  • Migration status for r-bioc-purecn (- to 2.8.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-bioc-purecn r-bioc-variantannotation (not considered)
    • Depends: r-bioc-purecn r-bioc-variantannotation (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-purecn r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-purecn r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-purecn r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-purecn r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-purecn r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-purecn r-bioc-rhdf5 (not considered)
    • Build-Depends(-Arch): r-bioc-purecn r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-purecn r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-purecn r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-purecn r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-purecn r-bioc-biostrings (not considered)
    • Depends: r-bioc-purecn r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-purecn r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-purecn r-bioc-genomicranges (not considered)
    • Depends: r-bioc-purecn r-bioc-iranges (not considered)
    • Depends: r-bioc-purecn r-bioc-rhdf5 (not considered)
    • Depends: r-bioc-purecn r-bioc-rsamtools (not considered)
    • Depends: r-bioc-purecn r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-purecn r-bioc-s4vectors (not considered)
    • Depends: r-bioc-purecn r-bioc-summarizedexperiment (not considered)
  • 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.8.1+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
    • 227 days old (needed 2 days)
• r-bioc-rcpi (- to 1.38.0+ds-1)
  • Migration status for r-bioc-rcpi (- to 1.38.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-rcpi r-bioc-gosemsim (not considered)
    • Depends: r-bioc-rcpi r-bioc-gosemsim (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-rcpi r-bioc-biostrings (not considered)
    • Depends: r-bioc-rcpi r-bioc-biostrings (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rcpi.html
    • autopkgtest for r-bioc-rcpi/1.38.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 227 days old (needed 2 days)
• r-bioc-rtracklayer (- to 1.62.0-1)
  • Migration status for r-bioc-rtracklayer (- to 1.62.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-rtracklayer would introduce bugs in testing: #1071347
    • Build-Depends(-Arch): r-bioc-rtracklayer r-bioc-biocio
    • Build-Depends(-Arch): r-bioc-rtracklayer r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-rtracklayer r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-rtracklayer r-bioc-genomicalignments
    • Build-Depends(-Arch): r-bioc-rtracklayer r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-rtracklayer r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-rtracklayer r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-rtracklayer r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-rtracklayer r-bioc-xvector (not considered)
    • Build-Depends(-Arch): r-bioc-rtracklayer r-cran-restfulr
    • Depends: r-bioc-rtracklayer r-bioc-biocio
    • Depends: r-bioc-rtracklayer r-bioc-biostrings (not considered)
    • Depends: r-bioc-rtracklayer r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-rtracklayer r-bioc-genomicalignments
    • Depends: r-bioc-rtracklayer r-bioc-genomicranges (not considered)
    • Depends: r-bioc-rtracklayer r-bioc-iranges (not considered)
    • Depends: r-bioc-rtracklayer r-bioc-rsamtools (not considered)
    • Depends: r-bioc-rtracklayer r-bioc-s4vectors (not considered)
    • Depends: r-bioc-rtracklayer r-bioc-xvector (not considered)
    • Depends: r-bioc-rtracklayer r-cran-restfulr
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rtracklayer.html
    • autopkgtest for r-bioc-rtracklayer/1.62.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: 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
    • 227 days old (needed 2 days)
• r-bioc-saturn (- to 1.10.0+dfsg-1)
  • Migration status for r-bioc-saturn (- to 1.10.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-saturn/1.10.0+dfsg-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
    • Build-Depends(-Arch): r-bioc-saturn r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-saturn r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-saturn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 227 days old (needed 5 days)
• r-bioc-scuttle (- to 1.12.0+dfsg-1)
  • Migration status for r-bioc-scuttle (- to 1.12.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-scuttle/1.12.0+dfsg-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
    • Build-Depends(-Arch): r-bioc-scuttle r-bioc-beachmat
    • Build-Depends(-Arch): r-bioc-scuttle r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-scuttle r-bioc-delayedmatrixstats
    • Build-Depends(-Arch): r-bioc-scuttle r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-scuttle r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-scuttle r-bioc-singlecellexperiment (not considered)
    • Build-Depends(-Arch): r-bioc-scuttle r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-scuttle r-bioc-beachmat
    • Depends: r-bioc-scuttle r-bioc-delayedarray
    • Depends: r-bioc-scuttle r-bioc-delayedmatrixstats
    • Depends: r-bioc-scuttle r-bioc-genomicranges (not considered)
    • Depends: r-bioc-scuttle r-bioc-s4vectors (not considered)
    • Depends: r-bioc-scuttle r-bioc-singlecellexperiment (not considered)
    • Depends: r-bioc-scuttle r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-scuttle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 227 days old (needed 5 days)
• r-bioc-singlecellexperiment (- to 1.24.0+ds-1)
  • Migration status for r-bioc-singlecellexperiment (- to 1.24.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-singlecellexperiment/1.24.0+ds-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
    • Build-Depends(-Arch): r-bioc-singlecellexperiment r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-singlecellexperiment r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-singlecellexperiment r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-singlecellexperiment r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-singlecellexperiment r-bioc-delayedarray
    • Depends: r-bioc-singlecellexperiment r-bioc-genomicranges (not considered)
    • Depends: r-bioc-singlecellexperiment r-bioc-s4vectors (not considered)
    • Depends: r-bioc-singlecellexperiment r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-singlecellexperiment.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 227 days old (needed 5 days)
• r-bioc-sva (- to 3.50.0-1)
  • Migration status for r-bioc-sva (- to 3.50.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-bioc-sva r-bioc-genefilter (not considered)
    • Depends: r-bioc-sva r-bioc-genefilter (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-sva.html
    • autopkgtest for r-bioc-sva/3.50.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
    • 227 days old (needed 2 days)
• r-bioc-tcgabiolinks (- to 2.30.0+dfsg-1)
  • Migration status for r-bioc-tcgabiolinks (- to 2.30.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-tcgabiolinks/2.30.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): r-bioc-tcgabiolinks r-bioc-biomart
    • Build-Depends(-Arch): r-bioc-tcgabiolinks r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-tcgabiolinks r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-tcgabiolinks r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-tcgabiolinks r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-tcgabiolinks r-bioc-biomart
    • Depends: r-bioc-tcgabiolinks r-bioc-genomicranges (not considered)
    • Depends: r-bioc-tcgabiolinks r-bioc-iranges (not considered)
    • Depends: r-bioc-tcgabiolinks r-bioc-s4vectors (not considered)
    • Depends: r-bioc-tcgabiolinks r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-tcgabiolinks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 227 days old (needed 5 days)
• r-bioc-tfbstools (- to 1.40.0+dfsg-1)
  • Migration status for r-bioc-tfbstools (- 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-tfbstools r-bioc-xvector (not considered)
    • Depends: r-bioc-tfbstools r-bioc-xvector (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-tfbstools r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-tfbstools r-bioc-bsgenome
    • Build-Depends(-Arch): r-bioc-tfbstools r-bioc-cner
    • Build-Depends(-Arch): r-bioc-tfbstools r-bioc-dirichletmultinomial
    • Build-Depends(-Arch): r-bioc-tfbstools r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-tfbstools r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-tfbstools r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-tfbstools r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-tfbstools r-bioc-s4vectors (not considered)
    • Depends: r-bioc-tfbstools r-bioc-biostrings (not considered)
    • Depends: r-bioc-tfbstools r-bioc-bsgenome
    • Depends: r-bioc-tfbstools r-bioc-cner
    • Depends: r-bioc-tfbstools r-bioc-dirichletmultinomial
    • Depends: r-bioc-tfbstools r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-tfbstools r-bioc-genomicranges (not considered)
    • Depends: r-bioc-tfbstools r-bioc-iranges (not considered)
    • Depends: r-bioc-tfbstools r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-tfbstools r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-tfbstools.html
    • autopkgtest for r-bioc-tfbstools/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
    • 227 days old (needed 2 days)
• r-bioc-variantannotation (- to 1.48.1-1)
  • Migration status for r-bioc-variantannotation (- to 1.48.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-variantannotation would introduce bugs in testing: #1071352
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-bsgenome
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-genomicfeatures (not considered)
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-rsamtools (not considered)
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-summarizedexperiment (not considered)
    • Build-Depends(-Arch): r-bioc-variantannotation r-bioc-xvector (not considered)
    • Depends: r-bioc-variantannotation r-bioc-annotationdbi
    • Depends: r-bioc-variantannotation r-bioc-biostrings (not considered)
    • Depends: r-bioc-variantannotation r-bioc-bsgenome
    • Depends: r-bioc-variantannotation r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-variantannotation r-bioc-genomicfeatures (not considered)
    • Depends: r-bioc-variantannotation r-bioc-genomicranges (not considered)
    • Depends: r-bioc-variantannotation r-bioc-iranges (not considered)
    • Depends: r-bioc-variantannotation r-bioc-rsamtools (not considered)
    • Depends: r-bioc-variantannotation r-bioc-rtracklayer (not considered)
    • Depends: r-bioc-variantannotation r-bioc-s4vectors (not considered)
    • Depends: r-bioc-variantannotation r-bioc-summarizedexperiment (not considered)
    • Depends: r-bioc-variantannotation r-bioc-xvector (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-variantannotation.html
    • autopkgtest for r-bioc-variantannotation/1.48.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: 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
    • 227 days old (needed 2 days)
• r-bioc-affxparser (- to 1.74.0-1)
  • Migration status for r-bioc-affxparser (- to 1.74.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-affxparser would introduce bugs in testing: #1071340
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-affxparser.html
    • autopkgtest for r-bioc-affxparser/1.74.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 228 days old (needed 2 days)
• r-bioc-altcdfenvs (- to 1:2.64.0-1)
  • Migration status for r-bioc-altcdfenvs (- to 1:2.64.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-bioc-altcdfenvs r-bioc-s4vectors (not considered)
    • Depends: r-bioc-altcdfenvs r-bioc-s4vectors (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-altcdfenvs r-bioc-biostrings (not considered)
    • Depends: r-bioc-altcdfenvs r-bioc-biostrings (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-altcdfenvs.html
    • autopkgtest for r-bioc-altcdfenvs/1:2.64.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
    • 228 days old (needed 2 days)
• r-bioc-annotate (- to 1.80.0+dfsg-1)
  • Migration status for r-bioc-annotate (- to 1.80.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-annotate r-bioc-annotationdbi (not considered)
    • Depends: r-bioc-annotate r-bioc-annotationdbi (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-annotate.html
    • autopkgtest for r-bioc-annotate/1.80.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
    • 228 days old (needed 2 days)
• r-bioc-annotationdbi (- to 1.64.1-1)
  • Migration status for r-bioc-annotationdbi (- to 1.64.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-annotationdbi r-bioc-s4vectors (not considered)
    • Depends: r-bioc-annotationdbi r-bioc-s4vectors (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-annotationdbi r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-annotationdbi r-bioc-keggrest
    • Depends: r-bioc-annotationdbi r-bioc-iranges (not considered)
    • Depends: r-bioc-annotationdbi r-bioc-keggrest
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-annotationdbi.html
    • autopkgtest for r-bioc-annotationdbi/1.64.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
    • 228 days old (needed 2 days)
• r-bioc-annotationfilter (- to 1.26.0+dfsg-1)
  • Migration status for r-bioc-annotationfilter (- to 1.26.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-annotationfilter r-bioc-genomicranges (not considered)
    • Depends: r-bioc-annotationfilter r-bioc-genomicranges (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-annotationfilter.html
    • autopkgtest for r-bioc-annotationfilter/1.26.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
    • 228 days old (needed 2 days)
• r-bioc-annotationhub (- to 3.10.0+dfsg-1)
  • Migration status for r-bioc-annotationhub (- to 3.10.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-annotationhub/3.10.0+dfsg-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
    • Build-Depends(-Arch): r-bioc-annotationhub r-bioc-annotationdbi
    • Build-Depends(-Arch): r-bioc-annotationhub r-bioc-s4vectors (not considered)
    • Depends: r-bioc-annotationhub r-bioc-annotationdbi
    • Depends: r-bioc-annotationhub r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-annotationhub.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 228 days old (needed 5 days)
• r-bioc-biocio (- to 1.12.0+dfsg-1)
  • Migration status for r-bioc-biocio (- to 1.12.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-biocio r-bioc-s4vectors (not considered)
    • Depends: r-bioc-biocio r-bioc-s4vectors (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biocio.html
    • autopkgtest for r-bioc-biocio/1.12.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
    • 228 days old (needed 2 days)
• r-bioc-biocsingular (- to 1.18.0+ds-1)
  • Migration status for r-bioc-biocsingular (- to 1.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-biocsingular r-bioc-delayedarray (not considered)
    • Depends: r-bioc-biocsingular r-bioc-delayedarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-biocsingular r-bioc-beachmat
    • Build-Depends(-Arch): r-bioc-biocsingular r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-biocsingular r-bioc-scaledmatrix
    • Depends: r-bioc-biocsingular r-bioc-beachmat
    • Depends: r-bioc-biocsingular r-bioc-s4vectors (not considered)
    • Depends: r-bioc-biocsingular r-bioc-scaledmatrix
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biocsingular.html
    • autopkgtest for r-bioc-biocsingular/1.18.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 228 days old (needed 2 days)
• r-bioc-biomformat (- to 1.30.0+dfsg-1)
  • Migration status for r-bioc-biomformat (- to 1.30.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)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-biomformat.html
    • autopkgtest for r-bioc-biomformat/1.30.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
    • 228 days old (needed 2 days)
• r-bioc-bluster (- to 1.12.0+dfsg-1)
  • Migration status for r-bioc-bluster (- to 1.12.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-bluster/1.12.0+dfsg-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
    • Build-Depends(-Arch): r-bioc-bluster r-bioc-biocneighbors
    • Build-Depends(-Arch): r-bioc-bluster r-bioc-s4vectors (not considered)
    • Depends: r-bioc-bluster r-bioc-biocneighbors
    • Depends: r-bioc-bluster r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-bluster.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 228 days old (needed 5 days)
• r-bioc-complexheatmap (- to 2.18.0+dfsg-1)
  • Migration status for r-bioc-complexheatmap (- to 2.18.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-complexheatmap r-bioc-iranges (not considered)
    • Depends: r-bioc-complexheatmap r-bioc-iranges (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-complexheatmap.html
    • autopkgtest for r-bioc-complexheatmap/2.18.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
    • 228 days old (needed 2 days)
• r-bioc-delayedarray (- to 0.28.0+dfsg-1)
  • Migration status for r-bioc-delayedarray (- to 0.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-delayedarray r-bioc-sparsearray (not considered)
    • Depends: r-bioc-delayedarray r-bioc-sparsearray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-delayedarray r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-delayedarray r-bioc-s4arrays (not considered)
    • Build-Depends(-Arch): r-bioc-delayedarray r-bioc-s4vectors (not considered)
    • Depends: r-bioc-delayedarray r-bioc-iranges (not considered)
    • Depends: r-bioc-delayedarray r-bioc-s4arrays (not considered)
    • Depends: r-bioc-delayedarray r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-delayedarray.html
    • autopkgtest for r-bioc-delayedarray/0.28.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
    • 228 days old (needed 2 days)
• r-bioc-delayedmatrixstats (- to 1.24.0+ds-1)
  • Migration status for r-bioc-delayedmatrixstats (- 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-delayedmatrixstats r-bioc-delayedarray (not considered)
    • Depends: r-bioc-delayedmatrixstats r-bioc-delayedarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-delayedmatrixstats r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-delayedmatrixstats r-bioc-s4vectors (not considered)
    • Depends: r-bioc-delayedmatrixstats r-bioc-iranges (not considered)
    • Depends: r-bioc-delayedmatrixstats r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-delayedmatrixstats.html
    • autopkgtest for r-bioc-delayedmatrixstats/1.24.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 228 days old (needed 2 days)
• r-bioc-dirichletmultinomial (- to 1.44.0-1)
  • Migration status for r-bioc-dirichletmultinomial (- to 1.44.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-bioc-dirichletmultinomial r-bioc-s4vectors (not considered)
    • Depends: r-bioc-dirichletmultinomial r-bioc-s4vectors (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-dirichletmultinomial r-bioc-iranges (not considered)
    • Depends: r-bioc-dirichletmultinomial r-bioc-iranges (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-dirichletmultinomial.html
    • autopkgtest for r-bioc-dirichletmultinomial/1.44.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
    • 228 days old (needed 2 days)
• r-bioc-drimseq (- to 1.30.0-1)
  • Migration status for r-bioc-drimseq (- to 1.30.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-bioc-drimseq r-bioc-s4vectors (not considered)
    • Depends: r-bioc-drimseq r-bioc-s4vectors (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-drimseq r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-drimseq r-bioc-iranges (not considered)
    • Depends: r-bioc-drimseq r-bioc-genomicranges (not considered)
    • Depends: r-bioc-drimseq r-bioc-iranges (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-drimseq.html
    • autopkgtest for r-bioc-drimseq/1.30.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
    • 228 days old (needed 2 days)
• r-bioc-eir (- to 1.42.0+ds-1)
  • Migration status for r-bioc-eir (- to 1.42.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-eir would introduce bugs in testing: #1074528
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-eir.html
    • autopkgtest for r-bioc-eir/1.42.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 228 days old (needed 2 days)
• r-bioc-genomicranges (- to 1.54.1+dfsg-1)
  • Migration status for r-bioc-genomicranges (- to 1.54.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-genomicranges/1.54.1+dfsg-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
    • Build-Depends(-Arch): r-bioc-genomicranges r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-genomicranges r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-genomicranges r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-genomicranges r-bioc-xvector (not considered)
    • Depends: r-bioc-genomicranges r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-genomicranges r-bioc-iranges (not considered)
    • Depends: r-bioc-genomicranges r-bioc-s4vectors (not considered)
    • Depends: r-bioc-genomicranges r-bioc-xvector (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-genomicranges.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 228 days old (needed 5 days)
• r-bioc-iranges (- to 2.36.0-1)
  • Migration status for r-bioc-iranges (- to 2.36.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-iranges would introduce bugs in testing: #1070841
    • autopkgtest for r-bioc-iranges/2.36.0-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): r-bioc-iranges r-bioc-s4vectors (not considered)
    • Depends: r-bioc-iranges r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-iranges.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 228 days old (needed 5 days)
• r-bioc-keggrest (- to 1.42.0+dfsg-1)
  • Migration status for r-bioc-keggrest (- to 1.42.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-keggrest r-bioc-biostrings (not considered)
    • Depends: r-bioc-keggrest r-bioc-biostrings (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-keggrest.html
    • autopkgtest for r-bioc-keggrest/1.42.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
    • 228 days old (needed 2 days)
• r-bioc-phyloseq (- to 1.46.0+dfsg-1)
  • Migration status for r-bioc-phyloseq (- to 1.46.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-phyloseq/1.46.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): r-bioc-phyloseq r-bioc-biomformat
    • Build-Depends(-Arch): r-bioc-phyloseq r-bioc-biostrings (not considered)
    • Depends: r-bioc-phyloseq r-bioc-biomformat
    • Depends: r-bioc-phyloseq r-bioc-biostrings (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-phyloseq.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 228 days old (needed 5 days)
• r-bioc-pwmenrich (- to 4.38.0-1)
  • Migration status for r-bioc-pwmenrich (- to 4.38.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-pwmenrich/4.38.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
    • Build-Depends(-Arch): r-bioc-pwmenrich r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-pwmenrich r-bioc-s4vectors (not considered)
    • Depends: r-bioc-pwmenrich r-bioc-biostrings (not considered)
    • Depends: r-bioc-pwmenrich r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-pwmenrich.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 228 days old (needed 5 days)
• r-bioc-qtlizer (- to 1.16.0+dfsg-1)
  • Migration status for r-bioc-qtlizer (- 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-qtlizer r-bioc-genomicranges (not considered)
    • Depends: r-bioc-qtlizer r-bioc-genomicranges (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-qtlizer.html
    • autopkgtest for r-bioc-qtlizer/1.16.0+dfsg-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
    • 228 days old (needed 2 days)
• r-bioc-residualmatrix (- to 1.12.0+dfsg-1)
  • Migration status for r-bioc-residualmatrix (- to 1.12.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-residualmatrix r-bioc-delayedarray (not considered)
    • Depends: r-bioc-residualmatrix r-bioc-delayedarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-residualmatrix r-bioc-s4vectors (not considered)
    • Depends: r-bioc-residualmatrix r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-residualmatrix.html
    • autopkgtest for r-bioc-residualmatrix/1.12.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
    • 228 days old (needed 2 days)
• r-bioc-rsamtools (- to 2.18.0+dfsg-1)
  • Migration status for r-bioc-rsamtools (- to 2.18.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-rsamtools would introduce bugs in testing: #1071346
    • Build-Depends(-Arch): r-bioc-rsamtools r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-bioc-rsamtools r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-rsamtools r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-rsamtools r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-rsamtools r-bioc-s4vectors (not considered)
    • Build-Depends(-Arch): r-bioc-rsamtools r-bioc-xvector (not considered)
    • Depends: r-bioc-rsamtools r-bioc-biostrings (not considered)
    • Depends: r-bioc-rsamtools r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-rsamtools r-bioc-genomicranges (not considered)
    • Depends: r-bioc-rsamtools r-bioc-iranges (not considered)
    • Depends: r-bioc-rsamtools r-bioc-s4vectors (not considered)
    • Depends: r-bioc-rsamtools r-bioc-xvector (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-rsamtools.html
    • autopkgtest for r-bioc-rsamtools/2.18.0+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: 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
    • 228 days old (needed 2 days)
• r-bioc-s4arrays (- to 1.2.0+dfsg-1)
  • Migration status for r-bioc-s4arrays (- to 1.2.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-s4arrays would introduce bugs in testing: #1071348
    • Build-Depends(-Arch): r-bioc-s4arrays r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-s4arrays r-bioc-s4vectors (not considered)
    • Depends: r-bioc-s4arrays r-bioc-iranges (not considered)
    • Depends: r-bioc-s4arrays r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-s4arrays.html
    • autopkgtest for r-bioc-s4arrays/1.2.0+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 228 days old (needed 2 days)
• r-bioc-s4vectors (- to 0.40.2+dfsg-1)
  • Migration status for r-bioc-s4vectors (- to 0.40.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-s4vectors would introduce bugs in testing: #1070843, #1071349
    • autopkgtest for r-bioc-s4vectors/0.40.2+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-s4vectors.html
    • 228 days old (needed 5 days)
• r-bioc-scaledmatrix (- to 1.10.0+dfsg-1)
  • Migration status for r-bioc-scaledmatrix (- to 1.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-scaledmatrix r-bioc-delayedarray (not considered)
    • Depends: r-bioc-scaledmatrix r-bioc-delayedarray (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-bioc-scaledmatrix r-bioc-s4vectors (not considered)
    • Depends: r-bioc-scaledmatrix r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-scaledmatrix.html
    • autopkgtest for r-bioc-scaledmatrix/1.10.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
    • 228 days old (needed 2 days)
• r-bioc-summarizedexperiment (- to 1.32.0+dfsg-1)
  • Migration status for r-bioc-summarizedexperiment (- to 1.32.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-bioc-summarizedexperiment/1.32.0+dfsg-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
    • Build-Depends(-Arch): r-bioc-summarizedexperiment r-bioc-delayedarray
    • Build-Depends(-Arch): r-bioc-summarizedexperiment r-bioc-genomeinfodb (not considered)
    • Build-Depends(-Arch): r-bioc-summarizedexperiment r-bioc-genomicranges (not considered)
    • Build-Depends(-Arch): r-bioc-summarizedexperiment r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-summarizedexperiment r-bioc-s4arrays (not considered)
    • Build-Depends(-Arch): r-bioc-summarizedexperiment r-bioc-s4vectors (not considered)
    • Depends: r-bioc-summarizedexperiment r-bioc-delayedarray
    • Depends: r-bioc-summarizedexperiment r-bioc-genomeinfodb (not considered)
    • Depends: r-bioc-summarizedexperiment r-bioc-genomicranges (not considered)
    • Depends: r-bioc-summarizedexperiment r-bioc-iranges (not considered)
    • Depends: r-bioc-summarizedexperiment r-bioc-s4arrays (not considered)
    • Depends: r-bioc-summarizedexperiment r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-summarizedexperiment.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 228 days old (needed 5 days)
• r-bioc-xvector (- to 0.42.0-1)
  • Migration status for r-bioc-xvector (- to 0.42.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-bioc-xvector would introduce bugs in testing: #1071353
    • Build-Depends(-Arch): r-bioc-xvector r-bioc-iranges (not considered)
    • Build-Depends(-Arch): r-bioc-xvector r-bioc-s4vectors (not considered)
    • Depends: r-bioc-xvector r-bioc-iranges (not considered)
    • Depends: r-bioc-xvector r-bioc-s4vectors (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-bioc-xvector.html
    • autopkgtest for r-bioc-xvector/0.42.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 228 days old (needed 2 days)
• network-manager-sstp (- to 1.3.2-1)
  • Migration status for network-manager-sstp (- to 1.3.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): network-manager-sstp sstp-client (not considered)
    • Depends: network-manager-sstp sstp-client (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/network-manager-sstp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 230 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
  • 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 ♻
    • 231 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
    • 231 days old (needed 2 days)
• r-cran-spdep (- to 1.3-1+dfsg-1)
  • Migration status for r-cran-spdep (- 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-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-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
    • 231 days old (needed 2 days)
• protontricks (- to 1.10.5-1)
  • Migration status for protontricks (- to 1.10.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating protontricks would introduce bugs in testing: #1063967, #1071809
    • autopkgtest for protontricks/1.10.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: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 232 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
    • 232 days old (needed 5 days)
• acedb (- to 4.9.39+dfsg.02-9)
  • Migration status for acedb (- to 4.9.39+dfsg.02-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating acedb would introduce bugs in testing: #1066334
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/acedb.html
    • 233 days old (needed 5 days)
• r-cran-seurat (- to 5.0.1-1)
  • Migration status for r-cran-seurat (- to 5.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-seurat/5.0.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
    • Build-Depends(-Arch): r-cran-seurat r-cran-spatstat.explore (not considered)
    • Depends: r-cran-seurat r-cran-spatstat.explore (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-seurat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 233 days old (needed 5 days)
• ccextractor (- to 0.94+ds1-3)
  • Migration status for ccextractor (- to 0.94+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ccextractor would introduce bugs in testing: #1074276
    • Build-Depends(-Arch): ccextractor gpac (not considered)
    • Depends: ccextractor gpac (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ccextractor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 234 days old (needed 5 days)
• mysql-workbench (- to 8.0.32+dfsg-2)
  • Migration status for mysql-workbench (- to 8.0.32+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mysql-workbench/amd64 has unsatisfiable dependency
    • mysql-workbench/arm64 has unsatisfiable dependency
    • mysql-workbench/armel has unsatisfiable dependency
    • mysql-workbench/armhf has unsatisfiable dependency
    • mysql-workbench/i386 has unsatisfiable dependency
    • mysql-workbench/mips64el has unsatisfiable dependency
    • mysql-workbench/ppc64el has unsatisfiable dependency
    • mysql-workbench/s390x has unsatisfiable dependency
    • Updating mysql-workbench would introduce bugs in testing: #1000093, #1074563
  • Additional info:
    • Piuparts tested OK - 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 ♻
    • 234 days old (needed 5 days)
• python-django-ratelimit (- to 4.1.0-1)
  • Migration status for python-django-ratelimit (- to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by fladi, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-ratelimit.html
    • autopkgtest for python-django-ratelimit/4.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 234 days old (needed 2 days)
• rust-datasize (- to 0.2.13-1)
  • Migration status for rust-datasize (- to 0.2.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-datasize/0.2.13-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, 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 ♻
    • 234 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: Regression or new test ♻, 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/n/node-wikibase-cli.html
    • 235 days old (needed 5 days)
• bespokesynth (- to 1.2.1+dfsg-4)
  • Migration status for bespokesynth (- to 1.2.1+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): bespokesynth juce (not considered)
    • Invalidated by build-dependency
  • 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 ♻
    • 236 days old (needed 5 days)
• spice-vdagent (- to 0.22.1-4)
  • Migration status for spice-vdagent (- to 0.22.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spice-vdagent would introduce bugs in testing: #1060560
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spice-vdagent.html
    • autopkgtest for spice-vdagent/0.22.1-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 237 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 ♻
    • 238 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 ♻
    • 238 days old (needed 5 days)
• rust-subversion (- to 0.0.3-1)
  • Migration status for rust-subversion (- to 0.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-subversion/0.0.3-1: amd64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-subversion.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 238 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 geany (not considered)
    • Depends: geany-plugins geany (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 ♻
    • 240 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 ♻
    • 241 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: Pass, riscv64: Regression or new test ♻
    • Build-Depends(-Arch): jupyter-ydoc ypy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jupyter-ydoc.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 242 days old (needed 5 days)
• ypy (- to 0.7.0~a1-2)
  • Migration status for ypy (- to 0.7.0~a1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ypy would introduce bugs in testing: #1071899
    • ypy unsatisfiable Build-Depends(-Arch) on amd64: librust-lib0-dev
    • ypy unsatisfiable Build-Depends(-Arch) on amd64: librust-yrs-dev
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ypy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 242 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 ♻
    • 244 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
    • Updating cp2k would introduce bugs in testing: #1060949
    • autopkgtest for cp2k/2023.2-2: amd64: Pass, arm64: Pass, i386: 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
    • Reproducible on i386 - info ♻
    • 245 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-340xx (- to 340.108-21)
  • Migration status for nvidia-graphics-drivers-legacy-340xx (- to 340.108-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-legacy-340xx would introduce bugs in testing: #1004848, #1011141, #1016615, #1025280, #1033775, #1039679, #1055137, #1064984, #1072793, #973599, #979671, #987217, #991352
    • autopkgtest for nvidia-graphics-drivers-legacy-340xx/340.108-21: amd64: No tests, superficial or marked flaky ♻, armhf: Regression or new test ♻, i386: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 245 days old (needed 5 days)
• android-platform-frameworks-base (- to 1:14~beta1-2)
  • Migration status for android-platform-frameworks-base (- to 1:14~beta1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-frameworks-base would introduce bugs in testing: #1062206
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-frameworks-base.html
    • autopkgtest for android-platform-frameworks-base/1:14~beta1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: 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
    • 246 days old (needed 2 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-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 ♻
    • 246 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 ♻
    • 246 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
    • 249 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 ♻
    • 249 days old (needed 5 days)
• neutron-taas (- to 12.0.0-1)
  • Migration status for neutron-taas (- to 12.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating neutron-taas would introduce bugs in testing: #1072753
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/neutron-taas.html
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 251 days old (needed 5 days)
• geany (- to 2.0-1)
  • Migration status for geany (- to 2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating geany would introduce bugs in testing: #1061346
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geany.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 252 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 ♻
    • 252 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 ♻
    • 253 days old (needed 5 days)
• python-django-ca (- to 1.25.0-2)
  • Migration status for python-django-ca (- to 1.25.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-django-ca would introduce bugs in testing: #1071778
    • autopkgtest for python-django-ca/1.25.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-ca.html
    • 253 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
    • 253 days old (needed 5 days)
• genomicsdb (- to 1.5.0-2)
  • Migration status for genomicsdb (- to 1.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libgenomicsdb-java/arm64 has unsatisfiable dependency
    • autopkgtest for genomicsdb/1.5.0-2: amd64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/genomicsdb.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 254 days old (needed 5 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 ♻
    • 258 days old (needed 5 days)
• checkinstall (- to 1.6.2+git20170426.d24a630-4)
  • Migration status for checkinstall (- to 1.6.2+git20170426.d24a630-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating checkinstall would introduce bugs in testing: #1069436
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/checkinstall.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 259 days old (needed 5 days)
• guerillabackup (- to 0.5.0-1)
  • Migration status for guerillabackup (- to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guerillabackup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 262 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 ♻
    • 262 days old (needed 5 days)
• r-cran-tigger (- to 1.1.0-1)
  • Migration status for r-cran-tigger (- to 1.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-tigger r-cran-alakazam (not considered)
    • Depends: r-cran-tigger r-cran-alakazam (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tigger.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-cran-tigger/1.1.0-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
    • 262 days old (needed 2 days)
• satellite-gtk (- to 0.4.2-1)
  • Migration status for satellite-gtk (- to 0.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for satellite-gtk/0.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 ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/satellite-gtk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 262 days old (needed 5 days)
• vecgeom (- to 1.2.5+dfsg-1)
  • Migration status for vecgeom (- to 1.2.5+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libvecgeom1.2/amd64 has unsatisfiable dependency
    • libvgdml1.2/amd64 has unsatisfiable dependency
    • libvgdml1.2/armel has unsatisfiable dependency
    • libvgdml1.2/armhf has unsatisfiable dependency
    • Updating vecgeom would introduce bugs in testing: #1063044
    • Build-Depends(-Arch): vecgeom embree
    • Depends: vecgeom embree
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vecgeom.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 262 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 ♻
    • 263 days old (needed 5 days)
• python-certbot-dns-gandi (- to 1.4.3-2)
  • Migration status for python-certbot-dns-gandi (- to 1.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-certbot-dns-gandi would introduce bugs in testing: #1038920
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-gandi.html
    • autopkgtest for python-certbot-dns-gandi/1.4.3-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 263 days old (needed 2 days)
• 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 ♻
    • 264 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 ♻
    • 264 days old (needed 5 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 ♻
    • 264 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 ♻
    • 265 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 ♻
    • 265 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 ♻
    • 265 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
    • 266 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 ♻
    • 266 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 ♻
    • 268 days old (needed 5 days)
• rust-tikv-jemalloc-ctl (- to 0.5.4-1)
  • Migration status for rust-tikv-jemalloc-ctl (- to 0.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-tikv-jemalloc-ctl/0.5.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • 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 ♻
    • 269 days old (needed 5 days)
• certmonger (- to 0.79.19-1)
  • Migration status for certmonger (- to 0.79.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating certmonger would introduce bugs in testing: #1060589
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/certmonger.html
    • 272 days old (needed 5 days)
• r-cran-shazam (- to 1.2.0-1)
  • Migration status for r-cran-shazam (- 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): r-cran-shazam r-cran-alakazam (not considered)
    • Depends: r-cran-shazam r-cran-alakazam (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-shazam.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-cran-shazam/1.2.0-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
    • 272 days old (needed 2 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
    • 272 days old (needed 2 days)
• golang-github-jedisct1-go-hpke-compact (- to 0.9.2-1)
  • Migration status for golang-github-jedisct1-go-hpke-compact (- to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by sergiodj@sergiodj.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jedisct1-go-hpke-compact.html
    • autopkgtest for golang-github-jedisct1-go-hpke-compact/0.9.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 273 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 ♻
    • 273 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
    • 273 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 ♻
    • 274 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 ♻
    • 274 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 ♻
    • 274 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 ♻
    • 274 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 ♻
    • 274 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
    • 275 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
    • 275 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
    • 276 days old (needed 5 days)
• r-cran-alakazam (- to 1.3.0-1)
  • Migration status for r-cran-alakazam (- 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): r-cran-alakazam r-bioc-genomicalignments (not considered)
    • Depends: r-cran-alakazam r-bioc-genomicalignments (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-alakazam r-bioc-biostrings (not considered)
    • Build-Depends(-Arch): r-cran-alakazam r-bioc-iranges (not considered)
    • Depends: r-cran-alakazam r-bioc-biostrings (not considered)
    • Depends: r-cran-alakazam r-bioc-iranges (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-alakazam.html
    • autopkgtest for r-cran-alakazam/1.3.0-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
    • 276 days old (needed 2 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
    • 276 days old (needed 2 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 ♻
    • 279 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
    • 281 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 ♻
    • 282 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 ♻
    • 282 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
    • 283 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 ♻
    • 283 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 ♻
    • 285 days old (needed 5 days)
• ghdl (- to 3.0.0+dfsg2-1)
  • Migration status for ghdl (- to 3.0.0+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ghdl would introduce bugs in testing: #1067446
    • missing build on arm64
    • missing build on armel
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • autopkgtest for ghdl/3.0.0+dfsg2-1: amd64: Pass, i386: Pass, ppc64el: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghdl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 288 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:
    • Updating yosys-plugin-ghdl would introduce bugs in testing: #1067465
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on arm64: libghdl-dev (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on arm64: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on armel: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on mips64el: ghdl-mcode (>= 3.0.0)
    • yosys-plugin-ghdl unsatisfiable Build-Depends(-Arch) on ppc64el: ghdl-mcode (>= 3.0.0)
    • missing build on arm64
    • missing build on armel
    • missing build on mips64el
    • missing build on ppc64el
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for yosys-plugin-ghdl/0.0~git20230419.5b64ccf-1: amd64: Pass, i386: Pass
    • Build-Depends(-Arch): yosys-plugin-ghdl ghdl (not considered)
    • Build-Depends(-Arch): yosys-plugin-ghdl yosys (not considered)
    • Depends: yosys-plugin-ghdl ghdl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yosys-plugin-ghdl.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 289 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 ♻
    • 290 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 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 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 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 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 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 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 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 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
    • autopkgtest for rust-gtk-sys/0.18.0-2: riscv64: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - 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 ♻
    • 290 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
    • 291 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
    • 291 days old (needed 5 days)
• kdevelop (- to 4:23.08.1-2)
  • Migration status for kdevelop (- to 4:23.08.1-2): 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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 294 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 ♻
    • 294 days old (needed 5 days)
• kdevelop-python (- to 23.08.1-1)
  • Migration status for kdevelop-python (- 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-python kdevelop (not considered)
    • Depends: kdevelop-python kdevelop (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdevelop-python.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 294 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 ♻
    • Required age reduced by 3 days because of autopkgtest
    • 295 days old (needed 2 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 ♻
    • 296 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 ♻
    • 296 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:
    • autopkgtest for skorch/0.15.0-1: amd64: Pass, arm64: Pass, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Pass
    • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 297 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: No tests, superficial or 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)
• graftcp (- to 0.3.1+ds1-2)
  • Migration status for graftcp (- to 0.3.1+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating graftcp would introduce bugs in testing: #981713
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/graftcp.html
    • Reproducible on amd64 - info ♻
    • 300 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
    • 300 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
    • 300 days old (needed 5 days)
• mono-tools (- to 4.2-3.2)
  • Migration status for mono-tools (- to 4.2-3.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: mono-tools cecil (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mono-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 300 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
    • 304 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
    • autopkgtest for xpra/3.1.5+dfsg1-0.2: riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - 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
    • 304 days old (needed 5 days)
• obs-color-monitor (- to 0.6.1-1)
  • Migration status for obs-color-monitor (- to 0.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • obs-color-monitor/ppc64el has unsatisfiable dependency
    • obs-color-monitor unsatisfiable Build-Depends(-Arch) on ppc64el: libobs-dev (>= 29)
    • autopkgtest for obs-color-monitor/0.6.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-color-monitor.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 306 days old (needed 5 days)
• mlpcap (- to 0.9-21)
  • Migration status for mlpcap (- to 0.9-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libmlpcap-ocaml/armel has unsatisfiable dependency
    • libmlpcap-ocaml/armhf has unsatisfiable dependency
    • Updating mlpcap would introduce bugs in testing: #1066654
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlpcap.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 307 days old (needed 5 days)
• ocamldap (- to 2.4.2-5)
  • Migration status for ocamldap (- to 2.4.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ocamldap pcre-ocaml (not considered)
    • Depends: ocamldap pcre-ocaml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamldap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 307 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
    • 307 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 ♻
    • 308 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
    • 309 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
    • Build-Depends(-Arch): haskell-hsyaml-aeson haskell-hsyaml (not considered)
    • Build-Depends-Indep: haskell-hsyaml-aeson haskell-hsyaml (not considered)
  • 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 ♻
    • 309 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
    • 310 days old (needed 5 days)
• pytorch-ignite (- to 0.4.12-1)
  • Migration status for pytorch-ignite (- to 0.4.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pytorch-ignite pytorch (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 310 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
    • Build-Depends(-Arch): pytorch-text pytorch (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch-text.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 310 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 ♻
    • 311 days old (needed 5 days)
• parsinsert (- to 1.04-15)
  • Migration status for parsinsert (- to 1.04-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating parsinsert would introduce bugs in testing: #1069488
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/parsinsert.html
    • autopkgtest for parsinsert/1.04-15: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 311 days old (needed 2 days)
• dolphin-emu (- to 5.0-19870+dfsg-1)
  • Migration status for dolphin-emu (- to 5.0-19870+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dolphin-emu would introduce bugs in testing: #1064753
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dolphin-emu.html
    • 312 days old (needed 5 days)
• nomacs (- to 3.17.2282+dfsg-2)
  • Migration status for nomacs (- to 3.17.2282+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nomacs would introduce bugs in testing: #1014124, #974616
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nomacs.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 312 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 ♻
    • 312 days old (needed 5 days)
• vuls (- to 0.6.1-5)
  • Migration status for vuls (- to 0.6.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: vuls golang-github-go-redis-redis (not considered)
    • Invalidated by built-using
    • Build-Depends(-Arch): vuls go-cve-dictionary
    • Build-Depends(-Arch): vuls go-exploitdb
    • Build-Depends(-Arch): vuls gost
    • Build-Depends(-Arch): vuls goval-dictionary
    • Built-Using: vuls go-cve-dictionary
    • Built-Using: vuls go-exploitdb
    • Built-Using: vuls gost
    • Built-Using: vuls goval-dictionary
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vuls.html
    • autopkgtest for vuls/0.6.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 312 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 ♻
    • 313 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
  • 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
    • 314 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 amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 315 days old (needed 5 days)
• obs-scene-tree-view (- to 0.1.7-1)
  • Migration status for obs-scene-tree-view (- to 0.1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • obs-scene-tree-view/ppc64el has unsatisfiable dependency
    • obs-scene-tree-view unsatisfiable Build-Depends(-Arch) on ppc64el: libobs-dev (>= 29)
    • autopkgtest for obs-scene-tree-view/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 ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-scene-tree-view.html
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 315 days old (needed 5 days)
• wmnut (- to 0.69-1)
  • Migration status for wmnut (- to 0.69-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): wmnut nut (not considered)
    • Depends: wmnut nut (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wmnut.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 315 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:
    • Updating gnome-shell-extension-weather would introduce bugs in testing: #1052111
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-weather.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 316 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
  • 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 ♻
    • 317 days old (needed 5 days)
• ocaml-http (- to 0.1.6-2)
  • Migration status for ocaml-http (- to 0.1.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ocaml-http pcre-ocaml (not considered)
    • Depends: ocaml-http pcre-ocaml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-http.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 317 days old (needed 5 days)
• ocamlsdl (- to 0.9.1-4)
  • Migration status for ocamlsdl (- to 0.9.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ocamlsdl would introduce bugs in testing: #1038076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamlsdl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 317 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
    • Build-Depends(-Arch): ormar asgi-lifespan (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ormar.html
    • autopkgtest for ormar/0.12.2-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 318 days old (needed 2 days)
• trocla (- to 0.5.1-2)
  • Migration status for trocla (- to 0.5.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): trocla ruby-moneta (not considered)
    • Depends: trocla ruby-moneta (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trocla.html
    • autopkgtest for trocla/0.5.1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 319 days old (needed 2 days)
• ddcci-driver-linux (- to 0.4.4-1)
  • Migration status for ddcci-driver-linux (- to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ddcci-driver-linux would introduce bugs in testing: #1071293
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/d/ddcci-driver-linux.html
    • autopkgtest for ddcci-driver-linux/0.4.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: Regression or new test ♻
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 320 days old (needed 5 days)
• r-cran-sjplot (- to 2.8.15+dfsg-1)
  • Migration status for r-cran-sjplot (- to 2.8.15+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.15+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
    • 322 days old (needed 2 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 ♻
    • 322 days old (needed 5 days)
• repetier-host (- to 0.85+dfsg-5)
  • Migration status for repetier-host (- to 0.85+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): repetier-host opentk (not considered)
    • Depends: repetier-host opentk (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/repetier-host.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 323 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
    • 325 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
    • 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:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bind-dyndb-ldap.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 326 days old (needed 5 days)
• kxd (- to 0.15-4.1)
  • Migration status for kxd (- to 0.15-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kxd would introduce bugs in testing: #1063700
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kxd.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 326 days old (needed 5 days)
• emacs-jedi (- to 0.2.8+git20220410.81c5a42-1)
  • Migration status for emacs-jedi (- to 0.2.8+git20220410.81c5a42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-jedi would introduce bugs in testing: #994171
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-jedi.html
    • autopkgtest for emacs-jedi/0.2.8+git20220410.81c5a42-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 328 days old (needed 2 days)
• 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 ♻
    • 328 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 ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 328 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
    • 329 days old (needed 2 days)
• asgi-csrf (- to 0.9-2)
  • Migration status for asgi-csrf (- to 0.9-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): asgi-csrf asgi-lifespan (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asgi-csrf.html
    • autopkgtest for asgi-csrf/0.9-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 330 days old (needed 2 days)
• asgi-lifespan (- to 2.1.0-2)
  • Migration status for asgi-lifespan (- to 2.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asgi-lifespan would introduce bugs in testing: #1066787
    • autopkgtest for asgi-lifespan/2.1.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asgi-lifespan.html
    • 330 days old (needed 5 days)
• node-socks-proxy-agent (- to 7.0.0+dfsg+~cs2.0.11-1)
  • Migration status for node-socks-proxy-agent (- to 7.0.0+dfsg+~cs2.0.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • node-socks-proxy-agent has no binaries on any arch
    • Updating node-socks-proxy-agent would introduce bugs in testing: #1071773
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 330 days old (needed 5 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 ♻
    • 330 days old (needed 5 days)
• node-lockfile (- to 1.0.4+~1.0.2-3)
  • Migration status for node-lockfile (- to 1.0.4+~1.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-lockfile would introduce bugs in testing: #1005940
    • autopkgtest for node-lockfile/1.0.4+~1.0.2-3: 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/n/node-lockfile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 331 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
    • 331 days old (needed 5 days)
• arb (- to 6.0.6-7)
  • Migration status for arb (- to 6.0.6-7): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 332 days old (needed 5 days)
• novnc (- to 1:1.3.0-2)
  • Migration status for novnc (- to 1:1.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: novnc websockify (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/novnc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 332 days old (needed 5 days)
• go-cve-dictionary (- to 0.3.1-5)
  • Migration status for go-cve-dictionary (- to 0.3.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Depends: go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-cve-dictionary.html
    • autopkgtest for go-cve-dictionary/0.3.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible 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)
• 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
    • 333 days old (needed 2 days)
• gost (- to 0.1.2-2)
  • Migration status for gost (- to 0.1.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gost golang-github-go-redis-redis (not considered)
    • Built-Using: gost golang-github-go-redis-redis (not considered)
    • Depends: gost golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gost.html
    • autopkgtest for gost/0.1.2-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible 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)
• goval-dictionary (- to 0.2.0-6)
  • Migration status for goval-dictionary (- to 0.2.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): goval-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: goval-dictionary golang-github-go-redis-redis (not considered)
    • Depends: goval-dictionary golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goval-dictionary.html
    • autopkgtest for goval-dictionary/0.2.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible 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)
• pcre-ocaml (- to 7.5.0-3)
  • Migration status for pcre-ocaml (- to 7.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pcre-ocaml would introduce bugs in testing: #1000004
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcre-ocaml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 333 days old (needed 5 days)
• tomopy (- to 1.14.1+ds1-1)
  • Migration status for tomopy (- to 1.14.1+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-tomopy/amd64 has unsatisfiable dependency
    • python3-tomopy/armel has unsatisfiable dependency
    • python3-tomopy/armhf has unsatisfiable dependency
    • python3-tomopy/mips64el has unsatisfiable dependency
    • python3-tomopy/s390x has unsatisfiable dependency
    • Updating tomopy would introduce bugs in testing: #1036684, #1061064
    • autopkgtest for tomopy/1.14.1+ds1-1: riscv64: Pass
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 333 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): go-exploitdb golang-github-go-redis-redis (not considered)
    • Built-Using: go-exploitdb golang-github-go-redis-redis (not considered)
    • Depends: go-exploitdb golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-exploitdb.html
    • autopkgtest for go-exploitdb/0.0~git20181130.7c961e7-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible 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)
• 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 ♻
    • 334 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 ♻
    • 334 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 ♻
    • 334 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 ♻
    • 334 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
    • 334 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.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 ♻
    • 335 days old (needed 5 days)
• xfce4-panel-profiles (- to 1.0.14-1)
  • Migration status for xfce4-panel-profiles (- to 1.0.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xfce4-panel-profiles would introduce bugs in testing: #1056704
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfce4-panel-profiles.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 335 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 ♻
    • 336 days old (needed 5 days)
• searx (- to 1.1.0+dfsg1-2)
  • Migration status for searx (- to 1.1.0+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating searx would introduce bugs in testing: #1051510
    • autopkgtest for searx/1.1.0+dfsg1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/searx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 336 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 ♻
    • 339 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 ♻
    • 340 days old (needed 5 days)
• aircrack-ng (- to 1:1.7+git20230807.4bf83f1a-1)
  • Migration status for aircrack-ng (- to 1:1.7+git20230807.4bf83f1a-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aircrack-ng would introduce bugs in testing: #1051201, #1071832
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aircrack-ng.html
    • Reproducible on i386 - info ♻
    • 342 days old (needed 5 days)
• freebsd-buildutils (- to 10.3~svn296373-7.1)
  • Migration status for freebsd-buildutils (- to 10.3~svn296373-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • freebsd-buildutils/armel has unsatisfiable dependency
    • freebsd-buildutils/armhf has unsatisfiable dependency
    • Updating freebsd-buildutils would introduce bugs in testing: #1067683
    • freebsd-buildutils unsatisfiable Build-Depends(-Arch) on mips64el: gcc-9
    • missing build on mips64el
    • Build-Depends(-Arch): freebsd-buildutils freebsd-glue (not considered)
    • Build-Depends(-Arch): freebsd-buildutils freebsd-libs (not considered)
    • Build-Depends(-Arch): freebsd-buildutils gcc-9 (not considered)
    • Depends: freebsd-buildutils freebsd-glue (not considered)
    • Depends: freebsd-buildutils freebsd-libs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freebsd-buildutils.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 342 days old (needed 5 days)
• itop (- to 0.1-4.1)
  • Migration status for itop (- to 0.1-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating itop would introduce bugs in testing: #904206
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/itop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 342 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 -> libglib2.0-0/2.78.4-1/armel
    • Impossible Depends: rmlint -> libglib2.0-0/2.78.4-1/armhf
    • Depends: rmlint elfutils
  • 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
    • 342 days old (needed 2 days)
• freebsd-glue (- to 0.2.22+nmu1)
  • Migration status for freebsd-glue (- to 0.2.22+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • freebsd-glue unsatisfiable Build-Depends(-Arch) on mips64el: gcc-9
    • missing build on mips64el
    • Build-Depends(-Arch): freebsd-glue freebsd-buildutils (not considered)
    • Build-Depends(-Arch): freebsd-glue gcc-9 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freebsd-glue.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 343 days old (needed 5 days)
• chkservice (- to 0.3-1.1)
  • Migration status for chkservice (- to 0.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chkservice would introduce bugs in testing: #988094
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chkservice.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 345 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
    • 345 days old (needed 5 days)
• lnav (- to 0.11.2-1)
  • Migration status for lnav (- to 0.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • lnav/armel has unsatisfiable dependency
    • lnav/armhf has unsatisfiable dependency
    • Updating lnav would introduce bugs in testing: #1067018, #1067284
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lnav.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 345 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 ♻
    • 346 days old (needed 5 days)
• npgsql (- to 2.2.7+dfsg3-1.1)
  • Migration status for npgsql (- to 2.2.7+dfsg3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating npgsql would introduce bugs in testing: #1070859
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/npgsql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 347 days old (needed 5 days)
• newsboat (- to 2.32-3)
  • Migration status for newsboat (- to 2.32-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating newsboat would introduce bugs in testing: #1054680
    • autopkgtest for newsboat/2.32-3: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • Depends: newsboat curl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/newsboat.html
    • 351 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 ♻
    • 352 days old (needed 5 days)
• mdanalysis (- to 2.5.0+dfsg1-2)
  • Migration status for mdanalysis (- to 2.5.0+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mdanalysis would introduce bugs in testing: #1071800
    • autopkgtest for mdanalysis/2.5.0+dfsg1-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdanalysis.html
    • Waiting for reproducibility test results on i386 - info ♻
    • 353 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: #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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 355 days old (needed 2 days)
• r-cran-maptools (- to 1:1.1-8+dfsg-1)
  • Migration status for r-cran-maptools (- to 1:1.1-8+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-maptools would introduce bugs in testing: #1071355
    • autopkgtest for r-cran-maptools/1:1.1-8+dfsg-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-maptools.html
    • 356 days old (needed 5 days)
• haskell-swish (- to 0.10.4.0-1)
  • Migration status for haskell-swish (- to 0.10.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-swish-doc/amd64 has unsatisfiable dependency
    • libghc-swish-doc/arm64 has unsatisfiable dependency
    • libghc-swish-dev/mips64el has unsatisfiable dependency
    • libghc-swish-prof/mips64el has unsatisfiable dependency
    • Updating haskell-swish would introduce bugs in testing: #1058746
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-swish.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 357 days old (needed 5 days)
• r-cran-geoknife (- to 1.6.11+dfsg-1)
  • Migration status for r-cran-geoknife (- to 1.6.11+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-geoknife/1.6.11+dfsg-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): r-cran-geoknife r-cran-sf (not considered)
    • Depends: r-cran-geoknife r-cran-sf (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-geoknife.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 358 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 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.2-3+deb12u7/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 -> libpng16-16/1.6.43-1/armel
    • Impossible Depends: openjdk-20 -> libpng16-16/1.6.43-1/armhf
    • Build-Depends(-Arch): openjdk-20 gtk+3.0
    • Depends: openjdk-20 gtk+3.0
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-20.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • 360 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 ♻
    • 360 days old (needed 5 days)
• python-package-smoke-test (- to 1.0-1)
  • Migration status for python-package-smoke-test (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ben@benfinney.id.au, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-package-smoke-test.html
    • autopkgtest for python-package-smoke-test/1.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 361 days old (needed 5 days)
• debian-parl (- to 1.9.31+nmu1)
  • Migration status for debian-parl (- to 1.9.31+nmu1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: debian-parl syncevolution (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-parl.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 362 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
  • 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 ♻
    • 362 days old (needed 5 days)
• spek (- to 0.8.5+dfsg-3)
  • Migration status for spek (- to 0.8.5+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • spek/armel has unsatisfiable dependency
    • spek/armhf has unsatisfiable dependency
    • Updating spek would introduce bugs in testing: #1067691
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spek.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 ♻
    • 362 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): iem-plugin-suite juce (not considered)
    • Built-Using: iem-plugin-suite juce (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iem-plugin-suite.html
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 363 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 ♻
    • Reproducible on i386 - info ♻
    • 364 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
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 366 days old (needed 5 days)
• rust-packed-simd (- to 0.3.8-1)
  • Migration status for rust-packed-simd (- to 0.3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-packed-simd/0.3.8-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: 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 ♻
    • 366 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 ♻
    • 366 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 ♻
    • Reproducible on i386 - info ♻
    • 367 days old (needed 5 days)
• gcc-9-cross (- to 29)
  • Migration status for gcc-9-cross (- to 29): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9-cross would introduce bugs in testing: #1032217, #994134
    • Build-Depends(-Arch): gcc-9-cross autoconf2.64 (not considered)
    • Build-Depends(-Arch): gcc-9-cross gcc-9 (not considered)
    • Built-Using: gcc-9-cross gcc-9 (not considered)
    • Depends: gcc-9-cross gcc-9 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9-cross.html
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 367 days old (needed 5 days)
• gcc-9-cross-ports (- to 27)
  • Migration status for gcc-9-cross-ports (- to 27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9-cross-ports would introduce bugs in testing: #1032216, #994135
    • Build-Depends(-Arch): gcc-9-cross-ports autoconf2.64 (not considered)
    • Build-Depends(-Arch): gcc-9-cross-ports gcc-9 (not considered)
    • Built-Using: gcc-9-cross-ports gcc-9 (not considered)
    • Depends: gcc-9-cross-ports gcc-9 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-9-cross-ports.html
    • 367 days old (needed 5 days)
• golang-github-go-enry-go-license-detector (- to 4.3.0+git20221007.a3a1cc6-3)
  • Migration status for golang-github-go-enry-go-license-detector (- to 4.3.0+git20221007.a3a1cc6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-go-enry-go-license-detector/4.3.0+git20221007.a3a1cc6-3: amd64: Pass, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-go-enry-go-license-detector.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 367 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 ♻
    • 367 days old (needed 5 days)
• gcc-10-cross-mipsen (- to 3+c6)
  • Migration status for gcc-10-cross-mipsen (- to 3+c6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • g++-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-10-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-10-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-10-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-10-multilib-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • Updating gcc-10-cross-mipsen would introduce bugs in testing: #1032218, #1040624
    • Build-Depends(-Arch): gcc-10-cross-mipsen gcc-10 (not considered)
    • Built-Using: gcc-10-cross-mipsen gcc-10 (not considered)
    • Depends: gcc-10-cross-mipsen gcc-10 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross-mipsen.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on i386 - info ♻
    • 369 days old (needed 5 days)
• golang-github-hashicorp-terraform-registry-address (- to 0.2.0-1)
  • Migration status for golang-github-hashicorp-terraform-registry-address (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by foka, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hashicorp-terraform-registry-address.html
    • autopkgtest for golang-github-hashicorp-terraform-registry-address/0.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 369 days old (needed 2 days)
• gcc-10-cross-ports (- to 24)
  • Migration status for gcc-10-cross-ports (- to 24): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-10-cross-ports gcc-10 (not considered)
    • Built-Using: gcc-10-cross-ports gcc-10 (not considered)
    • Depends: gcc-10-cross-ports gcc-10 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross-ports.html
    • 371 days old (needed 5 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:
    • 371 days old (needed 5 days)
• gcc-10-cross (- to 23)
  • Migration status for gcc-10-cross (- to 23): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-10-cross gcc-10 (not considered)
    • Built-Using: gcc-10-cross gcc-10 (not considered)
    • Depends: gcc-10-cross gcc-10 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-10-cross.html
    • New but not reproducible on i386 - info ♻
    • 372 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
  • 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
    • 372 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 ♻
    • 374 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 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.2-3+deb12u7/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 -> libpng16-16/1.6.43-1/armel
    • Impossible Depends: openjdk-19 -> libpng16-16/1.6.43-1/armhf
    • Build-Depends(-Arch): openjdk-19 gtk+3.0
    • Depends: openjdk-19 gtk+3.0
  • 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 ♻
    • 375 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 ♻
    • 375 days old (needed 5 days)
• binutils-msp430 (- to 2.40.50~ti1)
  • Migration status for binutils-msp430 (- to 2.40.50~ti1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils-msp430 would introduce bugs in testing: #1042343
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-msp430.html
    • 378 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
    • 378 days old (needed 2 days)
• markdown-toc-el (- to 0.1.5-3)
  • Migration status for markdown-toc-el (- to 0.1.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating markdown-toc-el would introduce bugs in testing: #1036359
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/markdown-toc-el.html
    • autopkgtest for markdown-toc-el/0.1.5-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 379 days old (needed 2 days)
• r-other-ascat (- to 3.1.2-1)
  • Migration status for r-other-ascat (- to 3.1.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-other-ascat r-bioc-iranges (not considered)
    • Depends: r-other-ascat r-bioc-iranges (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-other-ascat r-bioc-genomicranges (not considered)
    • Depends: r-other-ascat r-bioc-genomicranges (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-other-ascat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 380 days old (needed 5 days)
• plastimatch (- to 1.9.4+dfsg.1-2)
  • Migration status for plastimatch (- to 1.9.4+dfsg.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating plastimatch would introduce bugs in testing: #1075793
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plastimatch.html
    • autopkgtest for plastimatch/1.9.4+dfsg.1-2: amd64: Pass
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 381 days old (needed 2 days)
• ruby-rack-session (- to 2.0.0-1)
  • Migration status for ruby-rack-session (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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 ♻
    • 383 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 ♻
    • 383 days old (needed 5 days)
• sen (- to 0.7.0-1)
  • Migration status for sen (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sen would introduce bugs in testing: #1067287
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 383 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.random (not considered)
    • Depends: r-cran-sparr r-cran-spatstat.random (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): r-cran-sparr r-cran-spatstat
    • Build-Depends(-Arch): r-cran-sparr r-cran-spatstat.explore (not considered)
    • Depends: r-cran-sparr r-cran-spatstat
    • Depends: r-cran-sparr r-cran-spatstat.explore (not considered)
  • 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
    • 384 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 ♻
    • 387 days old (needed 5 days)
• psfex (- to 3.24.2-1)
  • Migration status for psfex (- to 3.24.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating psfex would introduce bugs in testing: #1056684
    • Build-Depends(-Arch): psfex atlas (not considered)
    • Depends: psfex atlas (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psfex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 387 days old (needed 5 days)
• source-extractor (- to 2.28.0+ds-1)
  • Migration status for source-extractor (- to 2.28.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating source-extractor would introduce bugs in testing: #1056688
    • Build-Depends(-Arch): source-extractor atlas (not considered)
    • Depends: source-extractor atlas (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/source-extractor.html
    • autopkgtest for source-extractor/2.28.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 387 days old (needed 2 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
    • 390 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 ♻
    • 390 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
    • 391 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
    • 392 days old (needed 2 days)
• octave-database (- to 2.4.4-8)
  • Migration status for octave-database (- to 2.4.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octave-database would introduce bugs in testing: #1004158
    • 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 ♻
    • Reproducible on i386 - info ♻
    • 392 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: #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
    • 392 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 ♻
    • 393 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
    • 394 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
    • 395 days old (needed 5 days)
• webcamoid (- to 9.1.1-1)
  • Migration status for webcamoid (- to 9.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating webcamoid would introduce bugs in testing: #1053808
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webcamoid.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 395 days old (needed 5 days)
• wifite (- to 2.7.0-1)
  • Migration status for wifite (- to 2.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for wifite/2.7.0-1: 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): wifite aircrack-ng (not considered)
    • Depends: wifite aircrack-ng (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wifite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 395 days old (needed 5 days)
• pcb (- to 1:4.3.0-3)
  • Migration status for pcb (- to 1:4.3.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pcb gtkglext (not considered)
    • Depends: pcb gtkglext (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 396 days old (needed 5 days)
• rust-hdrhistogram (- to 7.5.2-1)
  • Migration status for rust-hdrhistogram (- to 7.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-hdrhistogram would introduce bugs in testing: #1014034
    • autopkgtest for rust-hdrhistogram/7.5.2-1: amd64: Regression or new test ♻, arm64: Pass, armel: Regression or new test ♻, 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/rust-hdrhistogram.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 396 days old (needed 5 days)
• rapiddisk (- to 9.1.0-2)
  • Migration status for rapiddisk (- to 9.1.0-2): 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-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:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 397 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 ♻
    • 397 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
    • 398 days old (needed 5 days)
• cadabra2 (- to 2.4.3.2-1.1)
  • Migration status for cadabra2 (- to 2.4.3.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cadabra2/amd64 has unsatisfiable dependency
    • cadabra2/arm64 has unsatisfiable dependency
    • cadabra2/armel has unsatisfiable dependency
    • cadabra2/armhf has unsatisfiable dependency
    • cadabra2/i386 has unsatisfiable dependency
    • cadabra2/mips64el has unsatisfiable dependency
    • cadabra2/ppc64el has unsatisfiable dependency
    • cadabra2/s390x has unsatisfiable dependency
    • Updating cadabra2 would introduce bugs in testing: #1061319
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cadabra2.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 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 ♻
    • 414 days old (needed 5 days)
• rust-bendy (- to 0.3.3-1)
  • Migration status for rust-bendy (- to 0.3.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-bendy rust-failure (not considered)
    • Depends: rust-bendy rust-failure (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bendy.html
    • autopkgtest for rust-bendy/0.3.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻, 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 ♻
    • 417 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 ♻
    • 421 days old (needed 5 days)
• stravalib (- to 1.3.0-1)
  • Migration status for stravalib (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating stravalib would introduce bugs in testing: #1069826
    • autopkgtest for stravalib/1.3.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: Regression or new test ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 423 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
    • 426 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: #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 ♻
    • 427 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:
    • Updating ogmrip would introduce bugs in testing: #1074275
    • Depends: ogmrip gpac (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ogmrip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 427 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 ♻
    • 430 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
    • Depends: mate-equake-applet curl (not considered)
    • Depends: mate-equake-applet gtk+3.0
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-equake-applet.html
    • 433 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 ♻
    • 435 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 ♻
    • 435 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:
    • Piuparts tested OK - 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
    • 437 days old (needed 5 days)
• rust-env-logger-0.7 (- to 0.7.1-4)
  • Migration status for rust-env-logger-0.7 (- to 0.7.1-4): 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-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
    • 440 days old (needed 2 days)
• gplcver (- to 2.12a-2)
  • Migration status for gplcver (- to 2.12a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gplcver would introduce bugs in testing: #1066713
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gplcver.html
    • 446 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 ♻
    • 449 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 ♻
    • 452 days old (needed 5 days)
• covered (- to 0.7.10-4)
  • Migration status for covered (- to 0.7.10-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): covered gplcver (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/covered.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 454 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 ♻
    • 456 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 ♻
    • 460 days old (needed 5 days)
• php-spyc (- to 0.6.3-1)
  • Migration status for php-spyc (- to 0.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by alteholz, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-spyc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 460 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
    • 464 days old (needed 5 days)
• opentk (- to 1.1.4c+dfsg-2.2)
  • Migration status for opentk (- to 1.1.4c+dfsg-2.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: opentk cecil (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opentk.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 479 days old (needed 5 days)
• gitlab-ci-multi-runner (- to 14.10.1-1)
  • Migration status for gitlab-ci-multi-runner (- to 14.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab-ci-multi-runner would introduce bugs in testing: #1033480
    • gitlab-runner/amd64 has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/arm64 has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/armel has unsatisfiable Built-Using on golang-github-dgrijalva-jwt-go 3.2.0-3
    • gitlab-runner/armel has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • gitlab-runner/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/armhf has unsatisfiable Built-Using on golang-github-dgrijalva-jwt-go 3.2.0-3
    • gitlab-runner/armhf has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • gitlab-runner/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • gitlab-runner/i386 has unsatisfiable Built-Using on golang-github-dgrijalva-jwt-go 3.2.0-3
    • gitlab-runner/i386 has unsatisfiable Built-Using on golang-goprotobuf 1.3.4-2
    • gitlab-runner/mips64el has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/ppc64el has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • gitlab-runner/s390x has unsatisfiable Built-Using on golang-1.19 1.19.6-2
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-ci-multi-runner.html
    • 480 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 ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 486 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
    • 490 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: No tests, superficial or 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 ♻
    • 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 ♻
    • 492 days old (needed 5 days)
• igdiscover (- to 0.11-4)
  • Migration status for igdiscover (- to 0.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating igdiscover would introduce bugs in testing: #1032975
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/igdiscover.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for igdiscover/0.11-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • 493 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)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganeti.html
    • autopkgtest for ganeti/3.0.2-3: amd64: Pass, arm64: Pass, armel: Ignored failure, armhf: Ignored failure, i386: Pass, ppc64el: Pass, s390x: Ignored failure
    • 496 days old (needed 5 days)
• debian-pan (- to 0.4)
  • Migration status for debian-pan (- to 0.4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: debian-pan mathgl (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-pan.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 497 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 ♻
    • 500 days old (needed 5 days)
• emacs-helm-ag (- to 0.59-2)
  • Migration status for emacs-helm-ag (- to 0.59-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-helm-ag would introduce bugs in testing: #1057557
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-helm-ag.html
    • autopkgtest for emacs-helm-ag/0.59-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 501 days old (needed 2 days)
• ktp-text-ui (- to 22.12.3-1)
  • Migration status for ktp-text-ui (- to 22.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ktp-text-ui would introduce bugs in testing: #1070254
  • 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 ♻
    • 501 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 ♻
    • 502 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
    • 503 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
    • 503 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
    • 505 days old (needed 5 days)
• qpid-proton-j (- to 0.34.0-1)
  • Migration status for qpid-proton-j (- to 0.34.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by jello, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qpid-proton-j.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 506 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)
    • 507 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 ♻
    • 507 days old (needed 5 days)
• zoneminder (- to 1.36.33+dfsg1-1)
  • Migration status for zoneminder (- to 1.36.33+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zoneminder would introduce bugs in testing: #999919
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zoneminder.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 507 days old (needed 5 days)
• poliastro (- to 0.17.0-2)
  • Migration status for poliastro (- to 0.17.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for poliastro/0.17.0-2: amd64: Pass, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): poliastro astroquery (not considered)
    • Build-Depends(-Arch): poliastro numba (not considered)
    • Depends: poliastro astroquery (not considered)
    • Depends: poliastro numba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poliastro.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 508 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 apktool (not considered)
    • Invalidated by dependency
  • 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
    • 509 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
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/fava.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 509 days old (needed 5 days)
• golang-github-crewjam-saml (- to 0.4.12-2)
  • Migration status for golang-github-crewjam-saml (- to 0.4.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-crewjam-saml would introduce bugs in testing: #1033753, #1033864, #1054223
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-crewjam-saml.html
    • autopkgtest for golang-github-crewjam-saml/0.4.12-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 509 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 ♻
    • 510 days old (needed 5 days)
• oregano (- to 0.84.41+dfsg.1-1.1)
  • Migration status for oregano (- to 0.84.41+dfsg.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oregano would introduce bugs in testing: #1051281
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oregano.html
    • Reproducible on amd64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 512 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
    • 515 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)
    • 515 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 ♻
    • 516 days old (needed 5 days)
• torsocks (- to 2.4.0-1)
  • Migration status for torsocks (- to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating torsocks would introduce bugs in testing: #1066313
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/torsocks.html
    • 520 days old (needed 5 days)
• dogtag-pki (- to 11.2.1-2)
  • Migration status for dogtag-pki (- to 11.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pki-server/amd64 has unsatisfiable dependency
    • pki-server/arm64 has unsatisfiable dependency
    • pki-server/armel has unsatisfiable dependency
    • pki-server/armhf has unsatisfiable dependency
    • pki-server/i386 has unsatisfiable dependency
    • pki-server/mips64el has unsatisfiable dependency
    • pki-server/ppc64el has unsatisfiable dependency
    • pki-server/s390x has unsatisfiable dependency
    • Updating dogtag-pki would introduce bugs in testing: #1054480, #1065850
    • 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 ♻
    • Reproducible on i386 - info ♻
    • 521 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
    • 521 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 ♻
    • Build-Depends(-Arch): pytorch-audio pytorch (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 ♻
    • 521 days old (needed 5 days)
• invesalius (- to 3.1.99998-4)
  • Migration status for invesalius (- to 3.1.99998-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for invesalius/3.1.99998-4: 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: No tests, superficial or marked flaky ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/invesalius.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 522 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
    • 522 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 ♻
    • 523 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 ♻
    • 523 days old (needed 5 days)
• python-confection (- to 0.0.4-2)
  • Migration status for python-confection (- 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): python-confection python-srsly (not considered)
    • Depends: python-confection python-srsly (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-confection.html
    • autopkgtest for python-confection/0.0.4-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 523 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: Regression or new test ♻, riscv64: Pass, 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 ♻
    • 523 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
    • python3-sage/arm64 has unsatisfiable dependency
    • python3-sage/i386 has unsatisfiable dependency
    • Updating sagemath would introduce bugs in testing: #1042683, #1042935, #1050182, #1052051, #1056885, #1065953
    • sagemath unsatisfiable Build-Depends(-Arch) on amd64: libflint-arb-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on arm64: libflint-arb-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on i386: libflint-arb-dev
    • Build-Depends(-Arch): sagemath brial (not considered)
    • Build-Depends(-Arch): sagemath eclib (not considered)
    • Build-Depends(-Arch): sagemath palp (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 ♻
    • 523 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
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • autopkgtest for segyio/1.8.3-1.2: riscv64: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/segyio.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 523 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 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 ♻
    • 524 days old (needed 5 days)
• openems (- to 0.0.35+git20190103.6a75e98+dfsg.1-3.2)
  • Migration status for openems (- to 0.0.35+git20190103.6a75e98+dfsg.1-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libcsxcad0/amd64 has unsatisfiable dependency
    • libopenems0/amd64 has unsatisfiable dependency
    • libqcsxcad0/amd64 has unsatisfiable dependency
    • openems/amd64 has unsatisfiable dependency
    • python3-openems/amd64 has unsatisfiable dependency
    • libcsxcad0/arm64 has unsatisfiable dependency
    • libopenems0/arm64 has unsatisfiable dependency
    • libqcsxcad0/arm64 has unsatisfiable dependency
    • openems/arm64 has unsatisfiable dependency
    • python3-openems/arm64 has unsatisfiable dependency
    • libcsxcad0/i386 has unsatisfiable dependency
    • libopenems0/i386 has unsatisfiable dependency
    • libqcsxcad0/i386 has unsatisfiable dependency
    • openems/i386 has unsatisfiable dependency
    • python3-openems/i386 has unsatisfiable dependency
    • libcsxcad0/mips64el has unsatisfiable dependency
    • libopenems0/mips64el has unsatisfiable dependency
    • libqcsxcad0/mips64el has unsatisfiable dependency
    • openems/mips64el has unsatisfiable dependency
    • python3-openems/mips64el has unsatisfiable dependency
    • libcsxcad0/ppc64el has unsatisfiable dependency
    • libopenems0/ppc64el has unsatisfiable dependency
    • libqcsxcad0/ppc64el has unsatisfiable dependency
    • openems/ppc64el has unsatisfiable dependency
    • python3-openems/ppc64el has unsatisfiable dependency
    • libcsxcad0/s390x has unsatisfiable dependency
    • libopenems0/s390x has unsatisfiable dependency
    • libqcsxcad0/s390x has unsatisfiable dependency
    • openems/s390x has unsatisfiable dependency
    • python3-openems/s390x has unsatisfiable dependency
    • Updating openems would introduce bugs in testing: #1054794, #1056826
    • autopkgtest for openems/0.0.35+git20190103.6a75e98+dfsg.1-3.2: riscv64: Regression or new test ♻
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • Depends: openems boost1.74 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openems.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
    • Waiting for reproducibility test results on armhf - info ♻
    • 524 days old (needed 5 days)
• ruby-gitlab-markup (- to 1.9.0-1)
  • Migration status for ruby-gitlab-markup (- to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gitlab-markup would introduce bugs in testing: #1053838
    • Build-Depends(-Arch): ruby-gitlab-markup ruby-html-pipeline (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gitlab-markup.html
    • autopkgtest for ruby-gitlab-markup/1.9.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 524 days old (needed 2 days)
• ruby-gruff (- to 0.6.0-2)
  • Migration status for ruby-gruff (- to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-gruff would introduce bugs in testing: #1054733
    • autopkgtest for ruby-gruff/0.6.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: 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
    • 524 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
    • 525 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 ♻
    • 525 days old (needed 5 days)
• gfpoken (- to 1-4)
  • Migration status for gfpoken (- to 1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gfpoken blender (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfpoken.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 526 days old (needed 5 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
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/f/freesas.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 527 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 ♻
    • 527 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 ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 527 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
    • 527 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 ♻
    • 527 days old (needed 5 days)
• swift-im (- to 5.0~alpha2.145.g12d031cf8+dfsg-3)
  • Migration status for swift-im (- to 5.0~alpha2.145.g12d031cf8+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libswiften0/armel has unsatisfiable dependency
    • libswiften0/armhf has unsatisfiable dependency
    • Updating swift-im would introduce bugs in testing: #1032724, #1056100
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • Depends: swift-im boost1.74 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swift-im.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 527 days old (needed 5 days)
• polyml (- to 5.7.1-5)
  • Migration status for polyml (- to 5.7.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating polyml would introduce bugs in testing: #1033835
    • autopkgtest for polyml/5.7.1-5: amd64: Regression or new test ♻, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: 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 ♻
    • 528 days old (needed 5 days)
• python-catalogue (- to 2.1.0-4)
  • Migration status for python-catalogue (- to 2.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): 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-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 ♻
    • 529 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
    • 529 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
    • 530 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
    • 530 days old (needed 5 days)
• golang-github-containers-toolbox (- to 0.0.99.3+git20230118+446d7bfdef6a-2)
  • Migration status for golang-github-containers-toolbox (- to 0.0.99.3+git20230118+446d7bfdef6a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-containers-toolbox would introduce bugs in testing: #1060570
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-containers-toolbox.html
    • Reproducible on armhf - info ♻
    • 532 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)
    • Depends: psi4 chemps2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psi4.html
    • 532 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
    • 533 days old (needed 5 days)
• mikutter (- to 5.0.4+dfsg1-2)
  • Migration status for mikutter (- to 5.0.4+dfsg1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mikutter ruby-moneta (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mikutter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 533 days old (needed 5 days)
• mvdsv (- to 0.35-6)
  • Migration status for mvdsv (- to 0.35-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mvdsv would introduce bugs in testing: #1050187
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mvdsv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 533 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
    • 533 days old (needed 2 days)
• fence-agents (- to 4.12.1-1)
  • Migration status for fence-agents (- to 4.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fence-agents would introduce bugs in testing: #1060568
    • autopkgtest for fence-agents/4.12.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, 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/f/fence-agents.html
    • 534 days old (needed 5 days)
• php-horde (- to 5.2.23+debian0-6)
  • Migration status for php-horde (- to 5.2.23+debian0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde php-horde-rpc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 534 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
    • 535 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
    • 535 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 ♻
    • 536 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
    • 536 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 ♻
    • 538 days old (needed 5 days)
• lava (- to 2023.01-2)
  • Migration status for lava (- to 2023.01-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lava would introduce bugs in testing: #1041342
    • autopkgtest for lava/2023.01-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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
    • 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 ♻
    • 538 days old (needed 5 days)
• vtk-dicom (- to 0.8.14-3.1)
  • Migration status for vtk-dicom (- to 0.8.14-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vtk-dicom would introduce bugs in testing: #1063195
    • 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: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vtk-dicom.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 538 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
    • 539 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): sfepy mayavi2 (not considered)
    • Build-Depends(-Arch): sfepy python-sparse (not considered)
    • Depends: sfepy mayavi2 (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 i386 - info ♻
    • 539 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.1.5-1/armel
    • Impossible Depends: glirc -> libssl3/3.1.5-1/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 ♻
    • 540 days old (needed 5 days)
• ruby-github-markup (- to 1.7.0+dfsg-6)
  • Migration status for ruby-github-markup (- to 1.7.0+dfsg-6): BLOCKED: 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: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 540 days old (needed 2 days)
• darcs (- to 2.16.5-1)
  • Migration status for darcs (- to 2.16.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating darcs would introduce bugs in testing: #1054953
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on amd64: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on arm64: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on armel: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on armhf: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on i386: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on mips64el: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-vector-dev (<< 0.13)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-cryptonite-dev (<< 0.30)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-fgl-dev (<< 5.8)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-hashable-dev (<< 1.4)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-memory-dev (<< 0.17)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-unix-compat-dev (<< 0.6)
    • darcs unsatisfiable Build-Depends(-Arch) on s390x: libghc-vector-dev (<< 0.13)
    • 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 ♻
    • 541 days old (needed 5 days)
• gtk-sharp3 (- to 2.99.3-4.1)
  • Migration status for gtk-sharp3 (- to 2.99.3-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gtk-sharp3 would introduce bugs in testing: #1017897, #1067940, #1068135
    • Impossible Depends: gtk-sharp3 -> libatk1.0-0/2.50.0-1+b1/armel
    • Impossible Depends: gtk-sharp3 -> libatk1.0-0/2.50.0-1+b1/armhf
    • Impossible Depends: gtk-sharp3 -> libglib2.0-0/2.78.4-1/armel
    • Impossible Depends: gtk-sharp3 -> libglib2.0-0/2.78.4-1/armhf
    • Depends: gtk-sharp3 gtk+3.0
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtk-sharp3.html
    • 541 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 ♻
    • 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
    • 541 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
    • 543 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 ♻
    • 544 days old (needed 5 days)
• firejail (- to 0.9.72-2)
  • Migration status for firejail (- to 0.9.72-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating firejail would introduce bugs in testing: #1069449
    • autopkgtest for firejail/0.9.72-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Regression or new test ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firejail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 545 days old (needed 5 days)
• vim-ultisnips (- to 3.2-2)
  • Migration status for vim-ultisnips (- to 3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vim-ultisnips would introduce bugs in testing: #1033510
    • autopkgtest for vim-ultisnips/3.2-2: amd64: Pass, arm64: Regression or new test ♻, armel: Pass, armhf: Pass, i386: Pass, 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 ♻
    • 545 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
    • 548 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
    • 548 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 ♻
    • 550 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
    • 550 days old (needed 5 days)
• opencl-clang-14 (- to 14.0.0-4)
  • Migration status for opencl-clang-14 (- to 14.0.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): opencl-clang-14 llvm-toolchain-14 (not considered)
    • Depends: opencl-clang-14 llvm-toolchain-14 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): opencl-clang-14 spirv-llvm-translator-14
    • Depends: opencl-clang-14 spirv-llvm-translator-14
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opencl-clang-14.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 550 days old (needed 5 days)
• python-sinfo (- to 1.0.0-1)
  • Migration status for python-sinfo (- to 1.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-sinfo python-stdlib-list (not considered)
    • Depends: python-sinfo python-stdlib-list (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-sinfo.html
    • autopkgtest for python-sinfo/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
    • 550 days old (needed 2 days)
• drbd-utils (- to 9.22.0-1)
  • Migration status for drbd-utils (- to 9.22.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating drbd-utils would introduce bugs in testing: #1060545
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drbd-utils.html
    • autopkgtest for drbd-utils/9.22.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 ♻
    • 552 days old (needed 5 days)
• odpic (- to 4.6.0-1)
  • Migration status for odpic (- to 4.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating odpic would introduce bugs in testing: #1057936
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 552 days old (needed 5 days)
• libobjcryst (- to 2022.1.4+ds1-2)
  • Migration status for libobjcryst (- to 2022.1.4+ds1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libobjcryst newmat (not considered)
    • Depends: libobjcryst newmat (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libobjcryst.html
    • autopkgtest for libobjcryst/2022.1.4+ds1-2: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 553 days old (needed 2 days)
• pyobjcryst (- to 2.2.5-1)
  • Migration status for pyobjcryst (- to 2.2.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pyobjcryst libobjcryst (not considered)
    • Depends: pyobjcryst libobjcryst (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyobjcryst.html
    • autopkgtest for pyobjcryst/2.2.5-1: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 553 days old (needed 2 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
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/stimfit.html
    • Build-Depends(-Arch): stimfit sip4 (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
    • 553 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 ♻
    • 554 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 ♻
    • 554 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
    • 554 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)
    • 556 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)
    • 556 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)
    • 556 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)
    • 556 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
    • 556 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 ♻
    • 556 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
    • 557 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)
    • 557 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
    • 557 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
    • 557 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
    • 557 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
    • 558 days old (needed 2 days)
• tetradraw (- to 2.0.3-10)
  • Migration status for tetradraw (- to 2.0.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tetradraw would introduce bugs in testing: #1057594
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tetradraw.html
    • 558 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
    • 559 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
    • 559 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
    • 560 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
    • 560 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 ♻
    • 562 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
    • 563 days old (needed 5 days)
• tiemu (- to 3.04~git20220826.cda2db4+dfsg-2)
  • Migration status for tiemu (- to 3.04~git20220826.cda2db4+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): tiemu libglade2 (not considered)
    • Depends: tiemu libglade2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiemu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 563 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 ♻
    • 564 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 ♻
    • 565 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 ♻
    • 567 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
    • 567 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
    • 568 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 ♻
    • 569 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 ♻
    • 569 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
    • 570 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 ♻
    • 571 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 ♻
    • 572 days old (needed 5 days)
• indi-pentax (- to 1.0+20221221102411-1)
  • Migration status for indi-pentax (- to 1.0+20221221102411-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • indi-pentax/armhf has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch armhf, not running autopkgtest there
    • 572 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: 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/m/multiplex.html
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 573 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 ♻
    • 577 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 ♻
    • 578 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 ♻
    • 578 days old (needed 5 days)
• pigx-rnaseq (- to 0.1.0-1.1)
  • Migration status for pigx-rnaseq (- to 0.1.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pigx-rnaseq would introduce bugs in testing: #1071333
    • Build-Depends(-Arch): pigx-rnaseq r-bioc-deseq2 (not considered)
    • Build-Depends(-Arch): pigx-rnaseq r-bioc-rtracklayer (not considered)
    • Build-Depends(-Arch): pigx-rnaseq r-bioc-summarizedexperiment (not considered)
    • Depends: pigx-rnaseq r-bioc-deseq2 (not considered)
    • Depends: pigx-rnaseq r-bioc-rtracklayer (not considered)
    • Depends: pigx-rnaseq r-bioc-summarizedexperiment (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pigx-rnaseq.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 579 days old (needed 5 days)
• prospector (- to 1.1.7-4)
  • Migration status for prospector (- to 1.1.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • prospector/amd64 has unsatisfiable dependency
    • prospector/arm64 has unsatisfiable dependency
    • Updating prospector would introduce bugs in testing: #1055672, #1071808, #947551
    • autopkgtest for prospector/1.1.7-4: riscv64: Regression or new test ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/prospector.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 579 days old (needed 5 days)
• atitvout (- to 0.4-13.2)
  • Migration status for atitvout (- to 0.4-13.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating atitvout would introduce bugs in testing: #1063644
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • New but not reproducible on i386 - info ♻
    • 583 days old (needed 5 days)
• jhbuild (- to 3.38.0-3.1)
  • Migration status for jhbuild (- to 3.38.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jhbuild would introduce bugs in testing: #1054720, #1065882
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jhbuild.html
    • 583 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
    • 585 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
    • Depends: linssid qtbase-opensource-src (not considered)
  • 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 ♻
    • 585 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 ♻
    • 585 days old (needed 5 days)
• backblaze-b2 (- to 1.3.8-6)
  • Migration status for backblaze-b2 (- to 1.3.8-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating backblaze-b2 would introduce bugs in testing: #1066743
    • autopkgtest for backblaze-b2/1.3.8-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Pass, 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/b/backblaze-b2.html
    • 586 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
    • autopkgtest for r-other-wasabi/1.0.1-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 586 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 ♻
    • 586 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
    • 587 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
    • 588 days old (needed 2 days)
• python-bottle-beaker (- to 0.1.3-6)
  • Migration status for python-bottle-beaker (- to 0.1.3-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: python-bottle-beaker beaker (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bottle-beaker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 588 days old (needed 5 days)
• node-puppeteer (- to 13.4.1+dfsg-2)
  • Migration status for node-puppeteer (- to 13.4.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-puppeteer would introduce bugs in testing: #1026868, #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
    • 590 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
    • 590 days old (needed 5 days)
• gitbatch (- to 0.5.0-4)
  • Migration status for gitbatch (- to 0.5.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitbatch would introduce bugs in testing: #1069419
    • autopkgtest for gitbatch/0.5.0-4: 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/g/gitbatch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 593 days old (needed 5 days)
• golang-github-sethvargo-go-fastly (- to 1.2.1+git20190805.5c6c8bd-3)
  • Migration status for golang-github-sethvargo-go-fastly (- to 1.2.1+git20190805.5c6c8bd-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-sethvargo-go-fastly golang-github-ajg-form (not considered)
    • Depends: golang-github-sethvargo-go-fastly golang-github-ajg-form (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-sethvargo-go-fastly.html
    • autopkgtest for golang-github-sethvargo-go-fastly/1.2.1+git20190805.5c6c8bd-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 593 days old (needed 2 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
    • 593 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 ♻
    • 593 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
    • 595 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
  • 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 ♻
    • 595 days old (needed 5 days)
• octocatalog-diff (- to 2.1.0-1)
  • Migration status for octocatalog-diff (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octocatalog-diff would introduce bugs in testing: #1025300
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octocatalog-diff.html
    • autopkgtest for octocatalog-diff/2.1.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 595 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
    • 595 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 ♻
    • 595 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 ♻
    • 595 days old (needed 5 days)
• python-bonsai (- to 1.5.0+ds-3)
  • Migration status for python-bonsai (- to 1.5.0+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-bonsai would introduce bugs in testing: #1067266
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bonsai.html
    • autopkgtest for python-bonsai/1.5.0+ds-3: 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
    • 595 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 ♻
    • 596 days old (needed 5 days)
• pd-iemutils (- to 0.0.20210927-2)
  • Migration status for pd-iemutils (- to 0.0.20210927-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pd-iemutils would introduce bugs in testing: #1066502
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pd-iemutils.html
    • 596 days old (needed 5 days)
• perl-doc-html (- to 5.26.0-7)
  • Migration status for perl-doc-html (- to 5.26.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating perl-doc-html would introduce bugs in testing: #907974
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/perl-doc-html.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 596 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
    • 599 days old (needed 5 days)
• python-webargs (- to 8.0.1-2)
  • Migration status for python-webargs (- to 8.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-webargs/8.0.1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-webargs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 599 days old (needed 5 days)
• gnome-authenticator (- to 3.32.2+dfsg1-5)
  • Migration status for gnome-authenticator (- to 3.32.2+dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-authenticator would introduce bugs in testing: #993849
    • Build-Depends(-Arch): gnome-authenticator libhandy (not considered)
    • Depends: gnome-authenticator libhandy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-authenticator.html
    • autopkgtest for gnome-authenticator/3.32.2+dfsg1-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 601 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
    • 601 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
    • 601 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
    • 601 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 ♻
    • 601 days old (needed 5 days)
• heudiconv (- to 0.11.6-1)
  • Migration status for heudiconv (- to 0.11.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for heudiconv/0.11.6-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
    • Build-Depends(-Arch): heudiconv datalad (not considered)
    • Build-Depends(-Arch): heudiconv nipype (not considered)
    • Depends: heudiconv nipype (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/heudiconv.html
    • Waiting for reproducibility test results on armhf - info ♻
    • 601 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
    • 601 days old (needed 2 days)
• golang-github-jesseduffield-asciigraph (- to 0.4.1+git20190605.6d88e39-3)
  • Migration status for golang-github-jesseduffield-asciigraph (- to 0.4.1+git20190605.6d88e39-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-asciigraph would introduce bugs in testing: #1032108
    • autopkgtest for golang-github-jesseduffield-asciigraph/0.4.1+git20190605.6d88e39-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-jesseduffield-asciigraph.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 602 days old (needed 5 days)
• golang-github-jesseduffield-pty (- to 1.1.3+git20191112.07ed706-2)
  • Migration status for golang-github-jesseduffield-pty (- to 1.1.3+git20191112.07ed706-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-jesseduffield-pty would introduce bugs in testing: #1032111
    • autopkgtest for golang-github-jesseduffield-pty/1.1.3+git20191112.07ed706-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/g/golang-github-jesseduffield-pty.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 602 days old (needed 5 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 ♻
    • 602 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
    • 602 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
    • 602 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
    • 602 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
    • 602 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
    • 602 days old (needed 2 days)
• opensysusers (- to 0.7.3-2)
  • Migration status for opensysusers (- to 0.7.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opensysusers would introduce bugs in testing: #1055517
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opensysusers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 602 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 ♻
    • 602 days old (needed 5 days)
• shush (- to 1.2.3-5.1)
  • Migration status for shush (- to 1.2.3-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shush would introduce bugs in testing: #999964
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shush.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 602 days old (needed 5 days)
• syncmaildir (- to 1.3.0-2)
  • Migration status for syncmaildir (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating syncmaildir would introduce bugs in testing: #1000322
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/syncmaildir.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 604 days old (needed 5 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 ♻
    • 606 days old (needed 5 days)
• kodi-visualization-waveform (- to 20.2.1+ds1-1)
  • Migration status for kodi-visualization-waveform (- to 20.2.1+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kodi-visualization-waveform would introduce bugs in testing: #1069299
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kodi-visualization-waveform.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 607 days old (needed 5 days)
• platformio (- to 4.3.4-3)
  • Migration status for platformio (- to 4.3.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating platformio would introduce bugs in testing: #1053285, #988716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/platformio.html
    • autopkgtest for platformio/4.3.4-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 607 days old (needed 5 days)
• python-peachpy (- to 0.0~git20211013.257881e-1.1)
  • Migration status for python-peachpy (- to 0.0~git20211013.257881e-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-peachpy would introduce bugs in testing: #1072138
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-peachpy.html
    • Reproducible on amd64 - info ♻
    • 608 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 ♻
    • 609 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 ♻
    • 610 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 ♻
    • 611 days old (needed 5 days)
• fruit (- to 2.1.dfsg-10)
  • Migration status for fruit (- to 2.1.dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fruit would introduce bugs in testing: #1014187
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fruit.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 613 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
    • 613 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 ♻
    • 614 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 ♻
    • 617 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
    • 617 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 ♻
    • 618 days old (needed 5 days)
• objcryst-fox (- to 2022.1-1)
  • Migration status for objcryst-fox (- to 2022.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): objcryst-fox newmat (not considered)
    • Depends: objcryst-fox newmat (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/objcryst-fox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 619 days old (needed 5 days)
• octave-kernel (- to 0.32.0-4)
  • Migration status for octave-kernel (- to 0.32.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): octave-kernel metakernel (not considered)
    • Depends: octave-kernel metakernel (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-kernel.html
    • autopkgtest for octave-kernel/0.32.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
    • 620 days old (needed 2 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 ♻
    • 621 days old (needed 5 days)
• golang-github-blynn-nex (- to 0.0.0+git.2021.03.30.1a3320dab9-2)
  • Migration status for golang-github-blynn-nex (- to 0.0.0+git.2021.03.30.1a3320dab9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-blynn-nex would introduce bugs in testing: #1022957
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-blynn-nex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 622 days old (needed 5 days)
• pytest-services (- to 2.2.1+ds-3)
  • Migration status for pytest-services (- to 2.2.1+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytest-services would introduce bugs in testing: #1071776
    • autopkgtest for pytest-services/2.2.1+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 ♻
    • 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
    • 622 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
    • 623 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
    • 624 days old (needed 2 days)
• golang-github-libvirt-libvirt-go-xml (- to 7.4.0-1)
  • Migration status for golang-github-libvirt-libvirt-go-xml (- to 7.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-libvirt-libvirt-go-xml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 626 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 ♻
    • 632 days old (needed 5 days)
• flask-mongoengine (- to 1.0.0-1)
  • Migration status for flask-mongoengine (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flask-mongoengine would introduce bugs in testing: #1061042
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-mongoengine.html
    • 636 days old (needed 5 days)
• autolink (- to 0.10.0-1)
  • Migration status for autolink (- to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autolink.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 637 days old (needed 5 days)
• devpi-common (- to 3.2.2-3)
  • Migration status for devpi-common (- to 3.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating devpi-common would introduce bugs in testing: #1030453
    • autopkgtest for devpi-common/3.2.2-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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
    • 637 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)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dradio.html
    • 637 days old (needed 5 days)
• python-pytest-lazy-fixture (- to 0.6.3-2)
  • Migration status for python-pytest-lazy-fixture (- to 0.6.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pytest-lazy-fixture would introduce bugs in testing: #1063957
    • autopkgtest for python-pytest-lazy-fixture/0.6.3-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pytest-lazy-fixture.html
    • 637 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
    • 637 days old (needed 2 days)
• xcolmix (- to 1.07-10.1)
  • Migration status for xcolmix (- to 1.07-10.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xcolmix/armel has unsatisfiable dependency
    • xcolmix/armhf has unsatisfiable dependency
    • Updating xcolmix would introduce bugs in testing: #1066690
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcolmix.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 637 days old (needed 5 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
    • 638 days old (needed 5 days)
• libextutils-cbuilder-perl (- to 0.280236-2)
  • Migration status for libextutils-cbuilder-perl (- to 0.280236-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libextutils-cbuilder-perl would introduce bugs in testing: #1060712
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/libe/libextutils-cbuilder-perl.html
    • autopkgtest for libextutils-cbuilder-perl/0.280236-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: 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 ♻
    • 638 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 raku-meta6 (not considered)
    • Depends: raku raku-test-meta
  • 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 ♻
    • 638 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 ♻
    • 639 days old (needed 5 days)
• matrix-sydent (- to 2.5.1-1.1)
  • Migration status for matrix-sydent (- to 2.5.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating matrix-sydent would introduce bugs in testing: #1029442, #1035844, #1071799
    • 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 ♻
    • 639 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
    • autopkgtest for openscap-daemon/0.1.10-3.1: riscv64: Regression or new test ♻
  • 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 ♻
    • 639 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-bioc-titancna (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): bcbio freebayes (not considered)
    • Build-Depends(-Arch): bcbio r-bioc-degreport
    • Build-Depends(-Arch): bcbio r-bioc-htsfilter (not considered)
    • Build-Depends(-Arch): bcbio r-bioc-purecn
    • Build-Depends(-Arch): bcbio r-bioc-summarizedexperiment (not considered)
    • Build-Depends(-Arch): bcbio r-other-wasabi
  • 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 ♻
    • 641 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 ♻
    • 642 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
    • 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
    • 643 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
    • 647 days old (needed 5 days)
• bettercap-caplets (- to 0+git20210429-1)
  • Migration status for bettercap-caplets (- to 0+git20210429-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • bettercap-caplets/amd64 has unsatisfiable dependency
    • bettercap-caplets/arm64 has unsatisfiable dependency
    • Updating bettercap-caplets would introduce bugs in testing: #1053331
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/bettercap-caplets.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 648 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:
    • Updating theli would introduce bugs in testing: #1056689, #1069982
    • Build-Depends(-Arch): theli atlas (not considered)
    • Build-Depends(-Arch): theli scamp (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/theli.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 ♻
    • 650 days old (needed 5 days)
• cclive (- to 0.9.3-0.3)
  • Migration status for cclive (- to 0.9.3-0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cclive would introduce bugs in testing: #1000076
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cclive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 651 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvi2ps.html
    • 651 days old (needed 5 days)
• hw-probe (- to 1.6.5-1)
  • Migration status for hw-probe (- to 1.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: hw-probe hwinfo (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hw-probe.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 ♻
    • 658 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 ♻
    • 659 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, #1073096
    • autopkgtest for keras/2.3.1+dfsg2-1: riscv64: Regression or new test ♻
    • keras unsatisfiable Build-Depends(-Arch) on amd64: python3-theano
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/keras.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 661 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
    • 662 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
    • 664 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 ♻
    • 664 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-titan.html
    • 668 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 ♻
    • 668 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
    • 669 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/raku-meta6.html
    • 672 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
  • 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 ♻
    • 672 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 ♻
    • 673 days old (needed 5 days)
• watchman (- to 4.9.0-7)
  • Migration status for watchman (- to 4.9.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating watchman would introduce bugs in testing: #999930
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/watchman.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 673 days old (needed 5 days)
• roger-router (- to 2.4.2-3)
  • Migration status for roger-router (- to 2.4.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • roger-router/amd64 has unsatisfiable dependency
    • roger-router/arm64 has unsatisfiable dependency
    • roger-router/armel has unsatisfiable dependency
    • roger-router/armhf has unsatisfiable dependency
    • roger-router/i386 has unsatisfiable dependency
    • roger-router/mips64el has unsatisfiable dependency
    • roger-router/ppc64el has unsatisfiable dependency
    • roger-router/s390x has unsatisfiable dependency
    • Updating roger-router would introduce bugs in testing: #1019303, #1073299
    • Build-Depends(-Arch): roger-router librm (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/roger-router.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 677 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 ♻
    • 678 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
    • 684 days old (needed 2 days)
• librm (- to 2.2.3-1)
  • Migration status for librm (- to 2.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librm0/amd64 has unsatisfiable dependency
    • librm0/arm64 has unsatisfiable dependency
    • librm0/armel has unsatisfiable dependency
    • librm0/armhf has unsatisfiable dependency
    • librm0/i386 has unsatisfiable dependency
    • librm0/mips64el has unsatisfiable dependency
    • librm0/ppc64el has unsatisfiable dependency
    • librm0/s390x has unsatisfiable dependency
    • Updating librm would introduce bugs in testing: #1022008, #1037392
    • librm unsatisfiable Build-Depends(-Arch) on amd64: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on amd64: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on arm64: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on arm64: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armel: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armel: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armhf: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on armhf: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on i386: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on i386: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on mips64el: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on mips64el: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on ppc64el: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on ppc64el: libgssdp-1.2-dev | libgssdp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on s390x: libgupnp-1.2-dev | libgupnp-1.0-dev
    • librm unsatisfiable Build-Depends(-Arch) on s390x: libgssdp-1.2-dev | libgssdp-1.0-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libr/librm.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 686 days old (needed 5 days)
• gnome-subtitles (- to 1.8-1)
  • Migration status for gnome-subtitles (- to 1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-subtitles would introduce bugs in testing: #1053529, #1067191, #1069308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-subtitles.html
    • 690 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 ♻
    • 693 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:
    • Updating cpl-plugin-muse would introduce bugs in testing: #1069508, #1071682
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpl-plugin-muse.html
    • autopkgtest for cpl-plugin-muse/2.8.7+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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 699 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:
    • Updating cpl-plugin-uves would introduce bugs in testing: #1071685
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpl-plugin-uves.html
    • autopkgtest for cpl-plugin-uves/6.1.8+dfsg-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 699 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:
    • Updating cpl-plugin-vimos would introduce bugs in testing: #1071688
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpl-plugin-vimos.html
    • autopkgtest for cpl-plugin-vimos/4.1.7+dfsg-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 699 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:
    • python3-django-cachalot/amd64 has unsatisfiable dependency
    • python3-django-cachalot/arm64 has unsatisfiable dependency
    • Updating django-cachalot would introduce bugs in testing: #1055207
    • django-cachalot unsatisfiable Build-Depends(-Arch) on amd64: python3-django (<< 3:3.3~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/django-cachalot.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 ♻
    • 699 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
  • 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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 700 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 ♻
    • 701 days old (needed 5 days)
• debian-design (- to 3.0.27)
  • Migration status for debian-design (- to 3.0.27): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: debian-design scribus (not considered)
    • Invalidated by dependency
    • Depends: debian-design blender
    • Depends: debian-design bookletimposer (not considered)
    • Depends: debian-design pdfposter (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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 703 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 ♻
    • 704 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 ♻
    • 705 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
    • 705 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 ♻
    • 706 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
    • 706 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 711 days old (needed 5 days)
• pass-audit (- to 1.2-1.1)
  • Migration status for pass-audit (- to 1.2-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): pass-audit python-zxcvbn (not considered)
    • Depends: pass-audit python-zxcvbn (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pass-audit.html
    • autopkgtest for pass-audit/1.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
    • 711 days old (needed 2 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
    • 711 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
    • 711 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 ♻
    • 714 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
    • 714 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 ♻
    • 715 days old (needed 5 days)
• haskell-hsyaml (- to 0.2.1.1-2)
  • Migration status for haskell-hsyaml (- to 0.2.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hsyaml-dev/amd64 has unsatisfiable dependency
    • libghc-hsyaml-doc/amd64 has unsatisfiable dependency
    • libghc-hsyaml-prof/amd64 has unsatisfiable dependency
    • libghc-hsyaml-dev/arm64 has unsatisfiable dependency
    • libghc-hsyaml-doc/arm64 has unsatisfiable dependency
    • libghc-hsyaml-prof/arm64 has unsatisfiable dependency
    • libghc-hsyaml-dev/armel has unsatisfiable dependency
    • libghc-hsyaml-prof/armel has unsatisfiable dependency
    • libghc-hsyaml-dev/armhf has unsatisfiable dependency
    • libghc-hsyaml-prof/armhf has unsatisfiable dependency
    • libghc-hsyaml-dev/i386 has unsatisfiable dependency
    • libghc-hsyaml-prof/i386 has unsatisfiable dependency
    • libghc-hsyaml-dev/mips64el has unsatisfiable dependency
    • libghc-hsyaml-prof/mips64el has unsatisfiable dependency
    • libghc-hsyaml-dev/ppc64el has unsatisfiable dependency
    • libghc-hsyaml-prof/ppc64el has unsatisfiable dependency
    • libghc-hsyaml-dev/s390x has unsatisfiable dependency
    • libghc-hsyaml-prof/s390x has unsatisfiable dependency
    • Updating haskell-hsyaml would introduce bugs in testing: #1054863
    • 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-hsyaml.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 716 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 ♻
    • 722 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)
    • Depends: maildrop courier-authlib (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
    • 722 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 ♻
    • 722 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
    • 724 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 ♻
    • 724 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 ♻
    • 724 days old (needed 5 days)
• gcc-10-doc (- to 10.4.0-1)
  • Migration status for gcc-10-doc (- to 10.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-10-doc would introduce bugs in testing: #1032733
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 727 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)
    • 727 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
    • 728 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 ♻
    • 728 days old (needed 5 days)
• ruby-toml (- to 0.2.0-4)
  • Migration status for ruby-toml (- to 0.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ruby-toml/0.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-toml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 728 days old (needed 5 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
    • 735 days old (needed 2 days)
• php-fig-link-util (- to 1.2.0-1)
  • Migration status for php-fig-link-util (- to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-fig-link-util would introduce bugs in testing: #947346
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fig-link-util.html
    • autopkgtest for php-fig-link-util/1.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 736 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 ♻
    • 738 days old (needed 5 days)
• apertium-cy-en (- to 0.1.1~r57554-9)
  • Migration status for apertium-cy-en (- to 0.1.1~r57554-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-cy-en would introduce bugs in testing: #1016320
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-cy-en.html
    • autopkgtest for apertium-cy-en/0.1.1~r57554-9: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 740 days old (needed 2 days)
• apertium-mlt-ara (- to 0.2.0~r62623-3)
  • Migration status for apertium-mlt-ara (- to 0.2.0~r62623-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-mlt-ara would introduce bugs in testing: #1016336
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-mlt-ara.html
    • 741 days old (needed 5 days)
• synfig (- to 1.5.1+dfsg-3)
  • Migration status for synfig (- to 1.5.1+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating synfig would introduce bugs in testing: #1063004
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/synfig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 741 days old (needed 5 days)
• qtox (- to 1.17.6-0.1)
  • Migration status for qtox (- to 1.17.6-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for qtox/1.17.6-0.1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qtox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 745 days old (needed 5 days)
• ruby-fcgi (- to 0.9.2.1-3)
  • Migration status for ruby-fcgi (- to 0.9.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-fcgi/armel has unsatisfiable dependency
    • ruby-fcgi/armhf has unsatisfiable dependency
    • Updating ruby-fcgi would introduce bugs in testing: #1032485
    • autopkgtest for ruby-fcgi/0.9.2.1-3: 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/r/ruby-fcgi.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 745 days old (needed 5 days)
• astroquery (- to 0.4.6+dfsg-4)
  • Migration status for astroquery (- to 0.4.6+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating astroquery would introduce bugs in testing: #1057543
    • autopkgtest for astroquery/0.4.6+dfsg-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): astroquery astropy-helpers (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astroquery.html
    • 747 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
    • 747 days old (needed 2 days)
• r-cran-restfulr (- to 0.0.15-1)
  • Migration status for r-cran-restfulr (- to 0.0.15-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-restfulr r-bioc-s4vectors (not considered)
    • Depends: r-cran-restfulr r-bioc-s4vectors (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-restfulr.html
    • autopkgtest for r-cran-restfulr/0.0.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 752 days old (needed 2 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.2-3+deb12u7/armel
    • Impossible Depends: ippsample -> libcups2/2.4.2-3+deb12u7/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 ♻
    • 755 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 ♻
    • 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
    • 755 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
    • 755 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
  • 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 amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 756 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 ♻
    • 757 days old (needed 5 days)
• apertium-crh-tur (- to 0.3.0-2)
  • Migration status for apertium-crh-tur (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-crh-tur would introduce bugs in testing: #1016319
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-crh-tur.html
    • 758 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
    • New but not reproducible on amd64 - info ♻
    • 759 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 ♻
    • 760 days old (needed 5 days)
• netcdf-parallel (- to 1:4.9.0-1)
  • Migration status for netcdf-parallel (- to 1:4.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netcdf-parallel would introduce bugs in testing: #1071331
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netcdf-parallel.html
    • Reproducible on armhf - info ♻
    • 761 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
    • 762 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 ♻
    • 762 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 ♻
    • 762 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 ♻
    • 762 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 ♻
    • 762 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 ♻
    • 762 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 ♻
    • 762 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 ♻
    • 762 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 ♻
    • 762 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 ♻
    • 762 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 ♻
    • 762 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: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-k0swe-wsjtx-go.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 764 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 ♻
    • 765 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
    • 769 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 ♻
    • 770 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bsm-pool.html
    • autopkgtest for golang-github-bsm-pool/0.8.0-6: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 771 days old (needed 2 days)
• python-zxcvbn (- to 4.4.28-3)
  • Migration status for python-zxcvbn (- to 4.4.28-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-zxcvbn would introduce bugs in testing: #1068975
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-zxcvbn.html
    • autopkgtest for python-zxcvbn/4.4.28-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 ♻
    • 771 days old (needed 5 days)
• ripe-atlas-sagan (- to 1.2.2-3)
  • Migration status for ripe-atlas-sagan (- to 1.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ripe-atlas-sagan would introduce bugs in testing: #1026529
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ripe-atlas-sagan.html
    • 771 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 ♻
    • 774 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
    • 775 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
    • 780 days old (needed 5 days)
• flask-testing (- to 0.8.1-2)
  • Migration status for flask-testing (- to 0.8.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating flask-testing would introduce bugs in testing: #1026543
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask-testing.html
    • 781 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, #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 ♻
    • 781 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
    • 781 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
    • 782 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: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: 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: python-aiohttp-apispec python-webargs (not considered)
  • 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 ♻
    • 782 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-assert-cli rust-failure-derive (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): rust-assert-cli rust-failure
    • Depends: rust-assert-cli rust-failure
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-assert-cli.html
    • autopkgtest for rust-assert-cli/0.6.3-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻, 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 ♻
    • 783 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 ♻
    • 784 days old (needed 5 days)
• autoconf2.64 (- to 2.64+dfsg-1.1)
  • Migration status for autoconf2.64 (- to 2.64+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating autoconf2.64 would introduce bugs in testing: #1039531
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autoconf2.64.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 786 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 ♻
    • 786 days old (needed 5 days)
• python-cx-oracle (- to 8.3.0-3)
  • Migration status for python-cx-oracle (- to 8.3.0-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-cx-oracle odpic (not considered)
    • Depends: python-cx-oracle odpic (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for python-cx-oracle/8.3.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 786 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 ♻
    • 789 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
    • 795 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
    • 795 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
    • 795 days old (needed 5 days)
• cider (- to 0.19.0+dfsg-3)
  • Migration status for cider (- to 0.19.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cider would introduce bugs in testing: #1017834, #1071793
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cider.html
    • autopkgtest for cider/0.19.0+dfsg-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 796 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
    • 797 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
    • 797 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 ♻
    • 803 days old (needed 5 days)
• libx86emu (- to 3.5-1)
  • Migration status for libx86emu (- to 3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libx86emu would introduce bugs in testing: #1069498
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libx86emu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 807 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
  • 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
    • 810 days old (needed 2 days)
• django-macaddress (- to 1.5.0-3)
  • Migration status for django-macaddress (- to 1.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-macaddress would introduce bugs in testing: #1054372
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-macaddress.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 812 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
    • 822 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 ♻
    • 823 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
    • 824 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 ♻
    • 825 days old (needed 5 days)
• synfigstudio (- to 1.5.1-1)
  • Migration status for synfigstudio (- to 1.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): synfigstudio synfig (not considered)
    • Depends: synfigstudio synfig (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/synfigstudio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 826 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
    • 827 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 ♻
    • 829 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
    • 831 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
    • Depends: i2masschroq qtbase-opensource-src (not considered)
  • 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
    • 836 days old (needed 5 days)
• bully (- to 1.4.00-2)
  • Migration status for bully (- to 1.4.00-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: bully aircrack-ng (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bully.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 837 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
    • 840 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 ♻
    • 845 days old (needed 5 days)
• obs-ptz (- to 0.10.4-1)
  • Migration status for obs-ptz (- to 0.10.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • obs-ptz/armel has unsatisfiable dependency
    • obs-ptz/armhf has unsatisfiable dependency
    • Updating obs-ptz would introduce bugs in testing: #1022361
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/obs-ptz.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 845 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
    • 847 days old (needed 2 days)
• ats2-lang (- to 0.4.2-1.1)
  • Migration status for ats2-lang (- to 0.4.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ats2-lang would introduce bugs in testing: #1066211
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ats2-lang.html
    • 852 days old (needed 5 days)
• qiskit-ibmq-provider (- to 0.4.6-4)
  • Migration status for qiskit-ibmq-provider (- to 0.4.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qiskit-ibmq-provider would introduce bugs in testing: #1025181, #1071812
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/q/qiskit-ibmq-provider.html
    • 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:
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 855 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qiskit-terra.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 855 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 ♻
    • 860 days old (needed 5 days)
• notcurses (- to 3.0.7+dfsg.1-1)
  • Migration status for notcurses (- to 3.0.7+dfsg.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating notcurses would introduce bugs in testing: #1001661, #1015747
    • autopkgtest for notcurses/3.0.7+dfsg.1-1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Pass, riscv64: Pass, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/notcurses.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 875 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
    • 877 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
    • 879 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 ♻
    • 881 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
    • 882 days old (needed 5 days)
• scala-mode-el (- to 1:1.1.0-3)
  • Migration status for scala-mode-el (- to 1:1.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scala-mode-el would introduce bugs in testing: #1052917
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scala-mode-el.html
    • autopkgtest for scala-mode-el/1:1.1.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 882 days old (needed 2 days)
• node-devtools-protocol (- to 0.0.801017-1)
  • Migration status for node-devtools-protocol (- to 0.0.801017-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by andrius.merkys@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-devtools-protocol.html
    • autopkgtest for node-devtools-protocol/0.0.801017-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 883 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 ♻
    • 883 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
    • 883 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 ♻
    • 883 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 arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 884 days old (needed 2 days)
• consonance (- to 0.1.5-1)
  • Migration status for consonance (- to 0.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating consonance would introduce bugs in testing: #1058213
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/consonance.html
    • autopkgtest for consonance/0.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
    • 887 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 ♻
    • 887 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
    • 887 days old (needed 5 days)
• rust-exitfailure (- to 0.5.1-1)
  • Migration status for rust-exitfailure (- to 0.5.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-exitfailure rust-failure (not considered)
    • Depends: rust-exitfailure rust-failure (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-exitfailure.html
    • 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 ♻, 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 ♻
    • 888 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 ♻
    • 890 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gcc-h8300-hms binutils-h8300-hms (not considered)
    • Depends: gcc-h8300-hms binutils-h8300-hms (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-h8300-hms.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 ♻
    • 892 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
    • Waiting for reproducibility test results on armhf - info ♻
    • 894 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 ♻
    • 899 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 ♻
    • 899 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 ♻
    • 900 days old (needed 5 days)
• moviepy (- to 1.0.3-2)
  • Migration status for moviepy (- to 1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating moviepy would introduce bugs in testing: #1004642
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/moviepy.html
    • 902 days old (needed 5 days)
• python-freecontact (- to 1.1-6)
  • Migration status for python-freecontact (- to 1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-freecontact/armel has unsatisfiable dependency
    • python3-freecontact/i386 has unsatisfiable dependency
    • python3-freecontact/mips64el has unsatisfiable dependency
    • python3-freecontact/s390x has unsatisfiable dependency
    • autopkgtest for python-freecontact/1.1-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): python-freecontact freecontact (not considered)
    • Depends: python-freecontact freecontact (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-freecontact.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch i386, 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 ♻
    • 905 days old (needed 5 days)
• libfreecontact-perl (- to 0.08-9)
  • Migration status for libfreecontact-perl (- to 0.08-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): libfreecontact-perl freecontact (not considered)
    • Depends: libfreecontact-perl freecontact (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libf/libfreecontact-perl.html
    • autopkgtest for libfreecontact-perl/0.08-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
    • 907 days old (needed 2 days)
• imdbpy (- to 2021.04.18-3)
  • Migration status for imdbpy (- to 2021.04.18-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating imdbpy would introduce bugs in testing: #1017747
    • autopkgtest for imdbpy/2021.04.18-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/imdbpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 908 days old (needed 5 days)
• xcb (- to 2.4-8)
  • Migration status for xcb (- to 2.4-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xcb would introduce bugs in testing: #1050607
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 908 days old (needed 5 days)
• idseq-bench (- to 0.0~git20210602.27fb6dc-1)
  • Migration status for idseq-bench (- to 0.0~git20210602.27fb6dc-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for idseq-bench/0.0~git20210602.27fb6dc-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: 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 ♻
    • 910 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
    • 915 days old (needed 2 days)
• massivethreads (- to 1.00-4)
  • Migration status for massivethreads (- to 1.00-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating massivethreads would introduce bugs in testing: #1014566
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/massivethreads.html
    • 918 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 ♻
    • 918 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 ♻
    • 919 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 ♻
    • 921 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
    • 922 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 ♻
    • 924 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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiledarray.html
    • 924 days old (needed 5 days)
• mlucas (- to 20.1.1-1)
  • Migration status for mlucas (- to 20.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mlucas would introduce bugs in testing: #1013910, #1014547, #1027776
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on i386
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlucas.html
    • Reproducible on amd64 - info ♻
    • 925 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
    • 926 days old (needed 2 days)
• xtide (- to 2.15.2-1.1)
  • Migration status for xtide (- to 2.15.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xtide/armel has unsatisfiable dependency
    • xtide/armhf has unsatisfiable dependency
    • Updating xtide would introduce bugs in testing: #1026439
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xtide.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 928 days old (needed 5 days)
• zmodemjs (- to 0.1.10+dfsg-2)
  • Migration status for zmodemjs (- to 0.1.10+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zmodemjs would introduce bugs in testing: #1005454
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zmodemjs.html
    • 928 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
    • 930 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
    • 934 days old (needed 5 days)
• kore (- to 4.1.0-6)
  • Migration status for kore (- to 4.1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kore would introduce bugs in testing: #1033711
    • autopkgtest for kore/4.1.0-6: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kore.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 939 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
    • 941 days old (needed 5 days)
• mate-optimus (- to 21.04.0-1)
  • Migration status for mate-optimus (- to 21.04.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mate-optimus would introduce bugs in testing: #987819
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-optimus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 944 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
  • 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
    • 950 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 ♻
    • 951 days old (needed 5 days)
• epigrass (- to 3.0.3+dfsg-2)
  • Migration status for epigrass (- to 3.0.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating epigrass would introduce bugs in testing: #995966, #998265
    • autopkgtest for epigrass/3.0.3+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: epigrass numba (not considered)
    • Depends: epigrass python-altair (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 ♻
    • 952 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
    • 962 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
    • 962 days old (needed 5 days)
• ruby-diaspora-federation-rails (- to 0.2.7-1)
  • Migration status for ruby-diaspora-federation-rails (- to 0.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-diaspora-federation-rails would introduce bugs in testing: #1071779
    • autopkgtest for ruby-diaspora-federation-rails/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-rails ruby-diaspora-federation (not considered)
    • Depends: ruby-diaspora-federation-rails ruby-diaspora-federation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-diaspora-federation-rails.html
    • 962 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 ♻
    • 966 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 ♻
    • 967 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
    • 967 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 ♻
    • 968 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 ♻
    • 968 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 ♻
    • 968 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
    • 968 days old (needed 5 days)
• glogic (- to 2.6-6)
  • Migration status for glogic (- to 2.6-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating glogic would introduce bugs in testing: #1058575
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glogic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 971 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
    • 972 days old (needed 5 days)
• cpl-plugin-xshoo (- to 3.5.3+dfsg-1)
  • Migration status for cpl-plugin-xshoo (- to 3.5.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpl-plugin-xshoo would introduce bugs in testing: #1035786
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpl-plugin-xshoo.html
    • autopkgtest for cpl-plugin-xshoo/3.5.3+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 975 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
    • 976 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
    • 979 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 ♻
    • 982 days old (needed 5 days)
• mbdyn (- to 1.7.3-1)
  • Migration status for mbdyn (- to 1.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mbdyn would introduce bugs in testing: #999554
    • Not built on buildd: arch amd64 binaries uploaded by andrius.merkys@gmail.com
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mbdyn.html
    • 982 days old (needed 5 days)
• python-calendarweek (- to 0.5.0-1)
  • Migration status for python-calendarweek (- to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-calendarweek.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 982 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 ♻
    • 985 days old (needed 5 days)
• django-titofisto (- to 0.1.2.post1-1)
  • Migration status for django-titofisto (- to 0.1.2.post1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by natureshadow, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-titofisto.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 985 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 ♻
    • 985 days old (needed 5 days)
• cpl-plugin-fors (- to 5.5.7+dfsg-2)
  • Migration status for cpl-plugin-fors (- to 5.5.7+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpl-plugin-fors would introduce bugs in testing: #1071678
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpl-plugin-fors.html
    • autopkgtest for cpl-plugin-fors/5.5.7+dfsg-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 986 days old (needed 5 days)
• pprofile (- to 2.1.0-1)
  • Migration status for pprofile (- to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pprofile would introduce bugs in testing: #1058191
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pprofile.html
    • autopkgtest for pprofile/2.1.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 986 days old (needed 2 days)
• exodusii (- to 6.02.dfsg.1-10)
  • Migration status for exodusii (- to 6.02.dfsg.1-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): exodusii netcdf-parallel (not considered)
    • Depends: exodusii netcdf-parallel (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/exodusii.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 987 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
    • 990 days old (needed 2 days)
• python-gear (- to 0.5.8-6)
  • Migration status for python-gear (- to 0.5.8-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-gear would introduce bugs in testing: #1002430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gear.html
    • 991 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 ♻
    • 991 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 ♻
    • 993 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
    • 998 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
    • 1004 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, #999984
    • autopkgtest for prads/0.3.3-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • 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
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1004 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
    • 1005 days old (needed 5 days)
• php-webimpress-safe-writer (- to 2.2.0-1)
  • Migration status for php-webimpress-safe-writer (- to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-webimpress-safe-writer would introduce bugs in testing: #981233
    • autopkgtest for php-webimpress-safe-writer/2.2.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-webimpress-safe-writer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1006 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
    • 1008 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 ♻
    • 1008 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
    • 1010 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
    • 1010 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 ♻
    • 1013 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
    • 1015 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 ♻
    • 1015 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
    • 1019 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 ♻
    • 1023 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
    • 1025 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
    • 1027 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)
    • 1035 days old (needed 5 days)
• mdk3 (- to 6.0-8)
  • Migration status for mdk3 (- to 6.0-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: mdk3 aircrack-ng (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdk3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1036 days old (needed 5 days)
• shotdetect (- to 1.0.86-6)
  • Migration status for shotdetect (- to 1.0.86-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • shotdetect/amd64 has unsatisfiable dependency
    • shotdetect/arm64 has unsatisfiable dependency
    • shotdetect/armel has unsatisfiable dependency
    • shotdetect/armhf has unsatisfiable dependency
    • shotdetect/i386 has unsatisfiable dependency
    • shotdetect/mips64el has unsatisfiable dependency
    • shotdetect/ppc64el has unsatisfiable dependency
    • shotdetect/s390x has unsatisfiable dependency
    • Updating shotdetect would introduce bugs in testing: #1004719
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/shotdetect.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1037 days old (needed 5 days)
• snort (- to 2.9.15.1-6)
  • Migration status for snort (- to 2.9.15.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • snort/armel has unsatisfiable dependency
    • snort/armhf has unsatisfiable dependency
    • snort-common-libraries/ppc64el has unsatisfiable dependency
    • Updating snort would introduce bugs in testing: #1019230, #1021276, #1064328, #1067951, #1068036, #999956
    • snort unsatisfiable Build-Depends(-Arch) on ppc64el: libluajit-5.1-dev
    • Impossible Depends: snort -> libssl3/3.1.5-1/armel
    • Impossible Depends: snort -> libssl3/3.1.5-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snort.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 1043 days old (needed 5 days)
• eclipse-tracecompass (- to 7.0.0+repack-1)
  • Migration status for eclipse-tracecompass (- to 7.0.0+repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • eclipse-tracecompass/amd64 has unsatisfiable dependency
    • eclipse-tracecompass/arm64 has unsatisfiable dependency
    • Updating eclipse-tracecompass would introduce bugs in testing: #1010983, #1035594
    • 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
  • 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 ♻
    • 1049 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 ♻
    • 1054 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
    • 1054 days old (needed 5 days)
• gcc-9-doc (- to 9.4.0-1)
  • Migration status for gcc-9-doc (- to 9.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-9-doc would introduce bugs in testing: #995061
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1056 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 ♻
    • 1056 days old (needed 5 days)
• morty (- to 0.2.0-3)
  • Migration status for morty (- to 0.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating morty would introduce bugs in testing: #1052139
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/morty.html
    • autopkgtest for morty/0.2.0-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1059 days old (needed 2 days)
• purify (- to 2.0.0-6)
  • Migration status for purify (- to 2.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libpurify2.0/amd64 has unsatisfiable dependency
    • purify/amd64 has unsatisfiable dependency
    • libpurify2.0/arm64 has unsatisfiable dependency
    • purify/arm64 has unsatisfiable dependency
    • libpurify2.0/armel has unsatisfiable dependency
    • purify/armel has unsatisfiable dependency
    • libpurify2.0/armhf has unsatisfiable dependency
    • purify/armhf has unsatisfiable dependency
    • libpurify2.0/i386 has unsatisfiable dependency
    • purify/i386 has unsatisfiable dependency
    • libpurify2.0/ppc64el has unsatisfiable dependency
    • purify/ppc64el has unsatisfiable dependency
    • libpurify2.0/s390x has unsatisfiable dependency
    • purify/s390x has unsatisfiable dependency
    • Updating purify would introduce bugs in testing: #1001528
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/purify.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1065 days old (needed 5 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
    • 1065 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
    • 1077 days old (needed 5 days)
• qiskit-aer (- to 0.4.1-2)
  • Migration status for qiskit-aer (- to 0.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-qiskit-aer/amd64 has unsatisfiable dependency
    • python3-qiskit-aer/arm64 has unsatisfiable dependency
    • python3-qiskit-aer/armhf has unsatisfiable dependency
    • python3-qiskit-aer/i386 has unsatisfiable dependency
    • python3-qiskit-aer/mips64el has unsatisfiable dependency
    • python3-qiskit-aer/ppc64el has unsatisfiable dependency
    • Updating qiskit-aer would introduce bugs in testing: #1027206, #1028896, #1056881
    • Build-Depends(-Arch): qiskit-aer qiskit-terra (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/q/qiskit-aer.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • 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)
• 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 ♻
    • 1139 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
    • 1142 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
    • 1146 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:
    • slic3r/i386 has unsatisfiable dependency
    • Updating slic3r would introduce bugs in testing: #1034848
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r.html
    • uninstallable on arch i386, not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1176 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
    • Reproducible on armhf - info ♻
    • 1180 days old (needed 5 days)
• davs2 (- to 1.6-1)
  • Migration status for davs2 (- to 1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating davs2 would introduce bugs in testing: #1024722
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/davs2.html
    • New but not reproducible on amd64 - info ♻
    • 1190 days old (needed 5 days)
• xavs2 (- to 1.3-1)
  • Migration status for xavs2 (- to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xavs2 would introduce bugs in testing: #1024723, #1071817
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xavs2.html
    • 1190 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 ♻
    • 1194 days old (needed 5 days)
• spdx-licenses (- to 3.8+dfsg-3)
  • Migration status for spdx-licenses (- to 3.8+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spdx-licenses would introduce bugs in testing: #975120
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spdx-licenses.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1195 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)
    • 1201 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 ♻
    • 1212 days old (needed 5 days)
• svtplay-dl (- to 3.0-2)
  • Migration status for svtplay-dl (- to 3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating svtplay-dl would introduce bugs in testing: #1061023
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/svtplay-dl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1220 days old (needed 5 days)
• enigmail (- to 2:2.2.4-0.3)
  • Migration status for enigmail (- to 2:2.2.4-0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating enigmail would introduce bugs in testing: #1030186, #975926
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/enigmail.html
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • 1231 days old (needed 5 days)
• rust-rust-code-analysis-cli (- to 0.0.19-1)
  • Migration status for rust-rust-code-analysis-cli (- to 0.0.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-rust-code-analysis-cli would introduce bugs in testing: #1017649
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on amd64: librust-crossbeam-0.7+default-dev
    • rust-rust-code-analysis-cli unsatisfiable Build-Depends(-Arch) on 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 ♻
    • 1239 days old (needed 5 days)
• hotspot (- to 1.3.0-2)
  • Migration status for hotspot (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hotspot would introduce bugs in testing: #1025573
    • Impossible Depends: hotspot -> policykit-1/124-2/amd64
    • Impossible Depends: hotspot -> policykit-1/124-2/arm64
    • Impossible Depends: hotspot -> policykit-1/124-2/armel
    • Impossible Depends: hotspot -> policykit-1/124-2/armhf
    • Impossible Depends: hotspot -> policykit-1/124-2/i386
    • Impossible Depends: hotspot -> policykit-1/124-2/mips64el
    • Impossible Depends: hotspot -> policykit-1/124-2/ppc64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hotspot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1240 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 ♻
    • 1242 days old (needed 5 days)
• fonts-cascadia-code (- to 2102.03-1)
  • Migration status for fonts-cascadia-code (- to 2102.03-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-cascadia-code would introduce bugs in testing: #997317
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-cascadia-code.html
    • 1244 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 ♻
    • 1245 days old (needed 5 days)
• php-facedetect (- to 1.1.0-19-g135c72a-2)
  • Migration status for php-facedetect (- to 1.1.0-19-g135c72a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-facedetect/amd64 has unsatisfiable dependency
    • php-facedetect/arm64 has unsatisfiable dependency
    • php-facedetect/armel has unsatisfiable dependency
    • php-facedetect/armhf has unsatisfiable dependency
    • php-facedetect/i386 has unsatisfiable dependency
    • php-facedetect/mips64el has unsatisfiable dependency
    • php-facedetect/ppc64el has unsatisfiable dependency
    • php-facedetect/s390x has unsatisfiable dependency
    • Updating php-facedetect would introduce bugs in testing: #1020977
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/php-facedetect.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1246 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 ♻
    • 1246 days old (needed 5 days)
• aiorwlock (- to 1.0.0-0.2)
  • Migration status for aiorwlock (- to 1.0.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aiorwlock would introduce bugs in testing: #997106
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aiorwlock.html
    • autopkgtest for aiorwlock/1.0.0-0.2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1251 days old (needed 5 days)
• mydumper (- to 0.10.1-1)
  • Migration status for mydumper (- to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mydumper would introduce bugs in testing: #1000014
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mydumper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1251 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 ♻
    • 1252 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 ♻
    • 1252 days old (needed 5 days)
• nitrokey-app (- to 1.4.2-1)
  • Migration status for nitrokey-app (- to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nitrokey-app would introduce bugs in testing: #1060573, #1067912
    • Build-Depends(-Arch): nitrokey-app qtbase-opensource-src (not considered)
    • Depends: nitrokey-app qtbase-opensource-src (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nitrokey-app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1253 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
    • 1253 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:
    • 1253 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
    • 1254 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 ♻
    • 1254 days old (needed 5 days)
• ruby-upr (- to 0.3.0-3)
  • Migration status for ruby-upr (- to 0.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-upr would introduce bugs in testing: #1030689
    • autopkgtest for ruby-upr/0.3.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): ruby-upr ruby-moneta (not considered)
    • Depends: ruby-upr ruby-moneta (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-upr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1255 days old (needed 5 days)
• anytun (- to 0.3.8-1)
  • Migration status for anytun (- to 0.3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating anytun would introduce bugs in testing: #1065386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/anytun.html
    • Reproducible on armhf - info ♻
    • 1256 days old (needed 5 days)
• apertium-kaz-tat (- to 0.2.1-1)
  • Migration status for apertium-kaz-tat (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-kaz-tat would introduce bugs in testing: #1005670
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-kaz-tat.html
    • 1256 days old (needed 5 days)
• apertium-sme-nob (- to 0.6.1+ds.1-2)
  • Migration status for apertium-sme-nob (- to 0.6.1+ds.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apertium-sme-nob would introduce bugs in testing: #1008348
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apertium-sme-nob.html
    • 1256 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
    • 1256 days old (needed 5 days)
• picprog (- to 1.9.1-5)
  • Migration status for picprog (- to 1.9.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating picprog would introduce bugs in testing: #946039
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picprog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1257 days old (needed 5 days)
• golang-github-alicebob-miniredis (- to 2.2.1-5)
  • Migration status for golang-github-alicebob-miniredis (- to 2.2.1-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-alicebob-miniredis golang-github-bsm-redeo (not considered)
    • Depends: golang-github-alicebob-miniredis golang-github-bsm-redeo (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-alicebob-miniredis.html
    • autopkgtest for golang-github-alicebob-miniredis/2.2.1-5: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1258 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
    • 1258 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)
    • 1258 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 ♻
    • 1259 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
    • 1259 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
    • autopkgtest for backdoor-factory/3.4.2+dfsg-5: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Depends: backdoor-factory osslsigncode (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/backdoor-factory.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1260 days old (needed 5 days)
• pympler (- to 0.9+dfsg1-2)
  • Migration status for pympler (- to 0.9+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pympler would introduce bugs in testing: #1002173
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pympler.html
    • autopkgtest for pympler/0.9+dfsg1-2: amd64: No tests, superficial or 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 ♻
    • 1262 days old (needed 5 days)
• dfvfs (- to 20201219-1)
  • Migration status for dfvfs (- to 20201219-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dfvfs would introduce bugs in testing: #998527
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dfvfs.html
    • 1264 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
    • 1264 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
  • 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 ♻
    • 1265 days old (needed 5 days)
• vg (- to 1.30.0+ds-1)
  • Migration status for vg (- to 1.30.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • vg/amd64 has unsatisfiable dependency
    • vg/mips64el has unsatisfiable dependency
    • Updating vg would introduce bugs in testing: #1013061
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/v/vg.html
    • uninstallable on arch amd64, not running autopkgtest there
    • 1265 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 ♻
    • 1268 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
    • 1269 days old (needed 5 days)
• tulip (- to 5.4.0+dfsg-3)
  • Migration status for tulip (- to 5.4.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tulip would introduce bugs in testing: #1061424, #1065989
    • Build-Depends(-Arch): tulip sip4 (not considered)
    • Depends: tulip sip4 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tulip.html
    • 1273 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 ♻
    • 1274 days old (needed 5 days)
• stylish-haskell (- to 0.12.2.0-1)
  • Migration status for stylish-haskell (- to 0.12.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating stylish-haskell would introduce bugs in testing: #1017205
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on amd64: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on arm64: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on armhf: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on i386: libghc-strict-dev (<< 0.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-aeson-dev (<< 1.6)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-aeson-prof (<< 1.5)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-ghc-lib-parser-dev (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-ghc-lib-parser-prof (<< 8.12)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-semigroups-dev (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-semigroups-prof (<< 0.20)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-optparse-applicative-dev (<< 0.16)
    • stylish-haskell unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-strict-dev (<< 0.5)
    • Build-Depends(-Arch): stylish-haskell haskell-hsyaml (not considered)
    • Build-Depends(-Arch): stylish-haskell haskell-hsyaml-aeson (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/stylish-haskell.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1274 days old (needed 5 days)
• golang-github-manyminds-api2go (- to 1.0-RC4-1)
  • Migration status for golang-github-manyminds-api2go (- to 1.0-RC4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-manyminds-api2go would introduce bugs in testing: #1008425
    • autopkgtest for golang-github-manyminds-api2go/1.0-RC4-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-manyminds-api2go.html
    • 1275 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
    • 1277 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 ♻
    • 1277 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 ♻
    • 1277 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
    • 1281 days old (needed 5 days)
• golang-github-ajg-form (- to 1.5+git20160822.523a5da-1.1)
  • Migration status for golang-github-ajg-form (- to 1.5+git20160822.523a5da-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-ajg-form would introduce bugs in testing: #997539
    • autopkgtest for golang-github-ajg-form/1.5+git20160822.523a5da-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ajg-form.html
    • 1282 days old (needed 5 days)
• lsdb (- to 0.11-10.2)
  • Migration status for lsdb (- to 0.11-10.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lsdb would introduce bugs in testing: #965706
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lsdb.html
    • 1282 days old (needed 5 days)
• tldjs (- to 2.3.1-1.1)
  • Migration status for tldjs (- to 2.3.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tldjs would introduce bugs in testing: #986436
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tldjs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1282 days old (needed 5 days)
• vilistextum (- to 2.6.9-1.3)
  • Migration status for vilistextum (- to 2.6.9-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vilistextum would introduce bugs in testing: #1066284
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vilistextum.html
    • 1282 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
    • 1283 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, #961298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jodd.html
    • 1283 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
    • 1283 days old (needed 5 days)
• ruby-asetus (- to 0.3.0-1.1)
  • Migration status for ruby-asetus (- to 0.3.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-asetus ruby-toml (not considered)
    • Depends: ruby-asetus ruby-toml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-asetus.html
    • autopkgtest for ruby-asetus/0.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 ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1283 days old (needed 2 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 ♻
    • 1284 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
    • 1284 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 ♻
    • 1284 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 ♻
    • 1284 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
    • 1285 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
    • 1285 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
    • 1285 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
    • 1285 days old (needed 2 days)
• jwchat (- to 1.0+dfsg-1.5)
  • Migration status for jwchat (- to 1.0+dfsg-1.5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: jwchat jsjac (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jwchat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1285 days old (needed 5 days)
• ruby-omniauth-bitbucket (- to 0.0.2-1.1)
  • Migration status for ruby-omniauth-bitbucket (- to 0.0.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-bitbucket would introduce bugs in testing: #1030812
    • autopkgtest for ruby-omniauth-bitbucket/0.0.2-1.1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-bitbucket.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1285 days old (needed 5 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
    • 1286 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 ♻
    • 1287 days old (needed 5 days)
• jsjac (- to 1.3.4+dfsg-3)
  • Migration status for jsjac (- to 1.3.4+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jsjac would introduce bugs in testing: #1006027
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsjac.html
    • New but not reproducible on armhf - info ♻
    • 1287 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 ♻
    • 1287 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 ♻
    • 1287 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 ♻
    • 1287 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
    • 1287 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
    • 1287 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 ♻
    • 1288 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
    • 1289 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
    • Build-Depends(-Arch): android-platform-build android-platform-frameworks-base (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-build.html
    • 1289 days old (needed 5 days)
• leap-archive-keyring (- to 2017.11.24+nmu1)
  • Migration status for leap-archive-keyring (- to 2017.11.24+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating leap-archive-keyring would introduce bugs in testing: #880220
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/leap-archive-keyring.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1289 days old (needed 5 days)
• monkeysphere (- to 0.43-3.1)
  • Migration status for monkeysphere (- to 0.43-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating monkeysphere would introduce bugs in testing: #1011900, #1071941
    • autopkgtest for monkeysphere/0.43-3.1: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/monkeysphere.html
    • 1289 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 ♻
    • 1289 days old (needed 5 days)
• pafy (- to 0.5.2-2.1)
  • Migration status for pafy (- to 0.5.2-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pafy would introduce bugs in testing: #1016520
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pafy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1289 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 ♻
    • 1289 days old (needed 5 days)
• pysolfc-cardsets (- to 2.0+dfsg2-2.1)
  • Migration status for pysolfc-cardsets (- to 2.0+dfsg2-2.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: pysolfc-cardsets pysolfc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysolfc-cardsets.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1289 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
    • Depends: resvg qtbase-opensource-src (not considered)
  • 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 ♻
    • 1289 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 ♻
    • 1289 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 ♻
    • 1290 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
    • 1290 days old (needed 5 days)
• zeek-aux (- to 0.45-1)
  • Migration status for zeek-aux (- to 0.45-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zeek-aux would introduce bugs in testing: #985522
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zeek-aux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1292 days old (needed 5 days)
• scamp (- to 2.10.0-2)
  • Migration status for scamp (- to 2.10.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating scamp would introduce bugs in testing: #1056686
    • Build-Depends(-Arch): scamp atlas (not considered)
    • Depends: scamp atlas (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scamp.html
    • autopkgtest for scamp/2.10.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1293 days old (needed 2 days)
• cecil (- to 0.9.5+dfsg-5.1)
  • Migration status for cecil (- to 0.9.5+dfsg-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cecil would introduce bugs in testing: #1053554
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cecil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1294 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 ♻
    • 1296 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 ♻
    • 1297 days old (needed 5 days)
• broker (- to 1.4.0+ds1-1)
  • Migration status for broker (- to 1.4.0+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-broker/amd64 has unsatisfiable dependency
    • python3-broker/arm64 has unsatisfiable dependency
    • libbroker2/armel has unsatisfiable dependency
    • python3-broker/armel has unsatisfiable dependency
    • libbroker2/armhf has unsatisfiable dependency
    • python3-broker/armhf has unsatisfiable dependency
    • python3-broker/i386 has unsatisfiable dependency
    • python3-broker/mips64el has unsatisfiable dependency
    • python3-broker/ppc64el has unsatisfiable dependency
    • python3-broker/s390x has unsatisfiable dependency
    • Updating broker would introduce bugs in testing: #1037597, #1062029
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/b/broker.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1297 days old (needed 5 days)
• cycle-quotes (- to 0.1-4)
  • Migration status for cycle-quotes (- to 0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cycle-quotes would introduce bugs in testing: #1020192
    • autopkgtest for cycle-quotes/0.1-4: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cycle-quotes.html
    • 1297 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
    • 1297 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 ♻
    • 1300 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
    • 1302 days old (needed 5 days)
• adabrowse (- to 4.0.3-14)
  • Migration status for adabrowse (- to 4.0.3-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating adabrowse would introduce bugs in testing: #1008980
    • autopkgtest for adabrowse/4.0.3-14: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): adabrowse asis (not considered)
    • Depends: adabrowse asis (not considered)
    • Depends: adabrowse gcc-10 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adabrowse.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1303 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
    • 1303 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:
    • 1305 days old (needed 5 days)
• adacontrol (- to 1.21r6b-7)
  • Migration status for adacontrol (- to 1.21r6b-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • adacontrol/amd64 has unsatisfiable dependency
    • adacontrol/arm64 has unsatisfiable dependency
    • adacontrol/armel has unsatisfiable dependency
    • adacontrol/armhf has unsatisfiable dependency
    • adacontrol/i386 has unsatisfiable dependency
    • adacontrol/mips64el has unsatisfiable dependency
    • adacontrol/ppc64el has unsatisfiable dependency
    • adacontrol/s390x has unsatisfiable dependency
    • Updating adacontrol would introduce bugs in testing: #1008982
    • adacontrol unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on armel: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on armhf: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on i386: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll19-dev (>= 21.0.0-2)
    • adacontrol unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll19-dev (>= 21.0.0-2)
    • Build-Depends(-Arch): adacontrol asis (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 ♻
    • 1309 days old (needed 5 days)
• asis (- to 2019-5)
  • Migration status for asis (- to 2019-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • asis-programs/amd64 has unsatisfiable dependency
    • asis-programs/arm64 has unsatisfiable dependency
    • asis-programs/armel has unsatisfiable dependency
    • asis-programs/armhf has unsatisfiable dependency
    • asis-programs/i386 has unsatisfiable dependency
    • asis-programs/mips64el has unsatisfiable dependency
    • asis-programs/ppc64el has unsatisfiable dependency
    • asis-programs/s390x has unsatisfiable dependency
    • Updating asis would introduce bugs in testing: #1008979
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/a/asis.html
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on amd64: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on arm64: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on armel: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armel: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on armhf: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on i386: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on i386: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on mips64el: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlezout8-dev
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libgnatcoll19-dev (>= 21.0.0-2)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax10-dev (>= 21.0.0)
    • asis unsatisfiable Build-Depends(-Arch) on s390x: libxmlezout8-dev
    • Build-Depends(-Arch): asis gcc-10 (not considered)
    • Depends: asis gcc-10 (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
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1309 days old (needed 5 days)
• libaws (- to 20.2-2)
  • Migration status for libaws (- to 20.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libaws-bin/amd64 has unsatisfiable dependency
    • libaws20-dev/amd64 has unsatisfiable dependency
    • libaws6/amd64 has unsatisfiable dependency
    • libaws-bin/arm64 has unsatisfiable dependency
    • libaws20-dev/arm64 has unsatisfiable dependency
    • libaws6/arm64 has unsatisfiable dependency
    • libaws-bin/armel has unsatisfiable dependency
    • libaws20-dev/armel has unsatisfiable dependency
    • libaws6/armel has unsatisfiable dependency
    • libaws-bin/armhf has unsatisfiable dependency
    • libaws20-dev/armhf has unsatisfiable dependency
    • libaws6/armhf has unsatisfiable dependency
    • libaws-bin/i386 has unsatisfiable dependency
    • libaws20-dev/i386 has unsatisfiable dependency
    • libaws6/i386 has unsatisfiable dependency
    • libaws-bin/mips64el has unsatisfiable dependency
    • libaws20-dev/mips64el has unsatisfiable dependency
    • libaws6/mips64el has unsatisfiable dependency
    • libaws-bin/ppc64el has unsatisfiable dependency
    • libaws20-dev/ppc64el has unsatisfiable dependency
    • libaws6/ppc64el has unsatisfiable dependency
    • libaws-bin/s390x has unsatisfiable dependency
    • libaws20-dev/s390x has unsatisfiable dependency
    • libaws6/s390x has unsatisfiable dependency
    • Updating libaws would introduce bugs in testing: #1008981, #1023114, #997457
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on amd64: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on arm64: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armel: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on armhf: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on i386: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on mips64el: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on ppc64el: libxmlada-unicode10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libtemplates-parser14-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-dom10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-input10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-sax10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-schema10-dev (>= 21)
    • libaws unsatisfiable Build-Depends(-Arch) on s390x: libxmlada-unicode10-dev (>= 21)
    • Build-Depends(-Arch): libaws asis (not considered)
    • Build-Depends(-Arch): libaws gcc-10 (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 ♻
    • 1309 days old (needed 5 days)
• libhandy (- to 0.0.13-3)
  • Migration status for libhandy (- to 0.0.13-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libhandy would introduce bugs in testing: #991036
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhandy.html
    • autopkgtest for libhandy/0.0.13-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1311 days old (needed 2 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
    • 1315 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 ♻
    • 1318 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 ♻
    • 1319 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 ♻
    • 1321 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
    • 1321 days old (needed 5 days)
• rust-tcmalloc (- to 0.3.0-2)
  • Migration status for rust-tcmalloc (- to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-tcmalloc would introduce bugs in testing: #981869
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tcmalloc.html
    • autopkgtest for rust-tcmalloc/0.3.0-2: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1324 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 ♻
    • 1325 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-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on amd64: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on arm64: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armel: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on armhf: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on i386: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on mips64el: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on ppc64el: librust-tree-sitter-0.17+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-aho-corasick-0.7+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-petgraph-0.5+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-0.8+macros-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-phf-codegen-0.8+default-dev
    • rust-rust-code-analysis unsatisfiable Build-Depends(-Arch) on s390x: librust-tree-sitter-0.17+default-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-rust-code-analysis.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1326 days old (needed 5 days)
• chibi-scheme (- to 0.9.1-3)
  • Migration status for chibi-scheme (- to 0.9.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chibi-scheme would introduce bugs in testing: #981762
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/chibi-scheme.html
  • Additional info:
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for chibi-scheme/0.9.1-3: amd64: Pass, arm64: Pass, ppc64el: Pass, 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
    • 1327 days old (needed 2 days)
• python-opentracing (- to 2.4.0-1)
  • Migration status for python-opentracing (- to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-opentracing would introduce bugs in testing: #1026729
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-opentracing.html
    • 1329 days old (needed 5 days)
• dahdi-tools (- to 1:3.1.0-2)
  • Migration status for dahdi-tools (- to 1: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): dahdi-tools dahdi-linux (not considered)
    • Depends: dahdi-tools dahdi-linux (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • 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 ♻
    • 1331 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 ♻
    • 1341 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
    • 1344 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 ♻
    • 1351 days old (needed 5 days)
• nq (- to 0.3.1-4)
  • Migration status for nq (- to 0.3.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nq would introduce bugs in testing: #1005961
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nq.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1351 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
    • 1357 days old (needed 5 days)
• intel-hdcp (- to 20.3.0-1)
  • Migration status for intel-hdcp (- to 20.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-hdcp would introduce bugs in testing: #1052643, #1060469
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • Impossible Depends: intel-hdcp -> libssl3/3.1.5-1/armel
    • Impossible Depends: intel-hdcp -> libssl3/3.1.5-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-hdcp.html
    • 1359 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 ♻
    • 1362 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
    • 1362 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
    • 1364 days old (needed 2 days)
• rust-mdl (- to 1.0.4-1)
  • Migration status for rust-mdl (- to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-mdl would introduce bugs in testing: #1052952
    • autopkgtest for rust-mdl/1.0.4-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
    • Build-Depends(-Arch): rust-mdl rust-failure
    • Depends: rust-mdl rust-failure
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-mdl.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 ♻
    • 1364 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 ♻
    • 1365 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 ♻
    • 1367 days old (needed 5 days)
• homer-api (- to 5.0.6+dfsg2-3.2)
  • Migration status for homer-api (- to 5.0.6+dfsg2-3.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: homer-api kamailio (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/homer-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1369 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
    • 1371 days old (needed 5 days)
• sardana (- to 3.0.3-1)
  • Migration status for sardana (- to 3.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sardana would introduce bugs in testing: #1030905
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/sardana.html
  • Additional info:
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 1376 days old (needed 5 days)
• rust-rspotify (- to 0.7.0-3)
  • Migration status for rust-rspotify (- to 0.7.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-rspotify-dev/amd64 has unsatisfiable dependency
    • librust-rspotify-dev/arm64 has unsatisfiable dependency
    • librust-rspotify-dev/armel has unsatisfiable dependency
    • librust-rspotify-dev/armhf has unsatisfiable dependency
    • librust-rspotify-dev/i386 has unsatisfiable dependency
    • librust-rspotify-dev/mips64el has unsatisfiable dependency
    • librust-rspotify-dev/ppc64el has unsatisfiable dependency
    • librust-rspotify-dev/s390x has unsatisfiable dependency
    • Updating rust-rspotify would introduce bugs in testing: #1031072, #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-env-logger-0.7 (not considered)
    • Build-Depends(-Arch): rust-rspotify rust-failure
  • 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 ♻
    • 1379 days old (needed 5 days)
• xjig (- to 2.4-14.2)
  • Migration status for xjig (- to 2.4-14.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xjig/amd64 has unsatisfiable dependency
    • xjig/arm64 has unsatisfiable dependency
    • xjig/armel has unsatisfiable dependency
    • xjig/armhf has unsatisfiable dependency
    • xjig/i386 has unsatisfiable dependency
    • xjig/mips64el has unsatisfiable dependency
    • xjig/ppc64el has unsatisfiable dependency
    • xjig/s390x has unsatisfiable dependency
    • Updating xjig would introduce bugs in testing: #1014623, #1016403
    • xjig unsatisfiable Build-Depends(-Arch) on amd64: libnetpbm10-dev
    • xjig unsatisfiable Build-Depends(-Arch) on arm64: libnetpbm10-dev
    • xjig unsatisfiable Build-Depends(-Arch) on armel: libnetpbm10-dev
    • xjig unsatisfiable Build-Depends(-Arch) on armhf: libnetpbm10-dev
    • xjig unsatisfiable Build-Depends(-Arch) on i386: libnetpbm10-dev
    • xjig unsatisfiable Build-Depends(-Arch) on mips64el: libnetpbm10-dev
    • xjig unsatisfiable Build-Depends(-Arch) on ppc64el: libnetpbm10-dev
    • xjig unsatisfiable Build-Depends(-Arch) on s390x: libnetpbm10-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/x/xjig.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 1379 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
    • 1380 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 ♻
    • 1385 days old (needed 5 days)
• r-cran-spp (- to 1.16.0-2)
  • Migration status for r-cran-spp (- to 1.16.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-spp r-bioc-rsamtools (not considered)
    • Depends: r-cran-spp r-bioc-rsamtools (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-spp.html
    • autopkgtest for r-cran-spp/1.16.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1391 days old (needed 2 days)
• ruby-rails-assets-fine-uploader (- to 5.13.0-2)
  • Migration status for ruby-rails-assets-fine-uploader (- to 5.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rails-assets-fine-uploader would introduce bugs in testing: #1034027
    • autopkgtest for ruby-rails-assets-fine-uploader/5.13.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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 ♻
    • 1396 days old (needed 5 days)
• hping3 (- to 3.a2.ds2-10)
  • Migration status for hping3 (- to 3.a2.ds2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • hping3/armel has unsatisfiable dependency
    • hping3/armhf has unsatisfiable dependency
    • Updating hping3 would introduce bugs in testing: #1066662
    • autopkgtest for hping3/3.a2.ds2-10: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hping3.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 ♻
    • 1407 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
    • 1409 days old (needed 5 days)
• github-backup (- to 1.20200721-2)
  • Migration status for github-backup (- to 1.20200721-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating github-backup would introduce bugs in testing: #1017298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/github-backup.html
    • 1418 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 ♻
    • 1420 days old (needed 5 days)
• yrmcds (- to 1.1.9-1)
  • Migration status for yrmcds (- to 1.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • yrmcds/armel has unsatisfiable dependency
    • yrmcds/armhf has unsatisfiable dependency
    • Updating yrmcds would introduce bugs in testing: #1037907
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yrmcds.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1423 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
    • 1424 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
    • 1426 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
    • 1428 days old (needed 2 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 ♻
    • 1430 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
    • 1431 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 ♻
    • 1436 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)
    • 1438 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)
    • 1438 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)
    • 1442 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 ♻
    • 1445 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
    • 1446 days old (needed 5 days)
• crazydiskinfo (- to 1.1.0-2)
  • Migration status for crazydiskinfo (- to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crazydiskinfo would introduce bugs in testing: #997156
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crazydiskinfo.html
    • 1452 days old (needed 5 days)
• kwin-effect-xrdesktop (- to 0.15.1-1)
  • Migration status for kwin-effect-xrdesktop (- to 0.15.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kwin-effect-xrdesktop/amd64 has unsatisfiable dependency
    • kwin-effect-xrdesktop/arm64 has unsatisfiable dependency
    • kwin-effect-xrdesktop/armel has unsatisfiable dependency
    • kwin-effect-xrdesktop/armhf has unsatisfiable dependency
    • kwin-effect-xrdesktop/i386 has unsatisfiable dependency
    • kwin-effect-xrdesktop/mips64el has unsatisfiable dependency
    • kwin-effect-xrdesktop/ppc64el has unsatisfiable dependency
    • kwin-effect-xrdesktop/s390x has unsatisfiable dependency
    • Updating kwin-effect-xrdesktop would introduce bugs in testing: #1037382, #993015
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/k/kwin-effect-xrdesktop.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1452 days old (needed 5 days)
• effcee (- to 2019.1-1)
  • Migration status for effcee (- to 2019.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libeffcee0/amd64 has unsatisfiable dependency
    • libeffcee0/arm64 has unsatisfiable dependency
    • libeffcee0/armel has unsatisfiable dependency
    • libeffcee0/armhf has unsatisfiable dependency
    • libeffcee0/i386 has unsatisfiable dependency
    • libeffcee0/mips64el has unsatisfiable dependency
    • libeffcee0/ppc64el has unsatisfiable dependency
    • libeffcee0/s390x has unsatisfiable dependency
    • Updating effcee would introduce bugs in testing: #984048
    • Waiting for piuparts test results (stalls migration) - https://piuparts.debian.org/sid/source/e/effcee.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
    • 1454 days old (needed 5 days)
• ncbi-seg (- to 0.0.20000620-6)
  • Migration status for ncbi-seg (- to 0.0.20000620-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ncbi-seg would introduce bugs in testing: #1066563
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ncbi-seg.html
    • autopkgtest for ncbi-seg/0.0.20000620-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
    • 1454 days old (needed 2 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 ♻
    • 1458 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 ♻
    • 1459 days old (needed 5 days)
• dune-pdelab (- to 2.7~20200605-2)
  • Migration status for dune-pdelab (- to 2.7~20200605-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libdune-pdelab-dev/amd64 has unsatisfiable dependency
    • libdune-pdelab-dev/arm64 has unsatisfiable dependency
    • libdune-pdelab-dev/armel has unsatisfiable dependency
    • libdune-pdelab-dev/armhf has unsatisfiable dependency
    • libdune-pdelab-dev/i386 has unsatisfiable dependency
    • libdune-pdelab-dev/mips64el has unsatisfiable dependency
    • libdune-pdelab-dev/ppc64el has unsatisfiable dependency
    • libdune-pdelab-dev/s390x has unsatisfiable dependency
    • Updating dune-pdelab would introduce bugs in testing: #1023356, #976499
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/d/dune-pdelab.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1461 days old (needed 5 days)
• openrocket (- to 15.03.6)
  • Migration status for openrocket (- to 15.03.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openrocket would introduce bugs in testing: #984609
    • Depends: openrocket openjdk-8 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1461 days old (needed 5 days)
• 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
    • 1461 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 ♻
    • 1471 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 ♻
    • 1472 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 ♻
    • 1472 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 ♻
    • 1475 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 ♻
    • 1475 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 ♻
    • 1475 days old (needed 5 days)
• php-horde-mongo (- to 1.1.0-6)
  • Migration status for php-horde-mongo (- to 1.1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-mongo would introduce bugs in testing: #820091
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mongo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1475 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 ♻
    • 1475 days old (needed 5 days)
• mkcue (- to 1-7)
  • Migration status for mkcue (- to 1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mkcue would introduce bugs in testing: #984237
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkcue.html
    • 1482 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-panel (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 ♻
    • 1483 days old (needed 5 days)
• matchbox-panel (- to 0.9.3+git20100816-1)
  • Migration status for matchbox-panel (- to 0.9.3+git20100816-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • matchbox-panel/armel has unsatisfiable dependency
    • matchbox-panel/armhf has unsatisfiable dependency
    • Updating matchbox-panel would introduce bugs in testing: #1066592
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matchbox-panel.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 1483 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 ♻
    • 1494 days old (needed 5 days)
• iptables-converter (- to 0.9.8-1.2)
  • Migration status for iptables-converter (- to 0.9.8-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iptables-converter would introduce bugs in testing: #997602
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iptables-converter.html
    • 1497 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 ♻
    • 1499 days old (needed 5 days)
• breezy-loom (- to 3.0.0+bzr167-1)
  • Migration status for breezy-loom (- to 3.0.0+bzr167-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating breezy-loom would introduce bugs in testing: #988156
    • autopkgtest for breezy-loom/3.0.0+bzr167-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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 ♻
    • 1506 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
    • 1511 days old (needed 5 days)
• astropy-helpers (- to 4.0.1-1)
  • Migration status for astropy-helpers (- to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating astropy-helpers would introduce bugs in testing: #1058104
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astropy-helpers.html
    • 1515 days old (needed 5 days)
• fakeroot-ng (- to 0.18-4.1)
  • Migration status for fakeroot-ng (- to 0.18-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fakeroot-ng would introduce bugs in testing: #1016266
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fakeroot-ng.html
    • 1516 days old (needed 5 days)
• r-cran-fitcoach (- to 1.0-4)
  • Migration status for r-cran-fitcoach (- to 1.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-fitcoach r-cran-gbm (not considered)
    • Depends: r-cran-fitcoach r-cran-gbm (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-fitcoach.html
    • autopkgtest for r-cran-fitcoach/1.0-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1517 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
    • 1519 days old (needed 5 days)
• binutils64 (- to 1+c3)
  • Migration status for binutils64 (- to 1+c3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils64 would introduce bugs in testing: #987525, #987526
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1523 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 ♻
    • 1524 days old (needed 5 days)
• ethstats (- to 1.2.1-4)
  • Migration status for ethstats (- to 1.2.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: ethstats feature-check (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ethstats.html
    • autopkgtest for ethstats/1.2.1-4: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1527 days old (needed 2 days)
• sipxtapi (- to 3.3.0~test18+dfsg.1-0.1)
  • Migration status for sipxtapi (- to 3.3.0~test18+dfsg.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsipxtapi/amd64 has unsatisfiable dependency
    • libsipxtapi/arm64 has unsatisfiable dependency
    • libsipxtapi/armel has unsatisfiable dependency
    • libsipxtapi/armhf has unsatisfiable dependency
    • libsipxtapi/i386 has unsatisfiable dependency
    • libsipxtapi/mips64el has unsatisfiable dependency
    • libsipxtapi/ppc64el has unsatisfiable dependency
    • libsipxtapi/s390x has unsatisfiable dependency
    • Updating sipxtapi would introduce bugs in testing: #1058941, #984331, #986494, #999960
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sipxtapi.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1534 days old (needed 5 days)
• ruby-jekyll-asciidoc (- to 3.0.0-2)
  • Migration status for ruby-jekyll-asciidoc (- to 3.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-jekyll-asciidoc would introduce bugs in testing: #1030465
    • autopkgtest for ruby-jekyll-asciidoc/3.0.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-jekyll-asciidoc.html
    • 1544 days old (needed 5 days)
• rust-librespot-protocol (- to 0.1.0-2)
  • Migration status for rust-librespot-protocol (- to 0.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-librespot-protocol would introduce bugs in testing: #1002238
    • autopkgtest for rust-librespot-protocol/0.1.0-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-librespot-protocol.html
    • 1545 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 ♻
    • 1546 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
    • 1547 days old (needed 5 days)
• cclib-data (- to 1.6.2-2)
  • Migration status for cclib-data (- to 1.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cclib-data would introduce bugs in testing: #1057547
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1555 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 ♻
    • 1555 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 ♻
    • 1555 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
    • 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
    • autopkgtest for rust-failure-derive/0.1.7-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-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 ♻
    • 1555 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
    • 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:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sdaps.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1555 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
    • 1558 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
    • 1562 days old (needed 5 days)
• rust-failure (- to 0.1.7-1)
  • Migration status for rust-failure (- to 0.1.7-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-failure rust-failure-derive (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-failure.html
    • autopkgtest for rust-failure/0.1.7-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻, 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 ♻
    • 1563 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 ♻
    • 1567 days old (needed 5 days)
• airport-utils (- to 2-8)
  • Migration status for airport-utils (- to 2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating airport-utils would introduce bugs in testing: #414092
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/airport-utils.html
    • autopkgtest for airport-utils/2-8: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1568 days old (needed 2 days)
• gcc-9-cross-mipsen (- to 4+c2)
  • Migration status for gcc-9-cross-mipsen (- to 4+c2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cpp-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/amd64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/amd64 has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/arm64 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/arm64 has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/i386 has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/i386 has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/mips64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/mips64el has unsatisfiable dependency
    • cpp-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • cpp-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • cpp-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • cpp-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • g++-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gcc-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gccgo-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gdc-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gfortran-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gm2-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gnat-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc++-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mips-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mips64-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mips64el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsel-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa32r6el-linux-gnu/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • gobjc-9-mipsisa64r6el-linux-gnuabi64/ppc64el has unsatisfiable dependency
    • Updating gcc-9-cross-mipsen would introduce bugs in testing: #946352, #963998
    • Build-Depends(-Arch): gcc-9-cross-mipsen autoconf2.64 (not considered)
    • Build-Depends(-Arch): gcc-9-cross-mipsen gcc-9 (not considered)
    • Built-Using: gcc-9-cross-mipsen gcc-9 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gcc-9-cross-mipsen.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 1572 days old (needed 5 days)
• libneo4j-client (- to 2.2.0-1.1)
  • Migration status for libneo4j-client (- to 2.2.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libneo4j-client11/amd64 has unsatisfiable dependency
    • libneo4j-client11/arm64 has unsatisfiable dependency
    • libneo4j-client11/armel has unsatisfiable dependency
    • libneo4j-client11/armhf has unsatisfiable dependency
    • libneo4j-client11/i386 has unsatisfiable dependency
    • libneo4j-client11/mips64el has unsatisfiable dependency
    • libneo4j-client11/ppc64el has unsatisfiable dependency
    • libneo4j-client11/s390x has unsatisfiable dependency
    • Updating libneo4j-client would introduce bugs in testing: #984187
    • Build-Depends(-Arch): libneo4j-client libcypher-parser (not considered)
    • Depends: libneo4j-client libcypher-parser (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libn/libneo4j-client.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1584 days old (needed 5 days)
• mahimahi (- to 0.98-1.1)
  • Migration status for mahimahi (- to 0.98-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mahimahi/amd64 has unsatisfiable dependency
    • mahimahi/arm64 has unsatisfiable dependency
    • mahimahi/armel has unsatisfiable dependency
    • mahimahi/armhf has unsatisfiable dependency
    • mahimahi/i386 has unsatisfiable dependency
    • mahimahi/mips64el has unsatisfiable dependency
    • mahimahi/ppc64el has unsatisfiable dependency
    • mahimahi/s390x has unsatisfiable dependency
    • Updating mahimahi would introduce bugs in testing: #1072615, #977684, #984228
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mahimahi.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1589 days old (needed 5 days)
• tmperamental (- to 1.4)
  • Migration status for tmperamental (- to 1.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tmperamental would introduce bugs in testing: #1069505
    • autopkgtest for tmperamental/1.4: amd64: Pass, arm64: Pass, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tmperamental.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 1589 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 ♻
    • 1591 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
    • 1592 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 ♻
    • 1592 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 ♻
    • 1594 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 ♻
    • 1599 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 ♻
    • 1601 days old (needed 5 days)
• sassphp (- to 0.7-1)
  • Migration status for sassphp (- to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • php-sass/amd64 has unsatisfiable dependency
    • php-sass/arm64 has unsatisfiable dependency
    • php-sass/armel has unsatisfiable dependency
    • php-sass/armhf has unsatisfiable dependency
    • php-sass/i386 has unsatisfiable dependency
    • php-sass/mips64el has unsatisfiable dependency
    • php-sass/ppc64el has unsatisfiable dependency
    • php-sass/s390x has unsatisfiable dependency
    • Updating sassphp would introduce bugs in testing: #1035552
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sassphp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1601 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
    • 1603 days old (needed 5 days)
• pysolfc (- to 2.6.4-3)
  • Migration status for pysolfc (- to 2.6.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pysolfc would introduce bugs in testing: #1008708
    • autopkgtest for pysolfc/2.6.4-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysolfc.html
    • 1607 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 ♻
    • 1617 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
    • Depends: kcov curl (not considered)
    • Depends: kcov elfutils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kcov.html
    • 1618 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-include-dir-impl rust-failure (not considered)
    • Depends: rust-include-dir-impl rust-failure (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-include-dir-impl.html
    • autopkgtest for rust-include-dir-impl/0.5.0-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻, 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 ♻
    • 1623 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 ♻
    • 1625 days old (needed 5 days)
• vagrant-bindfs (- to 1.1.6-1)
  • Migration status for vagrant-bindfs (- to 1.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vagrant-bindfs would introduce bugs in testing: #953226
    • autopkgtest for vagrant-bindfs/1.1.6-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vagrant-bindfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1625 days old (needed 5 days)
• ghemical (- to 3.0.0-5)
  • Migration status for ghemical (- to 3.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ghemical/armel has unsatisfiable dependency
    • ghemical/armhf has unsatisfiable dependency
    • Updating ghemical would introduce bugs in testing: #1066986
    • Build-Depends(-Arch): ghemical gtkglext (not considered)
    • Build-Depends(-Arch): ghemical libglade2 (not considered)
    • Depends: ghemical gtkglext (not considered)
    • Depends: ghemical libglade2 (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
    • 1635 days old (needed 5 days)
• dafny (- to 2.3.0+dfsg-0.1)
  • Migration status for dafny (- to 2.3.0+dfsg-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dafny/2.3.0+dfsg-0.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): dafny boogie (not considered)
    • Depends: dafny boogie (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dafny.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1638 days old (needed 5 days)
• dltlyse (- to 1.1-1.1)
  • Migration status for dltlyse (- to 1.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dltlyse would introduce bugs in testing: #966926
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dltlyse.html
    • 1640 days old (needed 5 days)
• watson (- to 1.8.0-0.1)
  • Migration status for watson (- to 1.8.0-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating watson would introduce bugs in testing: #997487
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/watson.html
    • autopkgtest for watson/1.8.0-0.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1651 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 ♻
    • 1656 days old (needed 5 days)
• boogie (- to 2.4.1+dfsg-0.1)
  • Migration status for boogie (- to 2.4.1+dfsg-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating boogie would introduce bugs in testing: #1052886
    • autopkgtest for boogie/2.4.1+dfsg-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/boogie.html
    • 1661 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 ♻
    • 1666 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
    • 1667 days old (needed 5 days)
• pdfrw (- to 0.4-2.1)
  • Migration status for pdfrw (- to 0.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pdfrw would introduce bugs in testing: #958362
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdfrw.html
    • autopkgtest for pdfrw/0.4-2.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armel: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, 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 ♻
    • 1668 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
    • 1669 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 binutils-h8300-hms (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): brickos gcc-h8300-hms
  • 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 ♻
    • 1672 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
    • 1674 days old (needed 5 days)
• golang-github-ulule-limiter (- to 3.3.3-1)
  • Migration status for golang-github-ulule-limiter (- to 3.3.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
    • Depends: golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ulule-limiter.html
    • autopkgtest for golang-github-ulule-limiter/3.3.3-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1687 days old (needed 2 days)
• thawab (- to 4.1-2)
  • Migration status for thawab (- to 4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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
    • 1701 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 ♻
    • 1705 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 ♻
    • 1706 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 ♻
    • 1708 days old (needed 5 days)
• gr-dab (- to 0.4-2)
  • Migration status for gr-dab (- to 0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gr-dab/amd64 has unsatisfiable dependency
    • libgnuradio-dab3.8.0/amd64 has unsatisfiable dependency
    • gr-dab/arm64 has unsatisfiable dependency
    • libgnuradio-dab3.8.0/arm64 has unsatisfiable dependency
    • gr-dab/armel has unsatisfiable dependency
    • libgnuradio-dab3.8.0/armel has unsatisfiable dependency
    • gr-dab/armhf has unsatisfiable dependency
    • libgnuradio-dab3.8.0/armhf has unsatisfiable dependency
    • gr-dab/i386 has unsatisfiable dependency
    • libgnuradio-dab3.8.0/i386 has unsatisfiable dependency
    • gr-dab/mips64el has unsatisfiable dependency
    • libgnuradio-dab3.8.0/mips64el has unsatisfiable dependency
    • gr-dab/ppc64el has unsatisfiable dependency
    • libgnuradio-dab3.8.0/ppc64el has unsatisfiable dependency
    • gr-dab/s390x has unsatisfiable dependency
    • libgnuradio-dab3.8.0/s390x has unsatisfiable dependency
    • Updating gr-dab would introduce bugs in testing: #1002106, #1031346
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gr-dab.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1711 days old (needed 5 days)
• jsunit (- to 0.2.2-2)
  • Migration status for jsunit (- to 0.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jsunit would introduce bugs in testing: #974083
    • autopkgtest for jsunit/blocked-on-ci-infra: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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 ♻
    • 1713 days old (needed 5 days)
• termtris (- to 1.3-1)
  • Migration status for termtris (- to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating termtris would introduce bugs in testing: #966877
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/termtris.html
    • 1718 days old (needed 5 days)
• gandi-cli (- to 1.5-1)
  • Migration status for gandi-cli (- to 1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gandi-cli would introduce bugs in testing: #922420
    • autopkgtest for gandi-cli/1.5-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gandi-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1722 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
    • 1730 days old (needed 5 days)
• myhdl (- to 0.11-1)
  • Migration status for myhdl (- to 0.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating myhdl would introduce bugs in testing: #1071801, #991212
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/myhdl.html
    • autopkgtest for myhdl/0.11-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1731 days old (needed 2 days)
• beanbag (- to 1.9.2-1.2)
  • Migration status for beanbag (- to 1.9.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating beanbag would introduce bugs in testing: #977056
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/beanbag.html
    • 1732 days old (needed 5 days)
• frozen-flask (- to 0.11-3.1)
  • Migration status for frozen-flask (- to 0.11-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating frozen-flask would introduce bugs in testing: #1009968, #997354
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frozen-flask.html
    • 1736 days old (needed 5 days)
• python-ck (- to 1.9.4-1.1)
  • Migration status for python-ck (- to 1.9.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ck would introduce bugs in testing: #1058260
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ck.html
    • 1737 days old (needed 5 days)
• python-lepl (- to 5.1.3-2.1)
  • Migration status for python-lepl (- to 5.1.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-lepl would introduce bugs in testing: #950059
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lepl.html
    • 1737 days old (needed 5 days)
• socket-activate (- to 0.1-2)
  • Migration status for socket-activate (- to 0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating socket-activate would introduce bugs in testing: #922504
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/socket-activate.html
    • 1745 days old (needed 5 days)
• haskell98-tutorial (- to 200006-2-3)
  • Migration status for haskell98-tutorial (- to 200006-2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell98-tutorial would introduce bugs in testing: #965577
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell98-tutorial.html
    • 1748 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
    • 1753 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
    • 1756 days old (needed 5 days)
• python-ooolib (- to 0.0.22-5)
  • Migration status for python-ooolib (- to 0.0.22-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ooolib would introduce bugs in testing: #965794
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ooolib.html
    • 1764 days old (needed 5 days)
• drmips (- to 2.0.1-2.1)
  • Migration status for drmips (- to 2.0.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating drmips would introduce bugs in testing: #971184
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/drmips.html
    • 1768 days old (needed 5 days)
• gigedit (- to 1.1.1-1)
  • Migration status for gigedit (- to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gigedit/amd64 has unsatisfiable dependency
    • gigedit/arm64 has unsatisfiable dependency
    • gigedit/armel has unsatisfiable dependency
    • gigedit/armhf has unsatisfiable dependency
    • gigedit/i386 has unsatisfiable dependency
    • gigedit/mips64el has unsatisfiable dependency
    • gigedit/ppc64el has unsatisfiable dependency
    • gigedit/s390x has unsatisfiable dependency
    • Updating gigedit would introduce bugs in testing: #997203
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gigedit.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1768 days old (needed 5 days)
• crypto-policies (- to 20190816git-1)
  • Migration status for crypto-policies (- to 20190816git-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by henrich, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crypto-policies.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1769 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 ♻
    • 1769 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
    • 1770 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
    • 1771 days old (needed 5 days)
• python-arrayfire (- to 3.3.20160624-3)
  • Migration status for python-arrayfire (- to 3.3.20160624-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-arrayfire/3.3.20160624-3: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression or new test ♻, s390x: Pass
    • Build-Depends(-Arch): python-arrayfire arrayfire (not considered)
    • Depends: python-arrayfire arrayfire (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-arrayfire.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1774 days old (needed 5 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 ♻
    • 1777 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
    • 1780 days old (needed 2 days)
• hydroffice.bag (- to 0.2.15-3)
  • Migration status for hydroffice.bag (- to 0.2.15-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hydroffice.bag would introduce bugs in testing: #993003
    • autopkgtest for hydroffice.bag/0.2.15-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, 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
    • 1784 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 ♻
    • 1795 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: 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/g/gertty.html
    • 1798 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 ♻
    • 1802 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
    • 1819 days old (needed 5 days)
• versiontools (- to 1.9.1-4)
  • Migration status for versiontools (- to 1.9.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating versiontools would introduce bugs in testing: #1054736, #1056537, #1065998
    • autopkgtest for versiontools/1.9.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/v/versiontools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1819 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
    • 1822 days old (needed 5 days)
• hipspy (- to 0.2-3)
  • Migration status for hipspy (- to 0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hipspy would introduce bugs in testing: #1012277
    • autopkgtest for hipspy/0.2-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Build-Depends(-Arch): hipspy astropy-helpers (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hipspy.html
    • 1825 days old (needed 5 days)
• pluginhook (- to 0~20150216.0~a320158-2.1)
  • Migration status for pluginhook (- to 0~20150216.0~a320158-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pluginhook would introduce bugs in testing: #972915
    • pluginhook/amd64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/arm64 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/armel has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/armhf has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/i386 has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/mips64el has unsatisfiable Built-Using on golang-1.11 1.11.5-1
    • pluginhook/ppc64el has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • pluginhook/s390x has unsatisfiable Built-Using on golang-1.15 1.15.9-6
    • missing build on mips64el
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pluginhook.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 1844 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 ♻
    • 1880 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
    • 1881 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
    • 1916 days old (needed 2 days)
• ricochet-im (- to 1.1.4-3)
  • Migration status for ricochet-im (- to 1.1.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ricochet-im would introduce bugs in testing: #992668
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ricochet-im.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1939 days old (needed 5 days)
• pyfr (- to 1.5.0-3)
  • Migration status for pyfr (- to 1.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyfr would introduce bugs in testing: #997427
    • autopkgtest for pyfr/1.5.0-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyfr.html
    • 1958 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 ♻
    • 1961 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 ♻
    • 1961 days old (needed 5 days)
• libapache2-mod-auth-cas (- to 1.2-1)
  • Migration status for libapache2-mod-auth-cas (- to 1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache2-mod-auth-cas would introduce bugs in testing: #1000068
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache2-mod-auth-cas.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 1976 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
    • 1979 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
    • 1981 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
    • 1985 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 ♻
    • 1995 days old (needed 5 days)
• fonts-alegreya-sans (- to 2.008-1)
  • Migration status for fonts-alegreya-sans (- to 2.008-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-alegreya-sans would introduce bugs in testing: #944499
    • Not built on buildd: arch all binaries uploaded by jeremy@bicha.net, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-alegreya-sans.html
    • 2004 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-imutil (not considered)
    • Invalidated by dependency
    • Depends: yorick-full gyoto (not considered)
    • Depends: yorick-full yorick-curses (not considered)
    • Depends: yorick-full yorick-gl (not considered)
    • 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 ♻
    • 2005 days old (needed 5 days)
• minify-maven-plugin (- to 1.7.4-1.1)
  • Migration status for minify-maven-plugin (- to 1.7.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating minify-maven-plugin would introduce bugs in testing: #1006451
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/minify-maven-plugin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2009 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 ♻
    • 2010 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)
    • 2010 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 ♻
    • 2011 days old (needed 5 days)
• openr2 (- to 1.3.3-2)
  • Migration status for openr2 (- to 1.3.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): openr2 dahdi-linux (not considered)
    • Invalidated by build-dependency
    • Depends: openr2 dahdi-tools
  • 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 ♻
    • 2014 days old (needed 5 days)
• vorbis-java (- to 0.8-3)
  • Migration status for vorbis-java (- to 0.8-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): vorbis-java tika (not considered)
    • Depends: vorbis-java tika (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vorbis-java.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2016 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
    • 2019 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
    • 2021 days old (needed 5 days)
• mpqc3 (- to 0.0~git20170114-4.1)
  • Migration status for mpqc3 (- to 0.0~git20170114-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mpqc3/amd64 has unsatisfiable dependency
    • mpqc3/arm64 has unsatisfiable dependency
    • mpqc3/armel has unsatisfiable dependency
    • mpqc3/armhf has unsatisfiable dependency
    • mpqc3/i386 has unsatisfiable dependency
    • mpqc3/mips64el has unsatisfiable dependency
    • mpqc3/ppc64el has unsatisfiable dependency
    • Updating mpqc3 would introduce bugs in testing: #946452
    • Build-Depends(-Arch): mpqc3 tiledarray (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
    • 2037 days old (needed 5 days)
• evqueue-core (- to 2.1-1)
  • Migration status for evqueue-core (- to 2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating evqueue-core would introduce bugs in testing: #1000087, #914801
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/e/evqueue-core.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2071 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
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2073 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
    • 2074 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 ♻
    • 2076 days old (needed 5 days)
• mxt-app (- to 1.28-2)
  • Migration status for mxt-app (- to 1.28-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mxt-app would introduce bugs in testing: #952059
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mxt-app.html
    • 2079 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
    • 2086 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 ♻
    • 2093 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 ♻
    • 2102 days old (needed 5 days)
• aws-shell (- to 0.2.1-1)
  • Migration status for aws-shell (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • aws-shell/amd64 has unsatisfiable dependency
    • aws-shell/arm64 has unsatisfiable dependency
    • Updating aws-shell would introduce bugs in testing: #1050402, #944542
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/a/aws-shell.html
    • aws-shell unsatisfiable Build-Depends(-Arch) on amd64: awscli (<< 2.0.0)
    • Not built on buildd: arch all binaries uploaded by takaki, a new source-only upload is needed to allow migration
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel (which is allowed), not running autopkgtest there
    • uninstallable on arch armhf (which is allowed), not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2110 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 ♻
    • 2113 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 ♻
    • 2122 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 ♻
    • 2130 days old (needed 5 days)
• bdfproxy (- to 0.3.9-3)
  • Migration status for bdfproxy (- to 0.3.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bdfproxy would introduce bugs in testing: #1033923
    • autopkgtest for bdfproxy/0.3.9-3: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Depends: bdfproxy backdoor-factory (not considered)
    • Depends: bdfproxy mitmproxy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bdfproxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2133 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
    • 2159 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)
    • 2160 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
    • 2174 days old (needed 5 days)
• openmx (- to 3.8.5+dfsg1-1)
  • Migration status for openmx (- to 3.8.5+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openmx/armel has unsatisfiable dependency
    • openmx/armhf has unsatisfiable dependency
    • Updating openmx would introduce bugs in testing: #957639
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmx.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 2177 days old (needed 5 days)
• vowpal-wabbit (- to 8.6.1.dfsg1-1)
  • Migration status for vowpal-wabbit (- to 8.6.1.dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vowpal-wabbit would introduce bugs in testing: #1063055, #1073109, #836450, #893031
    • Not built on buildd: arch all binaries uploaded by yoh, a new source-only upload is needed to allow migration
    • missing build on arm64
    • missing build on armel
    • missing build on armhf
    • missing build on mips64el
    • missing build on ppc64el
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:armel not built yet, autopkgtest delayed there
    • arch:armhf not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Depends: vowpal-wabbit boost1.74 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vowpal-wabbit.html
    • 2179 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)
    • 2215 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 ♻
    • 2218 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
    • 2220 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 ♻
    • 2230 days old (needed 5 days)
• golang-github-coreos-go-tspi (- to 0.1.1-2)
  • Migration status for golang-github-coreos-go-tspi (- to 0.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-coreos-go-tspi would introduce bugs in testing: #849665
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-coreos-go-tspi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2282 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 ♻
    • 2283 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
    • 2302 days old (needed 5 days)
• metis-edf (- to 4.1-2-4)
  • Migration status for metis-edf (- to 4.1-2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating metis-edf would introduce bugs in testing: #1066955
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2362 days old (needed 5 days)
• ignore-me (- to 0.1.2-1)
  • Migration status for ignore-me (- to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ignore-me would introduce bugs in testing: #912037, #948875
    • Not built on buildd: arch all binaries uploaded by jonathan@bluemosh.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ignore-me.html
    • 2378 days old (needed 5 days)
• boinc-app-eah-brp (- to 0.20170426+dfsg-10)
  • Migration status for boinc-app-eah-brp (- to 0.20170426+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • boinc-app-eah-brp/amd64 has unsatisfiable dependency
    • boinc-app-eah-brp/arm64 has unsatisfiable dependency
    • boinc-app-eah-brp/armel has unsatisfiable dependency
    • boinc-app-eah-brp/armhf has unsatisfiable dependency
    • boinc-app-eah-brp/i386 has unsatisfiable dependency
    • boinc-app-eah-brp/mips64el has unsatisfiable dependency
    • boinc-app-eah-brp/ppc64el has unsatisfiable dependency
    • boinc-app-eah-brp/s390x has unsatisfiable dependency
    • Updating boinc-app-eah-brp would introduce bugs in testing: #887880, #949603
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on amd64: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on arm64: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on armel: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on armhf: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on i386: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on mips64el: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on ppc64el: g++-5 | g++ (<< 6)
    • boinc-app-eah-brp unsatisfiable Build-Depends(-Arch) on s390x: g++-5 | g++ (<< 6)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/boinc-app-eah-brp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2379 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 ♻
    • 2382 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
    • 2382 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
    • 2384 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
    • 2384 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 ♻
    • 2404 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
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2414 days old (needed 5 days)
• jajuk (- to 1:1.10.9+dfsg2-4)
  • Migration status for jajuk (- to 1:1.10.9+dfsg2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jajuk would introduce bugs in testing: #1071796, #923330
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jajuk.html
    • 2420 days old (needed 5 days)
• php-enum (- to 2.3.1-1)
  • Migration status for php-enum (- to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-enum would introduce bugs in testing: #882928
    • autopkgtest for php-enum/2.3.1-1: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by taffit, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-enum.html
    • 2435 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 ♻
    • 2454 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
    • 2492 days old (needed 5 days)
• opengrm-ngram (- to 1.3.2-3)
  • Migration status for opengrm-ngram (- to 1.3.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libngram-tools/amd64 has unsatisfiable dependency
    • libngram2/amd64 has unsatisfiable dependency
    • libngram-tools/arm64 has unsatisfiable dependency
    • libngram2/arm64 has unsatisfiable dependency
    • libngram-tools/armel has unsatisfiable dependency
    • libngram2/armel has unsatisfiable dependency
    • libngram-tools/armhf has unsatisfiable dependency
    • libngram2/armhf has unsatisfiable dependency
    • libngram-tools/i386 has unsatisfiable dependency
    • libngram2/i386 has unsatisfiable dependency
    • libngram-tools/mips64el has unsatisfiable dependency
    • libngram2/mips64el has unsatisfiable dependency
    • libngram-tools/ppc64el has unsatisfiable dependency
    • libngram2/ppc64el has unsatisfiable dependency
    • libngram-tools/s390x has unsatisfiable dependency
    • libngram2/s390x has unsatisfiable dependency
    • Updating opengrm-ngram would introduce bugs in testing: #1019172
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/opengrm-ngram.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2504 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 ♻
    • 2522 days old (needed 5 days)
• guidedog (- to 1.3.0-1)
  • Migration status for guidedog (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guidedog would introduce bugs in testing: #1025571
    • Impossible Depends: guidedog -> policykit-1/124-2/amd64
    • Impossible Depends: guidedog -> policykit-1/124-2/arm64
    • Impossible Depends: guidedog -> policykit-1/124-2/armel
    • Impossible Depends: guidedog -> policykit-1/124-2/armhf
    • Impossible Depends: guidedog -> policykit-1/124-2/i386
    • Impossible Depends: guidedog -> policykit-1/124-2/mips64el
    • Impossible Depends: guidedog -> policykit-1/124-2/ppc64el
    • Impossible Depends: guidedog -> policykit-1/124-2/s390x
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guidedog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2534 days old (needed 5 days)
• golang-github-minio-cli (- to 1.3.0+git20170313.0.8683fa7-1)
  • Migration status for golang-github-minio-cli (- to 1.3.0+git20170313.0.8683fa7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-minio-cli would introduce bugs in testing: #869190
    • Not built on buildd: arch all binaries uploaded by costamagnagianfranco@yahoo.it, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-minio-cli.html
    • 2559 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
    • 2564 days old (needed 5 days)
• ants (- to 2.1.0-5)
  • Migration status for ants (- to 2.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ants/amd64 has unsatisfiable dependency
    • ants/i386 has unsatisfiable dependency
    • Updating ants would introduce bugs in testing: #872741, #909833
    • ants unsatisfiable Build-Depends(-Arch) on amd64: libinsighttoolkit4-dev (>> 4.7.0~)
    • ants unsatisfiable Build-Depends(-Arch) on i386: libinsighttoolkit4-dev (>> 4.7.0~)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/ants.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2685 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): Will attempt migration (Any information below is purely informational)
  • 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 ♻
    • 2688 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
    • 2701 days old (needed 5 days)
• freebsd-libs (- to 10.3~svn296373-10)
  • Migration status for freebsd-libs (- to 10.3~svn296373-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by steven@pyro.eu.org, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): freebsd-libs freebsd-buildutils (not considered)
    • Build-Depends(-Arch): freebsd-libs freebsd-glue (not considered)
    • Depends: freebsd-libs freebsd-glue (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freebsd-libs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2718 days old (needed 5 days)
• lilyterm (- to 0.9.9.4+git20150208.f600c0-5)
  • Migration status for lilyterm (- to 0.9.9.4+git20150208.f600c0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating lilyterm would introduce bugs in testing: #970419
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lilyterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 2730 days old (needed 5 days)
• bookkeeper (- to 4.4.0-1)
  • Migration status for bookkeeper (- to 4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bookkeeper would introduce bugs in testing: #906340
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bookkeeper.html
    • 2736 days old (needed 5 days)
• gli (- to 0.8.2.0+ds1-2)
  • Migration status for gli (- to 0.8.2.0+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gli would introduce bugs in testing: #888933
    • autopkgtest for gli/0.8.2.0+ds1-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gli.html
    • 2740 days old (needed 5 days)
• rdup (- to 1.1.15-1)
  • Migration status for rdup (- to 1.1.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • rdup/amd64 has unsatisfiable dependency
    • rdup/arm64 has unsatisfiable dependency
    • rdup/armel has unsatisfiable dependency
    • rdup/armhf has unsatisfiable dependency
    • rdup/i386 has unsatisfiable dependency
    • rdup/mips64el has unsatisfiable dependency
    • rdup/ppc64el has unsatisfiable dependency
    • rdup/s390x has unsatisfiable dependency
    • Updating rdup would introduce bugs in testing: #941101, #999975
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rdup.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2744 days old (needed 5 days)
• verilog-mode (- to 20161124.fd230e6-2)
  • Migration status for verilog-mode (- to 20161124.fd230e6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating verilog-mode would introduce bugs in testing: #934977
    • verilog-mode unsatisfiable Build-Depends(-Arch) on amd64: emacs25
    • Not built on buildd: arch all binaries uploaded by spwhitton@spwhitton.name, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/verilog-mode.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Waiting for reproducibility test results on armhf - info ♻
    • Waiting for reproducibility test results on i386 - info ♻
    • 2749 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:
    • 2759 days old (needed 5 days)
• ruby-uglifier (- to 2.7.2+dfsg-2)
  • Migration status for ruby-uglifier (- to 2.7.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-uglifier would introduce bugs in testing: #981224
    • autopkgtest for ruby-uglifier/2.7.2+dfsg-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-uglifier.html
    • 2770 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 ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on i386 - info ♻
    • 2783 days old (needed 5 days)
• powermock (- to 1.6.6-1)
  • Migration status for powermock (- to 1.6.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating powermock would introduce bugs in testing: #1071806, #875358
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/powermock.html
    • 2802 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
    • 2840 days old (needed 5 days)
• kryo-serializers (- to 0.22-3)
  • Migration status for kryo-serializers (- to 0.22-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kryo-serializers would introduce bugs in testing: #875594
    • Not built on buildd: arch all binaries uploaded by ebourg@apache.org, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kryo-serializers.html
    • 2847 days old (needed 5 days)
• safecat (- to 1.13-3)
  • Migration status for safecat (- to 1.13-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating safecat would introduce bugs in testing: #1066354
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/safecat.html
    • 2876 days old (needed 5 days)
• arrayfire (- to 3.3.2+dfsg1-4)
  • Migration status for arrayfire (- to 3.3.2+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libarrayfire-opencl3/armel has unsatisfiable dependency
    • libarrayfire-opencl3/armhf has unsatisfiable dependency
    • Updating arrayfire would introduce bugs in testing: #1061920, #892288, #897707
    • autopkgtest for arrayfire/3.3.2+dfsg1-4: 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 ♻
    • Build-Depends(-Arch): arrayfire clblas (not considered)
    • Depends: arrayfire clblas (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arrayfire.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 2889 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 ♻
    • 2900 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
    • 2953 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
    • 2957 days old (needed 5 days)
• elektra (- to 0.8.14-5.1)
  • Migration status for elektra (- to 0.8.14-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • elektra-tests/amd64 has unsatisfiable dependency
    • libelektra4-python/amd64 has unsatisfiable dependency
    • python3-elektra/amd64 has unsatisfiable dependency
    • elektra-tests/arm64 has unsatisfiable dependency
    • libelektra4-python/arm64 has unsatisfiable dependency
    • python3-elektra/arm64 has unsatisfiable dependency
    • elektra-tests/armel has unsatisfiable dependency
    • libelektra4-python/armel has unsatisfiable dependency
    • python3-elektra/armel has unsatisfiable dependency
    • elektra-tests/armhf has unsatisfiable dependency
    • libelektra4-python/armhf has unsatisfiable dependency
    • python3-elektra/armhf has unsatisfiable dependency
    • elektra-tests/i386 has unsatisfiable dependency
    • libelektra4-python/i386 has unsatisfiable dependency
    • python3-elektra/i386 has unsatisfiable dependency
    • elektra-tests/mips64el has unsatisfiable dependency
    • libelektra4-python/mips64el has unsatisfiable dependency
    • python3-elektra/mips64el has unsatisfiable dependency
    • elektra-tests/ppc64el has unsatisfiable dependency
    • libelektra4-python/ppc64el has unsatisfiable dependency
    • python3-elektra/ppc64el has unsatisfiable dependency
    • elektra-tests/s390x has unsatisfiable dependency
    • libelektra4-python/s390x has unsatisfiable dependency
    • python3-elektra/s390x has unsatisfiable dependency
    • Updating elektra would introduce bugs in testing: #844145, #846200, #851592, #881676, #956949
    • elektra unsatisfiable Build-Depends(-Arch) on amd64: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on arm64: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on armel: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on armhf: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on i386: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on mips64el: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on ppc64el: swig3.0
    • elektra unsatisfiable Build-Depends(-Arch) on s390x: swig3.0
    • Not built on buildd: arch amd64 binaries uploaded by aeb
    • Not built on buildd: arch all binaries uploaded by aeb, a new source-only upload is needed to allow migration
    • Not built on buildd: arch mips64el binaries uploaded by aurel32
    • Depends: elektra qtbase-opensource-src (not considered)
  • 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
    • 2963 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
    • 2977 days old (needed 5 days)
• twofish (- to 0.3-5)
  • Migration status for twofish (- to 0.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating twofish would introduce bugs in testing: #997617
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/twofish.html
    • 2984 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
    • 3002 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
    • 3010 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
    • 3040 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
    • 3046 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
    • 3054 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
    • 3060 days old (needed 5 days)
• yorick-ynfft (- to 1.0.3-1)
  • Migration status for yorick-ynfft (- to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • yorick-ynfft/amd64 has unsatisfiable dependency
    • yorick-ynfft/arm64 has unsatisfiable dependency
    • yorick-ynfft/armel has unsatisfiable dependency
    • yorick-ynfft/armhf has unsatisfiable dependency
    • yorick-ynfft/i386 has unsatisfiable dependency
    • yorick-ynfft/mips64el has unsatisfiable dependency
    • yorick-ynfft/ppc64el has unsatisfiable dependency
    • yorick-ynfft/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): yorick-ynfft nfft (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/y/yorick-ynfft.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 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 ♻
    • 3072 days old (needed 5 days)
• libr3 (- to 1.3.4-1)
  • Migration status for libr3 (- to 1.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libr3 would introduce bugs in testing: #1000058
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libr3.html
    • autopkgtest for libr3/1.3.4-1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3080 days old (needed 2 days)
• literki (- to 0.0.0+20100113.git1da40724-1.2)
  • Migration status for literki (- to 0.0.0+20100113.git1da40724-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating literki would introduce bugs in testing: #892344, #899846, #999283
    • Impossible Depends: literki -> libpng16-16/1.6.43-1/armel
    • Impossible Depends: literki -> libpng16-16/1.6.43-1/armhf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/literki.html
    • 3087 days old (needed 5 days)
• fsharp (- to 4.0.0.4+dfsg2-2)
  • Migration status for fsharp (- to 4.0.0.4+dfsg2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fsharp/4.0.0.4+dfsg2-2: amd64: Regression or new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test ♻
    • Not built on buildd: arch all binaries uploaded by directhex, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fsharp.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • New but not reproducible on armhf - info ♻
    • New but not reproducible on i386 - info ♻
    • 3139 days old (needed 5 days)
• curlftpfs (- to 0.9.2-9)
  • Migration status for curlftpfs (- to 0.9.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • curlftpfs/armel has unsatisfiable dependency
    • curlftpfs/armhf has unsatisfiable dependency
    • Updating curlftpfs would introduce bugs in testing: #965476
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/curlftpfs.html
    • uninstallable on arch armel, not running autopkgtest there
    • uninstallable on arch armhf, not running autopkgtest there
    • 3254 days old (needed 5 days)
• bwctl (- to 1.5.4+dfsg1-1)
  • Migration status for bwctl (- to 1.5.4+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bwctl would introduce bugs in testing: #997326
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bwctl.html
    • 3265 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
    • 3288 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)
    • 3307 days old (needed 5 days)
• vncterm (- to 0.9.10-2)
  • Migration status for vncterm (- to 0.9.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vncterm would introduce bugs in testing: #898453
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vncterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3322 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
    • 3363 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
    • 3550 days old (needed 5 days)
• libnss-pgsql (- to 1.4.0debian-8)
  • Migration status for libnss-pgsql (- to 1.4.0debian-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libnss-pgsql would introduce bugs in testing: #1066673, #1072913
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libn/libnss-pgsql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3565 days old (needed 5 days)
• pam-pgsql (- to 0.7.3.2-1)
  • Migration status for pam-pgsql (- to 0.7.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pam-pgsql would introduce bugs in testing: #1071805, #1074051, #863650
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pam-pgsql.html
    • 3569 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 ♻
    • 3597 days old (needed 5 days)
• tart (- to 3.10-1)
  • Migration status for tart (- to 3.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tart would introduce bugs in testing: #965837
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tart.html
    • 3597 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
    • 3609 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
    • 3623 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
    • 3629 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 ♻
    • 3666 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
    • 3669 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
    • 3676 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
    • 3690 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
    • 3729 days old (needed 5 days)
• libpthread-workqueue (- to 0.9.1-1)
  • Migration status for libpthread-workqueue (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpthread-workqueue would introduce bugs in testing: #835107
    • Not built on buildd: arch amd64 binaries uploaded by rbalint
    • Not built on buildd: arch ppc64el binaries uploaded by aurel32
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpthread-workqueue.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 3781 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 ♻
    • 3831 days old (needed 5 days)
• yorick-gl (- to 1.1+cvs20070922+dfsg-6.1)
  • Migration status for yorick-gl (- to 1.1+cvs20070922+dfsg-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yorick-gl would introduce bugs in testing: #1066537
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-gl.html
    • 3881 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)
    • 3919 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)
    • 3980 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 ♻
    • 4054 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
    • 4087 days old (needed 5 days)
• xmms2-scrobbler (- to 0.4.0-4)
  • Migration status for xmms2-scrobbler (- to 0.4.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xmms2-scrobbler would introduce bugs in testing: #798099, #919037
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmms2-scrobbler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 4150 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
    • 4320 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
    • 4360 days old (needed 5 days)
• yorick-curses (- to 0.1-6)
  • Migration status for yorick-curses (- to 0.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yorick-curses would introduce bugs in testing: #1066635
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-curses.html
    • 4399 days old (needed 5 days)
• yorick-imutil (- to 0.5.7-3)
  • Migration status for yorick-imutil (- to 0.5.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yorick-imutil would introduce bugs in testing: #1066524
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yorick-imutil.html
    • 4399 days old (needed 5 days)
• dnstop (- to 20120611-2)
  • Migration status for dnstop (- to 20120611-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dnstop/armel has unsatisfiable dependency
    • dnstop/armhf has unsatisfiable dependency
    • Updating dnstop would introduce bugs in testing: #1066573
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnstop.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 ♻
    • 4409 days old (needed 5 days)
• pxe-kexec (- to 0.2.4-3)
  • Migration status for pxe-kexec (- to 0.2.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pxe-kexec would introduce bugs in testing: #984300
    • Impossible Depends: pxe-kexec -> libreadline8/8.2-3+b1/armel
    • Impossible Depends: pxe-kexec -> libreadline8/8.2-3+b1/armhf
    • Depends: pxe-kexec curl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pxe-kexec.html
    • 4442 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
    • 4470 days old (needed 5 days)
• navi2ch (- to 2.0.0~git20120331-1)
  • Migration status for navi2ch (- to 2.0.0~git20120331-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating navi2ch would introduce bugs in testing: #780480, #952259
    • Not built on buildd: arch all binaries uploaded by knok, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/navi2ch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 4471 days old (needed 5 days)
• privbind (- to 1.2-1.1)
  • Migration status for privbind (- to 1.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating privbind would introduce bugs in testing: #965787, #998987
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/privbind.html
    • 4478 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)
    • 4488 days old (needed 5 days)
• mixer.app (- to 1.8.0-5)
  • Migration status for mixer.app (- to 1.8.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mixer.app would introduce bugs in testing: #896580
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mixer.app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Reproducible on armhf - info ♻
    • Reproducible on i386 - info ♻
    • 4508 days old (needed 5 days)
• pstack (- to 1.3.1-1)
  • Migration status for pstack (- to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pstack would introduce bugs in testing: #950168
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pstack.html
    • Reproducible on amd64 - info ♻
    • Reproducible on i386 - info ♻
    • 4665 days old (needed 5 days)
• gems (- to 1.1.1-2)
  • Migration status for gems (- to 1.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gems would introduce bugs in testing: #965548
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gems.html
    • 4670 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 ♻
    • 4864 days old (needed 5 days)