Generated: 2025.09.20 11:05:11 +0000

• -3dchess (0.8.1-23 to -)
  • Migration status for -3dchess (0.8.1-23 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -4g8 (1.0-6 to -)
  • Migration status for -4g8 (1.0-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -amide (1.0.6-5 to -)
  • Migration status for -amide (1.0.6-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
• -bcron (0.11-23 to -)
  • Migration status for -bcron (0.11-23 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -bindfs (1.14.7-1.1 to -)
  • Migration status for -bindfs (1.14.7-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
• -bip (0.9.3-1.1 to -)
  • Migration status for -bip (0.9.3-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
• -blis (1.1-2 to -)
  • Migration status for -blis (1.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
• -bomberclone (0.11.9-7.1 to -)
  • Migration status for -bomberclone (0.11.9-7.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -bootp (2.4.3-21.1 to -)
  • Migration status for -bootp (2.4.3-21.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
• -brainparty (0.61+dfsg-7 to -)
  • Migration status for -brainparty (0.61+dfsg-7 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -briquolo (0.5.7-11 to -)
  • Migration status for -briquolo (0.5.7-11 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -bristol (0.60.11-5 to -)
  • Migration status for -bristol (0.60.11-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
• -bro-aux (0.42-1 to -)
  • Migration status for -bro-aux (0.42-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
• -bwbasic (2.20pl2-14 to -)
  • Migration status for -bwbasic (2.20pl2-14 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -cdcd (0.6.6-13.2 to -)
  • Migration status for -cdcd (0.6.6-13.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
• -cde (0.1+git9-g551e54d-2 to -)
  • Migration status for -cde (0.1+git9-g551e54d-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
• -cgoban (1.9.14-20 to -)
  • Migration status for -cgoban (1.9.14-20 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -checkpw (1.02-5 to -)
  • Migration status for -checkpw (1.02-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
• -ckermit (416~beta12-1 to -)
  • Migration status for -ckermit (416~beta12-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
• -clamsmtp (1.10-18 to -)
  • Migration status for -clamsmtp (1.10-18 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -clipit (1.4.5+git20241103-1 to -)
  • Migration status for -clipit (1.4.5+git20241103-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
• -clsync (0.4.5-2.1 to -)
  • Migration status for -clsync (0.4.5-2.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
• -codelite (17.0.0+dfsg-4 to -)
  • Migration status for -codelite (17.0.0+dfsg-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -colmap (3.10-2 to -)
  • Migration status for -colmap (3.10-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
• -conserver (8.2.7-3 to -)
  • Migration status for -conserver (8.2.7-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
• -cpdb-backend-cups (2.0b5-1 to -)
  • Migration status for -cpdb-backend-cups (2.0b5-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
• -cpp-hocon (0.3.0-1.1 to -)
  • Migration status for -cpp-hocon (0.3.0-1.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -cpptraj (5.1.0+dfsg-4 to -)
  • Migration status for -cpptraj (5.1.0+dfsg-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -crashmail (1.7-4 to -)
  • Migration status for -crashmail (1.7-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -crasm (1.8-3 to -)
  • Migration status for -crasm (1.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
• -creduce (2.11.0~20240909-2 to -)
  • Migration status for -creduce (2.11.0~20240909-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
• -criterion (2.4.1-2 to -)
  • Migration status for -criterion (2.4.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
• -cssc (1.4.1-1 to -)
  • Migration status for -cssc (1.4.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
• -cupt (2.10.4+nmu2 to -)
  • Migration status for -cupt (2.10.4+nmu2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -dact (0.8.42-6 to -)
  • Migration status for -dact (0.8.42-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -daemonize (1.7.8-4 to -)
  • Migration status for -daemonize (1.7.8-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -dbusada (0.6.3-2 to -)
  • Migration status for -dbusada (0.6.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
• -dd2 (0.2.2-5 to -)
  • Migration status for -dd2 (0.2.2-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
• -debdelta (0.70+nmu1 to -)
  • Migration status for -debdelta (0.70+nmu1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -dfu-programmer (0.6.1-1 to -)
  • Migration status for -dfu-programmer (0.6.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
• -dhcp-probe (1.3.1-1 to -)
  • Migration status for -dhcp-probe (1.3.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
• -dhex (0.69-4 to -)
  • Migration status for -dhex (0.69-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -diod (1.0.24-5.1 to -)
  • Migration status for -diod (1.0.24-5.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -dmrgpp (6.06-2 to -)
  • Migration status for -dmrgpp (6.06-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
• -dopewars (1.6.2-1 to -)
  • Migration status for -dopewars (1.6.2-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
• -drawterm-9front (0~git20220608.bee4db6-3 to -)
  • Migration status for -drawterm-9front (0~git20220608.bee4db6-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
• -drbd-utils (9.22.0-1.1 to -)
  • Migration status for -drbd-utils (9.22.0-1.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -driftnet (1.5.0-0.2 to -)
  • Migration status for -driftnet (1.5.0-0.2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -dvbtune (0.5.ds-5 to -)
  • Migration status for -dvbtune (0.5.ds-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
• -dwgsim (0.1.14-3 to -)
  • Migration status for -dwgsim (0.1.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
• -edge-addition-planarity-suite (3.0.2.0-2.1 to -)
  • Migration status for -edge-addition-planarity-suite (3.0.2.0-2.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
• -esys-particle (2.3.5+dfsg2-11 to -)
  • Migration status for -esys-particle (2.3.5+dfsg2-11 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -eta (1.0.1-1 to -)
  • Migration status for -eta (1.0.1-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -eukleides (1.5.4-5 to -)
  • Migration status for -eukleides (1.5.4-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
• -fasta3 (36.3.8i.14-Nov-2020-3 to -)
  • Migration status for -fasta3 (36.3.8i.14-Nov-2020-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
• -fastdds (3.1.2+ds-1 to -)
  • Migration status for -fastdds (3.1.2+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
• -fastjet (3.4.0+dfsg-1 to -)
  • Migration status for -fastjet (3.4.0+dfsg-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
• -fastlink (4.1P-fix100+dfsg-5 to -)
  • Migration status for -fastlink (4.1P-fix100+dfsg-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
• -filter (2.6.3+ds1-5 to -)
  • Migration status for -filter (2.6.3+ds1-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
• -fis-gtm (7.1-006-1 to -)
  • Migration status for -fis-gtm (7.1-006-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
• -flightgear (1:2020.3.19+dfsg-1 to -)
  • Migration status for -flightgear (1:2020.3.19+dfsg-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
• -floatbg (1.0-28.3 to -)
  • Migration status for -floatbg (1.0-28.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
• -freegish (1.53+git20170110+dfsg-2 to -)
  • Migration status for -freegish (1.53+git20170110+dfsg-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
• -fspy (0.1.1-4 to -)
  • Migration status for -fspy (0.1.1-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ftpmirror (1.96+dfsg-16.1 to -)
  • Migration status for -ftpmirror (1.96+dfsg-16.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
• -gatk-bwamem (1.0.4+dfsg2-3 to -)
  • Migration status for -gatk-bwamem (1.0.4+dfsg2-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
• -gcin (2.9.4+dfsg1-3 to -)
  • Migration status for -gcin (2.9.4+dfsg1-3 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -genparse (0.9.3-2 to -)
  • Migration status for -genparse (0.9.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
• -geomview (1.9.5-5 to -)
  • Migration status for -geomview (1.9.5-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
• -gfarm2fs (1.2.16-1 to -)
  • Migration status for -gfarm2fs (1.2.16-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
• -gftp (2.9.1~beta-4 to -)
  • Migration status for -gftp (2.9.1~beta-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -gkrellm-thinkbat (0.2.3-1 to -)
  • Migration status for -gkrellm-thinkbat (0.2.3-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -gkrellm-xkb (1.05-7 to -)
  • Migration status for -gkrellm-xkb (1.05-7 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -gkrellmoon (0.6-7.1 to -)
  • Migration status for -gkrellmoon (0.6-7.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -gkrelluim (0.3.2-2 to -)
  • Migration status for -gkrelluim (0.3.2-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
• -glhack (1.2-8 to -)
  • Migration status for -glhack (1.2-8 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -global (6.6.14-1 to -)
  • Migration status for -global (6.6.14-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
• -gmtp (1.3.11-3.1 to -)
  • Migration status for -gmtp (1.3.11-3.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -gnucobol4 (4.0~early~20200606-7 to -)
  • Migration status for -gnucobol4 (4.0~early~20200606-7 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -gnuit (4.9.5-5 to -)
  • Migration status for -gnuit (4.9.5-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
• -gnujump (1.0.8-5 to -)
  • Migration status for -gnujump (1.0.8-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
• -gopher (3.0.19 to -)
  • Migration status for -gopher (3.0.19 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -gprolog (1.4.5.0-3 to -)
  • Migration status for -gprolog (1.4.5.0-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
• -gpstrans (0.41-11 to -)
  • Migration status for -gpstrans (0.41-11 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -gr-dab (0.5-1 to -)
  • Migration status for -gr-dab (0.5-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -gr-gsm (1.0.0~20220727-1 to -)
  • Migration status for -gr-gsm (1.0.0~20220727-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
• -gramophone2 (0.8.13a-3.6 to -)
  • Migration status for -gramophone2 (0.8.13a-3.6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -grdesktop (0.23+d040330-8 to -)
  • Migration status for -grdesktop (0.23+d040330-8 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -gst-plugins-bad1.0-contrib (1.20.0-1.1 to -)
  • Migration status for -gst-plugins-bad1.0-contrib (1.20.0-1.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -halide (19.0.0-6 to -)
  • Migration status for -halide (19.0.0-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -haskell-system-fileio (0.3.16.4-6 to -)
  • Migration status for -haskell-system-fileio (0.3.16.4-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -hime (0.9.11+dfsg-4 to -)
  • Migration status for -hime (0.9.11+dfsg-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -hipsolver (5.5.1-8 to -)
  • Migration status for -hipsolver (5.5.1-8 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ht (2.1.0+repack1-5 to -)
  • Migration status for -ht (2.1.0+repack1-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
• -ifcplusplus (0~git20190402.13744d5+dfsg-4 to -)
  • Migration status for -ifcplusplus (0~git20190402.13744d5+dfsg-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ifhp (3.5.20-20 to -)
  • Migration status for -ifhp (3.5.20-20 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ifile (1.3.9-9 to -)
  • Migration status for -ifile (1.3.9-9 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -indi-eqmod (1.0+20230126190232-2 to -)
  • Migration status for -indi-eqmod (1.0+20230126190232-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
• -intercal (30:0.30-6 to -)
  • Migration status for -intercal (30:0.30-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ipv6calc (4.1.0-0.2 to -)
  • Migration status for -ipv6calc (4.1.0-0.2 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ircd-irc2 (2.11.2p3~dfsg-7.1 to -)
  • Migration status for -ircd-irc2 (2.11.2p3~dfsg-7.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -irsim (9.7.104-1.1 to -)
  • Migration status for -irsim (9.7.104-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
• -isatapd (0.9.7-5 to -)
  • Migration status for -isatapd (0.9.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
• -jamnntpd (1.3-1 to -)
  • Migration status for -jamnntpd (1.3-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -jester (1.0-16 to -)
  • Migration status for -jester (1.0-16 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -jpegpixi (1.1.1-5 to -)
  • Migration status for -jpegpixi (1.1.1-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
• -jskeus (1.2.6+dfsg-1 to -)
  • Migration status for -jskeus (1.2.6+dfsg-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
• -juman (7.0-3.9 to -)
  • Migration status for -juman (7.0-3.9 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -kannel (1.4.5-20 to -)
  • Migration status for -kannel (1.4.5-20 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -kdrill (6.5deb2-13.1 to -)
  • Migration status for -kdrill (6.5deb2-13.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
• -ketm (0.0.6-27 to -)
  • Migration status for -ketm (0.0.6-27 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -kodi-inputstream-adaptive (21.5.9+ds-1 to -)
  • Migration status for -kodi-inputstream-adaptive (21.5.9+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
• -kodi-pvr-hts (21.2.6+ds-1 to -)
  • Migration status for -kodi-pvr-hts (21.2.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
• -kraptor (0.0.20040403+ds-4 to -)
  • Migration status for -kraptor (0.0.20040403+ds-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -lcd4linux (0.11.0~svn1203-3 to -)
  • Migration status for -lcd4linux (0.11.0~svn1203-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
• -libast (0.7-11 to -)
  • Migration status for -libast (0.7-11 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -libdigidoc (3.10.5-6 to -)
  • Migration status for -libdigidoc (3.10.5-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -libint (1.2.1-6 to -)
  • Migration status for -libint (1.2.1-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -libkarma (0.1.2-11 to -)
  • Migration status for -libkarma (0.1.2-11 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -libshairport (1.2.1~git20120510.cbed0c1-4 to -)
  • Migration status for -libshairport (1.2.1~git20120510.cbed0c1-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -libunivalue (1.1.1+20191112-3 to -)
  • Migration status for -libunivalue (1.1.1+20191112-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
• -libxsmm (1.17-4 to -)
  • Migration status for -libxsmm (1.17-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -licenseutils (0.0.9-8 to -)
  • Migration status for -licenseutils (0.0.9-8 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -liquidwar (5.6.5-2 to -)
  • Migration status for -liquidwar (5.6.5-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
• -litecoin (0.21.4-1 to -)
  • Migration status for -litecoin (0.21.4-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
• -lm4tools (3:0.1.3-1 to -)
  • Migration status for -lm4tools (3:0.1.3-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -lmemory (0.6c-13 to -)
  • Migration status for -lmemory (0.6c-13 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -loadwatch (1.0+1.1alpha1-8 to -)
  • Migration status for -loadwatch (1.0+1.1alpha1-8 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -logtool (1.2.8-14 to -)
  • Migration status for -logtool (1.2.8-14 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -lookup (1.08b-14 to -)
  • Migration status for -lookup (1.08b-14 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -lunar (2.2-9 to -)
  • Migration status for -lunar (2.2-9 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -mactelnet (0.6.1-1.1 to -)
  • Migration status for -mactelnet (0.6.1-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
• -macutils (2.0b3-17 to -)
  • Migration status for -macutils (2.0b3-17 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -mathomatic (16.0.5-5 to -)
  • Migration status for -mathomatic (16.0.5-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
• -mcabber (1.1.2-2 to -)
  • Migration status for -mcabber (1.1.2-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
• -mccs (1:1.1-10 to -)
  • Migration status for -mccs (1:1.1-10 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -meritous (1.5-1.1 to -)
  • Migration status for -meritous (1.5-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
• -meshlab (2022.02+dfsg1-1 to -)
  • Migration status for -meshlab (2022.02+dfsg1-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
• -mhwaveedit (1.4.24-1 to -)
  • Migration status for -mhwaveedit (1.4.24-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
• -microdc2 (0.15.6-7 to -)
  • Migration status for -microdc2 (0.15.6-7 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -milter-greylist (4.6.4-4 to -)
  • Migration status for -milter-greylist (4.6.4-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -mimedefang (3.6-2 to -)
  • Migration status for -mimedefang (3.6-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
• -mp3splt (2.6.2+20170630-3.3 to -)
  • Migration status for -mp3splt (2.6.2+20170630-3.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
• -mtpaint (3.50.12-1 to -)
  • Migration status for -mtpaint (3.50.12-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
• -mudita24 (1.0.3+svn13-7 to -)
  • Migration status for -mudita24 (1.0.3+svn13-7 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -nabi (1.0.1-2 to -)
  • Migration status for -nabi (1.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
• -nanopolish (0.14.0-1 to -)
  • Migration status for -nanopolish (0.14.0-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -nat (1:1.0-7 to -)
  • Migration status for -nat (1:1.0-7 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ncbi-igblast (1.20.0-2 to -)
  • Migration status for -ncbi-igblast (1.20.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
• -ncdc (1.23.1-1 to -)
  • Migration status for -ncdc (1.23.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
• -ncl (6.6.2.dfsg.1-11 to -)
  • Migration status for -ncl (6.6.2.dfsg.1-11 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -nedit (1:5.7-5 to -)
  • Migration status for -nedit (1:5.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
• -netkit-ftp-ssl (0.17.34+really0.17-2 to -)
  • Migration status for -netkit-ftp-ssl (0.17.34+really0.17-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
• -netkit-telnet-ssl (0.17.41+really0.17-6 to -)
  • Migration status for -netkit-telnet-ssl (0.17.41+really0.17-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -netsniff-ng (0.6.9-1 to -)
  • Migration status for -netsniff-ng (0.6.9-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
• -newlisp (10.7.5-2 to -)
  • Migration status for -newlisp (10.7.5-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
• -nextpnr (0.7-1 to -)
  • Migration status for -nextpnr (0.7-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ng (1.5~beta1-14 to -)
  • Migration status for -ng (1.5~beta1-14 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ngetty (1.1-13 to -)
  • Migration status for -ngetty (1.1-13 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ngraph-gtk (6.09.09-1 to -)
  • Migration status for -ngraph-gtk (6.09.09-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
• -ninvaders (0.1.1-5 to -)
  • Migration status for -ninvaders (0.1.1-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
• -nitpic (0.1-21 to -)
  • Migration status for -nitpic (0.1-21 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -nmzmail (1.1-5 to -)
  • Migration status for -nmzmail (1.1-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
• -nn (6.7.3-16 to -)
  • Migration status for -nn (6.7.3-16 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -notify-osd (0.9.35+20.04.20191129-2 to -)
  • Migration status for -notify-osd (0.9.35+20.04.20191129-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
• -notion (4.0.3+dfsg-1 to -)
  • Migration status for -notion (4.0.3+dfsg-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
• -nrn-mod2c (8.2.2-1 to -)
  • Migration status for -nrn-mod2c (8.2.2-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
• -nvi (1.81.6-23 to -)
  • Migration status for -nvi (1.81.6-23 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -nwchem (7.2.3-10 to -)
  • Migration status for -nwchem (7.2.3-10 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -oaklisp (1.3.7-4 to -)
  • Migration status for -oaklisp (1.3.7-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -opendmarc (1.4.2-5 to -)
  • Migration status for -opendmarc (1.4.2-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
• -openfoam (1912.200626-3 to -)
  • Migration status for -openfoam (1912.200626-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
• -openvpn-auth-ldap (2.0.4-4 to -)
  • Migration status for -openvpn-auth-ldap (2.0.4-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -osdlyrics (0.5.15+dfsg-2 to -)
  • Migration status for -osdlyrics (0.5.15+dfsg-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
• -osmo (0.4.4-2.1 to -)
  • Migration status for -osmo (0.4.4-2.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
• -otp (1:1.2.2-5 to -)
  • Migration status for -otp (1:1.2.2-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
• -p7zip (16.02+transitional.1 to -)
  • Migration status for -p7zip (16.02+transitional.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Package not in unstable, will try to remove
• -paps (0.6.8-7.2 to -)
  • Migration status for -paps (0.6.8-7.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
• -paraglob (0.6.0-1 to -)
  • Migration status for -paraglob (0.6.0-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -pd-ekext (0.1.1-6 to -)
  • Migration status for -pd-ekext (0.1.1-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -pd-fftease (3.0.1-7 to -)
  • Migration status for -pd-fftease (3.0.1-7 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -penguin-command (1.6.11-4 to -)
  • Migration status for -penguin-command (1.6.11-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -pgn2web (0.4-3.1 to -)
  • Migration status for -pgn2web (0.4-3.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -phlipple (0.8.5-5.1 to -)
  • Migration status for -phlipple (0.8.5-5.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -php-pecl-http (4.2.6-3 to -)
  • Migration status for -php-pecl-http (4.2.6-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
• -php-zmq (1.1.3-30 to -)
  • Migration status for -php-zmq (1.1.3-30 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -pigpio (1.78-1.1 to -)
  • Migration status for -pigpio (1.78-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
• -pike8.0 (8.0.1956-1 to -)
  • Migration status for -pike8.0 (8.0.1956-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
• -pktstat (1.8.5-8 to -)
  • Migration status for -pktstat (1.8.5-8 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -plast (2.3.2+dfsg-10 to -)
  • Migration status for -plast (2.3.2+dfsg-10 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -polybar (3.7.2-1 to -)
  • Migration status for -polybar (3.7.2-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
• -polyglot (2.0.4+git20210322-1 to -)
  • Migration status for -polyglot (2.0.4+git20210322-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
• -poppassd (1.8.5-8 to -)
  • Migration status for -poppassd (1.8.5-8 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -prime-phylo (1.0.11-13 to -)
  • Migration status for -prime-phylo (1.0.11-13 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -proxsmtp (1.10-5 to -)
  • Migration status for -proxsmtp (1.10-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
• -purple-plugin-pack (2.8.0-1 to -)
  • Migration status for -purple-plugin-pack (2.8.0-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -pynormaliz (2.21+ds-1 to -)
  • Migration status for -pynormaliz (2.21+ds-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by ginggs
    • Package is broken, will try to remove
• -python-easysnmp (0.2.6-1 to -)
  • Migration status for -python-easysnmp (0.2.6-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -python-pyahocorasick (1.4.1-2 to -)
  • Migration status for -python-pyahocorasick (1.4.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
• -qxw (20200708-2 to -)
  • Migration status for -qxw (20200708-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
• -rasmol (2.7.6.0-4 to -)
  • Migration status for -rasmol (2.7.6.0-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -raster3d (3.0-7-2 to -)
  • Migration status for -raster3d (3.0-7-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
• -rc (1.7.4+97.gceb59bb-5 to -)
  • Migration status for -rc (1.7.4+97.gceb59bb-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
• -rdiff-backup-fs (1.0.0-8 to -)
  • Migration status for -rdiff-backup-fs (1.0.0-8 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -redland-bindings (1.0.17.1+dfsg-6 to -)
  • Migration status for -redland-bindings (1.0.17.1+dfsg-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -relion (3.1.3-4 to -)
  • Migration status for -relion (3.1.3-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -rgbpaint (0.8.7-7 to -)
  • Migration status for -rgbpaint (0.8.7-7 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -rocdbgapi (5.7.1-2 to -)
  • Migration status for -rocdbgapi (5.7.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
• -roguenarok (1.0.1-3 to -)
  • Migration status for -roguenarok (1.0.1-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
• -ros2-rosidl (3.3.1-1 to -)
  • Migration status for -ros2-rosidl (3.3.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
• -rstatd (4.0.1-12 to -)
  • Migration status for -rstatd (4.0.1-12 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ruby-fusefs (0.7.0-6 to -)
  • Migration status for -ruby-fusefs (0.7.0-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ruby-lapack (1.8.2-1 to -)
  • Migration status for -ruby-lapack (1.8.2-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
• -ruby-rbtrace (0.5.1-1.1 to -)
  • Migration status for -ruby-rbtrace (0.5.1-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
• -ruby-rpatricia (1.0.1-2 to -)
  • Migration status for -ruby-rpatricia (1.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
• -ruby-sequel-pg (1.14.0-1 to -)
  • Migration status for -ruby-sequel-pg (1.14.0-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -rust-actix-web (4.9.0-2 to -)
  • Migration status for -rust-actix-web (4.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
• -rust-async-h1 (2.3.4-1 to -)
  • Migration status for -rust-async-h1 (2.3.4-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
• -rust-http-types (2.12.0-3 to -)
  • Migration status for -rust-http-types (2.12.0-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
• -rust-indieweb (0.4.5-10 to -)
  • Migration status for -rust-indieweb (0.4.5-10 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -rust-serde-qs (0.13.0-8 to -)
  • Migration status for -rust-serde-qs (0.13.0-8 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -sc (7.16-1.1.2-1 to -)
  • Migration status for -sc (7.16-1.1.2-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
• -sciplot (1.36-19 to -)
  • Migration status for -sciplot (1.36-19 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -scsitools (0.12-6 to -)
  • Migration status for -scsitools (0.12-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -sendip (2.6-1 to -)
  • Migration status for -sendip (2.6-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
• -seyon (2.20c-36 to -)
  • Migration status for -seyon (2.20c-36 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -shntool (3.0.10+git20130108.4ca41f4-1 to -)
  • Migration status for -shntool (3.0.10+git20130108.4ca41f4-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
• -shogivar (1.55b-3 to -)
  • Migration status for -shogivar (1.55b-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
• -sjeng (11.2-15 to -)
  • Migration status for -sjeng (11.2-15 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -sketch (1:0.3.7-12 to -)
  • Migration status for -sketch (1:0.3.7-12 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -skktools (1.3.4+0.20210220-1 to -)
  • Migration status for -skktools (1.3.4+0.20210220-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
• -slony1-2 (2.2.11-6 to -)
  • Migration status for -slony1-2 (2.2.11-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -smenu (1.4.0-1 to -)
  • Migration status for -smenu (1.4.0-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -snmptrapfmt (1.19 to -)
  • Migration status for -snmptrapfmt (1.19 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -soapaligner (2.20-5 to -)
  • Migration status for -soapaligner (2.20-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
• -soapdenovo (1.05-6 to -)
  • Migration status for -soapdenovo (1.05-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -soapdenovo2 (242+dfsg-4 to -)
  • Migration status for -soapdenovo2 (242+dfsg-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -spacefm (1.0.6-9 to -)
  • Migration status for -spacefm (1.0.6-9 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -spd (1.3.0-2 to -)
  • Migration status for -spd (1.3.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
• -spim (8.0+dfsg-7 to -)
  • Migration status for -spim (8.0+dfsg-7 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -splint (1:3.1.2+dfsg-5 to -)
  • Migration status for -splint (1:3.1.2+dfsg-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
• -splitvt (1.6.6-17 to -)
  • Migration status for -splitvt (1.6.6-17 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -spring (106.0+dfsg-4 to -)
  • Migration status for -spring (106.0+dfsg-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -squidguard (1.6.0-6 to -)
  • Migration status for -squidguard (1.6.0-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -srain (1.7.0-1 to -)
  • Migration status for -srain (1.7.0-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -sshguard (2.4.3-1 to -)
  • Migration status for -sshguard (2.4.3-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -ssvnc (1.0.29-6.1 to -)
  • Migration status for -ssvnc (1.0.29-6.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
• -sumo (1.18.0+dfsg-4 to -)
  • Migration status for -sumo (1.18.0+dfsg-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -super (3.30.3-2 to -)
  • Migration status for -super (3.30.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
• -sweed (3.2.1+dfsg-6 to -)
  • Migration status for -sweed (3.2.1+dfsg-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -sylpheed (3.8.0~beta1-2 to -)
  • Migration status for -sylpheed (3.8.0~beta1-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
• -tart (3.10-2 to -)
  • Migration status for -tart (3.10-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
• -tcpspy (1.7d-16 to -)
  • Migration status for -tcpspy (1.7d-16 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -tcptrace (6.6.7-6 to -)
  • Migration status for -tcptrace (6.6.7-6 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Package not in unstable, will try to remove
• -thesias (3.1.1-3 to -)
  • Migration status for -thesias (3.1.1-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
• -ticker (1.15 to -)
  • Migration status for -ticker (1.15 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -tickr (0.7.1-1 to -)
  • Migration status for -tickr (0.7.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
• -tkgate (2.1+repack-7 to -)
  • Migration status for -tkgate (2.1+repack-7 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -tracetuner (3.0.6~beta+dfsg-3 to -)
  • Migration status for -tracetuner (3.0.6~beta+dfsg-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
• -tracker-miners (3.8.2-4 to -)
  • Migration status for -tracker-miners (3.8.2-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Package not in unstable, will try to remove
• -uci2wb (4.1+git200714-1.2 to -)
  • Migration status for -uci2wb (4.1+git200714-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
• -udevil (0.4.4-4 to -)
  • Migration status for -udevil (0.4.4-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -up-imapproxy (1.2.8~svn20171105-2 to -)
  • Migration status for -up-imapproxy (1.2.8~svn20171105-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
• -vecgeom (1.2.8+dfsg-2 to -)
  • Migration status for -vecgeom (1.2.8+dfsg-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
• -viking (1.10-4 to -)
  • Migration status for -viking (1.10-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -vrfy (990522-11 to -)
  • Migration status for -vrfy (990522-11 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -w-scan (20210218-1 to -)
  • Migration status for -w-scan (20210218-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
• -w1retap (1.5.5-2 to -)
  • Migration status for -w1retap (1.5.5-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
• -warzone2100 (4.5.5deb-1 to -)
  • Migration status for -warzone2100 (4.5.5deb-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
• -wdm (1.28-27 to -)
  • Migration status for -wdm (1.28-27 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -widelands (2:1.2.1-3 to -)
  • Migration status for -widelands (2:1.2.1-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
• -wit (3.01a-5 to -)
  • Migration status for -wit (3.01a-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
• -wnn6-sdk (1.0.0-21 to -)
  • Migration status for -wnn6-sdk (1.0.0-21 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -wtdbg2 (2.5-10 to -)
  • Migration status for -wtdbg2 (2.5-10 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xarclock (1.0-20 to -)
  • Migration status for -xarclock (1.0-20 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xbubble (0.5.11.2-4 to -)
  • Migration status for -xbubble (0.5.11.2-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xbuffy (3.3.bl.3.dfsg-11 to -)
  • Migration status for -xbuffy (3.3.bl.3.dfsg-11 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xcolorsel (1.1a-23 to -)
  • Migration status for -xcolorsel (1.1a-23 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xdu (3.0-20 to -)
  • Migration status for -xdu (3.0-20 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xdvik-ja (22.87.06+j1.42-3 to -)
  • Migration status for -xdvik-ja (22.87.06+j1.42-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
• -xfaces (3.3-30.3 to -)
  • Migration status for -xfaces (3.3-30.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
• -xfrisk (1.2-10 to -)
  • Migration status for -xfrisk (1.2-10 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xgalaga (2.1.1.0-7 to -)
  • Migration status for -xgalaga (2.1.1.0-7 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xgammon (0.99.1128-11 to -)
  • Migration status for -xgammon (0.99.1128-11 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xl2tpd (1.3.18-1 to -)
  • Migration status for -xl2tpd (1.3.18-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
• -xmorph (1:20150712-5.1 to -)
  • Migration status for -xmorph (1:20150712-5.1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xpaint (2.9.1.4-5 to -)
  • Migration status for -xpaint (2.9.1.4-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
• -xsane (0.999-12.2 to -)
  • Migration status for -xsane (0.999-12.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
• -xscavenger (1.4.5-10 to -)
  • Migration status for -xscavenger (1.4.5-10 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xsunpinyin (2.0.3-9 to -)
  • Migration status for -xsunpinyin (2.0.3-9 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xtrkcad (1:5.3.0GA-1.1 to -)
  • Migration status for -xtrkcad (1:5.3.0GA-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
• -xwpe (1.5.30a-4 to -)
  • Migration status for -xwpe (1.5.30a-4 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• -xzgv (0.9.2-2 to -)
  • Migration status for -xzgv (0.9.2-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
• -ytree (1.99pl1-2.2 to -)
  • Migration status for -ytree (1.99pl1-2.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
• -zulucrypt (6.2.0-1 to -)
  • Migration status for -zulucrypt (6.2.0-1 to -): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Removal request by auto-removals
    • Package is broken, will try to remove
• 0ad/amd64 (0.27.1-2 to 0.27.1-2)
  • Migration status for 0ad/amd64 (0.27.1-2 to 0.27.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: 0ad/amd64 miniupnpc (not considered)
    • Invalidated by dependency
• 0ad/arm64 (0.27.1-2 to 0.27.1-2)
  • Migration status for 0ad/arm64 (0.27.1-2 to 0.27.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: 0ad/arm64 miniupnpc (not considered)
    • Invalidated by dependency
• 3dchess/amd64 (0.8.1-23 to 0.8.1-23)
  • Migration status for 3dchess/amd64 (0.8.1-23 to 0.8.1-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 3dchess/arm64 (0.8.1-23 to 0.8.1-23)
  • Migration status for 3dchess/arm64 (0.8.1-23 to 0.8.1-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 3dchess/armhf (0.8.1-23 to 0.8.1-23)
  • Migration status for 3dchess/armhf (0.8.1-23 to 0.8.1-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 3dchess/i386 (0.8.1-23 to 0.8.1-23)
  • Migration status for 3dchess/i386 (0.8.1-23 to 0.8.1-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 3dchess/ppc64el (0.8.1-23 to 0.8.1-23)
  • Migration status for 3dchess/ppc64el (0.8.1-23 to 0.8.1-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 3dchess/riscv64 (0.8.1-23 to 0.8.1-23)
  • Migration status for 3dchess/riscv64 (0.8.1-23 to 0.8.1-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 3dchess/s390x (0.8.1-23 to 0.8.1-23)
  • Migration status for 3dchess/s390x (0.8.1-23 to 0.8.1-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 4g8/amd64 (1.0-6 to 1.0-6)
  • Migration status for 4g8/amd64 (1.0-6 to 1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 4g8/arm64 (1.0-6 to 1.0-6)
  • Migration status for 4g8/arm64 (1.0-6 to 1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 4g8/armhf (1.0-6 to 1.0-6)
  • Migration status for 4g8/armhf (1.0-6 to 1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 4g8/i386 (1.0-6 to 1.0-6)
  • Migration status for 4g8/i386 (1.0-6 to 1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 4g8/ppc64el (1.0-6 to 1.0-6)
  • Migration status for 4g8/ppc64el (1.0-6 to 1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 4g8/riscv64 (1.0-6 to 1.0-6)
  • Migration status for 4g8/riscv64 (1.0-6 to 1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 4g8/s390x (1.0-6 to 1.0-6)
  • Migration status for 4g8/s390x (1.0-6 to 1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• amide/amd64 (1.0.6-5 to 1.0.6-5)
  • Migration status for amide/amd64 (1.0.6-5 to 1.0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• amide/arm64 (1.0.6-5 to 1.0.6-5)
  • Migration status for amide/arm64 (1.0.6-5 to 1.0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• amide/armhf (1.0.6-5 to 1.0.6-5)
  • Migration status for amide/armhf (1.0.6-5 to 1.0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• amide/i386 (1.0.6-5 to 1.0.6-5)
  • Migration status for amide/i386 (1.0.6-5 to 1.0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• amide/ppc64el (1.0.6-5 to 1.0.6-5)
  • Migration status for amide/ppc64el (1.0.6-5 to 1.0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• amide/s390x (1.0.6-5 to 1.0.6-5)
  • Migration status for amide/s390x (1.0.6-5 to 1.0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bcron/amd64 (0.11-23 to 0.11-23)
  • Migration status for bcron/amd64 (0.11-23 to 0.11-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bcron/arm64 (0.11-23 to 0.11-23)
  • Migration status for bcron/arm64 (0.11-23 to 0.11-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bcron/armhf (0.11-23 to 0.11-23)
  • Migration status for bcron/armhf (0.11-23 to 0.11-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bcron/i386 (0.11-23 to 0.11-23)
  • Migration status for bcron/i386 (0.11-23 to 0.11-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bcron/ppc64el (0.11-23 to 0.11-23)
  • Migration status for bcron/ppc64el (0.11-23 to 0.11-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bcron/riscv64 (0.11-23 to 0.11-23)
  • Migration status for bcron/riscv64 (0.11-23 to 0.11-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bcron/s390x (0.11-23 to 0.11-23)
  • Migration status for bcron/s390x (0.11-23 to 0.11-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bindfs/amd64 (1.14.7-1.1 to 1.14.7-1.1)
  • Migration status for bindfs/amd64 (1.14.7-1.1 to 1.14.7-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
• bindfs/arm64 (1.14.7-1.1 to 1.14.7-1.1)
  • Migration status for bindfs/arm64 (1.14.7-1.1 to 1.14.7-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
• bindfs/armhf (1.14.7-1.1 to 1.14.7-1.1)
  • Migration status for bindfs/armhf (1.14.7-1.1 to 1.14.7-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
• bindfs/i386 (1.14.7-1.1 to 1.14.7-1.1)
  • Migration status for bindfs/i386 (1.14.7-1.1 to 1.14.7-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
• bindfs/ppc64el (1.14.7-1.1 to 1.14.7-1.1)
  • Migration status for bindfs/ppc64el (1.14.7-1.1 to 1.14.7-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
• bindfs/riscv64 (1.14.7-1.1 to 1.14.7-1.1)
  • Migration status for bindfs/riscv64 (1.14.7-1.1 to 1.14.7-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
• bindfs/s390x (1.14.7-1.1 to 1.14.7-1.1)
  • Migration status for bindfs/s390x (1.14.7-1.1 to 1.14.7-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
• bip/amd64 (0.9.3-1.1 to 0.9.3-1.1)
  • Migration status for bip/amd64 (0.9.3-1.1 to 0.9.3-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
• bip/arm64 (0.9.3-1.1 to 0.9.3-1.1)
  • Migration status for bip/arm64 (0.9.3-1.1 to 0.9.3-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
• bip/armhf (0.9.3-1.1 to 0.9.3-1.1)
  • Migration status for bip/armhf (0.9.3-1.1 to 0.9.3-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
• bip/i386 (0.9.3-1.1 to 0.9.3-1.1)
  • Migration status for bip/i386 (0.9.3-1.1 to 0.9.3-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
• bip/ppc64el (0.9.3-1.1 to 0.9.3-1.1)
  • Migration status for bip/ppc64el (0.9.3-1.1 to 0.9.3-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
• bip/riscv64 (0.9.3-1.1 to 0.9.3-1.1)
  • Migration status for bip/riscv64 (0.9.3-1.1 to 0.9.3-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
• bip/s390x (0.9.3-1.1 to 0.9.3-1.1)
  • Migration status for bip/s390x (0.9.3-1.1 to 0.9.3-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
• blis/amd64 (1.1-2 to 1.1-2)
  • Migration status for blis/amd64 (1.1-2 to 1.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
• blis/arm64 (1.1-2 to 1.1-2)
  • Migration status for blis/arm64 (1.1-2 to 1.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
• blis/armhf (1.1-2 to 1.1-2)
  • Migration status for blis/armhf (1.1-2 to 1.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
• blis/i386 (1.1-2 to 1.1-2)
  • Migration status for blis/i386 (1.1-2 to 1.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
• blis/ppc64el (1.1-2 to 1.1-2)
  • Migration status for blis/ppc64el (1.1-2 to 1.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
• blis/riscv64 (1.1-2 to 1.1-2)
  • Migration status for blis/riscv64 (1.1-2 to 1.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
• blis/s390x (1.1-2 to 1.1-2)
  • Migration status for blis/s390x (1.1-2 to 1.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
• bomberclone/amd64 (0.11.9-7.1 to 0.11.9-7.1)
  • Migration status for bomberclone/amd64 (0.11.9-7.1 to 0.11.9-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bomberclone/arm64 (0.11.9-7.1 to 0.11.9-7.1)
  • Migration status for bomberclone/arm64 (0.11.9-7.1 to 0.11.9-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bomberclone/armhf (0.11.9-7.1 to 0.11.9-7.1)
  • Migration status for bomberclone/armhf (0.11.9-7.1 to 0.11.9-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bomberclone/i386 (0.11.9-7.1 to 0.11.9-7.1)
  • Migration status for bomberclone/i386 (0.11.9-7.1 to 0.11.9-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bomberclone/ppc64el (0.11.9-7.1 to 0.11.9-7.1)
  • Migration status for bomberclone/ppc64el (0.11.9-7.1 to 0.11.9-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bomberclone/s390x (0.11.9-7.1 to 0.11.9-7.1)
  • Migration status for bomberclone/s390x (0.11.9-7.1 to 0.11.9-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bootp/amd64 (2.4.3-21.1 to 2.4.3-21.1)
  • Migration status for bootp/amd64 (2.4.3-21.1 to 2.4.3-21.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bootp/arm64 (2.4.3-21.1 to 2.4.3-21.1)
  • Migration status for bootp/arm64 (2.4.3-21.1 to 2.4.3-21.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bootp/armhf (2.4.3-21.1 to 2.4.3-21.1)
  • Migration status for bootp/armhf (2.4.3-21.1 to 2.4.3-21.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bootp/i386 (2.4.3-21.1 to 2.4.3-21.1)
  • Migration status for bootp/i386 (2.4.3-21.1 to 2.4.3-21.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bootp/ppc64el (2.4.3-21.1 to 2.4.3-21.1)
  • Migration status for bootp/ppc64el (2.4.3-21.1 to 2.4.3-21.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bootp/riscv64 (2.4.3-21.1 to 2.4.3-21.1)
  • Migration status for bootp/riscv64 (2.4.3-21.1 to 2.4.3-21.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bootp/s390x (2.4.3-21.1 to 2.4.3-21.1)
  • Migration status for bootp/s390x (2.4.3-21.1 to 2.4.3-21.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• brainparty/amd64 (0.61+dfsg-7 to 0.61+dfsg-7)
  • Migration status for brainparty/amd64 (0.61+dfsg-7 to 0.61+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• brainparty/arm64 (0.61+dfsg-7 to 0.61+dfsg-7)
  • Migration status for brainparty/arm64 (0.61+dfsg-7 to 0.61+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• brainparty/armhf (0.61+dfsg-7 to 0.61+dfsg-7)
  • Migration status for brainparty/armhf (0.61+dfsg-7 to 0.61+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• brainparty/i386 (0.61+dfsg-7 to 0.61+dfsg-7)
  • Migration status for brainparty/i386 (0.61+dfsg-7 to 0.61+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• brainparty/ppc64el (0.61+dfsg-7 to 0.61+dfsg-7)
  • Migration status for brainparty/ppc64el (0.61+dfsg-7 to 0.61+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• brainparty/s390x (0.61+dfsg-7 to 0.61+dfsg-7)
  • Migration status for brainparty/s390x (0.61+dfsg-7 to 0.61+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• briquolo/amd64 (0.5.7-11 to 0.5.7-11)
  • Migration status for briquolo/amd64 (0.5.7-11 to 0.5.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• briquolo/arm64 (0.5.7-11 to 0.5.7-11)
  • Migration status for briquolo/arm64 (0.5.7-11 to 0.5.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• briquolo/armhf (0.5.7-11 to 0.5.7-11)
  • Migration status for briquolo/armhf (0.5.7-11 to 0.5.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• briquolo/i386 (0.5.7-11 to 0.5.7-11)
  • Migration status for briquolo/i386 (0.5.7-11 to 0.5.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• briquolo/ppc64el (0.5.7-11 to 0.5.7-11)
  • Migration status for briquolo/ppc64el (0.5.7-11 to 0.5.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• briquolo/s390x (0.5.7-11 to 0.5.7-11)
  • Migration status for briquolo/s390x (0.5.7-11 to 0.5.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bristol/amd64 (0.60.11-5 to 0.60.11-5)
  • Migration status for bristol/amd64 (0.60.11-5 to 0.60.11-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bristol/arm64 (0.60.11-5 to 0.60.11-5)
  • Migration status for bristol/arm64 (0.60.11-5 to 0.60.11-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bristol/armhf (0.60.11-5 to 0.60.11-5)
  • Migration status for bristol/armhf (0.60.11-5 to 0.60.11-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bristol/i386 (0.60.11-5 to 0.60.11-5)
  • Migration status for bristol/i386 (0.60.11-5 to 0.60.11-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bristol/ppc64el (0.60.11-5 to 0.60.11-5)
  • Migration status for bristol/ppc64el (0.60.11-5 to 0.60.11-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bristol/riscv64 (0.60.11-5 to 0.60.11-5)
  • Migration status for bristol/riscv64 (0.60.11-5 to 0.60.11-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bristol/s390x (0.60.11-5 to 0.60.11-5)
  • Migration status for bristol/s390x (0.60.11-5 to 0.60.11-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bro-aux/amd64 (0.42-1 to 0.42-1)
  • Migration status for bro-aux/amd64 (0.42-1 to 0.42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bro-aux/arm64 (0.42-1 to 0.42-1)
  • Migration status for bro-aux/arm64 (0.42-1 to 0.42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bro-aux/armhf (0.42-1 to 0.42-1)
  • Migration status for bro-aux/armhf (0.42-1 to 0.42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bro-aux/i386 (0.42-1 to 0.42-1)
  • Migration status for bro-aux/i386 (0.42-1 to 0.42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bro-aux/ppc64el (0.42-1 to 0.42-1)
  • Migration status for bro-aux/ppc64el (0.42-1 to 0.42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bro-aux/riscv64 (0.42-1 to 0.42-1)
  • Migration status for bro-aux/riscv64 (0.42-1 to 0.42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bro-aux/s390x (0.42-1 to 0.42-1)
  • Migration status for bro-aux/s390x (0.42-1 to 0.42-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bwbasic/amd64 (2.20pl2-14 to 2.20pl2-14)
  • Migration status for bwbasic/amd64 (2.20pl2-14 to 2.20pl2-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bwbasic/arm64 (2.20pl2-14 to 2.20pl2-14)
  • Migration status for bwbasic/arm64 (2.20pl2-14 to 2.20pl2-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bwbasic/armhf (2.20pl2-14 to 2.20pl2-14)
  • Migration status for bwbasic/armhf (2.20pl2-14 to 2.20pl2-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bwbasic/i386 (2.20pl2-14 to 2.20pl2-14)
  • Migration status for bwbasic/i386 (2.20pl2-14 to 2.20pl2-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bwbasic/ppc64el (2.20pl2-14 to 2.20pl2-14)
  • Migration status for bwbasic/ppc64el (2.20pl2-14 to 2.20pl2-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bwbasic/riscv64 (2.20pl2-14 to 2.20pl2-14)
  • Migration status for bwbasic/riscv64 (2.20pl2-14 to 2.20pl2-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• bwbasic/s390x (2.20pl2-14 to 2.20pl2-14)
  • Migration status for bwbasic/s390x (2.20pl2-14 to 2.20pl2-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cdcd/amd64 (0.6.6-13.2 to 0.6.6-13.2)
  • Migration status for cdcd/amd64 (0.6.6-13.2 to 0.6.6-13.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cdcd/arm64 (0.6.6-13.2 to 0.6.6-13.2)
  • Migration status for cdcd/arm64 (0.6.6-13.2 to 0.6.6-13.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cdcd/armhf (0.6.6-13.2 to 0.6.6-13.2)
  • Migration status for cdcd/armhf (0.6.6-13.2 to 0.6.6-13.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cdcd/i386 (0.6.6-13.2 to 0.6.6-13.2)
  • Migration status for cdcd/i386 (0.6.6-13.2 to 0.6.6-13.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cdcd/ppc64el (0.6.6-13.2 to 0.6.6-13.2)
  • Migration status for cdcd/ppc64el (0.6.6-13.2 to 0.6.6-13.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cdcd/riscv64 (0.6.6-13.2 to 0.6.6-13.2)
  • Migration status for cdcd/riscv64 (0.6.6-13.2 to 0.6.6-13.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cdcd/s390x (0.6.6-13.2 to 0.6.6-13.2)
  • Migration status for cdcd/s390x (0.6.6-13.2 to 0.6.6-13.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cde/amd64 (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2)
  • Migration status for cde/amd64 (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cde/arm64 (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2)
  • Migration status for cde/arm64 (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cde/armhf (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2)
  • Migration status for cde/armhf (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cde/i386 (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2)
  • Migration status for cde/i386 (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cde/ppc64el (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2)
  • Migration status for cde/ppc64el (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cde/riscv64 (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2)
  • Migration status for cde/riscv64 (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cde/s390x (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2)
  • Migration status for cde/s390x (0.1+git9-g551e54d-2 to 0.1+git9-g551e54d-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cgoban/amd64 (1.9.14-20 to 1.9.14-20)
  • Migration status for cgoban/amd64 (1.9.14-20 to 1.9.14-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cgoban/arm64 (1.9.14-20 to 1.9.14-20)
  • Migration status for cgoban/arm64 (1.9.14-20 to 1.9.14-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cgoban/armhf (1.9.14-20 to 1.9.14-20)
  • Migration status for cgoban/armhf (1.9.14-20 to 1.9.14-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cgoban/i386 (1.9.14-20 to 1.9.14-20)
  • Migration status for cgoban/i386 (1.9.14-20 to 1.9.14-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cgoban/ppc64el (1.9.14-20 to 1.9.14-20)
  • Migration status for cgoban/ppc64el (1.9.14-20 to 1.9.14-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cgoban/riscv64 (1.9.14-20 to 1.9.14-20)
  • Migration status for cgoban/riscv64 (1.9.14-20 to 1.9.14-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cgoban/s390x (1.9.14-20 to 1.9.14-20)
  • Migration status for cgoban/s390x (1.9.14-20 to 1.9.14-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• checkpw/amd64 (1.02-5 to 1.02-5)
  • Migration status for checkpw/amd64 (1.02-5 to 1.02-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• checkpw/arm64 (1.02-5 to 1.02-5)
  • Migration status for checkpw/arm64 (1.02-5 to 1.02-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• checkpw/armhf (1.02-5 to 1.02-5)
  • Migration status for checkpw/armhf (1.02-5 to 1.02-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• checkpw/i386 (1.02-5 to 1.02-5)
  • Migration status for checkpw/i386 (1.02-5 to 1.02-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• checkpw/ppc64el (1.02-5 to 1.02-5)
  • Migration status for checkpw/ppc64el (1.02-5 to 1.02-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• checkpw/riscv64 (1.02-5 to 1.02-5)
  • Migration status for checkpw/riscv64 (1.02-5 to 1.02-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• checkpw/s390x (1.02-5 to 1.02-5)
  • Migration status for checkpw/s390x (1.02-5 to 1.02-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• chromium_pu (140.0.7339.185-1 to 140.0.7339.127-1~deb13u1)
  • Migration status for chromium_pu (140.0.7339.185-1 to 140.0.7339.127-1~deb13u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: chromium is newer in the target suite (140.0.7339.185-1 140.0.7339.127-1~deb13u1)
• cjson_pu (1.7.18-3.1 to 1.7.18-3.1+deb13u1)
  • Migration status for cjson_pu (1.7.18-3.1 to 1.7.18-3.1+deb13u1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • NEEDS APPROVAL BY RM
• ckermit/amd64 (416~beta12-1 to 416~beta12-1)
  • Migration status for ckermit/amd64 (416~beta12-1 to 416~beta12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ckermit/arm64 (416~beta12-1 to 416~beta12-1)
  • Migration status for ckermit/arm64 (416~beta12-1 to 416~beta12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ckermit/armhf (416~beta12-1 to 416~beta12-1)
  • Migration status for ckermit/armhf (416~beta12-1 to 416~beta12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ckermit/i386 (416~beta12-1 to 416~beta12-1)
  • Migration status for ckermit/i386 (416~beta12-1 to 416~beta12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ckermit/ppc64el (416~beta12-1 to 416~beta12-1)
  • Migration status for ckermit/ppc64el (416~beta12-1 to 416~beta12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ckermit/riscv64 (416~beta12-1 to 416~beta12-1)
  • Migration status for ckermit/riscv64 (416~beta12-1 to 416~beta12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ckermit/s390x (416~beta12-1 to 416~beta12-1)
  • Migration status for ckermit/s390x (416~beta12-1 to 416~beta12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clamsmtp/amd64 (1.10-18 to 1.10-18)
  • Migration status for clamsmtp/amd64 (1.10-18 to 1.10-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clamsmtp/arm64 (1.10-18 to 1.10-18)
  • Migration status for clamsmtp/arm64 (1.10-18 to 1.10-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clamsmtp/armhf (1.10-18 to 1.10-18)
  • Migration status for clamsmtp/armhf (1.10-18 to 1.10-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clamsmtp/i386 (1.10-18 to 1.10-18)
  • Migration status for clamsmtp/i386 (1.10-18 to 1.10-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clamsmtp/ppc64el (1.10-18 to 1.10-18)
  • Migration status for clamsmtp/ppc64el (1.10-18 to 1.10-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clamsmtp/riscv64 (1.10-18 to 1.10-18)
  • Migration status for clamsmtp/riscv64 (1.10-18 to 1.10-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clamsmtp/s390x (1.10-18 to 1.10-18)
  • Migration status for clamsmtp/s390x (1.10-18 to 1.10-18): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clipit/amd64 (1.4.5+git20241103-1 to 1.4.5+git20241103-1)
  • Migration status for clipit/amd64 (1.4.5+git20241103-1 to 1.4.5+git20241103-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clipit/arm64 (1.4.5+git20241103-1 to 1.4.5+git20241103-1)
  • Migration status for clipit/arm64 (1.4.5+git20241103-1 to 1.4.5+git20241103-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clipit/armhf (1.4.5+git20241103-1 to 1.4.5+git20241103-1)
  • Migration status for clipit/armhf (1.4.5+git20241103-1 to 1.4.5+git20241103-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clipit/i386 (1.4.5+git20241103-1 to 1.4.5+git20241103-1)
  • Migration status for clipit/i386 (1.4.5+git20241103-1 to 1.4.5+git20241103-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clipit/ppc64el (1.4.5+git20241103-1 to 1.4.5+git20241103-1)
  • Migration status for clipit/ppc64el (1.4.5+git20241103-1 to 1.4.5+git20241103-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clipit/riscv64 (1.4.5+git20241103-1 to 1.4.5+git20241103-1)
  • Migration status for clipit/riscv64 (1.4.5+git20241103-1 to 1.4.5+git20241103-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clipit/s390x (1.4.5+git20241103-1 to 1.4.5+git20241103-1)
  • Migration status for clipit/s390x (1.4.5+git20241103-1 to 1.4.5+git20241103-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clsync/amd64 (0.4.5-2.1 to 0.4.5-2.1)
  • Migration status for clsync/amd64 (0.4.5-2.1 to 0.4.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clsync/arm64 (0.4.5-2.1 to 0.4.5-2.1)
  • Migration status for clsync/arm64 (0.4.5-2.1 to 0.4.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clsync/armhf (0.4.5-2.1 to 0.4.5-2.1)
  • Migration status for clsync/armhf (0.4.5-2.1 to 0.4.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clsync/i386 (0.4.5-2.1 to 0.4.5-2.1)
  • Migration status for clsync/i386 (0.4.5-2.1 to 0.4.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clsync/ppc64el (0.4.5-2.1 to 0.4.5-2.1)
  • Migration status for clsync/ppc64el (0.4.5-2.1 to 0.4.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clsync/riscv64 (0.4.5-2.1 to 0.4.5-2.1)
  • Migration status for clsync/riscv64 (0.4.5-2.1 to 0.4.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• clsync/s390x (0.4.5-2.1 to 0.4.5-2.1)
  • Migration status for clsync/s390x (0.4.5-2.1 to 0.4.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• codelite/amd64 (17.0.0+dfsg-4 to 17.0.0+dfsg-4)
  • Migration status for codelite/amd64 (17.0.0+dfsg-4 to 17.0.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• codelite/arm64 (17.0.0+dfsg-4 to 17.0.0+dfsg-4)
  • Migration status for codelite/arm64 (17.0.0+dfsg-4 to 17.0.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• codelite/armhf (17.0.0+dfsg-4 to 17.0.0+dfsg-4)
  • Migration status for codelite/armhf (17.0.0+dfsg-4 to 17.0.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• codelite/i386 (17.0.0+dfsg-4 to 17.0.0+dfsg-4)
  • Migration status for codelite/i386 (17.0.0+dfsg-4 to 17.0.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• codelite/ppc64el (17.0.0+dfsg-4 to 17.0.0+dfsg-4)
  • Migration status for codelite/ppc64el (17.0.0+dfsg-4 to 17.0.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• codelite/riscv64 (17.0.0+dfsg-4 to 17.0.0+dfsg-4)
  • Migration status for codelite/riscv64 (17.0.0+dfsg-4 to 17.0.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• codelite/s390x (17.0.0+dfsg-4 to 17.0.0+dfsg-4)
  • Migration status for codelite/s390x (17.0.0+dfsg-4 to 17.0.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• colmap/amd64 (3.10-2 to 3.10-2)
  • Migration status for colmap/amd64 (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• colmap/arm64 (3.10-2 to 3.10-2)
  • Migration status for colmap/arm64 (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• colmap/armhf (3.10-2 to 3.10-2)
  • Migration status for colmap/armhf (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• colmap/i386 (3.10-2 to 3.10-2)
  • Migration status for colmap/i386 (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• colmap/ppc64el (3.10-2 to 3.10-2)
  • Migration status for colmap/ppc64el (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• colmap/riscv64 (3.10-2 to 3.10-2)
  • Migration status for colmap/riscv64 (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• colmap/s390x (3.10-2 to 3.10-2)
  • Migration status for colmap/s390x (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• conserver/amd64 (8.2.7-3 to 8.2.7-3)
  • Migration status for conserver/amd64 (8.2.7-3 to 8.2.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• conserver/arm64 (8.2.7-3 to 8.2.7-3)
  • Migration status for conserver/arm64 (8.2.7-3 to 8.2.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• conserver/armhf (8.2.7-3 to 8.2.7-3)
  • Migration status for conserver/armhf (8.2.7-3 to 8.2.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• conserver/i386 (8.2.7-3 to 8.2.7-3)
  • Migration status for conserver/i386 (8.2.7-3 to 8.2.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• conserver/ppc64el (8.2.7-3 to 8.2.7-3)
  • Migration status for conserver/ppc64el (8.2.7-3 to 8.2.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• conserver/riscv64 (8.2.7-3 to 8.2.7-3)
  • Migration status for conserver/riscv64 (8.2.7-3 to 8.2.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• conserver/s390x (8.2.7-3 to 8.2.7-3)
  • Migration status for conserver/s390x (8.2.7-3 to 8.2.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpdb-backend-cups/amd64 (2.0b5-1 to 2.0b5-1)
  • Migration status for cpdb-backend-cups/amd64 (2.0b5-1 to 2.0b5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpdb-backend-cups/arm64 (2.0b5-1 to 2.0b5-1)
  • Migration status for cpdb-backend-cups/arm64 (2.0b5-1 to 2.0b5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpdb-backend-cups/armhf (2.0b5-1 to 2.0b5-1)
  • Migration status for cpdb-backend-cups/armhf (2.0b5-1 to 2.0b5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpdb-backend-cups/i386 (2.0b5-1 to 2.0b5-1)
  • Migration status for cpdb-backend-cups/i386 (2.0b5-1 to 2.0b5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpdb-backend-cups/ppc64el (2.0b5-1 to 2.0b5-1)
  • Migration status for cpdb-backend-cups/ppc64el (2.0b5-1 to 2.0b5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpdb-backend-cups/riscv64 (2.0b5-1 to 2.0b5-1)
  • Migration status for cpdb-backend-cups/riscv64 (2.0b5-1 to 2.0b5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpdb-backend-cups/s390x (2.0b5-1 to 2.0b5-1)
  • Migration status for cpdb-backend-cups/s390x (2.0b5-1 to 2.0b5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpp-hocon/amd64 (0.3.0-1.1 to 0.3.0-1.1)
  • Migration status for cpp-hocon/amd64 (0.3.0-1.1 to 0.3.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpp-hocon/arm64 (0.3.0-1.1 to 0.3.0-1.1)
  • Migration status for cpp-hocon/arm64 (0.3.0-1.1 to 0.3.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpp-hocon/armhf (0.3.0-1.1 to 0.3.0-1.1)
  • Migration status for cpp-hocon/armhf (0.3.0-1.1 to 0.3.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpp-hocon/i386 (0.3.0-1.1 to 0.3.0-1.1)
  • Migration status for cpp-hocon/i386 (0.3.0-1.1 to 0.3.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpp-hocon/ppc64el (0.3.0-1.1 to 0.3.0-1.1)
  • Migration status for cpp-hocon/ppc64el (0.3.0-1.1 to 0.3.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpp-hocon/s390x (0.3.0-1.1 to 0.3.0-1.1)
  • Migration status for cpp-hocon/s390x (0.3.0-1.1 to 0.3.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpptraj/amd64 (5.1.0+dfsg-4 to 5.1.0+dfsg-4)
  • Migration status for cpptraj/amd64 (5.1.0+dfsg-4 to 5.1.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpptraj/arm64 (5.1.0+dfsg-4 to 5.1.0+dfsg-4)
  • Migration status for cpptraj/arm64 (5.1.0+dfsg-4 to 5.1.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpptraj/armhf (5.1.0+dfsg-4 to 5.1.0+dfsg-4)
  • Migration status for cpptraj/armhf (5.1.0+dfsg-4 to 5.1.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpptraj/i386 (5.1.0+dfsg-4 to 5.1.0+dfsg-4)
  • Migration status for cpptraj/i386 (5.1.0+dfsg-4 to 5.1.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpptraj/ppc64el (5.1.0+dfsg-4 to 5.1.0+dfsg-4)
  • Migration status for cpptraj/ppc64el (5.1.0+dfsg-4 to 5.1.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpptraj/riscv64 (5.1.0+dfsg-4 to 5.1.0+dfsg-4)
  • Migration status for cpptraj/riscv64 (5.1.0+dfsg-4 to 5.1.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cpptraj/s390x (5.1.0+dfsg-4 to 5.1.0+dfsg-4)
  • Migration status for cpptraj/s390x (5.1.0+dfsg-4 to 5.1.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• crashmail/amd64 (1.7-4 to 1.7-4)
  • Migration status for crashmail/amd64 (1.7-4 to 1.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• crashmail/arm64 (1.7-4 to 1.7-4)
  • Migration status for crashmail/arm64 (1.7-4 to 1.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• crashmail/armhf (1.7-4 to 1.7-4)
  • Migration status for crashmail/armhf (1.7-4 to 1.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• crashmail/i386 (1.7-4 to 1.7-4)
  • Migration status for crashmail/i386 (1.7-4 to 1.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• crashmail/ppc64el (1.7-4 to 1.7-4)
  • Migration status for crashmail/ppc64el (1.7-4 to 1.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• crashmail/riscv64 (1.7-4 to 1.7-4)
  • Migration status for crashmail/riscv64 (1.7-4 to 1.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• crashmail/s390x (1.7-4 to 1.7-4)
  • Migration status for crashmail/s390x (1.7-4 to 1.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• crasm/amd64 (1.8-3 to 1.8-3)
  • Migration status for crasm/amd64 (1.8-3 to 1.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
• crasm/arm64 (1.8-3 to 1.8-3)
  • Migration status for crasm/arm64 (1.8-3 to 1.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
• crasm/armhf (1.8-3 to 1.8-3)
  • Migration status for crasm/armhf (1.8-3 to 1.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
• crasm/i386 (1.8-3 to 1.8-3)
  • Migration status for crasm/i386 (1.8-3 to 1.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
• crasm/ppc64el (1.8-3 to 1.8-3)
  • Migration status for crasm/ppc64el (1.8-3 to 1.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
• crasm/riscv64 (1.8-3 to 1.8-3)
  • Migration status for crasm/riscv64 (1.8-3 to 1.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
• crasm/s390x (1.8-3 to 1.8-3)
  • Migration status for crasm/s390x (1.8-3 to 1.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
• creduce/amd64 (2.11.0~20240909-2 to 2.11.0~20240909-2)
  • Migration status for creduce/amd64 (2.11.0~20240909-2 to 2.11.0~20240909-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• creduce/arm64 (2.11.0~20240909-2 to 2.11.0~20240909-2)
  • Migration status for creduce/arm64 (2.11.0~20240909-2 to 2.11.0~20240909-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• creduce/armhf (2.11.0~20240909-2 to 2.11.0~20240909-2)
  • Migration status for creduce/armhf (2.11.0~20240909-2 to 2.11.0~20240909-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• creduce/i386 (2.11.0~20240909-2 to 2.11.0~20240909-2)
  • Migration status for creduce/i386 (2.11.0~20240909-2 to 2.11.0~20240909-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• creduce/ppc64el (2.11.0~20240909-2 to 2.11.0~20240909-2)
  • Migration status for creduce/ppc64el (2.11.0~20240909-2 to 2.11.0~20240909-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• creduce/riscv64 (2.11.0~20240909-2 to 2.11.0~20240909-2)
  • Migration status for creduce/riscv64 (2.11.0~20240909-2 to 2.11.0~20240909-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• creduce/s390x (2.11.0~20240909-2 to 2.11.0~20240909-2)
  • Migration status for creduce/s390x (2.11.0~20240909-2 to 2.11.0~20240909-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• criterion/amd64 (2.4.1-2 to 2.4.1-2)
  • Migration status for criterion/amd64 (2.4.1-2 to 2.4.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
• criterion/arm64 (2.4.1-2 to 2.4.1-2)
  • Migration status for criterion/arm64 (2.4.1-2 to 2.4.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
• criterion/armhf (2.4.1-2 to 2.4.1-2)
  • Migration status for criterion/armhf (2.4.1-2 to 2.4.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
• criterion/i386 (2.4.1-2 to 2.4.1-2)
  • Migration status for criterion/i386 (2.4.1-2 to 2.4.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
• criterion/ppc64el (2.4.1-2 to 2.4.1-2)
  • Migration status for criterion/ppc64el (2.4.1-2 to 2.4.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
• criterion/riscv64 (2.4.1-2 to 2.4.1-2)
  • Migration status for criterion/riscv64 (2.4.1-2 to 2.4.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
• criterion/s390x (2.4.1-2 to 2.4.1-2)
  • Migration status for criterion/s390x (2.4.1-2 to 2.4.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
• cssc/amd64 (1.4.1-1 to 1.4.1-1)
  • Migration status for cssc/amd64 (1.4.1-1 to 1.4.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
• cssc/arm64 (1.4.1-1 to 1.4.1-1)
  • Migration status for cssc/arm64 (1.4.1-1 to 1.4.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
• cssc/armhf (1.4.1-1 to 1.4.1-1)
  • Migration status for cssc/armhf (1.4.1-1 to 1.4.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
• cssc/i386 (1.4.1-1 to 1.4.1-1)
  • Migration status for cssc/i386 (1.4.1-1 to 1.4.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
• cssc/ppc64el (1.4.1-1 to 1.4.1-1)
  • Migration status for cssc/ppc64el (1.4.1-1 to 1.4.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
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cssc/s390x (1.4.1-1 to 1.4.1-1)
  • Migration status for cssc/s390x (1.4.1-1 to 1.4.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
• cups_pu (2.4.10-4 to 2.4.10-3+deb13u1)
  • Migration status for cups_pu (2.4.10-4 to 2.4.10-3+deb13u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: cups is newer in the target suite (2.4.10-4 2.4.10-3+deb13u1)
• cupt/amd64 (2.10.4+nmu2 to 2.10.4+nmu2)
  • Migration status for cupt/amd64 (2.10.4+nmu2 to 2.10.4+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cupt/arm64 (2.10.4+nmu2 to 2.10.4+nmu2)
  • Migration status for cupt/arm64 (2.10.4+nmu2 to 2.10.4+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cupt/armhf (2.10.4+nmu2 to 2.10.4+nmu2)
  • Migration status for cupt/armhf (2.10.4+nmu2 to 2.10.4+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cupt/i386 (2.10.4+nmu2 to 2.10.4+nmu2)
  • Migration status for cupt/i386 (2.10.4+nmu2 to 2.10.4+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cupt/ppc64el (2.10.4+nmu2 to 2.10.4+nmu2)
  • Migration status for cupt/ppc64el (2.10.4+nmu2 to 2.10.4+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• cupt/s390x (2.10.4+nmu2 to 2.10.4+nmu2)
  • Migration status for cupt/s390x (2.10.4+nmu2 to 2.10.4+nmu2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dact/amd64 (0.8.42-6 to 0.8.42-6)
  • Migration status for dact/amd64 (0.8.42-6 to 0.8.42-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dact/arm64 (0.8.42-6 to 0.8.42-6)
  • Migration status for dact/arm64 (0.8.42-6 to 0.8.42-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dact/armhf (0.8.42-6 to 0.8.42-6)
  • Migration status for dact/armhf (0.8.42-6 to 0.8.42-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dact/i386 (0.8.42-6 to 0.8.42-6)
  • Migration status for dact/i386 (0.8.42-6 to 0.8.42-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dact/ppc64el (0.8.42-6 to 0.8.42-6)
  • Migration status for dact/ppc64el (0.8.42-6 to 0.8.42-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dact/riscv64 (0.8.42-6 to 0.8.42-6)
  • Migration status for dact/riscv64 (0.8.42-6 to 0.8.42-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dact/s390x (0.8.42-6 to 0.8.42-6)
  • Migration status for dact/s390x (0.8.42-6 to 0.8.42-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• daemonize/amd64 (1.7.8-4 to 1.7.8-4)
  • Migration status for daemonize/amd64 (1.7.8-4 to 1.7.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• daemonize/arm64 (1.7.8-4 to 1.7.8-4)
  • Migration status for daemonize/arm64 (1.7.8-4 to 1.7.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• daemonize/armhf (1.7.8-4 to 1.7.8-4)
  • Migration status for daemonize/armhf (1.7.8-4 to 1.7.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• daemonize/i386 (1.7.8-4 to 1.7.8-4)
  • Migration status for daemonize/i386 (1.7.8-4 to 1.7.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• daemonize/ppc64el (1.7.8-4 to 1.7.8-4)
  • Migration status for daemonize/ppc64el (1.7.8-4 to 1.7.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• daemonize/riscv64 (1.7.8-4 to 1.7.8-4)
  • Migration status for daemonize/riscv64 (1.7.8-4 to 1.7.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• daemonize/s390x (1.7.8-4 to 1.7.8-4)
  • Migration status for daemonize/s390x (1.7.8-4 to 1.7.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dbusada/amd64 (0.6.3-2 to 0.6.3-2)
  • Migration status for dbusada/amd64 (0.6.3-2 to 0.6.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
• dbusada/arm64 (0.6.3-2 to 0.6.3-2)
  • Migration status for dbusada/arm64 (0.6.3-2 to 0.6.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
• dbusada/armhf (0.6.3-2 to 0.6.3-2)
  • Migration status for dbusada/armhf (0.6.3-2 to 0.6.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
• dbusada/i386 (0.6.3-2 to 0.6.3-2)
  • Migration status for dbusada/i386 (0.6.3-2 to 0.6.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
• dbusada/ppc64el (0.6.3-2 to 0.6.3-2)
  • Migration status for dbusada/ppc64el (0.6.3-2 to 0.6.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
• dbusada/riscv64 (0.6.3-2 to 0.6.3-2)
  • Migration status for dbusada/riscv64 (0.6.3-2 to 0.6.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
• dbusada/s390x (0.6.3-2 to 0.6.3-2)
  • Migration status for dbusada/s390x (0.6.3-2 to 0.6.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
• dd2/amd64 (0.2.2-5 to 0.2.2-5)
  • Migration status for dd2/amd64 (0.2.2-5 to 0.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dd2/arm64 (0.2.2-5 to 0.2.2-5)
  • Migration status for dd2/arm64 (0.2.2-5 to 0.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dd2/armhf (0.2.2-5 to 0.2.2-5)
  • Migration status for dd2/armhf (0.2.2-5 to 0.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dd2/i386 (0.2.2-5 to 0.2.2-5)
  • Migration status for dd2/i386 (0.2.2-5 to 0.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dd2/ppc64el (0.2.2-5 to 0.2.2-5)
  • Migration status for dd2/ppc64el (0.2.2-5 to 0.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dd2/riscv64 (0.2.2-5 to 0.2.2-5)
  • Migration status for dd2/riscv64 (0.2.2-5 to 0.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dd2/s390x (0.2.2-5 to 0.2.2-5)
  • Migration status for dd2/s390x (0.2.2-5 to 0.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• debdelta/amd64 (0.70+nmu1 to 0.70+nmu1)
  • Migration status for debdelta/amd64 (0.70+nmu1 to 0.70+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• debdelta/arm64 (0.70+nmu1 to 0.70+nmu1)
  • Migration status for debdelta/arm64 (0.70+nmu1 to 0.70+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• debdelta/armhf (0.70+nmu1 to 0.70+nmu1)
  • Migration status for debdelta/armhf (0.70+nmu1 to 0.70+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• debdelta/i386 (0.70+nmu1 to 0.70+nmu1)
  • Migration status for debdelta/i386 (0.70+nmu1 to 0.70+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• debdelta/ppc64el (0.70+nmu1 to 0.70+nmu1)
  • Migration status for debdelta/ppc64el (0.70+nmu1 to 0.70+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• debdelta/riscv64 (0.70+nmu1 to 0.70+nmu1)
  • Migration status for debdelta/riscv64 (0.70+nmu1 to 0.70+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• debdelta/s390x (0.70+nmu1 to 0.70+nmu1)
  • Migration status for debdelta/s390x (0.70+nmu1 to 0.70+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dfu-programmer/amd64 (0.6.1-1 to 0.6.1-1)
  • Migration status for dfu-programmer/amd64 (0.6.1-1 to 0.6.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
• dfu-programmer/arm64 (0.6.1-1 to 0.6.1-1)
  • Migration status for dfu-programmer/arm64 (0.6.1-1 to 0.6.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
• dfu-programmer/armhf (0.6.1-1 to 0.6.1-1)
  • Migration status for dfu-programmer/armhf (0.6.1-1 to 0.6.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
• dfu-programmer/i386 (0.6.1-1 to 0.6.1-1)
  • Migration status for dfu-programmer/i386 (0.6.1-1 to 0.6.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
• dfu-programmer/ppc64el (0.6.1-1 to 0.6.1-1)
  • Migration status for dfu-programmer/ppc64el (0.6.1-1 to 0.6.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
• dfu-programmer/riscv64 (0.6.1-1 to 0.6.1-1)
  • Migration status for dfu-programmer/riscv64 (0.6.1-1 to 0.6.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
• dfu-programmer/s390x (0.6.1-1 to 0.6.1-1)
  • Migration status for dfu-programmer/s390x (0.6.1-1 to 0.6.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
• dhcp-probe/amd64 (1.3.1-1 to 1.3.1-1)
  • Migration status for dhcp-probe/amd64 (1.3.1-1 to 1.3.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
• dhcp-probe/arm64 (1.3.1-1 to 1.3.1-1)
  • Migration status for dhcp-probe/arm64 (1.3.1-1 to 1.3.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
• dhcp-probe/armhf (1.3.1-1 to 1.3.1-1)
  • Migration status for dhcp-probe/armhf (1.3.1-1 to 1.3.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
• dhcp-probe/i386 (1.3.1-1 to 1.3.1-1)
  • Migration status for dhcp-probe/i386 (1.3.1-1 to 1.3.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
• dhcp-probe/ppc64el (1.3.1-1 to 1.3.1-1)
  • Migration status for dhcp-probe/ppc64el (1.3.1-1 to 1.3.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
• dhcp-probe/riscv64 (1.3.1-1 to 1.3.1-1)
  • Migration status for dhcp-probe/riscv64 (1.3.1-1 to 1.3.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
• dhcp-probe/s390x (1.3.1-1 to 1.3.1-1)
  • Migration status for dhcp-probe/s390x (1.3.1-1 to 1.3.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
• dhex/amd64 (0.69-4 to 0.69-4)
  • Migration status for dhex/amd64 (0.69-4 to 0.69-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dhex/arm64 (0.69-4 to 0.69-4)
  • Migration status for dhex/arm64 (0.69-4 to 0.69-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dhex/armhf (0.69-4 to 0.69-4)
  • Migration status for dhex/armhf (0.69-4 to 0.69-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dhex/i386 (0.69-4 to 0.69-4)
  • Migration status for dhex/i386 (0.69-4 to 0.69-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dhex/ppc64el (0.69-4 to 0.69-4)
  • Migration status for dhex/ppc64el (0.69-4 to 0.69-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dhex/riscv64 (0.69-4 to 0.69-4)
  • Migration status for dhex/riscv64 (0.69-4 to 0.69-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dhex/s390x (0.69-4 to 0.69-4)
  • Migration status for dhex/s390x (0.69-4 to 0.69-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• diod/amd64 (1.0.24-5.1 to 1.0.24-5.1)
  • Migration status for diod/amd64 (1.0.24-5.1 to 1.0.24-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• diod/arm64 (1.0.24-5.1 to 1.0.24-5.1)
  • Migration status for diod/arm64 (1.0.24-5.1 to 1.0.24-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• diod/armhf (1.0.24-5.1 to 1.0.24-5.1)
  • Migration status for diod/armhf (1.0.24-5.1 to 1.0.24-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• diod/i386 (1.0.24-5.1 to 1.0.24-5.1)
  • Migration status for diod/i386 (1.0.24-5.1 to 1.0.24-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• diod/ppc64el (1.0.24-5.1 to 1.0.24-5.1)
  • Migration status for diod/ppc64el (1.0.24-5.1 to 1.0.24-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• diod/s390x (1.0.24-5.1 to 1.0.24-5.1)
  • Migration status for diod/s390x (1.0.24-5.1 to 1.0.24-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dmrgpp/amd64 (6.06-2 to 6.06-2)
  • Migration status for dmrgpp/amd64 (6.06-2 to 6.06-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dmrgpp/arm64 (6.06-2 to 6.06-2)
  • Migration status for dmrgpp/arm64 (6.06-2 to 6.06-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dmrgpp/armhf (6.06-2 to 6.06-2)
  • Migration status for dmrgpp/armhf (6.06-2 to 6.06-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dmrgpp/i386 (6.06-2 to 6.06-2)
  • Migration status for dmrgpp/i386 (6.06-2 to 6.06-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dmrgpp/ppc64el (6.06-2 to 6.06-2)
  • Migration status for dmrgpp/ppc64el (6.06-2 to 6.06-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dmrgpp/riscv64 (6.06-2 to 6.06-2)
  • Migration status for dmrgpp/riscv64 (6.06-2 to 6.06-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dmrgpp/s390x (6.06-2 to 6.06-2)
  • Migration status for dmrgpp/s390x (6.06-2 to 6.06-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dolphin-emu/amd64 (2506+dfsg-3 to 2506+dfsg-3)
  • Migration status for dolphin-emu/amd64 (2506+dfsg-3 to 2506+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: dolphin-emu/amd64 miniupnpc (not considered)
    • Invalidated by dependency
• dolphin-emu/arm64 (2506+dfsg-3 to 2506+dfsg-3)
  • Migration status for dolphin-emu/arm64 (2506+dfsg-3 to 2506+dfsg-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: dolphin-emu/arm64 miniupnpc (not considered)
    • Invalidated by dependency
• dolphin-emu_pu (2506+dfsg-3 to 2503+dfsg-1+deb13u1)
  • Migration status for dolphin-emu_pu (2506+dfsg-3 to 2503+dfsg-1+deb13u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: dolphin-emu is newer in the target suite (2506+dfsg-3 2503+dfsg-1+deb13u1)
• dopewars/amd64 (1.6.2-1 to 1.6.2-1)
  • Migration status for dopewars/amd64 (1.6.2-1 to 1.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dopewars/arm64 (1.6.2-1 to 1.6.2-1)
  • Migration status for dopewars/arm64 (1.6.2-1 to 1.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dopewars/armhf (1.6.2-1 to 1.6.2-1)
  • Migration status for dopewars/armhf (1.6.2-1 to 1.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dopewars/i386 (1.6.2-1 to 1.6.2-1)
  • Migration status for dopewars/i386 (1.6.2-1 to 1.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dopewars/ppc64el (1.6.2-1 to 1.6.2-1)
  • Migration status for dopewars/ppc64el (1.6.2-1 to 1.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dopewars/s390x (1.6.2-1 to 1.6.2-1)
  • Migration status for dopewars/s390x (1.6.2-1 to 1.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drawterm-9front/amd64 (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3)
  • Migration status for drawterm-9front/amd64 (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drawterm-9front/arm64 (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3)
  • Migration status for drawterm-9front/arm64 (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drawterm-9front/armhf (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3)
  • Migration status for drawterm-9front/armhf (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drawterm-9front/i386 (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3)
  • Migration status for drawterm-9front/i386 (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drawterm-9front/ppc64el (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3)
  • Migration status for drawterm-9front/ppc64el (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drawterm-9front/riscv64 (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3)
  • Migration status for drawterm-9front/riscv64 (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drawterm-9front/s390x (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3)
  • Migration status for drawterm-9front/s390x (0~git20220608.bee4db6-3 to 0~git20220608.bee4db6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drbd-utils/amd64 (9.22.0-1.1 to 9.22.0-1.1)
  • Migration status for drbd-utils/amd64 (9.22.0-1.1 to 9.22.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drbd-utils/arm64 (9.22.0-1.1 to 9.22.0-1.1)
  • Migration status for drbd-utils/arm64 (9.22.0-1.1 to 9.22.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drbd-utils/armhf (9.22.0-1.1 to 9.22.0-1.1)
  • Migration status for drbd-utils/armhf (9.22.0-1.1 to 9.22.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drbd-utils/i386 (9.22.0-1.1 to 9.22.0-1.1)
  • Migration status for drbd-utils/i386 (9.22.0-1.1 to 9.22.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drbd-utils/ppc64el (9.22.0-1.1 to 9.22.0-1.1)
  • Migration status for drbd-utils/ppc64el (9.22.0-1.1 to 9.22.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drbd-utils/riscv64 (9.22.0-1.1 to 9.22.0-1.1)
  • Migration status for drbd-utils/riscv64 (9.22.0-1.1 to 9.22.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• drbd-utils/s390x (9.22.0-1.1 to 9.22.0-1.1)
  • Migration status for drbd-utils/s390x (9.22.0-1.1 to 9.22.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• driftnet/amd64 (1.5.0-0.2 to 1.5.0-0.2)
  • Migration status for driftnet/amd64 (1.5.0-0.2 to 1.5.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• driftnet/arm64 (1.5.0-0.2 to 1.5.0-0.2)
  • Migration status for driftnet/arm64 (1.5.0-0.2 to 1.5.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• driftnet/armhf (1.5.0-0.2 to 1.5.0-0.2)
  • Migration status for driftnet/armhf (1.5.0-0.2 to 1.5.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• driftnet/i386 (1.5.0-0.2 to 1.5.0-0.2)
  • Migration status for driftnet/i386 (1.5.0-0.2 to 1.5.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• driftnet/ppc64el (1.5.0-0.2 to 1.5.0-0.2)
  • Migration status for driftnet/ppc64el (1.5.0-0.2 to 1.5.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• driftnet/s390x (1.5.0-0.2 to 1.5.0-0.2)
  • Migration status for driftnet/s390x (1.5.0-0.2 to 1.5.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dvbtune/amd64 (0.5.ds-5 to 0.5.ds-5)
  • Migration status for dvbtune/amd64 (0.5.ds-5 to 0.5.ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dvbtune/arm64 (0.5.ds-5 to 0.5.ds-5)
  • Migration status for dvbtune/arm64 (0.5.ds-5 to 0.5.ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dvbtune/armhf (0.5.ds-5 to 0.5.ds-5)
  • Migration status for dvbtune/armhf (0.5.ds-5 to 0.5.ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dvbtune/i386 (0.5.ds-5 to 0.5.ds-5)
  • Migration status for dvbtune/i386 (0.5.ds-5 to 0.5.ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dvbtune/ppc64el (0.5.ds-5 to 0.5.ds-5)
  • Migration status for dvbtune/ppc64el (0.5.ds-5 to 0.5.ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dvbtune/s390x (0.5.ds-5 to 0.5.ds-5)
  • Migration status for dvbtune/s390x (0.5.ds-5 to 0.5.ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• dwgsim/amd64 (0.1.14-3 to 0.1.14-3)
  • Migration status for dwgsim/amd64 (0.1.14-3 to 0.1.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
• dwgsim/arm64 (0.1.14-3 to 0.1.14-3)
  • Migration status for dwgsim/arm64 (0.1.14-3 to 0.1.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
• dwgsim/armhf (0.1.14-3 to 0.1.14-3)
  • Migration status for dwgsim/armhf (0.1.14-3 to 0.1.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
• dwgsim/i386 (0.1.14-3 to 0.1.14-3)
  • Migration status for dwgsim/i386 (0.1.14-3 to 0.1.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
• dwgsim/ppc64el (0.1.14-3 to 0.1.14-3)
  • Migration status for dwgsim/ppc64el (0.1.14-3 to 0.1.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
• dwgsim/riscv64 (0.1.14-3 to 0.1.14-3)
  • Migration status for dwgsim/riscv64 (0.1.14-3 to 0.1.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
• dwgsim/s390x (0.1.14-3 to 0.1.14-3)
  • Migration status for dwgsim/s390x (0.1.14-3 to 0.1.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
• edge-addition-planarity-suite/amd64 (3.0.2.0-2.1 to 3.0.2.0-2.1)
  • Migration status for edge-addition-planarity-suite/amd64 (3.0.2.0-2.1 to 3.0.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• edge-addition-planarity-suite/arm64 (3.0.2.0-2.1 to 3.0.2.0-2.1)
  • Migration status for edge-addition-planarity-suite/arm64 (3.0.2.0-2.1 to 3.0.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• edge-addition-planarity-suite/armhf (3.0.2.0-2.1 to 3.0.2.0-2.1)
  • Migration status for edge-addition-planarity-suite/armhf (3.0.2.0-2.1 to 3.0.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• edge-addition-planarity-suite/i386 (3.0.2.0-2.1 to 3.0.2.0-2.1)
  • Migration status for edge-addition-planarity-suite/i386 (3.0.2.0-2.1 to 3.0.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• edge-addition-planarity-suite/ppc64el (3.0.2.0-2.1 to 3.0.2.0-2.1)
  • Migration status for edge-addition-planarity-suite/ppc64el (3.0.2.0-2.1 to 3.0.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• edge-addition-planarity-suite/riscv64 (3.0.2.0-2.1 to 3.0.2.0-2.1)
  • Migration status for edge-addition-planarity-suite/riscv64 (3.0.2.0-2.1 to 3.0.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• edge-addition-planarity-suite/s390x (3.0.2.0-2.1 to 3.0.2.0-2.1)
  • Migration status for edge-addition-planarity-suite/s390x (3.0.2.0-2.1 to 3.0.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eiskaltdcpp/amd64 (2.4.2-1.3 to 2.4.2-1.3)
  • Migration status for eiskaltdcpp/amd64 (2.4.2-1.3 to 2.4.2-1.3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: eiskaltdcpp/amd64 miniupnpc (not considered)
    • Invalidated by dependency
• eiskaltdcpp/arm64 (2.4.2-1.3 to 2.4.2-1.3)
  • Migration status for eiskaltdcpp/arm64 (2.4.2-1.3 to 2.4.2-1.3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: eiskaltdcpp/arm64 miniupnpc (not considered)
    • Invalidated by dependency
• eiskaltdcpp/armhf (2.4.2-1.3 to 2.4.2-1.3)
  • Migration status for eiskaltdcpp/armhf (2.4.2-1.3 to 2.4.2-1.3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: eiskaltdcpp/armhf miniupnpc (not considered)
    • Invalidated by dependency
• eiskaltdcpp/i386 (2.4.2-1.3 to 2.4.2-1.3)
  • Migration status for eiskaltdcpp/i386 (2.4.2-1.3 to 2.4.2-1.3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: eiskaltdcpp/i386 miniupnpc (not considered)
    • Invalidated by dependency
• eiskaltdcpp/ppc64el (2.4.2-1.3 to 2.4.2-1.3)
  • Migration status for eiskaltdcpp/ppc64el (2.4.2-1.3 to 2.4.2-1.3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: eiskaltdcpp/ppc64el miniupnpc (not considered)
    • Invalidated by dependency
• eiskaltdcpp/riscv64 (2.4.2-1.3 to 2.4.2-1.3)
  • Migration status for eiskaltdcpp/riscv64 (2.4.2-1.3 to 2.4.2-1.3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: eiskaltdcpp/riscv64 miniupnpc (not considered)
    • Invalidated by dependency
• eiskaltdcpp/s390x (2.4.2-1.3 to 2.4.2-1.3)
  • Migration status for eiskaltdcpp/s390x (2.4.2-1.3 to 2.4.2-1.3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: eiskaltdcpp/s390x miniupnpc (not considered)
    • Invalidated by dependency
• esys-particle/amd64 (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11)
  • Migration status for esys-particle/amd64 (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• esys-particle/arm64 (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11)
  • Migration status for esys-particle/arm64 (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• esys-particle/armhf (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11)
  • Migration status for esys-particle/armhf (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• esys-particle/i386 (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11)
  • Migration status for esys-particle/i386 (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• esys-particle/ppc64el (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11)
  • Migration status for esys-particle/ppc64el (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• esys-particle/riscv64 (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11)
  • Migration status for esys-particle/riscv64 (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• esys-particle/s390x (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11)
  • Migration status for esys-particle/s390x (2.3.5+dfsg2-11 to 2.3.5+dfsg2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eta/amd64 (1.0.1-1 to 1.0.1-1)
  • Migration status for eta/amd64 (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eta/arm64 (1.0.1-1 to 1.0.1-1)
  • Migration status for eta/arm64 (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eta/armhf (1.0.1-1 to 1.0.1-1)
  • Migration status for eta/armhf (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eta/i386 (1.0.1-1 to 1.0.1-1)
  • Migration status for eta/i386 (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eta/ppc64el (1.0.1-1 to 1.0.1-1)
  • Migration status for eta/ppc64el (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eta/riscv64 (1.0.1-1 to 1.0.1-1)
  • Migration status for eta/riscv64 (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eta/s390x (1.0.1-1 to 1.0.1-1)
  • Migration status for eta/s390x (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eukleides/amd64 (1.5.4-5 to 1.5.4-5)
  • Migration status for eukleides/amd64 (1.5.4-5 to 1.5.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eukleides/arm64 (1.5.4-5 to 1.5.4-5)
  • Migration status for eukleides/arm64 (1.5.4-5 to 1.5.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eukleides/armhf (1.5.4-5 to 1.5.4-5)
  • Migration status for eukleides/armhf (1.5.4-5 to 1.5.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eukleides/i386 (1.5.4-5 to 1.5.4-5)
  • Migration status for eukleides/i386 (1.5.4-5 to 1.5.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eukleides/ppc64el (1.5.4-5 to 1.5.4-5)
  • Migration status for eukleides/ppc64el (1.5.4-5 to 1.5.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eukleides/riscv64 (1.5.4-5 to 1.5.4-5)
  • Migration status for eukleides/riscv64 (1.5.4-5 to 1.5.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• eukleides/s390x (1.5.4-5 to 1.5.4-5)
  • Migration status for eukleides/s390x (1.5.4-5 to 1.5.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fasta3/amd64 (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3)
  • Migration status for fasta3/amd64 (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fasta3/arm64 (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3)
  • Migration status for fasta3/arm64 (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fasta3/armhf (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3)
  • Migration status for fasta3/armhf (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fasta3/i386 (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3)
  • Migration status for fasta3/i386 (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fasta3/ppc64el (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3)
  • Migration status for fasta3/ppc64el (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fasta3/riscv64 (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3)
  • Migration status for fasta3/riscv64 (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fasta3/s390x (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3)
  • Migration status for fasta3/s390x (36.3.8i.14-Nov-2020-3 to 36.3.8i.14-Nov-2020-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastdds/amd64 (3.1.2+ds-1 to 3.1.2+ds-1)
  • Migration status for fastdds/amd64 (3.1.2+ds-1 to 3.1.2+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
• fastdds/arm64 (3.1.2+ds-1 to 3.1.2+ds-1)
  • Migration status for fastdds/arm64 (3.1.2+ds-1 to 3.1.2+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
• fastdds/armhf (3.1.2+ds-1 to 3.1.2+ds-1)
  • Migration status for fastdds/armhf (3.1.2+ds-1 to 3.1.2+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
• fastdds/i386 (3.1.2+ds-1 to 3.1.2+ds-1)
  • Migration status for fastdds/i386 (3.1.2+ds-1 to 3.1.2+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
• fastdds/ppc64el (3.1.2+ds-1 to 3.1.2+ds-1)
  • Migration status for fastdds/ppc64el (3.1.2+ds-1 to 3.1.2+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
• fastdds/riscv64 (3.1.2+ds-1 to 3.1.2+ds-1)
  • Migration status for fastdds/riscv64 (3.1.2+ds-1 to 3.1.2+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
• fastdds/s390x (3.1.2+ds-1 to 3.1.2+ds-1)
  • Migration status for fastdds/s390x (3.1.2+ds-1 to 3.1.2+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
• fastjet/amd64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/amd64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastjet/arm64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/arm64 (3.4.0+dfsg-1 to 3.4.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastjet/armhf (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/armhf (3.4.0+dfsg-1 to 3.4.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastjet/i386 (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/i386 (3.4.0+dfsg-1 to 3.4.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastjet/ppc64el (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/ppc64el (3.4.0+dfsg-1 to 3.4.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastjet/s390x (3.4.0+dfsg-1 to 3.4.0+dfsg-1)
  • Migration status for fastjet/s390x (3.4.0+dfsg-1 to 3.4.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastlink/amd64 (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5)
  • Migration status for fastlink/amd64 (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastlink/arm64 (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5)
  • Migration status for fastlink/arm64 (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastlink/armhf (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5)
  • Migration status for fastlink/armhf (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastlink/i386 (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5)
  • Migration status for fastlink/i386 (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastlink/ppc64el (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5)
  • Migration status for fastlink/ppc64el (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastlink/riscv64 (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5)
  • Migration status for fastlink/riscv64 (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fastlink/s390x (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5)
  • Migration status for fastlink/s390x (4.1P-fix100+dfsg-5 to 4.1P-fix100+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• filter/amd64 (2.6.3+ds1-5 to 2.6.3+ds1-5)
  • Migration status for filter/amd64 (2.6.3+ds1-5 to 2.6.3+ds1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• filter/arm64 (2.6.3+ds1-5 to 2.6.3+ds1-5)
  • Migration status for filter/arm64 (2.6.3+ds1-5 to 2.6.3+ds1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• filter/armhf (2.6.3+ds1-5 to 2.6.3+ds1-5)
  • Migration status for filter/armhf (2.6.3+ds1-5 to 2.6.3+ds1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• filter/i386 (2.6.3+ds1-5 to 2.6.3+ds1-5)
  • Migration status for filter/i386 (2.6.3+ds1-5 to 2.6.3+ds1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• filter/ppc64el (2.6.3+ds1-5 to 2.6.3+ds1-5)
  • Migration status for filter/ppc64el (2.6.3+ds1-5 to 2.6.3+ds1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• filter/riscv64 (2.6.3+ds1-5 to 2.6.3+ds1-5)
  • Migration status for filter/riscv64 (2.6.3+ds1-5 to 2.6.3+ds1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• filter/s390x (2.6.3+ds1-5 to 2.6.3+ds1-5)
  • Migration status for filter/s390x (2.6.3+ds1-5 to 2.6.3+ds1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fis-gtm/amd64 (7.1-006-1 to 7.1-006-1)
  • Migration status for fis-gtm/amd64 (7.1-006-1 to 7.1-006-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fis-gtm/arm64 (7.1-006-1 to 7.1-006-1)
  • Migration status for fis-gtm/arm64 (7.1-006-1 to 7.1-006-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fis-gtm/armhf (7.1-006-1 to 7.1-006-1)
  • Migration status for fis-gtm/armhf (7.1-006-1 to 7.1-006-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fis-gtm/i386 (7.1-006-1 to 7.1-006-1)
  • Migration status for fis-gtm/i386 (7.1-006-1 to 7.1-006-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fis-gtm/ppc64el (7.1-006-1 to 7.1-006-1)
  • Migration status for fis-gtm/ppc64el (7.1-006-1 to 7.1-006-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fis-gtm/riscv64 (7.1-006-1 to 7.1-006-1)
  • Migration status for fis-gtm/riscv64 (7.1-006-1 to 7.1-006-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fis-gtm/s390x (7.1-006-1 to 7.1-006-1)
  • Migration status for fis-gtm/s390x (7.1-006-1 to 7.1-006-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• flightgear/amd64 (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1)
  • Migration status for flightgear/amd64 (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• flightgear/arm64 (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1)
  • Migration status for flightgear/arm64 (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• flightgear/armhf (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1)
  • Migration status for flightgear/armhf (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• flightgear/i386 (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1)
  • Migration status for flightgear/i386 (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• flightgear/ppc64el (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1)
  • Migration status for flightgear/ppc64el (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• flightgear/riscv64 (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1)
  • Migration status for flightgear/riscv64 (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• flightgear/s390x (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1)
  • Migration status for flightgear/s390x (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• floatbg/amd64 (1.0-28.3 to 1.0-28.3)
  • Migration status for floatbg/amd64 (1.0-28.3 to 1.0-28.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• floatbg/arm64 (1.0-28.3 to 1.0-28.3)
  • Migration status for floatbg/arm64 (1.0-28.3 to 1.0-28.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• floatbg/armhf (1.0-28.3 to 1.0-28.3)
  • Migration status for floatbg/armhf (1.0-28.3 to 1.0-28.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• floatbg/i386 (1.0-28.3 to 1.0-28.3)
  • Migration status for floatbg/i386 (1.0-28.3 to 1.0-28.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• floatbg/ppc64el (1.0-28.3 to 1.0-28.3)
  • Migration status for floatbg/ppc64el (1.0-28.3 to 1.0-28.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• floatbg/riscv64 (1.0-28.3 to 1.0-28.3)
  • Migration status for floatbg/riscv64 (1.0-28.3 to 1.0-28.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• floatbg/s390x (1.0-28.3 to 1.0-28.3)
  • Migration status for floatbg/s390x (1.0-28.3 to 1.0-28.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• freegish/amd64 (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2)
  • Migration status for freegish/amd64 (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• freegish/arm64 (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2)
  • Migration status for freegish/arm64 (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• freegish/armhf (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2)
  • Migration status for freegish/armhf (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• freegish/i386 (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2)
  • Migration status for freegish/i386 (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• freegish/ppc64el (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2)
  • Migration status for freegish/ppc64el (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• freegish/s390x (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2)
  • Migration status for freegish/s390x (1.53+git20170110+dfsg-2 to 1.53+git20170110+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fspy/amd64 (0.1.1-4 to 0.1.1-4)
  • Migration status for fspy/amd64 (0.1.1-4 to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fspy/arm64 (0.1.1-4 to 0.1.1-4)
  • Migration status for fspy/arm64 (0.1.1-4 to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fspy/armhf (0.1.1-4 to 0.1.1-4)
  • Migration status for fspy/armhf (0.1.1-4 to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fspy/i386 (0.1.1-4 to 0.1.1-4)
  • Migration status for fspy/i386 (0.1.1-4 to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fspy/ppc64el (0.1.1-4 to 0.1.1-4)
  • Migration status for fspy/ppc64el (0.1.1-4 to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fspy/riscv64 (0.1.1-4 to 0.1.1-4)
  • Migration status for fspy/riscv64 (0.1.1-4 to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• fspy/s390x (0.1.1-4 to 0.1.1-4)
  • Migration status for fspy/s390x (0.1.1-4 to 0.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ftpmirror/amd64 (1.96+dfsg-16.1 to 1.96+dfsg-16.1)
  • Migration status for ftpmirror/amd64 (1.96+dfsg-16.1 to 1.96+dfsg-16.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ftpmirror/arm64 (1.96+dfsg-16.1 to 1.96+dfsg-16.1)
  • Migration status for ftpmirror/arm64 (1.96+dfsg-16.1 to 1.96+dfsg-16.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ftpmirror/armhf (1.96+dfsg-16.1 to 1.96+dfsg-16.1)
  • Migration status for ftpmirror/armhf (1.96+dfsg-16.1 to 1.96+dfsg-16.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ftpmirror/i386 (1.96+dfsg-16.1 to 1.96+dfsg-16.1)
  • Migration status for ftpmirror/i386 (1.96+dfsg-16.1 to 1.96+dfsg-16.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ftpmirror/ppc64el (1.96+dfsg-16.1 to 1.96+dfsg-16.1)
  • Migration status for ftpmirror/ppc64el (1.96+dfsg-16.1 to 1.96+dfsg-16.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ftpmirror/riscv64 (1.96+dfsg-16.1 to 1.96+dfsg-16.1)
  • Migration status for ftpmirror/riscv64 (1.96+dfsg-16.1 to 1.96+dfsg-16.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ftpmirror/s390x (1.96+dfsg-16.1 to 1.96+dfsg-16.1)
  • Migration status for ftpmirror/s390x (1.96+dfsg-16.1 to 1.96+dfsg-16.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gatk-bwamem/amd64 (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3)
  • Migration status for gatk-bwamem/amd64 (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gatk-bwamem/arm64 (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3)
  • Migration status for gatk-bwamem/arm64 (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gatk-bwamem/armhf (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3)
  • Migration status for gatk-bwamem/armhf (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gatk-bwamem/i386 (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3)
  • Migration status for gatk-bwamem/i386 (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gatk-bwamem/ppc64el (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3)
  • Migration status for gatk-bwamem/ppc64el (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gatk-bwamem/riscv64 (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3)
  • Migration status for gatk-bwamem/riscv64 (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gatk-bwamem/s390x (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3)
  • Migration status for gatk-bwamem/s390x (1.0.4+dfsg2-3 to 1.0.4+dfsg2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gcin/amd64 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3)
  • Migration status for gcin/amd64 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gcin/arm64 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3)
  • Migration status for gcin/arm64 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gcin/armhf (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3)
  • Migration status for gcin/armhf (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gcin/i386 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3)
  • Migration status for gcin/i386 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gcin/ppc64el (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3)
  • Migration status for gcin/ppc64el (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gcin/riscv64 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3)
  • Migration status for gcin/riscv64 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gcin/s390x (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3)
  • Migration status for gcin/s390x (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• genparse/amd64 (0.9.3-2 to 0.9.3-2)
  • Migration status for genparse/amd64 (0.9.3-2 to 0.9.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
• genparse/arm64 (0.9.3-2 to 0.9.3-2)
  • Migration status for genparse/arm64 (0.9.3-2 to 0.9.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
• genparse/armhf (0.9.3-2 to 0.9.3-2)
  • Migration status for genparse/armhf (0.9.3-2 to 0.9.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
• genparse/i386 (0.9.3-2 to 0.9.3-2)
  • Migration status for genparse/i386 (0.9.3-2 to 0.9.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
• genparse/ppc64el (0.9.3-2 to 0.9.3-2)
  • Migration status for genparse/ppc64el (0.9.3-2 to 0.9.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
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• genparse/s390x (0.9.3-2 to 0.9.3-2)
  • Migration status for genparse/s390x (0.9.3-2 to 0.9.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
• geomview/amd64 (1.9.5-5 to 1.9.5-5)
  • Migration status for geomview/amd64 (1.9.5-5 to 1.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• geomview/arm64 (1.9.5-5 to 1.9.5-5)
  • Migration status for geomview/arm64 (1.9.5-5 to 1.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• geomview/armhf (1.9.5-5 to 1.9.5-5)
  • Migration status for geomview/armhf (1.9.5-5 to 1.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• geomview/i386 (1.9.5-5 to 1.9.5-5)
  • Migration status for geomview/i386 (1.9.5-5 to 1.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• geomview/ppc64el (1.9.5-5 to 1.9.5-5)
  • Migration status for geomview/ppc64el (1.9.5-5 to 1.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• geomview/riscv64 (1.9.5-5 to 1.9.5-5)
  • Migration status for geomview/riscv64 (1.9.5-5 to 1.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• geomview/s390x (1.9.5-5 to 1.9.5-5)
  • Migration status for geomview/s390x (1.9.5-5 to 1.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gfarm2fs/amd64 (1.2.16-1 to 1.2.16-1)
  • Migration status for gfarm2fs/amd64 (1.2.16-1 to 1.2.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gfarm2fs/arm64 (1.2.16-1 to 1.2.16-1)
  • Migration status for gfarm2fs/arm64 (1.2.16-1 to 1.2.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gfarm2fs/armhf (1.2.16-1 to 1.2.16-1)
  • Migration status for gfarm2fs/armhf (1.2.16-1 to 1.2.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gfarm2fs/i386 (1.2.16-1 to 1.2.16-1)
  • Migration status for gfarm2fs/i386 (1.2.16-1 to 1.2.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gfarm2fs/ppc64el (1.2.16-1 to 1.2.16-1)
  • Migration status for gfarm2fs/ppc64el (1.2.16-1 to 1.2.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gfarm2fs/s390x (1.2.16-1 to 1.2.16-1)
  • Migration status for gfarm2fs/s390x (1.2.16-1 to 1.2.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gftp/amd64 (2.9.1~beta-4 to 2.9.1~beta-4)
  • Migration status for gftp/amd64 (2.9.1~beta-4 to 2.9.1~beta-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gftp/arm64 (2.9.1~beta-4 to 2.9.1~beta-4)
  • Migration status for gftp/arm64 (2.9.1~beta-4 to 2.9.1~beta-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gftp/armhf (2.9.1~beta-4 to 2.9.1~beta-4)
  • Migration status for gftp/armhf (2.9.1~beta-4 to 2.9.1~beta-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gftp/i386 (2.9.1~beta-4 to 2.9.1~beta-4)
  • Migration status for gftp/i386 (2.9.1~beta-4 to 2.9.1~beta-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gftp/ppc64el (2.9.1~beta-4 to 2.9.1~beta-4)
  • Migration status for gftp/ppc64el (2.9.1~beta-4 to 2.9.1~beta-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gftp/riscv64 (2.9.1~beta-4 to 2.9.1~beta-4)
  • Migration status for gftp/riscv64 (2.9.1~beta-4 to 2.9.1~beta-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gftp/s390x (2.9.1~beta-4 to 2.9.1~beta-4)
  • Migration status for gftp/s390x (2.9.1~beta-4 to 2.9.1~beta-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-thinkbat/amd64 (0.2.3-1 to 0.2.3-1)
  • Migration status for gkrellm-thinkbat/amd64 (0.2.3-1 to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-thinkbat/arm64 (0.2.3-1 to 0.2.3-1)
  • Migration status for gkrellm-thinkbat/arm64 (0.2.3-1 to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-thinkbat/armhf (0.2.3-1 to 0.2.3-1)
  • Migration status for gkrellm-thinkbat/armhf (0.2.3-1 to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-thinkbat/i386 (0.2.3-1 to 0.2.3-1)
  • Migration status for gkrellm-thinkbat/i386 (0.2.3-1 to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-thinkbat/ppc64el (0.2.3-1 to 0.2.3-1)
  • Migration status for gkrellm-thinkbat/ppc64el (0.2.3-1 to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-thinkbat/riscv64 (0.2.3-1 to 0.2.3-1)
  • Migration status for gkrellm-thinkbat/riscv64 (0.2.3-1 to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-thinkbat/s390x (0.2.3-1 to 0.2.3-1)
  • Migration status for gkrellm-thinkbat/s390x (0.2.3-1 to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-xkb/amd64 (1.05-7 to 1.05-7)
  • Migration status for gkrellm-xkb/amd64 (1.05-7 to 1.05-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-xkb/arm64 (1.05-7 to 1.05-7)
  • Migration status for gkrellm-xkb/arm64 (1.05-7 to 1.05-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-xkb/armhf (1.05-7 to 1.05-7)
  • Migration status for gkrellm-xkb/armhf (1.05-7 to 1.05-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-xkb/i386 (1.05-7 to 1.05-7)
  • Migration status for gkrellm-xkb/i386 (1.05-7 to 1.05-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-xkb/ppc64el (1.05-7 to 1.05-7)
  • Migration status for gkrellm-xkb/ppc64el (1.05-7 to 1.05-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-xkb/riscv64 (1.05-7 to 1.05-7)
  • Migration status for gkrellm-xkb/riscv64 (1.05-7 to 1.05-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellm-xkb/s390x (1.05-7 to 1.05-7)
  • Migration status for gkrellm-xkb/s390x (1.05-7 to 1.05-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellmoon/amd64 (0.6-7.1 to 0.6-7.1)
  • Migration status for gkrellmoon/amd64 (0.6-7.1 to 0.6-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellmoon/arm64 (0.6-7.1 to 0.6-7.1)
  • Migration status for gkrellmoon/arm64 (0.6-7.1 to 0.6-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellmoon/armhf (0.6-7.1 to 0.6-7.1)
  • Migration status for gkrellmoon/armhf (0.6-7.1 to 0.6-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellmoon/i386 (0.6-7.1 to 0.6-7.1)
  • Migration status for gkrellmoon/i386 (0.6-7.1 to 0.6-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellmoon/ppc64el (0.6-7.1 to 0.6-7.1)
  • Migration status for gkrellmoon/ppc64el (0.6-7.1 to 0.6-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellmoon/riscv64 (0.6-7.1 to 0.6-7.1)
  • Migration status for gkrellmoon/riscv64 (0.6-7.1 to 0.6-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrellmoon/s390x (0.6-7.1 to 0.6-7.1)
  • Migration status for gkrellmoon/s390x (0.6-7.1 to 0.6-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrelluim/amd64 (0.3.2-2 to 0.3.2-2)
  • Migration status for gkrelluim/amd64 (0.3.2-2 to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrelluim/arm64 (0.3.2-2 to 0.3.2-2)
  • Migration status for gkrelluim/arm64 (0.3.2-2 to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrelluim/armhf (0.3.2-2 to 0.3.2-2)
  • Migration status for gkrelluim/armhf (0.3.2-2 to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrelluim/i386 (0.3.2-2 to 0.3.2-2)
  • Migration status for gkrelluim/i386 (0.3.2-2 to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrelluim/ppc64el (0.3.2-2 to 0.3.2-2)
  • Migration status for gkrelluim/ppc64el (0.3.2-2 to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gkrelluim/s390x (0.3.2-2 to 0.3.2-2)
  • Migration status for gkrelluim/s390x (0.3.2-2 to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• glhack/amd64 (1.2-8 to 1.2-8)
  • Migration status for glhack/amd64 (1.2-8 to 1.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• glhack/arm64 (1.2-8 to 1.2-8)
  • Migration status for glhack/arm64 (1.2-8 to 1.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• glhack/armhf (1.2-8 to 1.2-8)
  • Migration status for glhack/armhf (1.2-8 to 1.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• glhack/i386 (1.2-8 to 1.2-8)
  • Migration status for glhack/i386 (1.2-8 to 1.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• glhack/ppc64el (1.2-8 to 1.2-8)
  • Migration status for glhack/ppc64el (1.2-8 to 1.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• glhack/riscv64 (1.2-8 to 1.2-8)
  • Migration status for glhack/riscv64 (1.2-8 to 1.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• glhack/s390x (1.2-8 to 1.2-8)
  • Migration status for glhack/s390x (1.2-8 to 1.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• global/amd64 (6.6.14-1 to 6.6.14-1)
  • Migration status for global/amd64 (6.6.14-1 to 6.6.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• global/arm64 (6.6.14-1 to 6.6.14-1)
  • Migration status for global/arm64 (6.6.14-1 to 6.6.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• global/armhf (6.6.14-1 to 6.6.14-1)
  • Migration status for global/armhf (6.6.14-1 to 6.6.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• global/i386 (6.6.14-1 to 6.6.14-1)
  • Migration status for global/i386 (6.6.14-1 to 6.6.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• global/ppc64el (6.6.14-1 to 6.6.14-1)
  • Migration status for global/ppc64el (6.6.14-1 to 6.6.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• global/riscv64 (6.6.14-1 to 6.6.14-1)
  • Migration status for global/riscv64 (6.6.14-1 to 6.6.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• global/s390x (6.6.14-1 to 6.6.14-1)
  • Migration status for global/s390x (6.6.14-1 to 6.6.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gmtp/amd64 (1.3.11-3.1 to 1.3.11-3.1)
  • Migration status for gmtp/amd64 (1.3.11-3.1 to 1.3.11-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gmtp/arm64 (1.3.11-3.1 to 1.3.11-3.1)
  • Migration status for gmtp/arm64 (1.3.11-3.1 to 1.3.11-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gmtp/armhf (1.3.11-3.1 to 1.3.11-3.1)
  • Migration status for gmtp/armhf (1.3.11-3.1 to 1.3.11-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gmtp/i386 (1.3.11-3.1 to 1.3.11-3.1)
  • Migration status for gmtp/i386 (1.3.11-3.1 to 1.3.11-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gmtp/ppc64el (1.3.11-3.1 to 1.3.11-3.1)
  • Migration status for gmtp/ppc64el (1.3.11-3.1 to 1.3.11-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gmtp/s390x (1.3.11-3.1 to 1.3.11-3.1)
  • Migration status for gmtp/s390x (1.3.11-3.1 to 1.3.11-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnucobol4/amd64 (4.0~early~20200606-7 to 4.0~early~20200606-7)
  • Migration status for gnucobol4/amd64 (4.0~early~20200606-7 to 4.0~early~20200606-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnucobol4/arm64 (4.0~early~20200606-7 to 4.0~early~20200606-7)
  • Migration status for gnucobol4/arm64 (4.0~early~20200606-7 to 4.0~early~20200606-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnucobol4/armhf (4.0~early~20200606-7 to 4.0~early~20200606-7)
  • Migration status for gnucobol4/armhf (4.0~early~20200606-7 to 4.0~early~20200606-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnucobol4/i386 (4.0~early~20200606-7 to 4.0~early~20200606-7)
  • Migration status for gnucobol4/i386 (4.0~early~20200606-7 to 4.0~early~20200606-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnucobol4/ppc64el (4.0~early~20200606-7 to 4.0~early~20200606-7)
  • Migration status for gnucobol4/ppc64el (4.0~early~20200606-7 to 4.0~early~20200606-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnucobol4/riscv64 (4.0~early~20200606-7 to 4.0~early~20200606-7)
  • Migration status for gnucobol4/riscv64 (4.0~early~20200606-7 to 4.0~early~20200606-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnucobol4/s390x (4.0~early~20200606-7 to 4.0~early~20200606-7)
  • Migration status for gnucobol4/s390x (4.0~early~20200606-7 to 4.0~early~20200606-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnuit/amd64 (4.9.5-5 to 4.9.5-5)
  • Migration status for gnuit/amd64 (4.9.5-5 to 4.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnuit/arm64 (4.9.5-5 to 4.9.5-5)
  • Migration status for gnuit/arm64 (4.9.5-5 to 4.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnuit/armhf (4.9.5-5 to 4.9.5-5)
  • Migration status for gnuit/armhf (4.9.5-5 to 4.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnuit/i386 (4.9.5-5 to 4.9.5-5)
  • Migration status for gnuit/i386 (4.9.5-5 to 4.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnuit/ppc64el (4.9.5-5 to 4.9.5-5)
  • Migration status for gnuit/ppc64el (4.9.5-5 to 4.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnuit/riscv64 (4.9.5-5 to 4.9.5-5)
  • Migration status for gnuit/riscv64 (4.9.5-5 to 4.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnuit/s390x (4.9.5-5 to 4.9.5-5)
  • Migration status for gnuit/s390x (4.9.5-5 to 4.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnujump/amd64 (1.0.8-5 to 1.0.8-5)
  • Migration status for gnujump/amd64 (1.0.8-5 to 1.0.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnujump/arm64 (1.0.8-5 to 1.0.8-5)
  • Migration status for gnujump/arm64 (1.0.8-5 to 1.0.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnujump/armhf (1.0.8-5 to 1.0.8-5)
  • Migration status for gnujump/armhf (1.0.8-5 to 1.0.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnujump/i386 (1.0.8-5 to 1.0.8-5)
  • Migration status for gnujump/i386 (1.0.8-5 to 1.0.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnujump/ppc64el (1.0.8-5 to 1.0.8-5)
  • Migration status for gnujump/ppc64el (1.0.8-5 to 1.0.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnujump/riscv64 (1.0.8-5 to 1.0.8-5)
  • Migration status for gnujump/riscv64 (1.0.8-5 to 1.0.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gnujump/s390x (1.0.8-5 to 1.0.8-5)
  • Migration status for gnujump/s390x (1.0.8-5 to 1.0.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gopher/amd64 (3.0.19 to 3.0.19)
  • Migration status for gopher/amd64 (3.0.19 to 3.0.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gopher/arm64 (3.0.19 to 3.0.19)
  • Migration status for gopher/arm64 (3.0.19 to 3.0.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gopher/armhf (3.0.19 to 3.0.19)
  • Migration status for gopher/armhf (3.0.19 to 3.0.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gopher/i386 (3.0.19 to 3.0.19)
  • Migration status for gopher/i386 (3.0.19 to 3.0.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gopher/ppc64el (3.0.19 to 3.0.19)
  • Migration status for gopher/ppc64el (3.0.19 to 3.0.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gopher/riscv64 (3.0.19 to 3.0.19)
  • Migration status for gopher/riscv64 (3.0.19 to 3.0.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gopher/s390x (3.0.19 to 3.0.19)
  • Migration status for gopher/s390x (3.0.19 to 3.0.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gprolog/amd64 (1.4.5.0-3 to 1.4.5.0-3)
  • Migration status for gprolog/amd64 (1.4.5.0-3 to 1.4.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gprolog/arm64 (1.4.5.0-3 to 1.4.5.0-3)
  • Migration status for gprolog/arm64 (1.4.5.0-3 to 1.4.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gprolog/armhf (1.4.5.0-3 to 1.4.5.0-3)
  • Migration status for gprolog/armhf (1.4.5.0-3 to 1.4.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gprolog/i386 (1.4.5.0-3 to 1.4.5.0-3)
  • Migration status for gprolog/i386 (1.4.5.0-3 to 1.4.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gprolog/ppc64el (1.4.5.0-3 to 1.4.5.0-3)
  • Migration status for gprolog/ppc64el (1.4.5.0-3 to 1.4.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gprolog/riscv64 (1.4.5.0-3 to 1.4.5.0-3)
  • Migration status for gprolog/riscv64 (1.4.5.0-3 to 1.4.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gprolog/s390x (1.4.5.0-3 to 1.4.5.0-3)
  • Migration status for gprolog/s390x (1.4.5.0-3 to 1.4.5.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gpstrans/amd64 (0.41-11 to 0.41-11)
  • Migration status for gpstrans/amd64 (0.41-11 to 0.41-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gpstrans/arm64 (0.41-11 to 0.41-11)
  • Migration status for gpstrans/arm64 (0.41-11 to 0.41-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gpstrans/armhf (0.41-11 to 0.41-11)
  • Migration status for gpstrans/armhf (0.41-11 to 0.41-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gpstrans/i386 (0.41-11 to 0.41-11)
  • Migration status for gpstrans/i386 (0.41-11 to 0.41-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gpstrans/ppc64el (0.41-11 to 0.41-11)
  • Migration status for gpstrans/ppc64el (0.41-11 to 0.41-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gpstrans/riscv64 (0.41-11 to 0.41-11)
  • Migration status for gpstrans/riscv64 (0.41-11 to 0.41-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gpstrans/s390x (0.41-11 to 0.41-11)
  • Migration status for gpstrans/s390x (0.41-11 to 0.41-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-dab/amd64 (0.5-1 to 0.5-1)
  • Migration status for gr-dab/amd64 (0.5-1 to 0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-dab/arm64 (0.5-1 to 0.5-1)
  • Migration status for gr-dab/arm64 (0.5-1 to 0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-dab/armhf (0.5-1 to 0.5-1)
  • Migration status for gr-dab/armhf (0.5-1 to 0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-dab/i386 (0.5-1 to 0.5-1)
  • Migration status for gr-dab/i386 (0.5-1 to 0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-dab/ppc64el (0.5-1 to 0.5-1)
  • Migration status for gr-dab/ppc64el (0.5-1 to 0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-dab/riscv64 (0.5-1 to 0.5-1)
  • Migration status for gr-dab/riscv64 (0.5-1 to 0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-dab/s390x (0.5-1 to 0.5-1)
  • Migration status for gr-dab/s390x (0.5-1 to 0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-gsm/amd64 (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/amd64 (1.0.0~20220727-1 to 1.0.0~20220727-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-gsm/arm64 (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/arm64 (1.0.0~20220727-1 to 1.0.0~20220727-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-gsm/armhf (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/armhf (1.0.0~20220727-1 to 1.0.0~20220727-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-gsm/i386 (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/i386 (1.0.0~20220727-1 to 1.0.0~20220727-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-gsm/ppc64el (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/ppc64el (1.0.0~20220727-1 to 1.0.0~20220727-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gr-gsm/s390x (1.0.0~20220727-1 to 1.0.0~20220727-1)
  • Migration status for gr-gsm/s390x (1.0.0~20220727-1 to 1.0.0~20220727-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gramophone2/amd64 (0.8.13a-3.6 to 0.8.13a-3.6)
  • Migration status for gramophone2/amd64 (0.8.13a-3.6 to 0.8.13a-3.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gramophone2/arm64 (0.8.13a-3.6 to 0.8.13a-3.6)
  • Migration status for gramophone2/arm64 (0.8.13a-3.6 to 0.8.13a-3.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gramophone2/armhf (0.8.13a-3.6 to 0.8.13a-3.6)
  • Migration status for gramophone2/armhf (0.8.13a-3.6 to 0.8.13a-3.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gramophone2/i386 (0.8.13a-3.6 to 0.8.13a-3.6)
  • Migration status for gramophone2/i386 (0.8.13a-3.6 to 0.8.13a-3.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gramophone2/ppc64el (0.8.13a-3.6 to 0.8.13a-3.6)
  • Migration status for gramophone2/ppc64el (0.8.13a-3.6 to 0.8.13a-3.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gramophone2/riscv64 (0.8.13a-3.6 to 0.8.13a-3.6)
  • Migration status for gramophone2/riscv64 (0.8.13a-3.6 to 0.8.13a-3.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• gramophone2/s390x (0.8.13a-3.6 to 0.8.13a-3.6)
  • Migration status for gramophone2/s390x (0.8.13a-3.6 to 0.8.13a-3.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• grdesktop/amd64 (0.23+d040330-8 to 0.23+d040330-8)
  • Migration status for grdesktop/amd64 (0.23+d040330-8 to 0.23+d040330-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• grdesktop/arm64 (0.23+d040330-8 to 0.23+d040330-8)
  • Migration status for grdesktop/arm64 (0.23+d040330-8 to 0.23+d040330-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• grdesktop/armhf (0.23+d040330-8 to 0.23+d040330-8)
  • Migration status for grdesktop/armhf (0.23+d040330-8 to 0.23+d040330-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• grdesktop/i386 (0.23+d040330-8 to 0.23+d040330-8)
  • Migration status for grdesktop/i386 (0.23+d040330-8 to 0.23+d040330-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• grdesktop/ppc64el (0.23+d040330-8 to 0.23+d040330-8)
  • Migration status for grdesktop/ppc64el (0.23+d040330-8 to 0.23+d040330-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• grdesktop/s390x (0.23+d040330-8 to 0.23+d040330-8)
  • Migration status for grdesktop/s390x (0.23+d040330-8 to 0.23+d040330-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• halide/amd64 (19.0.0-6 to 19.0.0-6)
  • Migration status for halide/amd64 (19.0.0-6 to 19.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• halide/arm64 (19.0.0-6 to 19.0.0-6)
  • Migration status for halide/arm64 (19.0.0-6 to 19.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• halide/armhf (19.0.0-6 to 19.0.0-6)
  • Migration status for halide/armhf (19.0.0-6 to 19.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• halide/i386 (19.0.0-6 to 19.0.0-6)
  • Migration status for halide/i386 (19.0.0-6 to 19.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• halide/ppc64el (19.0.0-6 to 19.0.0-6)
  • Migration status for halide/ppc64el (19.0.0-6 to 19.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• halide/riscv64 (19.0.0-6 to 19.0.0-6)
  • Migration status for halide/riscv64 (19.0.0-6 to 19.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• halide/s390x (19.0.0-6 to 19.0.0-6)
  • Migration status for halide/s390x (19.0.0-6 to 19.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-system-fileio/amd64 (0.3.16.4-6 to 0.3.16.4-6)
  • Migration status for haskell-system-fileio/amd64 (0.3.16.4-6 to 0.3.16.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-system-fileio/arm64 (0.3.16.4-6 to 0.3.16.4-6)
  • Migration status for haskell-system-fileio/arm64 (0.3.16.4-6 to 0.3.16.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-system-fileio/armhf (0.3.16.4-6 to 0.3.16.4-6)
  • Migration status for haskell-system-fileio/armhf (0.3.16.4-6 to 0.3.16.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-system-fileio/i386 (0.3.16.4-6 to 0.3.16.4-6)
  • Migration status for haskell-system-fileio/i386 (0.3.16.4-6 to 0.3.16.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-system-fileio/ppc64el (0.3.16.4-6 to 0.3.16.4-6)
  • Migration status for haskell-system-fileio/ppc64el (0.3.16.4-6 to 0.3.16.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-system-fileio/riscv64 (0.3.16.4-6 to 0.3.16.4-6)
  • Migration status for haskell-system-fileio/riscv64 (0.3.16.4-6 to 0.3.16.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• haskell-system-fileio/s390x (0.3.16.4-6 to 0.3.16.4-6)
  • Migration status for haskell-system-fileio/s390x (0.3.16.4-6 to 0.3.16.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hime/amd64 (0.9.11+dfsg-4 to 0.9.11+dfsg-4)
  • Migration status for hime/amd64 (0.9.11+dfsg-4 to 0.9.11+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hime/arm64 (0.9.11+dfsg-4 to 0.9.11+dfsg-4)
  • Migration status for hime/arm64 (0.9.11+dfsg-4 to 0.9.11+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hime/armhf (0.9.11+dfsg-4 to 0.9.11+dfsg-4)
  • Migration status for hime/armhf (0.9.11+dfsg-4 to 0.9.11+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hime/i386 (0.9.11+dfsg-4 to 0.9.11+dfsg-4)
  • Migration status for hime/i386 (0.9.11+dfsg-4 to 0.9.11+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hime/ppc64el (0.9.11+dfsg-4 to 0.9.11+dfsg-4)
  • Migration status for hime/ppc64el (0.9.11+dfsg-4 to 0.9.11+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hime/s390x (0.9.11+dfsg-4 to 0.9.11+dfsg-4)
  • Migration status for hime/s390x (0.9.11+dfsg-4 to 0.9.11+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hipsolver/amd64 (5.5.1-8 to 5.5.1-8)
  • Migration status for hipsolver/amd64 (5.5.1-8 to 5.5.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hipsolver/arm64 (5.5.1-8 to 5.5.1-8)
  • Migration status for hipsolver/arm64 (5.5.1-8 to 5.5.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hipsolver/armhf (5.5.1-8 to 5.5.1-8)
  • Migration status for hipsolver/armhf (5.5.1-8 to 5.5.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hipsolver/i386 (5.5.1-8 to 5.5.1-8)
  • Migration status for hipsolver/i386 (5.5.1-8 to 5.5.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hipsolver/ppc64el (5.5.1-8 to 5.5.1-8)
  • Migration status for hipsolver/ppc64el (5.5.1-8 to 5.5.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hipsolver/riscv64 (5.5.1-8 to 5.5.1-8)
  • Migration status for hipsolver/riscv64 (5.5.1-8 to 5.5.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hipsolver/s390x (5.5.1-8 to 5.5.1-8)
  • Migration status for hipsolver/s390x (5.5.1-8 to 5.5.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• hsqldb1.8.0_pu (1.8.0.10+dfsg-14 to 1.8.0.10+dfsg-12.1+deb13u1)
  • Migration status for hsqldb1.8.0_pu (1.8.0.10+dfsg-14 to 1.8.0.10+dfsg-12.1+deb13u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: hsqldb1.8.0 is newer in the target suite (1.8.0.10+dfsg-14 1.8.0.10+dfsg-12.1+deb13u1)
• ht/amd64 (2.1.0+repack1-5 to 2.1.0+repack1-5)
  • Migration status for ht/amd64 (2.1.0+repack1-5 to 2.1.0+repack1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ht/arm64 (2.1.0+repack1-5 to 2.1.0+repack1-5)
  • Migration status for ht/arm64 (2.1.0+repack1-5 to 2.1.0+repack1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ht/armhf (2.1.0+repack1-5 to 2.1.0+repack1-5)
  • Migration status for ht/armhf (2.1.0+repack1-5 to 2.1.0+repack1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ht/i386 (2.1.0+repack1-5 to 2.1.0+repack1-5)
  • Migration status for ht/i386 (2.1.0+repack1-5 to 2.1.0+repack1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ht/ppc64el (2.1.0+repack1-5 to 2.1.0+repack1-5)
  • Migration status for ht/ppc64el (2.1.0+repack1-5 to 2.1.0+repack1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ht/s390x (2.1.0+repack1-5 to 2.1.0+repack1-5)
  • Migration status for ht/s390x (2.1.0+repack1-5 to 2.1.0+repack1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifcplusplus/amd64 (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4)
  • Migration status for ifcplusplus/amd64 (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifcplusplus/arm64 (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4)
  • Migration status for ifcplusplus/arm64 (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifcplusplus/armhf (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4)
  • Migration status for ifcplusplus/armhf (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifcplusplus/i386 (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4)
  • Migration status for ifcplusplus/i386 (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifcplusplus/ppc64el (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4)
  • Migration status for ifcplusplus/ppc64el (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifcplusplus/s390x (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4)
  • Migration status for ifcplusplus/s390x (0~git20190402.13744d5+dfsg-4 to 0~git20190402.13744d5+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifhp/amd64 (3.5.20-20 to 3.5.20-20)
  • Migration status for ifhp/amd64 (3.5.20-20 to 3.5.20-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifhp/arm64 (3.5.20-20 to 3.5.20-20)
  • Migration status for ifhp/arm64 (3.5.20-20 to 3.5.20-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifhp/armhf (3.5.20-20 to 3.5.20-20)
  • Migration status for ifhp/armhf (3.5.20-20 to 3.5.20-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifhp/i386 (3.5.20-20 to 3.5.20-20)
  • Migration status for ifhp/i386 (3.5.20-20 to 3.5.20-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifhp/ppc64el (3.5.20-20 to 3.5.20-20)
  • Migration status for ifhp/ppc64el (3.5.20-20 to 3.5.20-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifhp/s390x (3.5.20-20 to 3.5.20-20)
  • Migration status for ifhp/s390x (3.5.20-20 to 3.5.20-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifile/amd64 (1.3.9-9 to 1.3.9-9)
  • Migration status for ifile/amd64 (1.3.9-9 to 1.3.9-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifile/arm64 (1.3.9-9 to 1.3.9-9)
  • Migration status for ifile/arm64 (1.3.9-9 to 1.3.9-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifile/armhf (1.3.9-9 to 1.3.9-9)
  • Migration status for ifile/armhf (1.3.9-9 to 1.3.9-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifile/i386 (1.3.9-9 to 1.3.9-9)
  • Migration status for ifile/i386 (1.3.9-9 to 1.3.9-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifile/ppc64el (1.3.9-9 to 1.3.9-9)
  • Migration status for ifile/ppc64el (1.3.9-9 to 1.3.9-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifile/riscv64 (1.3.9-9 to 1.3.9-9)
  • Migration status for ifile/riscv64 (1.3.9-9 to 1.3.9-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ifile/s390x (1.3.9-9 to 1.3.9-9)
  • Migration status for ifile/s390x (1.3.9-9 to 1.3.9-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• imagemagick_pu (8:7.1.2.3+dfsg1-1 to 8:7.1.1.43+dfsg1-1+deb13u2)
  • Migration status for imagemagick_pu (8:7.1.2.3+dfsg1-1 to 8:7.1.1.43+dfsg1-1+deb13u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: imagemagick is newer in the target suite (8:7.1.2.3+dfsg1-1 8:7.1.1.43+dfsg1-1+deb13u2)
• indi-eqmod/amd64 (1.0+20230126190232-2 to 1.0+20230126190232-2)
  • Migration status for indi-eqmod/amd64 (1.0+20230126190232-2 to 1.0+20230126190232-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• indi-eqmod/arm64 (1.0+20230126190232-2 to 1.0+20230126190232-2)
  • Migration status for indi-eqmod/arm64 (1.0+20230126190232-2 to 1.0+20230126190232-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• indi-eqmod/armhf (1.0+20230126190232-2 to 1.0+20230126190232-2)
  • Migration status for indi-eqmod/armhf (1.0+20230126190232-2 to 1.0+20230126190232-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• indi-eqmod/i386 (1.0+20230126190232-2 to 1.0+20230126190232-2)
  • Migration status for indi-eqmod/i386 (1.0+20230126190232-2 to 1.0+20230126190232-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• indi-eqmod/ppc64el (1.0+20230126190232-2 to 1.0+20230126190232-2)
  • Migration status for indi-eqmod/ppc64el (1.0+20230126190232-2 to 1.0+20230126190232-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• indi-eqmod/riscv64 (1.0+20230126190232-2 to 1.0+20230126190232-2)
  • Migration status for indi-eqmod/riscv64 (1.0+20230126190232-2 to 1.0+20230126190232-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• indi-eqmod/s390x (1.0+20230126190232-2 to 1.0+20230126190232-2)
  • Migration status for indi-eqmod/s390x (1.0+20230126190232-2 to 1.0+20230126190232-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• intercal/amd64 (30:0.30-6 to 30:0.30-6)
  • Migration status for intercal/amd64 (30:0.30-6 to 30:0.30-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• intercal/arm64 (30:0.30-6 to 30:0.30-6)
  • Migration status for intercal/arm64 (30:0.30-6 to 30:0.30-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• intercal/armhf (30:0.30-6 to 30:0.30-6)
  • Migration status for intercal/armhf (30:0.30-6 to 30:0.30-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• intercal/i386 (30:0.30-6 to 30:0.30-6)
  • Migration status for intercal/i386 (30:0.30-6 to 30:0.30-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• intercal/ppc64el (30:0.30-6 to 30:0.30-6)
  • Migration status for intercal/ppc64el (30:0.30-6 to 30:0.30-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• intercal/riscv64 (30:0.30-6 to 30:0.30-6)
  • Migration status for intercal/riscv64 (30:0.30-6 to 30:0.30-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• intercal/s390x (30:0.30-6 to 30:0.30-6)
  • Migration status for intercal/s390x (30:0.30-6 to 30:0.30-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ipv6calc/amd64 (4.1.0-0.2 to 4.1.0-0.2)
  • Migration status for ipv6calc/amd64 (4.1.0-0.2 to 4.1.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ipv6calc/arm64 (4.1.0-0.2 to 4.1.0-0.2)
  • Migration status for ipv6calc/arm64 (4.1.0-0.2 to 4.1.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ipv6calc/armhf (4.1.0-0.2 to 4.1.0-0.2)
  • Migration status for ipv6calc/armhf (4.1.0-0.2 to 4.1.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ipv6calc/i386 (4.1.0-0.2 to 4.1.0-0.2)
  • Migration status for ipv6calc/i386 (4.1.0-0.2 to 4.1.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ipv6calc/ppc64el (4.1.0-0.2 to 4.1.0-0.2)
  • Migration status for ipv6calc/ppc64el (4.1.0-0.2 to 4.1.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ipv6calc/riscv64 (4.1.0-0.2 to 4.1.0-0.2)
  • Migration status for ipv6calc/riscv64 (4.1.0-0.2 to 4.1.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ipv6calc/s390x (4.1.0-0.2 to 4.1.0-0.2)
  • Migration status for ipv6calc/s390x (4.1.0-0.2 to 4.1.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ircd-irc2/amd64 (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1)
  • Migration status for ircd-irc2/amd64 (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ircd-irc2/arm64 (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1)
  • Migration status for ircd-irc2/arm64 (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ircd-irc2/armhf (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1)
  • Migration status for ircd-irc2/armhf (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ircd-irc2/i386 (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1)
  • Migration status for ircd-irc2/i386 (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ircd-irc2/ppc64el (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1)
  • Migration status for ircd-irc2/ppc64el (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ircd-irc2/riscv64 (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1)
  • Migration status for ircd-irc2/riscv64 (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ircd-irc2/s390x (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1)
  • Migration status for ircd-irc2/s390x (2.11.2p3~dfsg-7.1 to 2.11.2p3~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• irsim/amd64 (9.7.104-1.1 to 9.7.104-1.1)
  • Migration status for irsim/amd64 (9.7.104-1.1 to 9.7.104-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
• irsim/arm64 (9.7.104-1.1 to 9.7.104-1.1)
  • Migration status for irsim/arm64 (9.7.104-1.1 to 9.7.104-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
• irsim/armhf (9.7.104-1.1 to 9.7.104-1.1)
  • Migration status for irsim/armhf (9.7.104-1.1 to 9.7.104-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
• irsim/i386 (9.7.104-1.1 to 9.7.104-1.1)
  • Migration status for irsim/i386 (9.7.104-1.1 to 9.7.104-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
• irsim/ppc64el (9.7.104-1.1 to 9.7.104-1.1)
  • Migration status for irsim/ppc64el (9.7.104-1.1 to 9.7.104-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
• irsim/riscv64 (9.7.104-1.1 to 9.7.104-1.1)
  • Migration status for irsim/riscv64 (9.7.104-1.1 to 9.7.104-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
• irsim/s390x (9.7.104-1.1 to 9.7.104-1.1)
  • Migration status for irsim/s390x (9.7.104-1.1 to 9.7.104-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
• isatapd/amd64 (0.9.7-5 to 0.9.7-5)
  • Migration status for isatapd/amd64 (0.9.7-5 to 0.9.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
• isatapd/arm64 (0.9.7-5 to 0.9.7-5)
  • Migration status for isatapd/arm64 (0.9.7-5 to 0.9.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
• isatapd/armhf (0.9.7-5 to 0.9.7-5)
  • Migration status for isatapd/armhf (0.9.7-5 to 0.9.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
• isatapd/i386 (0.9.7-5 to 0.9.7-5)
  • Migration status for isatapd/i386 (0.9.7-5 to 0.9.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
• isatapd/ppc64el (0.9.7-5 to 0.9.7-5)
  • Migration status for isatapd/ppc64el (0.9.7-5 to 0.9.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
• isatapd/riscv64 (0.9.7-5 to 0.9.7-5)
  • Migration status for isatapd/riscv64 (0.9.7-5 to 0.9.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
• isatapd/s390x (0.9.7-5 to 0.9.7-5)
  • Migration status for isatapd/s390x (0.9.7-5 to 0.9.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
• jamnntpd/amd64 (1.3-1 to 1.3-1)
  • Migration status for jamnntpd/amd64 (1.3-1 to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jamnntpd/arm64 (1.3-1 to 1.3-1)
  • Migration status for jamnntpd/arm64 (1.3-1 to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jamnntpd/armhf (1.3-1 to 1.3-1)
  • Migration status for jamnntpd/armhf (1.3-1 to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jamnntpd/i386 (1.3-1 to 1.3-1)
  • Migration status for jamnntpd/i386 (1.3-1 to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jamnntpd/ppc64el (1.3-1 to 1.3-1)
  • Migration status for jamnntpd/ppc64el (1.3-1 to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jamnntpd/riscv64 (1.3-1 to 1.3-1)
  • Migration status for jamnntpd/riscv64 (1.3-1 to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jamnntpd/s390x (1.3-1 to 1.3-1)
  • Migration status for jamnntpd/s390x (1.3-1 to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jester/amd64 (1.0-16 to 1.0-16)
  • Migration status for jester/amd64 (1.0-16 to 1.0-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jester/arm64 (1.0-16 to 1.0-16)
  • Migration status for jester/arm64 (1.0-16 to 1.0-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jester/armhf (1.0-16 to 1.0-16)
  • Migration status for jester/armhf (1.0-16 to 1.0-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jester/i386 (1.0-16 to 1.0-16)
  • Migration status for jester/i386 (1.0-16 to 1.0-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jester/ppc64el (1.0-16 to 1.0-16)
  • Migration status for jester/ppc64el (1.0-16 to 1.0-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jester/riscv64 (1.0-16 to 1.0-16)
  • Migration status for jester/riscv64 (1.0-16 to 1.0-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jester/s390x (1.0-16 to 1.0-16)
  • Migration status for jester/s390x (1.0-16 to 1.0-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jpegpixi/amd64 (1.1.1-5 to 1.1.1-5)
  • Migration status for jpegpixi/amd64 (1.1.1-5 to 1.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jpegpixi/arm64 (1.1.1-5 to 1.1.1-5)
  • Migration status for jpegpixi/arm64 (1.1.1-5 to 1.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jpegpixi/armhf (1.1.1-5 to 1.1.1-5)
  • Migration status for jpegpixi/armhf (1.1.1-5 to 1.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jpegpixi/i386 (1.1.1-5 to 1.1.1-5)
  • Migration status for jpegpixi/i386 (1.1.1-5 to 1.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jpegpixi/ppc64el (1.1.1-5 to 1.1.1-5)
  • Migration status for jpegpixi/ppc64el (1.1.1-5 to 1.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jpegpixi/riscv64 (1.1.1-5 to 1.1.1-5)
  • Migration status for jpegpixi/riscv64 (1.1.1-5 to 1.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jpegpixi/s390x (1.1.1-5 to 1.1.1-5)
  • Migration status for jpegpixi/s390x (1.1.1-5 to 1.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jskeus/amd64 (1.2.6+dfsg-1 to 1.2.6+dfsg-1)
  • Migration status for jskeus/amd64 (1.2.6+dfsg-1 to 1.2.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jskeus/arm64 (1.2.6+dfsg-1 to 1.2.6+dfsg-1)
  • Migration status for jskeus/arm64 (1.2.6+dfsg-1 to 1.2.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jskeus/armhf (1.2.6+dfsg-1 to 1.2.6+dfsg-1)
  • Migration status for jskeus/armhf (1.2.6+dfsg-1 to 1.2.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jskeus/i386 (1.2.6+dfsg-1 to 1.2.6+dfsg-1)
  • Migration status for jskeus/i386 (1.2.6+dfsg-1 to 1.2.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jskeus/ppc64el (1.2.6+dfsg-1 to 1.2.6+dfsg-1)
  • Migration status for jskeus/ppc64el (1.2.6+dfsg-1 to 1.2.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jskeus/riscv64 (1.2.6+dfsg-1 to 1.2.6+dfsg-1)
  • Migration status for jskeus/riscv64 (1.2.6+dfsg-1 to 1.2.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• jskeus/s390x (1.2.6+dfsg-1 to 1.2.6+dfsg-1)
  • Migration status for jskeus/s390x (1.2.6+dfsg-1 to 1.2.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• juman/amd64 (7.0-3.9 to 7.0-3.9)
  • Migration status for juman/amd64 (7.0-3.9 to 7.0-3.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• juman/arm64 (7.0-3.9 to 7.0-3.9)
  • Migration status for juman/arm64 (7.0-3.9 to 7.0-3.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• juman/armhf (7.0-3.9 to 7.0-3.9)
  • Migration status for juman/armhf (7.0-3.9 to 7.0-3.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• juman/i386 (7.0-3.9 to 7.0-3.9)
  • Migration status for juman/i386 (7.0-3.9 to 7.0-3.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• juman/ppc64el (7.0-3.9 to 7.0-3.9)
  • Migration status for juman/ppc64el (7.0-3.9 to 7.0-3.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• juman/riscv64 (7.0-3.9 to 7.0-3.9)
  • Migration status for juman/riscv64 (7.0-3.9 to 7.0-3.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• juman/s390x (7.0-3.9 to 7.0-3.9)
  • Migration status for juman/s390x (7.0-3.9 to 7.0-3.9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kannel/amd64 (1.4.5-20 to 1.4.5-20)
  • Migration status for kannel/amd64 (1.4.5-20 to 1.4.5-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kannel/arm64 (1.4.5-20 to 1.4.5-20)
  • Migration status for kannel/arm64 (1.4.5-20 to 1.4.5-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kannel/armhf (1.4.5-20 to 1.4.5-20)
  • Migration status for kannel/armhf (1.4.5-20 to 1.4.5-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kannel/i386 (1.4.5-20 to 1.4.5-20)
  • Migration status for kannel/i386 (1.4.5-20 to 1.4.5-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kannel/ppc64el (1.4.5-20 to 1.4.5-20)
  • Migration status for kannel/ppc64el (1.4.5-20 to 1.4.5-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kannel/riscv64 (1.4.5-20 to 1.4.5-20)
  • Migration status for kannel/riscv64 (1.4.5-20 to 1.4.5-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kannel/s390x (1.4.5-20 to 1.4.5-20)
  • Migration status for kannel/s390x (1.4.5-20 to 1.4.5-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kdrill/amd64 (6.5deb2-13.1 to 6.5deb2-13.1)
  • Migration status for kdrill/amd64 (6.5deb2-13.1 to 6.5deb2-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kdrill/arm64 (6.5deb2-13.1 to 6.5deb2-13.1)
  • Migration status for kdrill/arm64 (6.5deb2-13.1 to 6.5deb2-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kdrill/armhf (6.5deb2-13.1 to 6.5deb2-13.1)
  • Migration status for kdrill/armhf (6.5deb2-13.1 to 6.5deb2-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kdrill/i386 (6.5deb2-13.1 to 6.5deb2-13.1)
  • Migration status for kdrill/i386 (6.5deb2-13.1 to 6.5deb2-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kdrill/ppc64el (6.5deb2-13.1 to 6.5deb2-13.1)
  • Migration status for kdrill/ppc64el (6.5deb2-13.1 to 6.5deb2-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kdrill/riscv64 (6.5deb2-13.1 to 6.5deb2-13.1)
  • Migration status for kdrill/riscv64 (6.5deb2-13.1 to 6.5deb2-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kdrill/s390x (6.5deb2-13.1 to 6.5deb2-13.1)
  • Migration status for kdrill/s390x (6.5deb2-13.1 to 6.5deb2-13.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ketm/amd64 (0.0.6-27 to 0.0.6-27)
  • Migration status for ketm/amd64 (0.0.6-27 to 0.0.6-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ketm/arm64 (0.0.6-27 to 0.0.6-27)
  • Migration status for ketm/arm64 (0.0.6-27 to 0.0.6-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ketm/armhf (0.0.6-27 to 0.0.6-27)
  • Migration status for ketm/armhf (0.0.6-27 to 0.0.6-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ketm/i386 (0.0.6-27 to 0.0.6-27)
  • Migration status for ketm/i386 (0.0.6-27 to 0.0.6-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ketm/ppc64el (0.0.6-27 to 0.0.6-27)
  • Migration status for ketm/ppc64el (0.0.6-27 to 0.0.6-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ketm/riscv64 (0.0.6-27 to 0.0.6-27)
  • Migration status for ketm/riscv64 (0.0.6-27 to 0.0.6-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ketm/s390x (0.0.6-27 to 0.0.6-27)
  • Migration status for ketm/s390x (0.0.6-27 to 0.0.6-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kodi-inputstream-adaptive/amd64 (21.5.9+ds-1 to 21.5.9+ds-1)
  • Migration status for kodi-inputstream-adaptive/amd64 (21.5.9+ds-1 to 21.5.9+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
• kodi-inputstream-adaptive/arm64 (21.5.9+ds-1 to 21.5.9+ds-1)
  • Migration status for kodi-inputstream-adaptive/arm64 (21.5.9+ds-1 to 21.5.9+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
• kodi-inputstream-adaptive/armhf (21.5.9+ds-1 to 21.5.9+ds-1)
  • Migration status for kodi-inputstream-adaptive/armhf (21.5.9+ds-1 to 21.5.9+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
• kodi-inputstream-adaptive/i386 (21.5.9+ds-1 to 21.5.9+ds-1)
  • Migration status for kodi-inputstream-adaptive/i386 (21.5.9+ds-1 to 21.5.9+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
• kodi-inputstream-adaptive/ppc64el (21.5.9+ds-1 to 21.5.9+ds-1)
  • Migration status for kodi-inputstream-adaptive/ppc64el (21.5.9+ds-1 to 21.5.9+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
• kodi-inputstream-adaptive/riscv64 (21.5.9+ds-1 to 21.5.9+ds-1)
  • Migration status for kodi-inputstream-adaptive/riscv64 (21.5.9+ds-1 to 21.5.9+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
• kodi-inputstream-adaptive/s390x (21.5.9+ds-1 to 21.5.9+ds-1)
  • Migration status for kodi-inputstream-adaptive/s390x (21.5.9+ds-1 to 21.5.9+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
• kodi-pvr-hts/amd64 (21.2.6+ds-1 to 21.2.6+ds-1)
  • Migration status for kodi-pvr-hts/amd64 (21.2.6+ds-1 to 21.2.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
• kodi-pvr-hts/arm64 (21.2.6+ds-1 to 21.2.6+ds-1)
  • Migration status for kodi-pvr-hts/arm64 (21.2.6+ds-1 to 21.2.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
• kodi-pvr-hts/armhf (21.2.6+ds-1 to 21.2.6+ds-1)
  • Migration status for kodi-pvr-hts/armhf (21.2.6+ds-1 to 21.2.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
• kodi-pvr-hts/i386 (21.2.6+ds-1 to 21.2.6+ds-1)
  • Migration status for kodi-pvr-hts/i386 (21.2.6+ds-1 to 21.2.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
• kodi-pvr-hts/ppc64el (21.2.6+ds-1 to 21.2.6+ds-1)
  • Migration status for kodi-pvr-hts/ppc64el (21.2.6+ds-1 to 21.2.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
• kodi-pvr-hts/riscv64 (21.2.6+ds-1 to 21.2.6+ds-1)
  • Migration status for kodi-pvr-hts/riscv64 (21.2.6+ds-1 to 21.2.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
• kodi-pvr-hts/s390x (21.2.6+ds-1 to 21.2.6+ds-1)
  • Migration status for kodi-pvr-hts/s390x (21.2.6+ds-1 to 21.2.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
• kraptor/amd64 (0.0.20040403+ds-4 to 0.0.20040403+ds-4)
  • Migration status for kraptor/amd64 (0.0.20040403+ds-4 to 0.0.20040403+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kraptor/arm64 (0.0.20040403+ds-4 to 0.0.20040403+ds-4)
  • Migration status for kraptor/arm64 (0.0.20040403+ds-4 to 0.0.20040403+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kraptor/armhf (0.0.20040403+ds-4 to 0.0.20040403+ds-4)
  • Migration status for kraptor/armhf (0.0.20040403+ds-4 to 0.0.20040403+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kraptor/i386 (0.0.20040403+ds-4 to 0.0.20040403+ds-4)
  • Migration status for kraptor/i386 (0.0.20040403+ds-4 to 0.0.20040403+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kraptor/ppc64el (0.0.20040403+ds-4 to 0.0.20040403+ds-4)
  • Migration status for kraptor/ppc64el (0.0.20040403+ds-4 to 0.0.20040403+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kraptor/riscv64 (0.0.20040403+ds-4 to 0.0.20040403+ds-4)
  • Migration status for kraptor/riscv64 (0.0.20040403+ds-4 to 0.0.20040403+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• kraptor/s390x (0.0.20040403+ds-4 to 0.0.20040403+ds-4)
  • Migration status for kraptor/s390x (0.0.20040403+ds-4 to 0.0.20040403+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lcd4linux/amd64 (0.11.0~svn1203-3 to 0.11.0~svn1203-3)
  • Migration status for lcd4linux/amd64 (0.11.0~svn1203-3 to 0.11.0~svn1203-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lcd4linux/arm64 (0.11.0~svn1203-3 to 0.11.0~svn1203-3)
  • Migration status for lcd4linux/arm64 (0.11.0~svn1203-3 to 0.11.0~svn1203-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lcd4linux/armhf (0.11.0~svn1203-3 to 0.11.0~svn1203-3)
  • Migration status for lcd4linux/armhf (0.11.0~svn1203-3 to 0.11.0~svn1203-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lcd4linux/i386 (0.11.0~svn1203-3 to 0.11.0~svn1203-3)
  • Migration status for lcd4linux/i386 (0.11.0~svn1203-3 to 0.11.0~svn1203-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lcd4linux/ppc64el (0.11.0~svn1203-3 to 0.11.0~svn1203-3)
  • Migration status for lcd4linux/ppc64el (0.11.0~svn1203-3 to 0.11.0~svn1203-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lcd4linux/s390x (0.11.0~svn1203-3 to 0.11.0~svn1203-3)
  • Migration status for lcd4linux/s390x (0.11.0~svn1203-3 to 0.11.0~svn1203-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libast/amd64 (0.7-11 to 0.7-11)
  • Migration status for libast/amd64 (0.7-11 to 0.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libast/arm64 (0.7-11 to 0.7-11)
  • Migration status for libast/arm64 (0.7-11 to 0.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libast/armhf (0.7-11 to 0.7-11)
  • Migration status for libast/armhf (0.7-11 to 0.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libast/i386 (0.7-11 to 0.7-11)
  • Migration status for libast/i386 (0.7-11 to 0.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libast/ppc64el (0.7-11 to 0.7-11)
  • Migration status for libast/ppc64el (0.7-11 to 0.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libast/riscv64 (0.7-11 to 0.7-11)
  • Migration status for libast/riscv64 (0.7-11 to 0.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libast/s390x (0.7-11 to 0.7-11)
  • Migration status for libast/s390x (0.7-11 to 0.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libcpanel-json-xs-perl_pu (4.39-2 to 4.39-2~deb13u1)
  • Migration status for libcpanel-json-xs-perl_pu (4.39-2 to 4.39-2~deb13u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libcpanel-json-xs-perl is newer in the target suite (4.39-2 4.39-2~deb13u1)
• libdigidoc/amd64 (3.10.5-6 to 3.10.5-6)
  • Migration status for libdigidoc/amd64 (3.10.5-6 to 3.10.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libdigidoc/arm64 (3.10.5-6 to 3.10.5-6)
  • Migration status for libdigidoc/arm64 (3.10.5-6 to 3.10.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libdigidoc/armhf (3.10.5-6 to 3.10.5-6)
  • Migration status for libdigidoc/armhf (3.10.5-6 to 3.10.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libdigidoc/i386 (3.10.5-6 to 3.10.5-6)
  • Migration status for libdigidoc/i386 (3.10.5-6 to 3.10.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libdigidoc/ppc64el (3.10.5-6 to 3.10.5-6)
  • Migration status for libdigidoc/ppc64el (3.10.5-6 to 3.10.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libdigidoc/riscv64 (3.10.5-6 to 3.10.5-6)
  • Migration status for libdigidoc/riscv64 (3.10.5-6 to 3.10.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libdigidoc/s390x (3.10.5-6 to 3.10.5-6)
  • Migration status for libdigidoc/s390x (3.10.5-6 to 3.10.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libint/amd64 (1.2.1-6 to 1.2.1-6)
  • Migration status for libint/amd64 (1.2.1-6 to 1.2.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libint/arm64 (1.2.1-6 to 1.2.1-6)
  • Migration status for libint/arm64 (1.2.1-6 to 1.2.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libint/armhf (1.2.1-6 to 1.2.1-6)
  • Migration status for libint/armhf (1.2.1-6 to 1.2.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libint/i386 (1.2.1-6 to 1.2.1-6)
  • Migration status for libint/i386 (1.2.1-6 to 1.2.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libint/ppc64el (1.2.1-6 to 1.2.1-6)
  • Migration status for libint/ppc64el (1.2.1-6 to 1.2.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libint/riscv64 (1.2.1-6 to 1.2.1-6)
  • Migration status for libint/riscv64 (1.2.1-6 to 1.2.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libint/s390x (1.2.1-6 to 1.2.1-6)
  • Migration status for libint/s390x (1.2.1-6 to 1.2.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libjson-xs-perl_pu (4.040-1 to 4.040-1~deb13u1)
  • Migration status for libjson-xs-perl_pu (4.040-1 to 4.040-1~deb13u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: libjson-xs-perl is newer in the target suite (4.040-1 4.040-1~deb13u1)
• libkarma/amd64 (0.1.2-11 to 0.1.2-11)
  • Migration status for libkarma/amd64 (0.1.2-11 to 0.1.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libkarma/arm64 (0.1.2-11 to 0.1.2-11)
  • Migration status for libkarma/arm64 (0.1.2-11 to 0.1.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libkarma/armhf (0.1.2-11 to 0.1.2-11)
  • Migration status for libkarma/armhf (0.1.2-11 to 0.1.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libkarma/i386 (0.1.2-11 to 0.1.2-11)
  • Migration status for libkarma/i386 (0.1.2-11 to 0.1.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libkarma/ppc64el (0.1.2-11 to 0.1.2-11)
  • Migration status for libkarma/ppc64el (0.1.2-11 to 0.1.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libkarma/riscv64 (0.1.2-11 to 0.1.2-11)
  • Migration status for libkarma/riscv64 (0.1.2-11 to 0.1.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libkarma/s390x (0.1.2-11 to 0.1.2-11)
  • Migration status for libkarma/s390x (0.1.2-11 to 0.1.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libshairport/amd64 (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4)
  • Migration status for libshairport/amd64 (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libshairport/arm64 (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4)
  • Migration status for libshairport/arm64 (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libshairport/armhf (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4)
  • Migration status for libshairport/armhf (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libshairport/i386 (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4)
  • Migration status for libshairport/i386 (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libshairport/ppc64el (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4)
  • Migration status for libshairport/ppc64el (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libshairport/riscv64 (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4)
  • Migration status for libshairport/riscv64 (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libshairport/s390x (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4)
  • Migration status for libshairport/s390x (1.2.1~git20120510.cbed0c1-4 to 1.2.1~git20120510.cbed0c1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libunivalue/amd64 (1.1.1+20191112-3 to 1.1.1+20191112-3)
  • Migration status for libunivalue/amd64 (1.1.1+20191112-3 to 1.1.1+20191112-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libunivalue/arm64 (1.1.1+20191112-3 to 1.1.1+20191112-3)
  • Migration status for libunivalue/arm64 (1.1.1+20191112-3 to 1.1.1+20191112-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libunivalue/armhf (1.1.1+20191112-3 to 1.1.1+20191112-3)
  • Migration status for libunivalue/armhf (1.1.1+20191112-3 to 1.1.1+20191112-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libunivalue/i386 (1.1.1+20191112-3 to 1.1.1+20191112-3)
  • Migration status for libunivalue/i386 (1.1.1+20191112-3 to 1.1.1+20191112-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libunivalue/ppc64el (1.1.1+20191112-3 to 1.1.1+20191112-3)
  • Migration status for libunivalue/ppc64el (1.1.1+20191112-3 to 1.1.1+20191112-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libunivalue/riscv64 (1.1.1+20191112-3 to 1.1.1+20191112-3)
  • Migration status for libunivalue/riscv64 (1.1.1+20191112-3 to 1.1.1+20191112-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libunivalue/s390x (1.1.1+20191112-3 to 1.1.1+20191112-3)
  • Migration status for libunivalue/s390x (1.1.1+20191112-3 to 1.1.1+20191112-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libxsmm/amd64 (1.17-4 to 1.17-4)
  • Migration status for libxsmm/amd64 (1.17-4 to 1.17-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libxsmm/arm64 (1.17-4 to 1.17-4)
  • Migration status for libxsmm/arm64 (1.17-4 to 1.17-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libxsmm/armhf (1.17-4 to 1.17-4)
  • Migration status for libxsmm/armhf (1.17-4 to 1.17-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libxsmm/i386 (1.17-4 to 1.17-4)
  • Migration status for libxsmm/i386 (1.17-4 to 1.17-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libxsmm/ppc64el (1.17-4 to 1.17-4)
  • Migration status for libxsmm/ppc64el (1.17-4 to 1.17-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libxsmm/riscv64 (1.17-4 to 1.17-4)
  • Migration status for libxsmm/riscv64 (1.17-4 to 1.17-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• libxsmm/s390x (1.17-4 to 1.17-4)
  • Migration status for libxsmm/s390x (1.17-4 to 1.17-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• licenseutils/amd64 (0.0.9-8 to 0.0.9-8)
  • Migration status for licenseutils/amd64 (0.0.9-8 to 0.0.9-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• licenseutils/arm64 (0.0.9-8 to 0.0.9-8)
  • Migration status for licenseutils/arm64 (0.0.9-8 to 0.0.9-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• licenseutils/armhf (0.0.9-8 to 0.0.9-8)
  • Migration status for licenseutils/armhf (0.0.9-8 to 0.0.9-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• licenseutils/i386 (0.0.9-8 to 0.0.9-8)
  • Migration status for licenseutils/i386 (0.0.9-8 to 0.0.9-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• licenseutils/ppc64el (0.0.9-8 to 0.0.9-8)
  • Migration status for licenseutils/ppc64el (0.0.9-8 to 0.0.9-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• licenseutils/riscv64 (0.0.9-8 to 0.0.9-8)
  • Migration status for licenseutils/riscv64 (0.0.9-8 to 0.0.9-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• licenseutils/s390x (0.0.9-8 to 0.0.9-8)
  • Migration status for licenseutils/s390x (0.0.9-8 to 0.0.9-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• liquidwar/amd64 (5.6.5-2 to 5.6.5-2)
  • Migration status for liquidwar/amd64 (5.6.5-2 to 5.6.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• liquidwar/arm64 (5.6.5-2 to 5.6.5-2)
  • Migration status for liquidwar/arm64 (5.6.5-2 to 5.6.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• liquidwar/armhf (5.6.5-2 to 5.6.5-2)
  • Migration status for liquidwar/armhf (5.6.5-2 to 5.6.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• liquidwar/i386 (5.6.5-2 to 5.6.5-2)
  • Migration status for liquidwar/i386 (5.6.5-2 to 5.6.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• liquidwar/ppc64el (5.6.5-2 to 5.6.5-2)
  • Migration status for liquidwar/ppc64el (5.6.5-2 to 5.6.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• liquidwar/riscv64 (5.6.5-2 to 5.6.5-2)
  • Migration status for liquidwar/riscv64 (5.6.5-2 to 5.6.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• liquidwar/s390x (5.6.5-2 to 5.6.5-2)
  • Migration status for liquidwar/s390x (5.6.5-2 to 5.6.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• litecoin/amd64 (0.21.4-1 to 0.21.4-1)
  • Migration status for litecoin/amd64 (0.21.4-1 to 0.21.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• litecoin/arm64 (0.21.4-1 to 0.21.4-1)
  • Migration status for litecoin/arm64 (0.21.4-1 to 0.21.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• litecoin/armhf (0.21.4-1 to 0.21.4-1)
  • Migration status for litecoin/armhf (0.21.4-1 to 0.21.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• litecoin/i386 (0.21.4-1 to 0.21.4-1)
  • Migration status for litecoin/i386 (0.21.4-1 to 0.21.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• litecoin/ppc64el (0.21.4-1 to 0.21.4-1)
  • Migration status for litecoin/ppc64el (0.21.4-1 to 0.21.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• litecoin/riscv64 (0.21.4-1 to 0.21.4-1)
  • Migration status for litecoin/riscv64 (0.21.4-1 to 0.21.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• litecoin/s390x (0.21.4-1 to 0.21.4-1)
  • Migration status for litecoin/s390x (0.21.4-1 to 0.21.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lm4tools/amd64 (3:0.1.3-1 to 3:0.1.3-1)
  • Migration status for lm4tools/amd64 (3:0.1.3-1 to 3:0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lm4tools/arm64 (3:0.1.3-1 to 3:0.1.3-1)
  • Migration status for lm4tools/arm64 (3:0.1.3-1 to 3:0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lm4tools/armhf (3:0.1.3-1 to 3:0.1.3-1)
  • Migration status for lm4tools/armhf (3:0.1.3-1 to 3:0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lm4tools/i386 (3:0.1.3-1 to 3:0.1.3-1)
  • Migration status for lm4tools/i386 (3:0.1.3-1 to 3:0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lm4tools/ppc64el (3:0.1.3-1 to 3:0.1.3-1)
  • Migration status for lm4tools/ppc64el (3:0.1.3-1 to 3:0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lm4tools/riscv64 (3:0.1.3-1 to 3:0.1.3-1)
  • Migration status for lm4tools/riscv64 (3:0.1.3-1 to 3:0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lm4tools/s390x (3:0.1.3-1 to 3:0.1.3-1)
  • Migration status for lm4tools/s390x (3:0.1.3-1 to 3:0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lmemory/amd64 (0.6c-13 to 0.6c-13)
  • Migration status for lmemory/amd64 (0.6c-13 to 0.6c-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lmemory/arm64 (0.6c-13 to 0.6c-13)
  • Migration status for lmemory/arm64 (0.6c-13 to 0.6c-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lmemory/armhf (0.6c-13 to 0.6c-13)
  • Migration status for lmemory/armhf (0.6c-13 to 0.6c-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lmemory/i386 (0.6c-13 to 0.6c-13)
  • Migration status for lmemory/i386 (0.6c-13 to 0.6c-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lmemory/ppc64el (0.6c-13 to 0.6c-13)
  • Migration status for lmemory/ppc64el (0.6c-13 to 0.6c-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lmemory/riscv64 (0.6c-13 to 0.6c-13)
  • Migration status for lmemory/riscv64 (0.6c-13 to 0.6c-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lmemory/s390x (0.6c-13 to 0.6c-13)
  • Migration status for lmemory/s390x (0.6c-13 to 0.6c-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lmms/ppc64el (1.2.2+dfsg1-6 to 1.2.2+dfsg1-6)
  • Migration status for lmms/ppc64el (1.2.2+dfsg1-6 to 1.2.2+dfsg1-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: lmms/ppc64el libgig (not considered)
    • Invalidated by dependency
• loadwatch/amd64 (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8)
  • Migration status for loadwatch/amd64 (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• loadwatch/arm64 (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8)
  • Migration status for loadwatch/arm64 (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• loadwatch/armhf (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8)
  • Migration status for loadwatch/armhf (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• loadwatch/i386 (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8)
  • Migration status for loadwatch/i386 (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• loadwatch/ppc64el (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8)
  • Migration status for loadwatch/ppc64el (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• loadwatch/riscv64 (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8)
  • Migration status for loadwatch/riscv64 (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• loadwatch/s390x (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8)
  • Migration status for loadwatch/s390x (1.0+1.1alpha1-8 to 1.0+1.1alpha1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• logtool/amd64 (1.2.8-14 to 1.2.8-14)
  • Migration status for logtool/amd64 (1.2.8-14 to 1.2.8-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• logtool/arm64 (1.2.8-14 to 1.2.8-14)
  • Migration status for logtool/arm64 (1.2.8-14 to 1.2.8-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• logtool/armhf (1.2.8-14 to 1.2.8-14)
  • Migration status for logtool/armhf (1.2.8-14 to 1.2.8-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• logtool/i386 (1.2.8-14 to 1.2.8-14)
  • Migration status for logtool/i386 (1.2.8-14 to 1.2.8-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• logtool/ppc64el (1.2.8-14 to 1.2.8-14)
  • Migration status for logtool/ppc64el (1.2.8-14 to 1.2.8-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• logtool/riscv64 (1.2.8-14 to 1.2.8-14)
  • Migration status for logtool/riscv64 (1.2.8-14 to 1.2.8-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• logtool/s390x (1.2.8-14 to 1.2.8-14)
  • Migration status for logtool/s390x (1.2.8-14 to 1.2.8-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lookup/amd64 (1.08b-14 to 1.08b-14)
  • Migration status for lookup/amd64 (1.08b-14 to 1.08b-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lookup/arm64 (1.08b-14 to 1.08b-14)
  • Migration status for lookup/arm64 (1.08b-14 to 1.08b-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lookup/armhf (1.08b-14 to 1.08b-14)
  • Migration status for lookup/armhf (1.08b-14 to 1.08b-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lookup/i386 (1.08b-14 to 1.08b-14)
  • Migration status for lookup/i386 (1.08b-14 to 1.08b-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lookup/ppc64el (1.08b-14 to 1.08b-14)
  • Migration status for lookup/ppc64el (1.08b-14 to 1.08b-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lookup/riscv64 (1.08b-14 to 1.08b-14)
  • Migration status for lookup/riscv64 (1.08b-14 to 1.08b-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lookup/s390x (1.08b-14 to 1.08b-14)
  • Migration status for lookup/s390x (1.08b-14 to 1.08b-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lunar/amd64 (2.2-9 to 2.2-9)
  • Migration status for lunar/amd64 (2.2-9 to 2.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lunar/arm64 (2.2-9 to 2.2-9)
  • Migration status for lunar/arm64 (2.2-9 to 2.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lunar/armhf (2.2-9 to 2.2-9)
  • Migration status for lunar/armhf (2.2-9 to 2.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lunar/i386 (2.2-9 to 2.2-9)
  • Migration status for lunar/i386 (2.2-9 to 2.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lunar/ppc64el (2.2-9 to 2.2-9)
  • Migration status for lunar/ppc64el (2.2-9 to 2.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lunar/riscv64 (2.2-9 to 2.2-9)
  • Migration status for lunar/riscv64 (2.2-9 to 2.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• lunar/s390x (2.2-9 to 2.2-9)
  • Migration status for lunar/s390x (2.2-9 to 2.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mactelnet/amd64 (0.6.1-1.1 to 0.6.1-1.1)
  • Migration status for mactelnet/amd64 (0.6.1-1.1 to 0.6.1-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
• mactelnet/arm64 (0.6.1-1.1 to 0.6.1-1.1)
  • Migration status for mactelnet/arm64 (0.6.1-1.1 to 0.6.1-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
• mactelnet/armhf (0.6.1-1.1 to 0.6.1-1.1)
  • Migration status for mactelnet/armhf (0.6.1-1.1 to 0.6.1-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
• mactelnet/i386 (0.6.1-1.1 to 0.6.1-1.1)
  • Migration status for mactelnet/i386 (0.6.1-1.1 to 0.6.1-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
• mactelnet/ppc64el (0.6.1-1.1 to 0.6.1-1.1)
  • Migration status for mactelnet/ppc64el (0.6.1-1.1 to 0.6.1-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
• mactelnet/riscv64 (0.6.1-1.1 to 0.6.1-1.1)
  • Migration status for mactelnet/riscv64 (0.6.1-1.1 to 0.6.1-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
• mactelnet/s390x (0.6.1-1.1 to 0.6.1-1.1)
  • Migration status for mactelnet/s390x (0.6.1-1.1 to 0.6.1-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
• macutils/amd64 (2.0b3-17 to 2.0b3-17)
  • Migration status for macutils/amd64 (2.0b3-17 to 2.0b3-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• macutils/arm64 (2.0b3-17 to 2.0b3-17)
  • Migration status for macutils/arm64 (2.0b3-17 to 2.0b3-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• macutils/armhf (2.0b3-17 to 2.0b3-17)
  • Migration status for macutils/armhf (2.0b3-17 to 2.0b3-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• macutils/i386 (2.0b3-17 to 2.0b3-17)
  • Migration status for macutils/i386 (2.0b3-17 to 2.0b3-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• macutils/ppc64el (2.0b3-17 to 2.0b3-17)
  • Migration status for macutils/ppc64el (2.0b3-17 to 2.0b3-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• macutils/riscv64 (2.0b3-17 to 2.0b3-17)
  • Migration status for macutils/riscv64 (2.0b3-17 to 2.0b3-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• macutils/s390x (2.0b3-17 to 2.0b3-17)
  • Migration status for macutils/s390x (2.0b3-17 to 2.0b3-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mathomatic/amd64 (16.0.5-5 to 16.0.5-5)
  • Migration status for mathomatic/amd64 (16.0.5-5 to 16.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mathomatic/arm64 (16.0.5-5 to 16.0.5-5)
  • Migration status for mathomatic/arm64 (16.0.5-5 to 16.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mathomatic/armhf (16.0.5-5 to 16.0.5-5)
  • Migration status for mathomatic/armhf (16.0.5-5 to 16.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mathomatic/i386 (16.0.5-5 to 16.0.5-5)
  • Migration status for mathomatic/i386 (16.0.5-5 to 16.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mathomatic/ppc64el (16.0.5-5 to 16.0.5-5)
  • Migration status for mathomatic/ppc64el (16.0.5-5 to 16.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mathomatic/riscv64 (16.0.5-5 to 16.0.5-5)
  • Migration status for mathomatic/riscv64 (16.0.5-5 to 16.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mathomatic/s390x (16.0.5-5 to 16.0.5-5)
  • Migration status for mathomatic/s390x (16.0.5-5 to 16.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mc_pu (3:4.8.33-1.1 to 3:4.8.33-1+deb13u1)
  • Migration status for mc_pu (3:4.8.33-1.1 to 3:4.8.33-1+deb13u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: mc is newer in the target suite (3:4.8.33-1.1 3:4.8.33-1+deb13u1)
• mcabber/amd64 (1.1.2-2 to 1.1.2-2)
  • Migration status for mcabber/amd64 (1.1.2-2 to 1.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mcabber/arm64 (1.1.2-2 to 1.1.2-2)
  • Migration status for mcabber/arm64 (1.1.2-2 to 1.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mcabber/armhf (1.1.2-2 to 1.1.2-2)
  • Migration status for mcabber/armhf (1.1.2-2 to 1.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mcabber/i386 (1.1.2-2 to 1.1.2-2)
  • Migration status for mcabber/i386 (1.1.2-2 to 1.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mcabber/ppc64el (1.1.2-2 to 1.1.2-2)
  • Migration status for mcabber/ppc64el (1.1.2-2 to 1.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mcabber/s390x (1.1.2-2 to 1.1.2-2)
  • Migration status for mcabber/s390x (1.1.2-2 to 1.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mccs/amd64 (1:1.1-10 to 1:1.1-10)
  • Migration status for mccs/amd64 (1:1.1-10 to 1:1.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mccs/arm64 (1:1.1-10 to 1:1.1-10)
  • Migration status for mccs/arm64 (1:1.1-10 to 1:1.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mccs/armhf (1:1.1-10 to 1:1.1-10)
  • Migration status for mccs/armhf (1:1.1-10 to 1:1.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mccs/i386 (1:1.1-10 to 1:1.1-10)
  • Migration status for mccs/i386 (1:1.1-10 to 1:1.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mccs/ppc64el (1:1.1-10 to 1:1.1-10)
  • Migration status for mccs/ppc64el (1:1.1-10 to 1:1.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mccs/s390x (1:1.1-10 to 1:1.1-10)
  • Migration status for mccs/s390x (1:1.1-10 to 1:1.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• meritous/amd64 (1.5-1.1 to 1.5-1.1)
  • Migration status for meritous/amd64 (1.5-1.1 to 1.5-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
• meritous/arm64 (1.5-1.1 to 1.5-1.1)
  • Migration status for meritous/arm64 (1.5-1.1 to 1.5-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
• meritous/armhf (1.5-1.1 to 1.5-1.1)
  • Migration status for meritous/armhf (1.5-1.1 to 1.5-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
• meritous/i386 (1.5-1.1 to 1.5-1.1)
  • Migration status for meritous/i386 (1.5-1.1 to 1.5-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
• meritous/ppc64el (1.5-1.1 to 1.5-1.1)
  • Migration status for meritous/ppc64el (1.5-1.1 to 1.5-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
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• meritous/s390x (1.5-1.1 to 1.5-1.1)
  • Migration status for meritous/s390x (1.5-1.1 to 1.5-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
• meshlab/amd64 (2022.02+dfsg1-1 to 2022.02+dfsg1-1)
  • Migration status for meshlab/amd64 (2022.02+dfsg1-1 to 2022.02+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• meshlab/arm64 (2022.02+dfsg1-1 to 2022.02+dfsg1-1)
  • Migration status for meshlab/arm64 (2022.02+dfsg1-1 to 2022.02+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• meshlab/armhf (2022.02+dfsg1-1 to 2022.02+dfsg1-1)
  • Migration status for meshlab/armhf (2022.02+dfsg1-1 to 2022.02+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• meshlab/i386 (2022.02+dfsg1-1 to 2022.02+dfsg1-1)
  • Migration status for meshlab/i386 (2022.02+dfsg1-1 to 2022.02+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• meshlab/ppc64el (2022.02+dfsg1-1 to 2022.02+dfsg1-1)
  • Migration status for meshlab/ppc64el (2022.02+dfsg1-1 to 2022.02+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• meshlab/riscv64 (2022.02+dfsg1-1 to 2022.02+dfsg1-1)
  • Migration status for meshlab/riscv64 (2022.02+dfsg1-1 to 2022.02+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• meshlab/s390x (2022.02+dfsg1-1 to 2022.02+dfsg1-1)
  • Migration status for meshlab/s390x (2022.02+dfsg1-1 to 2022.02+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mhwaveedit/amd64 (1.4.24-1 to 1.4.24-1)
  • Migration status for mhwaveedit/amd64 (1.4.24-1 to 1.4.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mhwaveedit/arm64 (1.4.24-1 to 1.4.24-1)
  • Migration status for mhwaveedit/arm64 (1.4.24-1 to 1.4.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mhwaveedit/armhf (1.4.24-1 to 1.4.24-1)
  • Migration status for mhwaveedit/armhf (1.4.24-1 to 1.4.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mhwaveedit/i386 (1.4.24-1 to 1.4.24-1)
  • Migration status for mhwaveedit/i386 (1.4.24-1 to 1.4.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mhwaveedit/ppc64el (1.4.24-1 to 1.4.24-1)
  • Migration status for mhwaveedit/ppc64el (1.4.24-1 to 1.4.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mhwaveedit/s390x (1.4.24-1 to 1.4.24-1)
  • Migration status for mhwaveedit/s390x (1.4.24-1 to 1.4.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• microdc2/amd64 (0.15.6-7 to 0.15.6-7)
  • Migration status for microdc2/amd64 (0.15.6-7 to 0.15.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• microdc2/arm64 (0.15.6-7 to 0.15.6-7)
  • Migration status for microdc2/arm64 (0.15.6-7 to 0.15.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• microdc2/armhf (0.15.6-7 to 0.15.6-7)
  • Migration status for microdc2/armhf (0.15.6-7 to 0.15.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• microdc2/i386 (0.15.6-7 to 0.15.6-7)
  • Migration status for microdc2/i386 (0.15.6-7 to 0.15.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• microdc2/ppc64el (0.15.6-7 to 0.15.6-7)
  • Migration status for microdc2/ppc64el (0.15.6-7 to 0.15.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• microdc2/riscv64 (0.15.6-7 to 0.15.6-7)
  • Migration status for microdc2/riscv64 (0.15.6-7 to 0.15.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• microdc2/s390x (0.15.6-7 to 0.15.6-7)
  • Migration status for microdc2/s390x (0.15.6-7 to 0.15.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• milter-greylist/amd64 (4.6.4-4 to 4.6.4-4)
  • Migration status for milter-greylist/amd64 (4.6.4-4 to 4.6.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• milter-greylist/arm64 (4.6.4-4 to 4.6.4-4)
  • Migration status for milter-greylist/arm64 (4.6.4-4 to 4.6.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• milter-greylist/armhf (4.6.4-4 to 4.6.4-4)
  • Migration status for milter-greylist/armhf (4.6.4-4 to 4.6.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• milter-greylist/i386 (4.6.4-4 to 4.6.4-4)
  • Migration status for milter-greylist/i386 (4.6.4-4 to 4.6.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• milter-greylist/ppc64el (4.6.4-4 to 4.6.4-4)
  • Migration status for milter-greylist/ppc64el (4.6.4-4 to 4.6.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• milter-greylist/riscv64 (4.6.4-4 to 4.6.4-4)
  • Migration status for milter-greylist/riscv64 (4.6.4-4 to 4.6.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• milter-greylist/s390x (4.6.4-4 to 4.6.4-4)
  • Migration status for milter-greylist/s390x (4.6.4-4 to 4.6.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mimedefang/amd64 (3.6-2 to 3.6-2)
  • Migration status for mimedefang/amd64 (3.6-2 to 3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mimedefang/arm64 (3.6-2 to 3.6-2)
  • Migration status for mimedefang/arm64 (3.6-2 to 3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mimedefang/armhf (3.6-2 to 3.6-2)
  • Migration status for mimedefang/armhf (3.6-2 to 3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mimedefang/i386 (3.6-2 to 3.6-2)
  • Migration status for mimedefang/i386 (3.6-2 to 3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mimedefang/ppc64el (3.6-2 to 3.6-2)
  • Migration status for mimedefang/ppc64el (3.6-2 to 3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mimedefang/riscv64 (3.6-2 to 3.6-2)
  • Migration status for mimedefang/riscv64 (3.6-2 to 3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mimedefang/s390x (3.6-2 to 3.6-2)
  • Migration status for mimedefang/s390x (3.6-2 to 3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• monero/amd64 (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1)
  • Migration status for monero/amd64 (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: monero/amd64 miniupnpc (not considered)
    • Invalidated by dependency
• monero/arm64 (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1)
  • Migration status for monero/arm64 (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: monero/arm64 miniupnpc (not considered)
    • Invalidated by dependency
• monero/armhf (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1)
  • Migration status for monero/armhf (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: monero/armhf miniupnpc (not considered)
    • Invalidated by dependency
• monero/i386 (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1)
  • Migration status for monero/i386 (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: monero/i386 miniupnpc (not considered)
    • Invalidated by dependency
• monero/ppc64el (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1)
  • Migration status for monero/ppc64el (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: monero/ppc64el miniupnpc (not considered)
    • Invalidated by dependency
• monero/riscv64 (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1)
  • Migration status for monero/riscv64 (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: monero/riscv64 miniupnpc (not considered)
    • Invalidated by dependency
• monero/s390x (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1)
  • Migration status for monero/s390x (0.18.4.2+~0+20200826-1 to 0.18.4.2+~0+20200826-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: monero/s390x miniupnpc (not considered)
    • Invalidated by dependency
• mp3splt/amd64 (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3)
  • Migration status for mp3splt/amd64 (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mp3splt/arm64 (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3)
  • Migration status for mp3splt/arm64 (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mp3splt/armhf (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3)
  • Migration status for mp3splt/armhf (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mp3splt/i386 (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3)
  • Migration status for mp3splt/i386 (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mp3splt/ppc64el (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3)
  • Migration status for mp3splt/ppc64el (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mp3splt/riscv64 (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3)
  • Migration status for mp3splt/riscv64 (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mp3splt/s390x (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3)
  • Migration status for mp3splt/s390x (2.6.2+20170630-3.3 to 2.6.2+20170630-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mtpaint/amd64 (3.50.12-1 to 3.50.12-1)
  • Migration status for mtpaint/amd64 (3.50.12-1 to 3.50.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mtpaint/arm64 (3.50.12-1 to 3.50.12-1)
  • Migration status for mtpaint/arm64 (3.50.12-1 to 3.50.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mtpaint/armhf (3.50.12-1 to 3.50.12-1)
  • Migration status for mtpaint/armhf (3.50.12-1 to 3.50.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mtpaint/i386 (3.50.12-1 to 3.50.12-1)
  • Migration status for mtpaint/i386 (3.50.12-1 to 3.50.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mtpaint/ppc64el (3.50.12-1 to 3.50.12-1)
  • Migration status for mtpaint/ppc64el (3.50.12-1 to 3.50.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mtpaint/riscv64 (3.50.12-1 to 3.50.12-1)
  • Migration status for mtpaint/riscv64 (3.50.12-1 to 3.50.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mtpaint/s390x (3.50.12-1 to 3.50.12-1)
  • Migration status for mtpaint/s390x (3.50.12-1 to 3.50.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mudita24/amd64 (1.0.3+svn13-7 to 1.0.3+svn13-7)
  • Migration status for mudita24/amd64 (1.0.3+svn13-7 to 1.0.3+svn13-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mudita24/arm64 (1.0.3+svn13-7 to 1.0.3+svn13-7)
  • Migration status for mudita24/arm64 (1.0.3+svn13-7 to 1.0.3+svn13-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mudita24/armhf (1.0.3+svn13-7 to 1.0.3+svn13-7)
  • Migration status for mudita24/armhf (1.0.3+svn13-7 to 1.0.3+svn13-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mudita24/i386 (1.0.3+svn13-7 to 1.0.3+svn13-7)
  • Migration status for mudita24/i386 (1.0.3+svn13-7 to 1.0.3+svn13-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mudita24/ppc64el (1.0.3+svn13-7 to 1.0.3+svn13-7)
  • Migration status for mudita24/ppc64el (1.0.3+svn13-7 to 1.0.3+svn13-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• mudita24/s390x (1.0.3+svn13-7 to 1.0.3+svn13-7)
  • Migration status for mudita24/s390x (1.0.3+svn13-7 to 1.0.3+svn13-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nabi/amd64 (1.0.1-2 to 1.0.1-2)
  • Migration status for nabi/amd64 (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nabi/arm64 (1.0.1-2 to 1.0.1-2)
  • Migration status for nabi/arm64 (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nabi/armhf (1.0.1-2 to 1.0.1-2)
  • Migration status for nabi/armhf (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nabi/i386 (1.0.1-2 to 1.0.1-2)
  • Migration status for nabi/i386 (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nabi/ppc64el (1.0.1-2 to 1.0.1-2)
  • Migration status for nabi/ppc64el (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nabi/s390x (1.0.1-2 to 1.0.1-2)
  • Migration status for nabi/s390x (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nanopolish/amd64 (0.14.0-1 to 0.14.0-1)
  • Migration status for nanopolish/amd64 (0.14.0-1 to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nanopolish/arm64 (0.14.0-1 to 0.14.0-1)
  • Migration status for nanopolish/arm64 (0.14.0-1 to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nanopolish/armhf (0.14.0-1 to 0.14.0-1)
  • Migration status for nanopolish/armhf (0.14.0-1 to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nanopolish/i386 (0.14.0-1 to 0.14.0-1)
  • Migration status for nanopolish/i386 (0.14.0-1 to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nanopolish/ppc64el (0.14.0-1 to 0.14.0-1)
  • Migration status for nanopolish/ppc64el (0.14.0-1 to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nanopolish/s390x (0.14.0-1 to 0.14.0-1)
  • Migration status for nanopolish/s390x (0.14.0-1 to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nat/amd64 (1:1.0-7 to 1:1.0-7)
  • Migration status for nat/amd64 (1:1.0-7 to 1:1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nat/arm64 (1:1.0-7 to 1:1.0-7)
  • Migration status for nat/arm64 (1:1.0-7 to 1:1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nat/armhf (1:1.0-7 to 1:1.0-7)
  • Migration status for nat/armhf (1:1.0-7 to 1:1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nat/i386 (1:1.0-7 to 1:1.0-7)
  • Migration status for nat/i386 (1:1.0-7 to 1:1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nat/ppc64el (1:1.0-7 to 1:1.0-7)
  • Migration status for nat/ppc64el (1:1.0-7 to 1:1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nat/riscv64 (1:1.0-7 to 1:1.0-7)
  • Migration status for nat/riscv64 (1:1.0-7 to 1:1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nat/s390x (1:1.0-7 to 1:1.0-7)
  • Migration status for nat/s390x (1:1.0-7 to 1:1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ncbi-igblast/amd64 (1.20.0-2 to 1.20.0-2)
  • Migration status for ncbi-igblast/amd64 (1.20.0-2 to 1.20.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
• ncbi-igblast/arm64 (1.20.0-2 to 1.20.0-2)
  • Migration status for ncbi-igblast/arm64 (1.20.0-2 to 1.20.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
• ncbi-igblast/armhf (1.20.0-2 to 1.20.0-2)
  • Migration status for ncbi-igblast/armhf (1.20.0-2 to 1.20.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
• ncbi-igblast/i386 (1.20.0-2 to 1.20.0-2)
  • Migration status for ncbi-igblast/i386 (1.20.0-2 to 1.20.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
• ncbi-igblast/ppc64el (1.20.0-2 to 1.20.0-2)
  • Migration status for ncbi-igblast/ppc64el (1.20.0-2 to 1.20.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
• ncbi-igblast/riscv64 (1.20.0-2 to 1.20.0-2)
  • Migration status for ncbi-igblast/riscv64 (1.20.0-2 to 1.20.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
• ncbi-igblast/s390x (1.20.0-2 to 1.20.0-2)
  • Migration status for ncbi-igblast/s390x (1.20.0-2 to 1.20.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
• ncdc/amd64 (1.23.1-1 to 1.23.1-1)
  • Migration status for ncdc/amd64 (1.23.1-1 to 1.23.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
• ncdc/arm64 (1.23.1-1 to 1.23.1-1)
  • Migration status for ncdc/arm64 (1.23.1-1 to 1.23.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
• ncdc/armhf (1.23.1-1 to 1.23.1-1)
  • Migration status for ncdc/armhf (1.23.1-1 to 1.23.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
• ncdc/i386 (1.23.1-1 to 1.23.1-1)
  • Migration status for ncdc/i386 (1.23.1-1 to 1.23.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
• ncdc/ppc64el (1.23.1-1 to 1.23.1-1)
  • Migration status for ncdc/ppc64el (1.23.1-1 to 1.23.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
• ncdc/riscv64 (1.23.1-1 to 1.23.1-1)
  • Migration status for ncdc/riscv64 (1.23.1-1 to 1.23.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
• ncdc/s390x (1.23.1-1 to 1.23.1-1)
  • Migration status for ncdc/s390x (1.23.1-1 to 1.23.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
• ncl/amd64 (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11)
  • Migration status for ncl/amd64 (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ncl/arm64 (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11)
  • Migration status for ncl/arm64 (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ncl/armhf (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11)
  • Migration status for ncl/armhf (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ncl/i386 (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11)
  • Migration status for ncl/i386 (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ncl/ppc64el (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11)
  • Migration status for ncl/ppc64el (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ncl/riscv64 (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11)
  • Migration status for ncl/riscv64 (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ncl/s390x (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11)
  • Migration status for ncl/s390x (6.6.2.dfsg.1-11 to 6.6.2.dfsg.1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nedit/amd64 (1:5.7-5 to 1:5.7-5)
  • Migration status for nedit/amd64 (1:5.7-5 to 1:5.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
• nedit/arm64 (1:5.7-5 to 1:5.7-5)
  • Migration status for nedit/arm64 (1:5.7-5 to 1:5.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
• nedit/armhf (1:5.7-5 to 1:5.7-5)
  • Migration status for nedit/armhf (1:5.7-5 to 1:5.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
• nedit/i386 (1:5.7-5 to 1:5.7-5)
  • Migration status for nedit/i386 (1:5.7-5 to 1:5.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
• nedit/ppc64el (1:5.7-5 to 1:5.7-5)
  • Migration status for nedit/ppc64el (1:5.7-5 to 1:5.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
• nedit/riscv64 (1:5.7-5 to 1:5.7-5)
  • Migration status for nedit/riscv64 (1:5.7-5 to 1:5.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
• nedit/s390x (1:5.7-5 to 1:5.7-5)
  • Migration status for nedit/s390x (1:5.7-5 to 1:5.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
• netkit-ftp-ssl/amd64 (0.17.34+really0.17-2 to 0.17.34+really0.17-2)
  • Migration status for netkit-ftp-ssl/amd64 (0.17.34+really0.17-2 to 0.17.34+really0.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-ftp-ssl/arm64 (0.17.34+really0.17-2 to 0.17.34+really0.17-2)
  • Migration status for netkit-ftp-ssl/arm64 (0.17.34+really0.17-2 to 0.17.34+really0.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-ftp-ssl/armhf (0.17.34+really0.17-2 to 0.17.34+really0.17-2)
  • Migration status for netkit-ftp-ssl/armhf (0.17.34+really0.17-2 to 0.17.34+really0.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-ftp-ssl/i386 (0.17.34+really0.17-2 to 0.17.34+really0.17-2)
  • Migration status for netkit-ftp-ssl/i386 (0.17.34+really0.17-2 to 0.17.34+really0.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-ftp-ssl/ppc64el (0.17.34+really0.17-2 to 0.17.34+really0.17-2)
  • Migration status for netkit-ftp-ssl/ppc64el (0.17.34+really0.17-2 to 0.17.34+really0.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-ftp-ssl/riscv64 (0.17.34+really0.17-2 to 0.17.34+really0.17-2)
  • Migration status for netkit-ftp-ssl/riscv64 (0.17.34+really0.17-2 to 0.17.34+really0.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-ftp-ssl/s390x (0.17.34+really0.17-2 to 0.17.34+really0.17-2)
  • Migration status for netkit-ftp-ssl/s390x (0.17.34+really0.17-2 to 0.17.34+really0.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-telnet-ssl/amd64 (0.17.41+really0.17-6 to 0.17.41+really0.17-6)
  • Migration status for netkit-telnet-ssl/amd64 (0.17.41+really0.17-6 to 0.17.41+really0.17-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-telnet-ssl/arm64 (0.17.41+really0.17-6 to 0.17.41+really0.17-6)
  • Migration status for netkit-telnet-ssl/arm64 (0.17.41+really0.17-6 to 0.17.41+really0.17-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-telnet-ssl/armhf (0.17.41+really0.17-6 to 0.17.41+really0.17-6)
  • Migration status for netkit-telnet-ssl/armhf (0.17.41+really0.17-6 to 0.17.41+really0.17-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-telnet-ssl/i386 (0.17.41+really0.17-6 to 0.17.41+really0.17-6)
  • Migration status for netkit-telnet-ssl/i386 (0.17.41+really0.17-6 to 0.17.41+really0.17-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-telnet-ssl/ppc64el (0.17.41+really0.17-6 to 0.17.41+really0.17-6)
  • Migration status for netkit-telnet-ssl/ppc64el (0.17.41+really0.17-6 to 0.17.41+really0.17-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-telnet-ssl/riscv64 (0.17.41+really0.17-6 to 0.17.41+really0.17-6)
  • Migration status for netkit-telnet-ssl/riscv64 (0.17.41+really0.17-6 to 0.17.41+really0.17-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netkit-telnet-ssl/s390x (0.17.41+really0.17-6 to 0.17.41+really0.17-6)
  • Migration status for netkit-telnet-ssl/s390x (0.17.41+really0.17-6 to 0.17.41+really0.17-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netsniff-ng/amd64 (0.6.9-1 to 0.6.9-1)
  • Migration status for netsniff-ng/amd64 (0.6.9-1 to 0.6.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netsniff-ng/arm64 (0.6.9-1 to 0.6.9-1)
  • Migration status for netsniff-ng/arm64 (0.6.9-1 to 0.6.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netsniff-ng/armhf (0.6.9-1 to 0.6.9-1)
  • Migration status for netsniff-ng/armhf (0.6.9-1 to 0.6.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netsniff-ng/i386 (0.6.9-1 to 0.6.9-1)
  • Migration status for netsniff-ng/i386 (0.6.9-1 to 0.6.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netsniff-ng/ppc64el (0.6.9-1 to 0.6.9-1)
  • Migration status for netsniff-ng/ppc64el (0.6.9-1 to 0.6.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netsniff-ng/riscv64 (0.6.9-1 to 0.6.9-1)
  • Migration status for netsniff-ng/riscv64 (0.6.9-1 to 0.6.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• netsniff-ng/s390x (0.6.9-1 to 0.6.9-1)
  • Migration status for netsniff-ng/s390x (0.6.9-1 to 0.6.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• newlisp/amd64 (10.7.5-2 to 10.7.5-2)
  • Migration status for newlisp/amd64 (10.7.5-2 to 10.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• newlisp/arm64 (10.7.5-2 to 10.7.5-2)
  • Migration status for newlisp/arm64 (10.7.5-2 to 10.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• newlisp/armhf (10.7.5-2 to 10.7.5-2)
  • Migration status for newlisp/armhf (10.7.5-2 to 10.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• newlisp/i386 (10.7.5-2 to 10.7.5-2)
  • Migration status for newlisp/i386 (10.7.5-2 to 10.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• newlisp/ppc64el (10.7.5-2 to 10.7.5-2)
  • Migration status for newlisp/ppc64el (10.7.5-2 to 10.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• newlisp/riscv64 (10.7.5-2 to 10.7.5-2)
  • Migration status for newlisp/riscv64 (10.7.5-2 to 10.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• newlisp/s390x (10.7.5-2 to 10.7.5-2)
  • Migration status for newlisp/s390x (10.7.5-2 to 10.7.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nextpnr/amd64 (0.7-1 to 0.7-1)
  • Migration status for nextpnr/amd64 (0.7-1 to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nextpnr/arm64 (0.7-1 to 0.7-1)
  • Migration status for nextpnr/arm64 (0.7-1 to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nextpnr/armhf (0.7-1 to 0.7-1)
  • Migration status for nextpnr/armhf (0.7-1 to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nextpnr/i386 (0.7-1 to 0.7-1)
  • Migration status for nextpnr/i386 (0.7-1 to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nextpnr/ppc64el (0.7-1 to 0.7-1)
  • Migration status for nextpnr/ppc64el (0.7-1 to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nextpnr/riscv64 (0.7-1 to 0.7-1)
  • Migration status for nextpnr/riscv64 (0.7-1 to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nextpnr/s390x (0.7-1 to 0.7-1)
  • Migration status for nextpnr/s390x (0.7-1 to 0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ng/amd64 (1.5~beta1-14 to 1.5~beta1-14)
  • Migration status for ng/amd64 (1.5~beta1-14 to 1.5~beta1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ng/arm64 (1.5~beta1-14 to 1.5~beta1-14)
  • Migration status for ng/arm64 (1.5~beta1-14 to 1.5~beta1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ng/armhf (1.5~beta1-14 to 1.5~beta1-14)
  • Migration status for ng/armhf (1.5~beta1-14 to 1.5~beta1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ng/i386 (1.5~beta1-14 to 1.5~beta1-14)
  • Migration status for ng/i386 (1.5~beta1-14 to 1.5~beta1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ng/ppc64el (1.5~beta1-14 to 1.5~beta1-14)
  • Migration status for ng/ppc64el (1.5~beta1-14 to 1.5~beta1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ng/riscv64 (1.5~beta1-14 to 1.5~beta1-14)
  • Migration status for ng/riscv64 (1.5~beta1-14 to 1.5~beta1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ng/s390x (1.5~beta1-14 to 1.5~beta1-14)
  • Migration status for ng/s390x (1.5~beta1-14 to 1.5~beta1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngetty/amd64 (1.1-13 to 1.1-13)
  • Migration status for ngetty/amd64 (1.1-13 to 1.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngetty/arm64 (1.1-13 to 1.1-13)
  • Migration status for ngetty/arm64 (1.1-13 to 1.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngetty/armhf (1.1-13 to 1.1-13)
  • Migration status for ngetty/armhf (1.1-13 to 1.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngetty/i386 (1.1-13 to 1.1-13)
  • Migration status for ngetty/i386 (1.1-13 to 1.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngetty/ppc64el (1.1-13 to 1.1-13)
  • Migration status for ngetty/ppc64el (1.1-13 to 1.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngetty/riscv64 (1.1-13 to 1.1-13)
  • Migration status for ngetty/riscv64 (1.1-13 to 1.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngetty/s390x (1.1-13 to 1.1-13)
  • Migration status for ngetty/s390x (1.1-13 to 1.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngraph-gtk/amd64 (6.09.09-1 to 6.09.09-1)
  • Migration status for ngraph-gtk/amd64 (6.09.09-1 to 6.09.09-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngraph-gtk/arm64 (6.09.09-1 to 6.09.09-1)
  • Migration status for ngraph-gtk/arm64 (6.09.09-1 to 6.09.09-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngraph-gtk/armhf (6.09.09-1 to 6.09.09-1)
  • Migration status for ngraph-gtk/armhf (6.09.09-1 to 6.09.09-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngraph-gtk/i386 (6.09.09-1 to 6.09.09-1)
  • Migration status for ngraph-gtk/i386 (6.09.09-1 to 6.09.09-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngraph-gtk/ppc64el (6.09.09-1 to 6.09.09-1)
  • Migration status for ngraph-gtk/ppc64el (6.09.09-1 to 6.09.09-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngraph-gtk/riscv64 (6.09.09-1 to 6.09.09-1)
  • Migration status for ngraph-gtk/riscv64 (6.09.09-1 to 6.09.09-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ngraph-gtk/s390x (6.09.09-1 to 6.09.09-1)
  • Migration status for ngraph-gtk/s390x (6.09.09-1 to 6.09.09-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ninvaders/amd64 (0.1.1-5 to 0.1.1-5)
  • Migration status for ninvaders/amd64 (0.1.1-5 to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ninvaders/arm64 (0.1.1-5 to 0.1.1-5)
  • Migration status for ninvaders/arm64 (0.1.1-5 to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ninvaders/armhf (0.1.1-5 to 0.1.1-5)
  • Migration status for ninvaders/armhf (0.1.1-5 to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ninvaders/i386 (0.1.1-5 to 0.1.1-5)
  • Migration status for ninvaders/i386 (0.1.1-5 to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ninvaders/ppc64el (0.1.1-5 to 0.1.1-5)
  • Migration status for ninvaders/ppc64el (0.1.1-5 to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ninvaders/riscv64 (0.1.1-5 to 0.1.1-5)
  • Migration status for ninvaders/riscv64 (0.1.1-5 to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ninvaders/s390x (0.1.1-5 to 0.1.1-5)
  • Migration status for ninvaders/s390x (0.1.1-5 to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nitpic/amd64 (0.1-21 to 0.1-21)
  • Migration status for nitpic/amd64 (0.1-21 to 0.1-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nitpic/arm64 (0.1-21 to 0.1-21)
  • Migration status for nitpic/arm64 (0.1-21 to 0.1-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nitpic/armhf (0.1-21 to 0.1-21)
  • Migration status for nitpic/armhf (0.1-21 to 0.1-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nitpic/i386 (0.1-21 to 0.1-21)
  • Migration status for nitpic/i386 (0.1-21 to 0.1-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nitpic/ppc64el (0.1-21 to 0.1-21)
  • Migration status for nitpic/ppc64el (0.1-21 to 0.1-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nitpic/riscv64 (0.1-21 to 0.1-21)
  • Migration status for nitpic/riscv64 (0.1-21 to 0.1-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nitpic/s390x (0.1-21 to 0.1-21)
  • Migration status for nitpic/s390x (0.1-21 to 0.1-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nmzmail/amd64 (1.1-5 to 1.1-5)
  • Migration status for nmzmail/amd64 (1.1-5 to 1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nmzmail/arm64 (1.1-5 to 1.1-5)
  • Migration status for nmzmail/arm64 (1.1-5 to 1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nmzmail/armhf (1.1-5 to 1.1-5)
  • Migration status for nmzmail/armhf (1.1-5 to 1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nmzmail/i386 (1.1-5 to 1.1-5)
  • Migration status for nmzmail/i386 (1.1-5 to 1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nmzmail/ppc64el (1.1-5 to 1.1-5)
  • Migration status for nmzmail/ppc64el (1.1-5 to 1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nmzmail/riscv64 (1.1-5 to 1.1-5)
  • Migration status for nmzmail/riscv64 (1.1-5 to 1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nmzmail/s390x (1.1-5 to 1.1-5)
  • Migration status for nmzmail/s390x (1.1-5 to 1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nn/amd64 (6.7.3-16 to 6.7.3-16)
  • Migration status for nn/amd64 (6.7.3-16 to 6.7.3-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nn/arm64 (6.7.3-16 to 6.7.3-16)
  • Migration status for nn/arm64 (6.7.3-16 to 6.7.3-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nn/armhf (6.7.3-16 to 6.7.3-16)
  • Migration status for nn/armhf (6.7.3-16 to 6.7.3-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nn/i386 (6.7.3-16 to 6.7.3-16)
  • Migration status for nn/i386 (6.7.3-16 to 6.7.3-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nn/ppc64el (6.7.3-16 to 6.7.3-16)
  • Migration status for nn/ppc64el (6.7.3-16 to 6.7.3-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nn/riscv64 (6.7.3-16 to 6.7.3-16)
  • Migration status for nn/riscv64 (6.7.3-16 to 6.7.3-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nn/s390x (6.7.3-16 to 6.7.3-16)
  • Migration status for nn/s390x (6.7.3-16 to 6.7.3-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notify-osd/amd64 (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2)
  • Migration status for notify-osd/amd64 (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notify-osd/arm64 (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2)
  • Migration status for notify-osd/arm64 (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notify-osd/armhf (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2)
  • Migration status for notify-osd/armhf (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notify-osd/i386 (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2)
  • Migration status for notify-osd/i386 (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notify-osd/ppc64el (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2)
  • Migration status for notify-osd/ppc64el (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notify-osd/riscv64 (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2)
  • Migration status for notify-osd/riscv64 (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notify-osd/s390x (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2)
  • Migration status for notify-osd/s390x (0.9.35+20.04.20191129-2 to 0.9.35+20.04.20191129-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notion/amd64 (4.0.3+dfsg-1 to 4.0.3+dfsg-1)
  • Migration status for notion/amd64 (4.0.3+dfsg-1 to 4.0.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notion/arm64 (4.0.3+dfsg-1 to 4.0.3+dfsg-1)
  • Migration status for notion/arm64 (4.0.3+dfsg-1 to 4.0.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notion/armhf (4.0.3+dfsg-1 to 4.0.3+dfsg-1)
  • Migration status for notion/armhf (4.0.3+dfsg-1 to 4.0.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notion/i386 (4.0.3+dfsg-1 to 4.0.3+dfsg-1)
  • Migration status for notion/i386 (4.0.3+dfsg-1 to 4.0.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notion/ppc64el (4.0.3+dfsg-1 to 4.0.3+dfsg-1)
  • Migration status for notion/ppc64el (4.0.3+dfsg-1 to 4.0.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notion/riscv64 (4.0.3+dfsg-1 to 4.0.3+dfsg-1)
  • Migration status for notion/riscv64 (4.0.3+dfsg-1 to 4.0.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• notion/s390x (4.0.3+dfsg-1 to 4.0.3+dfsg-1)
  • Migration status for notion/s390x (4.0.3+dfsg-1 to 4.0.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nrn-mod2c/amd64 (8.2.2-1 to 8.2.2-1)
  • Migration status for nrn-mod2c/amd64 (8.2.2-1 to 8.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nrn-mod2c/arm64 (8.2.2-1 to 8.2.2-1)
  • Migration status for nrn-mod2c/arm64 (8.2.2-1 to 8.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nrn-mod2c/armhf (8.2.2-1 to 8.2.2-1)
  • Migration status for nrn-mod2c/armhf (8.2.2-1 to 8.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nrn-mod2c/i386 (8.2.2-1 to 8.2.2-1)
  • Migration status for nrn-mod2c/i386 (8.2.2-1 to 8.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nrn-mod2c/ppc64el (8.2.2-1 to 8.2.2-1)
  • Migration status for nrn-mod2c/ppc64el (8.2.2-1 to 8.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nrn-mod2c/riscv64 (8.2.2-1 to 8.2.2-1)
  • Migration status for nrn-mod2c/riscv64 (8.2.2-1 to 8.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nrn-mod2c/s390x (8.2.2-1 to 8.2.2-1)
  • Migration status for nrn-mod2c/s390x (8.2.2-1 to 8.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nvi/amd64 (1.81.6-23 to 1.81.6-23)
  • Migration status for nvi/amd64 (1.81.6-23 to 1.81.6-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nvi/arm64 (1.81.6-23 to 1.81.6-23)
  • Migration status for nvi/arm64 (1.81.6-23 to 1.81.6-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nvi/armhf (1.81.6-23 to 1.81.6-23)
  • Migration status for nvi/armhf (1.81.6-23 to 1.81.6-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nvi/i386 (1.81.6-23 to 1.81.6-23)
  • Migration status for nvi/i386 (1.81.6-23 to 1.81.6-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nvi/ppc64el (1.81.6-23 to 1.81.6-23)
  • Migration status for nvi/ppc64el (1.81.6-23 to 1.81.6-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nvi/riscv64 (1.81.6-23 to 1.81.6-23)
  • Migration status for nvi/riscv64 (1.81.6-23 to 1.81.6-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nvi/s390x (1.81.6-23 to 1.81.6-23)
  • Migration status for nvi/s390x (1.81.6-23 to 1.81.6-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nwchem/amd64 (7.2.3-10 to 7.2.3-10)
  • Migration status for nwchem/amd64 (7.2.3-10 to 7.2.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nwchem/arm64 (7.2.3-10 to 7.2.3-10)
  • Migration status for nwchem/arm64 (7.2.3-10 to 7.2.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nwchem/armhf (7.2.3-10 to 7.2.3-10)
  • Migration status for nwchem/armhf (7.2.3-10 to 7.2.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nwchem/i386 (7.2.3-10 to 7.2.3-10)
  • Migration status for nwchem/i386 (7.2.3-10 to 7.2.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nwchem/ppc64el (7.2.3-10 to 7.2.3-10)
  • Migration status for nwchem/ppc64el (7.2.3-10 to 7.2.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nwchem/riscv64 (7.2.3-10 to 7.2.3-10)
  • Migration status for nwchem/riscv64 (7.2.3-10 to 7.2.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• nwchem/s390x (7.2.3-10 to 7.2.3-10)
  • Migration status for nwchem/s390x (7.2.3-10 to 7.2.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• oaklisp/amd64 (1.3.7-4 to 1.3.7-4)
  • Migration status for oaklisp/amd64 (1.3.7-4 to 1.3.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• oaklisp/arm64 (1.3.7-4 to 1.3.7-4)
  • Migration status for oaklisp/arm64 (1.3.7-4 to 1.3.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• oaklisp/armhf (1.3.7-4 to 1.3.7-4)
  • Migration status for oaklisp/armhf (1.3.7-4 to 1.3.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• oaklisp/i386 (1.3.7-4 to 1.3.7-4)
  • Migration status for oaklisp/i386 (1.3.7-4 to 1.3.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• oaklisp/ppc64el (1.3.7-4 to 1.3.7-4)
  • Migration status for oaklisp/ppc64el (1.3.7-4 to 1.3.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• oaklisp/riscv64 (1.3.7-4 to 1.3.7-4)
  • Migration status for oaklisp/riscv64 (1.3.7-4 to 1.3.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• oaklisp/s390x (1.3.7-4 to 1.3.7-4)
  • Migration status for oaklisp/s390x (1.3.7-4 to 1.3.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• opendmarc/amd64 (1.4.2-5 to 1.4.2-5)
  • Migration status for opendmarc/amd64 (1.4.2-5 to 1.4.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• opendmarc/arm64 (1.4.2-5 to 1.4.2-5)
  • Migration status for opendmarc/arm64 (1.4.2-5 to 1.4.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• opendmarc/armhf (1.4.2-5 to 1.4.2-5)
  • Migration status for opendmarc/armhf (1.4.2-5 to 1.4.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• opendmarc/i386 (1.4.2-5 to 1.4.2-5)
  • Migration status for opendmarc/i386 (1.4.2-5 to 1.4.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• opendmarc/ppc64el (1.4.2-5 to 1.4.2-5)
  • Migration status for opendmarc/ppc64el (1.4.2-5 to 1.4.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• opendmarc/riscv64 (1.4.2-5 to 1.4.2-5)
  • Migration status for opendmarc/riscv64 (1.4.2-5 to 1.4.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• opendmarc/s390x (1.4.2-5 to 1.4.2-5)
  • Migration status for opendmarc/s390x (1.4.2-5 to 1.4.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openfoam/amd64 (1912.200626-3 to 1912.200626-3)
  • Migration status for openfoam/amd64 (1912.200626-3 to 1912.200626-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openfoam/arm64 (1912.200626-3 to 1912.200626-3)
  • Migration status for openfoam/arm64 (1912.200626-3 to 1912.200626-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openfoam/armhf (1912.200626-3 to 1912.200626-3)
  • Migration status for openfoam/armhf (1912.200626-3 to 1912.200626-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openfoam/i386 (1912.200626-3 to 1912.200626-3)
  • Migration status for openfoam/i386 (1912.200626-3 to 1912.200626-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openfoam/ppc64el (1912.200626-3 to 1912.200626-3)
  • Migration status for openfoam/ppc64el (1912.200626-3 to 1912.200626-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openfoam/riscv64 (1912.200626-3 to 1912.200626-3)
  • Migration status for openfoam/riscv64 (1912.200626-3 to 1912.200626-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openfoam/s390x (1912.200626-3 to 1912.200626-3)
  • Migration status for openfoam/s390x (1912.200626-3 to 1912.200626-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• opengnb/amd64 (1.6.0.a-2 to 1.6.0.a-2)
  • Migration status for opengnb/amd64 (1.6.0.a-2 to 1.6.0.a-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: opengnb/amd64 miniupnpc (not considered)
    • Invalidated by dependency
• opengnb/arm64 (1.6.0.a-2 to 1.6.0.a-2)
  • Migration status for opengnb/arm64 (1.6.0.a-2 to 1.6.0.a-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: opengnb/arm64 miniupnpc (not considered)
    • Invalidated by dependency
• opengnb/armhf (1.6.0.a-2 to 1.6.0.a-2)
  • Migration status for opengnb/armhf (1.6.0.a-2 to 1.6.0.a-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: opengnb/armhf miniupnpc (not considered)
    • Invalidated by dependency
• opengnb/i386 (1.6.0.a-2 to 1.6.0.a-2)
  • Migration status for opengnb/i386 (1.6.0.a-2 to 1.6.0.a-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: opengnb/i386 miniupnpc (not considered)
    • Invalidated by dependency
• opengnb/ppc64el (1.6.0.a-2 to 1.6.0.a-2)
  • Migration status for opengnb/ppc64el (1.6.0.a-2 to 1.6.0.a-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: opengnb/ppc64el miniupnpc (not considered)
    • Invalidated by dependency
• opengnb/riscv64 (1.6.0.a-2 to 1.6.0.a-2)
  • Migration status for opengnb/riscv64 (1.6.0.a-2 to 1.6.0.a-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: opengnb/riscv64 miniupnpc (not considered)
    • Invalidated by dependency
• opengnb/s390x (1.6.0.a-2 to 1.6.0.a-2)
  • Migration status for opengnb/s390x (1.6.0.a-2 to 1.6.0.a-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: opengnb/s390x miniupnpc (not considered)
    • Invalidated by dependency
• openvpn-auth-ldap/amd64 (2.0.4-4 to 2.0.4-4)
  • Migration status for openvpn-auth-ldap/amd64 (2.0.4-4 to 2.0.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openvpn-auth-ldap/arm64 (2.0.4-4 to 2.0.4-4)
  • Migration status for openvpn-auth-ldap/arm64 (2.0.4-4 to 2.0.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openvpn-auth-ldap/armhf (2.0.4-4 to 2.0.4-4)
  • Migration status for openvpn-auth-ldap/armhf (2.0.4-4 to 2.0.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openvpn-auth-ldap/i386 (2.0.4-4 to 2.0.4-4)
  • Migration status for openvpn-auth-ldap/i386 (2.0.4-4 to 2.0.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openvpn-auth-ldap/ppc64el (2.0.4-4 to 2.0.4-4)
  • Migration status for openvpn-auth-ldap/ppc64el (2.0.4-4 to 2.0.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openvpn-auth-ldap/riscv64 (2.0.4-4 to 2.0.4-4)
  • Migration status for openvpn-auth-ldap/riscv64 (2.0.4-4 to 2.0.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• openvpn-auth-ldap/s390x (2.0.4-4 to 2.0.4-4)
  • Migration status for openvpn-auth-ldap/s390x (2.0.4-4 to 2.0.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osdlyrics/amd64 (0.5.15+dfsg-2 to 0.5.15+dfsg-2)
  • Migration status for osdlyrics/amd64 (0.5.15+dfsg-2 to 0.5.15+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osdlyrics/arm64 (0.5.15+dfsg-2 to 0.5.15+dfsg-2)
  • Migration status for osdlyrics/arm64 (0.5.15+dfsg-2 to 0.5.15+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osdlyrics/armhf (0.5.15+dfsg-2 to 0.5.15+dfsg-2)
  • Migration status for osdlyrics/armhf (0.5.15+dfsg-2 to 0.5.15+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osdlyrics/i386 (0.5.15+dfsg-2 to 0.5.15+dfsg-2)
  • Migration status for osdlyrics/i386 (0.5.15+dfsg-2 to 0.5.15+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osdlyrics/ppc64el (0.5.15+dfsg-2 to 0.5.15+dfsg-2)
  • Migration status for osdlyrics/ppc64el (0.5.15+dfsg-2 to 0.5.15+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osdlyrics/s390x (0.5.15+dfsg-2 to 0.5.15+dfsg-2)
  • Migration status for osdlyrics/s390x (0.5.15+dfsg-2 to 0.5.15+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osmo/amd64 (0.4.4-2.1 to 0.4.4-2.1)
  • Migration status for osmo/amd64 (0.4.4-2.1 to 0.4.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osmo/arm64 (0.4.4-2.1 to 0.4.4-2.1)
  • Migration status for osmo/arm64 (0.4.4-2.1 to 0.4.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osmo/armhf (0.4.4-2.1 to 0.4.4-2.1)
  • Migration status for osmo/armhf (0.4.4-2.1 to 0.4.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osmo/i386 (0.4.4-2.1 to 0.4.4-2.1)
  • Migration status for osmo/i386 (0.4.4-2.1 to 0.4.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osmo/ppc64el (0.4.4-2.1 to 0.4.4-2.1)
  • Migration status for osmo/ppc64el (0.4.4-2.1 to 0.4.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• osmo/s390x (0.4.4-2.1 to 0.4.4-2.1)
  • Migration status for osmo/s390x (0.4.4-2.1 to 0.4.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• otp/amd64 (1:1.2.2-5 to 1:1.2.2-5)
  • Migration status for otp/amd64 (1:1.2.2-5 to 1:1.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• otp/arm64 (1:1.2.2-5 to 1:1.2.2-5)
  • Migration status for otp/arm64 (1:1.2.2-5 to 1:1.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• otp/armhf (1:1.2.2-5 to 1:1.2.2-5)
  • Migration status for otp/armhf (1:1.2.2-5 to 1:1.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• otp/i386 (1:1.2.2-5 to 1:1.2.2-5)
  • Migration status for otp/i386 (1:1.2.2-5 to 1:1.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• otp/ppc64el (1:1.2.2-5 to 1:1.2.2-5)
  • Migration status for otp/ppc64el (1:1.2.2-5 to 1:1.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• otp/riscv64 (1:1.2.2-5 to 1:1.2.2-5)
  • Migration status for otp/riscv64 (1:1.2.2-5 to 1:1.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• otp/s390x (1:1.2.2-5 to 1:1.2.2-5)
  • Migration status for otp/s390x (1:1.2.2-5 to 1:1.2.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paps/amd64 (0.6.8-7.2 to 0.6.8-7.2)
  • Migration status for paps/amd64 (0.6.8-7.2 to 0.6.8-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paps/arm64 (0.6.8-7.2 to 0.6.8-7.2)
  • Migration status for paps/arm64 (0.6.8-7.2 to 0.6.8-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paps/armhf (0.6.8-7.2 to 0.6.8-7.2)
  • Migration status for paps/armhf (0.6.8-7.2 to 0.6.8-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paps/i386 (0.6.8-7.2 to 0.6.8-7.2)
  • Migration status for paps/i386 (0.6.8-7.2 to 0.6.8-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paps/ppc64el (0.6.8-7.2 to 0.6.8-7.2)
  • Migration status for paps/ppc64el (0.6.8-7.2 to 0.6.8-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paps/s390x (0.6.8-7.2 to 0.6.8-7.2)
  • Migration status for paps/s390x (0.6.8-7.2 to 0.6.8-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paraglob/amd64 (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/amd64 (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paraglob/arm64 (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/arm64 (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paraglob/armhf (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/armhf (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paraglob/i386 (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/i386 (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paraglob/ppc64el (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/ppc64el (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paraglob/riscv64 (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/riscv64 (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• paraglob/s390x (0.6.0-1 to 0.6.0-1)
  • Migration status for paraglob/s390x (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-ekext/amd64 (0.1.1-6 to 0.1.1-6)
  • Migration status for pd-ekext/amd64 (0.1.1-6 to 0.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-ekext/arm64 (0.1.1-6 to 0.1.1-6)
  • Migration status for pd-ekext/arm64 (0.1.1-6 to 0.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-ekext/armhf (0.1.1-6 to 0.1.1-6)
  • Migration status for pd-ekext/armhf (0.1.1-6 to 0.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-ekext/i386 (0.1.1-6 to 0.1.1-6)
  • Migration status for pd-ekext/i386 (0.1.1-6 to 0.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-ekext/ppc64el (0.1.1-6 to 0.1.1-6)
  • Migration status for pd-ekext/ppc64el (0.1.1-6 to 0.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-ekext/riscv64 (0.1.1-6 to 0.1.1-6)
  • Migration status for pd-ekext/riscv64 (0.1.1-6 to 0.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-ekext/s390x (0.1.1-6 to 0.1.1-6)
  • Migration status for pd-ekext/s390x (0.1.1-6 to 0.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-fftease/amd64 (3.0.1-7 to 3.0.1-7)
  • Migration status for pd-fftease/amd64 (3.0.1-7 to 3.0.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-fftease/arm64 (3.0.1-7 to 3.0.1-7)
  • Migration status for pd-fftease/arm64 (3.0.1-7 to 3.0.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-fftease/armhf (3.0.1-7 to 3.0.1-7)
  • Migration status for pd-fftease/armhf (3.0.1-7 to 3.0.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-fftease/i386 (3.0.1-7 to 3.0.1-7)
  • Migration status for pd-fftease/i386 (3.0.1-7 to 3.0.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-fftease/ppc64el (3.0.1-7 to 3.0.1-7)
  • Migration status for pd-fftease/ppc64el (3.0.1-7 to 3.0.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-fftease/riscv64 (3.0.1-7 to 3.0.1-7)
  • Migration status for pd-fftease/riscv64 (3.0.1-7 to 3.0.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pd-fftease/s390x (3.0.1-7 to 3.0.1-7)
  • Migration status for pd-fftease/s390x (3.0.1-7 to 3.0.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• penguin-command/amd64 (1.6.11-4 to 1.6.11-4)
  • Migration status for penguin-command/amd64 (1.6.11-4 to 1.6.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• penguin-command/arm64 (1.6.11-4 to 1.6.11-4)
  • Migration status for penguin-command/arm64 (1.6.11-4 to 1.6.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• penguin-command/armhf (1.6.11-4 to 1.6.11-4)
  • Migration status for penguin-command/armhf (1.6.11-4 to 1.6.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• penguin-command/i386 (1.6.11-4 to 1.6.11-4)
  • Migration status for penguin-command/i386 (1.6.11-4 to 1.6.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• penguin-command/ppc64el (1.6.11-4 to 1.6.11-4)
  • Migration status for penguin-command/ppc64el (1.6.11-4 to 1.6.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• penguin-command/riscv64 (1.6.11-4 to 1.6.11-4)
  • Migration status for penguin-command/riscv64 (1.6.11-4 to 1.6.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• penguin-command/s390x (1.6.11-4 to 1.6.11-4)
  • Migration status for penguin-command/s390x (1.6.11-4 to 1.6.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• petsc/armhf (3.22.5+dfsg1-2 to 3.22.5+dfsg1-2)
  • Migration status for petsc/armhf (3.22.5+dfsg1-2 to 3.22.5+dfsg1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: petsc/armhf mpich (not considered)
    • Invalidated by dependency
• petsc/i386 (3.22.5+dfsg1-2 to 3.22.5+dfsg1-2)
  • Migration status for petsc/i386 (3.22.5+dfsg1-2 to 3.22.5+dfsg1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: petsc/i386 mpich (not considered)
    • Invalidated by dependency
• pgn2web/amd64 (0.4-3.1 to 0.4-3.1)
  • Migration status for pgn2web/amd64 (0.4-3.1 to 0.4-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pgn2web/arm64 (0.4-3.1 to 0.4-3.1)
  • Migration status for pgn2web/arm64 (0.4-3.1 to 0.4-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pgn2web/armhf (0.4-3.1 to 0.4-3.1)
  • Migration status for pgn2web/armhf (0.4-3.1 to 0.4-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pgn2web/i386 (0.4-3.1 to 0.4-3.1)
  • Migration status for pgn2web/i386 (0.4-3.1 to 0.4-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pgn2web/ppc64el (0.4-3.1 to 0.4-3.1)
  • Migration status for pgn2web/ppc64el (0.4-3.1 to 0.4-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pgn2web/s390x (0.4-3.1 to 0.4-3.1)
  • Migration status for pgn2web/s390x (0.4-3.1 to 0.4-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• phlipple/amd64 (0.8.5-5.1 to 0.8.5-5.1)
  • Migration status for phlipple/amd64 (0.8.5-5.1 to 0.8.5-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• phlipple/arm64 (0.8.5-5.1 to 0.8.5-5.1)
  • Migration status for phlipple/arm64 (0.8.5-5.1 to 0.8.5-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• phlipple/armhf (0.8.5-5.1 to 0.8.5-5.1)
  • Migration status for phlipple/armhf (0.8.5-5.1 to 0.8.5-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• phlipple/i386 (0.8.5-5.1 to 0.8.5-5.1)
  • Migration status for phlipple/i386 (0.8.5-5.1 to 0.8.5-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• phlipple/ppc64el (0.8.5-5.1 to 0.8.5-5.1)
  • Migration status for phlipple/ppc64el (0.8.5-5.1 to 0.8.5-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• phlipple/s390x (0.8.5-5.1 to 0.8.5-5.1)
  • Migration status for phlipple/s390x (0.8.5-5.1 to 0.8.5-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-pecl-http/amd64 (4.2.6-3 to 4.2.6-3)
  • Migration status for php-pecl-http/amd64 (4.2.6-3 to 4.2.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-pecl-http/arm64 (4.2.6-3 to 4.2.6-3)
  • Migration status for php-pecl-http/arm64 (4.2.6-3 to 4.2.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-pecl-http/armhf (4.2.6-3 to 4.2.6-3)
  • Migration status for php-pecl-http/armhf (4.2.6-3 to 4.2.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-pecl-http/i386 (4.2.6-3 to 4.2.6-3)
  • Migration status for php-pecl-http/i386 (4.2.6-3 to 4.2.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-pecl-http/ppc64el (4.2.6-3 to 4.2.6-3)
  • Migration status for php-pecl-http/ppc64el (4.2.6-3 to 4.2.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-pecl-http/riscv64 (4.2.6-3 to 4.2.6-3)
  • Migration status for php-pecl-http/riscv64 (4.2.6-3 to 4.2.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-pecl-http/s390x (4.2.6-3 to 4.2.6-3)
  • Migration status for php-pecl-http/s390x (4.2.6-3 to 4.2.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-zmq/amd64 (1.1.3-30 to 1.1.3-30)
  • Migration status for php-zmq/amd64 (1.1.3-30 to 1.1.3-30): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-zmq/arm64 (1.1.3-30 to 1.1.3-30)
  • Migration status for php-zmq/arm64 (1.1.3-30 to 1.1.3-30): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-zmq/armhf (1.1.3-30 to 1.1.3-30)
  • Migration status for php-zmq/armhf (1.1.3-30 to 1.1.3-30): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-zmq/i386 (1.1.3-30 to 1.1.3-30)
  • Migration status for php-zmq/i386 (1.1.3-30 to 1.1.3-30): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-zmq/ppc64el (1.1.3-30 to 1.1.3-30)
  • Migration status for php-zmq/ppc64el (1.1.3-30 to 1.1.3-30): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-zmq/riscv64 (1.1.3-30 to 1.1.3-30)
  • Migration status for php-zmq/riscv64 (1.1.3-30 to 1.1.3-30): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• php-zmq/s390x (1.1.3-30 to 1.1.3-30)
  • Migration status for php-zmq/s390x (1.1.3-30 to 1.1.3-30): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pigpio/amd64 (1.78-1.1 to 1.78-1.1)
  • Migration status for pigpio/amd64 (1.78-1.1 to 1.78-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
• pigpio/arm64 (1.78-1.1 to 1.78-1.1)
  • Migration status for pigpio/arm64 (1.78-1.1 to 1.78-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
• pigpio/armhf (1.78-1.1 to 1.78-1.1)
  • Migration status for pigpio/armhf (1.78-1.1 to 1.78-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
• pigpio/i386 (1.78-1.1 to 1.78-1.1)
  • Migration status for pigpio/i386 (1.78-1.1 to 1.78-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
• pigpio/ppc64el (1.78-1.1 to 1.78-1.1)
  • Migration status for pigpio/ppc64el (1.78-1.1 to 1.78-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
• pigpio/riscv64 (1.78-1.1 to 1.78-1.1)
  • Migration status for pigpio/riscv64 (1.78-1.1 to 1.78-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
• pigpio/s390x (1.78-1.1 to 1.78-1.1)
  • Migration status for pigpio/s390x (1.78-1.1 to 1.78-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
• pike8.0/amd64 (8.0.1956-1 to 8.0.1956-1)
  • Migration status for pike8.0/amd64 (8.0.1956-1 to 8.0.1956-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pike8.0/arm64 (8.0.1956-1 to 8.0.1956-1)
  • Migration status for pike8.0/arm64 (8.0.1956-1 to 8.0.1956-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pike8.0/armhf (8.0.1956-1 to 8.0.1956-1)
  • Migration status for pike8.0/armhf (8.0.1956-1 to 8.0.1956-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pike8.0/i386 (8.0.1956-1 to 8.0.1956-1)
  • Migration status for pike8.0/i386 (8.0.1956-1 to 8.0.1956-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pike8.0/ppc64el (8.0.1956-1 to 8.0.1956-1)
  • Migration status for pike8.0/ppc64el (8.0.1956-1 to 8.0.1956-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pike8.0/riscv64 (8.0.1956-1 to 8.0.1956-1)
  • Migration status for pike8.0/riscv64 (8.0.1956-1 to 8.0.1956-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pike8.0/s390x (8.0.1956-1 to 8.0.1956-1)
  • Migration status for pike8.0/s390x (8.0.1956-1 to 8.0.1956-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pktstat/amd64 (1.8.5-8 to 1.8.5-8)
  • Migration status for pktstat/amd64 (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pktstat/arm64 (1.8.5-8 to 1.8.5-8)
  • Migration status for pktstat/arm64 (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pktstat/armhf (1.8.5-8 to 1.8.5-8)
  • Migration status for pktstat/armhf (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pktstat/i386 (1.8.5-8 to 1.8.5-8)
  • Migration status for pktstat/i386 (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pktstat/ppc64el (1.8.5-8 to 1.8.5-8)
  • Migration status for pktstat/ppc64el (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pktstat/riscv64 (1.8.5-8 to 1.8.5-8)
  • Migration status for pktstat/riscv64 (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• pktstat/s390x (1.8.5-8 to 1.8.5-8)
  • Migration status for pktstat/s390x (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• plast/amd64 (2.3.2+dfsg-10 to 2.3.2+dfsg-10)
  • Migration status for plast/amd64 (2.3.2+dfsg-10 to 2.3.2+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• plast/arm64 (2.3.2+dfsg-10 to 2.3.2+dfsg-10)
  • Migration status for plast/arm64 (2.3.2+dfsg-10 to 2.3.2+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• plast/armhf (2.3.2+dfsg-10 to 2.3.2+dfsg-10)
  • Migration status for plast/armhf (2.3.2+dfsg-10 to 2.3.2+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• plast/i386 (2.3.2+dfsg-10 to 2.3.2+dfsg-10)
  • Migration status for plast/i386 (2.3.2+dfsg-10 to 2.3.2+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• plast/ppc64el (2.3.2+dfsg-10 to 2.3.2+dfsg-10)
  • Migration status for plast/ppc64el (2.3.2+dfsg-10 to 2.3.2+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• plast/s390x (2.3.2+dfsg-10 to 2.3.2+dfsg-10)
  • Migration status for plast/s390x (2.3.2+dfsg-10 to 2.3.2+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polybar/amd64 (3.7.2-1 to 3.7.2-1)
  • Migration status for polybar/amd64 (3.7.2-1 to 3.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polybar/arm64 (3.7.2-1 to 3.7.2-1)
  • Migration status for polybar/arm64 (3.7.2-1 to 3.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polybar/armhf (3.7.2-1 to 3.7.2-1)
  • Migration status for polybar/armhf (3.7.2-1 to 3.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polybar/i386 (3.7.2-1 to 3.7.2-1)
  • Migration status for polybar/i386 (3.7.2-1 to 3.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polybar/ppc64el (3.7.2-1 to 3.7.2-1)
  • Migration status for polybar/ppc64el (3.7.2-1 to 3.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polybar/riscv64 (3.7.2-1 to 3.7.2-1)
  • Migration status for polybar/riscv64 (3.7.2-1 to 3.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polybar/s390x (3.7.2-1 to 3.7.2-1)
  • Migration status for polybar/s390x (3.7.2-1 to 3.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polyglot/amd64 (2.0.4+git20210322-1 to 2.0.4+git20210322-1)
  • Migration status for polyglot/amd64 (2.0.4+git20210322-1 to 2.0.4+git20210322-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polyglot/arm64 (2.0.4+git20210322-1 to 2.0.4+git20210322-1)
  • Migration status for polyglot/arm64 (2.0.4+git20210322-1 to 2.0.4+git20210322-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polyglot/armhf (2.0.4+git20210322-1 to 2.0.4+git20210322-1)
  • Migration status for polyglot/armhf (2.0.4+git20210322-1 to 2.0.4+git20210322-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polyglot/i386 (2.0.4+git20210322-1 to 2.0.4+git20210322-1)
  • Migration status for polyglot/i386 (2.0.4+git20210322-1 to 2.0.4+git20210322-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polyglot/ppc64el (2.0.4+git20210322-1 to 2.0.4+git20210322-1)
  • Migration status for polyglot/ppc64el (2.0.4+git20210322-1 to 2.0.4+git20210322-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polyglot/riscv64 (2.0.4+git20210322-1 to 2.0.4+git20210322-1)
  • Migration status for polyglot/riscv64 (2.0.4+git20210322-1 to 2.0.4+git20210322-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• polyglot/s390x (2.0.4+git20210322-1 to 2.0.4+git20210322-1)
  • Migration status for polyglot/s390x (2.0.4+git20210322-1 to 2.0.4+git20210322-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• poppassd/amd64 (1.8.5-8 to 1.8.5-8)
  • Migration status for poppassd/amd64 (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• poppassd/arm64 (1.8.5-8 to 1.8.5-8)
  • Migration status for poppassd/arm64 (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• poppassd/armhf (1.8.5-8 to 1.8.5-8)
  • Migration status for poppassd/armhf (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• poppassd/i386 (1.8.5-8 to 1.8.5-8)
  • Migration status for poppassd/i386 (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• poppassd/ppc64el (1.8.5-8 to 1.8.5-8)
  • Migration status for poppassd/ppc64el (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• poppassd/riscv64 (1.8.5-8 to 1.8.5-8)
  • Migration status for poppassd/riscv64 (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• poppassd/s390x (1.8.5-8 to 1.8.5-8)
  • Migration status for poppassd/s390x (1.8.5-8 to 1.8.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• presage_pu (0.9.1-2.7 to 0.9.1-2.6+deb13u1)
  • Migration status for presage_pu (0.9.1-2.7 to 0.9.1-2.6+deb13u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: presage is newer in the target suite (0.9.1-2.7 0.9.1-2.6+deb13u1)
• prime-phylo/amd64 (1.0.11-13 to 1.0.11-13)
  • Migration status for prime-phylo/amd64 (1.0.11-13 to 1.0.11-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• prime-phylo/arm64 (1.0.11-13 to 1.0.11-13)
  • Migration status for prime-phylo/arm64 (1.0.11-13 to 1.0.11-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• prime-phylo/armhf (1.0.11-13 to 1.0.11-13)
  • Migration status for prime-phylo/armhf (1.0.11-13 to 1.0.11-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• prime-phylo/i386 (1.0.11-13 to 1.0.11-13)
  • Migration status for prime-phylo/i386 (1.0.11-13 to 1.0.11-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• prime-phylo/ppc64el (1.0.11-13 to 1.0.11-13)
  • Migration status for prime-phylo/ppc64el (1.0.11-13 to 1.0.11-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• prime-phylo/riscv64 (1.0.11-13 to 1.0.11-13)
  • Migration status for prime-phylo/riscv64 (1.0.11-13 to 1.0.11-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• prime-phylo/s390x (1.0.11-13 to 1.0.11-13)
  • Migration status for prime-phylo/s390x (1.0.11-13 to 1.0.11-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• proxsmtp/amd64 (1.10-5 to 1.10-5)
  • Migration status for proxsmtp/amd64 (1.10-5 to 1.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• proxsmtp/arm64 (1.10-5 to 1.10-5)
  • Migration status for proxsmtp/arm64 (1.10-5 to 1.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• proxsmtp/armhf (1.10-5 to 1.10-5)
  • Migration status for proxsmtp/armhf (1.10-5 to 1.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• proxsmtp/i386 (1.10-5 to 1.10-5)
  • Migration status for proxsmtp/i386 (1.10-5 to 1.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• proxsmtp/ppc64el (1.10-5 to 1.10-5)
  • Migration status for proxsmtp/ppc64el (1.10-5 to 1.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• proxsmtp/riscv64 (1.10-5 to 1.10-5)
  • Migration status for proxsmtp/riscv64 (1.10-5 to 1.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• proxsmtp/s390x (1.10-5 to 1.10-5)
  • Migration status for proxsmtp/s390x (1.10-5 to 1.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• purple-plugin-pack/amd64 (2.8.0-1 to 2.8.0-1)
  • Migration status for purple-plugin-pack/amd64 (2.8.0-1 to 2.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• purple-plugin-pack/arm64 (2.8.0-1 to 2.8.0-1)
  • Migration status for purple-plugin-pack/arm64 (2.8.0-1 to 2.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• purple-plugin-pack/armhf (2.8.0-1 to 2.8.0-1)
  • Migration status for purple-plugin-pack/armhf (2.8.0-1 to 2.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• purple-plugin-pack/i386 (2.8.0-1 to 2.8.0-1)
  • Migration status for purple-plugin-pack/i386 (2.8.0-1 to 2.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• purple-plugin-pack/ppc64el (2.8.0-1 to 2.8.0-1)
  • Migration status for purple-plugin-pack/ppc64el (2.8.0-1 to 2.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• purple-plugin-pack/s390x (2.8.0-1 to 2.8.0-1)
  • Migration status for purple-plugin-pack/s390x (2.8.0-1 to 2.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-easysnmp/amd64 (0.2.6-1 to 0.2.6-1)
  • Migration status for python-easysnmp/amd64 (0.2.6-1 to 0.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-easysnmp/arm64 (0.2.6-1 to 0.2.6-1)
  • Migration status for python-easysnmp/arm64 (0.2.6-1 to 0.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-easysnmp/armhf (0.2.6-1 to 0.2.6-1)
  • Migration status for python-easysnmp/armhf (0.2.6-1 to 0.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-easysnmp/i386 (0.2.6-1 to 0.2.6-1)
  • Migration status for python-easysnmp/i386 (0.2.6-1 to 0.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-easysnmp/ppc64el (0.2.6-1 to 0.2.6-1)
  • Migration status for python-easysnmp/ppc64el (0.2.6-1 to 0.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-easysnmp/riscv64 (0.2.6-1 to 0.2.6-1)
  • Migration status for python-easysnmp/riscv64 (0.2.6-1 to 0.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-easysnmp/s390x (0.2.6-1 to 0.2.6-1)
  • Migration status for python-easysnmp/s390x (0.2.6-1 to 0.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• python-pyahocorasick/amd64 (1.4.1-2 to 1.4.1-2)
  • Migration status for python-pyahocorasick/amd64 (1.4.1-2 to 1.4.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
• python-pyahocorasick/arm64 (1.4.1-2 to 1.4.1-2)
  • Migration status for python-pyahocorasick/arm64 (1.4.1-2 to 1.4.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
• python-pyahocorasick/armhf (1.4.1-2 to 1.4.1-2)
  • Migration status for python-pyahocorasick/armhf (1.4.1-2 to 1.4.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
• python-pyahocorasick/i386 (1.4.1-2 to 1.4.1-2)
  • Migration status for python-pyahocorasick/i386 (1.4.1-2 to 1.4.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
• python-pyahocorasick/ppc64el (1.4.1-2 to 1.4.1-2)
  • Migration status for python-pyahocorasick/ppc64el (1.4.1-2 to 1.4.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
• python-pyahocorasick/riscv64 (1.4.1-2 to 1.4.1-2)
  • Migration status for python-pyahocorasick/riscv64 (1.4.1-2 to 1.4.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
• python-pyahocorasick/s390x (1.4.1-2 to 1.4.1-2)
  • Migration status for python-pyahocorasick/s390x (1.4.1-2 to 1.4.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
• qxw/amd64 (20200708-2 to 20200708-2)
  • Migration status for qxw/amd64 (20200708-2 to 20200708-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• qxw/arm64 (20200708-2 to 20200708-2)
  • Migration status for qxw/arm64 (20200708-2 to 20200708-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• qxw/armhf (20200708-2 to 20200708-2)
  • Migration status for qxw/armhf (20200708-2 to 20200708-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• qxw/i386 (20200708-2 to 20200708-2)
  • Migration status for qxw/i386 (20200708-2 to 20200708-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• qxw/ppc64el (20200708-2 to 20200708-2)
  • Migration status for qxw/ppc64el (20200708-2 to 20200708-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• qxw/riscv64 (20200708-2 to 20200708-2)
  • Migration status for qxw/riscv64 (20200708-2 to 20200708-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• qxw/s390x (20200708-2 to 20200708-2)
  • Migration status for qxw/s390x (20200708-2 to 20200708-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rasmol/amd64 (2.7.6.0-4 to 2.7.6.0-4)
  • Migration status for rasmol/amd64 (2.7.6.0-4 to 2.7.6.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rasmol/arm64 (2.7.6.0-4 to 2.7.6.0-4)
  • Migration status for rasmol/arm64 (2.7.6.0-4 to 2.7.6.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rasmol/armhf (2.7.6.0-4 to 2.7.6.0-4)
  • Migration status for rasmol/armhf (2.7.6.0-4 to 2.7.6.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rasmol/i386 (2.7.6.0-4 to 2.7.6.0-4)
  • Migration status for rasmol/i386 (2.7.6.0-4 to 2.7.6.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rasmol/ppc64el (2.7.6.0-4 to 2.7.6.0-4)
  • Migration status for rasmol/ppc64el (2.7.6.0-4 to 2.7.6.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rasmol/riscv64 (2.7.6.0-4 to 2.7.6.0-4)
  • Migration status for rasmol/riscv64 (2.7.6.0-4 to 2.7.6.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rasmol/s390x (2.7.6.0-4 to 2.7.6.0-4)
  • Migration status for rasmol/s390x (2.7.6.0-4 to 2.7.6.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• raster3d/amd64 (3.0-7-2 to 3.0-7-2)
  • Migration status for raster3d/amd64 (3.0-7-2 to 3.0-7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• raster3d/arm64 (3.0-7-2 to 3.0-7-2)
  • Migration status for raster3d/arm64 (3.0-7-2 to 3.0-7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• raster3d/armhf (3.0-7-2 to 3.0-7-2)
  • Migration status for raster3d/armhf (3.0-7-2 to 3.0-7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• raster3d/i386 (3.0-7-2 to 3.0-7-2)
  • Migration status for raster3d/i386 (3.0-7-2 to 3.0-7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• raster3d/ppc64el (3.0-7-2 to 3.0-7-2)
  • Migration status for raster3d/ppc64el (3.0-7-2 to 3.0-7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• raster3d/s390x (3.0-7-2 to 3.0-7-2)
  • Migration status for raster3d/s390x (3.0-7-2 to 3.0-7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rc/amd64 (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5)
  • Migration status for rc/amd64 (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rc/arm64 (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5)
  • Migration status for rc/arm64 (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rc/armhf (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5)
  • Migration status for rc/armhf (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rc/i386 (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5)
  • Migration status for rc/i386 (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rc/ppc64el (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5)
  • Migration status for rc/ppc64el (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rc/riscv64 (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5)
  • Migration status for rc/riscv64 (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rc/s390x (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5)
  • Migration status for rc/s390x (1.7.4+97.gceb59bb-5 to 1.7.4+97.gceb59bb-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rdiff-backup-fs/amd64 (1.0.0-8 to 1.0.0-8)
  • Migration status for rdiff-backup-fs/amd64 (1.0.0-8 to 1.0.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rdiff-backup-fs/arm64 (1.0.0-8 to 1.0.0-8)
  • Migration status for rdiff-backup-fs/arm64 (1.0.0-8 to 1.0.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rdiff-backup-fs/armhf (1.0.0-8 to 1.0.0-8)
  • Migration status for rdiff-backup-fs/armhf (1.0.0-8 to 1.0.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rdiff-backup-fs/i386 (1.0.0-8 to 1.0.0-8)
  • Migration status for rdiff-backup-fs/i386 (1.0.0-8 to 1.0.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rdiff-backup-fs/ppc64el (1.0.0-8 to 1.0.0-8)
  • Migration status for rdiff-backup-fs/ppc64el (1.0.0-8 to 1.0.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rdiff-backup-fs/riscv64 (1.0.0-8 to 1.0.0-8)
  • Migration status for rdiff-backup-fs/riscv64 (1.0.0-8 to 1.0.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rdiff-backup-fs/s390x (1.0.0-8 to 1.0.0-8)
  • Migration status for rdiff-backup-fs/s390x (1.0.0-8 to 1.0.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• redland-bindings/amd64 (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6)
  • Migration status for redland-bindings/amd64 (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• redland-bindings/arm64 (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6)
  • Migration status for redland-bindings/arm64 (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• redland-bindings/armhf (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6)
  • Migration status for redland-bindings/armhf (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• redland-bindings/i386 (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6)
  • Migration status for redland-bindings/i386 (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• redland-bindings/ppc64el (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6)
  • Migration status for redland-bindings/ppc64el (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• redland-bindings/s390x (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6)
  • Migration status for redland-bindings/s390x (1.0.17.1+dfsg-6 to 1.0.17.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• relion/amd64 (3.1.3-4 to 3.1.3-4)
  • Migration status for relion/amd64 (3.1.3-4 to 3.1.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• relion/arm64 (3.1.3-4 to 3.1.3-4)
  • Migration status for relion/arm64 (3.1.3-4 to 3.1.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• relion/armhf (3.1.3-4 to 3.1.3-4)
  • Migration status for relion/armhf (3.1.3-4 to 3.1.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• relion/i386 (3.1.3-4 to 3.1.3-4)
  • Migration status for relion/i386 (3.1.3-4 to 3.1.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• relion/ppc64el (3.1.3-4 to 3.1.3-4)
  • Migration status for relion/ppc64el (3.1.3-4 to 3.1.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• relion/riscv64 (3.1.3-4 to 3.1.3-4)
  • Migration status for relion/riscv64 (3.1.3-4 to 3.1.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• relion/s390x (3.1.3-4 to 3.1.3-4)
  • Migration status for relion/s390x (3.1.3-4 to 3.1.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rgbpaint/amd64 (0.8.7-7 to 0.8.7-7)
  • Migration status for rgbpaint/amd64 (0.8.7-7 to 0.8.7-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rgbpaint/arm64 (0.8.7-7 to 0.8.7-7)
  • Migration status for rgbpaint/arm64 (0.8.7-7 to 0.8.7-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rgbpaint/armhf (0.8.7-7 to 0.8.7-7)
  • Migration status for rgbpaint/armhf (0.8.7-7 to 0.8.7-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rgbpaint/i386 (0.8.7-7 to 0.8.7-7)
  • Migration status for rgbpaint/i386 (0.8.7-7 to 0.8.7-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rgbpaint/ppc64el (0.8.7-7 to 0.8.7-7)
  • Migration status for rgbpaint/ppc64el (0.8.7-7 to 0.8.7-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rgbpaint/riscv64 (0.8.7-7 to 0.8.7-7)
  • Migration status for rgbpaint/riscv64 (0.8.7-7 to 0.8.7-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rgbpaint/s390x (0.8.7-7 to 0.8.7-7)
  • Migration status for rgbpaint/s390x (0.8.7-7 to 0.8.7-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rocdbgapi/amd64 (5.7.1-2 to 5.7.1-2)
  • Migration status for rocdbgapi/amd64 (5.7.1-2 to 5.7.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
• rocdbgapi/arm64 (5.7.1-2 to 5.7.1-2)
  • Migration status for rocdbgapi/arm64 (5.7.1-2 to 5.7.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
• rocdbgapi/armhf (5.7.1-2 to 5.7.1-2)
  • Migration status for rocdbgapi/armhf (5.7.1-2 to 5.7.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
• rocdbgapi/i386 (5.7.1-2 to 5.7.1-2)
  • Migration status for rocdbgapi/i386 (5.7.1-2 to 5.7.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
• rocdbgapi/ppc64el (5.7.1-2 to 5.7.1-2)
  • Migration status for rocdbgapi/ppc64el (5.7.1-2 to 5.7.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
• rocdbgapi/riscv64 (5.7.1-2 to 5.7.1-2)
  • Migration status for rocdbgapi/riscv64 (5.7.1-2 to 5.7.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
• rocdbgapi/s390x (5.7.1-2 to 5.7.1-2)
  • Migration status for rocdbgapi/s390x (5.7.1-2 to 5.7.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
• roguenarok/amd64 (1.0.1-3 to 1.0.1-3)
  • Migration status for roguenarok/amd64 (1.0.1-3 to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• roguenarok/arm64 (1.0.1-3 to 1.0.1-3)
  • Migration status for roguenarok/arm64 (1.0.1-3 to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• roguenarok/armhf (1.0.1-3 to 1.0.1-3)
  • Migration status for roguenarok/armhf (1.0.1-3 to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• roguenarok/i386 (1.0.1-3 to 1.0.1-3)
  • Migration status for roguenarok/i386 (1.0.1-3 to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• roguenarok/ppc64el (1.0.1-3 to 1.0.1-3)
  • Migration status for roguenarok/ppc64el (1.0.1-3 to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• roguenarok/riscv64 (1.0.1-3 to 1.0.1-3)
  • Migration status for roguenarok/riscv64 (1.0.1-3 to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• roguenarok/s390x (1.0.1-3 to 1.0.1-3)
  • Migration status for roguenarok/s390x (1.0.1-3 to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ros2-rosidl/amd64 (3.3.1-1 to 3.3.1-1)
  • Migration status for ros2-rosidl/amd64 (3.3.1-1 to 3.3.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
• ros2-rosidl/arm64 (3.3.1-1 to 3.3.1-1)
  • Migration status for ros2-rosidl/arm64 (3.3.1-1 to 3.3.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
• ros2-rosidl/armhf (3.3.1-1 to 3.3.1-1)
  • Migration status for ros2-rosidl/armhf (3.3.1-1 to 3.3.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
• ros2-rosidl/i386 (3.3.1-1 to 3.3.1-1)
  • Migration status for ros2-rosidl/i386 (3.3.1-1 to 3.3.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
• ros2-rosidl/ppc64el (3.3.1-1 to 3.3.1-1)
  • Migration status for ros2-rosidl/ppc64el (3.3.1-1 to 3.3.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
• ros2-rosidl/riscv64 (3.3.1-1 to 3.3.1-1)
  • Migration status for ros2-rosidl/riscv64 (3.3.1-1 to 3.3.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
• ros2-rosidl/s390x (3.3.1-1 to 3.3.1-1)
  • Migration status for ros2-rosidl/s390x (3.3.1-1 to 3.3.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
• rstatd/amd64 (4.0.1-12 to 4.0.1-12)
  • Migration status for rstatd/amd64 (4.0.1-12 to 4.0.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstatd/arm64 (4.0.1-12 to 4.0.1-12)
  • Migration status for rstatd/arm64 (4.0.1-12 to 4.0.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstatd/armhf (4.0.1-12 to 4.0.1-12)
  • Migration status for rstatd/armhf (4.0.1-12 to 4.0.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstatd/i386 (4.0.1-12 to 4.0.1-12)
  • Migration status for rstatd/i386 (4.0.1-12 to 4.0.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstatd/ppc64el (4.0.1-12 to 4.0.1-12)
  • Migration status for rstatd/ppc64el (4.0.1-12 to 4.0.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstatd/riscv64 (4.0.1-12 to 4.0.1-12)
  • Migration status for rstatd/riscv64 (4.0.1-12 to 4.0.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rstatd/s390x (4.0.1-12 to 4.0.1-12)
  • Migration status for rstatd/s390x (4.0.1-12 to 4.0.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-fusefs/amd64 (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/amd64 (0.7.0-6 to 0.7.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-fusefs/arm64 (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/arm64 (0.7.0-6 to 0.7.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-fusefs/armhf (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/armhf (0.7.0-6 to 0.7.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-fusefs/i386 (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/i386 (0.7.0-6 to 0.7.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-fusefs/ppc64el (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/ppc64el (0.7.0-6 to 0.7.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-fusefs/s390x (0.7.0-6 to 0.7.0-6)
  • Migration status for ruby-fusefs/s390x (0.7.0-6 to 0.7.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-lapack/amd64 (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/amd64 (1.8.2-1 to 1.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-lapack/arm64 (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/arm64 (1.8.2-1 to 1.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-lapack/armhf (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/armhf (1.8.2-1 to 1.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-lapack/i386 (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/i386 (1.8.2-1 to 1.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-lapack/ppc64el (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/ppc64el (1.8.2-1 to 1.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-lapack/s390x (1.8.2-1 to 1.8.2-1)
  • Migration status for ruby-lapack/s390x (1.8.2-1 to 1.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-rbtrace/amd64 (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/amd64 (0.5.1-1.1 to 0.5.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-rbtrace/arm64 (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/arm64 (0.5.1-1.1 to 0.5.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-rbtrace/armhf (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/armhf (0.5.1-1.1 to 0.5.1-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
• ruby-rbtrace/i386 (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/i386 (0.5.1-1.1 to 0.5.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-rbtrace/ppc64el (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/ppc64el (0.5.1-1.1 to 0.5.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-rbtrace/riscv64 (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/riscv64 (0.5.1-1.1 to 0.5.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-rbtrace/s390x (0.5.1-1.1 to 0.5.1-1.1)
  • Migration status for ruby-rbtrace/s390x (0.5.1-1.1 to 0.5.1-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
• ruby-rpatricia/amd64 (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/amd64 (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-rpatricia/arm64 (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/arm64 (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-rpatricia/armhf (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/armhf (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-rpatricia/i386 (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/i386 (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-rpatricia/ppc64el (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/ppc64el (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-rpatricia/s390x (1.0.1-2 to 1.0.1-2)
  • Migration status for ruby-rpatricia/s390x (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-sequel-pg/amd64 (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/amd64 (1.14.0-1 to 1.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-sequel-pg/arm64 (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/arm64 (1.14.0-1 to 1.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-sequel-pg/armhf (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/armhf (1.14.0-1 to 1.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-sequel-pg/i386 (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/i386 (1.14.0-1 to 1.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-sequel-pg/ppc64el (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/ppc64el (1.14.0-1 to 1.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ruby-sequel-pg/s390x (1.14.0-1 to 1.14.0-1)
  • Migration status for ruby-sequel-pg/s390x (1.14.0-1 to 1.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-actix-web/amd64 (4.9.0-2 to 4.9.0-2)
  • Migration status for rust-actix-web/amd64 (4.9.0-2 to 4.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
• rust-actix-web/arm64 (4.9.0-2 to 4.9.0-2)
  • Migration status for rust-actix-web/arm64 (4.9.0-2 to 4.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
• rust-actix-web/armhf (4.9.0-2 to 4.9.0-2)
  • Migration status for rust-actix-web/armhf (4.9.0-2 to 4.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
• rust-actix-web/i386 (4.9.0-2 to 4.9.0-2)
  • Migration status for rust-actix-web/i386 (4.9.0-2 to 4.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
• rust-actix-web/ppc64el (4.9.0-2 to 4.9.0-2)
  • Migration status for rust-actix-web/ppc64el (4.9.0-2 to 4.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
• rust-actix-web/riscv64 (4.9.0-2 to 4.9.0-2)
  • Migration status for rust-actix-web/riscv64 (4.9.0-2 to 4.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
• rust-actix-web/s390x (4.9.0-2 to 4.9.0-2)
  • Migration status for rust-actix-web/s390x (4.9.0-2 to 4.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
• rust-async-h1/amd64 (2.3.4-1 to 2.3.4-1)
  • Migration status for rust-async-h1/amd64 (2.3.4-1 to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-async-h1/arm64 (2.3.4-1 to 2.3.4-1)
  • Migration status for rust-async-h1/arm64 (2.3.4-1 to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-async-h1/armhf (2.3.4-1 to 2.3.4-1)
  • Migration status for rust-async-h1/armhf (2.3.4-1 to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-async-h1/i386 (2.3.4-1 to 2.3.4-1)
  • Migration status for rust-async-h1/i386 (2.3.4-1 to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-async-h1/ppc64el (2.3.4-1 to 2.3.4-1)
  • Migration status for rust-async-h1/ppc64el (2.3.4-1 to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-async-h1/riscv64 (2.3.4-1 to 2.3.4-1)
  • Migration status for rust-async-h1/riscv64 (2.3.4-1 to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-async-h1/s390x (2.3.4-1 to 2.3.4-1)
  • Migration status for rust-async-h1/s390x (2.3.4-1 to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-http-types/amd64 (2.12.0-3 to 2.12.0-3)
  • Migration status for rust-http-types/amd64 (2.12.0-3 to 2.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-http-types/arm64 (2.12.0-3 to 2.12.0-3)
  • Migration status for rust-http-types/arm64 (2.12.0-3 to 2.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-http-types/armhf (2.12.0-3 to 2.12.0-3)
  • Migration status for rust-http-types/armhf (2.12.0-3 to 2.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-http-types/i386 (2.12.0-3 to 2.12.0-3)
  • Migration status for rust-http-types/i386 (2.12.0-3 to 2.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-http-types/ppc64el (2.12.0-3 to 2.12.0-3)
  • Migration status for rust-http-types/ppc64el (2.12.0-3 to 2.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-http-types/riscv64 (2.12.0-3 to 2.12.0-3)
  • Migration status for rust-http-types/riscv64 (2.12.0-3 to 2.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-http-types/s390x (2.12.0-3 to 2.12.0-3)
  • Migration status for rust-http-types/s390x (2.12.0-3 to 2.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-indieweb/amd64 (0.4.5-10 to 0.4.5-10)
  • Migration status for rust-indieweb/amd64 (0.4.5-10 to 0.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-indieweb/arm64 (0.4.5-10 to 0.4.5-10)
  • Migration status for rust-indieweb/arm64 (0.4.5-10 to 0.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-indieweb/armhf (0.4.5-10 to 0.4.5-10)
  • Migration status for rust-indieweb/armhf (0.4.5-10 to 0.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-indieweb/i386 (0.4.5-10 to 0.4.5-10)
  • Migration status for rust-indieweb/i386 (0.4.5-10 to 0.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-indieweb/ppc64el (0.4.5-10 to 0.4.5-10)
  • Migration status for rust-indieweb/ppc64el (0.4.5-10 to 0.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-indieweb/riscv64 (0.4.5-10 to 0.4.5-10)
  • Migration status for rust-indieweb/riscv64 (0.4.5-10 to 0.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-indieweb/s390x (0.4.5-10 to 0.4.5-10)
  • Migration status for rust-indieweb/s390x (0.4.5-10 to 0.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-liblzma/armhf (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-liblzma/armhf (0.4.4-1 to 0.4.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-liblzma/armhf rust-liblzma-sys (not considered)
    • Invalidated by dependency
• rust-liblzma/i386 (0.4.4-1 to 0.4.4-1)
  • Migration status for rust-liblzma/i386 (0.4.4-1 to 0.4.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-liblzma/i386 rust-liblzma-sys (not considered)
    • Invalidated by dependency
• rust-niffler/armhf (2.6.0-2 to 2.6.0-2)
  • Migration status for rust-niffler/armhf (2.6.0-2 to 2.6.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-niffler/armhf rust-liblzma/armhf (not considered)
    • Invalidated by dependency
• rust-niffler/i386 (2.6.0-2 to 2.6.0-2)
  • Migration status for rust-niffler/i386 (2.6.0-2 to 2.6.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: rust-niffler/i386 rust-liblzma/i386 (not considered)
    • Invalidated by dependency
• rust-serde-qs/amd64 (0.13.0-8 to 0.13.0-8)
  • Migration status for rust-serde-qs/amd64 (0.13.0-8 to 0.13.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-serde-qs/arm64 (0.13.0-8 to 0.13.0-8)
  • Migration status for rust-serde-qs/arm64 (0.13.0-8 to 0.13.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-serde-qs/armhf (0.13.0-8 to 0.13.0-8)
  • Migration status for rust-serde-qs/armhf (0.13.0-8 to 0.13.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-serde-qs/i386 (0.13.0-8 to 0.13.0-8)
  • Migration status for rust-serde-qs/i386 (0.13.0-8 to 0.13.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-serde-qs/ppc64el (0.13.0-8 to 0.13.0-8)
  • Migration status for rust-serde-qs/ppc64el (0.13.0-8 to 0.13.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-serde-qs/riscv64 (0.13.0-8 to 0.13.0-8)
  • Migration status for rust-serde-qs/riscv64 (0.13.0-8 to 0.13.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• rust-serde-qs/s390x (0.13.0-8 to 0.13.0-8)
  • Migration status for rust-serde-qs/s390x (0.13.0-8 to 0.13.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• samhain_pu (4.1.4-7 to 4.1.4-6+deb13u1)
  • Migration status for samhain_pu (4.1.4-7 to 4.1.4-6+deb13u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: samhain is newer in the target suite (4.1.4-7 4.1.4-6+deb13u1)
• sc/amd64 (7.16-1.1.2-1 to 7.16-1.1.2-1)
  • Migration status for sc/amd64 (7.16-1.1.2-1 to 7.16-1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sc/arm64 (7.16-1.1.2-1 to 7.16-1.1.2-1)
  • Migration status for sc/arm64 (7.16-1.1.2-1 to 7.16-1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sc/armhf (7.16-1.1.2-1 to 7.16-1.1.2-1)
  • Migration status for sc/armhf (7.16-1.1.2-1 to 7.16-1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sc/i386 (7.16-1.1.2-1 to 7.16-1.1.2-1)
  • Migration status for sc/i386 (7.16-1.1.2-1 to 7.16-1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sc/ppc64el (7.16-1.1.2-1 to 7.16-1.1.2-1)
  • Migration status for sc/ppc64el (7.16-1.1.2-1 to 7.16-1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sc/riscv64 (7.16-1.1.2-1 to 7.16-1.1.2-1)
  • Migration status for sc/riscv64 (7.16-1.1.2-1 to 7.16-1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sc/s390x (7.16-1.1.2-1 to 7.16-1.1.2-1)
  • Migration status for sc/s390x (7.16-1.1.2-1 to 7.16-1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sciplot/amd64 (1.36-19 to 1.36-19)
  • Migration status for sciplot/amd64 (1.36-19 to 1.36-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sciplot/arm64 (1.36-19 to 1.36-19)
  • Migration status for sciplot/arm64 (1.36-19 to 1.36-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sciplot/armhf (1.36-19 to 1.36-19)
  • Migration status for sciplot/armhf (1.36-19 to 1.36-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sciplot/i386 (1.36-19 to 1.36-19)
  • Migration status for sciplot/i386 (1.36-19 to 1.36-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sciplot/ppc64el (1.36-19 to 1.36-19)
  • Migration status for sciplot/ppc64el (1.36-19 to 1.36-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sciplot/riscv64 (1.36-19 to 1.36-19)
  • Migration status for sciplot/riscv64 (1.36-19 to 1.36-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sciplot/s390x (1.36-19 to 1.36-19)
  • Migration status for sciplot/s390x (1.36-19 to 1.36-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• scsitools/amd64 (0.12-6 to 0.12-6)
  • Migration status for scsitools/amd64 (0.12-6 to 0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• scsitools/arm64 (0.12-6 to 0.12-6)
  • Migration status for scsitools/arm64 (0.12-6 to 0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• scsitools/armhf (0.12-6 to 0.12-6)
  • Migration status for scsitools/armhf (0.12-6 to 0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• scsitools/i386 (0.12-6 to 0.12-6)
  • Migration status for scsitools/i386 (0.12-6 to 0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• scsitools/ppc64el (0.12-6 to 0.12-6)
  • Migration status for scsitools/ppc64el (0.12-6 to 0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• scsitools/riscv64 (0.12-6 to 0.12-6)
  • Migration status for scsitools/riscv64 (0.12-6 to 0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• scsitools/s390x (0.12-6 to 0.12-6)
  • Migration status for scsitools/s390x (0.12-6 to 0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sendip/amd64 (2.6-1 to 2.6-1)
  • Migration status for sendip/amd64 (2.6-1 to 2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sendip/arm64 (2.6-1 to 2.6-1)
  • Migration status for sendip/arm64 (2.6-1 to 2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sendip/armhf (2.6-1 to 2.6-1)
  • Migration status for sendip/armhf (2.6-1 to 2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sendip/i386 (2.6-1 to 2.6-1)
  • Migration status for sendip/i386 (2.6-1 to 2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sendip/ppc64el (2.6-1 to 2.6-1)
  • Migration status for sendip/ppc64el (2.6-1 to 2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sendip/riscv64 (2.6-1 to 2.6-1)
  • Migration status for sendip/riscv64 (2.6-1 to 2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sendip/s390x (2.6-1 to 2.6-1)
  • Migration status for sendip/s390x (2.6-1 to 2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• seyon/amd64 (2.20c-36 to 2.20c-36)
  • Migration status for seyon/amd64 (2.20c-36 to 2.20c-36): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• seyon/arm64 (2.20c-36 to 2.20c-36)
  • Migration status for seyon/arm64 (2.20c-36 to 2.20c-36): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• seyon/armhf (2.20c-36 to 2.20c-36)
  • Migration status for seyon/armhf (2.20c-36 to 2.20c-36): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• seyon/i386 (2.20c-36 to 2.20c-36)
  • Migration status for seyon/i386 (2.20c-36 to 2.20c-36): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• seyon/ppc64el (2.20c-36 to 2.20c-36)
  • Migration status for seyon/ppc64el (2.20c-36 to 2.20c-36): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• seyon/riscv64 (2.20c-36 to 2.20c-36)
  • Migration status for seyon/riscv64 (2.20c-36 to 2.20c-36): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• seyon/s390x (2.20c-36 to 2.20c-36)
  • Migration status for seyon/s390x (2.20c-36 to 2.20c-36): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shibboleth-sp_pu (3.5.1+dfsg-1 to 3.5.0+dfsg-2+deb13u1)
  • Migration status for shibboleth-sp_pu (3.5.1+dfsg-1 to 3.5.0+dfsg-2+deb13u1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: shibboleth-sp is newer in the target suite (3.5.1+dfsg-1 3.5.0+dfsg-2+deb13u1)
• shntool/amd64 (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1)
  • Migration status for shntool/amd64 (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shntool/arm64 (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1)
  • Migration status for shntool/arm64 (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shntool/armhf (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1)
  • Migration status for shntool/armhf (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shntool/i386 (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1)
  • Migration status for shntool/i386 (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shntool/ppc64el (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1)
  • Migration status for shntool/ppc64el (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shntool/riscv64 (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1)
  • Migration status for shntool/riscv64 (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shntool/s390x (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1)
  • Migration status for shntool/s390x (3.0.10+git20130108.4ca41f4-1 to 3.0.10+git20130108.4ca41f4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shogivar/amd64 (1.55b-3 to 1.55b-3)
  • Migration status for shogivar/amd64 (1.55b-3 to 1.55b-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shogivar/arm64 (1.55b-3 to 1.55b-3)
  • Migration status for shogivar/arm64 (1.55b-3 to 1.55b-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shogivar/armhf (1.55b-3 to 1.55b-3)
  • Migration status for shogivar/armhf (1.55b-3 to 1.55b-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shogivar/i386 (1.55b-3 to 1.55b-3)
  • Migration status for shogivar/i386 (1.55b-3 to 1.55b-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shogivar/ppc64el (1.55b-3 to 1.55b-3)
  • Migration status for shogivar/ppc64el (1.55b-3 to 1.55b-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shogivar/riscv64 (1.55b-3 to 1.55b-3)
  • Migration status for shogivar/riscv64 (1.55b-3 to 1.55b-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• shogivar/s390x (1.55b-3 to 1.55b-3)
  • Migration status for shogivar/s390x (1.55b-3 to 1.55b-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• simutrans/amd64 (124.3-2 to 124.3-2)
  • Migration status for simutrans/amd64 (124.3-2 to 124.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: simutrans/amd64 miniupnpc (not considered)
    • Invalidated by dependency
• simutrans/arm64 (124.3-2 to 124.3-2)
  • Migration status for simutrans/arm64 (124.3-2 to 124.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: simutrans/arm64 miniupnpc (not considered)
    • Invalidated by dependency
• simutrans/armhf (124.3-2 to 124.3-2)
  • Migration status for simutrans/armhf (124.3-2 to 124.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: simutrans/armhf miniupnpc (not considered)
    • Invalidated by dependency
• simutrans/i386 (124.3-2 to 124.3-2)
  • Migration status for simutrans/i386 (124.3-2 to 124.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: simutrans/i386 miniupnpc (not considered)
    • Invalidated by dependency
• simutrans/ppc64el (124.3-2 to 124.3-2)
  • Migration status for simutrans/ppc64el (124.3-2 to 124.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: simutrans/ppc64el miniupnpc (not considered)
    • Invalidated by dependency
• simutrans/riscv64 (124.3-2 to 124.3-2)
  • Migration status for simutrans/riscv64 (124.3-2 to 124.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: simutrans/riscv64 miniupnpc (not considered)
    • Invalidated by dependency
• simutrans/s390x (124.3-2 to 124.3-2)
  • Migration status for simutrans/s390x (124.3-2 to 124.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: simutrans/s390x miniupnpc (not considered)
    • Invalidated by dependency
• sjeng/amd64 (11.2-15 to 11.2-15)
  • Migration status for sjeng/amd64 (11.2-15 to 11.2-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sjeng/arm64 (11.2-15 to 11.2-15)
  • Migration status for sjeng/arm64 (11.2-15 to 11.2-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sjeng/armhf (11.2-15 to 11.2-15)
  • Migration status for sjeng/armhf (11.2-15 to 11.2-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sjeng/i386 (11.2-15 to 11.2-15)
  • Migration status for sjeng/i386 (11.2-15 to 11.2-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sjeng/ppc64el (11.2-15 to 11.2-15)
  • Migration status for sjeng/ppc64el (11.2-15 to 11.2-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sjeng/riscv64 (11.2-15 to 11.2-15)
  • Migration status for sjeng/riscv64 (11.2-15 to 11.2-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sjeng/s390x (11.2-15 to 11.2-15)
  • Migration status for sjeng/s390x (11.2-15 to 11.2-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sketch/amd64 (1:0.3.7-12 to 1:0.3.7-12)
  • Migration status for sketch/amd64 (1:0.3.7-12 to 1:0.3.7-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sketch/arm64 (1:0.3.7-12 to 1:0.3.7-12)
  • Migration status for sketch/arm64 (1:0.3.7-12 to 1:0.3.7-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sketch/armhf (1:0.3.7-12 to 1:0.3.7-12)
  • Migration status for sketch/armhf (1:0.3.7-12 to 1:0.3.7-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sketch/i386 (1:0.3.7-12 to 1:0.3.7-12)
  • Migration status for sketch/i386 (1:0.3.7-12 to 1:0.3.7-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sketch/ppc64el (1:0.3.7-12 to 1:0.3.7-12)
  • Migration status for sketch/ppc64el (1:0.3.7-12 to 1:0.3.7-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sketch/riscv64 (1:0.3.7-12 to 1:0.3.7-12)
  • Migration status for sketch/riscv64 (1:0.3.7-12 to 1:0.3.7-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sketch/s390x (1:0.3.7-12 to 1:0.3.7-12)
  • Migration status for sketch/s390x (1:0.3.7-12 to 1:0.3.7-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• skktools/amd64 (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1)
  • Migration status for skktools/amd64 (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• skktools/arm64 (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1)
  • Migration status for skktools/arm64 (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• skktools/armhf (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1)
  • Migration status for skktools/armhf (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• skktools/i386 (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1)
  • Migration status for skktools/i386 (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• skktools/ppc64el (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1)
  • Migration status for skktools/ppc64el (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• skktools/riscv64 (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1)
  • Migration status for skktools/riscv64 (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• skktools/s390x (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1)
  • Migration status for skktools/s390x (1.3.4+0.20210220-1 to 1.3.4+0.20210220-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• slony1-2/amd64 (2.2.11-6 to 2.2.11-6)
  • Migration status for slony1-2/amd64 (2.2.11-6 to 2.2.11-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• slony1-2/arm64 (2.2.11-6 to 2.2.11-6)
  • Migration status for slony1-2/arm64 (2.2.11-6 to 2.2.11-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• slony1-2/armhf (2.2.11-6 to 2.2.11-6)
  • Migration status for slony1-2/armhf (2.2.11-6 to 2.2.11-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• slony1-2/i386 (2.2.11-6 to 2.2.11-6)
  • Migration status for slony1-2/i386 (2.2.11-6 to 2.2.11-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• slony1-2/ppc64el (2.2.11-6 to 2.2.11-6)
  • Migration status for slony1-2/ppc64el (2.2.11-6 to 2.2.11-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• slony1-2/riscv64 (2.2.11-6 to 2.2.11-6)
  • Migration status for slony1-2/riscv64 (2.2.11-6 to 2.2.11-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• slony1-2/s390x (2.2.11-6 to 2.2.11-6)
  • Migration status for slony1-2/s390x (2.2.11-6 to 2.2.11-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• smenu/amd64 (1.4.0-1 to 1.4.0-1)
  • Migration status for smenu/amd64 (1.4.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• smenu/arm64 (1.4.0-1 to 1.4.0-1)
  • Migration status for smenu/arm64 (1.4.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• smenu/armhf (1.4.0-1 to 1.4.0-1)
  • Migration status for smenu/armhf (1.4.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• smenu/i386 (1.4.0-1 to 1.4.0-1)
  • Migration status for smenu/i386 (1.4.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• smenu/ppc64el (1.4.0-1 to 1.4.0-1)
  • Migration status for smenu/ppc64el (1.4.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• smenu/riscv64 (1.4.0-1 to 1.4.0-1)
  • Migration status for smenu/riscv64 (1.4.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• smenu/s390x (1.4.0-1 to 1.4.0-1)
  • Migration status for smenu/s390x (1.4.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• snmptrapfmt/amd64 (1.19 to 1.19)
  • Migration status for snmptrapfmt/amd64 (1.19 to 1.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• snmptrapfmt/arm64 (1.19 to 1.19)
  • Migration status for snmptrapfmt/arm64 (1.19 to 1.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• snmptrapfmt/armhf (1.19 to 1.19)
  • Migration status for snmptrapfmt/armhf (1.19 to 1.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• snmptrapfmt/i386 (1.19 to 1.19)
  • Migration status for snmptrapfmt/i386 (1.19 to 1.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• snmptrapfmt/ppc64el (1.19 to 1.19)
  • Migration status for snmptrapfmt/ppc64el (1.19 to 1.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• snmptrapfmt/riscv64 (1.19 to 1.19)
  • Migration status for snmptrapfmt/riscv64 (1.19 to 1.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• snmptrapfmt/s390x (1.19 to 1.19)
  • Migration status for snmptrapfmt/s390x (1.19 to 1.19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapaligner/amd64 (2.20-5 to 2.20-5)
  • Migration status for soapaligner/amd64 (2.20-5 to 2.20-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapaligner/arm64 (2.20-5 to 2.20-5)
  • Migration status for soapaligner/arm64 (2.20-5 to 2.20-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapaligner/armhf (2.20-5 to 2.20-5)
  • Migration status for soapaligner/armhf (2.20-5 to 2.20-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapaligner/i386 (2.20-5 to 2.20-5)
  • Migration status for soapaligner/i386 (2.20-5 to 2.20-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapaligner/ppc64el (2.20-5 to 2.20-5)
  • Migration status for soapaligner/ppc64el (2.20-5 to 2.20-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapaligner/riscv64 (2.20-5 to 2.20-5)
  • Migration status for soapaligner/riscv64 (2.20-5 to 2.20-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapaligner/s390x (2.20-5 to 2.20-5)
  • Migration status for soapaligner/s390x (2.20-5 to 2.20-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo/amd64 (1.05-6 to 1.05-6)
  • Migration status for soapdenovo/amd64 (1.05-6 to 1.05-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo/arm64 (1.05-6 to 1.05-6)
  • Migration status for soapdenovo/arm64 (1.05-6 to 1.05-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo/armhf (1.05-6 to 1.05-6)
  • Migration status for soapdenovo/armhf (1.05-6 to 1.05-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo/i386 (1.05-6 to 1.05-6)
  • Migration status for soapdenovo/i386 (1.05-6 to 1.05-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo/ppc64el (1.05-6 to 1.05-6)
  • Migration status for soapdenovo/ppc64el (1.05-6 to 1.05-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo/riscv64 (1.05-6 to 1.05-6)
  • Migration status for soapdenovo/riscv64 (1.05-6 to 1.05-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo/s390x (1.05-6 to 1.05-6)
  • Migration status for soapdenovo/s390x (1.05-6 to 1.05-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo2/amd64 (242+dfsg-4 to 242+dfsg-4)
  • Migration status for soapdenovo2/amd64 (242+dfsg-4 to 242+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo2/arm64 (242+dfsg-4 to 242+dfsg-4)
  • Migration status for soapdenovo2/arm64 (242+dfsg-4 to 242+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo2/armhf (242+dfsg-4 to 242+dfsg-4)
  • Migration status for soapdenovo2/armhf (242+dfsg-4 to 242+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo2/i386 (242+dfsg-4 to 242+dfsg-4)
  • Migration status for soapdenovo2/i386 (242+dfsg-4 to 242+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo2/ppc64el (242+dfsg-4 to 242+dfsg-4)
  • Migration status for soapdenovo2/ppc64el (242+dfsg-4 to 242+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo2/riscv64 (242+dfsg-4 to 242+dfsg-4)
  • Migration status for soapdenovo2/riscv64 (242+dfsg-4 to 242+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• soapdenovo2/s390x (242+dfsg-4 to 242+dfsg-4)
  • Migration status for soapdenovo2/s390x (242+dfsg-4 to 242+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spacefm/amd64 (1.0.6-9 to 1.0.6-9)
  • Migration status for spacefm/amd64 (1.0.6-9 to 1.0.6-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spacefm/arm64 (1.0.6-9 to 1.0.6-9)
  • Migration status for spacefm/arm64 (1.0.6-9 to 1.0.6-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spacefm/armhf (1.0.6-9 to 1.0.6-9)
  • Migration status for spacefm/armhf (1.0.6-9 to 1.0.6-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spacefm/i386 (1.0.6-9 to 1.0.6-9)
  • Migration status for spacefm/i386 (1.0.6-9 to 1.0.6-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spacefm/ppc64el (1.0.6-9 to 1.0.6-9)
  • Migration status for spacefm/ppc64el (1.0.6-9 to 1.0.6-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spacefm/riscv64 (1.0.6-9 to 1.0.6-9)
  • Migration status for spacefm/riscv64 (1.0.6-9 to 1.0.6-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spacefm/s390x (1.0.6-9 to 1.0.6-9)
  • Migration status for spacefm/s390x (1.0.6-9 to 1.0.6-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spd/amd64 (1.3.0-2 to 1.3.0-2)
  • Migration status for spd/amd64 (1.3.0-2 to 1.3.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
• spd/arm64 (1.3.0-2 to 1.3.0-2)
  • Migration status for spd/arm64 (1.3.0-2 to 1.3.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
• spd/armhf (1.3.0-2 to 1.3.0-2)
  • Migration status for spd/armhf (1.3.0-2 to 1.3.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
• spd/i386 (1.3.0-2 to 1.3.0-2)
  • Migration status for spd/i386 (1.3.0-2 to 1.3.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
• spd/ppc64el (1.3.0-2 to 1.3.0-2)
  • Migration status for spd/ppc64el (1.3.0-2 to 1.3.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
• spd/riscv64 (1.3.0-2 to 1.3.0-2)
  • Migration status for spd/riscv64 (1.3.0-2 to 1.3.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
• spd/s390x (1.3.0-2 to 1.3.0-2)
  • Migration status for spd/s390x (1.3.0-2 to 1.3.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
• spim/amd64 (8.0+dfsg-7 to 8.0+dfsg-7)
  • Migration status for spim/amd64 (8.0+dfsg-7 to 8.0+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spim/arm64 (8.0+dfsg-7 to 8.0+dfsg-7)
  • Migration status for spim/arm64 (8.0+dfsg-7 to 8.0+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spim/armhf (8.0+dfsg-7 to 8.0+dfsg-7)
  • Migration status for spim/armhf (8.0+dfsg-7 to 8.0+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spim/i386 (8.0+dfsg-7 to 8.0+dfsg-7)
  • Migration status for spim/i386 (8.0+dfsg-7 to 8.0+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spim/ppc64el (8.0+dfsg-7 to 8.0+dfsg-7)
  • Migration status for spim/ppc64el (8.0+dfsg-7 to 8.0+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spim/riscv64 (8.0+dfsg-7 to 8.0+dfsg-7)
  • Migration status for spim/riscv64 (8.0+dfsg-7 to 8.0+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spim/s390x (8.0+dfsg-7 to 8.0+dfsg-7)
  • Migration status for spim/s390x (8.0+dfsg-7 to 8.0+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splint/amd64 (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5)
  • Migration status for splint/amd64 (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splint/arm64 (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5)
  • Migration status for splint/arm64 (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splint/armhf (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5)
  • Migration status for splint/armhf (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splint/i386 (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5)
  • Migration status for splint/i386 (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splint/ppc64el (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5)
  • Migration status for splint/ppc64el (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splint/riscv64 (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5)
  • Migration status for splint/riscv64 (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splint/s390x (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5)
  • Migration status for splint/s390x (1:3.1.2+dfsg-5 to 1:3.1.2+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splitvt/amd64 (1.6.6-17 to 1.6.6-17)
  • Migration status for splitvt/amd64 (1.6.6-17 to 1.6.6-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splitvt/arm64 (1.6.6-17 to 1.6.6-17)
  • Migration status for splitvt/arm64 (1.6.6-17 to 1.6.6-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splitvt/armhf (1.6.6-17 to 1.6.6-17)
  • Migration status for splitvt/armhf (1.6.6-17 to 1.6.6-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splitvt/i386 (1.6.6-17 to 1.6.6-17)
  • Migration status for splitvt/i386 (1.6.6-17 to 1.6.6-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splitvt/ppc64el (1.6.6-17 to 1.6.6-17)
  • Migration status for splitvt/ppc64el (1.6.6-17 to 1.6.6-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splitvt/riscv64 (1.6.6-17 to 1.6.6-17)
  • Migration status for splitvt/riscv64 (1.6.6-17 to 1.6.6-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• splitvt/s390x (1.6.6-17 to 1.6.6-17)
  • Migration status for splitvt/s390x (1.6.6-17 to 1.6.6-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spring/amd64 (106.0+dfsg-4 to 106.0+dfsg-4)
  • Migration status for spring/amd64 (106.0+dfsg-4 to 106.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spring/arm64 (106.0+dfsg-4 to 106.0+dfsg-4)
  • Migration status for spring/arm64 (106.0+dfsg-4 to 106.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spring/armhf (106.0+dfsg-4 to 106.0+dfsg-4)
  • Migration status for spring/armhf (106.0+dfsg-4 to 106.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spring/i386 (106.0+dfsg-4 to 106.0+dfsg-4)
  • Migration status for spring/i386 (106.0+dfsg-4 to 106.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spring/ppc64el (106.0+dfsg-4 to 106.0+dfsg-4)
  • Migration status for spring/ppc64el (106.0+dfsg-4 to 106.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spring/riscv64 (106.0+dfsg-4 to 106.0+dfsg-4)
  • Migration status for spring/riscv64 (106.0+dfsg-4 to 106.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• spring/s390x (106.0+dfsg-4 to 106.0+dfsg-4)
  • Migration status for spring/s390x (106.0+dfsg-4 to 106.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• squidguard/amd64 (1.6.0-6 to 1.6.0-6)
  • Migration status for squidguard/amd64 (1.6.0-6 to 1.6.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• squidguard/arm64 (1.6.0-6 to 1.6.0-6)
  • Migration status for squidguard/arm64 (1.6.0-6 to 1.6.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• squidguard/armhf (1.6.0-6 to 1.6.0-6)
  • Migration status for squidguard/armhf (1.6.0-6 to 1.6.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• squidguard/i386 (1.6.0-6 to 1.6.0-6)
  • Migration status for squidguard/i386 (1.6.0-6 to 1.6.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• squidguard/ppc64el (1.6.0-6 to 1.6.0-6)
  • Migration status for squidguard/ppc64el (1.6.0-6 to 1.6.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• squidguard/riscv64 (1.6.0-6 to 1.6.0-6)
  • Migration status for squidguard/riscv64 (1.6.0-6 to 1.6.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• squidguard/s390x (1.6.0-6 to 1.6.0-6)
  • Migration status for squidguard/s390x (1.6.0-6 to 1.6.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• srain/amd64 (1.7.0-1 to 1.7.0-1)
  • Migration status for srain/amd64 (1.7.0-1 to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• srain/arm64 (1.7.0-1 to 1.7.0-1)
  • Migration status for srain/arm64 (1.7.0-1 to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• srain/armhf (1.7.0-1 to 1.7.0-1)
  • Migration status for srain/armhf (1.7.0-1 to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• srain/i386 (1.7.0-1 to 1.7.0-1)
  • Migration status for srain/i386 (1.7.0-1 to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• srain/ppc64el (1.7.0-1 to 1.7.0-1)
  • Migration status for srain/ppc64el (1.7.0-1 to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• srain/riscv64 (1.7.0-1 to 1.7.0-1)
  • Migration status for srain/riscv64 (1.7.0-1 to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• srain/s390x (1.7.0-1 to 1.7.0-1)
  • Migration status for srain/s390x (1.7.0-1 to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sshguard/amd64 (2.4.3-1 to 2.4.3-1)
  • Migration status for sshguard/amd64 (2.4.3-1 to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sshguard/arm64 (2.4.3-1 to 2.4.3-1)
  • Migration status for sshguard/arm64 (2.4.3-1 to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sshguard/armhf (2.4.3-1 to 2.4.3-1)
  • Migration status for sshguard/armhf (2.4.3-1 to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sshguard/i386 (2.4.3-1 to 2.4.3-1)
  • Migration status for sshguard/i386 (2.4.3-1 to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sshguard/ppc64el (2.4.3-1 to 2.4.3-1)
  • Migration status for sshguard/ppc64el (2.4.3-1 to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sshguard/riscv64 (2.4.3-1 to 2.4.3-1)
  • Migration status for sshguard/riscv64 (2.4.3-1 to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sshguard/s390x (2.4.3-1 to 2.4.3-1)
  • Migration status for sshguard/s390x (2.4.3-1 to 2.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ssvnc/amd64 (1.0.29-6.1 to 1.0.29-6.1)
  • Migration status for ssvnc/amd64 (1.0.29-6.1 to 1.0.29-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ssvnc/arm64 (1.0.29-6.1 to 1.0.29-6.1)
  • Migration status for ssvnc/arm64 (1.0.29-6.1 to 1.0.29-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ssvnc/armhf (1.0.29-6.1 to 1.0.29-6.1)
  • Migration status for ssvnc/armhf (1.0.29-6.1 to 1.0.29-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ssvnc/i386 (1.0.29-6.1 to 1.0.29-6.1)
  • Migration status for ssvnc/i386 (1.0.29-6.1 to 1.0.29-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ssvnc/ppc64el (1.0.29-6.1 to 1.0.29-6.1)
  • Migration status for ssvnc/ppc64el (1.0.29-6.1 to 1.0.29-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ssvnc/riscv64 (1.0.29-6.1 to 1.0.29-6.1)
  • Migration status for ssvnc/riscv64 (1.0.29-6.1 to 1.0.29-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ssvnc/s390x (1.0.29-6.1 to 1.0.29-6.1)
  • Migration status for ssvnc/s390x (1.0.29-6.1 to 1.0.29-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sumo/amd64 (1.18.0+dfsg-4 to 1.18.0+dfsg-4)
  • Migration status for sumo/amd64 (1.18.0+dfsg-4 to 1.18.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sumo/arm64 (1.18.0+dfsg-4 to 1.18.0+dfsg-4)
  • Migration status for sumo/arm64 (1.18.0+dfsg-4 to 1.18.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sumo/armhf (1.18.0+dfsg-4 to 1.18.0+dfsg-4)
  • Migration status for sumo/armhf (1.18.0+dfsg-4 to 1.18.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sumo/i386 (1.18.0+dfsg-4 to 1.18.0+dfsg-4)
  • Migration status for sumo/i386 (1.18.0+dfsg-4 to 1.18.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sumo/ppc64el (1.18.0+dfsg-4 to 1.18.0+dfsg-4)
  • Migration status for sumo/ppc64el (1.18.0+dfsg-4 to 1.18.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sumo/riscv64 (1.18.0+dfsg-4 to 1.18.0+dfsg-4)
  • Migration status for sumo/riscv64 (1.18.0+dfsg-4 to 1.18.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sumo/s390x (1.18.0+dfsg-4 to 1.18.0+dfsg-4)
  • Migration status for sumo/s390x (1.18.0+dfsg-4 to 1.18.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• super/amd64 (3.30.3-2 to 3.30.3-2)
  • Migration status for super/amd64 (3.30.3-2 to 3.30.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
• super/arm64 (3.30.3-2 to 3.30.3-2)
  • Migration status for super/arm64 (3.30.3-2 to 3.30.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
• super/armhf (3.30.3-2 to 3.30.3-2)
  • Migration status for super/armhf (3.30.3-2 to 3.30.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
• super/i386 (3.30.3-2 to 3.30.3-2)
  • Migration status for super/i386 (3.30.3-2 to 3.30.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
• super/ppc64el (3.30.3-2 to 3.30.3-2)
  • Migration status for super/ppc64el (3.30.3-2 to 3.30.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
• super/riscv64 (3.30.3-2 to 3.30.3-2)
  • Migration status for super/riscv64 (3.30.3-2 to 3.30.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
• super/s390x (3.30.3-2 to 3.30.3-2)
  • Migration status for super/s390x (3.30.3-2 to 3.30.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
• sweed/amd64 (3.2.1+dfsg-6 to 3.2.1+dfsg-6)
  • Migration status for sweed/amd64 (3.2.1+dfsg-6 to 3.2.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sweed/arm64 (3.2.1+dfsg-6 to 3.2.1+dfsg-6)
  • Migration status for sweed/arm64 (3.2.1+dfsg-6 to 3.2.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sweed/armhf (3.2.1+dfsg-6 to 3.2.1+dfsg-6)
  • Migration status for sweed/armhf (3.2.1+dfsg-6 to 3.2.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sweed/i386 (3.2.1+dfsg-6 to 3.2.1+dfsg-6)
  • Migration status for sweed/i386 (3.2.1+dfsg-6 to 3.2.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sweed/ppc64el (3.2.1+dfsg-6 to 3.2.1+dfsg-6)
  • Migration status for sweed/ppc64el (3.2.1+dfsg-6 to 3.2.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sweed/riscv64 (3.2.1+dfsg-6 to 3.2.1+dfsg-6)
  • Migration status for sweed/riscv64 (3.2.1+dfsg-6 to 3.2.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sweed/s390x (3.2.1+dfsg-6 to 3.2.1+dfsg-6)
  • Migration status for sweed/s390x (3.2.1+dfsg-6 to 3.2.1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sylpheed/amd64 (3.8.0~beta1-2 to 3.8.0~beta1-2)
  • Migration status for sylpheed/amd64 (3.8.0~beta1-2 to 3.8.0~beta1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sylpheed/arm64 (3.8.0~beta1-2 to 3.8.0~beta1-2)
  • Migration status for sylpheed/arm64 (3.8.0~beta1-2 to 3.8.0~beta1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sylpheed/armhf (3.8.0~beta1-2 to 3.8.0~beta1-2)
  • Migration status for sylpheed/armhf (3.8.0~beta1-2 to 3.8.0~beta1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sylpheed/i386 (3.8.0~beta1-2 to 3.8.0~beta1-2)
  • Migration status for sylpheed/i386 (3.8.0~beta1-2 to 3.8.0~beta1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sylpheed/ppc64el (3.8.0~beta1-2 to 3.8.0~beta1-2)
  • Migration status for sylpheed/ppc64el (3.8.0~beta1-2 to 3.8.0~beta1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sylpheed/riscv64 (3.8.0~beta1-2 to 3.8.0~beta1-2)
  • Migration status for sylpheed/riscv64 (3.8.0~beta1-2 to 3.8.0~beta1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• sylpheed/s390x (3.8.0~beta1-2 to 3.8.0~beta1-2)
  • Migration status for sylpheed/s390x (3.8.0~beta1-2 to 3.8.0~beta1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• systemd-boot-efi-amd64-signed_pu (258+1 to 257.8+1~deb13u2)
  • Migration status for systemd-boot-efi-amd64-signed_pu (258+1 to 257.8+1~deb13u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: systemd-boot-efi-amd64-signed is newer in the target suite (258+1 257.8+1~deb13u2)
• systemd-boot-efi-arm64-signed_pu (258+1 to 257.8+1~deb13u2)
  • Migration status for systemd-boot-efi-arm64-signed_pu (258+1 to 257.8+1~deb13u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: systemd-boot-efi-arm64-signed is newer in the target suite (258+1 257.8+1~deb13u2)
• systemd_pu (258-1 to 257.8-1~deb13u2)
  • Migration status for systemd_pu (258-1 to 257.8-1~deb13u2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ALERT: systemd is newer in the target suite (258-1 257.8-1~deb13u2)
• tart/amd64 (3.10-2 to 3.10-2)
  • Migration status for tart/amd64 (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tart/arm64 (3.10-2 to 3.10-2)
  • Migration status for tart/arm64 (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tart/armhf (3.10-2 to 3.10-2)
  • Migration status for tart/armhf (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tart/i386 (3.10-2 to 3.10-2)
  • Migration status for tart/i386 (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tart/ppc64el (3.10-2 to 3.10-2)
  • Migration status for tart/ppc64el (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tart/riscv64 (3.10-2 to 3.10-2)
  • Migration status for tart/riscv64 (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tart/s390x (3.10-2 to 3.10-2)
  • Migration status for tart/s390x (3.10-2 to 3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tcpspy/amd64 (1.7d-16 to 1.7d-16)
  • Migration status for tcpspy/amd64 (1.7d-16 to 1.7d-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tcpspy/arm64 (1.7d-16 to 1.7d-16)
  • Migration status for tcpspy/arm64 (1.7d-16 to 1.7d-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tcpspy/armhf (1.7d-16 to 1.7d-16)
  • Migration status for tcpspy/armhf (1.7d-16 to 1.7d-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tcpspy/i386 (1.7d-16 to 1.7d-16)
  • Migration status for tcpspy/i386 (1.7d-16 to 1.7d-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tcpspy/ppc64el (1.7d-16 to 1.7d-16)
  • Migration status for tcpspy/ppc64el (1.7d-16 to 1.7d-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tcpspy/riscv64 (1.7d-16 to 1.7d-16)
  • Migration status for tcpspy/riscv64 (1.7d-16 to 1.7d-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tcpspy/s390x (1.7d-16 to 1.7d-16)
  • Migration status for tcpspy/s390x (1.7d-16 to 1.7d-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• thesias/amd64 (3.1.1-3 to 3.1.1-3)
  • Migration status for thesias/amd64 (3.1.1-3 to 3.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• thesias/arm64 (3.1.1-3 to 3.1.1-3)
  • Migration status for thesias/arm64 (3.1.1-3 to 3.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• thesias/armhf (3.1.1-3 to 3.1.1-3)
  • Migration status for thesias/armhf (3.1.1-3 to 3.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• thesias/i386 (3.1.1-3 to 3.1.1-3)
  • Migration status for thesias/i386 (3.1.1-3 to 3.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• thesias/ppc64el (3.1.1-3 to 3.1.1-3)
  • Migration status for thesias/ppc64el (3.1.1-3 to 3.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• thesias/riscv64 (3.1.1-3 to 3.1.1-3)
  • Migration status for thesias/riscv64 (3.1.1-3 to 3.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• thesias/s390x (3.1.1-3 to 3.1.1-3)
  • Migration status for thesias/s390x (3.1.1-3 to 3.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ticker/amd64 (1.15 to 1.15)
  • Migration status for ticker/amd64 (1.15 to 1.15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ticker/arm64 (1.15 to 1.15)
  • Migration status for ticker/arm64 (1.15 to 1.15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ticker/armhf (1.15 to 1.15)
  • Migration status for ticker/armhf (1.15 to 1.15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ticker/i386 (1.15 to 1.15)
  • Migration status for ticker/i386 (1.15 to 1.15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ticker/ppc64el (1.15 to 1.15)
  • Migration status for ticker/ppc64el (1.15 to 1.15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ticker/riscv64 (1.15 to 1.15)
  • Migration status for ticker/riscv64 (1.15 to 1.15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ticker/s390x (1.15 to 1.15)
  • Migration status for ticker/s390x (1.15 to 1.15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tickr/amd64 (0.7.1-1 to 0.7.1-1)
  • Migration status for tickr/amd64 (0.7.1-1 to 0.7.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
• tickr/arm64 (0.7.1-1 to 0.7.1-1)
  • Migration status for tickr/arm64 (0.7.1-1 to 0.7.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
• tickr/armhf (0.7.1-1 to 0.7.1-1)
  • Migration status for tickr/armhf (0.7.1-1 to 0.7.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
• tickr/i386 (0.7.1-1 to 0.7.1-1)
  • Migration status for tickr/i386 (0.7.1-1 to 0.7.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
• tickr/ppc64el (0.7.1-1 to 0.7.1-1)
  • Migration status for tickr/ppc64el (0.7.1-1 to 0.7.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
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tickr/s390x (0.7.1-1 to 0.7.1-1)
  • Migration status for tickr/s390x (0.7.1-1 to 0.7.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
• tkgate/amd64 (2.1+repack-7 to 2.1+repack-7)
  • Migration status for tkgate/amd64 (2.1+repack-7 to 2.1+repack-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tkgate/arm64 (2.1+repack-7 to 2.1+repack-7)
  • Migration status for tkgate/arm64 (2.1+repack-7 to 2.1+repack-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tkgate/armhf (2.1+repack-7 to 2.1+repack-7)
  • Migration status for tkgate/armhf (2.1+repack-7 to 2.1+repack-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tkgate/i386 (2.1+repack-7 to 2.1+repack-7)
  • Migration status for tkgate/i386 (2.1+repack-7 to 2.1+repack-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tkgate/ppc64el (2.1+repack-7 to 2.1+repack-7)
  • Migration status for tkgate/ppc64el (2.1+repack-7 to 2.1+repack-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tkgate/riscv64 (2.1+repack-7 to 2.1+repack-7)
  • Migration status for tkgate/riscv64 (2.1+repack-7 to 2.1+repack-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tkgate/s390x (2.1+repack-7 to 2.1+repack-7)
  • Migration status for tkgate/s390x (2.1+repack-7 to 2.1+repack-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tracetuner/amd64 (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3)
  • Migration status for tracetuner/amd64 (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tracetuner/arm64 (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3)
  • Migration status for tracetuner/arm64 (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tracetuner/armhf (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3)
  • Migration status for tracetuner/armhf (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tracetuner/i386 (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3)
  • Migration status for tracetuner/i386 (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tracetuner/ppc64el (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3)
  • Migration status for tracetuner/ppc64el (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tracetuner/riscv64 (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3)
  • Migration status for tracetuner/riscv64 (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• tracetuner/s390x (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3)
  • Migration status for tracetuner/s390x (3.0.6~beta+dfsg-3 to 3.0.6~beta+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• transmission/amd64 (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5)
  • Migration status for transmission/amd64 (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: transmission/amd64 miniupnpc (not considered)
    • Invalidated by dependency
• transmission/arm64 (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5)
  • Migration status for transmission/arm64 (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: transmission/arm64 miniupnpc (not considered)
    • Invalidated by dependency
• transmission/armhf (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5)
  • Migration status for transmission/armhf (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: transmission/armhf miniupnpc (not considered)
    • Invalidated by dependency
• transmission/i386 (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5)
  • Migration status for transmission/i386 (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: transmission/i386 miniupnpc (not considered)
    • Invalidated by dependency
• transmission/ppc64el (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5)
  • Migration status for transmission/ppc64el (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: transmission/ppc64el miniupnpc (not considered)
    • Invalidated by dependency
• transmission/riscv64 (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5)
  • Migration status for transmission/riscv64 (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: transmission/riscv64 miniupnpc (not considered)
    • Invalidated by dependency
• transmission/s390x (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5)
  • Migration status for transmission/s390x (4.1.0~beta2+dfsg-5 to 4.1.0~beta2+dfsg-5): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: transmission/s390x miniupnpc (not considered)
    • Invalidated by dependency
• uci2wb/amd64 (4.1+git200714-1.2 to 4.1+git200714-1.2)
  • Migration status for uci2wb/amd64 (4.1+git200714-1.2 to 4.1+git200714-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
• uci2wb/arm64 (4.1+git200714-1.2 to 4.1+git200714-1.2)
  • Migration status for uci2wb/arm64 (4.1+git200714-1.2 to 4.1+git200714-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
• uci2wb/armhf (4.1+git200714-1.2 to 4.1+git200714-1.2)
  • Migration status for uci2wb/armhf (4.1+git200714-1.2 to 4.1+git200714-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
• uci2wb/i386 (4.1+git200714-1.2 to 4.1+git200714-1.2)
  • Migration status for uci2wb/i386 (4.1+git200714-1.2 to 4.1+git200714-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
• uci2wb/ppc64el (4.1+git200714-1.2 to 4.1+git200714-1.2)
  • Migration status for uci2wb/ppc64el (4.1+git200714-1.2 to 4.1+git200714-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
• uci2wb/riscv64 (4.1+git200714-1.2 to 4.1+git200714-1.2)
  • Migration status for uci2wb/riscv64 (4.1+git200714-1.2 to 4.1+git200714-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
• uci2wb/s390x (4.1+git200714-1.2 to 4.1+git200714-1.2)
  • Migration status for uci2wb/s390x (4.1+git200714-1.2 to 4.1+git200714-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
• udevil/amd64 (0.4.4-4 to 0.4.4-4)
  • Migration status for udevil/amd64 (0.4.4-4 to 0.4.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• udevil/arm64 (0.4.4-4 to 0.4.4-4)
  • Migration status for udevil/arm64 (0.4.4-4 to 0.4.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• udevil/armhf (0.4.4-4 to 0.4.4-4)
  • Migration status for udevil/armhf (0.4.4-4 to 0.4.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• udevil/i386 (0.4.4-4 to 0.4.4-4)
  • Migration status for udevil/i386 (0.4.4-4 to 0.4.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• udevil/ppc64el (0.4.4-4 to 0.4.4-4)
  • Migration status for udevil/ppc64el (0.4.4-4 to 0.4.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• udevil/riscv64 (0.4.4-4 to 0.4.4-4)
  • Migration status for udevil/riscv64 (0.4.4-4 to 0.4.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• udevil/s390x (0.4.4-4 to 0.4.4-4)
  • Migration status for udevil/s390x (0.4.4-4 to 0.4.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• up-imapproxy/amd64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/amd64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• up-imapproxy/arm64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/arm64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• up-imapproxy/armhf (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/armhf (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• up-imapproxy/i386 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/i386 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• up-imapproxy/ppc64el (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/ppc64el (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• up-imapproxy/riscv64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/riscv64 (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• up-imapproxy/s390x (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2)
  • Migration status for up-imapproxy/s390x (1.2.8~svn20171105-2 to 1.2.8~svn20171105-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vecgeom/amd64 (1.2.8+dfsg-2 to 1.2.8+dfsg-2)
  • Migration status for vecgeom/amd64 (1.2.8+dfsg-2 to 1.2.8+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vecgeom/arm64 (1.2.8+dfsg-2 to 1.2.8+dfsg-2)
  • Migration status for vecgeom/arm64 (1.2.8+dfsg-2 to 1.2.8+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vecgeom/armhf (1.2.8+dfsg-2 to 1.2.8+dfsg-2)
  • Migration status for vecgeom/armhf (1.2.8+dfsg-2 to 1.2.8+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vecgeom/i386 (1.2.8+dfsg-2 to 1.2.8+dfsg-2)
  • Migration status for vecgeom/i386 (1.2.8+dfsg-2 to 1.2.8+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vecgeom/ppc64el (1.2.8+dfsg-2 to 1.2.8+dfsg-2)
  • Migration status for vecgeom/ppc64el (1.2.8+dfsg-2 to 1.2.8+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vecgeom/riscv64 (1.2.8+dfsg-2 to 1.2.8+dfsg-2)
  • Migration status for vecgeom/riscv64 (1.2.8+dfsg-2 to 1.2.8+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vecgeom/s390x (1.2.8+dfsg-2 to 1.2.8+dfsg-2)
  • Migration status for vecgeom/s390x (1.2.8+dfsg-2 to 1.2.8+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• viking/amd64 (1.10-4 to 1.10-4)
  • Migration status for viking/amd64 (1.10-4 to 1.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• viking/arm64 (1.10-4 to 1.10-4)
  • Migration status for viking/arm64 (1.10-4 to 1.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• viking/armhf (1.10-4 to 1.10-4)
  • Migration status for viking/armhf (1.10-4 to 1.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• viking/i386 (1.10-4 to 1.10-4)
  • Migration status for viking/i386 (1.10-4 to 1.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• viking/ppc64el (1.10-4 to 1.10-4)
  • Migration status for viking/ppc64el (1.10-4 to 1.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• viking/riscv64 (1.10-4 to 1.10-4)
  • Migration status for viking/riscv64 (1.10-4 to 1.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• viking/s390x (1.10-4 to 1.10-4)
  • Migration status for viking/s390x (1.10-4 to 1.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vrfy/amd64 (990522-11 to 990522-11)
  • Migration status for vrfy/amd64 (990522-11 to 990522-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vrfy/arm64 (990522-11 to 990522-11)
  • Migration status for vrfy/arm64 (990522-11 to 990522-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vrfy/armhf (990522-11 to 990522-11)
  • Migration status for vrfy/armhf (990522-11 to 990522-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vrfy/i386 (990522-11 to 990522-11)
  • Migration status for vrfy/i386 (990522-11 to 990522-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vrfy/ppc64el (990522-11 to 990522-11)
  • Migration status for vrfy/ppc64el (990522-11 to 990522-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vrfy/riscv64 (990522-11 to 990522-11)
  • Migration status for vrfy/riscv64 (990522-11 to 990522-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• vrfy/s390x (990522-11 to 990522-11)
  • Migration status for vrfy/s390x (990522-11 to 990522-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w-scan/amd64 (20210218-1 to 20210218-1)
  • Migration status for w-scan/amd64 (20210218-1 to 20210218-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w-scan/arm64 (20210218-1 to 20210218-1)
  • Migration status for w-scan/arm64 (20210218-1 to 20210218-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w-scan/armhf (20210218-1 to 20210218-1)
  • Migration status for w-scan/armhf (20210218-1 to 20210218-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w-scan/i386 (20210218-1 to 20210218-1)
  • Migration status for w-scan/i386 (20210218-1 to 20210218-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w-scan/ppc64el (20210218-1 to 20210218-1)
  • Migration status for w-scan/ppc64el (20210218-1 to 20210218-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w-scan/riscv64 (20210218-1 to 20210218-1)
  • Migration status for w-scan/riscv64 (20210218-1 to 20210218-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w-scan/s390x (20210218-1 to 20210218-1)
  • Migration status for w-scan/s390x (20210218-1 to 20210218-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w1retap/amd64 (1.5.5-2 to 1.5.5-2)
  • Migration status for w1retap/amd64 (1.5.5-2 to 1.5.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w1retap/arm64 (1.5.5-2 to 1.5.5-2)
  • Migration status for w1retap/arm64 (1.5.5-2 to 1.5.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w1retap/armhf (1.5.5-2 to 1.5.5-2)
  • Migration status for w1retap/armhf (1.5.5-2 to 1.5.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w1retap/i386 (1.5.5-2 to 1.5.5-2)
  • Migration status for w1retap/i386 (1.5.5-2 to 1.5.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w1retap/ppc64el (1.5.5-2 to 1.5.5-2)
  • Migration status for w1retap/ppc64el (1.5.5-2 to 1.5.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w1retap/riscv64 (1.5.5-2 to 1.5.5-2)
  • Migration status for w1retap/riscv64 (1.5.5-2 to 1.5.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• w1retap/s390x (1.5.5-2 to 1.5.5-2)
  • Migration status for w1retap/s390x (1.5.5-2 to 1.5.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• warzone2100/amd64 (4.5.5deb-1 to 4.5.5deb-1)
  • Migration status for warzone2100/amd64 (4.5.5deb-1 to 4.5.5deb-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• warzone2100/arm64 (4.5.5deb-1 to 4.5.5deb-1)
  • Migration status for warzone2100/arm64 (4.5.5deb-1 to 4.5.5deb-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• warzone2100/armhf (4.5.5deb-1 to 4.5.5deb-1)
  • Migration status for warzone2100/armhf (4.5.5deb-1 to 4.5.5deb-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• warzone2100/i386 (4.5.5deb-1 to 4.5.5deb-1)
  • Migration status for warzone2100/i386 (4.5.5deb-1 to 4.5.5deb-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• warzone2100/ppc64el (4.5.5deb-1 to 4.5.5deb-1)
  • Migration status for warzone2100/ppc64el (4.5.5deb-1 to 4.5.5deb-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• warzone2100/riscv64 (4.5.5deb-1 to 4.5.5deb-1)
  • Migration status for warzone2100/riscv64 (4.5.5deb-1 to 4.5.5deb-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• warzone2100/s390x (4.5.5deb-1 to 4.5.5deb-1)
  • Migration status for warzone2100/s390x (4.5.5deb-1 to 4.5.5deb-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wdm/amd64 (1.28-27 to 1.28-27)
  • Migration status for wdm/amd64 (1.28-27 to 1.28-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wdm/arm64 (1.28-27 to 1.28-27)
  • Migration status for wdm/arm64 (1.28-27 to 1.28-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wdm/armhf (1.28-27 to 1.28-27)
  • Migration status for wdm/armhf (1.28-27 to 1.28-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wdm/i386 (1.28-27 to 1.28-27)
  • Migration status for wdm/i386 (1.28-27 to 1.28-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wdm/ppc64el (1.28-27 to 1.28-27)
  • Migration status for wdm/ppc64el (1.28-27 to 1.28-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wdm/riscv64 (1.28-27 to 1.28-27)
  • Migration status for wdm/riscv64 (1.28-27 to 1.28-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wdm/s390x (1.28-27 to 1.28-27)
  • Migration status for wdm/s390x (1.28-27 to 1.28-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wf-config/amd64 (0.9.0-2 to 0.9.0-2)
  • Migration status for wf-config/amd64 (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libwf-config1/0.9.0-2+b1/amd64 to testing makes reform-firedecor/2023-10-23-8+b1/amd64 uninstallable
• wf-config/arm64 (0.9.0-2 to 0.9.0-2)
  • Migration status for wf-config/arm64 (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libwf-config1/0.9.0-2+b1/arm64 to testing makes reform-firedecor/2023-10-23-8+b1/arm64 uninstallable
• wf-config/armhf (0.9.0-2 to 0.9.0-2)
  • Migration status for wf-config/armhf (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libwf-config1/0.9.0-2+b1/armhf to testing makes reform-firedecor/2023-10-23-8+b1/armhf uninstallable
• wf-config/i386 (0.9.0-2 to 0.9.0-2)
  • Migration status for wf-config/i386 (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libwf-config1/0.9.0-2+b1/i386 to testing makes reform-firedecor/2023-10-23-8+b1/i386 uninstallable
• wf-config/ppc64el (0.9.0-2 to 0.9.0-2)
  • Migration status for wf-config/ppc64el (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libwf-config1/0.9.0-2+b1/ppc64el to testing makes reform-firedecor/2023-10-23-8+b1/ppc64el uninstallable
• wf-config/riscv64 (0.9.0-2 to 0.9.0-2)
  • Migration status for wf-config/riscv64 (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libwf-config1/0.9.0-2+b1/riscv64 to testing makes reform-firedecor/2023-10-23-8+b1/riscv64 uninstallable
• wf-config/s390x (0.9.0-2 to 0.9.0-2)
  • Migration status for wf-config/s390x (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libwf-config1/0.9.0-2+b1/s390x to testing makes reform-firedecor/2023-10-23-8+b1/s390x uninstallable
• widelands/amd64 (2:1.2.1-3 to 2:1.2.1-3)
  • Migration status for widelands/amd64 (2:1.2.1-3 to 2:1.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• widelands/arm64 (2:1.2.1-3 to 2:1.2.1-3)
  • Migration status for widelands/arm64 (2:1.2.1-3 to 2:1.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• widelands/armhf (2:1.2.1-3 to 2:1.2.1-3)
  • Migration status for widelands/armhf (2:1.2.1-3 to 2:1.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• widelands/i386 (2:1.2.1-3 to 2:1.2.1-3)
  • Migration status for widelands/i386 (2:1.2.1-3 to 2:1.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• widelands/ppc64el (2:1.2.1-3 to 2:1.2.1-3)
  • Migration status for widelands/ppc64el (2:1.2.1-3 to 2:1.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• widelands/riscv64 (2:1.2.1-3 to 2:1.2.1-3)
  • Migration status for widelands/riscv64 (2:1.2.1-3 to 2:1.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• widelands/s390x (2:1.2.1-3 to 2:1.2.1-3)
  • Migration status for widelands/s390x (2:1.2.1-3 to 2:1.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wit/amd64 (3.01a-5 to 3.01a-5)
  • Migration status for wit/amd64 (3.01a-5 to 3.01a-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wit/arm64 (3.01a-5 to 3.01a-5)
  • Migration status for wit/arm64 (3.01a-5 to 3.01a-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wit/armhf (3.01a-5 to 3.01a-5)
  • Migration status for wit/armhf (3.01a-5 to 3.01a-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wit/i386 (3.01a-5 to 3.01a-5)
  • Migration status for wit/i386 (3.01a-5 to 3.01a-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wit/ppc64el (3.01a-5 to 3.01a-5)
  • Migration status for wit/ppc64el (3.01a-5 to 3.01a-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wit/riscv64 (3.01a-5 to 3.01a-5)
  • Migration status for wit/riscv64 (3.01a-5 to 3.01a-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wit/s390x (3.01a-5 to 3.01a-5)
  • Migration status for wit/s390x (3.01a-5 to 3.01a-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wnn6-sdk/amd64 (1.0.0-21 to 1.0.0-21)
  • Migration status for wnn6-sdk/amd64 (1.0.0-21 to 1.0.0-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wnn6-sdk/arm64 (1.0.0-21 to 1.0.0-21)
  • Migration status for wnn6-sdk/arm64 (1.0.0-21 to 1.0.0-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wnn6-sdk/armhf (1.0.0-21 to 1.0.0-21)
  • Migration status for wnn6-sdk/armhf (1.0.0-21 to 1.0.0-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wnn6-sdk/i386 (1.0.0-21 to 1.0.0-21)
  • Migration status for wnn6-sdk/i386 (1.0.0-21 to 1.0.0-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wnn6-sdk/ppc64el (1.0.0-21 to 1.0.0-21)
  • Migration status for wnn6-sdk/ppc64el (1.0.0-21 to 1.0.0-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wnn6-sdk/riscv64 (1.0.0-21 to 1.0.0-21)
  • Migration status for wnn6-sdk/riscv64 (1.0.0-21 to 1.0.0-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wnn6-sdk/s390x (1.0.0-21 to 1.0.0-21)
  • Migration status for wnn6-sdk/s390x (1.0.0-21 to 1.0.0-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wtdbg2/amd64 (2.5-10 to 2.5-10)
  • Migration status for wtdbg2/amd64 (2.5-10 to 2.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wtdbg2/arm64 (2.5-10 to 2.5-10)
  • Migration status for wtdbg2/arm64 (2.5-10 to 2.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wtdbg2/armhf (2.5-10 to 2.5-10)
  • Migration status for wtdbg2/armhf (2.5-10 to 2.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wtdbg2/i386 (2.5-10 to 2.5-10)
  • Migration status for wtdbg2/i386 (2.5-10 to 2.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wtdbg2/ppc64el (2.5-10 to 2.5-10)
  • Migration status for wtdbg2/ppc64el (2.5-10 to 2.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wtdbg2/riscv64 (2.5-10 to 2.5-10)
  • Migration status for wtdbg2/riscv64 (2.5-10 to 2.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• wtdbg2/s390x (2.5-10 to 2.5-10)
  • Migration status for wtdbg2/s390x (2.5-10 to 2.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xarclock/amd64 (1.0-20 to 1.0-20)
  • Migration status for xarclock/amd64 (1.0-20 to 1.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xarclock/arm64 (1.0-20 to 1.0-20)
  • Migration status for xarclock/arm64 (1.0-20 to 1.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xarclock/armhf (1.0-20 to 1.0-20)
  • Migration status for xarclock/armhf (1.0-20 to 1.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xarclock/i386 (1.0-20 to 1.0-20)
  • Migration status for xarclock/i386 (1.0-20 to 1.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xarclock/ppc64el (1.0-20 to 1.0-20)
  • Migration status for xarclock/ppc64el (1.0-20 to 1.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xarclock/riscv64 (1.0-20 to 1.0-20)
  • Migration status for xarclock/riscv64 (1.0-20 to 1.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xarclock/s390x (1.0-20 to 1.0-20)
  • Migration status for xarclock/s390x (1.0-20 to 1.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbubble/amd64 (0.5.11.2-4 to 0.5.11.2-4)
  • Migration status for xbubble/amd64 (0.5.11.2-4 to 0.5.11.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbubble/arm64 (0.5.11.2-4 to 0.5.11.2-4)
  • Migration status for xbubble/arm64 (0.5.11.2-4 to 0.5.11.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbubble/armhf (0.5.11.2-4 to 0.5.11.2-4)
  • Migration status for xbubble/armhf (0.5.11.2-4 to 0.5.11.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbubble/i386 (0.5.11.2-4 to 0.5.11.2-4)
  • Migration status for xbubble/i386 (0.5.11.2-4 to 0.5.11.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbubble/ppc64el (0.5.11.2-4 to 0.5.11.2-4)
  • Migration status for xbubble/ppc64el (0.5.11.2-4 to 0.5.11.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbubble/riscv64 (0.5.11.2-4 to 0.5.11.2-4)
  • Migration status for xbubble/riscv64 (0.5.11.2-4 to 0.5.11.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbubble/s390x (0.5.11.2-4 to 0.5.11.2-4)
  • Migration status for xbubble/s390x (0.5.11.2-4 to 0.5.11.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbuffy/amd64 (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11)
  • Migration status for xbuffy/amd64 (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbuffy/arm64 (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11)
  • Migration status for xbuffy/arm64 (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbuffy/armhf (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11)
  • Migration status for xbuffy/armhf (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbuffy/i386 (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11)
  • Migration status for xbuffy/i386 (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbuffy/ppc64el (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11)
  • Migration status for xbuffy/ppc64el (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbuffy/riscv64 (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11)
  • Migration status for xbuffy/riscv64 (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xbuffy/s390x (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11)
  • Migration status for xbuffy/s390x (3.3.bl.3.dfsg-11 to 3.3.bl.3.dfsg-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xcolorsel/amd64 (1.1a-23 to 1.1a-23)
  • Migration status for xcolorsel/amd64 (1.1a-23 to 1.1a-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xcolorsel/arm64 (1.1a-23 to 1.1a-23)
  • Migration status for xcolorsel/arm64 (1.1a-23 to 1.1a-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xcolorsel/armhf (1.1a-23 to 1.1a-23)
  • Migration status for xcolorsel/armhf (1.1a-23 to 1.1a-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xcolorsel/i386 (1.1a-23 to 1.1a-23)
  • Migration status for xcolorsel/i386 (1.1a-23 to 1.1a-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xcolorsel/ppc64el (1.1a-23 to 1.1a-23)
  • Migration status for xcolorsel/ppc64el (1.1a-23 to 1.1a-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xcolorsel/riscv64 (1.1a-23 to 1.1a-23)
  • Migration status for xcolorsel/riscv64 (1.1a-23 to 1.1a-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xcolorsel/s390x (1.1a-23 to 1.1a-23)
  • Migration status for xcolorsel/s390x (1.1a-23 to 1.1a-23): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdu/amd64 (3.0-20 to 3.0-20)
  • Migration status for xdu/amd64 (3.0-20 to 3.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdu/arm64 (3.0-20 to 3.0-20)
  • Migration status for xdu/arm64 (3.0-20 to 3.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdu/armhf (3.0-20 to 3.0-20)
  • Migration status for xdu/armhf (3.0-20 to 3.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdu/i386 (3.0-20 to 3.0-20)
  • Migration status for xdu/i386 (3.0-20 to 3.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdu/ppc64el (3.0-20 to 3.0-20)
  • Migration status for xdu/ppc64el (3.0-20 to 3.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdu/riscv64 (3.0-20 to 3.0-20)
  • Migration status for xdu/riscv64 (3.0-20 to 3.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdu/s390x (3.0-20 to 3.0-20)
  • Migration status for xdu/s390x (3.0-20 to 3.0-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdvik-ja/amd64 (22.87.06+j1.42-3 to 22.87.06+j1.42-3)
  • Migration status for xdvik-ja/amd64 (22.87.06+j1.42-3 to 22.87.06+j1.42-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdvik-ja/arm64 (22.87.06+j1.42-3 to 22.87.06+j1.42-3)
  • Migration status for xdvik-ja/arm64 (22.87.06+j1.42-3 to 22.87.06+j1.42-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdvik-ja/armhf (22.87.06+j1.42-3 to 22.87.06+j1.42-3)
  • Migration status for xdvik-ja/armhf (22.87.06+j1.42-3 to 22.87.06+j1.42-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdvik-ja/i386 (22.87.06+j1.42-3 to 22.87.06+j1.42-3)
  • Migration status for xdvik-ja/i386 (22.87.06+j1.42-3 to 22.87.06+j1.42-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdvik-ja/ppc64el (22.87.06+j1.42-3 to 22.87.06+j1.42-3)
  • Migration status for xdvik-ja/ppc64el (22.87.06+j1.42-3 to 22.87.06+j1.42-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xdvik-ja/s390x (22.87.06+j1.42-3 to 22.87.06+j1.42-3)
  • Migration status for xdvik-ja/s390x (22.87.06+j1.42-3 to 22.87.06+j1.42-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfaces/amd64 (3.3-30.3 to 3.3-30.3)
  • Migration status for xfaces/amd64 (3.3-30.3 to 3.3-30.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfaces/arm64 (3.3-30.3 to 3.3-30.3)
  • Migration status for xfaces/arm64 (3.3-30.3 to 3.3-30.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfaces/armhf (3.3-30.3 to 3.3-30.3)
  • Migration status for xfaces/armhf (3.3-30.3 to 3.3-30.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfaces/i386 (3.3-30.3 to 3.3-30.3)
  • Migration status for xfaces/i386 (3.3-30.3 to 3.3-30.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfaces/ppc64el (3.3-30.3 to 3.3-30.3)
  • Migration status for xfaces/ppc64el (3.3-30.3 to 3.3-30.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfaces/riscv64 (3.3-30.3 to 3.3-30.3)
  • Migration status for xfaces/riscv64 (3.3-30.3 to 3.3-30.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfaces/s390x (3.3-30.3 to 3.3-30.3)
  • Migration status for xfaces/s390x (3.3-30.3 to 3.3-30.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfrisk/amd64 (1.2-10 to 1.2-10)
  • Migration status for xfrisk/amd64 (1.2-10 to 1.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfrisk/arm64 (1.2-10 to 1.2-10)
  • Migration status for xfrisk/arm64 (1.2-10 to 1.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfrisk/armhf (1.2-10 to 1.2-10)
  • Migration status for xfrisk/armhf (1.2-10 to 1.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfrisk/i386 (1.2-10 to 1.2-10)
  • Migration status for xfrisk/i386 (1.2-10 to 1.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfrisk/ppc64el (1.2-10 to 1.2-10)
  • Migration status for xfrisk/ppc64el (1.2-10 to 1.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfrisk/riscv64 (1.2-10 to 1.2-10)
  • Migration status for xfrisk/riscv64 (1.2-10 to 1.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xfrisk/s390x (1.2-10 to 1.2-10)
  • Migration status for xfrisk/s390x (1.2-10 to 1.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgalaga/amd64 (2.1.1.0-7 to 2.1.1.0-7)
  • Migration status for xgalaga/amd64 (2.1.1.0-7 to 2.1.1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgalaga/arm64 (2.1.1.0-7 to 2.1.1.0-7)
  • Migration status for xgalaga/arm64 (2.1.1.0-7 to 2.1.1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgalaga/armhf (2.1.1.0-7 to 2.1.1.0-7)
  • Migration status for xgalaga/armhf (2.1.1.0-7 to 2.1.1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgalaga/i386 (2.1.1.0-7 to 2.1.1.0-7)
  • Migration status for xgalaga/i386 (2.1.1.0-7 to 2.1.1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgalaga/ppc64el (2.1.1.0-7 to 2.1.1.0-7)
  • Migration status for xgalaga/ppc64el (2.1.1.0-7 to 2.1.1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgalaga/riscv64 (2.1.1.0-7 to 2.1.1.0-7)
  • Migration status for xgalaga/riscv64 (2.1.1.0-7 to 2.1.1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgalaga/s390x (2.1.1.0-7 to 2.1.1.0-7)
  • Migration status for xgalaga/s390x (2.1.1.0-7 to 2.1.1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgammon/amd64 (0.99.1128-11 to 0.99.1128-11)
  • Migration status for xgammon/amd64 (0.99.1128-11 to 0.99.1128-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgammon/arm64 (0.99.1128-11 to 0.99.1128-11)
  • Migration status for xgammon/arm64 (0.99.1128-11 to 0.99.1128-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgammon/armhf (0.99.1128-11 to 0.99.1128-11)
  • Migration status for xgammon/armhf (0.99.1128-11 to 0.99.1128-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgammon/i386 (0.99.1128-11 to 0.99.1128-11)
  • Migration status for xgammon/i386 (0.99.1128-11 to 0.99.1128-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgammon/ppc64el (0.99.1128-11 to 0.99.1128-11)
  • Migration status for xgammon/ppc64el (0.99.1128-11 to 0.99.1128-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgammon/riscv64 (0.99.1128-11 to 0.99.1128-11)
  • Migration status for xgammon/riscv64 (0.99.1128-11 to 0.99.1128-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xgammon/s390x (0.99.1128-11 to 0.99.1128-11)
  • Migration status for xgammon/s390x (0.99.1128-11 to 0.99.1128-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xl2tpd/amd64 (1.3.18-1 to 1.3.18-1)
  • Migration status for xl2tpd/amd64 (1.3.18-1 to 1.3.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xl2tpd/arm64 (1.3.18-1 to 1.3.18-1)
  • Migration status for xl2tpd/arm64 (1.3.18-1 to 1.3.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xl2tpd/armhf (1.3.18-1 to 1.3.18-1)
  • Migration status for xl2tpd/armhf (1.3.18-1 to 1.3.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xl2tpd/i386 (1.3.18-1 to 1.3.18-1)
  • Migration status for xl2tpd/i386 (1.3.18-1 to 1.3.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xl2tpd/ppc64el (1.3.18-1 to 1.3.18-1)
  • Migration status for xl2tpd/ppc64el (1.3.18-1 to 1.3.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xl2tpd/riscv64 (1.3.18-1 to 1.3.18-1)
  • Migration status for xl2tpd/riscv64 (1.3.18-1 to 1.3.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xl2tpd/s390x (1.3.18-1 to 1.3.18-1)
  • Migration status for xl2tpd/s390x (1.3.18-1 to 1.3.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xmorph/amd64 (1:20150712-5.1 to 1:20150712-5.1)
  • Migration status for xmorph/amd64 (1:20150712-5.1 to 1:20150712-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xmorph/arm64 (1:20150712-5.1 to 1:20150712-5.1)
  • Migration status for xmorph/arm64 (1:20150712-5.1 to 1:20150712-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xmorph/armhf (1:20150712-5.1 to 1:20150712-5.1)
  • Migration status for xmorph/armhf (1:20150712-5.1 to 1:20150712-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xmorph/i386 (1:20150712-5.1 to 1:20150712-5.1)
  • Migration status for xmorph/i386 (1:20150712-5.1 to 1:20150712-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xmorph/ppc64el (1:20150712-5.1 to 1:20150712-5.1)
  • Migration status for xmorph/ppc64el (1:20150712-5.1 to 1:20150712-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xmorph/riscv64 (1:20150712-5.1 to 1:20150712-5.1)
  • Migration status for xmorph/riscv64 (1:20150712-5.1 to 1:20150712-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xmorph/s390x (1:20150712-5.1 to 1:20150712-5.1)
  • Migration status for xmorph/s390x (1:20150712-5.1 to 1:20150712-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xpaint/amd64 (2.9.1.4-5 to 2.9.1.4-5)
  • Migration status for xpaint/amd64 (2.9.1.4-5 to 2.9.1.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xpaint/arm64 (2.9.1.4-5 to 2.9.1.4-5)
  • Migration status for xpaint/arm64 (2.9.1.4-5 to 2.9.1.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xpaint/armhf (2.9.1.4-5 to 2.9.1.4-5)
  • Migration status for xpaint/armhf (2.9.1.4-5 to 2.9.1.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xpaint/i386 (2.9.1.4-5 to 2.9.1.4-5)
  • Migration status for xpaint/i386 (2.9.1.4-5 to 2.9.1.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xpaint/ppc64el (2.9.1.4-5 to 2.9.1.4-5)
  • Migration status for xpaint/ppc64el (2.9.1.4-5 to 2.9.1.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xpaint/riscv64 (2.9.1.4-5 to 2.9.1.4-5)
  • Migration status for xpaint/riscv64 (2.9.1.4-5 to 2.9.1.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xpaint/s390x (2.9.1.4-5 to 2.9.1.4-5)
  • Migration status for xpaint/s390x (2.9.1.4-5 to 2.9.1.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsane/amd64 (0.999-12.2 to 0.999-12.2)
  • Migration status for xsane/amd64 (0.999-12.2 to 0.999-12.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsane/arm64 (0.999-12.2 to 0.999-12.2)
  • Migration status for xsane/arm64 (0.999-12.2 to 0.999-12.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsane/armhf (0.999-12.2 to 0.999-12.2)
  • Migration status for xsane/armhf (0.999-12.2 to 0.999-12.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsane/i386 (0.999-12.2 to 0.999-12.2)
  • Migration status for xsane/i386 (0.999-12.2 to 0.999-12.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsane/ppc64el (0.999-12.2 to 0.999-12.2)
  • Migration status for xsane/ppc64el (0.999-12.2 to 0.999-12.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsane/riscv64 (0.999-12.2 to 0.999-12.2)
  • Migration status for xsane/riscv64 (0.999-12.2 to 0.999-12.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsane/s390x (0.999-12.2 to 0.999-12.2)
  • Migration status for xsane/s390x (0.999-12.2 to 0.999-12.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xscavenger/amd64 (1.4.5-10 to 1.4.5-10)
  • Migration status for xscavenger/amd64 (1.4.5-10 to 1.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xscavenger/arm64 (1.4.5-10 to 1.4.5-10)
  • Migration status for xscavenger/arm64 (1.4.5-10 to 1.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xscavenger/armhf (1.4.5-10 to 1.4.5-10)
  • Migration status for xscavenger/armhf (1.4.5-10 to 1.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xscavenger/i386 (1.4.5-10 to 1.4.5-10)
  • Migration status for xscavenger/i386 (1.4.5-10 to 1.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xscavenger/ppc64el (1.4.5-10 to 1.4.5-10)
  • Migration status for xscavenger/ppc64el (1.4.5-10 to 1.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xscavenger/riscv64 (1.4.5-10 to 1.4.5-10)
  • Migration status for xscavenger/riscv64 (1.4.5-10 to 1.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xscavenger/s390x (1.4.5-10 to 1.4.5-10)
  • Migration status for xscavenger/s390x (1.4.5-10 to 1.4.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsunpinyin/amd64 (2.0.3-9 to 2.0.3-9)
  • Migration status for xsunpinyin/amd64 (2.0.3-9 to 2.0.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsunpinyin/arm64 (2.0.3-9 to 2.0.3-9)
  • Migration status for xsunpinyin/arm64 (2.0.3-9 to 2.0.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsunpinyin/armhf (2.0.3-9 to 2.0.3-9)
  • Migration status for xsunpinyin/armhf (2.0.3-9 to 2.0.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsunpinyin/i386 (2.0.3-9 to 2.0.3-9)
  • Migration status for xsunpinyin/i386 (2.0.3-9 to 2.0.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsunpinyin/ppc64el (2.0.3-9 to 2.0.3-9)
  • Migration status for xsunpinyin/ppc64el (2.0.3-9 to 2.0.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xsunpinyin/s390x (2.0.3-9 to 2.0.3-9)
  • Migration status for xsunpinyin/s390x (2.0.3-9 to 2.0.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xtrkcad/amd64 (1:5.3.0GA-1.1 to 1:5.3.0GA-1.1)
  • Migration status for xtrkcad/amd64 (1:5.3.0GA-1.1 to 1:5.3.0GA-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
• xtrkcad/arm64 (1:5.3.0GA-1.1 to 1:5.3.0GA-1.1)
  • Migration status for xtrkcad/arm64 (1:5.3.0GA-1.1 to 1:5.3.0GA-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
• xtrkcad/armhf (1:5.3.0GA-1.1 to 1:5.3.0GA-1.1)
  • Migration status for xtrkcad/armhf (1:5.3.0GA-1.1 to 1:5.3.0GA-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
• xtrkcad/i386 (1:5.3.0GA-1.1 to 1:5.3.0GA-1.1)
  • Migration status for xtrkcad/i386 (1:5.3.0GA-1.1 to 1:5.3.0GA-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
• xtrkcad/ppc64el (1:5.3.0GA-1.1 to 1:5.3.0GA-1.1)
  • Migration status for xtrkcad/ppc64el (1:5.3.0GA-1.1 to 1:5.3.0GA-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
• xtrkcad/riscv64 (1:5.3.0GA-1.1 to 1:5.3.0GA-1.1)
  • Migration status for xtrkcad/riscv64 (1:5.3.0GA-1.1 to 1:5.3.0GA-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
• xtrkcad/s390x (1:5.3.0GA-1.1 to 1:5.3.0GA-1.1)
  • Migration status for xtrkcad/s390x (1:5.3.0GA-1.1 to 1:5.3.0GA-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
• xwpe/amd64 (1.5.30a-4 to 1.5.30a-4)
  • Migration status for xwpe/amd64 (1.5.30a-4 to 1.5.30a-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xwpe/arm64 (1.5.30a-4 to 1.5.30a-4)
  • Migration status for xwpe/arm64 (1.5.30a-4 to 1.5.30a-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xwpe/armhf (1.5.30a-4 to 1.5.30a-4)
  • Migration status for xwpe/armhf (1.5.30a-4 to 1.5.30a-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xwpe/i386 (1.5.30a-4 to 1.5.30a-4)
  • Migration status for xwpe/i386 (1.5.30a-4 to 1.5.30a-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xwpe/ppc64el (1.5.30a-4 to 1.5.30a-4)
  • Migration status for xwpe/ppc64el (1.5.30a-4 to 1.5.30a-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xwpe/riscv64 (1.5.30a-4 to 1.5.30a-4)
  • Migration status for xwpe/riscv64 (1.5.30a-4 to 1.5.30a-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xwpe/s390x (1.5.30a-4 to 1.5.30a-4)
  • Migration status for xwpe/s390x (1.5.30a-4 to 1.5.30a-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xzgv/amd64 (0.9.2-2 to 0.9.2-2)
  • Migration status for xzgv/amd64 (0.9.2-2 to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xzgv/arm64 (0.9.2-2 to 0.9.2-2)
  • Migration status for xzgv/arm64 (0.9.2-2 to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xzgv/armhf (0.9.2-2 to 0.9.2-2)
  • Migration status for xzgv/armhf (0.9.2-2 to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xzgv/i386 (0.9.2-2 to 0.9.2-2)
  • Migration status for xzgv/i386 (0.9.2-2 to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xzgv/ppc64el (0.9.2-2 to 0.9.2-2)
  • Migration status for xzgv/ppc64el (0.9.2-2 to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• xzgv/s390x (0.9.2-2 to 0.9.2-2)
  • Migration status for xzgv/s390x (0.9.2-2 to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ytree/amd64 (1.99pl1-2.2 to 1.99pl1-2.2)
  • Migration status for ytree/amd64 (1.99pl1-2.2 to 1.99pl1-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ytree/arm64 (1.99pl1-2.2 to 1.99pl1-2.2)
  • Migration status for ytree/arm64 (1.99pl1-2.2 to 1.99pl1-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ytree/armhf (1.99pl1-2.2 to 1.99pl1-2.2)
  • Migration status for ytree/armhf (1.99pl1-2.2 to 1.99pl1-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ytree/i386 (1.99pl1-2.2 to 1.99pl1-2.2)
  • Migration status for ytree/i386 (1.99pl1-2.2 to 1.99pl1-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ytree/ppc64el (1.99pl1-2.2 to 1.99pl1-2.2)
  • Migration status for ytree/ppc64el (1.99pl1-2.2 to 1.99pl1-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ytree/riscv64 (1.99pl1-2.2 to 1.99pl1-2.2)
  • Migration status for ytree/riscv64 (1.99pl1-2.2 to 1.99pl1-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• ytree/s390x (1.99pl1-2.2 to 1.99pl1-2.2)
  • Migration status for ytree/s390x (1.99pl1-2.2 to 1.99pl1-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• zulucrypt/amd64 (6.2.0-1 to 6.2.0-1)
  • Migration status for zulucrypt/amd64 (6.2.0-1 to 6.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• zulucrypt/arm64 (6.2.0-1 to 6.2.0-1)
  • Migration status for zulucrypt/arm64 (6.2.0-1 to 6.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• zulucrypt/armhf (6.2.0-1 to 6.2.0-1)
  • Migration status for zulucrypt/armhf (6.2.0-1 to 6.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• zulucrypt/i386 (6.2.0-1 to 6.2.0-1)
  • Migration status for zulucrypt/i386 (6.2.0-1 to 6.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• zulucrypt/ppc64el (6.2.0-1 to 6.2.0-1)
  • Migration status for zulucrypt/ppc64el (6.2.0-1 to 6.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 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): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• zulucrypt/s390x (6.2.0-1 to 6.2.0-1)
  • Migration status for zulucrypt/s390x (6.2.0-1 to 6.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
• 6tunnel (1:0.13-4 to 1:0.14-1)
  • Migration status for 6tunnel (1:0.13-4 to 1:0.14-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 7 days old
  • Additional info:
    • Updating 6tunnel will fix bugs in testing: #1096266
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/6/6tunnel.html
    • autopkgtest for 6tunnel/1:0.14-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• 9base (1:6-14 to 1:6-15)
  • Migration status for 9base (1:6-14 to 1:6-15): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Updating 9base will fix bugs in testing: #1096267
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/9/9base.html
    • autopkgtest for 9base/1:6-15: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• amavisd-milter (1.7.2-1 to 1.7.2-2)
  • Migration status for amavisd-milter (1.7.2-1 to 1.7.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating amavisd-milter will fix bugs in testing: #1096304
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/amavisd-milter.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• autoclass (3.3.6.dfsg.2-2 to 3.3.6.dfsg.2-3)
  • Migration status for autoclass (3.3.6.dfsg.2-2 to 3.3.6.dfsg.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating autoclass will fix bugs in testing: #1096348
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autoclass.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• autolog (0.42.1-3 to 0.42.2-1)
  • Migration status for autolog (0.42.1-3 to 0.42.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating autolog would introduce bugs in testing: #1096349
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autolog.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• cflow (1:1.7-5 to 1:1.8-1)
  • Migration status for cflow (1:1.7-5 to 1:1.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Updating cflow will fix bugs in testing: #1096425
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cflow.html
    • autopkgtest for cflow/1:1.8-1: amd64: Pass, arm64: 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
• ctn (3.2.0~dfsg-8 to 3.2.0~dfsg-9)
  • Migration status for ctn (3.2.0~dfsg-8 to 3.2.0~dfsg-9): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating ctn will fix bugs in testing: #1096489
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ctn.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• cyme (2.2.4+dfsg-4 to 2.2.5+dfsg-1)
  • Migration status for cyme (2.2.4+dfsg-4 to 2.2.5+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cyme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• emacs-libvterm (0.0.2+git20250113.056ad74-1 to 0.0.2+git20250113.056ad74-2)
  • Migration status for emacs-libvterm (0.0.2+git20250113.056ad74-1 to 0.0.2+git20250113.056ad74-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating emacs-libvterm will fix bugs in testing: #1115607
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-libvterm.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• fonts-ebgaramond (0.016+git20210310.42d4f9f2-1 to 0.016+git20230418-2)
  • Migration status for fonts-ebgaramond (0.016+git20210310.42d4f9f2-1 to 0.016+git20230418-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-ebgaramond.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• fonts-ebgaramond-initials (- to 0.016+git20230414-2)
  • Migration status for fonts-ebgaramond-initials (- to 0.016+git20230414-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-ebgaramond-initials.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• freerdp3 (3.17.1+dfsg-2 to 3.17.2+dfsg-2)
  • Migration status for freerdp3 (3.17.1+dfsg-2 to 3.17.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for freerdp3/3.17.2+dfsg-2: amd64: Pass, i386: Pass
    • autopkgtest for gnome-remote-desktop/48.1-4: amd64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)
    • missing build on arm64
    • missing build on armhf
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freerdp3.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• furo (2025.07.19+dfsg-2 to 2025.07.19+dfsg-3)
  • Migration status for furo (2025.07.19+dfsg-2 to 2025.07.19+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Updating furo will fix bugs in testing: #1114728
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/furo.html
    • autopkgtest for furo/2025.07.19+dfsg-3: amd64: Pass, arm64: 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
• gnome-shell-extension-appindicator (60+really.59-4 to 61-2)
  • Migration status for gnome-shell-extension-appindicator (60+really.59-4 to 61-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating gnome-shell-extension-appindicator will fix bugs in testing: #1115746
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-appindicator.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-shell-extension-caffeine (57-2 to 57-3)
  • Migration status for gnome-shell-extension-caffeine (57-2 to 57-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating gnome-shell-extension-caffeine will fix bugs in testing: #1115511
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-caffeine.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-sudoku (1:49~rc-1 to 1:49.0-1)
  • Migration status for gnome-sudoku (1:49~rc-1 to 1:49.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-sudoku.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnuradio (3.10.12.0-1 to 3.10.12.0-3)
  • Migration status for gnuradio (3.10.12.0-1 to 3.10.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gr-dab/0.5-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for gr-limesdr/3.0.1.10.69-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating gnuradio will fix bugs in testing: #1114129
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnuradio.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis, libast, netkit-telnet-ssl
• golang-1.24 (1.24.4-1 to 1.24.4-4)
  • Migration status for golang-1.24 (1.24.4-1 to 1.24.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-1.24 would introduce bugs in testing: #1115301
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for golang-1.24/1.24.4-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating golang-1.24 will fix bugs in testing: #1096750
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-1.24.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• golang-1.25 (1.25.0-1 to 1.25.0-2)
  • Migration status for golang-1.25 (1.25.0-1 to 1.25.0-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
    • autopkgtest for golang-1.25/1.25.0-2: arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating golang-1.25 will fix bugs in testing: #1115478
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-1.25.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• golang-github-cilium-ebpf (0.11.0-2 to 0.17.3+ds1-4)
  • Migration status for golang-github-cilium-ebpf (0.11.0-2 to 0.17.3+ds1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
    • Implicit dependency: golang-github-cilium-ebpf golang-github-containerd-cgroups
    • Implicit dependency: golang-github-cilium-ebpf runc (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-cilium-ebpf.html
    • autopkgtest for golang-github-cilium-ebpf/0.17.3+ds1-4: amd64: Pass, arm64: 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
• golang-github-gonvenience-text (1.0.7-2 to 1.0.9-1)
  • Migration status for golang-github-gonvenience-text (1.0.7-2 to 1.0.9-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gonvenience-text.html
    • autopkgtest for golang-github-gonvenience-text/1.0.9-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gsasl (2.2.2-3 to 2.2.2-4)
  • Migration status for gsasl (2.2.2-3 to 2.2.2-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsasl.html
    • autopkgtest for gsasl/2.2.2-4: amd64: Pass, arm64: Pass, i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gtkmm4.0 (4.19.1-4 to 4.20.0-1)
  • Migration status for gtkmm4.0 (4.19.1-4 to 4.20.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtkmm4.0.html
    • autopkgtest for gtkmm4.0/4.20.0-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 ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ibus-unikey (0.7.0~beta1-2 to 0.7.0~beta1-3)
  • Migration status for ibus-unikey (0.7.0~beta1-2 to 0.7.0~beta1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibus-unikey.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• indi (1.9.9+dfsg-3 to 1.9.9+dfsg-4)
  • Migration status for indi (1.9.9+dfsg-3 to 1.9.9+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
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating indi will fix bugs in testing: #1096834
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/indi.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• ktikz (0.13.2+ds1-1 to 0.13.2+ds1-2)
  • Migration status for ktikz (0.13.2+ds1-1 to 0.13.2+ds1-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/ktikz.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• lastz (1.04.22-2 to 1.04.52-1)
  • Migration status for lastz (1.04.22-2 to 1.04.52-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Updating lastz will fix bugs in testing: #1097151
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lastz.html
    • autopkgtest for lastz/1.04.52-1: amd64: Pass, arm64: 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
• lf (34+ds-2 to 38+ds-1)
  • Migration status for lf (34+ds-2 to 38+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
    • Build-Depends(-Arch): lf golang-fsnotify
    • Build-Depends(-Arch): lf golang-github-gdamore-tcell.v2
    • Built-Using: lf golang-1.24 (not considered)
    • Built-Using: lf golang-fsnotify
    • Built-Using: lf golang-github-gdamore-tcell.v2
    • Built-Using: lf golang-github-mattn-go-runewidth
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lf.html
    • autopkgtest for lf/38+ds-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• libsfml (3.0.1+dfsg-2 to 3.0.2+dfsg-1)
  • Migration status for libsfml (3.0.1+dfsg-2 to 3.0.2+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsfml.html
    • autopkgtest for libsfml/3.0.2+dfsg-1: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• lua-resty-core (0.1.31-1 to 0.1.31-3)
  • Migration status for lua-resty-core (0.1.31-1 to 0.1.31-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-resty-core.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • autopkgtest for lua-resty-core/0.1.31-3: amd64: Pass, arm64: Pass, i386: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• lua-resty-lrucache (0.15-2 to 0.15-4)
  • Migration status for lua-resty-lrucache (0.15-2 to 0.15-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-resty-lrucache.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • autopkgtest for lua-resty-lrucache/0.15-4: amd64: Pass, arm64: Pass, i386: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• mixxx (2.5.2+dfsg-1 to 2.5.3+dfsg-1)
  • Migration status for mixxx (2.5.2+dfsg-1 to 2.5.3+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mixxx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• nextcloud-spreed-signaling (1.2.4-3 to 2.0.2-2)
  • Migration status for nextcloud-spreed-signaling (1.2.4-3 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
    • autopkgtest for nextcloud-spreed-signaling/2.0.2-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
    • Built-Using: nextcloud-spreed-signaling golang-1.24 (not considered)
    • Built-Using: nextcloud-spreed-signaling golang-fsnotify
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nextcloud-spreed-signaling.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• nrg2iso (0.4-4.2 to 0.4-4.4)
  • Migration status for nrg2iso (0.4-4.2 to 0.4-4.4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nrg2iso.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• numcodecs (0.16.2+ds-2 to 0.16.3+ds-1)
  • Migration status for numcodecs (0.16.2+ds-2 to 0.16.3+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • 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: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
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/numcodecs.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• passt (0.0~git20250911.6cbcccc-1 to 0.0~git20250919.623dbf6-1)
  • Migration status for passt (0.0~git20250911.6cbcccc-1 to 0.0~git20250919.623dbf6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/passt.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• phast (1.7+dfsg-2 to 1.7+dfsg-3)
  • Migration status for phast (1.7+dfsg-2 to 1.7+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Updating phast will fix bugs in testing: #1097575
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phast.html
    • autopkgtest for phast/1.7+dfsg-3: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
    • Remove hint for (transitive) dependency: blis
• php-fpdf (3:1.8.4.dfsg-3 to 3:1.8.4.dfsg-4)
  • Migration status for php-fpdf (3:1.8.4.dfsg-3 to 3:1.8.4.dfsg-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fpdf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• play.it (2.33.1-1 to 2.33.2-1)
  • Migration status for play.it (2.33.1-1 to 2.33.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• play.it-adventure (2025-08-10-1 to 2025-09-19-1)
  • Migration status for play.it-adventure (2025-08-10-1 to 2025-09-19-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• play.it-community (2025-08-10-1 to 2025-09-19-1)
  • Migration status for play.it-community (2025-08-10-1 to 2025-09-19-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• play.it-puzzle (2025-08-10-1 to 2025-09-19-1)
  • Migration status for play.it-puzzle (2025-08-10-1 to 2025-09-19-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• play.it-strategy (2025-08-10-1 to 2025-09-19-1)
  • Migration status for play.it-strategy (2025-08-10-1 to 2025-09-19-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• play.it-vv221 (2025-08-10-1 to 2025-09-19-1)
  • Migration status for play.it-vv221 (2025-08-10-1 to 2025-09-19-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• postgrey (1.37-2.1 to 1.37-2.2)
  • Migration status for postgrey (1.37-2.1 to 1.37-2.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postgrey.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• powerpc-utils (1.3.13-1 to 1.3.13-2)
  • Migration status for powerpc-utils (1.3.13-1 to 1.3.13-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating powerpc-utils will fix bugs in testing: #1115718
    • 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 ♻
• ppp (2.5.2-1+1 to 2.5.2-1+1.1)
  • Migration status for ppp (2.5.2-1+1 to 2.5.2-1+1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
    • Depends: ppp openssl (not considered)
  • Additional info:
    • Updating ppp will fix bugs in testing: #1097645
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ppp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• pragha (1.3.4-3.1 to 1.3.4-3.2)
  • Migration status for pragha (1.3.4-3.1 to 1.3.4-3.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pragha.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• py3status (3.62-1 to 3.62-2)
  • Migration status for py3status (3.62-1 to 3.62-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for py3status/3.62-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/py3status.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• pyenv (2.5.4-1 to 2.5.5-2)
  • Migration status for pyenv (2.5.4-1 to 2.5.5-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyenv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-authlib (1.6.3-1 to 1.6.4-1)
  • Migration status for python-authlib (1.6.3-1 to 1.6.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for python-authlib/1.6.4-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-authlib.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• python-lib1305 (0~20250415.1-2 to 0~20250415.2-1)
  • Migration status for python-lib1305 (0~20250415.1-2 to 0~20250415.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lib1305.html
    • autopkgtest for python-lib1305/0~20250415.2-1: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• python-lib25519 (0~20241004.1-5 to 0~20241004.2-1)
  • Migration status for python-lib25519 (0~20241004.1-5 to 0~20241004.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lib25519.html
    • autopkgtest for python-lib25519/0~20241004.2-1: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• python-libtmux (0.46.1-1 to 0.46.2-1)
  • Migration status for python-libtmux (0.46.1-1 to 0.46.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for hexer/1.0.6-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • autopkgtest for python-libtmux/0.46.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression) ♻ (reference ♻)
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-libtmux.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• python-mceliece (0~20241009.1-5 to 0~20241009.2-1)
  • Migration status for python-mceliece (0~20241009.1-5 to 0~20241009.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mceliece.html
    • autopkgtest for python-mceliece/0~20241009.2-1: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• python-mitogen (0.3.27-1 to 0.3.29-1)
  • Migration status for python-mitogen (0.3.27-1 to 0.3.29-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mitogen.html
    • autopkgtest for python-mitogen/0.3.29-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed (not a regression) ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• python-ntruprime (0~20241021.4-5 to 0~20241021.5-1)
  • Migration status for python-ntruprime (0~20241021.4-5 to 0~20241021.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ntruprime.html
    • autopkgtest for python-ntruprime/0~20241021.5-1: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• python-outcome (1.2.0-1.1 to 1.2.0-2)
  • Migration status for python-outcome (1.2.0-1.1 to 1.2.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating python-outcome will fix bugs in testing: #1114319
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-outcome.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-p1monitor (3.1.0-1 to 3.2.0-1)
  • Migration status for python-p1monitor (3.1.0-1 to 3.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-p1monitor.html
    • autopkgtest for python-p1monitor/3.2.0-1: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• python-xlib (0.33-4 to 0.33-5)
  • Migration status for python-xlib (0.33-4 to 0.33-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xlib.html
    • autopkgtest for python-xlib/0.33-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• r-cran-rcpparmadillo (15.0.2-1-1 to 15.0.2-2-1)
  • Migration status for r-cran-rcpparmadillo (15.0.2-1-1 to 15.0.2-2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-rcpparmadillo.html
    • autopkgtest for r-cran-projpred/2.8.0+dfsg-1: amd64: Pass, arm64: Pass, i386: Test triggered (failure will be ignored), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• readstat (1.1.9-5 to 1.1.9-6)
  • Migration status for readstat (1.1.9-5 to 1.1.9-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating readstat will fix bugs in testing: #1097780
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/readstat.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• rosegarden (1:24.12.1-1 to 1:25.06-1)
  • Migration status for rosegarden (1:24.12.1-1 to 1:25.06-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rosegarden.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-annotate-snippets (0.11.4-1 to 0.11.5-1)
  • Migration status for rust-annotate-snippets (0.11.4-1 to 0.11.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-annotate-snippets/0.11.5-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-cargo/0.86.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-annotate-snippets.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• rust-anstream (0.6.15-1 to 0.6.20-1)
  • Migration status for rust-anstream (0.6.15-1 to 0.6.20-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-anstream/0.6.20-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-cargo/0.86.0-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: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-anstream.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-anstyle (1.0.8-1 to 1.0.11-1)
  • Migration status for rust-anstyle (1.0.8-1 to 1.0.11-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-anstyle/1.0.11-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-cargo/0.86.0-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: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-anstyle.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-bit-field (0.10.2-1 to 0.10.3-1)
  • Migration status for rust-bit-field (0.10.2-1 to 0.10.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bit-field.html
    • autopkgtest for rust-bit-field/0.10.3-1: amd64: Pass, arm64: 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
• rust-cargo-test-macro (0.3.0-1 to 0.4.2-1)
  • Migration status for rust-cargo-test-macro (0.3.0-1 to 0.4.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-test-macro.html
    • autopkgtest for rust-cargo-test-macro/0.4.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-cargo-test-support (- to 0.7.3-1)
  • Migration status for rust-cargo-test-support (- to 0.7.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
    • Build-Depends(-Arch): rust-cargo-test-support rust-anstream
    • Build-Depends(-Arch): rust-cargo-test-support rust-anstyle
    • Build-Depends(-Arch): rust-cargo-test-support rust-cargo-test-macro
    • Build-Depends(-Arch): rust-cargo-test-support rust-cargo-util
    • Build-Depends(-Arch): rust-cargo-test-support rust-crates-io
    • Depends: rust-cargo-test-support rust-anstream
    • Depends: rust-cargo-test-support rust-anstyle
    • Depends: rust-cargo-test-support rust-cargo-test-macro
    • Depends: rust-cargo-test-support rust-cargo-util
    • Depends: rust-cargo-test-support rust-crates-io
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-test-support.html
    • autopkgtest for rust-cargo-test-support/0.7.3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-cargo-util (0.2.14-2 to 0.2.20-1)
  • Migration status for rust-cargo-util (0.2.14-2 to 0.2.20-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-cargo/0.86.0-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: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for rust-cargo-util/0.2.20-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-cargo-util.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• rust-crates-io (0.40.4-1 to 0.40.10-1)
  • Migration status for rust-crates-io (0.40.4-1 to 0.40.10-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-cargo/0.86.0-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: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for rust-crates-io/0.40.10-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-crates-io.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• rust-gdk4-wayland (0.10.0-4 to 0.10.1-1)
  • Migration status for rust-gdk4-wayland (0.10.0-4 to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gdk4-wayland/0.10.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-gst-plugin-gtk4/0.14.0-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Regression ♻ (reference ♻)
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gdk4-wayland.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-gdk4-x11 (0.10.0-3 to 0.10.1-1)
  • Migration status for rust-gdk4-x11 (0.10.0-3 to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gdk4-x11/0.10.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-gst-plugin-gtk4/0.14.0-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Regression ♻ (reference ♻)
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gdk4-x11.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-gsk4 (0.10.0-3 to 0.10.1-1)
  • Migration status for rust-gsk4 (0.10.0-3 to 0.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gsk4.html
    • autopkgtest for rust-gsk4/0.10.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-gtk4/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-gtk4-sys (0.10.0-3 to 0.10.1-1)
  • Migration status for rust-gtk4-sys (0.10.0-3 to 0.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gtk4-sys.html
    • autopkgtest for rust-gtk4/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-gtk4-sys/0.10.1-1: amd64: Pass, arm64: 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
• rust-hashlink (0.8.4-1 to 0.10.0-1)
  • Migration status for rust-hashlink (0.8.4-1 to 0.10.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • autopkgtest for rust-hashlink/0.10.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-sqlx-core/0.8.3-3: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
    • Implicit dependency: rust-hashlink rust-rusqlite (not considered)
    • Implicit dependency: rust-hashlink rust-yaml-rust2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hashlink.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• rust-liblzma-sys (0.4.4-1 to 0.4.4-2)
  • Migration status for rust-liblzma-sys (0.4.4-1 to 0.4.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-liblzma-sys.html
    • autopkgtest for rust-liblzma-sys/0.4.4-2: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-oxhttp (0.3.1-3 to 0.3.1-4)
  • Migration status for rust-oxhttp (0.3.1-3 to 0.3.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-oxhttp.html
    • autopkgtest for oxigraph/0.4.11-4: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-oxhttp/0.3.1-4: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-proc-macro2-diagnostics (- to 0.10.1-2)
  • Migration status for rust-proc-macro2-diagnostics (- to 0.10.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-proc-macro2-diagnostics would introduce bugs in testing: #1102552
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proc-macro2-diagnostics.html
    • autopkgtest for rust-proc-macro2-diagnostics/0.10.1-2: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-rusqlite (0.29.0-3 to 0.29.0-4)
  • Migration status for rust-rusqlite (0.29.0-3 to 0.29.0-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for rust-cargo/0.86.0-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for rust-rusqlite/0.29.0-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rusqlite.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• rust-rustls (0.23.31+ds-7 to 0.23.32+ds-1)
  • Migration status for rust-rustls (0.23.31+ds-7 to 0.23.32+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-async-tls/0.13.0-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-axum-server/0.7.2-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-dockworker/0.7.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-hickory-client/0.24.4-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-hickory-proto/0.24.4-6: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-hickory-resolver/0.24.4-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-hickory-server/0.24.4-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-hyper-rustls/0.27.6-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-mail-send/0.5.2-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-ntp-proto/1.6.2-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-ntpd/1.6.2-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-reqwest/0.12.15-5: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-rustls/0.23.32+ds-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-rustls-platform-verifier/0.5.3+ds-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-sqlx-core/0.8.3-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-tokio-tungstenite/0.24.0-5: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-tungstenite/0.24.0-5: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-ureq/3.1.2+~0.5.2-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating rust-rustls will fix bugs in testing: #1115770
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustls.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-salsa (- to 0.23.0-2)
  • Migration status for rust-salsa (- to 0.23.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-salsa/0.23.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-salsa.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• rust-sequoia-chameleon-gnupg (0.13.1-3 to 0.13.1-4)
  • Migration status for rust-sequoia-chameleon-gnupg (0.13.1-3 to 0.13.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lintian/2.124.0: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for php-crypt-gpg/1.6.11-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression ♻ (reference ♻)
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating rust-sequoia-chameleon-gnupg will fix bugs in testing: #1115566
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-chameleon-gnupg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-sequoia-octopus-librnp (1.11.1-4 to 1.11.1-5)
  • Migration status for rust-sequoia-octopus-librnp (1.11.1-4 to 1.11.1-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating rust-sequoia-octopus-librnp will fix bugs in testing: #1115567
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-octopus-librnp.html
    • autopkgtest for rust-sequoia-octopus-librnp/1.11.1-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 ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-yaml-rust2 (0.10.3-1 to 0.10.3-2)
  • Migration status for rust-yaml-rust2 (0.10.3-1 to 0.10.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 rust-config/0.15.9-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
    • autopkgtest for rust-syntect/5.2.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
    • autopkgtest for rust-yaml-rust2/0.10.3-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-yaml-rust2.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• rust-zmq-sys (0.11.0-2 to 0.11.0-3)
  • Migration status for rust-zmq-sys (0.11.0-2 to 0.11.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-zmq-sys.html
    • autopkgtest for rust-zmq-sys/0.11.0-3: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• saga (9.9.1+dfsg-1 to 9.9.2+dfsg-1)
  • Migration status for saga (9.9.1+dfsg-1 to 9.9.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/saga.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• shed (1.16-1 to 1.16-2)
  • Migration status for shed (1.16-1 to 1.16-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • 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: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
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating shed will fix bugs in testing: #1097876
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shed.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• slidge (0.2.12-1 to 0.3.1-1)
  • Migration status for slidge (0.2.12-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:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slidge.html
    • autopkgtest for slidge/0.3.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• snac2 (2.82-1 to 2.83-1)
  • Migration status for snac2 (2.82-1 to 2.83-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snac2.html
    • autopkgtest for snac2/2.83-1: amd64: Pass, arm64: 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
• sourmash (4.8.14-3 to 4.9.4-3)
  • Migration status for sourmash (4.8.14-3 to 4.9.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
    • Build-Depends(-Arch): sourmash rust-needletail
  • Additional info:
    • Updating sourmash will fix bugs in testing: #1114393
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sourmash.html
    • autopkgtest for sourmash/4.9.4-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • No reference result, but not reproducibility on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • Remove hint for (transitive) dependency: blis
• spades (4.0.0+really3.15.5+dfsg-1 to 4.0.0+really3.15.5+dfsg-2)
  • Migration status for spades (4.0.0+really3.15.5+dfsg-1 to 4.0.0+really3.15.5+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Updating spades will fix bugs in testing: #1097913
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spades.html
    • autopkgtest for spades/4.0.0+really3.15.5+dfsg-2: amd64: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• sqlglot (27.12.0-1 to 27.16.3-1)
  • Migration status for sqlglot (27.12.0-1 to 27.16.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqlglot.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• sucrack (1.2.3-7 to 1.2.3-8)
  • Migration status for sucrack (1.2.3-7 to 1.2.3-8): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating sucrack will fix bugs in testing: #1097946
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sucrack.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• swift-im (5.0~alpha2.145.g12d031cf8+dfsg-4.1 to 5.0~alpha2.145.g12d031cf8+dfsg-5)
  • Migration status for swift-im (5.0~alpha2.145.g12d031cf8+dfsg-4.1 to 5.0~alpha2.145.g12d031cf8+dfsg-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
    • Depends: swift-im miniupnpc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swift-im.html
    • Reproducible on amd64 - info ♻
• switchbot-api (2.7.0-1 to 2.8.0-1)
  • Migration status for switchbot-api (2.7.0-1 to 2.8.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/switchbot-api.html
    • autopkgtest for switchbot-api/2.8.0-1: amd64: Pass, arm64: 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
• taglib (2.1.1-1 to 2.1.1-2)
  • Migration status for taglib (2.1.1-1 to 2.1.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/taglib.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• termit (3.1-3 to 3.2-1)
  • Migration status for termit (3.1-3 to 3.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/termit.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• tin (1:2.6.5~20250409-1 to 1:2.6.5~20250919-1)
  • Migration status for tin (1:2.6.5~20250409-1 to 1:2.6.5~20250919-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• virtuoso-opensource (7.2.12+dfsg-2 to 7.2.12+dfsg-4)
  • Migration status for virtuoso-opensource (7.2.12+dfsg-2 to 7.2.12+dfsg-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating virtuoso-opensource will fix bugs in testing: #1098067
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virtuoso-opensource.html
    • uninstallable on arch i386 (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 ♻
• volk (3.2.0-2 to 3.2.0-3)
  • Migration status for volk (3.2.0-2 to 3.2.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Updating volk will fix bugs in testing: #1098070
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/volk.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• xchpst (0.7.0-1 to 0.7.1-1)
  • Migration status for xchpst (0.7.0-1 to 0.7.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 xchpst/0.7.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xchpst.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• yuzu (0-1734+ds-6 to 0-1734+ds-7)
  • Migration status for yuzu (0-1734+ds-6 to 0-1734+ds-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
    • autopkgtest for yuzu/0-1734+ds-7: amd64: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 0 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yuzu.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Remove hint for (transitive) dependency: blis
• appstream-generator (0.9.1-1 to 0.10.0-1)
  • Migration status for appstream-generator (0.9.1-1 to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • appstream-generator unsatisfiable Build-Depends(-Arch) on amd64: inja-dev
    • appstream-generator unsatisfiable Build-Depends(-Arch) on arm64: inja-dev
    • appstream-generator unsatisfiable Build-Depends(-Arch) on armhf: inja-dev
    • appstream-generator unsatisfiable Build-Depends(-Arch) on i386: inja-dev
    • appstream-generator unsatisfiable Build-Depends(-Arch) on ppc64el: inja-dev
    • appstream-generator unsatisfiable Build-Depends(-Arch) on riscv64: inja-dev
    • appstream-generator unsatisfiable Build-Depends(-Arch) on s390x: inja-dev
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • 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: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
    • Waiting for lintian test results on ppc64el, amd64, arm64, i386, s390x, riscv64, armhf - info
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): appstream-generator appstream (not considered)
  • Additional info:
    • Updating appstream-generator will fix bugs in testing: #1115805
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appstream-generator.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• astc-encoder (5.2.0+ds-1 to 5.3.0+ds-5)
  • Migration status for astc-encoder (5.2.0+ds-1 to 5.3.0+ds-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating astc-encoder will fix bugs in testing: #1115565
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/astc-encoder.html
    • autopkgtest for astc-encoder/5.3.0+ds-5: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• austin (3.7.0-5 to 3.7.0-7)
  • Migration status for austin (3.7.0-5 to 3.7.0-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating austin will fix bugs in testing: #1114057
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/austin.html
    • autopkgtest for austin/3.7.0-7: amd64: Pass, arm64: 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
• awesome (4.3-7 to 4.3-8)
  • Migration status for awesome (4.3-7 to 4.3-8): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating awesome will fix bugs in testing: #1115591
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/awesome.html
    • autopkgtest for awesome/4.3-8: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• azure-devops-cli-extension (1.0.1-1 to 1.0.2-1)
  • Migration status for azure-devops-cli-extension (1.0.1-1 to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/azure-devops-cli-extension.html
    • autopkgtest for azure-devops-cli-extension/1.0.2-1: amd64: Pass, arm64: 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
    • Remove hint for (transitive) dependency: blis
• cava-alsa (0.10.4+dfsg-1 to 0.10.6+dfsg-1)
  • Migration status for cava-alsa (0.10.4+dfsg-1 to 0.10.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 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cava-alsa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ccache (4.11.3-1 to 4.12-1)
  • Migration status for ccache (4.11.3-1 to 4.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/c/ccache.html
    • autopkgtest for ccache/4.12-1: amd64: Pass, arm64: 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
• cedar-backup3 (3.9.2-1 to 3.10.1-1)
  • Migration status for cedar-backup3 (3.9.2-1 to 3.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cedar-backup3.html
    • autopkgtest for cedar-backup3/3.10.1-1: amd64: Pass, arm64: 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
• cl-xptest (1.2.4-3.2 to 1.2.4-4)
  • Migration status for cl-xptest (1.2.4-3.2 to 1.2.4-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-xptest.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• conmon (2.1.13+ds1-1 to 2.1.13+ds1-2)
  • Migration status for conmon (2.1.13+ds1-1 to 2.1.13+ds1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/conmon.html
    • autopkgtest for conmon/2.1.13+ds1-2: amd64: Pass, arm64: 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
• consult-el (2.3-1 to 2.8-1)
  • Migration status for consult-el (2.3-1 to 2.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/consult-el.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• copyright-update (2016.1018-6 to 2025.0404-1)
  • Migration status for copyright-update (2016.1018-6 to 2025.0404-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results on all - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/copyright-update.html
    • autopkgtest for copyright-update/2025.0404-1: amd64: Pass, arm64: 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
• cruft-ng (0.9.74 to 0.9.75)
  • Migration status for cruft-ng (0.9.74 to 0.9.75): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cruft-ng.html
    • autopkgtest for cruft-ng/0.9.75: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• cups-pdf (3.0.2-3 to 3.0.2-4)
  • Migration status for cups-pdf (3.0.2-3 to 3.0.2-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cups-pdf.html
    • autopkgtest for cups-pdf/3.0.2-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• debian-keyring (2025.07.26 to 2025.09.18)
  • Migration status for debian-keyring (2025.07.26 to 2025.09.18): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-keyring.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• dh-haskell (0.6.6 to 0.6.7)
  • Migration status for dh-haskell (0.6.6 to 0.6.7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dh-haskell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• dot-forward (1:0.71-8 to 1:0.71-9)
  • Migration status for dot-forward (1:0.71-8 to 1:0.71-9): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating dot-forward will fix bugs in testing: #1096539
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dot-forward.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ebib (2.49.1-1 to 2.51.1-1)
  • Migration status for ebib (2.49.1-1 to 2.51.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ebib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• elan (3.1.1-6 to 4.1.2-2)
  • Migration status for elan (3.1.1-6 to 4.1.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results on ppc64el, amd64, arm64, i386, s390x, riscv64, armhf - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elan.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• esnacc (1.8.1-5 to 1.8.1-6)
  • Migration status for esnacc (1.8.1-5 to 1.8.1-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 armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on s390x, amd64, all, ppc64el, arm64, i386, riscv64, armhf - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating esnacc will fix bugs in testing: #1096586
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/esnacc.html
• fastforward (1:0.51-10 to 1:0.51-11)
  • Migration status for fastforward (1:0.51-10 to 1:0.51-11): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating fastforward will fix bugs in testing: #1096610
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fastforward.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• flox (0.10.6-1 to 0.10.7-1)
  • Migration status for flox (0.10.6-1 to 0.10.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Waiting for lintian test results on all - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flox.html
    • autopkgtest for flox/0.10.7-1: amd64: Pass, arm64: 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
    • Remove hint for (transitive) dependency: blis
• forgejo-cli (- to 0.3.0-6)
  • Migration status for forgejo-cli (- to 0.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 1 of 5 days old
    • Build-Depends(-Arch): forgejo-cli rust-sha256 (not considered)
    • Build-Depends(-Arch): forgejo-cli rust-ssh2-config (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/forgejo-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• fortran-jonquil (- to 0.3.0-2)
  • Migration status for fortran-jonquil (- to 0.3.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results on ppc64el, amd64, arm64, i386, s390x, riscv64, armhf - info
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): fortran-jonquil fortran-testdrive
    • Build-Depends(-Arch): fortran-jonquil fortran-toml
    • Depends: fortran-jonquil fortran-toml
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fortran-jonquil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• fuzz (0.6-19.1 to 0.6-20)
  • Migration status for fuzz (0.6-19.1 to 0.6-20): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fuzz.html
    • autopkgtest for fuzz/0.6-20: amd64: Pass, arm64: 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
• fzf (0.60.3-1 to 0.65.1-1)
  • Migration status for fzf (0.60.3-1 to 0.65.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 fzf/0.65.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results on ppc64el, amd64, arm64, i386, s390x, riscv64, armhf - info
    • Too young, only 1 of 5 days old
    • Built-Using: fzf golang-1.24 (not considered)
    • Built-Using: fzf golang-github-charlievieth-fastwalk (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fzf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• generate-ninja (0.0~git20250430.487f835-1 to 0.0~git20250917.1a7c151-1)
  • Migration status for generate-ninja (0.0~git20250430.487f835-1 to 0.0~git20250917.1a7c151-1): Waiting for test 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/generate-ninja.html
    • autopkgtest for generate-ninja/0.0~git20250917.1a7c151-1: amd64: Pass, arm64: 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
• geotranz (- to 3.7-5)
  • Migration status for geotranz (- to 3.7-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geotranz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gir-rust-code-generator (0.21.0-2 to 0.21.1-1)
  • Migration status for gir-rust-code-generator (0.21.0-2 to 0.21.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gir-rust-code-generator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gjs (1.82.3-1 to 1.82.3-2)
  • Migration status for gjs (1.82.3-1 to 1.82.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gjs.html
    • autopkgtest for gjs/1.82.3-2: amd64: Pass, arm64: 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
• gnome-robots (1:41.2-2 to 1:41.2-3)
  • Migration status for gnome-robots (1:41.2-2 to 1:41.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating gnome-robots will fix bugs in testing: #1115755
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-robots.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-session (48.0-1 to 48.0-2)
  • Migration status for gnome-session (48.0-1 to 48.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-session.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-shell (48.4-1 to 48.5-2)
  • Migration status for gnome-shell (48.4-1 to 48.5-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-shell-extension-gsconnect (62-1 to 67-1)
  • Migration status for gnome-shell-extension-gsconnect (62-1 to 67-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-gsconnect.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gobject-introspection (1.84.0-1 to 1.86.0-2)
  • Migration status for gobject-introspection (1.84.0-1 to 1.86.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/gobject-introspection.html
    • autopkgtest for gobject-introspection/1.86.0-2: amd64: Pass, arm64: 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
• golang-fsnotify (1.8.0-3 to 1.9.0-1)
  • Migration status for golang-fsnotify (1.8.0-3 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 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-fsnotify.html
    • autopkgtest for golang-fsnotify/1.9.0-1: amd64: Pass, arm64: 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
• golang-github-containerd-cgroups (3.0.3-4 to 3.0.5-3)
  • Migration status for golang-github-containerd-cgroups (3.0.3-4 to 3.0.5-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): golang-github-containerd-cgroups golang-github-cilium-ebpf
    • Depends: golang-github-containerd-cgroups golang-github-cilium-ebpf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-containerd-cgroups.html
    • autopkgtest for golang-github-containerd-cgroups/3.0.5-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• golang-github-ctdk-chefcrypto (0.2.0-1.1 to 1.0.0-1)
  • Migration status for golang-github-ctdk-chefcrypto (0.2.0-1.1 to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-ctdk-chefcrypto/1.0.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ctdk-chefcrypto.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• golang-github-ctdk-go-trie (0.0~git20161027.0.6443fbc-1.1 to 0.0~git20161027.0.6443fbc-2)
  • Migration status for golang-github-ctdk-go-trie (0.0~git20161027.0.6443fbc-1.1 to 0.0~git20161027.0.6443fbc-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-ctdk-go-trie.html
    • autopkgtest for golang-github-ctdk-go-trie/0.0~git20161027.0.6443fbc-2: amd64: Pass, arm64: 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
• golang-github-evanw-esbuild (0.25.5-1 to 0.25.10-1)
  • Migration status for golang-github-evanw-esbuild (0.25.5-1 to 0.25.10-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 golang-github-evanw-esbuild/0.25.10-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
    • Built-Using: golang-github-evanw-esbuild golang-1.24 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-evanw-esbuild.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• golang-github-gdamore-tcell.v2 (2.7.4-1 to 2.9.0-1)
  • Migration status for golang-github-gdamore-tcell.v2 (2.7.4-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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gdamore-tcell.v2.html
    • autopkgtest for golang-github-gdamore-tcell.v2/2.9.0-1: amd64: Pass, arm64: 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
• golang-github-gonvenience-wrap (1.1.2-2 to 1.2.2-1)
  • Migration status for golang-github-gonvenience-wrap (1.1.2-2 to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-gonvenience-neat/1.3.11-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for golang-github-gonvenience-wrap/1.2.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-gonvenience-wrap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• golang-github-masterminds-semver-dev (3.2.0-1 to 3.4.0-1)
  • Migration status for golang-github-masterminds-semver-dev (3.2.0-1 to 3.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-masterminds-semver-dev.html
    • autopkgtest for golang-github-masterminds-semver-dev/3.4.0-1: amd64: Pass, arm64: 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
• golang-github-masterminds-vcs-dev (1.12.0-4.1 to 1.13.3-1)
  • Migration status for golang-github-masterminds-vcs-dev (1.12.0-4.1 to 1.13.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-masterminds-vcs-dev.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• golang-github-mattn-go-runewidth (0.0.16-1 to 0.0.16-2)
  • Migration status for golang-github-mattn-go-runewidth (0.0.16-1 to 0.0.16-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating golang-github-mattn-go-runewidth will fix bugs in testing: #1114134
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-mattn-go-runewidth.html
    • autopkgtest for golang-github-mattn-go-runewidth/0.0.16-2: amd64: Pass, arm64: 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
• golang-github-opencontainers-cgroups (- to 0.0.4-2)
  • Migration status for golang-github-opencontainers-cgroups (- to 0.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-opencontainers-cgroups/0.0.4-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): golang-github-opencontainers-cgroups golang-github-cilium-ebpf
    • Depends: golang-github-opencontainers-cgroups golang-github-cilium-ebpf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-opencontainers-cgroups.html
• golang-github-stevvooe-resumable (0.0~git20150521.0.51ad441-2.1 to 0.0~git20150521.0.51ad441-3)
  • Migration status for golang-github-stevvooe-resumable (0.0~git20150521.0.51ad441-2.1 to 0.0~git20150521.0.51ad441-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results on all - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-stevvooe-resumable.html
    • autopkgtest for golang-github-stevvooe-resumable/0.0~git20150521.0.51ad441-3: amd64: Pass, arm64: 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
• gtml (3.6.1-3 to 3.6.1-4)
  • Migration status for gtml (3.6.1-3 to 3.6.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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtml.html
    • autopkgtest for gtml/3.6.1-4: amd64: Pass, arm64: 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
• libclass-pluggable-perl (0.022-2.4 to 0.022-3)
  • Migration status for libclass-pluggable-perl (0.022-2.4 to 0.022-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libclass-pluggable-perl.html
    • autopkgtest for libclass-pluggable-perl/0.022-3: amd64: Pass, arm64: 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
• libhtp (1:0.5.51-1 to 1:0.5.52-1)
  • Migration status for libhtp (1:0.5.51-1 to 1:0.5.52-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhtp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• libtcod (1.24.0+dfsg-1 to 1.24.0+dfsg-2)
  • Migration status for libtcod (1.24.0+dfsg-1 to 1.24.0+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtcod.html
    • autopkgtest for libtcod/1.24.0+dfsg-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• libtext-iconv-perl (1.7-8 to 1.7-8.1)
  • Migration status for libtext-iconv-perl (1.7-8 to 1.7-8.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtext-iconv-perl.html
    • autopkgtest for libtext-iconv-perl/1.7-8.1: amd64: Pass, arm64: 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
• libvdestack (0.1.3-1 to 0.1.4-2)
  • Migration status for libvdestack (0.1.3-1 to 0.1.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating libvdestack will fix bugs in testing: #1097283
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvdestack.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• lintian (2.124.0 to 2.126.0)
  • Migration status for lintian (2.124.0 to 2.126.0): Waiting for test 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/lintian.html
    • autopkgtest for lintian/2.126.0: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• lua-dbi (0.7.4-1 to 0.7.5-1)
  • Migration status for lua-dbi (0.7.4-1 to 0.7.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results on s390x, amd64, all, arm64, ppc64el, i386, riscv64, armhf - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-dbi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• markdown-exec (1.10.3-1 to 1.11.0-1)
  • Migration status for markdown-exec (1.10.3-1 to 1.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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/markdown-exec.html
    • autopkgtest for markdown-exec/1.11.0-1: amd64: Pass, arm64: 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
• mkdocs-autorefs (1.4.2-1 to 1.4.3-1)
  • Migration status for mkdocs-autorefs (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:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mkdocs-autorefs.html
    • autopkgtest for mkdocs-autorefs/1.4.3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• moosefs (4.57.5-1 to 4.58.0-1)
  • Migration status for moosefs (4.57.5-1 to 4.58.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results on s390x, ppc64el, all, amd64, arm64, i386, riscv64, armhf - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/moosefs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• mrbuild (1.13-1 to 1.14-1)
  • Migration status for mrbuild (1.13-1 to 1.14-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results on all - info
    • Too young, only 1 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 ♻
• mutter (48.4-2 to 48.5-1)
  • Migration status for mutter (48.4-2 to 48.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/m/mutter.html
    • autopkgtest for mutter/48.5-1: amd64: Pass, arm64: 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
• ncompress (5.0-3 to 5.0-4)
  • Migration status for ncompress (5.0-3 to 5.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ncompress.html
    • autopkgtest for ncompress/5.0-4: amd64: Pass, arm64: 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
• newsboat (2.36-1.1 to 2.36-1.2)
  • Migration status for newsboat (2.36-1.1 to 2.36-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:
    • Updating newsboat will fix bugs in testing: #1114221
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/newsboat.html
    • autopkgtest for newsboat/2.36-1.2: amd64: Pass, arm64: 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
• openmpi (5.0.8-9 to 5.0.8-10)
  • Migration status for openmpi (5.0.8-9 to 5.0.8-10): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Depends: openmpi pmix
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmpi.html
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-18: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for esys-particle: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Test triggered (failure will be ignored)
    • autopkgtest for fenics-dolfinx/1:0.9.0-7: amd64: Pass, arm64: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for openmpi/5.0.8-10: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
• opm-simulators (2025.04+ds-1 to 2025.04+ds-2)
  • Migration status for opm-simulators (2025.04+ds-1 to 2025.04+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • autopkgtest for opm-simulators/2025.04+ds-2: amd64: Pass, arm64: Pass, ppc64el: Pass
    • Waiting for lintian test results on riscv64 - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opm-simulators.html
    • uninstallable on arch i386 (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 ♻
    • Remove hint for (transitive) dependency: blis
• pal (0.4.3-11 to 0.4.3-12)
  • Migration status for pal (0.4.3-11 to 0.4.3-12): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pal.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• pg-cron (1.6.5-1 to 1.6.7-1)
  • Migration status for pg-cron (1.6.5-1 to 1.6.7-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-cron.html
    • autopkgtest for pg-cron/1.6.7-1: 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
• pg-hint-plan-17 (1.7.0-1 to 1.7.1-1)
  • Migration status for pg-hint-plan-17 (1.7.0-1 to 1.7.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pg-hint-plan-17.html
    • autopkgtest for pg-hint-plan-17/1.7.1-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pg8000 (1.31.4-1 to 1.31.5-1)
  • Migration status for pg8000 (1.31.4-1 to 1.31.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/pg8000.html
    • autopkgtest for pg8000/1.31.5-1: amd64: Pass, arm64: 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
• php-dompdf (- to 3.1.0+dfsg-1)
  • Migration status for php-dompdf (- to 3.1.0+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): php-dompdf php-dompdf-svg-lib
    • Depends: php-dompdf php-dompdf-svg-lib
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-dompdf.html
    • autopkgtest for php-dompdf/3.1.0+dfsg-1: amd64: Pass, arm64: 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
• php-lcobucci-jwt (5.5.0-1 to 5.5.0-2)
  • Migration status for php-lcobucci-jwt (5.5.0-1 to 5.5.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-lcobucci-jwt.html
    • autopkgtest for php-lcobucci-jwt/5.5.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-league-uri-src (7.5.1-6 to 7.5.1-7)
  • Migration status for php-league-uri-src (7.5.1-6 to 7.5.1-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-league-uri-src.html
    • autopkgtest for php-league-uri-src/7.5.1-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-net-url2 (2.2.1-0.2 to 2.2.3-1)
  • Migration status for php-net-url2 (2.2.1-0.2 to 2.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 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-url2.html
    • autopkgtest for php-net-url2/2.2.3-1: amd64: Pass, arm64: 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
• php-parser (5.6.1-2 to 5.6.1-3)
  • Migration status for php-parser (5.6.1-2 to 5.6.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-parser.html
    • autopkgtest for php-parser/5.6.1-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-phar-io-version (3.2.1-3 to 3.2.1-4)
  • Migration status for php-phar-io-version (3.2.1-3 to 3.2.1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-phar-io-version.html
    • autopkgtest for php-phar-io-version/3.2.1-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-zend-code (4.16.0-2 to 4.16.0-3)
  • Migration status for php-zend-code (4.16.0-2 to 4.16.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-zend-code.html
    • autopkgtest for php-zend-code/4.16.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• php-zend-eventmanager (3.14.0-5 to 3.14.0-6)
  • Migration status for php-zend-eventmanager (3.14.0-5 to 3.14.0-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-zend-eventmanager.html
    • autopkgtest for php-zend-eventmanager/3.14.0-6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pistache (0.0.5+ds-5.1 to 0.4.26+ds-3)
  • Migration status for pistache (0.0.5+ds-5.1 to 0.4.26+ds-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 pistache will fix bugs in testing: #1097591
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pistache.html
    • autopkgtest for pistache/0.4.26+ds-3: amd64: Pass, arm64: 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
• plplot (5.15.0+dfsg2-15 to 5.15.0+dfsg2-16)
  • Migration status for plplot (5.15.0+dfsg2-15 to 5.15.0+dfsg2-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Waiting for lintian test results on s390x, amd64, all, arm64, ppc64el, i386, riscv64, armhf - info
    • Too young, only 1 of 2 days old
    • Build-Depends(-Arch): plplot swig
  • Additional info:
    • Updating plplot will fix bugs in testing: #1097622
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plplot.html
    • autopkgtest for plplot/5.15.0+dfsg2-16: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • No reference result, but not reproducibility on amd64 - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • Remove hint for (transitive) dependency: blis
• podman-compose (1.3.0-1 to 1.5.0-1)
  • Migration status for podman-compose (1.3.0-1 to 1.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/podman-compose.html
    • autopkgtest for podman-compose/1.5.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• postgresql-16-age (1.5.0~rc0-3 to 1.6.0~rc0-1)
  • Migration status for postgresql-16-age (1.5.0~rc0-3 to 1.6.0~rc0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/postgresql-16-age.html
    • autopkgtest for postgresql-16-age/1.6.0~rc0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pymupdf (1.25.4+ds1-3 to 1.25.4+ds1-4)
  • Migration status for pymupdf (1.25.4+ds1-3 to 1.25.4+ds1-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating pymupdf will fix bugs in testing: #1110807
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pymupdf.html
    • autopkgtest for pymupdf/1.25.4+ds1-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• pystac (1.13.0-1 to 1.14.1-1)
  • Migration status for pystac (1.13.0-1 to 1.14.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results on all - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pystac.html
    • autopkgtest for pystac/1.14.1-1: amd64: Pass, arm64: 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
• python-advanced-alchemy (1.4.1-1 to 1.6.2-1)
  • Migration status for python-advanced-alchemy (1.4.1-1 to 1.6.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-advanced-alchemy.html
    • autopkgtest for python-advanced-alchemy/1.6.2-1: amd64: Pass, arm64: 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
• python-cryptography (43.0.0-3 to 44.0.2-1)
  • Migration status for python-cryptography (43.0.0-3 to 44.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating python3-cryptography/44.0.2-1/amd64 to testing makes yubikey-manager/5.7.2-1/amd64 uninstallable
    • migrating python3-cryptography/44.0.2-1/arm64 to testing makes yubikey-manager/5.7.2-1/arm64 uninstallable
    • autopkgtest for ansible-core/2.19.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for dask.distributed/2024.12.1+ds-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for python-aiortc/1.11.0-1: amd64: Test triggered (failure will be ignored), arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for python-cryptography/44.0.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-openstacksdk/4.4.0-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Pass
    • autopkgtest for swift/2.35.1-2: amd64: Pass, arm64: Regression ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Test triggered (failure will be ignored)
    • autopkgtest for twisted/24.11.0-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for yalexs-ble/3.2.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Pass
    • autopkgtest for yubikey-manager/5.7.2-1: i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for yubikey-manager/5.8.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻)
    • Waiting for lintian test results on s390x, ppc64el, all, amd64, arm64, i386, riscv64, armhf - info
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): python-cryptography python-cryptography-vectors
    • Implicit dependency: python-cryptography yubikey-manager (not considered)
  • Additional info:
    • Updating python-cryptography will fix bugs in testing: #1115569
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cryptography.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-cryptography-vectors (43.0.0-1 to 44.0.2-1)
  • Migration status for python-cryptography-vectors (43.0.0-1 to 44.0.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cryptography-vectors.html
    • autopkgtest for python-cryptography-vectors/44.0.2-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-fitsio (1.2.6+dfsg-1 to 1.2.8+dfsg-1)
  • Migration status for python-fitsio (1.2.6+dfsg-1 to 1.2.8+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fitsio.html
    • autopkgtest for python-fitsio/1.2.8+dfsg-1: amd64: Pass, arm64: 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
    • Remove hint for (transitive) dependency: blis
• python-friendly-styles (- to 0.2+git20250605.bc0abfe-1)
  • Migration status for python-friendly-styles (- to 0.2+git20250605.bc0abfe-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-friendly-styles.html
    • autopkgtest for python-friendly-styles/0.2+git20250605.bc0abfe-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-hypothesis (6.138.14-1 to 6.139.2-1)
  • Migration status for python-hypothesis (6.138.14-1 to 6.139.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for accessible-pygments/0.0.5-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Pass
    • autopkgtest for mdanalysis: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Test triggered (failure will be ignored)
    • autopkgtest for ocrmypdf/16.10.4+dfsg1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • autopkgtest for python-bitstring/4.3.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
    • autopkgtest for python-fakeredis/2.29.0-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for python-hypothesis/6.139.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for twisted/24.11.0-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-hypothesis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-jsonrpc-websocket (3.1.5-2 to 3.1.6-1)
  • Migration status for python-jsonrpc-websocket (3.1.5-2 to 3.1.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating python-jsonrpc-websocket will fix bugs in testing: #1115563
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jsonrpc-websocket.html
    • autopkgtest for python-jsonrpc-websocket/3.1.6-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• python-scramp (1.4.6-1 to 1.4.6-2)
  • Migration status for python-scramp (1.4.6-1 to 1.4.6-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-scramp.html
    • autopkgtest for python-scramp/1.4.6-2: amd64: Pass, arm64: 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
• python3.14 (- to 3.14.0~rc3-1)
  • Migration status for python3.14 (- to 3.14.0~rc3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python3.14/3.14.0~rc3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
    • Waiting for lintian test results on riscv64 - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3.14.html
    • Waiting for reproducibility test results on amd64 - info ♻
• pyvirtualdisplay (3.0-1 to 3.0-2)
  • Migration status for pyvirtualdisplay (3.0-1 to 3.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyvirtualdisplay.html
    • autopkgtest for pyvirtualdisplay/3.0-2: amd64: Pass, arm64: 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
• ros2-colcon-core (0.19.0-1 to 0.20.0-1)
  • Migration status for ros2-colcon-core (0.19.0-1 to 0.20.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros2-colcon-core.html
    • autopkgtest for ros2-colcon-core/0.20.0-1: amd64: Pass, arm64: 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
• rust-cairo-rs (0.21.1-2 to 0.21.2-1)
  • Migration status for rust-cairo-rs (0.21.1-2 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/r/rust-cairo-rs.html
    • autopkgtest for rust-cairo-rs/0.21.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-gtk4/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-cairo-sys-rs (0.21.1-2 to 0.21.2-1)
  • Migration status for rust-cairo-sys-rs (0.21.1-2 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/r/rust-cairo-sys-rs.html
    • autopkgtest for rust-cairo-sys-rs/0.21.2-1: amd64: Pass, arm64: 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
• rust-czkawka-gui (8.0.0-4 to 8.0.0-5)
  • Migration status for rust-czkawka-gui (8.0.0-4 to 8.0.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating rust-czkawka-gui will fix bugs in testing: #1115793
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-czkawka-gui.html
    • Reproducible on amd64 - info ♻
• rust-gdk-pixbuf (0.21.1-2 to 0.21.2-1)
  • Migration status for rust-gdk-pixbuf (0.21.1-2 to 0.21.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gdk-pixbuf/0.21.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-gtk4/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-libshumate/0.7.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-sourceview5/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gdk-pixbuf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-gdk-pixbuf-sys (0.21.1-2 to 0.21.2-1)
  • Migration status for rust-gdk-pixbuf-sys (0.21.1-2 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/r/rust-gdk-pixbuf-sys.html
    • autopkgtest for rust-gdk-pixbuf-sys/0.21.2-1: amd64: Pass, arm64: 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
• rust-gdk4 (0.10.0-3 to 0.10.1-1)
  • Migration status for rust-gdk4 (0.10.0-3 to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gdk4/0.10.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-gtk4/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-libshumate/0.7.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-sourceview5/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gdk4.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-gdk4-sys (0.10.0-3 to 0.10.1-1)
  • Migration status for rust-gdk4-sys (0.10.0-3 to 0.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gdk4-sys.html
    • autopkgtest for rust-gdk4-sys/0.10.1-1: amd64: Pass, arm64: 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
• rust-gdk4-wayland-sys (0.10.0-3 to 0.10.1-1)
  • Migration status for rust-gdk4-wayland-sys (0.10.0-3 to 0.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gdk4-wayland-sys.html
    • autopkgtest for rust-gdk4-wayland-sys/0.10.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-gdk4-x11-sys (0.10.0-2 to 0.10.1-1)
  • Migration status for rust-gdk4-x11-sys (0.10.0-2 to 0.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gdk4-x11-sys.html
    • autopkgtest for rust-gdk4-x11-sys/0.10.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-getopts (0.2.21-4 to 0.2.24-1)
  • Migration status for rust-getopts (0.2.21-4 to 0.2.24-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-getopts.html
    • autopkgtest for rust-getopts/0.2.24-1: amd64: Pass, arm64: 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
• rust-gio (0.21.1-2 to 0.21.2-1)
  • Migration status for rust-gio (0.21.1-2 to 0.21.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gio/0.21.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for rust-gtk4/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-libshumate/0.7.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-sourceview5/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-gio-sys (0.21.1-3 to 0.21.2-1)
  • Migration status for rust-gio-sys (0.21.1-3 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/r/rust-gio-sys.html
    • autopkgtest for rust-gio-sys/0.21.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-glib/0.21.1-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-glib (0.21.1-4 to 0.21.2-1)
  • Migration status for rust-glib (0.21.1-4 to 0.21.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-glib/0.21.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for rust-gtk4/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-libshumate/0.7.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-sourceview5/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-glib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-glib-macros (0.21.0-2 to 0.21.2-1)
  • Migration status for rust-glib-macros (0.21.0-2 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/r/rust-glib-macros.html
    • autopkgtest for rust-glib/0.21.1-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for rust-glib-macros/0.21.2-1: amd64: Pass, arm64: 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
• rust-glib-sys (0.21.1-2 to 0.21.2-1)
  • Migration status for rust-glib-sys (0.21.1-2 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/r/rust-glib-sys.html
    • autopkgtest for rust-glib/0.21.1-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for rust-glib-sys/0.21.2-1: amd64: Pass, arm64: 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
• rust-glycin-utils (4.0.0~rc-3 to 4.0.0-2)
  • Migration status for rust-glycin-utils (4.0.0~rc-3 to 4.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/r/rust-glycin-utils.html
    • autopkgtest for rust-glycin-utils/4.0.0-2: amd64: Pass, arm64: 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
• rust-gobject-sys (0.21.1-3 to 0.21.2-1)
  • Migration status for rust-gobject-sys (0.21.1-3 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/r/rust-gobject-sys.html
    • autopkgtest for rust-glib/0.21.1-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for rust-gobject-sys/0.21.2-1: amd64: Pass, arm64: 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
• rust-graphene-rs (0.21.1-2 to 0.21.2-1)
  • Migration status for rust-graphene-rs (0.21.1-2 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/r/rust-graphene-rs.html
    • autopkgtest for rust-graphene-rs/0.21.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-gtk4/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-graphene-sys (0.21.1-2 to 0.21.2-1)
  • Migration status for rust-graphene-sys (0.21.1-2 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/r/rust-graphene-sys.html
    • autopkgtest for rust-graphene-sys/0.21.2-1: amd64: Pass, arm64: 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
• rust-gsk4-sys (0.10.0-3 to 0.10.1-1)
  • Migration status for rust-gsk4-sys (0.10.0-3 to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-gsk4/0.10.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Pass
    • autopkgtest for rust-gsk4-sys/0.10.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gsk4-sys.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-gstreamer (0.24.1-2 to 0.24.2-1)
  • Migration status for rust-gstreamer (0.24.1-2 to 0.24.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-aperture/0.11.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-gst-plugin-gtk4/0.14.0-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Regression ♻ (reference ♻)
    • autopkgtest for rust-gstreamer/0.24.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gstreamer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-gstreamer-sys (0.24.0-2 to 0.24.2-1)
  • Migration status for rust-gstreamer-sys (0.24.0-2 to 0.24.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gstreamer-sys.html
    • autopkgtest for rust-gstreamer-sys/0.24.2-1: amd64: Pass, arm64: 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
• rust-gtk4-macros (0.10.0-2 to 0.10.1-1)
  • Migration status for rust-gtk4-macros (0.10.0-2 to 0.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gtk4-macros.html
    • autopkgtest for rust-gtk4/0.10.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-gtk4-macros/0.10.1-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-hexplay (0.2.1-1 to 0.3.0-1)
  • Migration status for rust-hexplay (0.2.1-1 to 0.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-hexplay.html
    • autopkgtest for rust-hexplay/0.3.0-1: amd64: Pass, arm64: 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
• rust-kanata (1.9.0-2 to 1.9.0-8)
  • Migration status for rust-kanata (1.9.0-2 to 1.9.0-8): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results on amd64, ppc64el, arm64, i386, s390x, riscv64 - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-kanata.html
    • autopkgtest for rust-kanata/1.9.0-8: amd64: Pass, arm64: 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
• rust-oxilangtag (0.1.5-4 to 0.1.5-5)
  • Migration status for rust-oxilangtag (0.1.5-4 to 0.1.5-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-oxilangtag.html
    • autopkgtest for oxigraph/0.4.11-4: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for rust-oxilangtag/0.1.5-5: amd64: Pass, arm64: 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
• rust-pango-sys (0.21.1-2 to 0.21.2-1)
  • Migration status for rust-pango-sys (0.21.1-2 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/r/rust-pango-sys.html
    • autopkgtest for rust-pango-sys/0.21.2-1: amd64: Pass, arm64: 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
• rust-pangocairo (0.21.1-2 to 0.21.2-1)
  • Migration status for rust-pangocairo (0.21.1-2 to 0.21.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pangocairo.html
    • autopkgtest for rust-pangocairo/0.21.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-pangocairo-sys (0.21.1-2 to 0.21.2-1)
  • Migration status for rust-pangocairo-sys (0.21.1-2 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/r/rust-pangocairo-sys.html
    • autopkgtest for rust-pangocairo-sys/0.21.2-1: amd64: Pass, arm64: 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
• rust-redox-termios (0.1.2-1 to 0.1.3-1)
  • Migration status for rust-redox-termios (0.1.2-1 to 0.1.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-redox-termios.html
    • autopkgtest for rust-redox-termios/0.1.3-1: amd64: Pass, arm64: 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
• rust-regolith-powerd (0.3.9-3 to 0.3.9-4)
  • Migration status for rust-regolith-powerd (0.3.9-3 to 0.3.9-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-regolith-powerd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-rustdoc-stripper (0.1.12-1 to 0.1.19-1)
  • Migration status for rust-rustdoc-stripper (0.1.12-1 to 0.1.19-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustdoc-stripper.html
    • autopkgtest for rust-rustdoc-stripper/0.1.19-1: amd64: Pass, arm64: 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
• rust-rustls-webpki (0.103.4-2 to 0.103.5-1)
  • Migration status for rust-rustls-webpki (0.103.4-2 to 0.103.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Updating rust-rustls-webpki will fix bugs in testing: #1115773
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rustls-webpki.html
    • autopkgtest for rust-rustls-webpki/0.103.5-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• rust-sequoia-sq (1.3.1-2 to 1.3.1-3)
  • Migration status for rust-sequoia-sq (1.3.1-2 to 1.3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for apt/3.1.5: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating rust-sequoia-sq will fix bugs in testing: #1115568
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sequoia-sq.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-tiny-dfr (0.3.6-4 to 0.3.6-5)
  • Migration status for rust-tiny-dfr (0.3.6-4 to 0.3.6-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating rust-tiny-dfr will fix bugs in testing: #1115798
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tiny-dfr.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-webp (0.3.0-1 to 0.3.1-1)
  • Migration status for rust-webp (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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-webp.html
    • autopkgtest for rust-webp/0.3.1-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• simpleproxy (- to 3.5-2)
  • Migration status for simpleproxy (- 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 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simpleproxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• sopwith (2.8.0-1 to 2.8.0-2)
  • Migration status for sopwith (2.8.0-1 to 2.8.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sopwith.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• spew (1.0.8-1.2 to 1.0.8-2)
  • Migration status for spew (1.0.8-1.2 to 1.0.8-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spew.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• sunpy-sphinx-theme (2.0.22-1 to 2.0.23-1)
  • Migration status for sunpy-sphinx-theme (2.0.22-1 to 2.0.23-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sunpy-sphinx-theme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• swig (4.3.0-1 to 4.3.0-2)
  • Migration status for swig (4.3.0-1 to 4.3.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swig.html
    • autopkgtest for cmake/4.1.1+really3.31.6-1: amd64: Ignored failure ♻ (reference ♻), arm64: Ignored failure ♻ (reference ♻), i386: Ignored failure ♻ (reference ♻), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Ignored failure ♻ (reference ♻)
    • autopkgtest for swig/4.3.0-2: amd64: Pass, arm64: 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
• symfony (6.4.24+dfsg-1 to 6.4.25+dfsg-1)
  • Migration status for symfony (6.4.24+dfsg-1 to 6.4.25+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-twig/3.20.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for symfony/6.4.25+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/symfony.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• t50 (5.8.7b-1 to 5.8.7c-2)
  • Migration status for t50 (5.8.7b-1 to 5.8.7c-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/t50.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• tifffile (20250828-1 to 20250909-1)
  • Migration status for tifffile (20250828-1 to 20250909-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tifffile.html
    • autopkgtest for tifffile/20250909-1: amd64: Pass, arm64: 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
    • Remove hint for (transitive) dependency: blis
• trustedqsl (2.8.1-1 to 2.8.2-1)
  • Migration status for trustedqsl (2.8.1-1 to 2.8.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trustedqsl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ttf-ancient-fonts (2.60-2 to 2.60-3)
  • Migration status for ttf-ancient-fonts (2.60-2 to 2.60-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/ttf-ancient-fonts.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• unbound (1.23.1-1 to 1.24.0-1)
  • Migration status for unbound (1.23.1-1 to 1.24.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for unbound/1.24.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unbound.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• unicorn-engine (2.1.1-2 to 2.1.4-1)
  • Migration status for unicorn-engine (2.1.1-2 to 2.1.4-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on riscv64
    • missing build on s390x
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for unicorn-engine/2.1.4-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass
    • Waiting for lintian test results on riscv64, s390x - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unicorn-engine.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• upgrade-system (1.10.0 to 1.11.0)
  • Migration status for upgrade-system (1.10.0 to 1.11.0): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/upgrade-system.html
    • autopkgtest for upgrade-system/1.11.0: 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 ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• usemod-wiki (1.2.2-2 to 1.2.3-1)
  • Migration status for usemod-wiki (1.2.2-2 to 1.2.3-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/usemod-wiki.html
    • autopkgtest for usemod-wiki/1.2.3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• vdetelweb (1.2.3-1 to 1.2.4-2)
  • Migration status for vdetelweb (1.2.3-1 to 1.2.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Updating vdetelweb will fix bugs in testing: #1098059
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdetelweb.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• webkit2gtk (2.48.6-1 to 2.50.0-1)
  • Migration status for webkit2gtk (2.48.6-1 to 2.50.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webkit2gtk.html
    • Waiting for reproducibility test results on amd64 - info ♻
• wlmaker (0.5-1 to 0.6.1+git20250919+ds-1)
  • Migration status for wlmaker (0.5-1 to 0.6.1+git20250919+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
    • Build-Depends(-Arch): wlmaker wlroots (not considered)
    • Depends: wlmaker wlroots (not considered)
  • Additional info:
    • Updating wlmaker will fix bugs in testing: #1111150
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wlmaker.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• xmlcopyeditor (1.3.1.0-1.1 to 1.3.1.0-1.2)
  • Migration status for xmlcopyeditor (1.3.1.0-1.1 to 1.3.1.0-1.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmlcopyeditor.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
• xssproxy (1.1.1-1 to 1.1.2-1)
  • Migration status for xssproxy (1.1.1-1 to 1.1.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xssproxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• yubikey-manager (5.7.2-1 to 5.8.0-1)
  • Migration status for yubikey-manager (5.7.2-1 to 5.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/y/yubikey-manager.html
    • Waiting for lintian test results (stalls migration) - info
    • Too young, only 1 of 2 days old
  • Additional info:
    • autopkgtest for yubikey-manager/5.8.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
• zope.interface (7.2-1 to 8.0-1)
  • Migration status for zope.interface (7.2-1 to 8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for twisted/24.11.0-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Pass, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Pass
    • autopkgtest for txzmq/0.8.0-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
    • autopkgtest for zope.interface/8.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for zope.security/8.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zope.interface.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• zutils (1.15-3 to 1.15-5)
  • Migration status for zutils (1.15-3 to 1.15-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 1 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• altree (1.3.2-2 to 1.3.2-4)
  • Migration status for altree (1.3.2-2 to 1.3.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating altree will fix bugs in testing: #1096300
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/altree.html
    • autopkgtest for altree/1.3.2-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• asdf-standard (1.3.0-1 to 1.4.0-1)
  • Migration status for asdf-standard (1.3.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asdf-standard would introduce bugs in testing: #1115780
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on all - info
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asdf-standard.html
• aumix (2.9.1-7.1 to 2.9.1-8)
  • Migration status for aumix (2.9.1-7.1 to 2.9.1-8): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating aumix will fix bugs in testing: #1115537
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aumix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ballerburg (1.2.2-4 to 1.2.3+git20250916+ds-3)
  • Migration status for ballerburg (1.2.2-4 to 1.2.3+git20250916+ds-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/ballerburg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• c-blosc2 (2.17.1+ds-1 to 2.17.1+ds-2)
  • Migration status for c-blosc2 (2.17.1+ds-1 to 2.17.1+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/c-blosc2.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• cellbroadcastd (- to 0.0.2-2)
  • Migration status for cellbroadcastd (- to 0.0.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cellbroadcastd.html
    • autopkgtest for cellbroadcastd/0.0.2-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• cmake (4.1.1+really3.31.6-1 to 4.1.1+really3.31.6-2)
  • Migration status for cmake (4.1.1+really3.31.6-1 to 4.1.1+really3.31.6-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating cmake will fix bugs in testing: #1115461
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cmake.html
    • autopkgtest for assimp/6.0.2+ds-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test triggered (failure will be ignored)
    • autopkgtest for cmake/4.1.1+really3.31.6-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for cyrus-imapd/3.12.1-2: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-18: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for fenics-dolfinx/1:0.9.0-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for llvm-toolchain-17/1:17.0.6-22: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Test triggered (failure will be ignored), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • autopkgtest for llvm-toolchain-18/1:18.1.8-18: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for llvm-toolchain-19/1:19.1.7-3: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
• colplot (5.2.0-3 to 5.2.0-4)
  • Migration status for colplot (5.2.0-3 to 5.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/colplot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• davix (0.8.10-1 to 0.8.10-2)
  • Migration status for davix (0.8.10-1 to 0.8.10-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/davix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• debian-edu (2.13.3 to 2.13.4)
  • Migration status for debian-edu (2.13.3 to 2.13.4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-edu.html
    • autopkgtest for debian-edu/2.13.4: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• elk (3.99.8-9 to 3.99.8-10)
  • Migration status for elk (3.99.8-9 to 3.99.8-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:
    • Updating elk will fix bugs in testing: #1096572
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• extension-helpers (1.2.0-2 to 1.4.0-1)
  • Migration status for extension-helpers (1.2.0-2 to 1.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/extension-helpers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• firefox-esr (128.14.0esr-1 to 140.3.0esr-2)
  • Migration status for firefox-esr (128.14.0esr-1 to 140.3.0esr-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
    • Waiting for lintian test results on s390x - info
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firefox-esr.html
    • Reproducible on amd64 - info ♻
• fonts-freefont (20211204+svn4273-2 to 20211204+svn4273-4)
  • Migration status for fonts-freefont (20211204+svn4273-2 to 20211204+svn4273-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
    • Build-Depends-Indep: fonts-freefont fontforge
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-freefont.html
    • autopkgtest for xmds2/3.1.0+dfsg2-10: amd64: Test triggered (failure will be ignored), arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Failed (not a regression) ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• fortran-toml (- to 0.4.2-2)
  • Migration status for fortran-toml (- to 0.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 2 of 5 days old
    • Build-Depends(-Arch): fortran-toml fortran-testdrive
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fortran-toml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• foxeye (0.12.1-5.1 to 0.12.1-6)
  • Migration status for foxeye (0.12.1-5.1 to 0.12.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:
    • Updating foxeye will fix bugs in testing: #1114107
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foxeye.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• fungw (1.2.1-3.1 to 1.2.2-1)
  • Migration status for fungw (1.2.1-3.1 to 1.2.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fungw.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gap-ctbllib (1.3.9-2 to 1.3.11-1)
  • Migration status for gap-ctbllib (1.3.9-2 to 1.3.11-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gap-ctbllib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• garlic-doc (1.6-2 to 1.6-3)
  • Migration status for garlic-doc (1.6-2 to 1.6-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/garlic-doc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-shell-extension-desktop-icons-ng (48.1.0-1 to 49.0.4-1)
  • Migration status for gnome-shell-extension-desktop-icons-ng (48.1.0-1 to 49.0.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • 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 ♻
• gnome-shell-extension-gamemode (14.0-1 to 14.0-2)
  • Migration status for gnome-shell-extension-gamemode (14.0-1 to 14.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating gnome-shell-extension-gamemode will fix bugs in testing: #1115514
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-gamemode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-shell-extension-runcat (29-1 to 30-1)
  • Migration status for gnome-shell-extension-runcat (29-1 to 30-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-runcat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-shell-extension-tiling-assistant (51-2 to 53-1)
  • Migration status for gnome-shell-extension-tiling-assistant (51-2 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
  • 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 ♻
• gnome-shell-frippery (48.0-3 to 48.1-1)
  • Migration status for gnome-shell-frippery (48.0-3 to 48.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:
    • Updating gnome-shell-frippery will fix bugs in testing: #1115513
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-frippery.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gpaste (45.3-1 to 45.3-2)
  • Migration status for gpaste (45.3-1 to 45.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating gpaste will fix bugs in testing: #1115528
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpaste.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• granite (6.2.0-4 to 6.2.0-5)
  • Migration status for granite (6.2.0-4 to 6.2.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/granite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• granite-7 (7.6.0-2 to 7.6.0-3)
  • Migration status for granite-7 (7.6.0-2 to 7.6.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/granite-7.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• harfbuzz (11.4.5-1 to 11.5.0-1)
  • Migration status for harfbuzz (11.4.5-1 to 11.5.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • Waiting for lintian test results on armhf - info
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/harfbuzz.html
    • autopkgtest for harfbuzz/11.5.0-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 ♻
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for openjdk-21/21.0.9~5ea-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for openjdk-25/25~36ea-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for openjdk-26/26~12ea-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• indigo (1.2.3-3.1 to 1.2.3-4)
  • Migration status for indigo (1.2.3-3.1 to 1.2.3-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/indigo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• keyman (18.0.240-1 to 18.0.241-1)
  • Migration status for keyman (18.0.240-1 to 18.0.241-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/keyman.html
    • autopkgtest for keyman/18.0.241-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• libmawk (1.0.4-5 to 1.0.5-1)
  • Migration status for libmawk (1.0.4-5 to 1.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmawk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• libxfce4ui (4.20.1-1 to 4.20.2-1)
  • Migration status for libxfce4ui (4.20.1-1 to 4.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 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libx/libxfce4ui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• lxqt-config (2.2.0-1 to 2.2.0-2)
  • Migration status for lxqt-config (2.2.0-1 to 2.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/l/lxqt-config.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• lxqt-notificationd (2.2.0-1 to 2.2.0-2)
  • Migration status for lxqt-notificationd (2.2.0-1 to 2.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/l/lxqt-notificationd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• lyx (2.4.4-1 to 2.4.4-2)
  • Migration status for lyx (2.4.4-1 to 2.4.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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lyx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• malcontent (0.13.0-2 to 0.13.1-1)
  • Migration status for malcontent (0.13.0-2 to 0.13.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/malcontent.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• mate-session-manager (1.26.1-2 to 1.26.1-3)
  • Migration status for mate-session-manager (1.26.1-2 to 1.26.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mate-session-manager.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• mdadm (4.4-12 to 4.4-13)
  • Migration status for mdadm (4.4-12 to 4.4-13): Waiting for test results or 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/mdadm.html
    • autopkgtest for mdadm/4.4-13: 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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• mesa (25.2.2-1 to 25.2.3-1)
  • Migration status for mesa (25.2.2-1 to 25.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/m/mesa.html
    • autopkgtest for assimp/6.0.2+ds-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Test triggered (failure will be ignored)
    • autopkgtest for mesa/25.2.3-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 ♻
    • Reproducible on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• mousepad (0.6.3-1 to 0.6.5-1)
  • Migration status for mousepad (0.6.3-1 to 0.6.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/m/mousepad.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• node-leven (4.0.0+~cs1.1.1-2 to 4.1.0+~cs1.1.1-1)
  • Migration status for node-leven (4.0.0+~cs1.1.1-2 to 4.1.0+~cs1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-commist/3.2.0+ds-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for node-leven/4.1.0+~cs1.1.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 2 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-leven.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ofono (2.18-1 to 2.18-2)
  • Migration status for ofono (2.18-1 to 2.18-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/o/ofono.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• onednn (3.8.1+ds-1 to 3.9.1+ds-1)
  • Migration status for onednn (3.8.1+ds-1 to 3.9.1+ds-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for onednn/3.9.1+ds-1: amd64: Pass, arm64: Pass, riscv64: No tests, superficial or marked flaky ♻, s390x: Pass
    • Waiting for lintian test results on ppc64el - info
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/onednn.html
    • Reproducible on amd64 - info ♻
• openssl (3.5.2-1 to 3.5.3-1)
  • Migration status for openssl (3.5.2-1 to 3.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for apt/3.1.5: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for cyrus-imapd/3.12.1-2: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for nodejs/20.19.2+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for openssl/3.5.3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for oxigraph/0.4.11-4: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for python3.13/3.13.7-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for ros-ros-comm/1.17.0+ds-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openssl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• orca (48.1-2 to 49.0-1)
  • Migration status for orca (48.1-2 to 49.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/o/orca.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• php-dompdf-svg-lib (- to 1.0.0-2)
  • Migration status for php-dompdf-svg-lib (- to 1.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-dompdf-svg-lib php-horde-css-parser (not considered)
    • Depends: php-dompdf-svg-lib php-horde-css-parser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-dompdf-svg-lib.html
    • autopkgtest for php-dompdf-svg-lib/1.0.0-2: amd64: Pass, arm64: 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
    • 2 days old (needed 2 days)
• pmix (5.0.7-1 to 6.0.0+really5.0.8-1)
  • Migration status for pmix (5.0.7-1 to 6.0.0+really5.0.8-1): Will attempt migration due to a hint (Any information below is purely informational)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pmix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Too young, but urgency pushed by sramacher
    • 2 days old
• python-googleapi (2.180.0-1 to 2.182.0-1)
  • Migration status for python-googleapi (2.180.0-1 to 2.182.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-googleapi.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-zstandard (0.24.0-1 to 0.25.0-1)
  • Migration status for python-zstandard (0.24.0-1 to 0.25.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-zstandard.html
    • autopkgtest for python-zstandard/0.25.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• pytorch (2.6.0+dfsg-8 to 2.6.0+dfsg-9)
  • Migration status for pytorch (2.6.0+dfsg-8 to 2.6.0+dfsg-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pytorch/2.6.0+dfsg-9: amd64: Pass, arm64: Pass, ppc64el: Regression ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • Waiting for lintian test results on riscv64 - info
    • Too young, only 2 of 5 days old
    • Depends: pytorch gloo (not considered)
  • Additional info:
    • Updating pytorch will fix bugs in testing: #1115701
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytorch.html
    • Reproducible on amd64 - info ♻
    • Remove hint for (transitive) dependency: blis
• qad (0.0~git20230808.ae0c099+dfsg-1 to 0.0~git20240206.43adc42+dfsg-1)
  • Migration status for qad (0.0~git20230808.ae0c099+dfsg-1 to 0.0~git20240206.43adc42+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Updating qad will fix bugs in testing: #1097685
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qad.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• qgnomeplatform (0.9.2-4 to 0.9.2-5)
  • Migration status for qgnomeplatform (0.9.2-4 to 0.9.2-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qgnomeplatform.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ros-dynamic-reconfigure (1.7.3-2 to 1.7.6-1)
  • Migration status for ros-dynamic-reconfigure (1.7.3-2 to 1.7.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros-dynamic-reconfigure.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• ruby-asciidoctor-pdf (2.3.19-2 to 2.3.19-3)
  • Migration status for ruby-asciidoctor-pdf (2.3.19-2 to 2.3.19-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-asciidoctor-pdf.html
    • autopkgtest for ruby-asciidoctor-pdf/2.3.19-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ruby-kramdown-rfc2629 (1.7.14-1 to 1.7.29-1)
  • Migration status for ruby-kramdown-rfc2629 (1.7.14-1 to 1.7.29-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/ruby-kramdown-rfc2629.html
    • autopkgtest for ruby-kramdown-rfc2629/1.7.29-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• runc (1.1.15+ds1-2 to 1.3.0+ds1-3)
  • Migration status for runc (1.1.15+ds1-2 to 1.3.0+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-containers-buildah/1.39.3+ds1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for golang-github-containers-common/0.62.2+ds1-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for runc/1.3.0+ds1-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on riscv64 - info
    • Too young, only 2 of 5 days old
    • Build-Depends(-Arch): runc golang-github-cilium-ebpf
    • Build-Depends(-Arch): runc golang-github-opencontainers-cgroups (not considered)
    • Depends: runc golang-github-cilium-ebpf
    • Depends: runc golang-github-opencontainers-cgroups (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/runc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-needletail (0.5.1-1 to 0.6.3-2)
  • Migration status for rust-needletail (0.5.1-1 to 0.6.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Waiting for lintian test results on i386, armhf - info
    • Build-Depends(-Arch): rust-needletail rust-liblzma/armhf
    • Build-Depends(-Arch): rust-needletail rust-liblzma/i386
    • Depends: rust-needletail rust-liblzma/armhf
    • Depends: rust-needletail rust-liblzma/i386
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-needletail.html
    • autopkgtest for rust-needletail/0.6.3-2: amd64: Pass, arm64: 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
    • 2 days old (needed 2 days)
• saytime (1.0-36 to 1.0-37)
  • Migration status for saytime (1.0-36 to 1.0-37): Waiting for test results or 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 saytime will fix bugs in testing: #1097846
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/saytime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• slic3r-prusa (2.9.2+dfsg-2 to 2.9.3+dfsg-1)
  • Migration status for slic3r-prusa (2.9.2+dfsg-2 to 2.9.3+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r-prusa.html
    • autopkgtest for slic3r-prusa/2.9.3+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
• systemd-udeb (257.4-1 to 258-1)
  • Migration status for systemd-udeb (257.4-1 to 258-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)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• tqdm (4.67.1-5 to 4.67.1-6)
  • Migration status for tqdm (4.67.1-5 to 4.67.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dipy/1.11.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for ipyparallel/8.8.0-6: amd64: Pass, arm64: Pass, i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • autopkgtest for mdanalysis: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Test triggered (failure will be ignored)
    • autopkgtest for mpire/2.10.2-3: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
    • autopkgtest for python-pyvista/0.44.1-11: amd64: Pass, arm64: Regression ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tqdm.html
    • Waiting for reproducibility test results on arm64 - info ♻
• twisted (24.11.0-1 to 25.5.0-2)
  • Migration status for twisted (24.11.0-1 to 25.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for twisted/25.5.0-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Pass, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Pass
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/twisted.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• virtme-ng (1.35-1 to 1.37-1)
  • Migration status for virtme-ng (1.35-1 to 1.37-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virtme-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• yquake2 (8.51+dfsg-2 to 8.60+dfsg-1)
  • Migration status for yquake2 (8.51+dfsg-2 to 8.60+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 2 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• appstream (1.0.6-2 to 1.1.0-1)
  • Migration status for appstream (1.0.6-2 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for appstream/1.1.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for lintian/2.124.0: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Regression ♻ (reference ♻)
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/appstream.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• asm-jdk-bridge (- to 0.0.10-2)
  • Migration status for asm-jdk-bridge (- to 0.0.10-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asm-jdk-bridge.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• audit (1:4.1.1-1 to 1:4.1.2-1)
  • Migration status for audit (1:4.1.1-1 to 1:4.1.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/audit.html
    • autopkgtest for audit/1:4.1.2-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 ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for glibc/2.41-12: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ax25-apps (0.0.8-rc5+git20230513+afc4a5f-3 to 0.0.8-rc5+git20230513+afc4a5f-4)
  • Migration status for ax25-apps (0.0.8-rc5+git20230513+afc4a5f-3 to 0.0.8-rc5+git20230513+afc4a5f-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/a/ax25-apps.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• dqlite (1.18.2-1 to 1.18.2-3)
  • Migration status for dqlite (1.18.2-1 to 1.18.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating dqlite will fix bugs in testing: #1114094
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dqlite.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• entangle (3.0-4 to 3.0-5)
  • Migration status for entangle (3.0-4 to 3.0-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/entangle.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• etherape (0.9.20-2 to 0.9.21-1)
  • Migration status for etherape (0.9.20-2 to 0.9.21-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 etherape will fix bugs in testing: #1096593
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/etherape.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• evolution (3.56.2-2 to 3.56.2-3)
  • Migration status for evolution (3.56.2-2 to 3.56.2-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating evolution will fix bugs in testing: #1018120
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/evolution.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• fheroes2 (1.1.10+dfsg-1 to 1.1.11+dfsg-1)
  • Migration status for fheroes2 (1.1.10+dfsg-1 to 1.1.11+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• firefox (- to 143.0-1)
  • Migration status for firefox (- to 143.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating firefox would introduce bugs in testing: #1017919, #1099130, #817954, #992263, #993659
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results on s390x - info
    • Too young, only 3 of 5 days old
    • Build-Depends(-Arch): firefox nss
    • Depends: firefox nss
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firefox.html
    • Reproducible on amd64 - info ♻
• fontforge (1:20230101~dfsg-5 to 1:20230101~dfsg-7)
  • Migration status for fontforge (1:20230101~dfsg-5 to 1:20230101~dfsg-7): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fontforge.html
    • Reproducible on arm64 - info ♻
• fonts-fantasque-sans (1.8.0+git20220316+dfsg-2 to 1.8.0+git20220316+dfsg-3)
  • Migration status for fonts-fantasque-sans (1.8.0+git20220316+dfsg-2 to 1.8.0+git20220316+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
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-fantasque-sans.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• foot (1.23.1-1 to 1.24.0-1)
  • Migration status for foot (1.23.1-1 to 1.24.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foot.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• fortran-testdrive (- to 0.5.0-3)
  • Migration status for fortran-testdrive (- to 0.5.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fortran-testdrive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gambas3 (3.20.2-2 to 3.20.4-1)
  • Migration status for gambas3 (3.20.2-2 to 3.20.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating gambas3 will fix bugs in testing: #1096670
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gambas3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ganeti (3.1.0~rc2-3 to 3.1.0~rc2-4)
  • Migration status for ganeti (3.1.0~rc2-3 to 3.1.0~rc2-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganeti.html
    • autopkgtest for ganeti/3.1.0~rc2-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ganeti-os-noop (0.2-5 to 0.2-6)
  • Migration status for ganeti-os-noop (0.2-5 to 0.2-6): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganeti-os-noop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-contacts (48.0-3 to 49.0-1)
  • Migration status for gnome-contacts (48.0-3 to 49.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-contacts.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-mahjongg (1:48.1-2 to 1:49.0-1)
  • Migration status for gnome-mahjongg (1:48.1-2 to 1:49.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-mahjongg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-mines (1:48.1-2 to 1:49.0.1-1)
  • Migration status for gnome-mines (1:48.1-2 to 1:49.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-mines.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-nibbles (1:4.2.2-1 to 1:4.4.1-1)
  • Migration status for gnome-nibbles (1:4.2.2-1 to 1:4.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/g/gnome-nibbles.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-remote-desktop (48.1-4 to 48.2-1)
  • Migration status for gnome-remote-desktop (48.1-4 to 48.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • autopkgtest for gnome-remote-desktop/48.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Waiting for lintian test results on s390x - info
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-remote-desktop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• golang-github-cenk-rpc2 (0.0~git20160427.0.7ab76d2e88c7-1.1 to 0.0~git20240915.0.ff2a9be-1)
  • Migration status for golang-github-cenk-rpc2 (0.0~git20160427.0.7ab76d2e88c7-1.1 to 0.0~git20240915.0.ff2a9be-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-cenk-rpc2/0.0~git20240915.0.ff2a9be-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-cenk-rpc2.html
    • Reproducible on arm64 - info ♻
• golang-github-meilisearch-meilisearch-go (0.33.3-1 to 0.34.0-1)
  • Migration status for golang-github-meilisearch-meilisearch-go (0.33.3-1 to 0.34.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-meilisearch-meilisearch-go.html
    • autopkgtest for golang-github-meilisearch-meilisearch-go/0.34.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gtklp (1.3.4-3 to 1.3.4-4)
  • Migration status for gtklp (1.3.4-3 to 1.3.4-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gtklp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• guile-3.0 (3.0.10+really3.0.10-4 to 3.0.10+really3.0.10-6)
  • Migration status for guile-3.0 (3.0.10+really3.0.10-4 to 3.0.10+really3.0.10-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 guile-3.0 will fix bugs in testing: #1096788
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guile-3.0.html
    • Reproducible on arm64 - info ♻
• harlequin (- to 2.1.3-1)
  • Migration status for harlequin (- to 2.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating harlequin would introduce bugs in testing: #1099499
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/harlequin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• jigdo (0.8.2-1 to 0.8.2-1.2)
  • Migration status for jigdo (0.8.2-1 to 0.8.2-1.2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jigdo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• kf6-kio (6.13.0-6 to 6.13.0-7)
  • Migration status for kf6-kio (6.13.0-6 to 6.13.0-7): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • Waiting for lintian test results on arm64 - info
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating kf6-kio will fix bugs in testing: #1110456
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kf6-kio.html
    • Reproducible on amd64 - info ♻
• kinect-audio-setup (0.5-2 to 0.5-3)
  • Migration status for kinect-audio-setup (0.5-2 to 0.5-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating kinect-audio-setup will fix bugs in testing: #1063582
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• kio (5.116.0-1 to 5.116.0-2)
  • Migration status for kio (5.116.0-1 to 5.116.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on arm64 - info
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating kio will fix bugs in testing: #1110457
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kio.html
    • Reproducible on amd64 - info ♻
• klutshnik (0.2.1-1 to 0.2.1-1.1)
  • Migration status for klutshnik (0.2.1-1 to 0.2.1-1.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/klutshnik.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• lcrq (0.2.3-1 to 0.2.4-2)
  • Migration status for lcrq (0.2.3-1 to 0.2.4-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lcrq.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• libervia-pubsub (0.5.0~hg494-1 to 0.5.0~hg494-2)
  • Migration status for libervia-pubsub (0.5.0~hg494-1 to 0.5.0~hg494-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/libe/libervia-pubsub.html
    • autopkgtest for libervia-pubsub/0.5.0~hg494-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• libjs-img.srcset (2.0.0~20131003~dfsg-4.1 to 2.0.0~20131003~dfsg-5)
  • Migration status for libjs-img.srcset (2.0.0~20131003~dfsg-4.1 to 2.0.0~20131003~dfsg-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjs-img.srcset.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• librecast (0.9.1-1 to 0.11.2-2)
  • Migration status for librecast (0.9.1-1 to 0.11.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Build-Depends(-Arch): librecast lcrq (not considered)
    • Depends: librecast lcrq (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/librecast.html
    • autopkgtest for librecast/0.11.2-2: amd64: Pass, arm64: 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
    • 3 days old (needed 2 days)
• librime (1.13.1+dfsg1-1 to 1.14.0+dfsg1-1)
  • Migration status for librime (1.13.1+dfsg1-1 to 1.14.0+dfsg1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/librime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• mediawiki2latex (8.29-1 to 8.30-1)
  • Migration status for mediawiki2latex (8.29-1 to 8.30-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mediawiki2latex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• mstflint (4.31.0+1-4 to 4.33.0+1-1)
  • Migration status for mstflint (4.31.0+1-4 to 4.33.0+1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating mstflint will fix bugs in testing: #1097420
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mstflint.html
    • autopkgtest for mstflint/4.33.0+1-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• myspell-hy (0.20.0-2.2 to 0.20.0-4)
  • Migration status for myspell-hy (0.20.0-2.2 to 0.20.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating myspell-hy will fix bugs in testing: #1114877
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/myspell-hy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• nsntrace (4-1 to 4.5.g4d02e74-1)
  • Migration status for nsntrace (4-1 to 4.5.g4d02e74-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 nsntrace will fix bugs in testing: #1097480
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nsntrace.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• nss (2:3.114-1 to 2:3.116-1)
  • Migration status for nss (2:3.114-1 to 2:3.116-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/nss.html
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for openjdk-21/21.0.9~5ea-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for openjdk-25/25~36ea-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered (failure will be ignored), s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for openjdk-26/26~12ea-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for thunderbird/1:128.14.0esr-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored)
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• nvidia-graphics-drivers-legacy-340xx (- to 340.108-26)
  • Migration status for nvidia-graphics-drivers-legacy-340xx (- to 340.108-26): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-legacy-340xx would introduce bugs in testing: #1004848, #1011141, #1016615, #1025280, #1033775, #1039679, #1055137, #1064984, #1072793, #1085969, #1093909, #1104069, #1109908, #973599, #979671, #987217, #991352
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-legacy-340xx/340.108-26: amd64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
• openjdk-25 (25~36ea-1 to 25+36-1)
  • Migration status for openjdk-25 (25~36ea-1 to 25+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/o/openjdk-25.html
    • autopkgtest for bbmap/39.20+dfsg-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for openjdk-25/25+36-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: No tests, superficial or marked flaky ♻
• openmcdf (1.5.4-3.1 to 1.5.4+dfsg-2)
  • Migration status for openmcdf (1.5.4-3.1 to 1.5.4+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:
    • Updating openmcdf will fix bugs in testing: #1114875
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmcdf.html
    • No reference result, but not reproducibility on amd64 - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
• osmocom-dahdi-linux (0.0~git20241003.b2ea348-4 to 0.0~git20250226.6dada77-2)
  • Migration status for osmocom-dahdi-linux (0.0~git20241003.b2ea348-4 to 0.0~git20250226.6dada77-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/osmocom-dahdi-linux.html
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating osmocom-dahdi-linux will fix bugs in testing: #1106552
    • autopkgtest for osmocom-dahdi-linux/0.0~git20250226.6dada77-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• pkcs11-provider (1.0-3 to 1.1.0-1)
  • Migration status for pkcs11-provider (1.0-3 to 1.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pkcs11-provider.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• poco (1.13.0-6 to 1.14.2-2)
  • Migration status for poco (1.13.0-6 to 1.14.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating poco would introduce bugs in testing: #1115538
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating poco will fix bugs in testing: #1097628
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/poco.html
• python-certbot-dns-desec (1.2.1-4 to 1.3.2-1)
  • Migration status for python-certbot-dns-desec (1.2.1-4 to 1.3.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-desec.html
    • autopkgtest for python-certbot-dns-desec/1.3.2-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-nh3 (0.2.18-2 to 0.3.0-1)
  • Migration status for python-nh3 (0.2.18-2 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): python-nh3 rust-ouroboros (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Updating python-nh3 will fix bugs in testing: #1114314
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nh3.html
    • autopkgtest for python-nh3/0.3.0-1: amd64: Pass, arm64: 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
    • 3 days old (needed 2 days)
• qstat (2.17-1 to 2.17-2)
  • Migration status for qstat (2.17-1 to 2.17-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 qstat will fix bugs in testing: #1097713
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qstat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• quadrapassel (1:40.2-4 to 1:49.0-1)
  • Migration status for quadrapassel (1:40.2-4 to 1:49.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating quadrapassel will fix bugs in testing: #1018135
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quadrapassel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ros-actionlib (1.14.0-8 to 1.14.3-1)
  • Migration status for ros-actionlib (1.14.0-8 to 1.14.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Depends: ros-actionlib ros-ros-comm (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros-actionlib.html
    • autopkgtest for ros-actionlib/1.14.3-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• ros-bond-core (1.8.6-11 to 1.8.7-1)
  • Migration status for ros-bond-core (1.8.6-11 to 1.8.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
    • Depends: ros-bond-core ros-ros-comm (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros-bond-core.html
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• rst2pdf (0.102-4 to 0.102-5)
  • Migration status for rst2pdf (0.102-4 to 0.102-5): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rst2pdf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rsyslog-doc (8.2506.0+dfsg-2 to 8.2506.0+dfsg-3)
  • Migration status for rsyslog-doc (8.2506.0+dfsg-2 to 8.2506.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rsyslog-doc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-gtk4 (0.10.0-2 to 0.10.0-4)
  • Migration status for rust-gtk4 (0.10.0-2 to 0.10.0-4): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-gtk4.html
    • autopkgtest for rust-gst-plugin-gtk4/0.14.0-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for rust-gtk4/0.10.0-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-meow-cli (2.1.4-1 to 2.1.5-1)
  • Migration status for rust-meow-cli (2.1.4-1 to 2.1.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-meow-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-ouroboros-macro (0.15.6-1 to 0.18.5-1)
  • Migration status for rust-ouroboros-macro (0.15.6-1 to 0.18.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-ouroboros-macro rust-proc-macro2-diagnostics (not considered)
    • Depends: rust-ouroboros-macro rust-proc-macro2-diagnostics (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Implicit dependency: rust-ouroboros-macro rust-ouroboros
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ouroboros-macro.html
    • autopkgtest for rust-ouroboros-macro/0.18.5-1: amd64: Pass, arm64: 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
    • 3 days old (needed 2 days)
• rust-tealdeer (1.7.2-1 to 1.7.2-2)
  • Migration status for rust-tealdeer (1.7.2-1 to 1.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 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-tealdeer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rygel (45~rc-2 to 45.0-1)
  • Migration status for rygel (45~rc-2 to 45.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/rygel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• sccache (0.10.0-8 to 0.10.0-9)
  • Migration status for sccache (0.10.0-8 to 0.10.0-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/s/sccache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• sdl-kitchensink (1.0.12-1 to 1.0.13-1)
  • Migration status for sdl-kitchensink (1.0.12-1 to 1.0.13-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sdl-kitchensink.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• sphinx-data-viewer (0.1.5-2 to 0.1.5-3)
  • Migration status for sphinx-data-viewer (0.1.5-2 to 0.1.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sphinx-data-viewer sphinx-needs (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-data-viewer.html
    • autopkgtest for sphinx-data-viewer/0.1.5-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 3 days old (needed 2 days)
• subtitlecomposer (0.8.1-2 to 0.8.2-1)
  • Migration status for subtitlecomposer (0.8.1-2 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/subtitlecomposer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• thc-ipv6 (3.8-1 to 3.8-2)
  • Migration status for thc-ipv6 (3.8-1 to 3.8-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 thc-ipv6 will fix bugs in testing: #1097992, #1112674
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/thc-ipv6.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ui-auto (1.2.16-1 to 1.2.17-1)
  • Migration status for ui-auto (1.2.16-1 to 1.2.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ui-auto.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: bcron
• uronode (2.15-5 to 2.15-6)
  • Migration status for uronode (2.15-5 to 2.15-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 uronode will fix bugs in testing: #1098045
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uronode.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• valijson (1.0.3+repack-2 to 1.0.6+repack-0.1)
  • Migration status for valijson (1.0.3+repack-2 to 1.0.6+repack-0.1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Updating valijson will fix bugs in testing: #1114430
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/valijson.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• vinetto (1:0.8.0-5 to 1:0.9.13-1)
  • Migration status for vinetto (1:0.8.0-5 to 1:0.9.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vinetto.html
    • autopkgtest for vinetto/1:0.9.13-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• virtualbox (- to 7.2.2-dfsg-2)
  • Migration status for virtualbox (- to 7.2.2-dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating virtualbox would introduce bugs in testing: #794466
    • Too young, only 3 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for virtualbox/7.2.2-dfsg-2: amd64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
• vlfeat (0.9.21+full-3 to 0.9.21+full-4)
  • Migration status for vlfeat (0.9.21+full-3 to 0.9.21+full-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vlfeat.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• xlbiff (4.6.6-1 to 4.6.7-1)
  • Migration status for xlbiff (4.6.6-1 to 4.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 7 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xlbiff.html
    • autopkgtest for xlbiff/4.6.7-1: amd64: Pass, arm64: 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
• zkg (3.0.1-1 to 3.1.0-1)
  • Migration status for zkg (3.0.1-1 to 3.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zkg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• zmat (0.9.9+ds.1-4 to 0.9.9+ds.1-6)
  • Migration status for zmat (0.9.9+ds.1-4 to 0.9.9+ds.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zmat.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• zope.hookable (7.0-1 to 8.0-1)
  • Migration status for zope.hookable (7.0-1 to 8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zope.hookable would introduce bugs in testing: #1115803
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zope.hookable.html
    • autopkgtest for zope.hookable/8.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• zope.location (5.1-1 to 6.0-1)
  • Migration status for zope.location (5.1-1 to 6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating zope.location would introduce bugs in testing: #1115763
    • Too young, only 3 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zope.location.html
    • autopkgtest for zope.location/6.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• avogadro (1.100.0-2 to 1.101.0-1)
  • Migration status for avogadro (1.100.0-2 to 1.101.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/a/avogadro.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• bpftop (0.5.2.20.gc23a822-2 to 0.5.2.20.gc23a822-3)
  • Migration status for bpftop (0.5.2.20.gc23a822-2 to 0.5.2.20.gc23a822-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating bpftop will fix bugs in testing: #1115123
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bpftop.html
    • autopkgtest for bpftop/0.5.2.20.gc23a822-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• cccl (2.3.2-3 to 2.4.0-1)
  • Migration status for cccl (2.3.2-3 to 2.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cccl.html
    • autopkgtest for cccl/2.4.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
• converseen (0.15.0.2-1 to 0.15.0.3-1)
  • Migration status for converseen (0.15.0.2-1 to 0.15.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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/converseen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• d-spy (48.0-3 to 49.1-1)
  • Migration status for d-spy (48.0-3 to 49.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/d-spy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• dbab (1.5.8-1.1 to 1.6.1-1)
  • Migration status for dbab (1.5.8-1.1 to 1.6.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating dbab will fix bugs in testing: #1100058
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for dbab/1.6.1-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 ♻
• dconf (0.40.0-5 to 0.49.0-1)
  • Migration status for dconf (0.40.0-5 to 0.49.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/d/dconf.html
    • autopkgtest for ayatana-indicator-session: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Test triggered (failure will be ignored)
    • autopkgtest for dconf/0.49.0-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 ♻
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• emacs-git-modes (1.4.5-1 to 1.4.6-1)
  • Migration status for emacs-git-modes (1.4.5-1 to 1.4.6-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-git-modes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• erlang (1:27.3.4.1+dfsg-1 to 1:27.3.4.3+dfsg-1)
  • Migration status for erlang (1:27.3.4.1+dfsg-1 to 1:27.3.4.3+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/erlang.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• ferret-vis (7.6.0-8 to 7.6.0-9)
  • Migration status for ferret-vis (7.6.0-8 to 7.6.0-9): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating ferret-vis will fix bugs in testing: #1096625
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/ferret-vis.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• fio (3.39-1 to 3.41-2)
  • Migration status for fio (3.39-1 to 3.41-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• fonts-noto-color-emoji (2.048-1 to 2.051-1)
  • Migration status for fonts-noto-color-emoji (2.048-1 to 2.051-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-noto-color-emoji.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• foomatic-filters (4.0.17-16 to 4.0.17-17)
  • Migration status for foomatic-filters (4.0.17-16 to 4.0.17-17): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating foomatic-filters will fix bugs in testing: #1096646
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/foomatic-filters.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ft2-clone (1.95+ds-1 to 1.98+ds-1)
  • Migration status for ft2-clone (1.95+ds-1 to 1.98+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• gcc-13-cross-ports (23 to 24)
  • Migration status for gcc-13-cross-ports (23 to 24): Waiting for test results or another package, or too young (no action required now - 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/gcc-13-cross-ports.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
• gigolo (0.5.4-1 to 0.6.0-1)
  • Migration status for gigolo (0.5.4-1 to 0.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gigolo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-boxes (49~rc.1-1 to 49.0-1)
  • Migration status for gnome-boxes (49~rc.1-1 to 49.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-boxes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: bcron
• gnome-control-center (1:48.4-1 to 1:49.0-1)
  • Migration status for gnome-control-center (1:48.4-1 to 1:49.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-control-center.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-shell-extension-arc-menu (66-1 to 67.1-1)
  • Migration status for gnome-shell-extension-arc-menu (66-1 to 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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-arc-menu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-shell-extension-dash-to-panel (68-2 to 70-1)
  • Migration status for gnome-shell-extension-dash-to-panel (68-2 to 70-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-dash-to-panel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-shell-extension-dashtodock (101-1 to 102-1)
  • Migration status for gnome-shell-extension-dashtodock (101-1 to 102-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-dashtodock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gnome-shell-extension-hide-activities (48-2 to 49-1)
  • Migration status for gnome-shell-extension-hide-activities (48-2 to 49-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-shell-extension-hide-activities.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• golang-github-armon-consul-api (0.0~git20150107.0.dcfedd5-4.1 to 0.0~git20180202.0.eb2c6b5-1)
  • Migration status for golang-github-armon-consul-api (0.0~git20150107.0.dcfedd5-4.1 to 0.0~git20180202.0.eb2c6b5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-armon-consul-api/0.0~git20180202.0.eb2c6b5-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Pass
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-armon-consul-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• golang-github-google-go-cmp (0.6.0-1 to 0.7.0-1)
  • Migration status for golang-github-google-go-cmp (0.6.0-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 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-google-go-cmp.html
    • autopkgtest for golang-github-google-go-cmp/0.7.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gthumb (3:3.12.7-1 to 3:3.12.8-1)
  • Migration status for gthumb (3:3.12.7-1 to 3:3.12.8-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gthumb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gvfs (1.57.2-3 to 1.58.0-1)
  • Migration status for gvfs (1.57.2-3 to 1.58.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gvfs.html
    • autopkgtest for gvfs/1.58.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• hl-todo-el (3.8.5-1 to 3.9.0-1)
  • Migration status for hl-todo-el (3.8.5-1 to 3.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 4 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 ♻
• htmldoc (1.9.20-1 to 1.9.21-1)
  • Migration status for htmldoc (1.9.20-1 to 1.9.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/h/htmldoc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• htmx (2.0.6-1 to 2.0.7-1)
  • Migration status for htmx (2.0.6-1 to 2.0.7-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/htmx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• idlestat (0.8-8 to 0.8-9)
  • Migration status for idlestat (0.8-8 to 0.8-9): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/idlestat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• insserv (1.26.0-1 to 1.27.0-1)
  • Migration status for insserv (1.26.0-1 to 1.27.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating insserv will fix bugs in testing: #1096840
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/insserv.html
    • autopkgtest for insserv/1.27.0-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• intel-ipsec-mb (2.0.1-1 to 2.0.1-2)
  • Migration status for intel-ipsec-mb (2.0.1-1 to 2.0.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-ipsec-mb.html
    • Reproducible on amd64 - info ♻
• json-editor.js (1.3.2+ds-3 to 1.3.2+ds-4)
  • Migration status for json-editor.js (1.3.2+ds-3 to 1.3.2+ds-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/json-editor.js.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• juce (8.0.8+ds-1 to 8.0.9+ds-1)
  • Migration status for juce (8.0.8+ds-1 to 8.0.9+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for juce/8.0.9+ds-1: amd64: Pass, arm64: Regression ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/juce.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• k2pdfopt (2.55+ds-3.1 to 2.55+ds-4)
  • Migration status for k2pdfopt (2.55+ds-3.1 to 2.55+ds-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/k/k2pdfopt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• latticeextra (0.6-30-1 to 0.6-31-1)
  • Migration status for latticeextra (0.6-30-1 to 0.6-31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/latticeextra.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• lbreakouthd (1.1.11-1 to 1.2-2)
  • Migration status for lbreakouthd (1.1.11-1 to 1.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lbreakouthd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• lft (3.91-2 to 3.91-3)
  • Migration status for lft (3.91-2 to 3.91-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/l/lft.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• libobject-pad-perl (0.820-1 to 0.821-1)
  • Migration status for libobject-pad-perl (0.820-1 to 0.821-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 libobject-pad-perl/0.821-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results on i386 - info
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libobject-pad-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• libtest2-harness-perl (1.000158-1 to 1.000161-1)
  • Migration status for libtest2-harness-perl (1.000158-1 to 1.000161-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libtest2-harness-perl.html
    • autopkgtest for libtest2-harness-perl/1.000161-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• libxfce4windowing (4.20.3-1 to 4.20.4-1)
  • Migration status for libxfce4windowing (4.20.3-1 to 4.20.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/libx/libxfce4windowing.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• mcpp (2.7.2-5.2 to 2.7.2-5.3)
  • Migration status for mcpp (2.7.2-5.2 to 2.7.2-5.3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating mcpp will fix bugs in testing: #1097375
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mcpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• mdp-src (1.0.15-1 to 1.0.18-1)
  • Migration status for mdp-src (1.0.15-1 to 1.0.18-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mdp-src.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• megapixels (1.8.3-1 to 1.8.3-2)
  • Migration status for megapixels (1.8.3-1 to 1.8.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating megapixels will fix bugs in testing: #1097380
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/megapixels.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• miniupnpc (2.2.8-2 to 2.3.3-2)
  • Migration status for miniupnpc (2.2.8-2 to 2.3.3-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/miniupnpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• mozjs140 (140.2.0-1 to 140.3.0-1)
  • Migration status for mozjs140 (140.2.0-1 to 140.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/m/mozjs140.html
    • autopkgtest for mozjs140/140.3.0-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 ♻
    • Reproducible on amd64 - info ♻
• nautilus (48.3-2 to 49.0-1)
  • Migration status for nautilus (48.3-2 to 49.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
    • Implicit dependency: nautilus nautilus-python
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• no-littering-el (1.7.9-1 to 1.8.0-1)
  • Migration status for no-littering-el (1.7.9-1 to 1.8.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/no-littering-el.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• node-http-server (14.1.1+~cs3.16.36-1 to 14.1.1+~cs3.16.39-1)
  • Migration status for node-http-server (14.1.1+~cs3.16.36-1 to 14.1.1+~cs3.16.39-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-http-server.html
    • autopkgtest for node-http-server/14.1.1+~cs3.16.39-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ocaml-iomux (- to 0.3-1)
  • Migration status for ocaml-iomux (- to 0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/o/ocaml-iomux.html
    • Too young, only 4 of 5 days old
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ocaml-spawn (- to 0.17.0-1)
  • Migration status for ocaml-spawn (- to 0.17.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocaml-spawn.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• octave-bim (1.1.8-2 to 1.1.8-3)
  • Migration status for octave-bim (1.1.8-2 to 1.1.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating octave-bim will fix bugs in testing: #1115131
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-bim.html
    • autopkgtest for octave-bim/1.1.8-3: amd64: Pass, arm64: Pass, i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• pngcrush (1.8.13-2 to 1.8.13-3)
  • Migration status for pngcrush (1.8.13-2 to 1.8.13-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pngcrush.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• printer-driver-oki (1.0.2-1 to 1.0.2-2)
  • Migration status for printer-driver-oki (1.0.2-1 to 1.0.2-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/printer-driver-oki.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• psst (1.0-8 to 1.0-9)
  • Migration status for psst (1.0-8 to 1.0-9): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psst.html
    • Reproducible on amd64 - info ♻
• pyferret (7.6.5-9 to 7.6.5-10)
  • Migration status for pyferret (7.6.5-9 to 7.6.5-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 pyferret will fix bugs in testing: #1114278
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyferret.html
    • autopkgtest for pyferret/7.6.5-10: 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 ♻
    • No reference result, but not reproducibility on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
• python-fakeredis (2.29.0-4 to 2.29.0-5)
  • Migration status for python-fakeredis (2.29.0-4 to 2.29.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/p/python-fakeredis.html
    • autopkgtest for python-fakeredis/2.29.0-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-imgviz (1.7.5+ds-2 to 1.7.6+ds-2)
  • Migration status for python-imgviz (1.7.5+ds-2 to 1.7.6+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-imgviz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• python-pytest-asyncio (0.25.1-1 to 1.1.0-2)
  • Migration status for python-pytest-asyncio (0.25.1-1 to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for aiohttp-sse/2.2.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for aioimaplib/2.0.1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for opendrop/3.3.2-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for python-aiortc/1.11.0-1: amd64: Test triggered (failure will be ignored), arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for python-jsonrpc-websocket/3.1.5-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for python-pytest-asyncio/1.1.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rtsp-to-webrtc/0.6.1-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating python-pytest-asyncio will fix bugs in testing: #1114323
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pytest-asyncio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-repoze.sphinx.autointerface (1.0.0-2 to 1.0.0-3)
  • Migration status for python-repoze.sphinx.autointerface (1.0.0-2 to 1.0.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating python-repoze.sphinx.autointerface will fix bugs in testing: #1114327
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-repoze.sphinx.autointerface.html
    • autopkgtest for python-repoze.sphinx.autointerface/1.0.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-simple-pid (- to 2.0.1-1)
  • Migration status for python-simple-pid (- to 2.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-simple-pid.html
    • autopkgtest for python-simple-pid/2.0.1-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 ♻
    • Reproducible on amd64 - info ♻
• qatzip (1.3.1-2 to 1.3.1-3)
  • Migration status for qatzip (1.3.1-2 to 1.3.1-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qatzip.html
    • Reproducible on amd64 - info ♻
• qgis (3.40.10+dfsg-1 to 3.40.11+dfsg-1)
  • Migration status for qgis (3.40.10+dfsg-1 to 3.40.11+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qgis.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Remove hint for (transitive) dependency: blis
• rlpr (2.06-2 to 2.06-3)
  • Migration status for rlpr (2.06-2 to 2.06-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating rlpr will fix bugs in testing: #1097795
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rlpr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ros-ros-comm (1.17.0+ds-2 to 1.17.4+ds-3)
  • Migration status for ros-ros-comm (1.17.0+ds-2 to 1.17.4+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ros-ros-comm.html
    • autopkgtest for ros-ros-comm/1.17.4+ds-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• rust-opendal (- to 0.54.0-2)
  • Migration status for rust-opendal (- to 0.54.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-opendal-dev/armhf has unsatisfiable dependency
    • librust-opendal-dev/i386 has unsatisfiable dependency
    • autopkgtest for rust-opendal/0.54.0-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Too young, only 4 of 5 days old
    • Depends: rust-opendal rust-futures-rustls (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-opendal.html
    • uninstallable on arch i386, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-ouroboros (0.15.6-1 to 0.18.5-1)
  • Migration status for rust-ouroboros (0.15.6-1 to 0.18.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-ouroboros rust-ouroboros-macro (not considered)
    • Depends: rust-ouroboros rust-ouroboros-macro (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ouroboros.html
    • autopkgtest for rust-ouroboros/0.18.5-1: amd64: Pass, arm64: 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
    • 4 days old (needed 2 days)
• srpc (0.10.3-2 to 0.10.3-3)
  • Migration status for srpc (0.10.3-2 to 0.10.3-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for srpc/0.10.3-3: amd64: Pass, arm64: Pass, i386: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results on ppc64el - info
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating srpc will fix bugs in testing: #1114396
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/srpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• startpar (0.66-1 to 0.67-1)
  • Migration status for startpar (0.66-1 to 0.67-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 startpar will fix bugs in testing: #1097938
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/startpar.html
    • autopkgtest for startpar/0.67-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• thunar (4.20.4-1 to 4.20.5-1)
  • Migration status for thunar (4.20.4-1 to 4.20.5-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/thunar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• uucp (1.07-30 to 1.07-31)
  • Migration status for uucp (1.07-30 to 1.07-31): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating uucp will fix bugs in testing: #1098051
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uucp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: bcron
• vdt (0.4.4-4 to 0.4.4-5)
  • Migration status for vdt (0.4.4-4 to 0.4.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/v/vdt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• virglrenderer (1.1.0-2 to 1.2.0-2)
  • Migration status for virglrenderer (1.1.0-2 to 1.2.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/virglrenderer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• virtualbox-ext-pack (- to 7.2.2-1)
  • Migration status for virtualbox-ext-pack (- to 7.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • virtualbox-ext-pack/arm64 has unsatisfiable dependency
    • Too young, only 4 of 5 days old
    • 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 i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
• virtualbox-guest-additions-iso (7.2.0-3 to 7.2.2-1)
  • Migration status for virtualbox-guest-additions-iso (7.2.0-3 to 7.2.2-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
• wsjtx (2.7.0+repack-1 to 3.0.0~rc1+repack-2)
  • Migration status for wsjtx (2.7.0+repack-1 to 3.0.0~rc1+repack-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/w/wsjtx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• xfireworks (1.3-15 to 1.3-16)
  • Migration status for xfireworks (1.3-15 to 1.3-16): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating xfireworks will fix bugs in testing: #1114447
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xfireworks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• xgks (2.6.1+dfsg.2-17 to 2.6.1+dfsg.2-19)
  • Migration status for xgks (2.6.1+dfsg.2-17 to 2.6.1+dfsg.2-19): Waiting for test results or 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 xgks will fix bugs in testing: #1098141
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xgks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• xtb (6.7.1-2 to 6.7.1-3)
  • Migration status for xtb (6.7.1-2 to 6.7.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Updating xtb will fix bugs in testing: #1114451
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xtb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• yank (1.3.0-1 to 1.3.0-2)
  • Migration status for yank (1.3.0-1 to 1.3.0-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yank.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• yelp (42.3-3 to 49.0-3)
  • Migration status for yelp (42.3-3 to 49.0-3): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yelp.html
    • autopkgtest for yelp/49.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• zope.event (5.0-0.1 to 6.0-1)
  • Migration status for zope.event (5.0-0.1 to 6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 4 of 5 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zope.event.html
    • autopkgtest for zope.event/6.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• ghc (9.6.6-4 to 9.8.4-0~0exp3)
  • Migration status for ghc (9.6.6-4 to 9.8.4-0~0exp3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ghc would introduce bugs in testing: #1115801
    • ghc unsatisfiable Build-Depends(-Arch) on amd64: haskell-devscripts-minimal (>= 0.16.35)
    • ghc unsatisfiable Build-Depends(-Arch) on amd64: hadrian:native (>= 9.8.4~)
    • ghc unsatisfiable Build-Depends(-Arch) on arm64: haskell-devscripts-minimal (>= 0.16.35)
    • ghc unsatisfiable Build-Depends(-Arch) on arm64: hadrian:native (>= 9.8.4~)
    • ghc unsatisfiable Build-Depends(-Arch) on armhf: haskell-devscripts-minimal (>= 0.16.35)
    • ghc unsatisfiable Build-Depends(-Arch) on armhf: hadrian:native (>= 9.8.4~)
    • ghc unsatisfiable Build-Depends(-Arch) on i386: haskell-devscripts-minimal (>= 0.16.35)
    • ghc unsatisfiable Build-Depends(-Arch) on i386: hadrian:native (>= 9.8.4~)
    • ghc unsatisfiable Build-Depends(-Arch) on ppc64el: haskell-devscripts-minimal (>= 0.16.35)
    • ghc unsatisfiable Build-Depends(-Arch) on ppc64el: hadrian:native (>= 9.8.4~)
    • ghc unsatisfiable Build-Depends(-Arch) on riscv64: haskell-devscripts-minimal (>= 0.16.35)
    • ghc unsatisfiable Build-Depends(-Arch) on riscv64: hadrian:native (>= 9.8.4~)
    • ghc unsatisfiable Build-Depends(-Arch) on s390x: haskell-devscripts-minimal (>= 0.16.35)
    • ghc unsatisfiable Build-Depends(-Arch) on s390x: hadrian:native (>= 9.8.4~)
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on s390x, amd64, all, arm64, ppc64el, i386, riscv64, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ghc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 5 days old (needed 5 days)
• gnome-calculator (1:48.1-2 to 1:49.0-1)
  • Migration status for gnome-calculator (1:48.1-2 to 1:49.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-calculator would introduce bugs in testing: #1115326
    • missing build on armhf
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on i386, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-calculator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
• gnome-snapshot (48.0.1-1 to 49.0-1)
  • Migration status for gnome-snapshot (48.0.1-1 to 49.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gnome-snapshot rust-glycin (not considered)
    • Built-Using: gnome-snapshot rust-glycin (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Built-Using: gnome-snapshot rust-glycin-utils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-snapshot.html
    • Reproducible on amd64 - info ♻
    • 5 days old (needed 5 days)
• gst-plugins-bad1.0 (1.26.5-2 to 1.26.6-1)
  • Migration status for gst-plugins-bad1.0 (1.26.5-2 to 1.26.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on ppc64el
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Waiting for lintian test results on amd64, arm64, ppc64el - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gst-plugins-bad1.0.html
    • 5 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• gst-python1.0 (1.26.5-2 to 1.26.6-1)
  • Migration status for gst-python1.0 (1.26.5-2 to 1.26.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gst-python1.0 gst-plugins-bad1.0 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gst-python1.0.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
• gstreamer-vaapi (1.26.5-2 to 1.26.6-1)
  • Migration status for gstreamer-vaapi (1.26.5-2 to 1.26.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gstreamer-vaapi gst-plugins-bad1.0 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gstreamer-vaapi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
• harlequin-postgres (- to 1.2.2-1)
  • Migration status for harlequin-postgres (- to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: harlequin-postgres harlequin (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/harlequin-postgres.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• libbinio (1.5+dfsg-0.1 to 1.5+dfsg-2)
  • Migration status for libbinio (1.5+dfsg-0.1 to 1.5+dfsg-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbinio.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
• libodsstream (0.9.7-1 to 0.9.14-1)
  • Migration status for libodsstream (0.9.7-1 to 0.9.14-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 10 days old
  • Additional info:
    • Updating libodsstream will fix bugs in testing: #1097240
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libodsstream.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• llama.cpp (5882+dfsg-3 to 5882+dfsg-4)
  • Migration status for llama.cpp (5882+dfsg-3 to 5882+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for llama.cpp/5882+dfsg-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llama.cpp.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• nlohmann-json3 (3.11.3-2.1 to 3.12.0.really.3.12.0-3)
  • Migration status for nlohmann-json3 (3.11.3-2.1 to 3.12.0.really.3.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nlohmann-json3 would introduce bugs in testing: #1106446, #1106447, #1106448, #1110784, #1110787, #1110805
  • Additional info:
    • Updating nlohmann-json3 will fix bugs in testing: #1111390
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nlohmann-json3.html
    • autopkgtest for nlohmann-json3/3.12.0.really.3.12.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
• node-form-data (4.0.1-2 to 4.0.4+~2.1.0-1)
  • Migration status for node-form-data (4.0.1-2 to 4.0.4+~2.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): node-form-data node-to-buffer (not considered)
    • Depends: node-form-data node-to-buffer (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-form-data.html
    • autopkgtest for node-form-data/4.0.4+~2.1.0-1: amd64: Pass, arm64: 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
    • 5 days old (needed 2 days)
• node-sha.js (2.4.11+~2.4.0-2 to 2.4.12+~3.0.5-1)
  • Migration status for node-sha.js (2.4.11+~2.4.0-2 to 2.4.12+~3.0.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): node-sha.js node-to-buffer (not considered)
    • Depends: node-sha.js node-to-buffer (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Updating node-sha.js will fix bugs in testing: #1111769
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-sha.js.html
    • autopkgtest for node-sha.js/2.4.12+~3.0.5-1: amd64: Pass, arm64: 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
    • 5 days old (needed 2 days)
• node-to-buffer (- to 1.2.1+~cs4.3.9-2)
  • Migration status for node-to-buffer (- to 1.2.1+~cs4.3.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-to-buffer/1.2.1+~cs4.3.9-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-to-buffer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
• numatop (2.5.1-1 to 2.5.1-2)
  • Migration status for numatop (2.5.1-1 to 2.5.1-2): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 5 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/numatop.html
    • Reproducible on amd64 - info ♻
• polymake (4.12-3 to 4.14-1)
  • Migration status for polymake (4.12-3 to 4.14-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: polymake normaliz (not considered)
    • Invalidated by dependency
  • Additional info:
    • Updating polymake will fix bugs in testing: #1097635
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polymake.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
• pysequoia (0.1.27-1 to 0.1.29-1)
  • Migration status for pysequoia (0.1.27-1 to 0.1.29-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 10 days old
  • Additional info:
    • Updating pysequoia will fix bugs in testing: #1114283
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysequoia.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• python-telegram-bot (22.3-2 to 22.4-1)
  • Migration status for python-telegram-bot (22.3-2 to 22.4-1): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 5 of 10 days old
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-telegram-bot.html
    • autopkgtest for python-telegram-bot/22.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• rust-aligned-vec (- to 0.6.4-1)
  • Migration status for rust-aligned-vec (- to 0.6.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-aligned-vec/0.6.4-1: amd64: Pass, arm64: Pass, i386: Failed ♻, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-aligned-vec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 5 days old (needed 5 days)
• rust-bitstream-io (2.6.0-1 to 4.6.0-1)
  • Migration status for rust-bitstream-io (2.6.0-1 to 4.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-bitstream-io-dev/4.6.0-1/amd64 to testing makes librust-rav1e-dev/0.7.1-9+b2/amd64 uninstallable
    • migrating librust-bitstream-io-dev/4.6.0-1/arm64 to testing makes librust-rav1e-dev/0.7.1-9+b2/arm64 uninstallable
    • migrating librust-bitstream-io-dev/4.6.0-1/armhf to testing makes librust-rav1e-dev/0.7.1-9+b2/armhf uninstallable
    • migrating librust-bitstream-io-dev/4.6.0-1/i386 to testing makes librust-rav1e-dev/0.7.1-9+b2/i386 uninstallable
    • migrating librust-bitstream-io-dev/4.6.0-1/ppc64el to testing makes librust-rav1e-dev/0.7.1-9+b2/ppc64el uninstallable
    • migrating librust-bitstream-io-dev/4.6.0-1/riscv64 to testing makes librust-rav1e-dev/0.7.1-9+b2/riscv64 uninstallable
    • migrating librust-bitstream-io-dev/4.6.0-1/s390x to testing makes librust-rav1e-dev/0.7.1-9+b2/s390x uninstallable
    • Implicit dependency: rust-bitstream-io rust-bitvec-helpers
    • Implicit dependency: rust-bitstream-io rust-ivf
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bitstream-io.html
    • autopkgtest for rust-bitstream-io/4.6.0-1: amd64: Pass, arm64: 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
    • 5 days old (needed 2 days)
• rust-bitvec-helpers (3.1.6-1 to 4.0.0-1)
  • Migration status for rust-bitvec-helpers (3.1.6-1 to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: rust-bitvec-helpers rust-bitstream-io (not considered)
    • Invalidated by dependency
    • Implicit dependency: rust-bitvec-helpers rust-dolby-vision
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bitvec-helpers.html
    • autopkgtest for rust-bitvec-helpers/4.0.0-1: amd64: Pass, arm64: 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
    • 5 days old (needed 2 days)
• rust-dolby-vision (3.3.1-2 to 3.3.2-1)
  • Migration status for rust-dolby-vision (3.3.1-2 to 3.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): rust-dolby-vision rust-bitvec-helpers (not considered)
    • Depends: rust-dolby-vision rust-bitvec-helpers (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-dolby-vision.html
    • autopkgtest for rust-dolby-vision/3.3.2-1: amd64: Pass, arm64: 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
    • 5 days old (needed 2 days)
• rust-nasm-rs (0.2.5-1 to 0.3.0-1)
  • Migration status for rust-nasm-rs (0.2.5-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating librust-nasm-rs-dev/0.3.0-1/amd64 to testing makes librust-rav1e-dev/0.7.1-9+b2/amd64 uninstallable
    • migrating librust-nasm-rs-dev/0.3.0-1/arm64 to testing makes librust-rav1e-dev/0.7.1-9+b2/arm64 uninstallable
    • migrating librust-nasm-rs-dev/0.3.0-1/armhf to testing makes librust-rav1e-dev/0.7.1-9+b2/armhf uninstallable
    • migrating librust-nasm-rs-dev/0.3.0-1/i386 to testing makes librust-rav1e-dev/0.7.1-9+b2/i386 uninstallable
    • migrating librust-nasm-rs-dev/0.3.0-1/ppc64el to testing makes librust-rav1e-dev/0.7.1-9+b2/ppc64el uninstallable
    • migrating librust-nasm-rs-dev/0.3.0-1/riscv64 to testing makes librust-rav1e-dev/0.7.1-9+b2/riscv64 uninstallable
    • migrating librust-nasm-rs-dev/0.3.0-1/s390x to testing makes librust-rav1e-dev/0.7.1-9+b2/s390x uninstallable
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-nasm-rs.html
    • autopkgtest for rust-nasm-rs/0.3.0-1: amd64: Pass, arm64: 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
    • 5 days old (needed 2 days)
• rust-v-frame (0.3.7-1 to 0.3.9-1)
  • Migration status for rust-v-frame (0.3.7-1 to 0.3.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-v-frame rust-aligned-vec (not considered)
    • Depends: rust-v-frame rust-aligned-vec (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-v-frame.html
    • autopkgtest for rust-rav1e/0.7.1-9: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for rust-v-frame/0.3.9-1: amd64: Pass, arm64: 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
    • 5 days old (needed 2 days)
• gbatnav (1.0.4cvs20051004-7 to 1.0.4cvs20051004-8)
  • Migration status for gbatnav (1.0.4cvs20051004-7 to 1.0.4cvs20051004-8): Waiting for test results or another package, or too young (no action required now - check later)
  • Issues preventing migration:
    • Too young, only 6 of 10 days old
  • Additional info:
    • Updating gbatnav will fix bugs in testing: #1096679
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gbatnav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
• gloo (0.0~git20231202.5354032-5 to 0.0~git20250912.d97133a-1)
  • Migration status for gloo (0.0~git20231202.5354032-5 to 0.0~git20250912.d97133a-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for gloo/0.0~git20250912.d97133a-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for pytorch/2.6.0+dfsg-8: ppc64el: Regression ♻ (reference ♻)
  • Additional info:
    • Updating gloo will fix bugs in testing: #1096726
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gloo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
• golang-github-bluebreezecf-opentsdb-goclient (0.0~git20160515.0.539764b-1.1 to 0.0~git20190921.0.7961383-1)
  • Migration status for golang-github-bluebreezecf-opentsdb-goclient (0.0~git20160515.0.539764b-1.1 to 0.0~git20190921.0.7961383-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-bluebreezecf-opentsdb-goclient/0.0~git20190921.0.7961383-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bluebreezecf-opentsdb-goclient.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
• golang-github-bsphere-le-go (0.0~git20170215.0.7a984a8-1.1 to 0.0~git20200109.0.fc06dab-1)
  • Migration status for golang-github-bsphere-le-go (0.0~git20170215.0.7a984a8-1.1 to 0.0~git20200109.0.fc06dab-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-bsphere-le-go/0.0~git20200109.0.fc06dab-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bsphere-le-go.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
• i2pd (2.56.0-1 to 2.58.0-1)
  • Migration status for i2pd (2.56.0-1 to 2.58.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: i2pd miniupnpc (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/i2pd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
• loupe (49~rc-3 to 49.0-1)
  • Migration status for loupe (49~rc-3 to 49.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: loupe rust-glycin (not considered)
    • Invalidated by built-using
    • Built-Using: loupe rust-glycin-utils
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/loupe.html
    • 6 days old (needed 5 days)
• megaglest (3.13.0-9 to 3.13.0-10)
  • Migration status for megaglest (3.13.0-9 to 3.13.0-10): 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
    • Waiting for lintian test results on i386 - info
    • Depends: megaglest miniupnpc
  • Additional info:
    • Updating megaglest will fix bugs in testing: #1063593
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/megaglest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
• mshr (2019.2.0~git20230811.ff54a68+dfsg1-4 to 2019.2.0~git20230811.ff54a68+dfsg1-5)
  • Migration status for mshr (2019.2.0~git20230811.ff54a68+dfsg1-4 to 2019.2.0~git20230811.ff54a68+dfsg1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fenics/2:0.9.0.3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for mshr/2019.2.0~git20230811.ff54a68+dfsg1-5: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mshr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• openblas (0.3.29+ds-3 to 0.3.30+ds-3)
  • Migration status for openblas (0.3.29+ds-3 to 0.3.30+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for altree/1.3.2-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for dmrgpp/6.06-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-18: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for gemma/0.98.5+dfsg-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for macaulay2/1.24.11+ds-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for openblas/0.3.30+ds-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for openmolcas/25.02-2: amd64: Pass, arm64: Pass, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for pythran/0.17.0+ds-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for r-cran-projpred/2.8.0+dfsg-1: amd64: Pass, arm64: Pass, i386: Test triggered (failure will be ignored), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for xmds2/3.1.0+dfsg2-10: amd64: Test triggered (failure will be ignored), arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for xtensor-blas/0.21.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating openblas will fix bugs in testing: #1114016
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openblas.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 6 days old (needed 5 days)
• python-ruyaml (0.91.0-5 to 0.92.1-2)
  • Migration status for python-ruyaml (0.91.0-5 to 0.92.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-ruyaml/0.92.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-yamlfix/1.17.0-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ruyaml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
• rust-futures-rustls (- to 0.26.0-5)
  • Migration status for rust-futures-rustls (- to 0.26.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-futures-rustls would introduce bugs in testing: #1115821
    • autopkgtest for rust-futures-rustls/0.26.0-5: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-futures-rustls.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
• rust-glycin (3.0.0~rc.1-2 to 3.0.0-1)
  • Migration status for rust-glycin (3.0.0~rc.1-2 to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-glycin/3.0.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-glycin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
• sdpa (- to 7.3.19-1)
  • Migration status for sdpa (- to 7.3.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • sdpa/amd64 has unsatisfiable dependency
    • sdpam/amd64 has unsatisfiable dependency
    • sdpa/arm64 has unsatisfiable dependency
    • sdpam/arm64 has unsatisfiable dependency
    • sdpa/armhf has unsatisfiable dependency
    • sdpam/armhf has unsatisfiable dependency
    • sdpa/i386 has unsatisfiable dependency
    • sdpam/i386 has unsatisfiable dependency
    • sdpa/ppc64el has unsatisfiable dependency
    • sdpam/ppc64el has unsatisfiable dependency
    • sdpa/riscv64 has unsatisfiable dependency
    • sdpam/riscv64 has unsatisfiable dependency
    • sdpa/s390x has unsatisfiable dependency
    • sdpam/s390x has unsatisfiable dependency
    • Too young, only 6 of 10 days old
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sdpa.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Remove hint for (transitive) dependency: blis
• vte2.91 (0.80.3-3 to 0.82.0-1)
  • Migration status for vte2.91 (0.80.3-3 to 0.82.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for vte2.91/0.82.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: 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 ♻
    • Waiting for lintian test results on ppc64el - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vte2.91.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
• wlcs (1.7.0-1 to 1.8.1-1)
  • Migration status for wlcs (1.7.0-1 to 1.8.1-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • missing build on s390x
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results on i386, s390x - info
  • Additional info:
    • Updating wlcs will fix bugs in testing: #1114441
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wlcs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 6 days old (needed 5 days)
• aspell-el (0.50-3-8 to 0.50-3-9)
  • Migration status for aspell-el (0.50-3-8 to 0.50-3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/a/aspell-el.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 7 days old (needed 5 days)
• golang-bugst-testifyjson (- to 1.3.0-1)
  • Migration status for golang-bugst-testifyjson (- to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-bugst-testifyjson/1.3.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-bugst-testifyjson.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 7 days old (needed 5 days)
• golang-github-asaskevich-eventbus (- to 0.0~git20200907.49d4230-1)
  • Migration status for golang-github-asaskevich-eventbus (- to 0.0~git20200907.49d4230-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-asaskevich-eventbus/0.0~git20200907.49d4230-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-asaskevich-eventbus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 7 days old (needed 5 days)
• golang-github-containerd-otelttrpc (- to 0.1.0-1)
  • Migration status for golang-github-containerd-otelttrpc (- to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-containerd-otelttrpc/0.1.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-containerd-otelttrpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 7 days old (needed 5 days)
• golang-k8s-sigs-knftables (- to 0.0.18+ds1-1)
  • Migration status for golang-k8s-sigs-knftables (- to 0.0.18+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-k8s-sigs-knftables/0.0.18+ds1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-sigs-knftables.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 7 days old (needed 5 days)
• kf6-kfilemetadata (6.13.0-2 to 6.13.0-3)
  • Migration status for kf6-kfilemetadata (6.13.0-2 to 6.13.0-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
    • autopkgtest for kf6-kfilemetadata/6.13.0-3: amd64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results on arm64 - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kf6-kfilemetadata.html
    • Reproducible on amd64 - info ♻
    • 7 days old (needed 5 days)
• kfilemetadata-kf5 (5.116.0-2 to 5.116.0-3)
  • Migration status for kfilemetadata-kf5 (5.116.0-2 to 5.116.0-3): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
    • autopkgtest for kfilemetadata-kf5/5.116.0-3: amd64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results on arm64 - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kfilemetadata-kf5.html
    • Reproducible on amd64 - info ♻
    • 7 days old (needed 5 days)
• rust-rdftk (- to 0.1.0+20241125-4)
  • Migration status for rust-rdftk (- to 0.1.0+20241125-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-rdftk would introduce bugs in testing: #1115237
    • autopkgtest for rust-rdftk/0.1.0+20241125-4: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rdftk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 7 days old (needed 5 days)
• dolfinx-mpc (0.9.1-2 to 0.9.3-2)
  • Migration status for dolfinx-mpc (0.9.1-2 to 0.9.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dolfinx-mpc/0.9.3-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Updating dolfinx-mpc will fix bugs in testing: #1096535
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dolfinx-mpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 8 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• ecflow (5.14.1-2 to 5.15.0-1)
  • Migration status for ecflow (5.14.1-2 to 5.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ecflow would introduce bugs in testing: #1096561
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/ecflow.html
    • autopkgtest for ecflow/5.15.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 8 days old (needed 2 days)
• gcc-11-cross (- to 24)
  • Migration status for gcc-11-cross (- 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-11-cross gcc-11 (not considered)
    • Built-Using: gcc-11-cross gcc-11 (not considered)
    • Depends: gcc-11-cross gcc-11 (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11-cross.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 8 days old (needed 5 days)
• kexec-tools (1:2.0.29-2 to 1:2.0.31-1)
  • Migration status for kexec-tools (1:2.0.29-2 to 1:2.0.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kexec-tools unsatisfiable Build-Depends(-Arch) on armhf: libxen-dev [amd64 arm64 armhf]
    • missing build on armhf
    • Waiting for lintian test results on armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kexec-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 8 days old (needed 5 days)
• llvm-toolchain-19 (1:19.1.7-3 to 1:19.1.7-6)
  • Migration status for llvm-toolchain-19 (1:19.1.7-3 to 1:19.1.7-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating llvm-toolchain-19 would introduce bugs in testing: #1115194
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-18: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for fenics-dolfinx/1:0.9.0-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for llvm-toolchain-19/1:19.1.7-6: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for pythran/0.17.0+ds-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for ycmd/0+20240823+git8b61f19+ds-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating llvm-toolchain-19 will fix bugs in testing: #1113935
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llvm-toolchain-19.html
    • Reproducible on amd64 - info ♻
    • 8 days old (needed 5 days)
• lua-system (0.5.1-1 to 0.6.3-1)
  • Migration status for lua-system (0.5.1-1 to 0.6.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
    • autopkgtest for lua-system/0.6.3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Waiting for lintian test results on s390x - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lua-system.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 8 days old (needed 5 days)
• openseachest (24.08.1-1 to 25.05.2-1)
  • Migration status for openseachest (24.08.1-1 to 25.05.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on i386 - info
  • Additional info:
    • Updating openseachest will fix bugs in testing: #1097521
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openseachest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 8 days old (needed 5 days)
• performous (1.3.0+ds-2 to 1.3.1+ds-1)
  • Migration status for performous (1.3.0+ds-2 to 1.3.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/performous.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 8 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• rust-swaysome (2.1.2-1 to 2.3.1-1)
  • Migration status for rust-swaysome (2.1.2-1 to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-swaysome/2.3.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-swaysome.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 8 days old (needed 5 days)
• scifem (0.6.0-2 to 0.6.0-3)
  • Migration status for scifem (0.6.0-2 to 0.6.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for scifem/0.6.0-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scifem.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 8 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• shotcut (25.03.29+ds-1 to 25.08.16+ds-1)
  • Migration status for shotcut (25.03.29+ds-1 to 25.08.16+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el - info
    • Depends: shotcut mlt (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shotcut.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • 8 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• valentina (- to 1.0.0~dfsg-2)
  • Migration status for valentina (- to 1.0.0~dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating valentina would introduce bugs in testing: #1087710
    • autopkgtest for valentina/1.0.0~dfsg-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, s390x: Failed ♻
    • missing build on riscv64
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on riscv64 - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/valentina.html
    • 8 days old (needed 5 days)
• verilator (5.038-1 to 5.040-2)
  • Migration status for verilator (5.038-1 to 5.040-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • verilator unsatisfiable Build-Depends(-Arch) on armhf: architecture-is-64-bit
    • verilator unsatisfiable Build-Depends(-Arch) on i386: architecture-is-64-bit
    • missing build on armhf
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for verilator/5.040-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results on i386, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/verilator.html
    • Reproducible on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • 8 days old (needed 5 days)
• dolfin (2019.2.0~legacy20240219.1c52e83-18 to 2019.2.0~legacy20240219.1c52e83-21)
  • Migration status for dolfin (2019.2.0~legacy20240219.1c52e83-18 to 2019.2.0~legacy20240219.1c52e83-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-21: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for fenics/2:0.9.0.3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for mshr/2019.2.0~git20230811.ff54a68+dfsg1-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dolfin.html
    • Reproducible on amd64 - info ♻
    • 9 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• fenics-basix (0.9.0-2 to 0.9.0-3)
  • Migration status for fenics-basix (0.9.0-2 to 0.9.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fenics-basix/0.9.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for fenics-dolfinx/1:0.9.0-7: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Regression ♻ (reference ♻)
    • autopkgtest for scifem/0.6.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fenics-basix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 9 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• fenics-dolfinx (1:0.9.0-7 to 1:0.9.0-8)
  • Migration status for fenics-dolfinx (1:0.9.0-7 to 1:0.9.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for adios4dolfinx/0.9.3-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Pass
    • autopkgtest for dolfinx-mpc/0.9.1-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for fenics-dolfinx/1:0.9.0-8: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Regression ♻ (reference ♻)
    • autopkgtest for ngspetsc/0.1.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for scifem/0.6.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Updating fenics-dolfinx will fix bugs in testing: #1096624
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fenics-dolfinx.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • 9 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• gcc-11 (- to 11.5.0-7)
  • Migration status for gcc-11 (- to 11.5.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-11 would introduce bugs in testing: #1023690
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11.html
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-18: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for fenics-dolfinx/1:0.9.0-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for gcc-11/11.5.0-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for pythran/0.17.0+ds-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• golang-github-charlievieth-fastwalk (1.0.9-1 to 1.0.14-1)
  • Migration status for golang-github-charlievieth-fastwalk (1.0.9-1 to 1.0.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-charlievieth-fastwalk/1.0.14-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-charlievieth-fastwalk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 9 days old (needed 5 days)
• golang-k8s-utils (0.0~git20250321.1f6e0b7-1 to 0.0~git20250820.0af2bda-1)
  • Migration status for golang-k8s-utils (0.0~git20250321.1f6e0b7-1 to 0.0~git20250820.0af2bda-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-k8s-utils/0.0~git20250820.0af2bda-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻), s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-utils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 9 days old (needed 5 days)
• mlt (7.30.0-1 to 7.32.0-1)
  • Migration status for mlt (7.30.0-1 to 7.32.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlt.html
    • Reproducible on amd64 - info ♻
    • 9 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• picotool (2.1.1+dfsg-1 to 2.2.0-a4+dfsg-2)
  • Migration status for picotool (2.1.1+dfsg-1 to 2.2.0-a4+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for picotool/2.2.0-a4+dfsg-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/picotool.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 9 days old (needed 5 days)
• rocm-docs-core (- to 1.23.0-5)
  • Migration status for rocm-docs-core (- to 1.23.0-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rocm-docs-core doxysphinx (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rocm-docs-core.html
    • autopkgtest for rocm-docs-core/1.23.0-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 9 days old (needed 2 days)
• vcfanno (0.3.5+ds-2 to 0.3.5+ds-3)
  • Migration status for vcfanno (0.3.5+ds-2 to 0.3.5+ds-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 vcfanno/0.3.5+ds-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results on riscv64 - info
    • Built-Using: vcfanno golang-1.24 (not considered)
  • Additional info:
    • Updating vcfanno will fix bugs in testing: #1114433
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vcfanno.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 9 days old (needed 5 days)
• glow (2.0.0-1 to 2.1.1-1)
  • Migration status for glow (2.0.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
    • autopkgtest for glow/2.1.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results on riscv64 - info
    • Built-Using: glow golang-1.24 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glow.html
    • Reproducibility regression on amd64 - info ♻
    • Reproducibility regression on arm64 - info ♻
    • 10 days old (needed 5 days)
• libkeduvocdocument (4:25.04.0-1 to 4:25.08.0-1)
  • Migration status for libkeduvocdocument (4:25.04.0-1 to 4:25.08.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on arm64
    • arch:arm64 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on arm64 - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libk/libkeduvocdocument.html
    • Reproducible on amd64 - info ♻
    • 10 days old (needed 5 days)
• rust-apt-swarm (- to 0.5.1-5)
  • Migration status for rust-apt-swarm (- to 0.5.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-apt-swarm would introduce bugs in testing: #1101874
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-apt-swarm.html
    • autopkgtest for rust-apt-swarm/0.5.1-5: amd64: Pass, arm64: 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
    • 10 days old (needed 2 days)
• bpftune (0.0~git20250314.8fd59cc-1 to 0.0~git20250723.5966387-1)
  • Migration status for bpftune (0.0~git20250314.8fd59cc-1 to 0.0~git20250723.5966387-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
    • Waiting for lintian test results on i386 - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bpftune.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 11 days old (needed 5 days)
• btas (1.0.0-1 to 1.0.0-1.1)
  • Migration status for btas (1.0.0-1 to 1.0.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • missing build on arm64
    • missing build on ppc64el
    • missing build on riscv64
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el, arm64, riscv64 - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/btas.html
    • Reproducible on amd64 - info ♻
    • 11 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• iaito (- to 6.0.0+ds-1)
  • Migration status for iaito (- to 6.0.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): iaito radare2 (not considered)
    • Depends: iaito radare2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iaito.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 11 days old (needed 5 days)
• kew (3.2.0+ds-1 to 3.4.1+ds-1)
  • Migration status for kew (3.2.0+ds-1 to 3.4.1+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: kew chafa (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kew.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 11 days old (needed 5 days)
• lfortran (0.45.0-1 to 0.48.0-2)
  • Migration status for lfortran (0.45.0-1 to 0.48.0-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for lfortran/0.48.0-2: amd64: Pass, arm64: Pass, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • Waiting for lintian test results on ppc64el, i386, armhf - info
  • Additional info:
    • Updating lfortran will fix bugs in testing: #1114167
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lfortran.html
    • Reproducible on amd64 - info ♻
    • 11 days old (needed 5 days)
• mrpt (1:2.14.7+ds-1 to 1:2.14.7+ds-2)
  • Migration status for mrpt (1:2.14.7+ds-1 to 1:2.14.7+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mrpt would introduce bugs in testing: #1115155
    • missing build on amd64
    • missing build on ppc64el
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on ppc64el, all, amd64 - info
    • Depends: mrpt ros-ros-comm (not considered)
  • Additional info:
    • Updating mrpt will fix bugs in testing: #1114214
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mrpt.html
    • Reproducible on arm64 - info ♻
    • 11 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• nautilus-python (4.0.1-2 to 4.0.1-3)
  • Migration status for nautilus-python (4.0.1-2 to 4.0.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
  • Issues preventing migration:
    • Depends: nautilus-python nautilus (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus-python.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 11 days old (needed 5 days)
• setools (4.5.1-1.1 to 4.6.0-1)
  • Migration status for setools (4.5.1-1.1 to 4.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating setools would introduce bugs in testing: #1115783
    • setools unsatisfiable Build-Depends(-Arch) on amd64: python3-pdm-pep517
    • setools unsatisfiable Build-Depends(-Arch) on arm64: python3-pdm-pep517
    • setools unsatisfiable Build-Depends(-Arch) on armhf: python3-pdm-pep517
    • setools unsatisfiable Build-Depends(-Arch) on i386: python3-pdm-pep517
    • setools unsatisfiable Build-Depends(-Arch) on ppc64el: python3-pdm-pep517
    • setools unsatisfiable Build-Depends(-Arch) on riscv64: python3-pdm-pep517
    • setools unsatisfiable Build-Depends(-Arch) on s390x: python3-pdm-pep517
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • 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: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
    • Waiting for lintian test results on ppc64el, amd64, arm64, i386, s390x, riscv64, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/setools.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 11 days old (needed 5 days)
• wapiti (- to 3.2.5+dfsg-1)
  • Migration status for wapiti (- to 3.2.5+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wapiti would introduce bugs in testing: #1108450, #1110241
    • Depends: wapiti mitmproxy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wapiti.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 11 days old (needed 5 days)
• chasquid (1.15.0-1 to 1.16.0-1)
  • Migration status for chasquid (1.15.0-1 to 1.16.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: chasquid golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chasquid.html
    • autopkgtest for chasquid/1.16.0-1: amd64: Pass, arm64: 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
    • 12 days old (needed 2 days)
• frei0r (2.3.3-1 to 2.4.0-1)
  • Migration status for frei0r (2.3.3-1 to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for frei0r/2.4.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: 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 ♻
    • Waiting for lintian test results on ppc64el - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frei0r.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 12 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• gocryptfs (2.5.1-2 to 2.6.1-1)
  • Migration status for gocryptfs (2.5.1-2 to 2.6.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 gocryptfs/2.6.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Waiting for lintian test results on riscv64 - info
    • Built-Using: gocryptfs golang-1.24 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gocryptfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 12 days old (needed 5 days)
• golang-github-tinylib-msgp (1.2.5-1 to 1.4.0-1)
  • Migration status for golang-github-tinylib-msgp (1.2.5-1 to 1.4.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for golang-github-tinylib-msgp/1.4.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results on i386, armhf - info
    • Built-Using: golang-github-tinylib-msgp golang-1.24 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-tinylib-msgp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 12 days old (needed 5 days)
• node-nodemailer (7.0.5+~7.0.1-1 to 7.0.6+~7.0.1-1)
  • Migration status for node-nodemailer (7.0.5+~7.0.1-1 to 7.0.6+~7.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-nodemailer/7.0.6+~7.0.1-1: amd64: Pass, arm64: Pass, i386: Regression ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-nodemailer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 12 days old (needed 5 days)
• python-ewokscore (0.15.0-3 to 2.0.0-1)
  • Migration status for python-ewokscore (0.15.0-3 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for python-ewokscore/2.0.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-ewoksppf/1.2.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ewokscore.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 12 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• python-ewoksdask (0.2.0-4 to 2.0.0-1)
  • Migration status for python-ewoksdask (0.2.0-4 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): python-ewoksdask python-ewokscore (not considered)
    • Depends: python-ewoksdask python-ewokscore (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ewoksdask.html
    • autopkgtest for python-ewoksdask/2.0.0-1: amd64: Pass, arm64: 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
    • 12 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• swayosd (0.1.0-5 to 0.1.0-6)
  • Migration status for swayosd (0.1.0-5 to 0.1.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating swayosd would introduce bugs in testing: #1114997
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/swayosd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 12 days old (needed 5 days)
• esstra (- to 0.3.0-3)
  • Migration status for esstra (- to 0.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • esstra/amd64 has unsatisfiable dependency
    • esstra/arm64 has unsatisfiable dependency
    • esstra/armhf has unsatisfiable dependency
    • esstra/i386 has unsatisfiable dependency
    • esstra/ppc64el has unsatisfiable dependency
    • esstra/riscv64 has unsatisfiable dependency
    • esstra/s390x has unsatisfiable dependency
    • Updating esstra would introduce bugs in testing: #1114872
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/esstra.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 13 days old (needed 5 days)
• govarnam (1.9.0-2 to 1.9.1-1)
  • Migration status for govarnam (1.9.0-2 to 1.9.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: govarnam golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Updating govarnam will fix bugs in testing: #1096754
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/govarnam.html
    • autopkgtest for govarnam/1.9.1-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 ♻
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • 13 days old (needed 5 days)
• lomiri-teleports-app (- to 1.21-1)
  • Migration status for lomiri-teleports-app (- to 1.21-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lomiri-teleports-app rlottie (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): lomiri-teleports-app rlottie-qml
    • Depends: lomiri-teleports-app rlottie-qml
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lomiri-teleports-app.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 13 days old (needed 5 days)
• mlterm (3.9.3-3.1 to 3.9.4-2)
  • Migration status for mlterm (3.9.3-3.1 to 3.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): mlterm freewnn (not considered)
    • Depends: mlterm freewnn (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlterm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 13 days old (needed 5 days)
• etoys (- to 5.0.2408-2)
  • Migration status for etoys (- to 5.0.2408-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: etoys squeak-vm (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 14 days old (needed 5 days)
    • Remove hint for (transitive) dependency: libast, netkit-telnet-ssl
• golang-github-bep-gitmap (1.6.0-1 to 1.9.0-1)
  • Migration status for golang-github-bep-gitmap (1.6.0-1 to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-bep-gitmap would introduce bugs in testing: #1114629
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-bep-gitmap.html
    • autopkgtest for golang-github-bep-gitmap/1.9.0-1: amd64: Pass, arm64: 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
    • 14 days old (needed 2 days)
• opencl-clang-14 (- to 14.0.2-3)
  • Migration status for opencl-clang-14 (- to 14.0.2-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): 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 ♻
    • 14 days old (needed 5 days)
• pocl (6.0-6 to 6.0-7)
  • Migration status for pocl (6.0-6 to 6.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pocl/6.0-7: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • autopkgtest for ufo-filters/0.17.0.76.g691aa0e+dfsg1-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻)
  • Additional info:
    • Updating pocl will fix bugs in testing: #1097627
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pocl.html
    • Reproducible on arm64 - info ♻
    • 14 days old (needed 5 days)
• silx (2.2.1+dfsg-3 to 2.2.1+dfsg-4)
  • Migration status for silx (2.2.1+dfsg-3 to 2.2.1+dfsg-4): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on s390x, ppc64el, all, arm64, amd64, i386, riscv64, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/silx.html
    • 14 days old (needed 5 days)
• paramiko (3.5.1-3 to 4.0.0-1)
  • Migration status for paramiko (3.5.1-3 to 4.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for ansible-core/2.19.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for dask.distributed/2024.12.1+ds-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for libcloud/3.8.0+repack-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for paramiko/4.0.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for ros-ros-comm/1.17.0+ds-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paramiko.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 15 days old (needed 10 days)
• python-markdown (3.7-2 to 3.9-1)
  • Migration status for python-markdown (3.7-2 to 3.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: python-markdown node-jquery (not considered)
    • Invalidated by dependency
  • Additional info:
    • Updating python-markdown will fix bugs in testing: #1112111
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-markdown.html
    • autopkgtest for python-markdown/3.9-1: amd64: Pass, arm64: 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
    • 15 days old (needed 2 days)
• sbcl (2:2.5.2-1 to 2:2.5.8-1)
  • Migration status for sbcl (2:2.5.2-1 to 2:2.5.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for buildapp/1.5.6-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻)
    • autopkgtest for cl-ironclad/0.61-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
    • autopkgtest for cl-postmodern/20211113.git9d4332f-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 ♻ (reference ♻), riscv64: Test triggered (failure will be ignored)
    • autopkgtest for sbcl/2:2.5.8-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sbcl.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • 15 days old (needed 5 days)
• spirv-llvm-translator-14 (- to 14.0.15-2)
  • Migration status for spirv-llvm-translator-14 (- to 14.0.15-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.15-2: amd64: Pass, 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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 15 days old (needed 5 days)
• xmpp-dns (0.5.1-1 to 0.5.2-1)
  • Migration status for xmpp-dns (0.5.1-1 to 0.5.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: xmpp-dns golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xmpp-dns.html
    • autopkgtest for xmpp-dns/0.5.2-1: amd64: Pass, arm64: 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
    • 15 days old (needed 2 days)
• apptainer (1.4.0-7 to 1.4.2-1)
  • Migration status for apptainer (1.4.0-7 to 1.4.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: apptainer golang-1.24 (not considered)
    • Invalidated by built-using
    • Built-Using: apptainer rekor
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apptainer.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • 16 days old (needed 5 days)
• libcsaf-perl (- to 0.26-1)
  • Migration status for libcsaf-perl (- to 0.26-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: libcsaf-perl liburi-packageurl-perl (not considered)
    • Depends: libcsaf-perl liburi-packageurl-perl (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
    • Build-Depends-Indep: libcsaf-perl libcvss-perl (not considered)
    • Depends: libcsaf-perl libcvss-perl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libc/libcsaf-perl.html
    • autopkgtest for libcsaf-perl/0.26-1: amd64: Pass, arm64: 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
    • 16 days old (needed 2 days)
• llhttp (- to 9.3.3~really9.3.0+~cs12.11.8-3)
  • Migration status for llhttp (- to 9.3.3~really9.3.0+~cs12.11.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-undici/7.15.0+dfsg+~cs3.2.0-1: amd64: Pass, arm64: Pass, i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/llhttp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 16 days old (needed 5 days)
• loki-ecmwf (0.3.1-1 to 0.3.4-1)
  • Migration status for loki-ecmwf (0.3.1-1 to 0.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/l/loki-ecmwf.html
  • Additional info:
    • Updating loki-ecmwf will fix bugs in testing: #1115187
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 16 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• python-jpype (1.5.0-1 to 1.6.0-1)
  • Migration status for python-jpype (1.5.0-1 to 1.6.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for python-jpype/1.6.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results on i386, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-jpype.html
    • 16 days old (needed 5 days)
• le-dico-de-rene-cougnenc (1.4-1 to 1.4-3)
  • Migration status for le-dico-de-rene-cougnenc (1.4-1 to 1.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating le-dico-de-rene-cougnenc would introduce bugs in testing: #1113893
    • missing build on arm64
    • missing build on armhf
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results on s390x, ppc64el, arm64, riscv64, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/le-dico-de-rene-cougnenc.html
    • Reproducible on amd64 - info ♻
    • 17 days old (needed 5 days)
• rust-ttrpc (- to 0.8.2-2)
  • Migration status for rust-ttrpc (- to 0.8.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-ttrpc rust-protobuf (not considered)
    • Depends: rust-ttrpc rust-protobuf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-ttrpc rust-protobuf-codegen-pure
    • Depends: rust-ttrpc rust-protobuf-codegen-pure
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ttrpc.html
    • autopkgtest for rust-ttrpc/0.8.2-2: amd64: Pass, arm64: 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
    • 17 days old (needed 2 days)
• golang-github-canonical-go-dqlite (2.0.0-1 to 2.0.1-1)
  • Migration status for golang-github-canonical-go-dqlite (2.0.0-1 to 2.0.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: golang-github-canonical-go-dqlite golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-canonical-go-dqlite.html
    • autopkgtest for golang-github-canonical-go-dqlite/2.0.1-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 18 days old (needed 5 days)
• golang-k8s-cli-runtime (0.32.3-1 to 0.33.4-1)
  • Migration status for golang-k8s-cli-runtime (0.32.3-1 to 0.33.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-k8s-cli-runtime golang-k8s-client-go (not considered)
    • Depends: golang-k8s-cli-runtime golang-k8s-client-go (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-cli-runtime.html
    • autopkgtest for golang-k8s-cli-runtime/0.33.4-1: amd64: Pass, arm64: 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
    • 18 days old (needed 2 days)
• golang-k8s-client-go (0.32.3-2 to 0.33.4-1)
  • Migration status for golang-k8s-client-go (0.32.3-2 to 0.33.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-k8s-client-go would introduce bugs in testing: #1113806
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-client-go.html
    • autopkgtest for golang-k8s-client-go/0.33.4-1: amd64: Pass, arm64: 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
    • 18 days old (needed 2 days)
• golang-k8s-component-base (0.32.3-1 to 0.33.4-1)
  • Migration status for golang-k8s-component-base (0.32.3-1 to 0.33.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-k8s-component-base would introduce bugs in testing: #1113982
    • Build-Depends(-Arch): golang-k8s-component-base golang-k8s-client-go (not considered)
    • Depends: golang-k8s-component-base golang-k8s-client-go (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-component-base.html
    • autopkgtest for golang-k8s-component-base/0.33.4-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 18 days old (needed 2 days)
• golang-k8s-component-helpers (0.32.3-1 to 0.33.4-1)
  • Migration status for golang-k8s-component-helpers (0.32.3-1 to 0.33.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-k8s-component-helpers golang-k8s-client-go (not considered)
    • Depends: golang-k8s-component-helpers golang-k8s-client-go (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-component-helpers.html
    • autopkgtest for golang-k8s-component-helpers/0.33.4-1: amd64: Pass, arm64: 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
    • 18 days old (needed 2 days)
• golang-k8s-metrics (0.32.3-1 to 0.33.4-1)
  • Migration status for golang-k8s-metrics (0.32.3-1 to 0.33.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-k8s-metrics golang-k8s-client-go (not considered)
    • Depends: golang-k8s-metrics golang-k8s-client-go (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-k8s-metrics.html
    • autopkgtest for golang-k8s-metrics/0.33.4-1: amd64: Pass, arm64: 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
    • 18 days old (needed 2 days)
• gvmd (- to 26.2.1-1)
  • Migration status for gvmd (- to 26.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): 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/26.2.1-1: amd64: Pass, arm64: 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
    • 18 days old (needed 2 days)
• hurd (- to 1:0.9.git20250801-4)
  • Migration status for hurd (- to 1:0.9.git20250801-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hurd would introduce bugs in testing: #838244
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libc0.3-dev (>= 2.33-2~1)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-disk-dev (>= 0~20211031-2)
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-if-dev
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpnet-dev
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: librumpdev-usb-dev
    • hurd unsatisfiable Build-Depends(-Arch) on amd64: libacpica-dev
    • Not touching package due to block request by freeze (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hurd.html
    • 18 days old (needed 5 days)
• kubernetes (1.32.3+ds-2 to 1.33.4+ds-1)
  • Migration status for kubernetes (1.32.3+ds-2 to 1.33.4+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): kubernetes golang-k8s-component-base (not considered)
    • Depends: kubernetes golang-k8s-component-base (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): kubernetes golang-k8s-cli-runtime
    • Build-Depends(-Arch): kubernetes golang-k8s-client-go (not considered)
    • Build-Depends(-Arch): kubernetes golang-k8s-component-helpers
    • Build-Depends(-Arch): kubernetes golang-k8s-metrics
    • Depends: kubernetes golang-k8s-cli-runtime
    • Depends: kubernetes golang-k8s-client-go (not considered)
    • Depends: kubernetes golang-k8s-component-helpers
    • Depends: kubernetes golang-k8s-metrics
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kubernetes.html
    • autopkgtest for kubernetes/1.33.4+ds-1: amd64: Pass, 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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 18 days old (needed 5 days)
• localsearch (- to 3.8.2-7)
  • Migration status for localsearch (- to 3.8.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating localsearch would introduce bugs in testing: #1113704
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/localsearch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 18 days old (needed 5 days)
• orthanc-gdcm (1.8+dfsg-1 to 1.8+dfsg-2)
  • Migration status for orthanc-gdcm (1.8+dfsg-1 to 1.8+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: orthanc-gdcm orthanc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-gdcm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 18 days old (needed 5 days)
• orthanc-mysql (5.0+dfsg-1 to 5.0+dfsg-3)
  • Migration status for orthanc-mysql (5.0+dfsg-1 to 5.0+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: orthanc-mysql orthanc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-mysql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 18 days old (needed 5 days)
• orthanc-neuro (1.1+dfsg-1 to 1.1+dfsg-2)
  • Migration status for orthanc-neuro (1.1+dfsg-1 to 1.1+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: orthanc-neuro orthanc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-neuro.html
    • autopkgtest for orthanc-neuro/1.1+dfsg-2: amd64: Pass, arm64: 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
    • 18 days old (needed 2 days)
• orthanc-postgresql (5.0+dfsg-3 to 5.0+dfsg-5)
  • Migration status for orthanc-postgresql (5.0+dfsg-3 to 5.0+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: orthanc-postgresql orthanc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-postgresql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 18 days old (needed 5 days)
• orthanc-python (5.0+ds-3 to 6.0+ds-2)
  • Migration status for orthanc-python (5.0+ds-3 to 6.0+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): orthanc-python orthanc (not considered)
    • Built-Using: orthanc-python orthanc (not considered)
    • Depends: orthanc-python orthanc (not considered)
    • Invalidated by build-dependency
    • Invalidated by built-using
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-python.html
    • autopkgtest for orthanc-python/6.0+ds-2: amd64: Pass, arm64: 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
    • 18 days old (needed 2 days)
• orthanc-webviewer (2.10+dfsg-1 to 2.10+dfsg-2)
  • Migration status for orthanc-webviewer (2.10+dfsg-1 to 2.10+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: orthanc-webviewer orthanc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-webviewer.html
    • autopkgtest for orthanc-webviewer/2.10+dfsg-2: amd64: Pass, arm64: 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
    • 18 days old (needed 2 days)
• pcp (6.3.8-1 to 7.0.0-1)
  • Migration status for pcp (6.3.8-1 to 7.0.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pcp.html
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • 18 days old (needed 10 days)
• r-cran-v8 (6.0.2+dfsg-1 to 7.0.0+dfsg-1)
  • Migration status for r-cran-v8 (6.0.2+dfsg-1 to 7.0.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: r-cran-v8 nodejs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-v8.html
    • autopkgtest for r-cran-v8/7.0.0+dfsg-1: amd64: Pass, arm64: 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
    • 18 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• rust-tower-lsp (- to 0.20.0-1)
  • Migration status for rust-tower-lsp (- to 0.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-tower-lsp-dev/amd64 has unsatisfiable dependency
    • librust-tower-lsp-dev/arm64 has unsatisfiable dependency
    • librust-tower-lsp-dev/armhf has unsatisfiable dependency
    • librust-tower-lsp-dev/i386 has unsatisfiable dependency
    • librust-tower-lsp-dev/ppc64el has unsatisfiable dependency
    • librust-tower-lsp-dev/riscv64 has unsatisfiable dependency
    • librust-tower-lsp-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-tower-lsp.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 18 days old (needed 5 days)
• translate-toolkit (3.15.1-1 to 3.15.6-1)
  • Migration status for translate-toolkit (3.15.1-1 to 3.15.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for translate-toolkit/3.15.6-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/translate-toolkit.html
    • 18 days old (needed 5 days)
• umap-learn (- to 0.5.9.post2+dfsg-1)
  • Migration status for umap-learn (- to 0.5.9.post2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umap-learn would introduce bugs in testing: #1071816
    • autopkgtest for umap-learn/0.5.9.post2+dfsg-1: amd64: Failed ♻, arm64: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umap-learn.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 18 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• meli (0.8.11+dfsg-1 to 0.8.12+dfsg-2)
  • Migration status for meli (0.8.11+dfsg-1 to 0.8.12+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating meli would introduce bugs in testing: #1114202
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/meli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 19 days old (needed 5 days)
• openjdk-11 (- to 11.0.29~4ea-2)
  • Migration status for openjdk-11 (- to 11.0.29~4ea-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-11 would introduce bugs in testing: #1023237, #1071118
    • missing build on armhf
    • missing build on i386
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for bbmap/39.20+dfsg-2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for openjdk-11/11.0.29~4ea-2: 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 ♻
    • Waiting for lintian test results on i386, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openjdk-11.html
    • Reproducible on amd64 - info ♻
    • 19 days old (needed 5 days)
• napari (- to 0.6.4-2)
  • Migration status for napari (- to 0.6.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating napari would introduce bugs in testing: #1112605
    • autopkgtest for napari/0.6.4-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
    • Build-Depends(-Arch): napari napari-console (not considered)
    • Build-Depends(-Arch): napari napari-plugin-manager (not considered)
    • Build-Depends(-Arch): napari napari-svg (not considered)
    • Depends: napari napari-console (not considered)
    • Depends: napari napari-svg (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari.html
    • Reproducible on amd64 - info ♻
    • 20 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• asterisk (- to 1:22.5.2~dfsg+~cs6.15.60671435-1)
  • Migration status for asterisk (- to 1:22.5.2~dfsg+~cs6.15.60671435-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating asterisk would introduce bugs in testing: #1031046
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/asterisk.html
    • autopkgtest for asterisk/1:22.5.2~dfsg+~cs6.15.60671435-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 21 days old (needed 2 days)
• golang-github-lucas-clemente-quic-go (0.50.1-2 to 0.54.0-3)
  • Migration status for golang-github-lucas-clemente-quic-go (0.50.1-2 to 0.54.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-lucas-clemente-quic-go would introduce bugs in testing: #1113981
    • autopkgtest for golang-github-lucas-clemente-quic-go/0.54.0-3: amd64: Pass, arm64: Pass, i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • autopkgtest for golang-v2ray-core/4.34.0+ds-5: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for syncthing/1.29.5~ds1-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-lucas-clemente-quic-go.html
    • Reproducible on arm64 - info ♻
    • 21 days old (needed 5 days)
• golang-pault-go-ykpiv (1.3.4-2 to 1.5.0-1)
  • Migration status for golang-pault-go-ykpiv (1.3.4-2 to 1.5.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: golang-pault-go-ykpiv golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-pault-go-ykpiv.html
    • autopkgtest for golang-pault-go-ykpiv/1.5.0-1: amd64: Pass, arm64: 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
    • 21 days old (needed 2 days)
• huggingface-hub (- to 0.31.1-2)
  • Migration status for huggingface-hub (- to 0.31.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for huggingface-hub/0.31.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/huggingface-hub.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 21 days old (needed 5 days)
• interegular (- to 0.3.3-2)
  • Migration status for interegular (- to 0.3.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for interegular/0.3.3-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/interegular.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 21 days old (needed 5 days)
• libgig (4.4.1-1 to 4.5.0-1)
  • Migration status for libgig (4.4.1-1 to 4.5.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results on s390x - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 21 days old (needed 5 days)
• nftables (1.1.3-1 to 1.1.5-1)
  • Migration status for nftables (1.1.3-1 to 1.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for firewalld/2.3.1-2: amd64: Regression ♻ (reference ♻), 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 ♻
    • autopkgtest for nftables/1.1.5-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nftables.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 21 days old (needed 5 days)
• node-proxy-agents (0~2024040606-6 to 0~2025070717-2)
  • Migration status for node-proxy-agents (0~2024040606-6 to 0~2025070717-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): node-proxy-agents nodejs (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-proxy-agents.html
    • autopkgtest for node-proxy-agents/0~2025070717-2: amd64: Pass, arm64: Pass, 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 ♻)
    • 21 days old (needed 5 days)
• node-undici (7.3.0+dfsg1+~cs24.12.11-2 to 7.15.0+dfsg+~cs3.2.0-1)
  • Migration status for node-undici (7.3.0+dfsg1+~cs24.12.11-2 to 7.15.0+dfsg+~cs3.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-undici/7.15.0+dfsg+~cs3.2.0-1: amd64: Pass, arm64: Pass, i386: Regression ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for nodejs/20.19.2+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • Build-Depends(-Arch): node-undici llhttp (not considered)
    • Depends: node-undici llhttp (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-undici.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 21 days old (needed 5 days)
• openjdk-17 (- to 17.0.17~5ea-1)
  • Migration status for openjdk-17 (- to 17.0.17~5ea-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-17 would introduce bugs in testing: #1102113
    • 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/o/openjdk-17.html
    • autopkgtest for bbmap/39.20+dfsg-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Pass, i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for openjdk-17/17.0.17~5ea-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • 21 days old (needed 5 days)
• php-di (7.0.10-1 to 7.1.1-1)
  • Migration status for php-di (7.0.10-1 to 7.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for matomo/5.3.1+dfsg-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for php-di/7.1.1-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/php-di.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 21 days old (needed 5 days)
• ratt (0.0~git20250812.e11cf12-1 to 0.0~git20250829.39528ce-1)
  • Migration status for ratt (0.0~git20250812.e11cf12-1 to 0.0~git20250829.39528ce-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: ratt golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ratt.html
    • autopkgtest for ratt/0.0~git20250829.39528ce-1: amd64: Pass, arm64: 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
    • 21 days old (needed 2 days)
• flask (3.1.1-1 to 3.1.2-1)
  • Migration status for flask (3.1.1-1 to 3.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for flask/3.1.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for pagure/5.14.1+dfsg-7: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/flask.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 22 days old (needed 5 days)
• godot3 (- to 3.6+ds-3)
  • Migration status for godot3 (- to 3.6+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating godot3 would introduce bugs in testing: #1096747
    • Depends: godot3 recastnavigation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/godot3.html
    • autopkgtest for godot3/3.6+ds-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 22 days old (needed 2 days)
• xserver-xorg-video-vmware (1:13.4.0-1 to 1:13.4.0-2)
  • Migration status for xserver-xorg-video-vmware (1:13.4.0-1 to 1:13.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-vmware would introduce bugs in testing: #1112670
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-video-vmware.html
    • Reproducible on amd64 - info ♻
    • 22 days old (needed 5 days)
• evtest (1:1.35-1 to 1:1.36-1)
  • Migration status for evtest (1:1.35-1 to 1:1.36-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for umockdev/0.19.3-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/evtest.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 23 days old (needed 5 days)
• gcc-snapshot (- to 1:20250828-1)
  • Migration status for gcc-snapshot (- to 1:20250828-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-snapshot would introduce bugs in testing: #321449, #651291
    • autopkgtest for gcc-snapshot/1:20250828-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • 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 ♻
    • 23 days old (needed 5 days)
• howdoi (- to 2.0.20-2)
  • Migration status for howdoi (- to 2.0.20-2): 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/2.0.20-2: amd64: Pass, arm64: 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
    • 23 days old (needed 2 days)
• intel-compute-runtime (- to 25.31.34666.3-1)
  • Migration status for intel-compute-runtime (- to 25.31.34666.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): intel-compute-runtime intel-graphics-compiler2 (not considered)
    • Depends: intel-compute-runtime intel-graphics-compiler2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-compute-runtime.html
    • autopkgtest for intel-compute-runtime/25.31.34666.3-1: amd64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • 23 days old (needed 5 days)
• slm (1.32-3 to 2.3-1)
  • Migration status for slm (1.32-3 to 2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/s/slm.html
    • autopkgtest for slm/2.3-1: amd64: Regression ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: Failed (not a regression) ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Ignoring non-reproducibility on amd64 (not a regression) - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • 23 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• vip-manager (1.0.2-9 to 1.0.2-10)
  • Migration status for vip-manager (1.0.2-9 to 1.0.2-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: vip-manager golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vip-manager.html
    • autopkgtest for vip-manager/1.0.2-10: amd64: Pass, arm64: 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
    • 23 days old (needed 2 days)
• vip-manager2 (3.0.0-2 to 4.0.0-2)
  • Migration status for vip-manager2 (3.0.0-2 to 4.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: vip-manager2 golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vip-manager2.html
    • autopkgtest for vip-manager2/4.0.0-2: amd64: Pass, arm64: 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 ♻
    • Required age reduced by 3 days because of autopkgtest
    • 23 days old (needed 2 days)
• cage (0.2.0-2 to 0.2.0+20250816-2)
  • Migration status for cage (0.2.0-2 to 0.2.0+20250816-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): cage wlroots (not considered)
    • Depends: cage wlroots (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cage.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 24 days old (needed 5 days)
• godot (3.6+ds-2 to 4.4.1+ds-1)
  • Migration status for godot (3.6+ds-2 to 4.4.1+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: godot recastnavigation (not considered)
    • Invalidated by dependency
    • Depends: godot miniupnpc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/godot.html
    • autopkgtest for godot/4.4.1+ds-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻)
    • No reference result, but not reproducibility on amd64 - info ♻
    • 24 days old (needed 5 days)
• intake (- to 0.6.6-4)
  • Migration status for intake (- to 0.6.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intake would introduce bugs in testing: #1063953
    • autopkgtest for intake/0.6.6-4: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): intake entrypoints (not considered)
    • Depends: intake entrypoints (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intake.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 24 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• labwc (0.8.3-1 to 0.9.1-3)
  • Migration status for labwc (0.8.3-1 to 0.9.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): labwc wlroots (not considered)
    • Depends: labwc wlroots (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/labwc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 24 days old (needed 5 days)
• libbigwig (0.4.7+dfsg-3.1 to 0.4.8+dfsg-1)
  • Migration status for libbigwig (0.4.7+dfsg-3.1 to 0.4.8+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libbigwig would introduce bugs in testing: #1112179
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libb/libbigwig.html
    • autopkgtest for libbigwig/0.4.8+dfsg-1: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 24 days old (needed 5 days)
• llvm-toolchain-21 (- to 1:21.1.0-1)
  • Migration status for llvm-toolchain-21 (- to 1:21.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • llvm-toolchain-21 has no binaries on any arch
    • Updating llvm-toolchain-21 would introduce bugs in testing: #1113934
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on all - info
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 24 days old (needed 5 days)
• python-calendra (- to 7.11.1-1)
  • Migration status for python-calendra (- to 7.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-calendra would introduce bugs in testing: #1078636
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-calendra.html
    • 24 days old (needed 10 days)
• python-polyfactory (- to 2.22.2-1)
  • Migration status for python-polyfactory (- to 2.22.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: python-polyfactory python-auto-pytabs (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-polyfactory.html
    • autopkgtest for python-polyfactory/2.22.2-1: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 24 days old (needed 5 days)
• sway (1.10.1-2 to 1.11-2)
  • Migration status for sway (1.10.1-2 to 1.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): sway wlroots (not considered)
    • Depends: sway wlroots (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sway.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 24 days old (needed 5 days)
• ujson (5.10.0-1 to 5.11.0-1)
  • Migration status for ujson (5.10.0-1 to 5.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ujson would introduce bugs in testing: #1112173
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/ujson.html
    • autopkgtest for ujson/5.11.0-1: amd64: Pass, arm64: 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
    • 24 days old (needed 2 days)
• deja-dup (45.2-3 to 49~alpha-2)
  • Migration status for deja-dup (45.2-3 to 49~alpha-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating deja-dup would introduce bugs in testing: #1111200
  • Additional info:
    • Updating deja-dup will fix bugs in testing: #1115188
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deja-dup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 25 days old (needed 5 days)
• giada (- to 1.2.1-1)
  • Migration status for giada (- to 1.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating giada would introduce bugs in testing: #1112121
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • 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: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
    • Waiting for lintian test results on ppc64el, amd64, arm64, i386, s390x, riscv64, armhf - info
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/giada.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 25 days old (needed 5 days)
• gvm-tools (- to 25.3.2-1)
  • Migration status for gvm-tools (- to 25.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): 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/25.3.2-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 25 days old (needed 5 days)
• htpdate (1.3.7-2 to 2.0.0-2)
  • Migration status for htpdate (1.3.7-2 to 2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for htpdate/2.0.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/htpdate.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 25 days old (needed 5 days)
• intel-graphics-compiler2 (- to 2.16.0-2)
  • Migration status for intel-graphics-compiler2 (- to 2.16.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-graphics-compiler2 would introduce bugs in testing: #1114154
    • Build-Depends(-Arch): intel-graphics-compiler2 intel-vc-intrinsics (not considered)
    • Build-Depends(-Arch): intel-graphics-compiler2 llvm-toolchain-14 (not considered)
    • Build-Depends(-Arch): intel-graphics-compiler2 opencl-clang-14
    • Build-Depends(-Arch): intel-graphics-compiler2 spirv-llvm-translator-14
    • Depends: intel-graphics-compiler2 llvm-toolchain-14 (not considered)
    • Depends: intel-graphics-compiler2 opencl-clang-14
    • Depends: intel-graphics-compiler2 spirv-llvm-translator-14
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-graphics-compiler2.html
    • 25 days old (needed 5 days)
• manaplus (- to 2.1.3.17-8.1)
  • Migration status for manaplus (- to 2.1.3.17-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating manaplus would introduce bugs in testing: #1101180
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/manaplus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 25 days old (needed 5 days)
• node-jquery (3.6.1+dfsg+~3.5.14-1 to 3.7.1+dfsg+~3.5.33-1)
  • Migration status for node-jquery (3.6.1+dfsg+~3.5.14-1 to 3.7.1+dfsg+~3.5.33-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • migrating libjs-jquery/3.7.1+dfsg+~3.5.33-1/amd64 to testing makes adarkroom/1.4+dfsg.1-2/amd64 uninstallable
    • migrating libjs-jquery/3.7.1+dfsg+~3.5.33-1/arm64 to testing makes adarkroom/1.4+dfsg.1-2/arm64 uninstallable
    • autopkgtest for cython/3.0.11+dfsg-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for dipy/1.11.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-18: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for esys-particle: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Test triggered (failure will be ignored)
    • autopkgtest for fenics-dolfinx/1:0.9.0-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Pass, i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for llvm-toolchain-17/1:17.0.6-22: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Pass
    • autopkgtest for llvm-toolchain-18/1:18.1.8-18: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for llvm-toolchain-19/1:19.1.7-3: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for macaulay2/1.24.11+ds-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for node-jquery/3.7.1+dfsg+~3.5.33-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 ♻
    • autopkgtest for numba/0.61.2+dfsg-1: amd64: Pass, arm64: Pass, i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Test triggered (failure will be ignored), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for openbabel/3.1.1+dfsg-12: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Test triggered (failure will be ignored)
    • autopkgtest for openjdk-21/21.0.9~5ea-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for openjdk-25/25~36ea-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for openjdk-26/26~12ea-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: No tests, superficial or marked flaky ♻
    • autopkgtest for patroni/4.0.6-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for python3.13/3.13.7-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for pythran/0.17.0+ds-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for r-cran-jquerylib/0.1.4+dfsg-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for r-cran-pkgdown/2.1.1-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for r-cran-plumber/1.3.0+ds-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for sqlalchemy/2.0.43+ds1-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
    • autopkgtest for swift/2.35.1-2: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Test triggered (failure will be ignored)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-jquery.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 25 days old (needed 5 days)
• phoc (0.46.0-1 to 0.49.0-2)
  • Migration status for phoc (0.46.0-1 to 0.49.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): phoc wlroots (not considered)
    • Depends: phoc wlroots (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phoc.html
    • autopkgtest for phoc/0.49.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 25 days old (needed 5 days)
• wlroots (0.18.2-3 to 0.19.0-2)
  • Migration status for wlroots (0.18.2-3 to 0.19.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • removing libwlroots-0.18-dev/0.18.2-3/amd64 from testing makes wayfire-dev/0.9.0-5/amd64 uninstallable
    • removing libwlroots-0.18-dev/0.18.2-3/arm64 from testing makes wayfire-dev/0.9.0-5/arm64 uninstallable
    • removing libwlroots-0.18-dev/0.18.2-3/armhf from testing makes wayfire-dev/0.9.0-5/armhf uninstallable
    • removing libwlroots-0.18-dev/0.18.2-3/i386 from testing makes wayfire-dev/0.9.0-5/i386 uninstallable
    • removing libwlroots-0.18-dev/0.18.2-3/ppc64el from testing makes wayfire-dev/0.9.0-5/ppc64el uninstallable
    • removing libwlroots-0.18-dev/0.18.2-3/riscv64 from testing makes wayfire-dev/0.9.0-5/riscv64 uninstallable
    • removing libwlroots-0.18-dev/0.18.2-3/s390x from testing makes wayfire-dev/0.9.0-5/s390x uninstallable
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wlroots.html
    • autopkgtest for wlroots/0.19.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 25 days old (needed 5 days)
• alicevision (- to 3.3.0+repack-3)
  • Migration status for alicevision (- to 3.3.0+repack-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • alicevision/amd64 has unsatisfiable dependency
    • libalicevision-dev/amd64 has unsatisfiable dependency
    • libalicevision3/amd64 has unsatisfiable dependency
    • alicevision unsatisfiable Build-Depends(-Arch) on amd64: libalembic-graphics-dev
    • Build-Depends(-Arch): alicevision geogram (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • 26 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• gsad (- to 24.5.4-1)
  • Migration status for gsad (- to 24.5.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gsad gvm-libs (not considered)
    • Depends: gsad gvm-libs (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Depends: gsad gvmd
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gsad.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 26 days old (needed 5 days)
• harlequin-mysql (- to 1.2.0-1)
  • Migration status for harlequin-mysql (- to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: harlequin-mysql harlequin (not considered)
    • Depends: harlequin-mysql mysql-connector-python (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/harlequin-mysql.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 26 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• macaulay2 (1.24.11+ds-5 to 1.25.06+ds-8)
  • Migration status for macaulay2 (1.24.11+ds-5 to 1.25.06+ds-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: macaulay2 normaliz (not considered)
  • Additional info:
    • Updating macaulay2 will fix bugs in testing: #1115435
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/macaulay2.html
    • autopkgtest for macaulay2/1.25.06+ds-8: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • No reference result, but not reproducibility on amd64 - info ♻
    • No reference result, but not reproducibility on arm64 - info ♻
    • 26 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• mirrorbits (0.6-1 to 0.6.1-1)
  • Migration status for mirrorbits (0.6-1 to 0.6.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: mirrorbits golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mirrorbits.html
    • autopkgtest for mirrorbits/0.6.1-1: amd64: Pass, arm64: 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
    • 26 days old (needed 2 days)
• mpich (4.3.0+really4.2.1-1 to 4.3.1-3)
  • Migration status for mpich (4.3.0+really4.2.1-1 to 4.3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-18: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for fenics-dolfinx/1:0.9.0-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for mpi-defaults/1.18: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻ (reference ♻)
    • autopkgtest for mpich/4.3.1-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating mpich will fix bugs in testing: #1115083
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpich.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Ignoring non-reproducibility on arm64 (not a regression) - info ♻
    • 26 days old (needed 5 days)
• crmsh (- to 5.0.0-1)
  • Migration status for crmsh (- to 5.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crmsh would introduce bugs in testing: #1098983
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crmsh.html
    • autopkgtest for crmsh/5.0.0-1: amd64: Pass, arm64: 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
    • 27 days old (needed 2 days)
• geogram (- to 1.9.6-1)
  • Migration status for geogram (- to 1.9.6-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on amd64
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on amd64, all - info
    • Build-Depends(-Arch): geogram amgcl (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 27 days old (needed 5 days)
• privatebin-cli (2.0.2-1 to 2.1.0-2)
  • Migration status for privatebin-cli (2.0.2-1 to 2.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: privatebin-cli golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/privatebin-cli.html
    • autopkgtest for privatebin-cli/2.1.0-2: amd64: Pass, arm64: 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
    • 27 days old (needed 2 days)
• rust-ivf (0.1.3-1 to 0.1.4-1)
  • Migration status for rust-ivf (0.1.3-1 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-ivf rust-bitstream-io (not considered)
    • Depends: rust-ivf rust-bitstream-io (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ivf.html
    • autopkgtest for rust-ivf/0.1.4-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for rust-rav1e/0.7.1-9: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered (failure will be ignored), s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 27 days old (needed 2 days)
• yubikey-agent (0.1.4-2 to 0.1.4-3)
  • Migration status for yubikey-agent (0.1.4-2 to 0.1.4-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: yubikey-agent golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yubikey-agent.html
    • autopkgtest for yubikey-agent/0.1.4-3: amd64: Pass, arm64: 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
    • 27 days old (needed 2 days)
• golang-github-rootless-containers-bypass4netns (0.4.1-1.1 to 0.4.2-1)
  • Migration status for golang-github-rootless-containers-bypass4netns (0.4.1-1.1 to 0.4.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: golang-github-rootless-containers-bypass4netns golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-rootless-containers-bypass4netns.html
    • autopkgtest for golang-github-rootless-containers-bypass4netns/0.4.2-1: 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
    • 28 days old (needed 2 days)
• gst-plugins-bad1.0-contrib (1.20.0-1.1 to 1.26.5-2)
  • Migration status for gst-plugins-bad1.0-contrib (1.20.0-1.1 to 1.26.5-2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • Removal request by auto-removals
    • Trying to remove package, not update it
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el, amd64, arm64, i386, s390x, armhf - info
  • Additional info:
    • Updating gst-plugins-bad1.0-contrib will fix bugs in testing: #1111731
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 28 days old (needed 5 days)
• kustomize (5.6.0+ds-1 to 5.7.1+ds-1)
  • Migration status for kustomize (5.6.0+ds-1 to 5.7.1+ds-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: kustomize golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kustomize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 28 days old (needed 5 days)
• litestar-htmx (- to 0.5.0-1)
  • Migration status for litestar-htmx (- 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): litestar-htmx python-auto-pytabs (not considered)
    • Invalidated by build-dependency
    • Build-Depends(-Arch): litestar-htmx litestar (not considered)
    • Depends: litestar-htmx litestar (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/litestar-htmx.html
    • autopkgtest for litestar-htmx/0.5.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 28 days old (needed 2 days)
• mysql-8.0 (- to 8.0.43-3)
  • Migration status for mysql-8.0 (- to 8.0.43-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-8.0 would introduce bugs in testing: #1078629
    • autopkgtest for mysql-8.0/8.0.43-3: amd64: Failed ♻, arm64: 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
    • 28 days old (needed 5 days)
• pg-gvm (- to 22.6.11-1)
  • Migration status for pg-gvm (- to 22.6.11-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.11-1: amd64: Pass, arm64: 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
    • 28 days old (needed 2 days)
• python-ytmusicapi (- to 1.10.2-2)
  • Migration status for python-ytmusicapi (- to 1.10.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-ytmusicapi would introduce bugs in testing: #1101671
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on all - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ytmusicapi.html
    • 28 days old (needed 5 days)
• radicale (3.5.4-2 to 3.5.5-1)
  • Migration status for radicale (3.5.4-2 to 3.5.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for radicale/3.5.5-1: amd64: Pass, arm64: Pass, i386: Regression ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/radicale.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 28 days old (needed 5 days)
• direnv (2.32.1-2 to 2.37.1-1)
  • Migration status for direnv (2.32.1-2 to 2.37.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: direnv golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/direnv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 29 days old (needed 5 days)
• distrobuilder (3.2-3 to 3.2-4)
  • Migration status for distrobuilder (3.2-3 to 3.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: distrobuilder golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/distrobuilder.html
    • autopkgtest for distrobuilder/3.2-4: amd64: Pass, arm64: 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
    • 29 days old (needed 2 days)
• dnscrypt-proxy (2.1.8+ds1-1 to 2.1.13+ds1-1)
  • Migration status for dnscrypt-proxy (2.1.8+ds1-1 to 2.1.13+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dnscrypt-proxy/2.1.13+ds1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Built-Using: dnscrypt-proxy golang-1.24 (not considered)
    • Built-Using: dnscrypt-proxy golang-github-lucas-clemente-quic-go (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnscrypt-proxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 29 days old (needed 5 days)
• minio-client (0.0~20250403-3 to 0.0~20250403-4)
  • Migration status for minio-client (0.0~20250403-3 to 0.0~20250403-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: minio-client golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/minio-client.html
    • autopkgtest for minio-client/0.0~20250403-4: amd64: Pass, arm64: 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
    • 29 days old (needed 2 days)
• ospd-openvas (- to 22.9.0-1)
  • Migration status for ospd-openvas (- to 22.9.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: ospd-openvas openvas-scanner (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ospd-openvas.html
    • autopkgtest for ospd-openvas/22.9.0-1: amd64: Pass, arm64: 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
    • 29 days old (needed 2 days)
• pydantic (2.10.6-2 to 2.12.0~a1-1)
  • Migration status for pydantic (2.10.6-2 to 2.12.0~a1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for fastapi/0.115.11-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for pydantic/2.12.0~a1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for python-youtubeaio/2.0.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • Build-Depends(-Arch): pydantic pydantic-core
    • Depends: pydantic pydantic-core
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydantic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 29 days old (needed 5 days)
• pydantic-core (2.27.2-3 to 2.37.2-1)
  • Migration status for pydantic-core (2.27.2-3 to 2.37.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Implicit dependency: pydantic-core pydantic (not considered)
    • Invalidated by implicit-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydantic-core.html
    • autopkgtest for pydantic-core/2.37.2-1: amd64: Pass, arm64: 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
    • 29 days old (needed 2 days)
• python-gvm (- to 26.5.0-1)
  • Migration status for python-gvm (- to 26.5.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/26.5.0-1: amd64: Pass, arm64: 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
    • 29 days old (needed 2 days)
• snapd (2.68.3-3 to 2.71-3)
  • Migration status for snapd (2.68.3-3 to 2.71-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating snapd would introduce bugs in testing: #1101956, #1115583
    • Built-Using: snapd golang-1.24 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/snapd.html
    • autopkgtest for snapd/2.71-3: amd64: Pass, 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 ♻
    • Reproducible on arm64 - info ♻
    • 29 days old (needed 5 days)
• bidentd (- to 1.1.4-1.5)
  • Migration status for bidentd (- to 1.1.4-1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bidentd would introduce bugs in testing: #763430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bidentd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 30 days old (needed 5 days)
• miniflux (2.2.6-2 to 2.2.12-1)
  • Migration status for miniflux (2.2.6-2 to 2.2.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: miniflux golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/miniflux.html
    • autopkgtest for miniflux/2.2.12-1: amd64: Pass, arm64: 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
    • 30 days old (needed 2 days)
• nim (- to 2.2.0-1)
  • Migration status for nim (- to 2.2.0-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • Waiting for lintian test results on armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim.html
    • autopkgtest for nim/2.2.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 30 days old (needed 2 days)
• nodejs (20.19.2+dfsg-1 to 20.19.4+dfsg-1)
  • Migration status for nodejs (20.19.2+dfsg-1 to 20.19.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-proxy-agents/0~2024040606-6: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • autopkgtest for nodejs/20.19.4+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
  • Additional info:
    • Updating nodejs will fix bugs in testing: #1097473, #1106428
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nodejs.html
    • 30 days old (needed 5 days)
• vim-vimwiki (2024.01.24-2 to 2024.01.24-3)
  • Migration status for vim-vimwiki (2024.01.24-2 to 2024.01.24-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by krekhov.dev@gmail.com, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-vimwiki.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 30 days old (needed 5 days)
• certstream-server-go (1.7.0-2 to 1.8.1-2)
  • Migration status for certstream-server-go (1.7.0-2 to 1.8.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: certstream-server-go golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/certstream-server-go.html
    • autopkgtest for certstream-server-go/1.8.1-2: amd64: Pass, arm64: 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
    • 31 days old (needed 2 days)
• geophar (- to 18.10+dfsg1-7)
  • Migration status for geophar (- to 18.10+dfsg1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for geophar/18.10+dfsg1-7: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/geophar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 31 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• git-credential-oauth (0.15.0-1 to 0.15.1-1)
  • Migration status for git-credential-oauth (0.15.0-1 to 0.15.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: git-credential-oauth golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-credential-oauth.html
    • autopkgtest for git-credential-oauth/0.15.1-1: amd64: Pass, arm64: 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
    • 31 days old (needed 2 days)
• gpa (- to 0.11.0-3)
  • Migration status for gpa (- to 0.11.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpa would introduce bugs in testing: #1089914
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 31 days old (needed 5 days)
• mold (2.37.1+dfsg-1 to 2.40.4+dfsg-2)
  • Migration status for mold (2.37.1+dfsg-1 to 2.40.4+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mold would introduce bugs in testing: #1114210
    • mold unsatisfiable Build-Depends(-Arch) on arm64: gcc-multilib
    • mold unsatisfiable Build-Depends(-Arch) on armhf: gcc-multilib
    • mold unsatisfiable Build-Depends(-Arch) on ppc64el: gcc-multilib
    • mold unsatisfiable Build-Depends(-Arch) on riscv64: gcc-multilib
    • missing build on arm64
    • missing build on armhf
    • missing build on ppc64el
    • missing build on riscv64
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el, arm64, riscv64, armhf - info
  • Additional info:
    • Updating mold will fix bugs in testing: #1115505
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mold.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 31 days old (needed 5 days)
• openvas-scanner (- to 23.23.1-1)
  • Migration status for openvas-scanner (- to 23.23.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 ♻
    • 31 days old (needed 5 days)
• rekor (1.3.9-1 to 1.4.0-1)
  • Migration status for rekor (1.3.9-1 to 1.4.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: rekor golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rekor.html
    • autopkgtest for rekor/1.4.0-1: amd64: Pass, arm64: 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
    • 31 days old (needed 2 days)
• go-sendxmpp (0.15.0~beta1-2 to 0.15.0-1)
  • Migration status for go-sendxmpp (0.15.0~beta1-2 to 0.15.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: go-sendxmpp golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-sendxmpp.html
    • autopkgtest for go-sendxmpp/0.15.0-1: amd64: Pass, arm64: 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
    • 32 days old (needed 2 days)
• golang-github-micromdm-scep (2.3.0-1 to 2.3.0-2)
  • Migration status for golang-github-micromdm-scep (2.3.0-1 to 2.3.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: golang-github-micromdm-scep golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-micromdm-scep.html
    • autopkgtest for golang-github-micromdm-scep/2.3.0-2: amd64: Pass, arm64: 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
    • 32 days old (needed 2 days)
• orthanc (1.12.7+dfsg-4 to 1.12.9+dfsg-1)
  • Migration status for orthanc (1.12.7+dfsg-4 to 1.12.9+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for orthanc/1.12.9+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for orthanc-webviewer/2.10+dfsg-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 32 days old (needed 5 days)
• orthanc-dicomweb (1.20+dfsg-1 to 1.21+dfsg-1)
  • Migration status for orthanc-dicomweb (1.20+dfsg-1 to 1.21+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: orthanc-dicomweb orthanc (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/orthanc-dicomweb.html
    • autopkgtest for orthanc-dicomweb/1.21+dfsg-1: amd64: Pass, arm64: 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
    • 32 days old (needed 2 days)
• python-ocp (- to 7.8.1.2-2)
  • Migration status for python-ocp (- to 7.8.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python-ocp has no binaries on any arch
    • python-ocp unsatisfiable Build-Depends(-Arch) on amd64: libocct-ivtk-dev
    • python-ocp unsatisfiable Build-Depends(-Arch) on amd64: python3-opencascade-pywrap
    • nothing built yet, autopkgtest delayed
    • nothing built yet, lintian 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 ♻
    • 32 days old (needed 5 days)
• python-opencascade-pywrap (- to 0.0~git20250714210719.b608b60-4)
  • Migration status for python-opencascade-pywrap (- to 0.0~git20250714210719.b608b60-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python-opencascade-pywrap has no binaries on any arch
    • python-opencascade-pywrap unsatisfiable Build-Depends(-Arch) on amd64: python3-clang (>= 1:20) | python3-clang-20
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on all - info
  • 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 ♻
    • 32 days old (needed 5 days)
• collectl (4.3.1-1 to 4.3.6-2)
  • Migration status for collectl (4.3.1-1 to 4.3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating collectl would introduce bugs in testing: #1112178
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on all - info
  • Additional info:
    • Updating collectl will fix bugs in testing: #1115564
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/collectl.html
    • 33 days old (needed 5 days)
• crash (- to 8.0.6-2)
  • Migration status for crash (- to 8.0.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crash would introduce bugs in testing: #1096475, #1108875
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crash.html
    • autopkgtest for crash/8.0.6-2: amd64: Pass, 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 ♻
    • Reproducible on arm64 - info ♻
    • 33 days old (needed 5 days)
• feedgenerator (2.1.0-2 to 2.2.1-1)
  • Migration status for feedgenerator (2.1.0-2 to 2.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for feedgenerator/2.2.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for metalfinder/2.1.6-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/feedgenerator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 33 days old (needed 5 days)
• matrix-synapse (- to 1.136.0-1)
  • Migration status for matrix-synapse (- to 1.136.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating matrix-synapse would introduce bugs in testing: #1111723
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matrix-synapse.html
    • autopkgtest for matrix-synapse/1.136.0-1: amd64: Pass, arm64: 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
    • 33 days old (needed 2 days)
• normaliz (3.10.4+ds-1 to 3.10.5+ds-3)
  • Migration status for normaliz (3.10.4+ds-1 to 3.10.5+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for macaulay2: riscv64: Test triggered (failure will be ignored)
    • autopkgtest for normaliz/3.10.5+ds-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for pynormaliz/2.21+ds-1: amd64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/normaliz.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 33 days old (needed 5 days)
• pynormaliz (2.21+ds-1 to 2.22+ds-2)
  • Migration status for pynormaliz (2.21+ds-1 to 2.22+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Removal request by ginggs
    • Trying to remove package, not update it
    • Depends: pynormaliz normaliz (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynormaliz.html
    • autopkgtest for pynormaliz/2.22+ds-2: amd64: Pass, arm64: 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
    • 33 days old (needed 2 days)
    • Remove hint for (transitive) dependency: pynormaliz
• python-vector (- to 1.6.3-1)
  • Migration status for python-vector (- to 1.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): python-vector python-awkward (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-vector.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 33 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• recastnavigation (1.5.1+git20210215.e75adf8-1 to 1.6.0+dfsg-1)
  • Migration status for recastnavigation (1.5.1+git20210215.e75adf8-1 to 1.6.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating recastnavigation would introduce bugs in testing: #1112095
  • Additional info:
    • Updating recastnavigation will fix bugs in testing: #1115504
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/recastnavigation.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 33 days old (needed 10 days)
• chafa (1.14.5-1 to 1.16.2-1)
  • Migration status for chafa (1.14.5-1 to 1.16.2-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for chafa/1.16.2-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 ♻
    • Waiting for lintian test results on i386 - info
  • Additional info:
    • Updating chafa will fix bugs in testing: #1115434
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chafa.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 34 days old (needed 5 days)
• gloo-cuda (0.0~git20231202.5354032-4 to 0.0~git20231202.5354032-5)
  • Migration status for gloo-cuda (0.0~git20231202.5354032-4 to 0.0~git20231202.5354032-5): 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~git20231202.5354032-5: amd64: Pass
    • Waiting for lintian test results on ppc64el, arm64 - info
  • Additional info:
    • Updating gloo-cuda will fix bugs in testing: #1115506
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 34 days old (needed 5 days)
• rust-const-str (- to 0.6.3-1)
  • Migration status for rust-const-str (- to 0.6.3-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-const-str.html
    • autopkgtest for rust-const-str/0.6.3-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 34 days old (needed 5 days)
• rust-const-str-proc-macro (- to 0.6.3-1)
  • Migration status for rust-const-str-proc-macro (- to 0.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-const-str-proc-macro-dev/amd64 has unsatisfiable dependency
    • librust-const-str-proc-macro-dev/arm64 has unsatisfiable dependency
    • librust-const-str-proc-macro-dev/armhf has unsatisfiable dependency
    • librust-const-str-proc-macro-dev/i386 has unsatisfiable dependency
    • librust-const-str-proc-macro-dev/ppc64el has unsatisfiable dependency
    • librust-const-str-proc-macro-dev/riscv64 has unsatisfiable dependency
    • librust-const-str-proc-macro-dev/s390x has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-const-str-proc-macro.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 34 days old (needed 5 days)
• etlcpp (20.40.0+dfsg-1 to 20.42.2+dfsg-1)
  • Migration status for etlcpp (20.40.0+dfsg-1 to 20.42.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by dkogan, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating etlcpp will fix bugs in testing: #1115440
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/etlcpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 35 days old (needed 5 days)
• kiwi (- to 10.2.32-1)
  • Migration status for kiwi (- to 10.2.32-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency
    • Updating kiwi would introduce bugs in testing: #1102480
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kiwi.html
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 35 days old (needed 5 days)
• cambalache (- to 0.97.7-1)
  • Migration status for cambalache (- to 0.97.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cambalache would introduce bugs in testing: #1111398, #1111456
    • cambalache unsatisfiable Build-Depends(-Arch) on amd64: python-gi-dev (>= 3.52)
    • cambalache unsatisfiable Build-Depends(-Arch) on arm64: python-gi-dev (>= 3.52)
    • cambalache unsatisfiable Build-Depends(-Arch) on armhf: python-gi-dev (>= 3.52)
    • cambalache unsatisfiable Build-Depends(-Arch) on i386: python-gi-dev (>= 3.52)
    • cambalache unsatisfiable Build-Depends(-Arch) on ppc64el: python-gi-dev (>= 3.52)
    • cambalache unsatisfiable Build-Depends(-Arch) on riscv64: python-gi-dev (>= 3.52)
    • cambalache unsatisfiable Build-Depends(-Arch) on s390x: python-gi-dev (>= 3.52)
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • 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: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
    • Waiting for lintian test results on amd64, ppc64el, arm64, i386, s390x, riscv64, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cambalache.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 36 days old (needed 5 days)
• frugen (2.1-3 to 3.0-1)
  • Migration status for frugen (2.1-3 to 3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for frugen/3.0-1: amd64: Pass, arm64: Pass, i386: Regression ♻ (reference ♻), ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating frugen will fix bugs in testing: #1115186
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frugen.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 36 days old (needed 5 days)
• python-beanie (1.29.0-1 to 2.0.0-1)
  • Migration status for python-beanie (1.29.0-1 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-beanie would introduce bugs in testing: #1111346
  • Additional info:
    • Updating python-beanie will fix bugs in testing: #1115433
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-beanie.html
    • autopkgtest for python-beanie/2.0.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 36 days old (needed 5 days)
• webcamoid (- to 9.3.0-1)
  • Migration status for webcamoid (- to 9.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating webcamoid would introduce bugs in testing: #1089101
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on s390x
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el, i386, s390x, armhf - info
  • 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 ♻
    • 36 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• gvm-libs (- to 22.24.0-1)
  • Migration status for gvm-libs (- to 22.24.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 ♻
    • 37 days old (needed 5 days)
• mygui (3.4.2+dfsg-1.1 to 3.4.3+dfsg-2)
  • Migration status for mygui (3.4.2+dfsg-1.1 to 3.4.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libmygui.ogreplatform0debian1t64/armhf has unsatisfiable dependency
    • libmygui.opengl3platform0debian1t64/armhf has unsatisfiable dependency
    • libmygui.openglplatform0debian1t64/armhf has unsatisfiable dependency
  • Additional info:
    • Updating mygui will fix bugs in testing: #1115082
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mygui.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 37 days old (needed 5 days)
• gnutls28 (3.8.9-3 to 3.8.10-2)
  • Migration status for gnutls28 (3.8.9-3 to 3.8.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for cmake/4.1.1+really3.31.6-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for gnutls28/3.8.10-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for gsasl/2.2.2-3: amd64: Pass, arm64: Pass, i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Pass, s390x: Pass
  • Additional info:
    • Updating gnutls28 will fix bugs in testing: #1114881
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnutls28.html
    • 39 days old (needed 5 days)
• intel-vc-intrinsics (- to 0.23.1-1)
  • Migration status for intel-vc-intrinsics (- to 0.23.1-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 ♻
    • 39 days old (needed 5 days)
• kalamine (- to 0.38-4)
  • Migration status for kalamine (- to 0.38-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kalamine would introduce bugs in testing: #1107077
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kalamine.html
    • autopkgtest for kalamine/0.38-4: amd64: Pass, arm64: 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
    • 39 days old (needed 2 days)
• nipype (- to 1.9.2-4)
  • Migration status for nipype (- to 1.9.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): nipype python-etelemetry (not considered)
    • Depends: nipype python-etelemetry (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nipype.html
    • autopkgtest for nipype/1.9.2-4: amd64: Pass, arm64: 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
    • 39 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• rtfilter (- to 1.3-1)
  • Migration status for rtfilter (- to 1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rtfilter would introduce bugs in testing: #1111462
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rtfilter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 39 days old (needed 5 days)
• findpython (0.6.2-1 to 0.7.0-1)
  • Migration status for findpython (0.6.2-1 to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for findpython/0.7.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for poetry/2.1.2+dfsg-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Updating findpython will fix bugs in testing: #1114879
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/findpython.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 40 days old (needed 5 days)
• rust-sha256 (- to 1.6.0-4)
  • Migration status for rust-sha256 (- to 1.6.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-sha256/1.6.0-4: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-sha256.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 40 days old (needed 5 days)
• rust-ssh2-config (- to 0.5.4-5)
  • Migration status for rust-ssh2-config (- to 0.5.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ssh2-config/0.5.4-5: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ssh2-config.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 40 days old (needed 5 days)
• rust-terminal-prompt (0.2.3-4 to 0.2.3-7)
  • Migration status for rust-terminal-prompt (0.2.3-4 to 0.2.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-terminal-prompt/0.2.3-7: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Updating rust-terminal-prompt will fix bugs in testing: #1114882
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-terminal-prompt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 40 days old (needed 5 days)
• node-dns-packet (- to 5.6.1-1)
  • Migration status for node-dns-packet (- to 5.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): node-dns-packet node-leichtgewicht-ip-codec (not considered)
    • Depends: node-dns-packet node-leichtgewicht-ip-codec (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-dns-packet.html
    • autopkgtest for node-dns-packet/5.6.1-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 43 days old (needed 5 days)
• node-leichtgewicht-ip-codec (- to 2.0.2-1)
  • Migration status for node-leichtgewicht-ip-codec (- to 2.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-leichtgewicht-ip-codec.html
    • autopkgtest for node-leichtgewicht-ip-codec/2.0.2-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 43 days old (needed 5 days)
• node-multicast-dns (- to 7.2.5-1)
  • Migration status for node-multicast-dns (- to 7.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): node-multicast-dns node-dns-packet (not considered)
    • Build-Depends(-Arch): node-multicast-dns node-thunky (not considered)
    • Depends: node-multicast-dns node-dns-packet (not considered)
    • Depends: node-multicast-dns node-thunky (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-multicast-dns.html
    • autopkgtest for node-multicast-dns/7.2.5-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 43 days old (needed 5 days)
• node-thunky (- to 1.1.0-1)
  • Migration status for node-thunky (- 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 zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-thunky.html
    • autopkgtest for node-thunky/1.1.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 43 days old (needed 5 days)
• ruby-wikicloth (0.8.1+dfsg-4.1 to 0.8.3+dfsg-1)
  • Migration status for ruby-wikicloth (0.8.1+dfsg-4.1 to 0.8.3+dfsg-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
    • Waiting for lintian test results on all - info
  • Additional info:
    • Updating ruby-wikicloth will fix bugs in testing: #1114567
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-wikicloth.html
    • 43 days old (needed 5 days)
• mupdf (1.25.1+ds1-6 to 1.25.1+ds1-7)
  • Migration status for mupdf (1.25.1+ds1-6 to 1.25.1+ds1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pymupdf/1.25.4+ds1-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
  • Additional info:
    • Updating mupdf will fix bugs in testing: #1114566
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mupdf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 44 days old (needed 5 days)
• ruby-html2text (- to 0.2.0-2)
  • Migration status for ruby-html2text (- to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-html2text would introduce bugs in testing: #1107538
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-html2text.html
    • autopkgtest for ruby-html2text/0.2.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 44 days old (needed 2 days)
• extrepo-data (- to 1.0.5)
  • Migration status for extrepo-data (- to 1.0.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating extrepo-data would introduce bugs in testing: #1078614
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/extrepo-data.html
    • 47 days old (needed 5 days)
• node-glossy (- to 0.1.7-1)
  • Migration status for node-glossy (- to 0.1.7-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/n/node-glossy.html
    • autopkgtest for node-glossy/0.1.7-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 49 days old (needed 5 days)
• node-winston-syslog (- to 2.7.1-1)
  • Migration status for node-winston-syslog (- to 2.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-winston-syslog/2.7.1-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
    • Build-Depends(-Arch): node-winston-syslog node-glossy (not considered)
    • Depends: node-winston-syslog node-glossy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-winston-syslog.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 49 days old (needed 5 days)
• openjdk-8 (- to 8u462-ga-1)
  • Migration status for openjdk-8 (- to 8u462-ga-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-8 would introduce bugs in testing: #989736
    • 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/o/openjdk-8.html
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Pass, i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for openjdk-8: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), s390x: Test triggered (failure will be ignored)
    • Reproducible on amd64 - info ♻
    • 51 days old (needed 5 days)
• libhyprcursor (- to 0.1.11-1)
  • Migration status for libhyprcursor (- to 0.1.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libhyprcursor would introduce bugs in testing: #1106525
    • Build-Depends(-Arch): libhyprcursor hyprlang (not considered)
    • Depends: libhyprcursor hyprlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libh/libhyprcursor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 52 days old (needed 5 days)
• hyprutils (- to 0.7.0-1)
  • Migration status for hyprutils (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyprutils would introduce bugs in testing: #1090839, #1106523
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyprutils.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 54 days old (needed 5 days)
• hyprlang (- to 0.6.0-1)
  • Migration status for hyprlang (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyprlang would introduce bugs in testing: #1106521
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el - info
    • Build-Depends(-Arch): hyprlang hyprutils (not considered)
    • Depends: hyprlang hyprutils (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyprlang.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 55 days old (needed 5 days)
• hyprwayland-scanner (- to 0.4.4-1)
  • Migration status for hyprwayland-scanner (- to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyprwayland-scanner would introduce bugs in testing: #1106524
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyprwayland-scanner.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 55 days old (needed 5 days)
• ciborium (- to 1.0.2-2)
  • Migration status for ciborium (- to 1.0.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Built-Using: ciborium golang-1.24 (not considered)
    • Invalidated by built-using
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ciborium.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 58 days old (needed 5 days)
• pynecil (- to 4.1.1-2)
  • Migration status for pynecil (- to 4.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pynecil/4.1.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pynecil.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 59 days old (needed 5 days)
• endless-sky (- to 0.10.14-1)
  • Migration status for endless-sky (- to 0.10.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating endless-sky would introduce bugs in testing: #1061241
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on riscv64
    • missing build on s390x
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:riscv64 not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results on s390x, ppc64el, arm64, i386, riscv64, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/endless-sky.html
    • Reproducible on amd64 - info ♻
    • 61 days old (needed 5 days)
• receptor (- to 1.5.5-2)
  • Migration status for receptor (- to 1.5.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating receptor would introduce bugs in testing: #1109561
    • autopkgtest for receptor/1.5.5-2: ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Pass
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on amd64, arm64, i386, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/receptor.html
    • 61 days old (needed 5 days)
• partman-hfs (- to 17)
  • Migration status for partman-hfs (- to 17): 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 i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 62 days old (needed 5 days)
• openjdk-24 (- to 24.0.2+12-1)
  • Migration status for openjdk-24 (- to 24.0.2+12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-24 would introduce bugs in testing: #1078199
    • 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/o/openjdk-24.html
    • autopkgtest for bbmap/39.20+dfsg-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Pass, i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for openjdk-24/24.0.2+12-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Reproducible on amd64 - info ♻
    • 63 days old (needed 5 days)
• ruby-cutest (1.2.1-2.1 to 1.2.3-1)
  • Migration status for ruby-cutest (1.2.1-2.1 to 1.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-cutest/amd64 has unsatisfiable dependency
    • ruby-cutest/arm64 has unsatisfiable dependency
    • Updating ruby-cutest would introduce bugs in testing: #1115713
    • Not built on buildd: arch all binaries uploaded by praveen, a new source-only upload is needed to allow migration
  • Additional info:
    • Updating ruby-cutest will fix bugs in testing: #1111730
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/ruby-cutest.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 63 days old (needed 5 days)
• gophian (- to 0.6.1-1)
  • Migration status for gophian (- to 0.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gophian would introduce bugs in testing: #1099567
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gophian.html
    • autopkgtest for gophian/0.6.1-1: amd64: Pass, arm64: 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
    • 64 days old (needed 2 days)
• mllex-polyml (- to 0.0~git20210410.85768e9-1)
  • Migration status for mllex-polyml (- to 0.0~git20210410.85768e9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mllex-polyml polyml (not considered)
    • Depends: mllex-polyml polyml (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mllex-polyml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 64 days old (needed 5 days)
• ble.sh (- to 0.4.0~git20250321.d4c812b-1)
  • Migration status for ble.sh (- to 0.4.0~git20250321.d4c812b-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by keyholding@ncts.me, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/ble.sh.html
    • 66 days old (needed 5 days)
• libcvss-perl (- to 1.14-1)
  • Migration status for libcvss-perl (- to 1.14-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/libc/libcvss-perl.html
    • autopkgtest for libcvss-perl/1.14-1: amd64: Pass, arm64: 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
    • 71 days old (needed 2 days)
• liburi-packageurl-perl (- to 2.22-1)
  • Migration status for liburi-packageurl-perl (- to 2.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for liburi-packageurl-perl/2.22-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • 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/libu/liburi-packageurl-perl.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 71 days old (needed 5 days)
• gitlab (- to 17.6.5-19)
  • Migration status for gitlab (- to 17.6.5-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab would introduce bugs in testing: #1103306, #1109069
    • autopkgtest for gitlab/17.6.5-19: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Depends: gitlab ruby-html2text (not considered)
    • Depends: gitlab ruby-omniauth-oauth2-generic (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 72 days old (needed 5 days)
    • Remove hint for (transitive) dependency: bcron, ruby-rbtrace
• tkcvs (- to 8.2.3-6)
  • Migration status for tkcvs (- to 8.2.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • tkcvs has no binaries on any arch
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on all - info
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 77 days old (needed 5 days)
• python-anndata (- to 0.12.0~rc1-1)
  • Migration status for python-anndata (- to 0.12.0~rc1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-anndata would introduce bugs in testing: #1114293
    • autopkgtest for python-anndata/0.12.0~rc1-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): python-anndata python-awkward (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-anndata.html
    • 79 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• bcbio (- to 1.2.9-4)
  • Migration status for bcbio (- to 1.2.9-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bcbio would introduce bugs in testing: #928076
    • Build-Depends(-Arch): bcbio mosdepth (not considered)
    • Build-Depends(-Arch): bcbio umis (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for bcbio/1.2.9-4: 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 ♻
    • 82 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• doxysphinx (- to 3.3.12-6)
  • Migration status for doxysphinx (- to 3.3.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): doxysphinx sphinx-needs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/doxysphinx.html
    • autopkgtest for doxysphinx/3.3.12-6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 86 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• sphinx-needs (- to 5.1.0+dfsg-1)
  • Migration status for sphinx-needs (- to 5.1.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for sphinx-needs/5.1.0+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sphinx-needs.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 86 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-550 (- to 550.54.15-2)
  • Migration status for nvidia-graphics-drivers-tesla-550 (- to 550.54.15-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • nvidia-tesla-550-driver-full/ppc64el has unsatisfiable dependency
    • Updating nvidia-graphics-drivers-tesla-550 would introduce bugs in testing: #1104078, #1109917
    • autopkgtest for nvidia-graphics-drivers-tesla-550/550.54.15-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 88 days old (needed 5 days)
• nvidia-graphics-drivers-tesla (- to 525.147.05-16)
  • Migration status for nvidia-graphics-drivers-tesla (- to 525.147.05-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libnvidia-tesla-cfg1/ppc64el has unsatisfiable dependency
    • libnvidia-tesla-cuda1/ppc64el has unsatisfiable dependency
    • nvidia-tesla-driver/ppc64el has unsatisfiable dependency
    • nvidia-tesla-driver-libs/ppc64el has unsatisfiable dependency
    • nvidia-tesla-kernel-dkms/ppc64el has unsatisfiable dependency
    • nvidia-tesla-kernel-source/ppc64el has unsatisfiable dependency
    • nvidia-tesla-smi/ppc64el has unsatisfiable dependency
    • xserver-xorg-video-nvidia-tesla/ppc64el has unsatisfiable dependency
    • Updating nvidia-graphics-drivers-tesla would introduce bugs in testing: #1085244
    • autopkgtest for nvidia-graphics-drivers-tesla/525.147.05-16: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch ppc64el, not running autopkgtest there
    • 89 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-470 (- to 470.256.02-7)
  • Migration status for nvidia-graphics-drivers-tesla-470 (- to 470.256.02-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-tesla-470 would introduce bugs in testing: #1085242, #1085974, #1093914, #1104074, #1109913
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for nvidia-graphics-drivers-tesla-470/470.256.02-7: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻
    • 89 days old (needed 5 days)
• looking-glass (- to 0+b7+ds1-1)
  • Migration status for looking-glass (- to 0+b7+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating looking-glass would introduce bugs in testing: #1094308
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/looking-glass.html
    • Reproducible on amd64 - info ♻
    • 90 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-418 (- to 418.226.00-19)
  • Migration status for nvidia-graphics-drivers-tesla-418 (- to 418.226.00-19): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • xserver-xorg-video-nvidia-tesla-418/amd64 has unsatisfiable dependency
    • xserver-xorg-video-nvidia-tesla-418/ppc64el has unsatisfiable dependency
    • Updating nvidia-graphics-drivers-tesla-418 would introduce bugs in testing: #1005930, #1006718, #1011143, #1016617, #1025282, #1033777, #1039681, #1055139, #1064986, #1072795, #1081648, #1085971, #1093911, #1104071, #1109910
    • autopkgtest for nvidia-graphics-drivers-tesla-418/418.226.00-19: 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
    • 93 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-450 (- to 450.248.02-11)
  • Migration status for nvidia-graphics-drivers-tesla-450 (- to 450.248.02-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-tesla-450 would introduce bugs in testing: #1014304
    • autopkgtest for nvidia-graphics-drivers-tesla-450/450.248.02-11: amd64: Failed ♻, arm64: Failed ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed ♻
    • Depends: nvidia-graphics-drivers-tesla-450 nvidia-graphics-drivers-tesla-470 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 93 days old (needed 5 days)
• nvidia-graphics-drivers-tesla-460 (- to 460.106.00-21)
  • Migration status for nvidia-graphics-drivers-tesla-460 (- to 460.106.00-21): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-tesla-460 would introduce bugs in testing: #1027704
    • autopkgtest for nvidia-graphics-drivers-tesla-460/460.106.00-21: amd64: Failed ♻, arm64: Failed ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed ♻
    • Depends: nvidia-graphics-drivers-tesla-460 nvidia-graphics-drivers-tesla-470 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 93 days old (needed 5 days)
• nvidia-graphics-drivers-legacy-390xx (- to 390.157-13)
  • Migration status for nvidia-graphics-drivers-legacy-390xx (- to 390.157-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nvidia-graphics-drivers-legacy-390xx would introduce bugs in testing: #1006719, #1033776, #1039680, #1055138, #1064985, #1072794, #1085970, #1093910, #1104070, #1109909
    • 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-13: amd64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻
    • 94 days old (needed 5 days)
• golang-1.23 (- to 1.23.10-1)
  • Migration status for golang-1.23 (- to 1.23.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-1.23 would introduce bugs in testing: #1096748, #1102118, #1106310
    • autopkgtest for golang-1.23/1.23.10-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-1.23.html
    • Reproducible on amd64 - info ♻
    • 95 days old (needed 5 days)
• calamares-extensions (- to 3.3.12-1.2)
  • Migration status for calamares-extensions (- to 3.3.12-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating calamares-extensions would introduce bugs in testing: #1092373
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calamares-extensions.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 98 days old (needed 5 days)
• python-lua (- to 1.0-1)
  • Migration status for python-lua (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-lua would introduce bugs in testing: #1114309
    • autopkgtest for python-lua/1.0-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lua.html
    • Reproducible on arm64 - info ♻
    • 102 days old (needed 5 days)
• arctica-greeter (- to 0.99.9.4-1)
  • Migration status for arctica-greeter (- to 0.99.9.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: arctica-greeter remote-logon-service (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/arctica-greeter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 106 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis, notify-osd
• mysql-connector-python (- to 9.3.0-1)
  • Migration status for mysql-connector-python (- to 9.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mysql-connector-python would introduce bugs in testing: #923347
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mysql-connector-python.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 110 days old (needed 5 days)
• hyprland-protocols (- to 0.6.2-1)
  • Migration status for hyprland-protocols (- to 0.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyprland-protocols would introduce bugs in testing: #1106520
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyprland-protocols.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 113 days old (needed 5 days)
• prospector (- to 1.10.3-2)
  • Migration status for prospector (- to 1.10.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prospector would introduce bugs in testing: #1109437, #1114270
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prospector.html
    • Reproducible on arm64 - info ♻
    • 116 days old (needed 5 days)
• golang-github-twin-g8 (- to 3.0.0-2)
  • Migration status for golang-github-twin-g8 (- to 3.0.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-twin-g8 golang-github-twin-gocache (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twin-g8.html
    • autopkgtest for golang-github-twin-g8/3.0.0-2: amd64: Pass, arm64: 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
    • 117 days old (needed 2 days)
• golang-github-twin-gocache (- to 2.2.2-2)
  • Migration status for golang-github-twin-gocache (- to 2.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-twin-gocache/2.2.2-2: amd64: Pass, arm64: Pass, i386: Failed ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-twin-gocache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 117 days old (needed 5 days)
• python-certbot-dns-digitalocean (- to 4.0.0-1)
  • Migration status for python-certbot-dns-digitalocean (- to 4.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-certbot-dns-digitalocean python-digitalocean (not considered)
    • Depends: python-certbot-dns-digitalocean python-digitalocean (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-digitalocean.html
    • autopkgtest for python-certbot-dns-digitalocean/4.0.0-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 118 days old (needed 5 days)
• mitmproxy (- to 8.1.1-3)
  • Migration status for mitmproxy (- to 8.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mitmproxy would introduce bugs in testing: #1071640, #1103701, #1110243
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mitmproxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 125 days old (needed 5 days)
• nvchecker (- to 2.17-1)
  • Migration status for nvchecker (- to 2.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nvchecker/2.17-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nvchecker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 125 days old (needed 5 days)
• python-lsp-ruff (- to 1.5.3-3)
  • Migration status for python-lsp-ruff (- to 1.5.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-lsp-ruff ruff (not considered)
    • Depends: python-lsp-ruff ruff (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-lsp-ruff.html
    • autopkgtest for python-lsp-ruff/1.5.3-3: amd64: Pass, arm64: 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
    • 125 days old (needed 2 days)
• golang-github-notaryproject-notation-go (- to 1.2.1-4)
  • Migration status for golang-github-notaryproject-notation-go (- to 1.2.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-notaryproject-notation-go would introduce bugs in testing: #1094409
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-notaryproject-notation-go.html
    • autopkgtest for golang-github-notaryproject-notation-go/1.2.1-4: amd64: Pass, arm64: 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
    • 128 days old (needed 2 days)
• r-cran-cards (- to 0.6.0-1)
  • Migration status for r-cran-cards (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-cards/0.6.0-1: amd64: Pass, arm64: Pass, i386: Failed ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-cards.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 129 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• napari-console (- to 0.1.3-5)
  • Migration status for napari-console (- to 0.1.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for napari-console/0.1.3-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
    • Build-Depends(-Arch): napari-console napari (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari-console.html
    • Reproducible on arm64 - info ♻
    • 131 days old (needed 5 days)
• caddy (- to 2.6.2-12)
  • Migration status for caddy (- to 2.6.2-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating caddy would introduce bugs in testing: #1110530, #1114074
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/caddy.html
    • autopkgtest for caddy/2.6.2-12: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 133 days old (needed 2 days)
• simplesamlphp (- to 1.19.7-2)
  • Migration status for simplesamlphp (- to 1.19.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simplesamlphp would introduce bugs in testing: #1088816
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simplesamlphp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 133 days old (needed 5 days)
• napari-plugin-manager (- to 0.1.4-4)
  • Migration status for napari-plugin-manager (- to 0.1.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for napari-plugin-manager/0.1.4-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
    • Build-Depends(-Arch): napari-plugin-manager napari (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari-plugin-manager.html
    • Reproducible on amd64 - info ♻
    • 134 days old (needed 5 days)
• litestar (- to 2.16.0-1)
  • Migration status for litestar (- to 2.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating litestar would introduce bugs in testing: #1114186
    • Build-Depends-Indep: litestar litestar-htmx
    • Build-Depends-Indep: litestar python-polyfactory
    • Depends: litestar litestar-htmx
    • Depends: litestar python-polyfactory
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/litestar.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for litestar/2.16.0-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 135 days old (needed 2 days)
• puppetdb (- to 8.8.1-1~exp1)
  • Migration status for puppetdb (- to 8.8.1-1~exp1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating puppetdb would introduce bugs in testing: #1109417
    • autopkgtest for puppetdb/8.8.1-1~exp1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppetdb.html
    • 136 days old (needed 5 days)
• crm114 (- to 20100106-11)
  • Migration status for crm114 (- to 20100106-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crm114 would introduce bugs in testing: #1098983
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crm114.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 139 days old (needed 5 days)
• cheese (- to 44.1-5)
  • Migration status for cheese (- to 44.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cheese would introduce bugs in testing: #1018115
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cheese.html
    • autopkgtest for cheese/44.1-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 ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 140 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• harlequin-odbc (- to 0.3.1-2)
  • Migration status for harlequin-odbc (- to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: harlequin-odbc harlequin (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/harlequin-odbc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 141 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• node-jquery-validation (- to 1.21.0+dfsg-2)
  • Migration status for node-jquery-validation (- to 1.21.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for node-jquery-validation/1.21.0+dfsg-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-jquery-validation.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 141 days old (needed 5 days)
• simplyhtml (- to 0.17.3+dfsg1-1.1)
  • Migration status for simplyhtml (- to 0.17.3+dfsg1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simplyhtml would introduce bugs in testing: #1104088
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simplyhtml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 141 days old (needed 5 days)
• ttyd (- to 1.7.7-4)
  • Migration status for ttyd (- to 1.7.7-4): 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 ♻
    • 141 days old (needed 5 days)
• reflect-cpp (- to 0.18.0+ds-3)
  • Migration status for reflect-cpp (- to 0.18.0+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating reflect-cpp would introduce bugs in testing: #1112052, #1112554
    • autopkgtest for reflect-cpp/0.18.0+ds-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/reflect-cpp.html
    • 148 days old (needed 5 days)
• hyprpaper (- to 0.7.0-1.1)
  • Migration status for hyprpaper (- to 0.7.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyprpaper would introduce bugs in testing: #1106522
    • Build-Depends(-Arch): hyprpaper hyprlang (not considered)
    • Depends: hyprpaper hyprlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyprpaper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 153 days old (needed 5 days)
• narcissus (- to 1.0.7+ds-3)
  • Migration status for narcissus (- to 1.0.7+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libnarcissus-java/arm64 has unsatisfiable dependency
    • Updating narcissus would introduce bugs in testing: #1103295
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on amd64 - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/narcissus.html
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 154 days old (needed 5 days)
• guix (- to 1.4.0-9)
  • Migration status for guix (- to 1.4.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating guix would introduce bugs in testing: #1096790, #1108318, #1112143, #1115303
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/guix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 156 days old (needed 5 days)
• nanostat (- to 1.4.0-4)
  • Migration status for nanostat (- to 1.4.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nanostat/1.4.0-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nanostat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 156 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• octave-video (- to 2.1.3-1)
  • Migration status for octave-video (- to 2.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating octave-video would introduce bugs in testing: #1103757
    • missing build on ppc64el
    • arch:ppc64el not built yet, autopkgtest delayed there
    • autopkgtest for octave-video/2.1.3-1: amd64: Pass, arm64: Pass, i386: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results on ppc64el - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/octave-video.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 156 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• node-tldts (- to 6.1.85-1)
  • Migration status for node-tldts (- to 6.1.85-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by x.guimard@free.fr, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-tldts.html
    • autopkgtest for node-tldts/6.1.85-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 157 days old (needed 5 days)
• python-goodvibes (- to 3.2+dfsg-6)
  • Migration status for python-goodvibes (- to 3.2+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): python-goodvibes cclib (not considered)
    • Depends: python-goodvibes cclib (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-goodvibes.html
    • autopkgtest for python-goodvibes/3.2+dfsg-6: amd64: Pass, arm64: 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
    • 157 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• fava (- to 1.30.2+dfsg-1)
  • Migration status for fava (- to 1.30.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fava would introduce bugs in testing: #1031724
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fava.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 158 days old (needed 5 days)
• software-properties (- to 0.111-1)
  • Migration status for software-properties (- to 0.111-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating software-properties would introduce bugs in testing: #1038747
    • autopkgtest for software-properties/0.111-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/software-properties.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 158 days old (needed 5 days)
• gittuf (- to 0.9.0-5)
  • Migration status for gittuf (- to 0.9.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gittuf would introduce bugs in testing: #1104384
    • autopkgtest for gittuf/0.9.0-5: amd64: Failed ♻, arm64: Failed ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gittuf.html
    • Reproducible on arm64 - info ♻
    • 159 days old (needed 5 days)
• rust-bitfields (- to 0.12.4-1)
  • Migration status for rust-bitfields (- to 0.12.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-bitfields would introduce bugs in testing: #1103026
    • autopkgtest for rust-bitfields/0.12.4-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-bitfields.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 160 days old (needed 5 days)
• rust-rxml-validation (- to 0.11.0-1)
  • Migration status for rust-rxml-validation (- to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-rxml-validation would introduce bugs in testing: #1103028
    • autopkgtest for rust-rxml-validation/0.11.0-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-rxml-validation.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 160 days old (needed 5 days)
• gvm (- to 25.04.0)
  • Migration status for gvm (- to 25.04.0): 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 ♻
    • 161 days old (needed 5 days)
• iem-plugin-suite (- to 1.15.0-2)
  • Migration status for iem-plugin-suite (- to 1.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iem-plugin-suite would introduce bugs in testing: #1107569
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on s390x
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el, i386, s390x, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iem-plugin-suite.html
    • Reproducible on amd64 - info ♻
    • 161 days old (needed 5 days)
• python-xsdata (- to 24.1-2)
  • Migration status for python-xsdata (- to 24.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-xsdata would introduce bugs in testing: #1114337
    • Build-Depends(-Arch): python-xsdata ruff (not considered)
    • Depends: python-xsdata ruff (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-xsdata.html
    • autopkgtest for python-xsdata/24.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 162 days old (needed 2 days)
• spooles (- to 2.2-14.2)
  • Migration status for spooles (- to 2.2-14.2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • autopkgtest for spooles/2.2-14.2: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for lintian test results on i386, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/spooles.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 162 days old (needed 5 days)
• tcpxtract (- to 1.0.1-18.1)
  • Migration status for tcpxtract (- to 1.0.1-18.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tcpxtract would introduce bugs in testing: #1114402
    • autopkgtest for tcpxtract/1.0.1-18.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tcpxtract.html
    • New but not reproducible on arm64 - info ♻
    • 162 days old (needed 5 days)
• weakforced (- to 2.10.2-2)
  • Migration status for weakforced (- to 2.10.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating weakforced would introduce bugs in testing: #1114440
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/w/weakforced.html
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 162 days old (needed 5 days)
• quickroute-gps (- to 2.5-1)
  • Migration status for quickroute-gps (- to 2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quickroute-gps would introduce bugs in testing: #1110984
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quickroute-gps.html
    • New but not reproducible on arm64 - info ♻
    • 163 days old (needed 5 days)
• linphone-desktop (- to 5.2.6+dfsg-1)
  • Migration status for linphone-desktop (- to 5.2.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating linphone-desktop would introduce bugs in testing: #1102505, #1102669
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linphone-desktop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 164 days old (needed 5 days)
• golang-github-humanlogio-api (- to 0.0~git20250305.fa41d14-1)
  • Migration status for golang-github-humanlogio-api (- to 0.0~git20250305.fa41d14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-humanlogio-api would introduce bugs in testing: #1102683
    • Not built on buildd: arch all binaries uploaded by maytha8thedev@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-humanlogio-api.html
    • autopkgtest for golang-github-humanlogio-api/0.0~git20250305.fa41d14-1: amd64: Pass, arm64: 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
    • 167 days old (needed 2 days)
• rust-potential-utf (- to 0.1.2-1)
  • Migration status for rust-potential-utf (- to 0.1.2-1): Will attempt migration (Any information below is purely informational)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-potential-utf.html
    • autopkgtest for rust-potential-utf/0.1.2-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 167 days old (needed 5 days)
• elasticsearch-curator (- to 8.0.21-1)
  • Migration status for elasticsearch-curator (- to 8.0.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-elasticsearch-curator/amd64 has unsatisfiable dependency
    • python3-elasticsearch-curator/arm64 has unsatisfiable dependency
    • Updating elasticsearch-curator would introduce bugs in testing: #1110793
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/elasticsearch-curator.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 168 days old (needed 5 days)
• smifb2 (- to 2.4.1-1)
  • Migration status for smifb2 (- to 2.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smifb2 would introduce bugs in testing: #1106711
    • autopkgtest for smifb2/2.4.1-1: amd64: Failed ♻, arm64: Failed ♻, i386: No tests, superficial 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/s/smifb2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 168 days old (needed 5 days)
• bluefish (- to 2.2.17-1)
  • Migration status for bluefish (- to 2.2.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bluefish would introduce bugs in testing: #1106625
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bluefish.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 169 days old (needed 5 days)
• ikos (- to 3.5-2)
  • Migration status for ikos (- to 3.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ikos would introduce bugs in testing: #1114149
    • Build-Depends(-Arch): ikos llvm-toolchain-14 (not considered)
    • Depends: ikos llvm-toolchain-14 (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 169 days old (needed 5 days)
• whizzytex (- to 1.5.0-0.1)
  • Migration status for whizzytex (- to 1.5.0-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating whizzytex would introduce bugs in testing: #1102473
    • autopkgtest for whizzytex/1.5.0-0.1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whizzytex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 172 days old (needed 5 days)
• php-horde-editor (- to 2.0.5+debian0-5.1)
  • Migration status for php-horde-editor (- to 2.0.5+debian0-5.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-editor php-horde-browser (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-editor pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-editor php-horde-role
    • Depends: php-horde-editor ckeditor (not considered)
    • Depends: php-horde-editor php-horde-exception (not considered)
    • Depends: php-horde-editor php-horde-serialize (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-editor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 173 days old (needed 5 days)
• php-horde-imp (- to 6.2.27-3.1)
  • Migration status for php-horde-imp (- to 6.2.27-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-imp would introduce bugs in testing: #1038441, #1064391, #1101909, #1102003
    • autopkgtest for php-horde-imp/6.2.27-3.1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-imp pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-imp php-horde-role
    • Depends: php-horde-imp php-horde (not considered)
    • Depends: php-horde-imp php-horde-auth (not considered)
    • Depends: php-horde-imp php-horde-browser
    • Depends: php-horde-imp php-horde-cache (not considered)
    • Depends: php-horde-imp php-horde-compress (not considered)
    • Depends: php-horde-imp php-horde-core (not considered)
    • Depends: php-horde-imp php-horde-crypt (not considered)
    • Depends: php-horde-imp php-horde-css-parser (not considered)
    • Depends: php-horde-imp php-horde-date (not considered)
    • Depends: php-horde-imp php-horde-editor
    • Depends: php-horde-imp php-horde-exception (not considered)
    • Depends: php-horde-imp php-horde-icalendar (not considered)
    • Depends: php-horde-imp php-horde-image (not considered)
    • Depends: php-horde-imp php-horde-imap-client (not considered)
    • Depends: php-horde-imp php-horde-itip (not considered)
    • Depends: php-horde-imp php-horde-listheaders (not considered)
    • Depends: php-horde-imp php-horde-logintasks (not considered)
    • Depends: php-horde-imp php-horde-mail (not considered)
    • Depends: php-horde-imp php-horde-mail-autoconfig (not considered)
    • Depends: php-horde-imp php-horde-mime (not considered)
    • Depends: php-horde-imp php-horde-mime-viewer
    • Depends: php-horde-imp php-horde-nls
    • Depends: php-horde-imp php-horde-notification (not considered)
    • Depends: php-horde-imp php-horde-pack (not considered)
    • Depends: php-horde-imp php-horde-perms (not considered)
    • Depends: php-horde-imp php-horde-spellchecker (not considered)
    • Depends: php-horde-imp php-horde-stream (not considered)
    • Depends: php-horde-imp php-horde-stream-filter (not considered)
    • Depends: php-horde-imp php-horde-stream-wrapper (not considered)
    • Depends: php-horde-imp php-horde-support (not considered)
    • Depends: php-horde-imp php-horde-text-filter (not considered)
    • Depends: php-horde-imp php-horde-text-flowed (not considered)
    • Depends: php-horde-imp php-horde-tree (not considered)
    • Depends: php-horde-imp php-horde-url (not considered)
    • Depends: php-horde-imp php-horde-util (not considered)
    • Depends: php-horde-imp php-horde-vfs (not considered)
    • Depends: php-horde-imp php-horde-view (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-imp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 173 days old (needed 5 days)
• gourmand (- to 1.1.0+really1.1.0-1)
  • Migration status for gourmand (- to 1.1.0+really1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gourmand/amd64 has unsatisfiable dependency
    • gourmand/arm64 has unsatisfiable dependency
    • Updating gourmand would introduce bugs in testing: #1074472, #1103765
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gourmand.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 174 days old (needed 5 days)
• kokkos (- to 4.5.01-1.2)
  • Migration status for kokkos (- to 4.5.01-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kokkos would introduce bugs in testing: #1101487
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kokkos.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 176 days old (needed 5 days)
• unoconv (- to 0.7-2.1)
  • Migration status for unoconv (- to 0.7-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unoconv would introduce bugs in testing: #1087383
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unoconv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 176 days old (needed 5 days)
• mailagent (- to 1:3.1-106-1.2)
  • Migration status for mailagent (- to 1:3.1-106-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mailagent would introduce bugs in testing: #1097355, #1110931
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailagent.html
    • 180 days old (needed 5 days)
    • Remove hint for (transitive) dependency: bcron
• whitakers-words (- to 0.2020.10.27-1.5)
  • Migration status for whitakers-words (- to 0.2020.10.27-1.5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for whitakers-words/0.2020.10.27-1.5: amd64: Pass, arm64: Pass, i386: Failed ♻, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whitakers-words.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 180 days old (needed 5 days)
• pynpoint (- to 0.11.0-4)
  • Migration status for pynpoint (- to 0.11.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pynpoint/amd64 has unsatisfiable dependency
    • python3-pynpoint/arm64 has unsatisfiable dependency
    • 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 i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 184 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• sopv-gpgv (- to 0.1.4-1)
  • Migration status for sopv-gpgv (- to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sopv-gpgv would introduce bugs in testing: #1108757
    • autopkgtest for sopv-gpgv/0.1.4-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sopv-gpgv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 185 days old (needed 5 days)
• psychopy (- to 2023.2.4+dfsg-4)
  • Migration status for psychopy (- to 2023.2.4+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating psychopy would introduce bugs in testing: #1095849, #1102772, #953053
    • autopkgtest for psychopy/2023.2.4+dfsg-4: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/psychopy.html
    • 186 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• freeplane (- to 1.7.10-2)
  • Migration status for freeplane (- to 1.7.10-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: freeplane simplyhtml (not considered)
    • Depends: freeplane simplyhtml (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freeplane.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 187 days old (needed 5 days)
• intel-compute-runtime-legacy (- to 24.35.30872.32-2)
  • Migration status for intel-compute-runtime-legacy (- to 24.35.30872.32-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-compute-runtime-legacy would introduce bugs in testing: #1114152
    • autopkgtest for intel-compute-runtime-legacy/24.35.30872.32-2: amd64: Failed ♻
    • Build-Depends(-Arch): intel-compute-runtime-legacy intel-graphics-compiler (not considered)
    • Depends: intel-compute-runtime-legacy intel-graphics-compiler (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/intel-compute-runtime-legacy.html
    • 187 days old (needed 5 days)
• psi4 (- to 1:1.3.2+dfsg-6)
  • Migration status for psi4 (- to 1:1.3.2+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating psi4 would introduce bugs in testing: #1102525, #1114273
    • autopkgtest for psi4/1:1.3.2+dfsg-6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
    • 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
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 187 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis, libint
• python-redfish (- to 3.2.7-4)
  • Migration status for python-redfish (- to 3.2.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-redfish would introduce bugs in testing: #1093034
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-redfish.html
    • autopkgtest for python-redfish/3.2.7-4: amd64: Pass, arm64: 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
    • 187 days old (needed 2 days)
• rapiddisk (- to 9.2.0-1)
  • Migration status for rapiddisk (- to 9.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rapiddisk would introduce bugs in testing: #1097769, #1109903
    • autopkgtest for rapiddisk/9.2.0-1: amd64: Failed ♻, arm64: Failed ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rapiddisk.html
    • 187 days old (needed 5 days)
• undertow (- to 2.3.18-2)
  • Migration status for undertow (- to 2.3.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating undertow would introduce bugs in testing: #1103966
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/undertow.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 187 days old (needed 5 days)
• chemps2 (- to 1.8.12-4)
  • Migration status for chemps2 (- to 1.8.12-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chemps2 would introduce bugs in testing: #1102362
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chemps2.html
    • autopkgtest for chemps2/1.8.12-4: amd64: Test triggered (failure will be ignored), arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 188 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• mnemosyne (- to 2.11+ds1-2)
  • Migration status for mnemosyne (- to 2.11+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mnemosyne would introduce bugs in testing: #1110972
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mnemosyne.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 188 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• gost-crypto (- to 0.3.5-1.1)
  • Migration status for gost-crypto (- to 0.3.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gost-crypto would introduce bugs in testing: #1109904
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/g/gost-crypto.html
    • autopkgtest for gost-crypto/0.3.5-1.1: amd64: Failed ♻, arm64: Failed ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 189 days old (needed 5 days)
• napari-svg (- to 0.2.1-1)
  • Migration status for napari-svg (- to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating napari-svg would introduce bugs in testing: #1114220
    • autopkgtest for napari-svg/0.2.1-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): napari-svg napari (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/napari-svg.html
    • 189 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• smiles-scripts (- to 0.3.0+svn878+branch+system+deps-2)
  • Migration status for smiles-scripts (- to 0.3.0+svn878+branch+system+deps-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smiles-scripts would introduce bugs in testing: #1106828
    • autopkgtest for smiles-scripts/0.3.0+svn878+branch+system+deps-2: amd64: Pass, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smiles-scripts.html
    • 192 days old (needed 5 days)
• r-cran-broom.helpers (- to 1.20.0-1)
  • Migration status for r-cran-broom.helpers (- to 1.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-broom.helpers/1.20.0-1: amd64: Pass, arm64: Pass, i386: Failed ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Build-Depends(-Arch): r-cran-broom.helpers r-cran-cards (not considered)
    • Depends: r-cran-broom.helpers r-cran-cards (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-broom.helpers.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 194 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• r-cran-sjplot (- to 2.8.17+dfsg-1)
  • Migration status for r-cran-sjplot (- to 2.8.17+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-sjplot r-cran-sjstats (not considered)
    • Depends: r-cran-sjplot r-cran-sjstats (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-sjplot.html
    • autopkgtest for r-cran-sjplot/2.8.17+dfsg-1: amd64: Pass, arm64: 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
    • 194 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• xdg-desktop-portal-hyprland (- to 1.3.8-3)
  • Migration status for xdg-desktop-portal-hyprland (- to 1.3.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xdg-desktop-portal-hyprland would introduce bugs in testing: #1106531
    • Build-Depends(-Arch): xdg-desktop-portal-hyprland hyprland-protocols (not considered)
    • Build-Depends(-Arch): xdg-desktop-portal-hyprland hyprlang (not considered)
    • Build-Depends(-Arch): xdg-desktop-portal-hyprland hyprutils (not considered)
    • Build-Depends(-Arch): xdg-desktop-portal-hyprland hyprwayland-scanner (not considered)
    • Depends: xdg-desktop-portal-hyprland hyprlang (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xdg-desktop-portal-hyprland.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 195 days old (needed 5 days)
• rust-zerovec (- to 0.11.1-1)
  • Migration status for rust-zerovec (- to 0.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-zerovec-dev/amd64 has unsatisfiable dependency
    • librust-zerovec-dev/arm64 has unsatisfiable dependency
    • librust-zerovec-dev/armhf has unsatisfiable dependency
    • librust-zerovec-dev/i386 has unsatisfiable dependency
    • librust-zerovec-dev/ppc64el has unsatisfiable dependency
    • librust-zerovec-dev/riscv64 has unsatisfiable dependency
    • librust-zerovec-dev/s390x has unsatisfiable dependency
    • Updating rust-zerovec would introduce bugs in testing: #1115714
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-zerovec.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 196 days old (needed 5 days)
• iptables-netflow (- to 2.6-7.1)
  • Migration status for iptables-netflow (- to 2.6-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating iptables-netflow would introduce bugs in testing: #1106550
    • autopkgtest for iptables-netflow/2.6-7.1: amd64: Failed ♻, arm64: Failed ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/iptables-netflow.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 197 days old (needed 5 days)
• rust-yoke (- to 0.8.0-1)
  • Migration status for rust-yoke (- to 0.8.0-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/armhf has unsatisfiable dependency
    • librust-yoke-dev/i386 has unsatisfiable dependency
    • librust-yoke-dev/ppc64el has unsatisfiable dependency
    • librust-yoke-dev/riscv64 has unsatisfiable dependency
    • librust-yoke-dev/s390x has unsatisfiable dependency
    • Updating rust-yoke would introduce bugs in testing: #1073151
  • 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 i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 197 days old (needed 5 days)
• sight (- to 25.0.0-1)
  • Migration status for sight (- to 25.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sight would introduce bugs in testing: #1097881, #1111550
    • Impossible Depends: sight -> libopenigtlink1.11/1.11.0-6/amd64
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sight.html
    • Waiting for reproducibility test results on arm64 - info ♻
    • 201 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• singularity-container (- to 4.1.5+ds4-1)
  • Migration status for singularity-container (- to 4.1.5+ds4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating singularity-container would introduce bugs in testing: #1029669, #1101692, #1102938
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/singularity-container.html
    • 204 days old (needed 5 days)
• lava (- to 2024.09-1.1)
  • Migration status for lava (- to 2024.09-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for lava/2024.09-1.1: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lava.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 209 days old (needed 5 days)
    • Remove hint for (transitive) dependency: netkit-telnet-ssl
• paraview (- to 5.13.2+dfsg-3)
  • Migration status for paraview (- to 5.13.2+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating paraview would introduce bugs in testing: #1114253
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/paraview.html
    • autopkgtest for paraview/5.13.2+dfsg-3: amd64: Pass, arm64: Pass, i386: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 212 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• python-gassist-text (- to 0.0.11-1)
  • Migration status for python-gassist-text (- to 0.0.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-gassist-text.html
    • autopkgtest for python-gassist-text/0.0.11-1: amd64: Pass, arm64: 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
    • 213 days old (needed 2 days)
• circlator (- to 1.5.6-13)
  • Migration status for circlator (- to 1.5.6-13): 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 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-13: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 215 days old (needed 2 days)
• protontricks (- to 1.12.0-2)
  • Migration status for protontricks (- to 1.12.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for protontricks/1.12.0-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, 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)
    • 216 days old (needed 5 days)
• nat-rtsp (- to 0.7+5.3-0.4)
  • Migration status for nat-rtsp (- to 0.7+5.3-0.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nat-rtsp would introduce bugs in testing: #1088903
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nat-rtsp.html
    • autopkgtest for nat-rtsp/0.7+5.3-0.4: 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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 217 days old (needed 5 days)
• labelme (- to 5.6.1-1)
  • Migration status for labelme (- to 5.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating labelme would introduce bugs in testing: #1085797
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/labelme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 219 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• basemap (- to 1.4.1-1)
  • Migration status for basemap (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating basemap would introduce bugs in testing: #1110711
    • autopkgtest for basemap/1.4.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/basemap.html
    • 221 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• jaraco.stream (- to 3.0.4-1)
  • Migration status for jaraco.stream (- to 3.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Not built on buildd: arch all binaries uploaded by ben@benfinney.id.au, a new source-only upload is needed to allow migration
    • Build-Depends-Indep: jaraco.stream ruff (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jaraco.stream.html
    • autopkgtest for jaraco.stream/3.0.4-1: amd64: Pass, arm64: 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
    • 222 days old (needed 2 days)
• r-cran-gstat (- to 2.1-3-1)
  • Migration status for r-cran-gstat (- to 2.1-3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-gstat/2.1-3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gstat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 222 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• rust-ryu-js (- to 1.0.1-1)
  • Migration status for rust-ryu-js (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-ryu-js/1.0.1-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ryu-js.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 222 days old (needed 5 days)
• wasix-libc (- to 2024.07.08.1+ds-1)
  • Migration status for wasix-libc (- to 2024.07.08.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating wasix-libc would introduce bugs in testing: #1103497
    • wasix-libc unsatisfiable Build-Depends(-Arch) on amd64: clang-16
    • wasix-libc unsatisfiable Build-Depends(-Arch) on amd64: llvm-16
    • wasix-libc unsatisfiable Build-Depends(-Arch) on amd64: libclang-rt-16-dev-wasm32
    • Not built on buildd: arch amd64 binaries uploaded by onlyjob@member.fsf.org
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/wasix-libc.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 222 days old (needed 5 days)
• bdebstrap (- to 0.7.0-2)
  • Migration status for bdebstrap (- to 0.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bdebstrap would introduce bugs in testing: #1098877
    • autopkgtest for bdebstrap/0.7.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bdebstrap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 225 days old (needed 5 days)
• check-all-the-things (- to 2025.02.06)
  • Migration status for check-all-the-things (- to 2025.02.06): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating check-all-the-things would introduce bugs in testing: #1112174, #862378
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/check-all-the-things.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 225 days old (needed 5 days)
• libjpeg9 (- to 1:9f-2)
  • Migration status for libjpeg9 (- to 1:9f-2): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 225 days old (needed 5 days)
• vpb-driver (- to 4.2.61-1.7)
  • Migration status for vpb-driver (- to 4.2.61-1.7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vpb-driver would introduce bugs in testing: #1095278
    • autopkgtest for vpb-driver/4.2.61-1.7: amd64: Failed ♻, arm64: Failed ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vpb-driver.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 226 days old (needed 5 days)
• python-aioraven (- to 0.7.0-1)
  • Migration status for python-aioraven (- to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-aioraven/amd64 has unsatisfiable dependency
    • python3-aioraven/arm64 has unsatisfiable dependency
    • Updating python-aioraven would introduce bugs in testing: #1103495
    • python-aioraven unsatisfiable Build-Depends-Indep on amd64: python3-iso4217
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-aioraven.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 227 days old (needed 5 days)
• scrcpy (- to 1.25-1.1)
  • Migration status for scrcpy (- to 1.25-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for scrcpy/1.25-1.1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • scrcpy unsatisfiable Build-Depends-Indep on amd64: dalvik-exchange
    • Build-Depends-Indep: scrcpy android-framework-23 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scrcpy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 227 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• openafs (- to 1.8.13.2-1)
  • Migration status for openafs (- to 1.8.13.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openafs would introduce bugs in testing: #1097511, #1104420, #1112682
    • autopkgtest for openafs/1.8.13.2-1: amd64: Failed ♻, arm64: Failed ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openafs.html
    • New but not reproducible on arm64 - info ♻
    • 232 days old (needed 5 days)
• r-cran-effectsize (- to 1.0.0+dfsg-1)
  • Migration status for r-cran-effectsize (- to 1.0.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-bayestestr/0.15.2-1: amd64: Pass, arm64: Pass, i386: Test triggered (failure will be ignored), ppc64el: Pass, riscv64: Pass, s390x: Pass
    • autopkgtest for r-cran-effectsize/1.0.0+dfsg-1: amd64: Pass, arm64: Pass, i386: Failed ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-effectsize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 232 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• camo (- to 2.3.0+dfsg-3)
  • Migration status for camo (- to 2.3.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating camo would introduce bugs in testing: #1094548
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 233 days old (needed 5 days)
• python-molotov (- to 2.7-2)
  • Migration status for python-molotov (- to 2.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-molotov would introduce bugs in testing: #1102543
    • autopkgtest for python-molotov/2.7-2: amd64: Pass, arm64: Pass, i386: Failed ♻, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-molotov.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 233 days old (needed 5 days)
• fortunes-es (- to 1.36+nmu1)
  • Migration status for fortunes-es (- to 1.36+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fortunes-es would introduce bugs in testing: #1109166
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fortunes-es.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 236 days old (needed 5 days)
• xperia-flashtool (- to 0.9.34+ds-2)
  • Migration status for xperia-flashtool (- to 0.9.34+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): xperia-flashtool jarchivelib (not considered)
    • Depends: xperia-flashtool jarchivelib (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xperia-flashtool.html
    • uninstallable on arch 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 ♻
    • 237 days old (needed 5 days)
• rust-pdb-addr2line (- to 0.11.1-1)
  • Migration status for rust-pdb-addr2line (- to 0.11.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-pdb-addr2line rust-pdb2 (not considered)
    • Depends: rust-pdb-addr2line rust-pdb2 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pdb-addr2line.html
    • autopkgtest for rust-pdb-addr2line/0.11.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial 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 ♻
    • 239 days old (needed 5 days)
• rust-pdb2 (- to 0.9.1-1)
  • Migration status for rust-pdb2 (- to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-pdb2 would introduce bugs in testing: #1102550
    • autopkgtest for rust-pdb2/0.9.1-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pdb2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 239 days old (needed 5 days)
• openjdk-23 (- to 23.0.2+7-1)
  • Migration status for openjdk-23 (- to 23.0.2+7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-23 would introduce bugs in testing: #1078198, #1100335
    • 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/o/openjdk-23.html
    • autopkgtest for bbmap/39.20+dfsg-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Pass, i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for openjdk-23/23.0.2+7-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Reproducible on amd64 - info ♻
    • 241 days old (needed 5 days)
• odoo (- to 18.0.0+dfsg-2)
  • Migration status for odoo (- to 18.0.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating odoo would introduce bugs in testing: #1104455
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/odoo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 242 days old (needed 5 days)
• hyprland (- to 0.41.2+ds-1.3)
  • Migration status for hyprland (- to 0.41.2+ds-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hyprland would introduce bugs in testing: #1094632
    • Build-Depends(-Arch): hyprland hyprland-protocols (not considered)
    • Build-Depends(-Arch): hyprland hyprlang (not considered)
    • Build-Depends(-Arch): hyprland hyprutils (not considered)
    • Build-Depends(-Arch): hyprland hyprwayland-scanner (not considered)
    • Build-Depends(-Arch): hyprland libhyprcursor (not considered)
    • Depends: hyprland hyprlang (not considered)
    • Depends: hyprland hyprutils (not considered)
    • Depends: hyprland libhyprcursor (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hyprland.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 243 days old (needed 5 days)
• libpsml (- to 2.0.1-2)
  • Migration status for libpsml (- to 2.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpsml would introduce bugs in testing: #1071043
    • libpsml unsatisfiable Build-Depends(-Arch) on amd64: libxmlf90-dev
    • missing build on amd64
    • arch:amd64 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on amd64 - info
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libp/libpsml.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 243 days old (needed 5 days)
• mu-editor (- to 1.2.0+dfsg-2)
  • Migration status for mu-editor (- to 1.2.0+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): mu-editor python-uflash (not considered)
    • Depends: mu-editor python-uflash (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mu-editor.html
    • autopkgtest for mu-editor/1.2.0+dfsg-2: amd64: Pass, arm64: Pass, 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
    • 243 days old (needed 2 days)
• watchman (- to 4.9.0-8)
  • Migration status for watchman (- to 4.9.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • watchman/amd64 has unsatisfiable dependency
    • watchman/arm64 has unsatisfiable dependency
    • watchman/armhf has unsatisfiable dependency
    • watchman/i386 has unsatisfiable dependency
    • watchman/ppc64el has unsatisfiable dependency
    • watchman/riscv64 has unsatisfiable dependency
    • Updating watchman would introduce bugs in testing: #999930
    • watchman unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • watchman unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/watchman.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 243 days old (needed 5 days)
• amgcl (- to 1.4.4-1)
  • Migration status for amgcl (- to 1.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • amgcl unsatisfiable Build-Depends(-Arch) on i386: libopenmpi-dev
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on i386 - info
    • Build-Depends(-Arch): amgcl parmetis (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 249 days old (needed 5 days)
• radare2 (- to 5.9.8+dfsg-2)
  • Migration status for radare2 (- to 5.9.8+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating radare2 would introduce bugs in testing: #950372
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/radare2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 249 days old (needed 5 days)
• mailsync (- to 5.2.7-3.3)
  • Migration status for mailsync (- to 5.2.7-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mailsync would introduce bugs in testing: #1092645
    • Build-Depends(-Arch): mailsync uw-imap (not considered)
    • Depends: mailsync uw-imap (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mailsync.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 254 days old (needed 5 days)
• rust-utmp-classic (- to 0.1.6-1)
  • Migration status for rust-utmp-classic (- to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-utmp-classic-dev/amd64 has unsatisfiable dependency
    • librust-utmp-classic-dev/arm64 has unsatisfiable dependency
    • librust-utmp-classic-dev/armhf has unsatisfiable dependency
    • librust-utmp-classic-dev/i386 has unsatisfiable dependency
    • librust-utmp-classic-dev/ppc64el has unsatisfiable dependency
    • librust-utmp-classic-dev/riscv64 has unsatisfiable dependency
    • librust-utmp-classic-dev/s390x has unsatisfiable dependency
    • Updating rust-utmp-classic would introduce bugs in testing: #1111992
    • rust-utmp-classic unsatisfiable Build-Depends(-Arch) on amd64: librust-zerocopy-0.7+default-dev (>= 0.7.34-~~)
    • rust-utmp-classic unsatisfiable Build-Depends(-Arch) on arm64: librust-zerocopy-0.7+default-dev (>= 0.7.34-~~)
    • rust-utmp-classic unsatisfiable Build-Depends(-Arch) on armhf: librust-zerocopy-0.7+default-dev (>= 0.7.34-~~)
    • rust-utmp-classic unsatisfiable Build-Depends(-Arch) on i386: librust-zerocopy-0.7+default-dev (>= 0.7.34-~~)
    • rust-utmp-classic unsatisfiable Build-Depends(-Arch) on ppc64el: librust-zerocopy-0.7+default-dev (>= 0.7.34-~~)
    • rust-utmp-classic unsatisfiable Build-Depends(-Arch) on riscv64: librust-zerocopy-0.7+default-dev (>= 0.7.34-~~)
    • rust-utmp-classic unsatisfiable Build-Depends(-Arch) on s390x: librust-zerocopy-0.7+default-dev (>= 0.7.34-~~)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-utmp-classic.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 254 days old (needed 5 days)
• homer-api (- to 5.0.6+dfsg2-3.3)
  • Migration status for homer-api (- to 5.0.6+dfsg2-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • homer-api/amd64 has unsatisfiable dependency
    • homer-api/arm64 has unsatisfiable dependency
    • homer-api/armhf has unsatisfiable dependency
    • homer-api/i386 has unsatisfiable dependency
    • homer-api/ppc64el has unsatisfiable dependency
    • homer-api/riscv64 has unsatisfiable dependency
    • homer-api/s390x has unsatisfiable dependency
    • Updating homer-api would introduce bugs in testing: #1095931
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/homer-api.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 255 days old (needed 5 days)
• rust-clap-complete-nushell (- to 4.5.4-1)
  • Migration status for rust-clap-complete-nushell (- to 4.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librust-clap-complete-nushell-dev/amd64 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/arm64 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/armhf has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/i386 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/ppc64el has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/riscv64 has unsatisfiable dependency
    • librust-clap-complete-nushell-dev/s390x has unsatisfiable dependency
    • Updating rust-clap-complete-nushell would introduce bugs in testing: #1092486
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/r/rust-clap-complete-nushell.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 255 days old (needed 5 days)
• mender-connect (- to 2.3.0+ds1-1)
  • Migration status for mender-connect (- to 2.3.0+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mender-connect would introduce bugs in testing: #1102246
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mender-connect.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 258 days old (needed 5 days)
• openjdk-22 (- to 22.0.2+9-5)
  • Migration status for openjdk-22 (- to 22.0.2+9-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openjdk-22 would introduce bugs in testing: #1040771
    • 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/o/openjdk-22.html
    • autopkgtest for bbmap/39.20+dfsg-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • autopkgtest for libreoffice/4:25.8.1-1: amd64: Pass, arm64: Pass, i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • autopkgtest for openjdk-22/22.0.2+9-5: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • Reproducible on amd64 - info ♻
    • 258 days old (needed 5 days)
• deepboof (- to 0.5.1+ds-2)
  • Migration status for deepboof (- to 0.5.1+ds-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): deepboof jarchivelib (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/deepboof.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 260 days old (needed 5 days)
• gcc-11-cross-ports (- to 19)
  • Migration status for gcc-11-cross-ports (- to 19): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: gcc-11-cross-ports hsail-tools (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): gcc-11-cross-ports gcc-11 (not considered)
    • Built-Using: gcc-11-cross-ports gcc-11 (not considered)
    • Depends: gcc-11-cross-ports gcc-11 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11-cross-ports.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 260 days old (needed 5 days)
• tt-rss (- to 21~git20210204.b4cbc79+dfsg-2)
  • Migration status for tt-rss (- to 21~git20210204.b4cbc79+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tt-rss would introduce bugs in testing: #1021656, #1054608
    • Depends: tt-rss php-gettext (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tt-rss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 261 days old (needed 5 days)
• rust-netlink-packet-wireguard (- to 0.2.3-2)
  • Migration status for rust-netlink-packet-wireguard (- to 0.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-netlink-packet-wireguard/0.2.3-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-netlink-packet-wireguard.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 262 days old (needed 5 days)
• rlottie-qml (- to 0.1~git20240610.022644c-2)
  • Migration status for rlottie-qml (- to 0.1~git20240610.022644c-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rlottie-qml rlottie (not considered)
    • Depends: rlottie-qml rlottie (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rlottie-qml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 263 days old (needed 5 days)
• uw-imap (- to 8:2007f~dfsg-7.1)
  • Migration status for uw-imap (- to 8:2007f~dfsg-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating uw-imap would introduce bugs in testing: #1063040, #1091778, #1110233, #1114427
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/uw-imap.html
    • 263 days old (needed 5 days)
• golang-github-notaryproject-notation (- to 1.2.0-4)
  • Migration status for golang-github-notaryproject-notation (- to 1.2.0-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): golang-github-notaryproject-notation golang-github-notaryproject-notation-go (not considered)
    • Built-Using: golang-github-notaryproject-notation golang-github-notaryproject-notation-go (not considered)
    • Depends: golang-github-notaryproject-notation golang-github-notaryproject-notation-go (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/golang-github-notaryproject-notation.html
    • autopkgtest for golang-github-notaryproject-notation/1.2.0-4: amd64: Pass, arm64: 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
    • 268 days old (needed 2 days)
• php-codesniffer (- to 3.11.2-2)
  • Migration status for php-codesniffer (- to 3.11.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-codesniffer would introduce bugs in testing: #1092009
    • autopkgtest for php-codesniffer/3.11.2-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-codesniffer.html
    • 270 days old (needed 5 days)
• crystal (- to 1.14.0+dfsg-1)
  • Migration status for crystal (- to 1.14.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating crystal would introduce bugs in testing: #1107235
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/crystal.html
    • 273 days old (needed 5 days)
• pyrr (- to 0.10.3-7)
  • Migration status for pyrr (- to 0.10.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyrr would introduce bugs in testing: #1095085
    • autopkgtest for pyrr/0.10.3-7: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyrr.html
    • 273 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• request-tracker4 (- to 4.4.7+dfsg-4)
  • Migration status for request-tracker4 (- to 4.4.7+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating request-tracker4 would introduce bugs in testing: #1030749, #1103555, #1104424
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/request-tracker4.html
    • autopkgtest for request-tracker4/4.4.7+dfsg-4: 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 ♻
    • 273 days old (needed 5 days)
    • Remove hint for (transitive) dependency: bcron
• shards (- to 0.19.0-1)
  • Migration status for shards (- 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): shards crystal (not considered)
    • Depends: shards crystal (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shards.html
    • Reproducible on amd64 - info ♻
    • 273 days old (needed 5 days)
• python-dtcwt (- to 0.14.0-1)
  • Migration status for python-dtcwt (- to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-dtcwt would introduce bugs in testing: #1095371
    • autopkgtest for python-dtcwt/0.14.0-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-dtcwt.html
    • 274 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• libjpeg6b (- to 1:6b2-4)
  • Migration status for libjpeg6b (- to 1:6b2-4): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
  • Issues preventing migration:
    • Not touching package due to block request by elbrus (please contact debian-release if update is needed)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libj/libjpeg6b.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 275 days old (needed 5 days)
• nanook (- to 1.33+dfsg-6)
  • Migration status for nanook (- to 1.33+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nanook/1.33+dfsg-6: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nanook.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 275 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• camping (- to 2.3-2)
  • Migration status for camping (- to 2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating camping would introduce bugs in testing: #1094532
    • autopkgtest for camping/2.3-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/camping.html
    • 277 days old (needed 5 days)
• git-ubuntu (- to 1.1-2)
  • Migration status for git-ubuntu (- to 1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating git-ubuntu would introduce bugs in testing: #1103013
    • autopkgtest for git-ubuntu/1.1-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-ubuntu.html
    • 278 days old (needed 5 days)
• ruby-reverse-markdown (- to 3.0.0-1)
  • Migration status for ruby-reverse-markdown (- to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-reverse-markdown would introduce bugs in testing: #1107540
    • autopkgtest for ruby-reverse-markdown/3.0.0-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-reverse-markdown.html
    • 278 days old (needed 5 days)
• mosdepth (- to 0.3.10+ds-1)
  • Migration status for mosdepth (- to 0.3.10+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mosdepth would introduce bugs in testing: #1112654
    • Build-Depends(-Arch): mosdepth nim (not considered)
    • Build-Depends(-Arch): mosdepth nim-docopt (not considered)
    • Build-Depends(-Arch): mosdepth nim-hts (not considered)
    • Build-Depends(-Arch): mosdepth nim-regex (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mosdepth.html
    • autopkgtest for mosdepth/0.3.10+ds-1: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻
    • 280 days old (needed 5 days)
• sia (- to 1.3.0-4)
  • Migration status for sia (- to 1.3.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sia would introduce bugs in testing: #1089970, #1104575
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sia.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 282 days old (needed 5 days)
• umis (- to 1.0.9-2)
  • Migration status for umis (- to 1.0.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating umis would introduce bugs in testing: #1089115
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/umis.html
    • autopkgtest for umis/1.0.9-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 282 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• readucks (- to 0.0.3-6)
  • Migration status for readucks (- to 0.0.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for readucks/0.0.3-6: amd64: Pass, arm64: Failed ♻, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/readucks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 283 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• pbsuite (- to 15.8.24+dfsg-8)
  • Migration status for pbsuite (- to 15.8.24+dfsg-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pbsuite would introduce bugs in testing: #1091721
    • autopkgtest for pbsuite/15.8.24+dfsg-8: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pbsuite.html
    • 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 ♻
    • 284 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• apt-build (- to 0.12.51)
  • Migration status for apt-build (- to 0.12.51): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apt-build would introduce bugs in testing: #1108698
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt-build.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 285 days old (needed 5 days)
• resteasy (- to 3.6.2-3)
  • Migration status for resteasy (- to 3.6.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating resteasy would introduce bugs in testing: #879469
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resteasy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 285 days old (needed 5 days)
• python-aiobotocore (- to 2.13.1-1.1)
  • Migration status for python-aiobotocore (- to 2.13.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiobotocore would introduce bugs in testing: #1091485
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on all - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiobotocore.html
    • 286 days old (needed 5 days)
• open-adventure (- to 1.20-1)
  • Migration status for open-adventure (- to 1.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating open-adventure would introduce bugs in testing: #1091064
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open-adventure.html
    • 287 days old (needed 5 days)
• ppc64-diag (- to 2.7.9-1.1)
  • Migration status for ppc64-diag (- to 2.7.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): ppc64-diag libvpd (not considered)
    • Invalidated by build-dependency
    • Depends: ppc64-diag lsvpd
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 287 days old (needed 5 days)
• libvirt-php (- to 0.5.8-7)
  • Migration status for libvirt-php (- to 0.5.8-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libvirt-php would introduce bugs in testing: #1106642
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libv/libvirt-php.html
    • Reproducible on arm64 - info ♻
    • 289 days old (needed 5 days)
• pushpin (- to 1.39.1-3)
  • Migration status for pushpin (- to 1.39.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pushpin would introduce bugs in testing: #1084517
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results on s390x - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pushpin.html
    • 290 days old (needed 5 days)
• intel-graphics-compiler (- to 1.0.17791.18-1)
  • Migration status for intel-graphics-compiler (- to 1.0.17791.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating intel-graphics-compiler would introduce bugs in testing: #1061213, #1114153
    • 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
    • 291 days old (needed 5 days)
• nim-hts (- to 0.3.25+ds-2)
  • Migration status for nim-hts (- to 0.3.25+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nim-hts would introduce bugs in testing: #1112655
    • Build-Depends(-Arch): nim-hts nim (not considered)
    • Depends: nim-hts nim (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-hts.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for nim-hts/0.3.25+ds-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 291 days old (needed 2 days)
• php-imap (- to 3:1.0.3-1)
  • Migration status for php-imap (- to 3:1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-imap would introduce bugs in testing: #1092646
    • Build-Depends(-Arch): php-imap uw-imap (not considered)
    • Depends: php-imap uw-imap (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-imap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 291 days old (needed 5 days)
• python-easyenergy (- to 2.1.2-1)
  • Migration status for python-easyenergy (- to 2.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-easyenergy would introduce bugs in testing: #1088925
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-easyenergy.html
    • autopkgtest for python-easyenergy/2.1.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 291 days old (needed 2 days)
• hts-nim-tools (- to 0.2.1-2)
  • Migration status for hts-nim-tools (- to 0.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hts-nim-tools would introduce bugs in testing: #1112653
    • Build-Depends(-Arch): hts-nim-tools nim (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-docopt (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-hts (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-kexpr (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-lapper (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-regex (not considered)
    • Build-Depends(-Arch): hts-nim-tools nim-unicodedb
    • Build-Depends(-Arch): hts-nim-tools nim-unicodeplus
    • Depends: hts-nim-tools nim-hts (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hts-nim-tools.html
    • autopkgtest for hts-nim-tools/0.2.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 292 days old (needed 2 days)
• eye (- to 1:10.30.11~ds-1)
  • Migration status for eye (- to 1:10.30.11~ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eye would introduce bugs in testing: #1088839
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eye.html
    • autopkgtest for eye/1:10.30.11~ds-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 294 days old (needed 2 days)
• fotoxx (- to 24.70-1)
  • Migration status for fotoxx (- to 24.70-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fotoxx would introduce bugs in testing: #1018121
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fotoxx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 294 days old (needed 5 days)
• tinydyndns (- to 0.4.2.debian1-4)
  • Migration status for tinydyndns (- to 0.4.2.debian1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tinydyndns would introduce bugs in testing: #1090038
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • 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: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
    • Waiting for lintian test results on ppc64el, amd64, arm64, i386, s390x, riscv64, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tinydyndns.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 296 days old (needed 5 days)
• dadadodo (- to 1.04-10)
  • Migration status for dadadodo (- to 1.04-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for dadadodo/1.04-10: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dadadodo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 300 days old (needed 5 days)
• vg (- to 1.59.0+ds-0.1)
  • Migration status for vg (- to 1.59.0+ds-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vg would introduce bugs in testing: #1089275
    • autopkgtest for vg/1.59.0+ds-0.1: amd64: Failed ♻, arm64: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vg.html
    • 300 days old (needed 5 days)
• iconnect-tools (- to 0.1+nmu1)
  • Migration status for iconnect-tools (- to 0.1+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • iconnect-tools has no binaries on any arch
    • nothing built yet, autopkgtest delayed
    • nothing built yet, lintian delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 301 days old (needed 5 days)
• python-androidtv (- to 0.0.73-1.1)
  • Migration status for python-androidtv (- to 0.0.73-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: python-androidtv python-adb-shell (not considered)
    • Depends: python-androidtv python-adb-shell (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-androidtv.html
    • autopkgtest for python-androidtv/0.0.73-1.1: amd64: Pass, arm64: Pass, 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
    • 301 days old (needed 2 days)
• cpm (- to 0.32-1.6)
  • Migration status for cpm (- to 0.32-1.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cpm would introduce bugs in testing: #1106610
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cpm.html
    • 302 days old (needed 5 days)
• slic3r (- to 1.3.0+dfsg1-5.1)
  • Migration status for slic3r (- to 1.3.0+dfsg1-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating slic3r would introduce bugs in testing: #1034848
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slic3r.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 303 days old (needed 5 days)
• gpsim-doc (- to 0.22.0-8)
  • Migration status for gpsim-doc (- to 0.22.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gpsim-doc would introduce bugs in testing: #1093332
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gpsim-doc.html
    • autopkgtest for gpsim-doc/0.22.0-8: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 304 days old (needed 2 days)
• python-pysnmp-lextudio (- to 5.0.26-4)
  • Migration status for python-pysnmp-lextudio (- to 5.0.26-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pysnmp-lextudio/amd64 has unsatisfiable dependency
    • python3-pysnmp-lextudio/arm64 has unsatisfiable dependency
    • Updating python-pysnmp-lextudio would introduce bugs in testing: #1100189, #1101588
    • python-pysnmp-lextudio unsatisfiable Build-Depends-Indep on amd64: python3-pysnmp-pysmi
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pysnmp-lextudio.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 305 days old (needed 5 days)
• ruby-proc-to-ast (- to 0.2.0-1)
  • Migration status for ruby-proc-to-ast (- to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-proc-to-ast ruby-unparser (not considered)
    • Depends: ruby-proc-to-ast ruby-unparser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-proc-to-ast.html
    • autopkgtest for ruby-proc-to-ast/0.2.0-1: amd64: Pass, arm64: Pass, 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
    • 306 days old (needed 2 days)
• prewikka (- to 5.2.0-2.3)
  • Migration status for prewikka (- to 5.2.0-2.3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: prewikka libpreludedb (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prewikka.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 307 days old (needed 5 days)
• ruby-unparser (- to 0.6.13-1)
  • Migration status for ruby-unparser (- to 0.6.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-unparser would introduce bugs in testing: #1095009
    • autopkgtest for ruby-unparser/0.6.13-1: amd64: Pass, arm64: Pass, i386: Failed ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-unparser.html
    • 307 days old (needed 5 days)
• heudiconv (- to 1.3.2-1)
  • Migration status for heudiconv (- to 1.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 310 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• gensim (- to 4.3.3+dfsg-2)
  • Migration status for gensim (- to 4.3.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-gensim/amd64 has unsatisfiable dependency
    • python3-gensim/arm64 has unsatisfiable dependency
    • python3-gensim/armhf has unsatisfiable dependency
    • python3-gensim/i386 has unsatisfiable dependency
    • python3-gensim/ppc64el has unsatisfiable dependency
    • python3-gensim/riscv64 has unsatisfiable dependency
    • python3-gensim/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): gensim pyemd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gensim.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 313 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• node-zrender (- to 5.4.1+dfsg-2)
  • Migration status for node-zrender (- to 5.4.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-zrender would introduce bugs in testing: #1090025, #1114233
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-zrender.html
    • autopkgtest for node-zrender/5.4.1+dfsg-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 314 days old (needed 2 days)
• golang-github-vulcand-oxy (- to 2.0.0-3)
  • Migration status for golang-github-vulcand-oxy (- to 2.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-vulcand-oxy/2.0.0-3: amd64: Pass, arm64: Pass, i386: Failed ♻, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-vulcand-oxy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 316 days old (needed 5 days)
• rust-num-prime (- to 0.4.4-2)
  • Migration status for rust-num-prime (- to 0.4.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for rust-num-prime/0.4.4-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-num-prime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 321 days old (needed 5 days)
• ruby-rspec-parameterized-table-syntax (- to 1.0.1-1.1)
  • Migration status for ruby-rspec-parameterized-table-syntax (- to 1.0.1-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core (not considered)
    • Depends: ruby-rspec-parameterized-table-syntax ruby-rspec-parameterized-core (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized-table-syntax.html
    • autopkgtest for ruby-rspec-parameterized-table-syntax/1.0.1-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial 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 ♻
    • 323 days old (needed 5 days)
• nvidia-settings-tesla-470 (- to 470.256.02-1)
  • Migration status for nvidia-settings-tesla-470 (- to 470.256.02-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-tesla-470 nvidia-graphics-drivers-tesla-470 (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 325 days old (needed 5 days)
• rust-pprof (- to 0.13.0-5)
  • Migration status for rust-pprof (- to 0.13.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-pprof would introduce bugs in testing: #1103252
    • Depends: rust-pprof rust-protobuf (not considered)
    • Depends: rust-pprof rust-protobuf-codegen-pure
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-pprof.html
    • autopkgtest for rust-pprof/0.13.0-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 328 days old (needed 5 days)
• cecilia (- to 5.4.1-3)
  • Migration status for cecilia (- to 5.4.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cecilia would introduce bugs in testing: #1089034
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cecilia.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 331 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• tcm (- to 2.20+TSQD-8)
  • Migration status for tcm (- to 2.20+TSQD-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tcm would introduce bugs in testing: #1076222
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tcm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 334 days old (needed 5 days)
• haskell-lambdabot-novelty-plugins (- to 5.3.1.2-1)
  • Migration status for haskell-lambdabot-novelty-plugins (- to 5.3.1.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-lambdabot-novelty-plugins haskell-misfortune (not considered)
    • Build-Depends-Indep: haskell-lambdabot-novelty-plugins haskell-misfortune (not considered)
    • Depends: haskell-lambdabot-novelty-plugins haskell-misfortune (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-lambdabot-novelty-plugins.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 335 days old (needed 5 days)
• haskell-misfortune (- to 0.1.2.1-4)
  • Migration status for haskell-misfortune (- to 0.1.2.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • haskell-misfortune/amd64 has unsatisfiable dependency
    • haskell-misfortune/arm64 has unsatisfiable dependency
    • haskell-misfortune/armhf has unsatisfiable dependency
    • haskell-misfortune/i386 has unsatisfiable dependency
    • haskell-misfortune/ppc64el has unsatisfiable dependency
    • haskell-misfortune/riscv64 has unsatisfiable dependency
    • haskell-misfortune/s390x has unsatisfiable dependency
    • Updating haskell-misfortune would introduce bugs in testing: #1061618
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on amd64: libghc-regex-pcre-dev
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on amd64: libghc-regex-pcre-prof
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on arm64: libghc-regex-pcre-dev
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on arm64: libghc-regex-pcre-prof
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on armhf: libghc-regex-pcre-dev
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on armhf: libghc-regex-pcre-prof
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on i386: libghc-regex-pcre-dev
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on i386: libghc-regex-pcre-prof
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-regex-pcre-dev
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on ppc64el: libghc-regex-pcre-prof
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on riscv64: libghc-regex-pcre-dev
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on riscv64: libghc-regex-pcre-prof
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on s390x: libghc-regex-pcre-dev
    • haskell-misfortune unsatisfiable Build-Depends(-Arch) on s390x: libghc-regex-pcre-prof
    • haskell-misfortune unsatisfiable Build-Depends-Indep on amd64: libghc-regex-pcre-doc
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-misfortune.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 335 days old (needed 5 days)
• lambdabot (- to 5.3.1.2-1)
  • Migration status for lambdabot (- to 5.3.1.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lambdabot haskell-lambdabot-novelty-plugins (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lambdabot.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 335 days old (needed 5 days)
• gitit (- to 0.15.1.2+dfsg-1)
  • Migration status for gitit (- to 0.15.1.2+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-gitit-dev/amd64 has unsatisfiable dependency
    • libghc-gitit-prof/amd64 has unsatisfiable dependency
    • libghc-gitit-dev/arm64 has unsatisfiable dependency
    • libghc-gitit-prof/arm64 has unsatisfiable dependency
    • libghc-gitit-dev/armhf has unsatisfiable dependency
    • libghc-gitit-prof/armhf has unsatisfiable dependency
    • libghc-gitit-dev/i386 has unsatisfiable dependency
    • libghc-gitit-prof/i386 has unsatisfiable dependency
    • libghc-gitit-dev/ppc64el has unsatisfiable dependency
    • libghc-gitit-prof/ppc64el has unsatisfiable dependency
    • libghc-gitit-dev/riscv64 has unsatisfiable dependency
    • libghc-gitit-prof/riscv64 has unsatisfiable dependency
    • libghc-gitit-dev/s390x has unsatisfiable dependency
    • libghc-gitit-prof/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): gitit haskell-hoauth2
    • Build-Depends-Indep: gitit haskell-hoauth2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitit.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 339 days old (needed 5 days)
• tup (- to 0.8-1)
  • Migration status for tup (- to 0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tup would introduce bugs in testing: #1108538
    • autopkgtest for tup/0.8-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tup.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 340 days old (needed 5 days)
• haskell-hledger-web (- to 1.32.3-1)
  • Migration status for haskell-hledger-web (- to 1.32.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-hledger-web haskell-base64 (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hledger-web.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 342 days old (needed 5 days)
• haskell-hoauth2 (- to 2.10.0-1)
  • Migration status for haskell-hoauth2 (- to 2.10.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): haskell-hoauth2 haskell-base64 (not considered)
    • Build-Depends-Indep: haskell-hoauth2 haskell-base64 (not considered)
    • Depends: haskell-hoauth2 haskell-base64 (not considered)
    • Invalidated by build-dependency
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-hoauth2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 343 days old (needed 5 days)
• phploc (- to 7.0.2-4)
  • Migration status for phploc (- to 7.0.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • phploc/amd64 has unsatisfiable dependency
    • phploc/arm64 has unsatisfiable dependency
    • Updating phploc would introduce bugs in testing: #1092879
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phploc.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 344 days old (needed 5 days)
• haskell-github (- to 0.29-1)
  • Migration status for haskell-github (- to 0.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-github would introduce bugs in testing: #1085141
    • missing build on armhf
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on i386, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-github.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 346 days old (needed 5 days)
• eclipse-wtp (- to 3.35-1)
  • Migration status for eclipse-wtp (- to 3.35-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for eclipse-wtp/3.35-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: Failed ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-wtp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 347 days old (needed 5 days)
• python-homematicip (- to 1.1.2-1)
  • Migration status for python-homematicip (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-homematicip would introduce bugs in testing: #1084768
    • autopkgtest for python-homematicip/1.1.2-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-homematicip.html
    • 347 days old (needed 5 days)
• projectreactor (- to 2.0.8-2)
  • Migration status for projectreactor (- to 2.0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating projectreactor would introduce bugs in testing: #1091946
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/projectreactor.html
    • 349 days old (needed 5 days)
• entrypoints (- to 0.4-3)
  • Migration status for entrypoints (- to 0.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating entrypoints would introduce bugs in testing: #1105737
    • 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/e/entrypoints.html
    • autopkgtest for entrypoints/0.4-3: amd64: Pass, arm64: 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
    • 351 days old (needed 2 days)
• haskell-base64 (- to 0.4.2.4-4)
  • Migration status for haskell-base64 (- to 0.4.2.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating haskell-base64 would introduce bugs in testing: #1057652
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/haskell-base64.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 351 days old (needed 5 days)
• r-cran-gbm (- to 2.2.2-1)
  • Migration status for r-cran-gbm (- to 2.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating r-cran-gbm would introduce bugs in testing: #1064922
    • autopkgtest for r-cran-gbm/2.2.2-1: amd64: Pass, arm64: Failed ♻, i386: Pass, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-gbm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 351 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• kraft (- to 1.2.2-1)
  • Migration status for kraft (- to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • kraft/amd64 has unsatisfiable dependency
    • kraft/arm64 has unsatisfiable dependency
    • kraft/armhf has unsatisfiable dependency
    • kraft/i386 has unsatisfiable dependency
    • kraft/ppc64el has unsatisfiable dependency
    • kraft/riscv64 has unsatisfiable dependency
    • kraft/s390x has unsatisfiable dependency
    • Updating kraft would introduce bugs in testing: #1029734, #1088983
    • kraft unsatisfiable Build-Depends(-Arch) on amd64: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on amd64: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on arm64: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on arm64: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on armhf: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on armhf: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on i386: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on i386: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on ppc64el: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on riscv64: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on riscv64: libkf5akonadicontact-dev
    • kraft unsatisfiable Build-Depends(-Arch) on s390x: libkf5akonadi-dev
    • kraft unsatisfiable Build-Depends(-Arch) on s390x: libkf5akonadicontact-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kraft.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 353 days old (needed 5 days)
• ruby-rspec-parameterized-core (- to 1.0.0-1.1)
  • Migration status for ruby-rspec-parameterized-core (- to 1.0.0-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-rspec-parameterized-core ruby-unparser (not considered)
    • Depends: ruby-rspec-parameterized-core ruby-unparser (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): ruby-rspec-parameterized-core ruby-proc-to-ast
    • Depends: ruby-rspec-parameterized-core ruby-proc-to-ast
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized-core.html
    • autopkgtest for ruby-rspec-parameterized-core/1.0.0-1.1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial 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 ♻
    • 353 days old (needed 5 days)
• sepp (- to 4.5.5+dfsg-1)
  • Migration status for sepp (- to 4.5.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): 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.5+dfsg-1: amd64: Pass, arm64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 354 days old (needed 2 days)
• apt-transport-in-toto (- to 0.1.1-5)
  • Migration status for apt-transport-in-toto (- to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating apt-transport-in-toto would introduce bugs in testing: #1090090
    • Build-Depends(-Arch): apt-transport-in-toto in-toto (not considered)
    • Depends: apt-transport-in-toto in-toto (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apt-transport-in-toto.html
    • 359 days old (needed 5 days)
• php-horde-db (- to 2.4.1-8.1)
  • Migration status for php-horde-db (- to 2.4.1-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-db would introduce bugs in testing: #1089726
    • autopkgtest for php-horde-db/2.4.1-8.1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-db pear-channels (not considered)
    • Depends: php-horde-db php-horde-date (not considered)
    • Depends: php-horde-db php-horde-exception (not considered)
    • Depends: php-horde-db php-horde-support (not considered)
    • Depends: php-horde-db php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-db.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 360 days old (needed 5 days)
• open-infrastructure-system-tools (- to 20190301-lts1-5)
  • Migration status for open-infrastructure-system-tools (- to 20190301-lts1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating open-infrastructure-system-tools would introduce bugs in testing: #1093131
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open-infrastructure-system-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 362 days old (needed 5 days)
• unknown-horizons (- to 2019.1-8)
  • Migration status for unknown-horizons (- to 2019.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unknown-horizons would introduce bugs in testing: #1089495
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unknown-horizons.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 364 days old (needed 5 days)
• coremltools (- to 8.0-1)
  • Migration status for coremltools (- to 8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating coremltools would introduce bugs in testing: #1077292
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coremltools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 366 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• nrpe-ng (- to 0.2.0-1.3)
  • Migration status for nrpe-ng (- to 0.2.0-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nrpe-ng would introduce bugs in testing: #1087622
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nrpe-ng.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 371 days old (needed 5 days)
• epoptes (- to 23.08-2)
  • Migration status for epoptes (- to 23.08-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating epoptes would introduce bugs in testing: #1084716
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/epoptes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 375 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis, notify-osd, ssvnc
• node-microsoft-fast (- to 0~20240320+ds1-1)
  • Migration status for node-microsoft-fast (- to 0~20240320+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating node-microsoft-fast would introduce bugs in testing: #1081223
    • Not built on buildd: arch all binaries uploaded by x.guimard@free.fr, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-microsoft-fast.html
    • autopkgtest for node-microsoft-fast/0~20240320+ds1-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 376 days old (needed 5 days)
• python-bellows (- to 0.40.5-1)
  • Migration status for python-bellows (- to 0.40.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-bellows would introduce bugs in testing: #1098594
    • autopkgtest for python-bellows/0.40.5-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Not built on buildd: arch all binaries uploaded by zigo, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-bellows.html
    • 376 days old (needed 5 days)
• python-foobot-async (- to 1.0.1-2)
  • Migration status for python-foobot-async (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-foobot-async would introduce bugs in testing: #1090274
    • autopkgtest for python-foobot-async/1.0.1-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-foobot-async.html
    • 376 days old (needed 5 days)
• pocketsphinx-python (- to 1:0.1.15-7)
  • Migration status for pocketsphinx-python (- to 1:0.1.15-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pocketsphinx-python would introduce bugs in testing: #1088764
    • autopkgtest for pocketsphinx-python/1:0.1.15-7: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pocketsphinx-python.html
    • 377 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• python-aiowithings (- to 3.0.3-2)
  • Migration status for python-aiowithings (- to 3.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiowithings would introduce bugs in testing: #1084327
    • autopkgtest for python-aiowithings/3.0.3-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiowithings.html
    • 377 days old (needed 5 days)
• mindthegap (- to 2.3.0-4)
  • Migration status for mindthegap (- to 2.3.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for mindthegap/2.3.0-4: amd64: Pass, arm64: Pass, ppc64el: Failed ♻, riscv64: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mindthegap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 378 days old (needed 5 days)
• r-cran-filehash (- to 2.4-6-1)
  • Migration status for r-cran-filehash (- to 2.4-6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-filehash/2.4-6-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-filehash.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 379 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• python-auto-pytabs (- to 0.4.0-2)
  • Migration status for python-auto-pytabs (- to 0.4.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: python-auto-pytabs ruff (not considered)
    • Depends: python-auto-pytabs ruff (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-auto-pytabs.html
    • autopkgtest for python-auto-pytabs/0.4.0-2: amd64: Pass, arm64: 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
    • 381 days old (needed 2 days)
• calamares-settings-mobian (- to 0.3.6)
  • Migration status for calamares-settings-mobian (- to 0.3.6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: calamares-settings-mobian calamares-extensions (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calamares-settings-mobian.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 382 days old (needed 5 days)
• golang-github-traefik-paerser (- to 0.2.0-1)
  • Migration status for golang-github-traefik-paerser (- to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-traefik-paerser/0.2.0-1: amd64: Pass, arm64: Pass, i386: Failed ♻, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Not built on buildd: arch all binaries uploaded by alois@micard.lu, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-traefik-paerser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 386 days old (needed 5 days)
• rlottie (- to 0.1+dfsg-4.2)
  • Migration status for rlottie (- to 0.1+dfsg-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rlottie would introduce bugs in testing: #1109341
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rlottie.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 387 days old (needed 5 days)
• telegram-desktop (- to 4.14.9+ds-1.1)
  • Migration status for telegram-desktop (- to 4.14.9+ds-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • telegram-desktop/amd64 has unsatisfiable dependency
    • telegram-desktop/arm64 has unsatisfiable dependency
    • telegram-desktop/armhf has unsatisfiable dependency
    • telegram-desktop/i386 has unsatisfiable dependency
    • telegram-desktop/ppc64el has unsatisfiable dependency
    • telegram-desktop/riscv64 has unsatisfiable dependency
    • Updating telegram-desktop would introduce bugs in testing: #1091237, #1114647
    • Build-Depends(-Arch): telegram-desktop rlottie (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telegram-desktop.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 390 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• trafficserver (- to 9.2.5+ds-1)
  • Migration status for trafficserver (- to 9.2.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • trafficserver/amd64 has unsatisfiable dependency
    • trafficserver/arm64 has unsatisfiable dependency
    • Updating trafficserver would introduce bugs in testing: #1087531, #1099691, #1101996, #1108044, #999938
    • trafficserver unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • trafficserver unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trafficserver.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 392 days old (needed 5 days)
• py-libzfs (- to 0.0+git20240510.5ae7d5e-1)
  • Migration status for py-libzfs (- to 0.0+git20240510.5ae7d5e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-libzfs/amd64 has unsatisfiable dependency
    • python3-libzfs/arm64 has unsatisfiable dependency
    • python3-libzfs/armhf has unsatisfiable dependency
    • python3-libzfs/i386 has unsatisfiable dependency
    • python3-libzfs/ppc64el has unsatisfiable dependency
    • python3-libzfs/riscv64 has unsatisfiable dependency
    • python3-libzfs/s390x has unsatisfiable dependency
    • Updating py-libzfs would introduce bugs in testing: #1082340, #1093171
    • Build-Depends(-Arch): py-libzfs cython-legacy (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 393 days old (needed 5 days)
• png23d (- to 1.10-3)
  • Migration status for png23d (- to 1.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating png23d would introduce bugs in testing: #1108804
    • autopkgtest for png23d/1.10-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/png23d.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 394 days old (needed 5 days)
• pympler (- to 1.1+dfsg1-1)
  • Migration status for pympler (- to 1.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pympler would introduce bugs in testing: #1082154
    • autopkgtest for pympler/1.1+dfsg1-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pympler.html
    • 394 days old (needed 5 days)
• opendnssec (- to 1:2.1.13-1.2)
  • Migration status for opendnssec (- to 1:2.1.13-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opendnssec would introduce bugs in testing: #1108992
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opendnssec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 398 days old (needed 5 days)
• python-aiomodernforms (- to 0.1.8-2)
  • Migration status for python-aiomodernforms (- to 0.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aiomodernforms would introduce bugs in testing: #1084326
    • autopkgtest for python-aiomodernforms/0.1.8-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aiomodernforms.html
    • 401 days old (needed 5 days)
• golang-github-traefik-yaegi (- to 0.16.1-2)
  • Migration status for golang-github-traefik-yaegi (- to 0.16.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-traefik-yaegi would introduce bugs in testing: #1096224
    • autopkgtest for golang-github-traefik-yaegi/0.16.1-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Built-Using: golang-github-traefik-yaegi golang-1.23 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-traefik-yaegi.html
    • 402 days old (needed 5 days)
• tracy (- to 0.11.0+ds-1)
  • Migration status for tracy (- to 0.11.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tracy would introduce bugs in testing: #1078703
    • Not built on buildd: arch all binaries uploaded by tar, a new source-only upload is needed to allow migration
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tracy.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 404 days old (needed 5 days)
• gimp-plugin-registry (- to 9.20240808)
  • Migration status for gimp-plugin-registry (- to 9.20240808): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gimp-plugin-registry/amd64 has unsatisfiable dependency
    • gimp-plugin-registry/arm64 has unsatisfiable dependency
    • gimp-plugin-registry/armhf has unsatisfiable dependency
    • gimp-plugin-registry/i386 has unsatisfiable dependency
    • gimp-plugin-registry/ppc64el has unsatisfiable dependency
    • gimp-plugin-registry/riscv64 has unsatisfiable dependency
    • Updating gimp-plugin-registry would introduce bugs in testing: #1043232, #1110111
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on amd64: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on arm64: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on armhf: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on i386: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on ppc64el: libgimp2.0-dev
    • gimp-plugin-registry unsatisfiable Build-Depends(-Arch) on riscv64: libgimp2.0-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gimp-plugin-registry.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 407 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• libprelude (- to 5.2.0-5.6)
  • Migration status for libprelude (- to 5.2.0-5.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-prelude/amd64 has unsatisfiable dependency
    • ruby-libprelude/amd64 has unsatisfiable dependency
    • python3-prelude/arm64 has unsatisfiable dependency
    • ruby-libprelude/arm64 has unsatisfiable dependency
    • python3-prelude/armhf has unsatisfiable dependency
    • ruby-libprelude/armhf has unsatisfiable dependency
    • python3-prelude/i386 has unsatisfiable dependency
    • ruby-libprelude/i386 has unsatisfiable dependency
    • python3-prelude/ppc64el has unsatisfiable dependency
    • ruby-libprelude/ppc64el has unsatisfiable dependency
    • python3-prelude/riscv64 has unsatisfiable dependency
    • ruby-libprelude/riscv64 has unsatisfiable dependency
    • python3-prelude/s390x has unsatisfiable dependency
    • ruby-libprelude/s390x has unsatisfiable dependency
    • Updating libprelude would introduce bugs in testing: #1080647, #1081473
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/libp/libprelude.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 407 days old (needed 5 days)
• python-adb-shell (- to 0.4.4-2)
  • Migration status for python-adb-shell (- to 0.4.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-adb-shell would introduce bugs in testing: #1082192, #1086887
    • python-adb-shell unsatisfiable Build-Depends-Indep on amd64: python3-libusb1
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-adb-shell.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 409 days old (needed 5 days)
• python-open-meteo (- to 0.3.1-2)
  • Migration status for python-open-meteo (- to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-open-meteo would introduce bugs in testing: #1084343
    • Build-Depends-Indep: python-open-meteo ruff (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-open-meteo.html
    • 413 days old (needed 5 days)
• mimetex (- to 1.76-4)
  • Migration status for mimetex (- to 1.76-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mimetex would introduce bugs in testing: #1097399, #1103801
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mimetex.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 416 days old (needed 5 days)
• pychopper (- to 2.7.10-1)
  • Migration status for pychopper (- to 2.7.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pychopper would introduce bugs in testing: #1082368
    • autopkgtest for pychopper/2.7.10-1: amd64: Pass, arm64: Failed ♻, i386: Pass, ppc64el: Pass, riscv64: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pychopper.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • 416 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• cadabra2 (- to 2.4.3.2-2)
  • Migration status for cadabra2 (- to 2.4.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cadabra2 would introduce bugs in testing: #1061319, #1080566
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cadabra2.html
    • 419 days old (needed 5 days)
• markdown-toc-el (- to 0.1.5-4)
  • Migration status for markdown-toc-el (- to 0.1.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating markdown-toc-el would introduce bugs in testing: #1036359
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/markdown-toc-el.html
    • autopkgtest for markdown-toc-el/0.1.5-4: amd64: Pass, arm64: Pass, 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
    • 421 days old (needed 2 days)
• gnome-system-tools (- to 3.0.0-11)
  • Migration status for gnome-system-tools (- to 3.0.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gnome-system-tools would introduce bugs in testing: #1096735, #1099822
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-system-tools.html
    • Reproducible on arm64 - info ♻
    • 422 days old (needed 5 days)
• synfig (- to 1.5.1+dfsg-4)
  • Migration status for synfig (- to 1.5.1+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsynfig0t64/amd64 has unsatisfiable dependency
    • libsynfig0t64/arm64 has unsatisfiable dependency
    • libsynfig0t64/armhf has unsatisfiable dependency
    • libsynfig0t64/i386 has unsatisfiable dependency
    • libsynfig0t64/ppc64el has unsatisfiable dependency
    • libsynfig0t64/riscv64 has unsatisfiable dependency
    • libsynfig0t64/s390x has unsatisfiable dependency
    • Updating synfig would introduce bugs in testing: #1079335, #1086935
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/synfig.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 422 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• python-pymzml (- to 2.5.10+repack1-1)
  • Migration status for python-pymzml (- to 2.5.10+repack1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pymzml would introduce bugs in testing: #1092544
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pymzml.html
    • 423 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• pydrive2 (- to 1.20.0-1)
  • Migration status for pydrive2 (- to 1.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pydrive2 would introduce bugs in testing: #1083031
    • Build-Depends(-Arch): pydrive2 python-oauth2client (not considered)
    • Depends: pydrive2 python-oauth2client (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pydrive2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 428 days old (needed 5 days)
• sks (- to 1.1.6+git20210302.c3ba6d5a-4.1)
  • Migration status for sks (- to 1.1.6+git20210302.c3ba6d5a-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sks would introduce bugs in testing: #1073911, #1093110
    • autopkgtest for sks/1.1.6+git20210302.c3ba6d5a-4.1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sks.html
    • 432 days old (needed 5 days)
• toybox (- to 0.8.9+dfsg-1.1)
  • Migration status for toybox (- to 0.8.9+dfsg-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating toybox would introduce bugs in testing: #1108539
    • autopkgtest for toybox/0.8.9+dfsg-1.1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/toybox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 432 days old (needed 5 days)
• mes (- to 0.27-1)
  • Migration status for mes (- to 0.27-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mes would introduce bugs in testing: #1067952
    • missing build on armhf
    • Waiting for lintian test results on armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mes.html
    • 434 days old (needed 5 days)
• dovecot-antispam (- to 2.0+20171229-1.1)
  • Migration status for dovecot-antispam (- to 2.0+20171229-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dovecot-antispam/amd64 has unsatisfiable dependency
    • dovecot-antispam/arm64 has unsatisfiable dependency
    • dovecot-antispam/armhf has unsatisfiable dependency
    • dovecot-antispam/i386 has unsatisfiable dependency
    • dovecot-antispam/ppc64el has unsatisfiable dependency
    • dovecot-antispam/riscv64 has unsatisfiable dependency
    • dovecot-antispam/s390x has unsatisfiable dependency
    • Updating dovecot-antispam would introduce bugs in testing: #1096541, #1104033
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dovecot-antispam.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 439 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:
    • python3-cogent3/amd64 has unsatisfiable dependency
    • python3-cogent3/arm64 has unsatisfiable dependency
    • Updating python-cogent would introduce bugs in testing: #1090269
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-cogent.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 441 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• klystrack (- to 0.20171212-7)
  • Migration status for klystrack (- to 0.20171212-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating klystrack would introduce bugs in testing: #1075115
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/klystrack.html
    • 442 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yaramod.html
    • Reproducible on arm64 - info ♻
    • 443 days old (needed 5 days)
• q2-diversity-lib (- to 2024.5.0-1)
  • Migration status for q2-diversity-lib (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-diversity-lib/2024.5.0-1: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
    • Build-Depends(-Arch): q2-diversity-lib qiime (not considered)
    • Depends: q2-diversity-lib q2-emperor (not considered)
    • Depends: q2-diversity-lib q2-feature-table (not considered)
    • Depends: q2-diversity-lib qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-diversity-lib.html
    • uninstallable on arch 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 ♻
    • 447 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-emperor (- to 2024.5.0-2)
  • Migration status for q2-emperor (- to 2024.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): q2-emperor q2-types (not considered)
    • Build-Depends(-Arch): q2-emperor qiime (not considered)
    • Depends: q2-emperor q2-types (not considered)
    • Depends: q2-emperor qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-emperor.html
    • autopkgtest for q2-emperor/2024.5.0-2: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 447 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-sample-classifier (- to 2024.5.0-2)
  • Migration status for q2-sample-classifier (- to 2024.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-sample-classifier/2024.5.0-2: amd64: Failed ♻, arm64: Failed ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): q2-sample-classifier qiime (not considered)
    • Depends: q2-sample-classifier q2-feature-table (not considered)
    • Depends: q2-sample-classifier q2-types (not considered)
    • Depends: q2-sample-classifier qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-sample-classifier.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 447 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• sagenb-export (- to 3.4-1)
  • Migration status for sagenb-export (- to 3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sagenb-export would introduce bugs in testing: #1091611
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sagenb-export.html
    • autopkgtest for sagenb-export/3.4-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial 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 ♻
    • 447 days old (needed 5 days)
• caml-crush (- to 1.0.12-1.2)
  • Migration status for caml-crush (- to 1.0.12-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating caml-crush would introduce bugs in testing: #1074545, #1076869
    • caml-crush unsatisfiable Build-Depends(-Arch) on armhf: ocaml-native-compilers
    • caml-crush unsatisfiable Build-Depends(-Arch) on i386: ocaml-native-compilers
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/caml-crush.html
    • 450 days old (needed 5 days)
• q2-dada2 (- to 2024.5.0-1)
  • Migration status for q2-dada2 (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-dada2/2024.5.0-1: amd64: Failed ♻
    • Build-Depends(-Arch): q2-dada2 qiime (not considered)
    • Depends: q2-dada2 q2-types (not considered)
    • Depends: q2-dada2 qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-dada2.html
    • Reproducible on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 450 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2cli (- to 2024.5.0-2)
  • Migration status for q2cli (- to 2024.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • q2cli/amd64 has unsatisfiable dependency
    • q2cli/arm64 has unsatisfiable dependency
    • Updating q2cli would introduce bugs in testing: #1076080
    • Build-Depends(-Arch): q2cli qiime (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/q/q2cli.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 450 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-alignment (- to 2024.5.0-1)
  • Migration status for q2-alignment (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-alignment would introduce bugs in testing: #1076318
    • autopkgtest for q2-alignment/2024.5.0-1: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
    • Build-Depends(-Arch): q2-alignment q2-types (not considered)
    • Build-Depends(-Arch): q2-alignment qiime (not considered)
    • Depends: q2-alignment q2-types (not considered)
    • Depends: q2-alignment qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-alignment.html
    • uninstallable on arch 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 ♻
    • 451 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-demux (- to 2024.5.0+dfsg-1)
  • Migration status for q2-demux (- to 2024.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-demux would introduce bugs in testing: #1076315
    • autopkgtest for q2-demux/2024.5.0+dfsg-1: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
    • Build-Depends(-Arch): q2-demux q2-types (not considered)
    • Build-Depends(-Arch): q2-demux qiime (not considered)
    • Depends: q2-demux q2-types (not considered)
    • Depends: q2-demux qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-demux.html
    • uninstallable on arch 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 ♻
    • 451 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-metadata (- to 2024.5.0+dfsg-1)
  • Migration status for q2-metadata (- to 2024.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): q2-metadata q2-quality-filter (not considered)
    • Build-Depends(-Arch): q2-metadata q2-types (not considered)
    • Build-Depends(-Arch): q2-metadata qiime (not considered)
    • Depends: q2-metadata q2-quality-filter (not considered)
    • Depends: q2-metadata q2-types (not considered)
    • Depends: q2-metadata qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-metadata.html
    • autopkgtest for q2-metadata/2024.5.0+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 451 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• q2-phylogeny (- to 2024.5.0-1)
  • Migration status for q2-phylogeny (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-phylogeny would introduce bugs in testing: #1076317
    • autopkgtest for q2-phylogeny/2024.5.0-1: amd64: Failed ♻
    • Depends: q2-phylogeny q2-alignment (not considered)
    • Depends: q2-phylogeny q2-types (not considered)
    • Depends: q2-phylogeny qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-phylogeny.html
    • Reproducible on amd64 - info ♻
    • 451 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-quality-control (- to 2024.5.0-1)
  • Migration status for q2-quality-control (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-quality-control/2024.5.0-1: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
    • Build-Depends(-Arch): q2-quality-control q2-feature-table (not considered)
    • Build-Depends(-Arch): q2-quality-control q2-taxa (not considered)
    • Build-Depends(-Arch): q2-quality-control qiime (not considered)
    • Depends: q2-quality-control q2-taxa (not considered)
    • Depends: q2-quality-control qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-quality-control.html
    • uninstallable on arch 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 ♻
    • 451 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-taxa (- to 2024.5.0+dfsg-1)
  • Migration status for q2-taxa (- to 2024.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): q2-taxa q2-types (not considered)
    • Build-Depends(-Arch): q2-taxa qiime (not considered)
    • Depends: q2-taxa q2-types (not considered)
    • Depends: q2-taxa qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-taxa.html
    • autopkgtest for q2-taxa/2024.5.0+dfsg-1: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Pass, s390x: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 451 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-cutadapt (- to 2024.5.0-1)
  • Migration status for q2-cutadapt (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-cutadapt/2024.5.0-1: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
    • Build-Depends(-Arch): q2-cutadapt q2-types (not considered)
    • Build-Depends(-Arch): q2-cutadapt qiime (not considered)
    • Depends: q2-cutadapt q2-types (not considered)
    • Depends: q2-cutadapt qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-cutadapt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 452 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-feature-table (- to 2024.5.0+dfsg-1)
  • Migration status for q2-feature-table (- to 2024.5.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-feature-table/2024.5.0+dfsg-1: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
    • Build-Depends(-Arch): q2-feature-table q2-types (not considered)
    • Build-Depends(-Arch): q2-feature-table qiime (not considered)
    • Depends: q2-feature-table q2-types (not considered)
    • Depends: q2-feature-table qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-feature-table.html
    • uninstallable on arch 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 ♻
    • 452 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-fragment-insertion (- to 2024.5.0-1)
  • Migration status for q2-fragment-insertion (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-fragment-insertion/2024.5.0-1: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
    • Build-Depends(-Arch): q2-fragment-insertion qiime (not considered)
    • Depends: q2-fragment-insertion q2-types (not considered)
    • Depends: q2-fragment-insertion qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-fragment-insertion.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 452 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-quality-filter (- to 2024.5.0-1)
  • Migration status for q2-quality-filter (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for q2-quality-filter/2024.5.0-1: amd64: Failed ♻, arm64: Failed ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: No tests, superficial or marked flaky ♻
    • Build-Depends(-Arch): q2-quality-filter q2-types (not considered)
    • Build-Depends(-Arch): q2-quality-filter qiime (not considered)
    • Depends: q2-quality-filter q2-types (not considered)
    • Depends: q2-quality-filter qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-quality-filter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 452 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• q2-types (- to 2024.5.0-1)
  • Migration status for q2-types (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating q2-types would introduce bugs in testing: #1076316
    • autopkgtest for q2-types/2024.5.0-1: amd64: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
    • Build-Depends(-Arch): q2-types qiime (not considered)
    • Depends: q2-types qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-types.html
    • uninstallable on arch 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 ♻
    • 452 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• qiime (- to 2024.5.0-1)
  • Migration status for qiime (- to 2024.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating qiime would introduce bugs in testing: #1076314, #1084668
    • autopkgtest for qiime/2024.5.0-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qiime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 452 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• fonts-arapey (- to 0+git20200408-3)
  • Migration status for fonts-arapey (- to 0+git20200408-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-arapey would introduce bugs in testing: #1087299
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-arapey.html
    • 454 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-sjstats r-cran-effectsize (not considered)
    • Depends: r-cran-sjstats r-cran-effectsize (not considered)
  • 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, 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
    • 459 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• ntopng (- to 5.2.1+dfsg1-2)
  • Migration status for ntopng (- to 5.2.1+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ntopng would introduce bugs in testing: #1038842, #1090110
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/ntopng.html
    • 460 days old (needed 5 days)
• ruff (- to 0.0.291+dfsg1-4)
  • Migration status for ruff (- to 0.0.291+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruff would introduce bugs in testing: #1074734, #1108905
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruff.html
    • 460 days old (needed 5 days)
• pam-krb5-migrate (- to 0.0.11-5.1)
  • Migration status for pam-krb5-migrate (- to 0.0.11-5.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pam-krb5-migrate would introduce bugs in testing: #1075357
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pam-krb5-migrate.html
    • 462 days old (needed 5 days)
• hilive (- to 2.0a-4)
  • Migration status for hilive (- to 2.0a-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hilive would introduce bugs in testing: #1053499
    • autopkgtest for hilive/2.0a-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Failed ♻, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hilive.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 463 days old (needed 5 days)
• softether-vpn (- to 5.01.9674+git20200806+8181039+dfsg3-1)
  • Migration status for softether-vpn (- to 5.01.9674+git20200806+8181039+dfsg3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating softether-vpn would introduce bugs in testing: #1075525
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/softether-vpn.html
    • 463 days old (needed 5 days)
• archmbox (- to 4.10.0-7)
  • Migration status for archmbox (- to 4.10.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: archmbox uw-imap (not considered)
    • Depends: archmbox uw-imap (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/archmbox.html
    • autopkgtest for archmbox/4.10.0-7: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial 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 ♻
    • 464 days old (needed 5 days)
• simh (- to 3.8.1-6.2)
  • Migration status for simh (- to 3.8.1-6.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating simh would introduce bugs in testing: #1075511
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/simh.html
    • 466 days old (needed 5 days)
• netdiag (- to 1.2-1.3)
  • Migration status for netdiag (- to 1.2-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating netdiag would introduce bugs in testing: #1075311
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/netdiag.html
    • 467 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, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-awkward.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 470 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• harden-doc (- to 3.19+nmu3)
  • Migration status for harden-doc (- to 3.19+nmu3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating harden-doc would introduce bugs in testing: #1053602, #1114145
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/harden-doc.html
    • 475 days old (needed 5 days)
• eterm (- to 0.9.6-7.2)
  • Migration status for eterm (- to 0.9.6-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating eterm would introduce bugs in testing: #1074940
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eterm.html
    • 476 days old (needed 5 days)
    • Remove hint for (transitive) dependency: libast
• gfxreconstruct (- to 1.0.4+dfsg-1)
  • Migration status for gfxreconstruct (- to 1.0.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gfxreconstruct would introduce bugs in testing: #1081863
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gfxreconstruct.html
    • 476 days old (needed 5 days)
• python-pytray (- to 0.3.5-4)
  • Migration status for python-pytray (- to 0.3.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-pytray would introduce bugs in testing: #1092793
    • autopkgtest for python-pytray/0.3.5-4: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pytray.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 477 days old (needed 5 days)
• gcc-12-cross-mipsen (- to 5+c1)
  • Migration status for gcc-12-cross-mipsen (- to 5+c1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-12-cross-mipsen would introduce bugs in testing: #1089258, #1089889
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-12-cross-mipsen.html
    • 478 days old (needed 5 days)
• prelude-correlator (- to 5.2.0-1.2)
  • Migration status for prelude-correlator (- to 5.2.0-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): prelude-correlator libprelude (not considered)
    • Depends: prelude-correlator libprelude (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prelude-correlator.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 481 days old (needed 5 days)
• ledgersmb (- to 1.6.33+ds-2.2)
  • Migration status for ledgersmb (- to 1.6.33+ds-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ledgersmb would introduce bugs in testing: #1027472, #1104577
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ledgersmb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 483 days old (needed 5 days)
• tomoyo-tools (- to 2.6.1-20210910-1.1)
  • Migration status for tomoyo-tools (- to 2.6.1-20210910-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tomoyo-tools would introduce bugs in testing: #1088729
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tomoyo-tools.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 483 days old (needed 5 days)
• unicrypto (- to 0.0.10-2)
  • Migration status for unicrypto (- to 0.0.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating unicrypto would introduce bugs in testing: #1090176
    • autopkgtest for unicrypto/0.0.10-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): unicrypto python-mbedtls (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unicrypto.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 483 days old (needed 5 days)
• pplacer (- to 1.1~alpha19-8)
  • Migration status for pplacer (- to 1.1~alpha19-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pplacer would introduce bugs in testing: #1074546
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pplacer.html
    • autopkgtest for pplacer/1.1~alpha19-8: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 484 days old (needed 2 days)
• tla (- to 1.3.5+dfsg2-1)
  • Migration status for tla (- to 1.3.5+dfsg2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tla would introduce bugs in testing: #1075579
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tla.html
    • 485 days old (needed 5 days)
• quickml (- to 0.8-2)
  • Migration status for quickml (- to 0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating quickml would introduce bugs in testing: #1073471
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on all - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quickml.html
    • 486 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/ppc64el has unsatisfiable dependency
    • olive-editor/riscv64 has unsatisfiable dependency
    • olive-editor/s390x has unsatisfiable dependency
    • Updating olive-editor would introduce bugs in testing: #1072441
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/o/olive-editor.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 491 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• kde-config-systemd (- to 1.2.1-3.3)
  • Migration status for kde-config-systemd (- to 1.2.1-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kde-config-systemd would introduce bugs in testing: #1095535, #1110504
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kde-config-systemd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 493 days old (needed 5 days)
• python-fastparquet (- to 2024.2.0-2)
  • Migration status for python-fastparquet (- to 2024.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-fastparquet/amd64 has unsatisfiable dependency
    • python3-fastparquet/arm64 has unsatisfiable dependency
    • Build-Depends(-Arch): python-fastparquet python-cramjam (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fastparquet.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 494 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• python-mbedtls (- to 2.10.1-1)
  • Migration status for python-mbedtls (- to 2.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-mbedtls/amd64 has unsatisfiable dependency
    • python3-mbedtls/arm64 has unsatisfiable dependency
    • python3-mbedtls/armhf has unsatisfiable dependency
    • python3-mbedtls/i386 has unsatisfiable dependency
    • python3-mbedtls/ppc64el has unsatisfiable dependency
    • python3-mbedtls/riscv64 has unsatisfiable dependency
    • python3-mbedtls/s390x has unsatisfiable dependency
    • Updating python-mbedtls would introduce bugs in testing: #1075872
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-mbedtls.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 497 days old (needed 5 days)
• gngb (- to 20060309-6)
  • Migration status for gngb (- to 20060309-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gngb would introduce bugs in testing: #1075020
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gngb.html
    • 499 days old (needed 5 days)
• linux-ftpd-ssl (- to 0.17.36+really0.17-3)
  • Migration status for linux-ftpd-ssl (- to 0.17.36+really0.17-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating linux-ftpd-ssl would introduce bugs in testing: #1075225
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/linux-ftpd-ssl.html
    • 500 days old (needed 5 days)
• kdelibs4support (- to 5.115.0-3)
  • Migration status for kdelibs4support (- to 5.115.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kdelibs4support would introduce bugs in testing: #1099447
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kdelibs4support.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 503 days old (needed 5 days)
• hugs98 (- to 98.200609.21-7)
  • Migration status for hugs98 (- to 98.200609.21-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hugs98 would introduce bugs in testing: #1075073
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hugs98.html
    • 504 days old (needed 5 days)
• llvm-toolchain-14 (- to 1:14.0.6-20)
  • Migration status for llvm-toolchain-14 (- to 1:14.0.6-20): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • liblldb-14t64/amd64 has unsatisfiable dependency
    • liblldb-14t64/arm64 has unsatisfiable dependency
    • liblldb-14t64/armhf has unsatisfiable dependency
    • liblldb-14t64/i386 has unsatisfiable dependency
    • liblldb-14t64/ppc64el has unsatisfiable dependency
    • liblldb-14t64/s390x has unsatisfiable dependency
    • Updating llvm-toolchain-14 would introduce bugs in testing: #1036596, #1058822, #1068840, #1076412, #1084564, #1098881, #1100374
    • autopkgtest for dolfin: riscv64: Test triggered (failure will be ignored)
    • autopkgtest for fenics-dolfinx: riscv64: Test triggered (failure will be ignored)
    • autopkgtest for llvm-toolchain-14/1:14.0.6-20: riscv64: Failed ♻
    • autopkgtest for pythran: riscv64: Test triggered (failure will be ignored)
    • Impossible Depends: llvm-toolchain-14 -> libabsl20230802/20230802.1-4.2/amd64
    • Impossible Depends: llvm-toolchain-14 -> libabsl20230802/20230802.1-4.2/arm64
    • Impossible Depends: llvm-toolchain-14 -> libabsl20230802/20230802.1-4.2/armhf
    • Impossible Depends: llvm-toolchain-14 -> libabsl20230802/20230802.1-4.2/riscv64
    • Impossible Depends: llvm-toolchain-14 -> libabsl20230802/20230802.1-4.2/s390x
    • Impossible Depends: llvm-toolchain-14 -> libabsl20230802/20230802.1-4/ppc64el
    • Not touching package due to block request by sramacher (please contact debian-release if update is needed)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/l/llvm-toolchain-14.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 504 days old (needed 5 days)
• ganglia (- to 3.7.2-7)
  • Migration status for ganglia (- to 3.7.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ganglia would introduce bugs in testing: #1074977, #1104567, #1104580, #1104581
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganglia.html
    • autopkgtest for ganglia/3.7.2-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 513 days old (needed 2 days)
• python-measurement (- to 3.2.2-2)
  • Migration status for python-measurement (- to 3.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-measurement would introduce bugs in testing: #1078362
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-measurement.html
    • autopkgtest for python-measurement/3.2.2-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 513 days old (needed 5 days)
• sniffit (- to 0.6-1)
  • Migration status for sniffit (- to 0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sniffit would introduce bugs in testing: #1075521
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sniffit.html
    • autopkgtest for sniffit/0.6-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 514 days old (needed 2 days)
• libt3window (- to 0.4.0-1.1)
  • Migration status for libt3window (- to 0.4.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libt3window-dev/amd64 has unsatisfiable dependency
    • libt3window0/amd64 has unsatisfiable dependency
    • libt3window-dev/arm64 has unsatisfiable dependency
    • libt3window0/arm64 has unsatisfiable dependency
    • libt3window-dev/armhf has unsatisfiable dependency
    • libt3window0/armhf has unsatisfiable dependency
    • libt3window-dev/i386 has unsatisfiable dependency
    • libt3window0/i386 has unsatisfiable dependency
    • libt3window-dev/ppc64el has unsatisfiable dependency
    • libt3window0/ppc64el has unsatisfiable dependency
    • libt3window-dev/riscv64 has unsatisfiable dependency
    • libt3window0/riscv64 has unsatisfiable dependency
    • libt3window-dev/s390x has unsatisfiable dependency
    • libt3window0/s390x has unsatisfiable dependency
    • Updating libt3window would introduce bugs in testing: #1106504
    • libt3window unsatisfiable Build-Depends(-Arch) on amd64: libtranscript-dev (>= 0.2.2)
    • libt3window unsatisfiable Build-Depends(-Arch) on arm64: libtranscript-dev (>= 0.2.2)
    • libt3window unsatisfiable Build-Depends(-Arch) on armhf: libtranscript-dev (>= 0.2.2)
    • libt3window unsatisfiable Build-Depends(-Arch) on i386: libtranscript-dev (>= 0.2.2)
    • libt3window unsatisfiable Build-Depends(-Arch) on ppc64el: libtranscript-dev (>= 0.2.2)
    • libt3window unsatisfiable Build-Depends(-Arch) on riscv64: libtranscript-dev (>= 0.2.2)
    • libt3window unsatisfiable Build-Depends(-Arch) on s390x: libtranscript-dev (>= 0.2.2)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libt3window.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 515 days old (needed 5 days)
• loqui (- to 0.7.0-2.1)
  • Migration status for loqui (- to 0.7.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating loqui would introduce bugs in testing: #1075233
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/loqui.html
    • 515 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 ♻
    • 517 days old (needed 5 days)
• tss2 (- to 1045-3)
  • Migration status for tss2 (- to 1045-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tss2 would introduce bugs in testing: #971758
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tss2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 517 days old (needed 5 days)
• pyzbar (- to 0.1.9-2)
  • Migration status for pyzbar (- to 0.1.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pyzbar would introduce bugs in testing: #1080136
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyzbar.html
    • autopkgtest for pyzbar/0.1.9-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 519 days old (needed 2 days)
• hfsutils (- to 3.2.6-16)
  • Migration status for hfsutils (- to 3.2.6-16): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hfsutils would introduce bugs in testing: #1075067
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hfsutils.html
    • 524 days old (needed 5 days)
• kcemu (- to 0.5.2+dfsg-2)
  • Migration status for kcemu (- to 0.5.2+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kcemu would introduce bugs in testing: #1078231
    • Impossible Depends: kcemu -> libtheora0/1.2.0~alpha1+dfsg-6/riscv64
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 525 days old (needed 5 days)
• python-moderngl-window (- to 2.4.6-1)
  • Migration status for python-moderngl-window (- to 2.4.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): python-moderngl-window pyrr (not considered)
    • Depends: python-moderngl-window pyrr (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-moderngl-window.html
    • autopkgtest for python-moderngl-window/2.4.6-1: amd64: Pass, arm64: 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
    • 527 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• ibus-client-clutter (- to 0.0+git20090728.a936bacf-8)
  • Migration status for ibus-client-clutter (- to 0.0+git20090728.a936bacf-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ibus-client-clutter would introduce bugs in testing: #1018137
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ibus-client-clutter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 529 days old (needed 5 days)
• cython-legacy (- to 0.29.37-2)
  • Migration status for cython-legacy (- to 0.29.37-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • cython3-legacy/amd64 has unsatisfiable dependency
    • cython3-legacy/arm64 has unsatisfiable dependency
    • cython3-legacy/armhf has unsatisfiable dependency
    • cython3-legacy/i386 has unsatisfiable dependency
    • cython3-legacy/ppc64el has unsatisfiable dependency
    • cython3-legacy/riscv64 has unsatisfiable dependency
    • cython3-legacy/s390x has unsatisfiable dependency
    • Updating cython-legacy would introduce bugs in testing: #1078460
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/c/cython-legacy.html
    • Not touching package due to block request by ginggs (please contact debian-release if update is needed)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 530 days old (needed 5 days)
• gweled (- to 1.0~beta1-1)
  • Migration status for gweled (- to 1.0~beta1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gweled would introduce bugs in testing: #1060452
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gweled.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 537 days old (needed 5 days)
• aplus-fsf (- to 4.22.1-13)
  • Migration status for aplus-fsf (- to 4.22.1-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aplus-fsf would introduce bugs in testing: #1067921, #1088380
    • missing build on armhf
    • Waiting for lintian test results on armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aplus-fsf.html
    • 541 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 ♻
    • 546 days old (needed 5 days)
• python-uflash (- to 1.2.4+dfsg-11)
  • Migration status for python-uflash (- to 1.2.4+dfsg-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-uflash firmware-microbit-micropython (not considered)
    • Depends: python-uflash firmware-microbit-micropython (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-uflash.html
    • autopkgtest for python-uflash/1.2.4+dfsg-11: amd64: Pass, arm64: Pass, 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
    • 547 days old (needed 2 days)
• nvidia-settings-tesla (- to 525.147.05-1)
  • Migration status for nvidia-settings-tesla (- to 525.147.05-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: nvidia-settings-tesla nvidia-graphics-drivers-tesla (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 551 days old (needed 5 days)
• calculix-ccx (- to 2.21-1)
  • Migration status for calculix-ccx (- to 2.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): calculix-ccx spooles (not considered)
    • Depends: calculix-ccx spooles (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calculix-ccx.html
    • autopkgtest for calculix-ccx/2.21-1: amd64: Pass, arm64: 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
    • 553 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• utf8.h (- to 0.0~git20231220.535001e-2)
  • Migration status for utf8.h (- to 0.0~git20231220.535001e-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating utf8.h would introduce bugs in testing: #1102709
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/utf8.h.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 557 days old (needed 5 days)
• freewnn (- to 1.1.1~a021+cvs20130302-8)
  • Migration status for freewnn (- to 1.1.1~a021+cvs20130302-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freewnn would introduce bugs in testing: #1074968
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freewnn.html
    • 559 days old (needed 5 days)
• libapache2-mod-python (- to 3.5.0.1-3)
  • Migration status for libapache2-mod-python (- to 3.5.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libapache2-mod-python/amd64 has unsatisfiable dependency
    • libapache2-mod-python/arm64 has unsatisfiable dependency
    • libapache2-mod-python/armhf has unsatisfiable dependency
    • libapache2-mod-python/i386 has unsatisfiable dependency
    • libapache2-mod-python/ppc64el has unsatisfiable dependency
    • libapache2-mod-python/riscv64 has unsatisfiable dependency
    • libapache2-mod-python/s390x has unsatisfiable dependency
    • Updating libapache2-mod-python would introduce bugs in testing: #1080626, #1091289, #1092440
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/liba/libapache2-mod-python.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 561 days old (needed 5 days)
• libdbd-odbc-perl (- to 1.61-4)
  • Migration status for libdbd-odbc-perl (- to 1.61-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libdbd-odbc-perl would introduce bugs in testing: #1095351
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdbd-odbc-perl.html
    • autopkgtest for libdbd-odbc-perl/1.61-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 562 days old (needed 2 days)
• pdepend (- to 2.16.2-2)
  • Migration status for pdepend (- to 2.16.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pdepend would introduce bugs in testing: #1039755
    • autopkgtest for pdepend/2.16.2-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pdepend.html
    • 562 days old (needed 5 days)
• phpcpd (- to 6.0.3-3)
  • Migration status for phpcpd (- to 6.0.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • phpcpd/amd64 has unsatisfiable dependency
    • phpcpd/arm64 has unsatisfiable dependency
    • Updating phpcpd would introduce bugs in testing: #1070618
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpcpd.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 562 days old (needed 5 days)
• phpmd (- to 2.15.0-2)
  • Migration status for phpmd (- to 2.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phpmd would introduce bugs in testing: #1039795
    • autopkgtest for phpmd/2.15.0-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): phpmd pdepend (not considered)
    • Depends: phpmd pdepend (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phpmd.html
    • 562 days old (needed 5 days)
• libapache-sessionx-perl (- to 2.01-6)
  • Migration status for libapache-sessionx-perl (- to 2.01-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libapache-sessionx-perl would introduce bugs in testing: #930660
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/liba/libapache-sessionx-perl.html
    • autopkgtest for libapache-sessionx-perl/2.01-6: 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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 564 days old (needed 5 days)
• tvdb-api (- to 3.1-4)
  • Migration status for tvdb-api (- to 3.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tvdb-api would introduce bugs in testing: #1084947
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tvdb-api.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 567 days old (needed 5 days)
• tvnamer (- to 3.0.4-2)
  • Migration status for tvnamer (- to 3.0.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: tvnamer tvdb-api (not considered)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tvnamer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 567 days old (needed 5 days)
• jss (- to 5.5.0-1)
  • Migration status for jss (- to 5.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jss would introduce bugs in testing: #1091274
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jss.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 568 days old (needed 5 days)
• ldapjdk (- to 5.5.0+dfsg1-1)
  • Migration status for ldapjdk (- to 5.5.0+dfsg1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: ldapjdk jss (not considered)
    • Depends: ldapjdk jss (not considered)
    • Invalidated by build-dependency (indep)
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/ldapjdk.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 568 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/palabos.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 568 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/armhf has unsatisfiable dependency
    • python3-pywraps2/armhf has unsatisfiable dependency
    • libs2-0t64/i386 has unsatisfiable dependency
    • python3-pywraps2/i386 has unsatisfiable dependency
    • libs2-0t64/ppc64el has unsatisfiable dependency
    • python3-pywraps2/ppc64el has unsatisfiable dependency
    • libs2-0t64/riscv64 has unsatisfiable dependency
    • python3-pywraps2/riscv64 has unsatisfiable dependency
    • libs2-0t64/s390x has unsatisfiable dependency
    • python3-pywraps2/s390x has unsatisfiable dependency
    • Updating s2geometry would introduce bugs in testing: #1059228
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/s2geometry.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 568 days old (needed 5 days)
• shapetools (- to 1.4pl6-16.1)
  • Migration status for shapetools (- to 1.4pl6-16.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shapetools would introduce bugs in testing: #1075506, #1102700
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shapetools.html
    • 568 days old (needed 5 days)
• termrec (- to 0.19-2.1)
  • Migration status for termrec (- to 0.19-2.1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
  • Issues preventing migration:
    • missing build on armhf
    • Waiting for lintian test results on armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/termrec.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 568 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻
  • 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 ♻
    • 569 days old (needed 5 days)
• grok (- to 1.20110708.1-7.1)
  • Migration status for grok (- to 1.20110708.1-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • grok/amd64 has unsatisfiable dependency
    • libgrok1t64/amd64 has unsatisfiable dependency
    • grok/arm64 has unsatisfiable dependency
    • libgrok1t64/arm64 has unsatisfiable dependency
    • grok/i386 has unsatisfiable dependency
    • libgrok1t64/i386 has unsatisfiable dependency
    • grok/ppc64el has unsatisfiable dependency
    • libgrok1t64/ppc64el has unsatisfiable dependency
    • grok/riscv64 has unsatisfiable dependency
    • libgrok1t64/riscv64 has unsatisfiable dependency
    • grok/s390x has unsatisfiable dependency
    • libgrok1t64/s390x has unsatisfiable dependency
    • Updating grok would introduce bugs in testing: #1000065, #1065556
    • grok unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on riscv64: libpcre3-dev
    • grok unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
    • missing build on armhf
    • Waiting for lintian test results on armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grok.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 569 days old (needed 5 days)
• libonvif (- to 1.4.4-1.1)
  • Migration status for libonvif (- to 1.4.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libonvif1t64/amd64 has unsatisfiable dependency
    • libonvif1t64/arm64 has unsatisfiable dependency
    • libonvif1t64/armhf has unsatisfiable dependency
    • libonvif1t64/i386 has unsatisfiable dependency
    • libonvif1t64/ppc64el has unsatisfiable dependency
    • libonvif1t64/riscv64 has unsatisfiable dependency
    • libonvif1t64/s390x has unsatisfiable dependency
    • Updating libonvif would introduce bugs in testing: #1072430
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libo/libonvif.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 569 days old (needed 5 days)
• libpreludedb (- to 5.2.0-2.2)
  • Migration status for libpreludedb (- to 5.2.0-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpreludedb would introduce bugs in testing: #1080884
    • Build-Depends(-Arch): libpreludedb libprelude (not considered)
    • Depends: libpreludedb libprelude (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/libp/libpreludedb.html
    • 569 days old (needed 5 days)
• libsnl (- to 0.2.1.svn.18-1.2)
  • Migration status for libsnl (- to 0.2.1.svn.18-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libsnl would introduce bugs in testing: #1074861
    • autopkgtest for libsnl/0.2.1.svn.18-1.2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsnl.html
    • 569 days old (needed 5 days)
• libt3widget (- to 1.2.0-1.1)
  • Migration status for libt3widget (- to 1.2.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libt3widget-dev/amd64 has unsatisfiable dependency
    • libt3widget2t64/amd64 has unsatisfiable dependency
    • libt3widget-dev/arm64 has unsatisfiable dependency
    • libt3widget2t64/arm64 has unsatisfiable dependency
    • libt3widget-dev/armhf has unsatisfiable dependency
    • libt3widget2t64/armhf has unsatisfiable dependency
    • libt3widget-dev/i386 has unsatisfiable dependency
    • libt3widget2t64/i386 has unsatisfiable dependency
    • libt3widget-dev/ppc64el has unsatisfiable dependency
    • libt3widget2t64/ppc64el has unsatisfiable dependency
    • libt3widget-dev/riscv64 has unsatisfiable dependency
    • libt3widget2t64/riscv64 has unsatisfiable dependency
    • libt3widget-dev/s390x has unsatisfiable dependency
    • libt3widget2t64/s390x has unsatisfiable dependency
    • Updating libt3widget would introduce bugs in testing: #1106503
    • libt3widget unsatisfiable Build-Depends(-Arch) on amd64: libtranscript-dev (>= 0.2.2)
    • libt3widget unsatisfiable Build-Depends(-Arch) on arm64: libtranscript-dev (>= 0.2.2)
    • libt3widget unsatisfiable Build-Depends(-Arch) on armhf: libtranscript-dev (>= 0.2.2)
    • libt3widget unsatisfiable Build-Depends(-Arch) on i386: libtranscript-dev (>= 0.2.2)
    • libt3widget unsatisfiable Build-Depends(-Arch) on ppc64el: libtranscript-dev (>= 0.2.2)
    • libt3widget unsatisfiable Build-Depends(-Arch) on riscv64: libtranscript-dev (>= 0.2.2)
    • libt3widget unsatisfiable Build-Depends(-Arch) on s390x: libtranscript-dev (>= 0.2.2)
    • Build-Depends(-Arch): libt3widget libt3window (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libt/libt3widget.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 569 days old (needed 5 days)
• ogre-1.9 (- to 1.9.0+dfsg1-14.1)
  • Migration status for ogre-1.9 (- to 1.9.0+dfsg1-14.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ogre-1.9 would introduce bugs in testing: #1024182
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ogre-1.9.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 569 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• opendht (- to 3.0.1-1.1)
  • Migration status for opendht (- to 3.0.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating opendht would introduce bugs in testing: #1087610
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/opendht.html
    • autopkgtest for opendht/3.0.1-1.1: amd64: Pass, arm64: Pass, 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
    • 569 days old (needed 2 days)
• xbase64 (- to 3.1.2-14.1)
  • Migration status for xbase64 (- to 3.1.2-14.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libxbase64-bin/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
    • Reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 569 days old (needed 5 days)
• ygl (- to 4.2e-6.1)
  • Migration status for ygl (- to 4.2e-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ygl would introduce bugs in testing: #1075698
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/ygl.html
    • autopkgtest for ygl/4.2e-6.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 569 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:
    • python3-brial/riscv64 has unsatisfiable dependency
    • Updating brial would introduce bugs in testing: #1080888, #1093321
    • autopkgtest for brial/1.2.12-1.1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/b/brial.html
    • uninstallable on arch riscv64, not running autopkgtest there
    • 570 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
    • Waiting for lintian test results on i386 - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hepmc3.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 570 days old (needed 5 days)
• siconos (- to 4.4.0+dfsg-4)
  • Migration status for siconos (- to 4.4.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsiconos-numerics7/amd64 has unsatisfiable dependency
    • python3-siconos/amd64 has unsatisfiable dependency
    • libsiconos-numerics7/arm64 has unsatisfiable dependency
    • python3-siconos/arm64 has unsatisfiable dependency
    • libsiconos-numerics7/ppc64el has unsatisfiable dependency
    • python3-siconos/ppc64el has unsatisfiable dependency
    • libsiconos-numerics7/riscv64 has unsatisfiable dependency
    • python3-siconos/riscv64 has unsatisfiable dependency
    • Updating siconos would introduce bugs in testing: #1066316
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/siconos.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 577 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• cross-gcc (- to 249)
  • Migration status for cross-gcc (- to 249): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cross-gcc would introduce bugs in testing: #1107126
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cross-gcc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 578 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: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
    • Build-Depends(-Arch): q2-feature-classifier q2-feature-table (not considered)
    • Build-Depends(-Arch): q2-feature-classifier q2-quality-control (not considered)
    • Build-Depends(-Arch): q2-feature-classifier q2-taxa (not considered)
    • Build-Depends(-Arch): q2-feature-classifier q2-types (not considered)
    • Build-Depends(-Arch): q2-feature-classifier qiime (not considered)
    • Depends: q2-feature-classifier q2-feature-table (not considered)
    • Depends: q2-feature-classifier q2-quality-control (not considered)
    • Depends: q2-feature-classifier q2-taxa (not considered)
    • Depends: q2-feature-classifier q2-types (not considered)
    • Depends: q2-feature-classifier qiime (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/q2-feature-classifier.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 579 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• low-memory-monitor (- to 2.1-2)
  • Migration status for low-memory-monitor (- to 2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating low-memory-monitor would introduce bugs in testing: #1111310
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/low-memory-monitor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 580 days old (needed 5 days)
• prody (- to 2.4.1+dfsg-2)
  • Migration status for prody (- to 2.4.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-prody/amd64 has unsatisfiable dependency
    • python3-prody/arm64 has unsatisfiable dependency
    • python3-prody/armhf has unsatisfiable dependency
    • python3-prody/ppc64el has unsatisfiable dependency
    • python3-prody/riscv64 has unsatisfiable dependency
    • Updating prody would introduce bugs in testing: #1058454, #1071807
    • missing build on i386
    • arch:i386 not built yet, autopkgtest delayed there
    • Waiting for lintian test results on i386 - info
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/prody.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • 585 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• python-feather-format (- to 0.3.1+dfsg1-8)
  • Migration status for python-feather-format (- to 0.3.1+dfsg1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-feather-format/amd64 has unsatisfiable dependency
    • python3-feather-format/arm64 has unsatisfiable dependency
    • python3-feather-format/armhf has unsatisfiable dependency
    • python3-feather-format/i386 has unsatisfiable dependency
    • python3-feather-format/ppc64el has unsatisfiable dependency
    • python3-feather-format/riscv64 has unsatisfiable dependency
    • python3-feather-format/s390x has unsatisfiable dependency
    • Updating python-feather-format would introduce bugs in testing: #1090271, #1092784
    • Build-Depends(-Arch): python-feather-format cython-legacy (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-feather-format.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 589 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• ruby-mmap2 (- to 2.2.9-1)
  • Migration status for ruby-mmap2 (- to 2.2.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-mmap2/amd64 has unsatisfiable dependency
    • ruby-mmap2/arm64 has unsatisfiable dependency
    • ruby-mmap2/armhf has unsatisfiable dependency
    • ruby-mmap2/i386 has unsatisfiable dependency
    • ruby-mmap2/ppc64el has unsatisfiable dependency
    • ruby-mmap2/riscv64 has unsatisfiable dependency
    • ruby-mmap2/s390x has unsatisfiable dependency
    • Updating ruby-mmap2 would introduce bugs in testing: #1075466
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-mmap2.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 591 days old (needed 5 days)
• django-simple-redis-admin (- to 1.4.0-4)
  • Migration status for django-simple-redis-admin (- to 1.4.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating django-simple-redis-admin would introduce bugs in testing: #1072858
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-simple-redis-admin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 592 days old (needed 5 days)
• abinit (- to 9.10.4-3)
  • Migration status for abinit (- to 9.10.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating abinit would introduce bugs in testing: #1076027, #1089281
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/abinit.html
    • autopkgtest for abinit/9.10.4-3: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 593 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dt-schema.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 600 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • 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 ♻
    • 602 days old (needed 5 days)
• python-aioredlock (- to 0.7.3-3)
  • Migration status for python-aioredlock (- to 0.7.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): python-aioredlock aioredis (not considered)
    • Depends: python-aioredlock aioredis (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioredlock.html
    • autopkgtest for python-aioredlock/0.7.3-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 602 days old (needed 5 days)
• calculix-cgx (- to 2.21+dfsg-1)
  • Migration status for calculix-cgx (- to 2.21+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating calculix-cgx would introduce bugs in testing: #1077425
    • Build-Depends(-Arch): calculix-cgx libsnl (not considered)
    • Depends: calculix-cgx libsnl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/calculix-cgx.html
    • autopkgtest for calculix-cgx/2.21+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 607 days old (needed 2 days)
• pybj (- to 0.2.6-2)
  • Migration status for pybj (- to 0.2.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-bjdata/amd64 has unsatisfiable dependency
    • python3-bjdata/arm64 has unsatisfiable dependency
    • python3-bjdata/armhf has unsatisfiable dependency
    • python3-bjdata/i386 has unsatisfiable dependency
    • python3-bjdata/ppc64el has unsatisfiable dependency
    • python3-bjdata/riscv64 has unsatisfiable dependency
    • python3-bjdata/s390x has unsatisfiable dependency
    • Updating pybj would introduce bugs in testing: #1076204, #1076206
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pybj.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 607 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• python-refurb (- to 1.27.0-1)
  • Migration status for python-refurb (- to 1.27.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-refurb would introduce bugs in testing: #1077460
    • autopkgtest for python-refurb/1.27.0-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-refurb.html
    • 607 days old (needed 5 days)
• cypari2 (- to 2.1.4-1)
  • Migration status for cypari2 (- to 2.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-cypari2/amd64 has unsatisfiable dependency
    • python3-cypari2/arm64 has unsatisfiable dependency
    • python3-cypari2/armhf has unsatisfiable dependency
    • python3-cypari2/i386 has unsatisfiable dependency
    • python3-cypari2/ppc64el has unsatisfiable dependency
    • python3-cypari2/riscv64 has unsatisfiable dependency
    • python3-cypari2/s390x has unsatisfiable dependency
    • Updating cypari2 would introduce bugs in testing: #1081687
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cypari2.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 610 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
    • 615 days old (needed 5 days)
• fweb (- to 1.62-14.1)
  • Migration status for fweb (- to 1.62-14.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fweb would introduce bugs in testing: #1074976
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fweb.html
    • 616 days old (needed 5 days)
• sfwbar (- to 1.0~beta13-1)
  • Migration status for sfwbar (- to 1.0~beta13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sfwbar would introduce bugs in testing: #1091451, #1114373
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sfwbar.html
    • Reproducible on arm64 - info ♻
    • 616 days old (needed 5 days)
• libpam-alreadyloggedin (- to 0.3-14)
  • Migration status for libpam-alreadyloggedin (- to 0.3-14): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libpam-alreadyloggedin would introduce bugs in testing: #1095512
    • autopkgtest for libpam-alreadyloggedin/0.3-14: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libp/libpam-alreadyloggedin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 619 days old (needed 5 days)
• python-cramjam (- to 2.7.0.1+ds1-2)
  • Migration status for python-cramjam (- to 2.7.0.1+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-cramjam/amd64 has unsatisfiable dependency
    • python3-cramjam/arm64 has unsatisfiable dependency
    • Updating python-cramjam would introduce bugs in testing: #1061310
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-cramjam.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • 619 days old (needed 5 days)
• r-cran-tikzdevice (- to 0.12.6-1)
  • Migration status for r-cran-tikzdevice (- to 0.12.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-tikzdevice r-cran-filehash (not considered)
    • Depends: r-cran-tikzdevice r-cran-filehash (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-tikzdevice.html
    • autopkgtest for r-cran-tikzdevice/0.12.6-1: amd64: Pass, arm64: Pass, 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
    • 620 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• pysph (- to 1.0~b1-8)
  • Migration status for pysph (- to 1.0~b1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pysph/amd64 has unsatisfiable dependency
    • python3-pysph/arm64 has unsatisfiable dependency
    • Updating pysph would introduce bugs in testing: #1084148
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysph.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 621 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• 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 ♻
    • 623 days old (needed 5 days)
• civicrm (- to 5.68.1+dfsg1-1)
  • Migration status for civicrm (- to 5.68.1+dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • civicrm-common/amd64 has unsatisfiable dependency
    • civicrm-common/arm64 has unsatisfiable dependency
    • Updating civicrm would introduce bugs in testing: #1078951, #1104797
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/civicrm.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 624 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/einsteinpy.html
    • 627 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• 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
    • 629 days old (needed 5 days)
• yash (- to 2.55-2)
  • Migration status for yash (- to 2.55-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yash would introduce bugs in testing: #1086620
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yash.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 631 days old (needed 5 days)
• casparcg-server (- to 2.3.3+dfsg-3.2)
  • Migration status for casparcg-server (- to 2.3.3+dfsg-3.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • casparcg-server/amd64 has unsatisfiable dependency
    • casparcg-server/arm64 has unsatisfiable dependency
    • Updating casparcg-server would introduce bugs in testing: #1077504, #1101452, #1112604
  • 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
    • 634 days old (needed 5 days)
• aseba (- to 1.6.99+dfsg-9)
  • Migration status for aseba (- to 1.6.99+dfsg-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aseba would introduce bugs in testing: #1074821
    • aseba unsatisfiable Build-Depends(-Arch) on amd64: libqt5webkit5-dev
    • aseba unsatisfiable Build-Depends(-Arch) on arm64: libqt5webkit5-dev
    • aseba unsatisfiable Build-Depends(-Arch) on i386: libqt5webkit5-dev
    • aseba unsatisfiable Build-Depends(-Arch) on riscv64: libqt5webkit5-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aseba.html
    • 638 days old (needed 5 days)
• rdp-classifier (- to 2.10.2-7)
  • Migration status for rdp-classifier (- to 2.10.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rdp-classifier would introduce bugs in testing: #1099282
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rdp-classifier.html
    • 639 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)
    • 641 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
    • 641 days old (needed 5 days)
    • Remove hint for (transitive) dependency: libast, netkit-telnet-ssl
• apper (- to 1.0.0-5)
  • Migration status for apper (- to 1.0.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • apper/amd64 has unsatisfiable dependency
    • apper/arm64 has unsatisfiable dependency
    • apper/armhf has unsatisfiable dependency
    • apper/i386 has unsatisfiable dependency
    • apper/ppc64el has unsatisfiable dependency
    • apper/riscv64 has unsatisfiable dependency
    • apper/s390x has unsatisfiable dependency
    • Updating apper would introduce bugs in testing: #1090089
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/apper.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 642 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:
    • Updating pysurfer would introduce bugs in testing: #1102297
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pysurfer.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • autopkgtest for pysurfer/0.11.2-1: amd64: Pass, arm64: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 644 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• php-htmlpurifier (- to 4.11.0-2)
  • Migration status for php-htmlpurifier (- to 4.11.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-htmlpurifier pear-channels (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-htmlpurifier.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 645 days old (needed 5 days)
• python-nss (- to 1.0.1-2)
  • Migration status for python-nss (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-nss would introduce bugs in testing: #1080757
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-nss.html
    • 647 days old (needed 5 days)
• pandoc-sidenote (- to 0.23.0-1)
  • Migration status for pandoc-sidenote (- to 0.23.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-pandoc-sidenote-doc/amd64 has unsatisfiable dependency
    • pandoc-sidenote/amd64 has unsatisfiable dependency
    • libghc-pandoc-sidenote-doc/arm64 has unsatisfiable dependency
    • pandoc-sidenote/arm64 has unsatisfiable dependency
    • pandoc-sidenote/ppc64el has unsatisfiable dependency
    • pandoc-sidenote/s390x has unsatisfiable dependency
    • Updating pandoc-sidenote would introduce bugs in testing: #1055980
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pandoc-sidenote.html
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 649 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 ♻
    • 655 days old (needed 5 days)
• slashtime (- to 0.5.13-3)
  • Migration status for slashtime (- to 0.5.13-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): slashtime java-gnome (not considered)
    • Depends: slashtime java-gnome (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/slashtime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 656 days old (needed 5 days)
• comskip (- to 0.82.009+git20230112.d0cc422+ds.1-2.1)
  • Migration status for comskip (- to 0.82.009+git20230112.d0cc422+ds.1-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • comskip/amd64 has unsatisfiable dependency
    • comskip-gui/amd64 has unsatisfiable dependency
    • comskip/arm64 has unsatisfiable dependency
    • comskip-gui/arm64 has unsatisfiable dependency
    • comskip/armhf has unsatisfiable dependency
    • comskip-gui/armhf has unsatisfiable dependency
    • comskip/i386 has unsatisfiable dependency
    • comskip-gui/i386 has unsatisfiable dependency
    • comskip/ppc64el has unsatisfiable dependency
    • comskip-gui/ppc64el has unsatisfiable dependency
    • comskip/riscv64 has unsatisfiable dependency
    • comskip-gui/riscv64 has unsatisfiable dependency
    • comskip/s390x has unsatisfiable dependency
    • comskip-gui/s390x has unsatisfiable dependency
    • Updating comskip would introduce bugs in testing: #1072406
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/comskip.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 657 days old (needed 5 days)
• imexam (- to 0.9.1-6)
  • Migration status for imexam (- to 0.9.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating imexam would introduce bugs in testing: #1084277
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/imexam.html
    • autopkgtest for imexam/0.9.1-6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 662 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• hoteldruid (- to 3.0.6-1)
  • Migration status for hoteldruid (- to 3.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hoteldruid would introduce bugs in testing: #1101015, #1104020, #1108154
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hoteldruid.html
    • autopkgtest for hoteldruid/3.0.6-1: amd64: Pass, arm64: 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
    • 663 days old (needed 2 days)
• open-build-service (- to 2.9.4-10)
  • Migration status for open-build-service (- to 2.9.4-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating open-build-service would introduce bugs in testing: #1088953
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/open-build-service.html
    • autopkgtest for open-build-service/2.9.4-10: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 664 days old (needed 2 days)
• pygccjit (- to 0.4-13)
  • Migration status for pygccjit (- to 0.4-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-gccjit/amd64 has unsatisfiable dependency
    • python3-gccjit/arm64 has unsatisfiable dependency
    • python3-gccjit/armhf has unsatisfiable dependency
    • python3-gccjit/i386 has unsatisfiable dependency
    • python3-gccjit/ppc64el has unsatisfiable dependency
    • python3-gccjit/riscv64 has unsatisfiable dependency
    • python3-gccjit/s390x has unsatisfiable dependency
    • Updating pygccjit would introduce bugs in testing: #1082097, #1092782
    • Build-Depends(-Arch): pygccjit cython-legacy (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pygccjit.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 664 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
    • 665 days old (needed 5 days)
• xemacs21-packages (- to 2009.02.17.dfsg.3-3)
  • Migration status for xemacs21-packages (- to 2009.02.17.dfsg.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: xemacs21-packages xemacs21 (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xemacs21-packages.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 666 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-wikibase-cli.html
    • 667 days old (needed 5 days)
• gnome-split (- to 1.2-5)
  • Migration status for gnome-split (- to 1.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): gnome-split java-gnome (not considered)
    • Depends: gnome-split java-gnome (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnome-split.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 669 days old (needed 5 days)
• yersinia (- to 0.8.2-2.2)
  • Migration status for yersinia (- to 0.8.2-2.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating yersinia would introduce bugs in testing: #1075697
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/y/yersinia.html
    • 669 days old (needed 5 days)
• python-etelemetry (- to 0.3.1-1)
  • Migration status for python-etelemetry (- to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-etelemetry would introduce bugs in testing: #1108781
    • autopkgtest for python-etelemetry/0.3.1-1: amd64: Pass, arm64: Pass, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Pass, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-etelemetry.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 672 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 ♻
    • 673 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
    • Waiting for lintian test results on amd64 - info
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/y/ypy.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 674 days old (needed 5 days)
• in-toto (- to 2.0.0-1)
  • Migration status for in-toto (- to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating in-toto would introduce bugs in testing: #1090235
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/in-toto.html
    • 675 days old (needed 5 days)
• python-diagrams (- to 0.23.4-1)
  • Migration status for python-diagrams (- to 0.23.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-diagrams/amd64 has unsatisfiable dependency
    • python3-diagrams/arm64 has unsatisfiable dependency
    • Updating python-diagrams would introduce bugs in testing: #1057174
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/python-diagrams.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 676 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 ♻
    • 678 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
    • 685 days old (needed 5 days)
• robot-testing-framework (- to 2.0.1+ds1-3)
  • Migration status for robot-testing-framework (- to 2.0.1+ds1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • librobottestingframework-ruby2/amd64 has unsatisfiable dependency
    • librobottestingframework-ruby2/arm64 has unsatisfiable dependency
    • librobottestingframework-ruby2/armhf has unsatisfiable dependency
    • librobottestingframework-ruby2/i386 has unsatisfiable dependency
    • librobottestingframework-ruby2/ppc64el has unsatisfiable dependency
    • librobottestingframework-ruby2/riscv64 has unsatisfiable dependency
    • librobottestingframework-ruby2/s390x has unsatisfiable dependency
    • Updating robot-testing-framework would introduce bugs in testing: #1075449
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/robot-testing-framework.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 686 days old (needed 5 days)
    • Remove hint for (transitive) dependency: libast, netkit-telnet-ssl
• ruby-distribution (- to 0.8.0+dfsg-1)
  • Migration status for ruby-distribution (- to 0.8.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-distribution would introduce bugs in testing: #1110788
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-distribution.html
    • autopkgtest for ruby-distribution/0.8.0+dfsg-1: amd64: Pass, arm64: Pass, 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
    • 688 days old (needed 2 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:
    • python3-certbot-dns-gandi/amd64 has unsatisfiable dependency
    • python3-certbot-dns-gandi/arm64 has unsatisfiable dependency
    • Updating python-certbot-dns-gandi would introduce bugs in testing: #1038920, #1106471
    • python-certbot-dns-gandi unsatisfiable Build-Depends(-Arch) on amd64: python3-certbot-abi-2 | python3-certbot-abi-1
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-certbot-dns-gandi.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 695 days old (needed 5 days)
• empire-hub (- to 1.0.2.2+nmu1)
  • Migration status for empire-hub (- to 1.0.2.2+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating empire-hub would introduce bugs in testing: #1074937
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/empire-hub.html
    • 697 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
    • 698 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xflags-macros.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 698 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: Failed ♻, arm64: Failed ♻, ppc64el: Failed ♻, riscv64: Test triggered (failure will be ignored), s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/canu.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 700 days old (needed 5 days)
• rust-xflags (- to 0.3.1-1)
  • Migration status for rust-xflags (- to 0.3.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): rust-xflags rust-xflags-macros (not considered)
    • Depends: rust-xflags rust-xflags-macros (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-xflags.html
    • autopkgtest for rust-xflags/0.3.1-1: amd64: Pass, arm64: Pass, 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
    • 704 days old (needed 2 days)
• cdde (- to 0.3.1-1.1)
  • Migration status for cdde (- to 0.3.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cdde would introduce bugs in testing: #1066301
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cdde.html
    • 707 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
    • 715 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, #1102627
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jh7100-bootloader-recovery.html
    • 723 days old (needed 5 days)
• fbb (- to 7.011-3)
  • Migration status for fbb (- to 7.011-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fbb would introduce bugs in testing: #1091298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fbb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 724 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, i386: Failed ♻, 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 ♻
    • 728 days old (needed 5 days)
• jack-tools (- to 20131226-2)
  • Migration status for jack-tools (- to 20131226-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jack-tools would introduce bugs in testing: #1075097
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jack-tools.html
    • 732 days old (needed 5 days)
• materia-kde (- to 20220823-2)
  • Migration status for materia-kde (- to 20220823-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating materia-kde would introduce bugs in testing: #1091373
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/materia-kde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 733 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/armhf has unsatisfiable dependency
    • xpra/i386 has unsatisfiable dependency
    • xpra/ppc64el has unsatisfiable dependency
    • xpra/riscv64 has unsatisfiable dependency
    • xpra/s390x has unsatisfiable dependency
    • Updating xpra would introduce bugs in testing: #1067627, #1072463, #1086122, #1101929
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/x/xpra.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 736 days old (needed 5 days)
• cclib (- to 1.8-1)
  • Migration status for cclib (- to 1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cclib would introduce bugs in testing: #1108852
    • autopkgtest for cclib/1.8-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cclib.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 740 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• frama-c (- to 20220511-manganese-5)
  • Migration status for frama-c (- to 20220511-manganese-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • frama-c-base/amd64 has unsatisfiable dependency
    • frama-c-base/arm64 has unsatisfiable dependency
    • frama-c-base/armhf has unsatisfiable dependency
    • frama-c-base/i386 has unsatisfiable dependency
    • frama-c-base/ppc64el has unsatisfiable dependency
    • frama-c-base/riscv64 has unsatisfiable dependency
    • frama-c-base/s390x has unsatisfiable dependency
    • Updating frama-c would introduce bugs in testing: #1093102
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/frama-c.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 742 days old (needed 5 days)
• vuls (- to 0.6.1-5)
  • Migration status for vuls (- to 0.6.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vuls would introduce bugs in testing: #1085477
    • autopkgtest for vuls/0.6.1-5: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): vuls go-cve-dictionary (not considered)
    • Build-Depends(-Arch): vuls go-exploitdb (not considered)
    • Build-Depends(-Arch): vuls gost (not considered)
    • Build-Depends(-Arch): vuls goval-dictionary (not considered)
    • Built-Using: vuls go-cve-dictionary (not considered)
    • Built-Using: vuls go-exploitdb (not considered)
    • Built-Using: vuls golang-github-go-redis-redis (not considered)
    • Built-Using: vuls gost (not considered)
    • Built-Using: vuls goval-dictionary (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vuls.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 744 days old (needed 5 days)
• gcc-11-cross-mipsen (- to 6+c1+nmu1)
  • Migration status for gcc-11-cross-mipsen (- to 6+c1+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-11-cross-mipsen would introduce bugs in testing: #1032167, #1089256, #1089881
    • Build-Depends(-Arch): gcc-11-cross-mipsen gcc-11 (not considered)
    • Built-Using: gcc-11-cross-mipsen gcc-11 (not considered)
    • Depends: gcc-11-cross-mipsen gcc-11 (not considered)
    • Depends: gcc-11-cross-mipsen gcc-12-cross-mipsen (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gcc-11-cross-mipsen.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 747 days old (needed 5 days)
• w3cam (- to 0.7.2-6.4)
  • Migration status for w3cam (- to 0.7.2-6.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating w3cam would introduce bugs in testing: #1091279, #1113987
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/w3cam.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 747 days old (needed 5 days)
• haskell-hosc (- to 0.20-1)
  • Migration status for haskell-hosc (- to 0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hosc-doc/amd64 has unsatisfiable dependency
    • libghc-hosc-doc/arm64 has unsatisfiable dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hosc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 749 days old (needed 5 days)
• mmh (- to 0.4-6)
  • Migration status for mmh (- to 0.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mmh would introduce bugs in testing: #1075280, #1076958
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mmh.html
    • 750 days old (needed 5 days)
• ormar (- to 0.12.2-1)
  • Migration status for ormar (- to 0.12.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ormar would introduce bugs in testing: #1066769
    • autopkgtest for ormar/0.12.2-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ormar.html
    • 750 days old (needed 5 days)
• mia (- to 2.4.7-13)
  • Migration status for mia (- to 2.4.7-13): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libmia-2.4-4/amd64 has unsatisfiable dependency
    • mia-tools/amd64 has unsatisfiable dependency
    • libmia-2.4-4/arm64 has unsatisfiable dependency
    • mia-tools/arm64 has unsatisfiable dependency
    • libmia-2.4-4/armhf has unsatisfiable dependency
    • mia-tools/armhf has unsatisfiable dependency
    • libmia-2.4-4/i386 has unsatisfiable dependency
    • mia-tools/i386 has unsatisfiable dependency
    • libmia-2.4-4/ppc64el has unsatisfiable dependency
    • mia-tools/ppc64el has unsatisfiable dependency
    • libmia-2.4-4/riscv64 has unsatisfiable dependency
    • mia-tools/riscv64 has unsatisfiable dependency
    • libmia-2.4-4/s390x has unsatisfiable dependency
    • mia-tools/s390x has unsatisfiable dependency
    • Updating mia would introduce bugs in testing: #1075270
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/m/mia.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 753 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• shapetools-tutorial (- to 1.3-6)
  • Migration status for shapetools-tutorial (- to 1.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shapetools-tutorial would introduce bugs in testing: #1102700
    • Depends: shapetools-tutorial shapetools (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 758 days old (needed 5 days)
• python-oauth2client (- to 4.1.3-5)
  • Migration status for python-oauth2client (- to 4.1.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-oauth2client would introduce bugs in testing: #1058392, #1066132
    • autopkgtest for python-oauth2client/4.1.3-5: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • python-oauth2client unsatisfiable Build-Depends-Indep on amd64: python3-unittest2
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-oauth2client.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 764 days old (needed 5 days)
• go-cve-dictionary (- to 0.3.1-5)
  • Migration status for go-cve-dictionary (- to 0.3.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating go-cve-dictionary would introduce bugs in testing: #1085476, #1114131
    • autopkgtest for go-cve-dictionary/0.3.1-5: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: go-cve-dictionary golang-github-go-redis-redis (not considered)
    • Depends: go-cve-dictionary golang-github-go-redis-redis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-cve-dictionary.html
    • 765 days old (needed 5 days)
• gost (- to 0.1.2-2)
  • Migration status for gost (- to 0.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gost would introduce bugs in testing: #1085479
    • Build-Depends(-Arch): gost golang-github-go-redis-redis (not considered)
    • Built-Using: gost golang-github-go-redis-redis (not considered)
    • Depends: gost golang-github-go-redis-redis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gost.html
    • autopkgtest for gost/0.1.2-2: amd64: Pass, arm64: Pass, 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
    • 765 days old (needed 2 days)
• goval-dictionary (- to 0.2.0-6)
  • Migration status for goval-dictionary (- to 0.2.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating goval-dictionary would introduce bugs in testing: #1085471
    • Build-Depends(-Arch): goval-dictionary golang-github-go-redis-redis (not considered)
    • Built-Using: goval-dictionary golang-github-go-redis-redis (not considered)
    • Depends: goval-dictionary golang-github-go-redis-redis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/goval-dictionary.html
    • autopkgtest for goval-dictionary/0.2.0-6: amd64: Pass, arm64: Pass, 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
    • 765 days old (needed 2 days)
• go-exploitdb (- to 0.0~git20181130.7c961e7-3)
  • Migration status for go-exploitdb (- to 0.0~git20181130.7c961e7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating go-exploitdb would introduce bugs in testing: #1085478
    • Build-Depends(-Arch): go-exploitdb golang-github-go-redis-redis (not considered)
    • Built-Using: go-exploitdb golang-github-go-redis-redis (not considered)
    • Depends: go-exploitdb golang-github-go-redis-redis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/go-exploitdb.html
    • autopkgtest for go-exploitdb/0.0~git20181130.7c961e7-3: amd64: Pass, arm64: Pass, 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
    • 766 days old (needed 2 days)
• libengine-gost-openssl (- to 3.0.2-1)
  • Migration status for libengine-gost-openssl (- to 3.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • gostsum/armhf has unsatisfiable dependency
    • libengine-gost-openssl/armhf has unsatisfiable dependency
    • Updating libengine-gost-openssl would introduce bugs in testing: #1054922, #1115372
    • missing build on s390x
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results on s390x - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libe/libengine-gost-openssl.html
    • 767 days old (needed 5 days)
• xemacs21 (- to 21.4.24-12)
  • Migration status for xemacs21 (- to 21.4.24-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xemacs21 would introduce bugs in testing: #1075659, #1095538
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/amd64
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/arm64
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/armhf
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/i386
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/ppc64el
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/riscv64
    • Impossible Depends: xemacs21 -> libldap-2.5-0/2.5.19+dfsg-1/s390x
    • Build-Depends(-Arch): xemacs21 autoconf2.13 (not considered)
    • Depends: xemacs21 xemacs21-packages
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xemacs21.html
    • 767 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 ♻
    • 768 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/searx.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 768 days old (needed 5 days)
• ocamlmakefile (- to 6.39.2-2)
  • Migration status for ocamlmakefile (- to 6.39.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ocamlmakefile would introduce bugs in testing: #1108815
    • autopkgtest for ocamlmakefile/6.39.2-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocamlmakefile.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 770 days old (needed 5 days)
• ckeditor (- to 4.22.1+dfsg1-2)
  • Migration status for ckeditor (- to 4.22.1+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ckeditor would introduce bugs in testing: #1102677
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ckeditor.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 781 days old (needed 5 days)
• sptag (- to 0.0~git20230612.2ffaec6+ds-4)
  • Migration status for sptag (- to 0.0~git20230612.2ffaec6+ds-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sptag would introduce bugs in testing: #1091119
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sptag.html
    • autopkgtest for sptag/0.0~git20230612.2ffaec6+ds-4: amd64: No tests, superficial or marked flaky ♻
    • Reproducible on amd64 - info ♻
    • 786 days old (needed 5 days)
• openmw (- to 0.48.0-1)
  • Migration status for openmw (- to 0.48.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • openmw/amd64 has unsatisfiable dependency
    • openmw/arm64 has unsatisfiable dependency
    • openmw/armhf has unsatisfiable dependency
    • openmw/i386 has unsatisfiable dependency
    • openmw/s390x has unsatisfiable dependency
    • Updating openmw would introduce bugs in testing: #1072443, #1075344, #1108767
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openmw.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 791 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• python-tinyrpc (- to 0.6-5)
  • Migration status for python-tinyrpc (- to 0.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-tinyrpc would introduce bugs in testing: #1084578, #1090165
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-tinyrpc.html
    • autopkgtest for python-tinyrpc/0.6-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 792 days old (needed 5 days)
• renderdoc (- to 1.27+dfsg-1)
  • Migration status for renderdoc (- to 1.27+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • qrenderdoc/amd64 has unsatisfiable dependency
    • Updating renderdoc would introduce bugs in testing: #1067012, #999924
    • renderdoc unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • uninstallable on arch amd64, not running autopkgtest there
    • 798 days old (needed 5 days)
• rust-packed-simd (- to 0.3.8-1)
  • Migration status for rust-packed-simd (- to 0.3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-packed-simd would introduce bugs in testing: #1077952
    • autopkgtest for rust-packed-simd/0.3.8-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-packed-simd.html
    • 798 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 ♻
    • 799 days old (needed 5 days)
• libsendmail-milter-perl (- to 0.18-10)
  • Migration status for libsendmail-milter-perl (- to 0.18-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libsendmail-milter-perl would introduce bugs in testing: #807392
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libs/libsendmail-milter-perl.html
    • autopkgtest for libsendmail-milter-perl/0.18-10: amd64: Pass, arm64: 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
    • 803 days old (needed 2 days)
• php-gettext (- to 1.0.12-6)
  • Migration status for php-gettext (- to 1.0.12-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-gettext would introduce bugs in testing: #1092095
    • autopkgtest for php-gettext/1.0.12-6: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-gettext.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 809 days old (needed 5 days)
• golang-github-form3tech-oss-jwt-go (- to 3.2.3-2)
  • Migration status for golang-github-form3tech-oss-jwt-go (- to 3.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-form3tech-oss-jwt-go would introduce bugs in testing: #1038793, #1042736
    • autopkgtest for golang-github-form3tech-oss-jwt-go/3.2.3-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-form3tech-oss-jwt-go.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 822 days old (needed 5 days)
• xwrited (- to 3-2)
  • Migration status for xwrited (- to 3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xwrited would introduce bugs in testing: #1076333
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xwrited.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 822 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django-ical.html
    • 823 days old (needed 5 days)
• buzztrax (- to 0.10.2-9)
  • Migration status for buzztrax (- to 0.10.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating buzztrax would introduce bugs in testing: #1018114
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/buzztrax.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 827 days old (needed 5 days)
• ipmctl (- to 03.00.00.0485-1)
  • Migration status for ipmctl (- to 03.00.00.0485-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ipmctl would introduce bugs in testing: #1084577
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ipmctl.html
    • Reproducible on amd64 - info ♻
    • 830 days old (needed 5 days)
• mac-fdisk (- to 0.1-18.1)
  • Migration status for mac-fdisk (- to 0.1-18.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating mac-fdisk would introduce bugs in testing: #1091564
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 857 days old (needed 5 days)
• php-horde-mime-viewer (- to 2.2.4+debian0-2)
  • Migration status for php-horde-mime-viewer (- to 2.2.4+debian0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-mime-viewer php-horde-util (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-mime-viewer pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-mime-viewer php-horde-role
    • Depends: php-horde-mime-viewer php-horde-browser
    • Depends: php-horde-mime-viewer php-horde-compress (not considered)
    • Depends: php-horde-mime-viewer php-horde-exception (not considered)
    • Depends: php-horde-mime-viewer php-horde-mime (not considered)
    • Depends: php-horde-mime-viewer php-horde-text-filter (not considered)
    • Depends: php-horde-mime-viewer php-horde-text-flowed (not considered)
    • Depends: php-horde-mime-viewer php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mime-viewer.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 857 days old (needed 5 days)
• ruby-kakasi-ffi (- to 1.0.2-4)
  • Migration status for ruby-kakasi-ffi (- to 1.0.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-kakasi-ffi would introduce bugs in testing: #1109023
    • autopkgtest for ruby-kakasi-ffi/1.0.2-4: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-kakasi-ffi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 888 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/ponyorm.html
    • 896 days old (needed 5 days)
• ocrfeeder (- to 0.8.5-1)
  • Migration status for ocrfeeder (- to 0.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ocrfeeder would introduce bugs in testing: #1074646, #1084529, #1099552
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocrfeeder.html
    • 909 days old (needed 5 days)
• ruby-omniauth-oauth2-generic (- to 0.2.8-1)
  • Migration status for ruby-omniauth-oauth2-generic (- to 0.2.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-oauth2-generic would introduce bugs in testing: #1109026
    • autopkgtest for ruby-omniauth-oauth2-generic/0.2.8-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-oauth2-generic.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 911 days old (needed 5 days)
• gitlab-ci-multi-runner (- to 14.10.1-1)
  • Migration status for gitlab-ci-multi-runner (- to 14.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gitlab-ci-multi-runner would introduce bugs in testing: #1080062, #1086672
    • lintian triggered tags: aliased-location - info
    • 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/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
    • Built-Using: gitlab-ci-multi-runner golang-github-golang-protobuf-1-3 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gitlab-ci-multi-runner.html
    • 912 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/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
    • 922 days old (needed 5 days)
• php-horde-kolab-storage (- to 2.2.4-5)
  • Migration status for php-horde-kolab-storage (- to 2.2.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-kolab-storage/2.2.4-5: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-kolab-storage pear-channels (not considered)
    • Depends: php-horde-kolab-storage php-horde-cache (not considered)
    • Depends: php-horde-kolab-storage php-horde-exception (not considered)
    • Depends: php-horde-kolab-storage php-horde-kolab-format (not considered)
    • Depends: php-horde-kolab-storage php-horde-mime (not considered)
    • Depends: php-horde-kolab-storage php-horde-support (not considered)
    • Depends: php-horde-kolab-storage php-horde-translation (not considered)
    • Depends: php-horde-kolab-storage php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-storage.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 922 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • 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 ♻
    • 924 days old (needed 5 days)
• debian-timeline (- to 46)
  • Migration status for debian-timeline (- to 46): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating debian-timeline would introduce bugs in testing: #655664
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/debian-timeline.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 934 days old (needed 5 days)
• firmware-microbit-micropython (- to 1.0.1-4)
  • Migration status for firmware-microbit-micropython (- to 1.0.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating firmware-microbit-micropython would introduce bugs in testing: #1073304
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/firmware-microbit-micropython.html
    • 939 days old (needed 5 days)
• vertx-docgen (- to 0.9.4-2)
  • Migration status for vertx-docgen (- to 0.9.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vertx-docgen would introduce bugs in testing: #1081475
    • Build-Depends(-Arch): vertx-docgen openjdk-11 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vertx-docgen.html
    • 939 days old (needed 5 days)
• oregano (- to 0.84.41+dfsg.1-1.1)
  • Migration status for oregano (- to 0.84.41+dfsg.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating oregano would introduce bugs in testing: #1051281, #1081089, #1112060, #1112061
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/oregano.html
    • 944 days old (needed 5 days)
• php-horde-exception (- to 2.0.8-10)
  • Migration status for php-horde-exception (- to 2.0.8-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-exception/2.0.8-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-exception pear-channels (not considered)
    • Depends: php-horde-exception php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-exception.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 947 days old (needed 5 days)
• php-horde-kolab-format (- to 2.0.9-8)
  • Migration status for php-horde-kolab-format (- to 2.0.9-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-kolab-format/2.0.9-8: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-kolab-format pear-channels (not considered)
    • Depends: php-horde-kolab-format php-horde-exception (not considered)
    • Depends: php-horde-kolab-format php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-format.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 947 days old (needed 5 days)
• php-horde-kolab-session (- to 2.0.3-10)
  • Migration status for php-horde-kolab-session (- to 2.0.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-kolab-session would introduce bugs in testing: #1089775
    • autopkgtest for php-horde-kolab-session/2.0.3-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-kolab-session pear-channels (not considered)
    • Depends: php-horde-kolab-session php-horde-exception (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-session.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 947 days old (needed 5 days)
• php-horde-group (- to 2.1.1-12)
  • Migration status for php-horde-group (- to 2.1.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-group/2.1.1-12: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-group pear-channels (not considered)
    • Depends: php-horde-group php-horde-exception (not considered)
    • Depends: php-horde-group php-horde-support (not considered)
    • Depends: php-horde-group php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-group.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 950 days old (needed 5 days)
• php-horde-ldap (- to 2.4.2-6)
  • Migration status for php-horde-ldap (- to 2.4.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-ldap/2.4.2-6: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-ldap pear-channels (not considered)
    • Depends: php-horde-ldap php-horde-exception (not considered)
    • Depends: php-horde-ldap php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ldap.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 951 days old (needed 5 days)
• kworkflow (- to 20191112-1.2)
  • Migration status for kworkflow (- to 20191112-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kworkflow would introduce bugs in testing: #1110187
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kworkflow.html
    • autopkgtest for kworkflow/20191112-1.2: amd64: Pass, arm64: 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
    • 952 days old (needed 2 days)
• libgrokj2k (- to 10.0.5-1)
  • Migration status for libgrokj2k (- to 10.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libgrokj2k1/armhf has unsatisfiable dependency
    • Updating libgrokj2k would introduce bugs in testing: #1085165
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libg/libgrokj2k.html
    • Reproducible on amd64 - info ♻
    • 953 days old (needed 5 days)
• php-horde-wicked (- to 2.0.8-9)
  • Migration status for php-horde-wicked (- to 2.0.8-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-wicked/2.0.8-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-wicked pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-wicked php-horde-role
    • Depends: php-horde-wicked php-horde (not considered)
    • Depends: php-horde-wicked php-horde-auth (not considered)
    • Depends: php-horde-wicked php-horde-autoloader (not considered)
    • Depends: php-horde-wicked php-horde-core (not considered)
    • Depends: php-horde-wicked php-horde-db (not considered)
    • Depends: php-horde-wicked php-horde-exception (not considered)
    • Depends: php-horde-wicked php-horde-form
    • Depends: php-horde-wicked php-horde-http (not considered)
    • Depends: php-horde-wicked php-horde-lock (not considered)
    • Depends: php-horde-wicked php-horde-mail (not considered)
    • Depends: php-horde-wicked php-horde-mime (not considered)
    • Depends: php-horde-wicked php-horde-mime-viewer
    • Depends: php-horde-wicked php-horde-notification (not considered)
    • Depends: php-horde-wicked php-horde-perms (not considered)
    • Depends: php-horde-wicked php-horde-prefs (not considered)
    • Depends: php-horde-wicked php-horde-rpc
    • Depends: php-horde-wicked php-horde-text-diff (not considered)
    • Depends: php-horde-wicked php-horde-url (not considered)
    • Depends: php-horde-wicked php-horde-util (not considered)
    • Depends: php-horde-wicked php-horde-vfs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-wicked.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 953 days old (needed 5 days)
• adv-17v35x (- to 5.0.7.0-1)
  • Migration status for adv-17v35x (- to 5.0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating adv-17v35x would introduce bugs in testing: #1077217
    • autopkgtest for adv-17v35x/5.0.7.0-1: amd64: Failed ♻, arm64: Failed ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/a/adv-17v35x.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 954 days old (needed 5 days)
• golang-github-russellhaering-goxmldsig (- to 1.2.0-1)
  • Migration status for golang-github-russellhaering-goxmldsig (- to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-russellhaering-goxmldsig would introduce bugs in testing: #1078620
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-russellhaering-goxmldsig.html
    • autopkgtest for golang-github-russellhaering-goxmldsig/1.2.0-1: amd64: Pass, arm64: 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
    • 955 days old (needed 2 days)
• ruby-arbre (- to 1.5.0-1)
  • Migration status for ruby-arbre (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-arbre/amd64 has unsatisfiable dependency
    • ruby-arbre/arm64 has unsatisfiable dependency
    • Updating ruby-arbre would introduce bugs in testing: #1095379, #1106505
    • ruby-arbre unsatisfiable Build-Depends(-Arch) on amd64: ruby-activesupport (<< 2:7.1)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-arbre.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 955 days old (needed 5 days)
• sagemath (- to 9.5-6)
  • Migration status for sagemath (- to 9.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-sage/amd64 has unsatisfiable dependency
    • sagemath-jupyter/amd64 has unsatisfiable dependency
    • python3-sage/arm64 has unsatisfiable dependency
    • sagemath-jupyter/arm64 has unsatisfiable dependency
    • python3-sage/i386 has unsatisfiable dependency
    • Updating sagemath would introduce bugs in testing: #1042683, #1042935, #1050182, #1052051, #1056885, #1065953, #1076651
    • sagemath unsatisfiable Build-Depends(-Arch) on amd64: python3-distutils
    • sagemath unsatisfiable Build-Depends(-Arch) on amd64: libflint-arb-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on amd64: libsymmetrica2-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on amd64: jupyter-nbextension-jupyter-js-widgets
    • sagemath unsatisfiable Build-Depends(-Arch) on arm64: python3-distutils
    • sagemath unsatisfiable Build-Depends(-Arch) on arm64: libflint-arb-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on arm64: libsymmetrica2-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on arm64: jupyter-nbextension-jupyter-js-widgets
    • sagemath unsatisfiable Build-Depends(-Arch) on i386: python3-distutils
    • sagemath unsatisfiable Build-Depends(-Arch) on i386: libflint-arb-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on i386: libsymmetrica2-dev
    • sagemath unsatisfiable Build-Depends(-Arch) on i386: jupyter-nbextension-jupyter-js-widgets
    • Build-Depends(-Arch): sagemath brial (not considered)
    • Build-Depends(-Arch): sagemath cypari2 (not considered)
    • Build-Depends(-Arch): sagemath sagenb-export (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/sagemath.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 955 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis, edge-addition-planarity-suite
• 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/armhf has unsatisfiable dependency
    • python3-segyio/i386 has unsatisfiable dependency
    • python3-segyio/ppc64el has unsatisfiable dependency
    • python3-segyio/riscv64 has unsatisfiable dependency
    • python3-segyio/s390x has unsatisfiable dependency
    • Updating segyio would introduce bugs in testing: #1055728
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/s/segyio.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 955 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• 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
  • 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 ♻
    • 956 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gruff.html
    • 956 days old (needed 5 days)
• pyemd (- to 0.5.1.54.g802fa86-2)
  • Migration status for pyemd (- to 0.5.1.54.g802fa86-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-pyemd/amd64 has unsatisfiable dependency
    • python3-pyemd/arm64 has unsatisfiable dependency
    • python3-pyemd/armhf has unsatisfiable dependency
    • python3-pyemd/i386 has unsatisfiable dependency
    • python3-pyemd/ppc64el has unsatisfiable dependency
    • python3-pyemd/riscv64 has unsatisfiable dependency
    • python3-pyemd/s390x has unsatisfiable dependency
    • Updating pyemd would introduce bugs in testing: #1080277, #1103403
    • Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/p/pyemd.html
    • pyemd unsatisfiable Build-Depends(-Arch) on amd64: python3-numpy (<< 1:2.0.0)
    • pyemd unsatisfiable Build-Depends(-Arch) on arm64: python3-numpy (<< 1:2.0.0)
    • pyemd unsatisfiable Build-Depends(-Arch) on armhf: python3-numpy (<< 1:2.0.0)
    • pyemd unsatisfiable Build-Depends(-Arch) on i386: python3-numpy (<< 1:2.0.0)
    • pyemd unsatisfiable Build-Depends(-Arch) on ppc64el: python3-numpy (<< 1:2.0.0)
    • pyemd unsatisfiable Build-Depends(-Arch) on riscv64: python3-numpy (<< 1:2.0.0)
    • pyemd unsatisfiable Build-Depends(-Arch) on s390x: python3-numpy (<< 1:2.0.0)
  • Additional info:
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 957 days old (needed 5 days)
• python-aioxmpp (- to 0.13.3-1)
  • Migration status for python-aioxmpp (- to 0.13.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aioxmpp would introduce bugs in testing: #1042239
    • Build-Depends(-Arch): python-aioxmpp python-aioopenssl (not considered)
    • Depends: python-aioxmpp python-aioopenssl (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioxmpp.html
    • 957 days old (needed 5 days)
• xen-tools (- to 4.9.2-1)
  • Migration status for xen-tools (- to 4.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xen-tools would introduce bugs in testing: #1092454
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xen-tools.html
    • autopkgtest for xen-tools/4.9.2-1: amd64: Pass, arm64: Pass, 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
    • 957 days old (needed 2 days)
• webalizer (- to 2.23.08-3.3)
  • Migration status for webalizer (- to 2.23.08-3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating webalizer would introduce bugs in testing: #1075635
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/webalizer.html
    • 958 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 ♻
    • 959 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, #1101710
    • autopkgtest for polyml/5.7.1-5: amd64: Pass, arm64: Failed ♻, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/polyml.html
    • New but not reproducible on arm64 - info ♻
    • 960 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
    • 962 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• ruby-async-http (- to 0.59.5-1)
  • Migration status for ruby-async-http (- to 0.59.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ruby-async-http ruby-protocol-http1 (not considered)
    • Depends: ruby-async-http ruby-protocol-http1 (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-async-http.html
    • autopkgtest for ruby-async-http/0.59.5-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 963 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde would introduce bugs in testing: #1068183, #1102702
    • Build-Depends(-Arch): php-horde pear-channels (not considered)
    • Build-Depends(-Arch): php-horde php-horde-role
    • Depends: php-horde php-horde-alarm (not considered)
    • Depends: php-horde php-horde-argv (not considered)
    • Depends: php-horde php-horde-auth (not considered)
    • Depends: php-horde php-horde-autoloader (not considered)
    • Depends: php-horde php-horde-browser
    • Depends: php-horde php-horde-core (not considered)
    • Depends: php-horde php-horde-date (not considered)
    • Depends: php-horde php-horde-exception (not considered)
    • Depends: php-horde php-horde-form
    • Depends: php-horde php-horde-group (not considered)
    • Depends: php-horde php-horde-http (not considered)
    • Depends: php-horde php-horde-image (not considered)
    • Depends: php-horde php-horde-logintasks (not considered)
    • Depends: php-horde php-horde-mail (not considered)
    • Depends: php-horde php-horde-mime (not considered)
    • Depends: php-horde php-horde-nls
    • Depends: php-horde php-horde-perms (not considered)
    • Depends: php-horde php-horde-prefs (not considered)
    • Depends: php-horde php-horde-role
    • Depends: php-horde php-horde-rpc
    • Depends: php-horde php-horde-serialize (not considered)
    • Depends: php-horde php-horde-support (not considered)
    • Depends: php-horde php-horde-text-diff (not considered)
    • Depends: php-horde php-horde-text-filter (not considered)
    • Depends: php-horde php-horde-token (not considered)
    • Depends: php-horde php-horde-tree (not considered)
    • Depends: php-horde php-horde-url (not considered)
    • Depends: php-horde php-horde-util (not considered)
    • Depends: php-horde php-horde-vfs (not considered)
    • Depends: php-horde php-horde-view (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 966 days old (needed 5 days)
• php-horde-alarm (- to 2.2.10-10)
  • Migration status for php-horde-alarm (- to 2.2.10-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-alarm/2.2.10-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-alarm pear-channels (not considered)
    • Depends: php-horde-alarm php-horde-date (not considered)
    • Depends: php-horde-alarm php-horde-exception (not considered)
    • Depends: php-horde-alarm php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-alarm.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 966 days old (needed 5 days)
• php-horde-browser (- to 2.0.16-5)
  • Migration status for php-horde-browser (- to 2.0.16-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-browser php-horde-util (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-browser pear-channels (not considered)
    • Depends: php-horde-browser php-horde-exception (not considered)
    • Depends: php-horde-browser php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-browser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 966 days old (needed 5 days)
• php-horde-cache (- to 2.5.5-11)
  • Migration status for php-horde-cache (- to 2.5.5-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-cache/2.5.5-11: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-cache pear-channels (not considered)
    • Depends: php-horde-cache php-horde-compress-fast (not considered)
    • Depends: php-horde-cache php-horde-exception (not considered)
    • Depends: php-horde-cache php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-cache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 966 days old (needed 5 days)
• php-horde-kolab-server (- to 2.0.5-10)
  • Migration status for php-horde-kolab-server (- to 2.0.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-kolab-server would introduce bugs in testing: #1089774
    • autopkgtest for php-horde-kolab-server/2.0.5-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-kolab-server pear-channels (not considered)
    • Depends: php-horde-kolab-server php-horde-auth (not considered)
    • Depends: php-horde-kolab-server php-horde-exception (not considered)
    • Depends: php-horde-kolab-server php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kolab-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 966 days old (needed 5 days)
• php-horde-view (- to 2.0.6-10)
  • Migration status for php-horde-view (- to 2.0.6-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-view/2.0.6-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-view pear-channels (not considered)
    • Depends: php-horde-view php-horde-exception (not considered)
    • Depends: php-horde-view php-horde-support (not considered)
    • Depends: php-horde-view php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-view.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 966 days old (needed 5 days)
• php-horde-argv (- to 2.1.0-9)
  • Migration status for php-horde-argv (- to 2.1.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-argv/2.1.0-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-argv pear-channels (not considered)
    • Depends: php-horde-argv php-horde-cli
    • Depends: php-horde-argv php-horde-exception (not considered)
    • Depends: php-horde-argv php-horde-translation (not considered)
    • Depends: php-horde-argv php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-argv.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 967 days old (needed 5 days)
• php-horde-core (- to 2.31.18+debian0-2)
  • Migration status for php-horde-core (- to 2.31.18+debian0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-core would introduce bugs in testing: #1059770, #1089769
    • autopkgtest for php-horde-core/2.31.18+debian0-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-core pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-core php-horde-role
    • Depends: php-horde-core php-horde-alarm (not considered)
    • Depends: php-horde-core php-horde-auth (not considered)
    • Depends: php-horde-core php-horde-autoloader (not considered)
    • Depends: php-horde-core php-horde-browser
    • Depends: php-horde-core php-horde-cache (not considered)
    • Depends: php-horde-core php-horde-cli
    • Depends: php-horde-core php-horde-compress (not considered)
    • Depends: php-horde-core php-horde-compress-fast (not considered)
    • Depends: php-horde-core php-horde-controller (not considered)
    • Depends: php-horde-core php-horde-cssminify
    • Depends: php-horde-core php-horde-data (not considered)
    • Depends: php-horde-core php-horde-date (not considered)
    • Depends: php-horde-core php-horde-exception (not considered)
    • Depends: php-horde-core php-horde-group (not considered)
    • Depends: php-horde-core php-horde-hashtable (not considered)
    • Depends: php-horde-core php-horde-history (not considered)
    • Depends: php-horde-core php-horde-injector (not considered)
    • Depends: php-horde-core php-horde-javascriptminify (not considered)
    • Depends: php-horde-core php-horde-lock (not considered)
    • Depends: php-horde-core php-horde-log (not considered)
    • Depends: php-horde-core php-horde-logintasks (not considered)
    • Depends: php-horde-core php-horde-mime (not considered)
    • Depends: php-horde-core php-horde-mime-viewer
    • Depends: php-horde-core php-horde-notification (not considered)
    • Depends: php-horde-core php-horde-pack (not considered)
    • Depends: php-horde-core php-horde-perms (not considered)
    • Depends: php-horde-core php-horde-prefs (not considered)
    • Depends: php-horde-core php-horde-secret (not considered)
    • Depends: php-horde-core php-horde-serialize (not considered)
    • Depends: php-horde-core php-horde-sessionhandler (not considered)
    • Depends: php-horde-core php-horde-share (not considered)
    • Depends: php-horde-core php-horde-support (not considered)
    • Depends: php-horde-core php-horde-template (not considered)
    • Depends: php-horde-core php-horde-text-filter (not considered)
    • Depends: php-horde-core php-horde-token (not considered)
    • Depends: php-horde-core php-horde-translation (not considered)
    • Depends: php-horde-core php-horde-url (not considered)
    • Depends: php-horde-core php-horde-util (not considered)
    • Depends: php-horde-core php-horde-view (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-core.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 967 days old (needed 5 days)
• php-horde-crypt (- to 2.7.12-9)
  • Migration status for php-horde-crypt (- to 2.7.12-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-crypt would introduce bugs in testing: #1089770
    • autopkgtest for php-horde-crypt/2.7.12-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-crypt pear-channels (not considered)
    • Depends: php-horde-crypt php-horde-exception (not considered)
    • Depends: php-horde-crypt php-horde-http (not considered)
    • Depends: php-horde-crypt php-horde-mime (not considered)
    • Depends: php-horde-crypt php-horde-stream (not considered)
    • Depends: php-horde-crypt php-horde-stream-filter (not considered)
    • Depends: php-horde-crypt php-horde-translation (not considered)
    • Depends: php-horde-crypt php-horde-url (not considered)
    • Depends: php-horde-crypt php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-crypt.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 967 days old (needed 5 days)
• php-horde-idna (- to 1.1.2-6)
  • Migration status for php-horde-idna (- to 1.1.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-idna/1.1.2-6: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-idna pear-channels (not considered)
    • Depends: php-horde-idna php-horde-exception (not considered)
    • Depends: php-horde-idna php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-idna.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 967 days old (needed 5 days)
• php-horde-mail (- to 2.6.6-5)
  • Migration status for php-horde-mail (- to 2.6.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-mail/2.6.6-5: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-mail pear-channels (not considered)
    • Depends: php-horde-mail php-horde-exception (not considered)
    • Depends: php-horde-mail php-horde-idna (not considered)
    • Depends: php-horde-mail php-horde-stream-filter (not considered)
    • Depends: php-horde-mail php-horde-translation (not considered)
    • Depends: php-horde-mail php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 967 days old (needed 5 days)
• php-horde-rdo (- to 2.1.0-10)
  • Migration status for php-horde-rdo (- to 2.1.0-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-rdo/2.1.0-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-rdo pear-channels (not considered)
    • Depends: php-horde-rdo php-horde-db (not considered)
    • Depends: php-horde-rdo php-horde-exception (not considered)
    • Depends: php-horde-rdo php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-rdo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 967 days old (needed 5 days)
• php-horde-service-gravatar (- to 1.0.1-10)
  • Migration status for php-horde-service-gravatar (- to 1.0.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-service-gravatar/1.0.1-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-service-gravatar pear-channels (not considered)
    • Depends: php-horde-service-gravatar php-horde-http (not considered)
    • Depends: php-horde-service-gravatar php-horde-url (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-service-gravatar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 967 days old (needed 5 days)
• php-horde-service-weather (- to 2.5.6-1)
  • Migration status for php-horde-service-weather (- to 2.5.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-service-weather/2.5.6-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-service-weather pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-service-weather php-horde-role
    • Depends: php-horde-service-weather php-horde-date (not considered)
    • Depends: php-horde-service-weather php-horde-exception (not considered)
    • Depends: php-horde-service-weather php-horde-http (not considered)
    • Depends: php-horde-service-weather php-horde-translation (not considered)
    • Depends: php-horde-service-weather php-horde-url (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-service-weather.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 967 days old (needed 5 days)
• php-horde-test (- to 2.6.4+debian0-9)
  • Migration status for php-horde-test (- to 2.6.4+debian0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-test php-horde-util (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-test pear-channels (not considered)
    • Depends: php-horde-test php-horde-support (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-test.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 967 days old (needed 5 days)
• securefs (- to 0.13.1+ds-1)
  • Migration status for securefs (- to 0.13.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating securefs would introduce bugs in testing: #1035739
    • autopkgtest for securefs/0.13.1+ds-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/securefs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 967 days old (needed 5 days)
• php-horde-http (- to 2.1.7-11)
  • Migration status for php-horde-http (- to 2.1.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-http/2.1.7-11: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-http pear-channels (not considered)
    • Depends: php-horde-http php-horde-exception (not considered)
    • Depends: php-horde-http php-horde-support (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-http.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-injector (- to 2.0.5-12)
  • Migration status for php-horde-injector (- to 2.0.5-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-injector would introduce bugs in testing: #1089773
    • autopkgtest for php-horde-injector/2.0.5-12: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-injector pear-channels (not considered)
    • Depends: php-horde-injector php-horde-exception (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-injector.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-itip (- to 2.1.2-9)
  • Migration status for php-horde-itip (- to 2.1.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-itip/2.1.2-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-itip pear-channels (not considered)
    • Depends: php-horde-itip php-horde-icalendar (not considered)
    • Depends: php-horde-itip php-horde-mime (not considered)
    • Depends: php-horde-itip php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-itip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-log (- to 2.3.0-9)
  • Migration status for php-horde-log (- to 2.3.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-log would introduce bugs in testing: #1089776
    • autopkgtest for php-horde-log/2.3.0-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-log pear-channels (not considered)
    • Depends: php-horde-log php-horde-constraint (not considered)
    • Depends: php-horde-log php-horde-exception (not considered)
    • Depends: php-horde-log php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-log.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-mapi (- to 1.0.10-5)
  • Migration status for php-horde-mapi (- to 1.0.10-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-mapi would introduce bugs in testing: #1089727
    • autopkgtest for php-horde-mapi/1.0.10-5: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-mapi pear-channels (not considered)
    • Depends: php-horde-mapi php-horde-date (not considered)
    • Depends: php-horde-mapi php-horde-exception (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mapi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-mime (- to 2.11.2-2)
  • Migration status for php-horde-mime (- to 2.11.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-mime would introduce bugs in testing: #1089777
    • autopkgtest for php-horde-mime/2.11.2-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-mime pear-channels (not considered)
    • Depends: php-horde-mime php-horde-exception (not considered)
    • Depends: php-horde-mime php-horde-listheaders (not considered)
    • Depends: php-horde-mime php-horde-mail (not considered)
    • Depends: php-horde-mime php-horde-stream (not considered)
    • Depends: php-horde-mime php-horde-stream-filter (not considered)
    • Depends: php-horde-mime php-horde-support (not considered)
    • Depends: php-horde-mime php-horde-text-flowed (not considered)
    • Depends: php-horde-mime php-horde-translation (not considered)
    • Depends: php-horde-mime php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mime.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-notification (- to 2.0.4-10)
  • Migration status for php-horde-notification (- to 2.0.4-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-notification/2.0.4-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-notification pear-channels (not considered)
    • Depends: php-horde-notification php-horde-exception (not considered)
    • Depends: php-horde-notification php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-notification.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-passwd (- to 5.0.7-9)
  • Migration status for php-horde-passwd (- to 5.0.7-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-passwd/5.0.7-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-passwd pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-passwd php-horde-role
    • Depends: php-horde-passwd php-horde (not considered)
    • Depends: php-horde-passwd php-horde-auth (not considered)
    • Depends: php-horde-passwd php-horde-core (not considered)
    • Depends: php-horde-passwd php-horde-exception (not considered)
    • Depends: php-horde-passwd php-horde-injector (not considered)
    • Depends: php-horde-passwd php-horde-util (not considered)
    • Depends: php-horde-passwd php-horde-view (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-passwd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-secret (- to 2.0.6-10)
  • Migration status for php-horde-secret (- to 2.0.6-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-secret/2.0.6-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-secret pear-channels (not considered)
    • Depends: php-horde-secret php-horde-crypt-blowfish (not considered)
    • Depends: php-horde-secret php-horde-exception (not considered)
    • Depends: php-horde-secret php-horde-support (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-secret.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-serialize (- to 2.0.5-10)
  • Migration status for php-horde-serialize (- to 2.0.5-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-serialize/2.0.5-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-serialize pear-channels (not considered)
    • Depends: php-horde-serialize php-horde-exception (not considered)
    • Depends: php-horde-serialize php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-serialize.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-text-diff (- to 2.2.1-3)
  • Migration status for php-horde-text-diff (- to 2.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-text-diff/2.2.1-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-text-diff pear-channels (not considered)
    • Depends: php-horde-text-diff php-horde-exception (not considered)
    • Depends: php-horde-text-diff php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-text-diff.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-text-flowed (- to 2.0.4-3)
  • Migration status for php-horde-text-flowed (- to 2.0.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-text-flowed/2.0.4-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-text-flowed pear-channels (not considered)
    • Depends: php-horde-text-flowed php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-text-flowed.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• php-horde-token (- to 2.0.9-9)
  • Migration status for php-horde-token (- to 2.0.9-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-token would introduce bugs in testing: #1089779
    • autopkgtest for php-horde-token/2.0.9-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-token pear-channels (not considered)
    • Depends: php-horde-token php-horde-exception (not considered)
    • Depends: php-horde-token php-horde-translation (not considered)
    • Depends: php-horde-token php-horde-url (not considered)
    • Depends: php-horde-token php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-token.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 968 days old (needed 5 days)
• freedroidrpg (- to 1.0-1)
  • Migration status for freedroidrpg (- to 1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating freedroidrpg would introduce bugs in testing: #1074966
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/freedroidrpg.html
    • 969 days old (needed 5 days)
• php-horde-auth (- to 2.2.2-10)
  • Migration status for php-horde-auth (- to 2.2.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-auth would introduce bugs in testing: #1089768
    • autopkgtest for php-horde-auth/2.2.2-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-auth pear-channels (not considered)
    • Depends: php-horde-auth php-horde-exception (not considered)
    • Depends: php-horde-auth php-horde-translation (not considered)
    • Depends: php-horde-auth php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-auth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 969 days old (needed 5 days)
• php-horde-autoloader (- to 2.1.2-11)
  • Migration status for php-horde-autoloader (- to 2.1.2-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-autoloader/2.1.2-11: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-autoloader pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-autoloader.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 969 days old (needed 5 days)
• php-horde-compress (- to 2.2.4-3)
  • Migration status for php-horde-compress (- to 2.2.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-compress/2.2.4-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-compress pear-channels (not considered)
    • Depends: php-horde-compress php-horde-exception (not considered)
    • Depends: php-horde-compress php-horde-mime (not considered)
    • Depends: php-horde-compress php-horde-translation (not considered)
    • Depends: php-horde-compress php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-compress.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 969 days old (needed 5 days)
• php-horde-crypt-blowfish (- to 1.1.4-2)
  • Migration status for php-horde-crypt-blowfish (- to 1.1.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-crypt-blowfish/1.1.4-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-crypt-blowfish pear-channels (not considered)
    • Depends: php-horde-crypt-blowfish php-horde-exception (not considered)
    • Depends: php-horde-crypt-blowfish php-horde-support (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-crypt-blowfish.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 969 days old (needed 5 days)
• php-horde-hashtable (- to 1.2.6-12)
  • Migration status for php-horde-hashtable (- to 1.2.6-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-hashtable/1.2.6-12: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-hashtable pear-channels (not considered)
    • Depends: php-horde-hashtable php-horde-exception (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-hashtable.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 969 days old (needed 5 days)
• php-horde-memcache (- to 2.1.2-6)
  • Migration status for php-horde-memcache (- to 2.1.2-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-memcache php-horde-exception (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-memcache pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-memcache.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 969 days old (needed 5 days)
• php-horde-util (- to 2.5.12-2)
  • Migration status for php-horde-util (- to 2.5.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-util would introduce bugs in testing: #1102474
    • autopkgtest for php-horde-util/2.5.12-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-util pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-util.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 969 days old (needed 5 days)
• aribas (- to 1.65-1)
  • Migration status for aribas (- to 1.65-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aribas would introduce bugs in testing: #1074818
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aribas.html
    • autopkgtest for aribas/1.65-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 970 days old (needed 2 days)
• php-horde-support (- to 2.2.2-2)
  • Migration status for php-horde-support (- to 2.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-support/2.2.2-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-support pear-channels (not considered)
    • Depends: php-horde-support php-horde-exception (not considered)
    • Depends: php-horde-support php-horde-stream-wrapper (not considered)
    • Depends: php-horde-support php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-support.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 970 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/armhf has unsatisfiable dependency
    • libembperl-perl/i386 has unsatisfiable dependency
    • libembperl-perl/ppc64el has unsatisfiable dependency
    • libembperl-perl/s390x has unsatisfiable dependency
    • Updating libembperl-perl would introduce bugs in testing: #1042845
    • Build-Depends(-Arch): libembperl-perl libapache-sessionx-perl (not considered)
  • 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 i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 971 days old (needed 5 days)
• libmail-milter-perl (- to 0.07-2)
  • Migration status for libmail-milter-perl (- to 0.07-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends-Indep: libmail-milter-perl libsendmail-milter-perl (not considered)
    • Invalidated by build-dependency (indep)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmail-milter-perl.html
    • autopkgtest for libmail-milter-perl/0.07-2: amd64: Pass, arm64: 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
    • 971 days old (needed 2 days)
• remote-logon-service (- to 1.0.2.90-4)
  • Migration status for remote-logon-service (- to 1.0.2.90-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating remote-logon-service would introduce bugs in testing: #1073956
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/remote-logon-service.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 971 days old (needed 5 days)
• php-horde-imap-client (- to 2.30.6-3)
  • Migration status for php-horde-imap-client (- to 2.30.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-imap-client/2.30.6-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-imap-client pear-channels (not considered)
    • Depends: php-horde-imap-client php-horde-exception (not considered)
    • Depends: php-horde-imap-client php-horde-mail (not considered)
    • Depends: php-horde-imap-client php-horde-mime (not considered)
    • Depends: php-horde-imap-client php-horde-secret (not considered)
    • Depends: php-horde-imap-client php-horde-socket-client
    • Depends: php-horde-imap-client php-horde-stream (not considered)
    • Depends: php-horde-imap-client php-horde-stream-filter (not considered)
    • Depends: php-horde-imap-client php-horde-translation (not considered)
    • Depends: php-horde-imap-client php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-imap-client.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 973 days old (needed 5 days)
• pinpoint (- to 1:0.1.8-6)
  • Migration status for pinpoint (- to 1:0.1.8-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pinpoint would introduce bugs in testing: #1018133
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pinpoint.html
    • autopkgtest for pinpoint/1:0.1.8-6: amd64: Pass, arm64: 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
    • 975 days old (needed 2 days)
• relion-cuda (- to 3.1.3-2)
  • Migration status for relion-cuda (- to 3.1.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • 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
    • 975 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 ♻
    • 976 days old (needed 5 days)
• vim-ultisnips (- to 3.2-2)
  • Migration status for vim-ultisnips (- to 3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vim-ultisnips would introduce bugs in testing: #1033510
    • autopkgtest for vim-ultisnips/3.2-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vim-ultisnips.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 977 days old (needed 5 days)
• voctomix (- to 1.3-6)
  • Migration status for voctomix (- to 1.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating voctomix would introduce bugs in testing: #1109833
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/voctomix.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 979 days old (needed 5 days)
• cl-sql (- to 6.7.2-1.1)
  • Migration status for cl-sql (- to 6.7.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cl-sql would introduce bugs in testing: #1092382
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cl-sql.html
    • 981 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)
    • 984 days old (needed 5 days)
• organize (- to 2.4.0-1)
  • Migration status for organize (- to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating organize would introduce bugs in testing: #1080883, #1082579
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/organize.html
    • 984 days old (needed 5 days)
• golang-github-golang-protobuf-1-3 (- to 1.3.5-4)
  • Migration status for golang-github-golang-protobuf-1-3 (- to 1.3.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • golang-github-golang-protobuf-1-3 has no binaries on any arch
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on all - info
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 986 days old (needed 5 days)
• openzwave-controlpanel (- to 1.6~git20200306.4b8a39d-1)
  • Migration status for openzwave-controlpanel (- to 1.6~git20200306.4b8a39d-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating openzwave-controlpanel would introduce bugs in testing: #1091812
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 986 days old (needed 5 days)
• php-horde-lz4 (- to 1.0.10-10)
  • Migration status for php-horde-lz4 (- to 1.0.10-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-lz4/1.0.10-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-lz4 pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-lz4.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 986 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)
    • 988 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)
    • 988 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)
    • 988 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)
    • 988 days old (needed 5 days)
• php-horde-activesync (- to 2.41.9-1)
  • Migration status for php-horde-activesync (- to 2.41.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-activesync/2.41.9-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-activesync pear-channels (not considered)
    • Depends: php-horde-activesync php-horde-compress (not considered)
    • Depends: php-horde-activesync php-horde-date (not considered)
    • Depends: php-horde-activesync php-horde-exception (not considered)
    • Depends: php-horde-activesync php-horde-icalendar (not considered)
    • Depends: php-horde-activesync php-horde-log (not considered)
    • Depends: php-horde-activesync php-horde-mapi (not considered)
    • Depends: php-horde-activesync php-horde-mime (not considered)
    • Depends: php-horde-activesync php-horde-stream (not considered)
    • Depends: php-horde-activesync php-horde-support (not considered)
    • Depends: php-horde-activesync php-horde-translation (not considered)
    • Depends: php-horde-activesync php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-activesync.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 988 days old (needed 5 days)
• php-horde-sesha (- to 1.0.0~rc3-9)
  • Migration status for php-horde-sesha (- to 1.0.0~rc3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-sesha/1.0.0~rc3-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-sesha pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-sesha php-horde-role
    • Depends: php-horde-sesha php-horde (not considered)
    • Depends: php-horde-sesha php-horde-auth (not considered)
    • Depends: php-horde-sesha php-horde-autoloader (not considered)
    • Depends: php-horde-sesha php-horde-core (not considered)
    • Depends: php-horde-sesha php-horde-db (not considered)
    • Depends: php-horde-sesha php-horde-exception (not considered)
    • Depends: php-horde-sesha php-horde-form
    • Depends: php-horde-sesha php-horde-perms (not considered)
    • Depends: php-horde-sesha php-horde-prefs (not considered)
    • Depends: php-horde-sesha php-horde-rdo (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-sesha.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 988 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)
    • 989 days old (needed 5 days)
• php-horde-icalendar (- to 2.1.8-7)
  • Migration status for php-horde-icalendar (- to 2.1.8-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-icalendar/2.1.8-7: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-icalendar pear-channels (not considered)
    • Depends: php-horde-icalendar php-horde-date (not considered)
    • Depends: php-horde-icalendar php-horde-exception (not considered)
    • Depends: php-horde-icalendar php-horde-mail (not considered)
    • Depends: php-horde-icalendar php-horde-support (not considered)
    • Depends: php-horde-icalendar php-horde-translation (not considered)
    • Depends: php-horde-icalendar php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-icalendar.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 989 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, #1102714
    • autopkgtest for php-horde-turba/4.2.29-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-turba pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-turba php-horde-role
    • Depends: php-horde-turba php-horde (not considered)
    • Depends: php-horde-turba php-horde-auth (not considered)
    • Depends: php-horde-turba php-horde-content (not considered)
    • Depends: php-horde-turba php-horde-core (not considered)
    • Depends: php-horde-turba php-horde-data (not considered)
    • Depends: php-horde-turba php-horde-date (not considered)
    • Depends: php-horde-turba php-horde-dav
    • Depends: php-horde-turba php-horde-exception (not considered)
    • Depends: php-horde-turba php-horde-form
    • Depends: php-horde-turba php-horde-group (not considered)
    • Depends: php-horde-turba php-horde-history (not considered)
    • Depends: php-horde-turba php-horde-icalendar (not considered)
    • Depends: php-horde-turba php-horde-mail (not considered)
    • Depends: php-horde-turba php-horde-mime (not considered)
    • Depends: php-horde-turba php-horde-nls
    • Depends: php-horde-turba php-horde-perms (not considered)
    • Depends: php-horde-turba php-horde-prefs (not considered)
    • Depends: php-horde-turba php-horde-serialize (not considered)
    • Depends: php-horde-turba php-horde-share (not considered)
    • Depends: php-horde-turba php-horde-support (not considered)
    • Depends: php-horde-turba php-horde-url (not considered)
    • Depends: php-horde-turba php-horde-util (not considered)
    • Depends: php-horde-turba php-horde-vfs (not considered)
    • Depends: php-horde-turba php-horde-view (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-turba.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 989 days old (needed 5 days)
• php-horde-ingo (- to 3.2.16-9)
  • Migration status for php-horde-ingo (- to 3.2.16-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-ingo/3.2.16-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-ingo pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-ingo php-horde-role
    • Depends: php-horde-ingo php-horde (not considered)
    • Depends: php-horde-ingo php-horde-auth (not considered)
    • Depends: php-horde-ingo php-horde-autoloader (not considered)
    • Depends: php-horde-ingo php-horde-core (not considered)
    • Depends: php-horde-ingo php-horde-exception (not considered)
    • Depends: php-horde-ingo php-horde-form
    • Depends: php-horde-ingo php-horde-group (not considered)
    • Depends: php-horde-ingo php-horde-imap-client (not considered)
    • Depends: php-horde-ingo php-horde-mime (not considered)
    • Depends: php-horde-ingo php-horde-perms (not considered)
    • Depends: php-horde-ingo php-horde-share (not considered)
    • Depends: php-horde-ingo php-horde-util (not considered)
    • Depends: php-horde-ingo php-horde-view (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ingo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 990 days old (needed 5 days)
• php-horde-kronolith (- to 4.2.29-3)
  • Migration status for php-horde-kronolith (- to 4.2.29-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-kronolith would introduce bugs in testing: #1054531
    • autopkgtest for php-horde-kronolith/4.2.29-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-kronolith pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-kronolith php-horde-role
    • Depends: php-horde-kronolith php-date (not considered)
    • Depends: php-horde-kronolith php-horde (not considered)
    • Depends: php-horde-kronolith php-horde-auth (not considered)
    • Depends: php-horde-kronolith php-horde-autoloader (not considered)
    • Depends: php-horde-kronolith php-horde-content (not considered)
    • Depends: php-horde-kronolith php-horde-core (not considered)
    • Depends: php-horde-kronolith php-horde-data (not considered)
    • Depends: php-horde-kronolith php-horde-date (not considered)
    • Depends: php-horde-kronolith php-horde-date-parser (not considered)
    • Depends: php-horde-kronolith php-horde-dav
    • Depends: php-horde-kronolith php-horde-exception (not considered)
    • Depends: php-horde-kronolith php-horde-form
    • Depends: php-horde-kronolith php-horde-group (not considered)
    • Depends: php-horde-kronolith php-horde-history (not considered)
    • Depends: php-horde-kronolith php-horde-http (not considered)
    • Depends: php-horde-kronolith php-horde-icalendar (not considered)
    • Depends: php-horde-kronolith php-horde-image (not considered)
    • Depends: php-horde-kronolith php-horde-lock (not considered)
    • Depends: php-horde-kronolith php-horde-logintasks (not considered)
    • Depends: php-horde-kronolith php-horde-mail (not considered)
    • Depends: php-horde-kronolith php-horde-mime (not considered)
    • Depends: php-horde-kronolith php-horde-nls
    • Depends: php-horde-kronolith php-horde-notification (not considered)
    • Depends: php-horde-kronolith php-horde-perms (not considered)
    • Depends: php-horde-kronolith php-horde-serialize (not considered)
    • Depends: php-horde-kronolith php-horde-share (not considered)
    • Depends: php-horde-kronolith php-horde-support (not considered)
    • Depends: php-horde-kronolith php-horde-text-filter (not considered)
    • Depends: php-horde-kronolith php-horde-timezone (not considered)
    • Depends: php-horde-kronolith php-horde-url (not considered)
    • Depends: php-horde-kronolith php-horde-util (not considered)
    • Depends: php-horde-kronolith php-horde-view (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-kronolith.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 991 days old (needed 5 days)
• silkaj (- to 0.11.0-2)
  • Migration status for silkaj (- to 0.11.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating silkaj would introduce bugs in testing: #1094045
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/silkaj.html
    • autopkgtest for silkaj/0.11.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 991 days old (needed 2 days)
• php-horde-perms (- to 2.1.8-5)
  • Migration status for php-horde-perms (- to 2.1.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-perms/2.1.8-5: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-perms pear-channels (not considered)
    • Depends: php-horde-perms php-horde-db (not considered)
    • Depends: php-horde-perms php-horde-exception (not considered)
    • Depends: php-horde-perms php-horde-group (not considered)
    • Depends: php-horde-perms php-horde-translation (not considered)
    • Depends: php-horde-perms php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-perms.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 993 days old (needed 5 days)
• php-horde-share (- to 2.2.0-9)
  • Migration status for php-horde-share (- to 2.2.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-share/2.2.0-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-share pear-channels (not considered)
    • Depends: php-horde-share php-horde-db (not considered)
    • Depends: php-horde-share php-horde-exception (not considered)
    • Depends: php-horde-share php-horde-group (not considered)
    • Depends: php-horde-share php-horde-perms (not considered)
    • Depends: php-horde-share php-horde-support (not considered)
    • Depends: php-horde-share php-horde-translation (not considered)
    • Depends: php-horde-share php-horde-url (not considered)
    • Depends: php-horde-share php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-share.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 993 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabre-vobject.html
    • 995 days old (needed 5 days)
• php-horde-url (- to 2.2.6-9)
  • Migration status for php-horde-url (- to 2.2.6-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-url/2.2.6-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-url pear-channels (not considered)
    • Depends: php-horde-url php-horde-exception (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-url.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 998 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-ansel/3.0.10+debian1-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-ansel pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-ansel php-horde-role
    • Depends: php-horde-ansel php-horde (not considered)
    • Depends: php-horde-ansel php-horde-auth (not considered)
    • Depends: php-horde-ansel php-horde-autoloader (not considered)
    • Depends: php-horde-ansel php-horde-content (not considered)
    • Depends: php-horde-ansel php-horde-core (not considered)
    • Depends: php-horde-ansel php-horde-date (not considered)
    • Depends: php-horde-ansel php-horde-db (not considered)
    • Depends: php-horde-ansel php-horde-exception (not considered)
    • Depends: php-horde-ansel php-horde-form
    • Depends: php-horde-ansel php-horde-group (not considered)
    • Depends: php-horde-ansel php-horde-image (not considered)
    • Depends: php-horde-ansel php-horde-mime (not considered)
    • Depends: php-horde-ansel php-horde-nls
    • Depends: php-horde-ansel php-horde-perms (not considered)
    • Depends: php-horde-ansel php-horde-prefs (not considered)
    • Depends: php-horde-ansel php-horde-serialize (not considered)
    • Depends: php-horde-ansel php-horde-share (not considered)
    • Depends: php-horde-ansel php-horde-support (not considered)
    • Depends: php-horde-ansel php-horde-text-filter (not considered)
    • Depends: php-horde-ansel php-horde-url (not considered)
    • Depends: php-horde-ansel php-horde-util (not considered)
    • Depends: php-horde-ansel php-horde-vfs (not considered)
    • Depends: php-horde-ansel php-horde-view (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-ansel.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 999 days old (needed 5 days)
• php-horde-prefs (- to 2.9.0-9)
  • Migration status for php-horde-prefs (- to 2.9.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-prefs/2.9.0-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-prefs pear-channels (not considered)
    • Depends: php-horde-prefs php-horde-exception (not considered)
    • Depends: php-horde-prefs php-horde-mail (not considered)
    • Depends: php-horde-prefs php-horde-mime (not considered)
    • Depends: php-horde-prefs php-horde-translation (not considered)
    • Depends: php-horde-prefs php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-prefs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 999 days old (needed 5 days)
• speedcrunch (- to 0.12.0-6)
  • Migration status for speedcrunch (- to 0.12.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • speedcrunch unsatisfiable Build-Depends(-Arch) on amd64: python3-quark-sphinx-theme (>= 0.2)
    • speedcrunch unsatisfiable Build-Depends(-Arch) on arm64: python3-quark-sphinx-theme (>= 0.2)
    • speedcrunch unsatisfiable Build-Depends(-Arch) on armhf: python3-quark-sphinx-theme (>= 0.2)
    • speedcrunch unsatisfiable Build-Depends(-Arch) on i386: python3-quark-sphinx-theme (>= 0.2)
    • speedcrunch unsatisfiable Build-Depends(-Arch) on ppc64el: python3-quark-sphinx-theme (>= 0.2)
    • speedcrunch unsatisfiable Build-Depends(-Arch) on riscv64: python3-quark-sphinx-theme (>= 0.2)
    • speedcrunch unsatisfiable Build-Depends(-Arch) on s390x: python3-quark-sphinx-theme (>= 0.2)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/speedcrunch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1001 days old (needed 5 days)
• cloop (- to 3.14.1.3+nmu1)
  • Migration status for cloop (- to 3.14.1.3+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cloop would introduce bugs in testing: #1095263
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cloop.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1002 days old (needed 5 days)
• php-horde-history (- to 2.3.6-11)
  • Migration status for php-horde-history (- to 2.3.6-11): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-history/2.3.6-11: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-history pear-channels (not considered)
    • Depends: php-horde-history php-horde-db (not considered)
    • Depends: php-horde-history php-horde-exception (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-history.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1002 days old (needed 5 days)
• googler (- to 4.3.13-1)
  • Migration status for googler (- to 4.3.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating googler would introduce bugs in testing: #965067
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/googler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1005 days old (needed 5 days)
• jamin (- to 0.98.9~git20170111~199091~repack1-2)
  • Migration status for jamin (- to 0.98.9~git20170111~199091~repack1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jamin would introduce bugs in testing: #1060451, #1075099
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jamin.html
    • 1005 days old (needed 5 days)
• massxpert (- to 7.0.0-2)
  • Migration status for massxpert (- to 7.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating massxpert would introduce bugs in testing: #1084296
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/massxpert.html
    • 1005 days old (needed 5 days)
• o-saft (- to 22.11.22-1)
  • Migration status for o-saft (- to 22.11.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating o-saft would introduce bugs in testing: #1102172
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/o-saft.html
    • autopkgtest for o-saft/22.11.22-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1005 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 ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1017 days old (needed 5 days)
• dump1090-mutability (- to 1.15~20180310.4a16df3+dfsg-8.1)
  • Migration status for dump1090-mutability (- to 1.15~20180310.4a16df3+dfsg-8.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dump1090-mutability would introduce bugs in testing: #1074924
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dump1090-mutability.html
    • 1021 days old (needed 5 days)
• latte-dock (- to 0.10.9-1)
  • Migration status for latte-dock (- to 0.10.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating latte-dock would introduce bugs in testing: #1094298
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/latte-dock.html
    • Reproducible on arm64 - info ♻
    • 1022 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• mpqc (- to 2.3.1-22)
  • Migration status for mpqc (- to 2.3.1-22): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libsc-dev/amd64 has unsatisfiable dependency
    • libsc7v5/amd64 has unsatisfiable dependency
    • mpqc/amd64 has unsatisfiable dependency
    • libsc-dev/arm64 has unsatisfiable dependency
    • libsc7v5/arm64 has unsatisfiable dependency
    • mpqc/arm64 has unsatisfiable dependency
    • libsc-dev/ppc64el has unsatisfiable dependency
    • libsc7v5/ppc64el has unsatisfiable dependency
    • mpqc/ppc64el has unsatisfiable dependency
    • libsc-dev/riscv64 has unsatisfiable dependency
    • libsc7v5/riscv64 has unsatisfiable dependency
    • mpqc/riscv64 has unsatisfiable dependency
    • libsc-dev/s390x has unsatisfiable dependency
    • libsc7v5/s390x has unsatisfiable dependency
    • mpqc/s390x has unsatisfiable dependency
    • Updating mpqc would introduce bugs in testing: #1075293, #1077120
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mpqc.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1022 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis, libint
• telepathy-haze (- to 0.8.1-0.1)
  • Migration status for telepathy-haze (- to 0.8.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating telepathy-haze would introduce bugs in testing: #1075560
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/telepathy-haze.html
    • 1024 days old (needed 5 days)
• libapache-db-perl (- to 0.18-2)
  • Migration status for libapache-db-perl (- to 0.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libapache-db-perl/amd64 has unsatisfiable dependency
    • libapache-db-perl/arm64 has unsatisfiable dependency
    • libapache-db-perl/armhf has unsatisfiable dependency
    • libapache-db-perl/i386 has unsatisfiable dependency
    • libapache-db-perl/ppc64el has unsatisfiable dependency
    • libapache-db-perl/riscv64 has unsatisfiable dependency
    • libapache-db-perl/s390x has unsatisfiable dependency
    • Updating libapache-db-perl would introduce bugs in testing: #1040396
    • Not built on buildd: arch riscv64 binaries uploaded by aurel32
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/liba/libapache-db-perl.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1025 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 ♻, i386: No tests, superficial 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 ♻
    • 1027 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 ♻
    • 1028 days old (needed 5 days)
• django-measurement (- to 3.2.4-1)
  • Migration status for django-measurement (- to 3.2.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): django-measurement python-measurement (not considered)
    • Depends: django-measurement python-measurement (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/django-measurement.html
    • autopkgtest for django-measurement/3.2.4-1: amd64: Pass, arm64: Pass, 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
    • 1029 days old (needed 2 days)
• python-aioinflux (- to 0.9.0-5)
  • Migration status for python-aioinflux (- to 0.9.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aioinflux would introduce bugs in testing: #1084325
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioinflux.html
    • 1029 days old (needed 5 days)
• ocsinventory-server (- to 2.8.1+dfsg1+~2.11.1-1)
  • Migration status for ocsinventory-server (- to 2.8.1+dfsg1+~2.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ocsinventory-server would introduce bugs in testing: #1092649
    • Depends: ocsinventory-server php-imap (not considered)
    • Depends: ocsinventory-server php-pclzip (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/o/ocsinventory-server.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1030 days old (needed 5 days)
• binutils-djgpp (- to 2.35.1+dfsg-2)
  • Migration status for binutils-djgpp (- to 2.35.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating binutils-djgpp would introduce bugs in testing: #1091301
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/binutils-djgpp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1033 days old (needed 5 days)
• golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2)
  • Migration status for golang-github-leanovate-gopter (- to 0.2.9+git20210201.bbbf00e-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-leanovate-gopter/0.2.9+git20210201.bbbf00e-2: amd64: Pass, arm64: Pass, i386: Failed ♻, 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 ♻
    • 1033 days old (needed 5 days)
• bart-cuda (- to 0.8.00-2)
  • Migration status for bart-cuda (- to 0.8.00-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating bart-cuda would introduce bugs in testing: #1078156, #1096018
    • autopkgtest for bart-cuda/0.8.00-2: amd64: Failed ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1037 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• 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 ♻
    • 1038 days old (needed 5 days)
• between (- to 6+dfsg1-4)
  • Migration status for between (- to 6+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating between would introduce bugs in testing: #1072834
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/b/between.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1046 days old (needed 5 days)
• ruby-omniauth-rails-csrf-protection (- to 1.0.1-2)
  • Migration status for ruby-omniauth-rails-csrf-protection (- to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-omniauth-rails-csrf-protection would introduce bugs in testing: #1095380
    • autopkgtest for ruby-omniauth-rails-csrf-protection/1.0.1-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-omniauth-rails-csrf-protection.html
    • 1046 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/py-rnp.html
    • 1049 days old (needed 5 days)
• grpn (- to 1.4.1-1.1)
  • Migration status for grpn (- to 1.4.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating grpn would introduce bugs in testing: #1075046
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/grpn.html
    • 1050 days old (needed 5 days)
• jmodeltest (- to 2.1.10+dfsg-12)
  • Migration status for jmodeltest (- to 2.1.10+dfsg-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jmodeltest would introduce bugs in testing: #1099239
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jmodeltest.html
    • 1050 days old (needed 5 days)
• cl-umlisp (- to 1:2007ac.2-6.1)
  • Migration status for cl-umlisp (- to 1:2007ac.2-6.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: cl-umlisp cl-sql (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1051 days old (needed 5 days)
• cl-umlisp-orf (- to 3.3.2-3.1)
  • Migration status for cl-umlisp-orf (- to 3.3.2-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: cl-umlisp-orf cl-sql (not considered)
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1051 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
    • 1068 days old (needed 5 days)
• python-digitalocean (- to 1.16.0-3)
  • Migration status for python-digitalocean (- to 1.16.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-digitalocean would introduce bugs in testing: #1073401
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-digitalocean.html
    • 1072 days old (needed 5 days)
• xzoom (- to 0.3-27)
  • Migration status for xzoom (- to 0.3-27): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xzoom would introduce bugs in testing: #1075693
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xzoom.html
    • 1073 days old (needed 5 days)
• phabricator (- to 0~git20220903-2)
  • Migration status for phabricator (- to 0~git20220903-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating phabricator would introduce bugs in testing: #1038843
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/phabricator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1076 days old (needed 5 days)
• smlnj (- to 110.79-8)
  • Migration status for smlnj (- to 110.79-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating smlnj would introduce bugs in testing: #1075518
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/smlnj.html
    • 1082 days old (needed 5 days)
• nautilus-image-converter (- to 0.4.0-2)
  • Migration status for nautilus-image-converter (- to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nautilus-image-converter would introduce bugs in testing: #1074743
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nautilus-image-converter.html
    • 1083 days old (needed 5 days)
• php-fdomdocument (- to 1.6.7-2)
  • Migration status for php-fdomdocument (- to 1.6.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-fdomdocument would introduce bugs in testing: #1082448, #813866
    • autopkgtest for php-fdomdocument/1.6.7-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-fdomdocument pdepend (not considered)
    • Build-Depends(-Arch): php-fdomdocument php-codesniffer (not considered)
    • Build-Depends(-Arch): php-fdomdocument phpcpd (not considered)
    • Build-Depends(-Arch): php-fdomdocument phploc (not considered)
    • Build-Depends(-Arch): php-fdomdocument phpmd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fdomdocument.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1096 days old (needed 5 days)
• phpdox (- to 0.12.0-6)
  • Migration status for phpdox (- to 0.12.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • phpdox/amd64 has unsatisfiable dependency
    • phpdox/arm64 has unsatisfiable dependency
    • Updating phpdox would introduce bugs in testing: #1082485, #813861
    • Build-Depends(-Arch): phpdox php-codesniffer (not considered)
    • Build-Depends(-Arch): phpdox php-fdomdocument (not considered)
    • Build-Depends(-Arch): phpdox php-fxsl (not considered)
    • Build-Depends(-Arch): phpdox phpcpd (not considered)
    • Build-Depends(-Arch): phpdox phploc (not considered)
    • Build-Depends(-Arch): phpdox phpmd (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/phpdox.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1096 days old (needed 5 days)
• ruby-protocol-http1 (- to 0.14.6-1)
  • Migration status for ruby-protocol-http1 (- to 0.14.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-protocol-http1 would introduce bugs in testing: #1043432
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-protocol-http1.html
    • autopkgtest for ruby-protocol-http1/0.14.6-1: amd64: Pass, arm64: 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
    • 1098 days old (needed 2 days)
• eclipse-titan (- to 8.2.0-1)
  • Migration status for eclipse-titan (- to 8.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • eclipse-titan/amd64 has unsatisfiable dependency
    • eclipse-titan/arm64 has unsatisfiable dependency
    • eclipse-titan/armhf has unsatisfiable dependency
    • eclipse-titan/i386 has unsatisfiable dependency
    • eclipse-titan/ppc64el has unsatisfiable dependency
    • eclipse-titan/riscv64 has unsatisfiable dependency
    • eclipse-titan/s390x has unsatisfiable dependency
    • Updating eclipse-titan would introduce bugs in testing: #1071679, #1089251
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/eclipse-titan.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1100 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: #1041625
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/qreator.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1100 days old (needed 5 days)
• xserver-xorg-input-mutouch (- to 1:1.3.0-3)
  • Migration status for xserver-xorg-input-mutouch (- to 1:1.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-input-mutouch would introduce bugs in testing: #1075681
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xserver-xorg-input-mutouch.html
    • 1101 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Failed ♻, 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 ♻
    • 1105 days old (needed 5 days)
• php-easyrdf (- to 1.0.0-3)
  • Migration status for php-easyrdf (- to 1.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-easyrdf would introduce bugs in testing: #1082446
    • autopkgtest for php-easyrdf/1.0.0-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-easyrdf.html
    • 1111 days old (needed 5 days)
• vagrant-lxc (- to 1.4.3-3)
  • Migration status for vagrant-lxc (- to 1.4.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for vagrant-lxc/1.4.3-3: amd64: Failed ♻, 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/v/vagrant-lxc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1117 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:
    • gnome-subtitles/amd64 has unsatisfiable dependency
    • gnome-subtitles/arm64 has unsatisfiable dependency
    • gnome-subtitles/ppc64el has unsatisfiable dependency
    • gnome-subtitles/s390x has unsatisfiable dependency
    • 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
    • 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
    • 1122 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• 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
    • 1137 days old (needed 5 days)
• haskell-hindent (- to 5.3.4-1)
  • Migration status for haskell-hindent (- to 5.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libghc-hindent-dev/amd64 has unsatisfiable dependency
    • libghc-hindent-doc/amd64 has unsatisfiable dependency
    • libghc-hindent-prof/amd64 has unsatisfiable dependency
    • libghc-hindent-dev/arm64 has unsatisfiable dependency
    • libghc-hindent-doc/arm64 has unsatisfiable dependency
    • libghc-hindent-prof/arm64 has unsatisfiable dependency
    • libghc-hindent-dev/armhf has unsatisfiable dependency
    • libghc-hindent-prof/armhf has unsatisfiable dependency
    • libghc-hindent-dev/i386 has unsatisfiable dependency
    • libghc-hindent-prof/i386 has unsatisfiable dependency
    • libghc-hindent-dev/ppc64el has unsatisfiable dependency
    • libghc-hindent-prof/ppc64el has unsatisfiable dependency
    • libghc-hindent-dev/riscv64 has unsatisfiable dependency
    • libghc-hindent-prof/riscv64 has unsatisfiable dependency
    • libghc-hindent-dev/s390x has unsatisfiable dependency
    • libghc-hindent-prof/s390x has unsatisfiable dependency
    • Updating haskell-hindent would introduce bugs in testing: #1053982, #1103764
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/haskell-hindent.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1147 days old (needed 5 days)
• rust-protoc-rust (- to 2.27.1-1)
  • Migration status for rust-protoc-rust (- to 2.27.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-protoc-rust rust-protobuf (not considered)
    • Depends: rust-protoc-rust rust-protobuf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-protoc-rust rust-protobuf-codegen
    • Depends: rust-protoc-rust rust-protobuf-codegen
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-protoc-rust.html
    • autopkgtest for rust-protoc-rust/2.27.1-1: amd64: Pass, arm64: 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
    • 1147 days old (needed 2 days)
• rust-protobuf-codegen-pure (- to 2.27.1-1)
  • Migration status for rust-protobuf-codegen-pure (- to 2.27.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-protobuf-codegen-pure rust-protobuf (not considered)
    • Depends: rust-protobuf-codegen-pure rust-protobuf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): rust-protobuf-codegen-pure rust-protobuf-codegen
    • Depends: rust-protobuf-codegen-pure rust-protobuf-codegen
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-protobuf-codegen-pure.html
    • autopkgtest for rust-protobuf-codegen-pure/2.27.1-1: amd64: Pass, arm64: 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
    • 1148 days old (needed 2 days)
• rust-protobuf (- to 2.27.1-1)
  • Migration status for rust-protobuf (- to 2.27.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-protobuf would introduce bugs in testing: #1103833
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-protobuf.html
    • autopkgtest for rust-protobuf/2.27.1-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 ♻
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1154 days old (needed 5 days)
• rust-protobuf-codegen (- to 2.27.1-1)
  • Migration status for rust-protobuf-codegen (- to 2.27.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-protobuf-codegen rust-protobuf (not considered)
    • Depends: rust-protobuf-codegen rust-protobuf (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-protobuf-codegen.html
    • autopkgtest for rust-protobuf-codegen/2.27.1-1: amd64: Pass, arm64: 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
    • 1154 days old (needed 2 days)
• gcc-11-doc (- to 11.3.0-1)
  • Migration status for gcc-11-doc (- to 11.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gcc-11-doc would introduce bugs in testing: #1057560
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1159 days old (needed 5 days)
• parmetis (- to 4.0.3-7)
  • Migration status for parmetis (- to 4.0.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating parmetis would introduce bugs in testing: #1080199
    • autopkgtest for parmetis/4.0.3-7: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1160 days old (needed 5 days)
• php-horde-date (- to 2.4.1-9)
  • Migration status for php-horde-date (- to 2.4.1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-date/2.4.1-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-date pear-channels (not considered)
    • Depends: php-horde-date php-horde-exception (not considered)
    • Depends: php-horde-date php-horde-nls
    • Depends: php-horde-date php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-date.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1164 days old (needed 5 days)
• php-horde-data (- to 2.1.5-3)
  • Migration status for php-horde-data (- to 2.1.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-data would introduce bugs in testing: #1089772
    • autopkgtest for php-horde-data/2.1.5-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-data pear-channels (not considered)
    • Depends: php-horde-data php-horde-browser
    • Depends: php-horde-data php-horde-exception (not considered)
    • Depends: php-horde-data php-horde-icalendar (not considered)
    • Depends: php-horde-data php-horde-mail (not considered)
    • Depends: php-horde-data php-horde-mime (not considered)
    • Depends: php-horde-data php-horde-translation (not considered)
    • Depends: php-horde-data php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-data.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1166 days old (needed 5 days)
• php-horde-logintasks (- to 2.0.8-1)
  • Migration status for php-horde-logintasks (- to 2.0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-logintasks/2.0.8-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-logintasks pear-channels (not considered)
    • Depends: php-horde-logintasks php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-logintasks.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1166 days old (needed 5 days)
• php-horde-stream (- to 1.6.3-10)
  • Migration status for php-horde-stream (- to 1.6.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-stream/1.6.3-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-stream pear-channels (not considered)
    • Depends: php-horde-stream php-horde-exception (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-stream.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1166 days old (needed 5 days)
• php-horde-stream-filter (- to 2.0.5-1)
  • Migration status for php-horde-stream-filter (- to 2.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-stream-filter/2.0.5-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-stream-filter pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-stream-filter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1166 days old (needed 5 days)
• php-horde-rpc (- to 2.1.9-2)
  • Migration status for php-horde-rpc (- to 2.1.9-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-rpc php-horde-dav (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-rpc pear-channels (not considered)
    • Depends: php-horde-rpc php-horde-core (not considered)
    • Depends: php-horde-rpc php-horde-exception (not considered)
    • Depends: php-horde-rpc php-horde-perms (not considered)
    • Depends: php-horde-rpc php-horde-serialize (not considered)
    • Depends: php-horde-rpc php-horde-support (not considered)
    • Depends: php-horde-rpc php-horde-translation (not considered)
    • Depends: php-horde-rpc php-horde-util (not considered)
    • Depends: php-horde-rpc php-horde-xml-element (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-rpc.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1170 days old (needed 5 days)
• dvbcut (- to 0.7.4-1)
  • Migration status for dvbcut (- to 0.7.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • dvbcut/amd64 has unsatisfiable dependency
    • dvbcut/arm64 has unsatisfiable dependency
    • dvbcut/armhf has unsatisfiable dependency
    • dvbcut/i386 has unsatisfiable dependency
    • dvbcut/ppc64el has unsatisfiable dependency
    • dvbcut/riscv64 has unsatisfiable dependency
    • dvbcut/s390x has unsatisfiable dependency
    • Updating dvbcut would introduce bugs in testing: #1072411
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dvbcut.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1181 days old (needed 5 days)
• ippsample (- to 0.0~git20220607.72f89b3-1)
  • Migration status for ippsample (- to 0.0~git20220607.72f89b3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ippsample/armhf has unsatisfiable dependency
    • Updating ippsample would introduce bugs in testing: #1042570, #1069333
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/ippsample.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1187 days old (needed 5 days)
• php-sql-formatter (- to 1.2.17+dct1.1.3-1)
  • Migration status for php-sql-formatter (- to 1.2.17+dct1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sql-formatter would introduce bugs in testing: #1064641, #1073571
    • autopkgtest for php-sql-formatter/1.2.17+dct1.1.3-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sql-formatter.html
    • 1188 days old (needed 5 days)
• php-date (- to 1.4.7-3.1)
  • Migration status for php-date (- to 1.4.7-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-date would introduce bugs in testing: #1093491
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-date.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1194 days old (needed 5 days)
• php-text-languagedetect (- to 0.3.0-2.1)
  • Migration status for php-text-languagedetect (- to 0.3.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-text-languagedetect would introduce bugs in testing: #1093493
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-text-languagedetect.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1194 days old (needed 5 days)
• puppet-module-asciiduck-sssd (- to 0.3.0-1.1)
  • Migration status for puppet-module-asciiduck-sssd (- to 0.3.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating puppet-module-asciiduck-sssd would introduce bugs in testing: #1108801
    • autopkgtest for puppet-module-asciiduck-sssd/0.3.0-1.1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/puppet-module-asciiduck-sssd.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1194 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-pyepsg.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1197 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, i386: Pass, ppc64el: Failed ♻, riscv64: Pass, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-ioctl-sys.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1206 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, #1109793
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pfqueue.html
    • 1213 days old (needed 5 days)
    • Remove hint for (transitive) dependency: bcron
• 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 ♻
    • 1216 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 ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1218 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
    • 1227 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
    • 1227 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
    • 1227 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
    • 1229 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
    • 1229 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 ♻
    • Waiting for lintian test results on i386 - info
    • 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 ♻
    • 1235 days old (needed 5 days)
• r-cran-zelig (- to 5.1.7-3)
  • Migration status for r-cran-zelig (- to 5.1.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for r-cran-zelig/5.1.7-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/r-cran-zelig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1238 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• 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
    • autopkgtest for unburden-home-dir/0.4.2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • unburden-home-dir unsatisfiable Build-Depends(-Arch) on amd64: pcregrep
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/unburden-home-dir.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1242 days old (needed 5 days)
• libvpd (- to 2.2.9-1)
  • Migration status for libvpd (- to 2.2.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libvpd would introduce bugs in testing: #1091747
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1246 days old (needed 5 days)
• lsvpd (- to 1.7.14-1)
  • Migration status for lsvpd (- to 1.7.14-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): lsvpd libvpd (not considered)
    • Depends: lsvpd libvpd (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1246 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, #1090204
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/coyote.html
    • uninstallable on arch i386 (which is allowed), not running autopkgtest there
    • autopkgtest for coyote/2022.04.12-1: amd64: Pass, arm64: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Pass, s390x: Pass
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1255 days old (needed 5 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating redmine-plugin-custom-css would introduce bugs in testing: #1101466
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redmine-plugin-custom-css.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1257 days old (needed 5 days)
• synfigstudio (- to 1.5.1-1)
  • Migration status for synfigstudio (- to 1.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): synfigstudio synfig (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/synfigstudio.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1258 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• hackage-tracker (- to 0.1.1)
  • Migration status for hackage-tracker (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hackage-tracker would introduce bugs in testing: #1091077
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hackage-tracker.html
    • 1269 days old (needed 5 days)
• win32-loader (- to 0.10.6)
  • Migration status for win32-loader (- to 0.10.6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating win32-loader would introduce bugs in testing: #1089276
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/win32-loader.html
    • autopkgtest for win32-loader/0.10.6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1277 days old (needed 2 days)
• prelude-lml (- to 5.2.0-3)
  • Migration status for prelude-lml (- to 5.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prelude-lml would introduce bugs in testing: #1114268
    • Build-Depends(-Arch): prelude-lml libprelude (not considered)
    • Depends: prelude-lml libprelude (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prelude-lml.html
    • Reproducible on arm64 - info ♻
    • 1286 days old (needed 5 days)
• php-horde-socket-client (- to 2.1.4-1)
  • Migration status for php-horde-socket-client (- to 2.1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-socket-client php-horde-exception (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-socket-client pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-socket-client.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1291 days old (needed 5 days)
• php-horde-stream-wrapper (- to 2.1.5-1)
  • Migration status for php-horde-stream-wrapper (- to 2.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-stream-wrapper/2.1.5-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-stream-wrapper pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-stream-wrapper.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1291 days old (needed 5 days)
• php-horde-vfs (- to 2.4.2-1)
  • Migration status for php-horde-vfs (- to 2.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-vfs/2.4.2-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-vfs pear-channels (not considered)
    • Depends: php-horde-vfs php-horde-exception (not considered)
    • Depends: php-horde-vfs php-horde-translation (not considered)
    • Depends: php-horde-vfs php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-vfs.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1291 days old (needed 5 days)
• kickoff (- to 0.1.1)
  • Migration status for kickoff (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kickoff would introduce bugs in testing: #1091059
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kickoff.html
    • 1300 days old (needed 5 days)
• emacs-lintian (- to 0.1.1)
  • Migration status for emacs-lintian (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating emacs-lintian would introduce bugs in testing: #1077105
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/e/emacs-lintian.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1305 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 ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 1315 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, 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
    • 1315 days old (needed 2 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
    • 1319 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 ♻
    • 1322 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, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dumpasn1.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1331 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-proc-quote.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1331 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: #1081108
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xcb.html
    • 1340 days old (needed 5 days)
• nim-lapper (- to 0.1.7-5)
  • Migration status for nim-lapper (- to 0.1.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nim-lapper would introduce bugs in testing: #1112656
    • autopkgtest for nim-lapper/0.1.7-5: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): nim-lapper nim (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-lapper.html
    • 1341 days old (needed 5 days)
• uqm-russian (- to 1.0.2-6)
  • Migration status for uqm-russian (- to 1.0.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating uqm-russian would introduce bugs in testing: #1096163
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1346 days old (needed 5 days)
• vdr-plugin-remote (- to 0.7.0-6)
  • Migration status for vdr-plugin-remote (- to 0.7.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating vdr-plugin-remote would introduce bugs in testing: #1095397
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/v/vdr-plugin-remote.html
    • 1346 days old (needed 5 days)
• golang-github-go-redis-redis (- to 6.15.0-2)
  • Migration status for golang-github-go-redis-redis (- to 6.15.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-go-redis-redis would introduce bugs in testing: #1085472, #985011
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-go-redis-redis.html
    • autopkgtest for golang-github-go-redis-redis: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored), s390x: Test triggered (failure will be ignored)
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1351 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
    • 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 armhf binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch i386 binaries uploaded by ryanakca@kubuntu.org
    • Not built on buildd: arch s390x binaries uploaded by ryanakca@kubuntu.org
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mlton.html
    • uninstallable on arch ppc64el (which is allowed), not running autopkgtest there
    • uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1353 days old (needed 5 days)
• golang-github-charmbracelet-wish (- to 0.1.1-2)
  • Migration status for golang-github-charmbracelet-wish (- to 0.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-charmbracelet-wish would introduce bugs in testing: #1096175
    • autopkgtest for golang-github-charmbracelet-wish/0.1.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-charmbracelet-wish.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1356 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-duckpy.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1356 days old (needed 5 days)
• tiledarray (- to 1.0.0-1)
  • Migration status for tiledarray (- to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tiledarray would introduce bugs in testing: #1087560
    • missing build on amd64
    • missing build on arm64
    • missing build on armhf
    • missing build on i386
    • missing build on ppc64el
    • missing build on s390x
    • arch:amd64 not built yet, autopkgtest delayed there
    • arch:arm64 not built yet, autopkgtest delayed there
    • arch:i386 not built yet, autopkgtest delayed there
    • arch:ppc64el not built yet, autopkgtest delayed there
    • arch:s390x not built yet, autopkgtest delayed there
    • Waiting for lintian test results on ppc64el, amd64, arm64, i386, s390x, armhf - info
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tiledarray.html
    • 1356 days old (needed 5 days)
• php-fxsl (- to 1.1.1-6)
  • Migration status for php-fxsl (- to 1.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-fxsl would introduce bugs in testing: #813865
    • autopkgtest for php-fxsl/1.1.1-6: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-fxsl pdepend (not considered)
    • Build-Depends(-Arch): php-fxsl php-codesniffer (not considered)
    • Build-Depends(-Arch): php-fxsl phpcpd (not considered)
    • Build-Depends(-Arch): php-fxsl phploc (not considered)
    • Build-Depends(-Arch): php-fxsl phpmd (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-fxsl.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1358 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, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1362 days old (needed 2 days)
• magic (- to 8.3.105+ds.1-1.1)
  • Migration status for magic (- to 8.3.105+ds.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating magic would introduce bugs in testing: #1075249
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/magic.html
    • 1369 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/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
    • 1373 days old (needed 5 days)
• gbonds (- to 2.0.3-17)
  • Migration status for gbonds (- to 2.0.3-17): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gbonds would introduce bugs in testing: #1073944
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gbonds.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1377 days old (needed 5 days)
• php-sabredav (- to 1.8.12-10)
  • Migration status for php-sabredav (- to 1.8.12-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-sabredav would introduce bugs in testing: #1070597
    • autopkgtest for php-sabredav/1.8.12-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-sabredav php-sabre-vobject (not considered)
    • Depends: php-sabredav php-sabre-vobject (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-sabredav.html
    • 1394 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-mongodb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1399 days old (needed 5 days)
• jarchivelib (- to 1.2.0-2)
  • Migration status for jarchivelib (- to 1.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jarchivelib would introduce bugs in testing: #1086277
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jarchivelib.html
    • 1411 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: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-intel-go-cpuid.html
    • Reproducible on amd64 - info ♻
    • 1414 days old (needed 5 days)
• ruby-file-validators (- to 3.0.0-2)
  • Migration status for ruby-file-validators (- to 3.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-file-validators would introduce bugs in testing: #1093922
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-file-validators.html
    • autopkgtest for ruby-file-validators/3.0.0-2: amd64: Pass, arm64: 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
    • 1419 days old (needed 2 days)
• ruby-gd (- to 0.8.0-8)
  • Migration status for ruby-gd (- to 0.8.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • ruby-gd/amd64 has unsatisfiable dependency
    • ruby-gd/arm64 has unsatisfiable dependency
    • ruby-gd/armhf has unsatisfiable dependency
    • ruby-gd/i386 has unsatisfiable dependency
    • ruby-gd/ppc64el has unsatisfiable dependency
    • ruby-gd/riscv64 has unsatisfiable dependency
    • ruby-gd/s390x has unsatisfiable dependency
    • Updating ruby-gd would introduce bugs in testing: #1075461
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-gd.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1419 days old (needed 5 days)
• nim-kexpr (- to 0.0.2-3)
  • Migration status for nim-kexpr (- to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for nim-kexpr/0.0.2-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Failed ♻
    • Build-Depends(-Arch): nim-kexpr nim (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-kexpr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1429 days old (needed 5 days)
• libdfp (- to 1.0.16-1)
  • Migration status for libdfp (- to 1.0.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libdfp would introduce bugs in testing: #1077413
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libd/libdfp.html
    • 1431 days old (needed 5 days)
• idm-console-framework (- to 2.0.0-1)
  • Migration status for idm-console-framework (- to 2.0.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): idm-console-framework jss (not considered)
    • Depends: idm-console-framework jss (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
    • Build-Depends(-Arch): idm-console-framework ldapjdk
    • Depends: idm-console-framework ldapjdk
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/i/idm-console-framework.html
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • 1432 days old (needed 5 days)
• utalk (- to 1.0.2-2)
  • Migration status for utalk (- to 1.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating utalk would introduce bugs in testing: #1075611
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/utalk.html
    • 1435 days old (needed 5 days)
• prads (- to 0.3.3-7)
  • Migration status for prads (- to 0.3.3-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • prads/amd64 has unsatisfiable dependency
    • prads/arm64 has unsatisfiable dependency
    • prads/armhf has unsatisfiable dependency
    • prads/i386 has unsatisfiable dependency
    • prads/ppc64el has unsatisfiable dependency
    • prads/s390x has unsatisfiable dependency
    • Updating prads would introduce bugs in testing: #1069335, #1081091, #999984
    • prads unsatisfiable Build-Depends(-Arch) on amd64: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on arm64: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on armhf: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on i386: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on ppc64el: libpcre3-dev
    • prads unsatisfiable Build-Depends(-Arch) on s390x: libpcre3-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prads.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch 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 ♻
    • 1436 days old (needed 5 days)
• async-http-client (- to 2.12.3-1)
  • Migration status for async-http-client (- to 2.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating async-http-client would introduce bugs in testing: #1089228
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/async-http-client.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1463 days old (needed 5 days)
• aioredis (- to 1.3.1-2)
  • Migration status for aioredis (- to 1.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating aioredis would introduce bugs in testing: #1058292
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/aioredis.html
    • 1464 days old (needed 5 days)
• ganglia-modules-linux (- to 1.3.6-5)
  • Migration status for ganglia-modules-linux (- to 1.3.6-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): ganglia-modules-linux ganglia (not considered)
    • Depends: ganglia-modules-linux ganglia (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/ganglia-modules-linux.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1525 days old (needed 5 days)
• redisearch (- to 1:1.2.2-4)
  • Migration status for redisearch (- to 1:1.2.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating redisearch would introduce bugs in testing: #1091247
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/redisearch.html
    • autopkgtest for redisearch/1:1.2.2-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1570 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:
    • scrollz/armhf has unsatisfiable dependency
    • Updating scrollz would introduce bugs in testing: #1066483
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scrollz.html
    • 1578 days old (needed 5 days)
• micro-evtd (- to 3.4-7)
  • Migration status for micro-evtd (- to 3.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • micro-evtd has no binaries on any arch
    • nothing built yet, autopkgtest delayed
    • nothing built yet, lintian delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1582 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dstat.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1626 days old (needed 5 days)
• hotspot (- to 1.3.0-2)
  • Migration status for hotspot (- to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • hotspot/amd64 has unsatisfiable dependency
    • hotspot/arm64 has unsatisfiable dependency
    • hotspot/armhf has unsatisfiable dependency
    • hotspot/i386 has unsatisfiable dependency
    • hotspot/ppc64el has unsatisfiable dependency
    • hotspot/riscv64 has unsatisfiable dependency
    • Updating hotspot would introduce bugs in testing: #1025573, #1033848
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/h/hotspot.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1672 days old (needed 5 days)
• php-horde-sessionhandler (- to 2.3.0-1)
  • Migration status for php-horde-sessionhandler (- to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-sessionhandler/2.3.0-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-sessionhandler pear-channels (not considered)
    • Depends: php-horde-sessionhandler php-horde-exception (not considered)
    • Depends: php-horde-sessionhandler php-horde-support (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-sessionhandler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1674 days old (needed 5 days)
• php-horde-text-filter (- to 2.3.7-1)
  • Migration status for php-horde-text-filter (- to 2.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-text-filter/2.3.7-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-text-filter pear-channels (not considered)
    • Depends: php-horde-text-filter php-horde-exception (not considered)
    • Depends: php-horde-text-filter php-horde-idna (not considered)
    • Depends: php-horde-text-filter php-horde-secret (not considered)
    • Depends: php-horde-text-filter php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-text-filter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1674 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, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/u/utox.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1674 days old (needed 5 days)
• runsnakerun (- to 2.0.5-3)
  • Migration status for runsnakerun (- to 2.0.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating runsnakerun would introduce bugs in testing: #1093809
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/runsnakerun.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1684 days old (needed 5 days)
• gringotts (- to 1.2.10-4)
  • Migration status for gringotts (- to 1.2.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gringotts would introduce bugs in testing: #1075043
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gringotts.html
    • 1685 days old (needed 5 days)
• java-gnome (- to 4.1.3-10)
  • Migration status for java-gnome (- to 4.1.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating java-gnome would introduce bugs in testing: #1075098
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/java-gnome.html
    • 1685 days old (needed 5 days)
• libreadline-java (- to 0.8.0.1+dfsg-10)
  • Migration status for libreadline-java (- to 0.8.0.1+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating libreadline-java would introduce bugs in testing: #1075200
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/libr/libreadline-java.html
    • 1685 days old (needed 5 days)
• dewalls (- to 1.0.0+ds1-9)
  • Migration status for dewalls (- to 1.0.0+ds1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dewalls would introduce bugs in testing: #1101847
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dewalls.html
    • 1686 days old (needed 5 days)
• plotsauce (- to 0~0.1-1)
  • Migration status for plotsauce (- to 0~0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating plotsauce would introduce bugs in testing: #1072135
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/plotsauce.html
    • 1690 days old (needed 5 days)
• sugar-etoys-activity (- to 116-10)
  • Migration status for sugar-etoys-activity (- to 116-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: sugar-etoys-activity etoys (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1690 days old (needed 5 days)
    • Remove hint for (transitive) dependency: libast, netkit-telnet-ssl
• 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 ♻
    • 1691 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, #1109169
    • Build-Depends(-Arch): tika vorbis-java
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tika.html
    • 1691 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, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • New but not reproducible on amd64 - info ♻
    • New but not reproducible on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1696 days old (needed 2 days)
• git-reintegrate (- to 0.4-2.1)
  • Migration status for git-reintegrate (- to 0.4-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating git-reintegrate would introduce bugs in testing: #1094096
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/git-reintegrate.html
    • 1706 days old (needed 5 days)
• python-aioopenssl (- to 0.6.0-1)
  • Migration status for python-aioopenssl (- to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating python-aioopenssl would introduce bugs in testing: #1090130
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-aioopenssl.html
    • 1706 days old (needed 5 days)
• sptk (- to 3.9-3)
  • Migration status for sptk (- to 3.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sptk would introduce bugs in testing: #1091296
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sptk.html
    • Reproducible on arm64 - info ♻
    • 1706 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
    • 1715 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
    • 1715 days old (needed 5 days)
• shelr (- to 0.16.3-2.1)
  • Migration status for shelr (- to 0.16.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shelr would introduce bugs in testing: #1108063
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shelr.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1718 days old (needed 5 days)
• jsjac (- to 1.3.4+dfsg-3)
  • Migration status for jsjac (- to 1.3.4+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating jsjac would introduce bugs in testing: #1091600
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/j/jsjac.html
    • New but not reproducible on arm64 - info ♻
    • 1719 days old (needed 5 days)
• android-framework-23 (- to 6.0.1+r72-6)
  • Migration status for android-framework-23 (- to 6.0.1+r72-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-framework-23 would introduce bugs in testing: #1011567, #1038833, #1063811
    • 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, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1721 days old (needed 2 days)
• php-net-ftp (- to 1:1.4.0-2.1)
  • Migration status for php-net-ftp (- to 1:1.4.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-ftp would introduce bugs in testing: #1041477
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-ftp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1721 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: scratch squeak-vm (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/scratch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1722 days old (needed 5 days)
    • Remove hint for (transitive) dependency: libast, netkit-telnet-ssl
• 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 ♻
    • 1728 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/armhf has unsatisfiable dependency
    • python3-broker/armhf has unsatisfiable dependency
    • python3-broker/i386 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 i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1729 days old (needed 5 days)
• ruby-rspec-parameterized (- to 0.4.2-2)
  • Migration status for ruby-rspec-parameterized (- to 0.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ruby-rspec-parameterized would introduce bugs in testing: #1093930
    • autopkgtest for ruby-rspec-parameterized/0.4.2-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): ruby-rspec-parameterized ruby-proc-to-ast
    • Build-Depends(-Arch): ruby-rspec-parameterized ruby-unparser (not considered)
    • Depends: ruby-rspec-parameterized ruby-proc-to-ast
    • Depends: ruby-rspec-parameterized ruby-unparser (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-rspec-parameterized.html
    • 1733 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
    • 1735 days old (needed 5 days)
• autoconf2.13 (- to 2.13-69)
  • Migration status for autoconf2.13 (- to 2.13-69): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating autoconf2.13 would introduce bugs in testing: #1081532
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/autoconf2.13.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1741 days old (needed 5 days)
• php-horde-smtp (- to 1.9.6-2)
  • Migration status for php-horde-smtp (- to 1.9.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-smtp/1.9.6-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-smtp pear-channels (not considered)
    • Depends: php-horde-smtp php-horde-exception (not considered)
    • Depends: php-horde-smtp php-horde-mail (not considered)
    • Depends: php-horde-smtp php-horde-socket-client
    • Depends: php-horde-smtp php-horde-support (not considered)
    • Depends: php-horde-smtp php-horde-translation (not considered)
    • Depends: php-horde-smtp php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-smtp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1749 days old (needed 5 days)
• shoogle (- to 0.1.4-10)
  • Migration status for shoogle (- to 0.1.4-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating shoogle would introduce bugs in testing: #1083030
    • Depends: shoogle python-oauth2client (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/shoogle.html
    • autopkgtest for shoogle/0.1.4-10: amd64: Pass, arm64: Pass, 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
    • 1754 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 ♻
    • 1757 days old (needed 5 days)
• prelude-manager (- to 5.2.0-2)
  • Migration status for prelude-manager (- to 5.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating prelude-manager would introduce bugs in testing: #1077422
    • Build-Depends(-Arch): prelude-manager libprelude (not considered)
    • Build-Depends(-Arch): prelude-manager libpreludedb (not considered)
    • Depends: prelude-manager libprelude (not considered)
    • Depends: prelude-manager libpreludedb (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/prelude-manager.html
    • 1758 days old (needed 5 days)
• php-horde-javascriptminify (- to 1.1.5-7)
  • Migration status for php-horde-javascriptminify (- to 1.1.5-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-javascriptminify/1.1.5-7: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-javascriptminify pear-channels (not considered)
    • Depends: php-horde-javascriptminify php-horde-exception (not considered)
    • Depends: php-horde-javascriptminify php-horde-log (not considered)
    • Depends: php-horde-javascriptminify php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-javascriptminify.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1761 days old (needed 5 days)
• nim-docopt (- to 0.6.8-3)
  • Migration status for nim-docopt (- to 0.6.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nim-docopt would introduce bugs in testing: #1081085
    • autopkgtest for nim-docopt/0.6.8-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻
    • Build-Depends(-Arch): nim-docopt nim (not considered)
    • Build-Depends(-Arch): nim-docopt nim-regex (not considered)
    • Build-Depends(-Arch): nim-docopt nim-unicodedb
    • Build-Depends(-Arch): nim-docopt nim-unicodeplus
    • Depends: nim-docopt nim (not considered)
    • Depends: nim-docopt nim-regex (not considered)
    • Depends: nim-docopt nim-unicodedb
    • Depends: nim-docopt nim-unicodeplus
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-docopt.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 1769 days old (needed 5 days)
• nim-d3 (- to 0.1.3-2)
  • Migration status for nim-d3 (- to 0.1.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nim-d3 nim (not considered)
    • Depends: nim-d3 nim (not considered)
    • Invalidated by build-dependency
    • Invalidated by dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-d3.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1771 days old (needed 5 days)
• pmon-update (- to 0.3.1)
  • Migration status for pmon-update (- to 0.3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • pmon-update has no binaries on any arch
    • nothing built yet, autopkgtest delayed
    • nothing built yet, lintian delayed
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1772 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 armhf: ash
    • shc unsatisfiable Build-Depends(-Arch) on i386: 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, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • Required age reduced by 3 days because of autopkgtest
    • 1776 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 ♻
    • 1783 days old (needed 5 days)
• nim-regex (- to 0.17.0+ds-2)
  • Migration status for nim-regex (- to 0.17.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating nim-regex would introduce bugs in testing: #1112657
    • Build-Depends(-Arch): nim-regex nim (not considered)
    • Build-Depends(-Arch): nim-regex nim-unicodedb
    • Build-Depends(-Arch): nim-regex nim-unicodeplus
    • Depends: nim-regex nim (not considered)
    • Depends: nim-regex nim-unicodedb
    • Depends: nim-regex nim-unicodeplus
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-regex.html
    • uninstallable on arch s390x (which is allowed), not running autopkgtest there
    • 1784 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-mail-autoconfig pear-channels (not considered)
    • Depends: php-horde-mail-autoconfig php-horde-exception (not considered)
    • Depends: php-horde-mail-autoconfig php-horde-http (not considered)
    • Depends: php-horde-mail-autoconfig php-horde-imap-client (not considered)
    • Depends: php-horde-mail-autoconfig php-horde-mail (not considered)
    • Depends: php-horde-mail-autoconfig php-horde-smtp (not considered)
    • Depends: php-horde-mail-autoconfig php-net-dns2 (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mail-autoconfig.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1794 days old (needed 5 days)
• php-horde-mnemo (- to 4.2.14-10)
  • Migration status for php-horde-mnemo (- to 4.2.14-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-mnemo/4.2.14-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-mnemo pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-mnemo php-horde-role
    • Depends: php-horde-mnemo php-horde (not considered)
    • Depends: php-horde-mnemo php-horde-auth (not considered)
    • Depends: php-horde-mnemo php-horde-content (not considered)
    • Depends: php-horde-mnemo php-horde-core (not considered)
    • Depends: php-horde-mnemo php-horde-data (not considered)
    • Depends: php-horde-mnemo php-horde-exception (not considered)
    • Depends: php-horde-mnemo php-horde-form
    • Depends: php-horde-mnemo php-horde-group (not considered)
    • Depends: php-horde-mnemo php-horde-history (not considered)
    • Depends: php-horde-mnemo php-horde-icalendar (not considered)
    • Depends: php-horde-mnemo php-horde-injector (not considered)
    • Depends: php-horde-mnemo php-horde-perms (not considered)
    • Depends: php-horde-mnemo php-horde-prefs (not considered)
    • Depends: php-horde-mnemo php-horde-share (not considered)
    • Depends: php-horde-mnemo php-horde-support (not considered)
    • Depends: php-horde-mnemo php-horde-text-filter (not considered)
    • Depends: php-horde-mnemo php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-mnemo.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1794 days old (needed 5 days)
• php-net-dns2 (- to 1.5.0-1)
  • Migration status for php-net-dns2 (- to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-net-dns2 would introduce bugs in testing: #1042457
    • autopkgtest for php-net-dns2/1.5.0-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-net-dns2.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1796 days old (needed 5 days)
• php-horde-nag (- to 4.2.19-6)
  • Migration status for php-horde-nag (- to 4.2.19-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-nag would introduce bugs in testing: #1064389
    • autopkgtest for php-horde-nag/4.2.19-6: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-nag pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-nag php-horde-role
    • Depends: php-horde-nag php-horde (not considered)
    • Depends: php-horde-nag php-horde-auth (not considered)
    • Depends: php-horde-nag php-horde-content (not considered)
    • Depends: php-horde-nag php-horde-controller (not considered)
    • Depends: php-horde-nag php-horde-core (not considered)
    • Depends: php-horde-nag php-horde-data (not considered)
    • Depends: php-horde-nag php-horde-date (not considered)
    • Depends: php-horde-nag php-horde-date-parser (not considered)
    • Depends: php-horde-nag php-horde-dav
    • Depends: php-horde-nag php-horde-exception (not considered)
    • Depends: php-horde-nag php-horde-form
    • Depends: php-horde-nag php-horde-group (not considered)
    • Depends: php-horde-nag php-horde-history (not considered)
    • Depends: php-horde-nag php-horde-icalendar (not considered)
    • Depends: php-horde-nag php-horde-mail (not considered)
    • Depends: php-horde-nag php-horde-mime (not considered)
    • Depends: php-horde-nag php-horde-perms (not considered)
    • Depends: php-horde-nag php-horde-prefs (not considered)
    • Depends: php-horde-nag php-horde-routes (not considered)
    • Depends: php-horde-nag php-horde-share (not considered)
    • Depends: php-horde-nag php-horde-support (not considered)
    • Depends: php-horde-nag php-horde-text-filter (not considered)
    • Depends: php-horde-nag php-horde-url (not considered)
    • Depends: php-horde-nag php-horde-util (not considered)
    • Depends: php-horde-nag php-horde-view (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-nag.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1812 days old (needed 5 days)
• rust-core-foundation-sys (- to 0.8.1-1)
  • Migration status for rust-core-foundation-sys (- to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating rust-core-foundation-sys would introduce bugs in testing: #1100533
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rust-core-foundation-sys.html
    • autopkgtest for rust-core-foundation-sys/0.8.1-1: amd64: Pass, arm64: 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
    • 1814 days old (needed 2 days)
• php-horde-content (- to 2.0.6-7)
  • Migration status for php-horde-content (- to 2.0.6-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-content/2.0.6-7: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-content pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-content php-horde-role
    • Depends: php-horde-content php-horde-core (not considered)
    • Depends: php-horde-content php-horde-date (not considered)
    • Depends: php-horde-content php-horde-db (not considered)
    • Depends: php-horde-content php-horde-exception (not considered)
    • Depends: php-horde-content php-horde-injector (not considered)
    • Depends: php-horde-content php-horde-rdo (not considered)
    • Depends: php-horde-content php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-content.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1817 days old (needed 5 days)
• php-horde-text-filter-jsmin (- to 1.0.2-10)
  • Migration status for php-horde-text-filter-jsmin (- to 1.0.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-text-filter-jsmin/1.0.2-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-text-filter-jsmin pear-channels (not considered)
    • Depends: php-horde-text-filter-jsmin php-horde-text-filter (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1822 days old (needed 5 days)
• php-horde-xml-wbxml (- to 2.0.4-2)
  • Migration status for php-horde-xml-wbxml (- to 2.0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-xml-wbxml/2.0.4-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-xml-wbxml pear-channels (not considered)
    • Depends: php-horde-xml-wbxml php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-xml-wbxml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1822 days old (needed 5 days)
• php-horde-javascriptminify-jsmin (- to 1.0.2-9)
  • Migration status for php-horde-javascriptminify-jsmin (- to 1.0.2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-javascriptminify-jsmin/1.0.2-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-javascriptminify-jsmin pear-channels (not considered)
    • Depends: php-horde-javascriptminify-jsmin php-horde-javascriptminify (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1826 days old (needed 5 days)
• php-horde-feed (- to 2.0.4-9)
  • Migration status for php-horde-feed (- to 2.0.4-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-feed/2.0.4-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-feed pear-channels (not considered)
    • Depends: php-horde-feed php-horde-exception (not considered)
    • Depends: php-horde-feed php-horde-http (not considered)
    • Depends: php-horde-feed php-horde-xml-element (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-feed.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1828 days old (needed 5 days)
• php-horde-pdf (- to 2.0.8-2)
  • Migration status for php-horde-pdf (- to 2.0.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-pdf/2.0.8-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-pdf pear-channels (not considered)
    • Depends: php-horde-pdf php-horde-exception (not considered)
    • Depends: php-horde-pdf php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-pdf.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1828 days old (needed 5 days)
• php-horde-xml-element (- to 2.0.4-9)
  • Migration status for php-horde-xml-element (- to 2.0.4-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-xml-element/2.0.4-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-xml-element pear-channels (not considered)
    • Depends: php-horde-xml-element php-horde-exception (not considered)
    • Depends: php-horde-xml-element php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-xml-element.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1829 days old (needed 5 days)
• php-horde-routes (- to 2.0.5-9)
  • Migration status for php-horde-routes (- to 2.0.5-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-routes/2.0.5-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-routes pear-channels (not considered)
    • Depends: php-horde-routes php-horde-exception (not considered)
    • Depends: php-horde-routes php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-routes.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1831 days old (needed 5 days)
• php-horde-spellchecker (- to 2.1.3-9)
  • Migration status for php-horde-spellchecker (- to 2.1.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-spellchecker/2.1.3-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-spellchecker pear-channels (not considered)
    • Depends: php-horde-spellchecker php-horde-exception (not considered)
    • Depends: php-horde-spellchecker php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-spellchecker.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1831 days old (needed 5 days)
• php-horde-timezone (- to 1.1.0-7)
  • Migration status for php-horde-timezone (- to 1.1.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-timezone would introduce bugs in testing: #1089778
    • autopkgtest for php-horde-timezone/1.1.0-7: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-timezone pear-channels (not considered)
    • Depends: php-horde-timezone php-horde-date (not considered)
    • Depends: php-horde-timezone php-horde-icalendar (not considered)
    • Depends: php-horde-timezone php-horde-vfs (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-timezone.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1831 days old (needed 5 days)
• php-horde-image (- to 2.6.1-2)
  • Migration status for php-horde-image (- to 2.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-image/2.6.1-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-image pear-channels (not considered)
    • Depends: php-horde-image php-horde-exception (not considered)
    • Depends: php-horde-image php-horde-stream (not considered)
    • Depends: php-horde-image php-horde-support (not considered)
    • Depends: php-horde-image php-horde-translation (not considered)
    • Depends: php-horde-image php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-image.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1832 days old (needed 5 days)
• php-horde-pack (- to 1.0.7-7)
  • Migration status for php-horde-pack (- to 1.0.7-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-pack/1.0.7-7: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-pack pear-channels (not considered)
    • Depends: php-horde-pack php-horde-compress-fast (not considered)
    • Depends: php-horde-pack php-horde-exception (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-pack.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1832 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
    • 1841 days old (needed 5 days)
• gmanedit (- to 0.4.2-8)
  • Migration status for gmanedit (- to 0.4.2-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gmanedit would introduce bugs in testing: #1075015
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gmanedit.html
    • 1863 days old (needed 5 days)
• nim-unicodedb (- to 0.9.0-2)
  • Migration status for nim-unicodedb (- to 0.9.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nim-unicodedb nim (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-unicodedb.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1864 days old (needed 5 days)
• nim-unicodeplus (- to 0.5.1-2)
  • Migration status for nim-unicodeplus (- to 0.5.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): nim-unicodeplus nim (not considered)
    • Invalidated by build-dependency
    • Depends: nim-unicodeplus nim-unicodedb
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/nim-unicodeplus.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1864 days old (needed 5 days)
• hexchat-otr (- to 0.2.2-3)
  • Migration status for hexchat-otr (- to 0.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hexchat-otr would introduce bugs in testing: #1076888
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hexchat-otr.html
    • 1865 days old (needed 5 days)
• tree-style-tab (- to 3.5.20-1)
  • Migration status for tree-style-tab (- to 3.5.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tree-style-tab would introduce bugs in testing: #1071896
    • tree-style-tab unsatisfiable Build-Depends(-Arch) on amd64: mozilla-devscripts (>= 0.50~)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tree-style-tab.html
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1868 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)
    • 1870 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)
    • 1870 days old (needed 5 days)
• pyjdata (- to 0.3.6-1)
  • Migration status for pyjdata (- to 0.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for pyjdata/0.3.6-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pyjdata.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1871 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• 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)
    • 1874 days old (needed 5 days)
• gnucap-python (- to 0.0.2-1.2)
  • Migration status for gnucap-python (- to 0.0.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-gnucap/amd64 has unsatisfiable dependency
    • python3-gnucap/arm64 has unsatisfiable dependency
    • python3-gnucap/armhf has unsatisfiable dependency
    • python3-gnucap/i386 has unsatisfiable dependency
    • python3-gnucap/ppc64el has unsatisfiable dependency
    • python3-gnucap/riscv64 has unsatisfiable dependency
    • python3-gnucap/s390x has unsatisfiable dependency
    • Updating gnucap-python would introduce bugs in testing: #1067335
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/g/gnucap-python.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1878 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• php-horde-date-parser (- to 2.0.7-2)
  • Migration status for php-horde-date-parser (- to 2.0.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-date-parser/2.0.7-2: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-date-parser pear-channels (not considered)
    • Depends: php-horde-date-parser php-horde-date (not considered)
    • Depends: php-horde-date-parser php-horde-support (not considered)
    • Depends: php-horde-date-parser php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-date-parser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1880 days old (needed 5 days)
• php-horde-listheaders (- to 1.2.5-7)
  • Migration status for php-horde-listheaders (- to 1.2.5-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-listheaders/1.2.5-7: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-listheaders pear-channels (not considered)
    • Depends: php-horde-listheaders php-horde-mail (not considered)
    • Depends: php-horde-listheaders php-horde-translation (not considered)
    • Depends: php-horde-listheaders php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-listheaders.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1881 days old (needed 5 days)
• php-horde-template (- to 2.0.3-10)
  • Migration status for php-horde-template (- to 2.0.3-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-template/2.0.3-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-template pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-template.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1881 days old (needed 5 days)
• cen64 (- to 0.3+git20200723-1)
  • Migration status for cen64 (- to 0.3+git20200723-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cen64 would introduce bugs in testing: #1074875
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cen64.html
    • 1883 days old (needed 5 days)
• mongrel2 (- to 1.12.2-3)
  • Migration status for mongrel2 (- to 1.12.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • mongrel2-core/amd64 has unsatisfiable dependency
    • mongrel2-core/arm64 has unsatisfiable dependency
    • mongrel2-core/armhf has unsatisfiable dependency
    • mongrel2-core/i386 has unsatisfiable dependency
    • mongrel2-core/ppc64el has unsatisfiable dependency
    • mongrel2-core/riscv64 has unsatisfiable dependency
    • mongrel2-core/s390x has unsatisfiable dependency
    • Updating mongrel2 would introduce bugs in testing: #1075866
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mongrel2.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1885 days old (needed 5 days)
• php-horde-compress-fast (- to 1.1.1-10)
  • Migration status for php-horde-compress-fast (- to 1.1.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-compress-fast/1.1.1-10: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-compress-fast pear-channels (not considered)
    • Depends: php-horde-compress-fast php-horde-exception (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-compress-fast.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1886 days old (needed 5 days)
• php-horde-constraint (- to 2.0.3-9)
  • Migration status for php-horde-constraint (- to 2.0.3-9): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-constraint/2.0.3-9: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-constraint pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-constraint.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1886 days old (needed 5 days)
• php-horde-controller (- to 2.0.5-5)
  • Migration status for php-horde-controller (- to 2.0.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-controller/2.0.5-5: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-controller pear-channels (not considered)
    • Depends: php-horde-controller php-horde-exception (not considered)
    • Depends: php-horde-controller php-horde-injector (not considered)
    • Depends: php-horde-controller php-horde-log (not considered)
    • Depends: php-horde-controller php-horde-support (not considered)
    • Depends: php-horde-controller php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-controller.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1886 days old (needed 5 days)
• php-horde-css-parser (- to 1.0.11-8)
  • Migration status for php-horde-css-parser (- to 1.0.11-8): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-css-parser would introduce bugs in testing: #1089771, #1104702
    • autopkgtest for php-horde-css-parser/1.0.11-8: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-css-parser pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-css-parser.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1886 days old (needed 5 days)
• php-horde-lock (- to 2.1.4-7)
  • Migration status for php-horde-lock (- to 2.1.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-lock/2.1.4-7: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-lock pear-channels (not considered)
    • Depends: php-horde-lock php-horde-exception (not considered)
    • Depends: php-horde-lock php-horde-support (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-lock.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1886 days old (needed 5 days)
• fonts-kacst (- to 2.01+mry-15)
  • Migration status for fonts-kacst (- to 2.01+mry-15): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating fonts-kacst would introduce bugs in testing: #1041017
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/fonts-kacst.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1890 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 ♻
    • 1891 days old (needed 5 days)
• php-horde-translation (- to 2.2.2-7)
  • Migration status for php-horde-translation (- to 2.2.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for php-horde-translation/2.2.2-7: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
    • Build-Depends(-Arch): php-horde-translation pear-channels (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-translation.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1891 days old (needed 5 days)
• kytos-sphinx-theme (- to 0.0.1+dfsg-2)
  • Migration status for kytos-sphinx-theme (- to 0.0.1+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating kytos-sphinx-theme would introduce bugs in testing: #1040468
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kytos-sphinx-theme.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1895 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
    • Build-Depends(-Arch): php-horde-whups pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-whups php-horde-role
    • Depends: php-horde-whups php-horde-auth (not considered)
    • Depends: php-horde-whups php-horde-autoloader (not considered)
    • Depends: php-horde-whups php-horde-compress (not considered)
    • Depends: php-horde-whups php-horde-core (not considered)
    • Depends: php-horde-whups php-horde-date (not considered)
    • Depends: php-horde-whups php-horde-db (not considered)
    • Depends: php-horde-whups php-horde-exception (not considered)
    • Depends: php-horde-whups php-horde-form
    • Depends: php-horde-whups php-horde-group (not considered)
    • Depends: php-horde-whups php-horde-mail (not considered)
    • Depends: php-horde-whups php-horde-mime (not considered)
    • Depends: php-horde-whups php-horde-mime-viewer
    • Depends: php-horde-whups php-horde-notification (not considered)
    • Depends: php-horde-whups php-horde-perms (not considered)
    • Depends: php-horde-whups php-horde-prefs (not considered)
    • Depends: php-horde-whups php-horde-scheduler
    • Depends: php-horde-whups php-horde-share (not considered)
    • Depends: php-horde-whups php-horde-support (not considered)
    • Depends: php-horde-whups php-horde-text-filter (not considered)
    • Depends: php-horde-whups php-horde-util (not considered)
    • Depends: php-horde-whups php-horde-vfs (not considered)
    • Depends: php-horde-whups php-horde-view (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-whups.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1903 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-gollem would introduce bugs in testing: #1102708
    • Build-Depends(-Arch): php-horde-gollem pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-gollem php-horde-role
    • Depends: php-horde-gollem php-horde (not considered)
    • Depends: php-horde-gollem php-horde-auth (not considered)
    • Depends: php-horde-gollem php-horde-cache (not considered)
    • Depends: php-horde-gollem php-horde-core (not considered)
    • Depends: php-horde-gollem php-horde-editor
    • Depends: php-horde-gollem php-horde-exception (not considered)
    • Depends: php-horde-gollem php-horde-mime (not considered)
    • Depends: php-horde-gollem php-horde-mime-viewer
    • Depends: php-horde-gollem php-horde-perms (not considered)
    • Depends: php-horde-gollem php-horde-serialize (not considered)
    • Depends: php-horde-gollem php-horde-support (not considered)
    • Depends: php-horde-gollem php-horde-url (not considered)
    • Depends: php-horde-gollem php-horde-util (not considered)
    • Depends: php-horde-gollem php-horde-vfs (not considered)
    • Depends: php-horde-gollem php-horde-view (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 ♻
    • 1904 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
    • Build-Depends(-Arch): php-horde-trean pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-trean php-horde-role
    • Depends: php-horde-trean php-horde-autoloader (not considered)
    • Depends: php-horde-trean php-horde-content (not considered)
    • Depends: php-horde-trean php-horde-controller (not considered)
    • Depends: php-horde-trean php-horde-core (not considered)
    • Depends: php-horde-trean php-horde-date (not considered)
    • Depends: php-horde-trean php-horde-db (not considered)
    • Depends: php-horde-trean php-horde-exception (not considered)
    • Depends: php-horde-trean php-horde-form
    • Depends: php-horde-trean php-horde-notification (not considered)
    • Depends: php-horde-trean php-horde-perms (not considered)
    • Depends: php-horde-trean php-horde-queue
    • Depends: php-horde-trean php-horde-util (not considered)
    • Depends: php-horde-trean php-horde-vfs (not considered)
    • Depends: php-horde-trean php-horde-view (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-trean.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1904 days old (needed 5 days)
• php-horde-scribe (- to 2.0.3-6)
  • Migration status for php-horde-scribe (- to 2.0.3-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-horde-scribe pear-channels (not considered)
    • Invalidated by build-dependency
    • Depends: php-horde-scribe php-horde-thrift
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-scribe.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1906 days old (needed 5 days)
• php-horde-service-facebook (- to 2.0.10-6)
  • Migration status for php-horde-service-facebook (- to 2.0.10-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-service-facebook php-horde-util (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-service-facebook pear-channels (not considered)
    • Depends: php-horde-service-facebook php-horde-exception (not considered)
    • Depends: php-horde-service-facebook php-horde-http (not considered)
    • Depends: php-horde-service-facebook php-horde-support (not considered)
    • Depends: php-horde-service-facebook php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-service-facebook.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1906 days old (needed 5 days)
• php-horde-service-twitter (- to 2.1.6-6)
  • Migration status for php-horde-service-twitter (- to 2.1.6-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-service-twitter php-horde-util (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-service-twitter pear-channels (not considered)
    • Depends: php-horde-service-twitter php-horde-controller (not considered)
    • Depends: php-horde-service-twitter php-horde-exception (not considered)
    • Depends: php-horde-service-twitter php-horde-http (not considered)
    • Depends: php-horde-service-twitter php-horde-oauth
    • Depends: php-horde-service-twitter php-horde-url (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-service-twitter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1906 days old (needed 5 days)
• php-horde-syncml (- to 2.0.7-7)
  • Migration status for php-horde-syncml (- to 2.0.7-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-syncml php-horde-xml-wbxml (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-syncml pear-channels (not considered)
    • Depends: php-horde-syncml php-horde-date (not considered)
    • Depends: php-horde-syncml php-horde-icalendar (not considered)
    • Depends: php-horde-syncml php-horde-log (not considered)
    • Depends: php-horde-syncml php-horde-support (not considered)
    • Depends: php-horde-syncml php-horde-translation (not considered)
    • Depends: php-horde-syncml php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-syncml.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1906 days old (needed 5 days)
• php-horde-thrift (- to 2.0.3-6)
  • Migration status for php-horde-thrift (- to 2.0.3-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-horde-thrift pear-channels (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-thrift.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1906 days old (needed 5 days)
• php-horde-cli (- to 2.3.0-6)
  • Migration status for php-horde-cli (- to 2.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-cli php-horde-translation (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-cli pear-channels (not considered)
    • Depends: php-horde-cli php-horde-support (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-cli.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-cssminify (- to 1.0.4-6)
  • Migration status for php-horde-cssminify (- to 1.0.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-cssminify php-horde-url (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-cssminify pear-channels (not considered)
    • Depends: php-horde-cssminify php-horde-css-parser (not considered)
    • Depends: php-horde-cssminify php-horde-exception (not considered)
    • Depends: php-horde-cssminify php-horde-log (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-cssminify.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 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
    • Build-Depends(-Arch): php-horde-dav pear-channels (not considered)
    • Depends: php-horde-dav php-horde-auth (not considered)
    • Depends: php-horde-dav php-horde-core (not considered)
    • Depends: php-horde-dav php-horde-http (not considered)
    • Depends: php-horde-dav php-horde-stream (not considered)
    • Depends: php-horde-dav php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-dav.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-elasticsearch (- to 1.0.4-6)
  • Migration status for php-horde-elasticsearch (- to 1.0.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-elasticsearch php-horde-http (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-elasticsearch pear-channels (not considered)
    • Depends: php-horde-elasticsearch php-horde-exception (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-elasticsearch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-form (- to 2.0.20-2)
  • Migration status for php-horde-form (- to 2.0.20-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-form php-horde-util (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-form pear-channels (not considered)
    • Depends: php-horde-form php-horde-core (not considered)
    • Depends: php-horde-form php-horde-date (not considered)
    • Depends: php-horde-form php-horde-exception (not considered)
    • Depends: php-horde-form php-horde-mail (not considered)
    • Depends: php-horde-form php-horde-mime (not considered)
    • Depends: php-horde-form php-horde-nls
    • Depends: php-horde-form php-horde-token (not considered)
    • Depends: php-horde-form php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-form.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-groupware would introduce bugs in testing: #1102702, #1102708, #1102714
    • Build-Depends(-Arch): php-horde-groupware pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-groupware php-horde-role
    • Depends: php-horde-groupware php-horde (not considered)
    • Depends: php-horde-groupware php-horde-content (not considered)
    • Depends: php-horde-groupware php-horde-gollem (not considered)
    • Depends: php-horde-groupware php-horde-kronolith (not considered)
    • Depends: php-horde-groupware php-horde-mnemo (not considered)
    • Depends: php-horde-groupware php-horde-nag (not considered)
    • Depends: php-horde-groupware php-horde-timeobjects
    • Depends: php-horde-groupware php-horde-trean
    • Depends: php-horde-groupware php-horde-turba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-groupware.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-imsp (- to 2.0.10-6)
  • Migration status for php-horde-imsp (- to 2.0.10-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-imsp php-horde-util (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-imsp pear-channels (not considered)
    • Depends: php-horde-imsp php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-imsp.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-nls (- to 2.2.1-6)
  • Migration status for php-horde-nls (- to 2.2.1-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-nls php-horde-util (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-nls pear-channels (not considered)
    • Depends: php-horde-nls php-horde-translation (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-nls.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-oauth (- to 2.0.4-6)
  • Migration status for php-horde-oauth (- to 2.0.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-oauth php-horde-util (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-oauth pear-channels (not considered)
    • Depends: php-horde-oauth php-horde-exception (not considered)
    • Depends: php-horde-oauth php-horde-http (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-oauth.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-openxchange (- to 1.0.1-6)
  • Migration status for php-horde-openxchange (- to 1.0.1-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-openxchange php-horde-url (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-openxchange pear-channels (not considered)
    • Depends: php-horde-openxchange php-horde-date (not considered)
    • Depends: php-horde-openxchange php-horde-http (not considered)
    • Depends: php-horde-openxchange php-horde-perms (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-openxchange.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-queue (- to 1.1.5-6)
  • Migration status for php-horde-queue (- to 1.1.5-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-horde-queue pear-channels (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-queue.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-role (- to 1.0.1-17)
  • Migration status for php-horde-role (- to 1.0.1-17): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Build-Depends(-Arch): php-horde-role pear-channels (not considered)
    • Invalidated by build-dependency
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-role.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-scheduler (- to 2.0.3-6)
  • Migration status for php-horde-scheduler (- to 2.0.3-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-scheduler php-horde-vfs (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-scheduler pear-channels (not considered)
    • Depends: php-horde-scheduler php-horde-core (not considered)
    • Depends: php-horde-scheduler php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-scheduler.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-service-urlshortener (- to 2.0.3-6)
  • Migration status for php-horde-service-urlshortener (- to 2.0.3-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-service-urlshortener php-horde-url (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-service-urlshortener pear-channels (not considered)
    • Depends: php-horde-service-urlshortener php-horde-exception (not considered)
    • Depends: php-horde-service-urlshortener php-horde-http (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-service-urlshortener.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-timeobjects (- to 2.1.4-6)
  • Migration status for php-horde-timeobjects (- to 2.1.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
  • Issues preventing migration:
    • Depends: php-horde-timeobjects php-horde-util (not considered)
    • Invalidated by dependency
    • Build-Depends(-Arch): php-horde-timeobjects pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-timeobjects php-horde-role
    • Depends: php-horde-timeobjects php-horde-core (not considered)
    • Depends: php-horde-timeobjects php-horde-date (not considered)
    • Depends: php-horde-timeobjects php-horde-exception (not considered)
    • Depends: php-horde-timeobjects php-horde-url (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-timeobjects.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• php-horde-tree (- to 2.0.5-6)
  • Migration status for php-horde-tree (- to 2.0.5-6): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-tree would introduce bugs in testing: #1059571
    • Build-Depends(-Arch): php-horde-tree pear-channels (not considered)
    • Depends: php-horde-tree php-horde-exception (not considered)
    • Depends: php-horde-tree php-horde-url (not considered)
    • Depends: php-horde-tree php-horde-util (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-tree.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-horde-webmail would introduce bugs in testing: #1101909, #1102702, #1102708, #1102714
    • Build-Depends(-Arch): php-horde-webmail pear-channels (not considered)
    • Build-Depends(-Arch): php-horde-webmail php-horde-role
    • Depends: php-horde-webmail php-horde (not considered)
    • Depends: php-horde-webmail php-horde-content (not considered)
    • Depends: php-horde-webmail php-horde-gollem (not considered)
    • Depends: php-horde-webmail php-horde-imp (not considered)
    • Depends: php-horde-webmail php-horde-ingo (not considered)
    • Depends: php-horde-webmail php-horde-kronolith (not considered)
    • Depends: php-horde-webmail php-horde-mnemo (not considered)
    • Depends: php-horde-webmail php-horde-nag (not considered)
    • Depends: php-horde-webmail php-horde-timeobjects
    • Depends: php-horde-webmail php-horde-trean
    • Depends: php-horde-webmail php-horde-turba (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-horde-webmail.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1907 days old (needed 5 days)
• dpaste (- to 0.4.0-1)
  • Migration status for dpaste (- to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dpaste would introduce bugs in testing: #1082991
    • Build-Depends(-Arch): dpaste opendht (not considered)
    • Depends: dpaste opendht (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dpaste.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 1913 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 ♻
    • 1931 days old (needed 5 days)
• tilde (- to 1.1.2-1)
  • Migration status for tilde (- to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • tilde/amd64 has unsatisfiable dependency
    • tilde/arm64 has unsatisfiable dependency
    • tilde/armhf has unsatisfiable dependency
    • tilde/i386 has unsatisfiable dependency
    • tilde/ppc64el has unsatisfiable dependency
    • tilde/riscv64 has unsatisfiable dependency
    • tilde/s390x has unsatisfiable dependency
    • tilde unsatisfiable Build-Depends(-Arch) on amd64: libtranscript-dev (>= 0.2.0)
    • tilde unsatisfiable Build-Depends(-Arch) on arm64: libtranscript-dev (>= 0.2.0)
    • tilde unsatisfiable Build-Depends(-Arch) on armhf: libtranscript-dev (>= 0.2.0)
    • tilde unsatisfiable Build-Depends(-Arch) on i386: libtranscript-dev (>= 0.2.0)
    • tilde unsatisfiable Build-Depends(-Arch) on ppc64el: libtranscript-dev (>= 0.2.0)
    • tilde unsatisfiable Build-Depends(-Arch) on riscv64: libtranscript-dev (>= 0.2.0)
    • tilde unsatisfiable Build-Depends(-Arch) on s390x: libtranscript-dev (>= 0.2.0)
    • Build-Depends(-Arch): tilde libt3widget (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tilde.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1943 days old (needed 5 days)
• r-cran-fitcoach (- to 1.0-4)
  • Migration status for r-cran-fitcoach (- to 1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Build-Depends(-Arch): r-cran-fitcoach r-cran-gbm (not considered)
    • Depends: r-cran-fitcoach r-cran-gbm (not considered)
  • 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, 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
    • 1949 days old (needed 2 days)
    • Remove hint for (transitive) dependency: blis
• parcimonie (- to 0.12.0-2)
  • Migration status for parcimonie (- to 0.12.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating parcimonie would introduce bugs in testing: #1091033
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/parcimonie.html
    • autopkgtest for parcimonie/0.12.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 1974 days old (needed 2 days)
• syrthes (- to 4.3.5+20200129-dfsg1-1)
  • Migration status for syrthes (- to 4.3.5+20200129-dfsg1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • syrthes-tools/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
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 1978 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• code-saturne (- to 6.0.2-2)
  • Migration status for code-saturne (- to 6.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • code-saturne-bin/amd64 has unsatisfiable dependency
    • code-saturne-bin/arm64 has unsatisfiable dependency
    • code-saturne-bin/armhf has unsatisfiable dependency
    • code-saturne-bin/i386 has unsatisfiable dependency
    • code-saturne-bin/ppc64el has unsatisfiable dependency
    • code-saturne-bin/riscv64 has unsatisfiable dependency
    • code-saturne-bin/s390x has unsatisfiable dependency
    • Updating code-saturne would introduce bugs in testing: #1066231, #1068318
    • code-saturne unsatisfiable Build-Depends(-Arch) on armhf: libopenmpi-dev
    • code-saturne unsatisfiable Build-Depends(-Arch) on i386: libopenmpi-dev
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/code-saturne.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 1979 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
    • Build-Depends(-Arch): cclib-data cclib (not considered)
    • Depends: cclib-data cclib (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 1987 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• 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
    • 1990 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 ♻
    • 1999 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/armhf has unsatisfiable dependency
    • aboot-cross/i386 has unsatisfiable dependency
    • aboot-cross/ppc64el has unsatisfiable dependency
    • aboot-cross/riscv64 has unsatisfiable dependency
    • aboot-cross/s390x has unsatisfiable dependency
    • Updating aboot would introduce bugs in testing: #805988
    • missing build on all
    • arch:all not built yet, autopkgtest delayed
    • Waiting for lintian test results on all - info
  • 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 ♻
    • 2023 days old (needed 5 days)
• cafeobj (- to 1.6.0-2)
  • Migration status for cafeobj (- to 1.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating cafeobj would introduce bugs in testing: #1085008, #1093322
    • cafeobj unsatisfiable Build-Depends(-Arch) on armhf: sbcl
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/cafeobj.html
    • 2040 days old (needed 5 days)
• acpi-override (- to 0.1+nmu1)
  • Migration status for acpi-override (- to 0.1+nmu1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating acpi-override would introduce bugs in testing: #968604
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/acpi-override.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2063 days old (needed 5 days)
• form-history-control (- to 2.5.1.0-1)
  • Migration status for form-history-control (- to 2.5.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating form-history-control would introduce bugs in testing: #1085455
    • webext-form-history-control/amd64 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/arm64 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/armhf has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/i386 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/ppc64el has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/riscv64 has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
    • webext-form-history-control/s390x has unsatisfiable Built-Using on jquery 3.3.1~dfsg-3
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/f/form-history-control.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2077 days old (needed 5 days)
• golang-github-hashicorp-go-getter (- to 1.4.1-1)
  • Migration status for golang-github-hashicorp-go-getter (- to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating golang-github-hashicorp-go-getter would introduce bugs in testing: #1083184, #1111318
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-hashicorp-go-getter.html
    • autopkgtest for golang-github-hashicorp-go-getter/1.4.1-1: amd64: Pass, arm64: Pass, 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
    • 2080 days old (needed 2 days)
• hsail-tools (- to 0~20180830-1)
  • Migration status for hsail-tools (- to 0~20180830-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hsail-tools would introduce bugs in testing: #1101849
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hsail-tools.html
    • 2080 days old (needed 5 days)
• xbattbar (- to 1.4.9-2)
  • Migration status for xbattbar (- to 1.4.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xbattbar would introduce bugs in testing: #1075651
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/x/xbattbar.html
    • 2089 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: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-throttled-throttled/2.2.4-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
    • 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)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-throttled-throttled.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2101 days old (needed 5 days)
• golang-github-ulule-limiter (- to 3.3.3-1)
  • Migration status for golang-github-ulule-limiter (- to 3.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • autopkgtest for golang-github-ulule-limiter/3.3.3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Failed ♻, s390x: Pass
    • Build-Depends(-Arch): golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
    • Depends: golang-github-ulule-limiter golang-github-go-redis-redis (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/golang-github-ulule-limiter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2119 days old (needed 5 days)
• gausssum (- to 3.0.2-2)
  • Migration status for gausssum (- to 3.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Depends: gausssum cclib (not considered)
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gausssum.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2138 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• android-platform-external-nist-sip (- to 9.0.0+r35-1.1)
  • Migration status for android-platform-external-nist-sip (- to 9.0.0+r35-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating android-platform-external-nist-sip would introduce bugs in testing: #1065522
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/android-platform-external-nist-sip.html
    • 2154 days old (needed 5 days)
• gphoto2-cffi (- to 0.4.3~a1-1.1)
  • Migration status for gphoto2-cffi (- to 0.4.3~a1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating gphoto2-cffi would introduce bugs in testing: #1091277
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gphoto2-cffi.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2157 days old (needed 5 days)
• pymia (- to 0.1.9-2.1)
  • Migration status for pymia (- to 0.1.9-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • python3-mia/amd64 has unsatisfiable dependency
    • python3-mia/arm64 has unsatisfiable dependency
    • python3-mia/armhf has unsatisfiable dependency
    • python3-mia/i386 has unsatisfiable dependency
    • python3-mia/ppc64el has unsatisfiable dependency
    • python3-mia/riscv64 has unsatisfiable dependency
    • python3-mia/s390x has unsatisfiable dependency
    • Build-Depends(-Arch): pymia mia (not considered)
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pymia.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • Waiting for reproducibility test results on amd64 - info ♻
    • Waiting for reproducibility test results on arm64 - info ♻
    • 2158 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• tsung (- to 1.7.0-3.1)
  • Migration status for tsung (- to 1.7.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tsung would introduce bugs in testing: #1098720
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tsung.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2181 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• hydroffice.bag (- to 0.2.15-3)
  • Migration status for hydroffice.bag (- to 0.2.15-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating hydroffice.bag would introduce bugs in testing: #1079963, #993003
    • autopkgtest for hydroffice.bag/0.2.15-3: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/h/hydroffice.bag.html
    • 2216 days old (needed 5 days)
    • Remove hint for (transitive) dependency: blis
• php-pclzip (- to 2.8.2-5)
  • Migration status for php-pclzip (- to 2.8.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating php-pclzip would introduce bugs in testing: #1093433
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/php-pclzip.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2222 days old (needed 5 days)
• pear-channels (- to 0~20190819-1)
  • Migration status for pear-channels (- to 0~20190819-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pear-channels would introduce bugs in testing: #1093434
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pear-channels.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2223 days old (needed 5 days)
• pytest-salt (- to 2019.6.13-1)
  • Migration status for pytest-salt (- to 2019.6.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating pytest-salt would introduce bugs in testing: #1074682
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/pytest-salt.html
    • autopkgtest for pytest-salt/2019.6.13-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 2264 days old (needed 5 days)
• dnssecjava (- to 1.1.3-3)
  • Migration status for dnssecjava (- to 1.1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating dnssecjava would introduce bugs in testing: #1095340
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/d/dnssecjava.html
    • 2394 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/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
    • 2411 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
    • 2413 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: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-trust-webcrypto.html
    • 2417 days old (needed 5 days)
• sqwebmail-de (- to 6.0.0-1)
  • Migration status for sqwebmail-de (- to 6.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sqwebmail-de would introduce bugs in testing: #1093360
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sqwebmail-de.html
    • 2427 days old (needed 5 days)
    • Remove hint for (transitive) dependency: bcron
• 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 ♻
    • 2448 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, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2451 days old (needed 2 days)
• sn (- to 0.3.8-12)
  • Migration status for sn (- to 0.3.8-12): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sn would introduce bugs in testing: #1075519
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/s/sn.html
    • 2518 days old (needed 5 days)
    • Remove hint for (transitive) dependency: bcron
• chessx (- to 1.4.6-2)
  • Migration status for chessx (- to 1.4.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating chessx would introduce bugs in testing: #1074880
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/chessx.html
    • 2571 days old (needed 5 days)
• globjects (- to 1.1.0-3)
  • Migration status for globjects (- to 1.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libglobjects1/amd64 has unsatisfiable dependency
    • libglobjects1/arm64 has unsatisfiable dependency
    • libglobjects1/armhf has unsatisfiable dependency
    • libglobjects1/i386 has unsatisfiable dependency
    • libglobjects1/ppc64el has unsatisfiable dependency
    • libglobjects1/riscv64 has unsatisfiable dependency
    • libglobjects1/s390x has unsatisfiable dependency
    • Updating globjects would introduce bugs in testing: #1090229
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/g/globjects.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch i386, not running autopkgtest there
    • uninstallable on arch ppc64el, not running autopkgtest there
    • uninstallable on arch riscv64, not running autopkgtest there
    • uninstallable on arch s390x, not running autopkgtest there
    • 2635 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 ♻
    • 2662 days old (needed 5 days)
• ctioga2 (- to 0.14.1-2)
  • Migration status for ctioga2 (- to 0.14.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating ctioga2 would introduce bugs in testing: #1094131
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/c/ctioga2.html
    • autopkgtest for ctioga2/0.14.1-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • 2714 days old (needed 5 days)
• whowatch (- to 1.8.6-1)
  • Migration status for whowatch (- to 1.8.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating whowatch would introduce bugs in testing: #1091295
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/w/whowatch.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2719 days old (needed 5 days)
• sqlcl-package (- to 0.1.1)
  • Migration status for sqlcl-package (- to 0.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sqlcl-package would introduce bugs in testing: #1108546
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for sqlcl-package/0.1.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2757 days old (needed 2 days)
• metis-edf (- to 4.1-2-4)
  • Migration status for metis-edf (- to 4.1-2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating metis-edf would introduce bugs in testing: #1066955
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2794 days old (needed 5 days)
• sqldeveloper-package (- to 0.5.4)
  • Migration status for sqldeveloper-package (- to 0.5.4): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating sqldeveloper-package would introduce bugs in testing: #1029716
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • autopkgtest for sqldeveloper-package/0.5.4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
    • Required age reduced by 3 days because of autopkgtest
    • 2808 days old (needed 2 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
    • 2814 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
    • 2816 days old (needed 5 days)
• tz-converter (- to 1.0.1-1)
  • Migration status for tz-converter (- to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating tz-converter would introduce bugs in testing: #1038851
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/t/tz-converter.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2818 days old (needed 5 days)
• audiotools (- to 3.1.1-1.1)
  • Migration status for audiotools (- to 3.1.1-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating audiotools would introduce bugs in testing: #1080546, #1098528
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/audiotools.html
    • 2866 days old (needed 5 days)
• resolvconf-admin (- to 0.3-1)
  • Migration status for resolvconf-admin (- to 0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating resolvconf-admin would introduce bugs in testing: #1108778
    • autopkgtest for resolvconf-admin/0.3-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, ppc64el: Failed ♻, riscv64: Failed ♻, s390x: Failed ♻
  • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/r/resolvconf-admin.html
    • Reproducible on amd64 - info ♻
    • Reproducible on arm64 - info ♻
    • 2882 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 ♻
    • 2954 days old (needed 5 days)
• os8 (- to 2.1-7)
  • Migration status for os8 (- to 2.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating os8 would introduce bugs in testing: #1093347
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 2967 days old (needed 5 days)
• spellcast (- to 1.0-22)
  • Migration status for spellcast (- to 1.0-22): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating spellcast would introduce bugs in testing: #1077895
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 3308 days old (needed 5 days)
• ecere-sdk (- to 0.44.15-1)
  • Migration status for ecere-sdk (- to 0.44.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • libedasqlite0/amd64 has unsatisfiable dependency
    • libedasqlite0/arm64 has unsatisfiable dependency
    • libecere0/armhf has unsatisfiable dependency
    • libecereaudio0/armhf has unsatisfiable dependency
    • libedasqlite0/armhf has unsatisfiable dependency
    • libecere0/i386 has unsatisfiable dependency
    • libedasqlite0/i386 has unsatisfiable dependency
    • libedasqlite0/ppc64el has unsatisfiable dependency
    • libedasqlite0/s390x has unsatisfiable dependency
    • Updating ecere-sdk would introduce bugs in testing: #1102987, #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 armhf: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on i386: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on ppc64el: libgl1-mesa-glx
    • ecere-sdk unsatisfiable Build-Depends(-Arch) on s390x: libgl1-mesa-glx
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/e/ecere-sdk.html
    • uninstallable on arch amd64, not running autopkgtest there
    • uninstallable on arch arm64, not running autopkgtest there
    • uninstallable on arch 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 ♻
    • 3332 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
    • 3434 days old (needed 5 days)
• xserver-xorg-video-ivtvdev (- to 1.1.2-2)
  • Migration status for xserver-xorg-video-ivtvdev (- to 1.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
    • Updating xserver-xorg-video-ivtvdev would introduce bugs in testing: #1078229
  • Additional info:
    • Cannot be tested by piuparts (not a blocker) - (no link yet)
    • 4379 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)
    • 4412 days old (needed 5 days)